Step by Step guide for integrating CUCM with Conductor

Integrating cisco CUCM with Telepresence conductor

What is Ad-hoc conferencing?

                Creating conference by pressing conference button, merge, join on the end point is called as ad-hoc conferencing.

Rendezvous conferencing?

                A rendezvous conferencing is when dialing a conference bridge number directly by all the endpoints instead one adding other to conference.

In ad-hoc conferencing:

They use both xml rpc messaging.

The destination for these sip and xml rpc messaging (to conductor) is configured by configuring a bridge number in the unified cm.

This bridge number is then assigned to media resource group, and then media resource group is assigned to media resource group list and then finally this MRGL is assigned to a Device.

In Rendezvous conferencing:

For rendezvous conferencing, an alias will be configured in conductor, a dedicated sip trunk will be created in UCM with destination as rendezvous location’s IP which is configured in conductor. Then create a sip router pattern to route calls to that sip trunk.

Each conference bridge is a physical device.

Conductor 3.0 supports Telepresence MCU and Telepresence server.

For the auto dialed participants to work, SIP settings must be configured in the Telepresence server!!

In configuration à SIP   (to send the signaling messages)

Configuration overview for conferences in Conductor:

1.       Create conference bridge

2.       Add required conference bridges in bridge pool

3.       Add pools in service preference ( it’s a prioritized order for routing calls to TP servers)

4.       Add these service preferences in templates.

5.       Add these templates in conference aliases.

Create additional IP addresses for ad-hoc conferences in system ip address fields. They should be on the same subnet.

For creating ad-hoc conference:

1.       Create a template

2.       Create a location for ad-hoc conference

3.       In the location configuration select type as ad-hoc or both

4.       Select the ad-hoc template created above.

For creating rendezvous conference:

1.       Create a rendezvous template

2.       Create a conference alias with regular expressions like . * @ etc. you can use the accurate number also. It should be in the pattern, <pattern>@domain:port

For feasibility give like this <pattern>@.*

3.       Select the rendezvous template here.

Auto dialed participants:

1.       Give a name

2.       Select the correct template here. (the rendezvous template should be selected)

3.       Participant address should contain ip address of the CUCM. ( EXT@<CUCM IP>)

Rendezvous location:

1.       Select type as rendezvous

2.       Select rendezvous location ip created in additional ip address.

3.       In the Trunk 1 ip addresses give the IP of CUCM   (This is the SIP TRUNK Config)

Auto-dialed participant not connected If the auto-dialed participant does not get called: 

1. On the TelePresence Conductor go to Conference configuration > Auto-dialed participants and verify that the settings for the auto-dialed participant are correct, specifically check that: l Participant address is correct. l Conference name match will match a valid conference. State of the participant is Enabled.

2. On the TelePresence Conductor go to Status > Logs > Event Log > All events to check whether the TelePresence Conductor tried to call the auto-dialed participant.

3. On the TelePresence Conductor ensure that all conference bridge pools, which can be used by this autodialed participant, have a Location set. To do this:

a. Go to Conference configuration > Auto-dialed participants and check what the name of the associated conference template is.

b. Go to Conference configuration > Conference templates and check what the name of the associated Service Preference is.

c. Go to Conference configuration > Service Preference and check what the names of the associated Conference bridge pools are.

Cisco TelePresence ConductorwithUnifiedCM Deployment Guide (XC3.0)     Page70of91

Troubleshooting

 d. Go to Conference configuration > Conference bridge pools, select each Conference bridge pool identified above and check that it has a Location other than None set for the Location field.

4. On the TelePresence Conductor go to Conference configuration > Locations and verify that the Conference type is Rendezvous l the SIP trunk settings for out-dial calls are set correctly to route the auto-dialed participant back to Cisco VCS.

Troubleshooting:

Check the SIP configuration in TP Server.

Check the location set to correct.

Check the name of the auto dialed participant

Check the IP address of the CUCM is correctly configured in the location of rendezvous.