Avaya 1000 Installation And Commissioning Manual
  1. Manuals
  2. Brands
  3. Avaya Manuals
  4. Server
  5. 1000 Series
  6. Installation and commissioning manual

Avaya 1000 Installation And Commissioning Manual

Branch office
Hide thumbs Also See for 1000:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Configuration Manual, Installation & Commissioning Manual
Avaya Communication Server 1000
Branch Office Installation and
Commissioning
Release 7.6
NN43001-314
Issue 06.02 Standard
June 2014

Advertisement

Table of Contents
loading

Related Manuals for Avaya 1000

Summary of Contents for Avaya 1000

  • Page 1 Avaya Communication Server 1000 Branch Office Installation and Commissioning Release 7.6 NN43001-314 Issue 06.02 Standard June 2014...
  • Page 2 End User. written consent of Avaya can be a criminal, as well as a civil offense under the applicable law. Link disclaimer...
  • Page 3 Product or Hosted Service notices and articles, or to report a problem with your Avaya Product or Hosted Service. For a list of support telephone numbers and contact addresses, go to the Avaya Support website: http://support.avaya.com (or such successor site as designated by Avaya), scroll to the bottom of the page, and select Contact Avaya Support.

  • Page 4: Table Of Contents

    ..................... 13 Getting technical documentation ...................... 13 Getting product training ................. 13 Getting help from a distributor or reseller .............. 14 Getting technical support from the Avaya Web site Chapter 3: Introduction...................... 15 .......................... 15 Subject .................. 15 Note on legacy products and releases ........................ 16 Applicable systems ........................
  • Page 5 Configuring S2 IP Address to point to the main office TPS .................. 59 Patch Management Enhancements Chapter 5: How the Branch Office feature works.............. 60 .......................... 60 Contents ........................... 60 Introduction .................  61 Normal Mode and Local Mode operation June 2014 Branch Office Installation and Commissioning Comments? infodev@avaya.com...
  • Page 6 System security ...................... 80 Unauthorized access .................... 80 UNIStim security with DTLS .......................... 80 IP Security .......................  81 Patch Management Chapter 7: Adding a Branch Office.................. 82 .......................... 82 Contents ........................... 82 Introduction Branch Office Installation and Commissioning June 2014 Comments? infodev@avaya.com...
  • Page 7 .................... 84 Branch Office requirements ....................... 85 Implementation summary Adding an Avaya Communication Server 1000 Branch Office to a Main Office running a ......................  86 previous software release .. 87 Upgrade the entire network to the latest Avaya Communication Server 1000 software release Upgrade only the Main Office to the latest Avaya Communication Server 1000 software ..........................
  • Page 8 Signaling Server software installation ..........  150 Co-resident Call Server and Signaling Server software installation .................... 150 Preinstallation checklist .................. 156 Avaya Linux Base installation ............ 156 Call Server and Signaling Server software installation Chapter 13: Branch Office configuration................ 158 .......................... 158 Contents .................... 158 Configuring the Branch Office .......................
  • Page 9 Print MG 1000B software and system information .......... 205 Co-resident Call Server and Signaling Server restart commands Appendix A: Preprogrammed data.................. 206 .......................... 206 Contents ......................... 206 Introduction ...................... 206 Passwords and codes ...................... 207 Default numbering plan ........................... 207 First digits June 2014 Branch Office Installation and Commissioning Comments? infodev@avaya.com...
  • Page 10 Call Server Real-time usage ............ 220 MG 1000B Core and MG 1000B Expander requirements ..............  221 Bandwidth requirement for Branch Office LAN/WAN .............. 222 CS 1000 Main Office with MG 1000 B and SRG Branch Office Installation and Commissioning June 2014 Comments? infodev@avaya.com...

  • Page 11: Chapter 1: New In This Release

    Communication Server 1000 systems. August 2011 Standard 05.02. This document is up-issued to support Communication Server 1000 Release 7.5. The Overview section is updated to include a note about IPv6 and CP PM. June 2014 Branch Office Installation and Commissioning...
  • Page 12 New in this release November 2010 Standard 05.01. This document is issued to support Communication Server 1000 Release 7.5. June 2010 Standard 04.02. This document is up-issued to reflect changes in the Branch Office task flow graphic and to include CP PM version 2 content.

  • Page 13: Chapter 2: Customer Service

    Chapter 2: Customer service Visit the Avaya Web site to access the complete range of services and support that Avaya provides. Go to www.avaya.com or go to one of the pages listed in the following sections. Navigation • Getting technical documentation on page 13 •...

  • Page 14: Getting Technical Support From The Avaya Web Site

    Customer service Getting technical support from the Avaya Web site The easiest and most effective way to get technical support for Avaya products is from the Avaya Technical Support Web site at www.avaya.com/support. Branch Office Installation and Commissioning June 2014...

  • Page 15: Chapter 3: Introduction

    Note on legacy products and releases This document contains information about systems, components, and features that are compatible with Avaya Communication Server 1000 software. For more information about legacy products and releases, go to Avaya home page: www.avaya.com...

  • Page 16: Applicable Systems

    • Avaya Communication Server 1000E (Avaya CS 1000E) System migration When particular Meridian 1 systems are upgraded to run CS 1000 Release software and configured to include a Signaling Server, they become CS 1000 systems. Table 1: Meridian 1 systems to CS...
  • Page 17 • Media Gateway Extended Peripheral Equipment Controller (MG XPEC) card (NTDW20) • Common Processor Media Gateway (CP MG) card (NTDW56 and NTDW59) The following table shows CS 1000 supported roles for common hardware platforms Table 2: Hardware platform supported roles...

  • Page 18: Related Information

    • Avaya Features and Services Fundamentals, NN43001-106 • Avaya Unified Communications Management Common Services Fundamentals, NN43001-116 • Avaya IP Peer Networking Installation and Commissioning, NN43001-313 • Avaya Linux Platform Base and Applications Installation and Commissioning, NN43001-315 • Avaya Hospitality Features Fundamentals, NN43001-553 Online To access Avaya documentation online, go to the Avaya home page: www.avaya.com...

  • Page 19: Chapter 4: Overview

    59 What is Branch Office? The Branch Office feature extends Avaya Communication Server 1000 (Avaya CS 1000) features from a main office to one or more remote offices. The Branch Office feature is implemented on a Branch Office Media Gateway platform (MG 1000B).
  • Page 20 Signaling Server installation is not. For more information about installing a Signaling Server, see Avaya Signaling Server IP Line Applications Fundamentals, NN43001-125 A Branch Office works with a main office only if the two offices use a common dialing plan. Any other configuration is not guaranteed to work properly.

  • Page 21: Main Office And Branch Office Migration

    Figure 1: Branch Office associated with a CS 1000E main office Main Office and Branch Office migration All Main Office Call Servers in CS 1000 are Large System software-stream-based. The Main Office TN (MOTN) in a Branch Office is always set to the Large System software stream MOTN.

  • Page 22: Co-Resident Call Server And Signaling Server

    Ethernet switch. The Ethernet interface failover feature requires no special network configuration to function. The customer decides if two Layer 2 switches are used to implement the feature to minimize the service outage. For more information see the Avaya Communication Server 1000E Installation and Commissioning, NN43041-310.

  • Page 23: Sip Line Service

    Avaya recommends using hardware firewall to avoid DDoS attack on CPPM and CPMG platforms. The following tables show the existing Communication Server 1000 Call Server packages that are required for the Co-res CS and SS. Table 4: MG1000B Feature Package Requirements...

  • Page 24: S1/S2 Solution Mode

    • The PBXLink between the SMG and the Branch Office SLG is down. S1/S2 solution mode The S1/S2 solution mode includes the following requirements for the SIP clients: 1. The SIP client must support two proxies in their outbound proxy configuration. Branch Office Installation and Commissioning June 2014 Comments? infodev@avaya.com...

  • Page 25: Mo-Grmo Or Pcs-Scs Deployment

    S1 IP address pointing to the Main Office SIP Line Gateway (MO SLG) and the S2 IP address pointing to Geographically Redundant Main Office SIP Line Gateway (GRMO SLG). Figure 2: MO-GRMO or PCS-SCS deployment June 2014 Branch Office Installation and Commissioning Comments? infodev@avaya.com...
  • Page 26 7. The SIP client maintains regular keepalive message with the active proxy in the form of PING requests. 8. The SIP client maintains registration refreshes with the active proxy before registration timer expiry. Branch Office Installation and Commissioning June 2014 Comments? infodev@avaya.com...
  • Page 27 7. The SIP client maintains regular keepalive messages with the active proxy in the form of PING requests. 8. The SIP client maintains registration refreshes with the active proxy before registration timer expiry. June 2014 Branch Office Installation and Commissioning Comments? infodev@avaya.com...

  • Page 28: Mo-Bo Or Pcs-Smg Deployment

    SIP client is configured with the S1 IP address pointing to Geographically Redundant Main Office SIP Line Gateway (GRMO SLG) and the S2 IP address pointing to the Branch Office SIP Line Gateway (BO SLG). Branch Office Installation and Commissioning June 2014 Comments? infodev@avaya.com...
  • Page 29 6. The SIP client configures the MO SLG as its active proxy. After this configuration, incoming requests are received from this active proxy and any outgoing responses are sent to this active proxy. June 2014 Branch Office Installation and Commissioning Comments? infodev@avaya.com...
  • Page 30 5. The SIP client maintains regular keepalive messages with the active proxy in the form of PING requests. 6. The SIP client maintains registration refreshes with the active proxy before registration timer expiry. Branch Office Installation and Commissioning June 2014 Comments? infodev@avaya.com...

  • Page 31: Sip Client Support For S1/S2 Solution Mode

    The SIP client registers to the MO SLG. SIP client support for S1/S2 solution mode Table 5: SIP client support for S1/S2 solution mode on page 32 shows the features supported by the SIP clients. June 2014 Branch Office Installation and Commissioning Comments? infodev@avaya.com...

  • Page 32: Local Mode

    Overview Table 5: SIP client support for S1/S2 solution mode Feature \ Client Avaya 1120E and ipDialog (SIPTone Teledex 4200 (with IP Softphone 3456 1140E IP display) Deskphone Support for S1/S2 solution mode Support for registration redirection Registration timer 1 hour to 31 days...

  • Page 33: Ip Telephony Node Management

    Communication Management (Avaya UCM). The node management interface in Element Manger is used to add servers to a node from the list of servers that Avaya UCM has learned. Before you add the servers to a node, it is required that the CDM feature deploys the necessary software applications to each of the Linux servers.

  • Page 34: Zone Based Dialing

    SDI2 is not available during the Gateway Controller bootup; therefore, you cannot use it to access the installation menus. There are no DIP switches are on the Gateway Controller for configuring the baud rate of SDI0. Branch Office Installation and Commissioning June 2014 Comments? infodev@avaya.com...

  • Page 35: Single Cpu Implications

    Cabinet and chassis CEMux type cards are supported in a MG 1000B. The list of supported cards is as follows. Table 6: CEMux Packs and daughter boards supported in MG 1000B Pack Daughterboard IP expansion CEMux Application June 2014 Branch Office Installation and Commissioning Comments? infodev@avaya.com...

  • Page 36: Clock References

    The TMDI D-Channel ISM configured or removed for TMDI cards increment the existing large system software based DCH ISM. The maximum number of D-Channels, which is 255, supported with MG 1000B in Communication Server 1000 Release 5.5 or later, matches that of the Communication Server 1000M large systems.

  • Page 37: Main Office Hardware Description

    PM Call Server, CP PM Signaling Server, and a card with DSP DB as the Gateway Controller. The following examples show a Chassis and Chassis Expander, but you can also use an MG 1010 Chassis. June 2014 Branch Office Installation and Commissioning Comments? infodev@avaya.com...
  • Page 38 Overview Figure 5: Communication Server 1000 MG 1000B system The following figure shows an example of Communication Server 1000E with CP PM based Co- resident Call Server and Signaling Server. Figure 6: Communication Server 1000E with CP PM Co-resident Call Server and Signaling Server The following figure shows an example of a Branch Office (MG 1000B) with a CP PM based Co- resident Call Server and Signaling Server.
  • Page 39 MG 1000B platform hardware description Figure 7: Communication Server 1000 MG 1000B System with CP PM Co-resident Call Server and Signaling Server Communication Server 1000 Release 7.6 continues to support the legacy Branch Office configuration that uses the SSC processor and Release 5.0 or 5.5 software. Avaya no longer sells the SSC based-Branch Office.

  • Page 40: Mg 1000B Core

    Server can differ from the CS 1000E Server at the main office. Figure 8: MG 1000B Core/MG 1000B Expander on page 40shows an MG 1000B Core/MG 1000B Expander. Figure 8: MG 1000B Core/MG 1000B Expander Branch Office Installation and Commissioning June 2014 Comments? infodev@avaya.com...

  • Page 41: Mg 1000B Chassis

    2) Note 1: On a converted CS 1000 Mini Systems, slot 4 is dedicated to the 48-Port Digital Line Card (DLC). If you do not require the 48-Port DLC, you can cover it with a double-slot card inserted in slot 3.

  • Page 42: Mg 1000B Expander

    Overview • Avaya Integrated Conference Bridge card • cards to support Avaya CallPilot Mini or Avaya CallPilot 201i • Server cards The Voice Gateway Media Cards act exclusively as Voice Gateway Media Cards on the MG 1000B platform. Note: Voice Gateway Media Cards have no LTPS application on board in Communication Server 1000 Release 6.0 and later.

  • Page 43: Network Routing Service (Nrs)

    In an H.323-enabled system, the Signaling Server supports both en bloc and overlap signaling. En bloc signaling is standard. If overlap signaling is to be used, Avaya highly recommends that it be installed and enabled on all Signaling Servers in the network. Failure to do so results in delays in call completion due to overlap to en-bloc conversion.

  • Page 44: Telephones

    For information on configuring the NRS, refer to Network Routing Service Fundamentals, NN43001-130. Telephones The Branch Office supports IP Deskphones as detailed in Avaya IP Deskphone Fundamentals, NN43001-368, and analog and digital telephones as detailed in Avaya Telephones and Consoles Fundamentals, NN43001-567.

  • Page 45: Analog Or Digital Trunk Cards

    Analog or digital trunk cards Note: In Communication Server 1000 Release 6.0 and later, the MC32S and the Voice Gateway Media Card 32 (MC32) cards are supported. For more information, about Voice Gateway Media Card and IP Deskphone configuration, see Avaya Signaling Server IP Line Applications Fundamentals, NN43001-125 or Avaya Circuit Card Reference, NN43001-311.

  • Page 46: Lineside Cards

    The MG 1000B must have a data network connectivity to the ELAN port of the Main Office Call Server. The design of the data networking configuration is outside the scope of this document. The engineering of the data network is documented in the Avaya Converging the Data Network with VoIP Fundamentals, NN43001-260.

  • Page 47: Gateway Controller Network Connections

    Distributed means that the two Ethernet ports (TLAN or ELAN) of the dual-homing feature connect to separate Layer 2 switches, to provide another level of redundancy and no single point of failure June 2014 Branch Office Installation and Commissioning Comments? infodev@avaya.com...
  • Page 48 Overview with a Layer 2 switch. Avaya recommends distributed connections; support is available for nondistributed connections if the cost of the additional data networking equipment is an issue. The CE and CT ports on the are the only embedded Ethernet ports that allow a direct connection to another device, and the only hardware supported for this direct connection are CP PM or CP DC card Ethernet ports.
  • Page 49 The following figure illustrates a typical network configuration that supports dual homing of both the ELAN and TLAN. Multiple Layer 2 switches ensure there isn’t a single point of failure. Avaya recommends this configuration for the highest reliability in a single CPU Call Server configuration.

  • Page 50: Mg 1000B Platform Configuration Overview

    41. Each MG 1000B Core with a digital trunk card must have a clock controller. For more information on line side T1 and line side E1 cards, see Avaya Circuit Card Reference, NN43001-311. MG 1000B platform without a chassis expander...
  • Page 51 • Avaya Integrated Recorded Announcer card • cards to support Avaya CallPilot Mini or Avaya CallPilot 201i For more information on the Voice Gateway Media Card configuration, refer to Avaya Signaling Server IP Line Applications Fundamentals, NN43001-125. For more information on Integrated Conference Bridge, refer to Avaya Integrated Conference Bridge Service Implementation Guide, NN43001-558.

  • Page 52: Mg 1000B Platform With A Chassis Expander

    The MG 1000B Expander does not support digital trunks. An MG 1000B Expander is not required or supported with a MG 1010 chassis. Figure 15: MG 1000B platform with a chassis expander Branch Office Installation and Commissioning June 2014 Comments? infodev@avaya.com...

  • Page 53: Capacity

    • There can be a maximum of 255 SRGs • There can be a maximum of 1000 MG 1000Bs • There can be a maximum of 1000 SIP Media Gateways, of which 511 can be survivable with N-Way database replication •...

  • Page 54: Software Requirements

    Indefinite operation with a mixed-software configuration of Communication Server 1000 Release 4.5 or later Branch Offices, and a Communication Server 1000 Release 7.6 Main Office is supported. Consider this mixed software policy when planning your system upgrade. Branch Offices must be at Communication Server 1000 Release 4.5 or later before upgrading the Main Office to...

  • Page 55: Features In Mixed-Software Configurations

    Communication Server 1000 Release 7.6. IP Phone firmware When you add a new Communication Server 1000 Branch Office release to a network that has a previous release of CS 1000 Branch Office, you must choose whether to upgrade IP Phone firmware for existing Branch Offices.

  • Page 56: Supported Applications

    Branch Office with Communication Server 1000 Release 5.5 or later. For Communication Server 1000 Release 6.0 or later the Co-resident Call Server and Signaling Server is optional, however the Signaling Server is required for an IP-enabled Communication Server 1000 system. For more...
  • Page 57 MG 1000B Signaling Server. Avaya recommends that the NRS in the MG 1000B be configured as a Failsafe NRS. If the MG 1000B IP Phones go into Local Mode, they can use the MG 1000B NRS services.

  • Page 58: Active Call Failover

    Phone to do so. IP Phones clear all call information when registering to a Call Server or LTPS that does not support the feature. For further information on Active Call Failure, refer to Avaya Signaling Server IP Line Applications Fundamentals, NN43001-125.

  • Page 59: Patch Management Enhancements

    S2. For information on configuring the S2 IP address to point to the Main Office TPS and its limitations, see Avaya Signaling Server IP Line Applications Fundamentals, NN43001-125. Patch Management Enhancements The changes completed under this feature are applicable to Call Server, Gateway Controller, and Voice Gateway Media Cards.

  • Page 60: Chapter 5: How The Branch Office Feature Works

    PSTN. Access to PSTN digital or analog trunks at the Branch Office occurs through the MCDN Virtual Trunk. For more information on Virtual Trunks, refer to Avaya IP Peer Networking Installation and Commissioning , NN43001-313. For more information about Electronic Switched Networking (ESN), refer to Avaya Electronic Switched Network: Signaling and Transmission Guidelines, NN43001-280.

  • Page 61: Normal Mode And Local Mode Operation

    NCS for the Alternate Signaling Server's IP address. The MG 1000B will redirect the IP Phone to the Alternate Signaling Server and continue to receive call processing services from the main office Call June 2014 Branch Office Installation and Commissioning Comments? infodev@avaya.com...
  • Page 62 Local Mode, and then reregister with the main office once the call is complete. MG 1000 IP Phones in Normal Mode remain registered with the main office if the Primary NRS fails and no Alternate NRS is available. They can call any main office telephone or IP Phones in Normal Mode in other branch offices.
  • Page 63 The licensing feature applies only if more than four IP Phones are in Local Mode at the same time. If four or fewer phones are in Local Mode simultaneously, the licensing feature is not activated. June 2014 Branch Office Installation and Commissioning Comments? infodev@avaya.com...

  • Page 64: Virtual Trunks

    (NN43001-613). Virtual Trunks In order for endpoints in the Avaya Communication Server 1000 network to access endpoints in local mode at the Branch Office or to access the PSTN at the Branch Office, Virtual Trunks are used over the LAN/WAN.

  • Page 65: Ip Phone To Analog (500/2500-Type) Or Digital Telephone Calls

    Call Server so a direct media path between the IP Phone and the DSP resource can be set up when the call is established. Refer to Avaya IP Phone to analog (500/2500-type) or digital telephone calls, NN43001-313 for details.

  • Page 66: Group Call

    MG 1000B IP Phones register with the MG 1000B Call Server before being redirected to the main office. If the sets cannot register with the MG 1000B Call Server as described in the previous Branch Office Installation and Commissioning June 2014 Comments? infodev@avaya.com...

  • Page 67: Points To Remember

    IP Phone back to the MG 1000B TPS once the IP Phone becomes available again. This action enables the MG 1000B IP Phone to go back to Normal Mode by using S1 to register to the main office. June 2014 Branch Office Installation and Commissioning Comments? infodev@avaya.com...

  • Page 68: Configuring The S2 Ip Address Parameter

    To configure the S2 parameter, do the following: 1. Reboot the MG 1000B IP Phone. 2. When the "Avaya" banner displays, quickly press the four keys under the display in sequence, from left to right. 3. Program the IP address, subnet mask, and gateway addresses for the MG 1000B IP Phone.

  • Page 69: Multiple Appearance Dn (Madn)

    Emergency services Support for access to emergency services by Branch Users in Normal Mode is configured at the main office. For more information on Emergency services, see Avaya Emergency Services Access Fundamentals, NN43001-613 The key difference between the main office user and the Branch User is the route selected for the emergency call.

  • Page 70: Configuring Esa For Emergency Services

    Configuring ESA for emergency services Beginning with Communication Server 1000 Release 5.0 and later ESA, it is possible to configure up to 16 distinct ESDNs to better suit the needs of a multinational enterprise. With support for Multiple ESDN you are no longer restricted to a single ESDN for use in placing emergency calls.

  • Page 71: Configuring Spn For Emergency Services

    Alternatively, Virtual Trunks can utilize the MCS 5100 H.323 Gatekeeper. In this case, at least one dedicated Signaling Server is required to run as the primary Communication Server 1000 NCS, where the H.323 endpoints are configured as non-RAS endpoints because Virtual Trunks will establish a connection with MCS, not NCS.
  • Page 72 1000/2100 or to the remote CS 1000/2100 itself goes down, the IP Phones survive by registering with the local CS 1000, which provides telephony services while the link to the CS 1000/2100 or the CS 1000/2100 itself is down. When the link to the remote CS 1000/2100 or to the remote CS 1000/2100 itself is restored, the IP Phones are automatically redirected back to the remote CS 1000/2100 to receive telephony services.

  • Page 73: Chapter 6: Planning And Management

    Branch Office on page 76. Avaya recommends that the Branch User ID (BUID) be the same at the Branch Office as the DN at the main office. A BUID has a maximum of 15 digits. Under the recommended Coordinated Dialing Plan (CDP), it can be an extension (for example, 4567).

  • Page 74: Emergency Services

    Planning and management For more information about CDP, refer to Avaya Dialing Plans Reference, NN43001-283. For details on other Numbering Plan options, refer to Avaya Communication Server 1000S: Overview, NN43031-110. For more information on ESN, refer to ESN Access Codes on page 75.

  • Page 75: Zones

    ESN data is configured with two Access Codes called AC1 and AC2. AC1 normally applies to long- distance calls, whether placed on or off the customer's private network (for example, dialing "6"). AC2 normally applies to local calls (for example, dialing "9"). For more information, refer to Avaya Electronic Switched Network: Signaling and Transmission Guidelines, NN43001-280.

  • Page 76: Configuration Example For Pstn Resources At The Branch Office

    • Long-distance numbers at the main office are configured to go over the Virtual Trunk and use PSTN trunks at the main office, such as 1-613-967-1111 or 1-613-555-1212. • All other long-distance numbers have other routing as appropriate (1-NPA-NXX-XXXX), but most are routed through the main office. Branch Office Installation and Commissioning June 2014 Comments? infodev@avaya.com...

  • Page 77: Zone Configuration Description

    The dialed digits can now be converted to a long-distance format. It is up to NARS to partially route the number over the private network to take advantage of any long-distance benefits. June 2014 Branch Office Installation and Commissioning Comments? infodev@avaya.com...

  • Page 78: Management

    Planning and management Management The following sections pertain to MG 1000B management. Refer to Avaya System Management Reference, NN43001-600. Remote Access Remote Access to the MG 1000B Server is available through Ethernet connection or remote login through a dial-up modem.

  • Page 79: Call Detail Recording (Cdr)

    "1-613-555-1212". In other words, the main office Call Server produces a CDR record indicating that the user dialed a "long-distance" digit string because the feature converts the call from a local dialing pattern to a long-distance dialing pattern. June 2014 Branch Office Installation and Commissioning Comments? infodev@avaya.com...

  • Page 80: System Security

    The LTPS uses the UNIStim security with DTLS feature to detect if a phone uses Secure UNIStim. After the you install the Communication Server 1000 software on the system (either during a fresh install or upgrade), DTLS signaling security is disabled by default (DTLS policy is set to OFF). You must configure at least Basic Security Level to enable DTLS.

  • Page 81: Patch Management

    ISSS network elements, or targets, are classified into two categories: • Avaya UCM targets: these elements automatically belong to the Avaya UCM security domain; you need not add them using the Avaya UCM ISSS management interface. An example of an Avaya UCM target is a Call Server.

  • Page 82: Chapter 7: Adding A Branch Office

    82 Main office requirements on page 83 Implementation summary on page 85 Adding an Avaya Communication Server 1000 Branch Office to a Main Office running a previous software release on page 86 Introduction To install a Branch Office: 1.

  • Page 83: Main Office Requirements

    (500/2500-type) telephones in the Branch Office to share the voicemail system in the main office. For any configurations using centralized Avaya Call Pilot on the main office with one or more branch offices in separate time zones, the NMS package is required at the main office for the branch IP Phones.

  • Page 84: Branch Office Requirements

    The feature packages listed above are automatically enabled in the Branch Office software. If the Main Office is equipped with Location Code Expansion (LOCX) package 400, the Branch Office must also have this package. Refer to Avaya ISDN Primary Rate Interface Fundamentals , NN43001-569.

  • Page 85: Implementation Summary

    Implementation summary Implementation summary To prepare for a Branch Office, refer to the Avaya Communication Server 1000E: Planning and Engineering (NN43041-220) document. This contains important electrical information and safety guidelines. Follow these steps to implement the Communication Server 1000 Branch Office: 1.

  • Page 86: Adding An Avaya Communication Server 1000 Branch Office To A Main Office Running A Previous Software Release

    Avaya Communication Server 1000 Main Office running a previous software release. Therefore, you must upgrade the Main Office to the latest CS 1000 software release before you upgrade the Branch Office to the latest CS 1000 software release.

  • Page 87: Upgrade The Entire Network To The Latest Avaya Communication Server 1000 Software Release

    Important: A mixed software configuration between the CS 1000 Main Office running the latest software release and Branch Offices running CS 1000 Release 4.5 or later is permitted. In this case, indefinite operation with a mixed software configuration is supported.

  • Page 88: Upgrade Main Office With Ip Phone Firmware Upgrade

    Adding a Branch Office 2. Do not upgrade the IP Phone firmware in the existing prior release CS 1000 Branch Offices (see Upgrade Main Office without IP Phone firmware upgrade on page 88). Upgrade Main Office with IP Phone firmware upgrade To upgrade the Main Office to the latest Communication Server 1000 software release, and upgrade the IP Phone firmware in Communication Server 1000 Release 4.5 or later Branch Offices to the...
  • Page 89 2. At each existing Communication Server 1000 Branch Office: a. If necessary, execute the isetResetAll command on the MG 1000B Signaling Server(s). 3. Install the new Communication Server 1000 Branch Office running the latest software release, as described in Implementation summary on page 85.

  • Page 90: Chapter 8: Converting A Small System To A Branch Office

    Branch Office network. Important: This section describes how to upgrade an Avaya Communication Server 1000 Small System into a Survivable MG 1000E. Where no main office exists, one office can be configured as the main office, and the others converted to Branch Offices.

  • Page 91: Conversion

    To function as a Branch Office, the Small System must be equipped with the following components: • a Gateway Controller that meets the requirements for the latest Communication Server 1000 software release. • DSP resources provided by the Gateway Controller or Voice Gateway Media Cards.

  • Page 92: Implementation Summary

    Co-resident Call Server and Signaling Server, add a supported Server. For CP PM cards, ensure the CP PM has at least 2 GB of RAM and a 40 GB drive. e. Install a Voice Gateway Media Card if required. Refer to Avaya Signaling Server IP Line Applications Fundamentals, NN43001-125.
  • Page 93 The Media Gateway 1000B uses the standard license increment codes. Branch office unique codes are listed in the following table, see Figure 18: Media Gateway 1000B Parameters on page 94. June 2014 Branch Office Installation and Commissioning Comments? infodev@avaya.com...
  • Page 94 Converting a Small System to a Branch Office Figure 18: Media Gateway 1000B Parameters Branch Office Installation and Commissioning June 2014 Comments? infodev@avaya.com...
  • Page 95 Refer to Avaya Signaling Server IP Line Applications Fundamentals, NN43001-125. l. Install and provision the local trunks (the XUT, PRI, and DTI cards). Refer to Avaya Communication Server 1000M and Meridian 1 Small System Installation and Commissioning , NN43011-310.

  • Page 96: Chapter 9: Upgrading To Communication Server 1000 Release 7.6

    Branch Office Communication Server 1000 Release 6.0 and later software is required to enable and configure SIP Line Service. Configure the SIP client telephony users as Universal Extensions of subtype SIP Line.
  • Page 97 VxWorks-based Branch Office systems do not require a CP PM card BIOS upgrade. Upgrading the Main Office to Communication Server 1000 Release 7.6 1. Upgrade the main office software to Communication Server 1000 Release 7.6 through the Deployment Manager; see Avaya Linux Platform Base and Applications Installation and Commissioning, NN43001-315.

  • Page 98: Chapter 10: Main Office Configuration

    System Installation and Commissioning, NN43021-310 , appropriate for the system. IP Telephony Nodes The Element Manager application, within the Avaya UCM, provides an interface to configure IP Telephony Nodes in an Avaya Communication Server 1000 system. Branch Office Installation and Commissioning June 2014 Comments? infodev@avaya.com...
  • Page 99 4. In the New IP Telephony Node page (see Figure 20: New IP Telephony Node page page 100) enter the Node general properties; for example, Node ID, Node IP address, ELAN, and TLAN. June 2014 Branch Office Installation and Commissioning Comments? infodev@avaya.com...

  • Page 100: Importing An Ip Telephony Node File

    Main office configuration Figure 20: New IP Telephony Node page For more information about the IP Telephony Management, see Avaya Element Manager System Reference – Administration, NN43001-632. For more information about adding a new IP Telephony node, see Avaya Signaling Server IP Line Applications Fundamentals, NN43001-125.

  • Page 101: Exporting An Ip Telephony Node File

    Exporting an IP Telephony Node file Figure 21: IP Telephony Import page For more information about the IP Telephony Management, see Avaya Element Manager System Reference – Administration, NN43001-632. For more information about importing an IP Telephony Node file, see Avaya Signaling Server IP Line Applications Fundamentals, NN43001-125.

  • Page 102: Adding Linux Servers To A Node

    2. To confirm the deletion of the Node, click OK in the Delete Confirmation window. Adding Linux servers to a Node The Avaya UCM framework discovers every Linux server that is installed on the network. The Avaya UCM stores this list and the Node Management interface queries this list every time when a new server needs to be added in to the Node.

  • Page 103: Sip Client Configuration

    Main Office, Geographically Redundant Main Office, and Branch Office. Main Office The following example shows the SIP Line Services section from the config.ini file for the Main Office. [SIP Line Services] SLP_IP=0.0.0.0 SLP_Port=5060 June 2014 Branch Office Installation and Commissioning Comments? infodev@avaya.com...
  • Page 104 SLG_Role = 1 --> 0-MO, 1-GR, 2-BO SLG_Mode = 0 --> 0-Proxy mode MO_SLG_IP =47.11.25.183 --> MO SLG IP MO_SLG_Port =5070 MO_SLG_Transport =udp --> MO SLG Transport GR_SLG_IP = GR_SLG_Port =5070 GR_SLG_Transport =udp securityPolicy=0 clientAuthenticationEnabled=0 Branch Office Installation and Commissioning June 2014 Comments? infodev@avaya.com...

  • Page 105: Tftp Server Configuration (Avaya 1120E And 1140E Ip Deskphone)

    TFTP server configuration (Avaya 1120E and 1140E IP Deskphone) numByteRenegotiation= x509CertAuthenticationEnabled=0 Branch Office The following example shows the SIP Line Services section of the config.ini file for the Branch Office. [SIP Line Services] SLP_IP=0.0.0.0 SLP_Port=5060 SLP_Transport=UDP SLG_LocalSipPort = 5070 SLG_LocalTlsPort = 5071 SLG_Role = 2 -->...
  • Page 106 SIP_PING YES --> set to YES for keep alive AUTOLOGIN_ENABLE YES # Time configuration DST_ENABLED YES TIMEZONE_OFFSET -18000 VMAIL 2300 VMAIL_DELAY 300 AUTO_UPDATE YES AUTO_UPDATE_TIME 0 DEF_LANG English MAX_INBOX_ENTRIES 50 MAX_OUTBOX_ENTRIES 50 MAX_REJECTREASONS 5 MAX_PRESENCENOTE 5 Branch Office Installation and Commissioning June 2014 Comments? infodev@avaya.com...
  • Page 107 TFTP server configuration (Avaya 1120E and 1140E IP Deskphone) MAX_CALLSUBJECT 5 RECOVERY_LEVEL 0 DEF_AUDIO_QUALITY High DSCP_CONTROL 0 ENABLE_BT YES #Address book mode - NETWORK, LOCAL, BOTH ADDR_BOOK_MODE NETWORK ADMIN_PASSWORD 4321 MAX_IM_ENTRIES 50 ENABLE_3WAY_CALL YES TRANSFER_TYPE MCS ENABLE_PRACK NO REDIRECT_TYPE MCS --> set to MCS for Register redirection support...

  • Page 108: Zone Based Dialing

    ZBD option The following procedure demonstrates a basic overview of the steps to follow to configure the ZBD. For more information on the ZBD, see Avaya Dialing Plans Reference, NN43001-283. 1. Enable the Zone Based Dialing option in OVL15, 2. Set the dial plan option to the appropriate dial plan PUB or PRV.

  • Page 109: Unistim Ltps

    Gateway service. There are three options to configure on the Gateway configuration page; General, SIP Gateway Settings, and SIP Gateway Services. For more information on configuring the Gateway, see Avaya Element Manager System Reference - Administration, NN43001-632.
  • Page 110 Sets the node-level TN entry temporary password. For detailed command-line or Element Manager procedures, refer to Avaya Signaling Server IP Line Applications Fundamentals, NN43001-125. To use the Virtual Office feature, a Station Control Password (SCPW) must be configured at both the Branch Office and the Main Office.

  • Page 111: Mg 1000B Ip Phone Configuration

    Configuring MG 1000B IP Phones at the main office using LD 11 1. Configure the Branch Office zones and dialing plan. 2. Configure the following telephone data in LD 11: • Terminal type • Customer Number • TN • Zone June 2014 Branch Office Installation and Commissioning Comments? infodev@avaya.com...
  • Page 112 2033, 2210, 2211, 2212, 6120, 6140 SCPW xxxx Station Control Password. Must equal Station Control Password Length (SCPL) as defined in LD 15. Not prompted if SCPL = 0. Precede with X to delete. Branch Office Installation and Commissioning June 2014 Comments? infodev@avaya.com...

  • Page 113: Chapter 11: Mg 1000B Platform Hardware Installation

    • Extended Universal Trunk (analog) • 2.0 Mb Digital Trunk Interface (DTI) • 2.0 Mb Primary Rate Interface (PRI) Each MG 1000B Core with a digital trunk card must have a clock controller. See Avaya Circuit Card Reference, NN43001-311. June 2014 Branch Office Installation and Commissioning Comments? infodev@avaya.com...

  • Page 114: Readiness Checklist

    Completed the card slot assignment plan? This information is provided by your Planning and Engineering group. Obtained all the tools required to continue with the installation? Prepared the network data as suggested in Avaya Converging the Data Network with VoIP Fundamentals, NN43001-260 and Avaya Communication Server 1000E Installation and Commissioning, NN43041-310?

  • Page 115: Rack-Mounting An Mg 1000B

    To install each MG 1000B or MG 1000B Chassis Expander in a 19-inch rack, use the following items: • Equipment layout plan (for more information see, Avaya Communication Server 1000E Installation and Commissioning, NN43041-310. • One pair of left and right guide brackets •...
  • Page 116 MG 1000B. To determine the front of the bracket, locate the "R". This "R" must be at the top of the bracket and must face to the front of the MG 1000B. Branch Office Installation and Commissioning June 2014 Comments? infodev@avaya.com...
  • Page 117 (near the front). a. Use two #8-32 machine screws. Position the ear bracket so the four holes on the bracket flange are closer to the rear of the Media Gateway 1000. Note: To determine the front of the bracket, locate the “L” on the bracket. The “L” must be at the top of the bracket and face the front of the MG 1000B.
  • Page 118 MG 1000B platform hardware installation Figure 26: MG 1000B installed in a rack 7. Install the equipment ground wires for the MG 1000B and Signaling Server. See Avaya Communication Server 1000E: Installation and Configuration , NN43041-310. 8. Install a UPS (if required) according to the manufacturer's instructions.

  • Page 119: Installing Cards

    Upgrading the MG 1000B hardware Figure 27: Power switch on the front of the MG 1000B chassis 14. Install any remaining equipment, such as alarms. See Avaya Communication Server 1000E Installation and Configuration, NN43041-310. 15. Reinstall the front covers on the MG 1000B.

  • Page 120: Perform A Customer Backup Data Dump (Installation Release)

    • Power down the Media Gateway. • Remove the SSC card. • Destroy or return the SSC security device to your local Avaya Repairs/ Returns center. • If using a card as the Gateway Controller, Install the DSP Daughterboard on the card as...

  • Page 121: Installing The Cards

    It is illegal to continue to run the system software on the existing SSC card. Please DESTROY or RETURN the SSC dongle to your local Avaya Repairs/Returns center. No further orders will be accepted for the serial number since it will be decommissioned and tracked in Avaya’s database.

  • Page 122: Gateway Controller Installation

    1000E cabinet or chassis. Connect it to the SDI port on the cabinet and the COM RS232 port on the chassis. Figure 30: NTBK48 connectors on page 123 illustrates the two connectors. Branch Office Installation and Commissioning June 2014 Comments? infodev@avaya.com...
  • Page 123 Yes (requires null modem to connect to a TTY) SD11 No (No hardware flow control) SD12 No (No hardware flow control) No (Only available after FPGA is enabled. Not available during initial configuration menu display) June 2014 Branch Office Installation and Commissioning Comments? infodev@avaya.com...

  • Page 124: Server Card Installation

    Please DESTROY or RETURN the SSC dongle to your local Avaya Repairs/Returns center upon confirmation of a successful upgrade. If the SSC system was using remote dongles for any expansion cabinets, please DESTROY or RETURN to your local Avaya Repairs/Returns center upon confirmation of a successful upgrade.
  • Page 125 NTAK19EC cable (a female to female gender changer may be required). You must povide this adapter. • Connect the other end of the 25 pin to 9 pin straight through serial cable to the serial port on the maintenance terminal. June 2014 Branch Office Installation and Commissioning Comments? infodev@avaya.com...
  • Page 126 • Connect a NTC325AAE6 serial port adapter (9 pin or 25 pin) to the other end of the Ethernet cable. • Connect the Ethernet cable with serial port adapter to the serial port of a maintenance terminal. Branch Office Installation and Commissioning June 2014 Comments? infodev@avaya.com...

  • Page 127: Upgrading The Cp Pm Software

    3. Press the manual RESET button on the CP PM card faceplate. 4. The CP PM card reboots. Press F when prompted to boot from the faceplate Compact Flash card containing the installation software. June 2014 Branch Office Installation and Commissioning Comments? infodev@avaya.com...

  • Page 128: Installing A Signaling Server

    Press <CR> when ready ... Installing a Signaling Server Hardware installation Installation checklist Before you start to install a Signaling Server in a Communication Server 1000 system, complete the following checklist. Table 23: Installation checklist Have you: Received all server equipment and peripherals? •...
  • Page 129 - N0118766 - CP PM Signaling Server Hard Drive Installation instructions (CP PM only) - NTAK19ECE6 - 2 port SDI Cable assembly kit (for cabinet or MG 1000 chassis) - NTDU0606E6 - 25cm RJ45 Ethernet Cable kit (for MG 1000 chassis)

  • Page 130: Installing A Server Card Signaling Server

    Installation in a MG 1000B system The NTDW61 and NTDW99 models of the CP PM card are designed for use in a Avaya CS 1000E system. The first task that must be performed is to install the CP PM hard drive shipped with the server.
  • Page 131 Installing ELAN and TLAN Ethernet ports on the back of a CS 1000M UEM 1. Obtain the special cabling kit (NTDW69AAE5) shipped with the CS 1000M model of the Avaya CP PM Signaling Server (NTDW66AAE5). The NTDW69AAE5 cabling kit should include the items shown in the following figure.
  • Page 132 3. Insert the other Ethernet port coupler into the adapter plate. See the following figure. Figure 34: Two Ethernet port couplers in adapter plate 4. Loosely attach screws, washers, and nuts to the Ethernet port adapter plate. See the following figure. Branch Office Installation and Commissioning June 2014 Comments? infodev@avaya.com...
  • Page 133 5. Switch off the UEM power supplies. See the following figure. Figure 36: Shut down UEM power supplies 6. Select one of the J2-J5 knock-out plates on the back of the UEM. See the following figure. June 2014 Branch Office Installation and Commissioning Comments? infodev@avaya.com...
  • Page 134 8. Establish an ELAN port on the back panel of the UEM. a. Insert the end of one of the RJ-45 CAT5 Ethernet patch cables (supplied) into the ELAN network interface (ELAN port) on the faceplate of the server. Branch Office Installation and Commissioning June 2014 Comments? infodev@avaya.com...
  • Page 135 9. Connect the server to the TLAN subnet. a. Insert one end of the remaining RJ-45 CAT5 Ethernet patch cable (supplied) into the TLAN network interface (TLAN port) on the faceplate of the server. June 2014 Branch Office Installation and Commissioning Comments? infodev@avaya.com...
  • Page 136 Figure 41: TLAN connection on faceplate Figure 42: TLAN connection on Ethernet port coupler 10. Fit the Ethernet port adapter plate into the hole on the back of the UEM and tighten the screws. Branch Office Installation and Commissioning June 2014 Comments? infodev@avaya.com...
  • Page 137 The hard drive kit contains a hard drive with a jumper, 4 screws, and installation instructions (document N0120776). You need only a small Phillips screw driver to install the hard drive. June 2014 Branch Office Installation and Commissioning Comments? infodev@avaya.com...
  • Page 138 2. Place hard drive on printed circuit board and slide to mate with connector J32. Figure 46: CP PM hard drive and connector J32 3. Secure hard drive from the bottom side with the included screws. Branch Office Installation and Commissioning June 2014 Comments? infodev@avaya.com...
  • Page 139 Signaling Server. You must configure the on-board FMD switch (S5) to position 2 to designate the HD as the FMD for the Signaling Server. 5. Remove on-board compact flash retainer clip if populated. Figure 49: CP PM Signaling Server internal CF card retainer clip June 2014 Branch Office Installation and Commissioning Comments? infodev@avaya.com...

  • Page 140: Chapter 12: Mg 1000B Software Installation

    142 Signaling Server software installation on page 149 Co-resident Call Server and Signaling Server software installation on page 150 Call Server and Signaling Server software installation on page 156 Branch Office Installation and Commissioning June 2014 Comments? infodev@avaya.com...

  • Page 141: Installing Mg 1000B Software

    This section provides a high-level task flow for the installation of Avaya Communication Server 1000. The task flow indicates the recommended sequence of events to follow when configuring a system and provides the document number that contains the detailed procedures required for the task.

  • Page 142: Connecting The Mg 1000B Core To The Network

    For details on upgrading software on a Gateway Controller card, refer to Avaya Communication Server 1000E - Software Upgrades, NN43041-458. Upgrading Server card software For details on upgrading software on a Server card, refer to Avaya Communication Server 1000E - Software Upgrades, NN43041-458. Connecting the MG 1000B Core to the network Connecting the MG 1000B Core to the network The MG 1000B Core has two 100BaseT ports (1 and 2) for Ethernet connection to the network.
  • Page 143 In the case of Co-resident Call Server and Signaling Server, connect the two short Ethernet cables between the Server card and the two 100BaseT ports at the top right corner of the MG 1000B Core. June 2014 Branch Office Installation and Commissioning Comments? infodev@avaya.com...
  • Page 144 6. Verify default routing by entering the command: PRT ROUTE Note: For a single CPU machine, the secondary IP is not used. Note: The secondary IP is accessible only when a system is in split mode. Branch Office Installation and Commissioning June 2014 Comments? infodev@avaya.com...
  • Page 145 7. Save the ELAN network interface configuration. Enter the following command: UPDATE DBS 8. For the changes to take affect, enter the following commands in LD 137 to disable and enable the ELNK: DIS ELNK ENL ELNK June 2014 Branch Office Installation and Commissioning Comments? infodev@avaya.com...

  • Page 146: Using Element Manager To Configure The Node

    TLAN network interfaces to the switch. See MG 1000B platform hardware installation page 113. For more detailed information on the switch and router connections, see Avaya Converging the Data Network with VoIP Fundamentals, NN43001-260. Using Element Manager to configure the node...
  • Page 147 - select Secondary Proxy Supports Registration - Secondary CDS Proxy or Redirect server flag To configure a Follower Signaling Server, refer to Avaya Signaling Server Installation and Commissioning. To configure an Alternate and Failsafe (if required) NRS, refer to the corresponding procedures in Avaya IP Peer Networking Installation and Commissioning, NN43001-313.
  • Page 148 MG 1000B software installation Figure 54: Confirm IP telephony node values for Primary and Secondary NCS Figure 55: Confirm IP telephony node values SIP Redirect Server Branch Office Installation and Commissioning June 2014 Comments? infodev@avaya.com...

  • Page 149: Signaling Server Software Installation

    During the install of Linux base, the Signaling Server software is deployed and can be accessed through the Avaya Unified Communications Management (Avaya UCM) console. For more information about the Linux platform base install, see Avaya Linux Platform Base and Applications Installation and Commissioning, NN43001-315 .

  • Page 150: Co-Resident Call Server And Signaling Server Software Installation

    2 (NTDW99CAE6) meets the requirements for Co-res CS and SS. CP PM version 2 includes an updated hardware design, BIOS, and boot manager. For more information about the methods for ensuring the CP PM hardware meets the above requirements, see Avaya Co-resident Call Server and Signaling Server Fundamentals, NN43001-509.
  • Page 151 4. During the reboot memory check, quickly press CTRL C to enter the CP PM BIOS. Figure 57: CP PM BIOS setup on page 152 appears. Select Reset CMOS to factory defaults from the menu. June 2014 Branch Office Installation and Commissioning Comments? infodev@avaya.com...
  • Page 152 7. Once the reboot and memory check completes, Figure 59: CP PM faceplate drive boot page 153appears. Press the F key to boot from the Linux Base installation faceplate CF card. Branch Office Installation and Commissioning June 2014 Comments? infodev@avaya.com...
  • Page 153 154 appears if the CP PM version 1 card has a BIOS version less than 18. Press Y to proceed with the automatic upgrade. Caution: Do not interrupt the BIOS upgrade process. Damage to equipment may occur. June 2014 Branch Office Installation and Commissioning Comments? infodev@avaya.com...
  • Page 154 11. During the reboot memory check, quickly press CTRL C to enter the CP PM BIOS. Figure 61: CP PM BIOS setup on page 155 appears. Select Reset CMOS to factory defaults from the menu. Branch Office Installation and Commissioning June 2014 Comments? infodev@avaya.com...
  • Page 155 14. The system reboots. Once the reboot is complete, the new BIOS version is displayed. Verify that the BIOS version is 18 or higher. You can now proceed with the Linux Base software installation. June 2014 Branch Office Installation and Commissioning Comments? infodev@avaya.com...

  • Page 156: Avaya Linux Base Installation

    The Deployment Manager runs on the Avaya UCM Primary Security Server. You must start the Avaya UCM navigator and log on to the Avaya UCM Primary Security Server. In this model, the Centralized Deployment Manager deploys application software to the target servers in the Avaya UCM security domain.
  • Page 157 Important: For the Centralized Deployment Manager, you only need to upload the application software once. You can then deploy the software image to multiple target servers in the Avaya UCM security domain. The Deployment Manager supports new installation and upgrades. Both processes are similar but contain the following differences: •...

  • Page 158: Chapter 13: Branch Office Configuration

    Installing and configuring IP Phones on page 161). 6. Configure ZFDP (optional) 7. Configure Dial Plan (private if DIALPLAN option is set to PRV in CDB, or public if DIALPLAN option is set to PUB). Branch Office Installation and Commissioning June 2014 Comments? infodev@avaya.com...

  • Page 159: Configuring The Zone Based Dialing

    The workfile is delivered by the PC card or Element Manager and contains all Voice Gateway Media Card operating system and application files. The workfile is a single packed and compressed file. For more information on configuring the Voice Gateway Media Card, see Avaya Signaling Server IP Line Applications Fundamentals, NN43001-125 June 2014 Branch Office Installation and Commissioning Comments? infodev@avaya.com...

  • Page 160: Configuring The Trunks And Lines

    Branch Office configuration Configuring the trunks and lines To install the line and trunk cards, if the Branch Office is a converted Small System, refer to Avaya Communication Server 1000E Installation and Commissioning, NN43041-310. To configure lines, refer to Avaya Communication Server 1000E Installation and Commissioning, NN43041-310.

  • Page 161: Chapter 14: Mg 1000B Telephones

    111). They are also configured on the MG 1000B CP PM for survivability purposes. Automatic data synchronization is not carried out between the main office Call Server and MG 1000B CP PM. June 2014 Branch Office Installation and Commissioning Comments? infodev@avaya.com...

  • Page 162: Password Requirements

    Small System, refer to Avaya Communication Server 1000E Installation and Configuration, NN43041-310 document. To install an IP Phone at the Branch Office, Avaya strongly recommends that an IP Phone Installer's Password or a Temporary IP Phone Installer's Password be configured on the MG 1000B Signaling Server.

  • Page 163: Installing An Ip Phone Using The Keypad

    IP Phone 2004. The IP Phone 2001 and IP Phone 2002 have a one-line display. The IP Phone 2004, Avaya 2007 IP Deskphone and Avaya 2050 IP SoftPhone have a three-line display. Users can scroll through the display screens using the navigation keys.

  • Page 164: Branch User Config Command

    To complete the interface-based configuration of the Branch User, the administrator or a trusted user can configure the IP Phone with the Branch User Config command. Before proceeding, be sure to obtain the required passwords as described in Password requirements on page 162. Branch Office Installation and Commissioning June 2014 Comments? infodev@avaya.com...
  • Page 165 Whenever a valid change is made to BUID/MOTN in LD 11, the IP Phone, if in Local Mode, is automatically redirected to the main office. A service change to BUID/MOTN does not affect IP June 2014 Branch Office Installation and Commissioning Comments? infodev@avaya.com...
  • Page 166 4. Enter the branch password; that is, the IP Phone Installer's Password or Temporary IP Phone Installer's Password for the TPS node at the Branch Office. See Figure 68: Branch password on page 166. Figure 68: Branch password Branch Office Installation and Commissioning June 2014 Comments? infodev@avaya.com...
  • Page 167 IP Phone cannot. Symptom: The terminal registers to the MG 1000B TPS and is redirected to the main office (displaying the "Locating Remote Server" message). When it does not successfully June 2014 Branch Office Installation and Commissioning Comments? infodev@avaya.com...

  • Page 168: Survivability Test

    Caution: After all IP Phones are installed, perform a datadump (using LD 43 EDD or through NRS Manager) on the MG 1000B CP PM. Refer to Avaya Communication Server 1000E: Installation and Configuration (NN43041-310) for more information. 7. Execute the EDD command in LD 43.
  • Page 169 1140,1150, 1165, 1210, 1220,1230 CUST <num> Customer number. l s c u With Communication Server 1000 Release 5.0 or later, MG 1000B with Gateway Controller, the TN entered for an IP Phone is l s c u. Prompt Response Description...
  • Page 170 Press the Select soft key. This reregisters the telephone at the main office. If Resume Normal Mode is not selected, the IP Phone automatically returns to Normal Mode after ten minutes. Branch Office Installation and Commissioning June 2014 Comments? infodev@avaya.com...

  • Page 171: Installing Ip Phones Through Ld 11

    Setting and changing the Station Control Password Configuration page 110 to provision the Station Control Password at the Branch Office. To prevent user password confusion, Avaya recommends that the same SCPW be used at the main office and the Branch Office.
  • Page 172 Not prompted if SCPL = 0. Precede with X to delete. 3. (Optional) Disallow usage of Virtual Office. For more information on the Virtual Office feature, refer to Avaya Features and Services Fundamentals, NN43001-106-B1. Table 27: LD 11 Enable/disable Virtual Office (optional). Prompt...

  • Page 173: Using The Ip Phones

    Telephone Options The IP Phone Options feature is described in Avaya IP Deskphones Fundamentals, NN43001-368. Using the Telephone Options feature This procedure explains how to use IP Phone Options features. The IP Phone has been configured using Branch User Config and is operating in Normal Mode.

  • Page 174: Virtual Office Login On The Branch Office

    7. Press the Services key or the Cancel soft key to exit the Services menu. Virtual Office Login on the Branch Office The Virtual Office Login feature is described in Avaya IP Deskphones Fundamentals, NN43001-368. Branch Office Installation and Commissioning June 2014 Comments? infodev@avaya.com...
  • Page 175 7. To log out of Virtual Office: a. Press the Services key to display the Options menu. b. Use the navigation keys to highlight Virtual Office Logout. Figure 75: Virtual Office application menu on page 176. June 2014 Branch Office Installation and Commissioning Comments? infodev@avaya.com...

  • Page 176: Feature Interactions Between Branch User And Virtual Office Logins

    When a Branch User IP Phone re-powers, it registers with the MG 1000B Call Server, and is automatically redirected to the main office. If another IP Phone has already occupied the Main Office Branch Office Installation and Commissioning June 2014 Comments? infodev@avaya.com...

  • Page 177: Test Local Mode

    Press the Select soft key. If you fail to resume Normal Mode, Test Local Mode lasts for ten minutes, and then automatically redirects the telephone to the main office Call Server. June 2014 Branch Office Installation and Commissioning Comments? infodev@avaya.com...

  • Page 178: Personal Directory, Callers List, Redial List

    (on MG1000B) . As previously stated, these features are available in Normal mode only. Branch Users access their Personal Directory, Callers List, and Redial List using the SCPW. For more information on the Personal Directory, Callers List, and Redial List features, refer to Avaya Signaling Server IP Line Applications Fundamentals, NN43001-125.

  • Page 179: Digital Devices

    171. Digital devices supported by the Branch Office feature include digital telephones, consoles, and an Avaya CallPilot Mini or Avaya CallPilot 201i. M3900-series digital telephones also have a Virtual Office feature. This feature is not network-wide, like the Virtual Office feature on the IP Phones. For an M3900-series telephone, a Virtual Office login enables a registration to another TN within the MG 1000B CP PM.

  • Page 180: Chapter 15: Emergency Services Configuration

    191 Overview For MG 1000B applications, Avaya recommends two alternative general methods to specify which digit string results in a call to emergency services: • Use the Emergency Services Access (ESA) feature. This is the preferred method in North America, the Caribbean and Latin America (CALA), and in those countries that are members of the European Union (EU).

  • Page 181: Emergency Services Access (Esa)

    PSAP. Instead, that node must re-route the call to another node. This re-routing is an unnecessary use of resources. • If the node is a Avaya Communication Server 1000E node, the only tandem trunks are IP Peer trunks. There is no way to specify the appropriate rerouting digits (that is, Prepend Digits) to reroute the ESA call to another node with direct ESA trunks.

  • Page 182: Configuring Esa For The Branch Office

    • If the local TN is provisioned as Auto Update, then cached location data in the phone is rejected if undefined locally, and unknown location values (ERL = 0, ECL = 0, LocDesc = Branch Office Installation and Commissioning June 2014 Comments? infodev@avaya.com...
  • Page 183 NRS so that the Virtual Trunk routes the call to the Branch Office. Configuring the main office You can use Element Manager or the Command Line Interface for this procedure. Refer to Avaya IP Peer Networking Installation and Commissioning, NN43001-313 for details.
  • Page 184 AC0 is to be entered in place of AC1 or AC2. • ESA Prefix = Digit string added to start of ESDN. This is a unique prefix in the NRS. Avaya recommends that users use Branch Office Installation and Commissioning June 2014 Comments? infodev@avaya.com...
  • Page 185 Number defined for the Branch Office zone. Refer to Avaya IP Peer Networking Installation and Commissioning , NN43001-313. Avaya recommends that customers use "0" + the ESN Location code + ESDN. An example for location code 725 would be 0725911. The zero is recommended to prevent a collision in the ESN data with the HLOC entry.
  • Page 186 The maximum number of groups allowed is 5. - FLEN (0)-24 Flexible Length The number of digits the system expects to receive before accessing a trunk and outpulsing these digits. … Branch Office Installation and Commissioning June 2014 Comments? infodev@avaya.com...
  • Page 187 It the route number has been configured, remove it by entering "x" at the prompt. Configuring the Branch Office You can use Element Manager or the Command Line Interface for this procedure. Refer to Avaya IP Peer Networking Installation and Commissioning, NN43001-313. 1. Configure an emergency trunk (CAMA or PRI).
  • Page 188 Branch Office. Avaya recommends that a consistent pattern be followed for all ESA calls. For example, use "0" + ESN Location code of the Branch Office node + the ESDN. An example for location code 725 would be: 0725911.

  • Page 189: Configuring Esa In Element Manager

    From the Zone List window in Element Manager, select the Branch Office Emergency Service option, and enter the necessary information. Refer to Figure 78: Zone Emergency Service Information on page 189 Figure 78: Zone Emergency Service Information June 2014 Branch Office Installation and Commissioning Comments? infodev@avaya.com...

  • Page 190: Provisioning Esa Calls For A Central Deployment

    To dial the emergency number in this configuration, a Branch Office user must dial the appropriate Access Code. For example, if AC2 is 9, then the user must dial "9 999" to make a call to emergency services. Branch Office Installation and Commissioning June 2014 Comments? infodev@avaya.com...

  • Page 191: Clid Verification (Clidver)

    M911_NPID_FORM and NPID_TBL_NUM are not prompted in the RDB. If the 911P prompt is set to YES, IFC prompt is set to SL1 by default since 911P trunks are supported only over MCDN. June 2014 Branch Office Installation and Commissioning Comments? infodev@avaya.com...
  • Page 192 Emergency Services configuration Figure 79: Prompts and responses in LD 16 Branch Office Installation and Commissioning June 2014 Comments? infodev@avaya.com...

  • Page 193: Chapter 16: Maintenance And Diagnostics

    1150E IP Deskphone, Avaya 1165E IP Deskphone, Avaya 2033 IP Conference Phone, and Avaya 1210 IP Deskphone, Avaya 1220 IP Deskphone, Avaya 1230 IP Deskphone. It does not apply to the IP Phone KEM, Expansion Module for Avaya 1100 Series IP Deskphones, Avaya 2050 IP SoftPhone, WLAN 2210/2211/2212, WLAN 6120/6140, or IP Deskphones with SIP software.
  • Page 194 Virtual Office. However, the firmware files can be upgraded, if required, when the Virtual Office session is terminated. For information on Enhanced UNIStim Firmware, refer to Avaya Signaling Server IP Line Applications Fundamentals, NN43001-125. Each IP Deskphone that is redirected back to the Branch Office has its firmware version checked against the MG 1000B TPS firmware policy.

  • Page 195: Troubleshooting

    This display can only be cleared by pressing the Cancel key. While this display appears, the user can only receive calls; they cannot make outgoing calls. Upgrade procedures can be found in Avaya Signaling Server IP Line Applications Fundamentals, NN43001-125.
  • Page 196 Branch User ID not found in Check main office Branch User configuration, and ID (2) any equipped TN. update as required. Incorrect Branch User ID Correct Branch User ID configuration in Branch configured. Office TN. Branch Office Installation and Commissioning June 2014 Comments? infodev@avaya.com...
  • Page 197 Firmware incompatible with Upgrade IP Phone firmware at the MG 1000B TPS. main office TPS. Avaya recommends that customers upgrade all MG 1000B TPSs before they upgrade the main office TPS during firmware upgrade. The IP Phones are directed to the Branch Office for firmware upgrade, and then redirected to the main office automatically.
  • Page 198 Set or enable the IP Phone Installer's Password or or Temporary IP Phone Temporary IP Phone Installer's Password at the MG Installer's Password at the MG 1000B TPS. 1000B TPS not configured or disabled. Branch Office Installation and Commissioning June 2014 Comments? infodev@avaya.com...
  • Page 199 Server Unreachable Main office TPS is Check network configuration, and update as unreachable from the MG required. 1000B TPS. Main office TPS is down. Bring main office Signaling Server into service. June 2014 Branch Office Installation and Commissioning Comments? infodev@avaya.com...

  • Page 200: Signaling Server Cli Commands

    This section describes Command Line Interface (CLI) commands on the Signaling Server specific to the MG 1000B. Refer to Avaya Signaling Server IP Line Applications Fundamentals, NN43001-125 for a complete list of all CLI commands available on the Signaling Server.

  • Page 201: Verify Clid

    If the CLIDVER report is generated on the MG 1000B CP PM, the CLID is the same as the CLID entry composed in LD 15' For more information about this feature, see Avaya Emergency Services Access: Description and Administration, (NN43001-613).

  • Page 202: Print Branch Office Zone Information

    Description ENL ZBR [<Zone>] [ALL] [LOC] [ESA] [TIM] Enable features for the Branch Office zone. If no specific features are specified, ALL is assumed. DIS ZBR [<Zone>] [ALL] [LOC] [ESA] [TIM] Branch Office Installation and Commissioning June 2014 Comments? infodev@avaya.com...

  • Page 203: View Status Of Branch Office Zone At Main Office Call Server

    The notification level can be changed on a zone-by-zone basis so that a particular zone, such as a Branch Office zone, is monitored more closely than others. LD 117 contains commands for changing and viewing the notification level for a zone. For more information on PVQ, refer to Avaya Converging the Data Network with VoIP , NN43001-260.

  • Page 204: Print Pvq Statistics

    Print a table of the notification level for the specified zone. Print PVQ statistics LD 117 contains a command to print PVQ statistics for the Branch Office zone. For more information on PVQ, refer to Avaya Converging the Data Network with VoIP (NN43001-260). Table 41: LD 117 PVQ statistics. Command Description PRT ZQOS <Zone>...

  • Page 205: Print Mg 1000B Software And System Information

    Linux processes. Call Server VxWorks Shell (su) Reboot Invoke Call server warm start No impact to other Linux processes. Reboot -1 Invoke Call Server cold start No impact to other Linux processes. June 2014 Branch Office Installation and Commissioning Comments? infodev@avaya.com...

  • Page 206: Appendix A: Preprogrammed Data

    212 Introduction To install an Avaya Communication Server 1000E system as a Branch Office, you must first enter customer data in overlays. For example, you must assign features to the telephone keys. For software installation, it is not necessary to program data for the Call Server in advance. The Call Server can be programmed with the minimum number of files to enable the Branch Office feature to operate.

  • Page 207: Default Numbering Plan

    207 shows the default numbering plan for a Branch Office. Table 46: Default numbering plan First digit First digit Preprogrammed use for digit SPRE code Not used Not used Not used Not used June 2014 Branch Office Installation and Commissioning Comments? infodev@avaya.com...

  • Page 208: Important Extension Numbers

    208 lists the FFCs for the Communication Server 1000E system. Table 48: Flexible Feature Codes FFC Prompt Definition ASRC Automatic Set Relocation AREM Automatic Set Removal Code ADMN Administration Set Access Code CFWA Call Forward All Calls Activate Branch Office Installation and Commissioning June 2014 Comments? infodev@avaya.com...

  • Page 209: Sdi Ports

    The value for "XX" is set on the faceplate of the Server. Table 49: Pre-configured SDI ports TTY Number Card Port Configuration MTC/SCH/BUG XX/8/1/NONE MTC/SCH/BUG 1200/8/1/NONE 1200/8/1/NONE Table 50: Pre-configured PTY ports TTY Number Card Port MTC/SCH/BUG MTC/SCH/BUG June 2014 Branch Office Installation and Commissioning Comments? infodev@avaya.com...

  • Page 210: Modem Port

    The telephone tones in North America are as follows: • Dial tone: A continuous tone. • Special dial tone: Three beeps followed by continuous dial tone. • Overflow tone: Like a busy tone, except faster and higher. Branch Office Installation and Commissioning June 2014 Comments? infodev@avaya.com...

  • Page 211: Trunk Routes

    7141 7142 7143 7144 7150 7151 7152 Trunk routes marked with an asterisk (*) are configured to support Call Detail Recording (CDR) output. CDR is pre-configured in LD 16 as follows: June 2014 Branch Office Installation and Commissioning Comments? infodev@avaya.com...

  • Page 212: System Parameters

    Number of Call Registers (NCR) Multiple Appearance Redirection Prime (MARP) feature allowed Refer to "Capacity Engineering" in Avaya Communication Server 1000E: Planning and Engineering, NN43041-220 for further information on buffer sizes. The preprogrammed data also include virtual superloops 96, 100, 104, 108, and 112.
  • Page 213 LDR Wink Start Supv = YES 3COM/600 LDR Wink Start Supv = YES 3COM/900 LDR Wink Start Supv = YES 3COM/900 3COM/600 3COM/600 3COM/600 3COM/600 3COM/900 3COM/900 3COM/900 3COM/900 3COM/600 600/1200 600/1200 3COM/600 3COM/600 June 2014 Branch Office Installation and Commissioning Comments? infodev@avaya.com...
  • Page 214 Preprogrammed data Mode Card Model Signaling DIP or DTN BIMP and TIMP 3COM/600 3COM/600 3COM/900 3COM/900 3COM/900 3COM/900 -/600 -/600 3COM/600 3COM/600 3COM/600 3COM/600 3COM/900 3COM/900 3COM/900 3COM/900 Branch Office Installation and Commissioning June 2014 Comments? infodev@avaya.com...

  • Page 215: Appendix B: Branch Office Engineering Example

    Appendix B: Branch Office engineering example Introduction This chapter provides sample engineering calculations for a Branch Office with an Avaya Communication Server 1000M or Avaya Communication Server 1000E Main Office. Assumptions The following section assumes the equipment and traffic characteristics of the Branch Office.

  • Page 216: Calculations

    Core. An actual system could require different types and numbers of cards. Traffic Traffic calculations are based on the traffic flows shown in Figure 81: Branch Office traffic flow page 217. Branch Office Installation and Commissioning June 2014 Comments? infodev@avaya.com...
  • Page 217 VTRK_CCS = Total_IP_CCS – Intra_IP_CCS = 720 – 324 = 396 CCS 5. Calculate the TDM telephone to Branch Office IP Phone traffic (requires DSPs). TDM_IP_CCS = Total_TDM_CCS x % of calls to IP Phones = 240 x 0.6 = 144 CCS June 2014 Branch Office Installation and Commissioning Comments? infodev@avaya.com...

  • Page 218: Dsp Requirements

    2. Calculate the number of DSPs required to support this level of traffic by using Table 55: Erlang B and Poisson values in 32-port increments on page 218, Erlang B P.01 columns to determine the number of DSPs required at the Branch Office. Branch Office Installation and Commissioning June 2014 Comments? infodev@avaya.com...

  • Page 219: Virtual Trunk Requirements

    Call Server Real-time usage The following is a simplified engineering example of a Communication Server 1000E. For more information about engineering a Communication Server 1000E , see Avaya Communication Server 1000E — Planning and Engineering, NN43041-220. When a branch is operating in a normal branch mode, the Main Office handles the local UNIStim IP traffic, therefore only inbound virtual trunk traffic affects the branch.

  • Page 220: Mg 1000B Core And Mg 1000B Expander Requirements

    + 1.156 + 1.87 + 0.25 = 5.127 Note: For more information about real time factors (f4, f9, f10, error_term), see Avaya Communication Server 1000E — Planning and Engineering, NN43041-220. Use the Communication Server 1000E Co-resident Calling Server and Signaling Server column.

  • Page 221: Bandwidth Requirement For Branch Office Lan/Wan

    See the Branch Office Bandwidth Erlangs number, in the bandwidth table, to find the corresponding bandwidth required to carry the traffic to the Main Office. For information about the bandwidth table and calculating LAN/WAN bandwidth requirements, see Avaya Converging the Data Network with VoIP Fundamentals , NN43001-260. The codec selection greatly impacts the bandwidth requirements.

  • Page 222: Cs 1000 Main Office With Mg 1000 B And Srg

    Branch Office engineering example CS 1000 Main Office with MG 1000 B and SRG The following example shows a sample configuration of bandwidth zones for a Main Office location and two Branch Office locations. One branch location is an MG 1000B, and the other is a Survivable Remote Gateway (SRG).
  • Page 223 CS 1000 Main Office with MG 1000 B and SRG The Zone table for the Main site contains zone information for every MG 1000B and SRG. The MG 1000B must have the zone information for its own individual zone, plus a zone for the virtual trunks.

Table of Contents