[Asterisk-Users] SIP peer registration interval

[Robert Webb]

On Thu, 17 Feb 2005 15:04:50 +0100

Hi folks,
I'm registered with sipgate, a German SIP provider.
Configs works fine so far. Trouble is, after a while, it
seems, my registration is dropped by sipgate. How do I
tell * the interval for * registering with a provider? I
suppose, the re-registration interval is to long...
Regards,
Stefan
--
(o_ Stefan Gofferje | Linux Systems
Specialist
//\ Reg'd Linux User #247167 | Network Security
Specialist
V_/_ Linux is like a Wigwam - No gates, no windows,
Apache inside

defaultexpirey=120 :Default length of incoming/outoing
registration

I believe that is the correct option.

This site is your friend. Try searching...

http://www.voip-info.org/wiki-Asterisk+config+sip.conf

[n***@yorkukhosting.com]

Hi folks,
I'm registered with sipgate, a German SIP provider. Configs works fine
so far. Trouble is, after a while, it seems, my registration is

dropped

by sipgate. How do I tell * the interval for * registering with a
provider? I suppose, the re-registration interval is to long...
Regards,
Stefan

If you're behind NAT try enabling qualify in sip.conf. Either
qualify=yes
or try a specific value, for example qualify=1000. More info on the
wiki:

http://www.voip-info.org/tiki-index.php?page=Asterisk%20sip%20qualify

-nathan

[Michiel van Baak]

Post by n***@yorkukhosting.com
If you're behind NAT try enabling qualify in sip.conf. Either
qualify=yes
or try a specific value, for example qualify=1000. More info on the
http://www.voip-info.org/tiki-index.php?page=Asterisk%20sip%20qualify

As far as I understood, qualify has nothing to do with the registration
status but just checks if the peer is reachable. Actually, I am behind a
NAT but I have a firewall with a SIP ALG which does all the necessary
changes to the packets.

Dont know if this is related but I had the same problems
with sip registration of a snom 190.
Putting qualify=yes resolved it here.
I know it should be just for checking, but it will also keep
a state open on the firewall, so that might be the trick.

[Rich Adamson]

Post by Michiel van Baak

Post by n***@yorkukhosting.com
If you're behind NAT try enabling qualify in sip.conf. Either
qualify=yes
or try a specific value, for example qualify=1000. More info on the
http://www.voip-info.org/tiki-index.php?page=Asterisk%20sip%20qualify

As far as I understood, qualify has nothing to do with the registration
status but just checks if the peer is reachable. Actually, I am behind a
NAT but I have a firewall with a SIP ALG which does all the necessary
changes to the packets.

Dont know if this is related but I had the same problems
with sip registration of a snom 190.
Putting qualify=yes resolved it here.
I know it should be just for checking, but it will also keep
a state open on the firewall, so that might be the trick.

I have read in another (German) forum that qualify might be the cause
for the registration drop.
Anyway, I'm behind a Cisco PIX which is completely SIP aware and does
all the NAT wizardry. sip debug also shows me the re-register any 45
secs. At one point, it just stops re-registering... very very ugly...

Somewhat off topic, but we just seen the same kind of issue with
a pix passing vpn. After some period of time, the vpn link simply
disappears. Moving the vpn box outside the pix fixed the problem.

[Magnus Jungsbluth]

Hi,

I'm having the same problem with the same Provider running asterisk on
an "open" server that is in a hosted environment. The Problem is
definately not the defaultexpirey. I can watch asterisk refreshing the
registration every few minutes when using sip debugging. After a while
(days) asterisk stops refreshing the registration. "sip show registry"
shows that asterisk thinks it has a valid registration that expires
after 120sec, BUT it doesn't do anything about it. After a while the SIP
Provider assumes that asterisk is offline ....
My solution is to restart asterisk once a day which is not satisdying
but works fine so far.
Im using stable 1.0.2. The sipgate is using SER as proxy...

greetings,
Magnus

I'm registered with sipgate, a German SIP provider. Configs works
fine so far. Trouble is, after a while, it seems, my registration is
dropped by sipgate. How do I tell * the interval for * registering
with a provider? I suppose, the re-registration interval is to long...

defaultexpirey=120 :Default length of incoming/outoing registration

[Magnus Jungsbluth]

This is what I tryied on last Tuesday. It ran fine until yesterday (4
days) then asterisk stopped re-registering again. A "sip reload" fixed
the problem and asterisk now re-registers happily again. I'm just unsure
for how long ...

Hi folks,
I'm registered with sipgate, a German SIP provider. Configs works
fine so far. Trouble is, after a while, it seems, my registration is
dropped by sipgate. How do I tell * the interval for * registering
with a provider? I suppose, the re-registration interval is to long...

I finally found a solution. THe SER of Sipgate seem to dislike being
qualified, so setting qualify=no solved this problem.
I also set defaultexpirey=60, which is respected by Sipgate's SER and
makes re-registration after change of dynamic IP a bit faster and more
reliable.