Business Edition 7000 Appliances are shown in following
Call Controll (Cisco Unfiied Communication Manager)
Call control is the core element for any communications deployment. It provides endpoint registration,
call processing, and call admission control. Call control design considerations include the dial plan,
endpoint addressing scheme, calling party presentation, call admission control, codec selection, PSTN
connectivity, and general trunking requirements, as well as other factors.
Cisco Unified Communications Manager (Unified CM) provides a common call control platform for all
Cisco Collaboration deployments. Having a highly available and common call control
component for a communications infrastructure is crucial to provide consistent services for all devices
and communication types and to preserve a uniform dial plan and a consistent feature set across the
deployment.
Adding the IM and Presence Service to a Cisco Unified CM deployment provides instant messaging,
network-based presence, and federation for third-party chat servers, and it enables the use of Cisco
Jabber for instant messaging, presence, and audio and video communications.
Device Name CUCM-P1-T1
IP address , GW ??
Doman Name ??
DNS , IP ??
Administrator ID , Password MOGAdmin/******
Organization , Unit , Location , State and Country Mellita, CCUM, Dahra, Tripoli, Libya
NTP (Vspher & Router ) ??
Security Password ??
Aplication Username and Password MOGTEL/******
LDAP IP address ??
LDAP user ??
LADAP password ??
Device Name CUCM-S1-T1
IP address , GW ??
Doman Name ??
DNS , IP ??
Administrator ID , Password MOGAdmin/******
Organization , Unit , Location , State and Country Mellita, CCUM, Dahra, Tripoli, Libya
NTP (Vspher & Router ) ??
Security Password ??
Aplication Username and Password MOGTEL/******
LDAP IP address ??
LDAP user ??
LADAP password ??
Device Name CUCM-S2-T1
IP address , GW ??
Doman Name ??
DNS , IP ??
Administrator ID , Password MOGAdmin/******
Organization , Unit , Location , State and Country Mellita, CCUM, Dahra, Tripoli, Libya
NTP (Vspher & Router ) ??
Security Password ??
Aplication Username and Password MOGTEL/******
LDAP IP address ??
LDAP user ??
LADAP password ??
Device Name CUCM-M1-T1
IP address , GW ??
Doman Name ??
DNS , IP ??
Administrator ID , Password MOGAdmin/******
Organization , Unit , Location , State and Country Mellita, CCUM, Dahra, Tripoli, Libya
NTP (Vspher & Router ) ??
Security Password ??
Aplication Username and Password MOGTEL/******
LDAP IP address ??
LDAP user ??
LADAP password ??
After the first Unified CM platform is installed, there are several configuration steps that have to be completed in
order to prepare the publisher for the remaining servers.
Server Configuration
The server configuration to specify the address of the server where Cisco CallManager is installed. If your
network uses Domain Name System (DNS) services, you can specify the host name of the server. If your
network does not use DNS services, you must specify the Internet Protocol (IP) address of the server, Cisco
Recommends using the IP Addresses.
Step1: In a web browser, access the IP address or hostname of the publisher
Step 2 From Cisco Unified CM Administration, choose System > Enterprise Parameters.
Step3: In a web browser, Navigate to System > Server,
Click Find
You Can Change each Hostname to by IP Address if you don't using DNS Servers.
step 4: Check Unified Communications Manager Services
CM Groups Configuration
A Cisco Unified Communications Manager (CUCM) group specifies a prioritized list of up to three Cisco Unified
Communications Manager (CUCM)s. The first Cisco Unified Communications Manager (CUCM) in the list
serves as the primary Cisco Unified Communications Manager (CUCM) for that group, and the other members
of the group serve as secondary Cisco Unified Communications Manager (CUCM)s. Each device pool has one
Cisco Unified Communications Manager (CUCM) group assigned to it. When a device registers, it attempts to
connect to the primary (first) Cisco Unified Communications Manager (CUCM) in the group that is assigned to
its device pool. If the primary Cisco Unified Communications Manager (CUCM) is not available, the device tries
to connect to the next Cisco Unified Communications Manager (CUCM) that is listed in the group, and so on.
Cisco Unified Communications Manager (CUCM) groups provide important features for your system
· Redundancy: This feature enables you to designate a primary and backup Cisco Unified Communications
Manager (CUCM)s for each group.
· Call processing load balancing: This feature enables you to distribute the control of devices across multiple
Cisco Unified Communications Manager (CUCM)s.
Auto-Registration
Auto-registration allows Cisco Unified CM to automatically assign a directory number to new phones as they are
deployed in your network. With Cisco Unified Configurator for Collaboration (CUCC), auto-registration is enabled
by default in order to allow for quick and easy deployment of phones. After the phones are registered and the
guide has been followed completely, users configured in the system can utilize Cisco Extension Mobility to log
into the auto-registered phones.
By default, auto-registered phones are able to dial on-net directory numbers as well as off-net emergency 911
calls. They are not, however, able to dial off-net numbers.
Leaving auto-registration enabled carries a security risk in that “rogue” phones can
automatically register with Cisco Unified CM. You should only allow auto-registration for
brief periods when you want to perform bulk phone adds during phone deployment.
Communications Manager Date/Time Configuration
Date/Time Groups define time zones for the various devices that are connected to Cisco Unified
Communications Manager (CUCM). Cisco Unified Communications Manager (CUCM) provides a Date/Time
Group called Main_DTG that configures automatically when you install Cisco Unified Communications
Manager (CUCM); however, Cisco recommends that you configure a group for each local time zone.
Main_DTG synchronizes to the active date and time of the operating system on the Cisco Unified
Communications Manager (CUCM) server. After installing Cisco Unified Communications Manager (CUCM),
you can change the settings for Main_DTG as desired. Normally, you adjust the server date/time to the local
time zone date and time. Main_DTG is changed to LIBYA_DTG and configured for Africa/Tripoli Time Zone
(GMT+2) as Tripoli Time .
Region Configuration
Regions specify the bandwidth that is used for audio and video calls within a region and between existing used
per audio call. The video call bandwidth comprises the sum of the audio bandwidth and video bandwidth but
does not include overhead.
Location
Locations are used to implement call admission control in a centralized call-processing system. Call admission
control enables you to regulate audio quality and video availability by limiting the amount of bandwidth that is
available for audio and video calls over links between the locations. If you do not use call admission control to
limit the audio and video bandwidth on an IP WAN link, an unlimited number of calls can be active on that link
at the same time. This situation can cause the audio quality of each audio call and the video quality of each video
call to degrade as the link becomes oversubscribed. In a centralized call-processing system, a single Cisco
Unified Communications Manager (CUCM) cluster provides call processing for all locations on the IP telephony
network. The Cisco Unified Communications Manager(CUCM) cluster usually resides at the main (or central)
location, along with other devices such as phones and gateways. The remote locations contain additional
devices, but no Cisco Unified Communications Manager (CUCM). IP WAN links connect the remote locations
to the main location. Milieta uses the default Hub_None Location which is Unlimited Bandwidth
Call Admission Control
The default design is a hub-and-spoke topology in which each remote site is connected to the headquarters site
over a bandwidth-constrained WAN. The CUCC design uses regions and locations to define locations-based
Call Admission Control. For calls within a site, the regions are configured for the G.722 or G.711 codec running
at 80 kbps, and there are no limits to the number of calls allowed within a site
For calls between the sites, the regions are configured for the G.729 codec running at 24 kbps. The size of the
site determines the CUCC default voice bandwidth setting for inter-site calls. For sites with only 500 users, the
default setting is two inter-site calls (48kbps); for sites with 10,000 users, the default is eight inter-site calls (192
kbps). The amount of bandwidth in and out of each site can be modified within CUCC, if the defaults do not
match the provisioned WAN bandwidth.
By default, Call Admission Control is not calculated for calls to and from the central site (headquarters). It’s
expected that as long as the spokes are provisioned for Call Admission Control, the hub will not be
oversubscribed on a traditional WAN. This is the case for all hub-and-spoke topologies; however, for a
Multiprotocol Label Switching (MPLS)–based network, which is considered a hub-less hub and spoke, you will
need to modify the headquarters site default bandwidth within CUCC to provide the correct Call Admission
Control based on the speed of the link.
Device Pool
Device pools define sets of common characteristics for devices. The device pool structure supports the
separation of user and location information. The device pool now contains only device- and location-related
information. The Common Profile window records all the user-oriented information. Ensure that each device is
associated with a device pool and with a common profile for user-oriented information.
Active Directory Integration
Active Directory integration allows you to provision users automatically from the corporate directory into the
Cisco Unified CM database, which makes it possible to maintain a single directory as opposed to separate
directories. Therefore, you don’t have to add, remove, or modify core user information manually in Unified CM
each time a change occurs in the corporate directory. The other advantage is that end users are able to
authenticate to Unified CM and Cisco Unity Connection by using the same credentials in Active Directory,
which reduces the number of passwords across the network
User Authentication
The authentication process verifies the identity of the user by validating the user ID and password before
granting access to the system. Verification takes place against the existing database or the LDAP corporate
directory.
The system will make authentication available in the LDAP Authentication window because LDAP
synchronization will be enabled in the LDAP System window. Both synchronization and authentication will be
enabled; therefore the following actions take place:
**The system always authenticates application users against the Unified Communication Manager database but
since both synchronization and authentication are enabled, the user gets authenticated against the corporate
directory. Thus, users need to use their corporate directory password.
LDAP System Configuration for Militea’s UC Cluster
With synchronization enabled with the LDAP server, the following circumstances occur:
The administrator cannot modify end user data, except for the fields (attributes) that are not synchronized from
The administrator can modify the LDAP Directory information.
The administrator can modify LDAP Authentication information.
If synchronization with the LDAP server is not enabled (is disabled), the following circumstances occur:
The administrator cannot modify LDAP Directory information.
The administrator cannot modify LDAP Authentication information.
Microsoft Active Directory “LDAP Directory Configuration
Parameters Parameter Value
LDAP DIRECTORY CONFIGURATION (visible only after enabling synchronization from the Ldap System
configuration)
NOTE: After configuring the directory,
1. Existing End Users not Found in the Corporate directory will be deleted
2. For the correct integration of LDAP users with Unified Communication Manager, it is necessary that the
3. The username used in below must be a user who is an administrative user that has access rights to the LDAP
LDAP Directory Information
LDAP Configuration Name CN=
LDAP Manager Distinguished Name DN=
LDAP Password <NCE/Customer to enter password>
Confirm Password <NCE/Customer to enter password>
LDAP User Search Base Cn=users,dc=domain,dc=com
LDAP Directory Synchronization Schedule
Perform Sync Just Once UnChecked
Perform a Re-sync 1 Days
Next Re-sync Time (YYYY-MM-DD hh:mm) …........................
User Fields To Be Synchronized
Cisco Unified Communications Manager User Fields LDAP User Fields
User ID sAMAccountName First Name givenName
Middle Name middleName Last Name sn
Manager ID manager Department department
Phone Number telephoneNumber Mail ID sAMAccountName
LDAP Server Information
Host Name or IP Address for Server* 1.1.1.1
LDAP Port* 389
Use SSL Unchecked
Device
Cisco Unified Communications Manager (CUCM) allows you to configure the following devices in your telephony network:
Deploy IP phones
IP Phone Models that are installed in Miletta as per below:
Cisco 8841
Cisco 7841
Cisco CS-DESKPRO
Cisco CS-DESKMINI-
Cisco WL-730
Cisco 8832
Cisco 7940
Cisco 7945
Cisco 7965
Third-party SIP Device
ATA191-K9
Jabber Client (Cisco Jabber for Windows, iPhone, Android and iPAD).
Register IP Phone
Manually add SCCP Phones to Cisco Communications Manager
We will using that for Old Phone only after confirm the Aut Reg is Stop (only one phone from Each Type)
Before adding any SCCP phones manually into the CUCM, the MAC addresses of these Phones must be known.
1. On Cisco Unified Communications Manager Administration page, from the menu select Device > Phone.
2. On Find and list phones, click Find button to list all IP Phones have been configured on the cluster. If this is a new installation,
3. Click Add New button to add new IP Phone.
4. On Add a new phone button, select Cisco 7965 for the phone type, and click Next.
5. Select SCCP and click Next.
6. Add phone with the following parameter:
– Device Name: MAC address which is used by this particular phone
– Description: Phone2-1
– Device Pool: Chicago
– Owner: Anonymous
– Phone button Template: Standard Cisco 7965 SCCP
– Device Security Profile: Cisco 7965 – Standard SCCP Non-Secure Profile
7. Click Save.
8. On Phone configuration page, click Line [1] – Add a New DN link, to modify the phone number of the phone.
9. Use the following parameter for the directory number configuration:
– Directory number: 2018
10. If
11. you Save
Click wantand thenmore
to add Apply.
phones, you have to repeat steps 3 – 10. For example Phone 2-2 will have the following
configuration:
– Device Name: MAC address which is used by this particular phone
– Description: Phone 2-2
– Device Pool: Chicago
– Owner: Anonymous
– Phone button template: Default Cisco 7965 Template.
– Device security profile: Standard SCCP Profile for Cisco 7965
– Directory number: 2018
12. Click Save and then Apply.
Using BAT to register IP Phone
o Step 1 In Cisco Unified Communications Manager Serviceability, make sure that the Cisco Bulk Provisioning
service is activated on the publisher.
Create an IP Phone Template for Use with BAT
Step 2 In Cisco Unified Communications Manager Administration, navigate to Bulk Administration > Phones > Phone
Template and click Add New.
Step 3 Select Cisco 7965 for Phone Type and click Next.
Step 4 Leave SCCP as device protocol and click Next.
Step 5 Create the new phone template with these parameters:
Template Name: BAT-7965
Description: 7965 template
Device Pool: SubPub
Phone Button Template: Standard 7965 SCCP
Device Security Profile: Cisco 7965 – Standard SCCP Non-Secure Profile
Leave all other settings at their default values and click Save.
Create the CSV File Using the Cisco Unified Communications Manager BAT Spreadsheet
Step 6 Cisco Unified Communications Manager Administration, choose Bulk Administration > Upload/Download Files and
click Find.
Step 7 Check the check box next to the bat.xlt file and click Download Selected.
Step 8 In the new dialog window, click Save, and then navigate to the C:\ directory on your local PC.
Step 9 Change the filename in the File Name field to bat7960.xlt and click Save. Wait until the file is downloaded to your
local PC.
Step 10 Open the file on your local PC using MS Excel.
Step 11 On the Phones spreadsheet tab, click the Phones radio button, then click Create File Format.
Step 12 On the new dialog window, highlight the Directory Number in the Line Fields pane, and then click the right arrow
button to move it to the Selected Line Fields pane.
Step 13 Click Create, and then click Yes on the pop-up window to overwrite the existing file.
Step 14 In the Maximum Number of Phone Lines field, enter 2 to create two lines for new IP phones. Then click into any
other portion of the spreadsheet to leave the field so that phones. Then click into any other portion of the spreadsheet to
leave the field so that the sheet is updated with the selected number of lines. the sheet is updated with the selected
number of lines.
Step 15 Check the check box next to the Dummy MAC Address field.
Step 16 Enter All Others IP phones with the parameters
Validate the IP Phone Template and CSV File
Insert IP Phones into the Cisco Unified Communications Manager Database Using BAT
Complete these steps:
Step 1 Go to Bulk Administration > Phones > Insert Phones.
Step 2 Select the previously uploaded CSV file from the File Name drop-down menu.
Step 3 Select BAT-7961 from the Phone Template Name drop-down menu.
Step 4 Check the check box next to Create Dummy MAC Address.
Step 5 Click the Run Immediately radio button.
Step 6 Click Submit.
Step 7 Go to Bulk Administration > Job Scheduler and click Find.
Step 8 If the Status column of the phone insertion job does not show Completed, click Find
again. Repeat this step until you see the status “Completed.”
Step 9 Click the phone insertion Job Id link and make sure that the job has completed
successfully. You can also review the log file.
Configure User and Device Profiles
Step 1: Select Bulk Administration > Import/Export > Export.
Step 2: Enter a tar file name such as DirectoryUsers and select the End User check box within the User Data section.
Step 3: Select the Run Immediately button and select Submit and OK
Step 4: Select Bulk Administration > Job Scheduler and check the status of the export job submitted
Step 5: After the Job Status indicates successful completion, select Bulk Administration > Upload/Download Files.
Step 6: Select the exported file name (DirectoryUsers_date and time.tar) created by the export operation and then select
Download Selected. Save
Step 7: Open the downloaded tar file using an archive program that supports tar format and extract the enduser.csv file for
use later.
Step 8: Select Bulk Administration > User Device Profiles > UDP Template and select Add New
Step 9: Select the correct phone model from the Device Profile Type dropdown box and select Next.
Step 10: Select the Device Protocol as SCCP if the Device Protocol dropdown is presented.
Step 11: Enter a User Device Profile Template Name (i.e. 7965 Standard Template), select a Phone Button Template from
the drop-down and select Save.
Step 12: Select Line [1] - Add a New DN.
Step 13: Enter a name in the Line Template Name field (i.e. Default Line Template) and for Route Partition select
PAR_Base. Also check the Voice Mail check boxes for the items in the following figure, to enable forwarding to voice mail
correctly, and then select Save.
Step 14: Select the Go button to return to the UDP Template Configuration page, then select Save.
Step 15: From the RDMCT, check only User and Device Profile Configuration Phase and click Next.
Step 16: Assign one or more extension ranges to the headquarters site and each remote site. Enter a 4 digit starting
extension in Reserved Extension Range Start and a X digit ending extension in Reserved Extension Range End. Click + to
add additional start/end extension ranges or click – to remove the unwanted extension ranges. Click Next when complete.
Step 17: Click Browse to locate endusers.csv extracted in step 7.
Step 18: For each User Device Profile (UDP), populate the Directory Number, External Phone Number Mask, Line CSS,
and Line Text Label. Click Configure.
Step 19: After Configure is selected the system will display a confirmation dialog box, click OK to generate the list of files
that will be used for the rest of the procedure.
Step 20: Repeat for each UserDeviceProfiles.csv file created by RDMCT
Step 21 Repeat for each UDP Template created in step 8.
Step 22: Select Run Immediately and then select Submit.
Step 23: Download the Files
Step 24: Upload file after complete evry thing
Note: you can do the Phone Regestartion after completed the Dial Plane and Clsssification, it is easy for controlling /each
CTI route points .
A computer telephony integration (CTI) route point designates a virtual device that can receive multiple, simultaneous calls
for application-controlled redirection. For first-party call control, you can optionally add a CTI port for each active voice line
(the CTI application determines this). Applications that use CTI route points and CTI ports include Cisco IP Softphone,
Cisco Unified Communications Manager Auto-Attendant, and Cisco IP Interactive Voice Response System. After you add a
CTI route point to Cisco Unified Communications Manager Administration, information from the RIS Data Collector service
displays in the CTI Route Point Configuration window. When available, the IP address of the device and the name of the
Cisco Unified Communications Manager with which the device registered display. CTI RP is configured in Assaraya bank
for Self Provisioning IVR number XXXX When you dial the CTI Route point to associate a phone to the user,the IVR
prompts play.
Step 1 From Cisco Unified Serviceability, choose Tools > Service Activation.
Step 2 From the Server drop-down list, select the publisher node and click Go
tep 3 Under CM Services, check Cisco CTI Manager
Step 4 Under CTI Services, check Self Provisioning IVR. Click Save
Step 5 In Cisco Unified CM Administration, choose System > Cisco Unified CM. Click on the publisher node
Step 6 Select the Universal Device Template that you want to be applied to provisioned phones.
Step 7 Select the Universal Line Template that you want to be applied to the phone lines for provisioned phones.
Step 8 Use the Starting Directory Number and Ending Directory Number fields to enter a range of directory numbers to
apply to provisioned phones
Step 9 Uncheck the Auto-registration Disabled on the Cisco Unified Communications Manager check box.
Step 10 Confirm the ports that will be used for SIP registrations. In most cases, there is no need to change the ports from
their default settings. save
Step 11 From Cisco Unified CM Administration, choose, Device > CTI Route Points
Step 12 Complete either of the following steps:
Note: In the Device Name field, enter a unique name to identify the route point
Under Association click Line [1] - Add a new DN. (In the Directory Number field, enter the extension that you want
users to dial to access theSelf Provisioning IVR service.
Gateway
Cisco Unified Communications gateways enable Cisco Unified Communications Manager (CUCM) to communicate with
non-IP telecommunications devices. Cisco Unified Communications Manager (CUCM) supports several types of voice
gateways. This section contains the following gateway devices:
H.323 Gateway
MGCP Gateway
Basic Configuration of MGCP
Gateway CLI Configuration
(config)# mgcp call-agent X.X.X.X IP address for Server
(config)# ccm-manager config server IP address for Server
(config)# ccm-manager config
(config)# ccm-manager mgcp
(config)# mgcp
MGCP support in CUCM includes a wide range of analog and digital interfaces that can be used ton several Cisco router
and switch platforms. FXO, FXS, T1-CAS, T1-PRI, E1-CAS, E1-PRI but some voice ports are not supported by MGCP say,
E&M voice ports. CUCM pushes the Cisco IOS MGCP gateway configuration from the Cisco TFTP server to the gateway
when automatic configuration is configured.
ntrolling /each user
