Summary:ASTERISK-13981: sip unregister CLI command doesn't send register invite with expire=0 to remote client.
Reporter:Alisher (licedey)Labels:
Date Opened:2009-04-18 03:02:37Date Closed:2011-06-07 14:10:05
Versions:Frequency of
Description:It's possible to set expire time to 0 using CLI command "sip unregister" CLI for Asterisk sip peers, but it's not affected on active registered peers. Also in order to unregister peer/outbound sip trunk asterisk should transmit register invite with expire=0 in contact field to outbound trunk. But currently it doesn't.
Comments:By: Leif Madsen (lmadsen) 2009-05-27 11:11:14

This doesn't really seem like a feature request, but rather a bug in the way the unregister command words. I'm upgrading this to a trivial severity.

By: Kevin P. Fleming (kpfleming) 2009-06-15 15:03:40

These are two entirely different issues and should be addressed separately.

For outbound registrations, a manual 'unregister' should send a REGISTER (not INVITE) with the expire time set to immediate, so that Asterisk will be unregistered from the other SIP server.

For inbound registrations, I am not aware of any SIP request or response that could be sent to the endpoint that registered to notify it that its registration has been forcibly expired. Once we send a '200 OK' with an expiration time, the registering endpoint will assume (rightly so) that its registration will be valid until that time has passed. If it wants to query for the status of its registration it could do so, and possibly learn that it has been manually expired, but I doubt any existing endpoints do that.

By: Russell Bryant (russell) 2009-06-15 15:44:55

I'm closing out this issue.

As Kevin explained, there isn't really anything we can send when we forcibly expire an incoming registration.

Regarding expiration of outbound registrations, we currently have no feature that lets you do that.  The unregister CLI command is only for forcing the expiration of incoming registrations.