thr3ads.net - asterisk users - [Asterisk-Users] UK (British Telecom) Caller ID again [Sep 2004]

If this information is useful, please help other people find it:
Share via:

Patrick Lidstone (Personal e-mail)

2004-Sep-28 05:21 UTC

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

I've followed the recent thread on caller id with UK British Telecom
networks (where the caller id data is delivered before the first ring).
My understanding is that if I use a recent CVS head (e.g.
CVS-HEAD-09/18/04-17:45:52) and a TDM400 with FXO modules, all I need to
do is include the line:

usecallerid=uk 

In my zapata.conf (in the [channels] section)

I've done this, but I get:

Sep 28 13:08:02 NOTICE[20498]: chan_zap.c:5119 ss_thread:  Got event 2
(Ring/An
wered)...
    -- Detected ring pattern: 247,97,0
    -- 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
    -- Zap/1-1 is ringing
    -- Zap/2-1 is ringing
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

steve@daviesfam.org

2004-Sep-28 05:32 UTC

head link

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

On Tue, 28 Sep 2004, Patrick Lidstone (Personal e-mail) wrote:
> Sep 28 13:08:03 WARNING[20498]: chan_zap.c:3404 zt_handle_event: 
Didn't
> finish
> Caller-ID spill.  Cancelling.

If you are ringing your Zaptel FXS ports with UK-style cadence 
(ring-ring-pause-) then you need to adjust chan_zap.c, changing this line:

#define DEFAULT_CIDRINGS 2

(Default is 1, you need to make it 2).

There's not enough time between ring one and two.

Remains to be seen whether your connected phones recognise the outgoing 
CLI

Steve

Ian D. Wlloughby

2004-Sep-28 05:37 UTC

head link

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

Hi Patrick,
I haven't got a TDM400 (yet)  but I seem to remember from looking at the
config and the code that you have to use usecallerid=yes and set signalling=v23
(check out the sample file as I can't remember if it is called signalling
but the value is v23 for sure).

Regards
Ian




From: Patrick Lidstone (Personal e-mail)
Sent: Tue 28/09/2004 13:21
To: asterisk-users@lists.digium.com
Subject: [Asterisk-Users] UK (British Telecom) Caller ID again


I've followed the recent thread on caller id with UK British Telecom
networks (where the caller id data is delivered before the first ring).
My understanding is that if I use a recent CVS head (e.g.
CVS-HEAD-09/18/04-17:45:52) and a TDM400 with FXO modules, all I need to
do is include the line:

usecallerid=uk 

In my zapata.conf (in the [channels] section)

I've done this, but I get:

Sep 28 13:08:02 NOTICE[20498]: chan_zap.c:5119 ss_thread:  Got event 2
(Ring/An
wered)...
    -- Detected ring pattern: 247,97,0
    -- 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
    -- Zap/1-1 is ringing
    -- Zap/2-1 is ringing
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

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

------------------------------------------------------------
Mail was checked for spam by the Freeware Edition of No Spam Today!
The Freeware Edition is free for personal and non-commercial use.
You can remove this notice by purchasing a full license! To order
or to find out more please visit: http://www.no-spam-today.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20040928/7894f08c/attachment.htm

Karl Dyson

2004-Sep-28 05:42 UTC

head link

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

I currently have this in my zapata.conf, albeit for a X101P you may not
need the last line:

usecallerid = yes               ; we want Caller*ID support
cidsignalling = v23             ; UK (BT) Caller*ID uses the V.23 std
cidstart = history              ; use the Zaptel history (X100P)

Cheers,

Karl
> -----Original Message-----
> From: asterisk-users-bounces@lists.digium.com 
> [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of 
> Ian D. Wlloughby
> Sent: 28 September 2004 13:37
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> Subject: RE: [Asterisk-Users] UK (British Telecom) Caller ID again
> 
> Hi Patrick,
> I haven't got a TDM400 (yet)  but I seem to remember from 
> looking at the config and the code that you have to use 
> usecallerid=yes and set signalling=v23 (check out the sample 
> file as I can't remember if it is called signalling but the 
> value is v23 for sure).
>  
> Regards
> Ian
>  
> 
> ________________________________
> 
> From: Patrick Lidstone (Personal e-mail)
> Sent: Tue 28/09/2004 13:21
> To: asterisk-users@lists.digium.com
> Subject: [Asterisk-Users] UK (British Telecom) Caller ID again
> 
> 
> I've followed the recent thread on caller id with UK British 
> Telecom networks (where the caller id data is delivered 
> before the first ring).
> My understanding is that if I use a recent CVS head (e.g.
> CVS-HEAD-09/18/04-17:45:52) and a TDM400 with FXO modules, 
> all I need to do is include the line:
> 
> usecallerid=uk 
> 
> In my zapata.conf (in the [channels] section)
> 
> I've done this, but I get:
> 
> Sep 28 13:08:02 NOTICE[20498]: chan_zap.c:5119 ss_thread:  
> Got event 2 (Ring/An wered)...
>     -- Detected ring pattern: 247,97,0
>     -- 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
>     -- Zap/1-1 is ringing
>     -- Zap/2-1 is ringing
> 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
> 
> _______________________________________________
> Asterisk-Users mailing list
> Asterisk-Users@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
> 
> ------------------------------------------------------------
> Mail was checked for spam by the Freeware Edition of No Spam Today!
> The Freeware Edition is free for personal and non-commercial use.
> You can remove this notice by purchasing a full license! To 
> order or to find out more please visit: http://www.no-spam-today.com
> 
> ______________________________________________________________
> __________
> This e-mail has been scanned for all viruses by Star. The 
> service is powered by MessageLabs. For more information on a 
> proactive anti-virus service working around the clock, around 
> the globe, visit:
> http://www.star.net.uk <http://www.star.net.uk> 
> ______________________________________________________________
> __________
> 
> 
________________________________________________________________________
This e-mail has been scanned for all viruses by Star. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________

Karl Dyson

2004-Sep-28 06:06 UTC

head link

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

Yes, 'tis a patch to peusuade X10(0|1)P cards to do UK CID (distinctive
ringing a.k.a BT Call Sign also works, but I do not know if this is
related to the patches). I (obviously) have the patches, but they're not
mine (!) and so I'm reluctant to distribute them without obtaining
permission. See earlier posts about UK CID patches.
> -----Original Message-----
> From: asterisk-users-bounces@lists.digium.com 
> [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of 
> Ian D. Wlloughby
> Sent: 28 September 2004 14:01
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> Subject: RE: [Asterisk-Users] UK (British Telecom) Caller ID again
> 
> I think you might need cidstart = polarity for the TDM400.
>  
> I don't see anything in the code for cidstart=history is this a patch?
>  
> Regards
> Ian
>  
> 
> ________________________________
> 
> From: Karl Dyson
> Sent: Tue 28/09/2004 13:42
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> Subject: RE: [Asterisk-Users] UK (British Telecom) Caller ID again
> 
> 
> I currently have this in my zapata.conf, albeit for a X101P 
> you may not need the last line:
> 
> usecallerid = yes               ; we want Caller*ID support
> cidsignalling = v23             ; UK (BT) Caller*ID uses the V.23 std
> cidstart = history              ; use the Zaptel history (X100P)
> 
> Cheers,
> 
> Karl
> 
> > -----Original Message-----
> > From: asterisk-users-bounces@lists.digium.com
> > [mailto:asterisk-users-bounces@lists.digium.com] On Behalf 
> Of Ian D. 
> > Wlloughby
> > Sent: 28 September 2004 13:37
> > To: Asterisk Users Mailing List - Non-Commercial Discussion
> > Subject: RE: [Asterisk-Users] UK (British Telecom) Caller ID again
> > 
> > Hi Patrick,
> > I haven't got a TDM400 (yet)  but I seem to remember from 
> looking at 
> > the config and the code that you have to use 
> usecallerid=yes and set 
> > signalling=v23 (check out the sample file as I can't 
> remember if it is 
> > called signalling but the value is v23 for sure).
> >  
> > Regards
> > Ian
> >  
> > 
> > ________________________________
> > 
> > From: Patrick Lidstone (Personal e-mail)
> > Sent: Tue 28/09/2004 13:21
> > To: asterisk-users@lists.digium.com
> > Subject: [Asterisk-Users] UK (British Telecom) Caller ID again
> > 
> > 
> > I've followed the recent thread on caller id with UK 
> British Telecom 
> > networks (where the caller id data is delivered before the first 
> > ring).
> > My understanding is that if I use a recent CVS head (e.g.
> > CVS-HEAD-09/18/04-17:45:52) and a TDM400 with FXO modules, 
> all I need 
> > to do is include the line:
> > 
> > usecallerid=uk
> > 
> > In my zapata.conf (in the [channels] section)
> > 
> > I've done this, but I get:
> > 
> > Sep 28 13:08:02 NOTICE[20498]: chan_zap.c:5119 ss_thread:  
> > Got event 2 (Ring/An wered)...
> >     -- Detected ring pattern: 247,97,0
> >     -- 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
> >     -- Zap/1-1 is ringing
> >     -- Zap/2-1 is ringing
> > 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
> > 
> > _______________________________________________
> > Asterisk-Users mailing list
> > Asterisk-Users@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
> > 
> > ------------------------------------------------------------
> > Mail was checked for spam by the Freeware Edition of No Spam Today!
> > The Freeware Edition is free for personal and non-commercial use.
> > You can remove this notice by purchasing a full license! To 
> order or 
> > to find out more please visit: http://www.no-spam-today.com
> > 
> > ______________________________________________________________
> > __________
> > This e-mail has been scanned for all viruses by Star. The 
> service is 
> > powered by MessageLabs. For more information on a proactive 
> anti-virus 
> > service working around the clock, around the globe, visit:
> > http://www.star.net.uk <http://www.star.net.uk> 
> > ______________________________________________________________
> > __________
> > 
> > 
> 
> ______________________________________________________________
> __________
> This e-mail has been scanned for all viruses by Star. The
> service is powered by MessageLabs. For more information on a proactive
> anti-virus service working around the clock, around the globe, visit:
> http://www.star.net.uk
> ______________________________________________________________
> __________
> _______________________________________________
> Asterisk-Users mailing list
> Asterisk-Users@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
> 
> ------------------------------------------------------------
> Mail was checked for spam by the Freeware Edition of No Spam Today!
> The Freeware Edition is free for personal and non-commercial use.
> You can remove this notice by purchasing a full license! To order
> or to find out more please visit: http://www.no-spam-today.com
> 
> ______________________________________________________________
> __________
> This e-mail has been scanned for all viruses by Star. The
> service is powered by MessageLabs. For more information on a proactive
> anti-virus service working around the clock, around the globe, visit:
> http://www.star.net.uk <http://www.star.net.uk> 
> ______________________________________________________________
> __________
> 
> 
________________________________________________________________________
This e-mail has been scanned for all viruses by Star. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________

Edward Eastman

2004-Sep-28 06:21 UTC

head link

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

If you have a TDM400 + FXO Modules with recent CVS head ALL you should have
to do is:

usecallerid=yes
cidsignalling=v23
cidstart=polarity

in your zapata.conf

I have this working absolutely fine at the moment.

The X100P makes life a bit more difficult, because it doesn't detect
polarity reversal (which signals the start of CID data in the UK iirc) and I
think you'll need an extra patch to make this work (although it's a
little
unclear) - one of the patches on
http://bugs.digium.com/bug_view_page.php?bug_id=0000009 may work, although
I've not tried it at all.

HTH

Ed

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

I've followed the recent thread on caller id with UK British Telecom
networks (where the caller id data is delivered before the first ring).
My understanding is that if I use a recent CVS head (e.g.
CVS-HEAD-09/18/04-17:45:52) and a TDM400 with FXO modules, all I need to
do is include the line:

usecallerid=uk 

In my zapata.conf (in the [channels] section)

I've done this, but I get:

Sep 28 13:08:02 NOTICE[20498]: chan_zap.c:5119 ss_thread:  Got event 2
(Ring/An
wered)...
    -- Detected ring pattern: 247,97,0
    -- 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
    -- Zap/1-1 is ringing
    -- Zap/2-1 is ringing
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

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

Karl Dyson

2004-Sep-28 06:26 UTC

head link

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

I got them from Kevin Walsh (who is on this list, and I'm sure will
reply, possibly/probably with the patches). They appear to work well for
me so far, although I had to comment out the MMX bits. Apart from that,
all appears to be fine (UK CID and DRING). If you want my DRING settings
for BT Call Sign, just shout.

Cheers,

Karl
> -----Original Message-----
> From: asterisk-users-bounces@lists.digium.com 
> [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of 
> Ian D. Wlloughby
> Sent: 28 September 2004 14:20
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> Subject: RE: [Asterisk-Users] UK (British Telecom) Caller ID again
> 
> Hi Karl,
> Yep your patch has added the cidstart=history option, the 
> rest is bog standard code which will work with Patrick's TDM400. 
> This patch must be fairly new as it is post the polarity 
> reversal stuff which lets the TDM400 callerid work and also 
> cause so many CVS clashes with my orignal patch X100 
> installation. Any pointers as to where to get this new patch?
>  
> R's
> Ian
> 
> ________________________________
> 
> From: Karl Dyson
> Sent: Tue 28/09/2004 14:06
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> Subject: RE: [Asterisk-Users] UK (British Telecom) Caller ID again
> 
> 
> Yes, 'tis a patch to peusuade X10(0|1)P cards to do UK CID 
> (distinctive ringing a.k.a BT Call Sign also works, but I do 
> not know if this is related to the patches). I (obviously) 
> have the patches, but they're not mine (!) and so I'm 
> reluctant to distribute them without obtaining permission. 
> See earlier posts about UK CID patches.
> 
> ______________________________________________________________
> __________
> This e-mail has been scanned for all viruses by Star. The 
> service is powered by MessageLabs. For more information on a 
> proactive anti-virus service working around the clock, around 
> the globe, visit:
> http://www.star.net.uk <http://www.star.net.uk> 
> ______________________________________________________________
> __________
> 
> 
________________________________________________________________________
This e-mail has been scanned for all viruses by Star. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________

Patrick Lidstone (Personal e-mail)

2004-Sep-28 08:33 UTC

head link

[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@intern
context=intern
signalling=fxo_ks
callerid="3001"
channel=>1
;
;
mailbox=3002@default
context=intern
signalling=fxo_ks
callerid="3002"
mailbox=3002@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

Maybe Matching Threads

Search for more maybe matching threads

asterisk users - Sep 2004 - UK (British Telecom) Caller ID again

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

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

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

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

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

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

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

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

Maybe Matching Threads