> Can anyone help in unknown transport in Via Header > > 1. If the Proxy / Registrar received the below message. > > OPTIONS sip:[email protected] SIP/2.0 > To: sip:[email protected] > From: <sip:[email protected]>;tag=323 > Max-Forwards: 70 > Call-ID: transports.kijh4akdnaqjkwendsasfdj > Accept: application/sdp > CSeq: 60 OPTIONS > * Via: SIP/2.0/UNKNOWN t4.example.com;branch=z9hG4bKasd0f3en* > l: 0 > > What could be the response?
It is an abnormal situation; thus the UAS can basically act however it wants. Returning a 400 using received transport (obviously not the unknown transport) and not updating Via's transport would hopefully get the problem noticed/fixed. > 2. If the Proxy / Registrar received the below message. > > > OPTIONS sip:[email protected] SIP/2.0 > To: sip:[email protected] > From: <sip:[email protected]>;tag=323 > Max-Forwards: 70 > Call-ID: transports.kijh4akdnaqjkwendsasfdj > Accept: application/sdp > CSeq: 60 OPTIONS > * Via: UNKNOWN/2.0/UDP t4.example.com;branch=z9hG4bKasd0f3en* > l: 0 > > What could be the response? It is an abnormal situation; thus the UAS can basically act however it wants. Returning a 400 over SIP and not updating Via's protocol would hopefully get the problem noticed/fixed. _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
