You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openmeetings.apache.org by "Maxim Solodovnik (JIRA)" <ji...@apache.org> on 2013/11/11 06:42:22 UTC
[jira] [Updated] (OPENMEETINGS-471) Asterisk rooms context
[ https://issues.apache.org/jira/browse/OPENMEETINGS-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maxim Solodovnik updated OPENMEETINGS-471:
------------------------------------------
Fix Version/s: (was: 3.0.0 Apache Release)
3.1.0 Apache Release
> Asterisk rooms context
> ----------------------
>
> Key: OPENMEETINGS-471
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-471
> Project: Openmeetings
> Issue Type: Improvement
> Components: VoIP/SIP
> Affects Versions: 2.1.0 Apache Release
> Reporter: Jeff Clay
> Assignee: Timur Tleukenov
> Priority: Minor
> Fix For: 3.1.0 Apache Release
>
>
> I don't believe that using a database table for the rooms context is necessary, at least for asterisks requirements. The table can be replaced by using the lines below in extensions.conf instead of the db switch.
> [rooms]
> exten=_XXXXXXX,1,MeetMe(${EXTEN},dM)
> exten=_XXXXXXX,n,Hangup
> The _ says that we're matching a pattern, and the X's determine how long of a pattern we're looking for. This example will match any 7 digit number and then go to the MeetMe bridge of that number.
--
This message was sent by Atlassian JIRA
(v6.1#6144)