Mar 26

Cisco Jabber: Save Chat History to Outlook

To enable Cisco Jabber Chats to be saved to Outlook, you ‘ll need to modify the jabber-config.xml file. A subfolder called “Cisco jabber Chats” is created under the ‘Inbox’ folder in Outlook.

Note: Just like with emails, users are able to delete the chat folder and any chat conversation located inside. The deleted chat conversation will sit in the Deleted Items, when deleted from the Deleted Items, the chat conversation will site in the Recovered Deleted Items bin until Exchange purges the items.

Jabber for Windows 10.6 supports MS Exchange 2010 and Exchange 2013 and Jabber for Windows 11.0+ supports MS Office 365 as well.

In the example below, CUCM is selected for the authentication service, seeing that most (if not all) Cisco UC Implementation these days are sync’ed with Active Directory.

The Operation Mode “EnabledByPolicy” enables the option in Outlook “Save chat sessions to Cisco Jabber Chats Folder in MS Outlook”, and does not permit users to disable this option. If you wish for the users to enable/disable this feature as required, the Operation Mode  must be “EnabledByDefault”.

Most Exchange Environments have autodiscover enabled and configured, hence the Domain Names (Internal/External) are configured for the Exchange Addresses. If autodiscover is not enabled, simply the enter the Internal/External Hostnames for the Exchange CAS Servers.

 

Jabber-config.xml snippet.
<?xml version=”1.0″ encoding=”utf-8″?>
<config version=”1.0″>
<Options>
<Start_Client_On_Start_OS>true</Start_Client_On_Start_OS>
<SaveChatHistoryToExchangeOperationMode>EnabledByPolicy</SaveChatHistoryToExchangeOperationMode>
<Exchange_UseCredentialsFrom>CUCM</Exchange_UseCredentialsFrom>
<ExchangeAutodiscoverDomain>Internal_Domain_Name</ExchangeAutodiscoverDomain>
<InternalExchangeServer>Internal_Domain_Name</InternalExchangeServer>
<ExternalExchangeServer>External_Domain_Name</ExternalExchangeServer>
</Options>
</config>

Mar 18

Collaboration Systems Release 11 – Updates and Features

Have compiled a highlighted list of enhancements and features new to version 11 for the Cisco Unified Communications suite of products.

Cisco Unified CM Enhancements

Conference Now

Cisco have now closed the gap in the conference bridge market by introducing Conference Now into the CUCM Build. This allows users to create adhoc and scheduled conferences using a unique meeting ID and PIN. The Meeting ID will be tied to the Self-ID of the User. Meeting participants will wait in a lobby and will hear music (can be different stream to that of the standard phone MoH) until the host joins the meeting.

Jabber v11, also includes a single touch for chat/chat groups escalation into a conference now meeting.

Using the Self Care Portal, users can change/reset their conference PIN.CUCM Conference Now

QoS

QoS has been enhanced by including additional parameters in CUCM, allowing administrators to tag/mark audio packets within a video stream. Thus pulling the audio and video components apart.

Administrators can also customise video port range as well as the audio port range within a Video call, applies to both standard video and immersive video streams.

CUCM Qos

Security

Cisco have enhanced the encryption for SIP and SRTP, now includes TLS 1.2 and AES-256 RSA / ECDSA based cipher support. Other security updates include login audits logs/report and Login Banner Display.

LDAP

CUCM LDAP can now contain up to 20 sync agreements and include the synchronisation of Active Directory Distribution Groups. Support for open LDAP is now also supported in v11.

Unity Connection Enhancements

Video Auto Attendant

CUC V11 supports Video enabled call handlers in addition to Video Greetings (Supported in CUC 10.5). Videos can be recorded professionally then uploaded using via the Audio Text Manager Tool.

Missed Call Notifications

CUC v11 provides missed call notifications to a user’s mailbox, can be enabled/disabled on a per user basis. This is now at feature parity with MS Exchange UM solution.

CUC Missed Calls Notification

Summary Notifications

Cisco Have introduced an excellent feature detailing all voice messages logged in a summary email to the user. This can be scheduled daily etc. The user then has the ability to browse and select/listen/delete messages.

CUC Summary Notification

Expressway 8.7

Expressway 8.7 officially supports DX Phones and the 78/8800 series IP Phones over MRA. The feature set for MRA connectivity is almost on parity with Internally registered IP Phones.

DX and 7800/8800 IP Phones supported via MRA

Unified Contact Centre Express Enhancements

CAD/Finesse Agent

The CAD Agent has been officially retired. The Cisco Finesse Agent is now the only agent delivered with Contact Centre suite.

IP Phone Agent

The Finesse IP Phone Agent (IPPA) has been introduced in v11, the Standard License feature set unlocks the IPPA. The IPPA Provides basic IPCC functionality which incudes:

- Agents State changes and display
- Wrap Codes
- Display Context Data (Script Variables)

Finesse IP Phone Agent

Jabber Enhancements

In my opinion the Active Directory Groups integration into Jabber is a huge improvement. Also in v11 other features to be introduced include Far end camera control, the OPUS and G722 codec support, P2P Calling (not need for CUCM), integration into CMR Rooms, bridge escalations into the Conference Now Audio bridges.

Jabber Conference Escalation

Dial Via Office – Reverse (DVO-R) provides an alternative to mobile to mobile calling. This feature allows the Jabber device to use the CUCM server to fork out(establishe) two PSTN Call legs for audio quality.

Jabber DVO-R

CMR Cloud 3.0

New features include Proximity Join for mobiles apps and IOS and Android platforms, video callback to SIP URIs, enhanced Lync interoperability.

Collaboration Endpoint Software 8.0

The CE8.0 software now allows PC/MAC to share content (Static) from anywhere in a room without cables.

The Touch 10″ UI creates a unified experience with room based endpoints allowing drag and drop, move content/video between screens etc.

Touch 10 UI - Cisco Telepresence

CE 8.0 introduced Multistream for room based endpoints. This allows the room based endpoint to fully utilise both screens, in the past only screen was used for video and the second screen for content.

Cisco Multistream

Note: be sure to check compatibility guides before upgrading room based endpoints to CE8.0 software.

Mar 08

UCCX: Script Validation Failed: java.lang.NullPointerException

Come across a little error with UCCX Scripting. I had a working script configured. As the scripts are object based, sometimes the objects can be moved accidently while you are working on the script. Today I accidently moved the “Start” step and dropped it somewhere in the middle of the script. I moved this step back to beginning, however, the script would now fail. All the debugs would show java.lang.NullPointerException.

I ended up creating a new script and copy/paste the original to the new. Debugs then worked fine and the script was back in action.

Jave Exception Error

Cisco UCCX

Feb 28

WFO – Sync Issue – Check UCCX Name

Receiving a sync error in Cisco QM/AQM Server. The Cisco QM Server not sync any details from the UCCX Server. This issue was resolved by replacing all the hyphens in the UCCX Hostname with underscores.

Below is a snippet from the WFO Install guide.

When typing the database instance name,
use the following guidelines:
? Convert all uppercase characters to lowercase
characters
? Replace all hyphens with underscores
? If the host name starts with a number, add the
prefix i
? Append _uccx to complete the instance name
For example, if your host name is 80-ABC, your instance
name will be i80_abc_uccx.
Primary Instance Name Enter the instance name of the primary Unified CCX
database. When typing the database instance name,
use the following guidelines:
? Convert all uppercase characters to lowercase
characters
? Replace all hyphens with underscores
? If the host name starts with a number, add the
prefix i
? Append _uccx to complete the instance name
For example, if your host name is 80-ABC, your instance
name will be i80_abc_uccx.

Source supportforums.cisco.com/discussion/11077306/qm-80-manual-sync-failure

Feb 17

Multiple Patterns for VOIP Dial Peers

To make life easier configuring a Cisco Voice Gateway with an organisation that has multiple inbound number ranges, we can group the number ranges together and then apply the group to a single dial-peer saving lines of extra code.

First is to create a voice class e164-pattern-map, from the sub-menu we need to enter the number ranges as you would normally on a dial-peer using regex expressions. The second step is to apply the voice class to a dial-peer.

voice class e164-pattern-map 1
e164 296451[016]..
e164 296527[6-9]..
e164 2963268..
e164 2965145..

dial-peer voice 2 voip
description ## PSTN INBOUND ##
rtp payload-type nse 99
session protocol sipv2
session target sip-server
incoming called e164-pattern-map 1
voice-class codec 10
voice-class sip dtmf-relay force rtp-nte
dtmf-relay rtp-nte
fax protocol none

Jan 30

UCCX – CF_RESOURCE_OUT_OF_SERVICE

Agent receives the below error message while attempting to log into Finesse Agent. Agent has been configured to use an 8851 IP Phone. Same Agent can log onto the Finesse Agent using 7945/75 IP Phones.

finesse

The Remote Agent User requires CTI Access to the Agents phone. With the new 8851 IP Phone two extra user roles are required (same as the 9971 IP Phone) The roles required are: “Standard CTI Allow Control of Phones supporting Connect xfer and conf” and the “Standard CTI Allow Control of Phones supporting Rollover mode”

Jan 10

Prompt Recording UCCX – 0.6KB Files No Audio

Configuring a prompt recording script in UCCX requires the Codec G711ulaw be used. As of version 10.6 this is the only supported codec for recording prompts. Typically this was not an issue as the Regions determines the codec used and always prioritised G711ulaw above G711alaw. However with the later versions of CUCM, the Regions configuration menu now includes the ability to preference codecs. So one could give the G711alaw codec a higher preference above the G711ulaw codec. What this means is when you call into the UCCX System, you will still hear all the prompts, however if you attempt to record a prompt using a prompt recording script, the system will record the prompt in G711alaw. All indicators will point to a successful recording, however when looking in the Prompt Directory on the UCCX Server, the wav file is only 0.6KB in size. This file contains no audio.

Ensure the codec negotiated is G711ulaw when recording prompts on UCCX.

Dec 30

Faxing – Bearer Capability Not Implemented (65)

Faxes failing the negotiation process. When ringing through, the fax starts to signal, however after a couple of seconds, the signalling is supressed, followed by an error on the Fax Display or results sheet. The Disconnect cause is 65 – Bearer Capability Not Implemented.

Setup Traces in CUCM and display the output in the TranslatorX. TranslatorX displays the key information of a call leg within a couple of mouse clicks. Below we can see the an Internal Fax is attempting to fax out to the PSTN. The fax is connected to an ATA Device.

Due to the nature of faxes, the G729 codec is not compatible with fax signal. The G729 compresses the rtp and hence corrupts the fax transmission. Below we see the negotiated codec is G729. So we’ll have to check how this codec was negotiated and not the G711a/ulaw.

CUCM Fax

Check the codec negotiated.

1. Check the Device Pool of the ATA and Voice Gateway. Collect the Regions, the confirm the Regions between the ATA and the Voice Gateway can indeed negotiate G711a/ulaw.

2. If all looks good, log into the Voice Gateway and check the codecs configured for the dial peers. Voice dial-peers on IOS Voice Gateway default to G729 codec. You must configure a voice-class with a preference to use G711alaw first. This ensures G711alaw is negotiated between the ATA (Fax) and the Voice Gateway. In the below example, only the codecs G711alaw and G711ulaw are permitted on the dial-peers 10 and 11.

CUCM Fax

** With the latest CUCM Deployment models, there is also the option to create/modify Codec Preference list under the Regions Menu. This allows us to the preference codecs between endpoints registered to CUCM and/or the Voice Gateways leading to the PSTN Network.

Dec 20

CUCM – Auto Dial from SIP Phone (PLAR)

To allow a SIP IP Phone to dial out to a predetermined destination when the handset is lifted in Cisco Unified CM, follow the below steps.

Create a Partition for the PLAR. I called my partition PUBLIC_PT
CUCM Partitions

Create a CSS, and add the above partition to the ‘Selected Partitions’ window.
CUCM Partitions

Create a SIP Dial Rule. The pattern value should be blank.
CUCM CSS

Create an ‘Blank’ Translation Profile in the PUBLIC_PT partition. Also ensure the CSS of the Translation has access to the ‘translated’ destination pattern. In my case DEVICE_CSS has access to the DN (Extension) 1012222.
CUCM Translation Pattern

Navigate to the Phone configuration window. Select the Calling Search Space we created in step two. (PUBLIC_CSS).
CUCM Device Settings

Scroll down to the Protocol Specific Information section and select the SIP Dial Plan we created earlier.

Device SIP Settings

Give the Phone a reset and validate the above settings by lifting the handset.