On Thu, 12 Oct 2006 14:41:11 -0400, Doug Lytle wrote > sip wrote: > > I shall assume, then, from the lack of response any of the four things: > > > > A) I'm doing this correctly > > > > B) No one knows for certain > > > > C) No one does E164 caller IDs > > > > D) No one read this. > > > > I would fall into the categories of (B) (C) and (E) > > E} I don't know what E164 Caller IDs are. > > Doug >
http://en.wikipedia.org/wiki/E.164 By E164 caller ID, I mean a caller ID in E164 format. i.e. country code+prefix+number (for instance, the country code for the US is 1 followed by a LATA followed by a prefix (rate center) followed by a number... so a full E164 phone number contains all that: 14155551212 Country code for the UK is 44 followed by a prefix code followed by a number... so, for instance, a number in Milford Haven, UK might be 441646555112 (which would be its E164 phone number). Question is, most of the caller IDs I see with examples online are Bellcore style caller IDs (only useful in the US and a couple of other places) which are 10-digit. My question is, will the standard set(CALLERID(num)=BLAH) work with non-Bellcore caller ID strings? Is it expected to be able to also handle E164 numbers (which can be up to 15 digits) as well, or is there another method for that? N. _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
