1|P a g e

IP PHONE INFORMATION

Device Name Extension DID MAC Address

HQ Phone 1 2001 140820Y2001 02004C4F4111
HQ Phone 2 2002 140820Y2002 02004C4F4112
HQ Phone 3 2003 140820Y2003 02004C4F4113

SB Phone 1 3001 197230Y3001 02004C4F4111

SB Phone 2 3002 197230Y3002 02004C4F4112

SC Phone 1 4001 852250Y4001 03004C4F4111

SC Phone 2 4002 852250Y4002 03004C4F4112

2|Pa g e
LIST OF IP ADDRESSES FOR SERVER

Server Type Hostname IP Address Username Password

hq cucm hqucmpub 142.100.64.11 administrator voicebootcamp
pub
hq cucm hqucmsub 142.100.64.12 administrator voicebootcamp
sub
hq unity hqunity 142.100.64.15 administrator voicebootcamp
connection
uccx hquccx 142.100.64.19 administrator voicebootcamp
im & hqimp 142.100.64.17 administrator voicebootcamp
presence
sb cm sbucmpub 142.100.65.11 administrator voicebootcamp
publisher
sb imp Sbimp 142.100.65.17 administrator voicebootcamp
sc cm scucmpub 142.100.66.11 administrator voicebootcamp
publisher
sc imp Scimp 142.100.66.17 administrator voicebootcamp

expressway Expc 142.1Y.64.40 admin voicebootcamp

c
expressway expe 142.1Y.65.40 admin voicebootcamp
e

Router IP GW IP Loopback
HQ Router vcube1 142.100.64.254 Virtual IP 142.100.64.174
Primary
HQ Router vcube2 142.100.64.254
Secondary
SB CUBE Vcube1 142.100.65.254

3|P a g e
 SC Vcube1 142.100.66.254
PSTN 142.100.64.200 SME 142.100.64.101
NTP Server 135.11.11.11
DNS/Active 142.1Y.64.100 Ext DNS: 142.100.64.10
Directory
Certificate 170.170.170. Vbcpod.com\administrator voicebootcamp

Server

Pstn phone MAC: AAAABBBBCC11 TFTP: 142.100.64.200

Line 1 140820Y1111 candidate pc1 142.100.64.99 administrator/voicebootcamp
Line 2 19723032222 candidate pc2 142.100.65.99 administrator/voicebootcamp
Line 3 85225053333 candidate pc3 142.100.66.99 administrator/voicebootcamp
Line 4 442085054444
Line 5 911/999

4|P a g e
 1. CERTIFICATE AUTHORITY CONFIGURATION

Configure Certificate Server on 142.100.64.55. Ensure that every UC Server is secured using domain
vbcpodY.com. Configure Multi-Server Certificate on Cisco CUCM Cluster in HQ

1. Post Deployment Tasks 🡪 Configure Active Directory Services

A. 🗹 Certification Authority
B. 🗹 Certification Authority Web Enrollment
2. CA Console 🡪 Certificate Templates 🡪 Manage
3. Copy Web Server Template
A. Name CCIE
B. Client/Server Auth
4. CA Console 🡪 Certificate Templates 🡪 New 🡪 Certificate Template to Issue
A. Select CCIE
B. Click Save

5|P ag e
 2. DNS CONFIGURATION

All forward zones are configured. However, SRV record must be created as per the table:

Public DNS: 142.100.64.10

• Domain: vbcpodY.com
• _collab-edge → 142.1Y.65.40

Private DNS: 142.1Y.64.100

• Domain: vbcpodY.com
• _cisco-uds - hqucmpub.vbcpodY.com – Priority 2
• _cisco-uds – hqucmsub.vbcpodY.com – Priority 1
• _cup_login – hqimp.vbcpodY.com

6|P a g e
 3. UC SERVICE ACTIVATION

Configure HQ CUCM Cluster with Subscriber as active TFTP and Primary CallManager Server where
Jabber Phone will register to. While Fallback to Publisher. Ensure CUCM, TFTP, DNA, BAT, AXL
Services are activated.

Publisher should be configured with only one NTP Server: 128.100.56.135. No other NTP Server is
allowed.

SiteB and SiteC CUCM should also be configured with the above NTP Server with respective time zone.
Ensure CUCM, TFTP, DNA, BAT, AXL Services are activated.

Both HQ and SB IMP must have all services activated with NTP Server: 128.100.56.135

4. CUCM FUNDAMENTAL

Service Parameters in HQ/SB CUCM must be configured as follow

• T302 Timer = 3000

• Call Forward No Answer = 20
• Call Classification = OnNet

Register HQ phone 1 (jabber) to HQ CUCM cluster and Site B (jabber) phone 1 to Site B CUCM,
according to provided telephony number scheme provided. Ensure the HQ phone is provisioned with
TFTP redundancy such that the publisher CUCM is the backup TFTP server. Extension-to- extension
dialing of each site uses 4 digits only. Caller name display should be delivered on internal 4- digit calls-
use trivial caller names such as "HQ Phone 1" and "Site B Phone 1".

Lastly, both phones should display globalized calling numbers on the upper right-hand corner of the
phone screen. Refer to the exhibit below for an example captured on HQ Phone 1.

User Management with LDAP Integration

Synchronize HQ Users to Cisco Unified Communications Manager in HQ

◼ LDAP filters must be used to import only HQ users.

◼ Users to import are HQ Phone 1 (2001) and HQ Phone 2 (2002).
◼ Authenticate the user login against the LDAP server.

Integrate Cisco Unified Communications Manager with Cisco Unified Communications IM and
Presence

7|Pa g e
Cisco Jabber Setup and Verification, Register the Clients, and Verify Basic Functionality

◼ Register Cisco Jabber on PC1 (Jabber1) with user HQ Phone 1 (2001).

Use the Caller ID CSF HQ Phone 1.
◼ Register Cisco Jabber on your Laptop temporarily with the HQ setup as
user HQ Phone 2 (2002). Use the Caller ID CSF HQ Phone 2
◼ Authenticate the user logins against the LDAP server.
◼ Add contacts from the LDAP server to the contact list. For user 2001, add
2002, and vice versa.
◼ Make sure that users 2001 and 2002 can control their own phones, 2001
and 2002, with Cisco Jabber.
◼ Verify that you can call, IM, and see the presence status between user
2001 and user 2002.
◼ The presence status should also be reflected on Cisco Jabber when using
the phone.
◼ Calls should be working in softphone and deskphone mode.

5. SIP TRUNKING

Configure R1 (HQ-CUBE) as Cisco Unified Border Element interconnecting HQ and SiteB CUCM clusters
using SIP protocol using HA. All 4-digit inter-site calls between HQ and Site B must go through R1,
which must terminate media traffic, but pass through codec requested by endpoints. Make sure codec
is used for all inter-site calls between HQ and Site B. For example, when 2001 calls 3001, the call must
go through R1using ILBC codec

6. CUCM SIP TRUNK TO PSTN TROUBLESHOOTING

Build a SIP Trunk between the HQ CUCM cluster and the backbone CUCM (IP address 157.26.1.11) to
enableH.264 video over IP between HQ Phone 2 and the PSTN phone.

Create a single route pattern,85151111,on your CUCM and send the call over the SIP Trunk to the
backbone CUCM. Use 8202xxxx, where xxxx is the 4-digit internal extension number, as the calling
number for these calls. Do not send the calls through any intermediate routing identity (such as CUBE)

Use RTMT in CUCM traces to find out why calls failed to complete through the SIP trunk to backbone
CUCM. Find the following two SIP events and save the exact SIP messages in two separate notepad
files on PC-l's Desktop and name the files "SIP-TS-Eventl" and "SIP-TS- Event2" correspondently.

• Event 1: The SIP message where H.264 video capability is first passed.

8|P ag e
 • Event 2: The SIP message where the call failed

9|P a g e
 7. CALL-ROUTING POLICIES ON HQ

The Phone number in the United Kingdom does not need a 44 prefix if called from the United Kingdom.
It should simply be dialed with the access code 9 followed by 442085054444

Emergency, toll-free, and premium numbers are reachable only from their respective countries.

Test inbound calls by using line on the PSTN to HQ phone from UK. Calls from the PSTN do not require
an access code.

All PSTN calls routed by the HQ Cisco Unified Communications Manager must use a single route
pattern \+!

Users should dial PSTN access code 9 to place PSTN calls. International calls must be terminated with
the # key.

All PSTN calls should egress at the local gateway using Local Route Group. Do not send + prefix to the
PSTN. The PSTN expects number types on called numbers.

HQ gateway should send all outgoing calling numbers as a ten-digit number with TON=subscriber.

Ensure that HQ phones are reachable from the PSTN

10 | P a g e
 8. CALL-ROUTING POLICIES ON SB

Ensure that long distance national calls from SITEB continue to work using the HQ-CUBE first and local
gateway as backup.

Backup national calls that egress the SITEB gateway should be sent with calling numbers as a 10-digit
number with TON=national.

All calls must be dialed with access code 9.

11 | P a g e
 9. URI DIALING AND ILS

◼ Configure HQ phone 1 with the following URIs, all associated with the first
line (2001):
— [email protected] (primary URI)

— [email protected]

— [email protected]

◼ Configure SB phone 1 with the following URIs, all associated with the first
line (3001):
— [email protected] (primary URI)

— [email protected]

— [email protected]

◼ BB phone is preconfigured with the following URIs, all associated with the
first line (5001):
— [email protected] (primary URI)

— [email protected]

— [email protected]

1.2. CONFIGURE URI SPEED DIALS (BASIC: 2 POINTS)

◼ Configure HQ phone 1 with the following URI speed dials:
— [email protected]

— [email protected]

Configure SB phone 1 with the following URI speed dials:

— [email protected]

— [email protected]

Configure Intercluster URI Call Routing

◼ Call routing for number-based call routing is preconfigured (route patterns,

route lists, route groups, and SIP trunks). You can reuse and modify existing
configuration elements but make sure that number-based call routing
continues to work between the HQ, SB, clusters after you added support for
URI-based call routing.

12 | P a g e
 ◼ URI-based call routing is preconfigured at the BB cluster. The preconfigured
SIP route patterns are:
— hq.vbcpodY.com.vc

— sb.vbcpodY.com.vc

◼ HQ phone 1 has to be able to call all URIs configured in the other clusters.
SiteB phone 1 has to be able to call all URIs configured in the other clusters.

All intercluster calls should be routed directly to the destination cluster.

In the HQ the subscribers should be the preferred server for exchanging SIP signaling messages. The
publishers should be the backup server for exchanging SIP signaling messages.

Configure Class of Service for URI Call Routing

◼ Do not rename partition Directory URI.

◼ Do not add partition Directory URI to any CSS.
◼ Change the configuration so that the following URIs are all associated
with the first line of HQ phone 1 (2001):

— [email protected] (primary URI)

— [email protected]

— [email protected]

— [email protected]

— [email protected]

◼ Do not configure more than four URIs at the DN configuration page.

All configured URIs have to be reachable from all phones, except for the following calls.

13 | P a g e
 10. VOICE MESSAGING INTEGRATION

Integrate HQ to Cisco Unity Connection with Cisco Jabber

◼ Integrate Cisco Unity Connection and Cisco Unified Communications Manager in HQ via
SIP.
◼ Set up Cisco Unity Connection using the most efficient method.
◼ Synchronize the users 2001 and 2002 from the LDAP server or Cisco Unified
Communications Manager.
◼ Make sure that both users can retrieve their voice messages with Cisco Jabber.
◼ MWI notification should reflect leaving and retrieving voice messages on Cisco Jabber.

Configure SB to Integrate the Call Processing and Presence Systems

◼ Integrate Cisco Unified Communications Manager and Cisco Unified
Communications IM and Presence in SB with a minimum amount of effort.
◼ Manually configure user SB Phone 1 (user 3001) on SB.
◼ Register Jabber in location SB with user 3001.

14 | P a g e