[asterisk-bugs] [Asterisk 0014928]: sip unregister CLI command doesn't send register invite with expire=0 to remote client.

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=14928 
====================================================================== 
Reported By:                licedey
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   14928
Category:                   Channels/chan_sip/Registration
Reproducibility:            always
Severity:                   trivial
Priority:                   normal
Status:                     new
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.1 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-04-18 03:02 CDT
Last Modified:              2009-06-15 15:03 CDT
====================================================================== 
Summary:                    sip unregister CLI command doesn't send register
invite with expire=0 to remote client.
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.

====================================================================== 

---------------------------------------------------------------------- 
 (0106415) kpfleming (administrator) - 2009-06-15 15:03
 https://issues.asterisk.org/view.php?id=14928#c106415 
---------------------------------------------------------------------- 
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. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-06-15 15:03 kpfleming      Note Added: 0106415                          
======================================================================