Before you can configure SES for Distributed Office using Avaya Integrated Management for Distributed Office, you must complete the initial SES installation and system administration.
Distributed Office Central Manager uses the Management Access login and password information which you have configured for SES. See Installing SIP Enablement Services (SES)on page 7 for more details on these tasks.
Task 1: Installing Distributed Office Central Manager
Avaya Distributed Office Central Manager is a component installed with Avaya Integrated Management for Distributed Office. It can be installed by itself, or with other optional components. Central Manager supports certain remote administration functions.
You use the web-based interface of Avaya Distributed Office Central Manager to configure the core-routing functions (that is, routing between the locations) on your SES Edge 4.0 server.
Note:
Note: Avaya Distributed Office Local Manager cannot be used to administer SES or the
optional SIP server(s).
For details on how to install Avaya Distributed Office Central Manager, refer to Avaya Integrated Management for Distributed Office Release 4.0 Installation, 14-601539.
Task 2: Using Distributed Office Central Manager
Overview of steps to configure SES
Using the Enterprise menu screens in Distributed Office Central Manager, you must enable and configure enterprise private networking on the SES Edge 4.0 server for support of its
core-routing functions. An overview of the steps required to do this using Distributed Office Central Manager is as follows:
1. First, ensure that the box next to the label “Enable Private Networking” is checked. For more information, see Enable private networkingon page 24. Under the General tabon page 30, enter the SIP domain name and the length of the branch prefixes you are using for your Distributed Office network.
2. Under the SES tabon page 31, enter the IP address, login and password for the SES you are using to perform core-routing functions for your Distributed Office network. For more information, see Establish access to SESon page 24.
3. (Optionally) Under the SIP Servers tabon page 33, complete the information about any SIP (home) servers you have for users at your main (or headquarters) location. For more information, see Configure SIP server(s)on page 25.
4. Under the Branches tabon page 34, view the information about each branch location you have previously installed and configured in your Distributed Office network. If you have just enabled private networking, or if have not previously added branches using DIstributed Office Local Manager, then this screen will not show any entries yet. Before you can test and verify core routing and inter-location capabilities, you must ensure that entries for at least one branch are listed. For more information, see View branch locationson page 25.
Overview of steps to verify SES routing
After configuring SES, you can verify that SES is performing its core routing functions properly.
1. If you have not already done so, under the General tabon page 36 of the Branches screen, add a branch location to your Distributed Office network. Saving this information to the system will create a new synchronization job. After it is complete, proceed to the next step.
2. Also under the General tab of the Branches screen, enable enterprise private networking for the new branch. Complete any optional fields on the screen and save your changes again.
3. If you have not already done so, under the General tabon page 39 of the Stations screen, add a branch-location user’s station and its associated extension to the Distributed Office system. Save these changes
4. Repeat Add a new branch locationon page 26 and Include the branch in Private
Networkingon page 26 for each new branch in your Distributed Office network. You may use groups and templates to help you complete these steps for multiple branches. For more details, see the online help system for Avaya Distributed Office Central Manager.
5. Repeat Add a station and its extension to the branchon page 27 for each user’s station at a branch. You may use station templates to help you complete this step for multiple stations.
6. (Optionally) If you have properly configured SIP users in the main location and in one or more of the branch locations with private networking enabled, then you can test the routing of SIP messages by making calls from a station in the main location to a station at a branch, or a call between two branches. If you have supported IM client stations configured in both locations, you can also test instant messaging between them.
For more information
For more details on these steps, see the online help system for Avaya Distributed Office Central Manager or Avaya Distributed Office Central Manager User Reference, ID TBD.
Using the Enterprise menu screens
Under the Enterprise menu in Distributed Office Central Manager are three objects to help manage your network of locations:
● Selecting Network Management Console dataon page 28.
The Network Management Console (NMC) component helps manage various hardware components in your Avaya network. It performs network-node discovery and offers a single, consolidated view of the entire system. For more information, see the online help system or other documentation for Avaya Integrated Management for Distributed Office.
● Private Networkingon page 30
Private Networking is an Avaya Distributed Office Central Manager function for configuring your SES to perform core routing in a Distributed Office network. Optionally, you may have SIP (Home) Servers (typically serving SIP user needs in the main or headquarters location not served by one of the branch Distributed Office platforms), in addition to the SES Edge 4.0 performing core routing, and the total number of hosts can range from one to 1000.
● Software Update Manageron page 35.
The Software Update Manager (SUM) component keeps the software current on various platform components in your Avaya network. For more information, see the documentation or the online help system for Avaya Integrated Management for Distributed Office.
Enable private networking
1. Start a web-browser session and enter the IP address (or fully-qualified domain name, if your enterprise supports DNS) of the computer with Distributed Office Central Manager installed.
2. On the launch page that appears, select Distributed Office Central Manager from the set of installed Integrated Management applications.
3. Login to the system using your Avaya SSO administrative login and password. See your system administrator for more details on setting up this login at system installation time.
4. Select and expand the Enterprise folder in the left-hand navigation pane of the window.
5. Select the Private Networking item under the Enterprise menu, and the Enterprise Private Networking screen appears.
6. Ensure that the checkbox for Enable Private Networking is checked on this screen.
7. Enter the SIP Domain for your Distributed Office network on the General tabon page 30.
The domain must exactly match the Information on the System Properties screenon page 12 that you entered in the SES Master Administration web interface.
8. Enter the digit length for branch prefixes for your Distributed Office network on the General tabon page 30. The range is 1 to 10 digits, and the default length is 3 digits. In this release of Avaya Distributed Office, this branch prefix length must be the same for all Distributed Office locations, but the length of the extensions used at each of the branch locations may vary, so long as the total of the two lengths are no greater than 15 characters.
Establish access to SES
For any Distributed Office network that is not a simple standalone construct, you must ensure that SES is able to communicate with the rest of your Distributed Office network, as follows:
1. On the SES tabon page 31, enter the IP address of the SES Edge 4.0 server performing core routing for your Avaya Distributed Office network.
2. Enter the Management Access login and password information for the SES master database. This information must exactly match the Information on the System Properties screenon page 12.
3. Select the Test SES Connectivity button and a pop-up window should appear with the message “Successfully Connected to Core Router.”
Note:
Note: If this test fails, so will any other changes you try to submit to the SES server.
Double-check that you have entered the login and password correctly, and that they exactly match those you entered in the SES Master Administration interface.
Configure SIP server(s)
On the SIP Servers tabon page 33, enter the following information for each optional SIP server you may have installed to support Distributed Office network users in your main or headquarters location:
● Name for the SIP (home) server to identify it in Distributed Office Central Manager only
● IP address for the server
● Prefix (a numeric string) to uniquely identify this branch location. The prefixes can be from 1 to 10 digits long, and the default length is 3 digits. In this release of Avaya Distributed Office, branch prefixes must be the same length for all locations in the network.
● Extension Length (the number of digits for the extensions of the users supported by this SIP server). The length of these extensions may vary among the locations in your network, but the total length of Prefix+Extn must be no greater than 15 characters.
View branch locations
Optionally, under the Branches tabon page 34, you can view the following information about each of the existing branch locations you have added to your enterprise, and for which you have enabled private networking, in Distributed Office:
● The name identifying the branch.
● The IP address for the Distributed Office platform at the branch.
● A prefix of a fixed length that is to be used in referencing users at that branch. This field can be edited for each location, but the digit length of the prefixes must be the same as on the General tab of Private Networkingon page 30.
● A number indicating the length, in digits, of users’ numeric extensions at that location.
If you have just enabled private networking, but have not yet added branches using DIstributed Office Local Manager, then this screen will not show any information.
Verify SES routing
After configuring SES for core routing in Distributed Office Central Manager, test whether your configuration is correct and core-routing functions are performed properly with these tasks:
1.Add a new branch location
2.Include the branch in Private Networking 3.Add a station and its extension to the branch 4.Test SIP messaging
Add a new branch location
To add a new branch location (one that is not yet listed when you View branch locationson page 25) to your Avaya Distributed Office network, select Branches screenon page 35 from the left-hand navigation pane and specify information identifying each branch location, as follows:
1. Select the Add button at the top of the Branches screen. A screen with four tabs appears.
2. On the General tabon page 36, enter information in the first four enabled fields.
3. (Optionally) You can use Selecting Network Management Console dataon page 28 to browse your Avaya network of devices for the name of the Distributed Office platform you wish to add as a branch location.
4. You can test connectivity to Distributed Office hardware using the button on the screen.
5. Save this new information or use cancel to discard the information. When you select the save button, a job will be created to synchronize this new information with SES. Once that job has been completed successfully, you can do any of the following:
● Make changes to fields that are newly enabled on the General tabon page 36 for this branch.
● Repeat these steps for another branch location in your Distributed Office network.
● Continue with the steps that follow.
Include the branch in Private Networking
Include the branch or branches you just added in your Enterprise Private Network, as follows:
1. On the General tab of the Branches screen, complete the other fields enabled for data entry, as needed. These fields only become available after the branch has been added.
2. Under the heading Private Networking (PN) on the right-hand side of the screen, ensure
3. Enter the unique numeric branch prefix and number of PN trunks for the Distributed Office platform at this location in the respective fields. Note that the prefix must be the same number of digits in length for all branches in your enterprise private network.
4. Save the information. Continue with the next task, or repeat this step to include another branch in your Distributed Office private network. Cancel to discard your changes.
Add a station and its extension to the branch
Typically, users’ stations are configured at each branch location and then synchronized with SES. Once you add branches in Distributed Office Central Manager, existing branch users’
stations are also synchronized here. You can also manually add users’ stations and their associated extensions to the branch location(s) you have just configured in Distributed Office Central Manager, using the Stations screenon page 39, as follows:
1. On the General tabon page 39 of the Stations screen, enter data in the enabled fields.
2. You can browse for a branch or an extension using the Select... button for that field.
3. You can select user privileges, coverage path template, display language, as well as the station template, type and port number, from their respective drop-down lists of choices.
4. The choices for levels of branch user privileges are Administrative, High-, Medium-, Low, and No-privileged. See Distributed Office Central Manager online help for details.
5. Save the information. Repeat this step, as needed, for other users’ stations at this branch location. Cancel at any time to discard unsaved station additions or changes.
Test SIP messaging
(Optionally) If you have configured users’ stations and their extensions on SIP (Home) Server(s) in the main location, as well as the prefix(es) and stations at one or more branch locations with private networking enabled, then you can test the routing of SIP messages between them, as follows:
1. Make test calls between the main location and a branch location, or between two branch locations in your Distributed Office network.
2. Use supported IM clients to send instant messages between the main location and a branch location, or between two branches in the network.
These tasks will exercise the core routing capabilities of SES Edge; you may also want to test intra-location routing by making calls or sending messages between users at one location.
Selecting Network Management Console data
NMC data can help manage hardware component devices in your Avaya network from a system point of view. For more information, see the online help with Avaya NMC, or refer to Avaya Integrated Management for Distributed Office Network Management Console, 14-300189.
NMC Device Selection (this pop-up window lists only those locations in your network that have not already been configured as branches in Distributed Office Central Manager). Select a name and/or IP Address from the list that you want to add as a Distributed Office branch location, and then select the OK button to populate the fields on the General tab of the Branches screen. You
Private Networking
The Enterprise Private Networking screen is used primarily to configure Avaya SIP Enablement Services for a Distributed Office solution. In addition to Enabling (or disabling) Private
Networking, you can use this screen to submit or cancel entries or changes made on four tabs:
● General tab
● SES tab
● SIP Servers tab
● Branches tab
General tab
Use the General tab under Enterprise Private Networking to specify system-wide settings for your new Distributed Office network, such as the Domain Name and Branch Prefix Length.
SES tab
Use the SES tab under Enterprise Private Networking to configure access, and then test connectivity, to the SES Edge 4.0 server that is performing core-routing functions for your Distributed Office network. You can also force the SES Edge 4.0 Master Administration data to be synchronized with Distributed Office Central Manager on this screen, if this is ever needed.
The following fields appear on this tab:
● IP Address used for the SES Edge 4.0 server — This is either the unique IP address of one simplex server or virtual IP address for a duplex-server pair. Note that this address in not assigned or modified directly via Distributed Office Central Manager.
● Management Access Login — Enter the same login as you entered on SES Edge 4.0.
Information on the System Properties screenon page 12 must match the information you
● Management Access Password — Enter the same password as you entered on SES Edge 4.0. Information on the System Properties screenon page 12 must match the information you enter here.
● Test Connectivity button — verifies that the login and password are correct.
● Force Sync button — updates SES with the latest Distributed Office Central Manager data, in the event that job sync or other errors have caused the two to become out of sync.
Note:
Note: Performing a “force sync” affects inter-location calls and instant messages until
the job is complete. Current calls at the time the force-sync job starts are preserved, but any new calls or new instant messages will fail. Note that intra-branch calls and instant messages are not affected by a force-sync job.
SIP Servers tab
Use the SIP Servers tab under Enterprise Private Networking to add or remove the optional SIP (home) servers for your Distributed Office network. These servers manage and support users and their SIP devices and IM client software at the main or headquarters location.
The following fields appear on this tab:
● Name — This uniquely identifies the SIP home server.
● IP Address — This is the IP address of the SIP Enablement Services home server.
● Prefix (X digits) uniquely identifying a location in a Distributed Office network.
● Extension Length, or the digit length for users’ extensions on this SIP home server.
Branches tab
Use the Branches tab under Enterprise Private Networking to view information on your network branches. You can have as many as 1000 location platforms in a Distributed Office network.
Only branch locations for which Private Networking (PN) is enabled are listed on this screen.
The following fields appear on this tab:
● Branch Name — This is the name administered on the General tab of the Branches screen
● IP Address — This is the IP address for the Distributed Office platform at the branch location, as administered on the General tab of the Branches screen.
● Prefix (X digits) identifying this branch for inter-branch and main-to-branch location routing purposes, which was entered on the General tab after the branch was added.
● Extension Length, or the digit length for users’ extensions at this location; lengths may vary among branches, but total length of the Prefix+Extn must not exceed 15 characters, assuming one character, such as the digit 8, is used to access the AAR/ARS routing.
Software Update Manager
Use Avaya Distributed Office Local Manager to keep the software current on various
components in your Avaya Distributed Office network, and Software Update Manager (SUM) to help with the rest of your Avaya devices that are not Distributed Office platforms. For more
components in your Avaya Distributed Office network, and Software Update Manager (SUM) to help with the rest of your Avaya devices that are not Distributed Office platforms. For more