[Freeswitch-users] failover based on initial INVITE timeout

[Hristo Trendev]

I've seen this parameter when I started testing, but the name suggest
that it will do icmp ping to detect failed gateways (haven't really
tried it though). I need to detect sip service failure as well - the
case where the destination server is up (ping replies are received),
but the sip process is down and there is no response to sip requests.

If the ping parameter uses sip-based ping (like OPTIONS ping) this may
be a solution for me as well.

On Tue, Aug 18, 2009 at 9:30 PM, Brian West<brian at freeswitch.org> wrote:
> setup gateways and turn on the ping option.
> /b
>
> On Aug 18, 2009, at 1:24 PM, Hristo Trendev wrote:
>
>> TCP is not really an option for me. I have tried using different sofia
>> profile for that and set:
>>
>> <param name="timer-T1X64" value="1000" />
>>
>> This works the way I want and INVITEs to dead gateways are
>> disconnected with [RECOVERY_ON_TIMER_EXPIRE], but:
>> 1. It affects all calls sent via this "custom timer" profile
>> 2. I need to use one more SIP port to bind to (I need keep the
>> "default timers" profile as well)
>> 3. The timer is used by transactions other than the initial invite
>> message and that may cause unexpected problems.
>>
>> Obviously originate_timeout doesn't work the way it's supposed to
>> (according to the wiki) so I will report it as bug.
>>
>> The profile trick above actually solves my problem and may happen to
>> be a better solution after all, but I will need to test it for some
>> time before I know.
>
>
> _______________________________________________
> FreeSWITCH-users mailing list
> FreeSWITCH-users at lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> http://www.freeswitch.org
>