Hi All! This is my first question...and what question... I'm a skilled developer and I'm almost familiar with telephony in general since it's 15 years experience in telco companies. However I'm still facing a problem I couldn't find any solution yet and i hope someone could help in finding a solution As my present company can't afford an expensive soft switch I'm using Freeswitch 1.4 with a simple dialplan.xml and some scripts to load CDRs into mysql to send incoming calls to my remote peers. At present the live traffic is only 1 incoming IP and 1 outgoing peer, quite easy. On some calls I'm getting "408 Request Timeout" and FS is giving me a RECOVERY_ON_TIMER_EXPIRE cause (IDSN 102). The problem is that as most of the switches are not able to make automatic rerouting based on this cause and so, I will like to use instead the ISDN Cause 18 (I suppose "480 Temporarily unavailable"). Is this possible? I've used this snippet of code that use another relcause but with same concept (taken as is and pasted into the dialplan) but doesn't work as the 408 is given after 183. <extension name="AllDestinations_Inbound"> <condition field="destination_number" expression="^"> <condition field="network_addr" expression="^154\.48\.198\.190$"/> <action application="set" data="hangup_after_bridge=true"/> <action application="set" data="continue_on_fail=19"/> <action application="bridge" data="sofia/gateway/remote_outbound_peer/${destination_number}"/> <action application="transfer" data="408to503"/> </condition> </extension> <!--ISDN CAU 34 --> <extension name="408to503"> <condition field="${proto_specific_hangup_cause}" expression="<a href="sip:408">sip:408"> <action application="set" data="sip_ignore_remote_cause=true"/> <action application="respond" data="503"/> <action application="hangup" data="NORMAL_CIRCUIT_CONGESTION"/> </condition> </extension> How to correctly remap causes? If there is no way to change normal behaviour, do you think could be possible also to change the source code and recompile FS accordly? Thank yo so much and sorry for this long post I hope someone could help Max
RECOVERY_ON_TIMER_EXPIRE usually means you have a NAT issue, can you clarify your signaling paths? On Wed, Sep 3, 2014 at 6:01 AM, Massimo Varriale <mvar78@gmail.com> wrote:
Hi All! This is my first question...and what question... I'm a skilled developer and I'm almost familiar with telephony in general since it's 15 years experience in telco companies. However I'm still facing a problem I couldn't find any solution yet and i hope someone could help in finding a solution
As my present company can't afford an expensive soft switch I'm using *Freeswitch 1.4* with a simple *dialplan.xml* and some scripts to load *CDRs into mysql* to send incoming calls to my remote peers. At present the live traffic is only *1 incoming IP* and *1 outgoing peer*, quite easy.
On some calls I'm getting "408 Request Timeout" and FS is giving me a RECOVERY_ON_TIMER_EXPIRE cause (IDSN 102). The problem is that as most of the switches are not able to make automatic rerouting based on this cause and so, I will like to use instead the ISDN Cause 18 (I suppose "480 Temporarily unavailable"). Is this possible?
I've used this snippet of code that use another relcause but with same concept (taken as is and pasted into the dialplan) but doesn't work as the 408 is given after 183.
<extension name="AllDestinations_Inbound"> <condition field="destination_number" expression="^"> <condition field="network_addr" expression="^154\.48\.198\.190$"/> <action application="set" data="hangup_after_bridge=true"/> <action application="set" data="continue_on_fail=19"/> <action application="bridge" data="sofia/gateway/remote_outbound_peer/${destination_number}"/> <action application="transfer" data="408to503"/> </condition> </extension> <!--ISDN CAU 34 --> <extension name="408to503"> <condition field="${proto_specific_hangup_cause}" expression="<a href=" sip:408">sip:408"> <action application="set" data="sip_ignore_remote_cause=true"/> <action application="respond" data="503"/> <action application="hangup" data="NORMAL_CIRCUIT_CONGESTION"/> </condition> </extension>
How to correctly remap causes? If there is no way to change normal behaviour, do you think could be possible also to change the source code and recompile FS accordly?
Thank yo so much and sorry for this long post I hope someone could help Max
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.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
-- *Brian West* brian@freeswitch.org *Twitter: @FreeSWITCH , @briankwest* http://www.freeswitchbook.com http://www.freeswitchcookbook.com *T:*+19184209001 | *F:*+19184209002 | *M:*+1918424WEST (9378) *iNUM:*+883 5100 1420 9001 | *ISN:*410*543 | *Skype:*briankwest
Hi Brian, thanks for answering me! Actually I'm sure (or better quite sure) it's not something related to NAT as all the end points are using plain public IP addresses. They are some dedicated servers under OVH provider and they just use IPTABLES and FS ACL for allowing communications each other (this means no hard-FW) The scenario could be easily explained like this: Inbound (Public) + My FS 1.4 (Public) + Outbound (TELES Switch with Public IP Voip Card + PSTN E1 Interconnections) And also the FS is started with option -nonat, does this affect ? Thank you so much Max 2014-09-03 14:34 GMT+02:00 Brian West <brian@freeswitch.org>:
RECOVERY_ON_TIMER_EXPIRE usually means you have a NAT issue, can you clarify your signaling paths?
On Wed, Sep 3, 2014 at 6:01 AM, Massimo Varriale <mvar78@gmail.com> wrote:
Hi All! This is my first question...and what question... I'm a skilled developer and I'm almost familiar with telephony in general since it's 15 years experience in telco companies. However I'm still facing a problem I couldn't find any solution yet and i hope someone could help in finding a solution
As my present company can't afford an expensive soft switch I'm using *Freeswitch 1.4* with a simple *dialplan.xml* and some scripts to load *CDRs into mysql* to send incoming calls to my remote peers. At present the live traffic is only *1 incoming IP* and *1 outgoing peer*, quite easy.
On some calls I'm getting "408 Request Timeout" and FS is giving me a RECOVERY_ON_TIMER_EXPIRE cause (IDSN 102). The problem is that as most of the switches are not able to make automatic rerouting based on this cause and so, I will like to use instead the ISDN Cause 18 (I suppose "480 Temporarily unavailable"). Is this possible?
I've used this snippet of code that use another relcause but with same concept (taken as is and pasted into the dialplan) but doesn't work as the 408 is given after 183.
<extension name="AllDestinations_Inbound"> <condition field="destination_number" expression="^"> <condition field="network_addr" expression="^154\.48\.198\.190$"/> <action application="set" data="hangup_after_bridge=true"/> <action application="set" data="continue_on_fail=19"/> <action application="bridge" data="sofia/gateway/remote_outbound_peer/${destination_number}"/> <action application="transfer" data="408to503"/> </condition> </extension> <!--ISDN CAU 34 --> <extension name="408to503"> <condition field="${proto_specific_hangup_cause}" expression="<a href=" sip:408">sip:408"> <action application="set" data="sip_ignore_remote_cause=true"/> <action application="respond" data="503"/> <action application="hangup" data="NORMAL_CIRCUIT_CONGESTION"/> </condition> </extension>
How to correctly remap causes? If there is no way to change normal behaviour, do you think could be possible also to change the source code and recompile FS accordly?
Thank yo so much and sorry for this long post I hope someone could help Max
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.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
--
*Brian West* brian@freeswitch.org
*Twitter: @FreeSWITCH , @briankwest* http://www.freeswitchbook.com http://www.freeswitchcookbook.com
*T:*+19184209001 | *F:*+19184209002 | *M:*+1918424WEST (9378) *iNUM:*+883 5100 1420 9001 | *ISN:*410*543 | *Skype:*briankwest
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.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
I have gotten RECOVERY_ON_TIMER_EXPIRE cause (IDSN 102) from my provider by just letting the phone ring for too long (and no answering service). Could that be the cause? Guillermo On Wed, Sep 3, 2014 at 9:44 AM, Massimo Varriale <mvar78@gmail.com> wrote:
Hi Brian, thanks for answering me! Actually I'm sure (or better quite sure) it's not something related to NAT as all the end points are using plain public IP addresses. They are some dedicated servers under OVH provider and they just use IPTABLES and FS ACL for allowing communications each other (this means no hard-FW)
The scenario could be easily explained like this: Inbound (Public) + My FS 1.4 (Public) + Outbound (TELES Switch with Public IP Voip Card + PSTN E1 Interconnections)
And also the FS is started with option -nonat, does this affect ?
Thank you so much Max
2014-09-03 14:34 GMT+02:00 Brian West <brian@freeswitch.org>:
RECOVERY_ON_TIMER_EXPIRE usually means you have a NAT issue, can you
clarify your signaling paths?
On Wed, Sep 3, 2014 at 6:01 AM, Massimo Varriale <mvar78@gmail.com> wrote:
Hi All! This is my first question...and what question... I'm a skilled developer and I'm almost familiar with telephony in general since it's 15 years experience in telco companies. However I'm still facing a problem I couldn't find any solution yet and i hope someone could help in finding a solution
As my present company can't afford an expensive soft switch I'm using *Freeswitch 1.4* with a simple *dialplan.xml* and some scripts to load *CDRs into mysql* to send incoming calls to my remote peers. At present the live traffic is only *1 incoming IP* and *1 outgoing peer*, quite easy.
On some calls I'm getting "408 Request Timeout" and FS is giving me a RECOVERY_ON_TIMER_EXPIRE cause (IDSN 102). The problem is that as most of the switches are not able to make automatic rerouting based on this cause and so, I will like to use instead the ISDN Cause 18 (I suppose "480 Temporarily unavailable"). Is this possible?
I've used this snippet of code that use another relcause but with same concept (taken as is and pasted into the dialplan) but doesn't work as the 408 is given after 183.
<extension name="AllDestinations_Inbound"> <condition field="destination_number" expression="^"> <condition field="network_addr" expression="^154\.48\.198\.190$"/> <action application="set" data="hangup_after_bridge=true"/> <action application="set" data="continue_on_fail=19"/> <action application="bridge" data="sofia/gateway/remote_outbound_peer/${destination_number}"/> <action application="transfer" data="408to503"/> </condition> </extension> <!--ISDN CAU 34 --> <extension name="408to503"> <condition field="${proto_specific_hangup_cause}" expression="<a href=" sip:408">sip:408"> <action application="set" data="sip_ignore_remote_cause=true"/> <action application="respond" data="503"/> <action application="hangup" data="NORMAL_CIRCUIT_CONGESTION"/> </condition> </extension>
How to correctly remap causes? If there is no way to change normal behaviour, do you think could be possible also to change the source code and recompile FS accordly?
Thank yo so much and sorry for this long post I hope someone could help Max
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.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
--
*Brian West* brian@freeswitch.org
*Twitter: @FreeSWITCH , @briankwest* http://www.freeswitchbook.com http://www.freeswitchcookbook.com
*T:*+19184209001 | *F:*+19184209002 | *M:*+1918424WEST (9378) *iNUM:*+883 5100 1420 9001 | *ISN:*410*543 | *Skype:*briankwest
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.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
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.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
-- Guillermo Ruiz Camauer
participants (3)
-
Brian West
-
Guillermo Ruiz Camauer
-
Massimo Varriale