Integrate Cisco Unity Connection and Cisco Unified Communications Manager
Troubleshooting SCCP + SIP Integrations:
Here is my own take on EMCC:
- Part 1 is better viewed on a large screen (Lesson learnt!)
- Part 2 is lower res and looks good on any device
One for the lab, but here are the Cisco docs:
- Export certs to SFTP for all clusters that will participate
- Consolidate certificates (Only on 1 server)
- Import bulk certs into all clusters
- Create a EMCC template
- Add EMCC devices using template
- Add SIP Trunks to all clusters – EMCC no IP defined – Full mesh
- EMCC Feature Cfg and Intercluster Service Profile
- Cluster View
In summary, if you had Site A and Site B, if youre home site is A and you visit B and logon using EMCC, the phone at B will register to the A cluster as if you were there, however there is a EMCC CSS used, which sends calls via the EMCC SIP Trunk to the ‘visited’ cluster and therefore calls are routed out of this cluster correctly. Slightly confusing!
Also a great video from the wonderful Vik Malhi at Collabcert:
- Add new user to TPS for Conductor purposes
- API Access
More cfg than TPS!
- Maintenance + Option Keys – add release keys
- Users -> Admin Accounts
- Add account for CUCM purposes to add conf bridge later
- Add new IPs for adhoc and rendezvous meetings
- Restart Conductor
- Add conf bridge pool (TP MCU or TPS)
- Bridge pool contains conf bridges
- Create conf bridge with credentials from TPS server (Above)
- Service Preferences (Ordered list of bridge pools)
- Conference Template – sets parameters of conference
- Create one for adhoc and one rendezvous
- Add conference alias – point to conference template
- Add a location (Puts it all together!)
Now we go to CUCM….
- Add a SIP Trunk with a Route Patterns to send conf bridges to Conductor
- 1 for Adhoc and 1 for Rendezvous
- Add conf bridge to CUCM – type is Conductor!
- Use the SIP Trunk for either Adhoc or Conductor
- Add credentials we added from Conductor
- Now we need to add the CFB to a MRG and MRGL
- Add a new admin account to Conductor for TMS purposes
- CMR requires TMS PE to be installed and licenses
- 14.4 TMS to see CMR
- Add Conductor to TMS
This topic describes the Cisco TelePresence Management Suite (TMS) Provisioning Extension features.
TMS Provisioning Extension simplifies scaling of video across the enterprise:
|Provisioning Scale||Simplifies management of up to 100,000 telepresence users across disparate locations and networks Automated user account and phone book creation|
|Intuitive Meetings||Intuitive Collaboration Meeting Rooms (CMRs) Configure personal CMR preferences.|
|Intuitive Scheduling||Extend scheduling capability to everyone. Smart Scheduler simplifies the booking process for single and recurring telepresence meetings.|
|Endpoint Support||Quick deployment with predefined templates Low touch provisioning for C, E, EX, MX, and SX Series endpoints and Cisco Jabber Video for TelePresence and iPad|
The figure shows the main features and benefits of the Cisco TMS Provisioning Extension.
Smart Scheduler is a part of Cisco TMS Provisioning Extension.