Yeah: we are using pridialplan=local - am using AsteriskNOW by the way. Does it require some kind of a patch? for it to understand 'pridialplan' ?
My pri intense debug shows: > Calling Number (len= 4) [ Ext: 0 TON: National Number (2) NPI: ISDN/Telephony Numbering Plan (E.164/E.163) (1) > Presentation: Number not available (67) '' ] > [70 0b a1 39 37 38 39 30 39 31 30 31 31] > Called Number (len=13) [ Ext: 1 TON: National Number (2) NPI: ISDN/Telephony Numbering Plan (E.164/E.163) (1) '9789091011' ] Thanks Rajeev On Dec 19, 2007 3:47 AM, Tilghman Lesher <[EMAIL PROTECTED]> wrote: > On Tuesday 18 December 2007 15:22:18 Rajeev Natarajan wrote: > > We have a PRI line setup on an asterisk box using TE110P. Both outbound > and > > inbound are working fine BUT the provider claims that all our numbers > come > > prefixed with a '0' (in India a 0 prefix indicates long distance) and > that > > could become an issue with local calls. > > What is pridialplan set to in zapata.conf? This value sets an extra 4 > bits in > the PRI dialog between you and the telco. And typically, if you have it > set > to something like 'national', the telco will tell you you have numbers > prefixed, even when you don't, because their switch software is written to > make the translation. > > So what most people do (and what works most often) is to set pridialplan > to > 'unknown', which sets the bit field to all zeros and the number isn't > prefixed > at all at the telco switch, but simply routed based upon the number sent. > > -- > Tilghman > > _______________________________________________ > --Bandwidth and Colocation Provided by http://www.api-digital.com-- > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users >
_______________________________________________ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users