> Can anyone explain me the reason for sending BYE by UAC. You didn't provide enough information (such as time interval before BYE sent). For instance if BYE sent immediately upon receiving 200 response for INVITE, the SDP might be malformed or there was unexpected offer/answer behavior. I mention it because there was a 183 (likely with SDP), 180, and subsequent 2xx with SDP. If the 2xx's SDP is different (assuming same dialog), there can be interoperability issues since RFC 3261 indicates to ignore the SDP (although some vendors non compliantly send it as updated answer or new offer per configuration).
Since the BYE can be sent for variety of reasons, you might want to ask the client vendor (assuming BYE not instigated by user) why they sent BYE. > I want to know, if UAC does not support "TIMER" > functionality whether UAS can send this session > expires with support of "timer" in 200ok. Yes; see RFC 4028 Table 2. > is this the reason for sending BYE by UAC. I doubt it since the UAC didn't indicate timer support. However if UAC is actually a B2BUA and BYE sent around expiration time, it could be expected since answering device didn't refresh the session within the 200's Session-Expires interval. -- This email is intended solely for the person or entity to which it is addressed and may contain confidential and/or privileged information. If you are not the intended recipient and have received this email in error, please notify BroadSoft, Inc. immediately by replying to this message, and destroy all copies of this message, along with any attachment, prior to reading, distributing or copying it. _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
