Summary:	ASTERISK-03220: [request] Timeout for Connect?
Reporter:	Nabeel Jafferali (nabeelj)	Labels:
Date Opened:	2005-01-08 15:50:54.000-0600	Date Closed:	2011-06-07 14:05:15
Priority:	Major	Regression?	No
Status:	Closed/Complete	Components:	Core/NewFeature
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	I am using Dial() to initiate a call to another * server or IAX provider (which is further completing the call onto the PSTN network). Sometimes, that server/provider is trying to make the call and it is not succesfully connecting (common with international destinations). The remote server won't fail the call until some long timeout (like 60 or 90 secs). Using the timeout to get around this and fall back to a backup provider does not work, because the timeout is for the call to be answered, not the call the being ringing. Therefore, using (for example) a 20 sec timeout would mean that the call would never go to voicemail if a person doesn't answer. An additional option to specify a timeout to wait for the call to start ringing would be a great help.
Comments:	By: Andrey S Pankov (casper) 2005-01-11 07:37:20.000-0600 Not sure this should be an app_dial feature. What do you mean by "timeout to wait for the call to start ringing"? Is there any reply from remote iax server? Is this a network fail? Or buggy remote server? By: Nabeel Jafferali (nabeelj) 2005-01-11 10:04:06.000-0600 The remote server is attempting to make the call. However, because of a bad upstream connection, it is still waiting for progress information. This commonly happens on cheaper international connections (even on landlines). Now, the only way to avoid this problem and jump to the backup provider would be to have a timeout to when the call has been passed on to the PSTN successfully (and therefore begun ringing). This is what I refer to at the "ringing timeout". This is as opposed to the current timeout, which is to when the call is answered, which is what I refer to as the "answer timeout". When this situation happens, the only message I see on the console is "progess information being passed...". By: Clod Patry (junky) 2005-02-11 19:14:53.000-0600 Not sure to get the point here, can you add more infos like the problem in real life and maybe your dialplan for that part too. I'm sure there's a way to deal with it with the actual timeout. I think that's just a deal of dialplan logic. By: Kevin P. Fleming (kpfleming) 2005-02-12 10:11:43.000-0600 I have been thinking about adding this as well. When you pass a call off via IAX/SIP, and the provider accepts the call (and possibly generates "session progress") but nothing ever happens, there is no way to abort the call sooner than the master timeout. I can see a couple of a possibilities for this shorter timeout: - if no "session progress" is received - if no "alerting" is received - if "session progress" is received but no actual audio ever arrives on the back channel Basically I would refer to this as a "progress timeout", as opposed to the current "answer timeout". It would mean "if the call does not make adequate progress by this time, abort it". edited on: 02-12-05 10:12 By: Nabeel Jafferali (nabeelj) 2005-02-14 10:39:55.000-0600 Thinking about it, I agree with kpfleming's idea of a progress timeout. Unfortunately, this is way beyond my programming capabilities. By: Olle Johansson (oej) 2005-03-16 13:20:00.000-0600 TImeout for this request. Re-open if there's a patch. The report stays in the bug tracker for inspiration.