Obi202 - Phone Not Ringing...sometimes
voipmvtalk:
Ok premature celebration. Same issue. Inconsistent ringing even with their change or hanging directly on the comcast modem and bypassing router altogether.
I don't think it is a lookup issue with caller id. I had one friend call in and no ring. next friend one minute later it rang. so the first call seems to be opening up a port or "waking up" the device which the follow on calls take advantage of and ring. after some time period it seems to reset and require a wake up call to get another call to ring. So bizzare.
SteveInWA:
Well, regarding your router, if it has a "SIP ALG" setting, that setting should be DISABLED. I don't know how that translates to "SIP Passthrough". I am just guessing here, that SIP Passthrough ENabled = SIP ALG DISabled. The goal is for your router to NOT act on the SIP packets, so that sounds right.
I'm sticking with my original hunch that you have some sort of network (router) configuration problem. What model router is this? Did you replace it or update it when the problem started?
voipmvtalk:
Quote from: SteveInWA on September 14, 2016, 12:56:13 pm
Well, regarding your router, if it has a "SIP ALG" setting, that setting should be DISABLED. I don't know how that translates to "SIP Passthrough". I am just guessing here, that SIP Passthrough ENabled = SIP ALG DISabled. The goal is for your router to NOT act on the SIP packets, so that sounds right.
I'm sticking with my original hunch that you have some sort of network (router) configuration problem. What model router is this? Did you replace it or update it when the problem started?
Here is latest update and you are probably right regarding network/router. Callcentric also said same and wanted me to hook up to DMZ on my comcast modem. A little digging and my comcast modem was still in router mode and not bridge mode so it was doing its own routing before my router.
What I did was put the comcast modem into bridge mode (no router - straight shot to my router) and am now testing. My router is Asus.
So far all test calls in the last hour have been successful in ringing the phone. I will wait a couple hours and test calling again after no calls have hit the number for awhile in order to duplicate most closely what I was seeing before.
If this fixes it that means the comcast/xfinity modem's router was clogging up the SIP packets but not in a consistent way. Possibly acting as a port trigger with the first call to open it up and then the second call has the pathway through. Then the port trigger closes after some time and I was back to the same again. At least I'm hoping this is what was occuring here.
Will update after a few more tests throughout the afternoon and evening.
thanks
voipmvtalk:
Ok so good news. all the phone call tests so far have been successful and the phone is now ringing on first and follow up attempts even after longer intervals in between.
I'd say it is now safe to say the Comcast/Xfinity cable modem was the root cause. Being that it was in router mode (instead of Bridge mode) it was indeed acting as a router and must have been filtering SIP packets before they could ever hit the obitalk. The reason only follow on calls would ring the phone I suspect is that the initital call triggered a port which then opened it up for follow on calls afterwards. However once the port closed after after keepalive was over the next "first" call failed and so on.
So the fix was indeed to put comcast into Bridge mode and forward to my Asus router and let that do all the routing. Also they suggested my SIP passthrough be disabled.
Glad this is finally resolved. Big thanks to Callcentric Support and SteveInWa right here for providing the guidance, tips and assistance to track this one down and get it fixed up. One more day and I was going to lose it!
SteveInWA:
Glad to hear it. Yes, cascading through multiple NAT routers does cause problems with VoIP. Setting your Xfinity modem to bridge mode is the solution.
Navigation
[0] Message Index
[#] Next page
[*] Previous page