[asterisk-bugs] [JIRA] (ASTERISK-22094) res_sip - transport config object can't be modified on module reload - let the user know

[Rusty Newton (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-22094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rusty Newton updated ASTERISK-22094:
------------------------------------

    Status: Open  (was: Triage)
    
> res_sip - transport config object can't be modified on module reload - let the user know
> ----------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-22094
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22094
>             Project: Asterisk
>          Issue Type: Improvement
>          Components: Resources/res_sip
>    Affects Versions: SVN, 12
>         Environment: Trunk
>            Reporter: Rusty Newton
>
> During run-time the output from a "module reload res_sip.so" command will include:
> {noformat}
> [Jul  4 18:11:03] DEBUG[30972]: res_sorcery_config.c:269 sorcery_config_internal_load: Could not create an object of type 'transport' with id 'simpletrans' from configuration file 'res_sip.conf'
> {noformat}
> From what I understand this is because the transport configuration inherently can't be refreshed by only a module reload. A complete Asterisk restart is needed.
> If you don't know this, then seeing that message when troubleshooting configuration can send you down a wild goose chase.
> If possible let's add a debug message (or modify the one above if that makes more sense) on module reload of res_sip.so to let the user know that transport configuration can only be reloaded on a complete restart of Asterisk. 

--
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