Category Archives: Cisco UC

Dec 18

8831 IP Phones Stuck on Cisco Logo – 9-3-3-5

Posted on by

Cisco 8831 IP Phone out of the box with firmware sip8831.9-3-3-5 has the keypad displaying the Cisco logo on the screen with no functionality. The 8831 IP Phone displays as registered in CUCM and is able to be pinged and can log onto the web GUI of the phone.

Trying to update the firmware to sip8831.10.3.1.16 fails with the following debug message on the phone.

[15:20:12, 01/12/15] DeviceImageDownloadFailure DeviceName=SEPAC44F214892D IPAddress=10.199.237.42 Method=3 FailureReason=3 Active=sip8831.9-3-3-5 Inactive=sip8831.10-3-1-16 FailedLoadId=sip8831.10-3-1SR1-1 Server=13.100.192.10

This particular jump from firmware 9-3-3-5 to 10-3-1-16 is not permitted. An intermediate firmware must be loaded first to upgrade sip8831.9-3-3 firmware revisions to any sip8831.10-3-1 firmware revisions. The intermediate firmware is sip8831.9-3-3-TO-10-3-1-v2. Once this firmware is uploaded and installed onto the 8831 IP Phone, the 10-3-1-x firmware loads can be installed.

Basic steps.

1. Load the sip8831.9-3-3-TO-10-3-1-v2 firmware files onto the CUCM and update the 8831 Phones
2. Load the sip8831.10-3-1SR1-1 firmware files onto the CUCM and update the 8831 Phones.

Dec 15

Error Encountered. Selected File not Valid – CUCM

Posted on by

Trying to install firmware for 8831 into CUCM 8.6.2 is returning an error. Selected file is valid. MD5 hash value: xxxxx
firmware-1

The firmware file downloaded is:
firmware-2

Cisco have created new Public RSA Keys to improve software integrity protection. Any file such as firmware loads, dial plan, locales etc that have a ‘k3′ in then package name will include the new RSA keys. CUCM 10+ already have the new RSA Keys installed. However for CUCM 9.x and below, you will be required to install the cop file ‘ciscocm.version3-keys.cop.sgn‘. This doesn’t require a system reboot, however installation during off peak is recommended.

An exception to this is if your current CUCM Version is one the below. In this case there is no need to install the cop file.

- 8.5.1.17123
- 8.6.2.24122
- 9.1.2.11018

The cop file will install on any of the below systems. If you system does not meet the below, install the required SU.

- 8.5.1.10000-26
- 8.6.2.10000-12
- 9.1.2.10000-28

To verify the cop file is install and active, run the following cmd against the CUCM.

admin: show version active

Dec 10

CUAC Blind Transfers – Invalid Destination

Posted on by

In Cisco Unified Attendant Console operators have two options for call transfers. Blind and Consult. The major difference between these two transfer methods in technical terms is the Consult Transfer uses the Operator’s Phone CSS and the Blind Transfer uses the Service Queue’s (CTI) CSS. Most Engineers will configure the Operators handset to have the ability to call Internal and PSTN phone numbers. However, they neglect to give the same access to the Service Queue CTI Ports. In this scenario, the Operator would experience issues with attempting blind transfers to a PSTN Phone Number. The Console would return a “Invalid Destination” error and return the call to the Operator.

If you make a change to the CSS for the Service Queue CTI Port, you need to synchronise between CUAC and CUCM. Then to apply the changes, the CUAC Engine needs to be restarted from the Web Admin Console.

Dec 05

Jabber Softphones for Collaboration Edge Access

Posted on by

Cisco Jabber as evolved rapidly over the past couple of years with a lot of growth still to come. With the introduction of Collaboration Edge architecture, Cisco Jabber can be used from outside the corporate network while being secure (both Signalling and Audio).

For Cisco Jabber to connect through the Collaboration Edge environment and be feature rich the below is required.

- Cisco Unified CM
- Cisco IM & Presence
- Cisco Unity Connection
- SRV Records (External and Internal)
- Cisco Expressway-E and Expressway-C

The following Cisco Jabber Devices can be configured to connect through the Collaboration Edge environment.

- MS Windows Operating System
- MAC Operating System
- Apple iPad
- Apple iPhone
- Android mobile devices

Fro each of the above devices to connect through the Collaboration Edge environment a phone device is required to be configured in CUCM. Each phone device name must be prefixed to allow CUCM to identify the device type. Prefixes include:

- CSF (Windows/MAC)
- TCT (iPhone)
- TAB (iPad)
- BOT (Android)

I’ve outlined below the steps to create a Cisco Jabber softphone. (In the below example an iPhone device type will be created.

1. In CUCM navigate to Device -> Phones
2. Select Add New
3. Drop down the Phone Type Menu and select Dual Mode for iPhone.
Jabber

jabber-2

4. The Device Name is ‘TCTusername’ The device name has a 15 character limit.
5. Complete the Description, I always place the device type in the description as well for easy identification.
6. Complete the other required fields (with an *)
7. Select the appropriate user for the Owner Field
Jabber

8. Add a new DN (Top Left)
9. Enter the extension of the user. (The User would have an existing deskphone, make sure to use the same extension, creating a shared line like setup)
10. Select the Partition. (After the selecting the Partition, the Line details should auto populate until the ‘Line 1 on Device TCTUPLINX Section)
11. Complete the Display Name and External Phone Mask.
12. Select ‘Associate End Users and select the end user who will use this device/line. FYI, this section allows CUCM to auto publish phone status for a user. Example. If this line is busy, the system will change the user status to ‘OnCall’.
13. Click Save
14. Navigate to the User Management -> End User page
15. Find and select the required User.
16. Scroll down to Service Settings section and ensure the ‘Home Cluster’ and ‘Enable User for IM & Presence’ is checked.
17. Add the newly created device to the Controlled Devices window for the user.
18. Click Save.

This user is now ready to download the Cisco Jabber App and log into the UC System from both within the corporate network or from outside the corporate network.

** NOTE 1: RTP will be encrypted from the Mobile device to the Expressway-E Device. However, the default non-secure device security profile does not encrypt RTP from the Expressway-C to the CUCM. This is typically on the same LAN segment. If you are required to encrypt RTP over this LAN segment as well, create a secure Device Security profile with the appropriate encryption algorithms and assign the Device. (Device Page). Also, the Expressway-C must include the Device Security Profile name in its SAN Certificate.

**NOTE 2: Device Types are as follows:

- Android Device is ‘Dual Mode for Android’
- iPad Device Type is ‘Cisco Jabber for Tablet’
- Windows.MAC Device Type is ‘Cisco Unified Client Services Framework’
- iPhone Device Type is ‘Dual Mode for iPhone’

**NOTE 3: A Cisco Jabber softphone/mobile device will consume a UCL Enhanced License if the Owner remains as anonymous. If an owner is selected and the owner(user) already owns another device, the Cisco Jabber softphone/mobile device will add to the UCL Enhanced Plus or CUWL Std/Pro license count depending the number of devices owned by the user.

Nov 30

Cisco CUCM Failover with Cisco Unified Attendant Console HA

Posted on by

CUCM Failover with Cisco UAC Advanced in HA mode.

Scenario.

Two CUCM Subscribers with two Cisco UAC Servers in HA Mode. Each CUAC Server is required to be configured to connect to a difference CUCM Subscriber.

The Cisco UAC always uses the Primary UAC Server for CTI Registration, Triggers, Operator Logins etc. The Secondary UAC Server is in a Standby state.

To ensure CUAC continues to operate as per normal when a CUCM Server fails or is restarted, the below checkbox needs to be checked for both CUAC Servers. This allows each CUAC server to connect to both CUCM Subscribers.

Summary

1. The primary and secondary CUAC server connect to different CUCM Servers.

2. Ensure the “Add secondary CUCM information from other server” is checked.

cuac1

Nov 20

Sip Calls being Rejected – CUBE

Posted on by

When calling through to any of the DID number range for a customer, it was found that only a small percentage of calls were successful. The failed calls would either play an ISP announcement or just ring continuously until the timer expired.

This customer had a newly provisioned SIP Trunk to the ITSP and all was working well until this point. No changes had been made by the Internal IT. After tracing successful and failed inbound call attempts it was found the ITSP was sending additional information in the SIP SDP. The information being sent was the QoS SDP Parameters, the local CUBE was not equipped to handle/negotiate these parameters therefore the call negotiation process would fail.

Resolution was to provide the below information to the ITSP to strip the QoS SDP Parameters.

INVITE Captured during trace.

Received:
INVITE sip:2XXXXXXXX@X.X.X.X:5060 SIP/2.0
Via: SIP/2.0/UDP 203.52.1.167:5060;branch=z9hG4bKhs0g8n00eogroamlbun0.1
From: <sip:2XXXXXXXX@X.X.X.X;user=phone>;tag=866784654-1439255743666-
To: “Name”<sip:2XXXXXXXX@domain.com.au;user=phone>
Call-ID: BW111543666110815-468528800@10.83.154.184
CSeq: 220849754 INVITE
Contact: <sip:2XXXXXXXX@203.52.1.167:5060;transport=udp>
Supported: 100rel
Allow: ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY,UPDATE
Accept: application/media_control+xml,application/sdp,multipart/mixed
Max-Forwards: 29
Content-Type: application/sdp
Content-Length: 641

v=0
o=BroadWorks 3668715 1 IN IP4 X.X.X.X
s=-
c=IN IP4 X.X.X.X
t=0 0
a=sendrecv
a=media-release:hngl5rp9pujvivh05pvu6ibgr83pv898756s7s8auvmg62o6u724a2ur96v3nd0v1350ln1-6
a=media-release-con-addr:d6v1k1hv6hvh1002o9j0
m=audio 18064 RTP/AVP 8 0 18 96 97
c=IN IP4 X.X.X.X
b=RR:3000
b=RS:1000
a=curr:qos local none
a=curr:qos remote none
a=des:qos mandatory local sendrecv
a=des:qos optional remote sendrecv
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:96 AMR/8000
a=fmtp:96 mode-set=7;max-red=0
a=rtpmap:97 telephone-event/8000
a=fmtp:97 0-15
a=maxptime:40

Nov 10

Configuring an Analogue Device on the Second Port of an ATA190

Posted on by

To access the second port on an ATA190 device, you need to shift the device MAC Address by two digits and append the digits ’01′ to the end of the device MAC Address. Below is an example.

First Analogue Port MAC Address.

MAC Address of ATA190 is 34DBFD184921

Second Analogue Port MAC Address.

MAC Address of ATA190 is DBFD18492101 (the ’34′ has been discarded and ’01′ has been appended to the end)

Simply Add New Devices, select ATA190 then enter the required MAC Address to access the device configuration page.

Nov 05

Unusual Case Study of CUCM Call Recording Implementation

Posted on by

A week ago I’ve got a partnership offer from Cisco Solution Partner that develops various solutions on top of Cisco UCM, Telepresence and UCCX products and sells them through channel partners. While discussing their app suite for CUCM I was told about the interesting case study which I’ve decided to share with you to take a break from technical posts.

The client is a large media agency with hundreds of field reporters all over the country. They interview dozens of VIPs daily and the challenge was to minimize the time of delivering interview recordings to the agency newsmakers.

So here is the approach they took… When starting a new interview the reporter turns on his voice recorder (for high-quality recording) AND makes a phone call to the special office number placing the mobile phone on the table along with the voice recorder.

What happens next is:

1) CUCM routes the incoming call to the recording app, which establishes the connection with the reporter’s phone and starts recording the interview;

2) at the same time the recording application pushes the XML service to Cisco IP phones of several newsmakers who are subscribed to the call recordings of this reporter; the XML service plays “beep” informing newsmakers about the new interview started and shows the interface on the IP phone:

3) after pushing the “Listen” button, the newsmaker listens to the interview being recorded and composes the news message.

The whole picture looks like this:
recording1

This way the agency newsmakers receive new content just on the fly and the news message may go online even before the reporter returns to the office.

Quite an interesting client story, what do you think? If you need to learn more about them, here they are – aurus5.com