Device Package

Update Device Package in CUCM

Ever face a Problem with Adding a new Model IP Phone to your Environment such as 8845, 8865 ?
will Luckily Cisco always care about her customer and support them with upgrading their device package always
it’s available in the latest Device Package cmterm-devicepack8.6.2.26169-1.cop.sgn Which can be downloaded from Cisco Software download https://software.cisco.com/download/navigator.html?i=!mmd

I will show you the steps to Upgrade your Device Package
First Turn on your TFTP were you have your Device Package
3
Then Login to your CUCM OS Admin Page
The Choose Software upgrades – Install/Upgrade
1
Then Fill the Detail of the SFTP in CUCM page
2
Press Next and choose the Device Package you want
4
Press Next and the Downloading of the Device package Start5
After the Downloading is done it will ask to Install it
6

7
Now After it Finish you need to Restart the TFTP Service
go to Cisco unified Serviceability – Tools – Control Center  Feature Services and Restart the TFTP Service
in case of a big cluster you  need to add the Device Package to each server and Restart them starting by the Publisher
advice always do this after Duty  ;D

and Finally will find that you can add your new IP Phone Model 8845, 8865
8.png
;D

Standard
Collaboration, ILS, URI

URI Dialing Between Clusters

The last blog was about URI Dialing at the same cluster which an easy step https://ccieroot.com/2014/10/30/uri-dialing/
But when it come between cluster there is another new feature Called ILS “Inter-Cluster Look-up Service”
Inter-Cluster Look-up Service (ILS) is a cluster-wide service in CUCM that when configured on and between CUCM clusters, synchronizes information throughout the “ILS Network”.

So after finishing configure the Basic URI and made Sure it working we start next step by configure the trunk between both publisher

Go to Device – Trunk Add New and choose SIP Trunk and the Device Protocol also SIP and here is the final Look

Screenshot 2014-10-30 17.17.34

 

 

 

Screenshot 2014-10-30 17.18.04

 

 

 

If you want to use ILS to support intercluster URI dialing, check the Exchange Directory URI Catalogs with Remote Clusters check box in the Intercluster Directory URI Configuration window.
go to Call Routing – Intercluster Directory URI – Intercluster Directory URI Configuration and check the box and choose a name

Screenshot 2014-10-30 17.29.13

 

 

 

 

 

Before you start to configure the ILS go to the Enterprise Parameter – Change the name of  Cluster ID From StandAloneCluster to What ever name you wish in out case it’s CCIEROOT

ClusterID

 

 

then go to Advanced feature – ILS Configuration
and make your Publisher as the HUB and configure password and press ok but don’t put IP in the field of Registration Server

Screenshot 2014-10-30 17.33.43

 

 

 

 

 

 

 

in the Other Server you configure it as a spoke and put the IP of the hub in the Registration Server

Screenshot 2014-10-30 17.38.37

 

 

 

 

 

 

Then Configure the Route Pattern by going to Call Routing – SIP Route Pattern
from CCIEROOT To ATS and in ATS sever you configure a SIP Route Pattern From ATS to CCIEROOT were the IPv4 Pattern is to our ILS URI Configuration name which was MOTO.LOC

Screenshot 2014-10-30 17.40.21

 

 

 

 

 

Now you can test the call and it Succeed Between Cluster

 

Standard
URI

URI Dialing

SIP Uniform Resource Identifier (URI) based dialing One of the 9 newest feature for CUCM version 9
This is beyond anything you imagine Finally we will forget about calling each other by extension number and the we will start typing the email ID instead to make a call. Seriously SIP URI can be best compared to an email address such as Aysar.Mohamed@ccieroot.com or Aysar.Mohamed@mynaghi.com.sa . A users can dial the called party via URI if they are using 8961, 9951 or 9971.
make sure you have to upgrade the IP Phone firemware to 9.3.1

A SIP address or SIP URI is a Uniform Resource Identifier written in user@domain.tld format (semantically, much like an e-mail address). It addresses a specific telephone extension. A SIP URI can be automatically imported from LDAP (provided the cluster is integrated with an LDAP server such as a mail or the msRTCSIP-primaryuseraddress attribute.

Configuration Steps:

The user name is case sensitive however host is case insensitive (RFC 3261). This parameter is configurable starting CUCM 9.1 (under Enterprise Parameters – URI lookup policy)

Go to Enterprise Parameter
Screenshot 2014-10-30 13.25.35

 

Then when you import the user from LDAP make sure the URI Map to the appropriate LDAP attribute
Screenshot 2014-10-29 22.43.18

 

 

Now if you go to the End User Configuration you will find the Filed of Directory URI is your Email
Screenshot 2014-10-29 22.46.37

 

 

 

 

 

Now Configure a phone and Add Dn as you normally Do then go back to the end user and associate the Device and select the primary DN which you want to bind the Directory URI to it

Screenshot 2014-10-29 22.48.00

 

Screenshot 2014-10-30 11.53.03

 

Now Check the DN
Screenshot 2014-10-29 22.48.44

 

Its automatically bind to the DN

*The Directory URI is put into an automatically generated partition called “Directory URI”.  If you wanna call other DN with Directory URI configured, make sure your CSS has the partition Directory URI.*
You can try to make a call now.  It only supports on hook dialing for URI dialing, so you press the new call softkey, the press the “A B C” softkey so that you can enter alphanumeric characters.
If you don’t want to call the full directory URI, you want to call without the domain name, make sure you change the following in the Enterprise parameter.

Screenshot 2014-10-29 22.49.59

 

Now let’s Test it by dialing
2014-10-30 12.24.35-2

 

 

 

 

and yes it’s Calling by dialing the email address aysar.mohamed@mynaghi.com.sa not the extension

 

 

 

 

 

 

Standard
Active Directory, CUCM

CUCM integration with Active Directory

When you first finish installing the CUCM the Call Manager use it’s own LDAP Directory of End Users which is nice to use, but in case you work in a company with more than 1000 people it’s insane to add them all. so the preferred way is to integrate CUCM with a corporate LDAP weather it was Linux, OS or Windows. in our case i will show you how to integrate CUCM with Windows Active Directory

from Windows Side all what you need is a user with Administrator Right so you will be able to access the Active Directory

now back to CUCM

first activate the service that help you to Sync Between LDAP and CUCM

1

 

Then Go to Cisco Unified CM Administration > System > LDAP > LDAP System to identify what type of LDAP

2

 

 

 

 

 

 

 

Check the Box to Enable Sync from the LDAP Server

3

 

 

 

 

 

 

Now Go Click on System > LDAP > LDAP Directory and click Add New

in this example the Active Directory is my Domain CCIEROOT.COM
the admin user is : aysar.mohamed@ccieroot.com and i put the password for the authenticate with the LDAP
my LDAP Search Base is where i save the user it could be simple as under users. in my case i sync all the user in my domain

and my LDAP ip address is 192.168.200.1

Untitled

 

 

 

 

 

 

5

 

 

 

 

 

 

6

 

 

 

 

 

Click on System > LDAP > LDAP Authentication. This will authenticate CUCM End Users using Active Directory instead of the embedded CUCM directory.

7

 

 

 

 

 

 

8

 

 

 

 

 

at this point your CUCM is ready to Sync so go back to System > LDAP > LDAP Directory and Perform Full Sync10

 

 

 

After performing the synchronization the users which were created in Active Directory are now appearing in the CUCM End User

12

 

 
Open one of the users

13

 

 

 

 
That is it

Note. for the users that been created on the CUCM before the Sync they will be Disabled. to Solve this issue you need to create users for them in the LDAP Directory and Sync again and they will be hilighted.

Standard
CUCM

Installation of CUCM 8.6

yes i reached my second blog thanks god  ;D

the first thing that should be taught in the voice track is how to install the application that you are going to use for the rest of your life in case you didn’t get fired of your job afcors

i will show you here how to install the Cisco Unified Communication Manager 8.6 in a very small step

I have a small lab that contain VMWare  Machine with ESXI 5.0, Cisco Router that act as an NTP Server you could exchange this by your laptob windows timer and a Switch that all this item connected too

Let’s Start

first prepare your VMWare:

  • Operating system – Red Hat Enterprise Linux 5 (32 bit).
  • Processors – at least 2 cores
  • Memory – dedicate at least 4GB. 2 is enough but in a large environment Better to keep your precaution
  • HDD – one partition of 160GB
  • Network Adapter – bridge it directly to the physical one.
  • CD/DVD – I Already upload the Image to the Storage of the VMWare
  • Display – Auto

It end looking like this

8

Now Power the Machine and then it ask you to check the Image on the Cd just press No

9

10

After that it will verify the version of the CUCM

12

13

Since it’s a New Installation that mean there is no System to apply the patch to so press No

14

15

Then Choose the Location you are in

15-a

Let the NIC Speed and Duplex determined by the Virtual Machine in case you need to change it in the future

16

17

The Most important Part is the DHCP so be careful

18

19

We didnt choose DNS since it’s a lab only in most of the installation i attend no one using it except in the biggest scenario

20

Now Enter the Administrator Username and a Password

21

Enter the Company Name and City

22

in case this was not the first server you would press no and enter the cluster configuration which is another blog in the future but for now we would press Yes

23

Enter here our NTP Server which is our Router IP also it’s my Voice Gateway

24

This Part is useful later in case i add a subscriber this is the password that I’m going to use

25

Im not using SMTP here so i press No

26

Now Enter the user name and password for the Application Administrator

27

Last Step press the most beautiful Button to complete your mission

28

Like that it start the configuration go and take a cub of Cappuccino it will take Hours

Z

And Done

ZZ

just take the Same ip address you used and past it in the Firefox or whatever web browser you are using and login

1

2

Then from the Drop Down on the Right Corner Choose Cisco Unified Serviceability and press GO so you can be able to Activate all the Service on the CUCM

3
4
5
and Like That your CUCM 8.6 is Ready to be Configure

Standard
SIP

Unable to make outbound call from CUCM to ITSP via sip

Lately I saw this issue appear in many of the SIP Trunk that been provided by some of the ITSP Vendor and let’s not mention any name here I just started to blog ;D

I also face this problem in my site where I can make call to land line, National and international but not a mobile number which appear recently.

The first step is to identify if the calling and called numbers appear to the ITSP in a correct way that lead to a successful call The command is debug voice ccapi inout
In our case the calling and called number was correct so we had to go for the nest step

so the next command is to trace the SIP message in the router and the best command is debug ccsip messages
And it result That the Initial Invite is sent to ITSP SIP-TRUNK with no SDP inside it. you get Back a 183 session in Progress  with unsupported ptime in the SDP

debug ccsipMessages

 

 

 

 

And then I receive an error
debug ccsip messages 500
 

 

So The Issue is that I’m sending the INVITE from the call manager (192.168.200.53) with a delayed offer and CUBE forward it to ITSP with the same ( delayed offer no sdp included ) , then 183 session in progress is sent back which start negotiating the codec ( G711 A law is taking Priority in the offer ) but when the 183 reach the CUCM back it send 500 Internal error
Most ITSP I’ve come across requires SIP early offer. They use this to always decide on which codec to offer for the calls.

In an Early Offer, the session initiator (calling device) sends its capabilities (for example, codecs supported) in the SDP contained in the initial Invite (thus allowing the called device to choose its preferred codec for the session).

In a Delayed Offer, the session initiator does not send its capabilities in the initial Invite but waits for the called device to send its capabilities first (for example, the list of codecs supported by the called device, thus allowing the calling device to choose the codec to be used for the session).

Solution:

In normal Setup, ISP forwards SDP messages to client with DTMF instruction so, I can ask My ISP about it, or force the answer by sending My information on My invite.

For enable Early Offer is possible global:
SIP under voice service

 

For enable in a Dial-peer:
SIP under Dial-Peer

 

 

Standard