search for: ukcallerid

dear all, i am looking to enable CALLERID on an Asterisk system comprising a X101P FXO interface connecting to BT PSTN in the uk seems this is supported by the interface but there seems to be varying information on how to enable it in zapata.conf 1. usecallerid=uk 2. ukcallerid=yes being two of the configuration statements offered TIA GT

...2085034825=${CALLERID}${EXTEN}) exten => s,2,Dial(SIP/12345,20,tr) can anyone please help what could be the problem. My Zapata.conf: [channels] busydetect=1 busycount=7 relaxdtmf=yes callwaiting=yes callwaitingcallerid=yes threewaycalling=yes transfer=yes cancallforward=yes usecallerid=yes ukcallerid=yes echotraining=yes echocancel=yes echocancelwhenbridged=yes jitterbuffers=4 rxgain=0.0 txgain=0.0 group=1 pickupgroup=1-4 immediate=no context=default signalling=fxs_ks callerid=asreceived channel=1 Am I missing anything here? Kannaiyan

...g Sep 28 13:08:03 WARNING[20498]: chan_zap.c:3404 zt_handle_event: Didn't finish Caller-ID spill. Cancelling. I know for certain that caller id is working on this line. Any pointers on where I am going wrong, or how I can effectively debug this? I've also tried including the legacy "ukcallerid=yes" in zapata.conf. It makes no difference. If I can arrive at a definitive solution, I'll post it to the wiki. Many thanks, Patrick

...ocancelwhenbridged=no echotraining=300 immediate=no busydetect=no busycount=5 answeronpolarityswitch=yes hanguponpolarityswitch=yes callprogress=yes callwaiting=yes relaxdtmf=no progzone=uk useincomingcalleridonzaptransfer = yes usecallerid=no callerid=asreceived cidsignalling=v23 cidstart=polarity ukcallerid=yes channel => 4 # sip.conf [general] allow=ulaw allow=alaw allow=gsm allow=g723.1 context=incoming recordhistory=yes port=5060 bindaddr=0.0.0.0 srvlookup=yes tos=lowdelay defaultexpirey=120 nat=no localnet=192.168.0.0/255.255.252.0 [ronan] regextension=ronan regcontext=4L mailbox=100@default...

Hi, I'm currently running asterisk 1.0.9-r1 and zaptel 1.0.9_p1-r1 (the current gentoo ~x86 versions), with the UK CallerID patches from http://www.lusyn.com/asterisk/patches.html applied. The Zap interface itself seems to work fairly well - although it's a little quiet, there is no echo. Unfortunately, there's also no CallerID. My zapata.conf is as follows: [channels]

...1946622960") in new stack<br>&nbsp;&nbsp;&nbsp; -- Executing LookupCIDName("Zap/4-1", "") in new stack<br><br><br><br><br>zapata.conf<br><br>[channels]<br>switchtype=national<br>usecallerid=yes<br>ukcallerid=yes<br>cidsignalling=v23<br>cidstart=polarity<br>hidecallerid=no<br>sendcalleridafter=2<br>callwaiting=yes<br>;answeronpolarityswitch=no<br>usecallingpres=yes<br>callwaitingcallerid=yes<br>threewaycalling=yes<br>transfer=yes<br>canpa...

...faultzone = uk # alaw=1,2,3,4 chan_dahdi.conf - channel 4 (fxs) language=en context=incomming signalling=fxs_ks ;rxwink=300 ; Atlas seems to use long (250ms) winks ; ; Whether or not to do distinctive ring detection on FXO lines ; ;usedistinctiveringdetection=yes usecallerid=yes ;ukcallerid=yes cidsignalling=v23 ; Added for UK CLI detection cidstart=polarity ; Added for UK CLI detection restrictcid=no callerid=asreceived ;sendcalleridafter=0 polarityonanswerdelay=10 ;answeronpolarityswitch=yes ;hanguponpolarityswitch=yes resetpolarityonring=no busydetect=no callprogress=no ;progzone=u...

Hi All, Having searched the archives, I can see there has been much discussion at various points regarding capture of caller id information from good old BT. If I understand correctly, it seems that not only do the drivers not currently support it, but my X101P possibly/probably can't do it anyway due to hardware? So, that leaves me with the modem route, which seems more and more unlikely,