I started a client and let a sniffer running to observe the traffic.
At the initial REGISTER, there is an Expire: 3600 in the header. That is, after 3 minutes the registration "should" expire.
Taking a look at the sniffed traffic, even after 5 minutes, not even one REGISTER is sent. I see only OPTIONS probes sent by the server and SUBSCRIBE packets sent by the UA. But for every SUBSCRIBE it is sent a 401 back.
Is REGISTER really the only way for the UA to update its registration?
I read the RFC 3261 and there it says that REGISTER packets should refresh the registration, but I am not seeing this in practice.
Thanks for your help,
Felipe Louback
On 7/3/07, Klaus Darilion klaus.mailinglists@pernau.at wrote:
Felipe Louback wrote:
Hey,
How does SER updates a user location?
For exemple, upon the first REGISTER message, it keeps the location of the user in a database or so. But this entry has a expire time.
How is this expire time updated? SER updates it upon receiving another SIP REGISTER or OPTIONS messages?
the expiry time will be updated on the next successful REGISTER from the client.
Keep alive messages (CRLF or OPTIONS) do not update the contact.
regards klaus