2010/9/20 Aneesh Naik <[email protected]>: > > Following can be the possible behavior: > 1. Even though the GW cannot understand the Content-Type, it can skip the > parsing of the message mody, > process the non-2XX response and send an ACK message for it, and bring > down the call. > > 2. The GW can publish the Accept Header in initial INVITE, and if it recives > a response with Content-Type that it > does not understand, then it can silently drop the response message. > > 3. The current behavior by GW of dropping the Response with Contect-Type it > does not understand, if RFC says > so. I cound not find any answer for this.
The most important is that the response is a final non-2XX, so the gateway must terminate the transaction, regardless of the wrong/unexpected/unknown response body. Option is the correct one. -- Iñaki Baz Castillo <[email protected]> _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
