How do you configure Meet-Me Conferences in the CUCM v8.6? I created a meet-me number and put it in the same partition as all the phones are in, and set it to nonsecure. However, when I call the number it gives me a fast busy. I need to know how to set this up and also put a PIN on the conference. Does anyone know how to do this? Thanks!
This may be a simple question but when using MeetMe Line (MML), you must open the MML using a Cisco IP phone registered to the CUCM cluster. You can't just dial the MeetMe number to open the line. Internal and external parties joining the MeetMe conference won't be able to call in (fast busy) until someone opens the MML.
If you are using the default softkey setup then you can open the MML by going off hook on one of your registered IP phones. When the softkey pane updates, choose "More" and then choose "MeetMe". You will hear a tone and be prompted to enter the MeetMe number. Enter the number, and if everything else is setup correctly, you will be in business.
You can also use UCCX (unified contact center express) to set PINs to your meet-me sessions. You create a script where the people dials the PIN and if it is correct, then you redirect the call to the meet-me number. Also with scripts you can assign a different password everytime you will start a meet-me session (using database querys or looking for the password through an XML document)
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
[toc:faq]CUCM Database Replication is an area in which Cisco customers
and partners have asked for more in-depth training in being able to
properly assess a replication problem and potentially resolve an issue
without involving TAC. This document discusse...