Showing posts with label Cisco Unified Communication Manager. Show all posts
Showing posts with label Cisco Unified Communication Manager. Show all posts

Sunday, September 12, 2010

IP Phone Boot-up process (from www.cisco.com)


1.      Inline Power (ILP)
o   Inline Power Initialization


On Phone: Mute, Headset, Speaker Buttons Are Illuminated
2.      Cisco Discovery Protocol (CDP) or Link Layer Discovery Protocol-Media Endpoint Discovery (LLDP-MED)
o   ILP Negotiation, Voice VLAN ID


Phone displays:“Configuring VLAN”
Phone settings:Settings=>NetCfg=>“Operational VLAN ID”
NOTE: LLDP-MED is supported as of IP Phone Firmware 8.3(3)

3.      Dynamic Host Configuration Protocol (DHCP)
o   IP Assignment, TFTP Server Allocation, DNS (optional)


Phone displays: “Configuring IP”(DNS is optional)
Phone settings: Settings=>NetCfg=>“DHCP Server”Settings=>NetCfg=>“IP Address”Settings=>NetCfg=>“TFTP Server X”

4.      Trivial File Transfer Protocol (TFTP)
o   Configuration File, IP Phone Firmware


Sunday, May 17, 2009

configuring mobility features in cisco (mobile connect and mobile voice access)

Configuring Cisco Unified Mobility_Posted_12!10!08

(www.ucunleashed.com)Cisco Unified Communication Manager-Initial post-installation configurations

Once the Call manager Installation is complete,we need to complete Post-Installation task to complete the basic system configuration. In this post I will walk through some of the basic post-Install task and later on we will go through Advanced configuration such as Dial Plans etc.
  • Setting the Cisco Call Manager group.
A Cisco Call Manager group specifies a prioritized list of up to three CallManagers. The first CallManager in the group acts as the primary Cisco CallManager for that group. The others act as backup or secondary and tertiary CallManagers.
CallManager groups provide two important features:
1) Redundancy - able to designate backup CallManagers for each group
2) Call Processing Load Balancing - allows the distribution of device control across multiple CallManagers.
goto Server-> Cisco Unified CM Group-> and change the name of the “default” group to the name that suits the naming convention. Select the Cisco Call Manager node just installed from “Available Cisco Unified Communications Manager” to Selected Cisco Unified Communications Manager”
capture_02262009_1523261
click Save, and then reset button.
  • Setup Phone NTP reference and Set Date/Time Config
goto System-> Phone NTP Reference and click on “Add New”
Enter the NTP server details and select the Mode. In this case I am going to select Direct Broadcast.
capture_02262009_154228
goto System-> Date/Time Group, and associate the recently added NTP reference to the group by clicking on “Add Phone NTP Reference. Once added click on Save and then reset.
capture_02262009_154510
  • Creating Region and Device Pool
Device Pools- These are user configurable sets of defaults that are applied to each device as it is registered to a particular pool. The devices inherit all the settings from the device pool they are within. This simplifies the distribution of Call Manager groups and allows rapid scaling.
Regions- Defines codecs for a call based on what is an internal (LAN) and external (WAN). LAN uses G.711, WAN uses G.729 for optimization and G.711 for local section
To create a Head Quarter Region, goto System->Region
Select the “Default” region and change the name to “HQ_xxxx”. Click save and reset. We can choose various Codec such as G711, G729 (WAN) for the region and also choose Video Call bandwidth
capture_02262009_160945
to set Device Pools,
goto System-> Device Pool and select the “Default”
Rename the Default to the “HQ_xxxxxx” as per your naming convention. We call it head quarters. Set the “Region” that we configured in the step above and also the SRST reference if any. SRST is the survivable Mode system used for scenarios when the Call Manager goes down and this back up takes place.
capture_02262009_161343
  • Configure Service and Enterprise parameters
goto- System-> Enterprise paramaters and set “Enable Dependency Records” to “True”
This parameter determines whether to display dependency records. Valid values specify True (display dependency records) or False (do not display dependency records).
Displaying dependency records leads to high CPU usage and may impact call processing. It may take a long time to execute. If you monitor CPU usage, you might see high CPU usage alarms. To avoid possible performance issues, display dependency records only during off-peak hours or during the next maintenance window

In our case, we will set this value to True and leave everything as system default.
capture_02262009_1621521
Now lets set the service parameters. goto System-> service parameters and select the “Cisco call manager node name” Node and service as “Cisco Call Manager”.
in “System” Section, set “CDR Enabled” flag to “True”
capture_02262009_163042
  • Set Auto-Registration and Cisco Call Manager Port Information
Auto Registration is the feature in Cisco Call manager that allows the Cisco IP Phone to Register automatically and acquire a Directory Number. We can specify the Directory Number range supported for this Call Manager. There is also a flag that controls the Auto Registration feature for this Node. Auto registration is a useful feature which results in faster phone deployment without the need for creating device on the call manager, however this feature can cause security issues. This paramater needs to be activated after careful review of security policies.
goto- System-> Cisco Unified CM and select the CM from the list. Set the “Starting Directory Number” and “Ending Directory Number” as your DN Range. Click Save and Reset
capture_02262009_163829
  • Service Activation
We need to avtivate the services available on Cisco Call manager. goto- Cisco Unified Serviceability and login with the credentials. Select the Services you want to activate (usually Select all) and click “save”
capture_02262009_164550
Thats it, we are set to got further configuration. At this point, we can Take and Cisco IP Phone and configure the TFTP server IP address etc to work with this Cisco Call manager

(www.ucunleashed.com)Install Cisco Unified Communication Manager 7.x

Cisco Call Manager Installation steps.
Hardward used- HP 7845 MCS server
Pop the DVD in the drive and system will boot from DVD and a Media Check will be asked.
cucm-install-1
Once the Media check is complete the system will prompt for “Platform Installation Wizard” as shown below.

cucm-install-5
The Configuration Wizard will ask for the following information
  • Time Zone
  • For static networking it will ask for IP Address, Mask, Default gateway, DNS Server and if your DHCP is enabled simply select the “DHCP” option.
cucm-install-12
  • Administrator Login Credentials. This login is for login through the CLI (Command Line Interface).
  • Certificate Information for creating Security Context for this Node. For trusted relationship with other nodes, send this CSR to Trusted CA authority (Verisign, Geotrust) to get certificate authenticated.
cucm-install-14
  • Next step, the Installtion wizard will as you whether this is the first node in the cluster. If No, then it means this node is “Subscriber” and hence it will ask about the “Publishers” IP address
  • Network Time Protocol Server needs to be set for proper clock synchronization
  • Database security credentials for secure communication between cluster nodes.
  • Application user Name and Password. This is the username and pasword for login into Cisco Call Manager Administration via Portal.
cucm-install-20
After this the Software will proceed with the installation and no intervention is required from this point onwards. If everything goes fine you will be prompted with the CLI where you can login with the credentials suppilied during initial platform configuration.
cucm-install-23
The System will undergo auto reboot as a part of installation process.
cucm-install-25

Tuesday, May 12, 2009

Configuring MOBILE CONNECT

Step 1.- End User configuration, Enabling Mobility
Go to the Cisco Unified Communications Manager Administration page
Select User Management
Select End User
Click ADD NEW and proceed to create an End User, for the purposes of this document I will be creating user named mobilityuser
You may create the end user as usual with the exception that you must check the enable mobility check box and select SAVE, great you have just created an End user with the mobility feature enabled
Step 2.-Creating a mobility SoftKey template
Go to the Cisco Unified Communications Manager Administration page
Select Device
Select Device Settings
Select Softkey Template
Select ADD New
The system will ask you as to what sofktey template to be used as your new template to be based on, I will select for the purposes of this document the "Standard User" template then select Copy, here you will need to change the name of the Standard User Softkey Template for something that is appropriate, in my case I will change the name to Mobility_SK, select SAVE.
-Click the GO button that have the related link option "Configure Softkey Layout"
-Add the following options to the following states:
*On Hook Mobility
*Connected Mobility
Step 3.-Proceed to build a phone
Go to the Cisco Unified Communications Manager Administration page
Select Device
Select Phone
Select ADD NEW (in my case I will be building and configuring a Cisco 7961 using SIP as a protocol, you can configure your phone with SCCP protocol if you like)
Select the appropriate settings for your phone such as Device pool, CSS, MRGL's, device security profile, location, etc although you need to select the newly configured mobility SoftKey Template and select the newly created end user as the Owner User ID and Click the SAVE button
Proceed to set up a DN for this phone and configure things like a Partition, Calling Search Space, Voice mail profile if any, then Select and click the SAVE Button
Step 4.-Configure a Remote Destination Profile
Go to the Cisco Unified Communications Manager Administration page
Select Device Settings
Select Remote Destination Profile
Select and Click the Add New button
Configure the following settings
Name: mobilityuser_RDP
Description: Mobilityuser Remote Destination Profile
User ID: [your mobility user]
Device Pool: [an appropriate device pool]
Calling Search Space: [an appropriate CSS]
User Hold Audio Source: [your option of preference]
Network Hold MOH Audio Source: [your option of preference]
Privacy: [off]
Rerouting Calling Search: [preferably a CSS that have access to the pstn] *although I will suggest you to configure an special CSS for mobility to avoid fraud
Calling Party Transformation CSS: [none]
Leave all the rest as default
Select Save
Proceed to a new DN by clicking on the Line[1] – Add a new DN link
For this example I have created DN 0621, and it's the same DN that I am using in the Cisco 7961 IP Phone that I created above, so by entering the DN and selecting the a partition it should auto populate
-Click Save
Step 5.- Create a new Remote Destination
Go to the Cisco Unified Communications Manager Administration page
Select Device
Select Remote Destination
Click the Add New button
Enter the following Settings
Name: mobilityuser_mobilephone
Destination Number: 9+[mobile phone number] (please refer to your dialplan)
Answer too Soon Timer: leave as default
Answer too Late Timer: leave as default
Delay Before Ringing Timer: leave as default
Remote Destination Profile:[select the newly created remote destination profile]
Select the mobile phone check box
Click Save
Next select the Line association check box and click Save
You may need to reset the phone that is associated with the mobile connect user
Your user is now ready to begin using the mobile connect feature
While connected on a call the user will need to press the mobility softkey select
Send call to Mobile Phone and the call will sent to his/her mobile phone, to reverse back to his/her Cisco IP phone he/she will need to simply hang up their mobile phone
you need to assign a css to Rerouting Calling Search