Implementing the Avaya B5800 Branch Gateway Release 6.
© 2011 Avaya Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information in this document is complete and accurate at the time of printing, Avaya assumes no liability for any errors. Avaya reserves the right to make changes and corrections to the information in this document without the obligation to notify any person or organization of such changes.
The trademarks, logos and service marks (“Marks”) displayed in this site, the Documentation and Product(s) provided by Avaya are the registered or unregistered Marks of Avaya, its affiliates, or other third parties. Users are not permitted to use such Marks without prior written consent from Avaya or such third party which may own the Mark.
Implementing the Avaya B5800 Branch Gateway Comments? infodev@avaya.
Contents Chapter 1: Overview........................................................................................................... 13 Branch user deployment models.............................................................................................................. 13 Centralized solution................................................................................................................................... 14 PSTN trunking configurations...............................................
Adding music-on-hold files............................................................................................................... 52 9600 series phones screen saver file............................................................................................... 53 Base and trunk card installation................................................................................................................ 53 Trunk daughter card preparation.........................................................
Disabling the Network Management administration feature for the branch.............................................. 103 Disabling unused trunks............................................................................................................................ 104 Digital trunk clock source.......................................................................................................................... 105 Setting a trunk clock quality setting.................................................
Creating locations............................................................................................................................. 156 Creating adaptations........................................................................................................................ 157 Creating SIP entities......................................................................................................................... 157 Creating entity links...................................................
B5800 Branch Gateway SAL-based alarming.......................................................................................... 217 Universal Install/SAL Registration Request Form..................................................................................... 218 Chapter 13: Additional installation and system procedures.......................................... 219 System shutdown..........................................................................................................................
Viewing the card contents......................................................................................................................... 260 About backing up the System SD card..................................................................................................... 260 Backing up the primary folder using Manager.................................................................................. 260 Backing up the primary folder using the System Status application.........................
Routing concepts...................................................................................................................................... 287 Call flows................................................................................................................................................... 287 Sunny day................................................................................................................................................. 289 Rainy day...........................
Implementing the Avaya B5800 Branch Gateway November 2011
Chapter 1: Overview The Avaya B5800 Branch Gateway is a single-platform solution with multiple deployment options that enable seamless, user-centric access to Avaya Aura® Messaging, Avaya Aura® Conferencing, Avaya Aura® Presence services and much more. It's complimentary to any existing networking solution, adding communications and collaboration functionality in a “thin” device designed for branch use.
Overview Branch user model at the same time. The extensions supported in the Centralized Branch user model are SIP extensions only. Centralized solution The B5800 Branch Gateway can be deployed as a Distributed branch, a Centralized branch, or a Mixed branch. Both Distributed and Centralized branches can benefit from centralization. In Distributed branch deployments, the option to leverage centralized PSTN trunking and centralized applications such as voice mail and conferencing is provided.
Voicemail support options it can be configured to make and receive external calls via the central Avaya Aura®Session Manager. A combination of these methods can be used for PSTN calls based on the call type (local, national, international), time of day or even individual user. See Branch PSTN call routing examples on page 325 for more information. Voicemail support options B5800 Branch Gateway supports a range of options for voicemail services to the branch's native users.
Overview Note: If you are going to use Network Management for centralized management of the B5800 Branch Gateway system, Network Management (NM) 6.0, NM 6.0 SP2, plus an additional B5800 Branch Gateway patch hosted on the Avaya support web site must be installed and configured. For more information about Network Management, see the Avaya Integrated Management 6.0 Network Management Configuration guide which is available on the Avaya support web site.
Licensing • Additional E1 Channels license • 120-day trial license B5800 Branch Gateway uses the Avaya Product Licensing and Delivery System (PLDS) to manage license entitlements. See Chapter 11: Managing license files with PLDS for more information. The B5800 Branch Gateway licenses are described below. Avaya Branch Gateway System Software license This license is required for operation of the B5800 Branch Gateway system.
Overview provide the SIP connections between Avaya Aura®Session Manager and B5800 Branch Gateway. Additional channels licenses The PRI Universal (PRI-U) trunk card can be used in the B5800 Branch Gateway system. The PRI-U ports can be configured to support E1, E1R2, or T1 line types. Each port supports 8 B channels which do not require a license. Additional B channels beyond these 8 require a license.
System components right. They can be used in any order; however, if the capacity for a particular type of card is exceeded, the card in the right-most slot will be disabled. • SD card — The B5800 Branch Gateway SD card is a uniquely numbered dongle used to validate license keys entered into the B5800 Branch Gateway system configuration to enable features. It also provides embedded voicemail support and storage for system software files. The card fits into a slot in the rear of the control unit.
Overview • Trunk daughter cards — Most base cards can be fitted with a trunk daughter card to support the connection of trunks to the base card. The following trunk daughter cards are supported: • Analog trunk card — This card allows the base card to support 4 analog loop-start trunks. The analog phone ports do not include a ringing capacitor. Where this is a requirement, connection should be via a Master socket containing ringing capacitors.
Supported telephones • Power supplies — The control unit has an internal power supply unit. Each external expansion module is supplied with an external power supply unit. Additional power supply units may also be required for IP phones and some phone add-ons. • Power cords — Depending on the locale, different power cords need to be ordered for each control unit, external expansion module, and any phones or devices using external power supply units.
Overview Telephone Native extensions Survivable extensions 1 BM32 (DSS) 2402D 2410D 2420 3641 wireless 3645 wireless 3720 DECT R4 3725 DECT R4 4602IP 4602SW 4610IP 4610SW 4621 4625 5402 5410 5420 1 EU24 (DSS) 5601 5602IP 5602SW 5610IP 5610SW 5620 5621 22 EU24BL (DSS) 1 9620L 2 3 9620C 2 3 9630G 2 3 9640 2 3 9640G 2 3 Implementing the Avaya B5800 Branch Gateway Comments? infodev@avaya.
Software applications Telephone Native extensions Survivable extensions 9650 2 3 9650C 2 3 SMM24 1 9608 4 9611G 4 9621G 4 9641G 4 1 BM12 Avaya 1010/1020/1030/1040 video conferencing units Standards-compliant 3rdparty SIP audio and video endpoints 1 When connected to their respective telephones 2 With H.323 firmware 3 With SIP 2.6 firmware 4 With SIP 6.0 firmware Software applications The B5800 Branch Gateway software applications are provided on DVDs.
Overview • SoftConsole: is intended for telephone system operators or receptionists. It displays details of calls and allows them to quickly see the status of the callers required destination and transfer the call. The SoftConsole user is able to access a range of details about the status of users and groups on the B5800 Branch Gateway system. Up to 4 simultaneous SoftConsole users can be configured. This application does not require a license.
Supported country locales Locale Language Telep Phone Applications hony Display Manager Soft Console Voicemail Embedded Voicemai Voicemail l Pro Australia UK English Belgium Dutch Belgium French Brazil Brazilian Canada Canadian French Chile Latin Spanish China Mandarin Colombia Latin Spanish Denmark Danish - Finland Suomi - France French Germany German Greece Greek - - - - Hong Kong Cantones e - - - - Hungary Hungaria n - - - - Iceland Icelandic - - - -
Overview Locale Language Telep Phone Applications hony Display Manager Soft Console Peru Latin Spanish Poland Polish Voicemail Embedded Voicemai Voicemail l Pro - • Locale: The country represented by the locale. • Language: The voicemail prompt language used for that locale. • Telephony: The B5800 Branch Gateway provides default telephony settings matching the normal expected defaults for the locale.
Web sites Details of courses can be found on the Avaya University web site (http://www.avayalearning.com). The site can be used to check course availability and to book courses. It also includes on-line courses and on-line course assessments. The site requires users to setup a user name and password in order to track their personal training record. For a list of recommended courses available for the B5800 Branch Gateway, see Recommended courses for Avaya B5800 Branch Gateway training on page 335.
Overview Documents you may need to consult are as follows: • Administering Avaya Aura® Session Manager, document number 03-603324 • Avaya Integrated Management Release 6.0 Network Management Configuration • Avaya Integrated Management Release 6.0 Network Management Installation and Upgrade • Avaya Integrated Management Release 6.0 Network Management Console User Guide • IP Office Manager, document number 15-601011 • IP Office Release 6.
Chapter 2: Planning Before you begin installing and configuring the B5800 Branch Gateway system, you should already have determined the implementation issues listed in the table below. You have determined... The branch user model you are deploying. See Branch user deployment models on page 13 The dial plan you are configuring for the Dial plan considerations on page 30 system and each branch. The B5800 Branch Gateway licenses required for this installation.
Planning Dial plan considerations A uniform dial plan greatly simplifies configuration, management and phone calls within the network branch sites. For example, if each branch has similar roles such as reception, manager and warehouse - using the same extension number for each role and a unique prefix for each branch allows calls between sites with little need for directory lookups. It also means a standard configuration can be used at branches; simplifying installation, user training and maintenance.
Voicemail considerations • 6-digit survivable extension numbers of which the first 3 digits are equal to the branch prefix e.g. 811250. • Dial 9 prefix for outgoing PSTN calls. • National and international calls allowed but routed via the headquarters site's PSTN trunks. • Where a national call matches a branch location, it should be routed to the PSTN via that branch. • Local calls allowed from each branch using its own PSTN trunks.
Planning central voicemail system, at each branch you have the option to still use the local Embedded Voicemail for auto attendant operation and for announcements to waiting calls. See Configuring Modular Messaging on page 164 for more information. Note that for this configuration, Embedded Voicemail licenses are required. For more information about licensing, see Licensing on page 16. Branch PSTN call routing considerations Each B5800 Branch Gateway system can support its own external PSTN trunks.
B5800 Branch Gateway configuration methods The Network Management offer is a suite of software applications that enable centralized management of the B5800 Branch Gateway system. It provides a single access interface to manage multiple branch locations. The suite of applications include: • Avaya Network Management Console — allows you to view the devices in the network. • Manager — allows you to view and edit individual branches in the B5800 Branch Gateway system.
Planning Network assessment for VoIP requirements B5800 Branch Gateway is a converged telephony system, that is it combines aspects of traditional PABX telephone systems and IP data and telephony systems. This works at various levels. • Individual phone users can control the operation of their phone through applications running on their PC. • Data traffic can be routed from the LAN interface to a telephony trunk interface, for example a dial-up ISP connection.
Chapter 3: Installation requirements This chapter provides information about power supplies, cables, grounding and environmental and space requirements for installing the B5800 Branch Gateway control unit and external expansion modules. The B5800 Branch Gateway control unit can be mounted on the wall if no external expansion units are included in the installation.
Installation requirements Typical B5800 Branch Gateway System VA B5800 Branch Gateway system 230 Individual Equipment VA Analog 16 module 88 Digital Station 16 module 34 Digital Station 30 module 42 WAN3 module 17 So8 module 34 The 1151D2 power supply unit for Avaya H.323 IP phones includes a backup battery. This typically provides 15 minutes backup at maximum load (20 Watts) and up to 8 hours at light load (2 Watts).
Cables systems using punch-block connectors. This type of installation should be performed by an experienced wiring technician. • Trunk connections — The majority of B5800 Branch Gateway trunk ports use RJ45 connectors for acceptance of an RJ45-to-RJ45 cable. However, connection at the line provider's end may require use of a different plug type in order to match the line providers equipment. • RJ11 phone connectors — Many phones use RJ11 sockets and are supplied with RJ11to-RJ11 cables.
Installation requirements Grounding Use of ground connections reduces the likelihood of problems in most telephony and data systems. This is especially important in buildings where multiple items of equipment are interconnected using long cable runs, for example phone and data networks. All control units and external expansion modules must be connected to a functional ground.
Voice compression channels Call type Voice compression channel usage IP device to non-IP device These calls require a voice compression channel for the duration of the call. If no channel is available, busy indication is returned to the caller.
Installation requirements Measuring channel usage The B5800 Branch Gateway System Status Application can be used to display voice compression channel usage. Within the Resources section it displays the number of channels in use. It also displays how often there have been insufficient channels available and the last time such an event occurred. For the VCM cards, the level of channel usage is also indicated by the LEDs (1 to 8) on the front of the VCM card.
Environmental requirements Environmental requirements The planned location must meet the following requirements. If being installed into a rack system, these are requirements for within the rack: • Temperature: 0°C to 40°C / 32°F to 104°F. • Humidity: 10% to 95% non-condensing. • Check there are no flammable materials in the area. • Check there is no possibility of flooding. • Check that no other machinery or equipment needs to be moved first. • Check that it is not an excessively dusty atmosphere.
Installation requirements Note: See Important safety instructions when using your telephone equipment on page 275 for basic safety precautions to follow when using your telephone equipment. Space requirements The B5800 Branch Gateway control unit and external expansion modules are designed to be installed either in a free-standing stack or into a 19-inch rack system. Rack installation requires a rack mounting kit for each control unit and expansion module.
Space requirements External expansion modules The dimensions below are applicable to all external expansion modules.
Installation requirements Wall mounting space requirements The control unit can be wall mounted if not using any external expansion modules. A wall mounting kit is required in addition to 4.5mm fixings suitable for the wall type. A clearance of 500mm around the control unit is required. See Wall mounting on page 59 for more information. Rack space requirements The B5800 Branch Gateway control unit and external expansion modules can be rack mounted into standard 19-inch rack systems.
Space requirements Rack module positioning The integral expansion ports on a control unit are located on the rear of the unit. An additional 4 expansion ports can be added to the front of the control unit by installing a 4-port expansion card. • Each external expansion module is supplied with a blue 1 meter (3'3'') expansion interconnect cable. This cable must be used when connecting to expansion ports on the rear of a control unit.
Installation requirements 46 Implementing the Avaya B5800 Branch Gateway Comments? infodev@avaya.
Chapter 4: Hardware and software installation All hardware components should be turned off while they are installed and connected. Once the installation is complete, the system is turned on. The control unit will then upgrade all of the connected components, including phones, to the appropriate level of firmware. In addition, when the system is turned on, it should not be connected to the customer's data network.
Hardware and software installation # Description Section 8 Connect the external expansion modules. See External expansion modules on page 63. 9 Connect the control unit and external expansion modules to a functional ground. See Grounding on page 65. 10 Install the B5800 Branch Gateway See Installing the administration administration applications on the applications on page 72. installer PC. 11 Connect the PC to the control unit. See Installer PC connection on page 73.
Unpacking equipment • RJ45-RJ45 ethernet LAN cable • M4 cross-head screwdriver • Tools suitable for crimping a cable spade • If wall mounting, drills and tools for wall mounting fixtures • Additional parts required In addition to orderable system equipment, the following items are required. • 14AWG solid copper wire for ground connection of control units and expansion modules • Cable sleeve matching local regulator requirements for ground wires.
Hardware and software installation 4. Ensure that anti-static protection measures areobserved Ensure that anti-static protection measures are observed at all times when handling equipment with exposed electrical circuit boards. 5. Check all parts Visually inspect each item and check that all the necessary documentation and accessory items have been included. Report any errors or omissions to the dealer who supplied the equipment. 6.
SD card preparation If the card contains any dynamic system files, for example SMDR records, they are temporarily backed up by Manager and then restored after the card is recreated. Procedure 1. Insert the SD card into a card reader on the Manager PC. Note: Do not remove the SD card. Removing the SD card will interrupt the upgrade. 2. Using Manager, select File > Advanced > Recreate IP Office SD Card. 3. Select Avaya Branch Gateway. 4. Browse to the card location and click OK.
Hardware and software installation Note: For information about CSV files, see the Help available in the Manager application. From Manager, select Help > Contents. In the Manager Help window, in the left navigation pane, expand IP Office Configuration Mode and then expand Editing Configuration Settings. Then click Importing and Exporting Settings. 6. When completed, select File > Save Configuration As.
Base and trunk card installation Property Value Audio Format PCM Length Up to 90 seconds. Procedure 1. Rename the music file holdmusic.wav. 2. Using a card reader, copy the file into the /system/primary folder on the System SD memory card. 3. If the B5800 Branch Gateway system is configured for additional music-on-hold files (up to 3 additional files), copy those files to the same location. The name of the additional files must match those specified in the B5800 Branch Gateway system configuration.
Hardware and software installation Warning: • Correct anti-static protection steps should be taken before handling circuit boards. • Cards must never be added or removed from the control unit while it has power connected. Trunk daughter card preparation Trunk daughter cards can be fitted to any base card except the legacy card carrier. For combination cards, the trunk daughter card is pre-installed and cannot be changed.
Base and trunk card installation Parts and equipment required • Base card (except the legacy card carrier) • Trunk daughter card • 3 stand-off pillars (these are supplied with the trunk daughter card) Tools required • 5mm Flat-blade screwdriver • Anti-static wrist strap and ground point Installing a trunk daughter card Procedure 1. Check that correct cards have been supplied. 2. Ensure that you are wearing an anti-static wrist strap connected to a suitable ground point. 3.
Hardware and software installation • PRI T1 • PRI 30 E1R2 RJ45 • VCM 4 • Dual PRI T1 • Dual PRI E1R2 RJ45 • VCM 8 • PRI 30 E1 (1.4) • BRI-8 (UNI) • VCM 16 • Dual PRI E1 • ANLG 4 UNI (US only) • VCM 24 • VCM 30 Warning: Correct anti-static protection steps should be taken while handling circuit boards. Parts and equipment required • Legacy carrier card • VCM card 56 Implementing the Avaya B5800 Branch Gateway Comments? infodev@avaya.
Base and trunk card installation • 2 plastic stand-off pillars per card • Trunk cards are supplied with a replacement blanking plate which is not required. Tools required • 5mm Flat-blade screwdriver • Anti-static wrist strap and ground point Installing a legacy carrier card Procedure 1. Check that correct cards have been supplied. 2. Ensure that you are wearing an anti-static wrist strap connected to a suitable ground point. 3.
Hardware and software installation Warning: • Correct anti-static protection steps should be taken before handling circuit boards. • Cards must never be added or removed from the control unit while it has power connected. • Tools required • 5mm Flat-blade screwdriver • Anti-static wrist strap and ground point Installing a base card Procedure 1. Check that there is no power to the control unit. 2.
Wall mounting 5. At this point apply pressure at the base of the front of the card to complete insertion. 6. Using a flat-bladed screwdriver secure the card. Wall mounting B5800 Branch Gateway control units can be wall mounted. This requires a wall mounting kit plus additional 4.5mm fixtures and fittings suitable for the wall type. The wall mounting kit includes two brackets, one top and one bottom.
Hardware and software installation 60 Implementing the Avaya B5800 Branch Gateway Comments? infodev@avaya.
Rack mounting Rack mounting The B5800 Branch Gateway control unit and external expansion units can be rack mounted into 19-inch rack systems. This requires a rack mounting kit for each unit.
Hardware and software installation • Important: Only the screws (M3 x 6mm) provided with the mounting kit should used to attach the 62 Implementing the Avaya B5800 Branch Gateway Comments? infodev@avaya.
External expansion modules brackets to the control unit. As indicated in the diagram, the rack mounting bracket can be used in several positions on the unit. External expansion modules External expansion modules should be connected to the control unit before power is applied to the control unit. Ensure that modules are attached in the order that matches the planned or pre-built configuration. External expansion modules connect to the control unit using an expansion interconnect cable.
Hardware and software installation Parts and equipment required • External expansion module — each module is supplied with a suitable external power supply unit and a 1m blue interconnect cable. 2m yellow interconnect cables are supplied with the 4-Port expansion card and should only be used with that card.
Grounding Grounding Use of ground connections reduces the likelihood of problems in most telephony and data systems. This is especially important in buildings where multiple items of equipment are interconnected using long cable runs, for example phone and data networks. All control units and external expansion modules must be connected to a functional ground. Where the unit is connected to a power outlet using a power cord with an earth lead, the power outlet must be connected to a protective earth.
Hardware and software installation External expansion modules On expansion modules, the ground point is a 4mm screw located towards the right on the rear of the module. On some older modules, the dedicated ground point screw is not present. In those cases, the top-center cover fixing screw (3mm) can be used as an alternative ground connection point. A toothed washer should be added to ensure good contact.
Out-of-building connections/lightning protection • Cables of different types, for example trunk lines, phone extensions, ground and power connections, should be kept separate. • All cabling between buildings should be enclosed in grounded ducting. Ideally this ducting should be buried. • A Primary Protection Box must be provided at the point where the cables enter the building. This should be three point protection (tip, ring and ground).
Hardware and software installation Connection type External output switch Protection device type ITWLinx towerMAX SCL/8 (This device was previously referred to as the Avaya 146G.) Requirement Connections from an Ext O/P port to an external relay device must be via a surge protector. The towerMAX range of devices are supplied by ITWLinx (http://www.itwlinx.com).
Out-of-building connections/lightning protection Analog phone barrier boxes Where analog phone extensions are required in another building, phone barrier boxes and protective earth connections must be used . Warning: PHONE (POT) ports on the front of control units must not be used for extensions that are external to the main building. • The correct B5800 Branch Gateway barrier boxes must be used.
Hardware and software installation Main Building Barrier Box • Center screw — Connect to main building protective ground (or ground terminal of Barrier Box Rack Mounting Kit). Use 18AWG (minimum) wire with a green and yellow sleeve. Secondary Building • Center screw — Connect to main building protective ground. Use 18AWG (minimum) wire with a green and yellow sleeve. • Right-hand screw — Not used. • Right-hand screw — Connect to ground point on Phone module using ground cable supplied with barrier box.
Administration software suite 5. Using 14AWG wire with green and yellow sleeve, connect one of the earthing pillars to the buildings protective earth. 6. Using 14AWG wire with green and yellow sleeve, connect the other earthing pillar to the phone module. 7. Ensure that the following wires are not routed together in the same bundle: • Earth lead from the barrier box to the phone module. • Internal wires, e.g. wires going directly to the phone module.
Hardware and software installation progress. Details of the number of alarms are recorded and the time and date of the most recent alarms. • System Monitor The B5800 Branch Gateway System Monitor application is a tool that shows details of all activity on the B5800 Branch Gateway system. Because of the level of detail, interpretation of System Monitor traces requires a high-level of data and telephony protocol knowledge.
Installer PC connection 2. Select B5800 Branch Gateway Administration Suite. 3. Double-click on setup.exe. 4. Select the language you want to use for the installation process. This does not affect the language used by Manager when running. 5. Click Next. 6. Select who should be able to run the Administration Suite applications. 7. Click Next. 8. If required, select the destination to which the applications should be installed. It is recommended that you accept the default destination. 9. Click Next.
Hardware and software installation Connecting the PC directly to the control unit About this task The default address for a B5800 Branch Gateway control unit LAN port is 192.168.42.1/255.255.255.0. Use this procedure to change the TCP/IP properties for the LAN port on the PC and directly connect the PC to the control unit. Procedure 1. Change the TCP/IP properties of the LAN port on the PC to the following: • Fixed IP address: 192.168.42.203 • Subnet mask: 255.255.255.0 • Default gateway: 192.168.42.
Applying power to the system d) If there are no ping replies, enter ipconfig. The results should list the IP address settings of the Manager PC as required above. e) If the IP address settings of the Manager PC are displayed, enter exit and check the cable connection. Applying power to the system Procedure 1. With the power off on the control unit, insert the B5800 Branch Gateway System SD card into the System SD slot on the rear of the control unit. Ensure that you have the correct card.
Hardware and software installation • If a configuration file is already present on the System SD card, it is loaded by the B5800 Branch Gateway. If not, the B5800 Branch Gateway creates a default configuration based on the components of the system and copies that configuration onto the System SD card. You are now able to use Manager to access the B5800 Branch Gateway configuration.
Applying power to the system LED System SD CPU Description • Green on = card present • Green flashing = card in use • Orange steady = reset imminent • Red flashing = card initializing or shutting down • Red fast flashing = card full • Red steady = card failure/wrong type • Alternate red/green = starting up • Green on = okay • Red on = no software • Flashing Red = error/shutdown Base card LEDs Base Card All cards LEDs 1 to 8 Usage LED1 is used for base card status: • Red on = error • Red slow flash = in
Hardware and software installation Trunk daughter card LEDs Trunk Daughter Card All cards LEDs 9 to 12 Usage LED 9 is used for daughter card status: • Red on = error • Red slow flash = initializing • Red flash every 5 seconds = card okay • Red fast flash = system shutdown Analog trunk • Green on =card fitted • Green flashing = trunk in use BRI trunk • Off = no trunk present • Green on = trunk present • Green flashing = trunk in use PRI trunk • Off = no trunk present • Green on = trunk present • Gree
Default configuration configuration the Manager user can view and alter. Manager is also used to upgrade the system software files. Procedure 1. Select Start > Programs > IP Office > Manager. If the PC has firewall software installed, you may be prompted as to whether you want to allow this program to access the network. 2. If a prompt appears requesting permission to allow this program to access the network, select Yes or OK. 3. From the menu bar, select File > Open Configuration.
Hardware and software installation • Extensions and users — A user is automatically created for each physical extension port detected in the system. Users are assigned extension numbers starting from 201. User names take the form Extn201, Extn202, etc. • Hunt group — A single hunt group 200 called Main is created and the first 10 users are placed into that hunt group as members. • Incoming call routes — Two default incoming call routes are created. Voice calls are routed to the hunt group Main.
Changing the IP address settings Important: Once the control unit has obtained IP address and DHCP mode settings, it retains those settings even if rebooted without a configuration file present on the System SD card. To fully remove the existing IP address and DHCP mode setting the B5800 Branch Gateway must be defaulted using Manager. Changing the IP address settings About this task Use this procedure to change the system name, IP address, IP mask, or DHCP settings of the B5800 Branch Gateway system.
Hardware and software installation 12. Reboot the system. Connecting the control unit to the network About this task Once you have changed the B5800 Branch Gateway system default settings to those that match the customer requirements, you can connect the B5800 Branch Gateway control unit to the customer's network. Procedure 1. Disconnect the LAN cable from the installer PC. 2. Connect the LAN cable to the customer network. 3.
Default passwords 5. In the Security Service User Login window, enter a user name and password of an account that has security configuration access to the B5800 Branch Gateway system. The defaults are security and securitypwd. 6. In the left navigation pane, click System. 7. Click the Unsecured Interfaces tab. The password in the System Password field is used by Manager for remote software upgrade of the B5800 Branch Gateway system. The default password is password. 8.
Hardware and software installation 2. In the left navigation pane, click User. 3. In the user list, click RemoteManager. 4. On the User tab, do the following: a) In the Password field, enter a new password for the user. b) In the Confirm Password field, enter the new password again. 5. Click OK. 6. Select File > Save Configuration. Connecting phones Procedure 1. Connect the analog phones to the phone ports. 2.
96x1 phones SIP firmware download in B5800 Branch Gateway centralized branch deployments This section describes the process for 96x1 Series Phone SIP firmware download using the B5800 Branch Gateway. The procedure required to replace the H.323 version of the firmware to the SIP version is not covered here. B5800 Branch Gateway support for SIP phone firmware download This capability is made available in the B5800 Branch Gateway Release 6.1 SP2.
Hardware and software installation • SIP_CONTROLLER_LIST has to have the appropriate Avaya Aura® Session Manager IP address as a primary SIP server. • See Survivability settings on page 198 for the settings file parameters that are relevant to B5800 Branch Gateway centralized branch deployment. • HTTPSRVR IP address may have to be set to point to the B5800 Branch Gateway (if this is not what is already provided to the phone via DHCP). The SIP phone firmware load of the required version has to be obtained.
96x1 phones SIP firmware download in B5800 Branch Gateway centralized branch deployments Procedure 1. Start Manager and connect to the B5800 Branch Gateway. 2. Select File > Advanced > Embedded File Management. 3. Copy the configuration file onto the B5800 Branch Gateway SD card. About rebooting the phones The phones must be rebooted to start the firmware download from the B5800 Branch Gateway.
Hardware and software installation 4. In the list of users that is displayed, select the check box (on the left of each row) for the users to be rebooted. Note: Multiple users can be selected by checking the boxes of multiple entries on the list. For best results of the firmware download process, check multiple (up to 10) users from the list to reboot them together in one action. 5. Click the Reboot button (located next to AST Devices Notification above the list of users).
96x1 phones SIP firmware download in B5800 Branch Gateway centralized branch deployments Rebooting the phones by power cycling the phones About this task This procedure can be performed in sunny day or rainy day conditions. The phones do not need to be registered to Session Manager. Procedure To power cycle the phone, remove power to the phone, wait about one minute, then reapply power.
Hardware and software installation 90 Implementing the Avaya B5800 Branch Gateway Comments? infodev@avaya.
Chapter 5: Administration software suite The B5800 Branch Gateway administration software applications are installed on the installation PC. They are used by installers and maintainers to configure, manage, and monitor the B5800 Branch Gateway system. The B5800 Branch Gateway administration applications are: • Manager B5800 Branch Gateway Manager is used to access all parts of the B5800 Branch Gateway configuration.
Administration software suite • If Manager is also installed and is running, select File > Advanced > System Status. • Start a web browser and enter the IP address of the control unit. Then select the System Status Application link. The Logon window appears. 2. In the Logon window, enter the details of the B5800 Branch Gateway system to which you want it to connect as follows: a) In the Control Unit IP Address drop-down box, select the appropriate address, or enter the IP address of the control unit.
Starting System Monitor 3. In the Control Unit IP Address drop-down box, select the IP address of the control unit you want to monitor. 4. In the Password field, enter the appropriate password. Note: You are able to set a System Monitor password using Manager. If the B5800 Branch Gateway does not have a System Monitor password set, System Monitor uses the B5800 Branch Gateway System password.
Administration software suite 94 Implementing the Avaya B5800 Branch Gateway Comments? infodev@avaya.
Chapter 6: Initial configuration for a Centralized Branch This chapter provides initial configuration tasks required for each B5800 Branch Gateway branch deployed in the Centralized Branch user model. In the scenario where no survivable extensions are present and the same hardware is used at each branch, the branches can use the same configuration except for branch prefix and IP address.
Initial configuration for a Centralized Branch Centralized Branch configuration checklist Use this checklist to monitor your progress as you configure a B5800 Branch Gateway system deployed as Centralized Branch. # 1 Description Section Launch Network Management and start Network Management Console to discover devices in your network. See “Chapter 3: Discovering the Voice Network” in Avaya Integrated Management Release 6.0 Network Management Configuration.
Centralized Branch configuration checklist # Description Section 12 Add a second Session Manager line for redundancy. See Avaya Aura Session Manager line redundancy on page 118. 13 Set up outgoing call routing. • See Setting up outgoing call routing on page 120. • For information on routing back to the branch for fallback alternate routes, see Branch PSTN call routing examples on page 325. 14 Configure Modular Messaging as the See Voicemail operation on page 163.
Initial configuration for a Centralized Branch # Description Section 20 Create a time range. For Session Manager 6.1 or 6.0, see Creating time ranges on page 153. 21 Create a routing policy. • For Session Manager 6.1, see Creating routing policies on page 153. • For Session Manager 6.0, see Creating routing policies on page 159 22 Create a dial pattern. • For Session Manager 6.1, see Creating dial patterns on page 154. • For Session Manager 6.
Activating license files Procedure 1. See Activating license entitlements on page 209 to generate the licenses. 2. Depending upon which method you want to use to deliver the activated license files to each branch, see one of the following: • See Using Manager to deliver license files to the branches on page 99. • See Using Provisioning and Installation Manager to deliver license files to the branches on page 100.
Initial configuration for a Centralized Branch 4. Select File > Close Configuration. Using Provisioning and Installation Manager to deliver license files to the branches Before you begin License files have been activated. See Activating license entitlements on page 209. About this task Use this procedure to load the license files to Provisioning and Installation Manager (PIM) and then create a job to send the license files to the B5800 Branch Gateway branches.
Activating license files 8. Click Next. 9. On the Import Licenses Wizard page, choose one of the following: • To select a mapping file, click the Select Mapping File option button and then click Browse to locate the mapping file. Note: Mapping files are used for bulk provisioning. See Creating a mapping file on page 102 for more information. • To select a device and license file from a list, do the following: 1. Click the Select Devices from list option button. 2. Click the check box for the device. 3.
Initial configuration for a Centralized Branch a) Click the Full execution option button. b) Click the Ignore Warnings check box to deselect it so that warnings are not ignored during validation. 15. Click Next. 16. Review the summary, and then click Next. 17. Click Finish. The License Wizard closes. When the job is run, either now or on the date and time you specified, the license file(s) are pushed down to the designated devices using TFTP. 18.
Disabling the Network Management administration feature for the branch Note: The license file name is comprised of the host ID of the SD card followed by _HID.xml, for example 111306312781_HID.xml. The host ID is the Feature Key (FK) serial number printed on the SD card. 3. Repeat step 2 for each IP address/license file pair. Sample mapping file: 148.147.206.251,111306312781_HID.xml 148.147.206.160,111310198782_HID.xml 148.147.175.145,111313365847_HID.xml 4. Save the file.
Initial configuration for a Centralized Branch 9. Click OK. 10. Select File > Save Configuration. Disabling unused trunks About this task Each B5800 Branch Gateway trunk card provides a fixed number of trunk ports with digital trunk ports supporting a fixed number of digital channels. By default th B5800 Branch Gateway configuration will have settings for all the possible trunks and channels.
Digital trunk clock source Digital trunk clock source About this task Digital trunks require the telephone system at each end of the trunk to share a clock signal to ensure synchronization of call signalling. The B5800 Branch Gateway can obtain and use the clock signal from any of its digital trunks. Typically the clock signal provided by a digital trunk from the central office exchange is used as this will be the most accurate and reliable clock source.
Initial configuration for a Centralized Branch Setting a trunk clock quality setting About this task Procedure 1. Start Manager and connect to the B5800 Branch Gateway system. 2. In the left navigation pane, click Line. 3. For each digital line, do the following: a) Select the line. b) On the Line tab, select whether that trunk should provide the clock source for the network or whether the trunk is unsuitable. Note: For E1R2 trunks the Clock Quality setting is on the Advanced tab 4.
Setting the trunk prefixes Procedure 1. Start Manager and connect to the B5800 Branch Gateway system. 2. In the left navigation pane, click Line. 3. For each line enter the prefix. The location of the relevant setting varies for each trunk type. • For analog trunks, select the Line Settings tab and enter the prefix in the Prefix field. • For T1 and T1 PRI trunks, select the PRI 24 Line tab and enter the prefix in the Prefix field.
Initial configuration for a Centralized Branch • International Prefix: 900 • Country Code: 44 Number Received Processing Resulting Number +441707362200 Following rule 1 above, the + 901707362200 is replaced with the International Prefix (900), resulting in 900441707362200. The number now matches the International Prefix (900) and Country Code (44). Following rule 2 above they are replaced with the National Prefix (90).
Administering a Session Manager line for each branch • See Changing the default codec selection on page 112. Use this procedure to set the preferred order for codec negotiation. This can be done as a system default and also for each individual SIP and Avaya Aura® Session Manager line. • See Adding an Avaya Aura Session Manager line on page 114. Use this procedure to create a Session Manager line for calls to the Avaya Aura® Session Manager. • See Setting up outgoing call routing on page 120.
Initial configuration for a Centralized Branch 7. Click OK. 8. Select File > Save Configuration. The Send Configuration window appears and the Configuration Reboot Mode is set to Immediate. Do not change the reboot mode. Setting the branch prefix and local number length for extension numbering About this task Each B5800 Branch Gateway system in the network should have a unique branch number.
Administering a Session Manager line for each branch System tab field descriptions Name Range or Default Description Branch Prefix Range = 0 to 999999999 This number is used to identify the B5800 Branch Gateway system within the Avaya Aura® network. The branch prefix of each B5800 Branch Gateway system must be unique and must not overlap. For example 85, 861 and 862 are okay, but 86 and 861 overlap.
Initial configuration for a Centralized Branch Name Range or Default Description in order to check the status of line. This setting controls the frequency of the messages when the Avaya Aura®Session Manager line is currently out of service. Note that centralized extensions use their own settings. Changing the default codec selection About this task By default, all B5800 Branch Gateway IP trunks and extensions use automatic codec negotiation.
Administering a Session Manager line for each branch The Send Configuration window appears and the Configuration Reboot Mode is set to Immediate. Do not change the reboot mode. Automatic codec preference settings Setting Selected Preference 2nd Preference 3rd Preference G711 A-Law 64K 4th Preference G.729 G729(a) 8K CS- G711 U-Law ACELP 64K G723.1 6K3 MPMLQ G.723 G723.1 6K3 MP- G729(a) 8K CS- G711 U-Law MLQ ACELP 64K G.711 U-Law G711 U-Law 64K G711 A-Law 64K G729(a) 8K CS- G723.
Initial configuration for a Centralized Branch To see the Maximum SIP Trunk Sessions licensed for the system, in the left navigation pane, select PLDS License. 6. Click OK. 7. Select File > Save Configuration. Adding an Avaya Aura ® Session Manager line About this task Use this procedure to add an Avaya Aura®Session Manager line to the B5800 Branch Gateway system configuration.
Administering a Session Manager line for each branch Session Manager tab field descriptions Name Description Line Number This value is automatically assigned by B5800 Branch Gateway and should be unique for each line added to the configuration. In Service The default setting is enabled. This option can be used to manually take the Session Manager line out of service. It does not reflect or set the actual state of the line.
Initial configuration for a Centralized Branch Name Description Network Configuration These settings are fixed to TCP using send and receive ports 5060. VoIP tab field descriptions Name Range or Default Description Compression Mode Default = Automatic Select These settings are used to select the code negotiation order. • The default, Automatic Select, sets the line to use the codec order selected on the System > Telephony form.
Administering a Session Manager line for each branch Name Range or Default Description DTMF Support Default = RFC2833 This setting is used to select the method by which DTMF key presses are signaled to the remote end. The supported options are In Band, RFC2833 or Info. VoIP Silence Suppression Default = Off When selected, this option will detect periods of silence on any call over the line and will not send any data during those silent periods.
Initial configuration for a Centralized Branch Name Range or Default Description change the characteristics of the session, for example when the target of an incoming call or a transfer does not support the codec originally negotiated on the trunk. Use Offerer's Preferred Codec Default = Off Normally for SIP calls, the codec preference of the answering end is used. This option can be used to override that behavior and use the codec preferences offered by the caller.
Administering a Session Manager line for each branch The B5800 Branch Gateway system sends regular OPTION messages to both Avaya Aura® Session Manager lines in order to check their in-service or out-of-service status. If the current line in use changes to out of service and the other line is in service, the B5800 Branch Gateway will switch to using the other line. However it will not automatically switch back if the previous line returns back to in service.
Initial configuration for a Centralized Branch Setting up outgoing call routing About this task For calls from extensions on the B5800 Branch Gateway system to other numbers within the network, system short codes are used to route the calls to the Avaya Aura® Session Manager line. The Avaya Aura® Session Manager then performs the routing to determine where the call should go. Note: See Branch PSTN call routing examples on page 325 for information on routing back to the branch for fallback alternate routes.
Administering a Session Manager line for each branch Short Code tab field descriptions Name Description Code Enter the number dialed by users that should be matched to this short code. Use X wildcards for any single digit. Feature Leave this field set as Dial. Telephone Number Set this field to match a number that should be passed to the Avaya Aura®Session Manager for routing against its dialing pattern matches. The N wildcard can be used to match any wildcards in the Code.
Initial configuration for a Centralized Branch extension number. If there is no matching extension number, the call is targeted to any matching system short code. Incoming calls to a branch Incoming calls on an Avaya Aura®Session Manager line are treated as being internal calls and do not go through the B5800 Branch Gateway system's Incoming Call Route settings. • If the destination of the incoming call on the Avaya Aura® Session Manager line starts with the system's branch prefix, the prefix is removed.
Chapter 7: Initial configuration for a Distributed Branch This chapter provides initial configuration tasks required for each B5800 Branch Gateway branch deployed in the Distributed Branch user model. Distributed Branch configuration checklist Use this checklist to monitor your progress as you configure a B5800 Branch Gateway system deployed as Distributed Branch. # 1 Description Section Launch Network Management and start Network Management Console to discover devices in your network.
Initial configuration for a Distributed Branch # Description Section 8 Set the branch prefix and local number length for the extension numbering. See Setting the branch prefix and local number length for extension numbering on page 137. 9 Change the default codec selection. See Changing the default codec selection on page 139. 10 Change the maximum SIP sessions. See Changing the maximum SIP sessions on page 140. 11 Add a Session Manager line.
Activating license files # 18 Description Create an entity link. Section • For Session Manager 6.1, see Creating entity links on page 152. • For Session Manager 6.0, see Creating entity links on page 158 19 Create a time range. For Session Manager 6.1 or 6.0, see Creating time ranges on page 153. 20 Create a routing policy. • For Session Manager 6.1, see Creating routing policies on page 153. • For Session Manager 6.0, see Creating routing policies on page 159 21 Create a dial pattern.
Initial configuration for a Distributed Branch license file names are based on the Feature Key (FK) serial number on the SD cards. See Creating a mapping file on page 129 for more information. Note: B5800 Branch Gateway supports a 30-day grace period during which time the system is fully functional if a license error is detected or if a license file cannot be obtained, for example due to loss of WAN connectivity. Procedure 1. See Activating license entitlements on page 209 to generate the licenses. 2.
Activating license files Deleting the PLDS license file from the branch Procedure 1. Start Manager and connect to the B5800 Branch Gateway system. 2. In the left navigation pane, select PLDS License. 3. Right-click PLDS License and select Delete PLDS License file from Avaya Branch Gateway. 4. Select File > Close Configuration. Using Provisioning and Installation Manager to deliver license files to the branches Before you begin License files have been activated.
Initial configuration for a Distributed Branch license files, you can create a mapping file for bulk distribution. See Creating a mapping file on page 129 for more information. 6. To send the license file to the branch, from the Provisioning and Installation Manager main window, click Import Licenses at the top of the window. The Import Licenses Job Wizard appears. 7. On the General page, do the following: a) In the Job Name field, enter a name for this job.
Activating license files 1. Click the date/time icon and select the date and time you want the job to run. 2. In Time Zone drop-down box, select the appropriate time zone. • Click the I'll schedule the job later option button to schedule the job later. 13. Click Next. 14. On the Job Options page, do the following: a) Click the Full execution option button. b) Click the Ignore Warnings check box to deselect it so that warnings are not ignored during validation. 15. Click Next. 16.
Initial configuration for a Distributed Branch Procedure 1. Open a generic CSV text file. 2. Enter the B5800 Branch Gateway IP address and corresponding license file name in the following format: < IP address of the device>,< License file name >. Note: The license file name is comprised of the host ID of the SD card followed by _HID.xml, for example 111306312781_HID.xml. The host ID is the Feature Key (FK) serial number printed on the SD card. 3. Repeat step 2 for each IP address/license file pair.
Disabling unused trunks Note: When Network Management is installed, this check box is checked by default and you are not able to administer the branch through Manager. To be able to use Manager to administer the branch, this check box must be unchecked. 9. Click OK. 10. Select File > Save Configuration. Disabling unused trunks About this task Each B5800 Branch Gateway trunk card provides a fixed number of trunk ports with digital trunk ports supporting a fixed number of digital channels.
Initial configuration for a Distributed Branch 7. Select File > Save Configuration. Digital trunk clock source About this task Digital trunks require the telephone system at each end of the trunk to share a clock signal to ensure synchronization of call signalling. The B5800 Branch Gateway can obtain and use the clock signal from any of its digital trunks.
Digital trunk clock source When multiple trunks with the same setting are providing clock signals, trunks are used in the order of slots 1 to 4 and then by port on each slot. The current clock source being used by an B5800 Branch Gateway system is shown on the Resources page within the B5800 Branch Gateway System Status Application. Setting a trunk clock quality setting About this task Procedure 1. Start Manager and connect to the B5800 Branch Gateway system. 2. In the left navigation pane, click Line. 3.
Initial configuration for a Distributed Branch Setting the trunk prefixes About this task Where a prefix has been implemented for outgoing calls, that same prefix needs to be added to trunk settings. The prefix is then used as follows: • On incoming calls the prefix is added to any incoming ICLID received with the call. That allows the ICLID to be used by B5800 Branch Gateway phones and applications to make return calls.
Setting the trunk prefixes 1. If an incoming number (called or calling) starts with the + symbol, the + is replaced with the International Prefix. 2. If the Country Code has been set and an incoming number begins with that Country Code or with the International Prefix and Country Code, they are replaced with the National Prefix. 3. If the Country Code has been set and the incoming number does not start with the National Prefix or International Prefix, the International Prefix is added. 4.
Initial configuration for a Distributed Branch Administering a Session Manager line for each branch This section provides the procedures required to configure a Session Manager line between each branch site and the headquarters site. This section also describes how the B5800 Branch Gateway uses a configured Session Manager line to handle incoming and outgoing calls to and from the branch and explains how a second Session Manager line can be configured for Session Manager line redundancy.
Administering a Session Manager line for each branch Procedure 1. Start Manager and connect to the B5800 Branch Gateway system. 2. In the left navigation pane, click System. 3. Click the LAN1 or LAN2 tab as appropriate depending on which branch site LAN interface will be used for the data connection to the Avaya Aura® network. 4. Confirm that the IP address and IP Mask fields are set correctly for the site. 5. Click the VoIP tab. 6. Select the SIP Trunks Enable option.
Initial configuration for a Distributed Branch 3. Click the System tab. 4. Set the following fields as appropriate: • Branch Prefix • Local Number Length • Proactive • Reactive These 4 fields are the key settings for B5800 Branch Gateway operation. See System tab field descriptions on page 111 for more information. 5. Click OK. 6. Select File > Save Configuration. The Send Configuration window appears and the Configuration Reboot Mode is set to Immediate. Do not change the reboot mode.
Administering a Session Manager line for each branch Name Range or Default Description Length should not exceed 15 digits. Proactive Default = 60 seconds The B5800 Branch Gateway sends regular SIP OPTION messages to the Avaya Aura®Session Manager line in order to check the status of the line. This setting controls the frequency of the messages when the Avaya Aura®Session Manager line is currently in service. Note that centralized extensions use their own settings.
Initial configuration for a Distributed Branch Procedure 1. Start Manager and connect to the B5800 Branch Gateway system. 2. In the left navigation pane, click System. 3. Click the Telephony tab. 4. Click the Telephony sub-tab. 5. In the Automatic Codec Preference drop-down box, select the appropriate setting. The Automatic Codec Preference setting is used to indicate the preferred codec order for trunks and extensions that are using automatic codec negotiation.
Administering a Session Manager line for each branch operation and system capacities during the 30-day grace period that is in effect when the system is in License Error Mode because the license is not yet installed. Once the PLDS license is installed, the Maximum SIP Session setting should be changed to match what appears on the PLDS screen. This will change the License Mode setting that appears on the PLDS screen to Normal Mode. Procedure 1. Start Manager and connect to the B5800 Branch Gateway system.
Initial configuration for a Distributed Branch 5. Click OK. 6. Click the VoIP tab. 7. Click the Allow Direct Media Path check box to select this option. 8. Click the Re-Invite Supported check box to select this option. 9. Configure the remaining fields as appropriate. See VoIP tab field descriptions on page 116 for more information. 10. Click OK. 11. Select File > Save Configuration. The Send Configuration window appears and the Configuration Reboot Mode is set to Immediate. Do not change the reboot mode.
Administering a Session Manager line for each branch Name Description Inactivity timeout (seconds) The default setting is 0. Keep the default setting to maintain a persistent connection with Session Manager. Outgoing Group ID The default setting is 99999. This value is not changeable. However note the value as it is used in B5800 Branch Gateway short codes used to route calls to the Session Manager. Prefix This field is blank by default.
Initial configuration for a Distributed Branch Name Range or Default Description G711 option is used as the second choice codec. • The Advanced option can be used to manually configure the codec preference order and specify which codecs are used. 144 Call Initiation Timeout Default = 4 seconds The B5800 Branch Gateway sends regular OPTION messages to each Avaya Aura®Session Manager line in order to check the lines in or out of service status.
Administering a Session Manager line for each branch Name Range or Default Description alternately if possible within the network structure. • If enabled, connected calls can take routes other than through the B5800 Branch Gateway. This removes the need for a voice compression channel. • If disabled or not supported at one end of the call, the call is routed via the B5800 Branch Gateway.
Initial configuration for a Distributed Branch Note: See Branch PSTN call routing examples on page 325 for information on routing back to the branch for fallback alternate routes. Ideally the number of such system short codes should be kept to a minimum and the same short codes used on all branches in order to ease maintenance. This is where using a uniform dial plan for all branches helps, as explained in Dial plan considerations on page 30.
Administering a Session Manager line for each branch Short Code tab field descriptions Name Description Code Enter the number dialed by users that should be matched to this short code. Use X wildcards for any single digit. Feature Leave this field set as Dial. Telephone Number Set this field to match a number that should be passed to the Avaya Aura®Session Manager for routing against its dialing pattern matches. The N wildcard can be used to match any wildcards in the Code.
Initial configuration for a Distributed Branch extension number. If there is no matching extension number, the call is targeted to any matching system short code. Incoming calls to a branch Incoming calls on an Avaya Aura®Session Manager line are treated as being internal calls and do not go through the B5800 Branch Gateway system's Incoming Call Route settings. • If the destination of the incoming call on the Avaya Aura® Session Manager line starts with the system's branch prefix, the prefix is removed.
Chapter 8: Session Manager Configuration The Session Manager procedures in this chapter are for configuring Session Manager for the B5800 Branch Gateway. The B5800 Branch Gateway supports Session Manager 6.1 and Session Manager 6.0. Depending on the Session Manager version you are using, see one of the following sections: • Session Manager 6.1 on page 149 • Session Manager 6.
Session Manager Configuration 6. Create time ranges to control when different routing policies are used. See Creating time ranges on page 153. 7. Add a routing policy. A routing policy consists of a selected SIP entity as its destination and a number of time ranges that define when the policy can be used. See Creating routing policies on page 153. 8. Add dial patterns. Dial patterns are used to match digits received to a destination.
Session Manager 6.1 6. In the Managed Bandwidth Units field, accept the default setting. 7. In the Total Bandwidth field, accept the default setting, blank 8. In the Default Audio Bandwidth field, accept the default setting. 9. In the Location Pattern section, click Add to add a location pattern. 10. In the IP Address Pattern field, enter an IP address pattern that matches the IP LAN address range. The * character can be used as a match-all wildcard. For example, the pattern 192.168.42.
Session Manager Configuration 7. In the Notes field, enter a description to help identify this SIP entity, as appropriate. 8. In the Adaptation drop-down box, select the adaptation that contains the digit conversions to apply to calls to and from the location. 9. In the Location drop-down box, select the location that matches the location you configured in Creating locations on page 150. 10. In the Time Zone drop-down box, select the time zone for the location. 11.
Session Manager 6.1 5. In the SIP Entity 1 drop-down box, select the name of the Session Manager system that is at one end of the link. SIP Entity 1 must always be a Session Manager instance. For a Session Manager line from a B5800 Branch Gateway system, this should match the Session Manager set as the SM Address in the Session Manager line’s configuration. 6. In the Protocol drop-down box, select TCP. When TCP is selected, the Port field is automatically set as 5060.
Session Manager Configuration 4. On the Routing Policies Details page, in the Name field, enter a name to describe this routing policy. 5. For the Disabled check box, accept the default, unchecked. 6. In the Notes field, enter notes about this routing policy, as appropriate. 7. In the SIP Entity as Destination section, do the following: a. Click Select. b. On the SIP Entity List page, select the SIP entity to which the routing policy applies. c. Click Select. 8.
Session Manager 6.0 12. In the Routing Policies section, click the check box for the routing policy that was created for the branch. 13. Click Select. 14. If you need to specify that calls from certain locations be denied, do the following: a. In the Denied Originating Locations section, click Add. b. Do one of the following: • Click the Apply to All Originating Locations check box. • Click the check box(es) for the locations that should be denied. c. Click Select. 15.
Session Manager Configuration 7. Add a routing policy. A routing policy consists of a selected SIP entity as its destination and a number of time ranges that define when the policy can be used. See Creating routing policies on page 159. 8. Add dial patterns. Dial patterns are used to match digits received to a destination. Each dial pattern has an associated routing policy that defines the target entity for matched calls and when the match should be used. See Creating dial patterns on page 160.
Session Manager 6.0 8. In the IP Address Pattern field, enter an IP address pattern that matches the IP LAN address range. The * character can be used as a match-all wildcard. For example, the pattern 192.168.42.* matches all addresses in the range 192.168.42.1 to 192.168.42.255. 9. In the Notes field, enter notes about this location pattern, as appropriate. 10. Click Commit. Creating adaptations Occasionally calls to or from the branch may require digit conversion in order to ensure correct routing.
Session Manager Configuration 9. In the Time Zone drop-down box, select the time zone for the location. 10. For the Override Port & Transport with DNS SRV check box, accept the default setting, unchecked. 11. In the SIP Timer B/F (in seconds) field, accept the default setting, 4. Note: If you see that calls are abnormally terminated, you should increase this number. 12. In the Credential Name field, accept the default setting, blank. 13. In the Call Detail Recording field, accept the default setting. 14.
Session Manager 6.0 This check box must be checked. If it is not checked, calls from the associated SIP Entity 2 will be denied by Session Manager. 8. In the Notes field, enter notes regarding this entity link, as appropriate. 9. Click Commit. Creating time ranges Additional time ranges can be created and used with a routing policy to define when the routing policy is active. For most B5800 Branch Gateway implementations, you do not need to define additional time ranges.
Session Manager Configuration Creating dial patterns A dial pattern is defined to direct calls prefixed with the branch prefix to each branch. 1. On the System Manager console, in the left navigation pane, select Routing > Dial Patterns. 2. On the Dial Patterns page, click New to create a new dial pattern. 3. On the Dial Pattern Details page, in the Pattern field, enter the branch prefix. This is the dialed number or number prefix that the dial pattern is intended to match. 4.
Creating a System Manager link to Network Management Creating a System Manager link to Network Management About this task You are able to use Avaya Aura® Session Manager Release 6.x, cut-through capability to access Network Management. The System Manager cut-through allows the provisioning of the Network Management IP address with a unique menu name within the System Manager GUI.
Session Manager Configuration f) g) h) i) j) In the Port field, enter 443. In the URI field, enter /cgi-bin/launch_products.pl. In the Order field, enter the order in which the access points are accessed. In the Description field, enter a description of this access point. Click Save. 5. Expand the Port section, and do the following: a) b) c) d) e) f) Click New. In the Name field, enter the name of the port. In the Protocol drop-down box, select the appropriate protocol. In the Port field, enter 443.
Chapter 9: Voicemail operation The B5800 Branch Gateway system uses its Embedded Voicemail by default. However, a number of other voicemail options are supported. • Embedded Voicemail — Embedded Voicemail uses the system SD card in the B5800 Branch Gateway system control unit for storage of prompts and messages. Embedded Voicemail supports mailboxes for all local extension numbers, announcements to waiting callers, and auto attendants (up to 40) for external calls.
Voicemail operation Configuring Modular Messaging About this task The B5800 Branch Gateway system can be configured to use Modular Messaging as its voicemail server. Procedure 1. Start Manager and connect to the B5800 Branch Gateway system. 2. In the left navigation pane, click System. 3. Click the Voicemail tab. 4. In the Voicemail Type drop-down box, select Modular Messaging over SIP. Note: Fields applicable to this mode of voicemail support remain enabled. 5.
Modular Messaging PSTN Fallback 8. In the Maximum Record Time field, use the up and down arrows to set the maximum recording length in seconds for recorded announcement and auto attendant prompts. Note: You can set a number in this field only if Use embedded for AA and Announcements is checked. 9. Click OK. 10. Select File > Save Configuration. The Send Configuration window appears and the Configuration Reboot Mode is set to Immediate. Do not change the reboot mode.
Voicemail operation 3. Click 50: Main. Within the ARS form, the default 1N; short code is the one used for national calls. It would match the MM PSTN Number and attempt to route it to the SM Line which we know is out of service if the MM PSTN Number is being used for calls to voicemail. We can change the routing by adding a specific short code for the MM PSTN Number. 4. To add a short code, click the Add... button. 5.
Embedded Voicemail for auto attendants and announcements to those calls. 7. Click OK. 8. Select File > Save Configuration. Embedded Voicemail for auto attendants and announcements If Modular Messaging is used as the central voicemail system, you are able to still use the local Embedded Voicemail for auto attendant operation and for announcements to waiting calls. The procedures required to configure the auto attendant are provided in this section.
Voicemail operation Procedure 1. Start Manager and connect to the B5800 Branch Gateway system. 2. In the left navigation pane, right-click Auto Attendant and select New. 3. In the Auto Attendant tab, do the following: a) In the Name field, enter the name of the auto attendant. The name can be up to 15 characters in length. External calls can be routed to the auto attendant by entering AA:Name in the destination field of an Incoming Call Route.
Embedded Voicemail for auto attendants and announcements appropriate greeting is played to callers and followed by the Menu Options greeting which should list the available actions. • Time Profile — defines each period of auto attendant operation. When there are overlaps or gaps between time profiles, precedence is given in the order morning, afternoon and then evening. • Recording Name — appears next to the short code used for manually recording auto attendant prompts.
Voicemail operation Recording prompts About this task When a new auto attendant is created, a number of short codes are automatically added to the system short codes table. The short codes allow the recording of the various auto attendant prompts. The appropriate number to dial is indicated against each greeting on the Auto Attendant tab in Manager. The telephone number part takes the form "AA:Name.
Embedded Voicemail for auto attendants and announcements Transferring recordings to the system SD card About this task Use this procedure to manually copy the pre-recorded prompts and announcements onto the system SD card. Procedure 1. Start Manager and connect to the B5800 Branch Gateway system. 2. Select File > Advanced > Embedded File Management. 3. Drag and drop the recording into the folder dynamic\lvmail\AAG on the system SD card.
Voicemail operation 172 Implementing the Avaya B5800 Branch Gateway Comments? infodev@avaya.
Chapter 10: Extension administration This chapter provides the procedures to administer native and survivable extensions. When the B5800 Branch Gateway is deployed in the Distributed Branch user model, the extensions are referred to as native extensions. When the B5800 Branch Gateway is deployed in the Centralized Branch user model, the extensions are referred to as survivable extensions.
Extension administration Enabling branch SIP extension support About this task Before adding any SIP extensions, the B5800 Branch Gateway system must be enabled for SIP extension support. Use this procedure to configure the B5800 Branch Gateway to support the addition of SIP extensions. Important: The configuration changes in the following procedure will require the B5800 Branch Gateway system to be rebooted. Procedure 1. Start Manager and connect to the B5800 Branch Gateway system. 2.
Native extensions SIP Registrar tab field descriptions Name Default Description Domain Name Default = Blank This is the local SIP registrar domain name that will be needed by SIP devices in order to register with the B5800 Branch Gateway. If this field is left blank, registration is against the LAN IP address. For our examples we have been using a domain, example.com.
Extension administration Name Default Description auto create matching entries, the extension's Extension Mode setting defaults to Local (native) which is incorrect for a centralized (survivable) extension. • For local (native) extensions, this setting can be enabled. Adding extensions and users to the B5800 Branch Gateway About this task For each native extension, matching extension and user entries must be added to the B5800 Branch Gateway configuration.
Native extensions Note: The full range of B5800 Branch Gateway user settings can be configured for a native extension. However the key settings are the Name and Extension fields. 12. Click OK. 13. Click the Telephony tab. 14. Click the Call Settings tab. 15. Click the Call Waiting On check box to select this option. This setting is required to allow features such as transferring calls. 16. Click OK. 17.
Extension administration that if you do not select this feature, the user's mailbox is not disabled. Messages can still be forward to their mailbox and recordings can be placed in it. The mailbox can also still be accessed to collect messages. e) If you want users retrieving messages to automatically hear the prompt "For help at any time press 8" , check the Voicemail Help check box. If switched off, users can still press 8 for help.
Native extensions Name Default Description Device Type Default = Unknown SIP device This is an information field only. If the configuration has been loaded from a system with SIP extensions currently registered, the current type of SIP phone is listed if recognized. Module This field indicates the external expansion module on which the port is located. BP indicates an analog phone extension port on the base or control unit. BD indicates a digital station (DS) port on the control unit.
Extension administration Name Default Description system using the Name and Login Code configured for the user within the B5800 Branch Gateway configuration. For centralized extensions this should be set to On. Extension Mode Default = Local • For survivable extensions, this must be set to Centralized. • For native extensions, this must be set to Local. DID Numbers Default = Blank • This field does not apply to native extensions. When configuring a native extension, leave this field blank.
Survivable extensions Survivable extensions Survivable extensions support SIP phones only. For a list of supported telephones, see Supported telephones on page 21. Voicemail for survivable extensions is provided by Modular Messaging. When Modular Messaging is used as the central voicemail system, at each branch you have the option to still use the local Embedded Voicemail for auto attendant operation and for announcements to waiting calls.
Extension administration The B5800 Branch Gateway supports Session Manager 6.1 and Session Manager 6.0. Depending on the Session Manager version you are using, see one of the following sections: • Session Manager 6.1 configuration required for survivable extension support on page 185 • Session Manager 6.0 configuration required for survivable extension support on page 188 Survivable extension configuration checklist Use this checklist to monitor your progress as you administer survivable extensions.
Survivable extensions detects that connection to the Avaya Aura® Session Manager is available again, it dynamically registers with it and switches back to normal operation. Important: Branch Survivability Settings. Survivable extensions entering survivability mode with the branch will occur in parallel with the branch loosing whatever centralized call control and trunk services it was configured to receive from the Avaya Aura® Session Manager.
Extension administration Extension Type 184 Dialed Number Notes Survivable Survivable 8XXXX Dial the extension number as shown on the target extension. The call routing is done by the Avaya Aura® Session Manager and Communication Manager Feature Server. No additional configuration is required. Native Survivable 8XXXX Dial the extension number as shown on the target extension.
Survivable extensions Session Manager 6.1 configuration required for survivable extension support The topics in this section provide the Session Manager 6.1 procedures required to configure survivable extension mode. Note: In the Session Manager application, you must complete fields marked with an asterisk. Fields not marked with an asterisk are optional. Adding stations to Session Manager The survivable extension can now be added to Session Manager.
Extension administration g. In the Password field, enter the password required to log into System Manager for personal web configuration. h. In the Confirm Password field, enter the password again. i. In the Localized Display Name field, enter the name to be used as the calling party. j. In the Endpoint Display Name field, enter the user's full name. k. In the Honorific field, enter the user's title if applicable. l. In the Language Preference drop-down box, select the appropriate language. m.
Survivable extensions a. In the Primary Session Manager drop-down box, select the Session Manager instance that should be used as the home server for the currently displayed communication profile. b. In the Secondary Session Manager drop-down box, Session Manager instance that should be used as the backup server for the currently displayed communication profile. c. In the Origination Application Sequence drop-down box, select the Communication Manager Feature Server or Evolution Server. d.
Extension administration i. In the Voice Mail Number field, enter the number used to access the voicemail system. j. Check the Delete Endpoint on Unassign of Endpoint from User or on Delete Users check box to select this option. Note: You do not need to configure the Messaging Profile section for B5800 Branch Gateway at this time. 10. Click Commit. 11. Repeat this procedure to add each survivable extension. Viewing Session Manager registered users Procedure 1.
Survivable extensions 1. On the System Manager console, in the left navigation pane, select Users > Manage Users. 2. On the User Management page, click New. 3. On the New User Profile page, in the General section, do the following: a. In the Last Name field, enter the user's last name. Note: Since you are adding a station in this procedure and not a user, depending on how the branches and stations in your system are named and organized, you could enter a location name in this field, for example Chicago 25.
Extension administration 5. To add a postal address for this user, in the Address section, do the following: a. Click New. b. On the Add Address page, in the Name field, enter the user's name. c. In the Address Type drop-down box, select Office or Home, as appropriate. d. In the Building field, enter the building name. e. In the Room field, enter the room number. f. In the Street field, enter the street name. g. In the Locality field, enter the appropriate locale. h.
Survivable extensions Note: Do not designate the B5800 Branch Gateway in this field. The B5800 Branch Gateway address must be provided to the telephones through the settings file. See Survivability settings on page 198 for more information. Note that when running System Manager R6.1 SP1 or later, you are able to select B5800 in this field. See Adding stations to Session Manager on page 185 for more information. f.
Extension administration The list of registered users appears. 2. To see the complete registration status of an individual user, click the check box for the user you want to view. Enabling branch SIP extension support About this task Before adding any SIP extensions, the B5800 Branch Gateway system must be enabled for SIP extension support. Use this procedure to configure the B5800 Branch Gateway to support the addition of SIP extensions.
Survivable extensions 11. Click OK. 12. Select File > Save Configuration. The Send Configuration window appears and the Configuration Reboot Mode is set to Immediate. Do not change the reboot mode. SIP Registrar tab field descriptions Name Default Description Domain Name Default = Blank This is the local SIP registrar domain name that will be needed by SIP devices in order to register with the B5800 Branch Gateway. If this field is left blank, registration is against the LAN IP address.
Extension administration Name Default Description the B5800 Branch Gateway system if they match existing extension and user entries in the configuration. If a centralized (survivable) extension is allowed to auto create matching entries, the extension's Extension Mode setting defaults to Local (native) which is incorrect for a centralized (survivable) extension. • For local (native) extensions, this setting can be enabled.
Survivable extensions 10. In the Name field, enter the same user name used for the survivable extension login to B5800 Branch Gateway. 11. In the Extension field, enter the Base Extension setting used for the SIP extension entry. Note: The full range of B5800 Branch Gateway user settings can be configured for the centralized user while they are operating in survivability mode. However the key settings are the Name and Extension fields. 12. Click OK. 13. Click the Telephony tab. 14.
Extension administration Name Default Description digital and IP extensions, this value is fixed as On. Reset Volume After Calls Default = Off If selected, resets the phone's handset volume after each call. Device Type Default = Unknown SIP device This is an information field only. If the configuration has been loaded from a system with SIP extensions currently registered, the current type of SIP phone is listed if recognized.
Survivable extensions Name Default Description Currently connected calls are not affected by changes to this setting Force Authorization Default = On If enabled, SIP devices are required to register with the B5800 Branch Gateway system using the Name and Login Code configured for the user within the B5800 Branch Gateway configuration. For centralized extensions this should be set to On. Extension Mode Default = Local • For survivable extensions, this must be set to Centralized.
Extension administration Name Default Description target any matching centralized extension DID and then any centralized extension number before checking any alternative routes configured. Survivability settings The settings used by each survivable extension are set through System Manager, as described in Step 8e in Adding stations to Session Manager on page 185 and through the 46xxsettings.txt file loaded by each survivable extension when it is started. The 46xxsettings.
Survivable extensions During survivable mode, when registered to the B5800 Branch Gateway system, the phone is not able to obtain dial plan information from the Avaya Aura® Session Manager as it would normally expect. This DIALPLAN strings can be used to set what numbers are dialed immediately when matched without waiting for any dialing timeout. Multiple entries can be used, separated by | characters. For example, on a typical B5800 Branch Gateway system, the following might be used.
Extension administration • PSTN_VM_NUM This sets the number dialed when the Message button is pressed and the phone is in survivable mode. For example, a DID number for the Modular Messaging system. • RECOVERYREGISTERWAIT This is the monitoring interval used by the phone when no available controller was detected by a previous monitoring check. The phone waits for a response from each controller in the SIP_CONTROLLER_LIST with the CONTROLLER_SEARCH_INTERVAL setting.
Survivable extensions The enterprise SIP domain. This must match a domain set in the Avaya Aura® domains settings. • SIPREGPROXYPOLICY This setting controls how the list of SIP controllers specified above are monitored and used. The settings are: • alternate (SET SIPREGPROXYPOLICY alternate) Remain registered with only the active controller. This is the default setting.
Extension administration SIP controller monitoring It is important to understand that both the B5800 Branch Gateway system and the survivable extensions perform monitoring of the Avaya Aura® Session Manager availability. • The monitoring done by each survivable extension is used to determine when it should failover to another SIP controller. • The B5800 Branch Gateway system's monitoring is used to determine when the B5800 Branch Gateway system should allow survivable extensions to register with it.
Survivable extensions from it. B5800 Branch Gateway only responds to this request if its Avaya Aura® Session Manager lines are out of service. • If the phone does not have a current controller, it will register with the highest ranked available controller. • If a higher ranked controller then the extension's current active controller is available, it will switch its active controller to the higher ranked available controller. This only applies if the FAILBACK_POLICY is set to auto.
Extension administration 9600 extension operation Features available during failover The following apply while an extension is in the process of failover to another SIP controller. Typically the failover process will be completed within 2 minutes. • The phone will display the survivability warning icon. In addition: • If the extension is idle, it displays the message Link recovery. Limited phone service. Calls may be lost.
Survivable extensions • The message waiting indicator does not work and is switched off. • Voicemail may still be available using the PSTN_VM_NUM number configured in the survivability settings. • One-button voicemail access will be available if the central voice mail system continues to operate and will make a PSTN call to the voice mail system. Depends on correct provisioning. • Local telephone features will be available: audio selection (speaker / headset / handset), mute.
Extension administration Feature Normal operation Survivability mode with B5800 Branch Gateway Call Management Yes (CM COR) Yes (Some restrictions can be configured in the B5800 Branch Gateway either at the system level or for the user.
Chapter 11: Managing license files with PLDS Overview The Avaya Product Licensing and Delivery System (PLDS) provides customers, Avaya Partners, distributors, and Avaya Associates with easy-to-use tools for managing license entitlements. Using PLDS, you can perform operations such as license activations, license upgrades, and license moves. When you place an order for a PLDS-licensed software product, the license entitlements on the order are automatically created in PLDS.
Managing license files with PLDS Registering for PLDS Procedure 1. Go to the Avaya Product Licensing and Delivery System (PLDS) Web site (https:// plds.avaya.com). You will be redirected to the Single sign-on (SSO) Web site. 2. Log in to SSO using your SSO ID and Password. You will be redirected to the PLDS registration page. 3. If you are registering: • as an Avaya Partner, enter the Partner Link ID. If you do not know your Link ID, send an e-mail to prmadmin@avaya.com.
About license activation Types of license activation Types of activation include: • Regular activation: where license entitlements are activated to generate Activation Records. • Upgrade activation, which involves either: • Activating license entitlements that have been marked as upgradeable. When you activate these license entitlements, you can generate License/Key for either the current version or the old version.
Managing license files with PLDS Note: The Quick Activation automatically assumes that you want to activate all license entitlements on LAC and gives the option to remove line items and enter the amount of each license to activate (full or partial amount). 4. Enter the B5800 Branch Gateway information. 5. Click Next to validate the registration detail. 6. Enter the B5800 Branch Gateway information. This is the Feature Key Serial Number printed on the System SD card.
Searching for license entitlements • Group ID • License activation code In addition to these search criteria, PLDS also provides other additional advanced search criteria for searching license entitlements. Note: Avaya associate or Avaya Partners can only search license entitlements by company name. Procedure 1. Type http://plds.avaya.com in your Web browser to access the Avaya PLDS Web site. 2. Enter your Login ID and password to log on to the PLDS Web site. 3. Click Assets > View Entitlements.
Managing license files with PLDS Tip: You can use a wildcard (%) character if you do not know the exact LAC you are searching for. For example, if you enter AS0%, the system searches for all the LACs starting with AS0. You can enter a wildcard character (%) at any position in the search criteria. You will receive LACs in an e-mail if you have supplied the e-mail address to your sales order. If you do not have this code, you will need to search using one of the other search criteria. 7.
Regenerate License files 9. Perform the following steps to send an activation notification e-mail message: a) In the E-mail to field, enter e-mail addresses for any additional activation notification recipients. b) Enter any comments or special instructions in the Comments field. c) Click Finish. 10. Click View Activation Records. • The Overview tab displays a summary of the license activation information. • The Ownership tab displays the registration information.
Managing license files with PLDS 214 Implementing the Avaya B5800 Branch Gateway Comments? infodev@avaya.
Chapter 12: Standalone SAL Gateway for remote service Avaya Global Services (AGS) uses the Secure Access Link (SAL) Gateway to provide remote delivery of service to the B5800 Branch Gateway. The supported configuration requires a standalone SAL gateway that is deployed in the enterprise headquarters/data center and using the B5800 Branch Gateway administration applications — Manager, System Status, and System Monitor. See Administration software suite on page 71 for a description of these applications.
Standalone SAL Gateway for remote service Note: For B5800 Branch Gateway upgrades, you must access Manager that is installed on a PC or Network Management server that resides within the customer network. • System Status Application The System Status Application is an administration tool used to monitor the current status of individual branches in the B5800 Branch Gateway system. You are able to use SAL to access the System Status Application that is installed locally or remotely.
B5800 Branch Gateway registration and SAL Gateway on-boarding • Your company name • Avaya Sold-to Number (customer number) • Your contact information, so that Avaya can contact you if there are questions Avaya uses this information to register your gateway.
Standalone SAL Gateway for remote service Universal Install/SAL Registration Request Form You can download this form from the Avaya support web site as follows: 1. Go to the Avaya support Web site http://support.avaya.com. 2. Select More Resources > Equipment Registration. 3. Under Non-Regional (Product) Specific Documentation, select Universal Install/SAL Registration Request Form. 4. Complete the registration form as instructed. 218 Implementing the Avaya B5800 Branch Gateway Comments? infodev@avaya.
Chapter 13: Additional installation and system procedures The following topics are provided in this chapter: • Switching Off an IP Office System on page 219 • Rebooting an IP Office System on page 221 • About changing components on page 222 • Swapping Extension Users on page 226 • About changing extension numbers on page 226 • B5800 Branch Gateway software upgrade on page 228 • External output port (EXT O/P) on page 231 • Example of BRI So8 module configuration on page 233 • SNMP on page 236 • DTE Port Main
Additional installation and system procedures • The shutdown process takes up to a minute to complete. When shutdown, the CPU LED and the base card LEDs 1 and 9 (if trunk daughter card fitted) will flash red rapidly. The memory card LEDs are extinguished. Do not remove power from the system or remove any of the memory cards until the system is in the this state. • To restart a system when shutdown indefinitely, or to restart a system before the timed restart, switch power to the system off and on again.
Rebooting the system Shutting down the system using a system phone About this task To shut down the system using a system phone, you must be administered as a System Phone user. You can shut down the system using a 1400, 1600, or 9600 series phone (excluding XX01, XX02, and XX03 models). Unlike Manager, a system phone user cannot select an indefinite shutdown. A system phone user can set a timed shut down of between 5 minutes and 24 hours.
Additional installation and system procedures 4. Enter your user name and password. 5. In the Reboot window, do one of the following: • Select Immediate to reboot the system immediately. • Select When Free to reboot the system when there are no calls in progress. This selection can be combined with the Call Barring options. • Select Timed and then specify a time in hours and minutes. This reboots the system the same as When Free but first waits for a specific time.
About changing components Procedure 1. Turn the B5800 Branch Gateway system off. See System shutdown on page 219. 2. Remove the card or external expansion module. Note: The card slot or expansion port used as the replacement must be installed in the same position. 3. Install the replacement using the appropriate procedure for the type of component. See Base and trunk card installation on page 53 or Connecting external expansion modules on page 64 for more information. 4.
Additional installation and system procedures Replacing a component with one of lower capacity About this task If you are replacing a component with one of the same type but with lower capacity, when restarted the B5800 Branch Gateway system configuration must be edited to remove redundant entries. Procedure 1. Turn the B5800 Branch Gateway system off. See System shutdown on page 219. 2. Remove the card or external expansion module.
About changing components Adding a new component About this task If you are adding a new component to an available slot or port, when restarted the B5800 Branch Gateway system will automatically create configuration entries for the new trunks or extensions/users. Procedure 1. Turn the B5800 Branch Gateway system off. See System shutdown on page 219. 2. Install the new component using the appropriate procedure for the type of component.
Additional installation and system procedures Swapping extension users About this task This procedure explains how to swap extensions for two users. This example refers to User A and User B which represent any two users for whom you want to swap extensions. Procedure 1. Load the B5800 Branch Gateway configuration. 2. Select Extension. 3. In the Extension section of the window, select the extension for User A. 4. In the Base Extension field, change the extension to User B's extension.
About changing extension numbers configuration indicates the default associated user of the extension. It is not the extension number of that port. Renumbering all extensions and users About this task Use this procedure to shift all user extension numbers up or down by a set amount. Any settings linked to those numbers are adjusted including extension Base Extension settings. It does not affect hunt group extension numbers.
Additional installation and system procedures Manager automatically propagates the number change to any hunt groups, incoming call routes, user buttons, bridged appearance buttons and call coverage appearance buttons associated with the user's original extension number. If the user has an extension with which they are associated by being the extension's Base Extension setting, that setting is not automatically updated.
B5800 Branch Gateway software upgrade changes that occurred after this document was completed. Bulletins are available from http:// support.avaya.com • Multiple Managers — If more than one copy of Manager is running it is possible for the B5800 Branch Gateway system to request BIN files from a different Manager from the one that started the upgrade process. Ensure that only one copy of Manager is running when upgrading an B5800 Branch Gateway system.
Additional installation and system procedures Using the upgrade wizard About this task Before using the upgrade wizard, be sure you have a current backup of the system configuration. See Creating a backup of the system configuration on page 229 for more information. Procedure 1. Start Manager. 2. Select File > Advanced > Upgrade. The UpgradeWiz scans for B5800 Branch Gateway modules using the address specified in the Unit/Broadcast Address field. 3.
External output port (EXT O/P) • Click the check box for Backup System Files if, before upgrading to the new software, you want the current files in the System SD cards /primary folder copied to a /backup folder. • Click the check box for Upload System Files if you want the full set of software files that Manager has to be copied to the /primary folder on the System SD card. In addition to control unit and module software this will include phone software files.
Additional installation and system procedures State Switch 1 Switch 2 Open *40 *43 Pulse *41 *44 EXT O/P connections EXT O/P ports use a standard 3.5mm stereo jack plug for connection. The B5800 Branch Gateway is able to open (high resistance), close (low resistance) or pulse (close for 5 seconds and then open) two switches within the port. Either switch can be operated separately. These switches are intended for activation of external relays in systems such as door opening systems.
Example of BRI So8 module configuration Example of BRI So8 module configuration The ports on a BRI So8 module can be used for the connection of ISDN devices. Following are examples of how to configure a port on the BRI So8 module for an ISDN terminal and for video conferencing. Example 1: ISDN terminal About this task In this example, calls on DID 123456 are routed to the first port of the So8 expansion module. That port has been configured as Line Group ID 701. Procedure 1.
Additional installation and system procedures b) Configure incoming call route. The # is used here instead of "n" to avoid problems with "Main". The minus sign means the number is processed from the left and so will wait for the whole number. • Line Group ID: 701 • Incoming Number: -100x • Destination: # c) Repeat for Line Group ID 702 etc.
Example of BRI So8 module configuration To route an incoming video call on the PRI lines configured above to an So8 module requires the following: Procedure 1. Create a dial short code that has the SO port as its destination line group. For this example the following is used: • Short Code: 1500 • Number: • Feature: Dial • Line Group: 601 (the So8 port number) 2. Create an incoming call routing that routes the appropriate calls to that short code.
Additional installation and system procedures Characteristics Admin/Software and Hardware/ Software • Country: USA • Country Code: 1 • Language: English (USA) • Area Code: 732 • Auto Answer: Yes • Number A: blank • AllowDial: Yes • Number B: blank • Allow User Setup: Yes • ISDN Switch Protocol: Standard ETSI Euro-ISDN • Maximum Time on Call: 480 User Setup Admin/Video Network/IMUX • Auto Answer: Yes • Numbers: blank • PIP: Auto • SPID: blank • Far Control of Near Camera: Yes • Audio Qual
SNMP This allows the application to create a network map and to raise an alarm when devices previously present do not respond. • Most SNMP manager applications can also do simple IP address polling to locate non-SNMP enabled devices. However this method of polling does not identify the device type or other information. • SNMP polling including details about the responding device.
Additional installation and system procedures HP OpenView Network Node Manager Procedure 1. Copy the following MIB files to the application's MIB folder. MIB File Source rfc2737-entity-mib.mib snmp_mibs\standard folder on OpenView Install CD. avayagen-mib.mib \AdminCD\snmp_mibs\IPOffice folder on B5800 Branch Gateway Admin DVD. ipo-prod-mib.mib \AdminCD\snmp_mibs\IPOffice folder on B5800 Branch Gateway Admin DVD. ipo-mib.mib \AdminCD\snmp_mibs\IPOffice folder on B5800 Branch Gateway Admin DVD.
SNMP Castlerock SNMPc 5.1.6c and earlier Procedure 1. Copy the following MIB files to the application's MIB folder. This folder is typically C:\Program Files\SNMPc Network Manager\mibfiles. MIB file Source ENTITY-MIB \AdminCD\snmp_mibs\Standard on B5800 Branch Gateway Admin DVD. AVAYAGEN-MIB.mib \AdminCD\snmp_mibs\IPOffice on B5800 Branch Gateway Admin DVD. IPO-PROD-MIB.mib \AdminCD\snmp_mibs\IPOffice on B5800 Branch Gateway Admin DVD. IPO-MIB.
Additional installation and system procedures 3. In the SNMPv2-SMI.mib file find the definition of zeroDotZero and copy this to the clipboard. 4. In the STANDARD.MIB file find the SNMPv2-SMI section and paste in the definition of zeroDotZero from the clipboard before the end of this section (just before the END statement). 5. Save the modified STANDARD.MIB file. 6. Add the MIB file SNMP-FRAMEWORK-MIB.mib to the MIB database. 7. Add all the MIB files in the order listed. 8. Compile the MIBs ready for use.
SNMP establish communication and then changed (at both the SNMP agent and manager ends) for security. 7. Click OK. 8. Select File > Save Configuration to send the configuration back to the B5800 Branch Gateway and then select reboot. After the reboot, the SNMP manager will be able to discover the control unit. The discovery includes the control unit type and the current level of core software. Enabling SNMP trap sending Procedure 1. Start Manager and connect to the B5800 Branch Gateway system. 2.
Additional installation and system procedures b) In the IP Address field, enter the IP address of the PC running the SNMP manager application. c) In the Port field, enter the port on which the trap messages should be sent. This is the UDP port on which the B5800 Branch Gateway sends SNMP trap messages. The default is 162. d) In the Community field, enter the community that will be used by the agent and the SNMP manager. 13. In the Events section, click the check boxes for the events you want to send.
DTE port maintenance Data bits 8 Stop Bits 1 Settings > Emulation TTY DTE cables These cables are used for system maintenance and diagnostics under Avaya guidance. They can also be used for connection of RS232 serial terminal adaptor equipment to the control unit. This cable is a "Straight through DB9 female to DB9 male serial cable.
Additional installation and system procedures Erasing the configuration via debug About this task This procedure erases the system's configuration settings but does not alter the security settings. It is easier to use than the boot loader method. Before you perform this procedure, be sure you have a current backup of the system configuration. See Creating a backup of the system configuration on page 229 for more information. Procedure 1.
DTE port maintenance backup of the system configuration. See Creating a backup of the system configuration on page 229 for more information. Procedure 1. Attach the serial cable between the PC and the DTE port on the control unit. 2. Start the terminal program on your PC. Note: Ensure that the DTE port settings are configured as described in RS232 DTE port settings on page 242. Within a HyperTerminal session, the current settings are summarized across the base of the screen. 3.
Additional installation and system procedures Resetting the security settings to the default settings About this task This procedure resets the systems security settings back to the default settings but does not alter the configuration settings. Procedure 1. Attach the serial cable between the PC and the DTE port on the control unit. 2. Start the terminal program on your PC. Note: Ensure that the DTE port settings are configured as described in RS232 DTE port settings on page 242.
DTE port maintenance 2. Start the terminal program on your PC. Note: Ensure that the DTE port settings are configured as described in RS232 DTE port settings on page 242. Within a HyperTerminal session, the current settings are summarized across the base of the screen. 3. Arrange the program windows so that the terminal program and Manager TFTP log are visible at the same time. 4. Switch off power to the control unit. 5.
Additional installation and system procedures to a value in the 192.168.42.1 to 192.168.42.10 range. If this occurs it may be necessary to amend the BOOTP entry in Manager to match the address the system is using. Important: • Do not erase the core software unless absolutely necessary. The B5800 Branch Gateway software can normally be upgraded using Manager. See B5800 Branch Gateway software upgrade on page 228 for more information. • These procedures erase the operational software.
DTE port maintenance An OK response appears. 10. Enter AT-DEBUG. The time and date and then the Hello> prompt appears to show the system is ready to accept commands. 11. To erase the current configuration in RAM memory enter upgrade. The B5800 Branch Gateway system erases the current software and then sends out a BOOTP request on the network for new software. Manager responds and starts transferring the software using TFTP. Erasing the core software via the boot loader Procedure 1. Start Manager. 2.
Additional installation and system procedures 11. Power on the control unit and press the escape key every second until you get a loader message. An example of this message is: P12 Loader 2.4 CPU Revision 0x0900 12. Enter AT (upper case). An OK response appears. If OK does not appear, check the settings of your terminal program. 13. Enter AT-X. Multi-Sector Erase response appears. The control unit then requests the .bin file that is stored on the System SD card. 14.
AUX button Press Duration (seconds) Over 40 CPU LED Flashing green Action None Summary None AUX button The AUX button is on the control unit. If the AUX button is pressed during a restart of the control unit, the control unit skips booting from the /primary folder on the System SD card. If the AUX button is pressed for more than 5 seconds when a system is running, the control unit will shutdown for 10 minutes.
Additional installation and system procedures 4. Edit the WAN port. Do not create a new WAN port. The WAN port is automatically detected. If a WAN port is not displayed, connect the WAN cable, reboot the control unit and receive the configuration. The WAN port configuration form should now be added. 5. Create an IP Route. In the IP address field enter the network address of the remote end — not the IP address of the control unit. Under Destination select the service created above. 6.
Chapter 14: SD card management There are two SD card slots on the control unit. They are labeled System SD and Optional SD. System SD card slot • An Avaya System SD card must be present in this slot at all times. This card holds copies of the B5800 Branch Gateway firmware and configuration and is used as the control units non-volatile memory. • Each System SD card has a unique Feature Key serial number which is used for generating and validating licenses entered into the B5800 Branch Gateway configuration.
SD card management Warning: Memory cards should always be shut down before being removed when the system is running. Though the card slot LEDs indicate when data is being written to a card, lack of flashing LEDs is not a sufficient safeguard. Shutting down the card will disable embedded voicemail if being used. If the System SD card is removed, features licensed by the card's Feature Key serial number will continue operating for up to 2 hours.
Procedure Description Manage System System Minut r Status Phone es Caution: This process will erase all existing files on the card. Recreate on page 257 Create the folder structure on a memory card and copy a set of B5800 Branch Gateway software files into those folders. – – 15 Card specification Non-Avaya cards can be used in the Optional SD card slot as long as they match or exceed the following standard: SDHC 4GB minimum Class 2+. Single partition FAT32 format.
SD card management Booting from the SD cards When being powered up, the control unit looks for a valid .bin binary file to load. It does this using the possible source below in the order shown, skipping to the next source if the file is not present or is not valid. 1. System SD card primary folder. 2. The control unit's own internal non-volatile memory. Once a system has been installed, it uses its non-volatile memory to keep copies of the configuration and system binary files it is using.
About creating an B5800 Branch Gateway SD card • The normal boot-up process of upgrading expansion module firmware does not occur. If the File > Advanced > Upgrade command is used, only external expansion modules actually present in the system are listed for upgrade. Post boot operation During normal operation, configuration and binary files sent to the System SD card /primary folder using Manager are also written to the non-volatile memory.
SD card management any other method will remove the feature key used for B5800 Branch Gateway licensing from the card. These procedures are run on an SD card inserted in a card reader on the Manager PC. That card can then be used in the System SD card slot of a new system or in the Optional SD card slot of an existing system to upgrade that system. Formatting an SD card About this task Avaya SD cards should only be formatted using the format options provided within the B5800 Branch Gateway applications.
About creating an B5800 Branch Gateway SD card 2. In the navigation panel, select System > Memory Cards > System SD. 3. Click on the Format button at the bottom of the screen. The card is reformatted. All files and folders on the card will be deleted. This process takes a few seconds. Recreating an SD card About this task This procedure creates the folder structure on the SD card and copies the required firmware files from those installed with Manager onto the SD card.
SD card management Viewing the card contents About this task Using Manager you can view the folders and files on the System SD card and the Optional SD card. Procedure 1. Start Manager. 2. Select File > Embedded File Management. 3. From the Select IP Office window, select the B5800 Branch Gateway system you want to view. The file contents of the memory cards are displayed. About backing up the System SD card There are two levels of backup that can be performed.
About backing up the System SD card Procedure 1. Start Manager. 2. Select File > Embedded File Management. 3. From the Select IP Office window, select the appropriate system. The file contents of the memory cards are displayed. 4. Select File > Backup System Files. The contents of the primary folder on the System SD card are copied to the backup folder. This process takes approximately 6 minutes. Backing up the primary folder using the System Status application Procedure 1.
SD card management About restoring from the backup folder When you restore from the backup folder, you copy the contents of the backup folder on the System SD card to the primary folder on the System SD card. Files with matching file names are replaced. Warning: This procedure will cause the B5800 Branch Gateway system to be restarted, disconnecting any current calls and services in progress. Restoring from the backup folder using Manager Procedure 1. Start Manager. 2.
About backing up to the Optional SD card the process has been completed, the B5800 Branch Gateway system is restarted. Restoring from the backup folder using a system phone About this task A user configured as a system phone user can perform this procedure using a 1400, 1600, or 9600 Series phone (excluding XX01, XX02 and XX03 models). The user's login code is used to restrict access to system administration functions on the phone. Procedure 1. Select Features > Phone User > System Admin. 2.
SD card management Backing up to the Optional SD card using Manager Procedure 1. Start Manager. 2. Select File > Embedded File Management. 3. From the Select IP Office window, select the appropriate system. The file contents of the memory cards are displayed. 4. Select File > Copy System Card. The contents of the System SD card are copied to the Optional SD card. This takes at least 90 minutes and can take much longer. Backing up to the Optional SD card using the System Status application Procedure 1.
About restoring from the Optional SD card 2. Enter your B5800 Branch Gateway user login code. 3. From the menu select Memory Card. 4. Select Copy. The contents of the System SD card are copied to the Optional SD card. This takes at least 90 minutes and can take much longer. About restoring from the Optional SD card The files in the primary folder on the Optional SD card can be copied to the primary folder on the System SD card. Files with matching file names are replaced.
SD card management takes a few seconds. When the process has been completed, the B5800 Branch Gateway system is restarted. Restoring a configuration file from the Optional SD card using a system phone About this task A user configured as a system phone user can perform this procedure using a 1400, 1600, or 9600 Series phone (excluding XX01, XX02 and XX03 models). The user's login code is used to restrict access to system administration functions on the phone. Procedure 1.
System upgrade using the System SD card Restoring software files from the Optional SD card using a system phone About this task A user configured as a system phone user can perform this procedure using a 1400, 1600, or 9600 Series phone (excluding XX01, XX02 and XX03 models). The user's login code is used to restrict access to system administration functions on the phone. Procedure 1. Select Features > Phone User > System Admin. 2. Enter your B5800 Branch Gateway user login code. 3.
SD card management Method Description Location Software Files Embedded Voicemail Prompts Using Manager on Using Manager, the contents Local or page 268 of the card are compared to Remote the files that Manager has available and are upgraded if necessary. System SD Card Upgrade on page 269 In this method, the System SD card is shut down and removed from the control unit. The card's contents are upgraded using Manager.
System upgrade using the System SD card files. Depending on the files that need to be updated, this can take up to40 minutes. Upgrading the SD card locally About this task You can upgrade the SD card locally if you have physical access to the control unit. This method should be used with a timed reboot, allowing the card upgrade to be done during normal operation hours followed by a reboot outside of normal operation hours. See Rebooting the system on page 221 for more information.
SD card management Procedure 1. Insert the SD card into a card reader on the Manager PC. Note: Do not remove the SD card. Removing the SD card will interrupt the upgrade. 2. Using Manager, select File > Advanced > Recreate IP Office SD Card. 3. Select one of the following: • IP Office A-Law • IP Office U-Law This selection determines how the system operates when defaulted with the SD card installed in the System SD card slot. 4. Browse to the card location and click OK.
Memory card removal Shutting down a memory card using Manager Procedure 1. Start Manager. 2. Select File > Advanced > Memory Card Commands > Shutdown. 3. In the Select IP Office window, select the system containing the memory card. 4. Click OK. 5. At the back of the control unit, confirm that the appropriate memory card LED is off. 6. Remove the card.
SD card management Shutting down a memory card using System Status Procedure 1. Start System Status and access the status output. 2. In the navigation panel select System. 3. Select Memory Cards. 4. Select either System Card or Optional Card. 5. At the bottom of the screen select Shutdown. 6. At the back of the control unit, confirm that the appropriate memory card LED is off. 7. Remove the card.
Card startup Starting up a card using the System Status application Procedure 1. Start the System Status application and access the B5800 Branch Gateway status output. 2. In the navigation panel select System. 3. Select Memory Cards. 4. Select either System Card or Optional Card. 5. At the bottom of the window, select Start Up.
SD card management 274 Implementing the Avaya B5800 Branch Gateway Comments? infodev@avaya.
Chapter 15: Safety and regulatory information Safety statements The B5800 Branch Gateway modules are intended to be installed by Service Personnel and it is the responsibility of the Service Personnel to ensure that all subsidiary interconnected equipment is wired correctly and also meet the safety requirements of IEC60950 or UL60950 where applicable. • The CE mark affixed to this equipment means that the module complies with the 1999/5/ EC (R&TTE), 89/336/EEC (EMC) and 72/23EEC (LVD) Directives.
Safety and regulatory information • Do not use the telephone to report a gas leak in the vicinity of the leak. • Use only the power cord and batteries indicated in this manual. Lithium batteries A lithium battery is fitted to the real time clock on the control unit motherboard. Warning: The Lithium battery must only be replaced by Avaya personnel or authorized representatives. There is a danger of explosion if the battery is incorrectly replaced.
Safety statements Trunk interface modules To ensure the validation of the approvals, only the following types of trunk interface cards must be fitted in the B5800 Branch Gateway control unit. USA/Canada Product Quad BRI PRI E1 Single PRI T1 Dual Single ATM4 WAN ATM4 WAN Dual Control unit Rest of World Product Quad BRI PRI E1/E1R2 Single Dual PRI T1 Single Dual Control unit Note: E1R2 trunks are only supported in CALA and Korea.
Safety and regulatory information Port Name Port Description Port Classification Expansion ports Expansion Module connector. SELV Audio port Connector for Music on Hold. SELV External control port Connector for Controlling Ancillary circuits. SELV DC input port Connector for DC input power. SELV Interconnection circuits shall be selected to provide continued conformance with the requirements of EN 609050:1992/A3:1995 clause 2.
Regulatory Instructions for Use EMC caution for china Regulatory Instructions for Use Australia BRI interface During the configuration, ensure "000" emergency number is not barred, by performing the following: • Short Code: 000 • Telephone No: 000; • Function: DialEmergency Connections to TS013, the following bearer capabilities shall not be used: 7kHz Audio, Video, Restricted Digital Information. If unknown type of number is used in calling party number, the network will use the default CLI.
Safety and regulatory information During the configuration, ensure "000" emergency number is not barred, by performing the following: • Short Code: 000 • Telephone No: 000; • Function: DialEmergency Canada This equipment meets the applicable Industry Canada Terminal Equipment Technical Specifications. This is confirmed by the registration number.
Regulatory Instructions for Use China Implementing the Avaya B5800 Branch Gateway November 2011 281
Safety and regulatory information European Union • 999 and 112 calls must not be barred. Doing so will invalidate the approval. • All connections at the MDF shall be identifiable by suitable labeling. • The CE mark displayed on B5800 Branch Gateway equipment indicates the systems compliance with the EMC, LVD, and R&TTE Directives and common technical regulations for Primary Rate and Basic Rate ISDN.
Regulatory Instructions for Use Port FIC SOC USOC Jack REN IPO500 PRI 1U, 04DU9.BN, IPO500 PRI2U, 04DU9.DN, IP400 PRI-T1 04DU9.IKN, 04DU9.ISN 6.0Y RJ48C NA IPO500 ATM4U IP400 ATM4U OL13A, OL13B, OL13C, 02AC2, 02LA2, 02LB2, 02LC2, 02LR2, 02LS2 9.0Y RJ45S 0.1B IPO500 ATM16 OL13A, OL13B, OL13C, 02AC2, 02GS2, 02LA2, 02LB2, 02LC2, 02LR2, 02LF2 02GS2, 02LS2 9.0Y RJ45S 0.
Safety and regulatory information • Routed to a recorded announcement that can be administered by the customer premises equipment (CPE) user • Routed to a dial prompt • This equipment returns answer supervision signals on all DID calls forwarded back to the PSTN. Permissible exceptions are: • A call is unanswered. • A busy tone is received. • A reorder tone is received.
Regulatory Instructions for Use personnel may result in violation of the FCC rules. Qualified personnel may adjust gain settings above these levels only where: • Measurement is made to ensure that the power levels sent to line at each network interface connected does not exceed the maximum levels specified in FCC part 68 section 68.308(b) and TIA/EIA-IS-968 Section 4.5 for that specific interface type.
Safety and regulatory information 286 Implementing the Avaya B5800 Branch Gateway Comments? infodev@avaya.
Appendix A: Centralized deployment example call flows This appendix provides examples of call flows for a system that is configured in a centralized deployment. Routing concepts In the example network deployment provided in this appendix, all calls that are routed within Avaya Aura® Session Manager are converted to E.164. The primary function for this is to support Tail-End-Hop-Off (TEHO). E.164 E.
Centralized deployment example call flows Solution overview The Solution overview illustrates the store network. • CM-1 represents a Communication Manager used for features for the store phones. • CM-2 represents the primary Communication Manager used for corporate endpoints and PSTN trunking. • SM represents all Session Managers.
Sunny day Sunny day The first set of call flows are for sunny day. This is when all SIP endpoints have full connectivity across the WAN back to the core and are registered to the Session Manager. All SIP trunks are in service. Internal call 1 Store Phone originates call to a corporate station 1014553. 2 SM sends 1014553 to CM for origination processing. 3 CM identifies call as internal and routes 1014553 back to SM. 4 SM sends call to destination phone 1014553 at destination CM.
Centralized deployment example call flows Local PSTN dialing 290 1 Store Phone calls local extension 9-755-1234. 2 SM sends 9-755-1234 to CM for origination call processing. 3 CM translates the call into E.164 based on callers’ location and sends +1-916-755-1234 to SM. 4 SM adapts the call for the local carrier and sends 9-755-1234 back to original branch. Session Manager could use the E.164 formatted number to do TEHO routing at this step. 5 B5800 Branch sends 755-1234 to the PSTN.
Sunny day Long distance and international 1 Store Phone calls long distance number 9-011-912-2600-9000. 2 SM sends 9-011-912-2600-9000 to CM for origination call processing. 3 CM translates the call into E.164 based on callers’ location and sends +1-912-2600-9000 to SM. 4 SM adapts the call for the local carrier and sends 9-011-912-2600-9000 back to original branch. Session Manager could use the E.164 formatted number to do TEHO routing at this step.
Centralized deployment example call flows Incoming call 1 Customer dials store extension 1-916-788-1234 (the branch phone number). 2 B5800 Branch sends call to VDN 5000299 on CM via SM. Routing to a VDN allows reporting of branch calls. 3 SM matches call with a Route Pattern and sends to CM. 4 CM routes call to x-ported station that is bridged to all branch endpoints. (X-ported refers to AWOH (Admin With Out Hardware) stations that are administered as an endpoint without any physical hardware.
Rainy day reduced SIP feature set which does not support all sunny day features. In a rainy day inbound call scenario, the process would be as follows: an inbound call will ring on all phones until that call is answered. Because bridged line appearances are not supported as a rainy day feature, once that call is answered, the call will only appear on the active station, and all other stations will show idle.
Centralized deployment example call flows 2 B5800 Branch sends the call directly to all registered SIP stations in the hunt group. A RTP Media is established between the Store Phone and the B5800 Branch. Incoming call from corporate – coverage 294 1 Corporate user dials branch extension 5089110 2 SM routes call to CM-1 for origination call processing. 3 CM-1 and SM identify that branch is unreachable. CM-1 routes call to coverage path for 5089110.
Rainy day A RTP Media stream is established between the Store Phone and the B5800 Branch.
Centralized deployment example call flows 296 Implementing the Avaya B5800 Branch Gateway Comments? infodev@avaya.
Appendix B: Avaya port matrix for B5800 Branch Gateway and SIP phones This appendix provides example ingress and egress ports for B5800 Branch Gateway and SIP phones. What are ports and how are they used? TCP and UDP use ports (defined at http://www.iana.org/assignments/port-numbers) to route traffic arriving at a particular IP device to the correct upper layer application. These ports are logical descriptors (numbers) that help devices multiplex and de-multiplex information streams.
Avaya port matrix for B5800 Branch Gateway and SIP phones • Well known ports are those numbered from 0 through 1023. • Registered ports are those numbered from 1024 through 49151 • Dynamic ports are those numbered from 49152 through 65535 The well known and registered ports are assigned by IANA (Internet Assigned Numbers Authority) and are found at http://www.iana.org/assignments/port-numbers. Well known ports For the purpose of providing services to unknown clients, a service listen port is defined.
Firewall types • Date flow 1: 172.16.16.14:1234 — 10.1.2.3:2345 • Date flow 2: 172.16.16.14:1235 — 10.1.2.3:2345 • Date flow 3: 172.16.16.14:1234 — 10.1.2.4:2345 Data flow 1 has two different port numbers and two different IP addresses and is a valid and typical socket pair. Data flow 2 has the same IP addresses and the same port number on the second IP address as data flow 1, but since the port number on the first socket differs, the data flow is unique.
Avaya port matrix for B5800 Branch Gateway and SIP phones packet, up through the application layer, is examined. A stateful inspection firewall also monitors the state of the connection and compiles the information in a state table. Stateful inspection firewalls close off ports until the connection to the specific port is requested. This is an enhancement to security against port scanning. Port scanning is the act of systematically scanning a computer's ports.
Ingress ports for B5800 Branch Gateway and SIP phones < TFTP Data packet (1..n), src port 4153, dst port 2421 TFTP Acks (1..n), src port 2421, dst port 4153 Ingress ports for B5800 Branch Gateway and SIP phones # Dest. Port Network En /App or Protocol Dis ? Default Port State Remote Device Ext to Branch ? Description 1 22 TCP/ SSH No Open Admin terminal or SAL Gateway Yes System mgmt requiring shell access – Remote maintenance.
Avaya port matrix for B5800 Branch Gateway and SIP phones # Dest. Port Network En /App or Protocol Dis ? Default Port State Remote Device Ext to Branch ? Description 9 50805-C TCP/ HTTP B5800 config access No Open B5800 Manager Yes B5800 Configuration Service – Secured. See optional 50804. 10 50808-C TCP/ HTTP B5800 Sys Status Access No Open B5800 Manager Yes B5800 System Status Access.
Egress ports for B5800 Branch Gateway and SIP phones # Dest. Port Network En /App or Protocol Dis ? Default Port State Remote Device Ext to Branch ? B5800 Sec Settings Access Description Unsecured. See 50813. For a description of the column headings, see Table column heading definitions on page 305. Egress ports for B5800 Branch Gateway and SIP phones # Dest.
Avaya port matrix for B5800 Branch Gateway and SIP phones # Dest. Port Network En /App or Protocol Dis ? Default Port State Remote Device Ext to Branch ? Description 7 514 UDP/ SyslogCli Yes Open Syslog Server No, but Log files transmitted could be from IP phones to server. 8 5005-C RTCP Yes Open NMS Yes RTCP collector (HPOpenview, AIM, etc.). 9 5060 TCP/SIP No Open Yes SIP signaling.
Table column heading definitions Table column heading definitions Column heading Description Dest Port Destination port — this is the layer-4 port number to which the connection request is sent. Valid values include 0 – 65535. Network/App Protocol Network/application protocol — this is the name associated with the layer-4 protocol and layers-5-7 application.
Avaya port matrix for B5800 Branch Gateway and SIP phones • Email will not flow through the B5800 Branch Gateway in this example. See optional section for port 25. • An off-site DHCP server is used to supply IP addresses to phones and PCs. Otherwise, add ports 67 and 68 in optional sections. • The B5800 Branch Gateway IP address will be manually configured and not need a DHCP server. • TFTP service begins using port 69, but eventually uses the source ports from both sides.
Port usage diagram Port usage diagram Implementing the Avaya B5800 Branch Gateway November 2011 307
Avaya port matrix for B5800 Branch Gateway and SIP phones In this diagram, direction of the arrow depicts call initiation. Data traffic will typically be 2way. 308 Implementing the Avaya B5800 Branch Gateway Comments? infodev@avaya.
Appendix C: B5800 Branch Gateway call flows Calls from local extensions (i.e. deployed in Distributed branch model) 1. Local phone to local phone Local phone A B5800 Branch Gateway local phone B 2. Local phone to PSTN (using local trunking) Local phone B5800 Branch Gateway SIP Trunk) PSTN B5800 Branch Gateway trunk (e.g. FXO, ISDN, SP 3. Local phone to PSTN (using centralized trunking) Local phone B5800 Branch Gateway Session Manager central gateway/SBC PSTN 4.
B5800 Branch Gateway call flows Centralized phone A centralized phone B Avaya Aura core servers (including Session Manager and CM-FS) Note: The B5800 Branch Gateway is not involved in handling the call in this scenario. The call flow descriptions in this document are intended to clarify the call flow between the branch and the core with focus on B5800 Branch Gateway involvement.
Calls to Centralized phones in normal mode (aka sunny day) 1. From PSTN to centralized phone’s DID (LDN is associated with local B5800 Branch Gateway trunk) PSTN B5800 Branch Gateway trunk (e.g. FXO, ISDN, SP SIP trunk) B5800 Branch Gateway Session Manager CM-FS Session Manager centralized phone 2. From PSTN to centralized phone via B5800 Branch Gateway auto-attendant (branch autoattendant LDN is associated with local B5800 Branch Gateway trunk) PSTN B5800 Branch Gateway trunk (e.g.
B5800 Branch Gateway call flows Centralized phone B5800 Branch Gateway SP SIP trunk) PSTN B5800 Branch Gateway trunk (e.g. FXO, ISDN, 4. Centralized phone to headquarters or other enterprise site B5800 Branch Gateway can be administered to send such calls over the PSTN. See below. Calls to Centralized phones in survivability mode (aka rainy day) 1. From PSTN to centralized phone’s DID PSTN B5800 Branch Gateway trunk (e.g.
Appendix D: PSTN example call flow During normal operation, calls made by a survivable extension are received by the Avaya Aura®Session Manager and passed to the extension's Communication Manager Feature Server. The Communication Manager Feature Server then sends the call back to the Avaya Aura®Session Manager for routing elsewhere in the Avaya Aura® network. In this example, a survivable extension at branch 811 dials an external number in local area code 908.
PSTN example call flow 9. Route Pattern 11 routes the call to SIP Trunk Group Number 32. This connects the Communication Manager Feature Server to the Avaya Aura®Session Manager and is specifically configured for routing local PSTN calls to branches. 10. The Communication Manager Feature Server sends a new SIP INVITE to Avaya Aura®Session Manager over SIP Trunk Group Number 32 with the dialed digits of 19085551111. 11.
Configuring trunk-to-trunk transfer The difference between the two values needs to be greater than or equal to the desired number of simultaneous SIP trunk connections. Configuring trunk-to-trunk transfer Use this procedure to configure Communication Manager to allow trunk-to-trunk transfers. 1. Enter the change system-parameters features command. 2. In the Trunk-to-Trunk Transfer field, enter the appropriate number.
PSTN example call flow Configuring IP network regions An IP address map can be used for network region assignment. The network region assignment can be used to vary behaviors within and between regions. Typically, though this can be varied, each location will match an IP region and vice versa. The following screen illustrates a subset of the IP network map used for this example configuration. Branch 811 has IP addresses in 192.168.42.0/24 assigned to network region 11.
SIP signaling group and trunk group The ip-network-region form for Network Region 1 needs to be similarly configured. Network region 1 is for phones and servers as well as Session Manager at the central location. SIP signaling group and trunk group For this example configuration two SIP signaling groups and two associated trunk groups are used between Communication Manager and Avaya Aura® Session Manager in the example configuration.
PSTN example call flow 1. Enter the add signaling-group n command, where n is an available signaling group number. 2. Enter the following values for the specified fields and retain the default values for all remaining fields. a. In the Group Type field, enter sip. b. In the Transport Method field, enter tls. c. In the IMS Enabled? field, enter y. d. In the Near-end Node Name field, enter the IP node name added for the Communication Manager Feature Server. e.
Configuring SIP trunk groups Configuring SIP trunk groups Next, SIP trunk groups need to be added. 1. Enter the add trunk-group n command, where n is an available trunk group number to add to SIP trunk groups. 2. Enter the following values for the specified fields, and retain the default values for the remaining fields. a. In the Group Type field, enter sip. b. In the Group Name field, enter a description for the trunk group. c. In the TAC field, enter an available trunk access code as per the dial plan.
PSTN example call flow The trunk group 32 used for routing local PSTN calls from branch phones is similarly configured. Configuring route patterns Configure a route pattern to correspond to each of the two newly added SIP trunk groups. 1. Enter the change route-pattern n command, where n is an available route pattern. 2. Enter the following values for the specified fields, and retain the default values for the remaining fields. a. In the Pattern Name field, enter a descriptive name for the route pattern.
Configuring AAR Configuring AAR 1. Enter the change aar analysis command to add an entry for the extension range corresponding to the branch survivable extensions 2. Enter the following values for the specified fields, and retain the default values for the remaining fields. a. In the Dialed String field, enter the dialed prefix digits to match on. b. In the Total Min field, enter the minimum number of digits. c. In the Total Max field, enter the maximum number of digits. d.
PSTN example call flow Location specific ARS digit analysis Location based analysis is used before global analysis. Using it we could apply rules that only apply to calls from survivable extensions at location 11. For example, the pattern below routes calls prefixed 1908 from location 11 back to the Avaya Aura® Session Manager using Route Pattern 32 on page 320 when a match occurs.
Global ARS Digit Analysis Route Pattern 3 is configured to use a Trunk Group that connects to the Communication Manager Feature Server at the headquarters location for PSTN calls to and from that site.
PSTN example call flow 324 Implementing the Avaya B5800 Branch Gateway Comments? infodev@avaya.
Appendix E: Branch PSTN call routing examples Each B5800 Branch Gateway system can support its own external PSTN trunks. When deployed in an Avaya Aura® network, you have considerable flexibility over where outgoing PSTN calls should emerge from the network and similarly where incoming calls should be routed. The following examples demonstrate some of the options available: • Centralized call control on page 325 — External calls at a branch site can be rerouted to be dialed out at another site.
Branch PSTN call routing examples In this example, the company wants all national and international calls made at the branch to be routed to use the headquarter site's PSTN trunks. This is in order to benefit from a bulk cost reduction available for calls from that site. This example assumes that all the branches were initially setup with the default North American locale. For B5800 Branch Gateway that means that a dial 9 prefix is used for external calls.
Centralized call control 3. Click 50: Main. Within the ARS window, the default 0N; short code that matches international numbers currently routes those calls to any available trunk in line group 0. 4. To edit the short code, click the short code. 5. Click the Edit... button. 6. Make the following changes: a) In the Code field, leave this set to 0N;. b) In the Feature field, change this to Dial. c) In the Telephone Number field, change this to 90N.
Branch PSTN call routing examples 9. Click OK. 10. Select File > Save Configuration. Branch PSTN override In the example provided in Centralized call control on page 325, we configured the branch system so that all national and international calls go to the headquarters site for routing to the PSTN. There may occasionally be scenarios where a particular number needs to override this and be dialed via the branch system's own PSTN trunks.
Branch PSTN override 3. Click 50: Main. Within the ARS form, the default 1N; short code is the one used for national calls. It would match the MM PSTN Number and attempt to route it to the SM Line which we know is out of service if the MM PSTN Number is being used for calls to voicemail. We can change the routing by adding a specific short code for the MM PSTN Number. 4. To add a short code, click the Add... button. 5.
Branch PSTN call routing examples to those calls. 7. Click OK. 8. Select File > Save Configuration. PSTN trunk fallback In branch scenarios where centralized call control and trunking (see Centralized call control on page 325) has been configured for certain calls, loss of the Avaya Aura®Session Manager line connection will impact making those calls.
PSTN trunk fallback issue is resolved. However, even if that is the case, it may be recommended to configure a headquarters PSTN number that can be dialed to report the Avaya Aura® Session Manager line issue. See Branch PSTN override on page 328 for more information. • Provide PSTN trunk fallback within the branch configuration. See Configuring PSTN trunk fallback on page 331. Note however that PSTN fallback will also occur when the number of external calls exceeds the available SIP trunk licenses.
Branch PSTN call routing examples 7. Click OK. 8. Click OK. 9. Double click on the existing default ARS that was reconfigured to send all branch national and international calls to the Avaya Aura® Session Manager line. 10. In the Additional Route drop-down box , select the PSTN ARS form just created above. The form is now set such that, if the Avaya Aura® Session Manager line is not available (out of service or all licensed channels busy) calls can be checked for a dialing match in the PSTN ARS form.
PSTN trunk fallback • The Alternate Route Wait Time is used for caller's whose priority is not sufficient to use the alternate route immediately. The default setting is 30 seconds. However, you may want to adjust this setting to one that meets your requirements. • Since the only short code match in the alternate route in our example is for national calls, international calls will continue to wait for the Avaya Aura® Session Manager line. 11. Select File > Save Configuration.
Branch PSTN call routing examples 334 Implementing the Avaya B5800 Branch Gateway Comments? infodev@avaya.
Appendix F: Recommended courses for Avaya B5800 Branch Gateway training Avaya B5800 Branch Gateway Table 1: APSS – SMEC Type Code Course title Delivery Duration (hours) First offering Existing ASC00121 WEN Selling IP Office eLearning 4 Now New ASC00126 OEN Selling IP Office - Update Release 6.1 eLearning 0.5 October Table 2: ACIS – IP Office Type Code Course title Delivery Duration (hours) New ATU02142 WEN IP Office Technical Delta Release 6.
Recommended courses for Avaya B5800 Branch Gateway training Unified Communications Table 3: ACIS – Session Manager and System Manager Type 336 Code Course title Delivery Duration (hours) First offering Update ATU00180OE System Manager General eLearning Overview 1 Dec 6 Update ATU00171OEN Session Manager General Overview eLearning 2 Dec 6 Update ATU00183OEN System Manager Technical Overview eLearning 1 Dec 6 Update ATU00170OEN Session Manager Technical Overview eLearning 2 Dec 6 Up
Unified Communications Type Duration (hours) First offering Session Manager, CM vILT and other Feature Server Administration 5 Dec 6 Update ATC01840VEN Survivable Remote Session Manager Administration 6.1 eLearning 2 Dec 6 Update ATC01842OEN CM and System Manager eLearning 2 Dec 6 New ATA02540VEN Advanced System Manager Administration eLearning 3 Dec 6 New ATU02643OEN System Manager 6.1: Delta General Overview eLearning .5 Dec 6 New ATU01515OEN Session Manager 6.
Recommended courses for Avaya B5800 Branch Gateway training 338 Implementing the Avaya B5800 Branch Gateway Comments? infodev@avaya.
Glossary Centralized Branch user model This term describes aB5800 Branch Gateway deployment model where certain 9600 Avaya SIP phones can use the B5800 Branch Gateway as a survivability gateway. In normal operation, these phones register directly to the Avaya Aura®Session Manager in the enterprise core and get services from core applications such as the Communication Manager Feature Server or Evolution Server.
Failback Failback This term is used for the situation where a centralized extension that is working with a survivability call controller detects that its normal call controller is available again. The extension will go through a process of failback to its normal call controller. Failover This term is used for the situations where a centralized extension's preferred call controller is no longer available.
Tail-End-Hop-Off match those available from the headquarters system during normal operation. See Rainy day. Tail-End-Hop-Off Part of mixed mode trunking, this describes scenarios where certain calls at other branches or the headquarters site are routed to the PSTN of another branch.
Tail-End-Hop-Off 342 Implementing the Avaya B5800 Branch Gateway Comments? infodev@avaya.
