[Freeswitch-users] fail_on_single_reject ignored with LCR endpoint
Victor Chukalovskiy
victor.chukalovskiy at gmail.com
Tue Nov 26 00:54:17 MSK 2013
Hi,
I rely on fail_on_single_reject = INCOMPATIBLE_DESTINATION to make sure
calls don't fail-over to other routes. INCOMPATIBLE_DESTINATION is
returned as the first mod_lcr route. Call rejection works this way:
<action application="set"
data="fail_on_single_reject=INCOMPATIBLE_DESTINATION"/>
<action application="lcr" data="2411765512 test_profile"/>
<action application="bridge" data="${lcr_auto_route}"/>
However, when call is bridged to lcr endpoint, fail_on_single_reject is
ignored. Call gets failed-over to the second route after hitting
INCOMPATIBLE_DESTINATION:
<action application="set"
data="fail_on_single_reject=INCOMPATIBLE_DESTINATION"/>
<action application="bridge" data="lcr/test_profile/2411765512"/>
Is this a bug or something by-design???
Here is an example of LCR routes involved:
| Digit Match | Carrier | Rate | Codec | CID Regexp |
Limit | Dialstring |
| 241 | 488_REJECTION | 0.00001 | | |
ld_carriers 488_REJECTION -1 |
[lcr_carrier=488_REJECTION,lcr_rate=0.00001]error/INCOMPATIBLE_DESTINATION |
| 241 | CARRIER_1 | 0.40240 | | |
ld_carriers CARRIER_1 -1 |
[lcr_carrier=CARRIER_1,lcr_rate=0.40240]sofia/gateway/CARRIER_1_GW_1/+2411765512
|
Thank you,
Victor
Join us at ClueCon 2013 Aug 6-8, 2013
More information about the FreeSWITCH-users
mailing list