I don't remember the rfc regarding P-Asserted-identity completely, but it also has to do with trusted networks. When someone sends an invite to freeswitch that is authenticated, this side is authenticated and freeswitch trusts it's p-asserted-identity I believe, unless you overwrite it. When the other side is also trusted, it just forwards it, else it will strip it to anaonymous (or it should I think). Kind regards, Michel On Wed, Mar 19, 2014 at 10:54 PM, George Assaad <gassaad@emassembly.com>wrote:
Hi, When freeswitch receives 200 OK in the packet we see the following:
From: "company" <sip:+compnay phone #@IP;user=xxxx> P-Asserted-Identity:"vendor"<sip:+vendor phone #@IP;user=phone> Privecy: id
When freeswitch sends the same 200 OK packet to the endpoint: P-Asserted-Identity: "vendor" <sip:+vendor phone #@IP>
Ideally we need freeswitch to either stripped the identity or leave the *privacy id* header.
How to do that?
Regards,
George
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org