SIP registrations failing for 2 phones
-
@JaredBusch you reckon it's the 60xx port problem that we've both run into?
-
Put the phones back on network. And under the reporting tab in Fpbx check your devices. See if the two devices that are not working are getting super high ports. If so you can manually assign a sip port within range and they will work. Sorry typing from my phone at a client so I don't have my specific notes or anything. @JaredBusch helped me with this problem in the past.
-
@hubtechagain said in SIP registrations failing for 2 phones:
Put the phones back on network. And under the reporting tab in Fpbx check your devices. See if the two devices that are not working are getting super high ports. If so you can manually assign a sip port within range and they will work. Sorry typing from my phone at a client so I don't have my specific notes or anything. @JaredBusch helped me with this problem in the past.
There is one phone there right now that is now doing the same thing (this is the 3rd phone now) It currently is using port 42808
-
@fuznutz04 you can manually assign ports and it will fix this problem. 6051,2,3,4,5 etc if I'm not mistaken. Make sure not to duplicate any. That will get them functioning until you replace their shotty router.
-
@hubtechagain You mean manually specify in both the phone as well as the extension settings for these particular extensions?
-
@fuznutz04 said in SIP registrations failing for 2 phones:
@hubtechagain You mean manually specify in both the phone as well as the extension settings for these particular extensions?
Just in the phone.
You change the outbound port to be either random or something specific and all different.
Crappy routers have problems with multiple devices and NAT on the same port.
In the Yealink phones, they specifically all use port 5060 as their outbound port even though that should not be required. Changing them to 5061, 5062, etc will resolve crappy router NAT issues.
This has nothing to do with the PBX. It still uses 5060 for all the incoming SIP registrations.
-
@JaredBusch said in SIP registrations failing for 2 phones:
outers have problems with multiple devices and NAT on the same port.
In the Yealink phones, they specifically aI have a router coming tomorrow, so I'm pretty confident that will fix these issues. However, that's good to know, and I haven't run into this specific problem before. Good to know that changing the port to a lower one might fix the issue. @hubtechagain seems pretty confident that it will for sure fix it. I'll give it a shot, nothing to lose at this point.
-
@fuznutz04 said in SIP registrations failing for 2 phones:
@JaredBusch said in SIP registrations failing for 2 phones:
outers have problems with multiple devices and NAT on the same port.
In the Yealink phones, they specifically aI have a router coming tomorrow, so I'm pretty confident that will fix these issues. However, that's good to know, and I haven't run into this specific problem before. Good to know that changing the port to a lower one might fix the issue. @hubtechagain seems pretty confident that it will for sure fix it. I'll give it a shot, nothing to lose at this point.
He had a similar problem a few weeks back and I helped him resolve it by doing this.
-
@JaredBusch The moral of this story is that Comcast "business " all in one modems/firewalls suck. Specifically, they are not capable of handling more than about 2 current SIP registrations at once. Which is stupid, because my old WRT54G handled more than that when I needed to use it in a pinch.
-
That was my professional answer of course. "The router sucks" and "This is just stupid" are technical terms of course.
-
@fuznutz04 said in SIP registrations failing for 2 phones:
@JaredBusch The moral of this story is that Comcast "business " all in one modems/firewalls suck. Specifically, they are not capable of handling more than about 2 current SIP registrations at once. Which is stupid, because my old WRT54G handled more than that when I needed to use it in a pinch.
I've never trusted anything from an ISP. Take the cheapest cheapskate you ever knew, and that person buys better equipment than most ISP provided on-premise anything.
-
@travisdh1 said in SIP registrations failing for 2 phones:
@fuznutz04 said in SIP registrations failing for 2 phones:
@JaredBusch The moral of this story is that Comcast "business " all in one modems/firewalls suck. Specifically, they are not capable of handling more than about 2 current SIP registrations at once. Which is stupid, because my old WRT54G handled more than that when I needed to use it in a pinch.
I've never trusted anything from an ISP. Take the cheapest cheapskate you ever knew, and that person buys better equipment than most ISP provided on-premise anything.
True story.
-
So I installed a new ERL, assigned it a public static IP & Gateway and the internet is working. However, I am still having the same issue with only about 3 of the 6 devices. (where they keep being marked as unreachable.)
The Comcast "Gateway" has an option to go into Bridged Mode. This is what I was planning on doing, in an attempt to completely bypass the comcast box, and eliminate any chances of double NATing, or some other issue messing with SIP. I called Comcast and they tell me that enabling Bridged Mode will not work with a static IP address. So I tried switching to bridged mode anyway, and sure enough, it didn't work. No internet access was possible. Switching back to "normal" mode solves the internet issue, but I still have have the issues with the phones being marked as unreachable.
This really feels like some sort of double NAT issue, or something else on the Comcast gateway causing the NAT holes to close. It's almost like it cannot handle more than 3 simultaneous SIP connections. The problems are not with the phones, as I've tested them at other locations outside of this location and they have no issues whatsoever. The problems are not specific to specific phones either. There are always problems with 3 of the 6 devices.
-
@fuznutz04 said in SIP registrations failing for 2 phones:
This really feels like some sort of double NAT issue,
An unreasonable assumption. The likelihood is that it is the expected issue with the Comcast router, the router which you were intending to replace but did not so it is still in place causing the issue. The double NAT doesn't help, but we know isn't the issue as the issue existed before that.
-
Basically what Comcast is telling you is that they don't have any business offering.
-
@scottalanmiller said in SIP registrations failing for 2 phones:
Basically what Comcast is telling you is that they don't have any business offering.
Which is a joke, because it is their "business class" service. There has to be a way to bypass this. I know of others with Comcast business gateways that operate fine. I was reading many forums this evening and some people are saying that certain models of the business gateway have issues with VoIP and that I should request a new/different model from comcast.
-
@fuznutz04 said in SIP registrations failing for 2 phones:
@scottalanmiller said in SIP registrations failing for 2 phones:
Basically what Comcast is telling you is that they don't have any business offering.
Which is a joke, because it is their "business class" service. There has to be a way to bypass this. I know of others with Comcast business gateways that operate fine. I was reading many forums this evening and some people are saying that certain models of the business gateway have issues with VoIP and that I should request a new/different model from comcast.
Comcast specifically requires their router be used for static IP customers. You can bring your own modem only with DHCP service from them.
-
@JaredBusch said in SIP registrations failing for 2 phones:
@fuznutz04 said in SIP registrations failing for 2 phones:
@scottalanmiller said in SIP registrations failing for 2 phones:
Basically what Comcast is telling you is that they don't have any business offering.
Which is a joke, because it is their "business class" service. There has to be a way to bypass this. I know of others with Comcast business gateways that operate fine. I was reading many forums this evening and some people are saying that certain models of the business gateway have issues with VoIP and that I should request a new/different model from comcast.
Comcast specifically requires their router be used for static IP customers. You can bring your own modem only with DHCP service from them.
I wonder, how often do they change their DHCP provided addresses? Cox residential, in my area, rarely changes IPs. I had the same IP for over a year before.
-
What Jared said. We have a location on Comcast with a static IP. Comcast was supposed to send us a modem only, but send a modem/router instead. Even though we worked with Comcast support to bridge their piece of crap and could get our router connected, it never ever worked. FINALLY (after I think 3 maybe 4 support calls and truck rolls) thelast truck tech replaced it with an arris modem only and we got it to work. You may just have to call them and be as persistent as possible.
-
Is static really needed? How often is static needed for business customers today?
