I have three PBXes.com accounts -- two on www2 and one on www4. All three accounts are experiencing intermittent trunk timeouts. I am trying to determine the cause as this is resulting in occasional dropped calls.
Here are two examples from your system log today:
Jul 18 12:43:07 NOTICE[100255] chan_sip.c: -- Registration for 'aura_2@Vitelity' timed out, trying again (Attempt #1)
Jul 18 14:32:02 NOTICE[100255] chan_sip.c: -- Registration for 'aura_2@Vitelity' timed out, trying again (Attempt #1)
All three of these accounts use Vitelity for VoIP origination and termination. I submitted a ticket to Vitelity and they said: "The trunk configuration looks good from what I can tell. Typical registration does involve re-registering, but this is done on an hourly interval. It sounds like the cloud hosting service may be doing some quick maintenance at the times it loses registration."
Occasional timeouts on trunk re-registration to Vitelity are less on your account on www4. Therefore I recommend putting your three accounts to www4 as the connection to Vitelity seems to be better from there.
I took your advice and migrated the two PBXes.com accounts on your Seattle data center to your New York data center. This morning all calls failed until I noticed what was happening and switched the PBXes back to your Seattle data center.
Switching data centers resets the system log -- I didn't have a chance to thoroughly troubleshoot what was going on because this was an emergency. I didn't think to check Status area last night but I assume that the PBXes never reconnected to Vitelity trunk after switching data centers.
Any ideas? I've been very happy with your service for nearly a year but need to make sure connection remains stable.
We checked both accounts. For wearegs... the server move succeeded while for aural... it didn't. When trying to do this again, please make a testcall, look into the Status Display, or the System Log once to see that server move actually worked.
