Voxalot / SIP Broker Support Forums - View Single Post - Yet another "call forwarding not working" thread

beaver · 05-23-2010, 09:17 PM

Have you tried eu.voxalot.com? au.voxalot.com?

I experienced different problems (member call, dial plan update, common dial-out, vm access...) recently. Each could have its own fix under a specific proxy. For example, I am with eu.voxalot.com, at least most of my dial-plan works at most time (not always). But member call not working, nor vm. I just use the *010 for member call. I noticed under proxy01.us1.voxalot.com, my vm has no problem but my dial-plan not working completely. Hence, every week recently, I switched once to proxy01.us1.voxalot.com to listen to all of my vm and cleaned them out. Then back to eu.voxalot.com for my daily dial/call. The way it is.
Sometimes, dial-plan was not working well, VSP_A and VSP_B was mixed (I really don't know why). I have to temporarily delete my betamax account to avoid mis-use by other VSPs.

05-23-2010, 09:17 PM	#2
beaver Member Join Date: Feb 2010 Location: Beaverton, USA Posts: 72 Thanks: 8 Thanked 3 Times in 3 Posts	Have you tried eu.voxalot.com? au.voxalot.com? I experienced different problems (member call, dial plan update, common dial-out, vm access...) recently. Each could have its own fix under a specific proxy. For example, I am with eu.voxalot.com, at least most of my dial-plan works at most time (not always). But member call not working, nor vm. I just use the *010 for member call. I noticed under proxy01.us1.voxalot.com, my vm has no problem but my dial-plan not working completely. Hence, every week recently, I switched once to proxy01.us1.voxalot.com to listen to all of my vm and cleaned them out. Then back to eu.voxalot.com for my daily dial/call. The way it is. Sometimes, dial-plan was not working well, VSP_A and VSP_B was mixed (I really don't know why). I have to temporarily delete my betamax account to avoid mis-use by other VSPs.