VOIP etc > Voice Over IP - VOIP > VOIP Tech Chat > [Voip.ms] Cant answer incoming calls

reply to conitssap

Re: [Voip.ms] Cant answer incoming calls

reply to conitssap
I had the same problem on the same provider: every so often answer incoming calls, silence to me, ringing to caller.

Tried two ATAs: a PAP2T and a SPA112. Tried 2 routers: a WRT54GL and WL-520GU. Played with firmware, servers, and registration/NAT parameters in the ATA/router. Spent an insane amount of time on it, with no joy.

I really wanted to stay put but finally gave up and moved on. In the last 8 months using callcentric and anveo on the same equipment, have not seen the problem. Don't know what was at fault, but just saying.

Your situation is the exactly the same as what I have been going through for the last month - im going to test it with another ISP just to give it one last kick at the can.
I dont expect any different though

Maybe it's the phone handset? Have you tried a different one plugged directly into the ATA?

Sometimes you overlook the obvious – I’m using a Panasonic cordless phone. I will try it with a standard wired handset and see if that helps.

reply to Springbok
didnt work with a direct line plugged in - it actually got worse - took me 10 tries to get an answer while the cordless would take 2-3.
changed the phone cord and that did not help either.
not sure why it would get worse though - changed impedance and Ren setting but that did not make a difference.

Here's my ATA settings with voip.ms and although I dont use the analog phones much these days, it's always working when I try them:

PAP2T Firmware Version: 5.1.6(LS)
NAT Keep Alive Intvl: 15 seconds
Ring Waveform: Sinusoid
Ring Voltage: 90
Ring Frequency: 20
Register Expires: 60

I also remember being advised to use the hard IP address of my voip.ms POP and not the DNS name on this ATA (dont remember the reason).

reply to conitssap
had a load of problems getting incoming calls with voip.ms, I think it is just their system, so I just use them for outgoing only which has been pretty good

reply to Dave2
im pretty sure its not a problem with voip.ms but with my ATA

anyways i changed my FXS Ren setting to 5 and its been working fine for the last 15 minutes - moved it back to 0 as the same symptoms popped up again. it could be a coincidence so ill test it out for a longer period of time but it looks promising.
i didn't think a self powered phone would need a higher REN setting but it could be something to do with the cordless headset and would also explain why the problem only worsened on the standalone phone

spoke to soon - everythings the same this morning

reply to fritzthevan
its not your equipment or anyone elses, been having trouble with incoming calls for months now, no matter which server I change to makes no difference, don't know what they are doing bout it but I think nothing, tech support was no help, half of my incoming calls never get through, time toi switch ? i would rather not but this is getting pretty bad

reply to conitssap
is there any wifi in the picture? Getting worse with a cordless phone might point to that.

reply to Stewart

its blame to victim time again, obviously there are major problems with voip.ms handling incoming calls and they don't want to resolve it or even acknowledge it, they know most users do not talk to each other so most think it is their own problem, basically voip.ms is not usable for reliable incoming, too bad as their prices are good, but I guess you get what you pay for or in this case, less than what you pay for, getting rid of voip.ms as soon as possible

reply to conitssap
The plural of anecdote isn't data, but I'll add my own experience:

I ported to Voip.ms about a month ago after the CC fiasco. I have two DIDs (one ported, one new), with relatively low volume of calls. While I admit that my original server choice (Seattle) was leading to some packet loss, once PX put me on the right path to Houston, I've been all set. Not once, zero, have I had a call fail to complete, or a call fail to be received.

Am I just lucky? Maybe. But I think it's a little far fetched to say that Voip.ms is having a massive problem that they're keeping under wraps. I'm sure it's frustrating to have an issue that is taking time to resolve, and while my own limited experience with their tech support was positive, maybe they could use improvement there. I don't know. All I know is that my service (on the Houston server) has been rock solid.

reply to Stewart
I tried a dumb hub but that did not work - I am assuming I need a crossover cable when connecting it directly to the laptop?