Re: [asterisk-users] TDM400 FXO stopped working
On Mon, 26 Sep 2011, Michael L. Young wrote: 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) I think somehow the module is not recognized. Switching the signalling types doesn't help, i get the same error. Running dahdi_genconf generates this : # Span 1: WCTDM/4 "Wildcard TDM400P REV E/F Board 5" (MASTER) # channel 1, WCTDM/4/0, no module. # channel 2, WCTDM/4/1, no module. # channel 3, WCTDM/4/2, no module. fxsks=4 echocanceller=mg2,4 -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] TDM400 FXO stopped working
- Original Message - > From: "Remco Barendse" > To: "Asterisk Users Mailing List - Non-Commercial Discussion" > > 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) -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] TDM400 FXO stopped working
Remco, Please try temporarily removing all WCTDM parameters you might have in /etc/modprobe.d/dahdi.conf. Then try the same process. You also may want to try "service dahdi restart" or equivalent for your distribution. If none helps I would file a bug report. Regards, Vladimir On 9/26/2011 3:24 AM, Remco Barendse wrote: > Hi Vladimir, > > I tried the steps as you wrote them but i just get the same error : > Channel map: > > Channel 01: FXO Kewlstart (Default) (Echo Canceler: mg2) (Slaves: 01) > Channel 04: FXS Kewlstart (Default) (Echo Canceler: mg2) (Slaves: 04) > > 2 channels to configure. > > Changing signalling on channel 1 from Unused to FXO Kewlstart > 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 > > > The config i used has been working for years, i wonder what changed. > > Thanks!! > > Best regards, Remco > > On Sat, 24 Sep 2011, Vladimir Mikhelson wrote: > >> Remco, >> >> In my experience something could have gone wrong with the parameters >> you pass to WCTDM driver. >> >> You may want to check your /etc/modprobe.d/dahdi.conf >> >> Try loading the driver manually as follows: >> >> 1. Stop Asterisk >> 2. modprobe -r wctdm >> 3. modprobe wctdm >> 4. dahdi_cfg -vvv >> >> Good luck, >> Vladimir >> >> >> >> On 9/23/2011 4:27 AM, Remco Barendse wrote: >>> 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 >>> >>> >>> When i run dahdi_genconf it doesn't detect the module either : >>> # Autogenerated by /usr/sbin/dahdi_genconf on Fri Sep 23 11:24:16 2011 >>> # Span 1: WCTDM/4 "Wildcard TDM400P REV E/F Board 5" (MASTER) >>> # channel 1, WCTDM/4/0, no module. >>> # channel 2, WCTDM/4/1, no module. >>> # channel 3, WCTDM/4/2, no module. >>> fxsks=4 >>> echocanceller=mg2,4 >>> >>> >>> I already replaced both FXO modules with new ones but without result. >>> >>> Ideas anyone? >>> >>> -- >>> _ >>> -- Bandwidth and Colocation Provided by http://www.api-digital.com -- >>> New to Asterisk? Join us for a live introductory webinar every Thurs: >>> http://www.asterisk.org/hello >>> >>> asterisk-users mailing list >>> To UNSUBSCRIBE or update options visit: >>> http://lists.digium.com/mailman/listinfo/asterisk-users >>> >> >> -- >> _ >> -- Bandwidth and Colocation Provided by http://www.api-digital.com -- >> New to Asterisk? Join us for a live introductory webinar every Thurs: >> http://www.asterisk.org/hello >> >> asterisk-users mailing list >> To UNSUBSCRIBE or update options visit: >> http://lists.digium.com/mailman/listinfo/asterisk-users >> > > -- > _ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > New to Asterisk? Join us for a live introductory webinar every Thurs: > http://www.asterisk.org/hello > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] TDM400 FXO stopped working
Hi Vladimir, I tried the steps as you wrote them but i just get the same error : Channel map: Channel 01: FXO Kewlstart (Default) (Echo Canceler: mg2) (Slaves: 01) Channel 04: FXS Kewlstart (Default) (Echo Canceler: mg2) (Slaves: 04) 2 channels to configure. Changing signalling on channel 1 from Unused to FXO Kewlstart 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 The config i used has been working for years, i wonder what changed. Thanks!! Best regards, Remco On Sat, 24 Sep 2011, Vladimir Mikhelson wrote: Remco, In my experience something could have gone wrong with the parameters you pass to WCTDM driver. You may want to check your /etc/modprobe.d/dahdi.conf Try loading the driver manually as follows: 1. Stop Asterisk 2. modprobe -r wctdm 3. modprobe wctdm 4. dahdi_cfg -vvv Good luck, Vladimir On 9/23/2011 4:27 AM, Remco Barendse wrote: 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 When i run dahdi_genconf it doesn't detect the module either : # Autogenerated by /usr/sbin/dahdi_genconf on Fri Sep 23 11:24:16 2011 # Span 1: WCTDM/4 "Wildcard TDM400P REV E/F Board 5" (MASTER) # channel 1, WCTDM/4/0, no module. # channel 2, WCTDM/4/1, no module. # channel 3, WCTDM/4/2, no module. fxsks=4 echocanceller=mg2,4 I already replaced both FXO modules with new ones but without result. Ideas anyone? -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] TDM400 FXO stopped working
Remco, In my experience something could have gone wrong with the parameters you pass to WCTDM driver. You may want to check your /etc/modprobe.d/dahdi.conf Try loading the driver manually as follows: 1. Stop Asterisk 2. modprobe -r wctdm 3. modprobe wctdm 4. dahdi_cfg -vvv Good luck, Vladimir On 9/23/2011 4:27 AM, Remco Barendse wrote: > 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 > > > When i run dahdi_genconf it doesn't detect the module either : > # Autogenerated by /usr/sbin/dahdi_genconf on Fri Sep 23 11:24:16 2011 > # Span 1: WCTDM/4 "Wildcard TDM400P REV E/F Board 5" (MASTER) > # channel 1, WCTDM/4/0, no module. > # channel 2, WCTDM/4/1, no module. > # channel 3, WCTDM/4/2, no module. > fxsks=4 > echocanceller=mg2,4 > > > I already replaced both FXO modules with new ones but without result. > > Ideas anyone? > > -- > _ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > New to Asterisk? Join us for a live introductory webinar every Thurs: > http://www.asterisk.org/hello > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[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 When i run dahdi_genconf it doesn't detect the module either : # Autogenerated by /usr/sbin/dahdi_genconf on Fri Sep 23 11:24:16 2011 # Span 1: WCTDM/4 "Wildcard TDM400P REV E/F Board 5" (MASTER) # channel 1, WCTDM/4/0, no module. # channel 2, WCTDM/4/1, no module. # channel 3, WCTDM/4/2, no module. fxsks=4 echocanceller=mg2,4 I already replaced both FXO modules with new ones but without result. Ideas anyone? -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
