Re: CALLID header in SuccessfulAuth manager message

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


2014-09-11 13:48 GMT+02:00 Matthew Jordan <mjordan@xxxxxxxxxx>:

> That wouldn't be sufficient any way. A SIP device can send REGISTER requests
> as often as it wants; the duration of the registration is merely how long
> Asterisk will keep the registration. Devices should send a REGISTER request
> within that period of time, but they can spam them much more often than that
> as well.

Yes exactly:
from Asterisk point of view, re-registration occurs when and only when
a new REGISTER comes in during previous "REGISTER duration", if I may
call it this.

If I'm not mistaken, if you don't forget to also track Unregister
events along Register events, the only missing thing allowing a third
party app to detect re-registration (as defined above) is the
RegistrationDuration data, no matter how useful this knowledge might

Do we agree on that or did I miss something ?

For curiosity's sake, why do you need to detect registrations (and
avoid re-registrations) ?

> _______________________________________________
> asterisk-app-dev mailing list
> asterisk-app-dev@xxxxxxxxxxxxxxxx

asterisk-app-dev mailing list

[Index of Archives]     [Asterisk SS7]     [Asterisk Announcements]     [Asterisk Users]     [PJ SIP]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Linux API]

  Powered by Linux