sean-cc / jain-slee

Automatically exported from code.google.com/p/jain-slee
0 stars 0 forks source link

No dialog timeout event generated when dialog times out. Dialog silently terminated. #11

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Have a client send an INVITE and an Sbb responding to that, creating a 
dialog activity and attaching to it.
2. Have the client wait longer than 64*T1 before sending an ACK.
3. The ACK will be silently ignored and the dialog terminated. The Sbb is not 
aware of this situation.

What is the expected output? What do you see instead?
According RFC, a dialog timing out should prompt the sending of a BYE toward 
the client. When the dialog timeout is send as an event toward the Sbb this 
will give it the opportunity to respond to this, cleanup resources and send a 
BYE.

Please use labels and text to provide additional information.
Problem appears in 2.7.0.FINAL of sip-ra.
The JAIN-SIP stack already has provisions for this with the introduction of the 
SipListenerExt class.

See also: 
https://groups.google.com/forum/?fromgroups=#!topic/mobicents-public/glINr38U94Q

Original issue reported on code.google.com by tom.uijl...@gmail.com on 14 Nov 2012 at 11:12

GoogleCodeExporter commented 9 years ago
Pushed a change with git.

- Please review and schedule for inclusion in next release.

- Note: this change will now leave any timed-out dialogs (and related 
activities) open instead of silently terminating them. Regression checks are 
advised.

- Note2: first time git user. Let me know if I screwed-up.

TIA,
    Tom.

Original comment by tom.uijl...@gmail.com on 14 Nov 2012 at 11:24

GoogleCodeExporter commented 9 years ago
this needs to be reviewed and possibly moved upstream to telscale

Original comment by EMMart...@gmail.com on 11 Apr 2013 at 11:43

GoogleCodeExporter commented 9 years ago

Original comment by EMMart...@gmail.com on 9 Jul 2014 at 3:26