Re: [Asterisk-Users] TDM400P problems
On Friday 02 September 2005 11:38, Andrew Kohlsmith wrote: On Friday 02 September 2005 12:57, Martin wrote: I would be really curious if anyone else has the capability (digital multimeter) and enough knowledge to test their incoming CO (Central Office line) and board outputs. I will test mine at lunchtime today. -A. What was the result ??? ___ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@lists.digium.com 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
This is a well-known issue with the current drivers, although nobody's really stepped up to identify when exactly this started happenning (as the driver code was changed) or why. Do I understand that this would not be a problem with an 'older' version of Asterisk ? If so, any idea to which version I need to revert ? Who uses a Fax machine and/or Fax modem in Combination with TDM400P without problem ? What is the * version you are running ? 2) I'm trying 3 different Analog phones and having 3 different behaviors: 1 phone 'ringes' normally 1 phone 'ringes' a bit cripled (instead of ring-ring... ring-ring..., it does 'ring-ri... ri ring... ri...) 1 phone does not ring at all when Asterisk says 'Ringing Zap/6'. However, when I do an 'off-hook' on this phone, I get a normal tone signal and I can dial and talk perfectly. DTMF is recognised too. It simply does not ring on incoming calls. Have you tried the 'boostringer=1' module option? If you swap phones and ports around (i.e. try phone #3 in phone #1's port) does the problem stay with the phone or the port? I was not aware of this option, I'll try it. boostringer=1 does _not_ solve it. I'am sure it was activated, since there was a kernel message saying so. alex -- NEW: aXs GUARD hands-on Trainings v.7.0 more info at http://www.axsguard.com/indextraining.htm aXs GUARD has completed security and anti-virus checks on this e-mail (http://www.axsguard.com) --- Able NV: ond.nr 0457.938.087 ___ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@lists.digium.com 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
On Friday 02 September 2005 07:47, Alex Ongena wrote: This is a well-known issue with the current drivers, although nobody's really stepped up to identify when exactly this started happenning (as the driver code was changed) or why. Do I understand that this would not be a problem with an 'older' version of Asterisk ? If so, any idea to which version I need to revert ? 2) I'm trying 3 different Analog phones and having 3 different behaviors: 1 phone 'ringes' normally 1 phone 'ringes' a bit cripled (instead of ring-ring... ring-ring..., it does 'ring-ri... ri ring... ri...) 1 phone does not ring at all when Asterisk says 'Ringing Zap/6'. However, when I do an 'off-hook' on this phone, I get a normal tone signal and I can dial and talk perfectly. DTMF is recognised too. It simply does not ring on incoming calls. Interesting. I have just re-installed asterisk with the digium dev kit (Xp100 and TDM400P) and have problems with TDM400P port #3. I also see an issue with lack of drive to the phones. The more phones I add, the more ring issues. I can 'fix' the issue by switching phones. The docs ( http://www.intervoice.com/_docs/.433/601016.PDF ) say it shouldn't surpass 5, but that is per line and shouldn't be an issue with the TDM400P as it supplies up to 4 lines, each of up to 5 REN's if they followed the rules. Yes, the 4-pin power connector from the 400W PS is plugged in and there is only one H/D and one DVD drive, no floppy. Is this a driver issue, or a failure on the TDM400P ? As it say's above This is a well-known issue with the current drivers, if this is correct, what version is good ??? and how do you get it ? Regards...Martin ___ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@lists.digium.com 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
On Friday 02 September 2005 09:33, Martin wrote: On Friday 02 September 2005 07:47, Alex Ongena wrote: This is a well-known issue with the current drivers, although nobody's really stepped up to identify when exactly this started happenning (as the driver code was changed) or why. Interesting. I have just re-installed asterisk with the digium dev kit (Xp100 and TDM400P) and have problems with TDM400P port #3. I also see an issue with lack of drive to the phones. The more phones I add, the more ring issues. I can 'fix' the issue by switching phones. The docs ( http://www.intervoice.com/_docs/.433/601016.PDF ) I just ran some tests. The US FCC specs are:- Standing voltage= -48 VDC (minus) Ringing voltage = 85 - 105 VAC current supplied= 20 to 50mA (I haven't checked this as I would have to create a break and bridge with the digital multi-meter) My line from the central office Standing voltage= -51.1 VDC (minus) Ringing voltage = 90.7 VAC Port #1 Standing voltage= -48.4 VDC Ringing voltage = 42.7 VAC Port #2 Standing voltage= -48.2 VDC Ringing voltage = 42.7 VAC Port #4 Standing voltage= -44.4 VDC Ringing voltage = 43.5 VAC It looks like my card/modules, are not providing the required ring voltage. Anyone else checked their voltages ? Regards...Martin ___ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@lists.digium.com 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
Probably already been covered but you do have the power connector on the board connected right? -Jonathan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Martin Sent: Friday, September 02, 2005 12:32 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [Asterisk-Users] TDM400P problems On Friday 02 September 2005 09:33, Martin wrote: On Friday 02 September 2005 07:47, Alex Ongena wrote: This is a well-known issue with the current drivers, although nobody's really stepped up to identify when exactly this started happenning (as the driver code was changed) or why. Interesting. I have just re-installed asterisk with the digium dev kit (Xp100 and TDM400P) and have problems with TDM400P port #3. I also see an issue with lack of drive to the phones. The more phones I add, the more ring issues. I can 'fix' the issue by switching phones. The docs ( http://www.intervoice.com/_docs/.433/601016.PDF ) I just ran some tests. The US FCC specs are:- Standing voltage= -48 VDC (minus) Ringing voltage = 85 - 105 VAC current supplied= 20 to 50mA (I haven't checked this as I would have to create a break and bridge with the digital multi-meter) My line from the central office Standing voltage= -51.1 VDC (minus) Ringing voltage = 90.7 VAC Port #1 Standing voltage= -48.4 VDC Ringing voltage = 42.7 VAC Port #2 Standing voltage= -48.2 VDC Ringing voltage = 42.7 VAC Port #4 Standing voltage= -44.4 VDC Ringing voltage = 43.5 VAC It looks like my card/modules, are not providing the required ring voltage. Anyone else checked their voltages ? Regards...Martin ___ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@lists.digium.com 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
On Friday 02 September 2005 10:43, Jonathan k. Creasy wrote: Probably already been covered but you do have the power connector on the board connected right? -Jonathan Yes, from my earlier email Yes, the 4-pin power connector from the 400W PS is plugged in and there is only one H/D and one DVD drive, no floppy. Regards...Martin ___ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@lists.digium.com 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
On Friday 02 September 2005 12:31, Martin wrote: Port #1 Standing voltage = -48.4 VDC Ringing voltage = 42.7 VAC Port #2 Standing voltage = -48.2 VDC Ringing voltage = 42.7 VAC Port #4 Standing voltage = -44.4 VDC Ringing voltage = 43.5 VAC Sounds like you have defective modules or carrier board. Have you contacted the free (paid for in the price of the card) Digium technical support? -A. ___ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@lists.digium.com 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
On Friday 02 September 2005 10:51, Andrew Kohlsmith wrote: On Friday 02 September 2005 12:31, Martin wrote: Port #1 Standing voltage = -48.4 VDC Ringing voltage = 42.7 VAC Port #2 Standing voltage = -48.2 VDC Ringing voltage = 42.7 VAC Port #4 Standing voltage = -44.4 VDC Ringing voltage = 43.5 VAC Sounds like you have defective modules or carrier board. Have you contacted the free (paid for in the price of the card) Digium technical support? -A. Yes..I'm 'in process' now. I would be really curious if anyone else has the capability (digital multimeter) and enough knowledge to test their incoming CO (Central Office line) and board outputs. Regards...Martin ___ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@lists.digium.com 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
On Friday 02 September 2005 12:57, Martin wrote: I would be really curious if anyone else has the capability (digital multimeter) and enough knowledge to test their incoming CO (Central Office line) and board outputs. I will test mine at lunchtime today. -A. ___ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@lists.digium.com 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
On Thursday 01 September 2005 06:35, Alex Ongena wrote: I encounter 2 major problems: 1) Transmitting and receiving van Fax is very unreliable (on the CLI I see a Native bridging (seems to be 911.ulaw, 64 kbit high quality). Sometimes the Fax is Ok, sometimes I miss a few lines, sometimes it's impossible. The same problem is there when sending or receiving faxes. This is a well-known issue with the current drivers, although nobody's really stepped up to identify when exactly this started happenning (as the driver code was changed) or why. 2) I'm trying 3 different Analog phones and having 3 different behaviors: 1 phone 'ringes' normally 1 phone 'ringes' a bit cripled (instead of ring-ring... ring-ring..., it does 'ring-ri... ri ring... ri...) 1 phone does not ring at all when Asterisk says 'Ringing Zap/6'. However, when I do an 'off-hook' on this phone, I get a normal tone signal and I can dial and talk perfectly. DTMF is recognised too. It simply does not ring on incoming calls. Have you tried the 'boostringer=1' module option? If you swap phones and ports around (i.e. try phone #3 in phone #1's port) does the problem stay with the phone or the port? -A. ___ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@lists.digium.com 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
On Thu, 2005-09-01 at 08:12 -0400, Andrew Kohlsmith wrote: On Thursday 01 September 2005 06:35, Alex Ongena wrote: I encounter 2 major problems: 1) Transmitting and receiving van Fax is very unreliable (on the CLI I see a Native bridging (seems to be 911.ulaw, 64 kbit high quality). Sometimes the Fax is Ok, sometimes I miss a few lines, sometimes it's impossible. The same problem is there when sending or receiving faxes. This is a well-known issue with the current drivers, although nobody's really stepped up to identify when exactly this started happenning (as the driver code was changed) or why. Do I understand that this would not be a problem with an 'older' version of Asterisk ? If so, any idea to which version I need to revert ? 2) I'm trying 3 different Analog phones and having 3 different behaviors: 1 phone 'ringes' normally 1 phone 'ringes' a bit cripled (instead of ring-ring... ring-ring..., it does 'ring-ri... ri ring... ri...) 1 phone does not ring at all when Asterisk says 'Ringing Zap/6'. However, when I do an 'off-hook' on this phone, I get a normal tone signal and I can dial and talk perfectly. DTMF is recognised too. It simply does not ring on incoming calls. Have you tried the 'boostringer=1' module option? If you swap phones and ports around (i.e. try phone #3 in phone #1's port) does the problem stay with the phone or the port? I was not aware of this option, I'll try it. The problem stays with the phone, regardless of the port? Thanks already alex -A. ___ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users -- NEW: aXs GUARD hands-on Trainings v.7.0 more info at http://www.axsguard.com/indextraining.htm aXs GUARD has completed security and anti-virus checks on this e-mail (http://www.axsguard.com) --- Able NV: ond.nr 0457.938.087 ___ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@lists.digium.com 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
César Davi Ávila do Nascimento wrote: Hi All I've bought a TDM400P and need some help with configuration. Can you tell me what to do ? I've tried to install and the message below has appeared: [EMAIL PROTECTED] asterisk]# modprobe zaptel [EMAIL PROTECTED] asterisk]# modprobe wcfxo /lib/modules/2.4.22-1.2115.nptl/misc/wcfxo.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.22-1.2115.nptl/misc/wcfxo.o: insmod /lib/modules/2.4.22-1.2115.nptl/misc/wcfxo.o failed /lib/modules/2.4.22-1.2115.nptl/misc/wcfxo.o: insmod wcfxo failed Try to modprobe for wcfxs or wctdm. Wcfxo is for the old card. -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.6.8 - Release Date: 03/01/2005 ___ Asterisk-Users mailing list Asterisk-Users@lists.digium.com 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
On Thu, 2005-01-06 at 11:15 -0300, Csar Davi vila do Nascimento wrote: Hi All I've bought a TDM400P and need some help with configuration. Can you tell me what to do ? I've tried to install and the message below has appeared: [EMAIL PROTECTED] asterisk]# modprobe zaptel [EMAIL PROTECTED] asterisk]# modprobe wcfxo /lib/modules/2.4.22-1.2115.nptl/misc/wcfxo.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.22-1.2115.nptl/misc/wcfxo.o: insmod /lib/modules/2.4.22-1.2115.nptl/misc/wcfxo.o failed /lib/modules/2.4.22-1.2115.nptl/misc/wcfxo.o: insmod wcfxo failed Search the mailing list before posting **READ** the mailing list before posting DON'T send HTML garbage to the list (yes, I know, this email will probably be HTML as well, anyone want to tell me how to force evolution to convert it back to plain text when replying?) Finally, don't use the wcfxo module for a tdm card, use either the wctdm module from current development cvs, or preferably, the wcfxs module from the current release or stable CVS. Regards, Adam -- -- Adam Goryachev Website Managers Ph: +61 2 8304 [EMAIL PROTECTED] Fax: +61 2 9345 4396www.websitemanagers.com.au ___ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: X-SBClass: Spam ( Re: [Asterisk-Users] TDM400P Problems)
I have a problem in that the pci card is not detected at all. Other pci cards are detected fine but not the tdm400b. It's detected on a different - smaller - machine no probs. Any ideas of the magic bios setting to get it going? - Original Message - From: Lyle Giese [EMAIL PROTECTED] To: Asterisk Users Mailing List - Non-Commercial Discussion [EMAIL PROTECTED] Sent: Friday, August 27, 2004 12:41 PM Subject: X-SBClass: Spam ( Re: [Asterisk-Users] TDM400P Problems) Have you checked to see if there is a newer bios for the motherboard? - Original Message - From: Greg Hulands [EMAIL PROTECTED] To: Asterisk Users Mailing List - Non-Commercial Discussion [EMAIL PROTECTED] Sent: Thursday, August 26, 2004 9:31 PM Subject: Re: [Asterisk-Users] TDM400P Problems Even when the tdm400 is the only card in the computer, it still has this problem. I'm not sure how I would go about determining what is causing it. I have reset the bios to its factory settings to see if that helped, but alas it did not. Seems like i'm screwed. Greg On 27/08/2004, at 12:12 PM, Lyle Giese wrote: My guess is that you have PCI bus compatibility problems of some sort. Moving the cards around may help. Using a plug in NIC may help. A different Motherboard may help. This looks like hardware and trial and error and experience is all you have to lead you forward, if my guess is right. Lyle - Original Message - From: Greg Hulands [EMAIL PROTECTED] To: Asterisk Users Mailing List - Non-Commercial Discussion [EMAIL PROTECTED] Sent: Thursday, August 26, 2004 8:11 PM Subject: Re: [Asterisk-Users] TDM400P Problems When I did the lspci -v when it got to the tdm400p it seemed to go into an infinite loop on this line: Capabilities: [80] #00 []. When I redirected output to a file it filled to 8MB in about 3 seconds with this line. I moved the NIC so that it would be before the tdm400p, but it still did the same thing. I haven't a clue what is going on here. Any help is greatly appreciated. Regards, Greg Here is the output: 00:00.0 Host bridge: nVidia Corporation nForce2 AGP (different version?) (rev c1) Flags: bus master, 66Mhz, fast devsel, latency 0 Memory at d000 (32-bit, prefetchable) Capabilities: [40] AGP version 2.0 Capabilities: [60] #08 [2001] 00:00.1 RAM memory: nVidia Corporation nForce2 Memory Controller 1 (rev c1) Subsystem: Unknown device 17f2:3401 Flags: 66Mhz, fast devsel 00:00.2 RAM memory: nVidia Corporation nForce2 Memory Controller 4 (rev c1) Subsystem: Unknown device 17f2:3401 Flags: 66Mhz, fast devsel 00:00.3 RAM memory: nVidia Corporation nForce2 Memory Controller 3 (rev c1) Subsystem: Unknown device 17f2:3401 Flags: 66Mhz, fast devsel 00:00.4 RAM memory: nVidia Corporation nForce2 Memory Controller 2 (rev c1) Subsystem: Unknown device 17f2:3401 Flags: 66Mhz, fast devsel 00:00.5 RAM memory: nVidia Corporation nForce2 Memory Controller 5 (rev c1) Subsystem: Unknown device 17f2:3401 Flags: 66Mhz, fast devsel 00:01.0 ISA bridge: nVidia Corporation nForce2 ISA Bridge (rev a4) Subsystem: Unknown device 17f2:3401 Flags: bus master, 66Mhz, fast devsel, latency 0 Capabilities: [48] #08 [01e1] 00:01.1 SMBus: nVidia Corporation nForce2 SMBus (MCP) (rev a2) Subsystem: Unknown device 17f2:3401 Flags: 66Mhz, fast devsel, IRQ 12 I/O ports at bc00 Capabilities: [44] Power Management version 2 00:02.0 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4) (prog-if 10 [OHCI]) Subsystem: Unknown device 17f2:3401 Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 11 Memory at e4002000 (32-bit, non-prefetchable) Capabilities: [44] Power Management version 2 00:02.1 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4) (prog-if 10 [OHCI]) Subsystem: Unknown device 17f2:3401 Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 9 Memory at e4003000 (32-bit, non-prefetchable) Capabilities: [44] Power Management version 2 00:02.2 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4) (prog-if 20 [EHCI]) Subsystem: Unknown device 17f2:3401 Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 5 Memory at e4004000 (32-bit, non-prefetchable) Capabilities: [44] #0a [2080] Capabilities: [80] Power Management version 2 00:06.0 Multimedia audio controller: nVidia Corporation nForce2 AC97 Audio Controler (MCP) (rev a1) Subsystem: Unknown device 17f2:3401 Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 12 I/O ports at c000 I/O ports at b000 [size=128] Memory at e400 (32-bit, non-prefetchable) [size=4K] Capabilities: [44] Power Management version 2 00:08.0 PCI bridge: nVidia Corporation nForce2 External PCI Bridge
Re: X-SBClass: Spam ( Re: [Asterisk-Users] TDM400P Problems)
PHP Is this motherboard PCI 2.2 compliant? Is there a bios update availible for that motherboard(In other words, try all the suggestions below and elsewhere in this thread). Lyle - Original Message - From: PHP Mechanic [EMAIL PROTECTED] To: Asterisk Users Mailing List - Non-Commercial Discussion [EMAIL PROTECTED] Sent: Friday, August 27, 2004 1:31 AM Subject: Re: X-SBClass: Spam ( Re: [Asterisk-Users] TDM400P Problems) I have a problem in that the pci card is not detected at all. Other pci cards are detected fine but not the tdm400b. It's detected on a different - smaller - machine no probs. Any ideas of the magic bios setting to get it going? - Original Message - From: Lyle Giese [EMAIL PROTECTED] To: Asterisk Users Mailing List - Non-Commercial Discussion [EMAIL PROTECTED] Sent: Friday, August 27, 2004 12:41 PM Subject: X-SBClass: Spam ( Re: [Asterisk-Users] TDM400P Problems) Have you checked to see if there is a newer bios for the motherboard? - Original Message - From: Greg Hulands [EMAIL PROTECTED] To: Asterisk Users Mailing List - Non-Commercial Discussion [EMAIL PROTECTED] Sent: Thursday, August 26, 2004 9:31 PM Subject: Re: [Asterisk-Users] TDM400P Problems Even when the tdm400 is the only card in the computer, it still has this problem. I'm not sure how I would go about determining what is causing it. I have reset the bios to its factory settings to see if that helped, but alas it did not. Seems like i'm screwed. Greg On 27/08/2004, at 12:12 PM, Lyle Giese wrote: My guess is that you have PCI bus compatibility problems of some sort. Moving the cards around may help. Using a plug in NIC may help. A different Motherboard may help. This looks like hardware and trial and error and experience is all you have to lead you forward, if my guess is right. Lyle - Original Message - From: Greg Hulands [EMAIL PROTECTED] To: Asterisk Users Mailing List - Non-Commercial Discussion [EMAIL PROTECTED] Sent: Thursday, August 26, 2004 8:11 PM Subject: Re: [Asterisk-Users] TDM400P Problems When I did the lspci -v when it got to the tdm400p it seemed to go into an infinite loop on this line: Capabilities: [80] #00 []. When I redirected output to a file it filled to 8MB in about 3 seconds with this line. I moved the NIC so that it would be before the tdm400p, but it still did the same thing. I haven't a clue what is going on here. Any help is greatly appreciated. Regards, Greg Here is the output: 00:00.0 Host bridge: nVidia Corporation nForce2 AGP (different version?) (rev c1) Flags: bus master, 66Mhz, fast devsel, latency 0 Memory at d000 (32-bit, prefetchable) Capabilities: [40] AGP version 2.0 Capabilities: [60] #08 [2001] 00:00.1 RAM memory: nVidia Corporation nForce2 Memory Controller 1 (rev c1) Subsystem: Unknown device 17f2:3401 Flags: 66Mhz, fast devsel 00:00.2 RAM memory: nVidia Corporation nForce2 Memory Controller 4 (rev c1) Subsystem: Unknown device 17f2:3401 Flags: 66Mhz, fast devsel 00:00.3 RAM memory: nVidia Corporation nForce2 Memory Controller 3 (rev c1) Subsystem: Unknown device 17f2:3401 Flags: 66Mhz, fast devsel 00:00.4 RAM memory: nVidia Corporation nForce2 Memory Controller 2 (rev c1) Subsystem: Unknown device 17f2:3401 Flags: 66Mhz, fast devsel 00:00.5 RAM memory: nVidia Corporation nForce2 Memory Controller 5 (rev c1) Subsystem: Unknown device 17f2:3401 Flags: 66Mhz, fast devsel 00:01.0 ISA bridge: nVidia Corporation nForce2 ISA Bridge (rev a4) Subsystem: Unknown device 17f2:3401 Flags: bus master, 66Mhz, fast devsel, latency 0 Capabilities: [48] #08 [01e1] 00:01.1 SMBus: nVidia Corporation nForce2 SMBus (MCP) (rev a2) Subsystem: Unknown device 17f2:3401 Flags: 66Mhz, fast devsel, IRQ 12 I/O ports at bc00 Capabilities: [44] Power Management version 2 00:02.0 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4) (prog-if 10 [OHCI]) Subsystem: Unknown device 17f2:3401 Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 11 Memory at e4002000 (32-bit, non-prefetchable) Capabilities: [44] Power Management version 2 00:02.1 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4) (prog-if 10 [OHCI]) Subsystem: Unknown device 17f2:3401 Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 9 Memory at e4003000 (32-bit, non-prefetchable) Capabilities: [44] Power Management version 2 00:02.2 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4) (prog-if 20 [EHCI]) Subsystem: Unknown device 17f2:3401 Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 5
Re: [Asterisk-Users] TDM400P Problems
lspci -v should show more helpfull info, including I/O memory addresses. Lyle - Original Message - From: Greg Hulands [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, August 26, 2004 7:11 PM Subject: [Asterisk-Users] TDM400P Problems Hi, I have just started to setup and configure my asterisk box and am having trouble with it. I have a dlink nic in the box as well as the digium card. When the nic is in there by itself it works, but when I put the tdm400p in, there seems to be some sort of conflict with the network card. The tdm appears as another type of network card, which I don't think it should, should it? It shows up in lspci as 01:08.0 Network controller: Individual Computers - Jens Schoenfeld Intel 537. Does anyone know why this would be happening? Any help is greatly appreciated. Regards, Greg lspci with only network card in. [EMAIL PROTECTED] root]# lspci 00:00.0 Host bridge: nVidia Corporation nForce2 AGP (different version?) (rev c1) 00:00.1 RAM memory: nVidia Corporation nForce2 Memory Controller 1 (rev c1) 00:00.2 RAM memory: nVidia Corporation nForce2 Memory Controller 4 (rev c1) 00:00.3 RAM memory: nVidia Corporation nForce2 Memory Controller 3 (rev c1) 00:00.4 RAM memory: nVidia Corporation nForce2 Memory Controller 2 (rev c1) 00:00.5 RAM memory: nVidia Corporation nForce2 Memory Controller 5 (rev c1) 00:01.0 ISA bridge: nVidia Corporation nForce2 ISA Bridge (rev a4) 00:01.1 SMBus: nVidia Corporation nForce2 SMBus (MCP) (rev a2) 00:02.0 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4) 00:02.1 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4) 00:02.2 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4) 00:06.0 Multimedia audio controller: nVidia Corporation nForce2 AC97 Audio Controler (MCP) (rev a1) 00:08.0 PCI bridge: nVidia Corporation nForce2 External PCI Bridge (rev a3) 00:09.0 IDE interface: nVidia Corporation nForce2 IDE (rev a2) 00:1e.0 PCI bridge: nVidia Corporation nForce2 AGP (rev c1) 01:0a.0 Ethernet controller: VIA Technologies, Inc. VT86C100A [Rhine] (rev 06) 02:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV100 QY [Radeon 7000/VE] [EMAIL PROTECTED] root]# cat /proc/interrupts CPU0 0: 324262 XT-PIC timer 1: 76 XT-PIC i8042 2: 0 XT-PIC cascade 5: 0 XT-PIC NVidia nForce2 8: 1 XT-PIC rtc 9: 0 XT-PIC acpi, ehci_hcd 11: 1025 XT-PIC ohci_hcd, eth0 12: 26249 XT-PIC ohci_hcd, [EMAIL PROTECTED]:2:0:0 14: 14408 XT-PIC ide0 NMI: 0 ERR: 0 [EMAIL PROTECTED] root]# lspci with network card and tdm400p in [EMAIL PROTECTED] root]# lspci 00:00.0 Host bridge: nVidia Corporation nForce2 AGP (different version?) (rev c1) 00:00.1 RAM memory: nVidia Corporation nForce2 Memory Controller 1 (rev c1) 00:00.2 RAM memory: nVidia Corporation nForce2 Memory Controller 4 (rev c1) 00:00.3 RAM memory: nVidia Corporation nForce2 Memory Controller 3 (rev c1) 00:00.4 RAM memory: nVidia Corporation nForce2 Memory Controller 2 (rev c1) 00:00.5 RAM memory: nVidia Corporation nForce2 Memory Controller 5 (rev c1) 00:01.0 ISA bridge: nVidia Corporation nForce2 ISA Bridge (rev a4) 00:01.1 SMBus: nVidia Corporation nForce2 SMBus (MCP) (rev a2) 00:02.0 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4) 00:02.1 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4) 00:02.2 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4) 00:06.0 Multimedia audio controller: nVidia Corporation nForce2 AC97 Audio Controler (MCP) (rev a1) 00:08.0 PCI bridge: nVidia Corporation nForce2 External PCI Bridge (rev a3) 00:09.0 IDE interface: nVidia Corporation nForce2 IDE (rev a2) 00:1e.0 PCI bridge: nVidia Corporation nForce2 AGP (rev c1) 01:08.0 Network controller: Individual Computers - Jens Schoenfeld Intel 537 01:0a.0 Ethernet controller: Unknown device 9106:3043 (rev 06) 02:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV100 QY [Radeon 7000/VE] [EMAIL PROTECTED] root]# cat /proc/interrupts CPU0 0: 566133 XT-PIC timer 1:141 XT-PIC i8042 2: 0 XT-PIC cascade 5: 0 XT-PIC ehci_hcd 8: 1 XT-PIC rtc 9: 2730 XT-PIC acpi, ohci_hcd 11: 46773 XT-PIC ohci_hcd, [EMAIL PROTECTED]:2:0:0 12: 0 XT-PIC NVidia nForce2 14: 16583 XT-PIC ide0 NMI: 0 ERR: 18 ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit:
Re: [Asterisk-Users] TDM400P Problems
When I did the lspci -v when it got to the tdm400p it seemed to go into an infinite loop on this line: Capabilities: [80] #00 []. When I redirected output to a file it filled to 8MB in about 3 seconds with this line. I moved the NIC so that it would be before the tdm400p, but it still did the same thing. I haven't a clue what is going on here. Any help is greatly appreciated. Regards, Greg Here is the output: 00:00.0 Host bridge: nVidia Corporation nForce2 AGP (different version?) (rev c1) Flags: bus master, 66Mhz, fast devsel, latency 0 Memory at d000 (32-bit, prefetchable) Capabilities: [40] AGP version 2.0 Capabilities: [60] #08 [2001] 00:00.1 RAM memory: nVidia Corporation nForce2 Memory Controller 1 (rev c1) Subsystem: Unknown device 17f2:3401 Flags: 66Mhz, fast devsel 00:00.2 RAM memory: nVidia Corporation nForce2 Memory Controller 4 (rev c1) Subsystem: Unknown device 17f2:3401 Flags: 66Mhz, fast devsel 00:00.3 RAM memory: nVidia Corporation nForce2 Memory Controller 3 (rev c1) Subsystem: Unknown device 17f2:3401 Flags: 66Mhz, fast devsel 00:00.4 RAM memory: nVidia Corporation nForce2 Memory Controller 2 (rev c1) Subsystem: Unknown device 17f2:3401 Flags: 66Mhz, fast devsel 00:00.5 RAM memory: nVidia Corporation nForce2 Memory Controller 5 (rev c1) Subsystem: Unknown device 17f2:3401 Flags: 66Mhz, fast devsel 00:01.0 ISA bridge: nVidia Corporation nForce2 ISA Bridge (rev a4) Subsystem: Unknown device 17f2:3401 Flags: bus master, 66Mhz, fast devsel, latency 0 Capabilities: [48] #08 [01e1] 00:01.1 SMBus: nVidia Corporation nForce2 SMBus (MCP) (rev a2) Subsystem: Unknown device 17f2:3401 Flags: 66Mhz, fast devsel, IRQ 12 I/O ports at bc00 Capabilities: [44] Power Management version 2 00:02.0 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4) (prog-if 10 [OHCI]) Subsystem: Unknown device 17f2:3401 Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 11 Memory at e4002000 (32-bit, non-prefetchable) Capabilities: [44] Power Management version 2 00:02.1 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4) (prog-if 10 [OHCI]) Subsystem: Unknown device 17f2:3401 Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 9 Memory at e4003000 (32-bit, non-prefetchable) Capabilities: [44] Power Management version 2 00:02.2 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4) (prog-if 20 [EHCI]) Subsystem: Unknown device 17f2:3401 Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 5 Memory at e4004000 (32-bit, non-prefetchable) Capabilities: [44] #0a [2080] Capabilities: [80] Power Management version 2 00:06.0 Multimedia audio controller: nVidia Corporation nForce2 AC97 Audio Controler (MCP) (rev a1) Subsystem: Unknown device 17f2:3401 Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 12 I/O ports at c000 I/O ports at b000 [size=128] Memory at e400 (32-bit, non-prefetchable) [size=4K] Capabilities: [44] Power Management version 2 00:08.0 PCI bridge: nVidia Corporation nForce2 External PCI Bridge (rev a3) (prog-if 00 [Normal decode]) Flags: bus master, 66Mhz, fast devsel, latency 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=32 I/O behind bridge: 9000-9fff Memory behind bridge: e200-e3ff Expansion ROM at 9000 [disabled] [size=4K] 00:09.0 IDE interface: nVidia Corporation nForce2 IDE (rev a2) (prog-if 8a [Master SecP PriP]) Subsystem: Unknown device 17f2:3401 Flags: bus master, 66Mhz, fast devsel, latency 0 I/O ports at f000 [size=16] Capabilities: [44] Power Management version 2 00:1e.0 PCI bridge: nVidia Corporation nForce2 AGP (rev c1) (prog-if 00 [Normal decode]) Flags: bus master, 66Mhz, medium devsel, latency 32 Bus: primary=00, secondary=02, subordinate=02, sec-latency=32 I/O behind bridge: a000-afff Memory behind bridge: e000-e1ff Prefetchable memory behind bridge: d800-dfff Expansion ROM at a000 [disabled] [size=4K] 01:07.0 Network controller: Individual Computers - Jens Schoenfeld Intel 537 (prog-if 80) Subsystem: Unknown device b100:0001 Flags: bus master, medium devsel, latency 160, IRQ 10 I/O ports at 9000 Memory at e3009000 (32-bit, non-prefetchable) [size=4K] Memory at ignored (32-bit, non-prefetchable) Memory at ignored (32-bit, non-prefetchable) Memory at ignored (32-bit, non-prefetchable) Memory at ignored (32-bit, non-prefetchable) Capabilities: [40] Power Management version 2 Capabilities: [80] #00 [] Capabilities: [80] #00 [] Capabilities: [80] #00 [] Capabilities: [80] #00 [] Capabilities: [80] #00 [] Capabilities: [80] #00 [] On 27/08/2004, at 10:30 AM, Lyle Giese wrote: lspci -v should show more helpfull info, including I/O memory addresses. Lyle - Original Message - From: Greg Hulands [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, August 26, 2004 7:11 PM Subject: [Asterisk-Users]
Re: [Asterisk-Users] TDM400P Problems
My guess is that you have PCI bus compatibility problems of some sort. Moving the cards around may help. Using a plug in NIC may help. A different Motherboard may help. This looks like hardware and trial and error and experience is all you have to lead you forward, if my guess is right. Lyle - Original Message - From: Greg Hulands [EMAIL PROTECTED] To: Asterisk Users Mailing List - Non-Commercial Discussion [EMAIL PROTECTED] Sent: Thursday, August 26, 2004 8:11 PM Subject: Re: [Asterisk-Users] TDM400P Problems When I did the lspci -v when it got to the tdm400p it seemed to go into an infinite loop on this line: Capabilities: [80] #00 []. When I redirected output to a file it filled to 8MB in about 3 seconds with this line. I moved the NIC so that it would be before the tdm400p, but it still did the same thing. I haven't a clue what is going on here. Any help is greatly appreciated. Regards, Greg Here is the output: 00:00.0 Host bridge: nVidia Corporation nForce2 AGP (different version?) (rev c1) Flags: bus master, 66Mhz, fast devsel, latency 0 Memory at d000 (32-bit, prefetchable) Capabilities: [40] AGP version 2.0 Capabilities: [60] #08 [2001] 00:00.1 RAM memory: nVidia Corporation nForce2 Memory Controller 1 (rev c1) Subsystem: Unknown device 17f2:3401 Flags: 66Mhz, fast devsel 00:00.2 RAM memory: nVidia Corporation nForce2 Memory Controller 4 (rev c1) Subsystem: Unknown device 17f2:3401 Flags: 66Mhz, fast devsel 00:00.3 RAM memory: nVidia Corporation nForce2 Memory Controller 3 (rev c1) Subsystem: Unknown device 17f2:3401 Flags: 66Mhz, fast devsel 00:00.4 RAM memory: nVidia Corporation nForce2 Memory Controller 2 (rev c1) Subsystem: Unknown device 17f2:3401 Flags: 66Mhz, fast devsel 00:00.5 RAM memory: nVidia Corporation nForce2 Memory Controller 5 (rev c1) Subsystem: Unknown device 17f2:3401 Flags: 66Mhz, fast devsel 00:01.0 ISA bridge: nVidia Corporation nForce2 ISA Bridge (rev a4) Subsystem: Unknown device 17f2:3401 Flags: bus master, 66Mhz, fast devsel, latency 0 Capabilities: [48] #08 [01e1] 00:01.1 SMBus: nVidia Corporation nForce2 SMBus (MCP) (rev a2) Subsystem: Unknown device 17f2:3401 Flags: 66Mhz, fast devsel, IRQ 12 I/O ports at bc00 Capabilities: [44] Power Management version 2 00:02.0 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4) (prog-if 10 [OHCI]) Subsystem: Unknown device 17f2:3401 Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 11 Memory at e4002000 (32-bit, non-prefetchable) Capabilities: [44] Power Management version 2 00:02.1 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4) (prog-if 10 [OHCI]) Subsystem: Unknown device 17f2:3401 Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 9 Memory at e4003000 (32-bit, non-prefetchable) Capabilities: [44] Power Management version 2 00:02.2 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4) (prog-if 20 [EHCI]) Subsystem: Unknown device 17f2:3401 Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 5 Memory at e4004000 (32-bit, non-prefetchable) Capabilities: [44] #0a [2080] Capabilities: [80] Power Management version 2 00:06.0 Multimedia audio controller: nVidia Corporation nForce2 AC97 Audio Controler (MCP) (rev a1) Subsystem: Unknown device 17f2:3401 Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 12 I/O ports at c000 I/O ports at b000 [size=128] Memory at e400 (32-bit, non-prefetchable) [size=4K] Capabilities: [44] Power Management version 2 00:08.0 PCI bridge: nVidia Corporation nForce2 External PCI Bridge (rev a3) (prog-if 00 [Normal decode]) Flags: bus master, 66Mhz, fast devsel, latency 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=32 I/O behind bridge: 9000-9fff Memory behind bridge: e200-e3ff Expansion ROM at 9000 [disabled] [size=4K] 00:09.0 IDE interface: nVidia Corporation nForce2 IDE (rev a2) (prog-if 8a [Master SecP PriP]) Subsystem: Unknown device 17f2:3401 Flags: bus master, 66Mhz, fast devsel, latency 0 I/O ports at f000 [size=16] Capabilities: [44] Power Management version 2 00:1e.0 PCI bridge: nVidia Corporation nForce2 AGP (rev c1) (prog-if 00 [Normal decode]) Flags: bus master, 66Mhz, medium devsel, latency 32 Bus: primary=00, secondary=02, subordinate=02, sec-latency=32 I/O behind bridge: a000-afff Memory behind bridge: e000-e1ff Prefetchable memory behind bridge: d800-dfff Expansion ROM at a000 [disabled] [size=4K] 01:07.0 Network controller: Individual Computers - Jens Schoenfeld Intel 537 (prog-if 80) Subsystem: Unknown device b100:0001 Flags: bus master, medium devsel, latency 160, IRQ 10 I/O ports at 9000 Memory at e3009000 (32-bit, non-prefetchable) [size=4K] Memory at ignored (32-bit, non-prefetchable) Memory at ignored (32-bit, non-prefetchable) Memory at ignored (32-bit, non-prefetchable) Memory at ignored (32-bit, non-prefetchable
Re: [Asterisk-Users] TDM400P Problems
Even when the tdm400 is the only card in the computer, it still has this problem. I'm not sure how I would go about determining what is causing it. I have reset the bios to its factory settings to see if that helped, but alas it did not. Seems like i'm screwed. Greg On 27/08/2004, at 12:12 PM, Lyle Giese wrote: My guess is that you have PCI bus compatibility problems of some sort. Moving the cards around may help. Using a plug in NIC may help. A different Motherboard may help. This looks like hardware and trial and error and experience is all you have to lead you forward, if my guess is right. Lyle - Original Message - From: Greg Hulands [EMAIL PROTECTED] To: Asterisk Users Mailing List - Non-Commercial Discussion [EMAIL PROTECTED] Sent: Thursday, August 26, 2004 8:11 PM Subject: Re: [Asterisk-Users] TDM400P Problems When I did the lspci -v when it got to the tdm400p it seemed to go into an infinite loop on this line: Capabilities: [80] #00 []. When I redirected output to a file it filled to 8MB in about 3 seconds with this line. I moved the NIC so that it would be before the tdm400p, but it still did the same thing. I haven't a clue what is going on here. Any help is greatly appreciated. Regards, Greg Here is the output: 00:00.0 Host bridge: nVidia Corporation nForce2 AGP (different version?) (rev c1) Flags: bus master, 66Mhz, fast devsel, latency 0 Memory at d000 (32-bit, prefetchable) Capabilities: [40] AGP version 2.0 Capabilities: [60] #08 [2001] 00:00.1 RAM memory: nVidia Corporation nForce2 Memory Controller 1 (rev c1) Subsystem: Unknown device 17f2:3401 Flags: 66Mhz, fast devsel 00:00.2 RAM memory: nVidia Corporation nForce2 Memory Controller 4 (rev c1) Subsystem: Unknown device 17f2:3401 Flags: 66Mhz, fast devsel 00:00.3 RAM memory: nVidia Corporation nForce2 Memory Controller 3 (rev c1) Subsystem: Unknown device 17f2:3401 Flags: 66Mhz, fast devsel 00:00.4 RAM memory: nVidia Corporation nForce2 Memory Controller 2 (rev c1) Subsystem: Unknown device 17f2:3401 Flags: 66Mhz, fast devsel 00:00.5 RAM memory: nVidia Corporation nForce2 Memory Controller 5 (rev c1) Subsystem: Unknown device 17f2:3401 Flags: 66Mhz, fast devsel 00:01.0 ISA bridge: nVidia Corporation nForce2 ISA Bridge (rev a4) Subsystem: Unknown device 17f2:3401 Flags: bus master, 66Mhz, fast devsel, latency 0 Capabilities: [48] #08 [01e1] 00:01.1 SMBus: nVidia Corporation nForce2 SMBus (MCP) (rev a2) Subsystem: Unknown device 17f2:3401 Flags: 66Mhz, fast devsel, IRQ 12 I/O ports at bc00 Capabilities: [44] Power Management version 2 00:02.0 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4) (prog-if 10 [OHCI]) Subsystem: Unknown device 17f2:3401 Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 11 Memory at e4002000 (32-bit, non-prefetchable) Capabilities: [44] Power Management version 2 00:02.1 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4) (prog-if 10 [OHCI]) Subsystem: Unknown device 17f2:3401 Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 9 Memory at e4003000 (32-bit, non-prefetchable) Capabilities: [44] Power Management version 2 00:02.2 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4) (prog-if 20 [EHCI]) Subsystem: Unknown device 17f2:3401 Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 5 Memory at e4004000 (32-bit, non-prefetchable) Capabilities: [44] #0a [2080] Capabilities: [80] Power Management version 2 00:06.0 Multimedia audio controller: nVidia Corporation nForce2 AC97 Audio Controler (MCP) (rev a1) Subsystem: Unknown device 17f2:3401 Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 12 I/O ports at c000 I/O ports at b000 [size=128] Memory at e400 (32-bit, non-prefetchable) [size=4K] Capabilities: [44] Power Management version 2 00:08.0 PCI bridge: nVidia Corporation nForce2 External PCI Bridge (rev a3) (prog-if 00 [Normal decode]) Flags: bus master, 66Mhz, fast devsel, latency 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=32 I/O behind bridge: 9000-9fff Memory behind bridge: e200-e3ff Expansion ROM at 9000 [disabled] [size=4K] 00:09.0 IDE interface: nVidia Corporation nForce2 IDE (rev a2) (prog-if 8a [Master SecP PriP]) Subsystem: Unknown device 17f2:3401 Flags: bus master, 66Mhz, fast devsel, latency 0 I/O ports at f000 [size=16] Capabilities: [44] Power Management version 2 00:1e.0 PCI bridge: nVidia Corporation nForce2 AGP (rev c1) (prog-if 00 [Normal decode]) Flags: bus master, 66Mhz, medium devsel, latency 32 Bus: primary=00, secondary=02, subordinate=02, sec-latency=32 I/O behind bridge: a000-afff Memory behind bridge: e000-e1ff Prefetchable memory behind bridge: d800-dfff Expansion ROM at a000 [disabled] [size=4K] 01:07.0 Network controller: Individual Computers - Jens Schoenfeld Intel 537 (prog-if 80) Subsystem: Unknown device b100:0001 Flags: bus master, medium devsel, latency 160, IRQ 10 I/O ports at 9000 Memory at e3009000 (32-bit
Re: [Asterisk-Users] TDM400P Problems
Have you checked to see if there is a newer bios for the motherboard? - Original Message - From: Greg Hulands [EMAIL PROTECTED] To: Asterisk Users Mailing List - Non-Commercial Discussion [EMAIL PROTECTED] Sent: Thursday, August 26, 2004 9:31 PM Subject: Re: [Asterisk-Users] TDM400P Problems Even when the tdm400 is the only card in the computer, it still has this problem. I'm not sure how I would go about determining what is causing it. I have reset the bios to its factory settings to see if that helped, but alas it did not. Seems like i'm screwed. Greg On 27/08/2004, at 12:12 PM, Lyle Giese wrote: My guess is that you have PCI bus compatibility problems of some sort. Moving the cards around may help. Using a plug in NIC may help. A different Motherboard may help. This looks like hardware and trial and error and experience is all you have to lead you forward, if my guess is right. Lyle - Original Message - From: Greg Hulands [EMAIL PROTECTED] To: Asterisk Users Mailing List - Non-Commercial Discussion [EMAIL PROTECTED] Sent: Thursday, August 26, 2004 8:11 PM Subject: Re: [Asterisk-Users] TDM400P Problems When I did the lspci -v when it got to the tdm400p it seemed to go into an infinite loop on this line: Capabilities: [80] #00 []. When I redirected output to a file it filled to 8MB in about 3 seconds with this line. I moved the NIC so that it would be before the tdm400p, but it still did the same thing. I haven't a clue what is going on here. Any help is greatly appreciated. Regards, Greg Here is the output: 00:00.0 Host bridge: nVidia Corporation nForce2 AGP (different version?) (rev c1) Flags: bus master, 66Mhz, fast devsel, latency 0 Memory at d000 (32-bit, prefetchable) Capabilities: [40] AGP version 2.0 Capabilities: [60] #08 [2001] 00:00.1 RAM memory: nVidia Corporation nForce2 Memory Controller 1 (rev c1) Subsystem: Unknown device 17f2:3401 Flags: 66Mhz, fast devsel 00:00.2 RAM memory: nVidia Corporation nForce2 Memory Controller 4 (rev c1) Subsystem: Unknown device 17f2:3401 Flags: 66Mhz, fast devsel 00:00.3 RAM memory: nVidia Corporation nForce2 Memory Controller 3 (rev c1) Subsystem: Unknown device 17f2:3401 Flags: 66Mhz, fast devsel 00:00.4 RAM memory: nVidia Corporation nForce2 Memory Controller 2 (rev c1) Subsystem: Unknown device 17f2:3401 Flags: 66Mhz, fast devsel 00:00.5 RAM memory: nVidia Corporation nForce2 Memory Controller 5 (rev c1) Subsystem: Unknown device 17f2:3401 Flags: 66Mhz, fast devsel 00:01.0 ISA bridge: nVidia Corporation nForce2 ISA Bridge (rev a4) Subsystem: Unknown device 17f2:3401 Flags: bus master, 66Mhz, fast devsel, latency 0 Capabilities: [48] #08 [01e1] 00:01.1 SMBus: nVidia Corporation nForce2 SMBus (MCP) (rev a2) Subsystem: Unknown device 17f2:3401 Flags: 66Mhz, fast devsel, IRQ 12 I/O ports at bc00 Capabilities: [44] Power Management version 2 00:02.0 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4) (prog-if 10 [OHCI]) Subsystem: Unknown device 17f2:3401 Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 11 Memory at e4002000 (32-bit, non-prefetchable) Capabilities: [44] Power Management version 2 00:02.1 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4) (prog-if 10 [OHCI]) Subsystem: Unknown device 17f2:3401 Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 9 Memory at e4003000 (32-bit, non-prefetchable) Capabilities: [44] Power Management version 2 00:02.2 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4) (prog-if 20 [EHCI]) Subsystem: Unknown device 17f2:3401 Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 5 Memory at e4004000 (32-bit, non-prefetchable) Capabilities: [44] #0a [2080] Capabilities: [80] Power Management version 2 00:06.0 Multimedia audio controller: nVidia Corporation nForce2 AC97 Audio Controler (MCP) (rev a1) Subsystem: Unknown device 17f2:3401 Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 12 I/O ports at c000 I/O ports at b000 [size=128] Memory at e400 (32-bit, non-prefetchable) [size=4K] Capabilities: [44] Power Management version 2 00:08.0 PCI bridge: nVidia Corporation nForce2 External PCI Bridge (rev a3) (prog-if 00 [Normal decode]) Flags: bus master, 66Mhz, fast devsel, latency 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=32 I/O behind bridge: 9000-9fff Memory behind bridge: e200-e3ff Expansion ROM at 9000 [disabled] [size=4K] 00:09.0 IDE interface: nVidia Corporation nForce2 IDE (rev a2) (prog-if 8a [Master SecP PriP]) Subsystem: Unknown device 17f2:3401 Flags: bus master, 66Mhz, fast devsel, latency 0 I/O ports at f000 [size=16] Capabilities: [44] Power Management version 2 00:1e.0 PCI bridge: nVidia Corporation nForce2 AGP
Re: [Asterisk-Users] TDM400P Problems
- Original Message - From: Greg Hulands [EMAIL PROTECTED] To: Asterisk Users Mailing List - Non-Commercial Discussion [EMAIL PROTECTED] Sent: Thursday, August 26, 2004 9:31 PM Subject: Re: [Asterisk-Users] TDM400P Problems Even when the tdm400 is the only card in the computer, it still has this problem. I'm not sure how I would go about determining what is causing it. I have reset the bios to its factory settings to see if that helped, but alas it did not. Seems like i'm screwed. [HUGE SNIP] Have you checked that your motherboard supports the correct PCI version. From memory the digium cards require PCI 2.2 support... Check the digium website for the exact hardware requirements, and then check your motherboard suits. Also ensure you plugged in the extra power cord to the card... Regards, Adam ___ 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
On 27/08/2004, at 12:59 PM, Adam Goryachev wrote: Have you checked that your motherboard supports the correct PCI version. From memory the digium cards require PCI 2.2 support... Yes the mobo has pci 2.2. Check the digium website for the exact hardware requirements, and then check your motherboard suits. Everything suits Also ensure you plugged in the extra power cord to the card... Yes. But to tell you the truth there was one time today were I forgot to plug it back in, but knew it when the computer wouldn't boot! :-) Greg ___ 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
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
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
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
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/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
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
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 ___
