[Asterisk-Users] UK (British Telecom) Caller ID again
David J Carter
david.carter at codepipe.com
Tue Sep 28 09:38:17 MST 2004
Patrick,
This is my zapata.conf, slight mod from the one sent you off list, but works
with caller ID on both BT and Telewest.
; Zapata telephony interface
; Configuration file
;
[channels]
language=uk
rxink=300 ; Atlas seems to use long (250ms) winks
usecallerid=yes
cidsignalling=v23
cidstart=polarity
restrictcid=no
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=yes
relaxdtmf=yes
rxgain=0.0
txgain=2.0
group=1
callgroup=1
pickupgroup=1
immediate=no
callerid=asreceived
busydetect=yes
musiconhold=default
context=incoming
signalling=fxs_ks
channel => 1-2
signalling=fxo_ks
context=default
channel => 3-4
Check you lines for the fxs_ks and fxo_fs, also don't think you need the
ukcallerid anymore.
Dave
-----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
More information about the asterisk-users
mailing list