tag:blogger.com,1999:blog-1329449351744515518.post2347478126234174615..comments2023-09-16T01:28:38.178-07:00Comments on Wired n Wireless: IMS Dedicated bearersSantosh Dornalhttp://www.blogger.com/profile/08888256274707899999noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-1329449351744515518.post-86318781190246884912012-06-05T09:31:09.034-07:002012-06-05T09:31:09.034-07:00Thank you for the comment!Thank you for the comment!Santosh Dornalhttps://www.blogger.com/profile/08888256274707899999noreply@blogger.comtag:blogger.com,1999:blog-1329449351744515518.post-87324876110828261512012-06-05T08:13:14.079-07:002012-06-05T08:13:14.079-07:00If BYE is sent over UDP, and it is lost in the net...If BYE is sent over UDP, and it is lost in the network, then no 200 OK will be sent from IMS as acknowledgement. This triggers the UA/UE to retransmit the BYE message.<br /><br />According to the SIP RFC, retransmit can take place with exponential gaps until SIP Timer F in UA/UE fires. This time can be quite long: 32 seconds, if UA/UE use default timer values. After that, BYE transaction end in the SIP UA/UE, and BYE never ever arrives to IMS.<br /><br />However session timer extension to SIP (RFC4028) could provide possible solution for that. This extension allows either SIP end-points to check the availability of the signaling path. For example IMS can check periodically whether the UA/UE is reachable/alive. If it does so, it sends in dialog INVITE message to the UA/UE. If no answer arrives, the signaling path is considered to be dead, and the call release and removal of the dedicated bearer can be initiated by the IMS.Petihttps://www.blogger.com/profile/01057088427916269239noreply@blogger.com