Hello Iskren,

You could try to use sip-sticky-contact when bridging calls instead of using sip-force-contact, it may solve your issue (I've had no chance using sip-force-contact on my platform).

Regards
Florent


Le 23/06/2014 08:14, Iskren Hadzhinedev a écrit :

Greetings!

 

I'm looking at migrating my old FreeSWITCH 1.2.23 to 1.5.13b from git.

I have a Yealink T42G phone that has lots of issues, one of them being call drops after 32 seconds.

With 1.2.23 I was able to solve the problem using the following in my dialplan:

 

<extension name="Yealink Detection" continue="true">

<condition field="${sip_user_agent}" expression="^Yealink">

<action application="set" data="sip-force-contact=NDLB-connectile-dysfunction"/>

</condition>

</extension>

After the 1.5.13b upgrade this no longer works.

The full version I'm currently using is:

FreeSWITCH Version 1.5.13b+git~20140621T003222Z~47891d5caa~64bit (git 47891d5 2014-06-21 00:32:22Z 64bit)

Is this intended or I'm missing something obvious here :)

 

Thanks!

Kind regards,

--

Iskren Hadzhinedev



_________________________________________________________________________
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

-- 
Florent Krieg
Sewan Communications - Ingénieur R&D