> So in a call from when UAS is sending response [1xx and 200OK] > with a Server header but with a faulty value in that header > as per ABNF. All other headers values are perfect in those > responses. Then UAC is not sending ACK and the call is not > getting established. > Is it an expected behaviour from UAC as per RFC?
Because the header is malformed, the UAC can basically act however it wants. However with that said, the following is a snippet concerning UAS. There might be similar text somewhere concerning UAC. RFC 3261 section 8.2.2: "A UAS SHOULD ignore any malformed header fields that are not necessary for processing requests." _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
