Feature server or evolution server administration checklist

Last Updated : Nov 08, 2013 |
Prolog information
Use this checklist to administer Communication Manager as a feature server or an evolution server.
No.
Task
Link
1
Administer the dial plan.
2
Add the feature access codes for AAR and ARS.
3
Add the appropriate SIP domain in the network region.
4
Assign a node name to the IP address of the security module of Session Manager.
5
Add a SIP signaling group.
6
Add trunk groups for each Session Manager.
7
Configure the appropriate route patterns.
8
Administer the uniform dial plan for non-SIP calls.
9
Administer AAR.
10
Administer ARS for non-SIP calls.
11
Add the appropriate route pattern as the proxy route.
12
Administer the incoming call handling treatment.
13
If applicable, add a Survivable Remote server.
14
Modify the public unknown numbering so that a deskphone displays a number in the E.164 format.
15
If applicable, validate the minimum time of network stability for gateways to failback to Communication Manager when Communication Manager becomes available.
16
If applicable, validate the gateway recovery rule.
17
Save translations.
18
Add a privileged administrator for System Manager.
19
Administer Communication Manager as a managed element.
20
Synchronize the Communication Manager data.
21
Add the Communication Manager feature server or Communication Manager evolution server as a SIP Entity.
22
If adding Survivable Remote Session Manager, add as a SIP entity.
23
Create entity links between Session Manager and Communication Manager.
24
Verify the connection between Session Manager and Communication Manager.
25
Administer Communication Manager as an application.
26
Administer Communication Manager in an application sequence.
27
Add users.
28
Verify the users.
29
Test the calls between Session Manager and the Communication Manager feature server or evolution server.