VOIP Tech Chat → [Voip.ms] Delay in Answering Calls

I'm with voip.ms. For a lot of callers, when I pick up the phone, they cannot hear me. It takes about 10-15 seconds before they can hear me say "Hello". I'm using a Linksys SPA2102.
If you have any ideas on a fix for this, I would really appreciate it.

We have the EXACT same problem, and it does it whether I'm forwarding a call from voip.ms to my cell, or using a SIP phone. We answer and I hear the other person and I'm like "Hello?" wait 5 secs "Hello?" then finally they are like "Oh hi how are you?". I've changed servers and everything and it does this all the time, that's why in my other thread I've been trying to find another phone provider.

How come I dont have this issue?
If I understand correctly you change servers and the issue persists which states that is a voip.ms issue.
I use: Houston, Dallas, and sometimes Chicago and Atlanta.
No issues here with delay.

I notice that the two people having issues are Canadian. Coincidence?

Good catch Mango.
Seattle and Toronto have been having issues. Maybe is related...

For those having issues: if you use a VoIP.ms subaccount to call your VoIP.ms DID, the call will not be routed through the PSTN. Do the symptoms still occur?

I used Toronto for awhile then Montreal and then Chicago and it does it on all of them. It's not all the time but it is fairly often. I have my DID on voip.ms set to go to a ring group which only has my cell as a call forward member. I have that because I have 2 DIDs that I send to my cell and by using a ring group I can prepend the caller ID to say L1 or L2 for Line 1 or 2 before the caller ID.

However my employee is connected directly to voip.ms using an IP phone and 9 times out of 10 when I call her, my cell will say "Connected" and the timer starts and i hear silence, then 5 seconds later I'll hear her background noise come on and her being like "Hello????"

Then same with if someone calls my DID and it goes to my cell phone, I'll answer and hear them no problem and they just don't hear me.

I've had numerous customers reporting the same problem to me. VoIP.ms has offered numerous suggestions, none of which have been effective. The important point is that these same customers didn't used to have the problem. I have no doubt that the problem would cease if I were to port the customers to a different provider. That is not my goal, however, at some point the customers are going to become impatient and instruct me to do whatever it takes to permanently resolve the situation.

The problem of of the incoming caller not being able to hear the party who is answering the call at my customer locations only last 2 - 5 seconds and it appears to affect somewhere around 2% of the incoming calls.

A similar issue has been reported before with other providers.
»fonality.com/trixbox/for ··· nswering

I'm glad I'm not going crazy, and this is the whole reason that we are looking at other providers in another thread because it's embarrassing to have to keep answering. Like sometimes I'm like "Thank you for calling XYZ Company this is Connor speaking how may I help you?" then it's silence... then I'm like "Hello?" and the customer is like "Oh hi is this XYZ Company??" Since it sounds like I just picked up the phone saying Hello :S.

This really sounds like a network issue, where the firewall/router is initially holding up outbound rtp packets for some reason. The first thing I would do is go over the router/firewall settings, or even reboot the router first if it just started occurring.

yes same here intermittently, with different ATAs, this happens 30-60% of the time. voip.ms is not reliable for incoming calls, period.

If that was the case I would have the issue and so would a 1000 others.

I blame your setup/network/route/traffic.

I noticed this problem too this morning - but now none of my DID #'s work. All inbound calls are failing. What a POS company.

That's too bad. I assume you've tried to route the DIDs to the Echo Test already?

I been tracking this set of post and what I have seen in common is that is the same posters over and over complaining about the same issue.
I also see that the issue has been in the canadian pop's...
Why is it so hard to change pop's?

I was on a call this morning, heard some weird static noises and the call dropped, and it hasn't worked since. Calls from my Rogers cell to any of my GTA DID #'s fail. If you are in the GTA area, you might want to check your inbound # and verify it's working.

It seems that there is an issue with VoIP.ms' ISP Telecom DIDs this morning. At first glance it seems to be only Ontario that is having the problem.

Edit: the issue is now on the VoIP.ms issue tracker.

I have experienced similar issues starting about a month ago. When I was having this problem, people would call my voip.ms DID, I would answer and it would take about 2-3 seconds before the calling party could hear me.

I also have an IPKall DID pointed to my voip.ms SIP URI and it was experiencing the same issues too.

However, I have not experienced this issue for the last several weeks. I have been using the houston server during this time. I am not sure if changing the server fixed the problem, or not.

My DIDs are US DIDs, I am not registering to a Canadian POP, and I was having this issue. I do not think the problem is solely with Canadian DIDs/POPs.

And I stand firm that this must be isolated issues to end users.

Like I said in the past I use Houston, Dallas, and some times Chicago and Atlanta and I do not experience this issue.
When I was using Comcast residential I had all sort of issues including registration drop and it turned out to be a route issue. I been 100% solid sense I moved to Business.

Just saw this reply as well. To say it's the end user is a bit ridiculous. We used Voip.ms in our business for over a year first with an on prem Asterisk deployment using Rogers cable Internet for business, and had no problems other than sometimes on calls over an hour long it would start to get jitter for a minute then stop. Then we switched to a hosted asterisk and still no problems at all, had that maybe 6-8 months all worked fine.

Continued to use hosted Asterisk when we closed our office to work from home, so 4 users all different locations, Rogers Internet at some sites, Bell at others and TekSavvy at one all residential, no issues. Decided didnt' need the PBX so all users registered to the Montreal voip.ms server directly or Toronto, and again still no issues all worked fine.

Then suddenly starting 4 months or so ago non stop issues with dropped calls, poor call quality or now this delayed call issue starting a couple weeks ago. Tried different servers etc still happens, and that's on all 4 users in completely different locations, 2 in Toronto one in St. Catharines and 1 in Cambridge on all different Internet providers. (Just noticed as I'm writing this my IP phone now says no service, so registration has been lost, which happens once a day or so for about 3-5 minutes then comes back. I have 2 lines on my IP phone and it will be one or the other, never both even though they are both on the same voip.ms server).

I switched my parents to voip.ms several months ago with no issue but for the past month even she has been complaining to me and they are in a small town on Rogers using a Linksys ATA device. She says they keep getting emails saying new voicemail but the phone has never rang (my IP phone just registered again, so about 3 minutes since it dropped). Other times she will answer and no one is there, she hangs up and they call back asking why she hung up on them, or the phone will just ring randomly but they can't answer it. Again this is after it working no problem for 4-5 months then this all started a month ago.

I am a Bell Canada partner, but our business isn't large enough to warrant having business lines or a PRI as we have been spoiled by voip, getting direct lines etc. But even one of my customers yesterday was asking me about porting DIDs to their Bell PRI which we discussed for awhile, then after a few emails they told me the issue was that the numbers are with voip.ms but they are having tons of problems with inbound calls just not working. This is from someone that has no idea I even use voip.ms or had trouble with them. I don't know what is going on lately but in the past month they have gone way down hill.

We actually just went out and got Fido cell phones with their unlimited Canada-wide plan and are using Bell single number reach to handle our main menu IVR for the customers that prefer to call us toll free. While the SNR is being set up I have voip.ms forwarding the DIDs to the cell phones, and at least twice a day I'll get an email saying new voicemail in my voip.ms mailbox, without my cell phone even ringing once. I'm completely done with VoIP.

This is why I get so concerned when providers get ongoing issues, it spills over.

Please don't judge all of VoIP by one provider experience.

You know that in Canada you have lots of other options----

Fibernetics
»www.fibernetics.ca/

Fibernetics Business (Newt)
»business.fibernetics.ca/

Acrovoice
»www.acrovoice.ca/content ··· _service

Iristel
»www.iristel.ca/corporate ··· verview/

To name a few....

Yep, this is a battle I fight daily when talking to prospective customers who had a family member or colleague "try VoIP but it didn't work very well."

Just because you've had a poor experience with one provider doesn't mean the entire industry will have the same problems. There are many options available with different providers as PX listed that should be able to deliver the service you want at rates better than Bell with virtually identical call quality.

problem is with the entire system - they want us to think that isolated server problems on a daily basis (so much for "isolated") are to blame, or that somebody else is to blame, but just seems like the system is not reliable and can not handle the number of calls/customers. plain and simple. the sooner we realize this and stop spinning our wheels acting like all these problems are unique to one of us, the sooner they can do what needs to be done instead of stonewalling and taking some action to remedy the situation - and its not canada, and its not LA or NY - its the entire system, sorry to say

reviewed

No no I know it's not all Voip. We are an Allstream partner also where we sell SIP Trunking which doesn't even compare to these services, it's just minimum 15-25 channels required, but if used with Allstream Internet then it doesn't even run through the Internet, but even with 3rd party Internet at least calls are routed through an actual provider to the PSTN not through a multitude of carriers on the back end.

I used Anveo for 2 days was okay until they got that DDOS attack which took us down, so stopped that. I've used callcentric before but I know recently they were attacked and had that flooding issue etc. So all I mean is I'm just really tired of voip, that's why I am using Bell's SNR since at least I know it's all on Bell's network and not routing differently all the time.

It's the fact that even with voip.ms forwarding to a cell, I can call the DID and one time my cell might ring immediately. I then call it back and the phone rings once, twice, three times THEN my cell starts. Call it back, rings once, then cell starts ringing. Call it back again, rings once, twice, three times, four times, voip.ms answers with no cell phone ever ringing. Like it's always just so random. And again trust me I love voip.ms, I've used them for 3 years or so with no issues. It's just lately it seems like there's so many problems. I know that 99% of the time it's the end user, but I look at it like 3 years ago I knew NOTHING about voip. I get it set up and it works fine for us for months and months. Now I have non stop problems, so I try another PBX, bust out my Cisco UC540 to try it, try phones directly connected to it etc, problems non stop and I feel like a total newbie! Then I look back and say I didn't have ANY of these problems years ago when I was new at this, and we would make changes all the time, changing the phones we used, moving asterisk distributions, moving from on prem to hosted, etc, every time we'd make a change things would continue to work. Just now I have so many problems, so make a change such as going as far as selling my Cisco phones and buying Aastra and having it still do the same thing even with Softphones. I just find it hard to believe that I've somehow suddenly got so incompetent that I can't configure anything anymore.

Again I'm not trying to bash voip.ms or tell people not to sign up, I'm simply stating my personal experiences. I was about to post a thread on this delayed answer thing and was surprised to see one already started. Made me feel good to at least know I'm not crazy!