Umm what I am thinking is that maybe * is dropping the call due to a codec issue. can u send more details on your setup eg, sip->asterisk->zap ?? inbound call goes zap->asterisk->h323?

-Kiel

----- Original Message ----- From: "Kirk Davis" <[EMAIL PROTECTED]>
To: "'Asterisk on BSD discussion'" <[email protected]>
Sent: Wednesday, May 04, 2005 12:30 AM
Subject: RE: [Asterisk-bsd] Zaptel X100P card dropping calls



Hmmm...  I'm not sure where to go from here then.

I removed all unneeded hardware from the system and also made sure the X100P
card was locked down to it's own interrupt. I cvs'ed up my FreeBSD to the
latest 5.3 (I'm waiting until 5.4 is out of RC status) and rebuilt the
asterisk and zaptel ports.


The only thing I have added from the stock install was to create the
/usr/local/etc/zaptel.conf file as follows:

# Span 1: WCFXO/0 "Generic Clone Board 1"
fxsks=1
# Global data
loadzone        = us
defaultzone     = us

I also changed the default /usr/local/etc/asterisk/zapata.conf.  I changed
the signalling to signalling=fxs_ks and added channel => 1 at the end.

If I don't run asterisk it will not pick up the call, just rings. When I run
asterisk it will answer the call after the third ring but then just drops
the call right away but asterisk doesn't detect the dropped call and
continues to go though it's Background tasks.


I'm stuck now and will even accept and wild guesses ;-)

---- Kirk

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Kiel R Stirling
Sent: May 2, 2005 5:02 PM
To: Asterisk on BSD discussion
Subject: Re: [Asterisk-bsd] Zaptel X100P card dropping calls


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" <[EMAIL PROTECTED]>
To: "Asterisk on BSD discussion" <[email protected]>
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
[email protected]
http://lists.digium.com/mailman/listinfo/asterisk-bsd

_______________________________________________ Asterisk-BSD mailing list [email protected] http://lists.digium.com/mailman/listinfo/asterisk-bsd


_______________________________________________ Asterisk-BSD mailing list [email protected] http://lists.digium.com/mailman/listinfo/asterisk-bsd _______________________________________________ Asterisk-BSD mailing list [email protected] http://lists.digium.com/mailman/listinfo/asterisk-bsd


_______________________________________________ Asterisk-BSD mailing list [email protected] http://lists.digium.com/mailman/listinfo/asterisk-bsd

Reply via email to