Call Monitor / web interface issues 20.11.2015 15:52

Forum: Bugs

I have three PBXes premium accounts, two are on www2, one on www4.

For the past few days, whenever I access the Call Monitor area on my www2 accounts, the entire pbxes.com web site becomes completely unresponsive.

Currently, it seems I'm unable to access pbxes.com using any method: the computers on my network, web proxy, and my mobile device (which is using T-Mobile network). Forum still works, but pbxes.com goes nowhere.

Any ideas?
Update 9:40am EST: I'm now getting this error:

No database connection
Check AMP installation, asterisk database, or ARI main.conf

Update 9:42am EST: looks like everything is resolved now, no issues.

RE: Trunks timing out 23.07.2014 21:01

Forum: Bugs

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.

Trunks timing out 19.07.2014 01:02

Forum: Bugs

Hi,

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."

Any ideas?

Thanks!

Time Condition-based call routing 08.07.2014 21:02

Forum: Feature Requests

Hello,

From what I can see, it looks like there are only two available time conditions for inbound call routing: "Regular Hours" and "After Hours".

I'm trying to do a routing configuration like this: from 8am - 4pm, routes to a VoIP extension. From 4pm - 7pm, call routes to a call phone. All other times call routes to a voicemail box.

Is this configuration possible using the PBXes.com service?

Thanks.

Vitelity - Outgoing CID shows "Unknown" 12.11.2013 02:15

Forum: Providers

Hey guys -- not sure if this is the right place for this.

I have seven DIDs with Vitelity and am using a premium PBXes.com account to forward calls from these DIDs to mobile phones. My setup is currently very basic:

1. Trunk for Vitelity is configured w/ username/password/proxy/domain and is connecting properly.

2. Configured inbound route for one of my seven DIDs to forward to route to "Extension 701". I simply pasted my DID (10 digits) into "Trunk" for the extension.

3. Extension 701 is configured to record all calls Always (incoming and outgoing) and is set to forwaRD to my cell phone (1 + cell phone number -- in "Call Forwarding - All Calls"). Also tried putting my cell phone number in "PSTN Number" rather than "Call Forwarding - All Calls" and got the same result.

Calls are successfully delivered to my cell phone, but call ID always shows up as "Unknown". Call ID shows up in Call Monitor, which tells me that this must be a configuration problem with my PBXes.com account.

Any ideas?

Thanks!

Edit: I resolved this by toggling "sendrpid" to "yes" on my Vitelity trunk.