I sent a question yesterday about having problems setting the caller ID. I turned on pri debug for both a good and bad call and I see this in the good call
[2010-03-05 05:58:20.743] > [6c 0c 21 80 30 30 30 30 30 30 30 30 30 30] [2010-03-05 05:58:20.744] > Calling Number (len=14) [ Ext: 0 TON: National Number (2) NPI: ISDN/Telephony Numbering Plan (E.164/E.163) (1) [2010-03-05 05:58:20.744] > Presentation: Presentation permitted, user number not screened (0) '0000000000' ] and this is the bad one [2010-03-05 06:19:27.099] > [6c 0c 21 c3 30 30 30 30 30 30 30 30 30 30] [2010-03-05 06:19:27.099] > Calling Number (len=14) [ Ext: 0 TON: National Number (2) NPI: ISDN/Telephony Numbering Plan (E.164/E.163) (1) [2010-03-05 06:19:27.100] > Presentation: Number not available (67) '0000000000' ] Clearly this is why the caller ID is not being set. My question is who is figuring out if the forth value in the [ ] is 80 (where it works) or c3 (where it does not work)? The number was not actually 0000000000. The first call was made from a SIP phone registered to the Asterisk box with the PRI line and the second one was via an IAX trunk to the system with the PRI line. Is there some setting in some conf file that allows or disallows this behavior? -- Jim Dickenson mailto:[email protected] CfMC http://www.cfmc.com/ -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
