Start a new topic

Incoming calls fail to ring intermittently

I have:


a) a linksys pap2 with two lines configured in mini-pbx mode. Both online per pap2

b) two pots lines

c) google voice configured  with all the above to ring on incoming calls.


Outgoing calls work fine. Incoming calls fail to ring intermittently (approx50%) on the two linksys lines and never fail on the Pots lines. Google voice settings remain the same between working incoming calls and non working incoming calls.


Any help appreciated!




@Gregg Lebovitz

What is your device?

Hi Mark, Thanks for getting back to me.


I have a Grandstream GXP1405. I have tried a number of different configurations and non of them seem to fix this problem.


Gregg

Mark,


I forgot to mention. Calls consistently ring on my Hangouts and forwarded phone just fine, so the issue is not with Google.



If your NAT/firewall is closing the ports then a 10 minute registration cycle may not be enough. Make sure that NAT Keepalive pings are turned on or lower your registration interval to 180 sec so that there is frequent traffic passing through. If we are sending calls to you but your NAT/firewall has closed the ports on you then you won't get the call.


I have three Google Voice accounts that I use regularly, set up through GVGW: one is registered with an Asterisk server, another is configured with a SIP URI, and the third is registered directly on my Grandstream Wave softphone on Android. I tend to prefer TCP or TLS transport (not relevant with the SIP URI configuration). On all three of these I do not miss calls. I say this to assure you that it can be made to work but you may have to investigate more closely what's going on in your network.

Mark - Good to know you have this working. That is encouraging. I am using TCP (though I also tried UDP and had the exact same results). I will try the 3 minute registration cycle and see if that helps. The phone is listening on port 2062 and this is permanently mapped in the firewall. The phone is sending keep alives to keep the connection open.


Thanks for your suggestions.

You're welcome - and don't call me Mark. :)

Bill - yeah, I should read the from line to see who is helping me. Sorry about that.


The change to 3 minute registration cycle seems to have fixed the issue..  I let it run for a few days and I am still receiving calls.


Thanks for your help.

Bill,


NAT is not the issue in my case it is an asterisk with public IP and Asterisk always immediately answers the call, or at least when it gets there . The problem is sometimes it never gets there.


and stop calling me Shirley


Mark

Bill,


I wanted you to see this 


from the sip show registry below

GV177091ABCD registered at 00:40:12

105 seconds is 1 Minute 45 seconds

next registration should be at (completed by this time!) 00:41:57

Next reg did not occur till 00:42:07


No matter what I set in asterisk it seems the reg interval is always 105 seconds on GVGW . Often I see 3 or more registration attempts before it actually registers too.


SO of a call comes in between 00:41:57 and 00:42:07 (10 seconds) , my asterisk  is unreachable 


10 seconds of 105 seconds is nearly 10% of the time


i would like to try to get the sip reg interval to 3600 this, after all is a public IP with no NAT, this would then give me only 10 seconds of every hour to be unreachable.


Mark




gvgw.simonics.com:5060 Y GV177091ABCD 105 Registered Sun, 17 Sep 2017 00:40:12   

gvgw.simonics.com:5060 Y GV165020ABCD 105 Registered Sun, 17 Sep 2017 00:41:17

gvgw.simonics.com:5060 Y GV180192ABCD 105 Registered Sun, 17 Sep 2017 00:41:02

gvgw.simonics.com:5060 Y GV192936ABCD 105 Registered Sun, 17 Sep 2017 00:41:12

callcentric.com:5060 Y 17772840ABCD 50 Registered Sun, 17 Sep 2017 00:40:50

5 SIP registrations.

tel*CLI> sip show registry

Host dnsmgr Username Refresh State Reg.Time                 

gvgw.simonics.com:5060 Y GV177091ABCD 105 Request Sent Sun, 17 Sep 2017 00:40:12

gvgw.simonics.com:5060 Y GV165020ABCD 105 Registered Sun, 17 Sep 2017 00:41:17

gvgw.simonics.com:5060 Y GV180192ABCD 105 Registered Sun, 17 Sep 2017 00:41:02

gvgw.simonics.com:5060 Y GV192936ABCD 105 Registered Sun, 17 Sep 2017 00:41:12

callcentric.com:5060 Y 17772840ABCD 51 Registered Sun, 17 Sep 2017 00:41:41

5 SIP registrations.

tel*CLI> sip show registry

Host dnsmgr Username Refresh State Reg.Time                 

gvgw.simonics.com:5060 Y GV177091ABCD 105 Auth. Sent Sun, 17 Sep 2017 00:40:12

gvgw.simonics.com:5060 Y GV165020ABCD 105 Registered Sun, 17 Sep 2017 00:41:17

gvgw.simonics.com:5060 Y GV180192ABCD 105 Registered Sun, 17 Sep 2017 00:41:02

gvgw.simonics.com:5060 Y GV192936ABCD 105 Registered Sun, 17 Sep 2017 00:41:12

callcentric.com:5060 Y 17772840ABCD 51 Registered Sun, 17 Sep 2017 00:41:41

5 SIP registrations.

tel*CLI> sip show registry

Host dnsmgr Username Refresh State Reg.Time                 

gvgw.simonics.com:5060 Y GV177091ABCD 105 Auth. Sent Sun, 17 Sep 2017 00:40:12

gvgw.simonics.com:5060 Y GV165020ABCD 105 Registered Sun, 17 Sep 2017 00:41:17

gvgw.simonics.com:5060 Y GV180192ABCD 105 Registered Sun, 17 Sep 2017 00:41:02

gvgw.simonics.com:5060 Y GV192936ABCD 105 Registered Sun, 17 Sep 2017 00:41:12

callcentric.com:5060 Y 17772840ABCD 51 Registered Sun, 17 Sep 2017 00:41:41

5 SIP registrations.

tel*CLI> sip show registry

Host dnsmgr Username Refresh State Reg.Time                 

gvgw.simonics.com:5060 Y GV177091ABCD 105 Auth. Sent Sun, 17 Sep 2017 00:40:12

gvgw.simonics.com:5060 Y GV165020ABCD 105 Registered Sun, 17 Sep 2017 00:41:17

gvgw.simonics.com:5060 Y GV180192ABCD 105 Registered Sun, 17 Sep 2017 00:41:02

gvgw.simonics.com:5060 Y GV192936ABCD 105 Registered Sun, 17 Sep 2017 00:41:12

callcentric.com:5060 Y 17772840ABCD 51 Registered Sun, 17 Sep 2017 00:41:41

5 SIP registrations.

tel*CLI> sip show registry

Host dnsmgr Username Refresh State Reg.Time                 

gvgw.simonics.com:5060 Y GV177091ABCD 105 Auth. Sent Sun, 17 Sep 2017 00:40:12

gvgw.simonics.com:5060 Y GV165020ABCD 105 Registered Sun, 17 Sep 2017 00:41:17

gvgw.simonics.com:5060 Y GV180192ABCD 105 Registered Sun, 17 Sep 2017 00:41:02

gvgw.simonics.com:5060 Y GV192936ABCD 105 Registered Sun, 17 Sep 2017 00:41:12

callcentric.com:5060 Y 17772840ABCD 51 Registered Sun, 17 Sep 2017 00:41:41

5 SIP registrations.

tel*CLI> sip show registry

Host dnsmgr Username Refresh State Reg.Time                 

gvgw.simonics.com:5060 Y GV177091ABCD 105 Auth. Sent Sun, 17 Sep 2017 00:40:12

gvgw.simonics.com:5060 Y GV165020ABCD 105 Registered Sun, 17 Sep 2017 00:41:17

gvgw.simonics.com:5060 Y GV180192ABCD 105 Registered Sun, 17 Sep 2017 00:41:02

gvgw.simonics.com:5060 Y GV192936ABCD 105 Registered Sun, 17 Sep 2017 00:41:12

callcentric.com:5060 Y 17772840ABCD 51 Registered Sun, 17 Sep 2017 00:41:41

5 SIP registrations.

tel*CLI> sip show registry

Host dnsmgr Username Refresh State Reg.Time                 

gvgw.simonics.com:5060 Y GV177091ABCD 105 Registered Sun, 17 Sep 2017 00:42:07

gvgw.simonics.com:5060 Y GV165020ABCD 105 Registered Sun, 17 Sep 2017 00:41:17

gvgw.simonics.com:5060 Y GV180192ABCD 105 Registered Sun, 17 Sep 2017 00:41:02

gvgw.simonics.com:5060 Y GV192936ABCD 105 Registered Sun, 17 Sep 2017 00:41:12

callcentric.com:5060 Y 17772840ABCD 51 Registered Sun, 17 Sep 2017 00:41:41


We experienced some DoS-like loads on Sunday morning either from intentional heavy traffic or network problems at the provider. That might explain the problems you were having during that time.


As for the registration interval, that is configured in Asterisk on the registration line. Default is 3600 so if your registration is defaulting to 105 you may have changed it somewhere in your general SIP config.

FWIW, I was experiencing this same issue. After reading Bill's comments and checking the Asterisk Wiki and figuring out how to correctly port forward the user agent port it seems to have corrected the problem.

 

Login or Signup to post a comment