| Summary: | ASTERISK-01415: Some SIP clients due to poor firmware do not terminate correctly with * resulting in very long almost silent calls | ||
| Reporter: | chrisorme (chrisorme) | Labels: | |
| Date Opened: | 2004-04-15 18:01:05 | Date Closed: | 2011-06-07 14:05:25 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | Request for consideration of a feature in a future version of asterisk, when someone has time or motivation, to watch out in chan_sip.c for long silent SIP calls and terminate them after some time (30secs or a minute ? - make this user definable or a variable in chan_sip.c ?). Concern: I don't know how that would deal with calls on hold? I haven't looked in detail at how these clients mess these calls up that last forever. Perhaps there's some way apart from the silence to detect that a call has hung (pardon the pun) ie. crashed through the control stream/traffic? I think this is a request for sip session timers for a sip buff as a workaround for a limitation in SIP itself and SIP client firmware programmers ;). Is this really really hard ? Is there a quick and nasty fix instead ? ****** ADDITIONAL INFORMATION ****** Culprits: Draytek 2600V(G) (for now) and others - bugs reported here and there for other devices too. | ||
| Comments: | By: chrisorme (chrisorme) 2004-04-15 19:06:16 Elesign ESC1710 is an alleged culprit (ASTERISK-1371400) Kphone is an alleged culprit (ASTERISK-1600207) Draytek 2600V is a culprit (ASTERISK-1191239) Anyone else find this with their device ? By: Brian West (bkw918) 2004-04-15 19:12:39 This will require sip session timer support to fix By: Brian West (bkw918) 2004-04-15 19:13:46 Sip session timer support has already been added to the WE NEED THIS ASAP list but the problem is finding someone to implement this feature. I think bug 207 talked about this ALOT. | ||