Running an Asterisk certified/13.13-cert1 server on CentOS 6.
Server is configured with 2 trunks. Trunk #1 is the primary SIP provider & Trunk #2 is the secondary SIP provider. Trunk #2 is only exercised when Trunk #1 goes offline.
This redundancy works for the most part & was achieved by leveraging these two options:
- Defining “qualify=yes” for trunk #1 SIP settings (this then monitors the trunk & marks it offline when unavailable for => 2s)
- Defining a trunk sequence (Trunk #1 first, Trunk #2 second) for matching outbound routes (this then rolls over to the 2nd trunk, when warranted)
That said, it seems that any “Follow Me” related call does not honor this setup. Instead, it automatically uses the 2nd trunk.
For example, if extension 123 is setup to ring an off-site # (after some amount of seconds of a non-answer), this call wrongly goes through the 2nd trunk every single time. Normal outbound calls do not do this. They honor the trunk sequence. It is only “Follow Me” related actions that do not.
Trying the forum before considering it a bug worth reporting. Appreciate any/all help! Thanks.