| Summary: | ASTERISK-01419: Dial should have an IP connection timeout - separate from timeout. | ||
| Reporter: | jharragi (jharragi) | Labels: | |
| Date Opened: | 2004-04-16 14:10:48 | Date Closed: | 2011-06-07 14:05:14 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | This is a fork from feature request 1378. The syntax is the same but a different idea. [outlocalpri_works] exten = _9NXXXXXX,1,Dial(IAX2/REMOTE_A@PRI_B/${EXTEN}|2) exten = _9NXXXXXX,2,Wait(1) exten = _9NXXXXXX,3,Dial(IAX2/REMOTE_A@PRI_C/${EXTEN}) exten = _9NXXXXXX,4,Congestion We should create a secondary or default IP timeout. This is what I'm trying to accomplish with the timeout of 2 (in priority 1). However, when calling some destinations this is interprated as a real timeout (and rightly so - I don't know why this line works at all) and may ring the destination once then hangup (on timeout). Yet on most calls this is not the case and they work nicely. The timeout must be specified because if the PRI_B machine is not found (or maybe if asterisk is not running - I have not tested this) the dial application keeps looking for it for an indeterminate amount of time. ****** ADDITIONAL INFORMATION ****** There can be a timeout specified on the PRI_B machine that usually seems to determine the duration of the call attempt. | ||
| Comments: | By: Olle Johansson (oej) 2004-04-16 17:37:15 I don't think you can do such a general thing to dial, the channels take care of timeouts on various protocols and device channels. Check how the IAX2 channel handles calls to non-existing or non-reachable hosts instead. By: Olle Johansson (oej) 2004-04-16 17:37:44 Not a bug, feature request. Will stay in archive. | ||