Re: [Asterisk-Users] TDM400P problems with 1 FXS, 1 FXO
David, Not sure if you already got a reply or not - but it looks to me like your FXO module is on port 3 - not 2 (see the dmesg output). Give that a try. HTH- Ben On Wednesday, May 19, 2004, at 12:51 PM, David Creemer wrote: Hi- I'm totally stumped configuring my TDM400P with one FXS and one FXO module. Before I got the FXO module, I used to have an X101P, and everything was working very well. Now * doesn't seem to recognize the FXO channel. I've searched the wiki and the list archives. Stock Debian 3.0 stable installation. Any advice? Thanks. -- David Here's my configuration: modprobe zaptel modprobe wcfxs report no errors. box:/etc/asterisk# ztcfg -vv Zaptel Configuration == Channel map: Channel 01: FXO Kewlstart (Default) (Slaves: 01) Channel 02: FXS Kewlstart (Default) (Slaves: 02) 2 channels configured. --- So it looks like things are OK so far. Here's the relevant portion of my zaptel.conf: defaultzone=us # load FXO X100P channel 1, kewlstart signalling # turned off, card removed #fxsks=1 # load FXS TDM400P channel 1, kewlstart signalling fxoks=1 # load FXO TDM400P channel 2, kewlstart signalling fxsks=2 And here's what dmesg reports: Zapata Telephony Interface Registered on major 196 PCI: Found IRQ 12 for device 00:09.0 Freshmaker version: 63 Freshmaker passed register test Module 0: Installed -- AUTO FXS Module 1: Not installed Module 2: Installed -- AUTO FXO Module 3: Not installed Found a Wildcard TDM: Wildcard TDM400P REV E/F (4 modules) Registered tone zone 0 (United States / North America) --- the relevant portions of my zapata.conf are: [channels] language=en usecallerid=yes hidecallerid=no callwaiting=yes usecallingpres=yes callwaitingcallerid=yes callreturn=yes echocancel=yes echocancelwhenbridged=yes busydetect=yes callprogress=yes ; interfaces for internal analog phones signalling=fxo_ks threewaycalling=yes transfer=yes group=1 context=from-internal callerid="Creemer" <01> channel => 1 mailbox=01 ; interfaces to the external PSTN line signalling=fxs_ks context=from-pstn group=2 channel => 2 --- starting asterisk gives: [chan_zap.so] => (Zapata Telephony w/PRI) == Parsing '/etc/asterisk/zapata.conf': Found May 19 10:42:20 DEBUG[1024]: chan_zap.c:1077 update_conf: Updated conferencing on 1, with 0 conference users -- Registered channel 1, FXO Kewlstart signalling May 19 10:42:20 WARNING[1024]: chan_zap.c:665 zt_open: Unable to specify channel 2: No such device May 19 10:42:20 ERROR[1024]: chan_zap.c:5340 mkintf: Unable to open channel 2: No such device here = 0, tmp->channel = 2, channel = 2 May 19 10:42:20 ERROR[1024]: chan_zap.c:7376 setup_zap: Unable to register channel '2' May 19 10:42:20 WARNING[1024]: loader.c:313 ast_load_resource: chan_zap.so: load_module failed, returning -1 == Unregistered channel type 'Tor' == Unregistered channel type 'Zap' -- Unregistered channel 1 -- Unregistered channel 2 May 19 10:42:20 WARNING[1024]: loader.c:408 load_modules: Loading module chan_zap.so failed! ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] TDM400P problems with 1 FXS, 1 FXO
Following up with a thought experiment. If I start with one TDM400P, FXS module in slot 1, FXO module in slot 3, my zaptel.conf file looks like this: fxoks=1 fxsks=3 If I were to put an X101P in this machine, and load the wcfxo module *first*, what would the zaptel.conf channel list look like? This? fxsks=1,4 fxoks=2 If I load wcfxo *after* wcfxs, would it be this?: fxoks=1 fxsks=3,5 Curious. -- David On May 19, 2004, at 2:15 PM, David Creemer wrote: Problem fixed. Here's the solutions for those who care: - TDM400P has slots 1,2,3,4 - "channel" in the zaptel.conf must match the slot the card is in. I have the daughter cards in slot 1 and 3. BUT here's the kicker: if the zaptel.conf configures channel 1 and 2 (not 3). No error is reported, and ztcfg -vv reports: Channel 01: FXO Kewlstart (Default) (Slaves: 01) Channel 02: FXS Kewlstart (Default) (Slaves: 02) 2 channels configured. If zaptel.conf configures channels 1 and 3 (not 2), ztcfg-vv reports: Channel 01: FXO Kewlstart (Default) (Slaves: 01) Channel 03: FXS Kewlstart (Default) (Slaves: 03) Which is the right answer. -- David On May 19, 2004, at 1:36 PM, Rich Adamson wrote: Looks to me like you have 1 and 3 installed, not 1 and 2. Look close at your dmesg output. Hi- I'm totally stumped configuring my TDM400P with one FXS and one FXO module. Before I got the FXO module, I used to have an X101P, and everything was working very well. Now * doesn't seem to recognize the FXO channel. I've searched the wiki and the list archives. Stock Debian 3.0 stable installation. Any advice? Thanks. -- David Here's my configuration: modprobe zaptel modprobe wcfxs report no errors. box:/etc/asterisk# ztcfg -vv Zaptel Configuration == Channel map: Channel 01: FXO Kewlstart (Default) (Slaves: 01) Channel 02: FXS Kewlstart (Default) (Slaves: 02) 2 channels configured. --- So it looks like things are OK so far. Here's the relevant portion of my zaptel.conf: defaultzone=us # load FXO X100P channel 1, kewlstart signalling # turned off, card removed #fxsks=1 # load FXS TDM400P channel 1, kewlstart signalling fxoks=1 # load FXO TDM400P channel 2, kewlstart signalling fxsks=2 And here's what dmesg reports: Zapata Telephony Interface Registered on major 196 PCI: Found IRQ 12 for device 00:09.0 Freshmaker version: 63 Freshmaker passed register test Module 0: Installed -- AUTO FXS Module 1: Not installed Module 2: Installed -- AUTO FXO Module 3: Not installed Found a Wildcard TDM: Wildcard TDM400P REV E/F (4 modules) Registered tone zone 0 (United States / North America) --- the relevant portions of my zapata.conf are: [channels] language=en usecallerid=yes hidecallerid=no callwaiting=yes usecallingpres=yes callwaitingcallerid=yes callreturn=yes echocancel=yes echocancelwhenbridged=yes busydetect=yes callprogress=yes ; interfaces for internal analog phones signalling=fxo_ks threewaycalling=yes transfer=yes group=1 context=from-internal callerid="Creemer" <01> channel => 1 mailbox=01 ; interfaces to the external PSTN line signalling=fxs_ks context=from-pstn group=2 channel => 2 --- starting asterisk gives: [chan_zap.so] => (Zapata Telephony w/PRI) == Parsing '/etc/asterisk/zapata.conf': Found May 19 10:42:20 DEBUG[1024]: chan_zap.c:1077 update_conf: Updated conferencing on 1, with 0 conference users -- Registered channel 1, FXO Kewlstart signalling May 19 10:42:20 WARNING[1024]: chan_zap.c:665 zt_open: Unable to specify channel 2: No such device May 19 10:42:20 ERROR[1024]: chan_zap.c:5340 mkintf: Unable to open channel 2: No such device here = 0, tmp->channel = 2, channel = 2 May 19 10:42:20 ERROR[1024]: chan_zap.c:7376 setup_zap: Unable to register channel '2' May 19 10:42:20 WARNING[1024]: loader.c:313 ast_load_resource: chan_zap.so: load_module failed, returning -1 == Unregistered channel type 'Tor' == Unregistered channel type 'Zap' -- Unregistered channel 1 -- Unregistered channel 2 May 19 10:42:20 WARNING[1024]: loader.c:408 load_modules: Loading module chan_zap.so failed! ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ---End of Original Message- ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___
Re: [Asterisk-Users] TDM400P problems with 1 FXS, 1 FXO
Looks to me like you have 1 and 3 installed, not 1 and 2. Look close at your dmesg output. > Hi- > > I'm totally stumped configuring my TDM400P with one FXS and one FXO > module. Before I got the FXO module, I used to have an X101P, and > everything was working very well. Now * doesn't seem to recognize the > FXO channel. I've searched the wiki and the list archives. Stock Debian > 3.0 stable installation. Any advice? Thanks. > > -- David > > > Here's my configuration: > > modprobe zaptel > modprobe wcfxs > > report no errors. > > box:/etc/asterisk# ztcfg -vv > > Zaptel Configuration > == > > > Channel map: > > Channel 01: FXO Kewlstart (Default) (Slaves: 01) > Channel 02: FXS Kewlstart (Default) (Slaves: 02) > > 2 channels configured. > > --- > > So it looks like things are OK so far. Here's the relevant portion of > my zaptel.conf: > > defaultzone=us > # load FXO X100P channel 1, kewlstart signalling > # turned off, card removed > #fxsks=1 > # load FXS TDM400P channel 1, kewlstart signalling > fxoks=1 > # load FXO TDM400P channel 2, kewlstart signalling > fxsks=2 > > > And here's what dmesg reports: > > Zapata Telephony Interface Registered on major 196 > PCI: Found IRQ 12 for device 00:09.0 > Freshmaker version: 63 > Freshmaker passed register test > Module 0: Installed -- AUTO FXS > Module 1: Not installed > Module 2: Installed -- AUTO FXO > Module 3: Not installed > Found a Wildcard TDM: Wildcard TDM400P REV E/F (4 modules) > Registered tone zone 0 (United States / North America) > > --- > > the relevant portions of my zapata.conf are: > > [channels] > language=en > usecallerid=yes > hidecallerid=no > callwaiting=yes > usecallingpres=yes > callwaitingcallerid=yes > callreturn=yes > echocancel=yes > echocancelwhenbridged=yes > busydetect=yes > callprogress=yes > > ; interfaces for internal analog phones > signalling=fxo_ks > threewaycalling=yes > transfer=yes > group=1 > context=from-internal > callerid="Creemer" <01> > channel => 1 > mailbox=01 > > ; interfaces to the external PSTN line > signalling=fxs_ks > context=from-pstn > group=2 > channel => 2 > > --- > > starting asterisk gives: > [chan_zap.so] => (Zapata Telephony w/PRI) >== Parsing '/etc/asterisk/zapata.conf': Found > May 19 10:42:20 DEBUG[1024]: chan_zap.c:1077 update_conf: Updated > conferencing on 1, with 0 conference users > -- Registered channel 1, FXO Kewlstart signalling > May 19 10:42:20 WARNING[1024]: chan_zap.c:665 zt_open: Unable to > specify channel 2: No such device > May 19 10:42:20 ERROR[1024]: chan_zap.c:5340 mkintf: Unable to open > channel 2: No such device > here = 0, tmp->channel = 2, channel = 2 > May 19 10:42:20 ERROR[1024]: chan_zap.c:7376 setup_zap: Unable to > register channel '2' > May 19 10:42:20 WARNING[1024]: loader.c:313 ast_load_resource: > chan_zap.so: load_module failed, returning -1 >== Unregistered channel type 'Tor' >== Unregistered channel type 'Zap' > -- Unregistered channel 1 > -- Unregistered channel 2 > May 19 10:42:20 WARNING[1024]: loader.c:408 load_modules: Loading > module chan_zap.so failed! > > ___ > Asterisk-Users mailing list > [EMAIL PROTECTED] > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: >http://lists.digium.com/mailman/listinfo/asterisk-users ---End of Original Message- ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] TDM400P problems with 1 FXS, 1 FXO
Problem fixed. Here's the solutions for those who care: - TDM400P has slots 1,2,3,4 - "channel" in the zaptel.conf must match the slot the card is in. I have the daughter cards in slot 1 and 3. BUT here's the kicker: if the zaptel.conf configures channel 1 and 2 (not 3). No error is reported, and ztcfg -vv reports: Channel 01: FXO Kewlstart (Default) (Slaves: 01) Channel 02: FXS Kewlstart (Default) (Slaves: 02) 2 channels configured. If zaptel.conf configures channels 1 and 3 (not 2), ztcfg-vv reports: Channel 01: FXO Kewlstart (Default) (Slaves: 01) Channel 03: FXS Kewlstart (Default) (Slaves: 03) Which is the right answer. -- David On May 19, 2004, at 1:36 PM, Rich Adamson wrote: Looks to me like you have 1 and 3 installed, not 1 and 2. Look close at your dmesg output. Hi- I'm totally stumped configuring my TDM400P with one FXS and one FXO module. Before I got the FXO module, I used to have an X101P, and everything was working very well. Now * doesn't seem to recognize the FXO channel. I've searched the wiki and the list archives. Stock Debian 3.0 stable installation. Any advice? Thanks. -- David Here's my configuration: modprobe zaptel modprobe wcfxs report no errors. box:/etc/asterisk# ztcfg -vv Zaptel Configuration == Channel map: Channel 01: FXO Kewlstart (Default) (Slaves: 01) Channel 02: FXS Kewlstart (Default) (Slaves: 02) 2 channels configured. --- So it looks like things are OK so far. Here's the relevant portion of my zaptel.conf: defaultzone=us # load FXO X100P channel 1, kewlstart signalling # turned off, card removed #fxsks=1 # load FXS TDM400P channel 1, kewlstart signalling fxoks=1 # load FXO TDM400P channel 2, kewlstart signalling fxsks=2 And here's what dmesg reports: Zapata Telephony Interface Registered on major 196 PCI: Found IRQ 12 for device 00:09.0 Freshmaker version: 63 Freshmaker passed register test Module 0: Installed -- AUTO FXS Module 1: Not installed Module 2: Installed -- AUTO FXO Module 3: Not installed Found a Wildcard TDM: Wildcard TDM400P REV E/F (4 modules) Registered tone zone 0 (United States / North America) --- the relevant portions of my zapata.conf are: [channels] language=en usecallerid=yes hidecallerid=no callwaiting=yes usecallingpres=yes callwaitingcallerid=yes callreturn=yes echocancel=yes echocancelwhenbridged=yes busydetect=yes callprogress=yes ; interfaces for internal analog phones signalling=fxo_ks threewaycalling=yes transfer=yes group=1 context=from-internal callerid="Creemer" <01> channel => 1 mailbox=01 ; interfaces to the external PSTN line signalling=fxs_ks context=from-pstn group=2 channel => 2 --- starting asterisk gives: [chan_zap.so] => (Zapata Telephony w/PRI) == Parsing '/etc/asterisk/zapata.conf': Found May 19 10:42:20 DEBUG[1024]: chan_zap.c:1077 update_conf: Updated conferencing on 1, with 0 conference users -- Registered channel 1, FXO Kewlstart signalling May 19 10:42:20 WARNING[1024]: chan_zap.c:665 zt_open: Unable to specify channel 2: No such device May 19 10:42:20 ERROR[1024]: chan_zap.c:5340 mkintf: Unable to open channel 2: No such device here = 0, tmp->channel = 2, channel = 2 May 19 10:42:20 ERROR[1024]: chan_zap.c:7376 setup_zap: Unable to register channel '2' May 19 10:42:20 WARNING[1024]: loader.c:313 ast_load_resource: chan_zap.so: load_module failed, returning -1 == Unregistered channel type 'Tor' == Unregistered channel type 'Zap' -- Unregistered channel 1 -- Unregistered channel 2 May 19 10:42:20 WARNING[1024]: loader.c:408 load_modules: Loading module chan_zap.so failed! ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ---End of Original Message- ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] TDM400P problems with 1 FXS, 1 FXO
I am getting a similar problem with a TDM400P with 4 FXO ports, Module 1 not working properly, IE not picking up the calls at all. I have 3 TDM400P cards, 1 loaded with 4 FXO ports, 2 loaded with 4 FXS ports. Does anyone know if this problem with port 1 is only with the FXO modules or if it's also with FXS modules... I'm wondering if I should be moving ports around on the card not to use FXO ports on any port#1, even though it would be pretty confusing when connecting lines on the cards. Also could this problem with port #1 be associated with the Power Alarm on module 1, resetting? Thank you! Sylvain Gagnon [EMAIL PROTECTED] > There is a known problem with the first port on the TDM400P. For me, the > problem resulted in randomly dropped calls on the FXO port, which was > plugged into position 1. Since you only have two daughterboards, try > using positions 2-3-4 and don't use position 1, and see of that solves > your problem. > > Bruce Komito > High Sierra Networks, Inc. > www.servers-r-us.com > (775) 284-5800 ext 115 > > > On Wed, 19 May 2004, David Creemer wrote: > >> Hi- >> >> I'm totally stumped configuring my TDM400P with one FXS and one FXO >> module. Before I got the FXO module, I used to have an X101P, and >> everything was working very well. Now * doesn't seem to recognize the >> FXO channel. I've searched the wiki and the list archives. Stock Debian >> 3.0 stable installation. Any advice? Thanks. >> >> -- David >> >> >> Here's my configuration: >> >> modprobe zaptel >> modprobe wcfxs >> >> report no errors. >> >> box:/etc/asterisk# ztcfg -vv >> >> Zaptel Configuration >> == >> >> >> Channel map: >> >> Channel 01: FXO Kewlstart (Default) (Slaves: 01) >> Channel 02: FXS Kewlstart (Default) (Slaves: 02) >> >> 2 channels configured. >> >> --- >> >> So it looks like things are OK so far. Here's the relevant portion of >> my zaptel.conf: >> >> defaultzone=us >> # load FXO X100P channel 1, kewlstart signalling >> # turned off, card removed >> #fxsks=1 >> # load FXS TDM400P channel 1, kewlstart signalling >> fxoks=1 >> # load FXO TDM400P channel 2, kewlstart signalling >> fxsks=2 >> >> >> And here's what dmesg reports: >> >> Zapata Telephony Interface Registered on major 196 >> PCI: Found IRQ 12 for device 00:09.0 >> Freshmaker version: 63 >> Freshmaker passed register test >> Module 0: Installed -- AUTO FXS >> Module 1: Not installed >> Module 2: Installed -- AUTO FXO >> Module 3: Not installed >> Found a Wildcard TDM: Wildcard TDM400P REV E/F (4 modules) >> Registered tone zone 0 (United States / North America) >> >> --- >> >> the relevant portions of my zapata.conf are: >> >> [channels] >> language=en >> usecallerid=yes >> hidecallerid=no >> callwaiting=yes >> usecallingpres=yes >> callwaitingcallerid=yes >> callreturn=yes >> echocancel=yes >> echocancelwhenbridged=yes >> busydetect=yes >> callprogress=yes >> >> ; interfaces for internal analog phones >> signalling=fxo_ks >> threewaycalling=yes >> transfer=yes >> group=1 >> context=from-internal >> callerid="Creemer" <01> >> channel => 1 >> mailbox=01 >> >> ; interfaces to the external PSTN line >> signalling=fxs_ks >> context=from-pstn >> group=2 >> channel => 2 >> >> --- >> >> starting asterisk gives: >> [chan_zap.so] => (Zapata Telephony w/PRI) >>== Parsing '/etc/asterisk/zapata.conf': Found >> May 19 10:42:20 DEBUG[1024]: chan_zap.c:1077 update_conf: Updated >> conferencing on 1, with 0 conference users >> -- Registered channel 1, FXO Kewlstart signalling >> May 19 10:42:20 WARNING[1024]: chan_zap.c:665 zt_open: Unable to >> specify channel 2: No such device >> May 19 10:42:20 ERROR[1024]: chan_zap.c:5340 mkintf: Unable to open >> channel 2: No such device >> here = 0, tmp->channel = 2, channel = 2 >> May 19 10:42:20 ERROR[1024]: chan_zap.c:7376 setup_zap: Unable to >> register channel '2' >> May 19 10:42:20 WARNING[1024]: loader.c:313 ast_load_resource: >> chan_zap.so: load_module failed, returning -1 >>== Unregistered channel type 'Tor' >>== Unregistered channel type 'Zap' >> -- Unregistered channel 1 >> -- Unregistered channel 2 >> May 19 10:42:20 WARNING[1024]: loader.c:408 load_modules: Loading >> module chan_zap.so failed! >> >> ___ >> Asterisk-Users mailing list >> [EMAIL PROTECTED] >> http://lists.digium.com/mailman/listinfo/asterisk-users >> To UNSUBSCRIBE or update options visit: >>http://lists.digium.com/mailman/listinfo/asterisk-users >> > > > ___ > Asterisk-Users mailing list > [EMAIL PROTECTED] > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: >http://lists.digium.com/mailman/listinfo/asterisk-users > ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/a
Re: [Asterisk-Users] TDM400P problems with 1 FXS, 1 FXO
Hi, On Wed, 2004-05-19 at 14:51, David Creemer wrote: > Hi- > > I'm totally stumped configuring my TDM400P with one FXS and one FXO > module. Before I got the FXO module, I used to have an X101P, and > everything was working very well. Now * doesn't seem to recognize the > FXO channel. I've searched the wiki and the list archives. Stock Debian > 3.0 stable installation. Any advice? Thanks. I do not have an TDM400P, but read reports about it in this very list. Try replacing channel => 2 to 3 in zapata conf. The order of the modules seems to be relevant... -- Nicolas Gudino <[EMAIL PROTECTED]> House Internet S.R.L. ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] TDM400P problems with 1 FXS, 1 FXO
There is a known problem with the first port on the TDM400P. For me, the problem resulted in randomly dropped calls on the FXO port, which was plugged into position 1. Since you only have two daughterboards, try using positions 2-3-4 and don't use position 1, and see of that solves your problem. Bruce Komito High Sierra Networks, Inc. www.servers-r-us.com (775) 284-5800 ext 115 On Wed, 19 May 2004, David Creemer wrote: > Hi- > > I'm totally stumped configuring my TDM400P with one FXS and one FXO > module. Before I got the FXO module, I used to have an X101P, and > everything was working very well. Now * doesn't seem to recognize the > FXO channel. I've searched the wiki and the list archives. Stock Debian > 3.0 stable installation. Any advice? Thanks. > > -- David > > > Here's my configuration: > > modprobe zaptel > modprobe wcfxs > > report no errors. > > box:/etc/asterisk# ztcfg -vv > > Zaptel Configuration > == > > > Channel map: > > Channel 01: FXO Kewlstart (Default) (Slaves: 01) > Channel 02: FXS Kewlstart (Default) (Slaves: 02) > > 2 channels configured. > > --- > > So it looks like things are OK so far. Here's the relevant portion of > my zaptel.conf: > > defaultzone=us > # load FXO X100P channel 1, kewlstart signalling > # turned off, card removed > #fxsks=1 > # load FXS TDM400P channel 1, kewlstart signalling > fxoks=1 > # load FXO TDM400P channel 2, kewlstart signalling > fxsks=2 > > > And here's what dmesg reports: > > Zapata Telephony Interface Registered on major 196 > PCI: Found IRQ 12 for device 00:09.0 > Freshmaker version: 63 > Freshmaker passed register test > Module 0: Installed -- AUTO FXS > Module 1: Not installed > Module 2: Installed -- AUTO FXO > Module 3: Not installed > Found a Wildcard TDM: Wildcard TDM400P REV E/F (4 modules) > Registered tone zone 0 (United States / North America) > > --- > > the relevant portions of my zapata.conf are: > > [channels] > language=en > usecallerid=yes > hidecallerid=no > callwaiting=yes > usecallingpres=yes > callwaitingcallerid=yes > callreturn=yes > echocancel=yes > echocancelwhenbridged=yes > busydetect=yes > callprogress=yes > > ; interfaces for internal analog phones > signalling=fxo_ks > threewaycalling=yes > transfer=yes > group=1 > context=from-internal > callerid="Creemer" <01> > channel => 1 > mailbox=01 > > ; interfaces to the external PSTN line > signalling=fxs_ks > context=from-pstn > group=2 > channel => 2 > > --- > > starting asterisk gives: > [chan_zap.so] => (Zapata Telephony w/PRI) >== Parsing '/etc/asterisk/zapata.conf': Found > May 19 10:42:20 DEBUG[1024]: chan_zap.c:1077 update_conf: Updated > conferencing on 1, with 0 conference users > -- Registered channel 1, FXO Kewlstart signalling > May 19 10:42:20 WARNING[1024]: chan_zap.c:665 zt_open: Unable to > specify channel 2: No such device > May 19 10:42:20 ERROR[1024]: chan_zap.c:5340 mkintf: Unable to open > channel 2: No such device > here = 0, tmp->channel = 2, channel = 2 > May 19 10:42:20 ERROR[1024]: chan_zap.c:7376 setup_zap: Unable to > register channel '2' > May 19 10:42:20 WARNING[1024]: loader.c:313 ast_load_resource: > chan_zap.so: load_module failed, returning -1 >== Unregistered channel type 'Tor' >== Unregistered channel type 'Zap' > -- Unregistered channel 1 > -- Unregistered channel 2 > May 19 10:42:20 WARNING[1024]: loader.c:408 load_modules: Loading > module chan_zap.so failed! > > ___ > Asterisk-Users mailing list > [EMAIL PROTECTED] > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: >http://lists.digium.com/mailman/listinfo/asterisk-users > ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[Asterisk-Users] TDM400P problems with 1 FXS, 1 FXO
Hi- I'm totally stumped configuring my TDM400P with one FXS and one FXO module. Before I got the FXO module, I used to have an X101P, and everything was working very well. Now * doesn't seem to recognize the FXO channel. I've searched the wiki and the list archives. Stock Debian 3.0 stable installation. Any advice? Thanks. -- David Here's my configuration: modprobe zaptel modprobe wcfxs report no errors. box:/etc/asterisk# ztcfg -vv Zaptel Configuration == Channel map: Channel 01: FXO Kewlstart (Default) (Slaves: 01) Channel 02: FXS Kewlstart (Default) (Slaves: 02) 2 channels configured. --- So it looks like things are OK so far. Here's the relevant portion of my zaptel.conf: defaultzone=us # load FXO X100P channel 1, kewlstart signalling # turned off, card removed #fxsks=1 # load FXS TDM400P channel 1, kewlstart signalling fxoks=1 # load FXO TDM400P channel 2, kewlstart signalling fxsks=2 And here's what dmesg reports: Zapata Telephony Interface Registered on major 196 PCI: Found IRQ 12 for device 00:09.0 Freshmaker version: 63 Freshmaker passed register test Module 0: Installed -- AUTO FXS Module 1: Not installed Module 2: Installed -- AUTO FXO Module 3: Not installed Found a Wildcard TDM: Wildcard TDM400P REV E/F (4 modules) Registered tone zone 0 (United States / North America) --- the relevant portions of my zapata.conf are: [channels] language=en usecallerid=yes hidecallerid=no callwaiting=yes usecallingpres=yes callwaitingcallerid=yes callreturn=yes echocancel=yes echocancelwhenbridged=yes busydetect=yes callprogress=yes ; interfaces for internal analog phones signalling=fxo_ks threewaycalling=yes transfer=yes group=1 context=from-internal callerid="Creemer" <01> channel => 1 mailbox=01 ; interfaces to the external PSTN line signalling=fxs_ks context=from-pstn group=2 channel => 2 --- starting asterisk gives: [chan_zap.so] => (Zapata Telephony w/PRI) == Parsing '/etc/asterisk/zapata.conf': Found May 19 10:42:20 DEBUG[1024]: chan_zap.c:1077 update_conf: Updated conferencing on 1, with 0 conference users -- Registered channel 1, FXO Kewlstart signalling May 19 10:42:20 WARNING[1024]: chan_zap.c:665 zt_open: Unable to specify channel 2: No such device May 19 10:42:20 ERROR[1024]: chan_zap.c:5340 mkintf: Unable to open channel 2: No such device here = 0, tmp->channel = 2, channel = 2 May 19 10:42:20 ERROR[1024]: chan_zap.c:7376 setup_zap: Unable to register channel '2' May 19 10:42:20 WARNING[1024]: loader.c:313 ast_load_resource: chan_zap.so: load_module failed, returning -1 == Unregistered channel type 'Tor' == Unregistered channel type 'Zap' -- Unregistered channel 1 -- Unregistered channel 2 May 19 10:42:20 WARNING[1024]: loader.c:408 load_modules: Loading module chan_zap.so failed! ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
