If I disable the ignore early media, it do not get the messages such as network congestion or the number is out of service.  They are being playing during early media.  Went thru all those scenarios.   The case I am trying to solve is the dead carrier which does happen, would be nice to detect this somehow without waiting for the normal progress or answer timeout.
 
I use another product for some tandem switching that does upt to 4 Invites with a retry of 1 second on no trying message then allows for a failover, works very good.  Customers rarely notice the delay.  Would really like a similar function in the freeswitch.
 
Darcy
----- Original Message -----
From: Robert Hadley
To: FreeSWITCH Users Help
Sent: Friday, November 08, 2013 4:10 PM
Subject: Re: [Freeswitch-users] call timeout and failover

Hi,

Also try with setting the ignore_early_media=true or =ring_ready channel variable or in the dial string.

 

http://wiki.freeswitch.org/wiki/Channel_Variables#ignore_early_media

 

http://wiki.freeswitch.org/wiki/Early_Media#Ignoring_Early_Media

 

Regards,

Robert

 

 

From: François [mailto:fdelawarde@wirelessmundi.com]
Sent: Friday, November 08, 2013 12:54 PM
To: FreeSWITCH Users Help
Subject: Re: [Freeswitch-users] call timeout and failover

 

Did you try with the "leg_progress_timeout" variable?

François.

On Fri, 2013-11-08 at 15:06 -0500, fs wrote:

I wonder if anyone has any thoughts on this.   Using continue on fail works fine for failover but to the best of my knowledge it only works if you do not get an answer or session progress.  The trouble with this is if you are calling cell phones etc, it can take up to 12 seconds to get the messages.  I would like to explore if failover could be instituted by not receiving a Trying message.  This is usually returned immediately and does stop the freeswitch from sending more invites.  That way, a 4 second timer could be used and switch to an alternate route early and still give reasonable completion times. 

 

The tcap trace below shows a typical call to a cell in our area,  the trying is almost immediate while the cell in this case took 5.5 seconds.  I have seen this quite frequently take as long as 12 seconds.

 

Also, when calling internationally, longer times are quite common.

 

Perhaps this is already implemented but I have not been able to find it.

 

449.776291  SIP/SDP Request: INVITE sip:1613802xxxx@xxx.xxx.xxx.xx, with session description
449.782429  SIP Status: 100 Trying
456.211562  SIP/SDP Status: 183 Session Progress, with session description

Darcy Primrose

voice2net

 
_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com
 
FreeSWITCH-powered IP PBX: The CudaTel Communication Server
http://www.cudatel.com
 
Official FreeSWITCH Sites
http://www.freeswitch.org
http://wiki.freeswitch.org
http://www.cluecon.com
 
FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org

 


_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com

FreeSWITCH-powered IP PBX: The CudaTel Communication Server
http://www.cudatel.com

Official FreeSWITCH Sites
http://www.freeswitch.org
http://wiki.freeswitch.org
http://www.cluecon.com

FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org


No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4158 / Virus Database: 3615/6799 - Release Date: 11/01/13