2.  New Server and Site

 

Function

Description

Note

Deployment and Template

Ÿ  Deployment Modal

- CUCME-Midsize 500

- CUCM-Midsize 1000

- CUCM-Midsize 2500

 

Ÿ  CUCM Template

 - CUCM Template Packet

•     Deployment Modal support:

- Midsize 500 using CUMBE6K for up to 75 remote sites with 2 Servers running  VMWare and co-resident CUCx.

Ask if they want one or two servers node names.  One server will be the default.

- Midsize 1000 using CUCM +UCx for up to 75 remote sites with 2 CUCM servers + 1 CUCx Server

Ask for one or two CUCM server node names. Two server will be the default.

- Midsize 2500 using CUCM + Ucx for up to 75 remote sites with 3 CUCM Servers + 1 CUCx Server

Ask for one , two  or three CUCM server node names. Three server will be the default.

 

•     CUCM Template Packet in directory ‘template/server’, such as ‘ConfigurationExport.tar’. SBCC automatically read all template packets name and display them in the selection list. After a template packet is chosen, SBCC get CUCM version from header.txt in the template packet.

General Information

- CUCM Node(1 or2 or3)

- Headquarters Site

- Support Site(0-74)

The number of remote sites only 0-74.

Site Information

- Site Name

- Subset

- Subset Mask

- IP Address of the SIP Gateway

Detail information for each site.

Dian-Plan

- Phone Auto

Registration  w/DN

Extension Range

- Voice Messaging

Information

Voice Messaging Information includes Voicemail ports, Hunt, MWI On Number and MWI OFF Number.

Overview

Overview

Show all the parameters of the previous step for finally confirm.

Configuration

Ÿ  Export File

 - File Name

Ÿ  Configure Server

- IP Address

- Username

- Password

 

 

SBCC provide two ways to save configuration:

Ÿ  Export File - SBCC provides a default file name in the format Export_ Server_YYYYMMDDhhmm.tar (for example.

Export _Server_201107061530.tar). The file name can be modified and the file is stored in the directory ‘packet/server’.

Ÿ  Configure Server- SBCC will connect CUCM via IP address and Username/Password, and then get the CUCM version. If the version and version of template is different, SBCC will prompt that CUCM version does not match with the template, and cannot be updated. Otherwise, if they are the same, SBCC configure CUCM through AXL in real-time.

 

* Configuration value consists of the data entered by the SBCC and the data in template packet.

* The two options can be multiple choice.

Performance

Performance

Execute configuration and displays the log.