MeetMe (dialplan application)

13.44. MeetMe (dialplan application) ( Back to Tutorials Page )

1. MeetMe - this application allows you to create conference

NOTE: This application is valid for Asterisk version 1.0.9 and above.

Syntax:

MeetMe([confno][,[options][,pin]])

List with the possible options

'm' - The conference is in so called monitor mode ( Only listen, no talking)
't' - The conference is in talk mode ( Talk only, no listening)
'T' - Turns on the talker detection, it sends information to the manager interface and meetme list.
'i' - Announce who is joining/leaving the conference.
'p' - User can exit conference by pressing the # key.
'X' - User can exit conference by entering a single valid extensions ( ${MEETME_EXIT_CONTEXT} ), if this variable is not set - uses extension in current context.
'd' - Dynamically adds conference (Can not set pin for the conference).
'D' - Dynamically adds conference (Can set pin for the conference).
'e' - Selects first empty conference
'E' - Selects first empty pinless conference
'v' - The conference is in video mode.
'r' - If this option is selected, the conference conversation will be recorded in format ${MEETME_RECORDINGFORMAT} and saved as ${MEETME_RECORDINGFILE}.
'q' - Disable the enter/leave sounds.
'C' - On enter announce how many users are in the conference.
'M' - When there is only one user in the conference, music on hold will be played.
'x' - Close conference when last marked user exits
'w' - Wait until the marked user to enters the conference
'b' - Run AGI script set in the ${MEETME_AGI_BACKGROUND} variable, the default script is : conf-background.agi
Note: This works only with Zap channels in the same conference)

's' - Enter menu (user and administrator) when *-key is pressed
'a' - Set admin mode.
'A' - Set marked mode.
'P' - Always ask for pin even if it is specified.

List of all used variables

${MEETME_RECORDINGFILE} - What will be the filename for the recorded conference ( option 'r' ).
${MEETME_RECORDINGFORMAT} - Recording format (gsm, wav, ...).
${MEETME_EXIT_CONTEXT} - The context for exit out from conference.
${MEETME_AGI_BACKGROUND} - AGI script for the conference ( ZAP only ).
${MEETMESECS} - Number of seconds a user participated in conference

Purpose and usage

This application is used primary for creating so called conference 'rooms'.

Below, we will give you an example.

Prerequisites

To use this application you need a working Asterisk PBX with registered users in iax.conf, sip.conf or mgcp.conf(It depends on which protocol you would like to use) and made extensions.

To see how the application works we recommend to use our IAX softphone Idefisk. You can download it from here. Please also read our tutorial to learn how to configure it to work with Asterisk PBX.

Asterisk PBX configurations

NOTE: This is only an example of what for you can use this application. Of course you can use it and for other things.

iax.conf Configurations

We need two registered users in iax.conf file. This is because we are going to use the IAX2 protocol. If you want to use other protocol such as SIP or MGCP, you have to do the configurations below respectively in sip.conf or mgcp.conf.

So, we have registered the users:userA and userB.

Type=friend means that this user can make and receive calls. Host=dynamic means that the IP is not static but dynamic through a DHCP server. Allow=all means that the line which this user will use, could support all audio codecs. Context=training - this shows that this user is working with the extensions in this context of the configuration file extensions.conf.

Now lets add and one sip user.

sip.conf Configurations

We need one registered users in sip.conf file. This is because we want to test and the SIP protocol.

So, we have registered the user sip_user.

Type=friend means that this user can make and receive calls. Host=dynamic means that the IP is not static but dynamic through a DHCP server. Allow=all means that the line which this user will use, could support all audio codecs. Context=training - this shows that this user is working with the extensions in this context of the configuration file extensions.conf.

meetme.conf Configurations

In order create conference room we have to configure it in the meetme.conf (look the picture below):

For this tutorial we are going to use meetme room number 1234, it will have also and PIN code for access (1111), and PIN code for the conference administrator (2222). We just follow the standard template:

conf => conference number,PIN,Administrator PIN

Now we have only to add some extensions in the extensions.conf

extensions.conf Configurations

Now lets take a look at the extensions.conf file.

On the picture above you can see our extensions.conf file.

[training]

exten => 1234,1,Goto(conf,1)

exten => conf,1,Set(MEETME_RECORDINGFILE=/tmp/Tutorial-${TIMESTAMP})
exten => conf,2,Meetme(1234|sr)
exten => conf,3,Hangup()

Finally, in order to be sure that the Asterisk PBX will hang up the line after the conversation is over, it is a good idea to make an extension for hanging up the line.

2. Screenshots of what you can see on the CLI of the Asterisk PBX

3. Additional information

For more information about extensions.conf you can check here.
For more information about iax.conf you can check here.
For more information about sip.conf you can check here.

This application is tested with our IAX softphone Idefisk. You can download it from here. For more information about this softphone please read our tutorial.

If you would like to test this application with the SIP channel you can read our tutorials about the SIP Softphones to learn how to configure them to work with Asterisk PBX