Q: Scheduled 'self test call and notify if error via email' ?

[fortech]

Hi, I am wondering if this is possible, so figured I should ask. I can't see anything via search of docs / admin interface.

I've got a few small 3cx VMs running for a few small client offices locally. I'm using generally one voip provider based in Montreal Canada. Normally their stuff works smoothly / works well with 3cx.

The 'fun problem' In the last month. They had 2 x SIP Trunk servers with temporary routing/network issues. This is first I've seen them with problems like this.
Normally the problems are transitory, they deal with it pretty quickly - less than a few hours from (start of problem) to (resolution). While the primary server has issues I think they put a secondary into service and change the DNS records so that SIPSERVERNAME FQDN points to the secondary (functional) server.

What appears to be happening on the 3cx side when this happens?

- 3cx does not indicate any problem
- SIP trunks show online
- but inbound calls to the DID with this voip carrier - simply go to busy.

If I do a reboot of the 3cx VM. Or I stop and restart all services. Then things 'start working again'
If the carrier does the fall-back to the primary server - things get broken again. We need another reboot or service restart cycle.
They do send a heads-up email when they do maintenance on the servers. So possibly I just need to make a clear list for all my 3cx VMs as a reminder, and when I get one of those emails, do a cross-check and .. deal with it manually.

But it would be nice - and maybe there is? - some way for 3cx to do outbound test calls. And if the test call does not appear to succeed (ie, gets anything other than 'line is answered by the test call number IVR' - then it would send an email warn, something like "SIP TRUNK ISSUE CHECK IT OUT DEBUG TIME".

but I am not sure if this is possible / impossible /insane. Or already solved .. just hiding in plain sight somewhere.

So thought I would ask.

Many thanks!


Tim

 

[YiannisH_3CX]

Hi @fortech

I am guessing that your provider is IP based and does not have authentication. If that is the case then the trunk will always appear online in 3CX (green) as there is no way to detect that the trunk is down.
What you are looking for is keep alive messages from 3CX that "ping" the provider and let you know everything is OK. Unfortunately this is not supported by 3CX but outbound calls should not be an issue as you can add both trunks under the same outbound rule so if the first route fails (you need to wait 32 seconds as per RFC) the PBX will route the call through the second trunk.

The issue is with inbound calls as you need to correctly set up call source identification so that the PBX can identify to which trunk the call is coming to.
This article will help you understand how source identification works and this one will help you configure multiple trunks from the same provider.

Of course you can always opt for a supported provider which we have tested and pre-configured for you so you can avoid all the manual testing.