Guys I have a problem getting a TDM400P card to go. It has 4 FXS ports (green modules) and I get this error: [root@conmutador root]# ztcfg -vvvvv Zaptel Configuration ===================== Channel map: Channel 01: FXS Kewlstart (Default) (Slaves: 01) Channel 02: FXS Kewlstart (Default) (Slaves: 02) Channel 03: FXO Kewlstart (Default) (Slaves: 03) Channel 04: FXO Kewlstart (Default) (Slaves: 04) Channel 05: FXO Kewlstart (Default) (Slaves: 05) Channel 06: FXO Kewlstart (Default) (Slaves: 06) 6 channels configured. ZT_CHANCONFIG failed on channel 3: Invalid argument (22) Did you forget that FXS interfaces are configured with FXO signalling and that FXO interfaces use FXS signalling? My zaptel.conf reads: [root@conmutador root]# more /etc/zaptel.conf fxsks=1 fxsks=2 fxoks=3-6 loadzone=us defaultzone=us And my rc.local loads: /sbin/modprobe zaptel /sbin/modprobe wcfxo /sbin/modprobe wctdm The 2 100p cards load perfectly but the TDM is not. Any ideas?
Guys I have a problem getting a TDM400P card to go. It has 4 FXS ports (green modules) and I get this error: [root@conmutador root]# ztcfg -vvvvv Zaptel Configuration ===================== Channel map: Channel 01: FXS Kewlstart (Default) (Slaves: 01) Channel 02: FXS Kewlstart (Default) (Slaves: 02) Channel 03: FXO Kewlstart (Default) (Slaves: 03) Channel 04: FXO Kewlstart (Default) (Slaves: 04) Channel 05: FXO Kewlstart (Default) (Slaves: 05) Channel 06: FXO Kewlstart (Default) (Slaves: 06) 6 channels configured. ZT_CHANCONFIG failed on channel 3: Invalid argument (22) Did you forget that FXS interfaces are configured with FXO signalling and that FXO interfaces use FXS signalling? My zaptel.conf reads: [root@conmutador root]# more /etc/zaptel.conf fxsks=1 fxsks=2 fxoks=3-6 loadzone=us defaultzone=us And my rc.local loads: /sbin/modprobe zaptel /sbin/modprobe wcfxo /sbin/modprobe wctdm The 2 100p cards load perfectly but the TDM is not. Any ideas?
Anton Krall wrote:> Guys > > I have a problem getting a TDM400P card to go. > > It has 4 FXS ports (green modules) and I get this error: > > [root@conmutador root]# ztcfg -vvvvv > > Zaptel Configuration > =====================> > > Channel map: > > Channel 01: FXS Kewlstart (Default) (Slaves: 01) > Channel 02: FXS Kewlstart (Default) (Slaves: 02) > Channel 03: FXO Kewlstart (Default) (Slaves: 03) > Channel 04: FXO Kewlstart (Default) (Slaves: 04) > Channel 05: FXO Kewlstart (Default) (Slaves: 05) > Channel 06: FXO Kewlstart (Default) (Slaves: 06) > > 6 channels configured. > > ZT_CHANCONFIG failed on channel 3: Invalid argument (22) > Did you forget that FXS interfaces are configured with FXO signalling > and that FXO interfaces use FXS signalling? > > My zaptel.conf reads: > > [root@conmutador root]# more /etc/zaptel.conf > fxsks=1 > fxsks=2 > fxoks=3-6Why do you configure 6 channels if you only have 4 FXS? Try fxsks=1-4 regards, klaus> loadzone=us > defaultzone=us > > And my rc.local loads: > > /sbin/modprobe zaptel > /sbin/modprobe wcfxo > /sbin/modprobe wctdm > > The 2 100p cards load perfectly but the TDM is not. > > Any ideas? > > _______________________________________________ > 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 > >
> Guys > > I have a problem getting a TDM400P card to go. > > It has 4 FXS ports (green modules) and I get this error: > > [root@conmutador root]# ztcfg -vvvvv > > Zaptel Configuration > =====================> > > Channel map: > > Channel 01: FXS Kewlstart (Default) (Slaves: 01) Channel 02: > FXS Kewlstart (Default) (Slaves: 02) Channel 03: FXO > Kewlstart (Default) (Slaves: 03) Channel 04: FXO Kewlstart > (Default) (Slaves: 04) Channel 05: FXO Kewlstart (Default) > (Slaves: 05) Channel 06: FXO Kewlstart (Default) (Slaves: 06) > > 6 channels configured. > > ZT_CHANCONFIG failed on channel 3: Invalid argument (22) Did > you forget that FXS interfaces are configured with FXO > signalling and that FXO interfaces use FXS signalling? > > My zaptel.conf reads: > > [root@conmutador root]# more /etc/zaptel.conf > fxsks=1 > fxsks=2 > fxoks=3-6 > loadzone=us > defaultzone=us > > And my rc.local loads: > > /sbin/modprobe zaptel > /sbin/modprobe wcfxo > /sbin/modprobe wctdm > > The 2 100p cards load perfectly but the TDM is not. > > Any ideas?Could you post the contents of dmesg that are relavant when you load the modules?? Just want to make sure that things are actually loading in the order you have your zapatel.conf set for. It sounds like the cards are not loading in the same order you have the channels configed for. Robert
How do I remove it from kudzu? |-----Original Message----- |From: asterisk-users-bounces@lists.digium.com |[mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of |Robert Webb |Sent: Viernes, 29 de Abril de 2005 08:57 a.m. |To: Asterisk Users Mailing List - Non-Commercial Discussion |Subject: RE: [Asterisk-Users] Problems with TDM400P card | |> |> Zttool shows nothing inside thebox. |> |> I tried removing the x100 cards, moving the tdm card around, |disabled |> all usb and unnecessary stuff still, kudzu when booting up shows the |> card and the card shows up on /etc/sysconfig/hwconf but I wonder why |> it shows 2 of these and I only have 1 tdm400p card with 1 module |> | | |If I remember correctly, when I installed asterisk@home and it |did its reboot, the TDM was removed from kudzu as it loaded |the linux zaptel and you want to load the zaptel obtained from |Digium. Try removing it permanantly from kudzu then try |loading your modules. | |Robert | | | |_______________________________________________ |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 | |
I would also be interested in alternatives to the Tdm400p. I have had endless
problems with a tdm400p card not being able to get the zttest numbers above
99.975 and as a result not being able eliminate an intermitent but consistent
echo.I have tried to date 4 different motherboard and hardware combinations as
well as different linux versions to no avial.I would welcome some feedback on
this.
Geoffrey Sachs
----- Original Message -----
From: Anton Krall <akrall-lists@intruder.com.mx>
Date: Friday, April 29, 2005 11:54 am
Subject: RE: [Asterisk-Users] Problems with TDM400P card
> Which card do you recommend using instead of the tdm400p?
>
> |-----Original Message-----
> |From: asterisk-users-bounces@lists.digium.com
> |[asterisk-users-bounces@lists.digium.com] On Behalf Of
> |John Novack
> |Sent: Viernes, 29 de Abril de 2005 09:19 a.m.
> |To: Asterisk Users Mailing List - Non-Commercial Discussion
> |Subject: Re: [Asterisk-Users] Problems with TDM400P card
> |
> |Anton Krall wrote:
> |> Zttool shows nothing inside thebox.
> |I have had similar problems with a TDM400 and CERTAIN
> |Motherboards which are PCI 2.2 but the TDM400 is not seen, in
> |my case, AT ALL The one I have reports it as an E/F but the
> |silk-screen clearly says H, Digium contends there is no
> |problem with the card, the reporting of different version
> |numbers is a "known bug" but doesn't prevent the card from
> |working, and because I can place it in another machine and get
> |it working, they refuse to acknowledge there is any defect in
> |the board.
> |
> |Perhaps a different motherboard? That is Digium's answer.
> |Just keep going through hardware that otherwise meets
> |published specs until you find one that works.
> |
> |I have to conclude that, due to Digiums refusal to acknowledge
> |there are problems with the design, ( and there are more I
> |won't bore you with ) and no willingness to address the issues
> |that have been raised on this list time and time again, that
> |the TDM400 should be considered a "card of last resort" when
> |absolutely nothing else will work.
> |Seems their IAXy falls into that same classification.
> |Can't say about their T1/E1 cards
> |
> |JMO
> |
> |John Novack
> |
> |
> |>
> |> I tried removing the x100 cards, moving the tdm card around,
> |disabled
> |> all usb and unnecessary stuff still, kudzu when booting up
> shows the
> |> card and the card shows up on /etc/sysconfig/hwconf but I
> wonder why
> |> it shows 2 of these and I only have 1 tdm400p card with 1 module
> |>
> |> class: MODEM
> |> bus: PCI
> |> detached: 1
> |> driver: hisax
> |> desc: "Tiger Jet Network Inc.|Intel 537"
> |> vendorId: e159
> |> deviceId: 0001
> |> subVendorId: 8086
> |> subDeviceId: 0003
> |> pciType: 1
> |> -
> |> class: MODEM
> |> bus: PCI
> |> detached: 1
> |> driver: hisax
> |> desc: "Tiger Jet Network Inc.|Intel 537"
> |> vendorId: e159
> |> deviceId: 0001
> |> subVendorId: 8086
> |> subDeviceId: 0003
> |> pciType: 1
> |>
> |> Still, interrupts doesn't show the card
> |>
> |> [root@conmutador root]# cat /proc/interrupts
> |> CPU0
> |> 0: 3994353 XT-PIC timer
> |> 1: 2 XT-PIC keyboard
> |> 2: 0 XT-PIC cascade
> |> 8: 1 XT-PIC rtc
> |> 10: 95510 XT-PIC eth0
> |> 14: 129871 XT-PIC ide0
> |> NMI: 0
> |> ERR: 0
> |>
> |> And when trying to load the drvier
> |>
> |> [root@conmutador root]# modprobe zaptel [root@conmutador root]#
> |> modprobe wctdm
> |> /lib/modules/2.4.20-8/misc/wctdm.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.20-8/misc/wctdm.o: insmod
> |> /lib/modules/2.4.20-8/misc/wctdm.o failed
> |> /lib/modules/2.4.20-8/misc/wctdm.o: insmod wctdm failed You
> have new
> |> mail in /var/spool/mail/root
> |>
> |> I tried using diff. modules with no luck.,..... Could be the
> |mobo itself?
> |>
> |>
> |>
> |> |-----Original Message-----
> |> |From: asterisk-users-bounces@lists.digium.com
> |> |[asterisk-users-bounces@lists.digium.com] On Behalf Of Rich
> |> |Adamson
> |> |Sent: Viernes, 29 de Abril de 2005 08:59 a.m.
> |> |To: Asterisk Users Mailing List - Non-Commercial Discussion
> |> |Subject: Re: [Asterisk-Users] Problems with TDM400P card
> |> |
> |> |> I have a problem getting a TDM400P card to go.
> |> |>
> |> |> It has 4 FXS ports (green modules) and I get this error:
> |> |>
> |> |> [root@conmutador root]# ztcfg -vvvvv
> |> |>
> |> |> Zaptel Configuration
> |> |> =====================> |> |>
> |> |>
> |> |> Channel map:
> |> |>
> |> |> Channel 01: FXS Kewlstart (Default) (Slaves: 01) Channel 02:
> FXS
> |> |> Kewlstart (Default) (Slaves: 02) Channel 03: FXO Kewlstart
> |> |> (Default)
> |> |> (Slaves: 03) Channel 04: FXO Kewlstart (Default) (Slaves:
> |> |04) Channel
> |> |> 05: FXO Kewlstart (Default) (Slaves: 05) Channel 06: FXO
> Kewlstart|> |> (Default) (Slaves: 06)
> |> |>
> |> |> 6 channels configured.
> |> |>
> |> |> ZT_CHANCONFIG failed on channel 3: Invalid argument (22) Did
> you
> |> |> forget that FXS interfaces are configured with FXO
> |> |signalling and that
> |> |> FXO interfaces use FXS signalling?
> |> |>
> |> |> My zaptel.conf reads:
> |> |>
> |> |> [root@conmutador root]# more /etc/zaptel.conf
> |> |> fxsks=1
> |> |> fxsks=2
> |> |> fxoks=3-6
> |> |> loadzone=us
> |> |> defaultzone=us
> |> |>
> |> |> And my rc.local loads:
> |> |>
> |> |> /sbin/modprobe zaptel
> |> |> /sbin/modprobe wcfxo
> |> |> /sbin/modprobe wctdm
> |> |>
> |> |> The 2 100p cards load perfectly but the TDM is not.
> |> |>
> |> |> Any ideas?
> |> |
> |> |What does zttool indicate?
> |> |
> |> |Have you tried moving the cards around in different slots?
> |> |
> |> |Any shared interrupt issues?
> |> |
> |> |Try loading wctdm before wcfxo.
> |> |
> |> |Try removing the x100p's and loading the TDM card only. Any
> issues?|
> |_______________________________________________
> |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
> |
> |
>
> _______________________________________________
> 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
>
On Fri, April 29, 2005 4:58 pm, GEOFFREY SACHS said:> I would also be interested in alternatives to the Tdm400p. I have had endless > problems with a tdm400p card not being able to get the zttest numbers above > 99.975 and as a result not being able eliminate an intermitent but consistent echo. > I have tried to date 4 different motherboard and hardware combinations as > well as different linux versions to no avial.I would welcome some feedback on this.Since there appear to be several combinations of hardware and operating system which don't work well, here is a combination which appears to work fairly well: Intel 925XCV mb P-4 560 (3.6 gHz) wcfxs0: <Wildcard TDM400P REV E/F> FreeBSD 5.4-STABLE zttest -v Opened pseudo zap interface, measuring accuracy... 8192 samples in 8192 sample intervals 100.000000% 8192 samples in 8192 sample intervals 100.000000% 8192 samples in 8192 sample intervals 100.000000% 8192 samples in 8192 sample intervals 100.000000% 8192 samples in 8192 sample intervals 100.000000% 8192 samples in 8192 sample intervals 100.000000% 8192 samples in 8192 sample intervals 100.000000% 8192 samples in 8192 sample intervals 100.000000% 8192 samples in 8192 sample intervals 100.000000% 8192 samples in 8192 sample intervals 100.000000% ^C --- Results after 10 passes --- Best: 100.000000 -- Worst: 100.000000 -- Average: 100.000000 hope this helps -kim -- w8hdkim@gmail.com
On Sat, April 30, 2005 10:52 am, Rich Adamson said:>> On Fri, April 29, 2005 4:58 pm, GEOFFREY SACHS said: >> >>> I would also be interested in alternatives to the Tdm400p. I have >>> had endless problems with a tdm400p card not being able to get >>> the zttest numbers above 99.975 and as a result not being able >>> eliminate an intermitent but consistent echo.> Kim, that is helpful. I'm not a FreeBSD user, but does it have a > vmstat utility?Has vmstat, you might like FreeBSD.. :)> If so, what do see if you run 'vmstat 1' and let it run for about > twenty seconds? Do you see the cpu utilization going to about 100% > every five or six seconds?Negative: vmstat 1 procs memory page disk faults cpu r b w avm fre flt re pi po fr sr ad4 in sy cs us sy id 1 2 0 61684 966260 7 0 0 0 6 0 0 1326 392 482 0 0 99 0 2 0 61684 966260 1 0 0 0 1 0 0 1337 501 494 0 1 99 0 2 0 61684 966260 0 0 0 0 0 0 0 1345 486 490 0 0 100 0 2 0 61684 966260 0 0 0 0 0 0 6 1350 492 509 0 2 98 0 2 0 61684 966260 0 0 0 0 0 0 0 1344 488 490 1 0 99 0 2 0 61684 966260 0 0 0 0 0 0 0 1344 492 489 0 0 100 0 2 0 61684 966260 0 0 0 0 0 0 0 1345 494 488 0 0 100 0 2 0 61684 966260 0 0 0 0 0 0 0 1344 492 493 0 0 100 0 2 0 61684 966260 0 0 0 0 0 0 0 1344 488 490 0 0 100 0 2 0 61684 966260 0 0 0 0 0 0 0 1344 492 490 0 0 100 0 2 0 61684 966260 0 0 0 0 0 0 0 1345 486 487 0 1 99 0 2 0 61684 966260 0 0 0 0 0 0 0 1344 513 494 0 0 100 0 2 0 61684 966260 0 0 0 0 0 0 0 1344 494 494 0 0 100 0 2 0 61684 966260 0 0 0 0 0 0 0 1345 492 492 0 0 100 0 2 0 61684 966260 0 0 0 0 0 0 0 1344 486 487 0 0 100 0 2 0 61684 966260 0 0 0 0 0 0 0 1344 492 490 0 0 100 0 2 0 61684 966260 0 0 0 0 0 0 0 1344 496 491 0 0 100 0 2 0 61684 966260 0 0 0 0 0 0 0 1345 492 491 0 0 100 0 2 0 61684 966260 0 0 0 0 0 0 1 1345 486 491 0 0 100 0 2 0 61684 966260 0 0 0 0 0 0 0 1344 492 490 0 0 100 ^C -kim -- w8hdkim@yahoo.com
On Mon, May 2, 2005 1:12 am, Geoffrey Sachs said:> Thanks for the info. > What hard drives are you using ide or serial ata. Does it make a > difference. ThanksThere have been some references recently regarding disk drive types relating to tdm400 noise problems. Has anyone established there is a correlation between drive hardware and noise? If this is the case, it may be indicative of marginal interrupt timng performance on that hardware. FWIW the system described earlier has a single sata drive attached to the Intel 925XCV mb on-board controller, from dmesg: atapci1: <Intel ICH6 SATA150 controller> The drive is a Seagate ST3250823: ad4: 238475MB <ST3250823AS/3.01> -kim -- w8hdkim@gmail.com
On Mon, May 2, 2005 8:24 am, Rich Adamson said:> To help identify the source of the delays, I built a new system this > weekend from scratch. When that is complete, I'll use it to compare > the differences in motherboards, OS distro's, and maybe kernel versions.Very good Rich, the results of that work will be very interesting. Realtime scheduling modifications for Linux and FreeBSD are discussed on Mantis at: http://bugs.digium.com/bug_view_page.php?bug_id=0003203 Should you decide to evaluate Asterisk on FreeBSD, you might want to take a look at Staffan Ulfberg's excelllent contribution on the above site, with links to patches near the bottom of the page. The system described in my recent post was built from * CVS Head of 4-22-05 with these patches applied, with the exception of the changes which cause Asterisk to lower it's priority to normal after forking. The zaptel drivers for FreeBSD are from 4-26-05, downloaded from the Subversion repostory as described at: http://www.voip-info.org/wiki-FreeBSD+zaptel Patches to the zaptel drivers are described on the Mantis link above. -kim
On Tue, May 03, 2005 at 05:27:33PM +0000, Tony Mountifield wrote:> In article <Chameleon.1115129364.adar0@vegas>, > Rich Adamson <radamson@routers.com> wrote: > > - a modified zttest.c run on both systems to show the delays in reading > > 8192 bytes from the TDM card as 23,850 microseconds lateness on > > the old mobo, and 24,000 microsecond lateness on the new system. No > > significant change resulting from the differences in mobo, pci > > structure, interrupt structure, cpu speed, quantity of ram, kernel > > differences (v2.4 vs v2.6), etc. > > See my response to your zttest-mod.c posting. I think it is 8000 bytes > that are due every second, not 8192. That would make the timing on your > new system pretty accurate if 8192 bytes are arriving in 1,024,000us.Tony is correct. You should expect 8000 octets/sec from a digital sampler on a POTS line interface. http://lists.digium.com/pipermail/asterisk-users/2005-May/105148.html Reference: http://www.ncta.com/industry_overview/cableGlossary.cfm?indOverviewID=41 Sample Rate - In analog to digital signal processing, the sample rate is the interval at which samples of an analog signal are taken. The sample rate for digital telephony, for example, is 8000 per second. http://www.freesoft.org/CIE/Topics/127.htm G.711 is the international standard for encoding telephone audio on an 64 kbps channel. It is a pulse code modulation (PCM) scheme operating at a 8 kHz sample rate, with 8 bits per sample. According to the Nyquist theorem, which states that a signal must be sampled at twice its highest frequency component, G.711 can encode frequencies between 0 and 4 kHz. Telcos can select between two different varients of G.711: A-law and mu-law. A-law is the standard for international circuits. -- Mike
> -----Original Message----- > From: Adam Goryachev [mailto:mailinglists@websitemanagers.com.au] > Sent: Thursday, May 05, 2005 10:53 PM > To: Asterisk Users Mailing List - Non-Commercial Discussion > Subject: Re: [Asterisk-Users] Re: Problems with TDM400P card > > > On Thu, 2005-05-05 at 12:11 -0400, Andrew Kohlsmith wrote: > > On May 5, 2005 11:13 am, Mike Mueller wrote: > > > > Couple this with the fact that the driver now seems to pull 100% CPU > > > > every 5 seconds or so and it didn't before and I think we have a good > > > > case for there being something weird in the driver that is causing frame > > > > slips or other weirdness that is generally not audible for most people > > > > but wreaks havoc even for G3 or ECM (I think that's the term for > > > > error-correcting fax) fax machines. > > > > > > As measured with top? > > > > No; vmstat 1, without anything (not even asterisk) running. > > > > Driver unloaded: no spiking. Driver loaded: spiking. > > Of the three machines running asterisk just now, none of them display > this 'spike' as described. This was while asterisk was running etc as > well. >{clip} I also observe this spiking behavior with a t100p and cvs-head. I'm running kernel 2.6.11.8 with the realtime patches applied and see the cpu time going to the kthread servicing the interrupt that t100p is on (IRQ 9 in my case), with or without asterisk itself running. This occurs even after raising the priority of the IRQ 9 kthread to the highest priority process. However, this on its own doesn't noticeably affect the audio - small timing defects on the T1 can usually be noticed by dialing into a milliwatt() target on the problem box across that link. That said, perhaps the jitter is too slight to hear on a 1004hz sign wave and needs a T1 analyzer to detect properly. Kris Boutilier Information Systems Coordinator Sunshine Coast Regional District