| Summary: | ASTERISK-02369: rtptimeout hanging up "dialling channels" | ||
| Reporter: | duncan (duncan) | Labels: | |
| Date Opened: | 2004-09-08 09:40:28 | Date Closed: | 2004-09-25 02:04:43 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | if you set rtptimeout to be something low like 20, it will hangup channels that are just ringing for 20 seconds, before they have a chance to answer. this seems like bad behaviour, wouldnt it be possible to initiate rtp timeouts only on "answered/bridged" channels. as a result ive had to set my rtp timeouts to greater and greater values as it can take a while to route calls around my network. | ||
| Comments: | By: Brian West (bkw918) 2004-09-08 10:26:34 rtptimeout should be set to something like 300 seconds anyway. This is how it would behave because the RTP stream isn't even up yet. bkw By: Mark Spencer (markster) 2004-09-08 21:30:14 Clearly 20 seconds is an unreasonably low value for the rtptimeout, however I did make the change anyway so that it will only consider it if the channel is "UP". | ||