On Fri, Oct 12, 2012 at 11:47 AM, Matthew Jordan <[email protected]> wrote: > After loading, [peer01] shows up as a known SIP endpoint. Calling > peer01 displays the same caller ID as before, i.e., either 101/D40 01 or > 101/foo. Note that none of this using the DPMA either. Here's something important that I think I was missing. The CallerID construct seems to be working, but only after the call is answered. (In my testing, I didn't think to pick up the line, just ending the call from the source if I didn't see the CID.)
Turning on SIP debugging, I can see the PAI header being sent in the invite packet being sent to the D40 upon initiating (prior to answering). Does this shed any light on the issue? >> I don't know if that is necessarily true; the phones were new in box >> but were not purchased from Digium or an authorized reseller. >> > > Did they fall off the back of a truck? :-) > > Call anyway. If you purchased said phones in a legitimate manner, they > should be able to help you. They were acquired from a company that unexpectedly imploded, actually. I'm trying to avoid calling as that kills my ability to multitask on my other projects; naturally I'm the "do everything" guy at my company. > (And, as previously suggested, you may want to make sure you've upgraded > to the latest firmware, just to rule out any solved problems). They are absolutely all on 1.1.0. -- -Chris Harrington ACSDi Office: 763.559.5800 Mobile Phone: 612.326.4248 -- _____________________________________________________________________ -- 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
