CIPTV 1 - Configure Conferencing Device - Configuring Cisco Telepresence MCU

    Hi guys welcome back again, i hope your are enjoying my posts , im doing my best to keep up a good level,

Now today we will going trought the configration of the Cisco Telepresence MCU, we will see about tow differenet section:

• Deploying MCU with VCS
• Deploying MCU with CUCM

Presection:

whe you start off m first thing first you need to powrup your MCU, by default MCU uses DHCP to learn about it TCP/IP informations , 

1. disable dhcp
2. configure a specifi port
3. configure default route 

MCU:> ethertype A auto //set Port A negociation to auto MCU:> ethertype A 100 full //set port A speed to 100 Mbps and duplex to full-duplex mode MCU:> static A 10.13.208.2 255.255.255.0 10.13.208.1   // set ip address + mask + default gateway

now we are ready to login to the MCU web interface using https://@IP_ADRESSS/

• username : admin
• password :blank

• after login in , first thing you want to do is set a password (in the Users Menu)
• DNS configuration

in the DNS configuration page you will set major parametres which are :

• Hostname - System name : this i will also appear in TMS
• Name Server : he DNS name server IP address
• domain name : the domain of th MCU ( ex: collabtut.com )
• Don't forget the Update button to sage the configuration 9 

• Service Activation 

depending on you topology , scenario and your enviroment you will need MCU service up and running , ensure that all the services you intedn to use are enabled by checking the box beside the port number and also ensure that the port numbe used matched the one used on your network.

once you completed thes task, your ares now set to the next section : MCU via VCS

Section 1 : Deploying MCU with VCS

MCU is like any other dvice it going to need a Call control server in this section the call control server is the VCS.

MCU will register to the VCS.

MCU registration:

• Protocles : SIP and/or H.323
• Parametres : 
• Registration Prefix : its used to id the MCU when registaring to VCS so it will not overlap with other divces
•  Service Prefixe :  service prefix identify the service offered by MCU and it should do with a broader range and allow any dialed alias that macthed the SP to be routed to MCU.

a special parametrs to configure when the user dials an unknow alas for a conference , better not to drop the caller is to allow the conference to be adhocaly created. ( inveted the name) using the 'incoming calls to unknow conference or auto attendants ----setto--> Creats new adhoc conference '


to be more specifice about the protocole configuration here is the follwing table:

Protocole H.323	Protocole SIP
Gatekeeper Enabled	SIP Enabled Registrar
Gatekeeper IP Adress : VCS IP ADDRESS	SIP Domain : better to be the same domain of VCS
Port Association : is the one confired in the presection	Standard SIP
H.323 Alias to be register with : MCU@domain.com	Username : MCU alias “MCUCONF”
Prefix Registration	SIP Proxy IP address : VCS IP ADDRESS
Service Prefix
Check Allow Numerid Reg

*: need to look deep into SIP-based conference

Section 2 : Deploying MCU with CUCM

With CUCM MCU can be used only for rendez-vous and adhoc confeernce, no more scheduled conference

When MCU uses Media port reservation