Implementing Avaya B5800 Branch Gateway for a Communication Server 1000 Configuration Release 6.
© 2012 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.
All non-Avaya trademarks are the property of their respective owners, and “Linux” is a registered trademark of Linus Torvalds. 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 B5800 Branch Gateway for a CS 1000 Configuration Comments? infodev@avaya.
Contents Chapter 1: B5800 Branch Gateway overview................................................................... 13 PSTN trunking configurations................................................................................................................... 13 Voicemail support options......................................................................................................................... 14 Management.....................................................................................
Installation checklist.................................................................................................................................. 55 Tools and equipment required................................................................................................................... 56 Unpacking equipment............................................................................................................................... 57 SD card preparation........................................
Starting System Status.............................................................................................................................. 103 Starting System Monitor............................................................................................................................ 104 Chapter 9: Initial branch configuration............................................................................. 107 Configuration checklist...............................................................
Disabling the System Manager administration feature for the branch from System Manager......... 162 Disabling the System Manager administration feature for the branch from IP Office Manager........ 162 Enabling the Security Settings option for the branch....................................................................... 163 Synchronizing B5800 Branch Gateway with System Manager.................................................................
System shutdown...................................................................................................................................... 208 Shutting down the system using Manager....................................................................................... 208 Shutting down the system using the System Status application...................................................... 209 Shutting down the system using a system phone................................................................
Backing up the primary folder using Manager.................................................................................. 251 Backing up the primary folder using the System Status application................................................. 251 Backing up the primary folder using a system phone....................................................................... 252 About restoring from the backup folder...................................................................................................
Sockets..................................................................................................................................................... 278 Firewall types............................................................................................................................................ 279 Firewall policies......................................................................................................................................... 280 TFTP port usage..................
Implementing B5800 Branch Gateway for a CS 1000 Configuration October 2012
Chapter 1: B5800 Branch Gateway overview The Avaya B5800 Branch Gateway is a flexible, cost-effective communications platform for enterprise branch offices. It enables access via SIP to Avaya Aura® Session Manager in the enterprise center, optional access to centralized PSTN trunking, and access to centralized applications, such as conferencing, messaging, and more. The B5800 Branch Gateway solution provides centralized management by Avaya Aura® System Manager and centralized licensing by WebLM.
B5800 Branch Gateway overview call type (local, national, international), time of day or even individual user. See Branch PSTN call routing examples on page 291 for more information. Voicemail support options B5800 Branch Gateway supports a range of options for voicemail services to the branch's native users. It supports Embedded Voicemail for native branch users and auto attendants to service local PSTN trunks.
Management • Create B5800 Branch Gateway system configuration templates that can be applied to selected B5800 Branch Gateway systems. These templates are used for initial device provisioning. These templates can be edited, duplicated, or deleted. • Upload and convert audio files to System Manager to be used in the B5800 Branch Gateway System Configuration Auto Attendant feature. • Manage B5800 Branch Gateway system configurations.
B5800 Branch Gateway overview About upgrading B5800 Branch Gateways With the introduction of centralized management provided by Avaya Aura® System Manager, you are able to upgrade B5800 Branch Gateway firmware and software from System Manager. You are also able to upgrade an individual B5800 Branch Gateway system from IP Office Manager installed on an administration PC that is connected directly to the system. You can perform an upgrade from IP Office Manager using the upgrade wizard or the System SD card.
Licensing Support for individual PLDS license files for each branch (the licensing method provided in B5800 Branch Gateway R6.1) is also an option. WebLM licensing is the recommended method for B5800 Branch Gateway R6.2 and higher. Both licensing methods are described below. WebLM license management B5800 Branch Gateway R6.2 supports WebLM licensing in which a single license file is generated in PLDS for multiple branches.
B5800 Branch Gateway overview For the separate PLDS licensing method, branch licenses are issued and validated against the Feature Key serial number of the System SD card used by that B5800 Branch Gateway. That number is printed after the FK prefix on the System SD card and is also shown in the branch system configuration. This means that licenses issued for one branch cannot be used in the configuration of another branch.
License modes channels which do not require a license. Additional B channels beyond these 8 require a license. There are two additional channels licenses that define the number of additional channels (above the default 8): • Additional T1 Channels license — This license is for additional T1 trunks. • Additional E1 Channels license — This license is for additional E1 or E1R2 trunks.
B5800 Branch Gateway overview System components The B5800 Branch Gateway system is comprised of the following hardware components. • B5800 Branch Gateway control unit — B5800 Branch Gateway is supported on the IP500v2 platform or on the B5800 Branch Gateway hardware platform which is based on IP500v2. The B5800 Branch Gateway control unit stores the system configuration and performs the routing and switching for telephone calls and data traffic.
System components expansion modules on page 22 for a list of the supported external expansion modules. - BRI combination card — This card provides 6 digital station ports (1-6), 2 analog extension ports (7-8) and 2 BRI trunk ports (9-10, 4 channels). The card also includes 10 VCM channels. This card has a pre-installed BRI trunk daughter card. A maximum of 2 BRI combination cards of any type are allowed per control unit.
B5800 Branch Gateway overview 4 analog trunk ports or 4 BRI channels (2 ports). The trunk daughter card cannot be removed or replaced with another type of trunk daughter card. • External expansion modules — External expansion modules are used to add additional analog and digital ports. If the control unit is fitted with a 4–port expansion base card, then up to 12 external expansion modules are supported.
Supported telephones Supported telephones Telephone Native extensions (local extensions operating in the distributed branch user model) Analog 1120E SIP 1140E SIP 1220 SIP 1230 SIP 1403 digital 1408 digital 1416 digital 1603 1603SW 1608 1616 1603SW-I 1608-I 1616-I BM32 (DSS) 1 2402D 2410D 2420 3616 wireless 3620 wireless 3626 wireless 3641 wireless 3645 wireless 3720 DECT R4 3725 DECT R4 Implementing B5800 Branch Gateway for a CS 1000 Configuration October 2012 23
B5800 Branch Gateway overview Telephone Native extensions (local extensions operating in the distributed branch user model) 3740 DECT R4 3749 DECT R4 3810 digital wireless 4601 4602IP 4602SW 4610IP 4610SW 4621 4625 5402 5410 5420 1 EU24 (DSS) 5601 5602IP 5602SW 5610IP 5610SW 5620 5621 1 EU24 BL (DSS) 9504 digital 9508 digital 24 9608 2 9611G 2 9621G 2 9641G 2 9620L 2 9620C 2 Implementing B5800 Branch Gateway for a CS 1000 Configuration Comments? infodev@avaya.
Supported telephones Telephone Native extensions (local extensions operating in the distributed branch user model) 9630G 2 9640 2 9640G 2 9650 2 9650C 2 SBM24 1 Avaya 1010/1020/1030/1040 video conferencing units B149 conference phone B159 conference phone B179 conference phone BM12 1 BCM TDM sets: • DECT handsets 4xxx/7xxx series • T7316E • T7316 • T7406E • T7406 • T7208 • T7100 • T7000 • M7310 • M7310N • M7310+BLF • M7324 • M7324N • M7208 • M7208N • M7100 • M7100N Implementing B5800 Branc
B5800 Branch Gateway overview Telephone Native extensions (local extensions operating in the distributed branch user model) • Audio conference unit • T24 KIM (Key Indicator Module for T7316) DevConnect–approved 3rd-party SIP audio and video endpoints 1 When connected to their respective telephones. 2 Supported when running H.323 firmware; not supported when running SIP firmware. Software applications The B5800 Branch Gateway software applications are provided on DVDs.
Supported country locales - System Status: a monitoring application used to inspect the current status of B5800 Branch Gateway lines and extensions and to view records of recent alarms and events. It runs as a Java application. - System Monitor: shows a trace of all activity on the B5800 Branch Gateway system in detail. Interpretation of System Monitor traces requires a high-level of data and telephony protocol knowledge.
B5800 Branch Gateway overview Locale Language Telephony Phone Applications Display Manager Soft Console EVM and SVM* Denmark Danish - Finland Suomi - France French Germany German Greece Greek - - - SVM only Hong Kong Cantonese - - - - Hungary Hungarian - - - SVM only Iceland Icelandic - - - - India UK English - Italy Italian Korea Korean Mexico Latin Spanish Netherlands Dutch - - New Zealand UK English * Norway Norwegian Peru Latin Spanish Poland Po
Related resources • Manager: Indicates that the IP Office Manager application can run in the specific locale language. Manager uses the best match it has (French, German, Brazilian, Dutch, Italian, Mexican Spanish, Russian, or US English) for the regional location setting of the PC on which it is running, otherwise it defaults to UK English. If required the language used within the Manager screens can be overridden.
B5800 Branch Gateway overview • SIP Line Fundamentals – Avaya Communication Server 1000, document number NN43001-508 • Element Manager System Reference – Administration, document number NN43001-632 • Software Input Output Reference – Administration, document number NN43001-611 • SIP Software for Avaya 1100 Series IP Deskphones–Administration, document number NN43170–600 • SIP Software for Avaya 1200 Series IP Deskphones–Administration, document number NN43170–601 Avaya Mentor videos Avaya Mentor is an Ava
Revision history The official web site for Avaya. The front page also provides access to individual Avaya web sites for different countries. • Avaya Enterprise Portal (http://partner.avaya.com) This is the official web site for all Avaya Business Partners. The site requires registration for a user name and password. Once accessed, the site portal can be individually customized for what products and information types you wish to see and to be notified about by email. • Avaya Support (http://support.avaya.
B5800 Branch Gateway overview Issue Date Summary of changes • “Configuring the B5800 Branch Gateway for certificates” (This procedure replaces “Manually loading the certificate to the B5800 Branch Gateway.) • “Adding distributed users to System Manager” (Distributed H.323 users and SIP users do not require different configuration when being added to System Manager.) 32 Implementing B5800 Branch Gateway for a CS 1000 Configuration Comments? infodev@avaya.
Chapter 2: CS 1000 and B5800 Branch Gateway deployments B5800 Branch Gateway in CS 1000 deployments supports all phones listed in Supported telephones on page 23. Note that Norstar and BCM Digital T&M Series phones and 11xx and 12xx phones which may already be deployed in CS 1000 environments are supported in CS 1000 and B5800 Branch Gateway deployments. Note: The 11xx and 12xx phones must be upgraded to SIP 4.3 firmware to be supported on the B5800 Branch Gateway.
CS 1000 and B5800 Branch Gateway deployments Note: The CallPilot number must be configured as the central voicemail system in the B5800 Branch Gateway voicemail configuration. B5800 Branch Gateway does not support sending calls to CallPilot based on configuring Call Forwarding for individual users. For more information about voicemail options, see Voicemail options on page 173.
Option 2 Option 2 In this option, CS 1000 and B5800 Branch Gateway reside as peers and an additional SSG is required to support Session Manager. Configuration considerations The following guidelines must be considered when configuring B5800 Branch Gateways in CS 1000 deployments. • To enable CS 1000 and Session Manager to use TLS for secure communication, security certificates must be exchanged between the two systems.
CS 1000 and B5800 Branch Gateway deployments See Configuring B5800 Branch Gateway to use CallPilot for voicemail on page 179 for more information. • CallPilot supports the feature to send all calls unconditionally to voicemail. To configure this feature, in the Manager application, select User > Forwarding tab. Then complete the fields as appropriate. See the Manager on-line help for more information.
Chapter 3: 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 deployment option (option 1 or option 2) you are using. See CS 1000 and B5800 Branch Gateway deployments on page 33 The dial plan you are configuring for the Dial plan considerations on page 38 system and each branch. The B5800 Branch Gateway licenses required for this installation.
Planning • Avaya Communication Server 1000 R7.5 with SIP Line Gateway must be installed and configured at the headquarters location. • A stand-alone Secure Access Link (SAL) Gateway R2.1 must be deployed. Note: SAL Gateway does not support alarming for B5800 Branch Gateway managed devices in CS 1000 deployments. Note: System Platform's virtual SAL gateway is not supported.
Voicemail considerations such calls routed via the headquarters site wherever possible. In addition, the branch staff want to keep their branch phone numbers. • 3-digit branch numbers beginning with 8, ie. 800 to 899. • 3-digit native extension numbers beginning with 2, ie. 200 to 299. • Dial 9 prefix for outgoing PSTN calls. • National and international calls allowed but routed via the headquarters site's PSTN trunks.
Planning • Avaya Aura Messaging — The B5800 Branch Gateway system can be configured to use Avaya Aura Messaging as its voicemail server when Session Manager is used as the core SIP router. See Configuring B5800 Branch Gateway to use Avaya Aura Messaging for voicemail on page 177 for more information.
Network assessment for VoIP requirements cases where a specific number should still be routed via the branches own PSTN trunks. • PSTN trunk fallback on page 296 — The B5800 Branch Gateway can be configured to allow some calls that would normally use the Avaya Aura® Session Manager line to be routed via the PSTN when the Avaya Aura® Session Manager line is not available. The various methods used in the these examples can be combined to match the customer's needs.
Planning • The assessment should leave you confident that the implemented network will have the capacity for the foreseen data and voice traffic, and can support SIP, DHCP, TFTP and jitter buffers in SIP applications.
Chapter 4: 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 IP Office 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 265 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 67 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 54 Implementing B5800 Branch Gateway for a CS 1000 Configuration Comments? infodev@avaya.
Chapter 5: 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 # 7 Description Section Do one of the following: See one of the following: • Install the control unit on the wall. • Wall mounting on page 67. • Rack mounting on page 69. • Install the control unit in a rack. 8 Connect the external expansion modules. See External expansion modules on page 71. 9 Connect the control unit and external expansion modules to a functional ground. See Grounding on page 73.
Unpacking equipment - 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. Typically green for a functional ground and green/yellow for a protective ground. - If wall mounting, additional 4.
Hardware and software installation 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. Check all documentation Ensure that you read and retain any documentation included with the equipment. SD card preparation B5800 Branch Gateway control units are supplied with no installed firmware or configuration.
SD card preparation 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. Manager starts creating folders on the SD card and copying the required files into those folders. This process takes approximately 15 minutes.
Hardware and software installation 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. Adding a configuration file About this task Use this procedure to add a configuration file on the System SD card. That configuration file will then be used when the B5800 Branch Gateway system is started. Procedure 1.
Base and trunk card installation 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 while handling circuit boards. 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.
Base and trunk card installation 2. Ensure that you are wearing an anti-static wrist strap connected to a suitable ground point. 3. On the base card, identify the position of the 3 holes for the plastic pillars for the trunk daughter card. These are along the same edge as the card connector. 4. Fit the stand-off pillars to the base card. 5. If there is a clip-on metal shield over the connector block on the base card, remove it. 6.
Hardware and software installation Warning: Correct anti-static protection steps should be taken while handling circuit boards. Parts and equipment required • Legacy carrier card • VCM card • 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 64 Implementing B5800 Branch Gateway for a CS 1000 Configuration Comments? infodev@avaya.
Base and trunk card installation 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. On the carrier card identify the position of the jumper block and stand-off pillar holes for the IP400 card. The peg holes are labeled as VCM or TRUNK. 4.
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 68 Implementing B5800 Branch Gateway for a CS 1000 Configuration 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 70 Implementing B5800 Branch Gateway for a CS 1000 Configuration 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 B5800 Branch Gateway control unit On control units the ground point is located above the RS232 DTE port. 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.
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 Details of the number of alarms are recorded and the time and date of the most recent alarms. • System Monitor The IP Office 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 Installing the administration applications Procedure 1. Using the Add or Remove Programs option in the Windows Control Panel, check that the PC does not have an earlier version of the B5800 Branch Gateway Administration Suite installed. If there is, uninstall it. 2. Insert the B5800 Branch Gateway Administrator Applications DVD. 3. Select B5800 Branch Gateway Administration Suite. 4. Double-click on setup.exe. 5. Select the language you want to use for the installation process.
Hardware and software installation The B5800 Branch Gateway control unit is connected to the PC with a standard RJ45–RJ45 LAN cable. 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.
Applying power to the system The results should show a number of ping replies from the B5800 Branch Gateway . This confirms basic communication between the Manager PC and the B5800 Branch Gateway . 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.
Hardware and software installation • The control unit will then begin upgrading the external expansion modules. This is indicated by the red center LED on each module flashing red. The process is completed when the LED changes to steady green. • 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.
Applying power to the system About the LEDs Control unit LEDs LED Optional SD System SD CPU Description • Off = card shutdown • 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 i
Hardware and software installation Base Card LEDs 1 to 8 Usage • Green on = expansion module present • Red flashing = initializing • Red on = error • Orange regular flash = base card okay Combination LEDs 1 to 6 Green on = phone detected 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 =car
Default configuration External expansion module LEDs External expansion module All modules • Green on = module okay • Red flashing = module starting up • Red on = error Default configuration Unless you loaded a configuration file onto the System SD card, the B5800 Branch Gateway system will be configured with default settings when the system is started. Following are the basic default configuration settings for a B5800 Branch Gateway system. Network Settings LAN1 LAN2/WAN IP address 192.168.42.
Hardware and software installation values. The encoding default is set by the type of Feature Key installed when the system is first started. Default DHCP/IP address settings When a defaulted or new B5800 Branch Gateway control unit is switched on, it requests IP address information from a DHCP server on the network. This operation will occur whether the LAN cable is plugged in or not.
Connecting phones automatically detect the B5800 Branch Gateway and connect regardless of the PC or B5800 Branch Gateway LAN settings. This utility can be run on site or while the B5800 Branch Gateway control unit is being staged off site. Note: IP Office Manager preferences must be set to: • UDP discovery and 255.255.255.
Hardware and software installation 90 Implementing B5800 Branch Gateway for a CS 1000 Configuration Comments? infodev@avaya.
Chapter 6: About preserving staged button programming for BST phones Business Series Terminal (BST) phones are the M7 and T7 Digital Series Phones used by a BCM system. When migrating a BCM system to a B5800 Branch Gateway system, the M7 and T7 phones can be reused. When staging the T7 and M7 phones, user extensions are added and button programming is set up.
About preserving staged button programming for BST phones be 0 – 7. Note that because it is attenuation, the higher the value, the lower the ring volume. For example, 0 is full volume. 8. In the Line Group Id drop-down box, accept the default value, 0. 9. In the Locale drop-down box, accept the default value, blank. 10. For the Force Account Code check box, accept the default value, unchecked. 11. Click OK. The short code is displayed in the ShortCodes tab. 12.
Other DCP short codes Other DCP short codes There are other DCP short codes that preserve the user's extension configuration so that the configuration is not lost when the phone is plugged into the B5800 Branch Gateway system. • *DCP 4???????,0,1,1,0 Dial 0 (where ? is probably 0, but could be another number) — The presence of this short code will preserve button programming for a newly connected BST phone.
About preserving staged button programming for BST phones 94 Implementing B5800 Branch Gateway for a CS 1000 Configuration Comments? infodev@avaya.
Chapter 7: Upgrading an R6.2 system with an R6.2 service pack This chapter is for B5800 Branch Gateway systems that have already been upgraded from R6.1 to R6.2. Avaya periodically releases service packs to provide updates that fix existing problems or provide enhancements. This chapter describes how to perform an upgrade using Avaya Aura® System Manager. Avaya Aura® System Manager should be used on R6.2 systems when multiple branches require upgrades.
Upgrading an R6.2 system with an R6.2 service pack Remote Software Library for B5800 Branch Gateway upgrades For the B5800 Branch Gateway firmware upgrade files, an external server is required to act as a remote software library. This server hosts the firmware upgrade files through HTTP. The external server should have an FTP, SCP, or SFTP server to upload the firmware files from System Manager. While downloading from the PLDS web site, the firmware files are temporarily copied on System Manager.
Remote Software Library for B5800 Branch Gateway upgrades Component Requirement Recommendation Hard Drive 20GB free space There should be enough free space on the hard drive to store the firmware files. Memory 2GB As required by the operating system and the supported protocol services. Protocols (for the B5800 Branch Gateway elements to download files from the external server) HTTP server Any supported HTTP server installation.
Upgrading an R6.2 system with an R6.2 service pack Getting inventory Before you begin Ensure that all B5800 Branch Gateway devices have been added to System Manager. There are several methods available to add the B5800 Branch Gateways to System Manager. All methods require that you identify each individual B5800 Branch Gateway. See About adding B5800 Branch Gateways to System Manager on page 126 for more information.
Configuring user PLDS access 2. On the Inventory page, on the left navigation pane, click Manage Elements. 3. Click the check box for the appropriate element. 4. Click Edit. 5. On the Edit page, click the Attributes tab. 6. In the SNMP Attributes section, do the following: a. b. c. d. For the Version, click the radio button for V1. In the Read Community field, enter the read community of the device. In the Write Community field, enter the write community of the device.
Upgrading an R6.2 system with an R6.2 service pack 10. Click Commit. Creating a software library Procedure 1. From the System Manager console, under Elements, select Inventory. 2. On the Inventory page, click Upgrade Management > Software Library. 3. Click New. 4. On the Add Software Library page, in the Library Server Details tab, do the following: a. In the Name field, enter the appropriate name. b. In the IP Address field, enter the IP address of the library server. c.
Upgrading the B5800 Branch Gateway using System Manager Upgrading the B5800 Branch Gateway using System Manager About this task Use this task to upgrade the B5800 Branch Gateway. Included in this task are the steps to: • analyze the software to determine if a new version is available • download the firmware files from Avaya PLDS Avaya PLDS will automatically determine if a newer software version than what is currently installed is available.
Upgrading an R6.2 system with an R6.2 service pack The system displays the End User License Agreement page. 9. Click Accept to download the software. 10. When the download is complete, go to the Manage Software page. A yellow i indicates there is a newer version of software downloaded to the remote software library and the device can be upgraded. 11. Click the check box for the appropriate control unit. 12. Click Upgrade. The Upgrade button is enabled only if the state of the device is yellow. 13.
Chapter 8: Administration software suite The IP Office 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 IP Office administration applications are: • Manager IP Office Manager is used to access all parts of the B5800 Branch Gateway configuration. Different levels of access can be defined to control which parts of the configuration the Manager user can view and alter.
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 B5800 Branch Gateway 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.
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 106 Implementing B5800 Branch Gateway for a CS 1000 Configuration Comments? infodev@avaya.
Chapter 9: Initial branch configuration This chapter provides initial configuration tasks required for each B5800 Branch Gateway deployed in the distributed branch user model. Configuration checklist Use this checklist to monitor your progress as you configure a B5800 Branch Gateway system deployed as a distributed branch in a CS 1000 configuration. # Description 1 Confirm that your version of Avaya Aura® System Manager is R6.2 and SP1 has been installed.
Initial branch configuration # Description Section 5 Generate a certificate on Avaya Aura® System Manager. See Generating a certificate on System Manager on page 119. 6 Run the Initial Installation Utility. The See Using the Initial Installation Utility on Initial Installation utility provides page 121. configuration and security settings Note: that minimize initial installation activities and maximize security.
Configuration checklist # Description Section 9 Create a system template. (Optional) See Creating a system template on page 131. 10 Upload an auto attendant audio file. (Optional) See Uploading an auto attendant audio file on page 132. 11 Apply the system template to one or more branches. (Optional) See Applying the system template on page 133. 12 Create an endpoint template. See Creating an endpoint template on page 133. Note: You must create a B5800 Branch Gateway endpoint template.
Initial branch configuration # Description Section This procedure includes the steps to configure TLS transport for the Session Manager line. 21 Add a second Session Manager line See Avaya Aura Session Manager line for redundancy. redundancy on page 152. 22 Set up outgoing call routing. • See Setting up outgoing call routing on page 153. • For information on routing back to the branch for fallback alternate routes, see Branch PSTN call routing examples on page 291.
Setting up System Manager to launch IP Office Manager Setting up System Manager to launch IP Office Manager About this task From the administration PC, you can use the full version of IP Office Manager available on the B5800 Branch Gateway Administrator Applications DVD or IP Office Manager Lite that is provided in the B5800AdminLite.exe file to view and edit a B5800 Branch Gateway system configuration or security configuration from System Manager.
Initial branch configuration 5. Using any Linux editor, update the parameter abg_b5800_mgr_version in the / opt/Avaya/ABG//tools/ManagerSFXVersion.properties file with the version of IP Office Manager you downloaded from PLDS. Important: You must update the parameter abg_b5800_mgr_version each time you download a new version of IP Office Manager from PLDS and transfer to System Manager.
Setting up System Manager to launch IP Office Manager 9. Install IP Office Manager Lite on the administration PC. See Installing IP Office Manager from the System Manager server to a PC on page 113. Installing IP Office Manager from the System Manager server to a PC Before you begin The B5800AdminLite.exe file has been downloaded to the System Manager server. About this task Perform this task to install IP Office Manager from the System Manager server to a PC.
Initial branch configuration 11. Restart your PC. 12. To verify your PC is configured correctly, select My Computer > System Properties > Advanced tab > Environment Variables. Activating license files About this task B5800 Branch Gateway R6.2 uses the Avaya Product Licensing and Delivery System (PLDS) and integration with Web License Manager (WebLM) for B5800 Branch Gateway license management. B5800 Branch Gateway R6.
Activating license files license file, you must change the B5800 Branch Gateway back to System Manager control by enabling the System Manager administration feature for the branch. An alternative method to install the individual PLDS license on a B5800 Branch Gateway that is centrally managed by System Manager is to use the Embedded File Management feature available in B5800 Branch Gateway Manager. You do not need to disable/enabled System Manager administration for the branch using this method.
Initial branch configuration the System Manager administration feature for the branch from System Manager on page 162. 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 Send license file to Avaya Branch Gateway. 4. In the Upload Files window, select the PLDS license xml file.
Performing a certificate exchange between CS 1000 and Session Manager 6. Click OK. 7. In the Folders pane on the left, select System SD > System > Primary. 8. Select File > Upload file. 9. Select the PLDStemp.xml file. 10. Click OK. The Upload System Files window appears and shows the upload progress. 11. When the upload is complete, click Close. 12. From the Primary folder, perform a refresh. The B5800 Branch Gateway error mode will change to License Normal Mode. The PLDStemp.
Initial branch configuration 3. Add System Manager as a certificate authority. See Adding System Manager as a certificate authority on page 118. Exporting the System Manager certificate Procedure 1. From the System Manager console, under Services, select Security. 2. On the Security page, in the left navigation pane, select Certificates > Authority. 3. Click the Download pem file link. 4. In the File Download dialog box, click Save to save the file to the local desktop.
Generating a certificate on System Manager 3. Click the radio button associated with the IP address for the primary security server to view the certificate authorities associated with the system. 4. In the Certificate Authorities section, click Add. The Certificate Authority Add Wizard is launched. 5. In the Add a CA to the Service window, in the Friendly Name field, enter a descriptive name for the System Manager. 6.
Initial branch configuration Note: This password will be used as the Simple Certificate Enrollment Protocol (SCEP) password. d. In the Confirm Password field, enter the password again. e. In the CN, Common Name field, enter the appropriate name. This name should match the name of the B5800 Branch Gateway system you entered in the Username field. Note: The certificate name cannot contain spaces. In the Certificate Profile drop-down box, accept the default setting, ID_CLIENT_SERVER. g.
Using the Initial Installation Utility c. Click the Encryption tab. d. Click the View Certificates button. e. In the Certificate Management window, click the Your Certificates tab. 17. From your Firefox browser, to save the certificate in the X.509 PEM format, do the following: a. b. c. d. In the Certificate Management window, click the View button. In the Certificate Viewer window, click the Details tab. Click Export.
Initial branch configuration Warning: You are also able to select LAN2 to connect to the enterprise network. However, LAN2 is primarily intended to connect to the Internet or to public SIP trunks from carriers. The LAN2 firewall is normally disabled. If you select LAN2 and choose to enable the firewall, be sure to open the necessary ports for communicating with the enterprise network. For more information, see Avaya port matrix for B5800 Branch Gateway and SIP phones on page 277. 5.
Using the Initial Installation Utility e. In the Device Certificate Name field, enter the appropriate certificate authority name. Note: f. The device certificate name cannot contain spaces. In the Certificate Enrollment (SCEP) Password field, enter the appropriate password. 12. Click Save. The B5800 Branch Gateway reboots.
Initial branch configuration Configuring the B5800 Branch Gateway for certificates Before you begin Generate a certificate on System Manager. See Generating a certificate on System Manager on page 119. About this task Perform this procedure to configure the SCEP and security settings for a B5800 Branch Gateway. Note: Perform this procedure only if you did not run the Initial Installation Utility.
Configuring the B5800 Branch Gateway for certificates 12. In the Received Certificate Checks (Telephony Endpoints) drop-down box, accept the default setting, None. 13. In the SCEP Settings section, do the following: a. Click the Active check box to select that option. b. In the Request Interval (Seconds) box, accept the default setting, 120. c. In the SCEP Server IP/Name field, enter the IP address of the System Manager server. Include https:// at the beginning of the IP address, for example https://123.4.
Initial branch configuration About adding B5800 Branch Gateways to System Manager There are three different methods available that can be used to add B5800 Branch Gateways to System Manager. See one of the following topics: • Discovering B5800 Branch Gateways on page 126. This method requires you to identify the subnet IP address in which each branch is located. This method does not automatically discover all B5800 Branch Gateways in a network. • Bulk importing of devices on page 128.
About adding B5800 Branch Gateways to System Manager 9. Click Commit. 10. On the Configuration page, click the Subnets tab. 11. Click New. 12. On the Add Subnet Configuration page, in the Subnet IP field, enter the IP address of the subnet in which the branch is located. 13. In the Subnet Mask field, enter the subnet mask in which the branch is located. 14. In the Use SNMP V3 drop-down box, accept the default setting, No. 15.
Initial branch configuration 3. Click the System Events tab. 4. Select SNMP Enabled. 5. In the SNMP Port field, enter the UDP port number used by the SNMP agent to listen for and respond to SNMP traffic. The default is 161. 6. In the Community (Read-only) field, enter the community to which the device belongs for read access. This community name must match that used by the SNMP manager application when sending requests to the device.
About adding B5800 Branch Gateways to System Manager 6. Select one of the following import options: • To skip a matching record that already exists in the system during an import operation, click Skip. • To replace all data for an application, click Replace. • To merge application data so that you simultaneously perform an add and update operation of the application data, click Merge. • To delete the application data from the database that match the records in the xml file, click Delete. 7.
Initial branch configuration The fields for each B5800 Branch Gateway device that you add to the xml file will be the same except for the following two fields which contain unique information for each device: • where B5800 device is a unique name for this system. • where IP address is a unique IP address for this system.
Enabling WebLM licensing for the branch 16. Repeat steps 3 to 15 for each branch that is to be managed from System Manager. Enabling WebLM licensing for the branch About this task If you are going to use WebLM licensing, you must enable the WebLM licensing feature for the branch. See Licensing on page 16 for more information. Procedure 1. From the System Manager console, select the B5800 Branch Gateway device and click Edit to edit the system configuration for the device.
Initial branch configuration Note: An edited system template could be pushed to multiple branches if it is certain that the branches are identical, the modified system configuration applies to all the branches, and there are no local configuration changes that will be overwritten. Procedure 1. From the System Manager console, under Services, select Templates. 2. On the Templates page, in the left navigation pane, click B5800 System Configuration. 3.
Applying the system template 3. On the B5800 Branch Gateway System Configuration Templates page, under Templates List, select More Options > Manage Audio. 4. On the Manage Audio page, click the Browse button to locate the .wav file you want to upload. 5. Click the Upload button. The voice file is uploaded to System Manager in the .c11 format that is required for Embedded Voicemail on B5800 systems. The file is automatically converted from the .wav format to the .c11 format. 6.
Initial branch configuration 2. On the Templates page, in the left navigation pane, click B5800 Endpoint. 3. On the B5800 Branch Gateway Endpoint Templates page, do the following: a. Under Supported B5800 Branch Gateway Types, click the check box for B5800. b. Under Templates List, click New. 4. In the Name field, enter a name for this endpoint. 5. In the System Type drop-down box, select B5800. 6. In the Set Type drop-down box, select the appropriate set type. 7. In the Version drop-down box, select 6.2.
Disabling unused trunks 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 the B5800 Branch Gateway configuration will have settings for all the possible trunks and channels. In cases where the number of trunks or trunk channels in use is lower than the number supported by the trunk card, the unused trunks and channel must be disabled.
Initial branch 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. 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.
Digital trunk clock source Setting a trunk clock quality setting About this task Procedure 1. From the System Manager console, select the B5800 Branch Gateway device and click Edit to edit the system configuration for the device. IP Office Manager will be launched on your PC. For more information, see Editing a B5800 Branch Gateway system configuration from System Manager on page 159. 2. In the left navigation pane, click Line. 3. For each digital line, do the following: a. Select the line. b.
Initial branch configuration 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. • On outgoing calls, the short codes used to route the call to a trunk must remove the dialing prefix.
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 branch configuration 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. From the System Manager console, select the B5800 Branch Gateway device and click Edit to edit the system configuration for the device. IP Office Manager will be launched on your PC. For more information, see Editing a B5800 Branch Gateway system configuration from System Manager on page 159. 2. In the left navigation pane, click System. 3.
Initial branch configuration Beginning in B5800 Branch Gateway R6.2, you have the option to leave the Branch Prefix field blank. If you do not configure the Branch Prefix, the native extensions must be defined with the full enterprise number. You are also able to leave the Local Number Length field blank. By default B5800 Branch Gateway systems use 3-digit extension numbering starting from 200. The existing allocated numbers can be changed in bulk using the Tools > Extension Renumber option.
Administering a Session Manager line for each branch Name Range or Default Description and 862 are okay, but 86 and 861 overlap. On calls routed via an Avaya Aura®Session Manager line, the branch prefix is added to the caller's extension number. Beginning in B5800 Branch Gateway R6.2, you have the option to leave the Branch Prefix field blank. If you do not configure the Branch Prefix, the native extensions must be defined with the full enterprise number.
Initial branch configuration Name Range or Default Description frequency of the messages when the Avaya Aura®Session Manager line is currently out of service. Changing the default codec selection About this task By default, all B5800 Branch Gateway IP trunks and extensions use automatic codec negotiation. The default negotiation order is G729(a) 8K CS-ACELP, G711 U-Law 64K, G711 A-Law 64K, and G723.1 6K3 MP-MLQ. G.722 64K is also supported. Note: G.
Administering a Session Manager line for each branch 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.1 6K3 MPACELP MLQ G.711 A-Law G711 A-Law 64K G711 U-Law 64K G729(a) 8K CS- G723.1 6K3 MPACELP MLQ G711 A-Law 64K G.
Initial branch configuration 5. In the Maximum SIP Sessions box, click the up or down arrows to select the number that matches the Maximum SIP Trunk Sessions licensed for the system. 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.
Administering a Session Manager line for each branch 9. In the DTMF Support field, do the following: • If CallPilot is configured as the voicemail system, accept the default setting, RFC2833. • If users will call into the Meeting Exchange conferencing server, select either RFC2833 or Inband. Meeting Exchange does not support digit exchange through out-of band (that is, Info) signaling. 10. Configure the remaining fields as appropriate. See VoIP tab field descriptions on page 149 for more information. 11.
Initial branch configuration 148 Name Description 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 or NRS. Prefix This field is blank by default. This prefix will be added to any source number received with incoming calls. Max Calls The default setting is 10.
Administering a Session Manager line for each branch VoIP tab field descriptions Name Range or Default Description Codec Selection Default = System Default This field defines the codec or codecs offered during call setup. When System Default is selected, the codec list shown matches the codecs set in the system-wide Default Codec Selection (System > Codecs). Fax Transport Support Default = None This option is only selectable if the option Re-Invite Supported is also selected.
Initial branch configuration Name Range or Default Description either RFC2833 or Inband. Meeting Exchange does not support digit exchange through out-of band (that is, Info) signaling. Media Security Default = Disable Advanced Media security is not required. All media sessions (audio, video, and data) will be enforced to use RTP only. This option provides additional media security options. These options are not supported in B5800 Branch Gateway R6.2.
Administering a Session Manager line for each branch Name Range or Default Description 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.
Initial branch configuration Avaya Aura® Session Manager line redundancy In an Avaya Aura® network that includes multiple Avaya Aura® Session Managers for redundancy, the B5800 Branch Gateway system can be configured with a secondary Avaya Aura® Session Manager line. If for any reason the B5800 Branch Gateway system's primary Avaya Aura® Session Manager line goes out of service, the system will automatically attempt to use the secondary Avaya Aura® Session Manager line.
Administering a Session Manager line for each branch Secondary Avaya Aura ® Session Manager line configuration The secondary Avaya Aura® Session Manager line is configured in the same way as the primary Avaya Aura®Session Manager line. The only difference required is to set the SM Address field to the address of the alternate Avaya Aura®Session Manager from the one being used by the primary Avaya Aura® Session Manager line.
Initial branch configuration 3. Click the New icon and select Short Code. 4. Configure the settings as appropriate. See Short Code tab field descriptions on page 154 for more information. Note: To view more information about the system short codes, press F1. In particular, see the description of the Dial short code. 5. Click OK. 6. Select File > Save Configuration. Short Code tab field descriptions Name Description Code Enter the number dialed by users that should be matched to this short code.
Administering a Session Manager line for each branch Name Description Local Features that transfer the caller to Voicemail Pro can indicate the language locale required for prompts. This is subject to the language being supported and installed on the voicemail server. The default is blank. Force Account Code When selected, for short codes that result in the dialing of a number, the user is prompted to enter a valid account code before the call is allowed to continue. The default is Off.
Initial branch configuration thought to be in service. The Reactive setting is used for an Avaya Aura® Session Manager line currently thought to be out of service. • If a response is received and is not a 408, 500, 503 or 504 response, the Avaya Aura® Session Manager line is treated as in service; otherwise the line is treated as being out of service. • If the line is out of service, and call comes from the trunk, the trunks status is changed back to in service.
Enabling branch SIP extension support 8. Click the SIP Registrar tab. 9. Configure the fields on this tab as appropriate. See SIP Registrar tab field descriptions on page 157 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.
Initial branch configuration Name Default Description response is not received within this timeout the registration is failed. 158 Implementing B5800 Branch Gateway for a CS 1000 Configuration Comments? infodev@avaya.
Chapter 10: Managing B5800 Branch Gateways from System Manager This chapter provides tasks that you will use as you configure B5800 Branch Gateways that are managed from System Manager. Editing a B5800 Branch Gateway system configuration from System Manager Before you begin Avaya Aura® System Manager has been set up to launch IP Office Manager. See Setting up System Manager to launch IP Office Manager on page 111.
Managing B5800 Branch Gateways from System Manager specified. If you receive this message, click OK. Then see Setting up System Manager to launch IP Office Manager on page 111 for the procedure to install the B5800AdminLite.exe file on the System Manager server.
About disabling the System Manager administration feature for a B5800 Branch Gateway Note: Do not use IP Office Manager that is connected directly to the B5800 Branch Gateway device to edit users and extensions on systems that are centrally managed from System Manager. Changes made to users and extensions in this way will not be synced back to System Manager.
Managing B5800 Branch Gateways from System Manager Disabling the System Manager administration feature for the branch from System Manager Procedure 1. From the System Manager console, under Elements, click B5800 Branch Gateway. 2. On the B5800 Branch Gateway Element Management page, in the left navigation pane, click Security Configuration. 3. On the B5800 Branch Gateway Security Configuration page, click the radio button for the appropriate branch. 4. Click Edit. 5.
About disabling the System Manager administration feature for a B5800 Branch Gateway b. In the IP Office Manager Preferences dialog box, click the Set Simplified View as default check box to deselect this option c. Click OK. d. Close and restart IP Office Manager. 3. In the Select B5800 window, click the check box for the appropriate system. 4. Click OK. 5.
Managing B5800 Branch Gateways from System Manager 3. In the Preferences tab, click the Set Simplified View as default check box to deselect this option. 4. Click OK. 5. Close IP Office Manager. 6. See Disabling the System Manager administration feature for the branch from System Manager on page 162. Synchronizing B5800 Branch Gateway with System Manager About this task Some configuration changes cannot be synced with System Manager.
Synchronizing B5800 Branch Gateway with System Manager must first disable System Administration for the branch and then enable System Administration for the branch after you make your configuration changes. Then you must synchronize those changes with System Manager. There are some configuration changes that cannot be synchronized with System Manager. Those tasks should not be performed locally through IP Office Manager for branches that are centrally managed by System Manager.
Managing B5800 Branch Gateways from System Manager 166 Implementing B5800 Branch Gateway for a CS 1000 Configuration Comments? infodev@avaya.
Chapter 11: Session Manager Configuration This chapter provides procedures to configure Avaya Aura® Session Manager to support calls to and from B5800 Branch Gateway systems. Avaya Aura® System Manager R6.2 is used to administer Session Manager. Perform the following procedures: 1. View the SIP domains for which the Session Manager provides call management. Multiple domains can be listed. See Viewing the SIP domains on page 168. 2. Identify logical and/or physical locations where SIP entities reside.
Session Manager Configuration Viewing the SIP domains The domain for which the Session Manager is authoritative was added when Session Manager was initially configured for the B5800 Branch Gateway system. The domain name set in the B5800 Branch Gateway system's Session Manager line configuration (see Adding an Avaya Aura Session Manager line on page 146) should match one of the entries that is listed on the Domain Management page. 1. On the System Manager console, under Elements, click Routing. 2.
Creating adaptations 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. 14. In the Notes field, enter notes about this location pattern, as appropriate. 15. Click Commit. Creating adaptations Occasionally calls to or from the branch may require digit conversion in order to ensure correct routing. For example, reinserting an external dialing prefix.
Session Manager Configuration 10. In the Time Zone drop-down box, select the time zone for the location. 11. For the Override Port & Transport with DNS SRV check box, accept the default setting, unchecked. 12. 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. 13. In the Credential Name field, accept the default setting, blank. 14. In the Call Detail Recording field, accept the default setting. 15.
Creating time ranges This check box must be checked. If it is not checked, calls from the associated SIP Entity 2 will be denied by Session Manager. 9. In the Notes field, enter notes regarding this entity link, as appropriate. 10. 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, under Elements, click Routing. 2. In the left navigation pane, click Dial Patterns. 3. On the Dial Patterns page, click New to create a new dial pattern. 4. 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. 5.
Chapter 12: Voicemail configuration This chapter provides the procedures to configure the voicemail system that the B5800 Branch Gateway will use. If Embedded Voicemail or Standalone Voice Mail are configured, see one of the following documents for information on how to configure user mailboxes, hunt group mailboxes, and auto attendants: • Implementing Embedded Voicemail for B5800 Branch Gateway Release 6.2, document number 18-604098 • Implementing Standalone Voice Mail for B5800 Branch Gateway Release 6.
Voicemail configuration announcements to waiting calls. Note that for this configuration, Embedded Voicemail licenses are required. • CallPilot — The B5800 Branch Gateway system can be configured to use CallPilot as its voicemail server when Session Manager is used as the core SIP router. See Configuring B5800 Branch Gateway to use CallPilot for voicemail on page 179 for more information.
Configuring Standalone Voice Mail 9. In the Reception/Breakout (DTMF 0) drop-down box, select the number to which a caller is transferred if they press 0 while listening to the mailbox greeting rather than leaving a message. Do one of the following: a. To configure Park and Page for this DTMF breakout, select Park & Page and then do the following: i. In the Paging Number drop-down box, select the appropriate hunt group or user extension. ii.
Voicemail configuration components are provided on the IP Office Applications DVD. For more information, see Implementing Standalone Voice Mail for the Avaya B5800 Branch Gateway, document number 18-604088. Procedure 1. From the System Manager console, select the B5800 Branch Gateway device and click Edit to edit the system configuration for the device. IP Office Manager will be launched on your PC.
Configuring B5800 Branch Gateway to use Avaya Aura Messaging for voicemail iii. In the Retry timeout field, use the up and down arrows to set the amount of time to elapse before the page is repeated. The time is set in 15–second increments. b. To configure Centrex Transfer for this DTMF breakout, select Centrex Transfer and then enter the transfer number in the Transfer Number field. c.
Voicemail configuration 3. Click the Voicemail tab. 4. In the Voicemail Type drop-down box, select Avaya Aura Messaging. Note: Fields applicable to this mode of voicemail support remain enabled. 5. To enable the local B5800 Branch Gateway system features for Embedded Voicemail auto attendants and announcements, in the Use embedded for AA and Announcements drop-down box, select the appropriate embedded voicemail. The announcements are those that the callers hear when the call in on hold.
Configuring B5800 Branch Gateway to use CallPilot for voicemail digits are not automatically sent. Instead, the caller will dial the user's mail box number to manually send the required DTMF digits to access the mailbox. 9. 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.
Voicemail configuration launched on your PC. For more information, see Editing a B5800 Branch Gateway system configuration from System Manager on page 159. 2. In the left navigation pane, click System. 3. Click the Voicemail tab. 4. In the Voicemail Type drop-down box, select Call Pilot. Note: Fields applicable to this mode of voicemail support remain enabled. 5.
Configuring B5800 Branch Gateway to use CallPilot for voicemail Note: The Enable Voicemail Instructions Using DTMF check box and associated Call Pilot PSTN Number field are disabled in R6.2. B5800 Branch Gateway does not access the CallPilot system over the PSTN when the Session Manager line is down. 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.
Voicemail configuration Modular Messaging and Avaya Aura Messaging PSTN Fallback When the branch is configured to use Modular Messaging over SIP or Avaya Aura Messaging for its voicemail services, that configuration includes setting an internal Modular Messaging or Avaya Aura Messaging number (800700 for the following example) for calls to Modular Messaging or Avaya Aura Messaging which are automatically routed via the Session Manager line.
Adding an overriding short code 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 or AAM PSTN Number and attempt to route it to the SM Line which we know is out of service if the MM PSTN Number or AAM 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 or AAM PSTN Number. 4. To add a short code, click the Add... button. 5.
Voicemail configuration to those calls. 7. Click OK. 8. Select File > Save Configuration. Uploading an auto attendant audio file About this task You are able to upload and convert audio files to System Manager that can be used in the B5800 Branch Gateway system configuration auto attendant feature. Once uploaded, from IP Office Manager you are able to select the audio files from the Auto Attendant page.
Uploading an auto attendant audio file 5. Click the Upload button. The voice file is uploaded to System Manager in the .c11 format that is required for Embedded Voicemail on B5800 systems. The file is automatically converted from the .wav format to the .c11 format. 6. When finished, click the Done button.
Voicemail configuration 186 Implementing B5800 Branch Gateway for a CS 1000 Configuration Comments? infodev@avaya.
Chapter 13: User administration This chapter provides the procedures to add distributed users to B5800 Branch Gateway and Avaya Aura® System Manager. Adding distributed users to System Manager About this task When you add a distributed user to System Manager, you must configure a B5800 Branch Gateway Profile on System Manager. Procedure 1. On the System Manager console, under Users, click User Management. 2. In the left navigation pane, click Manage Users. 3. On the User Management page, click New. 4.
User administration 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 Title field, enter the user's title if applicable. l. In the Language Preference drop-down box, select the appropriate language. m. In the Time Zone drop-down box, select the user's time zone. n. In the Employee ID field, enter the user's employee ID. o.
Editing the B5800 Branch Gateway Endpoint Profile for a user When you select a template, the Set Type field is automatically populated based on the template selected. e. To change other parameters such as call appearances or feature buttons for this user, click the Endpoint Editor button and do the following: i. Update the fields as appropriate. ii. Click Save to save your changes. iii. Click Exit to exit the Endpoint Editor. This updates parameters for this user.
User administration 5. Click the Communication Profile tab to expand that section. 6. Expand the Communication Address section. 7. Expand the B5800 Branch Gateway Endpoint Profile. 8. To change the extension for this user, in the Extension field enter the appropriate extension. 9. To apply a different template to this user, in the Template drop-down box, select the appropriate template. 10. To change other parameters for this user, click the Endpoint Editor button.
Chapter 14: Managing license files with PLDS PLDS Overview The Avaya Product Licensing and Delivery System (PLDS) provides customers, Avaya Partners, distributors, and Avaya Associates with tools for managing license entitlements and electronic delivery of software and related license files. Using PLDS, you can perform operations such as license activations, license upgrades, license moves, and software downloads. Installation software packages for Avaya products are available as ISO files on PLDS.
Managing license files with PLDS Examples of license management tasks that you can perform in PLDS include: • Adding more license entitlements to an existing activation • Upgrading a license file to a new major release • Moving license entitlement activations between license hosts • Regenerating a license file with an new host ID Registering for PLDS Procedure 1. Go to the Avaya Product Licensing and Delivery System (PLDS) Web site at https:// plds.avaya.com.
About license activation is the Feature Key Serial Number printed on the B5800 Branch Gateway System SD card. For more information, see Licensing on page 16. When license entitlements are activated, PLDS generates Activation Records containing the activation information and License/Key. Types of license activation Types of activation include: • Regular activation: where license entitlements are activated to generate Activation Records.
Managing license files with PLDS 3. In the LAC(s) field of the Quick Activation section, enter the LAC that you received in an e-mail message. Note: If you do not have an e-mail message with your LAC, follow the steps in the Searching for Entitlements section and make a note of the appropriate LAC from the LAC column. Note: The Quick Activation automatically activates all license entitlements on the LAC.
Searching for license entitlements file. Install each license file on the WebLM server associated with the License Host. Note: For B5800 Branch Gateway, when using WebLM to manage licensing, a single license file is generated for all B5800 Branch Gateways in the multiple branches. A single license file is not generated for each branch or application. If you are not using WebLM to manage the licenses, individual license files are installed on a single branch at a time, where the branch is the License Host.
Managing license files with PLDS b. Enter the name or several characters of the name and a wildcard (%) character. c. Click Search Companies. d. Select the desired company name from the list of options. Tip: You can use a wildcard (%) character if you do not know the exact name of the company you are searching for. For example, if you enter Av%, the system searches for all the company names starting with the letter Av. You can enter a wildcard character at any position in the search criteria. 5.
Moving activated license entitlements Moving activated license entitlements Before you begin Host ID or License Host name of the move from/to License Host. About this task Use this functionality to move activated license entitlements from one License Host to another. You can chose to move all or a specified quantity of license entitlements.
Managing license files with PLDS Alternatively, you can click Add a License Host to select an existing License Host. 7. Validate the Registration Detail and click Next. 8. Enter the License Host Information. The Host ID is the MAC address of the server hosting the WebLM server. The Host ID is obtained from the Server Properties page of the WebLM server where the license file will be installed. Note: If you are not using WebLM to manage the licenses, you would enter the Host ID of the B5800 Branch Gateway.
Regenerate License files Regenerate License files Use this functionality to regenerate the license file on a selected License Host. During the regeneration process, you can only modify host ID information. Regenerating a license file 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 Activation > Regeneration from the Home page. 4. Search License Activations to Regenerate.
Managing license files with PLDS branches. A single license file is not generated for each branch or application. If you are not using WebLM to manage the licenses, individual license files are installed on a single branch at a time, where the branch is the License Host. For more information, see Licensing on page 16. 200 Implementing B5800 Branch Gateway for a CS 1000 Configuration Comments? infodev@avaya.
Chapter 15: Standalone SAL Gateway for remote service Avaya Client Services (ACS) 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 79 for a description of these applications.
Standalone SAL Gateway for remote service Note: For B5800 Branch Gateway upgrades and Embedded File Management, you must access Manager that is installed on a PC that resides within the customer network. • System Status Application System Status 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 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.
Chapter 16: Additional system procedures This chapter provides procedures for ongoing maintenance and management of your system, such as system shutdown and reboot, replacing components, and system backup. 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. By default the B5800 Branch Gateway system name is set to match its MAC address.
Additional system procedures 10. Click OK. 11. Select File > Save Configuration. 12. Reboot the system. Default passwords Do not change any other settings than those described below until you have read and understood the B5800 Branch Gateway Security Mode feature. See the IP Office Manager online help for more information. From IP Office Manager, click the Help button in the lowerright section of the window. Then in the left navigation pane, in the Contents tab, select Security Mode.
Default passwords The list shows the service user accounts that can access the system configuration. The default service users Administrator, Manager and Operator each use the same value (Administrator, Manager and Operator) as their password. 12. For each of these service users: a. b. c. d. Click on the service user name. In the Service User Details tab, click on Change and enter a new password. Click OK. Click OK. 13. Click on General.
Additional system procedures System shutdown B5800 Branch Gateway systems can be shut down in order to perform maintenance. The shut down can be either indefinite or for a set period of time after which the B5800 Branch Gateway will automatically reboot. During the shut down process, the current configuration in the control unit's RAM memory is copied to the System SD card. Warning: • A shutdown must always be used to switch off the system.
System shutdown 5. Click OK. Shutting down the system using the System Status application Procedure 1. Start System Status and access the system status output. 2. In the navigation panel select System. 3. At the bottom of the screen select Shutdown System. 4. Select the time duration for the shutdown or indefinite. 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.
Additional system procedures The control unit will shutdown with the restart timer set to 10 minutes. Rebooting the system About this task You can use Manager to reboot an B5800 Branch Gateway system. Procedure 1. Start Manager. 2. Select File > Advanced > Reboot. 3. In the Select B5800 window, select the B5800 Branch Gateway system. 4. Enter your user name and password. 5. In the Reboot window, do one of the following: • Select Immediate to reboot the system immediately.
About changing components About changing components Except for memory cards, cards and external expansions modules must only be removed and added to an B5800 Branch Gateway system when the system is turned off. See Memory card removal on page 261 and System shutdown on page 208 for more information. Note that for extension ports, by default both an extension entry and a user entry are configured in the system. Extension entries can be deleted without deleting the corresponding user entry.
Additional system procedures Replacing a component with one of higher capacity About this task If you are replacing a component with one of the same type but with higher capacity, 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 208. 2. Remove the card or external expansion module.
About changing components 4. Restart the B5800 Branch Gateway system. 5. Use Manager to delete the trunks or extensions/users in the configuration that are no longer supported by the replacement component. Replacing a component with one of a different type About this task If you are replacing a component with one of a different type, you must perform two procedures; one to permanently remove the component and then one to add the component. Procedure 1. Remove the existing component.
Additional system procedures Permanently removing a component About this task If you are permanently removing a component, 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 208. 2. Remove the card or external expansion module. 3. Restart the B5800 Branch Gateway system. 4.
About changing extension numbers 8. At each of the extensions, dial the log out short code set on the B5800 Branch Gateway system. The default is *36. 9. If either user is configured for Forced Login, they will have to complete the login process at their new extension using their Login Code. About changing extension numbers The default configuration for a new B5800 Branch Gateway system numbers each extension in sequence, going by module and port order, starting from 201.
Additional system procedures 5. Send the configuration back to the B5800 Branch Gateway and select the appropriate settings for the reboot. Changing a user's extension number Procedure 1. Select User. 2. Select the relevant user. 3. On the User tab, in the Extension field, change the extension number to the new number. 4. Click on another field. If an error warning appears it is most likely due to a conflict with an existing use of that extension number.
Creating a backup of the system configuration using IP Office Manager 9. Click to revalidate the configuration and check that there are no conflicts between users and associated extensions. 10. Send the configuration back to the B5800 Branch Gateway and select appropriate settings for the reboot. Creating a backup of the system configuration using IP Office Manager About this task Before performing an upgrade, ensure you have a current backup of the B5800 Branch Gateway system configuration.
Additional system procedures Manager. See Synchronizing B5800 Branch Gateway with System Manager on page 164 for more information. Procedure 1. From the System Manager console, under Elements, select B5800 Branch Gateway. 2. In the left navigation pane, click Backup and Restore. 3. On the B5800 Branch Gateway Backup and Restore page, select the B5800 Branch Gateway device for which you want to create a backup. 4. Click Backup. 5. Do one of the following: • Click Now to run the backup job now.
Upgrades using IP Office Manager one that started the upgrade process. Ensure that only one copy of Manager is running when upgrading an B5800 Branch Gateway system. • Other B5800 Branch Gateway applications — Upgrading the core software of the B5800 Branch Gateway control unit may require upgrades to associated software. Typically B5800 Branch Gateway is compatible with the previous release of most B5800 Branch Gateway applications.
Additional system procedures memory is still insufficient, the option is offered to either do an unvalidated upgrade or cancel. During a validated upgrade, the bin files required are transferred to the system and stored in temporary memory. The backup system files and upload system files actions are performed. Once all file transfers are completed, the upgrade wizard promps whether it is okay to proceed with the upgrade process. Select Yes to continue.
External output port (EXT O/P) 4. Click Restore. 5. On the B5800 Branch Gateway Restore page, do one of the following: • Click System Configuration to restore the respective system configurations available in System Manager to the B5800 Branch Gateway device. The configuration you restore is the latest configuration available in System Manager. • Click User to restore the respective users from System Manager to the B5800 Branch Gateway device.
Additional 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 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. d.
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 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 Quality: 168KB/s • M
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 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. inet-address-mib.
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 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 About this task Use this procedure to configure the SAL Gateway as a trap destination.
Additional system procedures 9. In the Location field, enter location information as appropriate. 10. Click the Alarm tab. 11. Click Add. 12. In the New Alarm section, do the following: a. Click the Trap option button. 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.
DTE port maintenance on the control units can be used for system maintenance and connection of serial terminal adaptors. An asynchronous terminal program such as HyperTerminal is also required. Configure this for operation via a PC serial port, as follows: Bits per second 38,400 Parity None Flow Control None Data bits 8 Stop Bits 1 Settings > Emulation TTY DTE cables These cables are used for system maintenance and diagnostics under Avaya guidance.
Additional system procedures These procedures should be performed from a PC with a fixed IP address, directly connected to the B5800 Branch Gateway control unit and with the B5800 Branch Gateway system disconnected from any network. The control unit IP address will default to 192.168.42.1. Important: Do not perform any of these processes unless absolutely necessary. The configuration settings can be returned to the default settings using Manager by selecting File > Advanced > Erase Configuration command.
DTE port maintenance 9. Use Manager to edit and then upload an old configuration file or receive and edit the system's now defaulted configuration. Erasing the configuration and security settings via the boot loader About this task This procedure erases the system's configuration settings and the security settings and resets them to the default settings. Before you perform this procedure, be sure you have a current backup of the system configuration.
Additional system procedures 12. Use Manager to edit and then upload an old configuration file or receive and edit the system's now defaulted configuration. 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.
DTE port maintenance 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 232. 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.
Additional system procedures The procedure should be performed from a PC with a fixed IP address, directly connected to the B5800 Branch Gateway control unit and with the B5800 Branch Gateway system disconnected from any network. During the process, the control unit's IP address may default 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.
DTE port maintenance Ensure that the DTE port settings are configured as described in RS232 DTE port settings on page 232. Within a HyperTerminal session, the current settings are summarized across the base of the screen. 9. Enter AT (upper case). 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.
Additional system procedures 9. Arrange the program windows so that the terminal program and Manager TFTP log are visible at the same time. 10. Switch off power to the control unit. 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.
DTE port maintenance Press Duration (seconds) CPU LED Action Summary erasing the operational firmware on page 237 for more information. Over 40 Flashing green None None Creating a WAN link About this task This procedure is a high level procedure for creating a data link from Site A to Site B via the WAN ports. For this example the IP address is 192.168.43.1. Procedure 1. At Site A, on IP address 192.168.43, create a normal service.
Additional system procedures 6. At Site B, on IP address 192.168.43, repeat steps 1 through 5 but alter the details to create a route from Site B to Site A. 242 Implementing B5800 Branch Gateway for a CS 1000 Configuration Comments? infodev@avaya.
Chapter 17: SD card management There are two SD card slots in the control unit. They are labeled System SD and Optional SD. Note: For B5800 Branch Gateway, the System SD card must be a B5800 Branch Gateway System SD card. You cannot use an IP Office SD card in the System SD card slot on a B5800 Branch Gateway device. For more information, see “B5800 Branch Gateway System SD card” under System components on page 20. System SD card slot • An Avaya System SD card must be present in this slot at all times.
SD card management Optional SD card slot • A card does not have to be present in this slot for normal B5800 Branch Gateway operation. The slot can be used for various maintenance actions. • A card with updated B5800 Branch Gateway software or configuration can be inserted into the Optional SD card slot and those files are then transferred to the System SD card in order to upgrade the B5800 Branch Gateway system.
Procedure Description Manage System System Minut r Status Phone es Manager on page 259 Viewing the card contents on page 250 View the folders and files on the control unit memory cards. – – – The following procedures can be performed on cards in an SD card reader on a PC running Manager. Formatting an SD card on page 248 Reformat a card for B5800 Branch Gateway use without removing the Feature Key serial number. – 1 – 15 Caution: This process will erase all existing files on the card.
SD card management • dynamic — contains files used by the B5800 Branch Gateway and retained through a reboot of the B5800 Branch Gateway system. • temp — contains temporary files used by the B5800 Branch Gateway and not retained through a reboot of the B5800 Branch Gateway system. The Optional SD card can contain a similar set of folders as the System SD card. The Optional SD card folders are used as an additional backup or they can be used as the source for upgrading the contents of the System SD card.
Booting from the SD cards - If a configuration file is not present, use the non-volatile memory copy unless the reboot is as a result of a default system command. • If the control unit booted using binary files from its non-volatile memory, it will also load the configuration copy from that location. - It will indicate a boot alarm (see Boot alarms below). - It will attempt to restore the firmware file in the System SD card /primary folder using the copy in its non-volatile memory.
SD card management About creating a B5800 Branch Gateway SD card The procedures in this section are for B5800 Branch Gateway SD cards for use in the System SD card slot. They can also be applied to non-Avaya SD cards for use in the Optional SD card slot. For the System SD card slot, only Avaya SD cards with a Feature Key should be used. The card must be in the following format: SDHC 4GB minimum Class 2+. Single partition FAT32 format.
About creating a B5800 Branch Gateway SD card The status bar at the bottom of Manager displays the progress of the formatting process. 5. When the formatting is complete, load the B5800 Branch Gateway folders and files onto the card from the Manager PC. See Recreating an SD card on page 249. Formatting a System SD card using the System Status application Procedure 1. Start the System Status application and access the System Status output. 2.
SD card management Note: Do not remove the SD card. Removing the SD card will interrupt the upgrade. 2. Select File > Advanced > Recreate IP Office SD Card > Avaya B5800 Branch Gateway. 3. Browse to the card location and click OK. Manager starts creating folders on the SD card and copying the required files into those folders. This process takes approximately 15 minutes. Do not remove the SD card until Manager shows a message that the recreation has finished.
About backing up the System SD card Note: The backup, restore, and copy operations will not be performed if the destination card has insufficient space for the files being copied. Backing up the primary folder using Manager About this task This procedure copies the contents of the primary folder on the System SD card to the backup folder on the System SD card. Files with matching file names are replaced. This procedure takes approximately 6 minutes. Procedure 1. Start Manager. 2.
SD card management Backing up the primary 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. Enter your B5800 Branch Gateway user login code. 3. From the menu select Memory Card. 4. Select System Backup.
About restoring from the backup folder the process has been completed, the B5800 Branch Gateway system is restarted. Restoring from the backup folder 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. At the bottom of the screen select Restore System Files. The contents of the backup folder on the System SD card are copied to the primary folder on the System SD card.
SD card management About backing up to the Optional SD card Backing up to the Optional SD card copies all files on the System SD card to the Optional SD card. This includes contents of the primary folder, backup folder, and embedded voicemail files including message files. Matching files and folders on the Optional SD card are overwritten. Any files already copied that change while this process is running are not recopied.
About restoring from the Optional SD card 5. At the bottom of the screen select 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 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).
SD card management Warning: This procedure will cause the B5800 Branch Gateway system to be restarted, disconnecting any current calls and services in progress. Restoring a configuration file from 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 > Upgrade Configuration. The configuration file config.
About restoring from the Optional SD card takes a few seconds. When the process has been completed, the B5800 Branch Gateway system is restarted. Restoring software files from 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 > Upgrade Binaries.
SD card management System upgrade using the System SD card In addition to using the upgrade wizard (see Using the upgrade wizard on page 219), control units can be upgraded by loading the required firmware files onto the System SD card and rebooting the system. There are several ways to load the required firmware onto the System SD card as described in the table below.
System upgrade using the System SD card Upgrading remotely using Manager About this task This procedure copies all system files not present or of a different version compared to those already present on 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.
SD card management This procedure overwrites the software files on the card with the files available in Manager. It will not affect any other files, for example the configuration file. This process takes approximately 15 minutes. 3. Reinsert the card into the System SD card slot on the control unit. 4. Using Manager, select File > Advanced > Reboot. 5. In the Select IP Office window, select the appropriate system and click OK. 6. Select the type of reboot you want to perform and click OK.
Memory card removal • See Restoring software files from the Optional SD card using a system phone on page 257. Memory card removal 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.
SD card management Shutting down a memory card using a system phone About this task To shut down a memory card using a system phone, you must be administered as a System Phone user. You can shut down a memory card using a 1400, 1600, or 9600 series phone. Your Login Code is used to restrict access to some system administration functions on the phone. Procedure 1. Select Features > Phone User > System Admin. 2. Enter your B5800 Branch Gateway user login code. 3. Select Memory Card. 4.
Memory card startup Memory card startup Reinserting a memory card into a system that is already switched on will automatically restart card operation. However, if the card has been shutdown but not removed, it can be restarted without requiring a reboot. Starting up a memory card using Manager About this task Use this task to restart a memory card without removing and reinserting it. Perform this task using IP Office Manager that is installed on a PC for the branch.
SD card management 4. At the bottom of the window, click Startup. Starting up a 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.
Chapter 18: 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 B5800 Branch Gateway for a CS 1000 Configuration October 2012 271
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 276 Implementing B5800 Branch Gateway for a CS 1000 Configuration Comments? infodev@avaya.
Appendix A: 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 285. 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.
Egress ports for B5800 Branch Gateway and SIP phones 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 B5800 Branch Gateway for a CS 1000 Configuration October 2012 287
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. 288 Implementing B5800 Branch Gateway for a CS 1000 Configuration Comments? infodev@avaya.
Appendix B: B5800 Branch Gateway call flows Calls from local extensions (i.e. deployed in the distributed branch user 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 290 Implementing B5800 Branch Gateway for a CS 1000 Configuration Comments? infodev@avaya.
Appendix C: 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 291 — External calls at a branch site can be rerouted to be dialed out at another site.
Branch PSTN call routing examples Routing B5800 Branch Gateway calls — example About this task 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 described in Centralized call control on page 291, 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 or AAM PSTN Number and attempt to route it to the SM Line which we know is out of service if the MM PSTN Number or AAM 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 or AAM 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 291) has been configured for certain calls, loss of the Avaya Aura®Session Manager line connection will impact making those calls.
PSTN trunk fallback a headquarters PSTN number that can be dialed to report the Avaya Aura® Session Manager line issue. See Branch PSTN override on page 294 for more information. • Provide PSTN trunk fallback within the branch configuration. See Configuring PSTN trunk fallback on page 297. 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 300 Implementing B5800 Branch Gateway for a CS 1000 Configuration Comments? infodev@avaya.
Appendix D: Authorization codes Authorization codes are not shown by default. IP Office Manager must be modified in order to support authorization codes. Each authorization code is associated with a particular user or user rights set. The user or users associated with the user rights can then dial numbers which are set to trigger forced authorization code entry. Once a code is entered, the short code settings of the user or user rights with which the code is associated are used to complete the call.
Authorization codes ARS Table Authorization Codes • 044N / . / Dial Allows calls to cell phone numbers. • 044N / . / Dial Allows calls to cell phone numbers. • 01N / . / Busy Blocks calls to long distance numbers. • 01N / . / Busy Allows calls to long distance numbers. • ? / . / Busy Block any other calls that require an authorization code. • ? / . / Busy Block any other calls that require an authorization code.
Force authorization codes 3. Restart Manager and load a configuration. Force authorization codes There are two methods to force a user to enter an authorization code in order to complete dialing an external call. • To Force Authorization Codes on All External Calls A user can be required to enter an authorization code for all external calls. This is done by selecting Force Authorization Code (under User > Telephony > Supervisor Settings).
Authorization codes Authorization code configuration settings • Authorization Code: The digits used for the authorization code can be up to 12 digits in length. Each code must be unique. Wild cards are not usable with authorization codes. • User Rights: This field is used to select the user right with which the authorization code is associated. The authorization code can then be used to authorize calls made by users currently associated with that set of user rights.
Appendix E: Recommended courses for Avaya B5800 Branch Gateway training This appendix lists recommended courses for B5800 Branch Gateway, Session Manager, System Manager, and Communication Manager. Recommended courses Table 1: B5800 Branch Gateway Type Code Course title Delivery Duration (hours) First offering Existing 2U00021O Avaya Branch Gateway — eLearning What Sales needs to know for the first conversation 0.
Recommended courses for Avaya B5800 Branch Gateway training Table 2: Avaya Aura ® Session Manager and System Manager Type Code Course title Delivery Duration (hours) First offering New 5U00106W Avaya Aura ® System Manager Overview WBT course 1 Available now New 5U00105W Avaya Aura ® Session Manager Overview WBT course 4.
Recommended courses Type Code Course title Delivery Duration (hours) First offering Existing 3101 Avaya Aura ® Communication ACSS Manager and CM Messaging Proctored - Embedded Maintenance Exam and Troubleshooting Exam 1.
Recommended courses for Avaya B5800 Branch Gateway training 308 Implementing B5800 Branch Gateway for a CS 1000 Configuration Comments? infodev@avaya.
Appendix F: T7000 and M7000 Series Digital Deskphones The Business Series Terminals (BST) T7000 and M7000 Series Digital Deskphones offer a feature-rich portfolio with enhanced capabilities that provide telephony solutions for a broad landscape of users, from high-volume call positions and executives to low-intensive users and small workgroups.
T7000 and M7000 Series Digital Deskphones B5800 Branch Gateway advanced features such as Visual Voice, feature menus, and self labeling keys (9500 telephones only). Features available on the T7000 and M7000 Series Digital Deskphones On the B5800 Branch Gateway the following features are available on the T7000 and M7000 Series Digital Deskphones using the feature key and the Feature Access Codes inherited from Norstar and BCM.
Features available on the T7000 and M7000 Series Digital Deskphones Feature Access Codes Description F75 Call Pickup Group F76 Call Pickup Extn F77 Call Timer F85 Do Not Disturb, F#85 cancel F802 Group Listen, F#802 cancel F803 Show Time F812 Call Log F981 Enter Voice Mail System (same as F65) AUDIO ONLY Implementing B5800 Branch Gateway for a CS 1000 Configuration October 2012 311
T7000 and M7000 Series Digital Deskphones 312 Implementing B5800 Branch Gateway for a CS 1000 Configuration Comments? infodev@avaya.
Appendix G: 1100 Series and 1200 Series IP Deskphones The 1100 Series and 1200 Series SIP 4.3 deskphones are supported on B5800 Branch Gateway using the SIP protocol. When used with BCM systems, the phones use the UNIStim protocol. Because of the different protocols, the user interface can be slightly different when the phones are used with B5800 Branch Gateway.
1100 Series and 1200 Series IP Deskphones • SIP Software for Avaya 1100 Series IP Deskphones–Administration , document number NN43170– 600 • SIP Software for Avaya 1200 Series IP Deskphones–Administration , document number NN43170– 601 Features available on the 1100 Series and 1200 Series SIP 4.3 phones On the B5800 Branch Gateway, the following features are available on the 1100 Series and 1200 Series SIP 4.3 phones.
Features available on the 1100 Series and 1200 Series SIP 4.
1100 Series and 1200 Series IP Deskphones 316 Implementing B5800 Branch Gateway for a CS 1000 Configuration Comments? infodev@avaya.
Glossary BCM Business Communications Manager; a system that includes hardware and software to provide private network and telephony management capability to small and meduim-sized businesses. BEM Business Element Manager; the primary management application for managing Business Communications Systems. It encompasses telephony programming, backup management, software update management, and log management.
Native extension Native extension This term is used to describe extensions that get their call services from the branch site and operate in the Distributed Branch user model. A native extension is also referred to as a local extension. NCM Network Configuration Manager; a server-based management application that provides configuration management tools to manage a network of Business Communications Manager devices.
Index Numerics Bulk importing of devices ..........................................128 1100 Series and 1200 Series SIP 4.3 phones ..........313 C A Cable ..........................................................................50 access requirements ............................................50 clearance requirements .......................................50 Cables ........................................................................44 Maximum cable distances ....................................
creating a backup of the system configuration using System Manager .........................................217 Creating a software library ........................................100 creating a system template .......................................131 creating a user template ...........................................133 CS 1000 and B5800 Branch Gateway deployments . .33 CS 1000 configuration considerations ........................35 D Default codec selection ............................................
wall mounting .......................................................67 installation checklist ....................................................55 installing a service pack .............................................95 Installing IP Office Manager Lite from the System Manager server to a PC ...............................113 installing the license file on the System Manager WebLM server ...........................................................115 IP Address ...........................................
related documents ......................................................29 related resources ........................................................30 Avaya Mentor videos ...........................................30 remote software library .........................................96, 97 remote software library for B5800 upgrades ..............96 Remotely forcing a BST phone to return to default settings ..........................................................92 Renumber extensions ......................
VoIP tab field descriptions ........................................149 V videos .........................................................................30 Avaya Mentor .......................................................30 Voice compression channels ......................................46 Voicemail considerations ............................................39 Voicemail operation ..................................................173 Voicemail options ...................................................
