Avaya B5800 Manuel d'utilisateur

Naviguer en ligne ou télécharger Manuel d'utilisateur pour Passerelles/contrôleurs Avaya B5800. Avaya B5800 User's Manual Manuel d'utilisatio

  • Télécharger
  • Ajouter à mon manuel
  • Imprimer
  • Page
    / 342
  • Table des matières
  • MARQUE LIVRES
  • Noté. / 5. Basé sur avis des utilisateurs

Résumé du contenu

Page 1 - November 2011

Implementing the Avaya B5800 BranchGatewayRelease 6.118-603853Issue 5November 2011

Page 2

Viewing the card contents...260A

Page 3

4. Select File > Close Configuration.Using Provisioning and Installation Manager to deliver license filesto the branchesBefore you beginLicense fil

Page 4

8. Click Next.9. On the Import Licenses Wizard page, choose one of the following:• To select a mapping file, click the Select Mapping File option butt

Page 5 - Contents

a) Click the Full execution option button.b) Click the Ignore Warnings check box to deselect it so that warnings are notignored during validation.15.

Page 6

Note:The license file name is comprised of the host ID of the SD card followed by_HID.xml, for example 111306312781_HID.xml. The host ID is the Featu

Page 7

9. Click OK.10. Select File > Save Configuration.Disabling unused trunksAbout this taskEach B5800 Branch Gateway trunk card provides a fixed number

Page 8

Digital trunk clock sourceAbout this taskDigital trunks require the telephone system at each end of the trunk to share a clock signal toensure synchro

Page 9

Setting a trunk clock quality settingAbout this taskProcedure1. Start Manager and connect to the B5800 Branch Gateway system.2. In the left navigation

Page 10

Procedure1. Start Manager and connect to the B5800 Branch Gateway system.2. In the left navigation pane, click Line.3. For each line enter the prefix.

Page 11

• International Prefix: 900• Country Code: 44Number Received Processing Resulting Number+441707362200 Following rule 1 above, the +is replaced with th

Page 12

• See Changing the default codec selection on page 112. Use this procedure to set thepreferred order for codec negotiation. This can be done as a syst

Page 14 - PSTN trunking configurations

7. Click OK.8. Select File > Save Configuration.The Send Configuration window appears and the Configuration Reboot Mode is setto Immediate. Do not

Page 15 - Centralized management

System tab field descriptionsName Range or Default DescriptionBranch Prefix Range = 0 to 999999999 This number is used toidentify the B5800 BranchGate

Page 16 - Licensing

Name Range or Default Descriptionin order to check the status ofline. This setting controls thefrequency of the messageswhen the AvayaAura®Session Man

Page 17 - SIP Trunk Sessions license

The Send Configuration window appears and the Configuration Reboot Mode is setto Immediate. Do not change the reboot mode.Automatic codec preference s

Page 18 - System components

To see the Maximum SIP Trunk Sessions licensed for the system, in the leftnavigation pane, select PLDS License.6. Click OK.7. Select File > Save Co

Page 19

Session Manager tab field descriptionsName DescriptionLine Number This value is automatically assigned byB5800 Branch Gateway and should beunique for

Page 20 - Overview

Name DescriptionNetwork Configuration These settings are fixed to TCP using sendand receive ports 5060.VoIP tab field descriptionsName Range or Defaul

Page 21 - Supported telephones

Name Range or Default DescriptionDTMF Support Default = RFC2833 This setting is used to selectthe method by which DTMFkey presses are signaled tothe r

Page 22

Name Range or Default Descriptionchange the characteristics ofthe session, for examplewhen the target of anincoming call or a transferdoes not support

Page 23 - Software applications

The B5800 Branch Gateway system sends regular OPTION messages to both Avaya Aura®Session Manager lines in order to check their in-service or out-of-se

Page 24 - Supported country locales

12 Implementing the Avaya B5800 Branch Gateway November 2011

Page 25

Setting up outgoing call routingAbout this taskFor calls from extensions on the B5800 Branch Gateway system to other numbers within thenetwork, system

Page 26 - Training

Short Code tab field descriptionsName DescriptionCode Enter the number dialed by users that shouldbe matched to this short code. Use Xwildcards for an

Page 27 - Web sites

extension number. If there is no matching extension number, the call is targeted to anymatching system short code.Incoming calls to a branchIncoming c

Page 28 - Revision history

Chapter 7: Initial configuration for aDistributed BranchThis chapter provides initial configuration tasks required for each B5800 Branch Gateway bran

Page 29 - Chapter 2: Planning

# Description Section8 Set the branch prefix and localnumber length for the extensionnumbering.See Setting the branch prefix and localnumber length fo

Page 30 - Dial plan example

# Description Section18 Create an entity link.• For Session Manager 6.1, see Creatingentity links on page 152.• For Session Manager 6.0, see Creatinge

Page 31 - Voicemail considerations

license file names are based on the Feature Key (FK) serial number on the SD cards. See Creating a mapping file on page 129 for more information. Note

Page 32 - Planning

Deleting the PLDS license file from the branchProcedure1. Start Manager and connect to the B5800 Branch Gateway system.2. In the left navigation pane,

Page 33

license files, you can create a mapping file for bulk distribution. See Creating amapping file on page 129 for more information.6. To send the license

Page 34

1. Click the date/time icon and select the date and time you want thejob to run.2. In Time Zone drop-down box, select the appropriate time zone.• Clic

Page 35 - Power supply backup (UPS)

Chapter 1: OverviewThe Avaya B5800 Branch Gateway is a single-platform solution with multiple deployment options thatenable seamless, user-centric ac

Page 36

Procedure1. Open a generic CSV text file.2. Enter the B5800 Branch Gateway IP address and corresponding license file namein the following format: <

Page 37

Note:When Network Management is installed, this check box is checked by defaultand you are not able to administer the branch through Manager. To be a

Page 38 - Voice compression channels

7. Select File > Save Configuration.Digital trunk clock sourceAbout this taskDigital trunks require the telephone system at each end of the trunk t

Page 39

When multiple trunks with the same setting are providing clock signals, trunks are used in theorder of slots 1 to 4 and then by port on each slot.The

Page 40 - Measuring channel usage

Setting the trunk prefixesAbout this taskWhere a prefix has been implemented for outgoing calls, that same prefix needs to be addedto trunk settings.

Page 41 - Environmental requirements

1. If an incoming number (called or calling) starts with the + symbol, the + is replacedwith the International Prefix.2. If the Country Code has been

Page 42 - Space requirements

Administering a Session Manager line for each branchThis section provides the procedures required to configure a Session Manager line betweeneach bran

Page 43 - External expansion modules

Procedure1. Start Manager and connect to the B5800 Branch Gateway system.2. In the left navigation pane, click System.3. Click the LAN1 or LAN2 tab as

Page 44 - Rack space requirements

3. Click the System tab.4. Set the following fields as appropriate:• Branch Prefix• Local Number Length• Proactive• ReactiveThese 4 fields are the key

Page 45 - Rack module positioning

Name Range or Default DescriptionLength should not exceed15 digits.Proactive Default = 60 seconds The B5800 Branch Gatewaysends regular SIP OPTIONmess

Page 46 - Installation requirements

Branch user model at the same time. The extensions supported in the Centralized Branchuser model are SIP extensions only.Centralized solutionThe B5800

Page 47 - Installation checklist

Procedure1. Start Manager and connect to the B5800 Branch Gateway system.2. In the left navigation pane, click System.3. Click the Telephony tab.4. Cl

Page 48 - Tools and equipment required

operation and system capacities during the 30-day grace period that is in effect when thesystem is in License Error Mode because the license is not ye

Page 49 - Unpacking equipment

5. Click OK.6. Click the VoIP tab.7. Click the Allow Direct Media Path check box to select this option.8. Click the Re-Invite Supported check box to s

Page 50 - SD card preparation

Name DescriptionInactivity timeout (seconds) The default setting is 0. Keep the defaultsetting to maintain a persistent connectionwith Session Manager

Page 51 - Creating a configuration file

Name Range or Default DescriptionG711 option is used as thesecond choice codec.• The Advanced option canbe used to manuallyconfigure the codecpreferen

Page 52 - Adding music-on-hold files

Name Range or Default Descriptionalternately if possible withinthe network structure.• If enabled, connected callscan take routes other thanthrough th

Page 53

Note:See Branch PSTN call routing examples on page 325 for information on routing back to thebranch for fallback alternate routes.Ideally the number

Page 54

Short Code tab field descriptionsName DescriptionCode Enter the number dialed by users that shouldbe matched to this short code. Use Xwildcards for an

Page 55

extension number. If there is no matching extension number, the call is targeted to anymatching system short code.Incoming calls to a branchIncoming c

Page 56 - • VCM card

Chapter 8: Session Manager ConfigurationThe Session Manager procedures in this chapter are for configuring Session Manager for the B5800Branch Gatewa

Page 57 - Base card insertion

it can be configured to make and receive external calls via the central Avaya Aura®SessionManager. A combination of these methods can be used for PSTN

Page 58 - Installing a base card

6. Create time ranges to control when different routing policies are used. See Creatingtime ranges on page 153.7. Add a routing policy. A routing poli

Page 59 - Wall mounting

6. In the Managed Bandwidth Units field, accept the default setting.7. In the Total Bandwidth field, accept the default setting, blank8. In the Defaul

Page 60

7. In the Notes field, enter a description to help identify this SIP entity, asappropriate.8. In the Adaptation drop-down box, select the adaptation t

Page 61 - Rack mounting

5. In the SIP Entity 1 drop-down box, select the name of the Session Manager systemthat is at one end of the link.SIP Entity 1 must always be a Sessio

Page 62 - Important:

4. On the Routing Policies Details page, in the Name field, enter a name to describethis routing policy.5. For the Disabled check box, accept the defa

Page 63

12. In the Routing Policies section, click the check box for the routing policy that wascreated for the branch.13. Click Select.14. If you need to spe

Page 64

7. Add a routing policy. A routing policy consists of a selected SIP entity as itsdestination and a number of time ranges that define when the policy

Page 65

8. In the IP Address Pattern field, enter an IP address pattern that matches the IPLAN address range.The * character can be used as a match-all wildca

Page 66

9. In the Time Zone drop-down box, select the time zone for the location.10. For the Override Port & Transport with DNS SRV check box, accept the

Page 67

This check box must be checked. If it is not checked, calls from the associated SIPEntity 2 will be denied by Session Manager.8. In the Notes field, e

Page 68 - DS phone IROB installation

Note:If you are going to use Network Management for centralized management of the B5800Branch Gateway system, Network Management (NM) 6.0, NM 6.0 SP2

Page 69 - Analog phone barrier boxes

Creating dial patternsA dial pattern is defined to direct calls prefixed with the branch prefix to each branch.1. On the System Manager console, in th

Page 70 - Rack mounting barrier boxes

Creating a System Manager link to Network ManagementAbout this taskYou are able to use Avaya Aura® Session Manager Release 6.x, cut-through capability

Page 71 - Administration software suite

f) In the Port field, enter 443.g) In the URI field, enter /cgi-bin/launch_products.pl.h) In the Order field, enter the order in which the access poin

Page 72 - PC requirements

Chapter 9: Voicemail operationThe B5800 Branch Gateway system uses its Embedded Voicemail by default. However, a number of othervoicemail options are

Page 73 - Installer PC connection

Configuring Modular MessagingAbout this taskThe B5800 Branch Gateway system can be configured to use Modular Messaging as itsvoicemail server.Procedur

Page 74

8. In the Maximum Record Time field, use the up and down arrows to set themaximum recording length in seconds for recorded announcement and autoattend

Page 75 - Applying power to the system

3. Click 50: Main.Within the ARS form, the default 1N; short code is the one used for national calls.It would match the MM PSTN Number and attempt to

Page 76 - About the LEDs

to those calls.7. Click OK.8. Select File > Save Configuration.Embedded Voicemail for auto attendants andannouncementsIf Modular Messaging is used

Page 77 - Base card LEDs

Procedure1. Start Manager and connect to the B5800 Branch Gateway system.2. In the left navigation pane, right-click Auto Attendant and select New.3.

Page 78 - Starting Manager

appropriate greeting is played to callers and followed by the Menu Optionsgreeting which should list the available actions.• Time Profile — defines ea

Page 79 - Default configuration

• Additional E1 Channels license• 120-day trial licenseB5800 Branch Gateway uses the Avaya Product Licensing and Delivery System (PLDS) tomanage licen

Page 80

Recording promptsAbout this taskWhen a new auto attendant is created, a number of short codes are automatically added tothe system short codes table.

Page 81

Transferring recordings to the system SD cardAbout this taskUse this procedure to manually copy the pre-recorded prompts and announcements onto thesys

Page 82 - Default passwords

Voicemail operation172 Implementing the Avaya B5800 Branch Gateway November 2011Comments? [email protected]

Page 83

Chapter 10: Extension administrationThis chapter provides the procedures to administer native and survivable extensions. When the B5800Branch Gateway

Page 84 - Connecting phones

Enabling branch SIP extension supportAbout this taskBefore adding any SIP extensions, the B5800 Branch Gateway system must be enabled forSIP extension

Page 85

SIP Registrar tab field descriptionsName Default DescriptionDomain Name Default = Blank This is the local SIP registrardomain name that will beneeded

Page 86 - Gateway SD card

Name Default Descriptionauto create matchingentries, the extension'sExtension Mode settingdefaults to Local (native)which is incorrect for acentr

Page 87 - About rebooting the phones

Note:The full range of B5800 Branch Gateway user settings can be configured for anative extension. However the key settings are the Name and Extensio

Page 88

that if you do not select this feature, the user's mailbox is not disabled.Messages can still be forward to their mailbox and recordings can be p

Page 89

Name Default DescriptionDevice Type Default = Unknown SIPdeviceThis is an information fieldonly. If the configuration hasbeen loaded from a systemwith

Page 90

provide the SIP connections between Avaya Aura®Session Manager and B5800 BranchGateway.Additional channels licensesThe PRI Universal (PRI-U) trunk car

Page 91 - Starting System Status

Name Default Descriptionsystem using the Name andLogin Code configured forthe user within the B5800Branch Gatewayconfiguration. Forcentralized extensi

Page 92 - Starting System Monitor

Survivable extensionsSurvivable extensions support SIP phones only. For a list of supported telephones, see Supported telephones on page 21. Voicemail

Page 93

The B5800 Branch Gateway supports Session Manager 6.1 and Session Manager 6.0.Depending on the Session Manager version you are using, see one of the f

Page 94

detects that connection to the Avaya Aura® Session Manager is available again, it dynamicallyregisters with it and switches back to normal operation.

Page 95 - Centralized Branch

Extension Type DialedNumberNotesSurvivable Survivable 8XXXX Dial the extension number as shown on thetarget extension. The call routing is done bythe

Page 96

Session Manager 6.1 configuration required for survivableextension supportThe topics in this section provide the Session Manager 6.1 procedures requir

Page 97

g. In the Password field, enter the password required to log into SystemManager for personal web configuration.h. In the Confirm Password field, enter

Page 98

a. In the Primary Session Manager drop-down box, select the SessionManager instance that should be used as the home server for thecurrently displayed

Page 99

i. In the Voice Mail Number field, enter the number used to access thevoicemail system.j. Check the Delete Endpoint on Unassign of Endpoint from User

Page 100 - Procedure

1. On the System Manager console, in the left navigation pane, select Users >Manage Users.2. On the User Management page, click New.3. On the New U

Page 101 - Activating license files

right. They can be used in any order; however, if the capacity for a particular type of cardis exceeded, the card in the right-most slot will be disab

Page 102 - Creating a mapping file

5. To add a postal address for this user, in the Address section, do the following:a. Click New.b. On the Add Address page, in the Name field, enter t

Page 103

Note:Do not designate the B5800 Branch Gateway in this field. The B5800Branch Gateway address must be provided to the telephones throughthe settings

Page 104 - Disabling unused trunks

The list of registered users appears.2. To see the complete registration status of an individual user, click the check box forthe user you want to vie

Page 105 - Digital trunk clock source

11. Click OK.12. Select File > Save Configuration.The Send Configuration window appears and the Configuration Reboot Mode is setto Immediate. Do no

Page 106 - Setting the trunk prefixes

Name Default Descriptionthe B5800 BranchGateway system if theymatch existing extensionand user entries in theconfiguration. If acentralized (survivabl

Page 107 - SIP trunk prefixes

10. In the Name field, enter the same user name used for the survivable extension loginto B5800 Branch Gateway.11. In the Extension field, enter the B

Page 108 - Comments? [email protected]

Name Default Descriptiondigital and IP extensions, thisvalue is fixed as On.Reset Volume After Calls Default = Off If selected, resets thephone's

Page 109 - Enabling SIP trunk support

Name Default DescriptionCurrently connected calls arenot affected by changes tothis settingForce Authorization Default = On If enabled, SIP devices ar

Page 110

Name Default Descriptiontarget any matchingcentralized extension DIDand then any centralizedextension number beforechecking any alternativeroutes conf

Page 111 - System tab field descriptions

During survivable mode, when registered to the B5800 Branch Gateway system, thephone is not able to obtain dial plan information from the Avaya Aura®

Page 112

© 2011 Avaya Inc.All Rights Reserved.NoticeWhile reasonable efforts have been made to ensure that theinformation in this document is complete and accu

Page 113

• Trunk daughter cards — Most base cards can be fitted with a trunk daughter card tosupport the connection of trunks to the base card. The following t

Page 114 - Session Manager line

• PSTN_VM_NUMThis sets the number dialed when the Message button is pressed and the phone is insurvivable mode. For example, a DID number for the Modu

Page 115

The enterprise SIP domain. This must match a domain set in the Avaya Aura® domainssettings.• SIPREGPROXYPOLICYThis setting controls how the list of SI

Page 116 - VoIP tab field descriptions

SIP controller monitoringIt is important to understand that both the B5800 Branch Gateway system and the survivableextensions perform monitoring of th

Page 117

from it. B5800 Branch Gateway only responds to this request if its Avaya Aura® SessionManager lines are out of service.• If the phone does not have a

Page 118 - Avaya Aura

9600 extension operationFeatures available during failoverThe following apply while an extension is in the process of failover to another SIP controll

Page 119 - Secondary Avaya Aura

• The message waiting indicator does not work and is switched off.• Voicemail may still be available using the PSTN_VM_NUM number configured in thesur

Page 120

Feature Normal operation Survivability mode withB5800 Branch GatewayCall Management Yes (CM COR) Yes (Some restrictions canbe configured in the B5800B

Page 121 - Manager line

Chapter 11: Managing license files withPLDSOverviewThe Avaya Product Licensing and Delivery System (PLDS) provides customers, AvayaPartners, distribu

Page 122 - Line status detection

Registering for PLDSProcedure1. Go to the Avaya Product Licensing and Delivery System (PLDS) Web site (https://plds.avaya.com).You will be redirected

Page 123 - Distributed Branch

Types of license activationTypes of activation include:• Regular activation: where license entitlements are activated to generate ActivationRecords.•

Page 124

• Power supplies — The control unit has an internal power supply unit. Each externalexpansion module is supplied with an external power supply unit. A

Page 125

Note:The Quick Activation automatically assumes that you want to activate all licenseentitlements on LAC and gives the option to remove line items an

Page 126

• Group ID• License activation codeIn addition to these search criteria, PLDS also provides other additional advanced searchcriteria for searching lic

Page 127

Tip:You can use a wildcard (%) character if you do not know the exact LAC you aresearching for. For example, if you enter AS0%, the system searches f

Page 128

9. Perform the following steps to send an activation notification e-mail message:a) In the E-mail to field, enter e-mail addresses for any additional

Page 129

Managing license files with PLDS214 Implementing the Avaya B5800 Branch Gateway November 2011Comments? [email protected]

Page 130

Chapter 12: Standalone SAL Gateway forremote serviceAvaya Global Services (AGS) uses the Secure Access Link (SAL) Gateway to provide remote delivery

Page 131

Note:For B5800 Branch Gateway upgrades, you must access Manager that is installed ona PC or Network Management server that resides within the custome

Page 132

• Your company name• Avaya Sold-to Number (customer number)• Your contact information, so that Avaya can contact you if there are questionsAvaya uses

Page 133

Universal Install/SAL Registration Request FormYou can download this form from the Avaya support web site as follows:1. Go to the Avaya support Web si

Page 134

Chapter 13: Additional installation andsystem proceduresThe following topics are provided in this chapter:•Switching Off an IP Office System on page

Page 135

Telephone Native extensions Survivable extensionsBM32 (DSS)12402D2410D24203641 wireless3645 wireless3720 DECT R43725 DECT R44602IP4602SW4610IP4610SW46

Page 136

• The shutdown process takes up to a minute to complete. When shutdown, the CPULED and the base card LEDs 1 and 9 (if trunk daughter card fitted) will

Page 137

Shutting down the system using a system phoneAbout this taskTo shut down the system using a system phone, you must be administered as a System Phoneus

Page 138

4. Enter your user name and password.5. In the Reboot window, do one of the following:• Select Immediate to reboot the system immediately.• Select Whe

Page 139

Procedure1. Turn the B5800 Branch Gateway system off. See System shutdown on page 219.2. Remove the card or external expansion module. Note:The card s

Page 140

Replacing a component with one of lower capacityAbout this taskIf you are replacing a component with one of the same type but with lower capacity, whe

Page 141

Adding a new componentAbout this taskIf you are adding a new component to an available slot or port, when restarted the B5800Branch Gateway system wil

Page 142

Swapping extension usersAbout this taskThis procedure explains how to swap extensions for two users. This example refers to User Aand User B which rep

Page 143

configuration indicates the default associated user of the extension. It is not the extensionnumber of that port.Renumbering all extensions and usersA

Page 144

Manager automatically propagates the number change to any hunt groups,incoming call routes, user buttons, bridged appearance buttons and callcoverage

Page 145

changes that occurred after this document was completed. Bulletins are available from http://support.avaya.com• Multiple Managers — If more than one c

Page 146

Telephone Native extensions Survivable extensions96502 39650C2 3SMM2419608 49611G 49621G49641G4BM121Avaya1010/1020/1030/1040video conferencing units

Page 147

Using the upgrade wizardAbout this taskBefore using the upgrade wizard, be sure you have a current backup of the systemconfiguration. See Creating a b

Page 148

• Click the check box for Backup System Files if, before upgrading to the newsoftware, you want the current files in the System SD cards /primary fold

Page 149 - Session Manager 6.1

State Switch 1 Switch 2Open *40 *43Pulse *41 *44EXT O/P connectionsEXT O/P ports use a standard 3.5mm stereo jack plug for connection. The B5800 Branc

Page 150 - Creating locations

Example of BRI So8 module configurationThe ports on a BRI So8 module can be used for the connection of ISDN devices. Followingare examples of how to c

Page 151 - Creating SIP entities

b) Configure incoming call route. The # is used here instead of "n" to avoidproblems with "Main". The minus sign means the number

Page 152 - Creating entity links

To route an incoming video call on the PRI lines configured above to an So8 module requiresthe following:Procedure1. Create a dial short code that has

Page 153 - Creating routing policies

Characteristics Admin/Software and Hardware/Software• Country: USA• Language: English (USA)• Auto Answer: Yes• AllowDial: Yes• Allow User Setup: Yes•

Page 154 - Creating dial patterns

This allows the application to create a network map and to raise an alarm when devicespreviously present do not respond.• Most SNMP manager applicatio

Page 155 - Session Manager 6.0

HP OpenView Network Node ManagerProcedure1. Copy the following MIB files to the application's MIB folder.MIB File Sourcerfc2737-entity-mib.mib sn

Page 156

Castlerock SNMPc 5.1.6c and earlierProcedure1. Copy the following MIB files to the application's MIB folder. This folder is typicallyC:\Program F

Page 157

• SoftConsole: is intended for telephone system operators or receptionists. It displaysdetails of calls and allows them to quickly see the status of t

Page 158

3. In the SNMPv2-SMI.mib file find the definition of zeroDotZero and copy this to theclipboard.4. In the STANDARD.MIB file find the SNMPv2-SMI section

Page 159

establish communication and then changed (at both the SNMP agent and managerends) for security.7. Click OK.8. Select File > Save Configuration to s

Page 160

b) In the IP Address field, enter the IP address of the PC running the SNMPmanager application.c) In the Port field, enter the port on which the trap

Page 161

Data bits 8 Stop Bits 1 Settings > Emulation TTYDTE cablesThese cables are used for system maintenance and diagnostics under Avaya guidance. Theyca

Page 162 - Session Manager Configuration

Erasing the configuration via debugAbout this taskThis procedure erases the system's configuration settings but does not alter the securitysettin

Page 163

backup of the system configuration. See Creating a backup of the system configuration onpage 229 for more information.Procedure1. Attach the serial ca

Page 164 - Configuring Modular Messaging

Resetting the security settings to the default settingsAbout this taskThis procedure resets the systems security settings back to the default settings

Page 165

2. Start the terminal program on your PC. Note:Ensure that the DTE port settings are configured as described in RS232 DTE portsettings on page 242. Wi

Page 166 - Voicemail operation

to a value in the 192.168.42.1 to 192.168.42.10 range. If this occurs it may be necessary toamend the BOOTP entry in Manager to match the address the

Page 167 - Creating an auto attendant

An OK response appears.10. Enter AT-DEBUG.The time and date and then the Hello> prompt appears to show the system isready to accept commands.11. To

Page 168

Locale Language TelephonyPhoneDisplayApplications VoicemailManager SoftConsoleEmbeddedVoicemailVoicemail ProAustralia UKEnglishBelgium DutchBelgium Fr

Page 169

11. Power on the control unit and press the escape key every second until you get aloader message. An example of this message is:P12 Loader 2.4CPU Rev

Page 170 - Recording announcements

Press Duration(seconds)CPU LED Action SummaryOver 40 Flashing green None NoneAUX buttonThe AUX button is on the control unit. If the AUX button is pre

Page 171

4. Edit the WAN port.Do not create a new WAN port. The WAN port is automatically detected. If a WANport is not displayed, connect the WAN cable, reboo

Page 172

Chapter 14: SD card managementThere are two SD card slots on the control unit. They are labeled System SD and Optional SD.System SD card slot• An Ava

Page 173 - Native extensions

Warning:Memory cards should always be shut down before being removed when the system is running. Thoughthe card slot LEDs indicate when data is being

Page 174

Procedure Description ManagerSystemStatusSystemPhoneMinutes Caution:This process will erase all existing fileson the card.Recreate onpage 257Create th

Page 175

Booting from the SD cardsWhen being powered up, the control unit looks for a valid .bin binary file to load. It does thisusing the possible source bel

Page 176

• The normal boot-up process of upgrading expansion module firmware does notoccur. If the File > Advanced > Upgrade command is used, only extern

Page 177

any other method will remove the feature key used for B5800 Branch Gateway licensingfrom the card.These procedures are run on an SD card inserted in a

Page 178 - Extn tab field descriptions

2. In the navigation panel, select System > Memory Cards > System SD.3. Click on the Format button at the bottom of the screen.The card is refor

Page 179

Locale Language TelephonyPhoneDisplayApplications VoicemailManager SoftConsoleEmbeddedVoicemailVoicemail ProPeru LatinSpanishPoland Polish -• Locale:

Page 180

Viewing the card contentsAbout this taskUsing Manager you can view the folders and files on the System SD card and the Optional SDcard.Procedure1. Sta

Page 181 - Survivable extensions

Procedure1. Start Manager.2. Select File > Embedded File Management.3. From the Select IP Office window, select the appropriate system.The file con

Page 182 - Survivability operation

About restoring from the backup folderWhen you restore from the backup folder, you copy the contents of the backup folder on theSystem SD card to the

Page 183 - Internal calls

the process has been completed, the B5800 Branch Gateway system isrestarted.Restoring from the backup folder using a system phoneAbout this taskA user

Page 184

Backing up to the Optional SD card using ManagerProcedure1. Start Manager.2. Select File > Embedded File Management.3. From the Select IP Office wi

Page 185

2. Enter your B5800 Branch Gateway user login code.3. From the menu select Memory Card.4. Select Copy.The contents of the System SD card are copied to

Page 186 - Extension administration

takes a few seconds. When the process has been completed, the B5800 BranchGateway system is restarted.Restoring a configuration file from the Optional

Page 187

Restoring software files from the Optional SD card using a systemphoneAbout this taskA user configured as a system phone user can perform this procedu

Page 188

Method Description Location SoftwareFilesEmbeddedVoicemailPromptsUsing Manager onpage 268Using Manager, the contentsof the card are compared tothe fil

Page 189

files. Depending on the files that need to be updated, this can take up to40minutes.Upgrading the SD card locallyAbout this taskYou can upgrade the SD

Page 190

Details of courses can be found on the Avaya University web site (http://www.avaya-learning.com). The site can be used to check course availability an

Page 191

Procedure1. 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

Page 192

Shutting down a memory card using ManagerProcedure1. Start Manager.2. Select File > Advanced > Memory Card Commands > Shutdown.3. In the Sele

Page 193 - 11. Click OK

Shutting down a memory card using System StatusProcedure1. Start System Status and access the status output.2. In the navigation panel select System.3

Page 194

Starting up a card using the System Status applicationProcedure1. Start the System Status application and access the B5800 Branch Gateway statusoutput

Page 195

SD card management274 Implementing the Avaya B5800 Branch Gateway November 2011Comments? [email protected]

Page 196

Chapter 15: Safety and regulatoryinformationSafety statementsThe B5800 Branch Gateway modules are intended to be installed by Service Personnel andit

Page 197

• 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 b

Page 198 - Survivability settings

Trunk interface modulesTo ensure the validation of the approvals, only the following types of trunk interface cards mustbe fitted in the B5800 Branch

Page 199

Port Name Port Description Port ClassificationExpansion ports Expansion Moduleconnector.SELVAudio port Connector for Music onHold.SELVExternal control

Page 200 - 35.1.1.51:5060;transport=tcp

EMC caution for chinaRegulatory Instructions for UseAustraliaBRI interfaceDuring the configuration, ensure "000" emergency number is not bar

Page 201 - Using the group parameters

Documents you may need to consult are as follows:• Administering Avaya Aura® Session Manager, document number 03-603324• Avaya Integrated Management R

Page 202 - SIP controller monitoring

During the configuration, ensure "000" emergency number is not barred, by performing thefollowing:• Short Code: 000• Telephone No: 000;• Fun

Page 203

ChinaRegulatory Instructions for UseImplementing the Avaya B5800 Branch Gateway November 2011 281

Page 204 - 9600 extension operation

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 suit

Page 205

Port FIC SOC USOC Jack RENIPO500 PRI 1U,IPO500 PRI2U,IP400 PRI-T104DU9.BN,04DU9.DN,04DU9.IKN,04DU9.ISN6.0Y RJ48C NAIPO500 ATM4UIP400 ATM4UOL13A, OL13B

Page 206

• Routed to a recorded announcement that can be administered by the customerpremises equipment (CPE) user• Routed to a dial prompt• This equipment ret

Page 207

personnel may result in violation of the FCC rules. Qualified personnel may adjust gain settingsabove these levels only where:• Measurement is made to

Page 208 - About license activation

Safety and regulatory information286 Implementing the Avaya B5800 Branch Gateway November 2011Comments? [email protected]

Page 209 - Types of license activation

Appendix A: Centralized deploymentexample call flowsThis appendix provides examples of call flows for a system that is configured in a centralizeddepl

Page 210

Solution overviewThe Solution overview illustrates the store network.• CM-1 represents a Communication Manager used for features for the store phones.

Page 211

Sunny dayThe first set of call flows are for sunny day. This is when all SIP endpoints have full connectivityacross the WAN back to the core and are r

Page 212 - Regenerate License files

Chapter 2: PlanningBefore you begin installing and configuring the B5800 Branch Gateway system, you should already havedetermined the implementation

Page 213

Local PSTN dialing1 Store Phone calls local extension 9-755-1234.2 SM sends 9-755-1234 to CM for origination call processing.3 CM translates the call

Page 214

Long distance and international1 Store Phone calls long distance number 9-011-912-2600-9000.2 SM sends 9-011-912-2600-9000 to CM for origination call

Page 215

Incoming call1 Customer dials store extension 1-916-788-1234 (the branch phone number).2 B5800 Branch sends call to VDN 5000299 on CM via SM. Routing

Page 216

reduced SIP feature set which does not support all sunny day features. In a rainy day inboundcall scenario, the process would be as follows: an inboun

Page 217

2 B5800 Branch sends the call directly to all registered SIP stations in the huntgroup.A RTP Media is established between the Store Phone and the B580

Page 218

A RTP Media stream is established between the Store Phone and the B5800Branch.Rainy dayImplementing the Avaya B5800 Branch Gateway November 2011 2

Page 219 - System shutdown

Centralized deployment example call flows296 Implementing the Avaya B5800 Branch Gateway November 2011Comments? [email protected]

Page 220

Appendix B: Avaya port matrix for B5800Branch Gateway and SIPphonesThis appendix provides example ingress and egress ports for B5800 Branch Gateway an

Page 221 - Rebooting the system

• Well known ports are those numbered from 0 through 1023.• Registered ports are those numbered from 1024 through 49151• Dynamic ports are those numbe

Page 222 - About changing components

• 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:2345Data f

Page 223

The trademarks, logos and service marks (“Marks”) displayed in thissite, the Documentation and Product(s) provided by Avaya are theregistered or unreg

Page 224

Dial plan considerationsA uniform dial plan greatly simplifies configuration, management and phone calls within thenetwork branch sites. For example,

Page 225 - Adding a new component

packet, up through the application layer, is examined. A stateful inspection firewall alsomonitors the state of the connection and compiles the inform

Page 226 - Swapping extension users

< TFTP Data packet (1..n), src port 4153, dstport 2421TFTP Acks (1..n), src port 2421, dst port4153Ingress ports for B5800 Branch Gateway and SIP p

Page 227

# Dest.PortNetwork/AppProtocolEnorDis?DefaultPortStateRemoteDeviceExt toBranch?Description9 50805-C TCP/HTTPB5800configaccessNo Open B5800ManagerYes B

Page 228

# Dest.PortNetwork/AppProtocolEnorDis?DefaultPortStateRemoteDeviceExt toBranch?DescriptionB5800SecSettingsAccessUnsecured. See50813.For a description

Page 229

# Dest.PortNetwork/AppProtocolEnorDis?DefaultPortStateRemoteDeviceExt toBranch?Description7 514 UDP/Syslog-CliYes Open SyslogServerNo, butcould beLog

Page 230 - Using the upgrade wizard

Table column heading definitionsColumnheadingDescriptionDest Port Destination port — this is the layer-4 port number to which the connectionrequest is

Page 231 - Closed *39 *42

• Email will not flow through the B5800 Branch Gateway in this example. See optionalsection for port 25.• An off-site DHCP server is used to supply IP

Page 232 - EXT O/P connections

Port usage diagramPort usage diagramImplementing the Avaya B5800 Branch Gateway November 2011 307

Page 233 - Example 1: ISDN terminal

In this diagram, direction of the arrow depicts call initiation. Data traffic will typically be 2-way.Avaya port matrix for B5800 Branch Gateway and S

Page 234 - Example 2: video conference

Appendix C: B5800 Branch Gateway callflowsCalls from local extensions (i.e. deployed in Distributed branch model)1. Local phone to local phoneLocal ph

Page 235

• 6-digit survivable extension numbers of which the first 3 digits are equal to the branchprefix e.g. 811250.• Dial 9 prefix for outgoing PSTN calls.•

Page 236

Centralized phone A Avaya Aura core servers (including Session Manager and CM-FS) centralized phone B Note:The B5800 Branch Gateway is not involved

Page 237

Calls to Centralized phones in normal mode (aka sunny day)1. From PSTN to centralized phone’s DID (LDN is associated with local B5800 Branch Gatewaytr

Page 238

Centralized phone B5800 Branch Gateway B5800 Branch Gateway trunk (e.g. FXO, ISDN,SP SIP trunk) PSTN4. Centralized phone to headquarters or othe

Page 239 - Castlerock SNMPc V5.0.1

Appendix D: PSTN example call flowDuring normal operation, calls made by a survivable extension are received by the Avaya Aura®SessionManager and pass

Page 240

9. Route Pattern 11 routes the call to SIP Trunk Group Number 32. This connects theCommunication Manager Feature Server to the Avaya Aura®Session Mana

Page 241 - Enabling SNMP trap sending

The difference between the two values needs to be greater than or equal to thedesired number of simultaneous SIP trunk connections.Configuring trunk-t

Page 242 - DTE port maintenance

Configuring IP network regionsAn IP address map can be used for network region assignment. The network regionassignment can be used to vary behaviors

Page 243

The ip-network-region form for Network Region 1 needs to be similarly configured. Networkregion 1 is for phones and servers as well as Session Manager

Page 244

1. Enter the add signaling-group n command, where n is an available signaling groupnumber.2. Enter the following values for the specified fields and r

Page 245

Configuring SIP trunk groupsNext, SIP trunk groups need to be added.1. Enter the add trunk-group n command, where n is an available trunk group number

Page 246

central voicemail system, at each branch you have the option to still use the localEmbedded Voicemail for auto attendant operation and for announcemen

Page 247

The trunk group 32 used for routing local PSTN calls from branch phones is similarlyconfigured.Configuring route patternsConfigure a route pattern to

Page 248

Configuring AAR1. Enter the change aar analysis command to add an entry for the extension rangecorresponding to the branch survivable extensions2. Ent

Page 249

Location specific ARS digit analysisLocation based analysis is used before global analysis. Using it we could apply rules that onlyapply to calls from

Page 250 - Reset button

Route Pattern 3 is configured to use a Trunk Group that connects to the CommunicationManager Feature Server at the headquarters location for PSTN call

Page 251 - Creating a WAN link

PSTN example call flow324 Implementing the Avaya B5800 Branch Gateway November 2011Comments? [email protected]

Page 252

Appendix E: Branch PSTN call routingexamplesEach B5800 Branch Gateway system can support its own external PSTN trunks. When deployed in anAvaya Aura®

Page 253

In this example, the company wants all national and international calls made at the branch tobe routed to use the headquarter site's PSTN trunks.

Page 254 - Card maintenance

3. Click 50: Main.Within the ARS window, the default 0N; short code that matches internationalnumbers currently routes those calls to any available tr

Page 255 - SD card folders

9. Click OK.10. Select File > Save Configuration.Branch PSTN overrideIn the example provided in Centralized call control on page 325, we configured

Page 256 - Booting from the SD cards

3. Click 50: Main.Within the ARS form, the default 1N; short code is the one used for national calls.It would match the MM PSTN Number and attempt to

Page 257 - Boot alarms

The Network Management offer is a suite of software applications that enable centralizedmanagement of the B5800 Branch Gateway system. It provides a s

Page 258 - Formatting an SD card

to those calls.7. Click OK.8. Select File > Save Configuration.PSTN trunk fallbackIn branch scenarios where centralized call control and trunking (

Page 259 - Recreating an SD card

issue is resolved. However, even if that is the case, it may be recommended to configurea headquarters PSTN number that can be dialed to report the Av

Page 260 - Viewing the card contents

7. Click OK.8. Click OK.9. Double click on the existing default ARS that was reconfigured to send all branchnational and international calls to the Av

Page 261

• The Alternate Route Wait Time is used for caller's whose priority is notsufficient to use the alternate route immediately. The default setting

Page 262

Branch PSTN call routing examples334 Implementing the Avaya B5800 Branch Gateway November 2011Comments? [email protected]

Page 263

Appendix F: Recommended courses forAvaya B5800 Branch GatewaytrainingAvaya B5800 Branch GatewayTable 1: APSS – SMECType Code Course title Delivery Du

Page 264

Unified CommunicationsTable 3: ACIS – Session Manager and System ManagerType Code Course title Delivery Duration(hours)FirstofferingUpdate ATU00180OE

Page 265

Type Code Course title Delivery Duration(hours)FirstofferingNew ATI02445VEN Session Manager, CMand other Feature ServerAdministrationvILT 5 Dec 6Updat

Page 266

Recommended courses for Avaya B5800 Branch Gateway training338 Implementing the Avaya B5800 Branch Gateway November 2011Comments? [email protected]

Page 267

GlossaryCentralizedBranch user modelThis term describes aB5800 Branch Gateway deployment model wherecertain 9600 Avaya SIP phones can use the B5800 Br

Page 268

Network assessment for VoIP requirementsB5800 Branch Gateway is a converged telephony system, that is it combines aspects oftraditional PABX telephone

Page 269 - Upgrading the SD card locally

Failback This term is used for the situation where a centralized extension that isworking with a survivability call controller detects that its normal

Page 270 - Memory card removal

match those available from the headquarters system during normaloperation. See Rainy day.Tail-End-Hop-Off Part of mixed mode trunking, this describes

Page 271

Tail-End-Hop-Off342 Implementing the Avaya B5800 Branch Gateway November 2011Comments? [email protected]

Page 272 - Card startup

Chapter 3: Installation requirementsThis chapter provides information about power supplies, cables, grounding and environmental and spacerequirements

Page 273

Typical B5800 Branch Gateway System VAB5800 Branch Gateway system 230Individual Equipment VAAnalog 16 module 88Digital Station 16 module 34Digital Sta

Page 274 - SD card management

systems using punch-block connectors. This type of installation should be performed byan experienced wiring technician.• Trunk connections — The major

Page 275 - Safety statements

GroundingUse of ground connections reduces the likelihood of problems in most telephony and datasystems. This is especially important in buildings whe

Page 276 - Lithium batteries

Call type Voice compression channel usageIP device to non-IP device These calls require a voice compression channel for theduration of the call. If no

Page 277 - Port safety classification

4 Implementing the Avaya B5800 Branch Gateway November 2011Comments? [email protected]

Page 278 - EMC cautions

Measuring channel usageThe B5800 Branch Gateway System Status Application can be used to display voicecompression channel usage. Within the Resources

Page 279 - Australia

Environmental requirementsThe planned location must meet the following requirements. If being installed into a racksystem, these are requirements for

Page 280

Note:See Important safety instructions when using your telephone equipment on page 275 forbasic safety precautions to follow when using your telephon

Page 281

External expansion modulesThe dimensions below are applicable to all external expansion modules.Space requirementsImplementing the Avaya B5800 Branch

Page 282 - FCC notification

Wall mounting space requirementsThe control unit can be wall mounted if not using any external expansion modules. A wallmounting kit is required in ad

Page 283

Rack module positioningThe integral expansion ports on a control unit are located on the rear of the unit. An additional4 expansion ports can be added

Page 284 - Compliance with FCC rules

Installation requirements46 Implementing the Avaya B5800 Branch Gateway November 2011Comments? [email protected]

Page 285

Chapter 4: Hardware and softwareinstallationAll hardware components should be turned off while they are installed and connected. Once the installatio

Page 286

# Description Section8 Connect the external expansionmodules.See External expansion modules onpage 63.9 Connect the control unit andexternal expansion

Page 287 - Call flows

• RJ45-RJ45 ethernet LAN cable• M4 cross-head screwdriver• Tools suitable for crimping a cable spade• If wall mounting, drills and tools for wall moun

Page 288 - Solution overview

ContentsChapter 1: Overview...13Branch user de

Page 289 - Sunny day

4. Ensure that anti-static protection measures areobservedEnsure that anti-static protection measures are observed at all times when handlingequipment

Page 290 - Local PSTN dialing

If the card contains any dynamic system files, for example SMDR records, they are temporarilybacked up by Manager and then restored after the card is

Page 291

Note:For information about CSV files, see the Help available in the Managerapplication. From Manager, select Help > Contents. In the Manager Helpw

Page 292 - Rainy day

Property ValueAudio Format PCMLength Up to 90 seconds.Procedure1. Rename the music file holdmusic.wav.2. Using a card reader, copy the file into the /

Page 293

Warning:• Correct anti-static protection steps should be taken before handling circuit boards.• Cards must never be added or removed from the control

Page 294

Parts and equipment required• Base card (except the legacy card carrier)• Trunk daughter card• 3 stand-off pillars (these are supplied with the trunk

Page 295

• PRI T1• Dual PRI T1• PRI 30 E1 (1.4)• Dual PRI E1• PRI 30 E1R2 RJ45• Dual PRI E1R2 RJ45• BRI-8 (UNI)• ANLG 4 UNI (US only)• VCM 4• VCM 8• VCM 16• VC

Page 296

• 2 plastic stand-off pillars per card• Trunk cards are supplied with a replacement blanking plate which is not required.Tools required• 5mm Flat-blad

Page 297 - Branch Gateway and SIP

Warning:• Correct anti-static protection steps should be taken before handling circuit boards.• Cards must never be added or removed from the control

Page 298 - Dynamic ports

5. At this point apply pressure at the base of the front of the card to completeinsertion.6. Using a flat-bladed screwdriver secure the card.Wall moun

Page 299 - Firewall types

Adding music-on-hold files...529600 series

Page 300 - TFTP port usage

Hardware and software installation60 Implementing the Avaya B5800 Branch Gateway November 2011Comments? [email protected]

Page 301

Rack mountingThe B5800 Branch Gateway control unit and external expansion units can be rack mountedinto 19-inch rack systems. This requires a rack mou

Page 302

• Important:Only the screws (M3 x 6mm) provided with the mounting kit should used to attach theHardware and software installation62 Implementing t

Page 303

brackets to the control unit. As indicated in the diagram, the rack mounting bracket canbe used in several positions on the unit.External expansion mo

Page 304

Parts and equipment required• External expansion module — each module is supplied with a suitable external powersupply unit and a 1m blue interconnect

Page 305

GroundingUse of ground connections reduces the likelihood of problems in most telephony and datasystems. This is especially important in buildings whe

Page 306

External expansion modulesOn expansion modules, the ground point is a 4mm screw located towards the right on the rearof the module. On some older mo

Page 307 - Port usage diagram

• Cables of different types, for example trunk lines, phone extensions, ground and powerconnections, should be kept separate.• All cabling between bui

Page 308

Connection type Protection device type RequirementExternal output switch ITWLinx towerMAX SCL/8(This device was previouslyreferred to as the Avaya146G

Page 309

Analog phone barrier boxesWhere analog phone extensions are required in another building, phone barrier boxes andprotective earth connections must be

Page 310

Disabling the Network Management administration feature for the branch...103Disabling unused trunks...

Page 311

Main Building Barrier Box Secondary Building• Center screw — Connect tomain building protectiveground (or ground terminal ofBarrier Box Rack MountingK

Page 312

5. Using 14AWG wire with green and yellow sleeve, connect one of the earthing pillarsto the buildings protective earth.6. Using 14AWG wire with green

Page 313

progress. Details of the number of alarms are recorded and the time and date of the mostrecent alarms.• System MonitorThe B5800 Branch Gateway System

Page 314 - PSTN example call flow

2. Select B5800 Branch Gateway Administration Suite.3. Double-click on setup.exe.4. Select the language you want to use for the installation process.T

Page 315 - Configuring IP codec set

Connecting the PC directly to the control unitAbout this taskThe default address for a B5800 Branch Gateway control unit LAN port is192.168.42.1/255.2

Page 316

d) If there are no ping replies, enter ipconfig.The results should list the IP address settings of the Manager PC as requiredabove.e) If the IP addres

Page 317

• If a configuration file is already present on the System SD card, it is loaded bythe B5800 Branch Gateway. If not, the B5800 Branch Gateway creates

Page 318

LED DescriptionSystem SD• Green on = card present• Green flashing = card in use• Orange steady = reset imminent• Red flashing = card initializing or s

Page 319 - Configuring SIP trunk groups

Trunk daughter card LEDsTrunk Daughter Card LEDs 9 to 12 UsageAll cards LED 9 is used for daughter card status:• Red on = error• Red slow flash = init

Page 320 - Configuring private numbering

configuration the Manager user can view and alter. Manager is also used to upgrade the systemsoftware files.Procedure1. Select Start > Programs >

Page 321 - ARS Access Code

Creating locations...156Crea

Page 322 - Global ARS Digit Analysis

• Extensions and users — A user is automatically created for each physical extensionport detected in the system. Users are assigned extension numbers

Page 323

Important:Once the control unit has obtained IP address and DHCP mode settings, it retains thosesettings even if rebooted without a configuration fil

Page 324

12. Reboot the system.Connecting the control unit to the networkAbout this taskOnce you have changed the B5800 Branch Gateway system default settings

Page 325 - Centralized call control

5. In the Security Service User Login window, enter a user name and password of anaccount that has security configuration access to the B5800 Branch G

Page 326

2. In the left navigation pane, click User.3. In the user list, click RemoteManager.4. On the User tab, do the following:a) In the Password field, ent

Page 327

This section describes the process for 96x1 Series Phone SIP firmware download using theB5800 Branch Gateway. The procedure required to replace the H.

Page 328 - Branch PSTN override

• SIP_CONTROLLER_LIST has to have the appropriate Avaya Aura® Session Manager IPaddress as a primary SIP server.• See Survivability settings on page 1

Page 329

Procedure1. Start Manager and connect to the B5800 Branch Gateway.2. Select File > Advanced > Embedded File Management.3. Copy the configuration

Page 330 - PSTN trunk fallback

4. In the list of users that is displayed, select the check box (on the left of each row)for the users to be rebooted. Note:Multiple users can be sele

Page 331

Rebooting the phones by power cycling the phonesAbout this taskThis procedure can be performed in sunny day or rainy day conditions. The phones do not

Page 332

B5800 Branch Gateway SAL-based alarming...217Universal Install/

Page 333

Hardware and software installation90 Implementing the Avaya B5800 Branch Gateway November 2011Comments? [email protected]

Page 334

Chapter 5: Administration software suiteThe B5800 Branch Gateway administration software applications are installed on the installation PC. Theyare u

Page 335 - Avaya B5800 Branch Gateway

• If Manager is also installed and is running, select File > Advanced > SystemStatus.• Start a web browser and enter the IP address of the contr

Page 336 - Unified Communications

3. In the Control Unit IP Address drop-down box, select the IP address of the controlunit you want to monitor.4. In the Password field, enter the appr

Page 337

Administration software suite94 Implementing the Avaya B5800 Branch Gateway November 2011Comments? [email protected]

Page 338

Chapter 6: Initial configuration for aCentralized BranchThis chapter provides initial configuration tasks required for each B5800 Branch Gateway bran

Page 339 - Glossary

Centralized Branch configuration checklistUse this checklist to monitor your progress as you configure a B5800 Branch Gateway systemdeployed as Centra

Page 340 - Failback

# Description Section12 Add a second Session Manager linefor redundancy.See Avaya Aura Session Manager lineredundancy on page 118.13 Set up outgoing c

Page 341 - Tail-End-Hop-Off

# Description Section20 Create a time range. For Session Manager 6.1 or 6.0, see Creating time ranges on page 153.21 Create a routing policy.• For Ses

Page 342

Procedure1. See Activating license entitlements on page 209 to generate the licenses.2. Depending upon which method you want to use to deliver the act

Commentaires sur ces manuels

Pas de commentaire