SRG Configuration Guide (Survivable Remote Gateway) SRG software version 1.0

Transcription

1 Part No. P March 24, 2004 SRG Configuration Guide (Survivable Remote Gateway) SRG software version 1.0

2 2 Copyright 2004 Nortel Networks All rights reserved. The information in this document is subject to change without notice. The statements, configurations, technical data, and recommendations in this document are believed to be accurate and reliable, but are presented without express or implied warranty. Users must take full responsibility for their applications of any products specified in this document. The information in this document is proprietary to Nortel Networks NA Inc. Trademarks NORTEL NETWORKS is a trademark of Nortel Networks. Microsoft, MS, MS-DOS, Windows, and Windows NT are registered trademarks of Microsoft Corporation. Symbol, Spectrum24, and NetVision are registered trademarks of Symbol Technologies, Inc. All other trademarks and registered trademarks are the property of their respective owners. P

3 Contents 3 Preface Before you begin Important notes Symbols used in this guide Text conventions Acronyms used in this guide How to get help Chapter 1 SRG overview How does SRG fit into an IP network? Succession Main Office configuration for SBO Interoperability between systems Configuring SRG Where to get configuration information Process map for creating an SRG Chapter 2 Before you start: Gathering information SRG information to Main Office administrator Main Office information SRG network information SRG information Chapter 3 Creating an SRG Creating the SRG Installing the SRG hardware Entering the SRG keycode Running the Quick Start Wizard Running the SRG wizard Viewing and changing Main Office settings Determining SRG status Chapter 4 Setting up the private VoIP network Notes about networking Bandwidth Management (Succession 1000/M interoperability) Configurations for all levels Firewall input and output filter entries for SRG Setting up MCDN Configuring the Private dialing plan SRG Configuration Guide

4 4 Contents Setting up Target lines Configuring VoIP trunking Configuring the VoIP trunks (local gateway) Configuring VoIP lines Assigning Remote Access Packages to VoIP lines Routing between systems Basic routing (internal calls to the Main Office) Advanced routing: Seamless dialing across modes Gatekeeper routing Switching from VoIP trunk to PSTN (fallback) Configuring outgoing routing and destination codes Configuring destination codes to the SRG PSTN Chapter 5 Configuring PSTN lines Configuring the Public dialing plan Setting up PSTN lines Local mode line configuration Chapter 6 Setting up IP telephones Setting up telephone records Adding DN records with a wizard Adding DN records individually Setting up the IP telephone for registration Configuring and registering IP telephones on-site Adding Main Office parameters to redirect IP telephones Testing in Local mode Advanced programming Chapter 7 Setting up analog devices Chapter 8 Troubleshooting Initial configuration troubleshooting IP terminal status messages Troubleshooting fallback to Local mode Manually redirecting IP telephones Error when accessing the wizard button page Notes to the user: SRG in local mode IP telephones i2050 Software Phone in Local Mode i2004 in Local mode P

5 Contents 5 i2002 in Local mode ATA extension features Glossary Succession and SRG terminology Glossary of terms Index SRG Configuration Guide

6 6 Contents P

7 Preface 7 This guide explains how to setup and configure a Survivable Remote Gateway (SRG) Branch Office for an IP network. This section includes the following general information: Before you begin on page 7 Important notes on page 7 Symbols used in this guide on page 8 Text conventions on page 9 Acronyms used in this guide on page 9 How to get help on page 10 Before you begin This guide is intended for two main audiences: the person who installs and sets up the BCM200 or BCM400 into SRG mode the system administrator who manages the system once the SRG is installed and running This guide assumes the following: installers are familiar with Business Communications Manager hardware and software and IP telephony and VoIP trunk configuration on the Business Communications Manager and/or Branch Office configuration and VoIP trunk configuration for the equipment being used as the Main Office. operators managing the data portion of the system are familiar with network management and applications required Main Office Call Server and Signaling Server hardware and software is installed and running correctly; the Branch Office IP telephone H.323 end points have been configured on the Main Office server, and the necessary information has been provided to the SRG installer, refer to Main Office information on page 22. required PSTN lines, media bay modules, IP telephones, ATAs and analog equipment or ISDN equipment for the SRG have been obtained and are ready to be installed. Important notes BCM1000/M is not supported as an SRG. Network Control Manager (NCM) for BCM does not support SRG administration. This document provides information relevant to the SRG configuration, only. Configuration information that is the same as for Business Communications Manager will be referred to in brief and provided with a reference to the main Business Communications Manager documentation. Also, all help links on the Unified Manager are based on Business SRG Configuration Guide

8 8 Preface Communications Manager documentation. The help links under the Services//SRG heading are linked to this document. Main office server configuration Succession Main Office configurations must be running software version 3.0 or newer to support this SRG configuration. Ensure that all relevant patches are also installed. For Succession Main Office programming for SRG, refer to the Succession 1000/M Main Office Configuration Guide for SRG, which provides specifics for Succession configuration of an SRG. This document is located on the SRG documentation CD. For general information about Succession Branch Office configuration, refer to the Branch Office NTP ( ) in the Succession documentation suite. Symbols used in this guide This guide uses symbols to draw your attention to important information. The following symbols appear in this guide: Caution: Caution Symbol Alerts you to conditions where you can damage the equipment. Danger: Electrical Shock Hazard Symbol Alerts you to conditions where you can get an electrical shock. Warning: Warning Symbol Alerts you to conditions where you can cause the system to fail or work improperly. Note: Note Symbol A Note alerts you to important information. Tip: Tip Symbol Alerts you to additional information that can help you perform a task.! Security Note: This symbol indicates a point of system security where a default should be changed, or where the administrator needs to make a decision about the level of security required for the system. P

9 Preface 9 Text conventions This guide uses the following text conventions: angle brackets (< >) bold Courier text italic text plain Courier text FEATURE HOLD RELEASE Indicates that you choose the text to enter based on the description inside the brackets. Do not type the brackets when entering the command. Example: If the command syntax is: ping <ip_address> you enter: ping Indicates command names and options and text that you need to enter. Example: Use the dinfo command. Example: Enter show ip {alerts routes}. Indicates book titles Indicates command syntax and system output, for example, prompts and system messages. Example: Set Trap Monitor Filters Indicates that you press the button with the coordinating icon on whichever set you are using. Acronyms used in this guide This guide uses the following acronyms: ATA (or ATA2) BCM BO BUID CCR DSP FW GUI IP ISDN LAN MCDN MO MOTN MSC Analog Terminal Adapter Business Communications Manager Branch Office Branch User ID Custom Call Routing Digital Signaling Processor Firmware Graphical User Interface Internet protocol Integrated Services Digital Network Local Area Network Meridian Customer Defined Network Main Office Main Office TN Media Services Card (Branch Office) SRG Configuration Guide

10 10 Preface NPI OTM PSTN SRG VPNI ZACB ZDP Numbering Plan ID Optivity Telephony Manager Public Switched Telephone Network Survivable Remote Gateway Virtual Private Network Identifier (Main Office) Zone Access Code Behavior Zone Digit Prefix How to get help If you do not see an appropriate number in this list, go to USA and Canada Authorized Distributors - ITAS Technical Support Telephone: NORTEL ( ) If you already have a PIN Code, you can enter Express Routing Code (ERC) 196#. If you do not yet have a PIN Code, or for general questions and first line support, you can enter ERC 338#. Website: Presales Support (CSAN) Telephone: NORTEL ( ) Use Express Routing Code (ERC) 1063# EMEA (Europe, Middle East, Africa) Technical Support - CTAS Telephone: * European Freephone European Alternative/ United Kingdom +44 (0) Africa Israel * Note: Calls are not free from all countries in Europe, Middle East or Africa Fax: emeahelp@nortelnetworks.com CALA (Caribbean & Latin America) Technical Support - CTAS Telephone: csrmgmt@nortelnetworks.com P

11 Preface 11 APAC (Asia Pacific) Technical Support - CTAS Telephone: Fax: asia_support@nortelnetworks.com In-country toll free numbers Australia 1800NORTEL ( ) China India Indonesia Japan Malaysia New Zealand Philippines Singapore South Korea Taiwan Thailand Service Business Centre & Pre-Sales Help Desk SRG Configuration Guide

12 12 Preface P

13 Chapter 1 SRG overview 13 This section describes how a Survivable Remote Gateway (SRG) acts as an IP Branch Office to a central Main Office server. For this release (version 1.0), SRG can act as a Branch Office for Succession 1000/M systems running version 3.0 software. Overview information is included in: How does SRG fit into an IP network? Succession Main Office configuration for SBO on page 14 Configuring SRG on page 15 Process map for creating an SRG on page 17 How does SRG fit into an IP network? The SRG provides IP telephony service for small offices. During Normal mode operation, the IP telephones register to the Main Office, which provides the services and features supported by the Main Office software. All calls to the SRG are routed through the Main Office. This includes local calls to the SRG, which are automatically forwarded to the Main Office to process, although the connected call may only require a local IP channel. If the SRG loses the WAN connection with the Main Office, the SRG IP telephones revert to Local mode. This means that they reregister with the SRG. During Local mode a very limited set of call features is available to the telephone, since these features are based on the SRG feature set, which differs from the Main Office feature set. By providing a minimum of features, users who are familiar with the Main Office features can still make calls using familiar steps. The telephone display changes to indicate the available features, and to notify the user that the telephone is in Local mode. Once IP communication is restored, the IP telephones automatically reregister with the Main Office, and users once again have access to all the Main Office services. The following figure shows how an SRG fits into an IP network. SRG Configuration Guide

14 SUCCESSION SUCCESSION 14 Chapter 1 SRG overview Figure 1 Networking between the Main Office, the SRG, and the IP telephones Media Gateway Server Main Office IP telephone Gatekeeper VoIP trunk IP network connections SRG LAN Signaling Server Call Server WAN LAN IP Telephone Not all IP devices on the SRG need to be redirected to the Main Office. If IP telephones are not redirected, these telephones remain controlled by the SRG software, and use the SRG local mode feature set. Call traffic between the two systems is resolved through a Gatekeeper, which needs to be programmed with both the Main Office and SRG routing and IP information. Succession Main Office configuration for SBO Main Office programming for branch offices is contained in the Succession 1000/M Branch Office NTP ( ). The relevant tasks in this NTP describe how to set up the Succession Main Office to support a Succession Branch Office (SBO). SRG-specific configuration for the Main Office is contained in a book called Succession 1000/M Main Office Configuration Guide for SRG, which is included on the SRG documentation CD. This book provides a process map that outlines the configuration required on a Succession Main Office to support SRG. The document also highlights the relevant sections in the Succession 1000/M Branch Office NTP. Due to differences in how the two systems handle dialing plans and routing, and the different terminology used for these processes, the Main Office administrator needs to be aware of the information in both books to ensure that the Main Office settings accommodate SRG capabilities. Important note: The Succession 1000/M Main Office Configurative Guide for SRG assumes that the person performing the Succession configuration is familiar with Succession Branch Office configuration and has access to the required Succession documentation. P

15 Chapter 1 SRG overview 15 Interoperability between systems Information must be exchanged between the Main Office and SRG for proper configuration of both systems. The system administrator for the Main Office provides the required details for the SRG Wizard and a list of telephone records that have been configured on the Main Office system for the SRG IP telephones that will redirected to the Main Office. The Succession Main Office also controls bandwidth management and zone information that determines how the SRG calls are handled on the main office. You must coordinate this information with the destination codes you choose for routing calls to and from the Main Office. This book and the Succession 1000/M Main Office Configuration Guide for SRG contain charts that can be filled out with the required operational information. Refer to Chapter 2, Before you start: Gathering information, on page 21. The Main Office guide also provides a section that describes how dialing plans are accommodated between the two systems and the gatekeeper, including simple examples showing how call dial strings are handled from one system to the other. Also included is an overview of Bandwidth Management configuration on the Main Office, and a list of interoperability issues between the two systems. Configuring SRG SRG is configured on a BCM200 or BCM400 hardware platform running BCM 3.6 software. Warning: You cannot revert back after you configure the system as an SRG. Any existing data, except network information, is deleted during the conversion process. 1 The hardware is installed in the same way as for any Business Communications Manager setup. Trunk media bay modules connect PSTN lines to the system. Station media bay modules connect analog equipment, such as fax machines, to the system. If the computer you are going to use to configure the system is not on the same LAN as the equipment, you will need to set an IP address and Netmask for the system to allow configuration from a remote computer. Refer to the BCM200/BCM400 Hardware Installation Guide (P ) for detailed instructions. Telephony hardware note: The SRG does not support digital telephones. Only IP telephones, analog equipment, and ISDN equipment are supported. If you use a digital station module (DSM) in your system, you must connect an ATA2 for each piece of analog equipment. IP keycodes: The conversion to SRG installs VoIP trunk and IP telephony functionality. There is no need to acquire keycodes for these features. SRG Configuration Guide

16 16 Chapter 1 SRG overview Figure 2 SRG hardware platform: BCM400 CTM 4 BCM400 1 Aux Primar Mirror Alarm Maste DSM PowerStatus NOTE: The media bay modules shown in the diagrams are for context only. Figure 3 SRG hardware platform: BCM200 DSM PowerStatus 2 Once the system is installed, open the Unified Manager and enter an SRG keycode and reboot the system. Note: Keycodes are obtained through the normal keycode generation process. Refer to the keycode document that came with your SRG kit or ask your service support for instructions. 3 On the rebooted system, run the Quick Start Wizard to set up the telephony system settings, such as market profile, start DN and DN length. When you submit the wizard, the system reboots again. 4 On the rebooted system, run the SRG Wizard, which enters the Main Office connect information. This information appears on the SRG//Main office and IP Telephony//IP Trunks//H.323 trunks on the Local Gateway IP Interface screen. 5 Configure the private network between the SRG and the Main Office and the PSTN network connected to the SRG. Ensure that the VoIP lines are set up with a Remote Access package that provides the required access to the SRG and to the SRG PSTN. 6 Configure PSTN lines and create a PSTN line pool. 7 Ensure that routing is correctly configured for calls leaving and coming into the SRG. Bandwidth management parameters and zone parameters are configured at the Main Office for the SRG. This functionality must be taken into account when configuring destination codes on the SRG. 8 Program the telephones. a Set up the DN record for each telephone. b c Set up the IP terminals record to allow registration to the SRG. Configure each IP telephone so that it registers with the SRG. P

17 Chapter 1 SRG overview 17 At this point, the telephones are only running in local mode. The display shows only three features: Transfer, Last Number Redial, and a key that displays the DN of the telephone, which is used as a line/intercom key. Test the telephones in this mode. 9 Configure those IP telephones that you want redirect to the Main Office server. When a telephone successfully registers to the Main Office, the display changes, and the telephone now has access to all the Main Office call features. The rest of this guide provides touchstones that point out the configuration information that is unique to SRG, or which needs to be adjusted to accommodate Main Office configuration requirements. The information is for a generic installation that is connected directly to the WAN, and to PSTN trunks. More complicated installations will need to assess what information is required to set up the system to work as described. Where to get configuration information Detailed system configuration can be found in the Business Communications Manager documentation suite (refer to BCM documentation attached to the Unified Manager and/or on the BCM documentation CD). Also, each heading and tab on the Unified Manager navigation tree has a help link. Help links provide information specific to the topic, as well as a portal to the main documentation. The following documents are referred to within this guide when tasks require standard BCM configuration. First Time Install Guide (in the box with the BCM200/BCM400 hardware) (P ) BCM200/BCM400 Installation Guide (P ). Programming Operations Guide (P ). IP Telephony Configuration Guide (P ). Programming Records (documentation CD only) (P ). Process map for creating an SRG The following process maps describe the steps required to create an SRG. Refer to: Creating the SRG environment on page 18 Configuring the SRG on page 19 SRG Configuration Guide

18 18 Chapter 1 SRG overview Figure 4 Process map: Setting up the environment Creating the SRG environment The Main Office is installed and running and has configured the information to support SRG. You have the required network and configuration information. ( Before you start: Gathering information on page 21) Install the BCM200 or BCM400. Ensure that the power switch is off. Set dip switches on the media bay modules and install them into the BCM200/BCM400 Wire PSTN lines and any analog lines and connect them to the BCM200/BCM400 Turn the power switch to the On position. Allow the system to boot (LEDs on front of hardware) Connect a computer through the serial port or use a cross-over cable. Set the IP address and subnet mask for the BCM, if required, so you can open the Unified Manager. Open Unified Manager over the network. Enter the SRG keycode. ( Entering the SRG keycode on page 28). Reboot the system when prompted to do so. The system reconfigures as an SRG Log out of all Browser windows, then re-open the Unified Manager. Run the Quick Start Wizard. ( Running the Quick Start Wizard on page 29). The system will reboot again. Go to the process map: Configuring the SRG on page 19. P

19 Chapter 1 SRG overview 19 Figure 5 Process map: Configuring the SRG Configuring the SRG Re-enter the Unified Manager and run the SRG wizard. ( Running the SRG wizard on page 30) Configure the modules, VoIP trunks, PSTN lines, dialing plan, and routing. ( Setting up the private VoIP network on page 37 and Configuring PSTN lines on page 63) Configure the IP telephones and analog devices. ( Setting up IP telephones on page 67 and Setting up analog devices on page 81) Install the IP telephones and devices on site. (IP Telephony Configuration Guide) The IP telephones register to the SRG. Dialing plan Access codes Private network data engineering VoIP and PSTN line config/ redirection, CLID/OLI display Check that the Main Office is ready to register the SRG. Configure the IP telephones to register to the Main Office. ( Adding Main Office parameters to redirect IP telephones on page 75 Refer to BCM documentation VoIP, PSTN routing Fallback scheduling (optional) Refer to Advanced routing: Seamless dialing across modes on page 50 Check SRG Terminal parameters record ( Adding Main Office parameters to redirect IP telephones on page 75) to determine terminal status. ( IP terminal status messages on page 86) Test the telephones and analog equipment in Local mode Allow each telephone to register to the Main Office. Troubleshoot any registration issues. Test the telephones and analog equipment in Normal mode Familiarize users with the services for local mode. ( Notes to the user: SRG in local mode on page 91) SRG Configuration Guide

20 20 Chapter 1 SRG overview P

21 Chapter 2 Before you start: Gathering information 21 You need to know the information contained in the tables in this section before you start your installation and Survivable Remote Gateway (SRG) configuration. This information comes from the IP network administrator, the Main Office administrator, and the customer or site engineer for the SRG. This section includes the following prerequisite tables: SRG information to Main Office administrator Main Office information SRG network information SRG information SRG information to Main Office administrator The Main Office administrator requires the following SRG information before the SRG information can be configured at the Main Office. Table 1 SRG information for the Main Office What you need to supply to the Main Office administrator Information about this system IP network information: SRG public IP address (refer to SRG network information on page 24) SRG net mask Telephony information: List of types of IP telephones, and the quantity of each. Note: Telephone types are hard-coded to the telephone numbers (TNs) at the Main Office. Therefore, you must install the same type of telephones to the DN on the SRG that you intend to match to a specific TN on the Main Office. PSTN number to dial into the Branch Office (in local mode) i2002 i2004 i2050 SRG Configuration Guide

22 22 Chapter 2 Before you start: Gathering information Main Office information The Main Office administrator configures a zone on the Main Office server dedicated to the SRG and the IP telephones which connect to it. You need to obtain this information so that you can program the telephones to be compatible with the call server settings. You also need any specific programming on the Main Office server that affects VoIP trunking. Most of this information is entered into the SRG wizard and shows up on the SRG//Main office screen. The routing and IP telephony information is used to coordinate the SRG information with the call server requirements. Enter this information into the appropriate Programming Record worksheets. Table 2 Main Office interoperation information What you need to get from the Main Office administrator Information about this system Main office IP network information: Main office call server type Primary network connect server Address (subnet?) Succession: same as Gatekeeper IP Alternate Network connect server Network Connect Server port Heartbeat Protocol Port Range Trunk/telephony preferred codecs and jitter buffers list in order of preference, based on Bandwidth Management configuration Gatekeeper requirements Ports required for interoperability. ( Firewall input and output filter entries for SRG on page 40) Telephony programming: TN length, TN range Numbering plan ID *Type of number If UDP: supply LOC code for MO and SRG) * Note: Refer also to the addendum: Succession 1000/M SRG Main Office Configuration for SRG, under the section Matching Succession and SRG dialing configurations. Node ID Virtual Private network ID ( Bandwidth Management (Succession 1000/M interoperability) on page 39) S1000 (default) Private (default) ESN CDP (default) P

23 Chapter 2 Before you start: Gathering information 23 Table 2 Main Office interoperation information (Continued) What you need to get from the Main Office administrator Zone ID ( Bandwidth Management (Succession 1000/M interoperability) on page 39) Main office dial-up number (for PSTN calls to the Main Office in local mode) Access code to reach Main Office PSTN through VoIP trunks. Zone dialing: ZDP appended to SRG IP telephone PSTN dial strings to redirect the call to the SRG PSTN Any steering codes (destination codes) that need to be mirrored by SRG programming. (for instance, is 9 used to dial local calls; what is the long-distance steering code, and so on) IP telephone configuration: Information about this system MOTN list, including what type of telephone is assigned to each number (enter information into the Programming Record) Note: You will need to note the leading number, as SRG will use this as the DN range for CDP dialing. If the CDP access code is more than one digit, the second digit must also be used to further define the DN range. Current IP telephony firmware version Is a VLAN required? SRG Configuration Guide

24 24 Chapter 2 Before you start: Gathering information SRG network information You will need to obtain this information from the person who administers the IP network for your LAN/WAN that connects the SRG to the network. Table 3 SRG information for network connections What you need to know about the SRG IP network Information about this system Refer to the IP Telephony Configuration Guide, Prerequisites chapter for data network prerequisites. Special IP network requirements: Firewall filter ports that need to be manually entered( Firewall input and output filter entries for SRG on page 40) QoS on the SRG: Supports packet hierarchy, but not line quality. H.323 ID (Gatekeeper identification of the SRG) <SRG system name> SRG IP address (public IP address/lan or WAN?) Net mask (if required) Next hop router IP address IP addresses and netmasks for all IP telephones (use programming record worksheets to track installations for systems not using DHCP) Default gateway between the IP telephones and the SRG Any other pertinent network information that may affect either the IP connection or the VoIP trunks. P

25 Chapter 2 Before you start: Gathering information 25 SRG information You need to obtain the following information from the customer or distributor: Table 4 SRG information What you need to know about the SRG IP network information: MCDN network settings, if applicable Confirm that the computers that will be installed with i2050 Software Phone software meet system requirements and can support the USB headset. Ensure that power and network connections have been provisioned for IP telephones at the required locations. Are any telephones located off-site? Gatekeeper information (routing codes) Routing information: Main office screen ( Viewing and changing Main Office settings on page 33): *VoIP trunk access code, if required MO Access Code Length Lines and routing ( Setting up the private VoIP network on page 37 and Configuring PSTN lines on page 63) Number of VoIP lines and the line pools Number of PSTN lines and line pools Make note about routes and destination codes. Remote access package settings for VoIP lines (to access PSTN) Telephony information: Authorization code (included with SRG CD kit). SRG keycode (Refer to Software Keycode Installation Guide (P ) if you require detailed instructions about obtaining a keycode.) Important note: IP telephony, VoIP trunk, and MCDN keycodes are not required for an SRG. These services are automatically activated when the system is configured as an SRG. Required telephony profile DN length (based on MO dialing plan) Available DN range for IP telephones on local system (based on MOTNs and dialing plan requirements) (subtract 300 to find Start DN) Type of PSTN lines/media bay modules TAT required Must match line pool access code/destination code for VoIP trunk route to Main Office UDP dialing plan, only SRG Configuration Guide

26 26 Chapter 2 Before you start: Gathering information Table 4 SRG information (Continued) What you need to know about the SRG Type of station lines/media bay modules. Are ATAs required? ATA installation information is included with each ATA device. How many VoIP lines are required (maximum: 60)? Is more than one VoIP line pool required? IP telephones and analog devices: IP telephones only: List of MOTNs from Main Office administrator. Note which devices are assigned to each terminal number. Location and allocation of IP telephones and analog devices and telephones (record in programming record). Note which IP telephones will configure to the Main Office, and which ones will be used in local mode all the time. Refer to SRG network information on page 24 for IP information for telephone configuration. P

27 Chapter 3 Creating an SRG 27 This chapter describes the tasks that are required for installing the survivable remote gateway (SRG) hardware, and converting the system software to SRG. This section assumes that the hardware has not already been configured as SRG by the distributor or manufacturer. Refer also to the process flowchart, titled: Process map: Setting up the environment on page 18. This section contains the following information: Creating the SRG on page 27 Viewing and changing Main Office settings on page 33 Determining SRG status on page 36 Creating the SRG The following sections describe the actions that are required to install and create an SRG system: Installing the SRG hardware on page 27 Entering the SRG keycode on page 28 Running the Quick Start Wizard on page 29 Running the SRG wizard on page 30 Installing the SRG hardware 1 Ensure that you have gathered all the information outlined in the tables under Before you start: Gathering information on page 21. You can also refer to the Business Communications Manager BCM200/BCM400 Installation Guide if you require more detailed information about hardware installation. 2 Install the BCM200 or BCM400 as you would for any Business Communications Manager installation. Each BCM200/BCM400 comes with a First Time Install Guide. Use this guide for general information about installing the hardware and for information about setting the network address so that you can connect to the Unified Manager from a computer. Use the information you entered into the table under SRG information on page 25. The BCM200/BCM400 Installation Guide provides detailed information about: installing the BCM200 or BCM400 setting the DIP switches on the media bay modules installing the modules wiring the trunk and station connectors and connecting to the hardware installing ATA modules, if required SRG Configuration Guide

28 28 Chapter 3 Creating an SRG 3 When the hardware is operating correctly, on your computer, connect to the Unified Manager and continue with the next section ( Entering the SRG keycode ). Entering the SRG keycode The first thing you need to do is convert the system to the SRG configuration. This is performed by entering an SRG keycode in the Unified Manager under System//Licensing. 1 Click on Licensing. 2 On the top menu, click on Configuration and select Enter a keycode. Figure 6 Accessing the Applied Keycodes dialog Navigation Tree menu Top menu The Applied Keycodes dialog appears. 3 Enter the SRG keycode you noted under SRG information on page 25. Note: The key code has three groups of eight numbers. Enter a hyphen between each group. Figure 7 Applied Keycodes dialog Click Save. A dialog box appears that prompts you to reboot the system (System, (top menu) Logoff//Reboot). 5 When the reboot completes, close all browser windows. P

29 Chapter 3 Creating an SRG 29 6 Go to the next section for instructions about running the Quick Start wizard ( Running the Quick Start Wizard ). Note: IP telephony, VoIP trunk, and MCDN keycodes are not required for an SRG. These services are automatically activated when the system converts to SRG. Running the Quick Start Wizard To set up basic functionality on your system, run the Quick Start Wizard and enter the system information, as required. 1 Log into the Unified Manager. 2 Click the Wizards button. 3 Enter the administrator user name and password in the popup logon dialog box. 4 Click on the Quick Start Wizard button. For details about the Unified Manager wizards, refer to the Programming Operations Guide or click on the help link beside the button. 5 Change the defaults on the various pages, as required by the system. The following table notes the wizard pages and the information each contains. Page 1 Set system name and ensure the time zone is correct. Page 2 - Network Ensure network information is correct Page 3 - Telephony Set Region, Start DN length, Start DN, Received # length (should be the same as Start DN length, unless you change it). Important note: The Start DN and the first number of the DN range for the IP telephones are not the same. The Start DN starts with the first DN of the range of DNs assigned to the station module ports. This range precedes the IP DN range. Page 3 - IP telephones Leave these headings set to the defaults. Page 4 - CallPilot Retain default values. CallPilot is disabled on the SRG. Page 5 Summary page. Check the settings. Click the Submit button when you confirm that the information is correct. The system displays a page indicating that the updates are in process. The system will reboot as part of this process. 6 When the reboot completes, exit the browser windows. 7 Go to the next section for information about running the SRG wizard ( Running the SRG wizard ). SRG Configuration Guide

30 30 Chapter 3 Creating an SRG Running the SRG wizard Run the SRG wizard to enter basic Main Office information and SRG IP gateway information. Refer to the information you entered into the tables under Before you start: Gathering information on page 21 and to fill out the corresponding fields in the wizard. 1 Log into the Unified Manager. 2 Click the Wizards button. 3 Enter the administrator user name and password in the popup logon dialog box. 4 Click the SRG wizard button that now appears in the list of Wizard buttons. 5 Use the table below as a guide through the wizard: Table 5 SRG wizard fields Screen 1, SRG info Refer also to Viewing and changing Main Office settings on page 33 Choose what type of system is being used as the Main Office call server. Enter the IP address for the Main Office network connect server (Entry becomes the Gatekeeper default value.) If you are allow calls to fallback to a backup server, enter the IP address of this alternate Main Office server. (Entry becomes the backup Gatekeeper default value.) (Main Office Call Server Type) S1000 (only option) (Primary Network Connect Server Address) <XXX.XXX.XXX.XXX> (Alternate Network Connect Server Address) <XXX.XXX.XXX.XXX> P

31 Chapter 3 Creating an SRG 31 Table 5 SRG wizard fields (Continued) Enter the port number on the Main Office server/gatekeeper that will allow traffic from this SRG. Enter the port number on the Main Office server/gatekeeper that will receive the heartbeat signal from this SRG. (Network Connect Server Port) Default: (Heartbeat Protocol port) Default: Enter the VOIP Trunk Access Code for the Main Office. (VOIP Trunk Access Code) Enter the period between when the IP telephones are set to Test Local Mode and when they will reset to the Main Office server. Enter a system identifier for the SRG that the Gatekeeper will use to identify signals from the SRG. (Entry becomes Gatekeeper Alias Names default value) Format:XXXXX, where X is the case-sensitive name registered on the gatekeeper. Choose the call identifier that will be used for calls using the VoIP trunk. Choose the type of dialing plan that the Main Office uses to recognize calls from this SRG. Enter the network identification ID number that is written to the IP telephone firmware when the IP telephone registers with the Main Office. This is the node on the Main Office system where the IP telephone DN is configured. Enter the length of any additional digits that need to be added to the BUID when a call is forwarded to the Main Office. Screen 2, SRG H323 Info Refer also to Configuring the VoIP trunks (local gateway) on page 44. Do you want an outbound call to fallback to a PSTN trunk if the VoIP trunk is unavailable? How do you want call signaling to be handled on the network? *Change from default to GatekeeperRouted. Enter the IP address of the gatekeeper for the network. (Defaults to value entered for Primary Network Connect Server address.) Enter any alias names that the gatekeeper needs to recognize for traffic from the SRG. (Defaults to H323 ID field entry.) (Test Local Mode Timer) Default: 10 minutes (H323 ID) Default: NAME:SRG* *This setting must be changed. The system automatically adds Name: to the entry. (Numbering Plan ID) Default: Private (Type of Number) Default: ESN CDP* *This is the recommended type. (Node ID) Default: 999 (MO Access Code Length) Default: 0* *No digits are added if the type of number is ESN CDP. The access code is part of the BUID in a CDP network. (Fallback to Circuit-Switched) Default: Enabled-All (Call Signaling) Default: GatekeeperResolved* (Gatekeeper IP) <XXX.XXX.XXX.XXX> (Alias Names) Enter the number of seconds between TTL registration signals. (Registration TTL) Default: 60 seconds Enter the protocol to be used by the VoIP gateway. Succession 1000/M systems require CSE. (Gateway Protocol) Default: CSE SRG Configuration Guide

32 32 Chapter 3 Creating an SRG 6 On the Summary page, confirm that the settings are correct, then click the Apply button. 7 In the confirmation dialog box, click OK to continue with the setup. 8 When the Enter Network Password dialog appears, enter the administrator User Name and Password, then click OK. An SRG Wizard Results screen appears. 9 When the results screen indicates Completed beside the title and in the Status field, exit the dialog. Errors: If the results screen indicates that errors occurred, check the error logs for an explanation (Errors and This URL fields). 10 When the wizard runs without errors, configure the system trunks and IP telephones for Local and Normal mode operations. Refer to: Chapter 4, Setting up the private VoIP network, on page 37 Chapter 5, Configuring PSTN lines, on page 63 Chapter 6, Setting up IP telephones, on page 67 Chapter 7, Setting up analog devices, on page 81. For detailed configuration information, refer to the Business Communications Manager documentation suite or to the help files connected to the Unified Manager. P

33 Chapter 3 Creating an SRG 33 Viewing and changing Main Office settings In the Unified Manager, Main Office configuration is displayed under Services//SRG//Main Office. This screen reflects the information that you entered into the first page of the SRG Wizard. You can change this information, as required. 1 Click on the SRG heading. 2 In the right frame, click on the Main Office tab. Figure 8 SRG Main Office screen SRG Configuration Guide

34 34 Chapter 3 Creating an SRG 3 Make the required changes. The table below provides information about each field on this screen. Table 6 Main office tab values Field Values Description Main Office Call Server Type Primary Network Connect Server Address Alternate Network Connector Server Address Network Connect Server Port S1000 <ip address> <ip address> This read-only field indicates type of system being used as the Main Office. This is the same IP address as for the network Gatekeeper. Refer also to Configuring the VoIP trunks (local gateway) on page 44. This is the network address for the backup network Gatekeeper, if there is one. Refer also to Configuring the VoIP trunks (local gateway) on page (default) Range: 0 to This is the port number that the SRG uses to connect to the network Gatekeeper Heartbeat Protocol Port (default) Range: 0 to This is the port that the SRG and Main Office use to periodically confirm that the WAN connection exists. VoIP trunk access code The access code for the Main Office VoIP trunk. (CDP only, if required). UDP: access code is part of BUID Use this code as part of your access code/ destination code configuration. Refer to Advanced routing: Seamless dialing across modes on page 50. Test Local Mode Timer 10 minutes Range: 2 to 10 minutes This is the period that the IP telephones which have been set in local mode by the Test Local Mode setting on the Main Office remain in local mode before returning automatically to normal mode. H.323 ID Default: SRG* Format:XXXX, where X is the case-sensitive name configured in the Gatekeeper. This is a Gatekeeper setting that identifies the SRG. *You must change this setting. This value should match the value in the Alias Names field of the Local IP gateway ( Configuring the VoIP trunks (local gateway) on page 44) P

35 Chapter 3 Creating an SRG 35 Table 6 Main office tab values (Continued) Field Values Description Numbering Plan ID Type of Number Unknown ISDN/Telephony (E.164) Private Telephony (E.163) Telex (F.69) Data (X.121) National Standard Unknown International Number National Number Special Number Subscriber Number ESN LOC (UDP) ESN CDP ESN Special Number 4 Click anywhere outside the window to activate the changes. Identifies the type of numbering plan at the Main Office. Default: Private Refer also to Configuring the Private dialing plan on page 42. This setting identifies the dialing plan the Main Office uses. Default: ESN CDP (for CDP dialing plans) (BUID = DN) UDP dialing plans: select ESN LOC (UDP) (BUID = LOC+DN) Note: Refer also to the addendum: Succession 1000/M SRG Main Office Configuration for SRG, under the section Matching Succession and SRG dialing configurations. Ensure that the SRG Private Dialing Plan is configured to match the selected value ( Configuring the Private dialing plan on page 42.) Node ID Default: 9999 This setting is automatically written to the IP telephone firmware when the IP telephone registers with the Main Office. This number is used to identify the node on the Main Office associated with the IP telephone DN. MO Access Code Length 0-34 This defines the number of digits that needs to be added to the BUID (DN) so the Main Office system can determine if the incoming call is valid. CDP dialing plans: set to 0 UDP dialing plans: set to length of line pool access code or destination code in front of LOC. SRG Configuration Guide

36 36 Chapter 3 Creating an SRG Determining SRG status Use the SRG Summary tab to view the status of the SRG. 1 Click on the SRG heading. The SRG Summary tab displays in the right frame. Figure 9 SRG Summary and Status Table 7 SRG summary tab Field Values Description Name SRG This read-only field displays SRG. Version <SRG version> This read-only field displays the current version of SRG software. Description Survivable Remote This read-only field displays the description of SRG. Gateway Status Up, Disabled, Enabled This read-only field displays the current status of the SRG process. Up: SRG is configured and active Disabled: SRG is not yet configured Enabled: SRG is configured, but not active 2 Ensure that the status reads Up before you continue with the configuration in the following chapters. P

37 Chapter 4 Setting up the private VoIP network 37 It does not matter what level of calling service you want from the SRG, you need to create a private network to the Main Office. You also need to configure the call routing features to work with the Bandwidth Management and Zone call routing dialing rules for the SRG specified at the Succession 1000/M Main Office. The level of routing configuration that you choose depends on how seamlessly you want the dialing switch from Normal to Local mode to appear for the users. The following information is included in this chapter: Bandwidth Management (Succession 1000/M interoperability) on page 39 Configurations for all levels on page 40 Setting up MCDN on page 41 Configuring the Private dialing plan on page 42 Setting up Target lines on page 42 Configuring VoIP trunking on page 43 Configuring the VoIP trunks (local gateway) on page 44 Configuring VoIP lines on page 46 Basic routing (internal calls to the Main Office) on page 48 Advanced routing: Seamless dialing across modes on page 50 This section refers specifically the following part of the process map. Refer to Process map: Configuring the SRG on page 19 for the complete process. Figure 10 Process map: Network and dialing configuration Configuring the SRG Re-enter the Unified Manager and run the SRG wizard. ( Running the SRG wizard on page 30) Configure the modules, VoIP trunks, PSTN lines, dialing plan, and routing. Dialing plan Access codes Private network data engineering VoIP and PSTN line config/ redirection, CLID/OLI display VoIP, PSTN routing Fallback scheduling (optional) Refer to BCM documentation SRG Configuration Guide

38 SUCCESSION SUCCESSION 38 Chapter 4 Setting up the private VoIP network Notes about networking This chapter assumes that the IP networking from the Main Office to the WAN and from the SRG to the WAN is set up and working (thin, solid line shown in the figure below). This includes ensuring that any network Gatekeepers are updated with the SRG information. To set up the VoIP trunk network (thick, dashed line shown in the figure below) between the Main Office and the SRG, and provide dialing access, you need the IP information you gathered under Main Office information on page 22 and SRG network information on page 24. From the SRG perspective, setting up a private network on an SRG is performed in the same way as setting up a private networks for the Business Communications Manager. This section will note any settings that may be SRG-specific. Otherwise, the Programming Operations Guide provides information about setting up lines and private networks, and the IP Telephony Configuration Guide provides detailed information about VoIP trunk setup. The Succession 1000/M Main Office controls the Gatekeeper(s) on the network. The Gatekeeper routes call signals between the two systems. Both systems and the Gatekeeper programming need to be coordinated to ensure that systems are clearly defined. Figure 11 Networking between the Main Office, the SRG, and the IP telephones. Media Gateway Server Main Office IP telephone Gatekeeper VoIP trunk IP network connections SRG LAN Signaling Server Call Server WAN LAN IP Telephone On a basic system, where the SRG is communicating with the Main Office through the VoIP network, you can set up Line pool access codes that the SRG users enter on the telephone dial pad before dialing a number at the Main Office. Refer to Basic routing (internal calls to the Main Office) on page 48) To accommodate SRG function in Normal mode, you also set up line redirection for manually-answered lines and target lines to direct all calls through a Main Office call attendant during Normal mode. In Local mode, redirected lines would terminate at a Prime telephone on the P

39 Chapter 4 Setting up the private VoIP network 39 SRG. Calls received on auto-answer lines in Normal mode are automatically call forwarded to the Main Office for call processing. If the system reverts to Local mode, this call forwarding feature is suspended and the calls arrive at the targeted telephone on the SRG. If you want more complex routing, you can set up specific destination codes based on call type. You can also set up schedules and routing that allow the calls to fallback from the VoIP network to the PSTN lines if the IP WAN link is down, or if all the VoIP network lines are busy. As well, you can set up routing so that the SRG-based analog and IP telephones can call the Main Office, or tandem out of the Main Office into the local PSTN at that location, and vice versa. Refer to Advanced routing: Seamless dialing across modes on page 50. Bandwidth Management (Succession 1000/M interoperability) This release of SRG 1.0 supports interoperation with the Succession 1000/M Network Bandwidth Management feature. This feature is used to define the codec selection policy and track bandwidth used for calls which traverse the WAN (inter zone calls) and the LAN (intra zone calls). SRG has been designed to interoperate with this feature in a manner similar to Succession Branch Office. This means that the Succession administrator sets up dialing based on a zone that is specific to the SRG. There are a couple of limitations with how the two systems use Bandwidth Management to interoperate: The functionality requires a patch on the Main Office Succession 1000/M to overcome codec negotiation issues. Please refer to release notes for patch details. A functional limitation exists in that codec selection for calls between SRG redirected IP telephones and the SRG PSTN are based on the inter zone policy, rather than the intra zone policy defined in the Succession 1000/M Main Office. Conversely, the zone table is updated based on the intra zone policy. The net result of this limitation is that calls between SRG IP telephone users and the SRG PSTN will always use a Best Bandwidth codec, but the calls will be accounted for as Best Quality. This may impact the perception of call quality in this scenario, but it will not result in early call blocking. There are no impacts to codec selection or bandwidth usage tracking for calls which require WAN bandwidth. From a configuration perspective, there are two main areas to configure, the Succession Main Office and the SRG. In the Main Office, configuration of the Bandwidth Management feature is identical to the configuration required for Bandwidth Management on a Succession Branch Office. It is important that the correct SRG Bandwidth Management patch has been installed on the Succession 1000/M to support this functionality. Main Office configuration for bandwidth management is described in detail in the Succession 1000/M Branch Office NTP. The Succession 1000/M Main Office Configuration Guide for SRG provides an overview of the steps required. In the SRG, you need to enter the Virtual Private Network ID and Zone ID that were configured by the Main Office system (Services//Telephony Services//General settings// IP trunking). This information is supplied by the Main Office Administrator as part of the SRG Configuration Guide

40 40 Chapter 4 Setting up the private VoIP network prerequisite information ( Main Office information on page 22). These two settings are entered under the IP trunking heading. Configurations for all levels The configurations in this section are required for any level of private networking over VoIP trunks. This information includes: Firewall input and output filter entries for SRG on page 40 Setting up MCDN on page 41 Configuring the Private dialing plan on page 42 Setting up Target lines on page 42 Firewall input and output filter entries for SRG You need to ensure that all the IP signals and voice paths are allowed through the firewall ports. These settings differ from those used for the Business Communications Manager. If one or more of the signals are blocked, you will experience one-way voice traffic, or no voice traffic over the VoIP trunks. Table 8 SRG firewall filters for IP telephones and trunks Filter value Normal mode IP telephones Local mode IP telephones VoIP gateway UniSTIM rtp/rtcp Input filters Source IP Main office TPS ALL Source Port 4100, 5100, 7300 ALL Destination IP IP address range for Normal mode IP telephones behind the firewall IP address range for Local mode IP telephones behind the firewall SRG VoIP gateway IP Destination Port P

41 Chapter 4 Setting up the private VoIP network 41 Table 8 SRG firewall filters for IP telephones and trunks (Continued) Filter value Normal mode IP telephones Local mode IP telephones VoIP gateway UniSTIM rtp/rtcp Output filters Source IP IP address range for Normal mode IP telephones behind the firewall IP address range for Local mode IP telephones behind the firewall SRG VoIP gateway IP Source Port Destination IP Main office TPS ALL Destination Port 4100, 5100, 7300 ALL Firewall information is set up under the Policy Management heading, which is located under Services. If you are not familiar with setting up firewall filters on the SRG, refer to the Programming Operations Guide chapter about Configuring IP Firewall Filters. Setting up MCDN MCDN is automatically activated when the system is converted to SRG. However, there is one network setting that you must set to ensure that redirected IP telephones can transfer calls to the SRG local telephones. On the navigation tree, under Services//Telephony Services//General Settings// NetworkServices//MCDN, set TAT to Y. Note that TRO will automatically revert to N. SRG Configuration Guide

42 42 Chapter 4 Setting up the private VoIP network Configuring the Private dialing plan Any level of private networking requires that the dialing plans between the systems are compatible. Private dialing plan configuration is described in detail in the Programming Operations Guide. Dialing plans are configured under System//Telephony System//General settings//dialing plan. From an SRG perspective, you can configure either a CDP (recommended) or UDP dialing plan. The Main Office will determine which type of plan is required. CDP requires the least dialing manipulation between systems. Dialing plan type is noted under Main Office information on page 22. Refer also to the Matching Succession and SRG dialing configurations appendix in the Succession 1000/M Main Office Configuration Guide for SRG. This document can be found on the SRG documentation CD. The type of dialing plan you use also determines whether the DN number on the SRG matches the assigned TN (BUID) on the Main Office, or whether you need to manipulate the routing programming to accommodate any changes during call routing to the Main Office. Setting up Target lines Target lines are internal pathways between the incoming trunks and individual telephones. To ensure that calls dialed through the VoIP network or over PRI lines reach the correct telephone, enter Target lines for each telephone in the system. Target lines are configured under Services//Telephony Services//Lines//Target lines//line ( ) The information you need to enter or change in target lines configuration includes: Line XXX//Trunk/line data//received number: In the Private number and Public number fields, enter the DN for the telephone where you want the target line to terminate. Calls coming into the system over the VoIP trunk will use the Private number (usually the same as the DN) to determine a target line destination. If the call comes over the PSTN lines, the Public number determines the target line destination. P

43 Chapter 4 Setting up the private VoIP network 43 Configuring VoIP trunking When the SRG is operating in Normal mode, all calls are forwarded to the Succession Main Office over voice over IP (VoIP) trunks. Local calls are then deflected back over the VoIP trunks to the SRG. There are 60 available VoIP lines on an SRG system. You may not choose to use all of them, or you split them into more than one line pool. For a basic system, you would put all the VoIP lines in one line pool. Ensure that you define a remote access package for each VoIP line. The system views all calls coming into the system through the VoIP trunks as remote access calls, even though the VoIP pathway is a dedicated trunk to another closed system. Refer to the information under the following headings: Configuring the VoIP trunks (local gateway) on page 44 Configuring VoIP lines on page 46 Assigning Remote Access Packages to VoIP lines on page 47 Reference: IP Telephony Configuration Guide and Programming Operations Guide. SRG Configuration Guide

44 44 Chapter 4 Setting up the private VoIP network Configuring the VoIP trunks (local gateway) Under Services//IP Telephony//IP Trunks, the H.323 Trunks heading provides two tabs. The information under the Local Gateway IP Interface tab is set when you run the SRG wizard ( Running the SRG wizard on page 30), but you can change it through this table. 1 On the Local Gateway IP Interface dialog, ensure that: All systems: Fallback to Circuit-Switched is set to Enabled if you want to use the fallback facility to switch from VoIP trunks to the PSTN lines. For a system that will not use destination codes, set this field to Disabled. Call Signaling is set to GatekeeperRouted. The Gatekeeper IP addresses beside Gatekeeper IP and Backup Gatekeeper(s) should be the same as the IP addresses for the Primary and Secondary Network Call Server settings on the Main Office screen. Refer to Viewing and changing Main Office settings on page 33. SRG Gatekeeper aliases (Alias Names field) should be the same value as the H323 ID value that you entered on the Main Office screen. Refer to Viewing and changing Main Office settings on page 33. Set Gateway Protocol to CSE Reference: IP Telephony Configuration Guide under Setting up the local gateway. P

45 Chapter 4 Setting up the private VoIP network 45 2 On the Media Parameters dialog, adjust the settings to match the requirements of the Main Office network requirements. Note: Payload size: The Payload Size fields must match the payload size required by the Main Office configuration. The default settings for SRG (30 ms for all codecs) are set for Business Communications Manager compatibility. Coordinate the settings on this screen with the Main Office network requirements. Reference: IP Telephony Configuration Guide under Configuring Media Parameters. SRG Configuration Guide

46 46 Chapter 4 Setting up the private VoIP network Configuring VoIP lines You need to configure the VoIP lines into line pools. VoIP lines are configured under Services//Telephony Services//Lines//VoIP lines//enabled VoIP lines//line ( ). Lines and line pool configuration is covered in the Programming Operations Guide. This section discusses the specific topics that need to be configured. 1 All configurations: Open each VoIP line record that you want to use, and assign the line to a line pool. Note: Do not use line pool A. Line pool A is the default line pool for public PSTN lines. Refer to Setting up PSTN lines on page 64. Assign each VoIP line ( ) to a line pool Reference: Programming Operations Guide under Configuring Lines. 2 Restriction filters (for outbound calls) are handled the same way as they are in the Business Communications Manager. Refer to the Programming Operations Guide for details. P

47 Chapter 4 Setting up the private VoIP network 47 Assigning Remote Access Packages to VoIP lines If you want to allow tandem dialing from the Main Office through the SRG PSTN (public lines) or want the redirected SRG IP telephones to use the SRG local PSTN, you need to specify a remote package that allows access to the PSTN line pool. This remote package is then assigned to each VoIP line used in the line pool between the Main Office and the SRG. 1 Set up a remote package with the PSTN line pool. (Services//Telephony Services// General settings//remote access packages//package 01//Line pool access) Note: Remote access package 01 defaults to Pool A, so if you used that for the PSTN lines, you do not need to perform this step. Otherwise, click on a package number and add the PSTN line pool. A 2 Assign the package to each VoIP line. (Services//Telephony Services//Lines//Enabled VoIP lines//line XXX//General) SRG Configuration Guide

48 48 Chapter 4 Setting up the private VoIP network Routing between systems How you choose to set up routing will be determined by the level of complexity you want to configure in terms of how the users will need to dial. If you want to use basic routing, you can use line pool access codes that route calls through the VoIP trunk and to the PSTN. Refer to Basic routing (internal calls to the Main Office) on page 48. If you want more consistency in how the users dial numbers, you need to set up more complex routing, using destination codes and fall back scheduling. Refer to Advanced routing: Seamless dialing across modes on page 50. The appendix, Matching Succession and SRG dialing configurations, in the Succession 1000/ M Main Office Configuration Guide for SRG (SRG documentation CD) provides specific examples, based on type of dialing code, about how calls route between systems. If you are using a CDP dialing plan, ensure that the access code or destination code to the Main Office contains the VoIP trunk access code that you specified on the Main Office screen. Refer to Viewing and changing Main Office settings on page 33. Ensure that you coordinate with the Main Office administrator when setting up access codes or destination codes to provide the user with as simple a dialing scheme as possible. When the SRG connects to a Succession 1000/M Main Office, Bandwidth Management and zone configuration for the SRG on the Main Office system dictate how calls route between the system. Refer to Bandwidth Management (Succession 1000/M interoperability) on page 39. Basic routing (internal calls to the Main Office) If consistent dialing in both modes is not an issue, you can create basic call routing using line pool access codes. These codes are set under Services//Telephony Services//General Settings//Access codes//line pool codes. 1 Put PSTN lines into Pool A. In the Line pool access codes table, Pool A defaults to the line access code 9. Refer to Configuring PSTN lines on page 63. If you want to use a different number, change the line pool access code for the PSTN line pool to a number that is not already assigned to another access code. Note: If you have PRI or BRI lines, you need to use routing and destination codes. Refer to the next section for details about this configuration. Put PSTN lines into a line pool P

49 Chapter 4 Setting up the private VoIP network 49 2 Assign the line pool access code to the PSTN line pool. Assign a Line pool access code to line pool To make a call through the PSTN to a telephone on the Main Office or in the public system, dial 9 and then the complete dial string for the target telephone. 3 VoIP trunks need to be configured to a line pool ( Configuring VoIP lines on page 46). This pool can then be assigned with a Line pool access code. If the dialing plan is set to CDP, this access code is the same as the first digit of the DN range of the Main Office. If the dialing plan is set to UPD, this access code needs to include the network code and the LOC code. For example: 6403, 6 being the network code for the VoIP trunk, and 403 being the location code for the UDP dialing plan. When the SRG is running in Normal mode, callers would use the VoIP line pool code plus the telephone number to reach someone at the Main Office. When the system is running in Local mode, callers would use the PSTN line pool code plus the entire dial string to reach someone at the Main Office. Refer to the following chapter, Configuring PSTN lines on page 63 for details about setting up PSTN line. When the system is running in Normal mode, callers use the VoIP line pool access code to dial telephones in the Main Office. SRG Configuration Guide

50 50 Chapter 4 Setting up the private VoIP network Advanced routing: Seamless dialing across modes You use routes and destination codes instead of line pool access codes if you want: to provide an SRG environment where user dialing has the least disruption between Normal and Local modes to allow outgoing calls to fall back to the PSTN line if the VoIP link fails to allow tandem dialing from the Main Office through the SRG local PSTN to use PRI or BRI lines for PSTN lines On a Succession Branch Office (SBO), the DNs for the Main Office telephones system are marked off by the vacant number routing feature. SRG does not support Vacant Number Routing (VNR). SRG uses Call Forward All Calls to emulate VNR for the SRG IP telephones that are in Normal mode. When the telephones switch to Local mode, Call Forward All Calls is cancelled for those telephones. A single destination code and route (or a group of destination codes and routes) can be set up on SRG to route all the calls that are not terminated locally by the SRG. These calls will be routed via the VOIP trunks. In case of VoIP trunks being unavailable, the calls can be routed to the proper location using PSTN fallback. This would be similar to the VNR feature in SBO. Seamless dialing requires that the start digit of the DNs for each system are unique (coordinated). If the start digit is the same on both systems, the local users on the SRG need to dial a separate destination code before the Main Office DN. This section includes an overview of fallback and least-cost routing ( Switching from VoIP trunk to PSTN (fallback) ), and the process for creating this type of routing ( Configuring outgoing routing and destination codes on page 52). The Business Communications Manager Programming Operations Guide provides more detailed information about routes and destination codes. Gatekeeper routing The Gatekeeper routes the calls based on an internal numbering table. Ensure that Gatekeeper administrator for the network has a list of the numbers that identify the SRG and the SRG PSTN. Example: If the system is running with a CDP dialing plan and the SRG DN range is from 3000 to 3199, the Gatekeeper needs to be able to route calls starting with 30 and 31 to the SRG. Likewise, if the PSTN to which the SRG connects has a location code of 521, the Gatekeeper must have a record of this code in the SRG list so that Main Office calls to the SRG PSTN can be routed correctly. Succession 1000/M Main Office zone configuration for the SRG allows the Main Office to define specific routing parameters for calls to and from the SRG that allow the user experience to be consistent across the network. For instance, both a Main Office user and a SRG IP telephone (in Normal mode) user can dial 1-XXX-XXX-XXXX to make a long distance call. The Main Office P

51 Chapter 4 Setting up the private VoIP network 51 uses zone configuration to set up SRG configuration in a separate zone from the Main Office dialing. This means that the Main Office system can differentiate between the calls and send the Main Office call through the Main Office PSTN, while the SRG call can be rerouted to exit through the SRG PSTN. Switching from VoIP trunk to PSTN (fallback) Once the lines and line pools have been configured, you can establish routes and destination codes that allow the users to dial the Main Office extensions through the VoIP trunks and through the PSTN lines in both Normal mode and Local mode without changing the way they dial. As part of this setup, you establish a schedule so that the calls can default to a second route (PSTN lines) when the WAN link is down. There are two ways that this type of routing can be accomplished. Refer to the local gateway section under Configuring the VoIP trunks (local gateway) on page 44 for setting the enable/ disable the fallback feature. You enable fallback on the local gateway record, so that when the VoIP trunk is not available, or the Main Office or Gatekeeper are not available, the call will fall back to a designated PSTN line pool. This process is explained in detail in the IP Telephony Configuration Guide. You can set up least-cost routing. When the VoIP trunk is unavailable, the system uses a second route (a PSTN line) to route the call. Least-cost routing is explained in detail in the Programming Operations Guide. There are a number of settings that are common to both types of routing. Refer the next section for programming highlights. SRG Configuration Guide

52 52 Chapter 4 Setting up the private VoIP network Configuring outgoing routing and destination codes 1 Change a schedule name (optional) For either method, you need to specify a schedule for SRG. To make it easier to remember, you can change a schedule name to SRG. Schedule names are configured under Services// Telephony Services//Scheduled Services//Common settings//schedule names. You can choose any schedule on the list and change the name. In the figure below, Schedule 4 was chosen, and the name was changed to SRG. Reference: Programming Operations Guide, under Changing schedule names. 2 Change the schedule time You need to change the schedule to run all day. Schedule times are set under Services//Telephony Services//Scheduled Services//Common settings//schedule times//<monday to Sunday>//Schedules//<schedule name> When you select the schedule you want to use, you can change the Start Time and Stop Time. To have the schedule run all day, enter the same time for both settings. Do this for the same schedule under each weekday heading. P

53 Chapter 4 Setting up the private VoIP network 53 Reference: Programming Operations Guide, under Changing schedule times. 3 Adjust the routing service. To ensure that the correct routing service runs, you need to make sure that it runs automatically. This setting is configured under Services//Telephony Services//Scheduled services//routing service//<schedule name>. On the schedule screen, ensure that Service setting is set to Auto. Reference: Programming Operations Guide, under Routing service. 4 Define the PSTN and VoIP routes for MO calling. You need to create routes for the line pools you created, so they can be assigned to a destination code that allows users to dial the least amount of numbers for Main Office locals over either the VoIP trunks or PSTN trunks. Routes are configured under Services//Telephony Services//Call routing//routes. To add a route, click on the Routes heading and then click on the Add button, located at the top of the navigation tree. The Add routes dialog allows you to specify a line pool to associate with the route. SRG Configuration Guide

54 54 Chapter 4 Setting up the private VoIP network VoIP route: Beside the Use Pool heading, choose a line pool that contains the VoIP trunks. Ensure that DN type is set to Private. The system sees VoIP trunks as a private network connection to the Main Office system. VoIP Route PSTN route: Beside External # enter the PSTN number to dial to access the Main Office. Beside the Use Pool heading, choose the line pool that contains the PSTN lines. Set the DN type to Public. PSTN (public) Route Note: In this example, the offices have a five-digit DN plan. Hence this number entered here includes the PSTN long distance number, the area code, and the first two digits of the local code, which ends in the first number of the system DNs 5 Define a destination code to access the routes. P

55 Chapter 4 Setting up the private VoIP network 55 You now need to define a destination code that can be used in both Normal and Local mode so that the user does not experience any changes in dialing practices to the Main Office. Destination codes are configured under Services//Telephony Services//Call routing// Destination codes. a Add a destination code: If you click on the Destination Codes heading, the Add button at the top of the navigation tree becomes active. If you click this button, a dialog box appears that allows you to specify a destination code. In this example, the 7 is also the destination digit (remote system VoIP access code) for the VoIP trunk. The A represents any number from 0 to 9 because the terminal numbers on the Main Office range from 7000 to Together, they create the access code for the routes assigned to this destination code record. Reference: Programming Operations Guide under Configuring call routing. b Assigning routes to a destination code: Once you define the destination code, you need to define the routes to the destination code schedule. You add routes to destination codes under Services//Telephony Services//Call routing//destination codes//<xx>schedules//<schedule name> Least-cost routing: When you click on the schedule name, you are prompted to define up to three routes and how much of the destination code needs to be absorbed before the system dials out the number. Since you want the telephones to use the VoIP trunks in most circumstances, you define that route as the First Route. You add the PSTN route number to the Second Route. Note: If the Main Office is a local number, the dial-out would reflect that. SRG Configuration Guide

56 56 Chapter 4 Setting up the private VoIP network Fallback routing: Fallback routing uses both the Normal and the SRG schedules. Specify only the first route in the SRG schedule. The PSTN line pool is assigned to the Normal route. The VoIP line pool is assigned to the SRG schedule. Both routes want to maintain the destination code as part of the dialed out digits. In least-cost routing, if the first route is not available, the system reverts to the second route and dials out <external number>+<dn dialed by user, including destination code>. In fallback routing, if the VoIP line is not available, the system falls back to the Normal schedule, which has the PSTN route, and dials out <external number>+<dn dialed by user, including destination code>. P

57 Chapter 4 Setting up the private VoIP network 57 Figure 12 Destination code schedules for fallback routing Figure 13 How the destination codes and fallback routing work SRG user dials MO local number Call goes to VoIP line Destination code 7* (77) No VoIP trunk available. Call goes to PSTN line Destination code 7* (77) System adds dialout digits: System dialout (77)243 System dialout: (77)243 Main office (received # = five digits) MO local user receives the call SRG Configuration Guide

58 58 Chapter 4 Setting up the private VoIP network Configuring destination codes to the SRG PSTN There are three types of calls that need to be configured for access to the SRG PSTN: calls from local SRG telephones or IP telephones in Local mode. calls that the Main Office chooses to redirect to the SRG PSTN on SRG IP telephones that are registered with the Main Office. calls from Main Office telephones through the SRG VoIP to the SRG PSTN. To allow SRG telephones to dial out over the PSTN and to allow Main Office telephones to tandem out through the local SRG PSTN, you need to define a destination code that just accesses line pool B without a dial-out code. Frequently, this is 9, but does not have to be. SRG IP telephones that are registered on a Succession 1000/M Main Office, on the other hand, have special routing requirements due to Bandwidth Management and Zone configuration on the Main Office. The following configuration shows a basic PSTN routing setup. 1 Add new route. 2 Assign PSTN line pool. Note: Ensure that the lines in this line pool have been assigned the correct remote access package. The system views calls from the Main Office as remote access calls. Refer to Assigning Remote Access Packages to VoIP lines on page 47. P

59 Chapter 4 Setting up the private VoIP network 59 3 Add the destination code to access the local PSTN: this is the code the users on local SRG and on Main Office telephones will dial to access a local PSTN. If this code only goes to the SRG PSTN, enter 9A, where A is a wild card allowing any numbers not used by other 9-based destination codes. Note: In Succession 1000/M Main Office programming this would be the offnet dialing code that the Gatekeeper would recognize as being routed to the SRG. Programming note: The default line pool access code for pool A is 9. Delete this before you attempt to create a destination code with 9. (Services//Telephony Services//General settings//access codes//line pool codes//pool A). this is the code that will be forwarded from the Main Office for SRG IP telephone calls (in Normal mode) to the SRG PSTN. Note: PSTN calls from SRG IP telephones registered on the Main Office have additional coding added by the Main Office zone-based digit manipulation that allows the Main Office to differentiate between local PSTN calls made from Main Office telephones (to the Main Office PSTN) and PSTN calls made from SRG IP telephones registered to the Main Office (to the SRG PSTN). The Main Office administrator for the Succession 1000/M system supplies this ZDP (Zone Digit Prefix) with the prerequisite information. Refer to Main Office information on page 22. In this example, the ZDP is 910. Wild card note: Note that after destination code 910 is added, the destination code 9A wild card for 1 is tagged as unavailable. SRG Configuration Guide

60 60 Chapter 4 Setting up the private VoIP network c Assign the Normal and SRG scheduled route for the two destination codes: Note: You may need to add other routes and destination codes, depending on what types of calls and over which lines you want to route calls. For instance, if you have more than one line pool because of different restriction settings, you will need to determine routing and destination codes for each line pool. Programming note: The Main Office may have special calling codes (National, Local, Special) that require additional destination code refinement. You also would need to set up access codes for these settings. The specifics for special call routing is described in the Programming Operations Guide under Outgoing calls in the section Using the MCDN access codes (tandem calls). P

61 Chapter 4 Setting up the private VoIP network 61 Figure 14 How local and tandem routing to the SRG PSTN works MO user dials local number at SRG location SRG IP telephone in Normal mode dials local number at SRG location MO recognizes that 9 is the off net access code. Routes call to Gatekeeper. MO recognizes that call as coming from an SRG IP telephone, and adds ZDP code (910) so that the call routes to the SRG. System routes call to Gatekeeper System dialout System dialout Gatekeeper recognizes dial string as call to SRG SRG user dials local number SRG recognizes leading digits (9X and 91) as destination codes to the route for the local PSTN System dialout Local telephone: PSTN SRG Configuration Guide

62 62 Chapter 4 Setting up the private VoIP network P

63 Chapter 5 Configuring PSTN lines 63 When the system is in local mode, or if you want to set up tandem dialing from the Main Office through the Survivable Remote Gateway (SRG) local PSTN, you need to have one or more PSTN trunks configured on the system. The following information is included in this chapter: Configuring the Public dialing plan on page 63 Setting up PSTN lines on page 64 Local mode line configuration on page 66 The simplest configuration would be a system with an analog trunk module and an analog station module. When a digital station module is required, each line must have an analog terminal adaptor (ATA) connected between the module and the analog device. The PSTN lines should have been wired and connected when the system hardware was installed. At this point, they appear under the Services//Telephony Services//Lines//Active lines heading, or in the case of a BRI module, under Services//Telephony Services//Loops//Active loops. If you do not plan to use fallback for your VoIP trunks, or any special call routing, then the system can be set up to route PSTN calls with a line pool access code. Analog lines default to line pool A, which, in turn, has a default line pool access code of 9. Note: PRI lines default to line pool PRI-A. However, to use these lines, you must set up routes and destination codes, which are explained in detail in Advanced routing: Seamless dialing across modes on page 50. Configuring the Public dialing plan The Public dialing plan is described in the Programming Operations Guide. Dialing plans are configured under System//Telephony System//General settings//dialing plan. The Public dialing plan defines which dialing strings will be recognized by the system as needing to be passed to the local PSTN. This record defines the leading digits and the number of digits that the system needs to look at. For example, if a caller in the system dials a string of numbers that contain an external PSTN number (<PSTN dest./access code>01-xxxxx-xxx-xxx-xxxx). After the route is determined, and, in this example, the destination/access code is dropped, the system recognizes the leading digits as a public call type that requires 17 digits. It checks to see if there are 17 digits in the string, and that there are no restrictions to bar the call. If the number meets these checks, the system sends the dial string through the designated route to the public network. Tandem calls: Calls from the Main Office to the SRG PSTN lines over the VoIP trunk are considered, by the SRG, to be remote call-ins. Because of this, the Remote Access Package for the VoIP trunks determine if calls from the Main Office can use the SRG PSTN lines. Refer to SRG Configuration Guide

64 64 Chapter 5 Configuring PSTN lines Assigning Remote Access Packages to VoIP lines on page 47 for information about setting up Remote Access Packages to allow Main Office telephones to use the SRG PSTN. Setting up PSTN lines The PSTN lines for the local service need to be individually configured to reflect the requirements for local service. Reference: Programming Operations Guide, Configuring lines and Configuring BRI loops. Lines are configured under Services//Telephony Services//Lines//Physical lines//enabled physical lines//line XXX//Trunk/Line Data. If no lines appear under the Enabled physical lines heading, ensure that the PSTN cable is connected correctly to the trunk media bay module. If it is, go back and check the media bay module record in the Unified Manager to ensure that the module is being acknowledged by the system. Loops (for a BRI module) are configured under Services//Telephony Services//Loops// LoopXXX. When the loops are provisioned (under the Resources//Media Bay Modules heading), they are assigned to line numbers, which are configured under Services//Telephony Services//Lines//Physical lines//enabled physical lines//line XXX//Trunk/Line Data. 1 Put each active line into a line pool (usually line pool A). Programming note: Line pool A defaults to line pool access code 9, which is the usual default PSTN access code. 2 If the line is a manual-answer line, in the Redirect to field, enter the line pool access code and the dial string for the Main Office attendant telephone. Refer to the figure below. Note: If the line is an auto-answer line in Normal mode, incoming calls are automatically call forwarded to the Main Office. When the SRG IP telephones revert to Local mode, the system discontinues call forward all calls and calls are delivered directly to the SRG IP telephones which are reregistered with the SRG. P

65 Chapter 5 Configuring PSTN lines 65 This is the PSTN line pool Manual-answered lines can be redirected to the MO attendant 3 Configure local PSTN routing: Basic routing: Refer to Basic routing (internal calls to the Main Office) on page 48. Advanced routing: Refer to Switching from VoIP trunk to PSTN (fallback) on page 51. Put PSTN lines into a line pool Assign Line pool access code to line pool SRG Configuration Guide

66 66 Chapter 5 Configuring PSTN lines Enhanced routing: If you want to allow a smoother transition by making the dialing seamless whether the telephones are in Normal or Local mode, you need to define routes and destination codes that accommodate the extra digits. Also, if you want to allow calls from the Main Office to tandem through the SRG during Normal mode, and out to the SRG public system, you need to set up the appropriate routes and destination codes to allow all call types to transfer correctly. Refer to Advanced routing: Seamless dialing across modes on page 50 and the Business Communications Manager Programming Operations Guide for details about call routing. If you are using routing and destination codes, you need to delete the entry under the Line pool codes heading for Line pool A. Local mode line configuration In Local mode, the SRG telephones can only access the Main Office through PSTN lines. As well, all calls coming in on the local lines terminate at a telephone on the SRG. If the system has a basic configuration which uses line pool access codes instead of routing, to access the PSTN route, the user enters the PSTN line pool access code and then dials the entire dial string for the target Main Office telephone. If you configured more advanced routing and destination codes, you could configure the system so that the user dials the same dial string for a telephone on the Main Office system in either Normal or Local modes. In this case, the system adds the additional digits that are required to dial through the PSTN network. Refer to Advanced routing: Seamless dialing across modes on page 50. P

67 Chapter 6 Setting up IP telephones 67 IP telephone setup is described in detail in the IP Telephony Configuration Guide. This chapter briefly covers the process and notes any settings that are different from the default settings or which are specifically required for SRG configuration to allow the telephones to register with the Main Office server. There are four parts to IP telephone configuration for SRG: setting up the DN records for each IP telephone ( Setting up telephone records ) setting the IP terminals record to accept registration ( Setting up the IP telephone for registration on page 71) configuring the telephones on-site ( Configuring and registering IP telephones on-site on page 73) assigning the Main Office telephony information to the IP terminal, and triggering the telephone to redirect to the Main Office ( Adding Main Office parameters to redirect IP telephones on page 75) Setting up telephone records Survivable remote gateway (SRG) supports IP telephones (i2004, i2002, i2050 Software Phone), the Symbol NetVision IP wireless handsets, ISDN devices, and analog telephones and devices such as fax machines. However, only the IP telephones can be redirected to the Main Office. The Main Office administrator supplies a list of terminal numbers for the SRG, which are hard-coded to specific models of IP telephones. Ensure that you set up DN records that match these records, or the IP telephone will not register properly with the Main Office. Adding DN records with a wizard You can use the Add User Wizard to set up the DN records that have the same settings. Within the Add User Wizard, you can choose the SRG-specific Add Users Template to set the defaults for the IP telephone DNs. You can also choose to use the Add Users Template Wizard to create a new template, and then select that template when you run the Add Users Wizard. Refer to the Programming Operations Guide, under Configuring DNs using the Wizards for details about using these wizards, and for a description of the information they contain. Note that some fields on the wizard are not available to IP telephones because these features are not available to the telephones when they are in Local mode. Leave these headings set to the default. The system will ignore them. However, analog telephones do have access to the SRG features, so ensure that these fields are set correctly for those records. Voice Mail: CallPilot is disabled for SRG since network uses the Main Office voice mail system for centralized voice mail, so ignore these settings in the wizard. The Main Office sets up this SRG Configuration Guide

68 68 Chapter 6 Setting up IP telephones service for the redirected telephones at the Main Office. On the IP telephone DN records, set up the public call number for the centralized voice mail on the voice mail access button so that users still have access to the voice mail system in Local mode. Refer to step 5 in the next section, Adding DN records individually. Local SRG telephones can be set up for centralized voice mail as remote users. Refer to the System setup for satellite systems in the Programming Operations Guide, System setup for satellite systems in the Configuring Centralized voice mail chapter. Adding DN records individually You also can set up each DN record individually. Use the following sections as a guide to the type of information that may need to change from the default settings. Refer to the Programming Operations Guide under Configuring DNs for system devices for detailed programming directions. Under an appropriate DN number, set the following. 1 DN XXX//General: Beside Model, choose the appropriate IP telephone that has been assigned this DN (i2004/2050, i2002, IPWls) Note: The device port will change when the telephone registers to the system. WARNING: The model is hardcoded on the head office system, so ensure that the model you choose is the same as the one corresponding to this DN record on the Main Office MOTN/ BUID list. 2 DN XXX//Line access: SRG programming defaults to 1 intercom key. To support outgoing caller ID over the VoIP trunk, Private OLI must be set to the DN number. Note: This number may be automatically populated by the system. If you want to support outgoing number display over the PSTN, enter the public access number for the telephone in the Public OLI field. P

69 Chapter 6 Setting up IP telephones 69 3 DNXXX//Line access//line assignment: If you want to assign specific PSTN lines to each telephone, add the line here. You might do this if you want one user to field all customer calls while the system is in Local mode. This is also where you assign the target line to the telephone. Refer to Setting up Target lines on page 42. a To add a line, click on Line assignment. The Add button becomes active. Click the Add button to display the Add Line assignment dialog. Enter the line number you want to assign to the telephone and click on Save. b Define how the telephone perceives the line, click on the Line XXX. Ensure that Appearance type is set to Ring only since there are no line appearances available on the telephones in local mode. Ring Only SRG Configuration Guide

70 70 Chapter 6 Setting up IP telephones c DNXXX//Line access//line pool access: Assign both the PSTN and VoIP trunk line pools to all the telephones that you want to be active in both Normal and Local modes. To add a line pool, click on Line pool access. The Add button becomes active. Click on the Add button to display the Add line pool access dialog. Enter the line pool letter and click on Save. 4 DNXXX//Capabilities//Call Forward all calls: You do not need to enter a value into this field. The SRG automatically call forwards all calls to this telephone when the system is in Normal mode. When the telephone is in Normal mode, use this screen to check that calls are being forwarded to the correct destination number. When the telephone is in Local mode, call forward all calls is automatically discontinued. Programming note: Call Forward all calls does not require Allow redirect to be enabled. 5 DNXXX//User preferences//button programming: Program the voice mail access button with the PSTN dialup for the Main Office voice message system. i2002: button 06 i2004/i2050: button 08 i2002 P

71 Chapter 6 Setting up IP telephones 71 i2004/i2050 Advanced programming: Refer to the Programming Operations Guide under Defining restriction filters for details about setting up restriction filters and entering filters into DN records. Setting up the IP telephone for registration Once you define the DNs you require for the IP telephones, you can set up the system to register the telephones and determine the default code and jitter buffer settings. Programming note: Skip this section if you set Registration to On when you ran the Quick Start Wizard. IP telephones are configured under Services//IP Telephony//IP Terminals//Nortel IP Terminals. Under the General tab, ensure that the following is set: Registration to ON (SRG default) Password field is cleared, unless you want installers to enter a password when they install each telephone. Auto Assign DNs to OFF (default) Advertisement/Logo defaults to Local Mode. Change this if you want the IP telephones to display a different message to users during Local mode operation. Default Codec, Default Jitter Buffer, G.XXX Payload Size fields: Coordinate these settings with the Main Office settings. SRG Configuration Guide

72 72 Chapter 6 Setting up IP telephones P

73 Chapter 6 Setting up IP telephones 73 Configuring and registering IP telephones on-site The IP Telephony Configuration Guide under Installing IP telephones provides a detailed process for configuring network information for the IP telephones and allowing them to register to the system. Refer to the Programming Record entries you created with the information you received from the Main Office administrator (DN numbers) and the network administrator (IP addresses for the SRG and each telephone and the subnet mask for the IP telephone). You will also need the default gateway IP address. 1 The figure below shows the displays, and the values for each, that appear on the IP telephone display during initial configuration: Table 9 IP telephone configuration settings Field Value Mode DHCP 0 or 1 SET IP <ip address> DHCP = 0 NETMASK <subnet mask address> DHCP = 0 DEF GW <ip address> DHCP = 0 Manual Cfg? DHCP: 0 (Full) or 1 (Partial) DHCP = 1 S1 IP <ip address> DHCP = 0 or DHCP =1/partial S1 PORT Default: 7300* DHCP = 0 or DHCP =1/partial S1 ACTION Default: 1 DHCP = 0 or DHCP =1/partial S1 RETRY COUNT <digits between 0 and 255> DHCP = 0 or DHCP =1/partial S2 IP <ip address> DHCP = 0 or DHCP =1/partial S2 PORT Default: 7300* DHCP = 0 or DHCP =1/partial S2 ACTION Default: 1 DHCP = 0 or DHCP =1/partial S2 RETRY COUNT <digits between 0 and 255> DHCP = 0 or DHCP =1/partial VLAN 0: No VLAN 1: Manual VLAN 2: Automatically discover VLAN using DHCP DHCP = 0 or DHCP =1/partial Cfg XAS 0 or 1 DHCP = 0 or DHCP =1/partial XAS IP: <ip address> DHCP = 0 or DHCP =1/partial * This is a different default than that used by BCM-based IP telephones. 2 When the telephone connects with the SRG, the display prompts for a DN. Enter the SRG DN number that you assigned to the telephone. 3 When the telephone display shows the Local Mode display, the telephone is correctly registered to the SRG. 4 When the telephones have successfully registered with the SRG, perform basic call testing to ensure that the configuration works as expected. Check registration status: SRG//IP Terminal Status tab. Refer to Notes to the user: SRG in local mode on page 91 and test the local mode features: SRG Configuration Guide

74 74 Chapter 6 Setting up IP telephones Make and receive calls. Check button features (transfer, redial). Check connection to voice mail. Programming note: When the telephone is redirected to the Main Office to go into Normal mode, the telephone must supply a Node ID as well as the MO TN to be recognized by the Main Office. The Node ID, which was entered on the Main Office screen ( Viewing and changing Main Office settings on page 33), and the MO TN, which is entered on the IP Terminal Status tab screen ( Adding Main Office parameters to redirect IP telephones on page 75), are automatically written to the telephone address during this process. The IP telephone does not require a Node ID to register with the SRG. IMPORTANT NOTE: When you have finished registering the IP telephones, remember to turn the Registration field to OFF on the Nortel IP Terminals//General tab screen. Where to look for the DN record of a registered telephone Once the telephone is registered to the SRG system, the DN record appears under the Services//Telephony Services//System DNs//Active set DNs heading. The registered IP telephones DN also appears under Services//Telephony Services//System DNs/ /DN Registration//IP set DNs reg d. Under this heading you can check to see if a given IP telephone is Active or Inactive. Registered NetVision handsets appear under Services//Telephony Services//System DNs//DN Registration//IP wireless DNsreg d. Under this heading you can check to see if a given handset is Active or Inactive. P

75 Chapter 6 Setting up IP telephones 75 Adding Main Office parameters to redirect IP telephones Once the telephone registers to the SRG, enter the parameters that identify it to the Main Office. Each telephone that gets redirected to the Main Office must have a record already configured in the Main Office. Enter the identifying parameters for each telephone under the SRG//IP Terminal Status tab. Programming note: Completing the following task automatically prompts the IP telephone to attempt to redirect to the Main Office. If the IP telephone cannot connect properly to the Main Office, check the Status field for error messages. You may need to manually redirect the telephone at this point. Refer to Troubleshooting on page 85 for information about status messages and how to manually redirect a telephone to the Main Office. Defining the BUID and MOTN 1 On the IP Terminal Status tab, highlight the telephone record that you want change. 2 On the top menu, click on Configuration, then select Modify Parameter. Local Mode - non-redirected set SRG Configuration Guide

76 76 Chapter 6 Setting up IP telephones 3 Enter the pertinent information into the MOTN and BUID fields. Table 10 SRG IP terminal parameters tab Field Values Description DN Read-only. The SRG DN record assigned to the telephone. H/W ID Read-only. This address was read from the IP telephone firmware. Status Read-only. Current status of the telephone. Refer to IP terminal status messages on page 86. Note: You need to expand the field to read the entire status message. F/W Version Read-only. This information was read from the IP telephone firmware. MOTN XXX The number the Main Office uses to define this IP telephone. BUID CDP network: <DN> UDP network: <VoIP access code>+<loc>+<dn> The number that the SRG uses to identify this telephone. If possible, the SRG DN and the BUID should be the same* (based on the BUID expected by the Main Office), to minimize confusion about which IP telephone is configured to which Main Office setting. *With a CDP network, this may not be possible, in which case, keep the trailing digits the same to minimize user confusion. Example: if the BUID is 32432, assign the telephone to X2432. MO TPS Read-only This field displays the Main Office IP address where the IP telephone is redirected when the system is in Normal mode. 4 Click the Save button at the bottom of the dialog. The terminal attempts to redirect to the Main Office. Check the Status field to ensure that the terminal registered correctly with the Main Office. If the redirection was unsuccessful, check your settings. If the telephone continues to fail to redirect, contact the SRG administrator and troubleshoot the Main Office settings for the telephone ( Troubleshooting on page 85). Testing in Local mode Once a telephone is converted to Normal mode, to test it in Local mode, the user can signal the Main Office to redirect the telephone back to the SRG. Press the button on an IP telephone, and choose TEST in local mode. The telephone re-registers with the SRG in Test mode. To exit Test in local mode, wait for the feature to time out or, before timeout, press the key with the Exit button ( ), which is only active when the telephone is manually put into Test in Local mode in this manner. P

77 Chapter 6 Setting up IP telephones 77 Advanced programming The programming in this section is optional to a basic system setup, but which might enhance how the IP telephones operate in local mode. Configuring telephone feature settings Feature settings (Services//Telephony Services//General settings//feature settings) determine how all telephones in a system work in relation to specific features. IP telephones in Local mode will not have access to most of these features. Features that affect the IP telephones in local mode include: Background music: if it is provided for on-hold On hold: determines if a caller on hold hears tones, music, or nothing. Note: This feature should be coordinated with what the Main Office application offers while a caller is on hold so that the caller experiences the same context, regardless of the system mode. The Installation Guide provides a section about installing a local music source. The Programming Operations Guide provides details about setting up IP music files for on hold operations. Receiver volume: set to use the system volume, since IP users cannot use the feature code to set a default telephone volume. *Delayed ring transfer: If a transfer to an external number is not answered, you can indicate if the call will be dropped (Off) or transferred to the designated Prime telephone. Held line reminder: if set to a time, determines period between when a call is put on hold and when a short tone sounds at the telephone to indicate the call is still on hold Alarm set: enter a DN to a two-line analog telephone, since the IP telephones will not be able to access the alarms, or set to None if you do not want to use an alarm set on the system. Can affect IP telephones in local mode SRG Configuration Guide

78 78 Chapter 6 Setting up IP telephones * In conjunction with the Delayed ring transfer setting, check the Transfer Callback Timer (Services//Telephony Services//General settings//timers). This setting defaults to After 4 rings. If you are using the Delayed ring transfer feature, turn this feature to Off if you want all unanswered transferred calls to ring at the Prime set, which is usually the system attendant. If you want the transferred call to ring at the telephone from which it was transferred first, set this field to any setting less than what you set for the Delayed ring transfer feature. Set to less than the setting in Delayed ring transfer (Feature settings) Setting user preferences Under User preferences (DNXXX//User preferences), if you have the information from the Main Office administrator, set the Language and Contrast settings to match the Main Office settings to ensure that the telephone displays in the same way in both modes of operation. Match to Main Office settings P

79 Chapter 6 Setting up IP telephones 79 Other system programming Programming for the following settings is not discussed in this book, as there are no differences from Business Communications Manager programming if you choose to use these features. Programming for these features is discussed in detail in the Programming Operations Guide. Any settings not on this list, or in the rest of this document, do not apply to the SRG environment. Restriction filters (Services//Telephony Services//Restriction filters, and assigned under Lines and DN record programming) COS passwords (Services//Telephony Services//General settings//cos passwords) SRG Configuration Guide

80 80 Chapter 6 Setting up IP telephones P

81 Chapter 7 Setting up analog devices 81 On the Survivable Remote Gateway (SRG), analog, ISDN telephones and devices and NetVision wireless handsets always function as local telephones to the SRG. They can use the VoIP trunk to the Main Office using access codes or destination codes, if the VoIP trunk line pool is assigned to the device, but the Main Office does not have any settings or administration for these devices. For a basic setup, use the default DN settings. This means that the analog devices are plugged into sockets that are wired to the station module(s) and allowed to boot up with the default DN settings. If a digital station module (DSM) is installed, an analog terminal adaptor (ATA) sits between the media bay module wiring and the wiring to the telephone location. If you perform no extra configuration, the telephones will have internal access to each other, and will default to line pool A (PSTN line pool) accessed with line pool access code 9. Analog telephones do not have a Feature key. Instead, they use a Link (*) key to access system features. Therefore, these telephones have greater feature access on the SRG than the IP telephones in Local mode, if you leave the analog telephone records at the default settings. If you do not want different feature access on the analog telephones, turn these settings off as you program the telephone. This section provides key points to analog telephone configuration. For programming details refer to the Programming Operations Guide. Analog telephone records are configured in the same way as they are for Business Communications Manager applications. You can use the Add Users Wizard or the individual DN screens. Refer to the Programming Operations Guide under Configuring DNs using the wizards or Configuring DNs for system devices. The information under the following headings explains settings that may have specific impacts for SRG analog telephones. 1 DN XXX//General: Model appears as Other. SRG Configuration Guide

82 82 Chapter 7 Setting up analog devices The DN General screen is detailed in the Programming Operations Guide under Identifying the telephone (General heading). 2 DN XXX//Line access: The Private OLI defaults to the telephone DN number. Do not change this number. If you want to support outgoing number display over the PSTN, enter the public access number for the telephone in the Public OLI field. DN line access configuration is detailed in the Programming Operations Guide under Configuring line access. 3 DNXXX//Line access//line assignment If you want to assign specific PSTN lines to each telephone, add the line(s) here. You might do this if you want one user to field all customer calls while the system is in Local mode. This is also where you assign the target line to the telephone. Refer to Setting up Target lines on page 42. P

83 Chapter 7 Setting up analog devices 83 Ensure that Appearance type for the line is set to Ring only since there are no line appearances on analog telephones. If the line is a target line or an analog line that allows CLID, and you want the telephone to display this information, set Caller ID set to Y. Note: The screen shown is for a target line or an analog line with CLID capability. Screens for other types of lines do not show the Caller ID set field. 4 DNXXX//Line access//line pool access: Assign both the PSTN and VoIP trunk line pools to all the telephones that you want to be able to make calls over the PSTN or to the Main Office over the VoIP trunk. Note: If you want the analog telephones to emulate local mode call functionality, assign only the PSTN line pool to the analog devices. If you used the default settings for the PSTN lines, they default to line pool A, which is the default assigned line pool for these telephones. 5 DNXXX//Capabilities: Click on the Capabilities heading to see the Capabilities dialog. Set Handsfree to None. Set HF Answerback to N. Set Paging to N. Set Allow Redirect to Y if you want the user to be able to call forward to the Main Office or redirect lines to the Main Office. SRG Configuration Guide

84 84 Chapter 7 Setting up analog devices The Programming Operations Guide describes each heading on this screen in Defining device capabilities. 6 DNXXX//Capabilities//ATA settings: This only appears for analog telephones and for devices connected through ATA devices. Analog telephone configuration is provided in the Programming Operations Guide under Determining ATA settings. P

85 Chapter 8 Troubleshooting 85 This section provides details about messages and errors that can occur during SRG configuration and IP terminal registration. Refer to IP terminal status messages. There is also a section about other activities that can cause the IP telephones to fall back into Local mode. Refer to Troubleshooting fallback to Local mode on page 88 and Manually redirecting IP telephones on page 89. If you have a problem accessing the Wizard buttons, refer to Error when accessing the wizard button page on page 89 For maintenance information refer to the Business Communications Manager Management User Guide, which discusses the maintenance tools found in the Unified Manager, the backup and restore utility (BRU), and event and error logging. Initial configuration troubleshooting Here are a few possible issues you may encounter when you first configure an IP telephone to the SRG, including a description of what may cause them, and how to troubleshoot the issue. Table 11 IP telephone troubleshooting Problem Telephone does not connect to system Slow connection between the handset and the Business Communications Manager Change the contrast level Block individual IP sets from dialing outside the system. Suggested solution or cause If an IP telephone does not display the text Connecting to server within two minutes after power up, the telephone was unable to establish communications with the SRG. Double check the IP configuration of the telephone, and the IP connectivity to the SRG (cables, hubs, etc.). If the connection between the IP client and the SRG is slow (ISDN, dialup modem), change the preferred CODEC for the telephone from G.711 to G.729. When an IP telephone is connected for the first time, the contrast level is set to the default setting of 1. Most users find this value is too low. Therefore, after the telephone is installed, use FEATURE *9 and use the UP or DOWN key to adjust the contrast. If you want to block one or more IP telephones from calling outside the system, use Restriction filters and assign them to the telephones you want to block. Restriction filters are set up under Services//Telephony Services//Restriction filters. SRG Configuration Guide

86 86 Chapter 8 Troubleshooting Table 11 IP telephone troubleshooting (Continued) Problem Suggested solution or cause One-way or no speech paths Signaling between the IP telephones and the SRG uses port Voice packets are exchanged using the default RTP: Source port (output filters)/destination port (input filters): through for the VoIP gateway. Output filter Destination IP is set to ALL. Input filter Destination IP is the IP address of the SRG local gateway. Source port (output filters)/destination port (input filters): for the IP telephones. Output Destination IP is set to ALL. Input filter Destination IPs are the IP range for all IP telephones (behind the firewall) in Normal mode. Source port (output filters)/destination port (input filters): for the local mode IP sets. Destination port (output filter) and Source Port (input filter) are set to ALL. Output Destination IP is set to ALL. Input filter Destination IPs are the IP range for all IP telephones (behind the firewall) in Local mode. UniSTIM signals use specific source and destination ports: Output filters: Source port, 5000; Destination port, 4100, 5100, Output filter Destination IP is the IP address of the Main Office TPS. Input filters: Source port, 4100, 5100, 7300; Destination port, 5000.Input filter Destination IPs are the IP range for all IP telephones (behind the firewall) in Normal mode. If these ports are blocked by the firewall or NAT, you will experience one-way or no-way speech paths. Firewall note: If the firewall filter is set to Pass Outgoing and Block Incoming Except IP Phones, this only allows IP telephony registration traffic through, but blocks all other traffic, including H.323 calls on this interface. You must still specify an H.323 rule to allow IP call voice traffic. IP terminal status messages The following table lists the status messages that could be displayed in Unified Manager (Services//SRG//IP Terminals Status tab) for the IP telephones when they connect or attempt to connect to the Main Office. Refer to Adding Main Office parameters to redirect IP telephones on page 75. Periodic retries may result in the same condition being detected over and over again. In these cases the SRG state machine will use flags to indicate that a given event has been logged. Table 12 Registered IP telephone status messages Status Event Log Severity Comment Net Connect Server Unreachable Yes Error Indicates connectivity problem MO TPS Unreachable Yes Error Indicates connectivity problem P

87 Chapter 8 Troubleshooting 87 Table 12 Registered IP telephone status messages (Continued) Status Event Log Severity Comment Invalid ID (1) No endpoint in Gatekeeper database Invalid ID (2) ID unknown within the Call Server Invalid ID (3) - Endpoint in Gatekeeper database is Originating Call Server Main Office Parameters not Provisioned Yes Warning Indicates configuration problem Yes Warning Indicates configuration problem Yes Warning Indicates configuration problem Yes Warning Indicates configuration problem Test Local Mode Yes Information Test feature Firmware is Out of Sync with the Main Office Call Server Firmware Upgrade in Progress Yes Information Normal Mode Redirected to Yes Information Main Office Redirection Pending (Set on call) Yes Information Firmware Upgrade Pending Set Yes Information on call Yes Error Indicates that IP set FW on Main Office has been upgraded and the required FW version is not available on SRG Information Indicates that IP set FW on Main Office has been upgraded and the required FW version is available on the SRG SRG Configuration Guide

88 88 Chapter 8 Troubleshooting Troubleshooting fallback to Local mode If the system reverts to Local mode and you determine that the problem is not the WAN link to the Main Office, you can check out the possibilities discussed in this section as a possible cause. IP telephone firmware discrepancies One of the most likely causes for a non-network reversion to Local mode is that the IP telephone firmware has been updated on the Succession Main Office and not on the SRG. Check the SRG// IP Terminal Parameters dialog for this message in the Status field: Firmware is Out of Sync with the Main Office Call Server The preferred way of handling firmware upgrades is to install the patch onto the SRG first, then on the Main Office equipment. When the IP telephone firmware is updated on the Main Office, the Main Office redirects all SRG IP telephones back to the SRG for a firmware upgrade. If the SRG has already been patched with the new firmware, the telephone grabs this firmware as it registers with the SRG. Once the telephone has the new firmware, the system automatically allows the telephone to re-register with the Main Office. If the SRG has not been upgraded with the new firmware, the telephones remain in Local mode until the firmware is upgraded on the SRG and the telephones have a chance to download the update. Gatekeeper failure If an IP telephone fails to establish communication with the gatekeeper when it tries to register to the Main Office, the telephone remains registered to the SRG, remaining in Local mode. Troubleshoot the problem by checking the settings in the Main Office screen ( Viewing and changing Main Office settings on page 33) and the IP trunks Local Gateway and Media Parameters screens, especially the gatekeeper settings ( Configuring VoIP trunking on page 43). If you make any changes, you will need to manually attempt to redirect the telephones. Refer to Manually redirecting IP telephones. P

89 Chapter 8 Troubleshooting 89 Manually redirecting IP telephones If you make programming changes to the Main Office configuration screen, you may need to manually redirect each telephone back to the Main Office. You perform this process using a menu item under Services//SRG//IP Terminal Status. 1 Click on the telephone listing that you want to convert to Normal mode. 2 Either alternate-click on the listing, or choose Configuration and select Register with Main Office. 3 Click Save on the confirmation box. The telephone re-registers with the Main Office. 4 Click on the Status tab to view the Status field. If Status displays Up, the conversion was successful. If the IP terminal does not register correctly with the Main Office, refer back to the IP Terminal Status tab, Status field and review the message to determine where the problem occurred. Refer to IP terminal status messages on page 86. If the conversion occurred correctly, perform basic telephony tests to ensure that the telephones are working as expected: Make and receive calls. Check feature access. Check voice mail access Refer to the feature guides for the Main Office application for specific information about making calls and using features. Error when accessing the wizard button page If you receive an error when you try to access the wizard button page from the first page of the Unified Manager, restart the NSACD service, and then stop and start the Voic and VBMain Services on the SRG. For detailed information about these services, refer to the Business Communications Manager Management User Guide. SRG Configuration Guide

90 90 Chapter 8 Troubleshooting P

91 Notes to the user: SRG in local mode 91 There are no user cards supplied with the Survivable Remote Gateway (SRG). Familiarize your users with the local mode features presented in this section. Normal mode features are described in the user cards for the Main Office application. When the IP telephones are in Local mode, they reflect the features based on the SRG software. Refer to the diagrams under IP telephones, which show the default display settings for the three IP telephones in Local mode. This chapter also provides a quick reference list to accessing SRG features from an analog telephone ( ATA extension features on page 94). IP telephones In Local mode, the IP telephones have an extremely restricted feature set to minimize the confusion between the feature characteristics of the SRG and the Main Office application. Users must use the PSTN lines to dial the Main Office or to the public system. All calls coming in on the PSTN lines will be processed through the SRG. If routing and destination codes are set up as suggested in Advanced routing: Seamless dialing across modes on page 50, the users would use the same dialing sequence as in Normal mode to dial the Main Office. If the system is set up with a basic configuration, the users enter an access code and then dial the entire dial string for the Main Office telephone. In the following figures, each available Local mode feature is labeled for each model of IP telephone. i2050 Software Phone in Local Mode on page 92 i2004 in Local mode on page 93 i2002 in Local mode on page 93 SRG Configuration Guide

92 92 Notes to the user: SRG in local mode i2050 Software Phone in Local Mode Exit key: only active if MO set to Test in local mode Programmable label Not active Intercom/Line Autodials voice mail through PSTN Activate Test in local mode P

93 Notes to the user: SRG in local mode 93 i2004 in Local mode Not active Transfer Lastnum 345 Aug 6 9:43 am Local Mode Intercom/Line Programmable label Activate Test in Local mode Exit key: only active if set to Test in local mode Autodials voice mail through PSTN i2002 in Local mode Transfer Lastnum 345 Aug 6 9:43 am Local mode Intercom/Line Programmable label Exit key: only active if MO set to Test in local mode Autodials voice mail through PSTN Activate Test in Local mode SRG Configuration Guide