CUCM 14SU3 New Feature Auto Provision of Cisco Jabber Devices As Part Of LDAP

In Unified Communications Manager, you can auto provision the Webex App or Cisco Jabber devices when new LDAP users are synchronized from Microsoft Active Directory. The Write back to LDAP option allows you to write the Primary DN chosen from Unified CM back to the LDAP server. LDAP attributes available for write back are: telephoneNumber, ipPhone, and mobile.

User Interface Updates
To support this feature, the following menu items are updated in the Cisco Unified CM Administration user interface:

  • In the System > Service Parameters Configuration page, a new service parameter Provision Jabber Device As Part Of LDAP Sync is added under “Cisco DirSync” service, to enable auto provisioning of Cisco Jabber devices:
  • If the Provision Jabber Device As Part Of LDAP Sync service parameter is enabled and you have selected Microsoft Active Directory in the System > LDAP > LDAP System Configuration page, a new section Jabber Endpoint Provisioning is displayed on the LDAP Directory Settings page.

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/rel_notes/14_0_1/SU3/cucm_b_release-notes-for-cucm-imp-14su3.html#Cisco_Concept.dita_2f92e619-5b7c-4478-9b9f-81f474813cb1

How to download a Music on Hold (MoH) file from Cisco Call Manager server

Procedure

  1. Establish a Secure Shell (SSH) connection to the Call Manager, where the MoH file is
    uploaded.
  2. Check the list of all MoH files available on the server with this command:

admin:file list activelog /mohprep
CiscoMOHSourceReport.xml SampleAudioSource.alaw.wav
SampleAudioSource.g729.wav SampleAudioSource.ulaw.wav
SampleAudioSource.wb.wav SampleAudioSource.xml
SilenceAudioSource.alaw.wav SilenceAudioSource.g729.wav
SilenceAudioSource.ulaw.wav SilenceAudioSource.wb.wav
SilenceAudioSource.xml ToneOnHold.alaw.wav
ToneOnHold.g729.wav ToneOnHold.ulaw.wav
ToneOnHold.wb.wav ToneOnHold.xml
dir count = 0, file count = 16
admin:

  1. Download the required file with this command:
    I used Freeftpd SFTP server (Third Party)

admin:file get activelog /mohprep/*.wav
Please wait while the system is gathering files info …
 Get file: /var/log/active/mohprep/SampleAudioSource.alaw.wav

 Get file: /var/log/active/mohprep/SampleAudioSource.g729.wav

 Get file: /var/log/active/mohprep/SampleAudioSource.ulaw.wav

 Get file: /var/log/active/mohprep/SampleAudioSource.wb.wav

 Get file: /var/log/active/mohprep/SilenceAudioSource.alaw.wav

 Get file: /var/log/active/mohprep/SilenceAudioSource.g729.wav

 Get file: /var/log/active/mohprep/SilenceAudioSource.ulaw.wav

 Get file: /var/log/active/mohprep/SilenceAudioSource.wb.wav

 Get file: /var/log/active/mohprep/ToneOnHold.alaw.wav

 Get file: /var/log/active/mohprep/ToneOnHold.g729.wav

 Get file: /var/log/active/mohprep/ToneOnHold.ulaw.wav

 Get file: /var/log/active/mohprep/ToneOnHold.wb.wav
done.
Sub-directories were not traversed.
Number of files affected: 12
Total size in Bytes: 18533494
Total size in Kbytes: 18099.115
Would you like to proceed [y/n]? y
SFTP server IP: 10.26.22.50
SFTP server port [22]:
User ID: mzougari
Password:
Download directory: /

…………
Transfer completed.
admin:

The custom announcement wav file being uploaded must also be uploaded to each CUCM server in the cluster

Jabber Client UDS Authentication and Configuration version 12.9 and Earlier

GET UDS Version:
2017-06-19 14:54:53,856 INFO [0x00001afc] [etutils\src\http\CurlHttpUtils.cpp(1106)] [csf.httpclient] [csf::http::CurlHttpUtils::configureEasyRequest] – —– Configuring request #27 GET https://cucmpub.ciscoliveus.net:8443/cucm-uds/version
GET UDS Version Response:
2017-06-19 14:54:54,016 INFO [0x00001afc] [ls\src\http\BasicHttpClientImpl.cpp(478)] [csf.httpclient] [csf::http::executeImpl] – —– HTTP response code 200 for request #27 to https://cucmpub.ciscoliveus.net:8443/cucm-uds/version
XML is Parsed and UDS version is returned:
2017-06-19 14:54:54,016 DEBUG [0x00001afc] [vices\impl\uds\UdsResponseParser.cpp(72)] [csf.uds] [CSFUnified::UdsResponseParser::parseXmlDocument] – Found key (version) with value (11.5.1).

Continue reading “Jabber Client UDS Authentication and Configuration version 12.9 and Earlier”

Unified CM UDS-to-LDAP Proxy


This method of corporate directory access relies on the Unified CM UDS service resolving or proxying directory searches against the corporate LDAP directory rather than using the local user directory. UDS-to-LDAP proxy allows Jabber users to search against the entire corporate directory rather than being limited by the local Unified CM cluster end-user database.

This enables Jabber clients to search a corporate directory that exceeds the
number of users supported within Unified CM

From Cisco Live
From Cisco Live

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/srnd/collab12/collab12/directry.html#marker-1260619

SOURCE Cisco Systems, Inc

Cisco Unified CM User Data Service (UDS)

UDS provides a contact source API that can be used by Jabber over Cisco Expressway mobile and remote access (MRA) for the contact source.The UDS contact source uses the Unified CM end user table information to provide a contact lookup service.
Beginning with Cisco Unified CM 11.5, the UDS-to-LDAP Proxy feature can also be used for contact searches. When enabled, contact searches are still handled by UDS but are proxied to the corporate LDAP directory, with UDS relaying results back to the Jabber client. This enables Jabber clients to search a corporate directory that exceeds the maximum number of users supported within Unified CM.
The UDS contact service is always used for remote Jabber clients connected over MRA access and it is an optional contact service for clients on the corporate network. You can populate the UDS contact source data by using the Unified CM web interface (by creating end users),by using the LDAP sync function to Active Directory or other supported LDAP source, or by using the UDS-to-LDAP Proxy function.

Jabber Phone Only Mode

While the UDS service runs on all nodes in the Unified CM cluster, when configuring DNS SRV records for Unified CM UDS service, administrators should configure records for resolution to Unified CM subscriber nodes only. This ensures that client interaction with the UDS service avoids the publisher node and instead distributes the load across call processing nodes within the cluster.

Continue reading “Cisco Unified CM User Data Service (UDS)”

Cisco Jabber New parameters

refer_BIB_Recorder
Applies to Cisco Jabber desktop clients In deployments with Unified Communications Manager Release 12.5(1) and later, Jabber can support Unified CM’s on-demand recording using Jabber’s Built-In Bridge (BiB). By default, if the user joins a conference call that has an external bridge set up to record calls, Jabber uses that external bridge for recording.
Some organizations might prefer all recording to use the Jabber BiB for compliance reasons. You can use the Prefer_BIB_Recorder parameter to enforce recording on the Jabber BiB. The allowed values are:
• true—Use the Jabber BiB recorder for all calls.
• false (default)—If available, record on the external bridge.

Continue reading “Cisco Jabber New parameters”

Device Location Discovery Methods in Cisco Emergency Responder: SNMP vs CDP

CDP (Cisco Discovery Protocol) :Determine the exact location
SNMP:Discover the phones

Emergency Responder uses the following methods (in priority order) to
identify an emergency caller’s location:

  1. Switch port discovery .The more specific location discovery
  2. Access point association
  3. IP subnet
  4. Static DN assignment
  5. Default route
Continue reading “Device Location Discovery Methods in Cisco Emergency Responder: SNMP vs CDP”

LWM – CUCM Disk Partitions

LogPartitionLowWaterMarkExceeded alarm is generated when the used disk space percentage in Log partition reaches the configured Low WaterMark value. This alarm should be taken as an early notification for an administrator to clean up the disk space.
CUCM won’t start an automated cleanup process until the High WaterMark value will be reached.

show status command will list you all the partitions and its usage (See the image below)

These are the three partitions created in an UC application like CUCM during installation.

Disk/active – holds the current version and its configuration
Disk/inactive – contains the previous version in case you need to swithc after an upgrade for any reason
Disk/logging – this is also called common partition which holds all the enabled log/trace files and also used to store the upgrade iso file during upgrade temporarily

Continue reading “LWM – CUCM Disk Partitions”