Hello, I am not sure what triggers this but I get a bad P-Asserted-Identity header from Free-SWITCH in an UPDATE request when I create a conference and send an INVITE to that conference. Here is the offending Request : UPDATE sip:502@192.168.5.75:6060;x-sipX-nonat SIP/2.0 Via: SIP/2.0/UDP 192.168.5.75:15060;rport;branch=z9hG4bK2ZtpZ94m4Zg7F Route: <sip:192.168.5.75:5060;lr;sipXecs-rs=*auth~.*from~OUQ1MENEMEQtODAzNjU5QkU%60.900_ntap*id~MTQ0MDMtOQ%60%60!34e982a809955a84b401940d3c785d61> Max-Forwards: 70 From: <sip:502@sipxtest.sipxtest.net;user=phone>;tag=2ecF2jHpjjH6c To: "user1" <sip:user1@sipxtest.sipxtest.net>;tag=9D50CD0D-803659BE Call-ID: 41745e29-669e33ca-619711cf@192.168.5.242 CSeq: 6399341 UPDATE Contact: <sip:502@192.168.5.75:15060;transport=udp> User-Agent: FreeSWITCH-mod_sofia/1.0.head-2 Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, UPDATE, INFO, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE Supported: timer, precondition, path, replaces Content-Type: application/sdp Content-Disposition: session Content-Length: 297 P-Asserted-Identity: "conference" <conference> p-asserted-identity should specify a SIP URI and it does not. Is this indicative of a misconfiguration somewhere or is it a bug? Where is the P-A-I header constructed from? Thanks Regards, Ranga -- M. Ranganathan