Jira FS-6008 opened for this. $200 bounty to fix it in 1.2.stable On 13-11-26 12:37 PM, Victor Chukalovskiy wrote:
Hi, I wonder if Anthony or Rupa can have a quick look here. Else, I assume it's a bug and go ahead with Jira
On 13-11-25 04:54 PM, Victor Chukalovskiy wrote:
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