[Asterisk-Users] UK (British Telecom) Caller ID again

[Edward Eastman]

My guesses (and they are only guesses - I'm no expert, this is based purely
on my experience with messing around with this) would be:

You have ukcallerid=yes also present in the file, I'd try removing this and
seeing if it has any effect - I've a feeling this broke my setup when I
still had it in - maybe there's some legacy code still in there?

Is dring detection still done via a patch - if so could that be breaking
CID?

When you tried commenting out the rxgain=10 did you do a full reload of the
zaptel drivers as well as asterisk, I've been unable to find a definitive
answer on this, but some posters at least recommend doing this whenever you
make zapata.conf changes.


On an unrelated note I'd be interested to hear your experiences with
busydetect/callprogress, for me they did nothing at best and introduced
frequent random hang-ups at worst.

Ed

-----Original Message-----
From: asterisk-users-bounces at lists.digium.com
[mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Patrick
Lidstone (Personal e-mail)
Sent: 28 September 2004 16:34
To: asterisk-users at lists.digium.com
Subject: RE: [Asterisk-Users] UK (British Telecom) Caller ID again

Thanks Edward, Ian et al.

I'm getting warmer. With Edwards:

Cidsignalling=v23
Cidstart=polarity
Usecallerid=yes

I now see:

    -- Starting simple switch on 'Zap/4-1'
Sep 28 14:47:35 NOTICE[19476]: chan_zap.c:5119 ss_thread:  Got event 17
(Event 1
7)...
    -- Detected ring pattern: 332,0,0
 Sep 28 14:47:41 WARNING[19476]: chan_zap.c:5190 ss_thread:  CallerID
returned w
ith error on channel 'Zap/4-1'
     -- Executing Dial("Zap/4-1", "zap/1&zap/2&zap/5|120|Ttr") in new
stack
     -- Called 1
     -- Called 2
     -- Called 5
    -- Zap/1-1 is ringing
    -- Zap/2-1 is ringing
    -- Zap/5-1 is ringing
    -- Zap/1-1 is ringing
    -- Zap/2-1 is ringing
    -- Zap/5-1 is ringing
Sep 28 14:47:42 WARNING[19476]: chan_zap.c:3404 zt_handle_event:  Didn't
finish
Caller-ID spill.  Cancelling.
     -- Zap/1-1 is ringing

There's no obvious clue as to what is causing the error. Sometimes there
is no error reported immediately after the ring pattern detect, and I
just see the later caller-id spill lines. I currently have rxgain=10,
but commenting that out and restarting doesn't seem to make any
difference. Any more ideas? Here is my current zapata.conf in part:

[channels]
echocancel=yes
echocancelwhenbridged=yes
language=en
usecallerid=yes
cidsignalling=v23
cidstart=polarity
ukcallerid=yes
busydetect=yes
busycount=5
callprogress=yes
rxgain=10
;
; Analogue phone interface
mailbox=3001 at intern
context=intern
signalling=fxo_ks
callerid="3001"
channel=>1
;
;
mailbox=3002 at default
context=intern
signalling=fxo_ks
callerid="3002"
mailbox=3002 at intern
context=intern
signalling=fxo_ks
callerid="3002"
channel=>2
;
;
signalling=fxs_ks
context=main-line-7711
usedistinctiveringdetection=yes
dring1=247,159,0
dring1context=dummy
;
channel=>3
;
;
signalling=fxs_ks
context=main-line-5555
channel=>4
;

PS. Telappliant will supply TDM400's in the UK, but do not supply FXO
modules because "they haven't been certified". Cost wise, there isn't a
big difference between Telappliant and going direct to digium, and
digium was, ironically, faster (for me).

Patrick

_______________________________________________
Asterisk-Users mailing list
Asterisk-Users at 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