Register expiry
-
- Posts: 44
- Joined: Wed Jul 14, 2010 3:28 pm
Register expiry
Good day folks.
Don't mean to take over the tech support forum, but I'm unable to call my GV number from time to time. I figured out, that if I unregister the "callcentric" provider and than register it again, everything starts working again.
The register expiry is set to 3600 on my PAP2T and it was also 3600 for the provider setting in sipsorcery, but I set it to 2000 in sipsorcery, just to see if it makes a difference. I know sometimes the server has a default setting.
If anyone could give me some tips, I would greatly appreciate that.
Don't mean to take over the tech support forum, but I'm unable to call my GV number from time to time. I figured out, that if I unregister the "callcentric" provider and than register it again, everything starts working again.
The register expiry is set to 3600 on my PAP2T and it was also 3600 for the provider setting in sipsorcery, but I set it to 2000 in sipsorcery, just to see if it makes a difference. I know sometimes the server has a default setting.
If anyone could give me some tips, I would greatly appreciate that.
Re: Register expiry
It would be strange if reducing the registration expiry on your callcentric provider made any difference. The sipsorcery server is on a public IP address and there is no NAT involved so there is nothing that will prevent request from callcentric getting through to sipsorcery for the whole 3600s.
However the expiry interval for your PAP2 could be causing a problem. Generally I'd recommend setting the expiry timeout to between 180 and 300s to cope with any NATs in between it and the sipsorcery server. You need to change that setting on your PAP2. With it set at 3600 it's likely that your NAT will block incoming requests after a certain period of inactivity and your incomign GV calls won't start working again until the PAP2 re-registers.
However the expiry interval for your PAP2 could be causing a problem. Generally I'd recommend setting the expiry timeout to between 180 and 300s to cope with any NATs in between it and the sipsorcery server. You need to change that setting on your PAP2. With it set at 3600 it's likely that your NAT will block incoming requests after a certain period of inactivity and your incomign GV calls won't start working again until the PAP2 re-registers.
-
- Posts: 44
- Joined: Wed Jul 14, 2010 3:28 pm
Re: Register expiry
Thanx AaronAaron wrote:It would be strange if reducing the registration expiry on your callcentric provider made any difference. The sipsorcery server is on a public IP address and there is no NAT involved so there is nothing that will prevent request from callcentric getting through to sipsorcery for the whole 3600s.
However the expiry interval for your PAP2 could be causing a problem. Generally I'd recommend setting the expiry timeout to between 180 and 300s to cope with any NATs in between it and the sipsorcery server. You need to change that setting on your PAP2. With it set at 3600 it's likely that your NAT will block incoming requests after a certain period of inactivity and your incomign GV calls won't start working again until the PAP2 re-registers.
I changed the PAP2T to 300s. However, after a while, calls to DID went to voicemail. I logged in to sipsorcery, messed with the registry expiry for provider "callcentric" and the service is back. Now what?
Re: Register expiry
Have you got any other devices registering with your callcentric account?
Maybe another device is overwriting the sipsorcery contact which would explain why it then starts working again when you change the settings at the sipsorcery end and force it to re-register.
Maybe another device is overwriting the sipsorcery contact which would explain why it then starts working again when you change the settings at the sipsorcery end and force it to re-register.
-
- Posts: 44
- Joined: Wed Jul 14, 2010 3:28 pm
Re: Register expiry
Aaron wrote:Have you got any other devices registering with your callcentric account?
Maybe another device is overwriting the sipsorcery contact which would explain why it then starts working again when you change the settings at the sipsorcery end and force it to re-register.
No other device is logging into sipsorcery.
Re: Register expiry
Looks like you are using the Advanced Settings in Sip Provider (SipSorcery).
Just try it Not using the advanced settings and see if the problem is Solved.
Just try it Not using the advanced settings and see if the problem is Solved.
-
- Posts: 44
- Joined: Wed Jul 14, 2010 3:28 pm
Re: Register expiry
DoDo wrote:Looks like you are using the Advanced Settings in Sip Provider (SipSorcery).
Just try it Not using the advanced settings and see if the problem is Solved.
It is 3600 by default. No way to get rid of it.
Re: Register expiry
Don't use Realm,Auth Username...etc. In Advanced Settings. And if you did, Just delete The Sip Provider And Create it Again Without Using Advanced Settings.