[cisco-voip] Peeking under the hood - hardware conferencing on CUCME (UNCLASSIFIED)

[Girard, Jeffrey T COL RET]

Classification: UNCLASSIFIED
The CUCME System Admin Guide explains how to configure the CUCME, but does not explain the “why” these configuration commands are needed.  I have gone through the “Configuring Conferencing” chapter several times – and am still with questions.

Specifically, I want to understand the reason for the multiple ephone-dns that need to be created and how they are used.  

This is my current assumption:

When the conference initiator presses the Conf softkey to bring in an additional party into the conference, the CUCME recognizes the “hardware” keyword under the telephony-service settings.  Next, the CUCME searches for the next available ephone-dn that is part of the ad hoc conference pool.  Once it finds an open/available ephone-dn, it uses that dn as the source DN to place a call to the desired conference participate.  If the call completes, the hadware DSPs are used to join this new call leg into the conference.

So, how accurate is my assumption?



--------------------------------------------
Dr. Jeffrey T. Girard (Jeff), PhD
Senior Network Engineer / VoIP Engineer - WireMeHappy.com
Senior Network Engineer / Operations Specialist - EnSync Interactive Solutions
reply to: jeffrey.girard at wiremehappy.com
          jeffrey.girard at us.army.mil
(845)977-0363 (home office)
(845)764-1661 (mobile)              
Classification: UNCLASSIFIED