PBXes (http://www1.pbxes.com/forum/index.php)
- English (http://www1.pbxes.com/forum/board.php?boardid=16)
-- Miscellaneous (http://www1.pbxes.com/forum/board.php?boardid=19)
--- (http://www1.pbxes.com/forum/threadid.php?threadid=1520)

www2 server not responding?

Hi there,

I'm trying to access my PBXes account this morning but when it redirects to https://www1.pbxes.com/config.php it just times out. The other PBXes sites seem to be working OK, and my phones/etc are registering OK with the SIP server - I just can't access the config interface.

Any ideas?

C

Server fail-over

Most probably the San Diego server lost connectivity, and the Premium accounts were automatically moved to the NY server.

Are you able to log in to your account through the www4 interface?

Zitat:

Most probably the San Diego server lost connectivity, and the Premium accounts were automatically moved to the NY server.

I noted that and yes I can log into the www4 server but lots of things aren't working. Some outbound routes are now not functioning, and my IVR is playing up.

Starting with the IVR, I assume that is tied into an incoming DID or several of them. When you setup the DID on your provider's side, to which URI are they sending it?

If the DID is sent to crowland@www4.pbxes.com then it probably cannot be redirected properly. Try sending it to crowland@pbxes.org and see if that makes a difference.

Also verify on which server your extensions are registered to.

For your Outbound trunks, try clicking Submit Changes once again, and if all else fails click on Submit & Start in the Personal Data section.

Zitat:

Originally posted by Diafora Starting with the IVR, I assume that is tied into an incoming DID or several of them. When you setup the DID on your provider's side, to which URI are they sending it?

The problem was that it wouldn't route to certain extensions - I solved it by deleting and re-setting up the extensions in question, and then it worked OK. A bit of a pain - but easily fixed.

Zitat:

...Also verify on which server your extensions are registered to.

Originally they were set up on www2 and when they transferred to www4 they didn't go across too well - see fix above which got them going.

Zitat:

For your Outbound trunks, try clicking Submit Changes once again, and if all else fails click on Submit & Start in the Personal Data section.

I think the 3600 timeout caused the problem here - after about an hour the trunks just started working again of their own accord - easy