[Asterisk-bsd] Zaptel X100P card dropping calls
Kiel R Stirling
kiel at knss.net
Mon May 2 18:01:48 CDT 2005
Hi,
I run 5.3-STABLE with an XP clone and the ported versions of the required
software. Touch wood, so far I've been really happy with the results. Are
you sure its not an interrupt problem? I've seen hardware clashes do funny
things to theses cards.
-Kiel
----- Original Message -----
From: "Luigi Rizzo" <rizzo at icir.org>
To: "Asterisk on BSD discussion" <asterisk-bsd at lists.digium.com>
Sent: Tuesday, May 03, 2005 8:39 AM
Subject: Re: [Asterisk-bsd] Zaptel X100P card dropping calls
> no idea about 5.3 but things do work for me on FreeBSD 4.11 with
> the driver in the ports (patched to fix a bug in the loader glue
> that should affect only 4.x)
>
> cheers
> luigi
>
> On Mon, May 02, 2005 at 04:28:59PM -0600, Kirk Davis wrote:
>> Hi,
>> I'm not sure if this is a zaptel-bsd driver problem or asterisk. I
>> have looked through the archives with out much luck.
>>
>> I have a X100P Clone Card. It works perfectly find under linux.
>> I'm now trying to get Asterisk 1.0.7 (from the ports) working under
>> FreeBSD
>> 5.3. I have tried the zaptel drivers from the ports collection and also
>> the
>> latest SVN snapshot with the same results.
>>
>> When I dial the number of the POTS line that the zaptel card is
>> connected to, asterisk detects the incoming call. The line rings 3 time
>> (one more after the Answer("Zap/1-1", "") line shows on asterisk). Then
>> the
>> line is dropped by the X100P card. Asterisk doesn't seem to detect the
>> dropped call because it goes on to try and play the background message I
>> have and then eventually times out. I get the Timeout message long after
>> the call is already dropped.
>>
>> Here is what I see under asterisk:
>>
>> -- Starting simple switch on 'Zap/1-1'
>> May 2 16:15:37 NOTICE[55666]: chan_zap.c:5626 ss_thread: Got event
>> 2 (Ring/Answered)...
>> -- Executing Answer("Zap/1-1", "") in new stack
>> -- Executing BackGround("Zap/1-1", "demo-instruct") in new stack
>> -- Playing 'demo-instruct' (language 'en')
>> May 2 16:16:55 WARNING[55666]: pbx.c:1949 ast_pbx_run: Timeout, but
>> no rule 't' in context 'default'
>> -- Hungup 'Zap/1-1'
>>
>> Any ideas where to begin trouble shooting this?
>>
>> Here is the zaptel device information from dmesg
>>
>> May 1 11:33:17 devel kernel: Zapata Telephony Interface Registered
>> on major 196
>> May 1 11:33:17 devel kernel: ZapTel device: vendor=e159 device=1
>> subvendor=8086
>> May 1 11:33:17 devel kernel: wcfxo0: <Generic Clone> port
>> 0x9800-0x98ff mem 0xf9023000-0xf9023fff irq 22 at device 11.0 on pci2
>> May 1 11:33:17 devel kernel: ZapTel Attach for wcfxo0: deviceID :
>> 0xe159
>> May 1 11:33:17 devel kernel: wcfxo0: [GIANT-LOCKED]
>> May 1 11:33:18 devel kernel: wcfxo: DAA mode is 'FCC'
>> May 1 11:33:18 devel kernel: Found a Wildcard FXO: Generic Clone
>> May 1 11:33:18 devel kernel: ZapTel device loaded.
>> May 1 11:33:42 devel kernel: Registered tone zone 0 (United States
>> / North America)
>>
>> ----- Kirk
>
>> _______________________________________________
>> Asterisk-BSD mailing list
>> Asterisk-BSD at lists.digium.com
>> http://lists.digium.com/mailman/listinfo/asterisk-bsd
>
> _______________________________________________
> Asterisk-BSD mailing list
> Asterisk-BSD at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-bsd
>
More information about the Asterisk-BSD
mailing list