Hi All, I am working with a third party who is sending Remote-Party-ID with an additional space than we typically see, and our app is not parsing the name properly to display on the phone. I am trying to understand if the third party SIP is behaving appropriately with the Remote-Party-ID:
Incoming Message: INVITE sip:1210408#[email protected]:5060;transport=udp SIP/2.0 Via: SIP/2.0/UDP x.x.x.x:5060;branch=z9hG4bK928944d55440bffe739c6d1dc9ea8e43.0 Session-Expires: 14400 Record-Route: <sip:[email protected];lr> Record-Route: <sip:x.x.x.x;lr;ftag=gK071366e5> Record-Route: <sip:x.x.x.x;lr=on;ftag=gK071366e5> Via: SIP/2.0/UDP x.x.x.x;branch=z9hG4bKe6a7.a5e075a7.0.fso88Pc4o0lLG-kbMSZ2Bg__ Via: SIP/2.0/UDP x.x.x.x;branch=z9hG4bKe6a7.7f99a4e6.1.A5UQyGfP-ul0FAx-HK+hCQ__ Via: SIP/2.0/UDP x.x.x.x:5060;branch=z9hG4bK07Bedb7466ad9a4b760.mGc9WrRat2LaP6yV0oADNQ__ From: "CISCO SYSTEMS " <sip:+1919392#[email protected]>;tag=gK071366e5 To: <sip:[email protected]> Call-ID: [email protected] CSeq: 27151 INVITE Max-Forwards: 56 Contact: <sip:ewsvb3zduuuoer7tava1qmwzltp4ysprlr04szrfxwfksakpd6r6m6oczbjjbf...@x.x.x.x> Content-Length: 279 Content-Disposition: session; handling=required Content-Type: application/sdp Remote-Party-ID: "CISCO SYSTEMS " <sip:[email protected]:5060>;privacy=off P-Asserted-Identity: <sip:+1919392#[email protected]:5060> Notice after the "CISCO SYSTEMS " there are two space before the <sip The BNF doesn't seem clear on if the spacing is significant: http://www.ietf.org/proceedings/50/I-D/sip-privacy-01.txt Remote-Party-ID = "Remote-Party-ID" ":" [display-name] "<" addr-spec">" *(";" rpi-token) Can anyone comment if this is correct Remote-Party-ID syntax or if only a single space should be allowed? (which our app is expecting) Thanks, -- Adam _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
