> However, in ACK, the Server is not including any > transport field in the Contact header.
As indicated within RFC 3261 section 12.2, "ACK is NOT a target refresh request". Thus an ACK's Contact should have no impact upon the dialog. However, I assume that the INVITE's Contact indicated the same thing. I'll also assume that there was no Record-Route added during call setup. > Now, as per RFC3261, if there is no transport > mentioned in the Contact header, then by default, > it shall be considered as UDP transport. As described within RFC 3263, this is not completely true since there is the potential for NAPTR and SRV to indicate another transport. For instance if the Contact did not contain a port and did not contain an IP address, the NAPTR and SRV queries should occur. > So, my UA sends BYE using transport as UDP. But the Server > does not recognize it and does not terminate session. The transport type might not be the reason that they are ignoring the request. And if it is, there may be a configuration issue. > Similar kind of case occurs when INVITE with > TCP is send by Client and Server does not > mention transport in Contact header of 200 OK > against INVITE message. > > So, what shall be the actual behavior in this case? Not sure since NAPTR and SRV may have been appropriate and indicated to send over a transport other than UDP. Otherwise, the device has communicated a preference to receive mid-dialog requests over UDP (assuming not a sips Contact). _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
