From what I understand with a simultaneous ring strategy if any ring group members have "follow-me" rules set FusionPBX will only call the first destination (unlike enterprise which will try all).
My issue is as follows, the scenario described above looks to work (using Fusion 4.4.11) however when it tries that first destination (extension 2001) it failed and I get a "LOSE_RACE" in the CLI, the ring group will then try the second follow-me destination. Below is a snippet from my freeswitch log where I made the first and second destination in the follow-me 2001. At first I get a LOSE_RACE and it hangs up but the second attempt to 2001 works. Does anybody have any idea for a fix here so that I don't need to get all ring group members to change their follow-me settings?
It doesnt matter what combination of extensions or softphone/hardware etc. Whatever extension number is listed in the second follow-me box rings and whatever is listed in the first box gets a LOSE_RACE
My issue is as follows, the scenario described above looks to work (using Fusion 4.4.11) however when it tries that first destination (extension 2001) it failed and I get a "LOSE_RACE" in the CLI, the ring group will then try the second follow-me destination. Below is a snippet from my freeswitch log where I made the first and second destination in the follow-me 2001. At first I get a LOSE_RACE and it hangs up but the second attempt to 2001 works. Does anybody have any idea for a fix here so that I don't need to get all ring group members to change their follow-me settings?
Code:
2020-04-19 19:58:39.801680 [DEBUG] switch_ivr_async.c:1614 No silence detection configured; assuming start of speech
2020-04-19 19:58:39.821676 [NOTICE] switch_ivr_originate.c:1450 Hangup sofia/internal/2001@172.16.20.10:12043 [CS_INIT] [LOSE_RACE]
2020-04-19 19:58:39.821676 [DEBUG] switch_core_state_machine.c:584 (sofia/internal/2001@172.16.20.10:12043) Running State Change CS_HANGUP (Cur 4 Tot 60)
2020-04-19 19:58:39.821676 [DEBUG] switch_core_state_machine.c:847 (sofia/internal/2001@172.16.20.10:12043) Callstate Change DOWN -> HANGUP
2020-04-19 19:58:39.821676 [DEBUG] switch_core_state_machine.c:849 (sofia/internal/2001@172.16.20.10:12043) State HANGUP
2020-04-19 19:58:39.821676 [DEBUG] mod_sofia.c:449 Channel sofia/internal/2001@172.16.20.10:12043 hanging up, cause: LOSE_RACE
2020-04-19 19:58:39.821676 [DEBUG] switch_core_state_machine.c:60 sofia/internal/2001@172.16.20.10:12043 Standard HANGUP, cause: LOSE_RACE
2020-04-19 19:58:39.821676 [DEBUG] switch_core_state_machine.c:849 (sofia/internal/2001@172.16.20.10:12043) State HANGUP going to sleep
2020-04-19 19:58:39.821676 [DEBUG] switch_core_state_machine.c:619 (sofia/internal/2001@172.16.20.10:12043) State Change CS_HANGUP -> CS_REPORTING
2020-04-19 19:58:39.821676 [DEBUG] switch_core_state_machine.c:584 (sofia/internal/2001@172.16.20.10:12043) Running State Change CS_REPORTING (Cur 4 Tot 60)
2020-04-19 19:58:39.821676 [DEBUG] switch_core_state_machine.c:935 (sofia/internal/2001@172.16.20.10:12043) State REPORTINGIt doesnt matter what combination of extensions or softphone/hardware etc. Whatever extension number is listed in the second follow-me box rings and whatever is listed in the first box gets a LOSE_RACE
Last edited: