Hi All, Having searched the archives, I can see there has been much discussion at various points regarding capture of caller id information from good old BT. If I understand correctly, it seems that not only do the drivers not currently support it, but my X101P possibly/probably can't do it anyway due to hardware? So, that leaves me with the modem route, which seems more and more unlikely, due to the seeming difficulties finding a modem that will *definitely* do it, or the CD50 mod. Which brings me to my question (finally).... Has anyone done this [the CD50] mod? It seems the CD50 can be found for a few quid, and I'm not afraid of my soldering iron... I just wondered how people in the UK were capturing callerid..... there is so much more you can get asterisk to do if you have access to callerid info..... By the way..... much as I'd like to do this by switching to ISDN, and be done with it, this server is at my home for me to play with, and ISDN is *not* cheap.... in fact it would roughly double my quarterly phone bill..... other than the price, ISDN would be my solution of choice! 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 ________________________________________________________________________
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 <tmh@nodomain.org> Key ID: 104D/4F4B6917 2003-09-13 Fingerprint: 063C AFB4 3026 F724 0AA2 02B8 E547 470E 4F4B 6917
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: asterisk-users-admin@lists.digium.com [mailto:asterisk-users- > admin@lists.digium.com] On Behalf Of Tony Hoyle > Sent: 22 May 2004 23:55 > To: asterisk-users@lists.digium.com > Subject: Re: [Asterisk-Users] Caller ID with BT CD50 > > Karl Dyson wrote: > > > Hi All, > > > > Having searched the archives, I can see there has been muchdiscussion> > at various points regarding capture of caller id information fromgood> > 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 itanyway> > 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 arePace,> Hayes > (Europe), and 3Com/US Robotics." > > It then goes on to state all 3 of those manufactures no longer supportit.> > I wonder if the low cost geographic VOIP numbers support it? > > Tony > > -- > Te audire no possum. Musa sapientum fixa est in aure. > > Tony Hoyle <tmh@nodomain.org> Key ID: 104D/4F4B6917 2003-09-13 > Fingerprint: 063C AFB4 3026 F724 0AA2 02B8 E547 470E 4F4B 6917 > _______________________________________________ > 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 > >________________________________________________________________________> 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 ________________________________________________________________________
> I have a USR modem too but it's a brick unfortunately... Pity as itwas> 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 softmodems> 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 ________________________________________________________________________
> > 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: 0x00000000 HardwareVersion: 0x0006 0x0000 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 ________________________________________________________________________
> If you had CID to start with, I'd expect it to work - eg. you wouldn'tget> it > from the POTS line but if a VOIP call came in and the ATA186retransmitted> 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 ________________________________________________________________________
> >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, theyhave> 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 ________________________________________________________________________
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: asterisk-users-admin@lists.digium.com [mailto:asterisk-users-admin@lists.digium.com] On Behalf Of Tony Hoyle Sent: 26 May 2004 13:09 To: asterisk-users@lists.digium.com 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 cardIf 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 <tmh@nodomain.org> 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 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
Can confirm it works with Generic X101P *BIG* Thank you :) -----Original Message----- From: asterisk-users-admin@lists.digium.com [mailto:asterisk-users-admin@lists.digium.com] On Behalf Of Kevin Walsh Sent: 26 May 2004 16:15 To: asterisk-users@lists.digium.com Subject: RE: [Asterisk-Users] Caller ID with BT CD50 Tony Hoyle [tmh@nodomain.org] wrote:> > Lost some of the mails on this topic somewhere. > > > > Does this need the BT50 mod or will the X100p now output the CallerID?> > > 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 _/ _/ _/ _/ _/ _/ _/ _/_/ kevin@cursor.biz _/ _/ _/_/_/_/ _/ _/_/_/ _/ _/ _______________________________________________ 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 ________________________________________________________________________ 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 ________________________________________________________________________
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: asterisk-users-admin@lists.digium.com [mailto:asterisk-users-admin@lists.digium.com]On Behalf Of Tony Hoyle Sent: 27 May 2004 22:31 To: asterisk-users@lists.digium.com 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 <tmh@nodomain.org> Key ID: 104D/4F4B6917 2003-09-13 Fingerprint: 063C AFB4 3026 F724 0AA2 02B8 E547 470E 4F4B 6917 _______________________________________________ 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
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: asterisk-users-admin@lists.digium.com [mailto:asterisk-users- > admin@lists.digium.com] On Behalf Of Kevin Walsh > Sent: 28 May 2004 09:12 > To: asterisk-users@lists.digium.com > Subject: RE: [Asterisk-Users] Caller ID with BT CD50 > > Robert Boardman [robb@boardman.me.uk] 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 home2but> > '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 sh> _/ _/ _/ _/ _/ _/ _/ _/_/ kevin@cursor.biz > _/ _/ _/_/_/_/ _/ _/_/_/ _/ _/ > > >________________________________________________________________________> 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 ________________________________________________________________________
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: asterisk-users-admin@lists.digium.com [mailto:asterisk-users- > admin@lists.digium.com] On Behalf Of Kevin Walsh > Sent: 28 May 2004 12:07 > To: asterisk-users@lists.digium.com > Subject: RE: [Asterisk-Users] Caller ID with BT CD50 > > Karl Dyson [kd@junesta.com] 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 sh> _/ _/ _/ _/ _/ _/ _/ _/_/ kevin@cursor.biz > _/ _/ _/_/_/_/ _/ _/_/_/ _/ _/ > > _______________________________________________ > 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 > >________________________________________________________________________> 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 ________________________________________________________________________
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: asterisk-users-admin@lists.digium.com [mailto:asterisk-users- > admin@lists.digium.com] On Behalf Of Karl Dyson > Sent: 28 May 2004 12:36 > To: asterisk-users@lists.digium.com > 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: asterisk-users-admin@lists.digium.com [mailto:asterisk-users- > > admin@lists.digium.com] On Behalf Of Kevin Walsh > > Sent: 28 May 2004 12:07 > > To: asterisk-users@lists.digium.com > > Subject: RE: [Asterisk-Users] Caller ID with BT CD50 > > > > Karl Dyson [kd@junesta.com] 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 twolines> > 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 ls> h > > _/ _/ _/ _/ _/ _/ _/ _/_/ kevin@cursor.biz > > _/ _/ _/_/_/_/ _/ _/_/_/ _/ _/ > > > > _______________________________________________ > > 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 > > > > >________________________________________________________________________> > This e-mail has been scanned for all viruses by Star Internet. The > > service is powered by MessageLabs. For more information on aproactive> > 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 > 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 > >________________________________________________________________________> 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 ________________________________________________________________________
Certainly Tony's original patch for CID works with my generic X101P (reports itself as an Intel 537 IIRC). I will get around to downloading his new single patch that includes distinctive ringing and testing it in the next couple of days. Cheers for now, Karl> -----Original Message----- > From: asterisk-users-admin@lists.digium.com [mailto:asterisk-users- > admin@lists.digium.com] On Behalf Of Tony Mountifield > Sent: 29 May 2004 19:06 > To: asterisk-users@lists.digium.com > Subject: [Asterisk-Users] Re: Caller ID with BT CD50 > > In article <40B8CD14.4080106@nodomain.org>, > Tony Hoyle <tmh@nodomain.org> wrote: > > Kevin Walsh wrote: > > > > > I downloaded the latest version of your patch, from your website,and> > > it works perfectly. I had waited until I had some time available > > > because I thought I'd have to play around with it for a while. > > > > Great. Just need to make sure that it still works for US lines and > it's all set. > > > > There's some debate whether to use this patch or to wait for onethat> uses > > line reversal/guard tone detection... there is the slight problemthat> the > > X100P can't detect line reversal so it'd mean everyone upgradingtheir> > hardware... still, I have what 'works for me' and will continuehosting> it > > for a while whatever happens. > > Is that the X100P generically, including the X101P? > > I would include both algorithms - the line reversal one for thehardware> that can do it, and your current one for those that can't. > > Cheers, > Tony > -- > Tony Mountifield > Work: tony@softins.co.uk - http://www.softins.co.uk > Play: tony@mountifield.org - http://tony.mountifield.org > _______________________________________________ > 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 > >________________________________________________________________________> 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 ________________________________________________________________________
Ok, I can report that I have just (within the last 2 hours, anyway) downloaded the current cvs head for zaptel and asterisk, and applied Tony's current patches downloaded freshly this evening from nodomain. All applied and compiled, and with a tweak to my dring statements after running asterisk in debug, cli and dring are both working :) Calls with no CLI on either number go straight to voicemail without ringing a phone (usually cold callers in my experience), and I lookup the caller id in a mysql db using an AGI written in perl, that also allows me to display which number the caller dialled as well as a friendly name against the cli in the 7905 displays :) Thanks All, Karl> -----Original Message----- > From: asterisk-users-admin@lists.digium.com [mailto:asterisk-users- > admin@lists.digium.com] On Behalf Of Karl Dyson > Sent: 30 May 2004 00:33 > To: asterisk-users@lists.digium.com > Subject: RE: [Asterisk-Users] Re: Caller ID with BT CD50 > > Certainly Tony's original patch for CID works with my generic X101P > (reports itself as an Intel 537 IIRC). I will get around todownloading> his new single patch that includes distinctive ringing and testing itin> the next couple of days. > > Cheers for now, > > Karl > > > -----Original Message----- > > From: asterisk-users-admin@lists.digium.com [mailto:asterisk-users- > > admin@lists.digium.com] On Behalf Of Tony Mountifield > > Sent: 29 May 2004 19:06 > > To: asterisk-users@lists.digium.com > > Subject: [Asterisk-Users] Re: Caller ID with BT CD50 > > > > In article <40B8CD14.4080106@nodomain.org>, > > Tony Hoyle <tmh@nodomain.org> wrote: > > > Kevin Walsh wrote: > > > > > > > I downloaded the latest version of your patch, from yourwebsite,> and > > > > it works perfectly. I had waited until I had some timeavailable> > > > because I thought I'd have to play around with it for a while. > > > > > > Great. Just need to make sure that it still works for US linesand> > it's all set. > > > > > > There's some debate whether to use this patch or to wait for one > that > > uses > > > line reversal/guard tone detection... there is the slightproblem> that > > the > > > X100P can't detect line reversal so it'd mean everyone upgrading > their > > > hardware... still, I have what 'works for me' and will continue > hosting > > it > > > for a while whatever happens. > > > > Is that the X100P generically, including the X101P? > > > > I would include both algorithms - the line reversal one for the > hardware > > that can do it, and your current one for those that can't. > > > > Cheers, > > Tony > > -- > > Tony Mountifield > > Work: tony@softins.co.uk - http://www.softins.co.uk > > Play: tony@mountifield.org - http://tony.mountifield.org > > _______________________________________________ > > 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 > > > > >________________________________________________________________________> > This e-mail has been scanned for all viruses by Star Internet. The > > service is powered by MessageLabs. For more information on aproactive> > 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 > 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 > >________________________________________________________________________> 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 ________________________________________________________________________