Brett Tate <br...@broadsoft.com> writes: >> If UAS receives a SIP message (over UDP/TCP in our >> case) from peer and in this case there is only one >> VIA header present and transport type of this VIA >> header in UNKNOWN (Here, UNKNOWN transport type means >> either we are not supporting this transport or the >> transport specified in VIA header is INVALID). Now, >> what should be the behavior of UAS? Will UAS rejects >> this message with 400 "inconsistent transport" or >> call gets successful over transport on which request >> is received (TCP/UDP). > > Since the sender is non-compliant, the UAS can basically act however it > wants.
Worse, since the UAS can't understand the transport type, there is no defined way for it to send an error response to the UAC. I suppose it could guess what the transport type should be, based on how the message was received, but RFC 3261 doesn't require that. Dale _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
