[asterisk-users] TDM400 FXO stopped working

[Michael L. Young]

----- Original Message -----
> From: "Remco Barendse" <asterisk at barendse.to>
> To: "Asterisk Users Mailing List - Non-Commercial Discussion" <asterisk-users at lists.digium.com>
> Sent: Friday, September 23, 2011 5:27:27 AM
> Subject: [asterisk-users] TDM400 FXO stopped working
> Hi list
> 
> I have 2 servers with a TDM400 card, port 1 populated by an FXO (red)
> module), port 4 populated with an FXS module. I am using dahdi
> linux and tools 2.5.0.1. The servers are running CentOS 4 and the
> other
> box CentOS 6.
> 
> Both modules have been working fine but recently stopped working, when
> i
> start dahdi with just FXS enabled everything is fine.
> 
> This is the error i get :
> Loading DAHDI hardware modules:
> wctdm: [ OK ]
> 
> Running dahdi_cfg: DAHDI_CHANCONFIG failed on channel 1: Invalid
> argument
> (22)
> Selected signaling not supported
> Possible causes:
> FXO signaling is being used on a FXO interface (use a FXS
> signaling variant)
> RBS signaling is being used on a E1 CCS span
> Signaling is being assigned to channel 16 of an E1 CAS span
> [FAILED]
> 
> 
> This is in my system.conf :
> fxoks=1
> echocanceller=mg2,1
> # channel 2, WCTDM/4/1, no module.
> # channel 3, WCTDM/4/2, no module.
> fxsks=4
> echocanceller=mg2,4
> 
> # Global data
> 
> loadzone = nl
> defaultzone = nl

I think the clue is actually right there in the error message.

You say that port 1 is an FXO module?  Then your signaling is set wrong.  The signaling should be fxsks.

For port 4, it should be fxoks.

Remember, that in the configuration files, the signaling option used is opposite of what the module is.

Regards,
Michael Young
(elguero)