Using CM as external directory for CME

Unanswered Question
Oct 22nd, 2009
User Badges:

Hi all,


It is mentioned in the CME Admin Guide, that if we want to use CM as External Directory for CME, we need to register the MAC address of the CME IP phones to the CM.


My question is : If the CME users just want to browse the CM directory but doesn't need to be listed in the CM directory, do we still need to register the CME IP phones to the CM ?


Because registering the CME ip phones to the CM means we need more extra licenses right ?


Thanks in advance


Regards,

Regi

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 3 (2 ratings)
Loading.
Rob Huffman Thu, 10/22/2009 - 05:29
User Badges:
  • Super Blue, 32500 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 IP Telephony, Unified Communications

Hi Regi,


The phones will not actually register with CUCM in this model so no licenses should be required :)


To enable an external directory resource on supported Cisco Unified IP phones and disable local directory services on those same phones, perform the following steps.


Prerequisites

To use a Cisco Unified Communications Manager directory as an external directory source for Cisco Unified CME phones, the Cisco Unified Communications Manager must be made aware of the phones. You must list the MAC addresses of the Cisco Unified CME phones in the Cisco Unified Communications Manager and reset the phones from the Cisco Unified Communications Manager. It is not necessary for you to assign ephone-dns to the phones or for the phones to register with Cisco Unified Communications Manager.


Restrictions

Provisioning of the directory URL to select an external directory resource disables the Cisco Unified CME local directory service.


SUMMARY STEPS

1. enable


2. configure terminal


3. telephony -service


4. url {directory | service} url ***something like http://172.16.242.240/CCMCIP/xmldirectory.asp for CCM 4.x or


url directories http://x.x.x.x:8080/CiscoWebs/IPPhoneservices/CCMIP/xmldirectory.asp for CUCM 5.x,6.x or 7.x



5. end



From this good CME doc;


http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/admin/configuration/guide/cmedirs.html#wp1015876



Hope this helps!

Rob


regi_firnanda Thu, 10/22/2009 - 18:45
User Badges:

Hi Rob,


Thanks for the reply :)


I just want to clarify one last thing. How can I list the the MAC address of the CME phones in the CM.


Is it like adding a new IP phone (through Device > Phones > Add New) ? Because, if the answer is yes, doesn't it mean that it will consume ip phone licenses.


Thanks again.


j.huizinga Fri, 10/23/2009 - 04:12
User Badges:
  • Silver, 250 points or more

CME and Callmanager don't share phones. They can however speak with each other using H323 GW configuration on CM and dial-peer configuration on CCME.

shane.orr Mon, 10/26/2009 - 11:08
User Badges:
  • Silver, 250 points or more

It is my understanding that the reason you can't just point a CME Phones to CUCM directory is is becuase the CUCM requires the LOCALE to be specified during the lookup and if an unknown device makes a lookup request it will error out. The workaround has been to add the phone in call manager even though the CME phone is not actually registering to call manager so it will satisfy the requirement of having a LOCALE. Now this workaround has become less attractive since the implementation of DLU's for licensing. So to answer your question above, the answer is yes it will take up a license per phone that wants to use CUCM for it's idle URL. For customers that have needed this functionality and is willing to pay for it I have implemented a 3rd party URL Dirctectory that in my few cases queried AD for the Name/Extension output.

regi_firnanda Mon, 10/26/2009 - 19:45
User Badges:

Thanks for the info Shane.


So, this means that I have to buy 2 types of licenses for each CME's IP Phones (for CME and for CM) just to be able to browse the CM directory. Hhmmmm...






shane.orr Tue, 10/27/2009 - 10:49
User Badges:
  • Silver, 250 points or more

Yes, it would appear to be the case for this particular solution/workaround.

Actions

This Discussion