voip.ms discussion

[dheian]

Got home after a few days away...red light flashing on our Vista 350. After checking the messages waiting for us, we hung up and the light kept flashing.

I know it sometimes takes a while after hanging up for the light to stop flashing, but we're talking about 20 minutes here.

Phone's attached to a PAP2T.

[FunkyTown]

I've had this happen before even with Bell. I'm not sure what causes it - I'm guessing a piece of the notify gets garbled and the phone cannot obtain the off signal.

If it happens a lot, check the cord on your phone to ensure it's not shorting out. Wiggle it while talking and listen for static. The MWI off notification is a very short burst of data. So even a millisecond missing will cause the light to stay on.

[dheian]

Thanks Funkytown. Ended up leaving myself a message and erasing it. This time it caught the signal and stopped.

[gzink]

Don't need an answer...just to vent. I use this service once a week maybe. Every time lately it disappoints me. Right now it is dialing and not going anywhere. I have reset and I'm using the Seattle server because that is the best ping.
What a joke..is how I feel about this piece * *

I would like to get rid of pots but cannot argue to do this based on latest experience.

[Mango]

If you would like to troubleshoot your equipment, please let us know and we would be delighted to help you.

[FunkyTown]

Sorry to read that gzink. Is this happening all of the time? I have not had this happen lately, and the friends I have who use VoIP.ms haven't had this happen a lot. Two weeks ago there was a friend of mine who had trouble calling her mom in Halifax. It never connected and she tried about 10 times. Are you calling the Halifax region?

If this is happening to you often it could be a configuration issue on your end.

[gzink]

Just calling down the road in Kamloops BC. I reset again and it is up. I just had to vent a bit. The service is still acceptable for cheap calls on the road and at home when it works. I just expect electronics to work these days.
It just doesn't strike me as ready to replace the old pots.
I had thought it would. Not a big saving for me if it did anyway due to "bundling", so no big deal.

[Mango]

Sometimes VoIP isn't acceptable as a POTS replacement due to various factors (power outages, internet outages, etc,) but it should be more reliable than you're experiencing. I checked my logs and Seattle had no issues today.

By any chance do you have a Tomato router?

[FunkyTown]

I was speaking with my friend earlier who runs a business using VoIP.ms for their phone service. They have had some problems, but today there was absolutely no downtime. They are connected to the Montreal2 server. They have a very high call volume, so usually when there's an issue they experience it.

[gzink]

DLink dir 615 standard router....telus dsl 5MB. Also have a trendnet router on the network. A couple of laptops on the network and a wired desktop. Very little internet traffic, except for my use.
No custom firmware or anything like that. Windows 7 ultimate(free from MS). Windows 7 Home Premium. 32 bit OS

[Mango]

Okay, try the following with the router's configuration:
Setup >> Network Settings >> Remove the tick in Enable DNS Relay
Tools >> Log Settings >> Remove the tick in Attacks
In some versions of the router, this last one has been moved to Status >> Logs

You will need to remove the power to the router, wait 15 seconds, and power on the router for at least the first one to take effect.

This is to get around two bugs in some models of D-Link routers that 1) stop responding to DNS requests and 2) incorrectly classify legitimate traffic as an attack and create too much load on the router by logging it all.

What VoIP equipment do you use? And is it double-NATted? i.e. is it daisy-chained to both routers, or just the primary router? Better if it's just connected to the primary router.

m.

[gzink]

First setting changed.
2nd nowhere to be found.
Linksys PAP2T

I did notice that the IP address on the network for the PAP2T was not "reserved" and was renewed every so often. Changed it to reserved.

[Mikey0124]

Hello everyone! Just wanted to say my service with Voip.ms so far if pretty good! I was experiencing some voice quality issues with sound cutting out but recently setup my QoS through my router and everything has been okay. My only problem is sometimes the callers that I am talking to can here noise in the background once and a while like someone is pushing a button on the phone or something. Or my wife said someone said it sounded like she hung up once or twice. Now this sort of stuff doesn't happen pretty often but was just wondering if there was anything that could be done to fix this problem? Maybe should I try changing servers? Right now I am using the Toronto servers but was thinking of maybe trying to change over to the Montreal ones. Other then that right now I am using the Value service. I was using premium but with the amount of time we were using the phone it was costing to much. I really wish voip.ms had an unlimited package. Anyway any suggestions would be greatly appreciated!

[FunkyTown]

Hello,

Happy New Year All!

In my syslog I'm getting a "bad event" message constantly. The phone is registering OK with VoIP.ms and everything is working well, but this seems really odd to be getting this bad event message. I looked it up and it states the receiver doesn't understand the notify message being sent. So here are the notifies:

This is what I'm sending to VoIP.ms:

01-01-2011 14:25:43 Local7.Debug 192.168.0.162
NOTIFY sip:toronto2.voip.ms SIP/2.0<013><010>Via: SIP/2.0/UDP 192.168.0.162:5062;branch=z9hG4bK-7306161c
From: "My Name" <sip:aaaaa_xxx@toronto2.voip.ms>;tag=99c4319ab1e02d32o2
To: <sip:toronto2.voip.ms>
Call-ID: 9059213a-8a770212@192.168.0.162
CSeq: 11 NOTIFY
Max-Forwards: 70
Contact: "My Name" <sip:aaaaa_xxx@192.168.0.162:5062>
Event: keep-alive
User-Agent: Cisco/SPA504G-7.4.7
Content-Length: 0


This is what they are sending back:

01-01-2011 14:25:43 Local7.Debug 192.168.0.162
SIP/2.0 489 Bad event
Via: SIP/2.0/UDP 192.168.0.162:5062;branch=z9hG4bK-7306161c;received=192.168.0.162
From: "My Name" <sip:aaaaa_xxx@toronto2.voip.ms>;tag=99c4319ab1e02d32o2
To: <sip:toronto2.voip.ms>;tag=as63be5d26
Call-ID: 9059213a-8a770212@192.168.0.162
CSeq: 11 NOTIFY
User-Agent: VoIPMS/SERAST
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Supported: replaces
Content-Length: 0

Does anyone have any insight as to why this would be happening?

Thanks.

[FunkyTown]

I think I found the answer. After another hour of searching I'm reading that this sometimes happens when NAT is enabled on some equipment. The Cisco SPA5XX phones appear to have the issue.

Thanks.