[asterisk-bugs] [JIRA] (ASTERISK-23065) On Asterisk start, device state is INVALID for previously registered PJSIP endpoints, despite re-registrations
Rusty Newton (JIRA)
noreply at issues.asterisk.org
Mon Dec 23 19:07:03 CST 2013
[ https://issues.asterisk.org/jira/browse/ASTERISK-23065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rusty Newton updated ASTERISK-23065:
------------------------------------
Description:
*Reproduction and observation:*
* Register an endpoint to Asterisk for the first time. (or wipe AstDB and then register). The Device state will be "NOT_INUSE".
* Stop and start Asterisk. Device state shows "INVALID" for the endpoint.
* After the endpoint re-registers, we continue to show "INVALID" for the endpoint.
* Using the endpoint to dial an extension in dialplan, results in appropriate state changes (INUSE, RINGING, etc) and after hanging up, it ends up at "NOT_INUSE"
* If you restart a phone and the phone unregisters, then Asterisk will make a state change to "UNAVAILABLE" and then "NOT_INUSE" after registration, which seems appropriate.
*Notes:*
In testing this, I notice that OPTIONS for the purpose of qualification do not get sent out unless the state is something other than INVALID. Though this is erratic and with a few tries I can reproduce endpoints in a "NOT_INUSE" state that don't have OPTIONS being generated for them.
*Debug:*
* cli_comment_output.txt contains "pjsip show endpoints" output after an initial registration of the phones, where the astdb had been wiped, plus output after a restart of Asterisk (stop and then start) where the AstDB info still exists for the previous registrations.
* full_initial_reg.txt contains the full log from the initial run
* full_after_restart_rereg.txt contains the full log from the restart where I wait for the endpoints to re-register
was:
*Reproduction and observation:*
* Register an endpoint to Asterisk for the first time. (or wipe AstDB and then register). The Device state will be "NOT_INUSE".
* Stop and start Asterisk. Device state shows "INVALID" for the endpoint.
* After the endpoint re-registers, we continue to show "INVALID" for the endpoint.
* Using the endpoint to dial an extension in dialplan, results in appropriate state changes (INUSE, RINGING, etc) and after hanging up, it ends up at "NOT_INUSE"
* If you restart a phone and the phone unregisters, then Asterisk will make a state change to "UNAVAILABLE" and then "NOT_INUSE" after registration, which seems appropriate.
*Notes:*
In testing this, I notice that OPTIONS for the purpose of qualification do not get sent out unless the state is something other than INVALID. Though this is erratic and with a few tries I can reproduce endpoints in a "NOT_INUSE" state that don't have OPTIONS being generated for them.
> On Asterisk start, device state is INVALID for previously registered PJSIP endpoints, despite re-registrations
> --------------------------------------------------------------------------------------------------------------
>
> Key: ASTERISK-23065
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-23065
> Project: Asterisk
> Issue Type: Bug
> Components: Core/General, Resources/res_pjsip
> Affects Versions: 12.0.0
> Environment: SVN-branch-12-r404531
> Reporter: Rusty Newton
> Severity: Minor
> Attachments: cli_command_output.txt, full_after_restart_rereg.txt, full_initial_reg.txt, pjsip.conf.txt
>
>
> *Reproduction and observation:*
> * Register an endpoint to Asterisk for the first time. (or wipe AstDB and then register). The Device state will be "NOT_INUSE".
> * Stop and start Asterisk. Device state shows "INVALID" for the endpoint.
> * After the endpoint re-registers, we continue to show "INVALID" for the endpoint.
> * Using the endpoint to dial an extension in dialplan, results in appropriate state changes (INUSE, RINGING, etc) and after hanging up, it ends up at "NOT_INUSE"
> * If you restart a phone and the phone unregisters, then Asterisk will make a state change to "UNAVAILABLE" and then "NOT_INUSE" after registration, which seems appropriate.
> *Notes:*
> In testing this, I notice that OPTIONS for the purpose of qualification do not get sent out unless the state is something other than INVALID. Though this is erratic and with a few tries I can reproduce endpoints in a "NOT_INUSE" state that don't have OPTIONS being generated for them.
> *Debug:*
> * cli_comment_output.txt contains "pjsip show endpoints" output after an initial registration of the phones, where the astdb had been wiped, plus output after a restart of Asterisk (stop and then start) where the AstDB info still exists for the previous registrations.
> * full_initial_reg.txt contains the full log from the initial run
> * full_after_restart_rereg.txt contains the full log from the restart where I wait for the endpoints to re-register
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the asterisk-bugs
mailing list