Page 504 - Asterisk™: The Future of Telephony

[oreilly]
secret = notvery
deny=0.0.0.0/0.0.0.0
permit= 192.168.1.0/255.255.255.0
read = system,call,log,verbose,command,agent,user,config
write = system,call,log,verbose,command,agent,user,config
For more information on the Asterisk Manager Interface, see Chapter 10.

meetme.conf

MeetMe is one of the more remarkable applications in Asterisk. It allows you to set up
predefined audio conference rooms. This rather simple concept has proven to be ex-
tremely expensive to implement in every other PBX, but what seems like a big deal to
them is simple to Asterisk. Whether by using a dedicated server, or through the use of
a service, Asterisk now delivers this functionality as a standard application.
MeetMe conferences can be created either dynamically, with the d flag in the Dial()
application, or statically in the meetme.conf file. The format for creating conference
rooms is as follows:
conf => conference_number[,pin][,administrator_pin]
All conferences must be defined under the [rooms] section header.
[rooms]
conf => 4569
conf => 5060,54377017
conf => 3389,4242,1337
conf => 333,,2424

mgcp.conf

The Media Gateway Control Protocol (MGCP) has only primitive support in Asterisk.
This is likely due to the fact that SIP has stolen the limelight from every other VoIP
protocol (except IAX, of course). Because of this, you should attempt to use Asterisk’s
MCGP channel in a production environment only if you are prepared to perform ex-
tensive testing, are willing to pay to have features and patches implemented within your
time frames, and have in-house expertise with the protocol.
Having said that, we are not prepared to pronounce MGCP dead. SIP is not yet the
panacea it has been touted as, and MGCP has proven itself to be very useful in carrier
backbone environments. Many believe MGCP will fill a niche or void that has not yet
been discovered, and we remain interested in it.

476 | Appendix D: Configuration Files