MOP

Method of
Procedure

TABLE OF CONTENTS

Table of Contents.................................................................................................................... 1

OPTANIX MOP V1.0 1

Revision History...................................................................................................................... 1

Change details........................................................................................................................ 2

Affected devices...................................................................................................................... 2

Associated devices.................................................................................................................. 2

Contacts.................................................................................................................................. 2

Supplemental information....................................................................................................... 3

Terminal Servers.................................................................................................................. 3

Vendor Documentation........................................................................................................ 3

Purpose................................................................................................................................... 3

Description........................................................................................................................... 3

Reason for change............................................................................................................... 3

Technical impact/Risk............................................................................................................. 3

Requirements.......................................................................................................................... 3

Preliminary steps.................................................................................................................... 4

Pre-change output collection................................................................................................... 4

Implementation plan............................................................................................................... 4

Implementation.................................................................................................................... 4

Verification........................................................................................................................... 4

Backout Plan........................................................................................................................... 5

Backout Implementation...................................................................................................... 5

Backout Verification............................................................................................................. 5

post-change output collection................................................................................................. 5

Final Steps.............................................................................................................................. 5

REVISION HISTORY
Revisi Tea
Date Engineer Notes
on m

OPTANIX MOP V1.0 2

 1.1

CHANGE DETAILS
Information Details
Optanix Ticket # SSR
Customer Ticket #
Vendor Ticket #
Estimated Duration of
00 hrs and 30 mins
Pre-Checks
Estimated Change
00 hrs and 00 mins
Duration

AFFECTED DEVICES

The following list contains devices that will be modified:

Device Name IP Address Device Type/Function

ASSOCIATED DEVICES

The following list contains devices that will NOT be modified but may be indirectly impacted.

Device Name IP Address Device Type/Function

CONTACTS

The following list contains all individuals involved with the change (including vendors):

Name Organizati Role Email Address Phone Number Primar

OPTANIX MOP V1.0 3

 y
on Contac
t

SUPPLEMENTAL INFORMATION

TERMINAL SERVERS

 Access to the devices is available via jump server

VENDOR DOCUMENTATION

 N/A

PURPOSE

DESCRIPTION

 Certain calls are failing due to internal DN presenting to the carrier. The change is to
check the option in RPs to send the correct CLD.

REASON FOR CHANGE

 Certain calls are failing due to internal DN presenting to the carrier. The change is to
check the option in RPs to send the correct CLD.

TECHNICAL IMPACT/RISK

Low Risk // Medium-High Impact

Risk is low as the work will be done one RP at a time.

REQUIREMENTS
Function Required Details (if function required)
Onsite support ☐

Vendor or TAC ☐

Hardware RMA ☐

Customer/User/App ☒
Testing
WebEx or ☒ WebEx

OPTANIX MOP V1.0 4

 Conference Bridge
Customer contact ☒ Pre/Post Notifications
required before
change

PRELIMINARY STEPS
 Review all steps in the implementation plan before proceeding
 If applicable, create outage for associated device(s) to suppress alarms
 If required, join bridge
 Update case with details from the above steps taken and change case status to “Work in
progress”.
 Notify all listed in the Contact(s) section via email, please follow the format specified in
the Change Management documentation.

PRE-CHANGE OUTPUT COLLECTION

 Take the necessary backups/screenshots of the current configurations that will be
modified and any informative “show” commands. Please reference, MOP Workflow for
more details.
 Filename should utilize a similar format to the below:
[devicename]_[pre,post]-change_[date].log
Date format: yyyy.mm.dd
Example: Router001_pre-change_2014.12.3.log

Cisco CUCM - Pre-Change Output Collection:

The devices have been listed under “Affected Devices” on previous steps.
The actual commands and details are found in: https://tacconnect > Home > Homepage > Health
Checks
Perform a Pre-change Health Check from each node as follows: (Gather, Review and Document)
System Status
System Versions (Active and Inactive)
Hardware from Application perspective
Run a Diagnose Test
Gather a list of Services and Status
NTP Status
Check Last backup and backup history
Cluster Replication
Check for any core dumps

Via RTMT/CLI/GUI:
Gather/Review/Document the following:

 System Resources: CPU, Memory, Disk Usage

 System Health from Alerts– Errors, Warnings, Critical
 Take appropriate action based on Alert Severity
 Phone/Device/End-Point Registration counts.
 Registration details for:
 Phones
 Gateway
 SIP
 Media Resources
 Licensing information and Status

OPTANIX MOP V1.0 5

Cisco Voice Gateway/CUBE - Pre-Change Output Collection:
The devices have been listed under “Affected Devices” on previous steps.
The actual commands and details are found in: https://tacconnect > Home > Homepage > Health
Checks
Perform a Pre-change Health Check from each device as follows: (Gather, Review and Document)
System running configurations
Software Versions
Hardware Inventory and Status
Licensing Status
Interface/Controller Status
Local Flash/Storage details
All voice interface Status (FXO/PRI/FXS)
System Resources health (CPU/Memory)
Signaling Protocol Status (MGCP/SCCP/H323/SIP)
Active Calls Report (if any)
CUBE HA Status (if enabled)
Commit the configurations in flash to the startup configurations.

Client/Server Health Checks:

Gather/Review/Document the following from the “server/CUCM”:

 Gateway/End-Point Registration counts.

o Registration details for:
 Gateway (MGCP/H323/SCCP)
 SIP Trunks
 Media Resources (SCCP)

IOS Backups:

 The data gathered and documented above includes a copy of the configurations, which will be
used as a backup.

IMPLEMENTATION PLAN

Cisco Unified Communications Manager

1. Log in to CUCM Pub:
a. Search each RPs listed below and check the option “Use Calling Party's External
Phone Number Mask” under Calling Party Transformations and save.

routepattern partition
=================== ====================
9.1316212XXXX ICT_Site_Specific_PT
9.1316227XXXX ICT_Site_Specific_PT
9.1316244XXXX ICT_Site_Specific_PT
9.1316281XXXX ICT_Site_Specific_PT

OPTANIX MOP V1.0 6

9.1316283XXXX ICT_Site_Specific_PT
9.1316288XXXX ICT_Site_Specific_PT
9.1316313XXXX ICT_Site_Specific_PT
9.1316321XXXX ICT_Site_Specific_PT
9.1316323XXXX ICT_Site_Specific_PT
9.1316377XXXX ICT_Site_Specific_PT
9.1316435XXXX ICT_Site_Specific_PT
9.1316452XXXX ICT_Site_Specific_PT
9.1316453XXXX ICT_Site_Specific_PT
9.1316535XXXX ICT_Site_Specific_PT
9.1316587XXXX ICT_Site_Specific_PT
9.1316667XXXX ICT_Site_Specific_PT
9.1316745XXXX ICT_Site_Specific_PT
9.1316746XXXX ICT_Site_Specific_PT
9.1316804XXXX ICT_Site_Specific_PT
9.1316835XXXX ICT_Site_Specific_PT
9.1316842XXXX ICT_Site_Specific_PT
9.1316889XXXX ICT_Site_Specific_PT

2. Log into both VGs and update the below translation rules from old to new:

old:
voice translation-rule 5
rule 1 /^1(..........)/ /\1/
rule 2 /^91(..........)/ /\1/ <---

new:
voice translation-rule 5
rule 1 /^1(..........)/ /\1/
rule 2 /^91(..........)/ /\1/ <---

3. If at any point during implementation there are unexpected results that may cause
impact to production:
a. Spot check the appliance to assist in determining the impact
b. Take steps noted in the Unsuccessful Implementation section under Final Steps
c. Call the customer listed in the Contact(s) section
d. Do your best to remediate the issue

VERIFICATION
1. Confirm CUCM Functionality:
• Please a test call from the non-working number and confirm it’s working now.
• Log into the VGs and ensure the correct CLD presenting to the carrier.
• Verify phone functions by making the following types of calls (if applicable):
i. Inter/Intra office
ii. Inbound Calls from PSTN
iii. Outbound calls to PSTN
1. Mobile phone
2. Local
3. National

OPTANIX MOP V1.0 7

 4. International
iv. Voice mail, MWI
• Test the following phone features if applicable:
i. Extension Mobility
ii. Directories
iii. Conference
iv. Barge / C-Barge
v. Transfer
vi. Ring on shared lines (pick up/hold/transfer)
vii. Do Not Disturb
viii. Privacy
ix. Presence
x. CTI call control
xi. Busy Lamp Field
2. Confirm CUC Functionality:
• Leave and retrieve voicemail(s)
• MWI on/off on the end-point
• Message Time Stamps are correct.
• Call Handler:
i. Correct Greeting is played
ii. Navigate thru CH by selecting available options via TUI.
3. If verification fails:
a. Do your best to remediate the issue
b. If unable to remediate, jump to the “Back-out Plan” section
4. If verification succeeds, jump to the “Post Output Collection” section

BACKOUT PLAN

BACKOUT IMPLEMENTATION

1. There is no back out plan for the server/device decommission.

2. Proper vetting should take place prior to deleting the configurations noted in “Config
Cleanup” to confirm they will not in fact be needed anymore.
3. Use a DRS Backup to restore the cluster to a state prior to the.

BACKOUT VERIFICATION

1. N/A

POST-CHANGE OUTPUT COLLECTION

 Take the necessary backups/screenshots of the current configurations and any
informative “show” commands that were run in the “Pre-change Output Collection”
section. Verify for any differences between the pre and post output.
 Filename should utilize a similar format to pre-change filenames

Cisco CUCM - Post-Change Output Collection

OPTANIX MOP V1.0 8

The devices have been listed under “Affected Devices” on previous steps:

 The steps needed here are the same or similar to the “Pre-change output collection” from
previous steps. Repeat all the steps from the “Pre-Change Output Collection” and compare the
outputs to confirm that they match accordingly.

Cisco Voice Gateway/CUBE - Post-Change Output Collection

The devices have been listed under “Affected Devices” on previous steps:

 The steps needed here are the same or similar to the “Pre-change output collection” from
previous steps. Repeat all the steps from the “Pre-Change Output Collection” and compare the
outputs to confirm that they match accordingly.

FINAL STEPS
 Ensure that all debugs and elevated traces are disabled unless explicitly stated
otherwise
 Please refer to the Operations documentation, Change Management, and complete all
steps to finalize the change and to communicate effectively on the change
status/completion.

OPTANIX MOP V1.0 9