Hi Brett, There is no Record-Route added in the INVITE or ACK sent by Server in this case. Also, domain name is not used for Server in this case. So, NAPTR and SRV is not the case here.
I had referred section 12.2 in RFC3261 and it says that; "For dialogs that have been established with an INVITE, the only target refresh request defined is re-INVITE (see Section 14). Other extensions may define different target refresh requests for dialogs established in other ways. Note that an ACK is NOT a target refresh request." So, agreed that ACK shall not be considered here for any type of session refreshing procedure. Regarding your following comment; " The transport type might not be the reason that they are ignoring the request. And if it is, there may be a configuration issue." Are you trying to say that, irrespective of session is occurred using any transport, if the session termination request (or any other mid-session request) is generated using different transport, then also it shall be entertained??? Is such thing mentioned in any RFC? Thanks, Mohit Soni -----Original Message----- From: Brett Tate [mailto:br...@broadsoft.com] Sent: Sunday, August 25, 2013 7:36 PM To: Mohit Soni; Sip-implementors@lists.cs.columbia.edu Subject: RE: [Sip-implementors] What if transport=tcp is not mentioned in Contact header of any request/response? > 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 Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
