dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
1190
share rss forum feed

tbrummell2

join:2002-02-09
Ottawa, ON
kudos:1

[Voip.ms] Anyone having incoming problems?

Unable to get incoming calls on my Voip.ms DID's. Wireshark is showing me I am receiving the Invite but my pbx appears to be ignoring it.
I notice in the trace they are using Asterisk 11.2.1, just wondering if this is something new on their side? Anyone know?

This was working fine on the weekend so I'm not sure when it went down.



Qsig

join:2009-05-18
Kanata, ON

Just tested my DID (613 area code), works fine. I'm running FreePBX here.


jhouston21

join:2004-12-17
Hampton, NH
reply to tbrummell2

Yes, I just got a call from a customer indicating that their incoming calls were not working. They were using the Dallas POP. We switched to the Seattle POP. After their gateway restarted, the VoIP.ms customer portal showed that they were registered with Tampa, not Seattle. So, right now, we switched to Chicago POP and the VoIP.ms customer portal indicates that we're actually registered there. So, for now, until the Chicago POP melts down, the customer is sticking with that.

This situation underscores why I will not put any new customers with VoIP.ms for at least 6 months after I begin to hear reports that their service is back to the reliability that I observed prior to October or so of 2012. While Callcentric had it's troubles in October and November, all indications are that they quickly put their troubles behind and made the necessary investment to guard their service against ongoing DDoS attacks. Right now I'd be more inclined to switch customers back to Callcentric and other good providers (very favorable experience with Anveo!) than I would be to even consider VoIP.ms.

Come on, VoIP.ms, you've got a great set of capabilities, make your system as reliable as it once was!


tbrummell2

join:2002-02-09
Ottawa, ON
kudos:1

I think I've determined that it is my firewall. The Invite is making it to my firewall, but not to my Asterisk server, something going on in my firewall by the looks of it. Not sure what to do at this point as my 2 other providers still work.



Qsig

join:2009-05-18
Kanata, ON

What're you using for the firewall?


tbrummell2

join:2002-02-09
Ottawa, ON
kudos:1

pfSense.


Oceans11

join:2013-01-21
united state
reply to jhouston21

Earlier this AM I installed/programmed an OBI-202 for use on VOIP.MS and so far no incoming / outgoing call issues from my SOHO located in Rockingham County, NH


tbrummell2

join:2002-02-09
Ottawa, ON
kudos:1
reply to tbrummell2

Well, after working my ticket from support, I'm working again on Houston server.
For whatever reason, Invites from Chicago and/or Montreal2 will not forward through my firewall, yet Houston does. Something doesn't sound right there, but I'm getting calls again.


Mango
What router are you using?
Premium
join:2008-12-25
www.toao.net
kudos:12

FYI: »Re: [Voip.ms] Voicemail hangs up?


tbrummell2

join:2002-02-09
Ottawa, ON
kudos:1

Yeah, they mentioned the upgrade in the ticket. I see differences in the traces, but it doesn't explain why one Invite will forward through my firewall and the other won't. The new servers are Asterisk 11.2.1, you can see the version in the Invite, the old server (Houston) doesn't show me a version. If this happens on all the servers and can't be resolved with my firewall......


MartinM
VoIP.ms
Premium,VIP
join:2008-07-21
kudos:3
reply to tbrummell2

I would love to make a trace on both servers to you to see the difference in the invite if you have time.

The new versions that are deployed have additional nat traversal mechanisms but until we roll out the update on all servers we can't make it available via the portal. However, I can set it individually on a per account basis.

We didn't really receive reports of devices not able to receive invites but if you've got it working on a server and not th e other, I would love to find the reason.

Let me know if you're interested in doing these quick tests, we can discuss via PM. Thanks

Regards
--
Martin - VoiP.ms



Qsig

join:2009-05-18
Kanata, ON

Click for full size
I bet it is that exactly Martin.

My system was losing the nat state to FreePBX so I would re-register and it would work great for a bit but then wouldn't after a while.

For pfSense, I had to change my NAT mode to Manual. I made a rule for FreePBX to not change the source port and then a catchall rule.
I posted a picture for reference.

tbrummell2

join:2002-02-09
Ottawa, ON
kudos:1
reply to MartinM

I already have the traces from Chicago, Montreal & Houston. Call me proactive. Let me know where I can send them....or I can just attach them to my ticket.


tbrummell2

join:2002-02-09
Ottawa, ON
kudos:1
reply to Qsig

My NAT was already set to Manual (needed to do that to have it work with Freephoneline), but I do not have a specific entry for 5060.


tbrummell2

join:2002-02-09
Ottawa, ON
kudos:1
reply to MartinM

Traces attached to 277133.



Qsig

join:2009-05-18
Kanata, ON
reply to tbrummell2

I have that NAT rule and I have 5060 going to my FreePBX via port forwarding. My firewall rule only allows the Voip.MS servers through for that so no worries about having 5060 open to everyone.


music4praise

join:2006-02-22
Big Rapids, MI
reply to tbrummell2

I haven't been receiving incoming for four days now. Outgoing works fine and my message waiting light comes on when someone leaves a voicemail. I have a ticket in on it so hopefully we can get it all going again. Fortunately, since the VM notification comes through, I can call someone back.


tbrummell2

join:2002-02-09
Ottawa, ON
kudos:1
reply to Qsig

I am forwarding 5060 to FreePBX as well as I registered extensions from the world, well, North America.
It does not explain why pfSense will not forward from those servers in question.


tbrummell2

join:2002-02-09
Ottawa, ON
kudos:1
reply to music4praise

What server are you on? Have you tried changing to one of the older servers (see Mango's post for a list of the older servers)?


music4praise

join:2006-02-22
Big Rapids, MI

1 edit

Thanks for the suggestion. I have been using the New York server so I tried several of the servers not yet upgraded. Unfortunately, it didn't provide a solution.


Biker

join:2012-11-04
Longueuil, QC

Had that problem this week.
Incoming calls not provided with rings and going directly to the voice mailbox.
Using SPA 2102, after hours of testing I had the main portal DID set to CODECS=ALL. I changed it to only G.729u.
Then, everything came back on track with only that change.
That was on the Montreal2.voip.ms server.
Before the change I have made, it was not working on Montreal and Toronto as well.
But note that it was working on Atlanta.
Codecs seem to be sensitive.
Hopefully it's not just coincidence.


azmike

join:2012-07-19
Phoenix, AZ
reply to Qsig

Click for full size
I've found that conservative "Firewall Optimization Options" solves incoming call issues.

tbrummell2

join:2002-02-09
Ottawa, ON
kudos:1

I'll keep that in mind when they upgrade the other servers.