Hello Ishfaq,

I just tried it and it did create a P-Asserted header however it
contains the extension
of the asterisk peer not what was passed by our switch. From the
previous example:

P-Asserted-Identity: "222" <sip:222@192.168.2.10> (which is asterisk
peer extension and not)
P-Asserted-Identity: "John Doe"
<sip:14167493...@toronto.location.com>; user=phone; nat=yes. (which is
being passed by the call leg)

Is there a flag that retains the rpid from the call leg?

Kind Regards,

Nick

-- 
_____________________________________________________________________
-- 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

Reply via email to