Actually, they claim to take anything we give them. In reality, they assume a Bellcore standard with a 1 preceding, so they take the first 10 digits after arbitrarily dropping the first digit.
Acceptable (although not terribly useful for callbacks, since we require the 1) for 10-digit US-domestic numbers. Utterly useless for anything using a non-Bellcore standard (EU, Asia, etc). I do so love it when 'international' carriers play these games. It shows how non-international they really are. N. On Fri, 13 Oct 2006 14:59:31 -0400, Andrew Joakimsen wrote > So the answer is. you need to co-ordinate with your upstream provider > how to handle E164 caller ID. They might for example just take the > first 10 digits you give them.,... but they are the only ones that > should know the answer. > > On 13 Oct 2006 10:29:03 +0200, Benny Amorsen > <[EMAIL PROTECTED]> wrote: > > >>>>> "sip" == sip <[EMAIL PROTECTED]> writes: > > > > sip> My question is, will the standard set(CALLERID(num)=BLAH) work > > sip> with non-Bellcore caller ID strings? Is it expected to be able to > > sip> also handle E164 numbers (which can be up to 15 digits) as well, > > sip> or is there another method for that? > > > > CALLERID(num) is just a field. You can put any digits you want in > > there. > > > > > > /Benny > > > > > > > > _______________________________________________ > > --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 > > > _______________________________________________ > --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 _______________________________________________ --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
