Theme

Welcome · log in · join	food

Home

Reviews

Speed Test

	All Forums		Hot Topics		Gallery

Search similar:

Forums → VOIP etc → VOIP →

VOIP Tech Chat → VoipMS

uniqs
785

« [General] I though GOOGLE VOICE was going down • Echo on conference call when using VOIP on voip.ms »

VexorgTR join:2012-08-27 Sheffield Lake, OH	VexorgTR Member 2014-Jul-1 11:36 am VoipMS Chicago4 is down.... as of 11:30 EST.
	actions · 2014-Jul-1 11:36 am ·
Mango Use DMZ and you get a kick in the dick. Premium Member join:2008-12-25 www.toao.net	Mango Premium Member 2014-Jul-1 11:38 am No, it's not.
	actions · 2014-Jul-1 11:38 am ·
mbellaire join:2007-12-16 Canton, MI	mbellaire to VexorgTR Member 2014-Jul-1 1:20 pm to VexorgTR I had to change from Chicago to New York yesterday evening. I assumed it was a routing problem (I'm in the Detroit area).
	actions · 2014-Jul-1 1:20 pm ·
mackey Premium Member join:2007-08-20	mackey to VexorgTR Premium Member 2014-Jul-1 2:01 pm to VexorgTR Don't know about Chicago, but L.A. was experiencing significant packet loss about that time. Portal lists it as fixed an hour later. Calls sucked during that time >_> /M
	actions · 2014-Jul-1 2:01 pm ·
crazyk4952 Premium Member join:2002-02-04 united state	crazyk4952 to VexorgTR Premium Member 2014-Jul-1 2:08 pm to VexorgTR I'm currently having trouble with the Seattle server.
	actions · 2014-Jul-1 2:08 pm ·
VexorgTR join:2012-08-27 Sheffield Lake, OH	VexorgTR Member 2014-Jul-1 2:55 pm Routing, whatever.... My client called about it... switched for CHI4 to CHI2, worked... for 2-4 hours... then flopped again. Trying Atlanta now... This is baloney either way for his Biz.
	actions · 2014-Jul-1 2:55 pm ·
Mango Use DMZ and you get a kick in the dick. Premium Member join:2008-12-25 www.toao.net	Mango Premium Member 2014-Jul-1 3:01 pm What troubleshooting did you do while the problem was happening and can you post the results?
	actions · 2014-Jul-1 3:01 pm ·
VexorgTR join:2012-08-27 Sheffield Lake, OH	VexorgTR Member 2014-Jul-1 3:37 pm 01-Jul-2014 14:45:13.702 Registration attempt for Lc:10001(@VoipMsMaint[]) is scheduled in 40 sec. 01-Jul-2014 14:45:06.063 Registration attempt for Lc:10000(@voip.ms[]) is scheduled in 20 sec. 01-Jul-2014 14:44:58.276 Registration attempt for Lc:10003(@VoipMsLandlord[]) is scheduled in 20 sec. 01-Jul-2014 14:44:47.881 Registration attempt for Lc:10004(@VoipMSJoeS[]) is scheduled in 20 sec. 01-Jul-2014 14:44:33.897 [CM504003]: Sent registration request for Lc:10000(@voip.ms[]) 01-Jul-2014 14:44:31.376 Registration attempt for Lc:10002(@VoipMS lease[]) is scheduled in 20 sec. 01-Jul-2014 14:44:26.061 [CM504003]: Sent registration request for Lc:10003(@VoipMsLandlord[]) 01-Jul-2014 14:44:21.438 Registration attempt for Lc:10001(@VoipMsMaint[]) is scheduled in 20 sec. 01-Jul-2014 14:44:15.737 [CM504003]: Sent registration request for Lc:10004(@VoipMSJoeS[]) 01-Jul-2014 14:43:59.311 [CM504003]: Sent registration request for Lc:10002(@VoipMS lease[]) 01-Jul-2014 14:43:49.368 [CM504003]: Sent registration request for Lc:10001(@VoipMsMaint[]) 01-Jul-2014 14:42:33.866 [CM504007]: Next attempt to register Lc:10000(@voip.ms[]) is scheduled in 120 seconds 01-Jul-2014 14:42:33.863 [CM504005]: Registration failed for: Lc:10000(@voip.ms[]); Cause: Cause: 408 Request Timeout/REGISTER from local 01-Jul-2014 14:42:26.025 [CM504007]: Next attempt to register Lc:10003(@VoipMsLandlord[]) is scheduled in 120 seconds 01-Jul-2014 14:42:26.022 [CM504005]: Registration failed for: Lc:10003(@VoipMsLandlord[]); Cause: Cause: 408 Request Timeout/REGISTER from local 01-Jul-2014 14:42:15.713 [CM504007]: Next attempt to register Lc:10004(@VoipMSJoeS[]) is scheduled in 120 seconds 01-Jul-2014 14:42:15.709 [CM504005]: Registration failed for: Lc:10004(@VoipMSJoeS[]); Cause: Cause: 408 Request Timeout/REGISTER from local 01-Jul-2014 14:41:59.284 [CM504007]: Next attempt to register Lc:10002(@VoipMS lease[]) is scheduled in 120 seconds 01-Jul-2014 14:41:59.281 [CM504005]: Registration failed for: Lc:10002(@VoipMS lease[]); Cause: Cause: 408 Request Timeout/REGISTER from local 01-Jul-2014 14:41:49.353 [CM504007]: Next attempt to register Lc:10001(@VoipMsMaint[]) is scheduled in 120 seconds 01-Jul-2014 14:41:49.348 [CM504005]: Registration failed for: Lc:10001(@VoipMsMaint[]); Cause: Cause: 408 Request Timeout/REGISTER from local 01-Jul-2014 14:41:21.696 Registration attempt for Lc:10000(@voip.ms[]) is scheduled in 40 sec. 01-Jul-2014 14:41:13.816 Registration attempt for Lc:10003(@VoipMsLandlord[]) is scheduled in 40 sec. 01-Jul-2014 14:41:03.471 Registration attempt for Lc:10004(@VoipMSJoeS[]) is scheduled in 40 sec. 01-Jul-2014 14:40:47.000 Registration attempt for Lc:10002(@VoipMS lease[]) is scheduled in 40 sec. 01-Jul-2014 14:40:37.061 Registration attempt for Lc:10001(@VoipMsMaint[]) is scheduled in 40 sec. 01-Jul-2014 14:40:29.389 Registration attempt for Lc:10000(@voip.ms[]) is scheduled in 20 sec. 01-Jul-2014 14:40:21.574 Registration attempt for Lc:10003(@VoipMsLandlord[]) is scheduled in 20 sec. 01-Jul-2014 14:40:11.232 Registration attempt for Lc:10004(@VoipMSJoeS[]) is scheduled in 20 sec. 01-Jul-2014 14:39:57.219 [CM504003]: Sent registration request for Lc:10000(@voip.ms[]) 01-Jul-2014 14:39:54.719 Registration attempt for Lc:10002(@VoipMS lease[]) is scheduled in 20 sec. 01-Jul-2014 14:39:49.425 [CM504003]: Sent registration request for Lc:10003(@VoipMsLandlord[]) 01-Jul-2014 14:39:44.881 Registration attempt for Lc:10001(@VoipMsMaint[]) is scheduled in 20 sec. 01-Jul-2014 14:39:39.101 [CM504003]: Sent registration request for Lc:10004(@VoipMSJoeS[]) 01-Jul-2014 14:39:22.593 [CM504003]: Sent registration request for Lc:10002(@VoipMS lease[]) 01-Jul-2014 14:39:12.736 [CM504003]: Sent registration request for Lc:10001(@VoipMsMaint[])
	actions · 2014-Jul-1 3:37 pm ·
VexorgTR	VexorgTR Member 2014-Jul-1 3:53 pm This happened first at about noon with Chicago4.... then again 2 hours later with Chicago2...... Whatever it is, it sucks. It's my customer's network/system, so I am looking for the fastest way to get their phones on... I put them on another city's POP... working for the last 2 hours. Could be a router somewhere, could be anything... Our offices have the Same ISP.. My Voip system is linked to CallCentric... and that hasn't glitched today.... It's just annoying me since it's NOT the 3CX system's fault that it's not registering.
	actions · 2014-Jul-1 3:53 pm ·
iamhere join:2013-01-26 canada	iamhere Member 2014-Jul-1 4:04 pm Traceroutes and MTR to the servers from the client location would be very useful.
	actions · 2014-Jul-1 4:04 pm ·
OzarkEdge join:2014-02-23 USA 1 edit	OzarkEdge to VexorgTR Member 2014-Jul-1 7:32 pm to VexorgTR Re: NOT VoIP.ms? said by VexorgTR: This happened first at about noon with Chicago4.... then again 2 hours later with Chicago2...... Whatever it is, it sucks. It's my customer's network/system, so I am looking for the fastest way to get their phones on... I put them on another city's POP... working for the last 2 hours. Could be a router somewhere, could be anything... Our offices have the Same ISP.. My Voip system is linked to CallCentric... and that hasn't glitched today.... It's just annoying me since it's NOT the 3CX system's fault that it's not registering. Chicago was hit by severe straight-line storms yesterday, a Derecho, with peak winds of 85 mph. Lots of upheaval... perhaps some VoIP links came undone. Edit: I don't see any related trouble reported on the VoIP.ms website. So maybe the issue is not with VoIP.ms. OE
	actions · 2014-Jul-1 7:32 pm ·
Mango Use DMZ and you get a kick in the dick. Premium Member join:2008-12-25 www.toao.net 1 recommendation	Mango to VexorgTR Premium Member 2014-Jul-1 8:43 pm to VexorgTR Re: VoipMS That's not troubleshooting. That's a copy/paste of a log file that says little more than "it ain't". Did the VoIP.ms PoP respond to ping? If not, what did a traceroute look like? If so, was there any packet loss? If not, did you shut down 3CX for longer than the router's UDP timeout to allow old connections time to expire? Did you use Wireshark to inspect the SIP traffic between your PBX and the VoIP.ms PoP? Did you try to use a different machine on the same LAN, connected directly to VoIP.ms? Did you do anything at all other than switching PoPs, the one thing that will make it near-impossible to diagnose the problem until it inevitably happens again? Also, why do you have so many registrations? You only need one per PoP. m.
	actions · 2014-Jul-1 8:43 pm ·

VoIP2Go join:2013-12-14	VoIP2Go to VexorgTR Member 2014-Jul-1 10:07 pm to VexorgTR As a temporary solution, I have a spare domain name setup with DNS SRV failover for some voip.ms servers that you are welcome to use. The domain voip2go.asia is for some future plans and it is temporarily setup to failover in the following priority: 1. chicago3.voip.ms 2. newyork2.voip.ms 3. houston.voip.ms 4. denver.voip.ms I know the server order will not suit everyone so that's why I chose the most reliable server as the number 1 priority.
	actions · 2014-Jul-1 10:07 pm ·
VexorgTR join:2012-08-27 Sheffield Lake, OH	VexorgTR to Mango Member 2014-Jul-1 11:23 pm to Mango I'd have to go on-site to do any real digging.... It's been flakey all around for them... in many ways.
	actions · 2014-Jul-1 11:23 pm ·

Forums → VOIP etc → VOIP → VOIP Tech Chat	« [General] I though GOOGLE VOICE was going down • Echo on conference call when using VOIP on voip.ms »

VOIP Tech Chat → VoipMS

VoipMS

Re: NOT VoIP.ms?

Re: VoipMS