[asterisk-bugs] [JIRA] (ASTERISK-22817) ooh323 reload command doesn't send request for registreation to gk

Mon Nov 4 14:32:05 CST 2013

    [ https://issues.asterisk.org/jira/browse/ASTERISK-22817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=211492#comment-211492 ] 

Alexander Anikin commented on ASTERISK-22817:
---------------------------------------------

Hello,

ooh323 support reload on cli command 'ooh323 reload' not by 'module reload chan_ooh323.so'. 
I will produce patch here to support 'module reload' cmd also.

Gatekeeper reregistration on reload is supported also beginning from 11 version,
please use this version or newer.

> ooh323 reload command doesn't send request for registreation to gk
> ------------------------------------------------------------------
>
>                 Key: ASTERISK-22817
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22817
>             Project: Asterisk
>          Issue Type: Information Request
>      Security Level: None
>          Components: Addons/chan_ooh323
>    Affects Versions: 1.8.22.0
>            Reporter: sam
>            Assignee: Alexander Anikin
>
> ooh323 asterisk gw is registered in cisco gk with e164=2. ooh323.conf is changed and another e164=3 is added to it. after running ooh323 reload command, ooh323 doesn't send request for new registration to gk. so gk doesn't know the new e164=3 and can not route calls with this number.
> if i unload and load ooh323 module, it sends new registration request to gk and  it works fine. but loading and unloading module, disconnect all current ooh323 calls and it's not good at all for me.
> any idea what should i do to apply my new configuration while i have active ooh323 calls?

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