Re: [Asterisk-Users] Caller ID with BT CD50
On Wednesday 26 May 2004 19:42, Jon Lawrence wrote: It looks like my missing digit problems are down to the dect phone I have connected to my handytone ata-286. When i have my Binatone dect connected, I only get the first 8 digits, if I connect my panasonic dect then I see all the digits - looks like I need a different dect phone :( Any ways, It looks like the patch works perfectly to me. It also works fine on my Telewest (Eurobell). I'm even more confused now. If I have the number in the phones phone book then it will show the relevant name, otherwise it only shows the first 8 digits. Has anyone ever heard of anything like this ? TIA Jon ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] Caller ID with BT CD50
Tony Hoyle [EMAIL PROTECTED] wrote: I forget how I determined the cadence values, as it was some time ago. The values work for me. Running asterisk in verbose mode prints the values out when it gets the ring... It's actually calculated as a repeated subtraction from a constant value (400), so you're saying your dring1 is a single ring of length 33, and your dring2 is a single ring of length 153. Yes - the verbose mode must be where I got the values. The single ring definition sounds weird though; Perhaps it's detecting the first ring of a ring ring... ring ring... It works anyway, so I'm happy. -- _/ _/ _/_/_/_/ _/_/ _/_/_/ _/_/ _/_/_/ _/_/ _/_/_/_/_/ _/ K e v i n W a l s h _/ _/_/ _/ _/ _/_/ _/_/[EMAIL PROTECTED] _/ _/ _/_/_/_/ _/_/_/_/ _/_/ ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Caller ID with BT CD50
I would love to test it, but I need some help with the zapata config settings. In the US you can have up to 4 numbers on a line each with a ring pattern. The ring patterns are: Long ring - 1st number (this is a normal ring - like if you didn't have distinctive ringing at all) Double ring - 2nd number Short short long - 3rd number Short long short - 4th number I have 3 phone numbers on one line so can test all but the last. How would I configure in zapata.conf? From the example I would think that dring1 = the double ring and dring2 = short short long and if it didn't match either of those it would be the normal long ring? Or is that referring to two different things and dring1 = long, dring2 = double and dring3 = ssl and dring4 = sls (assuming there is a dring3 and dring4)? ;dring1=95,0,0 ;dring1context=internal1 ;dring2=325,95,0 ;dring2context=internal2 ; If no pattern is matched here is where we go. ;context=default ;channel = 1 Then I am a little confused about the values after the = can you tell me what they would be for the above ring patterns? I see others that have tested (in Europe?) using: dring1 = 367,0,0 dring1context = incoming-pstn-personal dring2 = 247,0,0 dring2context = incoming-pstn-business I apologize if this is documented somewhere, but I couldn't find it in any searches in the wiki. Ben On Friday, May 28, 2004, at 06:30 PM, Tony Hoyle wrote: Tony Hoyle wrote: I've changed the patch to fix the buffer overrun, plus a hack to only look for the dring values you specify, thus: btw. It would be great if someone in the US can test these changes to make sure I haven't broken the CID/DR on their side by doing this. Tony -- Te audire no possum. Musa sapientum fixa est in aure. Tony Hoyle [EMAIL PROTECTED] Key ID: 104D/4F4B6917 2003-09-13 Fingerprint: 063C AFB4 3026 F724 0AA2 02B8 E547 470E 4F4B 6917 ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Caller ID with BT CD50
First of all thanks for the patch it works great, but i think it breaks the distinctive ringing, I have 2 incoming numbers in one x100p in contexts home1 and home2 but 'default' is always chosen has anyone else seen this? if you need any more info just ask Robb Tony Hoyle wrote: David J Carter wrote: Where would I find cdr-csv? Usually in /var/log/asterisk The line looks funny because of the line breaks. zapata.conf ukcallerid=yes callerid=asreceived signalling=fxs_ks channel = 1 : BT line channel = 2 : Telewest line I also have immediate=yes, but that shouldn't affect anything. Are you sure you've updated the modules correctly (done make/make install, done an rmmod on the old zaptel module and a modprobe on the new one)? There isn't much to go wrong beyond that... if you run asterisk with debugging you'll get a log if it finds a callerID but it's basically the same that goes into the cdr-csv file. Tony ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] Caller ID with BT CD50
Cheers Tony. Your a star. Works a treat. Dave -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Tony Hoyle Sent: 28 May 2004 00:48 To: [EMAIL PROTECTED] Subject: Re: [Asterisk-Users] Caller ID with BT CD50 David J Carter wrote: Where would I find cdr-csv? Usually in /var/log/asterisk The line looks funny because of the line breaks. zapata.conf ukcallerid=yes callerid=asreceived signalling=fxs_ks channel = 1 : BT line channel = 2 : Telewest line I also have immediate=yes, but that shouldn't affect anything. Are you sure you've updated the modules correctly (done make/make install, done an rmmod on the old zaptel module and a modprobe on the new one)? There isn't much to go wrong beyond that... if you run asterisk with debugging you'll get a log if it finds a callerID but it's basically the same that goes into the cdr-csv file. Tony -- Te audire no possum. Musa sapientum fixa est in aure. Tony Hoyle [EMAIL PROTECTED] Key ID: 104D/4F4B6917 2003-09-13 Fingerprint: 063C AFB4 3026 F724 0AA2 02B8 E547 470E 4F4B 6917 ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] Caller ID with BT CD50
Robert Boardman [EMAIL PROTECTED] wrote: First of all thanks for the patch it works great, but i think it breaks the distinctive ringing, I have 2 incoming numbers in one x100p in contexts home1 and home2 but 'default' is always chosen has anyone else seen this? Yes - it does break the distinctive ring detection, but that's easily sorted out. The correct way would be to move the if (p-use_callerid == 2) code within the existing if (p-use_callerid) block, with a couple more if conditionals here and there. The quick way, however, is to apply the attached chan_zap.c hack over the top of Tony Hoyle's great work. In the standard chan_zap.c, you can't have distinctive ring detection unless you also need Caller*ID detection. My hack makes two changes: 1. Changes an else if into an if to get the world = USA Caller*ID code to run. This will waste a little time, but no more than we were wasting anyway, before Tony's patch was applied. 2. Comment out a line of code to ensure that we always answer after the first ring. We need the first ring to give the the distinctive ring code something to work with, of course. It works for me. Hopefully it'll work for you too. -- _/ _/ _/_/_/_/ _/_/ _/_/_/ _/_/ _/_/_/ _/_/ _/_/_/_/_/ _/ K e v i n W a l s h _/ _/_/ _/ _/ _/_/ _/_/[EMAIL PROTECTED] _/ _/ _/_/_/_/ _/_/_/_/ _/_/ chan_zap.c.diff Description: Binary data
Re: [Asterisk-Users] Caller ID with BT CD50
Kevin, Could you add this to http://bugs.digium.com/bug_view_page.php?bug_id=0001719 Chris - Original Message - From: Kevin Walsh [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, May 28, 2004 9:12 AM Subject: RE: [Asterisk-Users] Caller ID with BT CD50 Robert Boardman [EMAIL PROTECTED] wrote: First of all thanks for the patch it works great, but i think it breaks the distinctive ringing, I have 2 incoming numbers in one x100p in contexts home1 and home2 but 'default' is always chosen has anyone else seen this? Yes - it does break the distinctive ring detection, but that's easily sorted out. The correct way would be to move the if (p-use_callerid == 2) code within the existing if (p-use_callerid) block, with a couple more if conditionals here and there. The quick way, however, is to apply the attached chan_zap.c hack over the top of Tony Hoyle's great work. In the standard chan_zap.c, you can't have distinctive ring detection unless you also need Caller*ID detection. My hack makes two changes: 1. Changes an else if into an if to get the world = USA Caller*ID code to run. This will waste a little time, but no more than we were wasting anyway, before Tony's patch was applied. 2. Comment out a line of code to ensure that we always answer after the first ring. We need the first ring to give the the distinctive ring code something to work with, of course. It works for me. Hopefully it'll work for you too. -- _/ _/ _/_/_/_/ _/_/ _/_/_/ _/_/ _/_/_/ _/_/ _/_/_/_/_/ _/ K e v i n W a l s h _/ _/_/ _/ _/ _/_/ _/_/[EMAIL PROTECTED] _/ _/ _/_/_/_/ _/_/_/_/ _/_/ ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] Caller ID with BT CD50
Just tried to apply the patch: Just checked out asterisk stable and zaptel, patched using Tony's patches (which worked, and compiled previously) Then got this when applying your patch. bash # cat ../chan_zap.c.diff | patch -p0 patching file channels/chan_zap.c Hunk #1 succeeded at 4642 (offset -148 lines). Hunk #2 FAILED at 4681. 1 out of 2 hunks FAILED -- saving rejects to file channels/chan_zap.c.rej bash # Cheers, Karl -Original Message- From: [EMAIL PROTECTED] [mailto:asterisk-users- [EMAIL PROTECTED] On Behalf Of Kevin Walsh Sent: 28 May 2004 09:12 To: [EMAIL PROTECTED] Subject: RE: [Asterisk-Users] Caller ID with BT CD50 Robert Boardman [EMAIL PROTECTED] wrote: First of all thanks for the patch it works great, but i think it breaks the distinctive ringing, I have 2 incoming numbers in one x100p in contexts home1 and home2 but 'default' is always chosen has anyone else seen this? Yes - it does break the distinctive ring detection, but that's easily sorted out. The correct way would be to move the if (p-use_callerid == 2) code within the existing if (p-use_callerid) block, with a couple more if conditionals here and there. The quick way, however, is to apply the attached chan_zap.c hack over the top of Tony Hoyle's great work. In the standard chan_zap.c, you can't have distinctive ring detection unless you also need Caller*ID detection. My hack makes two changes: 1. Changes an else if into an if to get the world = USA Caller*ID code to run. This will waste a little time, but no more than we were wasting anyway, before Tony's patch was applied. 2. Comment out a line of code to ensure that we always answer after the first ring. We need the first ring to give the the distinctive ring code something to work with, of course. It works for me. Hopefully it'll work for you too. -- _/ _/ _/_/_/_/ _/_/ _/_/_/ _/_/ _/_/_/ _/_/ _/_/_/_/_/ _/ K e v i n W a l s h _/ _/_/ _/ _/ _/_/ _/_/[EMAIL PROTECTED] _/ _/ _/_/_/_/ _/_/_/_/ _/_/ This e-mail has been scanned for all viruses by Star Internet. 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 This e-mail has been scanned for all viruses by Star Internet. 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 [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] Caller ID with BT CD50
Karl Dyson [EMAIL PROTECTED] wrote: Just checked out asterisk stable and zaptel, patched using Tony's patches (which worked, and compiled previously) Then got this when applying your patch. bash # cat ../chan_zap.c.diff | patch -p0 patching file channels/chan_zap.c Hunk #1 succeeded at 4642 (offset -148 lines). Hunk #2 FAILED at 4681. 1 out of 2 hunks FAILED -- saving rejects to file channels/chan_zap.c.rej bash # Could you try applying the changes by hand. There are only two lines to change and it looks as if the first one went through. I'll check my patch to see if I messed up the original or something silly. -- _/ _/ _/_/_/_/ _/_/ _/_/_/ _/_/ _/_/_/ _/_/ _/_/_/_/_/ _/ K e v i n W a l s h _/ _/_/ _/ _/ _/_/ _/_/[EMAIL PROTECTED] _/ _/ _/_/_/_/ _/_/_/_/ _/_/ ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Caller ID with BT CD50
Karl Dyson wrote: Just tried to apply the patch: Just checked out asterisk stable and zaptel, patched using Tony's patches (which worked, and compiled previously) Then got this when applying your patch. bash # cat ../chan_zap.c.diff | patch -p0 patching file channels/chan_zap.c Hunk #1 succeeded at 4642 (offset -148 lines). Hunk #2 FAILED at 4681. 1 out of 2 hunks FAILED -- saving rejects to file channels/chan_zap.c.rej bash # The patch is against the HEAD branch not the stable one. Tony -- All your code belongs to Santa Tony Hoyle [EMAIL PROTECTED] Key ID: 104D/4F4B6917 2003-09-13 Fingerprint: 063C AFB4 3026 F724 0AA2 02B8 E547 470E 4F4B 6917 Phone(FWD): (0845 004 5566) 413300 ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] Caller ID with BT CD50
Oddly, it looks like the changes were made(!?) It might be, having read Tony's reply, that it's because I applied the uk cli patches from Tony and yourself to the stable rather than head branches? I'll try compiling and let you know. Cheers for now, Karl -Original Message- From: [EMAIL PROTECTED] [mailto:asterisk-users- [EMAIL PROTECTED] On Behalf Of Kevin Walsh Sent: 28 May 2004 12:07 To: [EMAIL PROTECTED] Subject: RE: [Asterisk-Users] Caller ID with BT CD50 Karl Dyson [EMAIL PROTECTED] wrote: Just checked out asterisk stable and zaptel, patched using Tony's patches (which worked, and compiled previously) Then got this when applying your patch. bash # cat ../chan_zap.c.diff | patch -p0 patching file channels/chan_zap.c Hunk #1 succeeded at 4642 (offset -148 lines). Hunk #2 FAILED at 4681. 1 out of 2 hunks FAILED -- saving rejects to file channels/chan_zap.c.rej bash # Could you try applying the changes by hand. There are only two lines to change and it looks as if the first one went through. I'll check my patch to see if I messed up the original or something silly. -- _/ _/ _/_/_/_/ _/_/ _/_/_/ _/_/ _/_/_/ _/_/ _/_/_/_/_/ _/ K e v i n W a l s h _/ _/_/ _/ _/ _/_/ _/_/[EMAIL PROTECTED] _/ _/ _/_/_/_/ _/_/_/_/ _/_/ ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users This e-mail has been scanned for all viruses by Star Internet. 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 This e-mail has been scanned for all viruses by Star Internet. 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 [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] Caller ID with BT CD50
Well compiles and runs OK, but it doesn't identify the dring. I only started playing with it this morning (only realised it *did* dring when I saw your it's broken dring post) This is what I have in zapata.conf dring1=95,0,0 dring1context=inbound-pstn-1 dring2=325,95,0 dring2context=inbound-pstn-2 is this correct for the UK? (I suspect not, and yes, I have dring on my bt line). Cheers, Karl -Original Message- From: [EMAIL PROTECTED] [mailto:asterisk-users- [EMAIL PROTECTED] On Behalf Of Karl Dyson Sent: 28 May 2004 12:36 To: [EMAIL PROTECTED] Subject: RE: [Asterisk-Users] Caller ID with BT CD50 Oddly, it looks like the changes were made(!?) It might be, having read Tony's reply, that it's because I applied the uk cli patches from Tony and yourself to the stable rather than head branches? I'll try compiling and let you know. Cheers for now, Karl -Original Message- From: [EMAIL PROTECTED] [mailto:asterisk-users- [EMAIL PROTECTED] On Behalf Of Kevin Walsh Sent: 28 May 2004 12:07 To: [EMAIL PROTECTED] Subject: RE: [Asterisk-Users] Caller ID with BT CD50 Karl Dyson [EMAIL PROTECTED] wrote: Just checked out asterisk stable and zaptel, patched using Tony's patches (which worked, and compiled previously) Then got this when applying your patch. bash # cat ../chan_zap.c.diff | patch -p0 patching file channels/chan_zap.c Hunk #1 succeeded at 4642 (offset -148 lines). Hunk #2 FAILED at 4681. 1 out of 2 hunks FAILED -- saving rejects to file channels/chan_zap.c.rej bash # Could you try applying the changes by hand. There are only two lines to change and it looks as if the first one went through. I'll check my patch to see if I messed up the original or something silly. -- _/ _/ _/_/_/_/ _/_/ _/_/_/ _/_/ _/_/_/ _/_/ _/_/_/_/_/ _/ K e v i n W a l s h _/ _/_/ _/ _/ _/_/ _/_/[EMAIL PROTECTED] _/ _/ _/_/_/_/ _/_/_/_/ _/_/ ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users This e-mail has been scanned for all viruses by Star Internet. 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 This e-mail has been scanned for all viruses by Star Internet. 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 [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users This e-mail has been scanned for all viruses by Star Internet. 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 This e-mail has been scanned for all viruses by Star Internet. 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 [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] Caller ID with BT CD50
Karl Dyson [EMAIL PROTECTED] wrote: Well compiles and runs OK, but it doesn't identify the dring. I only started playing with it this morning (only realised it *did* dring when I saw your it's broken dring post) This is what I have in zapata.conf dring1=95,0,0 dring1context=inbound-pstn-1 dring2=325,95,0 dring2context=inbound-pstn-2 is this correct for the UK? (I suspect not, and yes, I have dring on my bt line). I have this on my home setup: dring1 = 367,0,0 dring1context = incoming-pstn-personal dring2 = 247,0,0 dring2context = incoming-pstn-business -- _/ _/ _/_/_/_/ _/_/ _/_/_/ _/_/ _/_/_/ _/_/ _/_/_/_/_/ _/ K e v i n W a l s h _/ _/_/ _/ _/ _/_/ _/_/[EMAIL PROTECTED] _/ _/ _/_/_/_/ _/_/_/_/ _/_/ ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Caller ID with BT CD50
Kevin Walsh wrote:
Yes - it does break the distinctive ring detection, but that's easily
sorted out.
Actually it's the first time I've ever heard of distinctive ring being
available in the UK... :)
The correct way would be to move the if (p-use_callerid == 2)
code within the existing if (p-use_callerid) block, with a couple
more if conditionals here and there. The quick way, however, is
to apply the attached chan_zap.c hack over the top of Tony Hoyle's
great work.
It needs an extra conditional - no need to add the extra delay before
the phone starts ringing if there's no need to (I prefer my phone to
start ringing immediately).
Try this patch. It also enables distinctive ring detection even if
usecallerid=no. It's not well tested yet (well, at all actually since I
don't have access to distinctive ring...)
Tony
--
All your code belongs to Santa
Tony Hoyle [EMAIL PROTECTED] Key ID: 104D/4F4B6917 2003-09-13
Fingerprint: 063C AFB4 3026 F724 0AA2 02B8 E547 470E 4F4B 6917
Phone(FWD): (0845 004 5566) 413300
? channels/chan_zap.cx
Index: callerid.c
===
RCS file: /usr/cvsroot/asterisk/callerid.c,v
retrieving revision 1.16
diff -u -r1.16 callerid.c
--- callerid.c 4 May 2004 06:42:06 - 1.16
+++ callerid.c 25 May 2004 20:04:27 -
@@ -134,6 +134,12 @@
return cid;
}
+void callerid_set_v23(struct callerid_state *cid)
+{
+ cid-fskd.f_mark_idx = 4; /* 1300 Hz */
+ cid-fskd.f_space_idx = 5; /* 2100 Hz */
+}
+
void callerid_get(struct callerid_state *cid, char **name, char **number, int *flags)
{
*flags = cid-flags;
@@ -255,7 +260,7 @@
break;
case 2: /* Number */
case 3: /* Number (for Zebble) */
- case 4: /* Number */
+ case 4: /* Number (UK: Reason for
number withheld) */
res = cid-rawdata[x];
if (res 32) {
ast_log(LOG_NOTICE,
Truncating long caller ID number from %d bytes to 32\n, cid-rawdata[x]);
@@ -266,7 +271,7 @@
cid-number[res] = '\0';
break;
case 7: /* Name */
- case 8: /* Name */
+ case 8: /* Name (UK: Reason for
absence of name) */
res = cid-rawdata[x];
if (res 32) {
ast_log(LOG_NOTICE,
Truncating long caller ID name from %d bytes to 32\n, cid-rawdata[x]);
@@ -275,6 +280,11 @@
memcpy(cid-name, cid-rawdata
+ x + 1, res);
cid-name[res] = '\0';
break;
+ case 17: /* Call type (UK) */
+ /* Currently defined: 1 =
Voice call, 2 = Ringback when free, 129 = Message waiting */
+ break;
+ case 19: /* Network message system
status (UK) */
+ break;
case 22: /* Something French */
break;
default:
Index: coef_in.h
===
RCS file: /usr/cvsroot/asterisk/coef_in.h,v
retrieving revision 1.1
diff -u -r1.1 coef_in.h
--- coef_in.h 20 Mar 2001 20:11:26 - 1.1
+++ coef_in.h 25 May 2004 16:55:41 -
@@ -6,4 +6,8 @@
}, {
9.8539686961e-02,-5.6297236492e-02,4.2915323820e-01,-1.2609358633e+00,2.2399213250e+00,-2.9928879142e+00,2.5990173742e+00,0.00e+00,
}, }, { {
1.8229206610e-04,-7.8997325866e-01,-7.7191410839e-01,-2.8075643964e+00,-1.6948618347e+00,-3.0367273700e+00,-9.0333559408e-01,0.00e+00,
}, {
9.8531161839e-02,-5.6297236492e-02,-1.1421579050e-01,-4.8122536483e-01,-4.0121072432e-01,-7.4834487567e-01,-6.9170822332e-01,0.00e+00,
- }, },
+ }, }, { { 1.8229206611e-04,-7.8997325866e-01, 2.5782298908e+00,
-5.3629717478e+00, 6.5890882172e+00, -5.8012914776e+00, 3.0171839130e+00,
-0.00e+00,
+ }, { 9.8534230718e-02,-5.6297236492e-02, 3.8148618075e-01, -1.0848760410e+00,
Re: [Asterisk-Users] Caller ID with BT CD50
Karl Dyson wrote: Well compiles and runs OK, but it doesn't identify the dring. I only started playing with it this morning (only realised it *did* dring when I saw your it's broken dring post) This is what I have in zapata.conf dring1=95,0,0 dring1context=inbound-pstn-1 dring2=325,95,0 dring2context=inbound-pstn-2 is this correct for the UK? (I suspect not, and yes, I have dring on my bt line). I expect you'll need usedistinctiveringdetection=yes as well. To my untrained eye it looks like the patch aborts after the first ring... I've done it in a slightly different way which may (or may not) work better. Tony -- All your code belongs to Santa Tony Hoyle [EMAIL PROTECTED] Key ID: 104D/4F4B6917 2003-09-13 Fingerprint: 063C AFB4 3026 F724 0AA2 02B8 E547 470E 4F4B 6917 Phone(FWD): (0845 004 5566) 413300 ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] Caller ID with BT CD50
Tony Hoyle [EMAIL PROTECTED] wrote: Kevin Walsh wrote: Yes - it does break the distinctive ring detection, but that's easily sorted out. Actually it's the first time I've ever heard of distinctive ring being available in the UK... :) It costs the same as Caller*ID, so I just got it to separate business and personal calls received at home. I have Asterisk now, so I can be a little bit cleverer and set the times when I want to receive business calls at home etc. :-) The correct way would be to move the if (p-use_callerid == 2) code within the existing if (p-use_callerid) block, with a couple more if conditionals here and there. The quick way, however, is to apply the attached chan_zap.c hack over the top of Tony Hoyle's great work. It needs an extra conditional - no need to add the extra delay before the phone starts ringing if there's no need to (I prefer my phone to start ringing immediately). Yes, but it'd need to ring at least once if the distinctive ring is to be detected. As you said - a conditional should do the trick. Try this patch. It also enables distinctive ring detection even if usecallerid=no. It's not well tested yet (well, at all actually since I don't have access to distinctive ring...) I applied your new patch but it resulted in the caller hearing a ring tone but no phones actually ringing. I don't have time to look into it right now, but I'll take a look later and see what's going on. I put my chan_zap.c back in and the re-tests were ok. I has assumed that the only change between your previous patch file and your latest was in chan_zap.c, so I extracted the patch and applied it to that single file only. If that's not the case then I'll have to apply the whole thing. I'll probably have more time later in the day. -- _/ _/ _/_/_/_/ _/_/ _/_/_/ _/_/ _/_/_/ _/_/ _/_/_/_/_/ _/ K e v i n W a l s h _/ _/_/ _/ _/ _/_/ _/_/[EMAIL PROTECTED] _/ _/ _/_/_/_/ _/_/_/_/ _/_/ ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Caller ID with BT CD50
Kevin Walsh wrote: I applied your new patch but it resulted in the caller hearing a ring tone but no phones actually ringing. I don't have time to look into it right now, but I'll take a look later and see what's going on. I put my chan_zap.c back in and the re-tests were ok. I've changed it around slightly as (I think) the last one will result in the phone getting the ringtone noise when they pick up.. it was bypassing the actual reading of the data, whereas it's better to read and ignore it. I put that one on the web page. Tony -- All your code belongs to Santa Tony Hoyle [EMAIL PROTECTED] Key ID: 104D/4F4B6917 2003-09-13 Fingerprint: 063C AFB4 3026 F724 0AA2 02B8 E547 470E 4F4B 6917 Phone(FWD): (0845 004 5566) 413300 ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Caller ID with BT CD50
On Fri, 28 May 2004, Tony Hoyle wrote: Actually it's the first time I've ever heard of distinctive ring being available in the UK... :) BT launched Call Sign sometime in 1996. ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] Caller ID with BT CD50
On Fri, 2004-05-28 at 10:27, Kevin Walsh wrote: Chris Stenton [EMAIL PROTECTED] wrote: Could you add this to http://bugs.digium.com/bug_view_page.php?bug_id=0001719 I thought that, if it was confirmed as working for people other than just me, Tony Hoyle might want to add it to his original patch. People could then apply his single master patch, rather than a handful of patches to patches. Yes, but it can start with you adding as-is to the bugtracker confirming that you've sent in a disclaimer. Then it can safely be merged into 1 patch. F ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] Caller ID with BT CD50
Tony Hoyle [EMAIL PROTECTED] wrote: Kevin Walsh wrote: I applied your new patch but it resulted in the caller hearing a ring tone but no phones actually ringing. I don't have time to look into it right now, but I'll take a look later and see what's going on. I put my chan_zap.c back in and the re-tests were ok. I've changed it around slightly as (I think) the last one will result in the phone getting the ringtone noise when they pick up.. it was bypassing the actual reading of the data, whereas it's better to read and ignore it. I put that one on the web page. Ok - now the phones ring but there are three problems: 1. The distinctive ring is not recognised - both types of ring are directed to the same context. 2. Callers to the primary number hear three rings before the phones actually ring. 3. callers to the secondary number hear four rings before the phones actually ring, which is different from #2 and therefore indicates that something's happening. The Caller*ID detection still works, which is always a bonus. Did you make any changes elsewhere, or just to chan_zap.c? I moved my chan_zap.c, updated it from the CVS head and applied your patch. All of the other files are patches as per your previous diffs. After testing, I put my chan_zap.c back, compiled, installed and it all started working again. Although I was able to do a couple of quick tests, I don't have time to fix it up right now. As I have distinctive ring, I may as well hack the chan_zap.c for you and send you the results for review. Once I've done that, you can include the diffs in your master patch if you like. I probably won't have any time tomorrow so I'll take a look into this on Sunday or (bank holiday) Monday. -- _/ _/ _/_/_/_/ _/_/ _/_/_/ _/_/ _/_/_/ _/_/ _/_/_/_/_/ _/ K e v i n W a l s h _/ _/_/ _/ _/ _/_/ _/_/[EMAIL PROTECTED] _/ _/ _/_/_/_/ _/_/_/_/ _/_/ ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Caller ID with BT CD50
Kevin Walsh wrote: Ok - now the phones ring but there are three problems: 1. The distinctive ring is not recognised - both types of ring are directed to the same context. No idea why that could happen - it's not obvious how detection works in the first place though (not sure what it's testing - something called 'ringt' which isn't explained in the comments). 2. Callers to the primary number hear three rings before the phones actually ring. That's the way the code is written (which is why you have 3 values in the dring entry I think). There's an assumption in the code that it has 3 rings to compare with. From the code it looks like in the US the distinctive ring is sent followed by the caller ID - so you'd get some rings, the caller id then the loop would exit and asterisk would begin comparison. In the UK of course this is not the case, and the detection has no termination point - you always get the maximum 3 rings. The hack of forcing it to break after the first ring will work in the UK but will of course break in the US, so isn't really an answer. Maybe possibly removing the restriction to 3 rings is possible, but it's hardcoded to 3 in many places and I'm not sure I'd want to get the CID patch mixed in with that level of change. 3. callers to the secondary number hear four rings before the phones actually ring, which is different from #2 and therefore indicates that something's happening. I suspect that's more due to timing than anything else - the actual ring detection (comparison with the 3 rings sampled previously) doesn't do anything different. Did you make any changes elsewhere, or just to chan_zap.c? I moved my chan_zap.c, updated it from the CVS head and applied your patch. All of the other files are patches as per your previous diffs. After testing, I put my chan_zap.c back, compiled, installed and it all started working again. The only real difference (aside from the ability to drop into the ring detect code) is an if around the callerid_feed call - everything else is unchanged. If you run asterisk with in verbose mode does it log anything useful? Tony -- Te audire no possum. Musa sapientum fixa est in aure. Tony Hoyle [EMAIL PROTECTED] Key ID: 104D/4F4B6917 2003-09-13 Fingerprint: 063C AFB4 3026 F724 0AA2 02B8 E547 470E 4F4B 6917 ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Caller ID with BT CD50
Tony Hoyle wrote:
That's the way the code is written (which is why you have 3 values in
the dring entry I think). There's an assumption in the code that it has
3 rings to compare with.
Actually it's worse than that... there is actually no terminator in the code.
It's looking for a distinct pattern of ring,ring,short ring and it
terminates after short ring. If you never get that theoretically it'll
never terminate (and scrawl already the stack, memory etc. which isn't a good
thing for an app running in the root context!!!).
The standard ring BT pattern I see is 367,247,217,96 (which is actually
120,30,121, but the numbers are cumulative). The 96 causes a break out of the
loop after the 3rd ring. If the 4th ring was 200 it would be a buffer
overrun (this could be caused easily by, for example, two short rings followed
by a long one).
So what I *suspect* is happening is this:
1. The code is working as written, but isn't really suitable for the UK... it
will work though (you'll have to specify all 3 dring values though).
2. The 4th ring on your second number is actually causing a buffer overrun and
corrupting asterisk... you're lucky it doesn't crash :)
I've changed the patch to fix the buffer overrun, plus a hack to only look for
the dring values you specify, thus:
(just after the ++receivedRingT):
if(receivedRingT==3)
break; /* More than 3 rings would overrun our test buffer */
/* If all 3 dring values are zero, then there's nothing left to detect */
for (counter=0; counter 3; counter++) {
if (p-drings.ringnum[counter].ring[receivedRingT])
break;
}
if (counter == 3)
break;
In my case if I specify dring1=367,0,0 it'll stop trying to detect after the
first ring.
Not sure I like all the hardcoded numbers for number of drings etc... that's
another patch though :)
Tony
--
Te audire no possum. Musa sapientum fixa est in aure.
Tony Hoyle [EMAIL PROTECTED] Key ID: 104D/4F4B6917 2003-09-13
Fingerprint: 063C AFB4 3026 F724 0AA2 02B8 E547 470E 4F4B 6917
___
Asterisk-Users mailing list
[EMAIL PROTECTED]
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Caller ID with BT CD50
Tony Hoyle wrote: I've changed the patch to fix the buffer overrun, plus a hack to only look for the dring values you specify, thus: btw. It would be great if someone in the US can test these changes to make sure I haven't broken the CID/DR on their side by doing this. Tony -- Te audire no possum. Musa sapientum fixa est in aure. Tony Hoyle [EMAIL PROTECTED] Key ID: 104D/4F4B6917 2003-09-13 Fingerprint: 063C AFB4 3026 F724 0AA2 02B8 E547 470E 4F4B 6917 ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] Caller ID with BT CD50
Tony, I have downloades and installed the patches, (I think. I used patch -p0 /usr/src/zaptel/[patch], for bothe the zaptel ones, and [asterisk] for the asterisk one). I have addes the ukcallerid=yes to my zapata.conf, and also got callerid=asreceived set. The phones now ring without the screen showing starting simple switch 3-4 times, but alas no callerid on my GS phone. Any thoughts or hints appreciated. Regards Dave -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Tony Hoyle Sent: 26 May 2004 13:09 To: [EMAIL PROTECTED] Subject: Re: [Asterisk-Users] Caller ID with BT CD50 I keep rolling buffer of the last couple of seconds of the incoming audio, so when the ring is detected the chan_zap driver can grab this and feed it to the callerid processing routines. If it's necessary to assign copyright to digium then there's no problem doing that. At the moment there's a rather lame 'ukcallerid=yes' command... it needs something better certainly but there's plenty of time to get that stuff right. The current patches are at http://www.nodomain.org/asterisk/ Ugh. V23 after first ring... It also matters of course if the cable co. has changed the wire data format - you might be able to grab the data but then not be able to make any sense of it.. Tony -- ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Caller ID with BT CD50
David J Carter wrote: I have addes the ukcallerid=yes to my zapata.conf, and also got callerid=asreceived set. No idea what that option does... The phones now ring without the screen showing starting simple switch 3-4 times, but alas no callerid on my GS phone. Check your cdr-csv file to see if asterisk is getting the incoming CID. It could just be the phone not displaying it. Presumably you have signed up with BT to have caller ID sent on your line? Tony -- Te audire no possum. Musa sapientum fixa est in aure. Tony Hoyle [EMAIL PROTECTED] Key ID: 104D/4F4B6917 2003-09-13 Fingerprint: 063C AFB4 3026 F724 0AA2 02B8 E547 470E 4F4B 6917 ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] Caller ID with BT CD50
Where would I find cdr-csv? I have looked at all the asterisk directories. CLI is on all 3 lines I have into the house. I have addes the ukcallerid=yes to my zapata.conf, and also got callerid=asreceived set. The line looks funny because of the line breaks. zapata.conf ukcallerid=yes callerid=asreceived signalling=fxs_ks channel = 1 : BT line channel = 2 : Telewest line Dave -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Tony Hoyle Sent: 27 May 2004 22:31 To: [EMAIL PROTECTED] Subject: Re: [Asterisk-Users] Caller ID with BT CD50 David J Carter wrote: I have addes the ukcallerid=yes to my zapata.conf, and also got callerid=asreceived set. No idea what that option does... The phones now ring without the screen showing starting simple switch 3-4 times, but alas no callerid on my GS phone. Check your cdr-csv file to see if asterisk is getting the incoming CID. It could just be the phone not displaying it. Presumably you have signed up with BT to have caller ID sent on your line? Tony -- Te audire no possum. Musa sapientum fixa est in aure. Tony Hoyle [EMAIL PROTECTED] Key ID: 104D/4F4B6917 2003-09-13 Fingerprint: 063C AFB4 3026 F724 0AA2 02B8 E547 470E 4F4B 6917 ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Caller ID with BT CD50
David J Carter wrote: Where would I find cdr-csv? Usually in /var/log/asterisk The line looks funny because of the line breaks. zapata.conf ukcallerid=yes callerid=asreceived signalling=fxs_ks channel = 1 : BT line channel = 2 : Telewest line I also have immediate=yes, but that shouldn't affect anything. Are you sure you've updated the modules correctly (done make/make install, done an rmmod on the old zaptel module and a modprobe on the new one)? There isn't much to go wrong beyond that... if you run asterisk with debugging you'll get a log if it finds a callerID but it's basically the same that goes into the cdr-csv file. Tony -- Te audire no possum. Musa sapientum fixa est in aure. Tony Hoyle [EMAIL PROTECTED] Key ID: 104D/4F4B6917 2003-09-13 Fingerprint: 063C AFB4 3026 F724 0AA2 02B8 E547 470E 4F4B 6917 ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Caller ID with BT CD50
Tony - This sounds great. Are you monitoring the line constantly for the inbound caller ID or are you somehow detecting the polarity reversal? Look forward to trying out your solution! I think you will have a lot of happy bunnies here in Blighty, as the current lack of caller ID on our BT lines is the thing that makes Asterisk less viable for most home users If it works and is stable, will you disclaim your code so that it will get merged into the main CVS? There should probably be a couple of settings in zapata.conf for the caller id coding scheme to be used for each card calleridtones = (V23, Bell or DTMF) calleridarrives = (afterring, afterrev, etc) since a lot of people here in UK have a line from BT and a cable co line, where the cable co either uses Bellcore after 1st ring, or V23 after 1st ring. So you need to be able to chose the method for each line. What a mess, eh? Rgds Tim Tony Hoyle wrote: Anyway, the caller ID patch is finished and works really well - it was easier than I thought... once you've decoded the V23 data the packet format is the same as the US Bell system. I've got some more testing to do to make sure it doesn't cause asterisk (or the kernel) to explode then I'll stick it on my website for general consumption/laughter/criticism Tony ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Caller ID with BT CD50
Tim Robinson wrote: Tony - This sounds great. Are you monitoring the line constantly for the inbound caller ID or are you somehow detecting the polarity reversal? I keep rolling buffer of the last couple of seconds of the incoming audio, so when the ring is detected the chan_zap driver can grab this and feed it to the callerid processing routines. If it works and is stable, will you disclaim your code so that it will get merged into the main CVS? There should probably be a couple of settings in zapata.conf for the caller id coding scheme to be used for each card If it's necessary to assign copyright to digium then there's no problem doing that. At the moment there's a rather lame 'ukcallerid=yes' command... it needs something better certainly but there's plenty of time to get that stuff right. The current patches are at http://www.nodomain.org/asterisk/ since a lot of people here in UK have a line from BT and a cable co line, where the cable co either uses Bellcore after 1st ring, or V23 after 1st ring. So you need to be able to chose the method for each line. What a mess, eh? Ugh. V23 after first ring... It also matters of course if the cable co. has changed the wire data format - you might be able to grab the data but then not be able to make any sense of it.. Tony -- All your code belongs to Santa Tony Hoyle [EMAIL PROTECTED] Key ID: 104D/4F4B6917 2003-09-13 Fingerprint: 063C AFB4 3026 F724 0AA2 02B8 E547 470E 4F4B 6917 Phone(FWD): (0845 004 5566) 413300 ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] Caller ID with BT CD50
Tony, Lost some of the mails on this topic somewhere. Does this need the BT50 mod or will the X100p now output the Caller ID? Dave -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Tony Hoyle Sent: 26 May 2004 13:09 To: [EMAIL PROTECTED] Subject: Re: [Asterisk-Users] Caller ID with BT CD50 Tim Robinson wrote: Tony - This sounds great. Are you monitoring the line constantly for the inbound caller ID or are you somehow detecting the polarity reversal? I keep rolling buffer of the last couple of seconds of the incoming audio, so when the ring is detected the chan_zap driver can grab this and feed it to the callerid processing routines. If it works and is stable, will you disclaim your code so that it will get merged into the main CVS? There should probably be a couple of settings in zapata.conf for the caller id coding scheme to be used for each card If it's necessary to assign copyright to digium then there's no problem doing that. At the moment there's a rather lame 'ukcallerid=yes' command... it needs something better certainly but there's plenty of time to get that stuff right. The current patches are at http://www.nodomain.org/asterisk/ since a lot of people here in UK have a line from BT and a cable co line, where the cable co either uses Bellcore after 1st ring, or V23 after 1st ring. So you need to be able to chose the method for each line. What a mess, eh? Ugh. V23 after first ring... It also matters of course if the cable co. has changed the wire data format - you might be able to grab the data but then not be able to make any sense of it.. Tony -- All your code belongs to Santa Tony Hoyle [EMAIL PROTECTED] Key ID: 104D/4F4B6917 2003-09-13 Fingerprint: 063C AFB4 3026 F724 0AA2 02B8 E547 470E 4F4B 6917 Phone(FWD): (0845 004 5566) 413300 ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] Caller ID with BT CD50
Presumably this can then be modified for DTMF caller ID by those in NL, Brazil etc? I will give it a go soon. Thanks Tim -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tony Hoyle Sent: 26 May 2004 13:09 To: [EMAIL PROTECTED] Subject: Re: [Asterisk-Users] Caller ID with BT CD50 Tim Robinson wrote: Tony - This sounds great. Are you monitoring the line constantly for the inbound caller ID or are you somehow detecting the polarity reversal? I keep rolling buffer of the last couple of seconds of the incoming audio, so when the ring is detected the chan_zap driver can grab this and feed it to the callerid processing routines. If it works and is stable, will you disclaim your code so that it will get merged into the main CVS? There should probably be a couple of settings in zapata.conf for the caller id coding scheme to be used for each card If it's necessary to assign copyright to digium then there's no problem doing that. At the moment there's a rather lame 'ukcallerid=yes' command... it needs something better certainly but there's plenty of time to get that stuff right. The current patches are at http://www.nodomain.org/asterisk/ since a lot of people here in UK have a line from BT and a cable co line, where the cable co either uses Bellcore after 1st ring, or V23 after 1st ring. So you need to be able to chose the method for each line. What a mess, eh? Ugh. V23 after first ring... It also matters of course if the cable co. has changed the wire data format - you might be able to grab the data but then not be able to make any sense of it.. Tony -- All your code belongs to Santa Tony Hoyle [EMAIL PROTECTED] Key ID: 104D/4F4B6917 2003-09-13 Fingerprint: 063C AFB4 3026 F724 0AA2 02B8 E547 470E 4F4B 6917 Phone(FWD): (0845 004 5566) 413300 ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Caller ID with BT CD50
David J Carter wrote: Tony, Lost some of the mails on this topic somewhere. Does this need the BT50 mod or will the X100p now output the Caller ID? It's to allow the X100P to output the caller ID. My soldering skills just weren't up to the BT50 mod :) Tony -- All your code belongs to Santa Tony Hoyle [EMAIL PROTECTED] Key ID: 104D/4F4B6917 2003-09-13 Fingerprint: 063C AFB4 3026 F724 0AA2 02B8 E547 470E 4F4B 6917 Phone(FWD): (0845 004 5566) 413300 ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Caller ID with BT CD50
Robinson Tim-W10277 wrote: Presumably this can then be modified for DTMF caller ID by those in NL, Brazil etc? I will give it a go soon. I'd expect so. The zaptel mod just lets you grab what happened just before the ring... processing it is a relatively simple addition (no idea how you'd do DTMF though). Tony -- All your code belongs to Santa Tony Hoyle [EMAIL PROTECTED] Key ID: 104D/4F4B6917 2003-09-13 Fingerprint: 063C AFB4 3026 F724 0AA2 02B8 E547 470E 4F4B 6917 Phone(FWD): (0845 004 5566) 413300 ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Caller ID with BT CD50
Tony, The patches work great, picks up the BT callerid everytime. A really big thankyou! Chris - Original Message - From: Tony Hoyle [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, May 26, 2004 2:09 PM Subject: Re: [Asterisk-Users] Caller ID with BT CD50 David J Carter wrote: Tony, Lost some of the mails on this topic somewhere. Does this need the BT50 mod or will the X100p now output the Caller ID? It's to allow the X100P to output the caller ID. My soldering skills just weren't up to the BT50 mod :) Tony -- All your code belongs to Santa Tony Hoyle [EMAIL PROTECTED] Key ID: 104D/4F4B6917 2003-09-13 Fingerprint: 063C AFB4 3026 F724 0AA2 02B8 E547 470E 4F4B 6917 Phone(FWD): (0845 004 5566) 413300 ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] Caller ID with BT CD50
Chris Stenton wrote: Tony, The patches work great, picks up the BT callerid everytime. A really big thankyou! A big THANK YOU from me too!!! ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Caller ID with BT CD50
Tony, Are you going to submit the patches to the cvs head? Chris - Original Message - From: Kevin Walsh [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, May 26, 2004 4:15 PM Subject: RE: [Asterisk-Users] Caller ID with BT CD50 Tony Hoyle [EMAIL PROTECTED] wrote: Lost some of the mails on this topic somewhere. Does this need the BT50 mod or will the X100p now output the Caller ID? It's to allow the X100P to output the caller ID. I can confirm that it works for me. I applied the patches, compiled and installed zaptel, compiled and installed Asterisk and it just worked. Well done. I'll abandon my attempt now. :-) -- _/ _/ _/_/_/_/ _/_/ _/_/_/ _/_/ _/_/_/ _/_/ _/_/_/_/_/ _/ K e v i n W a l s h _/ _/_/ _/ _/ _/_/ _/_/[EMAIL PROTECTED] _/ _/ _/_/_/_/ _/_/_/_/ _/_/ ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] Caller ID with BT CD50
Can confirm it works with Generic X101P *BIG* Thank you :) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Walsh Sent: 26 May 2004 16:15 To: [EMAIL PROTECTED] Subject: RE: [Asterisk-Users] Caller ID with BT CD50 Tony Hoyle [EMAIL PROTECTED] wrote: Lost some of the mails on this topic somewhere. Does this need the BT50 mod or will the X100p now output the Caller ID? It's to allow the X100P to output the caller ID. I can confirm that it works for me. I applied the patches, compiled and installed zaptel, compiled and installed Asterisk and it just worked. Well done. I'll abandon my attempt now. :-) -- _/ _/ _/_/_/_/ _/_/ _/_/_/ _/_/ _/_/_/ _/_/ _/_/_/_/_/ _/ K e v i n W a l s h _/ _/_/ _/ _/ _/_/ _/_/[EMAIL PROTECTED] _/ _/ _/_/_/_/ _/_/_/_/ _/_/ ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users This e-mail has been scanned for all viruses by Star Internet. 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 This e-mail has been scanned for all viruses by Star Internet. 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 [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Caller ID with BT CD50
Chris Stenton wrote: Tony, Are you going to submit the patches to the cvs head? http://bugs.digium.com/bug_view_page.php?bug_id=0001719 Tony -- All your code belongs to Santa Tony Hoyle [EMAIL PROTECTED] Key ID: 104D/4F4B6917 2003-09-13 Fingerprint: 063C AFB4 3026 F724 0AA2 02B8 E547 470E 4F4B 6917 Phone(FWD): (0845 004 5566) 413300 ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] Caller ID with BT CD50
Chris Stenton [EMAIL PROTECTED] wrote: Tony, Are you going to submit the patches to the cvs head? He has published his patches, but probably doesn't have commit access to the Asterisk CVS archive (correct me if I'm wrong). The people who do have CVS commit access can pick up the published patch files and apply them if they want. I would suggest that someone with commit access should examine the patches and make a decision, as the changes appear to work very well. -- _/ _/ _/_/_/_/ _/_/ _/_/_/ _/_/ _/_/_/ _/_/ _/_/_/_/_/ _/ K e v i n W a l s h _/ _/_/ _/ _/ _/_/ _/_/[EMAIL PROTECTED] _/ _/ _/_/_/_/ _/_/_/_/ _/_/ ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Caller ID with BT CD50
On Wednesday 26 May 2004 17:07, Karl Dyson wrote: Can confirm it works with Generic X101P *BIG* Thank you :) I can confirm it works with my generic X100P (at least I think that's what it is :) ). The full callerID is put into my database, so I know it's receiving the complete CID. The phone only seems to get sent the first 8 digit's - I'm sure this is something in my configs, but I've not had chance to look into it yet. Jon ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Caller ID with BT CD50
The full callerID is put into my database, so I know it's receiving the complete CID. The phone only seems to get sent the first 8 digit's - I'm sure this is something in my configs, but I've not had chance to look into it yet. It looks like my missing digit problems are down to the dect phone I have connected to my handytone ata-286. When i have my Binatone dect connected, I only get the first 8 digits, if I connect my panasonic dect then I see all the digits - looks like I need a different dect phone :( Any ways, It looks like the patch works perfectly to me. It also works fine on my Telewest (Eurobell). Jon ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Caller ID with BT CD50
Amaury Jacquot wrote: Tony Hoyle wrote: Guess what... BT actually charge a monthly rental fee (£1.50 or ~$2.40 per month) for providing this information. Gotta love state monopolies hmm? Hope they don't take too long provisioning it... heh, they'll probably mess up some other setting on that line, or mess up your neibor's line in the process... It actually came online at midnight of all things... a batch job I expect (totally automated system... so I'm even more annoyed they charge for it!) Anyway, the caller ID patch is finished and works really well - it was easier than I thought... once you've decoded the V23 data the packet format is the same as the US Bell system. I've got some more testing to do to make sure it doesn't cause asterisk (or the kernel) to explode then I'll stick it on my website for general consumption/laughter/criticism Tony -- Te audire no possum. Musa sapientum fixa est in aure. Tony Hoyle [EMAIL PROTECTED] Key ID: 104D/4F4B6917 2003-09-13 Fingerprint: 063C AFB4 3026 F724 0AA2 02B8 E547 470E 4F4B 6917 ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Caller ID with BT CD50
Tony Hoyle wrote: The CID specs look really simple... I'll definately have a go at implementing something like it. Just need to find a spec sheet for the Intel chipset in the FX100/FX101 (to see if you somehow see the pulse that comes just before the ring - I always wondered why phones tended to blip a second before starting to ring these days.. now I know). Got my FX101 today, and it worked straight away (almost, there was a bug in the driver..). You can sample the line on-hook, so a CID driver looks doable ... Howver I found out that there was no CID info being transmitted before the ring. Guess what... BT actually charge a monthly rental fee (£1.50 or ~$2.40 per month) for providing this information. Gotta love state monopolies hmm? Hope they don't take too long provisioning it... Tony -- Te audire no possum. Musa sapientum fixa est in aure. Tony Hoyle [EMAIL PROTECTED] Key ID: 104D/4F4B6917 2003-09-13 Fingerprint: 063C AFB4 3026 F724 0AA2 02B8 E547 470E 4F4B 6917 ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Caller ID with BT CD50
Tony Hoyle wrote: Guess what... BT actually charge a monthly rental fee (£1.50 or ~$2.40 per month) for providing this information. Gotta love state monopolies hmm? Hope they don't take too long provisioning it... heh, they'll probably mess up some other setting on that line, or mess up your neibor's line in the process... ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] Caller ID with BT CD50
Well, I have a USR015630B, which, according to the FAQ supports (UK) CLI. It supports the at #cli command, but no matter what I try, it will not pick up the caller id. Lucky I already had it and didn't buy it soley for this purpose! My caller display unit (unfortunately a CD60 -- which I've opened to look for CD50 like boards, chips etc) picks up CLI no problem (as you'd expect), as do my DECT phones. of course, only when they're plugged into the line, and not when they're plugged into the ATA186. I will be persuading someone I know to swap the USR for a Hayes modem later today to see if that will do it. otherwise out will come the soldering iron, and eBay will see me bidding on CD50s! Cheers, Karl -Original Message- From: [EMAIL PROTECTED] [mailto:asterisk-users- [EMAIL PROTECTED] On Behalf Of Tony Hoyle Sent: 22 May 2004 23:55 To: [EMAIL PROTECTED] Subject: Re: [Asterisk-Users] Caller ID with BT CD50 Karl Dyson wrote: 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? From the details on http://www.ainslie.org.uk/callerid/cli_faq.htm it sounds like it wouldn't be too hard to implement, however: The only manufacturers that have ever supported BT Caller ID are Pace, Hayes (Europe), and 3Com/US Robotics. It then goes on to state all 3 of those manufactures no longer support it. I wonder if the low cost geographic VOIP numbers support it? Tony -- Te audire no possum. Musa sapientum fixa est in aure. Tony Hoyle [EMAIL PROTECTED] Key ID: 104D/4F4B6917 2003-09-13 Fingerprint: 063C AFB4 3026 F724 0AA2 02B8 E547 470E 4F4B 6917 ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users This e-mail has been scanned for all viruses by Star Internet. 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 This e-mail has been scanned for all viruses by Star Internet. 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 [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Caller ID with BT CD50
Karl Dyson wrote: Well, I have a USR015630B, which, according to the FAQ supports (UK) CLI. It supports the at #cli command, but no matter what I try, it will not pick up the caller id. Lucky I already had it and didn't buy it soley for this purpose! My caller display unit (unfortunately a CD60 -- which I've opened to look for CD50 like boards, chips etc) picks up CLI no problem (as you'd expect), as do my DECT phones. of course, only when they're plugged into the line, and not when they're plugged into the ATA186. I have a USR modem too but it's a brick unfortunately... Pity as it was a nice modem... the right model too so it might have worked. I wonder what it would take to get the zaptel drivers to pick up CID (or even a cheap conexxant modem or something like that) - these soft modems are pretty dumb so I'd expect there to be some scope for frobbing them to do new stuff. Tony ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] Caller ID with BT CD50
I have a USR modem too but it's a brick unfortunately... Pity as it was a nice modem... the right model too so it might have worked. I wonder what it would take to get the zaptel drivers to pick up CID (or even a cheap conexxant modem or something like that) - these soft modems are pretty dumb so I'd expect there to be some scope for frobbing them to do new stuff. Tony As I say, I lent a Hayes modem to mother in law a year ago, but have since upgraded her to a 56k internal, but cunningly left the old kit in her loft (think of it as redundant storage of my old computer crap ;)) so will pick it up later and try it. failing that, I've located a possible Pace candidate Of course, although my wife is happy with the Cisco 7905s that have sprung up around the house, she still likes the cordless DECT units we have, and so they're plugged into an ATA186. Problem is, they no longer display caller id due to the ATA186 not poking it out in BT format I guess. If I were to buy some US cordless handsets would they do the caller id display? Or am I pushing my luck now! (I'm afraid, nice as they look, the Cisco 7920 cordless phones are a bit out of my price range!!) Cheers, Karl This e-mail has been scanned for all viruses by Star Internet. 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 [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] Caller ID with BT CD50
On Sun, 23 May 2004, Karl Dyson wrote: Of course, although my wife is happy with the Cisco 7905s that have sprung up around the house, she still likes the cordless DECT units we have, and so they're plugged into an ATA186. Problem is, they no longer display caller id due to the ATA186 not poking it out in BT format I guess. If I were to buy some US cordless handsets would they do the ATA186 firmware 3.0+ supports more formats. Certainly with 3.0 my BT DECT 3010 (rebadged Siemens) base copes fine. ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Caller ID with BT CD50
Karl Dyson wrote: Of course, although my wife is happy with the Cisco 7905s that have sprung up around the house, she still likes the cordless DECT units we have, and so they're plugged into an ATA186. Problem is, they no longer display caller id due to the ATA186 not poking it out in BT format I guess. If I were to buy some US cordless handsets would they do the caller id display? Or am I pushing my luck now! (I'm afraid, nice as they look, the Cisco 7920 cordless phones are a bit out of my price range!!) If you had CID to start with, I'd expect it to work - eg. you wouldn't get it from the POTS line but if a VOIP call came in and the ATA186 retransmitted that in US format then a US handset would pick it up. The CID specs look really simple... I'll definately have a go at implementing something like it. Just need to find a spec sheet for the Intel chipset in the FX100/FX101 (to see if you somehow see the pulse that comes just before the ring - I always wondered why phones tended to blip a second before starting to ring these days.. now I know). Tony -- Te audire no possum. Musa sapientum fixa est in aure. Tony Hoyle [EMAIL PROTECTED] Key ID: 104D/4F4B6917 2003-09-13 Fingerprint: 063C AFB4 3026 F724 0AA2 02B8 E547 470E 4F4B 6917 ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] Caller ID with BT CD50
ATA186 firmware 3.0+ supports more formats. Certainly with 3.0 my BT DECT 3010 (rebadged Siemens) base copes fine. Oooh Now which setting would I need to check?? I have a Philips Onis DECT system, which does CLI quite happily on the BT line, and I just checked the ATA and its running : ata000e841adb36 Version: v3.0.0 atasip (Build 031210A) MAC: 0.14.132.26.219.54 SerialNumber: INM07491B0E ProductId: ATA186I2 Features: 0x HardwareVersion: 0x0006 0x So. I guess I must have a setting incorrect?? Thanks in advance, Karl This e-mail has been scanned for all viruses by Star Internet. 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 [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] Caller ID with BT CD50
On Sun, 23 May 2004, gARetH baBB wrote: On Sun, 23 May 2004, Karl Dyson wrote: Of course, although my wife is happy with the Cisco 7905s that have sprung up around the house, she still likes the cordless DECT units we have, and so they're plugged into an ATA186. Problem is, they no longer display caller id due to the ATA186 not poking it out in BT format I guess. If I were to buy some US cordless handsets would they do the ATA186 firmware 3.0+ supports more formats. Certainly with 3.0 my BT DECT 3010 (rebadged Siemens) base copes fine. I also found my Philips DECT phone in the UK had a few CID modes of which one worked with the ATA. Only downside was CID only displayed after the first ring-ring. Steve ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] Caller ID with BT CD50
If you had CID to start with, I'd expect it to work - eg. you wouldn't get it from the POTS line but if a VOIP call came in and the ATA186 retransmitted that in US format then a US handset would pick it up. But once I can get the cid working, I'm hoping I can persuade the DECT units to pick it up obviously the 7905s display CID happily. but currently only from each other, or incoming IAX calls. I always wondered why phones tended to blip a second before starting to ring these days.. now I know). Me too. suddenly dawned on me recently that old phones would blip due to the CLI coming through moments before the ring This e-mail has been scanned for all viruses by Star Internet. 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 [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] Caller ID with BT CD50
On Sun, 23 May 2004, Karl Dyson wrote: Oooh Now which setting would I need to check?? I have a Philips Onis DECT system, which does CLI quite happily on the BT line, and I just checked the ATA and its running : http://www.cisco.com/en/US/products/hw/gatecont/ps514/products_administration_guide_chapter09186a00801e0eb0.html#wp1113416 ETSI method (type 2). I know my CD50 still doesn't like this method, but then as the first generation device it can be *very* fussy at the best of times - indeed, I think very short line lengths were a problem with this device, they have problems with ISDN where the local NTE actually generates CDS. But as said the BT DECT 3010 is fine, and so is my CD20 etc. ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] Caller ID with BT CD50
http://www.cisco.com/en/US/products/hw/gatecont/ps514/products_administr at ion_guide_chapter09186a00801e0eb0.html#wp1113416 ETSI method (type 2). I know my CD50 still doesn't like this method, but then as the first generation device it can be *very* fussy at the best of times - indeed, I think very short line lengths were a problem with this device, they have problems with ISDN where the local NTE actually generates CDS. But as said the BT DECT 3010 is fine, and so is my CD20 etc. Thanks for that I had only really thought of it while typing one of my earlier replies about inbound CLI, and has automatically assumed that the ata186 would not do CLI in a BT/UK way! It looks like the Philips units don't like it anyway (they are ~4 yrs old, mind). I've tried 19e62 and 19e66 so far (the main bits should be fine as defaults I think, and so I just tried getting it to send it before ringing, and after the 1st ring). I'll try the BT CD 60 unit I have in a while to see if that can see the CLI coming from the ATA. Cheers, Karl This e-mail has been scanned for all viruses by Star Internet. 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 [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Caller ID with BT CD50
Karl Dyson wrote: 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? From the details on http://www.ainslie.org.uk/callerid/cli_faq.htm it sounds like it wouldn't be too hard to implement, however: The only manufacturers that have ever supported BT Caller ID are Pace, Hayes (Europe), and 3Com/US Robotics. It then goes on to state all 3 of those manufactures no longer support it. I wonder if the low cost geographic VOIP numbers support it? Tony -- Te audire no possum. Musa sapientum fixa est in aure. Tony Hoyle [EMAIL PROTECTED] Key ID: 104D/4F4B6917 2003-09-13 Fingerprint: 063C AFB4 3026 F724 0AA2 02B8 E547 470E 4F4B 6917 ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
