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 2017/11/13 11:23:01 UTC
[jira] [Commented] (OPENMEETINGS-471) Asterisk rooms context
[ https://issues.apache.org/jira/browse/OPENMEETINGS-471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16249415#comment-16249415 ]
Maxim Solodovnik commented on OPENMEETINGS-471:
-----------------------------------------------
I understand this reply might be too late, BUT would it work for {{EXTEN}} of variable length?
Right now {{EXTEN}} == ROOM_PREFIX concat ROOM_ID
So all below are valid {{EXTEN}}s (ROOM_PREFIX == 400):
* 4001
* 40011
* 400111
* ............
> 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: 4.0.1
>
>
> 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.4.14#64029)