openmeetings-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Clay (JIRA)" <>
Subject [jira] [Commented] (OPENMEETINGS-470) SIP meeting extensions
Date Fri, 15 Feb 2013 02:47:12 GMT


Jeff Clay commented on OPENMEETINGS-470:

when I was testing, the SIP bridge numbers were in sequential order. This makes it very easy
for unwanted users to call into the SIP DID (external phone number) and try to join audio
conferences in a sequential pattern; like 40103, 40104, 40105, etc.. Would it be possible,
instead of using sequential room ID's and appending those to a set prefixed number (40) to
have it randomly generated? Based on your explenation, I would imagine that this is done in
two parts currently; so to keep it simple to implement, instead of having "40" assigned statically,
have it randomly generate a 2 digit integer, assign that to whatever variable "40" is currently
assigned to; then randomly generate 3 digit integer and assign that to room ID? This way,
the room ID's won't be in sequential numeric order and the meetme prefix won't always be 40.
> SIP meeting extensions
> ----------------------
>                 Key: OPENMEETINGS-470
>                 URL:
>             Project: Openmeetings
>          Issue Type: Improvement
>          Components: UI, VoIP/SIP
>    Affects Versions: 2.1 Apache Release
>            Reporter: Jeff Clay
>            Assignee: SebastianWagner
>             Fix For: 3.0 Apache Release
> When using asterisk with realtime/database driven backend, it would be nice if the meetme
conferences weren't in sequential order, and if it would include that information within the
meeting invite and within the web-ui when you join. Since they're created dynamically, and
asterisk uses whatever it reads in the meetme table, then I don't see a reason (at least on
asterisks side) why this can't be implemented. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message