3CX Notification: Trunk Failover or max amount of calls

[David_K]

Hello

I have an installation with 2 SIP trunks

Our main SIP trunk that can handle 4 calls, let's call itTRUNK1
A backup SIP trunk that can handle 1 call, let's call it TRUNK2

All outbound rules configured with Route1 as TRUNK1 and Route2 as TRUNK2

And quite often I get the alert "3CX Notification: Trunk Failover or max amount of calls" about TRUNK2 like :

"Device 999999 dialed on (AnyLine@TRUNK2) had no available outgoing trunk(s) to call(from "Anonymous"<sip:[email protected]:5060;nf=e> to 999999)
A trunk failover occurs when the maximum amount of calls available via the trunk have been exceeded"

Of course 999999 and fqdn are replaced for privacy.

This message should NOT happen since TRUNK1 should be used, and TRUNK2 only if TRUNK1 is over it's limit or down?

But I often get this.
Like yesterday, was Sunday. We've got 1 incoming call during the whole day. And that call generated this error.
To be more precise : since Sunday, we do not pickup the call so it's forwarded to an external number. But anyway that shoud be 1 incoming + 1 outgoing calls, so 2 in total. TRUNK1 can handle that.
So why do I get this message about TRUNK2 ?

 

[YiannisH_3CX]

Hello @David_K

The first thing you should do is check the activity log after you set to verbose logging and see what triggers the failover.
Also you haven't mentioned if your trunks are IP based or auth based which have different triggers for failover.

 

[David_K]

Hello @David_K

The first thing you should do is check the activity log after you set to verbose logging and see what triggers the failover.
Also you haven't mentioned if your trunks are IP based or auth based which have different triggers for failover.

Thanks @YiannisH_3CX
The trunks are auth based

 

[YiannisH_3CX]

The trunks are auth based

Then I would look for an error message from the provider for Trunk1 or track the registration cycle to see if maybe the registration goes down at some point and then comes back.