[asterisk-bugs] [JIRA] (ASTERISK-23035) ConfBridge with name longer than max (32 chars) results in several bridges with same conf_name

[Iñaki Cívico (JIRA)]

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

Iñaki Cívico commented on ASTERISK-23035:
-----------------------------------------

Yes, I think that should be enough.
Maybe a note about max length in command documentation?

Thanks!
                
> ConfBridge with name longer than max (32 chars) results in several bridges with same conf_name
> ----------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-23035
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-23035
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_confbridge
>    Affects Versions: 12.0.0-beta2
>            Reporter: Iñaki Cívico
>            Severity: Minor
>
> This simple dialplan is used to reproduce issue:
> exten => _X.,1,ConfBridge(${confid})
> where confid is longer than MAX_CONF_NAME (apps/confbridge/include/confbridge.h)
> Each time a call arrives to this point, a new bridge is created with same name (confid truncated to MAX_CONF_NAME length) but different uuid.
> In app_confbridge/join_conference_bridge, ao2_find() searches with full conference name (longer than max length). ao2_find result is always null as bridge has a truncated name, then a new bridge is created with the same name.
> Behavior is extrange resulting in a several calls connected to the same conf but not earing each other. Here is a console trace:
> CLI> confbridge list
> Conference Bridge Name           Users  Marked Locked?
> ================================ ====== ====== ========
> 7e012c4d-9f34-4628-a483-c152ad5       1      0 unlocked
> 7e012c4d-9f34-4628-a483-c152ad5       1      0 unlocked

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