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

[Asterisk Bug Tracker]

The following issue has been UPDATED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=14928 
====================================================================== 
Reported By:                licedey
Assigned To:                russell
====================================================================== 
Project:                    Asterisk
Issue ID:                   14928
Category:                   Channels/chan_sip/Registration
Reproducibility:            always
Severity:                   trivial
Priority:                   normal
Status:                     closed
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.1 
SVN Revision (number only!):  
Request Review:              
Resolution:                 no change required
Fixed in Version:           
====================================================================== 
Date Submitted:             2009-04-18 03:02 CDT
Last Modified:              2009-06-15 15:44 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.

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

---------------------------------------------------------------------- 
 (0106421) russell (administrator) - 2009-06-15 15:44
 https://issues.asterisk.org/view.php?id=14928#c106421 
---------------------------------------------------------------------- 
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. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-06-15 15:44 russell        Note Added: 0106421                          
2009-06-15 15:44 russell        Status                   new => resolved     
2009-06-15 15:44 russell        Resolution               open => no change
required
2009-06-15 15:44 russell        Assigned To               => russell         
2009-06-15 15:44 russell        Status                   resolved => closed  
======================================================================