I'm having an issue where originate_timeout doesn't seem to be working as I think it would. I am using lcr to get the gateways. I can bridge to either gateway1 or 2 just fine. Then I set it up with bridge using both gateways for failover and it worked fine. I decided to change gateway1 to a fake IP to test failover and it works, but it takes 30 seconds to timeout. I then found originate_timeout and set it to 4 seconds, but it doesn't timeout. It still takes 30 seconds. Here is the snippet from my dialplan: <action application="set" data="originate_timeout=4"/> <action application="bridge" data="${lcr_route_1}|${lcr_route_2}"/> Here is the debug that shows it is being set: EXECUTE sofia/internal/1111@192.168.1.108 set(originate_timeout=4) 2010-04-28 16:06:28.265187 [DEBUG] mod_dptools.c:818 sofia/internal/1111@192.168.1.108 SET [originate_timeout]=[4] EXECUTE sofia/internal/1111@192.168.1.108 bridge([lcr_carrier=tex,lcr_rate=0.01900]sofia/gateway/Tex/5551212|[lcr_carr ier=tel,lcr_rate=0.03000]sofia/gateway/Tel/5551212) Then I get this: 2010-04-28 16:07:00.273156 [NOTICE] sofia.c:4547 Hangup sofia/external/5551212 [CS_CONSUME_MEDIA] [RECOVERY_ON_TIMER_EXPIRE] And it successfully goes out gateway2, but it is 30 seconds later, not 4 as I would guess. Am I using the timeout wrong? Or is there some other setting I need instead?
Is it failing because gateway1 is not responding at all? If so then I'd say you'd need to use leg_timeout or leg_media_timeout on each leg as needed: <action application="bridge" data="[leg_timeout=4]${lcr_route_1}|[leg_timeout=6]${lcr_route_2}"/> Check these variables: http://wiki.freeswitch.org/wiki/Channel_Variables#leg_timeout Test it out and let us know. -MC On Wed, Apr 28, 2010 at 2:17 PM, Peder <peder@networkoblivion.com> wrote:
I'm having an issue where originate_timeout doesn't seem to be working as I think it would. I am using lcr to get the gateways. I can bridge to either gateway1 or 2 just fine. Then I set it up with bridge using both gateways for failover and it worked fine. I decided to change gateway1 to a fake IP to test failover and it works, but it takes 30 seconds to timeout. I then found originate_timeout and set it to 4 seconds, but it doesn't timeout. It still takes 30 seconds.
Here is the snippet from my dialplan:
<action application="set" data="originate_timeout=4"/> <action application="bridge" data="${lcr_route_1}|${lcr_route_2}"/>
Here is the debug that shows it is being set:
EXECUTE sofia/internal/1111@192.168.1.108 set(originate_timeout=4) 2010-04-28 16:06:28.265187 [DEBUG] mod_dptools.c:818 sofia/internal/1111@192.168.1.108 SET [originate_timeout]=[4] EXECUTE sofia/internal/1111@192.168.1.108
bridge([lcr_carrier=tex,lcr_rate=0.01900]sofia/gateway/Tex/5551212|[lcr_carr ier=tel,lcr_rate=0.03000]sofia/gateway/Tel/5551212)
Then I get this: 2010-04-28 16:07:00.273156 [NOTICE] sofia.c:4547 Hangup sofia/external/5551212 [CS_CONSUME_MEDIA] [RECOVERY_ON_TIMER_EXPIRE]
And it successfully goes out gateway2, but it is 30 seconds later, not 4 as I would guess. Am I using the timeout wrong? Or is there some other setting I need instead?
_______________________________________________ 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
MSC, I think you mean leg_progress_timeout instead of leg_media_timeout, right? And actually, this is one good question. What is the difference between leg_timeout and leg_progress_timeout? leg_timeout if till call completes and leg_progress_timeout is only til 180/183? Is that the correct understanding? JM On Wed, Apr 28, 2010 at 9:00 PM, Michael Collins <msc@freeswitch.org> wrote:
Is it failing because gateway1 is not responding at all? If so then I'd say you'd need to use leg_timeout or leg_media_timeout on each leg as needed:
<action application="bridge" data="[leg_timeout=4]${lcr_route_1}|[leg_timeout=6]${lcr_route_2}"/>
Check these variables: http://wiki.freeswitch.org/wiki/Channel_Variables#leg_timeout
Test it out and let us know. -MC
On Wed, Apr 28, 2010 at 2:17 PM, Peder <peder@networkoblivion.com> wrote:
I'm having an issue where originate_timeout doesn't seem to be working as I think it would. I am using lcr to get the gateways. I can bridge to either gateway1 or 2 just fine. Then I set it up with bridge using both gateways for failover and it worked fine. I decided to change gateway1 to a fake IP to test failover and it works, but it takes 30 seconds to timeout. I then found originate_timeout and set it to 4 seconds, but it doesn't timeout. It still takes 30 seconds.
Here is the snippet from my dialplan:
<action application="set" data="originate_timeout=4"/> <action application="bridge" data="${lcr_route_1}|${lcr_route_2}"/>
Here is the debug that shows it is being set:
EXECUTE sofia/internal/1111@192.168.1.108 set(originate_timeout=4) 2010-04-28 16:06:28.265187 [DEBUG] mod_dptools.c:818 sofia/internal/1111@192.168.1.108 SET [originate_timeout]=[4] EXECUTE sofia/internal/1111@192.168.1.108
bridge([lcr_carrier=tex,lcr_rate=0.01900]sofia/gateway/Tex/5551212|[lcr_carr ier=tel,lcr_rate=0.03000]sofia/gateway/Tel/5551212)
Then I get this: 2010-04-28 16:07:00.273156 [NOTICE] sofia.c:4547 Hangup sofia/external/5551212 [CS_CONSUME_MEDIA] [RECOVERY_ON_TIMER_EXPIRE]
And it successfully goes out gateway2, but it is 30 seconds later, not 4 as I would guess. Am I using the timeout wrong? Or is there some other setting I need instead?
_______________________________________________ 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
_______________________________________________ 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
Didn't like that at all. Here is what I have in dialplan: <action application="bridge" data="[leg_timeout=4]${lcr_route_1}|[leg_timeout=6]${lcr_route_2}"/> Here is debug: EXECUTE sofia/internal/1111@192.168.1.108 bridge([leg_timeout=4][lcr_carrier=tex,lcr_rate=0.01900]sofia/gateway/Tex/55 51212|[leg_timeout=6][lcr_carrier=tel,lcr_rate=0.03000]sofia/gateway/Tel/555 1212) 2010-04-29 15:40:12.370181 [ERR] switch_core_session.c:360 Could not locate channel type [lcr_carrier=tex|lcr_rate=0.01900]sofia 2010-04-29 15:40:12.370181 [ERR] switch_ivr_originate.c:2480 Cannot create outgoing channel of type [[lcr_carrier=tex|lcr_rate=0.01900]sofia] cause: [CHAN_NOT_IMPLEMENTED] 2010-04-29 15:40:12.370181 [DEBUG] switch_ivr_originate.c:3299 Originate Resulted in Error Cause: 66 [CHAN_NOT_IMPLEMENTED] 2010-04-29 15:40:12.370181 [ERR] switch_core_session.c:360 Could not locate channel type [lcr_carrier=tel|lcr_rate=0.03000]sofia 2010-04-29 15:40:12.370181 [ERR] switch_ivr_originate.c:2480 Cannot create outgoing channel of type [[lcr_carrier=tel|lcr_rate=0.03000]sofia] cause: [CHAN_NOT_IMPLEMENTED] Since ${lcr_route_1} already contains variables in [], it appears that the extra set in the beginning may be causing an issue. Note that it is chopping off the dialstring after sofia (should be sofia/gateway/Tex/5551212 and just shows as sofia) and the "leg_timeout" appears to disappear too. If I remove the leg timeouts, I do see it bridge "sofia/external/5551212". Any other ideas? From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Michael Collins Sent: Wednesday, April 28, 2010 7:00 PM To: freeswitch-users@lists.freeswitch.org Subject: Re: [Freeswitch-users] Dial Timeout Issue Is it failing because gateway1 is not responding at all? If so then I'd say you'd need to use leg_timeout or leg_media_timeout on each leg as needed: <action application="bridge" data="[leg_timeout=4]${lcr_route_1}|[leg_timeout=6]${lcr_route_2}"/> Check these variables: http://wiki.freeswitch.org/wiki/Channel_Variables#leg_timeout Test it out and let us know. -MC On Wed, Apr 28, 2010 at 2:17 PM, Peder <peder@networkoblivion.com> wrote: I'm having an issue where originate_timeout doesn't seem to be working as I think it would. I am using lcr to get the gateways. I can bridge to either gateway1 or 2 just fine. Then I set it up with bridge using both gateways for failover and it worked fine. I decided to change gateway1 to a fake IP to test failover and it works, but it takes 30 seconds to timeout. I then found originate_timeout and set it to 4 seconds, but it doesn't timeout. It still takes 30 seconds. Here is the snippet from my dialplan: <action application="set" data="originate_timeout=4"/> <action application="bridge" data="${lcr_route_1}|${lcr_route_2}"/> Here is the debug that shows it is being set: EXECUTE sofia/internal/1111@192.168.1.108 set(originate_timeout=4) 2010-04-28 16:06:28.265187 [DEBUG] mod_dptools.c:818 sofia/internal/1111@192.168.1.108 SET [originate_timeout]=[4] EXECUTE sofia/internal/1111@192.168.1.108 bridge([lcr_carrier=tex,lcr_rate=0.01900]sofia/gateway/Tex/5551212|[lcr_carr ier=tel,lcr_rate=0.03000]sofia/gateway/Tel/5551212) Then I get this: 2010-04-28 16:07:00.273156 [NOTICE] sofia.c:4547 Hangup sofia/external/5551212 [CS_CONSUME_MEDIA] [RECOVERY_ON_TIMER_EXPIRE] And it successfully goes out gateway2, but it is 30 seconds later, not 4 as I would guess. Am I using the timeout wrong? Or is there some other setting I need instead? _______________________________________________ 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
You won't be able to do it that way. lcr is already using the [] and you can't get two for each leg. So, either use the same timeout for all legs using {leg_timeout=5} or you can push me to get the new mod_lcr in which lets you put arbitrary key/value pairs in their populated from your custom_sql. Unfortunately I'm travelling next week so I don't see doing something sooner than that... On Thu, Apr 29, 2010 at 10:50 AM, Peder <peder@networkoblivion.com> wrote:
Didn’t like that at all. Here is what I have in dialplan:
<action application="bridge" data="[leg_timeout=4]${lcr_route_1}|[leg_timeout=6]${lcr_route_2}"/>
Here is debug:
EXECUTE sofia/internal/1111@192.168.1.108bridge([leg_timeout=4][lcr_carrier=tex,lcr_rate=0.01900]sofia/gateway/Tex/5551212|[leg_timeout=6][lcr_carrier=tel,lcr_rate=0.03000]sofia/gateway/Tel/5551212)
2010-04-29 15:40:12.370181 [ERR] switch_core_session.c:360 Could not locate channel type [lcr_carrier=tex|lcr_rate=0.01900]sofia
2010-04-29 15:40:12.370181 [ERR] switch_ivr_originate.c:2480 Cannot create outgoing channel of type [[lcr_carrier=tex|lcr_rate=0.01900]sofia] cause: [CHAN_NOT_IMPLEMENTED]
2010-04-29 15:40:12.370181 [DEBUG] switch_ivr_originate.c:3299 Originate Resulted in Error Cause: 66 [CHAN_NOT_IMPLEMENTED]
2010-04-29 15:40:12.370181 [ERR] switch_core_session.c:360 Could not locate channel type [lcr_carrier=tel|lcr_rate=0.03000]sofia
2010-04-29 15:40:12.370181 [ERR] switch_ivr_originate.c:2480 Cannot create outgoing channel of type [[lcr_carrier=tel|lcr_rate=0.03000]sofia] cause: [CHAN_NOT_IMPLEMENTED]
Since ${lcr_route_1} already contains variables in [], it appears that the extra set in the beginning may be causing an issue. Note that it is chopping off the dialstring after sofia (should be sofia/gateway/Tex/5551212 and just shows as sofia) and the “leg_timeout” appears to disappear too. If I remove the leg timeouts, I do see it bridge “sofia/external/5551212”. Any other ideas?
*From:* freeswitch-users-bounces@lists.freeswitch.org [mailto: freeswitch-users-bounces@lists.freeswitch.org] *On Behalf Of *Michael Collins *Sent:* Wednesday, April 28, 2010 7:00 PM *To:* freeswitch-users@lists.freeswitch.org *Subject:* Re: [Freeswitch-users] Dial Timeout Issue
Is it failing because gateway1 is not responding at all? If so then I'd say you'd need to use leg_timeout or leg_media_timeout on each leg as needed:
<action application="bridge" data="[leg_timeout=4]${lcr_route_1}|[leg_timeout=6]${lcr_route_2}"/>
Check these variables: http://wiki.freeswitch.org/wiki/Channel_Variables#leg_timeout
Test it out and let us know. -MC
On Wed, Apr 28, 2010 at 2:17 PM, Peder <peder@networkoblivion.com> wrote:
I'm having an issue where originate_timeout doesn't seem to be working as I think it would. I am using lcr to get the gateways. I can bridge to either gateway1 or 2 just fine. Then I set it up with bridge using both gateways for failover and it worked fine. I decided to change gateway1 to a fake IP to test failover and it works, but it takes 30 seconds to timeout. I then found originate_timeout and set it to 4 seconds, but it doesn't timeout. It still takes 30 seconds.
Here is the snippet from my dialplan:
<action application="set" data="originate_timeout=4"/> <action application="bridge" data="${lcr_route_1}|${lcr_route_2}"/>
Here is the debug that shows it is being set:
EXECUTE sofia/internal/1111@192.168.1.108 set(originate_timeout=4) 2010-04-28 16:06:28.265187 [DEBUG] mod_dptools.c:818 sofia/internal/1111@192.168.1.108 SET [originate_timeout]=[4] EXECUTE sofia/internal/1111@192.168.1.108
bridge([lcr_carrier=tex,lcr_rate=0.01900]sofia/gateway/Tex/5551212|[lcr_carr ier=tel,lcr_rate=0.03000]sofia/gateway/Tel/5551212)
Then I get this: 2010-04-28 16:07:00.273156 [NOTICE] sofia.c:4547 Hangup sofia/external/5551212 [CS_CONSUME_MEDIA] [RECOVERY_ON_TIMER_EXPIRE]
And it successfully goes out gateway2, but it is 30 seconds later, not 4 as I would guess. Am I using the timeout wrong? Or is there some other setting I need instead?
_______________________________________________ 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
_______________________________________________ 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
-- -Rupa
That works, thanks. Anybody have any idea why this doesn't accomplish the same thing: <action application="set" data="originate_timeout=4"/> From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Rupa Schomaker Sent: Thursday, April 29, 2010 1:37 PM To: freeswitch-users Subject: Re: [Freeswitch-users] Dial Timeout Issue You won't be able to do it that way. lcr is already using the [] and you can't get two for each leg. So, either use the same timeout for all legs using {leg_timeout=5} or you can push me to get the new mod_lcr in which lets you put arbitrary key/value pairs in their populated from your custom_sql. Unfortunately I'm travelling next week so I don't see doing something sooner than that... On Thu, Apr 29, 2010 at 10:50 AM, Peder <peder@networkoblivion.com> wrote: Didn't like that at all. Here is what I have in dialplan: <action application="bridge" data="[leg_timeout=4]${lcr_route_1}|[leg_timeout=6]${lcr_route_2}"/> Here is debug: EXECUTE sofia/internal/1111@192.168.1.108 bridge([leg_timeout=4][lcr_carrier=tex,lcr_rate=0.01900]sofia/gateway/Tex/55 51212|[leg_timeout=6][lcr_carrier=tel,lcr_rate=0.03000]sofia/gateway/Tel/555 1212) 2010-04-29 15:40:12.370181 [ERR] switch_core_session.c:360 Could not locate channel type [lcr_carrier=tex|lcr_rate=0.01900]sofia 2010-04-29 15:40:12.370181 [ERR] switch_ivr_originate.c:2480 Cannot create outgoing channel of type [[lcr_carrier=tex|lcr_rate=0.01900]sofia] cause: [CHAN_NOT_IMPLEMENTED] 2010-04-29 15:40:12.370181 [DEBUG] switch_ivr_originate.c:3299 Originate Resulted in Error Cause: 66 [CHAN_NOT_IMPLEMENTED] 2010-04-29 15:40:12.370181 [ERR] switch_core_session.c:360 Could not locate channel type [lcr_carrier=tel|lcr_rate=0.03000]sofia 2010-04-29 15:40:12.370181 [ERR] switch_ivr_originate.c:2480 Cannot create outgoing channel of type [[lcr_carrier=tel|lcr_rate=0.03000]sofia] cause: [CHAN_NOT_IMPLEMENTED] Since ${lcr_route_1} already contains variables in [], it appears that the extra set in the beginning may be causing an issue. Note that it is chopping off the dialstring after sofia (should be sofia/gateway/Tex/5551212 and just shows as sofia) and the "leg_timeout" appears to disappear too. If I remove the leg timeouts, I do see it bridge "sofia/external/5551212". Any other ideas? From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Michael Collins Sent: Wednesday, April 28, 2010 7:00 PM To: freeswitch-users@lists.freeswitch.org Subject: Re: [Freeswitch-users] Dial Timeout Issue Is it failing because gateway1 is not responding at all? If so then I'd say you'd need to use leg_timeout or leg_media_timeout on each leg as needed: <action application="bridge" data="[leg_timeout=4]${lcr_route_1}|[leg_timeout=6]${lcr_route_2}"/> Check these variables: http://wiki.freeswitch.org/wiki/Channel_Variables#leg_timeout Test it out and let us know. -MC On Wed, Apr 28, 2010 at 2:17 PM, Peder <peder@networkoblivion.com> wrote: I'm having an issue where originate_timeout doesn't seem to be working as I think it would. I am using lcr to get the gateways. I can bridge to either gateway1 or 2 just fine. Then I set it up with bridge using both gateways for failover and it worked fine. I decided to change gateway1 to a fake IP to test failover and it works, but it takes 30 seconds to timeout. I then found originate_timeout and set it to 4 seconds, but it doesn't timeout. It still takes 30 seconds. Here is the snippet from my dialplan: <action application="set" data="originate_timeout=4"/> <action application="bridge" data="${lcr_route_1}|${lcr_route_2}"/> Here is the debug that shows it is being set: EXECUTE sofia/internal/1111@192.168.1.108 set(originate_timeout=4) 2010-04-28 16:06:28.265187 [DEBUG] mod_dptools.c:818 sofia/internal/1111@192.168.1.108 SET [originate_timeout]=[4] EXECUTE sofia/internal/1111@192.168.1.108 bridge([lcr_carrier=tex,lcr_rate=0.01900]sofia/gateway/Tex/5551212|[lcr_carr ier=tel,lcr_rate=0.03000]sofia/gateway/Tel/5551212) Then I get this: 2010-04-28 16:07:00.273156 [NOTICE] sofia.c:4547 Hangup sofia/external/5551212 [CS_CONSUME_MEDIA] [RECOVERY_ON_TIMER_EXPIRE] And it successfully goes out gateway2, but it is 30 seconds later, not 4 as I would guess. Am I using the timeout wrong? Or is there some other setting I need instead? _______________________________________________ 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 _______________________________________________ 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 -- -Rupa
participants (4)
-
João Mesquita
-
Michael Collins
-
Peder
-
Rupa Schomaker