| Summary: | ASTERISK-24411: [patch] Status of outbound registration is not changed upon unregistering. | ||
| Reporter: | John Bigelow (jbigelow) | Labels: | |
| Date Opened: | 2014-10-11 22:53:26 | Date Closed: | 2014-10-31 11:23:15 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | Resources/res_pjsip_outbound_registration |
| Versions: | SVN 12.6.0 13.0.0-beta2 | Frequency of Occurrence | Constant |
| Related Issues: | |||
| Environment: | Asterisk 13 branch @ r424940, PJSIP | Attachments: | ( 0) unregister-patch1.txt |
| Description: | Executing the AMI action {{PJSIPUnregister}} or CLI command {{pjsip send unregister}} on a registered outbound registration does properly send a REGISTER message with an expiration of 0 and unregisters. However the status of the outbound registration is *not* changed to {{Unregistered}}. Upon receiving any 200 OK response whether for registering or unregistering, the outbound registration status is always set to {{Registered}}.
The attached patch sets the status of the outbound registration to reflect when it has been unregistered. Since the registration is unregistered rather than stopped, the registration schedule remains active as before. The patch also updates the documentation of both the AMI and CLI commands. | ||
| Comments: | By: John Bigelow (jbigelow) 2014-10-14 10:41:25.672-0500 *Note*: When resolved, the testsuite test corresponding to https://reviewboard.asterisk.org/r/4077/ needs to be updated to remove the {{expectedResult}} property from the tests YAML file. | ||