openmeetings-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maxim Solodovnik (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (OPENMEETINGS-470) SIP meeting extensions
Date Tue, 05 Mar 2013 14:33:14 GMT

     [ https://issues.apache.org/jira/browse/OPENMEETINGS-470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Maxim Solodovnik closed OPENMEETINGS-470.
-----------------------------------------

    
> SIP meeting extensions
> ----------------------
>
>                 Key: OPENMEETINGS-470
>                 URL: https://issues.apache.org/jira/browse/OPENMEETINGS-470
>             Project: Openmeetings
>          Issue Type: Improvement
>          Components: UI, VoIP/SIP
>    Affects Versions: 2.1 Apache Release
>            Reporter: Jeff Clay
>            Assignee: SebastianWagner
>             Fix For: 2.1 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: http://www.atlassian.com/software/jira

Mime
View raw message