More than year ago when I started using Nokia Eseries one of the reasons to switch to new mobile platform was SIP stack and client support with Eseries (I used to have Nokia E71, now I am proud owner of Nokia E72). By that, I was able to connect to Asterisk or Cisco Unified Communications Manager (by using SIP digest authentication) and that was working like a charm (I am still using SIP integration heavily).
Then, I started to think about different approaches with Nokia in business environment, followed with different cost saving strategies so i asked myself about Nokia Eseries integration with Unified Communication Manager (UCCM and CME environment) by using SCCP. That was logical thing to think of, since there is SIP support already integrated into this phone series and there are plenty of Call Manager deployments in production worldwide natively working with Skinny (SCCP stands for Skinny Client Control Protocol which is often just called Skinny). And, as expected, there was really nice integration prepared by Nokia for their business users called Nokia Call Connect for Cisco.
Nokia Call Connect for Cisco integrates compatible Nokia Eseries devices with compatible enterprise voice infrastructure. When you enter the coverage area of the office wireless local area network, your device automatically registers to Cisco Unified Communications Manager and thereby activates business mode. In business mode, you can use Cisco Unified Communications Manager services to handle business calls.
With Call Connect, you can:
- Use high-speed WLANs instead of cellular networks to make calls when you are within WLAN coverage
- Use the services of Cisco Unified Communications Manager to handle business calls
- Route calls over the enterprise voice and data network to help minimize mobile phone bills
- Benefit from improved mobile phone coverage within buildings by using high-speed WLANs
- Receive notifications of new voice mail as text messages
- Access online services, such as corporate directory
Solution deployment can be splited in two parts:
- Configuring Unified Communications Manager
- Configuring Nokia Eseries phone
Since I am working in lab environment with Unified Communications Manager 6.0 and Nokia E72, I needed to make sure to download proper required packages, as follows:
Nokia Call Connect for Cisco client v2.0 (v2.0(1005)) (SIS, 1,66 MB)
NOTE: Supported devices include Nokia E52, Nokia E55, Nokia E63, Nokia E66, Nokia E71, Nokia E72 and Nokia E75
Cisco option package (COP) file for CUCM 4.x, 5.x and 6.0 for Nokia Call Connect for Cisco clients (.zip, 8 kB)
The file should be imported to Cisco Unified Communications Manager server 4.x, 5.x and 6.0 to add the Nokia Eseries devices in the device list of Communications Manager if the correct device type isn’t yet included there.
Please note that client file provided in the list above is actually trail version of the Nokia Call Connect for Cisco, and it is going to be active for 60 days after which it is going to expire and you will need to purchase real license. This text is not going to describe how to install this client, but I will suggest to install it from OVI store (it is easiest and most convenient way to do so).
Cisco Unified Communications Manager Configuration
After we have downloaded above files, we need to import Cisco Option Package to Unified Communications Manager. Once we are done with that process we will have Nokia S60 listed as valid phone type in CallManager Phones configuration. Process of adding COP file is straight forward and is described in following sections. Please note that you will need to have up and running FTP server in your network to accomplish installation of COP file.
First, we need to navigate to Cisco Unified Communications Manager Serviceability configuration pages (selection can be made from upper right corner as shown on screenshot):
Once logged into Serviceability configuration pages, we need to navigate to Software Upgrades drop down menu, and we need to select Install/Upgrade:
Once there, we need to assume control if there was some previous session:
Next thing is to select preferred source of installation. In our case that is going to be FTP server. Valid options are Remote Filesystem and CD/DVD.
Please fill all required fields (fields indicated with *). Also, make sure to put COP file in root directory of your FTP server, so that CallManager is able to find it as valid upgrade option. You will need to provide Directory (put / for root on your FTP server), Server (IP address of your FTP server), Username and Password (valid user information) and Transfer protocol which can be SFTP and FTP.
Once done with filling up required field, press Next and Call Manager will attempt to contact FTP server. If there is valid COP file (valid upgrade option), and if we are working with proper user information and running FTP server, Call Manager will list valid upgrade options as per following screenshot:
Please note that valid COP file for Nokia S60 phone type is called cmterm-nokia_s60_001-sccp.cop.sgn. If that is what you have listed, press Next and importing process will start (downloading):
Once it is downloaded you will be presented with MD5 hash value which you can compare with one provided by Nokia from security reasons:
Once you press Next, import process will start and you will be presented with progress as follows:
Process will run for few minutes and once it has been completed, you will be prompted about it as follows:
Once done with this step, we have imported new phone type to Call Manager: Nokia S60. To make sure that it is there, we will need to check it in Cisco Unified CM Administration configuration pages. Therefore, we will need to make proper selection in upper right corner:
Once we are in Cisco Unified CM Administration pages, we need to navigate to Device drop down menu and we need to select Phone.
Once there, we will need to add new phone, and we can do that by pressing Add new button as per following picture:
Once the page is loaded we need to make proper selection, and in our case we need to select Nokia S60. If we are able to see Nokia S60 then our COP import was successful.
Now, assuming that you have installed Call Connect client (.sis) on your Nokia Eseries device and that it works fine, we can continue with configuration. In this section, we will add new phone with phone type device Nokia S60 as listed above. Please notice that product type is now listed as Nokia S60 and that Device protocol is Skinny:
Next thing that we need to do is to check wireless MAC address on phone since it is one of the required fields in order to add new phone. Fastest way to achieve that on Nokia E71/E72 is to type following code: *#62209526# and you will be prompted with WLAN MAC address. Once you type that into MAC address field, Description field will be populated automatically. Please note that we need to fill up all the fields indicated with asterisk (*).
We will needed to select Phone Button Template and Commong Phone Profile fields since they are required. Also, that includes Presence Groups and Device Security Profile fields as shown on following screenshot:
Once done with basic configuration, we need to save changes by hiting Save button. Then, we need to configure associated information which includes configuration of directory numbers as per following:
Once there, we need to click on Line [1] – Add a new DN and we need to fill up required fields. Field of interest is Directory number. Also, please notice that in Associated Devices box, our Nokia Eseries device will be listed:
Once done with directory number configuration, click on Save and you will have your new Nokia S60 phone configured and listed on phone list, as follows:
Once we are done with configuring Cisco Unified Communications Manager side which includes importing COP file and configuring new phone, we can start configuring Call Connect client which we installed on Nokia Eseries phone.
Configuring Nokia Eseries phone
Since we have server side up and running, we can start configuring our Nokia Eseries Call Connect client. In our lab environment, we are using Nokia E72 and following screenshots are taken on that phone. First thing that we need to do is to open installed application by navigating to Menu > Apps > Nokia CC Cisco. Please notice that Call Connect is offering multiple productivity features such as Call pick up, Group Call pickup, Call divert and DND. Also, please notice that we do not have SCCP active profiles, and in following sections we will describe process of configuring one.
To configure new SCCP service, select Options > Settings > New profile
Once in the New profile configuration mode, we will need to configure Profile name, select default Access Point and configure TFTP server. Please note that in our example Profile name is set to Call Manager, 6BFlat5 is default access point and that TFTP is manually set to 192.168.1.10 which is in our case IP address of our lab Call Manager. Valid option for selecting TFTP server is also DHCP, but in that case we would need to configure DHCP server with option 150, which would indicate IP address of our TFTP server.
Once we are done with basic profile configuration, we can click on Back. We will see our new profile in “Not registered” state. To register service, we will need to navigate to Contacts and then from viable options drop down list we need to select Cisco VoIP and select “Activate service”, as shown below:
Once you activate the service, you will see your newly created profile registered.
Once registered, one additional step can be made in order to make sure that all is working properly. Navigate to Menu > Apps > Nokia CC Cisco and select Status information. You will be able to check what is the Stack version, Outgoing phone number, License information, MAC address, DHCP related information, Networking information and SCCP profile information.
To make sure that all is running fine on Unified Communications Manager, navigate to Cisco Unified CM Administration configuration pages, select Devices drop down list and from there pick up Phones and click on Find/List. You should receive output that indicates that SCCP phone is registered, as follows:
Please notice that in upper right corner on your phone you will be able to see your configured directory number followed by the SCCP profile name (in our example it is (1003)CallManager), and also, registration status will be indicated by the small VoIP icon in bottom part of the screen of your Nokia Eseries phone. Once you have your profile registered with Unified Communications Manager, you can start making VoIP phone calls and you can start using productivity features that we already mentioned in previous text.
For more details about Call Connect please refer to following links:
- Nokia Call Connect For Cisco
- Nokia Call Connect For Cisco: Licensing and Support
May 18th, 2010 by 
admin 
Richard M. Stallman is an American software freedom activist and computer programmer. In September 1983, he launched the GNU Project to create a free Unix-like operating system, and has been the project’s lead architect and organizer. With the launch of the GNU Project, he initiated the free software movement and, in October 1985, set up the Free Software Foundation.
2 Comments »
Kao to sam i najavio u nekoliko postova prije, instalirao sam Linux na iPod. Naime, ve? neko vrijeme sam ponosni vlasnik iPod video-a (30 GB model) i Apple-ov softver koji dolazi sa njime bio je sasvim zadovoljavaju?i. Me?utim, kako sam pobornik FOSS solucija to nije potedilo ni iPod. Na iPod sam instalirao Podzillu ali i Rockbox i neko vrijeme testirao oba firmware-a.