Solved Odd issue with Second Outbound Route

[fancyHeat]

Hey everyone,

During testing we noticed that when we simulate the primary trunk going down (simulating an outage), the call successfully goes though by failing over to the 2nd backup trunk. However immediately we get the following email: 3CX Notification: Trunk Failover or max amount of calls available for the trunk has been reached.

We simulate the outage by turning off Allow outbound calls and Allow inbound calls in the trunk options.

Is this expected behavior?

 

[YiannisH_3CX]

Hi @fancyHeat

Since a failover occurs to the second trunk then it is expected that will get a notification if that specific notification is enabled. You can get a notification even if the primary trunk is not unregistered but the call fails over to the second trunk because of an error message from the primary provider.

 

[fancyHeat]

Hi @fancyHeat

Since a failover occurs to the second trunk then it is expected that will get a notification if that specific notification is enabled. You can get a notification even if the primary trunk is not unregistered but the call fails over to the second trunk because of an error message from the primary provider.

Apologies, I misspoke in my original post. If our secondary trunk goes down we get that error whenever a successful call is placed on the primary trunk.

But you're saying that is normal as well?

 

[YiannisH_3CX]

Apologies, I misspoke in my original post. If our secondary trunk goes down we get that error whenever a successful call is placed on the primary trunk.

But you're saying that is normal as well?

We will need to look into to see if this is supposed to happen. We will let you know once we have something. Thank you for reporting

 

[YiannisH_3CX]

I just got a clarification from our dev team that this is a known issue. When any route in the outbound rule is unregistered the email notification is triggered. I cannot provide as ETA as to when this will be fixed however.