[VoIP] SIP Registration

[Lee Spenadel]

Shane,

Thanks for shedding light on this.  I wasn't expecting any particular
registration interval and am not looking to change it.  I was merely trying
to understand the re-registration process, which I now do.  So thanks for
that! 

Oh, my SIP object defining the ATA relationship does not have a qualify=yes
statement, yet I never have a problem reaching my friend.  Given this, it
sounds like there would be no benefit to adding it to my object, correct?

Many thanks
Lee

-----Original Message-----
From: voip-bounces at ckts.info [mailto:voip-bounces at ckts.info] On Behalf Of
Shane Young
Sent: Thursday, October 25, 2007 9:06 AM
To: voip at ckts.info
Subject: Re: [VoIP] SIP Registration

It's re-registering because it's registration was set to expire in one  
hour (3600 seconds = 1 hour)

It can be set in several places, including the ATA and the sip objects  
within sip.conf.

What frequency of registration are you expecting?

There are several reasons why you'd want a device to re-register at  
what you might consider "frequent" times.

For example, if your friend's IP address changed, your Asterisk box  
would think his ATA is still registered at the old IP address until it  
re-registered.  If you tried to call him, it would send the invite to  
the wrong IP and he would not be able to receive calls.  He would  
likely be able to make callse because the ATA would authenticate when  
it placed a call (but not necessarily re-register)

A firewall reset could prevent the sip messages from your machine  
getting back to his ATA.

Firewalls generally close the dynamic holes that are opened for the  
return traffic.  If you don't have "qualify=yes" in your SIP object,  
you might not be able to send traffic to his ATA if the firewall has  
closed the hole.  Leaving "qualify=yes" on will make asterisk and the  
ATA chat with each other frequently enough to keep the firewall happy.

Some sip-based systems can detect if NAT/PAT is being used on a  
firewall or router and will adjust the register time to make sure  
firewalls don't close the holes that were opened dynamically for the  
outbound registration.

So, that might be the long answer.  The short answer is "it's normal".

--Shane



Quoting Lee Spenadel <lee at spenadel.com>:

> I have an ATA at a friend's house that hangs off my Asterisk switch.
Every
> hour or so I get a SIP registration message on my console:
>
>
>
>     -- Registered SIP '349XXXX' at 24.60.244.56 port 2231 expires 3600
>
>
>
> Does anyone know why I would be getting the reg message at this frequency?
>
>
>
> Thanks
>
> Lee
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> VoIP mailing list
> VoIP at ckts.info
> http://lists.ckts.info/mailman/listinfo/voip
> Project Web Page: http://www.ckts.info/
>

--Shane
+1-821-7311 CNET

----------------------------------------------------------------

_______________________________________________
VoIP mailing list
VoIP at ckts.info
http://lists.ckts.info/mailman/listinfo/voip
Project Web Page: http://www.ckts.info/