Home

Avaya B5800 Configuration manual

1. Locale Language Telephony Phone Applications EVM and Display Manager Soft SVM Console Denmark Danish lt lt 2 x Finland Suomi 4 lt gt 4 4 France French 4 vi vi lt 4 Germany German v lt 4 lt lt v Greece Greek Pi SVM only Hong Kong Cantonese 4 Hungary Hungarian x 5 E SVM only Iceland Icelandic 4 z gt India UK English lt lt lt Italy Italian 4 lt 4 lt 4 Korea Korean vi 4 Mexico Latin 4 vi vi lt 4 Spanish Netherlands Dutch v s s lt lt New Zealand UK English v lt 4 lt 4 Norway Norwegian J lt lt 4 Peru Latin s lt 4 lt 4 Spanish Poland Polish 4 SVM only EVM is Embedded Voicemail SVM is Standalone Voice Mail Note Hungarian Polish and Greek are not supported by Embedded Voicemail but they are supported by Standalone Voice Mail e Locale The country represented by the locale e Language The voicemail prompt language used for that locale e Telephony The B5800 Branch Gateway provides default telephony settings matching the normal expected defaults for the locale e Phone Display Indicates that display messages from the B5800 Branch Gateway to Avaya phones can be sent using the appropriate language for that locale Note that the user locale can be used to override the system locale for these messages Note also that some phones support their own language sel
2. ccesecceeecesseeeeeceaeeeseeeeeaeeenes 53 installing a service PACK sssssssssssseeeresrrnrrreseeeernnnns 97 Installing IP Office Manager Lite from the System Manager server to a PC cccccceeeeseeseeeeees 114 installing the license file on the System Manager WebLM SOIV ER ichiisiece duns EE E E EE 117 IP Address iiciin anaa E NE 167 IP Office Operation in ccccccccccceeessesssteeeeeeeeeeeeeenees 270 USA aia a E 270 L Gall NOCES srinata oniiis iar a EE A AEA 2 license entitlements ccccceccccceceseeeeeeeeeeeeeeee 191 193 October 2012 ACUIV ALIN e E E E a genes 191 searching fOr sissesccsevecsdnciiseraiecssiwetvasractvnedeadee 193 license MOSS cansi aaa 19 LICENSING ss ssadecreaicnasaahwecancnttnnisamereda na aaaea a aad 16 Lightening Portection seessseeeeeerreeersrrrressererrnenenns 264 Lightening protection caseras e 72 Link Monitoring 2 cece cece cece eeee cette eee e tees eeeeeeeeteeeeeeeees 167 Lithium BatterieS cccceccccecceseseceecesesseeeeeseeeeeeseaees 264 Location adding cecceeeeeee cette tee eeeeeeeeeeeeeeeeeeeeeees 166 M management iicc cece cceceeetesen ste ceceecaceaeasneeaeeescanenanaes 14 Manager eeeeseesseeesenesrnssrnernrnsrrnsnnn 134 137 213 216 Clock quali eecscarninonninn 135 extension NUMDETSS ccececcecesseeeeeceeeceeeeeeeeses 213 prefix dialgar 137 trunk clock quality Setting 0 0 0 0 eeeeeeeeeeeeeeeeeee 136 t
3. 30 Create a routing policy See Creating routing policies on page 169 31 Create a dial pattern See Creating dial patterns on page 170 32 Add distributed users This task is performed from Avaya Aura System Manager using the User Management feature See User administration on page 185 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 112 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration Comments infodev avaya com October 2012 Setting up System Manager to launch IP Office Manager configuration or security configuration from System Manager System Manager launches either version of IP Office Manager in the appropriate mode for the configuration task that was initiated such as endpoint or template configuration If you use IP Office Manager that was installed from the B5800 Branch Gateway Administrator Applications DVD you must ensure the version installed on the administration PC is the same version in the B5800AdminLite exe file If they are not the same version you must either upgrade the version of IP Office Manager on the administration PC or you
4. 3 If you are registering as an Avaya Partner enter the Partner Link ID If you do not know your Partner Link ID send an e mail to prmadmin avaya com as a customer enter one of the following Company Sold To Ship To number License authorization code LAC 4 Click Submit Avaya will send you the PLDS access confirmation within one business day About license activation What is license activation License activation is a process of activating license entitlements by specifying a license host and host ID of the WebLM server The process includes generating the license file Note If you are not using WebLM to manage the licenses you must provide the host ID of each B5800 Branch Gateway in your network to generate a license for each branch The host ID 190 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev 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 e Regular activation where license entitlements are activated to generate Activation Records Upgrade activation which involves either Activating license entitlements that ha
5. Inthe Folders pane on the left select System SD gt System gt Primary Sz Select File gt Upload file Select the PLDStemp xml file Click OK The Upload System Files window appears and shows the upload progress O O ON OD 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 xml filename is automatically renamed to PLDSkeys xml 118 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Generating a certificate on System Manager Note If the PLDS file is not accepted by B5800 Branch Gateway the B5800 Branch Gateway will remain in License Error Mode and the PLDStemp xml file is not renamed Generating a certificate on System Manager About this task Use this procedure to add a B5800 Branch Gateway End Entity to System Manager This procedure adds the B5800 Branch Gateway to the System Manager trust domain and is required to establish a trust relationship between the B5800 Branch Gateway and System Manager Procedure 1 From the System Manager console under Services select Security 2 On the Security page in the left navigation pane select Certificates gt Authority 3 In the left navigation pane click Add End Entity 4 On the Add End Entity page do the following a Inthe End Entity Profile
6. O29aA05 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 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 115 Initial branch configuration management B5800 Branch Gateway R6 2 also supports local licensing using an individual PLDS license file that can be installed directly on the B5800 Branch Gateway using B5800 Branch Gateway Manager provided in R6 1 For more information about both of these licensing methods see Licensing on page 16 Note B5800 Branch Gateway supports a 30 day grace period during which time the system is fully functional if e a license error is detected e the WebLM server is not available for example due to loss of connectivity between the B5800 Branch Gateway and the WebLM server if using the WebLM licensing method e a license file cannot be obtained for example due to loss of WAN connectivity if using the local PLDS licensing method Procedure 1 See Activating license entitlements on page 191 to generate the licenses 2 See one of the following e To use the WebLM licensing method and install the license file on the WebLM server see Installing the shared PLDS license file on the System Manager WebLM server on page 117 e To use the individual PLDS licensing method and
7. Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 279 Avaya port matrix for B5800 Branch Gateway and SIP phones 280 Dest Network En Default Remote Ext to Description Port App or Port Device Branch Protocol Dis State 9 50805 C TCP No Open B5800 Yes B5800 Configuration HTTP Manager Service Secured See B5800 optional 50804 config access 10 50808 C TCP No Open B5800 Yes B5800 System Status HTTP Manager Access B5800 Sys Status Access 11 50813 C TCP No Open B5800 Yes B5800 Security HTTP Manager Settings Access B5800 Secured See optional Sec 50812 Settings Access OPTIONAL I A 68 UDP Yes Open DHCP Srv Yes If configured B5800 DHCP obtains its IP address Cli from a remote server I B 443 TCP No Open Dect R4 Yes File transfer Web client HTTP access I C 1718 TCP No Open Branch No Offering H 323 service H323 Trunk to IP phones Disc l D 1719 TCP No Open IP Phones No Offering H 323 service RAS to IP phones l E 5061 TCP Yes Closed Session Yes Encrypted SIP TLS Manager signaling I F 50796 UDP Yes Closed Phone Mgr Yes Control of telephones Partner from Phone Manager App Soft Console l G 50804 C TCP No Open B5800 Yes B5800 Configuration HTTPS Manager Service Unsecured B5800 See 50805 Config Access I H 50812 C
8. Creating a backup of the system configuration using IP Office Manager Click v to revalidate the configuration and check that there are no conflicts between users and associated extensions 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 If you do not use this procedure to create a backup of the system configuration Procedure 1 Select File gt Open Configuration oa fF WO DP Start Manager Inthe Select B5800 Branch Gateway window select the appropriate system Click OK Enter the name and password for a service user account on that system Click OK A BOOTP entry for the system is created in Manager This also confirms communication between the Manager PC and the B5800 Branch Gateway system Select File gt Save Configuration As and save a copy of the configuration file onto the PC Creating a backup of the system configuration using System Manager About this task When you perform a backup of the system configuration from System Manager the backup is stored on the local B5800 Branch Gateway To store the system configuration backup on the System Manager server you must synchronize the B5800 Branch Gateway with System Implementi
9. Designated Processor means a single stand alone computing device Server means a Designated Processor that hosts a software application to be accessed by multiple users License types Designated System s License DS End User may install and use each copy of the Software only on a number of Designated Processors up to the number indicated in the order Avaya may require the Designated Processor s to be identified in the order by type serial number feature key location or other specific designation or to be provided by End User to Avaya through electronic means established by Avaya specifically for this purpose Copyright Except where expressly stated otherwise no use should be made of materials on this site the Documentation Software or hardware provided by Avaya All content on this site the documentation and the Product provided by Avaya including the selection arrangement and design of the content is owned either by Avaya or its licensors and is protected by copyright and other intellectual property laws including the sui generis rights relating to the protection of databases You may not modify copy reproduce republish upload post transmit or distribute in any way any content in whole or in part including any code and software unless expressly authorized by Avaya Unauthorized reproduction transmission dissemination storage and or use without the express written consent of Avaya can be a criminal as we
10. Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration Comments infodev avaya com October 2012 Egress ports for B5800 Branch Gateway and SIP phones Table column heading definitions Column Description heading 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 Network application protocol this is the name associated with the Protocol layer 4 protocol and layers 5 7 application En or Dis Optionally Enabled or Disabled this field indicates whether customers can enable or disable a layer 4 port changing its default port setting Valid values are Yes or No No means the default port state cannot be changed that is enable or disabled e Yes means the default port state can be changed that is enabled or disabled Default Port Default Port State a port is either open closed filtered or N A Stale e Open ports will respond to queries e Closed ports may or may not respond to queries and are only listed when they can be optionally enabled Filtered ports can be open or closed Filtered UDP ports will not respond to queries Filtered TCP will respond to queries but will not allow connectivity e N A is used for the egress default port state since these are not listening ports on the product Remote Device Remote Device this is the remote device th
11. 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 Configuration changes that cannot be synchronized and therefore should not be performed locally are e adding users or extensions editing user core attributes that is name number password or extension number e changing any of the following security configuration settings SMGRB5800Admin user settings SCEP settings certificates settings Web services settings Also note that the User Rights feature is not integrated with System Manager The User Rights feature is available only in the local IP Office Manager and is intended only for B5800 Branch Gateways that are not configured to be managed centrally through System Manager Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 163 Managing B5800 Branch Gateways from System Manager 164 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Chapter 10 Session Manager Configuration Thi
12. 1 Start Manager and connect to the B5800 Branch Gateway system 2 Select File gt Advanced gt Embedded File Management 3 Do the following a Select the first B5800 Branch Gateway system b Right click the file name PLDSkeys xml c Click Delete 4 Repeat Step 3 for each branch Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 95 Upgrading an R6 1 system to R6 2 96 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Chapter 6 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 Two other methods which require using IP Office Manager that is connected directly to the B5800 Branch Gateway system are available to perform an upgrade You can perform an upgrade using the IP Office Manager upgrade wizard or using the System SD card For more information see e Using the upgrade wizard on page 217 e System upgrade using the System SD card on page 256 R6 2 service pack installation checklist Descriptio
13. Click Commit Creating entity links For each SIP entity communicating with the Avaya Aura Session Manager an entity link needs to be configured That includes one for each B5800 Branch Gateway 1 On the System Manager console under Elements click Routing 2 In the left navigation pane click Entity Links 3 On the Entity Links page click New 4 In the Name field enter a name to describe this link 5 Inthe SIP Entity 1 drop down box select the name of the Session Manager system that is at one end of the link SIP Entity 1 must always be a Session Manager instance For a Session Manager line from a B5800 Branch Gateway system this should match the Session Manager set as the SM Address in the Session Manager line s configuration 6 In the Protocol drop down box select TCP When TCP is selected the Port field is automatically set as 5060 This is the port to which the SIP Entity 2 sends SIP requests 7 Inthe SIP Entity 2 drop down box select the name of the B5800 Branch Gateway system that is at the other end of the link When you selected TCP in the previous step the Port field was automatically set as 5060 8 Select the Trusted check box 168 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com 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 Ma
14. Each B5800 Branch Gateway system in the network should have a unique branch number That number is added as a prefix to the caller s extension number for calls routed from native extensions to the Avaya Aura Session Manager This means that native extensions are defined on the B5800 Branch Gateway without the branch prefix so that when the branch 140 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Administering a Session Manager line for each branch prefix is added the number is the correct length and format expected by Avaya Aura Session Manager The prefix is also used in the Avaya Aura Session Manager configuration to create unique dial patterns for routing calls to the appropriate B5800 Branch Gateway 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 gt Extension Renumber option This will add or remove a set value from all existing extension numbers in the configuration Procedure 1 From the System Manager console select the B5800 Branch Gateway device and click Ed
15. Lithium batteries A lithium battery is fitted to the real time clock on the control unit motherboard A 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 Replace only with the same or equivalent type recommended by the manufacturer Dispose of used batteries according to the manufacturer s instructions Lightening protection hazard symbols Lightning protectors The buildings lightning protectors must be verified as follow 1 Check the lightning protectors at the trunk cable entry point to the building housing the B5800 Branch Gateway system paying special attention to the lightning protection grounding Report any problems in writing to the telephone company 2 Equipment that is designed to be connected using internal wiring is typically not lightning protected Hence B5800 Branch Gateway extension cabling must not leave the building For installations where telephones and or other standard tip ring devices are installed in another building then lightning protection is required see Out of Building Telephone Installations on page 72 A Hazard Symbol The shock hazard symbol is intended to alert personnel to electrical hazard or equipment damage The following precautions must also be observed when installing telephone equipment e Never install telephone wiring during a lightning storm e Neve
16. Select the type of reboot you want to perform and click OK When the system reboots the software files are loaded in the primary folder of the System SD card Upgrading using an Optional SD card About this task This method allows an Optional SD card to be used as the source from which the System SD card is upgraded It only upgrades the software files it does not update embedded voicemail prompts 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 gt Advanced gt Recreate IP Office SD Card Select one of the following IP Office A Law e IP Office U Law This selection determines how the system operates when defaulted with the SD card installed in the System SD card slot 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 5 Insert the card into the Optional SD card slot on the control unit 6 Use one of the following procedures to copy the software from the Optional SD card to the System SD card e See Restoring software files from the Optional SD card using Manager on page 255 258 Implementing the Avaya B5800 Branch Gateway for an Ava
17. 2 Edit the following fields to match the System Manager field constraints a Edit the field lt csm deviceName gt name of device as added on System Manager lt csm deviceName gt to match the Managed Element name of the device as it was added in System Manager This field is exported as the System name field in the B5800 Branch Gateway configuration so it must be changed to match the Managed Element name of the device in System Manager 92 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Bulk importing of users b Ifthe lt givenName gt field does not contain an entry edit the field lt givenNames gt first name lt givenName gt where first name is the user s first name Note The entry for this field is derived from the Full Name field that is configured when a user is added to the system The Full Name field is configured in IP Office Manager under User gt User tab If the Full Name field was not completed when the user was added to the system the lt givenName gt field for the user will be blank when the user is exported to the xml file The lt givenNames field must contain a value Do not use punctuation characters such as or Do not begin the entry with a space c Edit the field lt loginName gt ogin name for the user lt loginName gt where login name for the user is in the format loginname somedomain com for example Extn5411000 a
18. 4 Configure the line settings as appropriate See Session Manager tab field descriptions on page 146 for more information 5 Click OK 6 Click the VoIP tab Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 145 Initial branch configuration 7 Click the Re Invite Supported check box to select this option 8 Click the Allow Direct Media Path check box to select this option You can select this option only if you selected Re Invite Supported 9 Configure the remaining fields as appropriate See VoIP tab field descriptions on page 147 for more information 10 Click OK 11 Select File gt Save Configuration The Send Configuration window appears and the Configuration Reboot Mode is set to Immediate Do not change the reboot mode Session Manager tab field descriptions Name Description Line Number This value is automatically assigned by B5800 Branch Gateway and should be unique for each line added to the configuration In Service The default setting is enabled This option can be used to manually take the Session Manager line out of service It does not reflect or set the actual state of the line SM Domain Name This name should match a SIP domain defined in the Session Manager system s SIP Domains table Unless there are reasons to do otherwise all the B5800 Branch Gateway systems in the Avaya Aura network can share the same domain Note See Viewi
19. Click Commit Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Chapter 13 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 Users can download the ISO images to a PC and choose to either burn a DVD for installation or transfer the ISO file to the target server for installation Note The B5800 Branch Gateway R6 2 administrator applications are provided on DVD They are not available for download from PLDS However once available you will be able to download B5800 Branch Gateway R6 2 Service Packs from PLDS You can check PLDS to determine if a later service pack or software release is available If updates do exist see the appropriate upgrade procedures contact Avaya or contact the Avaya Partner Service representative When you place an order for a PLDS licensed software product the license entitlements on the order are automatically created in PLDS Once these license entitlements are created you receive an e ma
20. Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 223 Additional system procedures SNMP 224 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration Characteristics Admin Software and Hardware Software e Country USA e Language English USA e Auto Answer Yes e AllowDial Yes e Allow User Setup Yes e Maximum Time on Call 480 e Country Code 1 e Area Code 732 e Number A blank e Number B blank ISDN Switch Protocol Standard ETSI Euro ISDN User Setup Admin Video Network IMUX e Auto Answer Yes e PIP Auto e Far Control of Near Camera Yes e MP Mode Auto Numbers blank SPID blank e Audio Quality 168KB s e Advanced Dialing Dial Channels in Parallel System Information Admin Software and Hardware Hardware Release 7 0 1 e Model VS 512 Camera NTSC e Video Comm Interface ISDN_Quad_BRI e Network Interface Type S T Interface Admin Video Network Admin Video Network Call Preference e MultiPoint Setup Auto e ISDN Video Calls H 320 Yes SNMP Simple Network Management Protocol is a standard network protocol that allows the monitoring and management of data devices across a network An SNMP agent can be built into network devices such as routers and hubs An SNMP manager application for example CastleRock or HP OpenView can then communicate with those devic
21. 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 The System Monitor password and System password are both set within the B5800 Branch Gateway system security settings 5 For Control Unit Type select Avaya B5800 Branch Gateway 6 Click OK Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 107 Administration software suite 108 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Chapter 8 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 Description Section 1 Confirm that your version of Avaya Aura System Manager is R6 2 and SP1 has been installed 2 Download IP Office Manager onto the System Manager server See Setting up System Manager to launch IP Office Manager on page 112 Note This task is not required if you have downloaded the B5800AdminLite exe file using the Upgrade Management link in System Manager 3 Install the shared PLDS license file on th
22. Remove the card Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 259 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 gt Phone User gt System Admin Enter your B5800 Branch Gateway user login code Select Memory Card Select System for the System SD card or Option for the Optional SD card Select Shutdown ona A WwW NY At the back of the control unit confirm that the appropriate memory card LED is off 7 Remove the card Shutting down a memory card using System Status Procedure 1 Open System Status and access the status output 2 In the navigation pane select System gt Memory Cards 3 Click System SD or Optional SD 4 At the bottom of the window click Shutdown 5 At the back of the control unit confirm that the appropriate memory card LED is off 6 Remove the card 260 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Memory card startup Memory card startup Reinserting a memory card into a system that is already switched on w
23. TCP No Open B5800 Yes B5800 Security HTTP Manager Settings Access Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration Comments infodev avaya com October 2012 Egress ports for B5800 Branch Gateway and SIP phones Dest Network En Default Remote Ext to Description Port App or Port Device Branch Protocol Dis State 9 B5800 Unsecured See Sec 50813 Settings Access For a description of the column headings see Table column heading definitions on page 283 Egress ports for B5800 Branch Gateway and SIP phones Dest Network En Default Remote Ext to Description Port App or Port Device Branch Protocol Dis State 1 53 UDP No Open DNS Yes DNS service to resolve DNS Server URL and IP addresses 2 69 UDP No Open Manager Yes B5800 Branch Gateway TFTP status configuration data program data See Port type ranges on page 275 for ranges 3 123 UDP No Open NTP Yes NTP RFC4330 NTP Server Service 4 162 UDP Yes Closed Trap Yes Trap generation from SNMP Receiver B5800 Branch Gateway 5 389 TCP Yes Closed LDAP Yes Import of directory LDAP Server information from LDAP database 6 500 UDP Yes Closed Security Yes Form IPSec IKE device associations with remote security devices Requires license Implementing the Avaya B5800 Branch Gateway
24. The file contents of the memory cards are displayed 4 Select File gt Backup System Files The contents of the primary folder on the System SD card are copied to the backup folder This process takes approximately 6 minutes Backing up the primary folder using the System Status application Procedure 1 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 Backup System Files The contents of the primary folder on the System SD card are copied to the backup folder This process takes approximately 6 minutes Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 249 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 gt Phone User gt System Admin 2 Enter your B5800 Branch Gateway user login code 3 From the menu select Memory Card 4 Select System Backup The contents of the primary folder on the System SD card are copied to the backup folder This process takes approximately 6 minutes About restoring from the backup folder When you restore from the
25. Acall is unanswered Abusy tone is received Areorder tone is received Avaya attests that this registered equipment is capable of providing users access to interstate providers of operator services through the use of access codes Modification of this equipment by call aggregators to block access dialing codes is a violation of the Telephone Operator Consumers Act of 1990 Automatic dialers When programming emergency numbers and or making test calls to emergency numbers e Remain on the line and briefly explain to the dispatcher the reason for the call e Perform such activities in the off peak hours such as early morning or late evenings Toll restriction and least cost routing equipment The software contained in this equipment to allow user access to the network must be upgraded to recognize newly established network area codes and exchange codes as they are placed into service Failure to upgrade the premises systems or peripheral equipment to recognize the new codes as they are established will restrict the customer and the customer s employees from gaining access to the network and to these codes FCC part 68 supplier s declarations of conformity Avaya Inc in the United States of America hereby certifies that the equipment described in this document and bearing a TIA TSB 168 label identification number complies with the FCC s Rules and Regulations 47 CFR Part 68 and the Administrative Council on Terminal Attachments
26. Authorization code conliguration Settings ccc csscivcensecescurssscnessurevedsdteswarreanay ennen r raana ENET nE 302 Appendix E Recommended courses for Avaya B5800 Branch Gateway training 303 Recommended COUISE Ss ciicsscesssreresicensnretessqeanarenensgaqnared ecsqannsarecasquenssrreasntennsrreasaerssarrressetansrressitessarrieasnians 303 RMSE A E E E A E r T 307 MOE eae 309 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 11 12 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura 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 Gateways are deployed in the distributed branch user model In the distributed branch user model call processing for the branch phones is provided locally Non IP phones are connected to the B5800 Branch Gateway and IP and certain SIP endpoints not including the Avaya 9600 SIP phones can be administered with B5800 Branch Gateway as their controller see Supported telephon
27. Configuration 6 In the Service Details tab click the check box for Under SMGR Administration to deselect this option Note This check box is checked by default and you are not able to administer the branch through Manager To be able to use Manager to administer the branch this check box must be unchecked 7 Click OK 8 Select File gt Save Configuration Disabling the System Manager administration feature for the branch from IP Office Manager Procedure 1 Start IP Office Manager 2 Select File gt Advanced gt Security Settings Note If the Security Settings option does not appear under Advanced do the following a Select File gt Preferences 160 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com 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 In the Security Service User Login window enter a user name and password of an account that has security configuration access to the B5800 Branch Gateway system The defaults are security and securitypwd 6 In the Security Settings pane select Services gt Configur
28. Standalone Voice Mail provides additional port capacity 40 ports provided on a Linux server You must have a Linux server installed to use this option e Endpoints support for the following new native phones operating in distributed branch user model 3740 3749 DECT R4 3810 digital wireless 9504 9508 digital 9611G B149 B159 and B179 conference phones former Konftel 1120E 1140E 1220 1230 SIP The following BCM digital phones DECT handsets 4xxx 7xxx series T7316E T7316 T7406E T7406 T7208 T7100 T7000 M7310 M7310N M7310 BLF M7324 M7324N M7208 M7208N M7100 M7100N ACU audio conference unit e Contact Center support for Contact Center service interoperability IP Agent or Avaya one X Agent in branch in Telecommuter mode with CC Elite calls transferred from B5800 Branch Gateway to contact center B5800 Branch Gateway handling VoicePortal transfer with UUI in SIP e Park and Page support for the Park and Page feature when the system voicemail type is configured as Embedded Voicemail or Standalone Voice Mail Park and Page is also supported on systems where Avaya Aura Messaging Modular Messaging over SIP or CallPilot is configured as the central voicemail system and the local Embedded Voicemail provides auto attendant operation The Park and Page feature allows a call to be parked while a page is made to a hunt group or extension Additional new features Enable voicemail instructions using DT
29. The card is labeled System SD BRANCH 2 Apply power to the external expansion modules The power outlet used must include a switch and in cases where the power cord includes an earth lead that outlet must have a protective earth connection 3 Apply power to the control unit The power outlet used must include a switch and the power outlet must have a protective earth connection When power is applied to the control unit the following occurs e The control unit begins loading firmware from the System SD card with which it will upgrade itself and the components installed in the control unit This process takes approximately a minute The end of this process is indicated by LED1 on each base card flashing every 5 seconds and LED9 on each base card fitted with a trunk daughter card flashing every 5 seconds Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 81 Hardware and software installation e 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 e 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 The B5800 Branch Gateway Initial I
30. This setting controls the 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 available If bandwidth between the B5800 Branch Gateway and Avaya Aura sites is sufficient change the first default preference to one of the G711 codecs Note that the specific setting for individual branch trunks and extensions can be set to override the system setting if necessary Important The configuration changes in the following procedure will require the B5800 Branch Gateway system to be rebooted 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 157 2 In the left navigation pane click System 3 Click the Codecs tab 4 Inthe Available Codecs section check the appropriate codecs and move them to the Selected section The order of the codecs listed in the Selected section indicates the preferred codec order for trunks and extensions that are using aut
31. Use this procedure to configure user PLDS access and define the default support site Procedure 1 Oo ON OOA From the System Manager console under Elements click Inventory 2 On the Inventory page click Upgrade Management gt User Settings 3 4 For the Use Avaya Support Site check box accept the default setting checked On the User Settings page click Edit Note Use Other Website only if a service technician directs you to use an alternate site for downloads Inthe SSO User Name field enter the user s SSO user name for PLDS Inthe SSO Password field enter the user s SSO password for PLDS Click the Use Proxy check box if the user has a proxy Inthe Host field enter the host details for this proxy server Inthe Port field enter the port number for this proxy server Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 101 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 gt Software Library 3 Click New 4 On the Add Software Library page in the Library Server Details tab do the following a Inthe Name field enter the appropriate name b Inthe IP Address field enter the IP address of the library server c Inthe Description field enter a description of
32. product and or status from the field 8 Click Search Entitlements Result All corresponding entitlement records appear at the bottom of the page 194 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com 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 Note If you move a specified number of activated license entitlements from one host to another by using the Rehost Move transaction in PLDS two new license files are generated e One license file reduces the number of license entitlements on the License Host from which you are moving license entitlements e One license file increases the number of license entitlements on the License Host to which you are moving license entitlements Install each of these license files on the appropriate server If you move all activated license entitlements only one license file is generated Install this new license file on the License Host to which you are moving license entitlements Remove the license file from the License Host from which you are moving all license entitlements Procedure 1 Type http plds avaya com in
33. 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 e Power cord for the power supply unit e Rack mounting kit optional e Cable labeling tags Connecting external expansion modules About this task Note External expansion modules should not be attached to a control unit that has power Procedure 1 If the system is being installed in a rack attach the rack mounting kit to the expansion module See Rack mounting on page 67 2 Attach the external expansion module s power supply but do not switch power on 3 Connect the expansion interconnect cable from the module s EXPANSION port to the EXPANSION port on the control unit Make careful note of the port used and include this detail on the cable label and any other system records OOCOOOGOCG o gocoocca VSSoneag peta tatatalalalay Oop 70 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com 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 outle
34. 11 to 20 for each branch that is to be managed from System Manager Enabling SNMP and polling support About this task In order for the B5800 Branch Gateway control unit to be discovered and polled by an SNMP manager its SNMP agent must be enabled and placed in the same read community as the SNMP manager Procedure 1 Start Manager and connect to the B5800 Branch Gateway system 2 In the left navigation pane click System 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 The community public is frequently used to establish communication and then changed at both the SNMP agent and manager ends for security 7 Click OK 8 Select File gt Save Configuration to send the configuration back to the B5800 Branch Gateway and then select reboot Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 127 Initial branch configuration 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 Bulk importing of devices Before y
35. 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 gt Phone User gt System Admin 2 Enter your B5800 Branch Gateway user login code 3 From the menu select Memory Card 4 Select Copy The contents of the System SD card are copied to the Optional SD card This takes at least 90 minutes and can take much longer About restoring from the Optional SD card The files in the primary folder on the Optional SD card can be copied to the primary folder on the System SD card Files with matching file names are replaced There are two levels of restore that can be performed e Restoring only configuration files from the Optional SD card Only the configuration file config cfg and the licenses file keys txt are copied from the Optional SD card to the System SD card e Restoring only software files from the Optional SD card All files in the primary folder except the configuration file config cfg and licenses file keys txt are coped from the Optional SD card to the System SD card This process does not restore embedded voicmail prompts This process takes approximately 5 minutes Being able to restore just the software files allows software files to be copied from an Optional SD card without affecting the existing configuration of that system Implementing the Avaya B5800 Branch Gateway for an Avaya A
36. B5800 Branch Gateway for an Avaya Aura Configuration October 2012 103 Upgrading an R6 2 system with an R6 2 service pack 104 The system displays the End User License Agreement page 9 Click Accept to download the software 11 12 13 14 15 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 Click the check box for the appropriate control unit Click Upgrade The Upgrade button is enabled only if the state of the device is yellow On the B5800 Branch Gateway Upgrade Configuration page select the appropriate library and the release to which you want to upgrade By default the library which has the latest upgrade package is automatically selected Do one of the following e Click Now to start the upgrade e Click Later to schedule the upgrade at a specified time To view the upgrade status on the Manage Software page click the B5800 Branch Gateway being upgraded then click Status When the upgrade is complete a final status window is displayed The state of the device turns green showing that it has the latest firmware installed Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Chapter 7 Administration software suite The IP Office administration software applications are installed on th
37. B5800 Branch Gateway training 306 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Centralized management Centralized trunking Distributed Branch user model Distributed trunking Local extension Local management Mixed mode trunking Native extension Rainy day Sunny day Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration Glossary This term is used to describe a central management system that delivers a set of shared management services and provides a single access interface to administer multiple branch locations and multiple distributed B5800 Branch Gateway users This term describes routing outgoing external calls from the branch sites to the central site in order to utilize the central sites PSTN trunks The same applies for distributing incoming PSTN calls from the central site to the appropriate branches This term describes a B5800 Branch Gateway deployment model where call processing for the branch phones is provided locally Non IP phones are connected to B5800 Branch Gateway and IP and certain SIP endpoints not including the Avaya 9600 SIP phones can be administered with B5800 Branch Gateway as their controller Access to and from the rest of the Avaya Aura network is via the B5800 Branch Gateway system s Avaya Aura Session Manager link across the enterprise WAN This connection allows for VoIP conn
38. 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 e An Avaya System SD card must be present in this slot at all times This card holds copies of the B5800 Branch Gateway firmware and configuration and is used as the control units non volatile memory e Each System SD card has a unique Feature Key serial number which is used for generating and validating licenses entered into the B5800 Branch Gateway configuration e The card stores the prompts for Embedded Voicemail operation and acts as the message store for embedded voicemail messages e Prior to any planned shutdown or restart of the B5800 Branch Gateway system the current configuration running in the system s RAM memory is copied to the primary folder on the System SD card and to the systems non volatile memory e Following a restart the software in the primary folder is loaded by the control unit If the required software is not present or valid a sequence of fallback options is used see Booting from the SD Cards on page 244 for more information e Following a restart the configuration file if present in the primary folder is loaded by the control unit If no file is present the system will check for a file in its internal non volatile memory If no copy is found it will gene
39. Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com 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 You can shut down the system using a 1400 1600 or 9600 series phone excluding XX01 XX02 and XX03 models Unlike Manager a system phone user cannot select an indefinite shutdown A system phone user can set a timed shut down of between 5 minutes and 24 hours Your Login Code is used to restrict access to some system administration functions on the phone Procedure 1 Select Features gt Phone User gt System Admin 2 Enter your B5800 Branch Gateway user login code 3 From the menu select System Shutdown 4 Select a time period for the shutdown It must be in between 5 minutes and 24 hours 5 Select Done and then Confirm to begin the shutdown Shutting down the system using the AUX button Procedure On the control unit press the AUX button for more than 5 seconds Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration
40. Branch Gateway for an Avaya Aura Configuration October 2012 209 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 206 2 Remove the card or external expansion module Note The card slot or expansion port used as the replacement must be installed in the same position 3 Install the replacement using the appropriate procedure for the type of component See Base and trunk card installation on page 59 or Connecting external expansion modules _on page 70 for more information 4 Restart the B5800 Branch Gateway system 5 Use Manager to configure the new trunks or extension users Replacing a component with one of lower capacity About this task If you are replacing a component with one of the same type but with lower capacity when restarted the B5800 Branch Gateway system configuration must be edited to remove redundant entries Procedure 1 Turn the B5800 Branch Gateway system off See System shutdown on page 206 2 Remove the card or external expansion module Note The card slot or expansion port used as the replacement must be installed i
41. Check the SIP Registrar Enable check box This is necessary for support of SIP extensions directly by the branch or when providing survivability support for Avaya Aura SIP extensions 7 Click OK 8 Click the SIP Registrar tab 9 Configure the fields on this tab as appropriate See SIP Registrar tab field descriptions on page 155 for more information Click OK Select File gt Save Configuration The Send Configuration window appears and the Configuration Reboot Mode is set to Immediate Do not change the reboot mode SIP Registrar tab field descriptions Name Default Description Domain Name Default Blank This is the local SIP registrar domain name that will be needed by SIP devices in order to register with the B5800 Branch Gateway If this field is left blank registration is against the LAN IP address For our examples we have been using a domain example com Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 155 Initial branch configuration Name Default Description Layer 4 Protocol Default UDP TCP TLS This is the transport protocol for SIP traffic between the DET SIE pols vee B5800 Branch Gateway and e TCP SIP port 5060 SIP extension devices e TLS SIP port 5061 Challenge Expiry Time Default 10 The challenge expiry time is sec used during SIP extension registration When a device registers the SIP Registrar
42. Click OK Click on General The general security settings are displayed in the main display area Next to the Password field click on Change and enter a new password for the security administrator Click on File gt Configuration to exit security configuration mode and return to the B5800 Branch Gateway configuration Changing the remote user password About this task The B5800 Branch Gateway configuration contains a user whose password is used as the default for remote dial in access to the B5800 Branch Gateway network Use this procedure to change this user s password Procedure 1 Start Manager and connect to the B5800 Branch Gateway system 2 In the left navigation pane click User 3 4 On the User tab do the following In the user list click RemoteManager a Inthe Password field enter a new password for the user b Inthe Confirm Password field enter the new password again 5 Click OK 6 Select File gt Save Configuration Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 205 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 A
43. Gateways to System Manager arides a A 125 About the xml file containing the B5800 Branch Gateway CEVICES rrisin ean ereak S raK 129 About upgrading B5800 Branch Gateway software 16 activating license entitlements c ccceceees 191 Activating license files cceeceeeeeeeeeeeeeeeeaeeeeeeeeees 115 activation PFOCESS ceceeeeeeeeeecceecaeceeeeeeeeeeeteeeeeeees 190 Adding distributed users to System Manager 185 additional system procedures cscccsecseeeeeeeeeeees 203 Administering USCIS ccecseecsecceeecaeceeeeeeeeeeeeeeeees 185 centralized USES ccccceeeececceeeseceeceueeeeeeeeseeees 185 distributed users seececceeeeeeeeeeeeseeeeeeeeaeeenes 185 Alternate Route Priority Level eseeeeeeee 294 Alternate Route Wait Time cccccesssseeeeeseseeeeees 294 Analog aeie aaia EE a AEE a E aa Ea 75 phone barrier DOXES eeeeeeeeeeeeeeeereeeaeeee 75 ARS EE IE EE E A AE 294 AUI siirsi anaE Eaa 44 Codec CONVESSION ccssecceceeesseeeeeeaeseeeeneeseeeeeees 44 Authorization code configuration settings 302 Authorization codes ccccccesscceeeneeeeeceaeeeeeseaseeees 299 Automatic codec preference settings cccce 144 Avaya Mentor videos c cscccccceeceeeeeeeeeeeeeeeteeeteeees 31 B B5800 Branch Gateway administration tools 199 using SAL tO ACCESS n 1
44. Licensing on page 16 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 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 191 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 However you can remove line items or specify a number of licenses to activate from the quantity available 4 Enter the License Host information You can either create a new license host or use an existing license host 5 Click Next to validate the registration detail 6 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 This is the Feature Key Serial Number printed on the System SD card You must add dashes between pairs of digits to provide the
45. Manager TFTP log are visible at the same time Switch off power to the control unit 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 Enter AT upper case An OK response appears If OK does not appear check the settings of your terminal program Enter AT X Multi Sector Erase response appears The control unit then requests the bin file that is stored on the System SD card If the files do not appear to be transferring check that the IP address shown in the TFTP log matches the BOOTP entry Adjust the BOOTP entry if necessary When the file transfers are completed the system reboots Reset button The Reset button is on the control unit Pressing the button while the control unit is starting up will pause the start up until the button is released The effect of pressing the button during normal operation will depend on how long the button is pressed and is indicated by the CPU LED Press Duration CPU LED Action Summary seconds Oto5 Off None None 5 to 10 Orange Reboot when free Reboot when free with new incoming outgoing call barring A reboot using the reset button is recorded in the audit trail 10 to 30 Flashing orange Erase Erase the configuration alarm configuration log and audit trail Immediate immediate reboot reboot without waiting for active calls to end See About
46. Office Manager on page 215 for more information Procedure 1 Start Manager 2 Select File gt Advanced gt Upgrade 3 4 Click Upgrade Click the check box for the appropriate system The UpgradeWiz scans for B5800 Branch Gateway modules using the address specified in the Unit Broadcast Address field If the expected control units are not shown adjust the address in the Unit Broadcast Address field and click Refresh The current version of each B5800 Branch Gateway bin file held in the control units memory is displayed This is regardless of whether that bin file is currently being used by any module in the system In the Available column Manager lists the versions of software it has available If Manager detects that there is a higher version available the check box for that row is automatically selected 6 Click the check box for the modules you want to upgrade 7 Click the check box for Validate When this option is selected the upgrade wizard checks the amount of free RAM memory available in the control unit to temporarily store the new bin files If insufficient memory is available you will be prompted whether to continue with an off line upgrade or cancel upgrading If offline is selected the system is rebooted into offline mode It may be necessary to use the Refresh option within the upgrade wizard to reconnect following the reboot Validate upgrade can then be attempted again to check the amount o
47. Prefix International Prefix 4 Select File gt Save Configuration Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 137 Initial branch configuration SIP trunk prefixes The prefix fields Prefix National Prefix Country Code and International Prefix are available with the SIP line settings These fields are used in the following order 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 If the incoming number does not begin with either the National Prefix or International Prefix then the Prefix is added For example if the SIP line is configured with the following prefixes the numbers are processed as described in the table below e Line Prefix 9 e National Prefix 90 e International Prefix 900 e Country Code 44 Number Received Processing Resulting Number 441707362200 Following rule 1 above the 901707362200 is replaced with the International Prefix 900 resulting in 900441707362200 The number now matches the International Prefix 900 and Countr
48. Status The IP Office System Status application is a monitoring and reporting tool that provides a wide range of information about the current status of the system It can report the available resources and components within the system and details of calls in progress Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 77 Hardware and software installation Details of the number of alarms are recorded and the time and date of the most recent alarms e 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 Installers and maintainers must understand how to run System Monitor when necessary as Avaya may request copies of System Monitor traces to resolve support issues PC requirements The minimum Microsoft Windows PC requirements for the B5800 Branch Gateway system tools are provided in the following table If other applications are to be installed on the PC then those individual requirements should also be met Requirement Minimum Recommended Processor 600MHz Pentium or AMD 800MHz Pentium or AMD Opteron AMD Athlon64 Opteron AMD Athlon64 AMD Athlon XP AMD Athlon XP RAM 128MB 256MB HD Space 1GB 800MB for NET2 1 4GB 800MB for NET2 200MB for Manag
49. Write src port 4153 dst port 69 278 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Ingress ports for B5800 Branch Gateway and SIP phones lt 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 Network En Default Remote Ext to Description Port App or Port Device Branch Protocol Dis State 9 1 22 TCP No Open Admin Yes System mgmt requiring SSH terminal or shell access Remote SAL maintenance Gateway 2 69 UDP No Open NM Yes B5800 Branch Gateway TFTP Manager status configuration data program data See Port type ranges on page 275 for ranges 3 80 TCP No Open NM Yes Web client access Inter HTTP Manager B5800 Directory Exchange optional 4 123 UDP No Open NTP Yes NTP RFC4330 NTP Server Service 5 161 C UDP Yes Closed Admin Yes Read only access to SNMP terminal or MIB entries NMS 6 5060 TCP SIP No Open Yes SIP Signaling 7 49152 UDP Yes Open IP Phones Yes Dynamically allocated 53247 C RTP RTCP ports used during VoIP RTCP Collector calls for RTP and RTCP traffic The port range can be adjusted through the System gt Gatekeeper tab 8 50802 TCP Yes Open B5800 Yes TCP Discovery Who Is Manager
50. You can also manually enable the System Manager administration feature for a branch using either of the procedures listed below and clicking the check box for Under SMGR Administration to enable the feature To disable the System Manager administration feature for a branch see one of the following e Disabling the System Manager administration feature for the branch from System Manager on page 160 e Disabling the System Manager administration feature for the branch from IP Office Manager on page 160 To synchronize the B5800 Branch Gateway with System Manager see Synchronizing B5800 Branch Gateway with System Manager on page 162 Some configuration changes cannot be synced with System Manager See Configuration changes performed through Manager that cannot be synced with System Manager on page 162 for more information Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 159 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 In the Security Settings pane select Services gt
51. a 209 Replacing a component with one of higher Capacity eecceesseeseeneeseceeeseeeconeteneeneeeeesenaneneeessaeess 210 Replacing a component with one of lower Capacity nc cissscricenss cca vereseccacsminsiveomaecseriersennsoatienss 210 Replacing a component with one of a different type ees eseeeseceeseneeeeceeeeseeseeeeeeeteeeeteeeeeeeeeanees 211 Adding a new compone Mi i ssrccsstiiiscndsnme tireless n Jetta 211 Permanently removing a compone Miesciissiircnin a Ra 212 Swapping ONS SIO USES aieri iarencectabiniss coczantanencedatcnneeteneauaanrpacenatummberineataamysdbeacsmmrscncaats 212 AOU SHS extension MMD Sainani aae TAAA S SEE aN a S 213 Remumbenmng alaxtensione and USG S ae cess soaccas ce akivuseccveg auaddaceadeagaasdoddaas eaebialeaanseoaiinioccneneanaiued 213 Changing a user 2 extension numba ansieae n N EN EN A 214 Creating a backup of the system configuration using IP Office Manager essessereereerserrrerrreerrrerres 215 Creating a backup of the system configuration using System Managet cccceeseeeeseeeeeeeeesneeeeeeeeeaes 215 Upgrades using IF Cre Plas sarcasvarran desibeaetertesevauedareete tademeeeeulentcresvuleamcxanoludmaetouieemaesiiniets 216 WIS IG me upgrade Wiza eiiiai des bossabiiiidueitre tii pateices tiapri siidadtediniaatanlteeinies 217 Restoring the system configuration using System ManaQel ccceeceeeeeeneeeeeeseeeeeeeesesaeeeaeeeeeeeenaeees 218 External Sutil pont EXT OIF J score e a T ar EEE
52. and Embedded File Management you must access Manager that is installed on a PC that resides within the customer network e System Status Application Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 199 Standalone SAL Gateway for remote service 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 e System Monitor Tier3 4 tool only System Monitor is an administration tool that provides detailed traces of all activity on the B5800 Branch Gateway system Note You are able to use SAL to access the System Monitor application that is installed on a PC that resides within the customer network Avaya Aura System Manager System Manager is a central management system that delivers a set of shared management services and a common console for System Manager and its components System Manager provides a single access interface to administer multiple branch locations and multiple distributed or centralized B5800 Branch Gateway users For more information about the B5800 Branch Gateway administration tools and System Manager see Management on page 14 and Administration software suite on page 77 SAL Gateway installation and registration To install SAL Gateway see Chapter 2 in Secure Access Link 2 1 SAL Gatewa
53. are as follows e Administering Avaya Aura System Manager e Administering Avaya Aura Session Manager document number 03 603324 e Avaya IP Office Manager Release 6 2 document number 15 601011 e Implementing Embedded Voicemail for B5800 Branch Gateway Release 6 2 document number 18 604098 e Implementing Standalone Voice Mail for B5800 Branch Gateway Release 6 2 document number 18 604088 e Avaya B5800 Branch Gateway Solution Overview Release 6 2 document number 18 603903 e Avaya WebLM Administration Guide e Administering Avaya WebLM standalone Avaya Mentor videos Avaya Mentor is an Avaya run channel on YouTube that includes technical content on how to install configure and troubleshoot Avaya products Visit http www youtube com AvayaMentor and do one of the following e Enter a key word or key words in the Search channel to search for a specific product or topic e Click the name of a playlist to scroll through the posted videos Training Avaya University provides a wide range of training courses for B5800 Branch Gateway and its associated applications This includes courses necessary for B5800 Branch Gateway resellers Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 31 B5800 Branch Gateway overview to become Avaya Authorized Channel Partners and for individuals to achieve B5800 Branch Gateway certification Details of courses can be found on the Avaya University web s
54. available see Branch PSTN call routing examples on page 289 The examples demonstrate the following options e Centralized call control on page 289 External calls at a branch site can be rerouted to be dialed out at another site This can be done for reasons of call cost and call control For example the central site may have a bulk call tariff for national and international calls that would benefit all branches e Branch PSTN Override on page 292 Having configured the branch to send outgoing external calls to the Avaya Aura Session Manager for onward routing there may be cases where a specific number should still be routed via the branches own PSTN trunks e PSTN Fallback on page 294 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 However the main aim should be as follows e To keep the branch configuration as generic as possible i e to use the same PSTN call control in all branch configurations This simplifies maintenance of multiple branches e To centralize as much of the PSTN call control in the Avaya Aura Session Manager as possible Again this simplifies maintenance and control 38 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configu
55. 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 In addition to the existing environmental requirements on page 47 the following requirements apply when wall mounting a unit e The wall surface must be vertical flat and vibration free e The brackets must be used as shown with the deeper tray like bracket used at the bottom of the wall mounted control unit e Only the screws M3 x 6mm provided with the mounting kit should be used to attach the brackets to the control unit Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 65 Hardware and software installation 700430150 Fix to solid vertical surface using wall fixings suitable for the wall type A Orientation must be as shown A minimum clearance of 500mm 19 7 is required on all sides 66 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com 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 The rack mounting kit includes e A rack mounting bracket and screws for attachment of the
56. bracket to the unit e Nuts and bolts for rack attachment e Brackets and cable ties for cable tidying Environmental requirements In addition to the environmental requirements on page 47 the following factors must be considered when rack mounting a unit e Rack positioning Ensure compliance with the rack manufacturers safety instructions For example check that the rack legs have been lowered and fixing brackets have been used to stop toppling e Elevated operating ambient If installed in a closed or multi unit rack assembly the operating ambient temperature of the rack environment may be greater than room ambient Therefore consideration should be given to installing the equipment in an environment compatible with the maximum ambient temperature Tma specified by the manufacturer Operating temperature 0 C 32 F to 40 C 104 F Operating humidity 10 to 95 non condensing e Reduced air flow Installation of the equipment in a rack should be such that the amount of air flow required for safe operation of the equipment is not compromised Proper ventilation must be maintained The side ventilation slots on the control unit should not be covered or blocked e Mechanical loading Mounting of the equipment in the rack should be such that a hazardous condition is not achieved due to uneven mechanical loading e Circuit overloading Consideration should be given to the connection of the equipment to the supp
57. capabilities including its ability to meet both current and planned voice and data needs e A determination of network objectives including the dominant traffic type choice of technologies and setting voice quality objectives e 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 e An outline of the expected network assessment targets is Test Minimum Assessment Target Latency Less than 150ms Packet Loss Less than 3 Duration Monitor statistics once every minute for a full week Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 39 Planning 40 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Chapter 3 Installation requirements This chapter provides information about power supplies cables grounding and environmental and space requirements for installing the B5800 Branch Gateway control unit and external expansion modules The B5800 Branch Gateway control unit can be mounted on the wall if no external expansion units are included in the installation If the installation includes external expansion modules the control unit and external expansion modules can be mounted into a standard 19 inch rack system Power supply backup UPS The use
58. connections lightning protection Main Building Control Unit C COs4x4 o Barrier Box External Contact Closure Device e 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 Typically this would be gas tube protection provided by the local telephone company The ground wire must be thick enough to handle all the lines being affected by indirect strike at the same time Connection type Protection device type Requirement DS phone extensions External expansion module DS ports only ITWLinx towerMAX DS 2 Supports up to 4 connections This device was previously referred to as the Avaya 146E Analog phone extensions Phones external expansion module POT or Phone ports only Barrier box Supports a single connection Maximum of 16 on any expansion module e Connection from the expansion module to the phone must be via a surge protector at each end and via the primary protection point in each building e The expansion module control unit and IROB devices must be connected to the protective ground point in their building e The between buil
59. different applications Conflicts can occur in an enterprise when a port with one meaning is used by two servers with different meanings Dynamic ports Dynamic ports sometimes called private ports are available to use for any general purpose This means there are no meanings associated with these ports similar to RFC 1918 IP Address Usage These are the safest ports to use because no application types are linked to these ports The dynamic port range is 49152 65535 Sockets A socket is the pairing of an IP address with a port number An example would be 192 168 5 17 3009 where 3009 is the socket number associated with the IP address A data flow or conversation requires two sockets one at the source device and one at the destination device The data flow then has two sockets with a total of four logical elements Each data flow must be unique If one of the four elements is unique the data flow is unique The following three data flows are uniquely identified by socket number and or IP address 276 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Firewall types e Date flow 1 172 16 16 14 1234 10 1 2 3 2345 e Date flow 2 172 16 16 14 1235 10 1 2 3 2345 e 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 sam
60. e backup contains a copy of the primary folder at some previous point A backup copy of the primary contents to this folder can be invoked manually using Manager or SSA or as part of the B5800 Branch Gateway software upgrade using Manager e lvmail a sub folder that is used to store individual user and group mailbox messages name recordings and announcements used by Embedded Voicemail The storage capacity for Embedded Voicemail is limited to 15 hours regardless of the capacity of the card Mailbox messages and greetings are stored in a sub folder of the dynamic folder e AAG a sub folder that is used to store embedded voicemail auto attendant greetings e doc contains initial installation documentation for B5800 Branch Gateway Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 243 SD card management e dynamic contains files used by the B5800 Branch Gateway and retained through a reboot of the B5800 Branch Gateway system e 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 When being powered up the control unit looks for a valid bin
61. in the Variable value field change the value to match the version of B5800AdminLite for example 6 2 Click OK Click OK for each subsequent dialog box and then click Apply 8 If the PC is running Windows XP do the following a papo h i From the Start menu right click My Computer Click Properties In the System Properties dialog box click the Advanced tab Click Environment Variables In the Environment Variables dialog box in the User variables for lt name gt area select AVAYAB5800_VER Click Edit In the Edit User Variable dialog box in the Variable value field change the value to match the version of B5800AdminLite for example 6 2 Click OK Click OK for each subsequent dialog box and then click Apply 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 114 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 114 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Activating license files About this task Perform this task to install IP Office Manager from the System Manager server to a PC Once you perform this task the next time you attempt to view or edit a B5800 Branch Gateway device from System Man
62. individual packet rather than blindly copying bytes ALGs can also send alerts via email alarms or other methods and keep log files to track significant events Hybrid Hybrid firewalls are dynamic systems tracking each connection traversing all interfaces of the firewall and making sure they are valid In addition to looking at headers the content of the Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 277 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 Since a port is a place where information goes into and out of a computer port scanning identifies open doors to a computer Port scanning has legitimate uses in managing networks but port scanning also can be malicious in nature if someone is looking for a weakened access point to break into your computer Firewall policies The goals of firewall policies are to monitor authorize and log data flows and events They also restrict access using IP addresses port numbers and application types and sub types This appendix focuses on identify
63. install the license file on the B5800 Branch Gateway see Using Manager to deliver license files to the branches on page 117 Note If the B5800 Branch Gateway is centrally managed by System Manager to install the individual PLDS license file on the B5800 Branch Gateway using Manager you must first disable the System Manager administration feature for the branch See Disabling the System Manager administration feature for the branch from System Manager on page 160 After you upload the 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 See Using Embedded File Management to install a PLDS license on page 118 for more information 116 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Activating license files Installing the shared PLDS license file on the System Manager WebLM server Before you begin Ashared B5800 Branch Gateway license file has been activated with the Host ID of the WebLM server See Activating license entitlements
64. is used for an Avaya Aura Session Manager line currently thought to be out of service e 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 e If no response is received within 32 seconds SIP Timer F the line is treated as being out of service e If the line is out of service and call comes from the trunk the trunks status is changed back to in service e If the line is in service a call may fail due to either being unable to deliver the message or receive a 100 response within a configured timeout The line will not go out of service because this may be a temporary failure due to a busy system 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 Setting up outgoing call routing About this task For calls from extensions on the B5800 Branch Gateway system to other numbers within the network system short codes are used to route the calls to the Avaya Aura Session Manager line The Avaya Aura Session Manager then performs the routing to determine where the call shoul
65. left navigation pane select PLDS License 6 Click OK 7 Select File gt Save Configuration Adding an Avaya Aura Session Manager line About this task Use this procedure to add an Avaya Aura Session Manager line to the B5800 Branch Gateway system configuration If multiple Avaya Aura Session Managers are available at the headquarters site an additional Avaya Aura Session Manager line can be added for Session Manager line redundancy The two Session Manager lines are prioritized based on the line number The lower line number is considered the primary Session Manager line Based on the priority of the Session Manager lines designated by the line number the active line to which the B5800 Branch Gateway sends all calls will always be the highest priority Session Manager line in service See the IP Office Manager online help and Avaya Aura Session Manager line redundancy on page 150 for more information Important The configuration changes in the following procedure will require the B5800 Branch Gateway system to be rebooted 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 157 2 In the left navigation pane click Line 3 Click the New icon and select SM Line
66. may be a temporary failure due to a busy system e In addition each Avaya Aura Session Manager line can be manually set to in or out of service using the In Service option on the Avaya Aura Session Manager line s Session Manager tab Enabling branch SIP extension support About this task Before adding any SIP extensions the B5800 Branch Gateway system must be enabled for SIP extension support Use this procedure to configure the B5800 Branch Gateway to support the addition of SIP extensions Important The configuration changes in the following procedure will require the B5800 Branch Gateway system to be rebooted 154 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Enabling branch SIP extension support Procedure 10 11 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 157 In the left navigation pane click System 3 Click the LAN1 or LAN2 tab depending on which branch site LAN interface will be used for the SIP extensions Inthe LAN Settings tab make a note of the IP Address and IP Mask details as these will be required during the SIP extension configuration 5 Click the VoIP tab 6
67. optimize external PSTN trunk usage The B5800 Branch Gateway is a full PABX and by default uses its own PSTN trunks However it can be configured to make and receive external calls via the central Avaya Aura Session Manager A combination of these methods can be used for PSTN calls based on the call type Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 13 B5800 Branch Gateway overview local national international time of day or even individual user See Branch PSTN call routing examples on page 289 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 Standalone Voice Mail is also available for B5800 Branch Gateway systems when additional port capacity is required Centralized voice messaging systems Avaya Aura Messaging or Modular Messaging over SIP can also be configured When using either of these centralized voice messaging systems you are still able to use Embedded Voicemail or Standalone Voice Mail at each branch to provide auto attendant operation and announcements for waiting calls For more information see Voicemail options on page 171 Management The primary method for configuring and managing the branches in a B5800 Branch Gateway system is centrally using Avaya Aura System Ma
68. or Avaya Aura Messaging without the external dialing prefix b Inthe Feature drop down box select Dial3K1 c Inthe Telephone Number field set this to N to match the whole number in the Code field Note For a setup where the voicemail mail box numbers configured on Modular Messaging or Avaya Aura Messaging are the same as the caller s DID the short code to route the PSTN call should be configured so that the caller ID is withheld To do this enter a w in the Telephone Number field of the short code This ensures that during rainy day operation the voicemail system does not automatically go to the voicemail mail box of the caller based on the caller ID d Inthe Line Group Id drop down box select the line group ID being used for the branch s PSTN trunks The default is 0 6 Click OK The ARS now has two short codes that will potentially match external national calls However one is a more exact match for certain calls and therefore will be applied Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 293 Branch PSTN call routing examples to those calls ARS ARS Route Id Secondary Dial tone Route Name SystemTone v Dial Delay Time System Default 4 Check User Call Barring In Service Out of Service Route lt None gt v l Time Profile Out of Hours Route lt None gt v Code Telephone Number Feature Line Group Id 11 911 Dial Emergency 0 i Remove 911
69. or documentation provided by Avaya Avaya is not responsible for the accuracy of any information statement or content provided on these sites and does not necessarily endorse the products services or information described or offered within them Avaya does not guarantee that these links will work all the time and has no control over the availability of the linked pages Warranty Avaya provides a limited warranty on its hardware and Software Product s Refer to your sales agreement to establish the terms of the limited warranty In addition Avaya s standard warranty language as well as information regarding support for this Product while under warranty is available to Avaya customers and other parties through the Avaya Support website http support avaya com Please note that if you acquired the Product s from an authorized Avaya reseller outside of the United States and Canada the warranty is provided to you by said Avaya reseller and not by Avaya Software means computer programs in object code provided by Avaya or an Avaya Channel Partner whether as stand alone products or pre installed on hardware products and any upgrades updates bug fixes or modified versions thereto Licenses THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE HTTP SUPPORT AVAYA COM LICENSEINFO ARE APPLICABLE TO ANYONE WHO DOWNLOADS USES AND OR INSTALLS AVAYA SOFTWARE PURCHASED FROM AVAYA INC ANY AVAYA AFFILIATE OR AN AU
70. pane click Upgrade Management gt Manage Software 3 On the Manage Software page click Get Inventory 4 Do one of the following Click Now to get the device inventory e Click Schedule to get the device inventory at a later time Setting B5800 Branch Gateway SNMP attributes Procedure 1 From the System Manager console under Elements click Inventory 100 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com O oa A WwW NY Configuring user PLDS access On the Inventory page on the left navigation pane click Manage Elements Click the check box for the appropriate element Click Edit On the Edit lt system name gt page click the Attributes tab Inthe SNMP Attributes section do the following a For the Version click the radio button for V1 b Inthe Read Community field enter the read community of the device c Inthe Write Community field enter the write community of the device d Inthe Retries field select the appropriate number of times the application should poll the device without receiving a response before timing out e Inthe Timeout ms field select the appropriate number of milliseconds that the application should poll the device without receiving a response before timing out f In the Device Type drop down box select the appropriate device type Click Commit Configuring user PLDS access About this task
71. phones It also includes the prompt files for embedded voicemail operation This procedure can be used to upgrade an existing SD card to match the file set installed with Manager For the card to be used in the System SD card slot the card must be an Avaya SD Feature Key card The card must be correctly formatted See Formatting an SD card on page 246 If the card contains any dynamic system files for example SMDR records they are temporarily backed up by Manager and then restored after the card is recreated This procedure takes approximately 15 minutes Procedure 1 Insert the SD card into a card reader on the Manager PC Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 247 SD card management Note Do not remove the SD card Removing the SD card will interrupt the upgrade 2 Select File gt Advanced gt Recreate IP Office SD Card gt 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 Viewing the card contents About this task Using Manager you can view the folders and files on the System SD card and the Optional SD card Procedure 1 Start Manager 2 Select File gt Embedded File Management 3 From the Select
72. request on the network for new software Manager responds and starts transferring the software using TFTP Erasing the core software via the boot loader Procedure 1 2 oN O O Start Manager In the BOOTP entries check that there is an entry that matches the MAC address IP address and bin file used by the system An entry is normally automatically created when a configuration has been loaded from the B5800 Branch Gateway system If an entry is not present do the following a Create a new entry manually The MAC address and IP address can be found in the control unit settings in the configuration file b Close Manager c Restart Manager Under File gt Preferences ensure that Manager is set to 255 255 255 255 Also check that Enable BootP Server is checked Select View gt TFTPLog Check that the required bin file is present in Manager s working directory Attach the serial cable between the PC and the DTE port on the control unit 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 230 Within a HyperTerminal session the current settings are summarized across the base of the screen Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 237 Additional system procedures 10 11 12 13 14 Arrange the program windows so that the terminal program and
73. 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 e Short Code 1500 e Number e Feature Dial e Line Group 601 the So8 port number 2 Create an incoming call routing that routes the appropriate calls to that short code For this example the following is used e Line Group 95 identifies calls using the PRI lines configured above e Destination 1500 the short code created above e Bearer Any 3 To allow the video device on the SO port to make outgoing calls to the PRI lines also requires a short code For this example the following is used e Code 91N e Number N e Feature Dial e Line Group 95 Polycom Video module settings The Polycom modules used in the previous example were the Viewstation 128 Viewstation 256 and Viewstation MP The Polycom module must have software that supports Standard ETSI ISDN European ISDN and have its ISDN Switch Protocol setting set to Standard ETSI Euro ISDN The following were the settings used during testing Characteristics Admin Software and Hardware Software e Polycom View Station 512 MP e Software 7 0 1 e NTSC UIS Interface e Network Interface S T Interface e View Station PVS 1419 e ISDN Version IEUS v18 a00320 Admin General Setup Admin Video Network ISDN Video Network
74. 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 mib AdminCD snmp_mibs IPOffice on B5800 Branch Gateway Admin DVD INET ADDRESS MIB mib AdminCD snmp_mibs Standard on B5800 Branch Gateway Admin DVD INTEGRATED SERVICES MIB AdminCD snmp_mibs Standard on B5800 Branch Gateway Admin DVD DIFFSERV DSCP TC mib AdminCD snmp_mibs Standard on B5800 Branch Gateway Admin DVD DIFFSERV MIB mib AdminCD snmp_mibs Standard on B5800 Branch Gateway Admin DVD IPO PHONES MIB mib AdminCD snmp_mibs IPOffice on B5800 Branch Gateway Admin DVD 2 In SMNPc select Config gt MIB Database 3 Select Add and select the MIB files listed above in the order listed Castlerock SNMPc V5 0 1 Procedure 1 Copy all of the B5800 Branch Gateway MIBs and standard MIBs from the B5800 Branch Gateway Administrator Applications DVD to the SNMPc mibfiles directory 2 Inthe SNMPc mibfiles directory open the files STANDARD mib and SNMPv2 SMI mib in Notepad Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 227 Additional system procedures CoN OA Inthe SNMPv2 SMI mib file find the definition of zeroDotZero and copy this to the clipboard Inthe STAN
75. software installation 5 Edit the configuration to match the customer requirements This can include importing information from prepared CSV files Note For information about CSV files see the Help available in the Manager application From Manager select Help gt Contents In the Manager Help window in the left navigation pane expand IP Office Configuration Mode and then expand Editing Configuration Settings Then click Importing and Exporting Settings 6 When completed select File gt 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 Create an offline configuration that matches the customer requirements and the equipment that will be installed in the B5800 Branch Gateway system See Creating a configuration file on page 57 2 Rename the configuration file config cfg 3 Using a card reader copy the file into the system primary folder on the System SD memory card Adding music on hold files About this task By default B5800 Branch Gateway uses internal music on hold by uploading a music file You can load a file onto the System SD card prior to installing it in the control unit The file must be of the following format and must be called holdmusic wav Property Value File Type WAV Bit
76. sufficient safeguard Shutting down the card will disable embedded voicemail if being used If the System SD card is removed features licensed by the card s Feature Key serial number will continue operating for up to 2 hours Card maintenance Using Manager the System Status application or a phone configured as a system phone you can perform the following procedure on the SD cards Procedure Description Manage System System Minut r Status Phone es Backing up the Copy the files in the primary folder onthe v J 4 6 primary folder System SD card to the backup folder on the using Manager on card page 249 Restoring from the Copy the files in the backup folder on the v lt 4 6 backup folder System SD card to the primary folder on the using Manager on card and restart the B5800 Branch page 250 Gateway system Backing up to the Copy all the files on the System SD card to v J vi 90 Optional SD card the Optional SD card using Manager on page 252 Upgrading using Copy the configuration file in the primary v 15 an Optional SD folder on the Optional SD card to the card on page 258 primary folder on the System SD card and then restart the B5800 Branch Gateway system Upgrading Upload a set of B5800 Branch Gateway lt 40 remotely using software and embedded voicemail prompts to the System SD card 242 Implementing the Avaya B5800 Branch Gateway for an Avaya A
77. system programming and future maintenance e Check that there is sufficient working space for installation and future maintenance Ensure that likely activities near the system will not cause any problems e g access to and maintenance of any other equipment in the area e Where ventilation holes are present on any of the B5800 Branch Gateway units those holes should not be covered or blocked e The surface must be flat horizontal for free standing or rack mounted installations Wall mounting In additional to the requirements above the following are applicable to control units that are mounted on the wall e Units must only be mounted onto permanent wall surfaces e The surface must be vertical and flat e Orientation of the unit must be as shown in the section on IP500 Wall Mounting on page 65 e The appropriate Avaya wall mounting kits must be used Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 47 Installation requirements Note See Important safety instructions when using your telephone equipment on page 263 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 See Rack moun
78. the appropriate file from those installed with Manager When the firmware loaded by the B5800 Branch Gateway control unit is erased the control unit will first look for replacement firmware on the System SD card before falling back to using a BOOTP request to Manager Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 235 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 Important e Do not erase the core software unless absolutely necessary The B5800 Branch Gateway software can normally be upgraded using Manager e These procedures erase the operational software Before performing these procedures you must know the MAC and IP addresses of the system plus have a system backup and the correct bin file for the control unit type and level of software The presence of any firewall blocking TFTP and or BOOTP will cause these procedures to fail Erasing the core software via debug Procedure 1 Start Manager 2 In the BOOTP entries check that there is an entry that matches the MAC
79. the appropriate procedure for the type of component See Base and trunk card installation on page 59 or Connecting external expansion modules on page 70 for more information 3 Restart the B5800 Branch Gateway system 4 Use Manager to configure the new trunks or extension users Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 211 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 206 2 Remove the card or external expansion module 3 4 Use Manager to delete the trunks or extensions users in the configuration that relate Restart the B5800 Branch Gateway system to the component removed Inthe Control Unit section of the configuration delete the entry for the component that is no longer present in the system Swapping extension users About this task This procedure explains how to swap extensions for two users This example refers to User A and User B which represent any two users for whom you want to swap extensions Procedure 1 Load the B5800 Branch Gateway configuration 2 Select Extension 3 4 Inthe Base Extension field change the extension to User B s extension In the Ex
80. the configuration settings Procedure 1 Attach the serial cable between the PC and the DTE port on the control unit 2 Start the terminal program on your PC Note Ensure that the DTE port settings are configured as described in RS232 DTE port settings on page 230 Within a HyperTerminal session the current settings are summarized across the base of the screen 3 Enter AT upper case An OK response appears If OK does not appear check the settings of your terminal program 4 Enter AT SECURITYRESETALL You are prompted to confirm the control unit s MAC address 5 Enter the MAC address An OK response appears 6 Close the terminal program session 7 Use Manager to edit the system s now defaulted security settings Resetting the configuration and security settings to the default 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 See Creating a backup of the system configuration using IP Office Manager on page 215 for more information 234 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com DTE port maintenance Procedure 1 Attach the serial cable between the PC and the DTE port on the control unit
81. the distributed branch user model from R6 1 to R6 2 The procedures in this chapter are performed using both IP Office Manager that is connected directly to the B5800 Branch Gateway system and Avaya Aura System Manager where some procedures are performed from the System Manager Web console Upgrade installation checklist Use this checklist to monitor your progress as you upgrade an R6 1 B5800 Branch Gateway system to an R6 2 system Description Section Vv Confirm that your version of Avaya Aura System Manager is R6 2 and SP1 has been installed Create a backup of each B5800 Branch Gateway See Creating a backup of the system configuration using IP Office Manager on page 215 Upgrade the B5800 Branch Gateway The upgrade wizard upgrades all of the B5800 Branch Gateway components including the modules cards and phone firmware See Using the upgrade wizard on page 217 Upgrade the administration applications See Upgrading the administration applications on page 90 Export users to an xml file Note Be sure to perform this task before you launch the Initial Installation Utility After you launch the Initial Installation See Exporting users to an xml file on page 92 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 89 Upgrading an R6 1 system to R6 2 Description Section Utilit
82. the link included on the sheet Avaya will send you a list of SEIDs from the locations you selected B5800 Branch Gateway registration and SAL Gateway on boarding Each B5800 Branch Gateway deployed must be registered with Avaya To add managed devices to your SAL Gateway using the Solution Element IDs SEID provided to you during SAL Gateway registration described above see Managed element configuration in Chapter 4 in the Secure Access Link 2 1 SAL Gateway Implementation Guide document number 146775 which is available on the Avaya support Web site When you have added all your managed devices complete Step 2 of the SAL Gateway registration form for each managed device you added to your SAL Gateway and send the form to salreg avaya com When this form is received the Avaya registration team makes the appropriate changes to allow access to your managed devices through the SAL Gateway Avaya will then confirm via an e mail notification that remote access to your product has been enabled through your SAL Gateway B5800 Branch Gateway SAL based alarming The SAL Gateway supports alarming for the B5800 Branch Gateway managed device You must change the alarm destination on your B5800 Branch Gateway managed device so that alarms are routed to your centralized SAL Gateway See SNMP on page 224 for more information During the registration and on boarding process of each branch the Avaya registration team also tests alarming through the SA
83. the process has been completed the B5800 Branch Gateway system is restarted Restoring from the backup folder using a system phone About this task A user configured as a system phone user can perform this procedure using a 1400 1600 or 9600 Series phone excluding XX01 XX02 and XX03 models The user s login code is used to restrict access to system administration functions on the phone Procedure 1 Select Features gt Phone User gt System Admin 2 Enter your B5800 Branch Gateway user login code 3 4 Select System Restore From the menu select Memory Card The contents of the backup folder on the System SD card are copied to the primary folder on the System SD card The process takes approximately 6 minutes When the process has been completed the B5800 Branch Gateway system is restarted Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 251 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 Any new files added for example voicemail messages while the process is running may not be copied Ba
84. to the card location and click OK Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com 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 247 Formatting a System SD card using the System Status application Procedure 1 Start the System Status application and access the System Status output 2 In the navigation panel select System gt Memory Cards gt System SD 3 Click on the Format button at the bottom of the screen The card is reformatted All files and folders on the card will be deleted This process takes a few seconds Recreating an SD card Before you begin To enable this option the working directory defined in File gt Preferences gt Directories must be set to the parent directory of the Memory Cards folder Be sure to back up the PLDSKeys xml file in the primary folder before you perform this task When you perform this task the PLDSKeys xml file is deleted About this task This procedure creates the folder structure on the SD card and copies the required firmware files from those installed with Manager onto the SD card This includes the binary files for the system any external expansion modules and
85. training record e Avaya Community http www aucommunity com This is the official discussion forum for Avaya product users However it does not include any separate area for discussion of B5800 Branch Gateway issues 32 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Revision history Revision history Issue Date Summary of changes 2 07 2012 The name of the B5800 Branch Gateway security certificate cannot contain spaces This is explained in a note in the appropriate places e The order of the steps in the Configuration checklist have been changed The step to add the B5800 Branch Gateway to System Manager has been moved to after you generate a certificate and run the Initial Installation Utility e Two additional fields may need to be edited in the xml file used to export users during an R6 1 to R6 2 upgrade Those fields have been added to the procedure Editing the xml file containing the users 3 10 2012 Modifications have been made to the following procedures e Generating a certificate on System Manager Additional steps have been added to the procedure for clarity e Using the Initial Installation Utility It is recommended to select LAN1 to configure the WAN interface e Configuring the B5800 Branch Gateway for certificates This procedure replaces Manually loading the certificate to the B580
86. unique information for each device e lt ApplicationSystem name B5800 device isTrusted false gt where B5800 device is a unique name for this system e lt Host ipaddress P address gt lt Host gt where IP address is a unique IP address for this system Adding the B5800 Branch Gateways to System Manager About this task Use this procedure to manually add the B5800 Branch Gateways to System Manager This procedure must be performed for each B5800 Branch Gateway Procedure 1 From the System Manager console under Elements select Inventory 2 On the Inventory page click Manage Elements Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 129 Initial branch configuration 3 On the Elements page click New 4 On the New Elements page in the Type drop down box select B5800 Branch Gateway On the New B5800 Branch Gateway page in the Name field enter a name for this B5800 Branch Gateway 6 In the Type drop down box select B5800 Branch Gateway 7 Inthe Description field enter a description to help identify this B5800 Branch 12 13 14 15 16 Gateway Inthe Node field enter the IP address of the B5800 Branch Gateway Click the Attributes tab 10 11 For the SNMP Attributes Version click V1 In the Read Community field enter the community to which the device belongs for read access In the Write Community field enter t
87. use the up and down arrows to select the port number of the WebLM server The default is 52233 Click File gt Save Configuration Creating a system template About this task System templates are designed for new systems They are not designed to distribute edited system configurations to the branches Distributing an edited system template to a branch would override any local configuration changes that were made to a specific branch 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 2 N OO A From the System Manager console under Services select Templates On the Templates page in the left navigation pane click B5800 System Configuration On the B5800 Branch Gateway System Configuration Templates page do the following a Under Supported B5800 Branch Gateway Types click the check box for B5800 b Under Templates List click New Inthe Name field enter a name for this template Inthe System Type drop down box select B5800 In the Version drop down box select the appropriate release To add more details to this system template click Details IP Office Manager is launched Complete the fields as appropriate Implementing the Avaya B5800 Branch Gateway for an Avaya
88. user name that has been configured for System Status access in the B5800 Branch Gateway security settings e Inthe Password field enter the appropriate password f Check the Auto Reconnect check box if you want System Status to attempt to reconnect using the same settings if connection to the B5800 Branch Gateway is lost 3 Click Logon Starting System Monitor About this task 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 Installers and maintainers must understand how to run System Monitor when necessary as Avaya may request copies of System Monitor traces to resolve support issues Procedure 1 Select Start gt Programs gt Avaya B5800 Branch Gateway Admin Suite gt Monitor If System Monitor has been run before it will attempt to connect with the system which it monitored previously 2 To monitor a different system select File gt Select Unit The Select System to Monitor window appears 106 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com 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
89. will send a challenge back to the device and waits for an appropriate response If the response is not received within this timeout the registration is failed 156 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Chapter 9 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 112 About this task Use this procedure to launch IP Office Manager from System Manager to edit a B5800 Branch Gateway system configuration Note You cannot configure users when editing a B5800 Branch Gateway system configuration from System Manager User configuration is performed from System Manager User Management For more information see Restrictions when editing aB5800 Branch Gateway system configuration from System Manager on page 158 Procedure 1 From the System Manager console under Elements select B5800 Branch Gateway 2 In the left navigation pane click System Configuration 3 On the B5800 Branch Gateway System Configuration page select the B5800 Branch Gateway device whose system configurati
90. yacanunds 79 Connecting ihe PC directly to the control UNM sariini ow eee aetioutisane 80 ON AE he Sy SIO iaaa a aS 81 ARTO MOTT LEDS Sirup Sege sc ei eiaa AERA E Eea ADIE OAE 82 PAT Te sp A aaa eae ERE RA 83 Lye ACNE OO PAA IA AHO psascacsic nea seaecin assadedauen eidareamiuaneuiedaeauenecacdsoncensyaeemuunncanuddeex ant pacaseuc ene gicasnoeameunuemecansennds 85 Connecting tie taritral tilt tothe Neth i cetciaeise cada Nana iets Eerad 86 FIP EMC TIPNG Pone Gc Sinitacan dec e a e Ea 87 Chapter 5 Upgrading an R6 1 system tO R6 2 cceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeees 89 Ubora merano IV le Us inuia aa dash aaia 89 Upgrading Me administrator ARIS sicie eaa sate a EEE 90 Enabling secure communication after upgrading IP Office Managet ccccccccceseseeeeeeeeeeeeeeeees 91 Exporing users 10 an SIMMS orssccssanctcsaedenmvecssvesneviasteniamvedsdeddwtrcatianintaedninei ani diheyl aroha yiasdiideaiaion 92 Editing thie xml ile contaning te SONS siosio niai a aaae iai earan 92 Bulk TPIS ETOAC of USE Pierna Aiia na AEn 93 About migrating individual PLDS license files to a WebLM Servel cccceeeeeeeeeeeeeeeeeeeeeeeeeeteeeeeeeeees 94 Deleting the PLDS license file from the OPAC sca occieinscetacciedadsetensiaiecnntcbsiadeceetasetedesdelapeiadeesabancinides 95 Chapter 6 Upgrading an R6 2 system with an R6 2 service Pack cccccssssseseesseeeeeeees 97 Pee savic pak Nstalaion CNOCkiS E iiciin Waganbets ladedsenectad
91. you can migrate the individual PLDS license files to the System Manager WebLM server This requires that you first move the individual PLDS license files from one license host to another license host that is from the B5800 Branch Gateway to the System Manager WebLM server and then install 94 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com About migrating individual PLDS license files to a WebLM server the shared license file on the System Manager WebLM server To perform these procedures see e Moving activated license entitlements on page 195 In this procedure you will move the activated license entitlements from the current host ID which is the individual B5800 Branch Gateway to the host ID of the WebLM server e Enabling WebLM licensing for the branch on page 130 e Installing the shared PLDS license file on the System Manager WebLM server on page 117 e Deleting the PLDS license file from the branch on page 95 Deleting the PLDS license file from the branch About this task After the license entitlements in PLDS have been moved from the individual B5800 Branch Gateway license file to the shared WebLM license file the individual license file installed on each B5800 Branch Gateway must be deleted Note Failure to delete the individual license file on the B5800 Branch Gateway will create a violation of the end user license agreement Procedure
92. 0 Branch Gateway e Adding distributed users to System Manager Distributed H 323 users and SIP users do not require different configuration when being added to System Manager Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 33 B5800 Branch Gateway overview 34 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Chapter 2 Planning Before you begin installing and configuring the B5800 Branch Gateway system you should already have determined the implementation issues listed in the table below You have determined See Y The dial plan you are configuring for the Dial plan considerations on page 36 system and each branch The B5800 Branch Gateway licenses Licensing on page 16 required for this installation How you are going to route outgoing Branch PSTN call routing considerations on PSTN calls page 38 The voicemail solution you are going to Voicemail considerations on page 37 deploy VolP requirements Network assessment for VolP requirements on page 39 Prerequisites Depending upon the deployment the following applications and servers must be installed and configured before the B5800 Branch Gateway system is installed e If you are going to connect the B5800 Branch Gateway to an enterprise over the WAN Avaya Aura Session Manager R6 1 o
93. 0 154 enabling secure communication after upgrading IP Offfice Manager cceseccceeeeeesstteeeeeeeeeeesees 91 Enabling WebLM licensing for the branch 130 Enty AK vevecvcsnssanatenveenvsnnhaneecatiesis ssakaeteeemnebiaaeatdanceens 168 Envirmental requirement cccceeeeeeeeeeeeeeeeeneeeees 47 Example of So8 BRI module configuration 221 exporting users to an xml file aseeseen 92 EXT O P POF spenner sosvccsaniel svasseueueesasveveneseatanatevenss 220 Extension NUMDELS ccccceeceeeeeeeeeeeeeeeeaeeeees 212 213 CHANGING eeraa IN 213 Renumbering 2 cceeceeeeeeeneecaeeeeeeeeeeeeeeeeneteaeees 213 SWAPPING rnanis E eaetennneeetioncay 212 external Servel siipra anenai EEEE 98 F F AMD ACK acs saddveiadsatattaindueedadedadiudiectedadeaedivsavedadeanaieales 294 FCG RUGS ia vcisivsncssctinveatavevaisvaveataraicnassnrevaasaensicvaveaeey 272 firewall policies ccecccciswctcatacaccsacisuev er tadesdwecsaetebivanadec es 278 firewall tyP S ccccceeeeesecceceeeeeseeceeeeeeneeeeeeeeeeenenneees 277 Force authorization codes ccccccceeeseseeeeeeeeaeaees 301 FODN i ecccavscaicanvcctatessursaacacitanestdeauancucesgaseanastanaet tases 167 310 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration G General information cccccccccsssseseeeeceeeeeeeeeesaeaeaeeees 31 training COUISES 0 2 0 0 eee ee eeeeeeeeeeeeteeeeeeeeeeeeeeeeteeeees 3i
94. 0 Branch Gateway system configuration from System Manager When you edit the system configuration of a B5800 Branch Gateway device that is managed from System Manager IP Office Manager is launched in system mode The following restrictions apply when editing a B5800 Branch Gateway system configuration from System Manager with IP Office Manager in system mode e Extension is visible in the Extn tab only but is disabled All users other than NoUser and RemoteManager are visible in the User tab only but are disabled e NoUser has User and Source Number tabs visable and editable The rest of the tab is not visable and therefore not editable e RemoteManager has the User tab visable and editable The rest of the tab is not visable and therefore not editable The User Management feature available in System Manager is used to manage users and extensions on B5800 Branch Gateway systems that are centrally managed from System Manager See User administration on page 185 for more information 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 158 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com About disabling the System Manager administration feature for a B5800 Branch Gateway Changes made to users and extensions in this way will not b
95. 0 Branch Gateway to use Avaya Aura Messaging for voicemail About this task The B5800 Branch Gateway system can be configured to use Avaya Aura Messaging as its voicemail server Note If Avaya Aura Messaging is used as the central voicemail system you are able to still use the local Embedded Voicemail or Standalone Voice Mail for auto attendant operation and for announcements to waiting calls 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 157 2 In the left navigation pane click System 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 176 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Configuring B5800 Branch Gateway to use Avaya Aura Messaging for voicemail Note You mus
96. 00 Branch Gateway device e Click Restore Backup Stored on Devices to restore the locally backed up configuration to the B5800 Branch Gateway device 6 Do one of the following e Click Now to perform the restore activity now e Click Schedule to perform the restore activity at a scheduled date and time External output port EXT O P The B5800 Branch Gateway control unit is equipped with an external output port The port is marked as EXT O P and is located on the back of the control unit adjacent to the power supply input socket The port can be used to control up to two external devices such as door entry relay switches The usual application for these switches is to activate relays on door entry systems However as long as the criteria for maximum current voltage and if necessary protection are met the switches can be used for other applications The switches can be switched closed open or pulsed closed for 5 seconds and then open This can be done in a number of ways e Using B5800 Branch Gateway short codes e Through the Door Release option in B5800 Branch Gateway SoftConsole Default short codes The following are the default short codes in the B5800 Branch Gateway configuration for external output switch operation They use the short code features Relay On closed Relay Off open and Relay Pulse State Switch 1 Switch 2 Closed 39 42 Implementing the Avaya B5800 Branch Gateway for an Avaya Au
97. 00 Branch Gateway to an xml file that is then used for bulk import to System Manager e Adding the B5800 Branch Gateways to System Manager on page 129 This method requires you to manually add each branch to System Manager by identifying the IP address of the B5800 Branch Gateway Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 125 Initial branch configuration Discovering B5800 Branch Gateways Before you begin Enable SNMP on the B5800 Branch Gateway to be updated See Enabling SNMP and polling support on page 127 About this task Use this task to discover the B5800 Branch Gateways in the network and add them to System Manager This task requires that you identify the subnet IP address in which the branch is located There is always one B5800 Branch Gateway per branch and each branch is ina different subnet This procedure must be performed for each branch Procedure 1 o 13 14 15 16 17 From the System Manager console under Elements select Inventory 2 On the Inventory page select Inventory Management gt Configuration 3 4 On the Add SNMP Access Configuration page in the Type drop down box select On the Configuration page click New V1 Inthe Description field enter a description to help identify this SNMP access configuration Set the Read Community field as configured on the device Set the Write Community field as configure
98. 04098 e Implementing Standalone Voice Mail for B5800 Branch Gateway Release 6 2 document number 18 604088 Note Standalone Voice Mail must be installed on a separate Linux server Voicemail options The B5800 Branch Gateway system uses its Embedded Voicemail by default However a number of other voicemail options are supported e Embedded Voicemail Embedded Voicemail uses the system SD card in the B5800 Branch Gateway system control unit for storage of prompts and messages Embedded Voicemail supports mailboxes for all local extension numbers announcements to waiting callers and auto attendants up to 40 for external calls Its capacity is limited to 15 hours of recorded messages prompts and announcements Embedded Messaging Port licenses must be purchased with sufficient quantity to support the configured number of ports e Standalone Voice Mail Standalone Voice Mail provides the same features as Embedded Voicemail but with additional port capacity provided on a Linux server You must have a Linux server installed to use this option When you select this option you must enter the IP address of the Linux server where Standalone Voice Mail is installed This option provides a maximum capacity of 40 ports while the Embedded Voicemail option provides a maximum capacity of 6 ports Embedded Messaging Port licenses must be purchased with sufficient quantity to support the configured number of ports e Avaya Aura Messaging Th
99. 1 911 Dial Emergency 0 Remove 911 911 Dial Emergency 0 ON ON Dial 3K1 99999 Edit 1N 1N Dial 3K1 99999 XN N Dial 3K1 0 AXAXARARAAN N Dial 3K1 0 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 Make the changes as follows a Inthe Code field set this to match the external PSTN number for Modular Messaging or Avaya Aura Messaging without the external dialing prefix b Inthe Feature drop down box select Dial3K1 c Inthe Telephone Number field set this to N to match the whole number in the Code field Note For a setup where the voicemail mail box numbers configured on Modular Messaging or Avaya Aura Messaging are the same as the caller s DID the short code to route the PSTN call should be configured so that the caller ID is withheld To do this enter a w in the Telephone Number field of the short code This ensures that during rainy day operation the voicemail system does not automatically go to the voicemail mail box of the caller based on the caller ID d Inthe Line Group Id drop down box select the line group ID being used for
100. 14 AWG solid wire with either a green sleeve for a functional ground or green and yellow sleeve for a protective ground Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 71 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 PRBS RRS Oc IP DTE j EXPANSION K D 16 24 DC 5 04 MAX DIGITAL STATION Y2 24v DC 1 54 PHONE 2 On some older modules the dedicated ground point screw is not present In those cases the top center cover fixing screw 8mm can be used as an alternative ground connection point A toothed washer should be added to ensure good contact Out of building connections lightning protection The following are the only supported scenarios in which wired extensions and devices outside the main building can be connected to the B5800 Branch Gateway system In these scenarios additional protection in the form of protective grounding and surge protectors must be fitted A Warning The fitting of additional protection does not remove the risk of damage It merely reduces the chances of damage 72 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Out of building
101. 17 Safety and regulatory informatiOn ccccsssseeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeees 263 SE EAEE E E A T A A nated E A 263 Important safety instructions when using your telephone equipment sseesssersssssrrresrssrrsssrrsrres 263 Sit NT et No asta ise NE E E AE Maat sash ca laisauh daaanuaee 264 Lightening protectioiwvhazard Symbols cise ccccte tracert ccecsereetiacsustninde dacekarieaciiadninandeniateachisondaceanians 264 Tunk merate Module Seinien aar eaa enlene cake ROEE E 265 EE EE UN E A E E S E E E E 265 ENC CONG Ea tetany antec stedaags 266 Regiiatory Iinstuctions Tor USE aai S 267 T ccd chant aia E E E A E E E E E AE E T 267 AN a ER E 268 Sa e a E EA E E E E A A A E A a T 269 European UMO a E EA Tan Terr eoer Ty Pre Torre tnT Tce Terry Tree 270 Pre LO aaa aaa 270 ESIE E E E NEE EE E E T A A E IEA O A eS 270 Campione Wih FOG ES cnnan a reRme ler steer tore 272 Appendix A Avaya port matrix for B5800 Branch Gateway and SIP phones 275 What are poris and how are they Ned risiini aiaa SaaS 275 Pon wpe rangi S acta cee iasectnns te cesdecebetuacatauete ccd dohaied baiitabaededudsvdetetaacavd orice cade tuaddaderteaatataabepaudd N 275 Pee ess daa E A A A deme lamin tutinadn alte Pad AA A Ginga dd E A E A E A 276 Firewall IPES oica5ccscsdcinccnsacencarsanmrencceasnpnrcnctaacmanenaketuaamiavacetinaniynciaisnanlsndiecunsatsaieasamaralaiaNanisiacantanmesacetans 277 10 Implementing the Avaya B5800 Branch Gateway fo
102. 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 230 Within a HyperTerminal session the current settings are summarized across the base of the screen 3 Arrange the program windows so that the terminal program and Manager TFTP log are visible at the same time 4 Switch off power to the control unit 5 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 6 Enter AT upper case An OK response appears If OK does not appear check the settings of your terminal program 7 To erase the backup configuration stored in non volatile memory enter AT X2 An OK response appears 8 To erase the current configuration in RAM memory enter AT X3 A series of OK responses appear 9 Switch power to the control unit off and then back on Messages appear as the control unit performs the start up tasks 10 Close the terminal program session 11 Use Manager to edit and then upload an old configuration file or receive and edit the system s now defaulted configuration About erasing the operational firmware When the firmware loaded by the control unit is erased the control unit begins making BOOTP requests for a replacement firmware file Manager can act as a BOOTP server and respond to the control units request with
103. 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 Local Number Length Range Blank Off or 3 to 9 for native extensions This field sets the default length for extension numbers for extensions users and hunt groups added to the B5800 Branch Gateway configuration Entry of an extension number of a different length will cause an error warning by Manager The combined Branch Prefix and Local Number Length should not exceed 15 digits Beginning in B5800 Branch Gateway R6 2 you have the option to leave the Local Number Length field blank Proactive Default 60 seconds Range 60 to 100000 seconds The B5800 Branch Gateway sends regular SIP OPTION messages to the Avaya Aura Session Manager line in order to check the status of the line This setting controls the frequency of the messages when the Avaya Aura Session Manager line is currently in service Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration Comments infodev avaya com October 2012 Administering a Session Manager line for each branch Name Range or Default Description Reactive Default 60 seconds The B5800 Branch Gateway Range 10 to 3600 seconds sends regular SIP OPTION messages to the Avaya Aura Session Manager line in order to check the status of line
104. 201 and take the form Extn201 Extn202 etc You must manually configure a user for each extension Users are not created automatically Note that there can be extensions on the system that have not yet had users assigned to them e Hunt group A single hunt group 200 called Main is created and the first 10 users are placed into that hunt group as members e Incoming call routes Two default incoming call routes are created Voice calls are routed to the hunt group Main Data calls are routed to the RAS user Dialln Default short codes A Law or U Law variant operation is determined by the Feature Key installed in the control unit Depending on the variant different short codes and trunk settings are added to the default configuration A Law or Mu Law Pulse Code Modulation PCM is a method for encoding voice as data In telephony two methods of PCM encoding are widely used A law and Mu law also called U law Typically Mu law is used in North America and a few other locations while A law is used by the rest of the world As well as setting the correct PCM encoding for the region the A Law or Mu Law setting of a B5800 Branch Gateway system when it is first started affects a wide range of regional defaults relating to line settings and other Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 85 Hardware and software installation values The encoding default is set by the t
105. 3 is a REN of 0 3 For earlier products the REN is separately shown on the label Means of connection Connection of this equipment to the telephone network is shown in the following table 270 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Regulatory Instructions for Use Port FIC soc USOC Jack REN IPO500 PRI 1U 04DU9 BN 6 0Y RJ48C NA IPO500 PRI2U 04DU9 DN IP400 PRI T1 04DU9 IKN 04DU9 ISN IPO500 ATM4U OL13A OL13B 9 0Y RJ45S 0 1B IP400 ATM4U OL13C 02AC2 02LA2 02LB2 02LC2 02LR2 02LS2 IPO500 ATM16 OL13A OL13B 9 0Y RJ45S 0 1B OL13C 02AC2 02GS82 02LA2 02LB2 02LC2 02LR2 02LF2 02GS82 02LS2 If this equipment causes harm to the telephone network the telephone company will notify you in advance that temporary discontinuance of service may be required But if advance notice is not practical the telephone company will notify the customer as soon as possible Also you will be advised of your right to file a complaint with the FCC if you believe it is necessary The telephone company may make changes in its facilities equipment operations or procedures that could affect the operation of the equipment If this happens the telephone company will provide advance notice in order for you to make necessary modifications to maintain uninterrupted service If trouble is experienced with this equ
106. 5800 Branch Gateway cables The following are Avaya standard cables available for use with B5800 Branch Gateway systems The maximum length is applicable if the standard Avaya cable is replaced with an alternate cable Cable Description Standard Maximum Length Length 9 way DTE cable Connects to control unit RS232 DTE 2m 6 6 2m 6 6 port 9 way D type plug to 9 way D type socket Structured cabling Connects from RJ45 sockets to RJ11 4m 13 2 DS line cable socketed DS and analog phones BRI PRI trunk cable Connects BRI PRI trunk ports to the 3m 9 10 line provider s network termination point RJ45 to RJ45 Red Expansion Connects the control unit to expansion 1m 3 3 1m 3 3 interconnect cable modules except WAN3 modules RJ45 to RJ45 Blue LAN cable Connects from B5800 Branch 3m 9 10 100m 328 Gateway LAN ports toB5800 Branch Gateway devices RJ45 to RJ45 Grey V 24 WAN cable 37 way D type plug to 25 way D type 3m 9 10 5m 16 5 plug V 35 WAN cable 37 way D type plug to 34 way MRAC 3m 9 10 5m 16 5 plug X 21 WAN cable 37 way D type plug to 15 way D type 3m 9 10 5m 16 5 plug Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 43 Installation requirements Grounding Use of ground connections reduces the likelihood of problems in most telephony and data systems This is especially important in buildings wh
107. 5mm 14 4 Total with clearance 545mm 21 5 220mm 8 7 Clearance 30mm 3 5 External expansion modules The dimensions below are applicable to all external expansion modules 7Fimm 2 8 1 6U Clearance 75mm 3 445mm 17 5 Unit 245mm 9 7 Total with clearance 395mm 15 7 Clearance 75mm 3 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 49 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 65 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 Each unit requires a 2U slot space within the rack Rack mounting requires a rack mounting kit for each control unit and external expansion module See Rack mounting on page 67 for more information about the rack mounting kit Where B5800 Branch Gateway systems are being rack mounted the effect of conditions within the rack cabinet must be considered For example the rack temperature may be above the room temperature and airflow within the rack will be restricted The environmental requirements for the individual control unit and exp
108. 7310 BLF e M7324 e M7324N e M7208 e M7208N e M7100 e M7100N Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 25 B5800 Branch Gateway overview Telephone Native extensions local extensions operating in the distributed branch user model e Audio conference unit e T24 KIM Key Indicator Module for T7316 DevConnect approved 3rd party SIP v 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 e User applications The following applications are supported for use by native users on a B5800 Branch Gateway system Embedded Voicemail supports basic voicemail mailbox operation simple auto attendants and hunt group announcements It is provided on the Avaya SD card Embedded Voicemail on a B5800 Branch Gateway system provides 6 ports This voicemail option requires a license See Licensing on page 16 for more information Standalone Voicemail provides additional port capacity 40 ports on a Linux server You must have a Linux server installed to use this option This voicemail option requires a license See Licensing on page 16 for more information SoftConsole is intended for telephone system operators or receptionists It displays details of call
109. 800 Branch Gateway sends regular OPTION messages to each Avaya Aura Session Manager line in order to check the lines in or out of service status If a response is not received within this timeout the line is treated as being out of service DTMF Support Default RFC2833 This setting is used to select the method by which DTMF key presses are signaled to the remote end The supported options are In Band RFC2833 or Info Media Security Default Disable Media security is not required All media sessions audio video and data will be enforced to use RTP only Advanced This option provides additional media security options These options are not supported in B5800 Branch Gateway R6 2 VoIP Silence Suppression Default Off When selected this option will detect periods of silence on any call over the line and will not send any data during those silent periods 148 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Administering a Session Manager line for each branch Name Range or Default Description Allow Direct Media Path Default On This setting controls whether connected calls must remain routed via the B5800 Branch Gateway or can be routed alternately if possible within the network structure If enabled connected calls can take routes other than through the B5800 Branch Gateway This removes the ne
110. 911 Dial Emergency 0 ON ON Dial 3K1 0 Edit 1N 1N Dial 3K1 99999 XN N Dial 3K1 0 ARAKARASASN N Dial 3K1 0 15553800701 N Dial a 7 Click OK 8 Select File gt Save Configuration PSTN trunk fallback In branch scenarios where centralized call control and trunking see Centralized call control on page 289 has been configured for certain calls loss of the Avaya Aura Session Manager line connection will impact making those calls For instance in our example where all branch national and international calls are routed via the headquarters site loss of the Avaya Aura Session Manager line will leave the branch users only able to make local calls Since loss of the Avaya Aura Session Manager line should only be an infrequent and temporary condition some restriction during that state may be acceptable However the following options can be used to allow continued branch operation e If the headquarters site has multiple Avaya Aura Session Managers for redundancy each branch can also be configured with multiple Avaya Aura Session Manager lines See Avaya Aura Session Manager line redundancy on page 150 for more information e As in our example business centralized call control has not been applied to all branch local calls Therefore local calls are still available without any additional configuration for the loss of the Avaya Aura Session Manager line connection e Since loss of the Avaya Aura Session Mana
111. 99 B5800 Branch Gateway licenses 18 B5800 upgrades s iiisseerinsriinuuerinnuiiis eurini 98 Barrier DOX S cihan ekaa ie 75 76 analog phone gt ere 25 TACK MOUNTING cinean aa 76 BANOS siicck ccccstedicnnseeedestsnsecddeavanccdsstsabogeweaecooedeuzens 264 Sg 0 gg Weert Pee erereeee erence cee moe E 264 branch and extension numbering ceeeeeeeeees 140 bulk import Of USCIS eee eeeeeeeeeeeeeeeetaeeeeeeeeeeaaeees 93 Bulk importing Of devices eeeeeeeeeeeeeeeeeeeeeteeeee 128 Cc Cable eee niente a ee ene eee eee eee 48 ACCESS requirements eee cece cette eeeeeeentteeeeeeeeenaaees 48 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration Clearance requirements ccccccccceeeeeeeeeeeeeeteeees 48 Cables sinso a a a aid 42 Maximum cable distances ccccccssessseeeeeeeeees 42 Standard IP Office i cccceseeseeeseeeessseeeeeeeees 42 CADNO enia E 72 lightening Protection cceeeeeeeseeeeeeeeeeeeetaeeeees 72 Call TOWS aiausaateece eras senna valid sav aevanetesoushaneatareteadaehannaatad 287 Castle ROCK wccissiriiideavacereviclavercccateiovdieiva aaasddvenavedaveds 224 Centralized call control cccceeeecceceseeeeeeeeeeeeeeeees 289 Change NIStOry eeeeeeeceeeeeeeeeeeeneeeeeeeeeeeaaaeeeeeeeeenaaaees 33 Ghannels oiire aeiaai a a 44 COMPrESSION scisdscedentsesavecedneencestecingeseeIneauceueadeateeees 44 GOS arit 135 Compression channels c
112. ACTA adopted technical criteria Avaya further asserts that Avaya handset equipped terminal equipment described in this document complies with Paragraph 68 316 of the FCC Rules and Regulations defining Hearing Aid Compatibility and is deemed compatible with hearing aids Compliance with FCC rules Transmit and receive gain settings for PRI T1 and analog ports The Gain settings are password controlled for use by qualified installation personnel only and must not be made available to the end user The default gain settings of OdB ensures compliance with FCC part 68 section 68 308 b 5 and TIA EIA IS 968 Section 4 5 2 5 Through transmission amplification from ports for the connection of separately registered equipment or from other network connection ports Gain setting adjustment by unqualified 272 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com 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 e Where gain adjustment away from the default values are made precautions should be taken to ensure that the connect
113. AVAYA Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration Release 6 2 18 603853 Issue 3 October 2012 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 Documentation disclaimer Documentation means information published by Avaya in varying mediums which may include product information operating instructions and performance specifications that Avaya generally makes available to users of its products Documentation does not include marketing materials Avaya shall not be responsible for any modifications additions or deletions to the original published version of documentation unless such modifications additions or deletions were performed by Avaya End User agrees to indemnify and hold harmless Avaya Avaya s agents servants and employees against all claims lawsuits demands and judgments arising out of or in connection with subsequent modifications additions or deletions to this documentation to the extent made by End User Link disclaimer Avaya is not responsible for the contents or reliability of any linked websites referenced within this site
114. Aura Configuration October 2012 131 Initial branch configuration 9 When finished select File gt Save Template and Exit 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 Note If you are using a system template you can add the audio file to the template to push the audio file down to multiple B5800 Branch Gateway systems Procedure 1 From the System Manager console under Services select Templates 2 On the Templates page click B5800 System Configuration 3 On the B5800 Branch Gateway System Configuration Templates page under Templates List select More Options gt Manage Audio 4 Onthe 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 When finished click the Done button Applying the system template 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 132 Im
115. Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com 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 Configure an incoming call routing The destination is a short code that directs the call to the line group ID that contains the SO lines The Bearer Capability has been set to Any to allow data and voice via this route e Line Group ID 0 e Incoming Number 123456 e Destination 123456 e Bearer Capability Any 2 Create a system short code This is the destination used in the incoming call route e Short Code 123456 e Telephone Number 123456 e Line Group ID 701 e Feature Dial 3 Send the configuration to the control unit Any call coming into the main system on DID 123456 will now be passed directly to the first port 4 If you wish to assign DIDs from your main pool to individual ports and avoid network charges when dialing between them try variations on the following a You have DID ranges for example 7325551000 to 7325551099 Y
116. Comments infodev avaya com Using the Initial Installation Utility 18 If you are not going to use the Initial Installation Utility go to Configuring the B5800 Branch Gateway for certificates on page 123 Using the Initial Installation Utility About this task The B5800 Branch Gateway Initial Installation utility provides a default configuration and security settings that minimize initial installation activities and maximize security The system must be configured with the default settings before the system can be administered by Avaya Aura System Manager This utility is used for new installations and after an R6 1 to R6 2 upgrade to enable System Manager administration of the B5800 Branch Gateway Note For new installations use the Initial Installation Utility before the control unit is connected to the network See Connecting the control unit to the network on page 86 for more information The Initial Installation Utility can be used to administer the control unit on site or while the B5800 Branch Gateway control unit is being staged off site This procedure includes the steps to manually launch the Initial Installation utility When a new B5800 Branch Gateway is detected the Initial Installation utility is launched automatically so you would begin with Step 3 Procedure 1 Start Manager and connect to the B5800 Branch Gateway system 2 Select File gt Advanced gt Launch Initial Installation Utility 3 In the Sys
117. D 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 A Warning Avaya supplied SD cards should not be formatted using any other method than the format commands within Manager and the System Status application Formatting the cards using any other method will remove the feature key used for B5800 Branch Gateway licensing from the card These procedures are run on an SD card inserted in a card reader on the Manager PC That card can then be used in the System SD card slot of a new system or in the Optional SD card slot of an existing system to upgrade that system Formatting an SD card 246 Before you begin To enable this option the working directory defined in File gt Preferences gt Directories must be set to the parent directory of the Memory Cards folder About this task Avaya SD cards should only be formatted using the format options provided within the B5800 Branch Gateway applications A Warning This procedure will erase any existing files and folders on the card Procedure 1 Start Manager 2 Insert the SD card into a reader slot on the Manager PC 3 Select File gt Advanced gt Format IP Office SD Card gt Avaya B5800 Branch Gateway 4 Browse
118. DARD 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 Save the modified STANDARD MIB file Add the MIB file SNMP FRAMEWORK MIB mib to the MIB database Add all the MIB files in the order listed Compile the MIBs ready for use Note The IPO PHONES MIB mib relies upon the DIFFSERV MIB mib for the definition of the textual convention of IndexInteger The DIFFSERV MIB needs the definition of the textual convention zeroDotZero which is normally defined in SNMPv2 SMI mib However including SNMPv2 SMI mib in the MIB file compilation list results in errors due to conflicts with what appear to be internal definitions within SNMPc and the SNMPv2 SMI section in its STANDARD mib file Therefore to resolve the issue the required definition of zeroDotZero must be placed in the SNMPv2 SMI section in SNMPc s STANDARD mib file Enabling SNMP and polling support About this task In order for the B5800 Branch Gateway control unit to be discovered and polled by an SNMP manager its SNMP agent must be enabled and placed in the same read community as the SNMP manager Procedure ar OO N Start Manager and connect to the B5800 Branch Gateway system In the left navigation pane click System Click the System Events tab Select SNMP Enabled Inthe SNMP Port field enter the UDP port number used by the SNMP agen
119. E SESESNS SSS SYS 3616 wireless 3620 wireless 3626 wireless 3641 wireless 3645 wireless 3720 DECT R4 3725 DECT R4 UNN YN YNYYS Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 23 B5800 Branch Gateway overview 24 Telephone Native extensions local extensions operating in the distributed branch user model 3740 DECT R4 v 3749 DECT R4 3810 digital wireless wv 4601 v 4602IP v 4602SW v 4610IP v 4610SW v 4621 v 4625 v 5402 v 5410 v 5420 v EU24 DSS a 5601 v 5602IP v 5602SW v 5610IP v 5610SW v 5620 v 5621 v EU24 BL DSS v 9504 digital v 9508 digital 9608 wv 9611G vw 9621G wv 9641G vw 9620L wv 9620C wv Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Supported telephones Telephone Native extensions local extensions operating in the distributed branch user model 9630G wv 9640 v 9640G We 9650 wv 9650C vw SBM24 wv Avaya 1010 1020 1030 1040 video v conferencing units B149 conference phone v B159 conference phone wv B179 conference phone v BM12 wv BCM TDM sets r e DECT handsets 4xxx 7xxx series e T7316E e T7316 T7406E e T7406 e T7208 e T7100 e T7000 e M7310 e M7310N e M
120. Entity List page select the SIP entity to which the routing policy applies c Click Select Skip the Time of Day section Dial Patterns section and Regular Expressions section You do not need to configure these settings Click Commit Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 169 Session Manager Configuration Creating dial patterns A dial pattern is defined to direct calls prefixed with the branch prefix to each branch 1 12 13 14 15 On the System Manager console under Elements click Routing 2 In the left navigation pane click Dial Patterns 3 4 On the Dial Pattern Details page in the Pattern field enter the branch prefix On the Dial Patterns page click New to create a new dial pattern This is the dialed number or number prefix that the dial pattern is intended to match Inthe Min field enter the minimum length 1 to 36 of the dialed number that the pattern should match For example if the branch prefix is 3 digits and the extension number length is 4 digits you would enter 7 Inthe Max field enter the maximum length 1 to 36 of the dialed number that the pattern should match For example if you set this to the same value as the Min value the dial pattern will match only internal calls For the Emergency Call check box leave the check box set to the default setting unchecked Inthe SIP Domain drop down box sel
121. I is required the URI Type should be set to SIPS SIPS can be used only when Layer 4 Protocol is set to TLS Layer 4 Protocol This can be set to TLS or TCP Set to TLS to choose SIPS as the URI Type when SIP Secured URI is required Send Port When Layer 4 Protocol is set to TLS the default setting is 5061 When Layer 4 Protocol is set to TCP the default setting is 5060 Listen Port When Layer 4 Protocol is set to TLS the default setting is 5061 When Layer 4 Protocol is set to TCP the default setting is 5060 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 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 147 Initial branch configuration Name Range or Default Description Default Codec Selection System gt Codecs Fax Transport Support Default None This option is only selectable if the option Re Invite Supported is also selected If enabled the B5800 Branch Gateway is able to support the sending and receiving of faxes via the Avaya Aura Session Manager line using the T38 protocol The settings for T38 are set on the T38 Fax tab Call Initiation Timeout Default 4 seconds The B5
122. IP Office window select the B5800 Branch Gateway system you want to view The file contents of the memory cards are displayed About backing up the System SD card There are two levels of backup that can be performed e Backup the System SD card primary folder The contents of the primary folder on the System SD card are copied to the backup folder on the System SD This can be performed remotely e Backup all files on the System SD card The contents of the primary folder backup folder and embedded voicemail files including message files on the System SD card are copied to the Optional SD card This can be performed remotely However the contents can only be copied back manually using a card reader 248 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com 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 Select File gt Embedded File Management 3 From the Select IP Office window select the appropriate system
123. If the required license quantity cannot be obtained or renewed for an already configured value of Maximum SIP Sessions then the B5800 Branch Gateway will be in License Error mode or in License Restricted mode if the 30 day grace period has expired The license error can be resolved either by making a sufficient quantity of SIP Trunk Session licenses available or by reducing the configured Maximum SIP Sessions setting to a value for which sufficient license quantity is available Regardless of the license mode the number of concurrent SIP sessions allowed in system operation is determined by the Maximum SIP Sessions setting 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 157 144 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Administering a Session Manager line for each branch Inthe left navigation pane click System Click the Telephony tab Click the Telephony sub tab a A O N Inthe 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
124. L Gateway and back into Avaya alarm receivers 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 gt Equipment Registration Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 201 Standalone SAL Gateway for remote service 3 Under Non Regional Product Specific Documentation select Universal Install SAL Registration Request Form 4 Complete the registration form as instructed 202 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Chapter 15 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 The system name can be changed to something more distinctive For more information about the system default settings see Default configuration on page 85 Note that if you change the IP address settings you must restart the system Procedure 1 2 Start Manager and connect
125. Linux editor update the parameter abg_b5800_mgr_version in the opt Avaya ABG lt version gt 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 If you fail to do so when you try to launch IP Office Manager from System Manager the launch will fail and the system will display an error message prompting you to update the parameter Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 113 Initial branch configuration 6 On the administration PC that will be used to launch IP Office Manager Lite set the environment variable to match the version of the B5800AdminLite exe file Depending on the version of Windows running on the PC do one of the following e If the PC is running Windows 7 go to step 7 e If the PC is running Windows XP go to step 8 7 If the PC is running Windows 7 do the following a 2295 gt h i From the Start menu right click Computer Click Properties In the left navigation pane click Advanced system settings In the System Properties dialog box click Environment Variables In the Environment Variable dialog box in the User variables for lt name gt area select AVAYAB5800_VER Click Edit In the Edit User Variables dialog box
126. MF support for enhanced voicemail continuity over the PSTN Available for Avaya Aura Messaging or Modular Messaging over SIP central voicemail systems this feature facilitates getting the call to the specific mailbox rather than to the general prompt When a PSTN number is configured B5800 Branch Gateway will send voicemail calls to that PSTN number when Avaya Aura Session Manager is not available Note In Release 6 2 this feature is not available for CallPilot Export user tool for an R6 1 to R6 2 upgrade support for exporting all users or selected users from a loaded configuration to an XML file that is then imported in Avaya Aura System Manager During a B5800 Branch Gateway R6 1 to R6 2 upgrade users are not automatically created in System Manager After an R6 1 to R6 2 upgrade B5800 Branch Gateway users are exported to a file and then the file is imported to System Manager Music on Hold administrator is able to change the Music on Hold Supported audio file formats are PCM or WAW 30 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Related resources Related resources Related documents Ensure that you have read this manual before starting the installation Also read the installation documentation for any other equipment and applications being installed as part of the B5800 Branch Gateway system Documents you may need to consult
127. Maximum Record Time field use the up and down arrows to set the maximum record time in seconds for recorded announcement and auto attendant prompts messages and prompts In the VoiceMail ports field use the up and down arrows to set the number of voicemail ports This field must match the number of voicemail ports that are licensed for the system Inthe 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 amp Page and then do the following i In the Paging Number drop down box select the appropriate hunt group or user extension ii In the Retries field use the up and down arrows to set the number of times to repeat the page Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 173 Voicemail configuration 10 11 12 13 14 15 Configuring 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 Toconfigure Centrex Transfer for this DTMF breakout select Centrex Transfer and then enter the transfer number in the Transfer Number field c To configure an extension number for this DTMF breakout select the appropriate extension number from the
128. N Enter the normal defaults for such a short code as follows ar OO N gt 6 Make the changes as follows a Inthe Code field enter 1N For this example 1N will match any national number dialing b Inthe Feature field leave the entry set as Dial3K1 c Inthe Telephone Number field enter 1N For this example 1N will match the number dialed by the user after the dial 9 prefix d Inthe Line Group Id drop down box select the line group used for the B5800 Branch Gateway system s external trunks The default is 0 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 295 Branch PSTN call routing examples 7 Click OK ARS ARS Route Id Secondary Dial tone Route Name PSTN SystemTone v Dial Delay Time System Default 4 Check User Call Barring In Service gt Out of Service Route lt None gt v l Time Profile N Out of Hours Route lt None gt v Code Telephone Number Feature Line Group Id 1N 1N Dial 0 Remnve 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 ARS ARS Route Id Secondary Dial tone Route Name SystemTone v Dial Delay Time System Default 4 Check User Call Barring In Service Out of Service Route lt None gt v
129. October 2012 Comments infodev avaya com Configuring the B5800 Branch Gateway for certificates 12 Click Save The B5800 Branch Gateway reboots Result When the B5800 Branch Gateway is administered by System Manager the following is automatically configured SNMP enabled e SNMP trap destination 1 from System Manager IP address All SNMP traps active e WebLM client active e WebLM service address from System Manager IP address e Remove all default extension users leaving NoUser and RemoteManager Additional features configured by the Initial Installation Utility After you run the Initial Installation Utility the following features are also configured e System Status Interface SSA service security level Unsecure only e Configuration service security level Secure Medium e Security Administration service security level Secure Medium e OAMP Web Services service security level Secure Low if locally administered e OAMP Web Services service security level Secure High if administered by System Manager e Admin Client Certificate checks High if administered by System Manager e SCEP client active if administered by System Manager e SCEP server IP address from SMGR IP address if administered by System Manager e Legacy Program Code Active if locally administered Configuring the B5800 Branch Gateway for certificates Before you begin Generate a certificate on Syst
130. October 2012 207 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 gt Advanced gt Reboot 3 In the Select B5800 window select the B5800 Branch Gateway system 4 5 Inthe Reboot window do one of the following Enter your user name and password e Select Immediate to reboot the system immediately e Select When Free to reboot the system when there are no calls in progress This selection can be combined with the Call Barring options e Select Timed and then specify a time in hours and minutes This reboots the system the same as When Free but first waits for a specific time After the specified time the system waits for there to be no calls in progress and then reboots This selection can be combined with the Call Barring options Note If the time is after midnight the system s normal daily backup is canceled Inthe Call Barring section select Incoming Calls and or Outgoing Calls These settings are used when the reboot mode is When Free They bar the sending or receiving of any new calls Click OK 208 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com About changing components About changing components Except for mem
131. R6 2 improves this TFTP port issue greatly in a number of ways System Manager does not use TFTP SysMonitor and IP Office Manager have configurable TFTP UDP port ranges e HTTPS is used for DECT R4 administration 284 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Port usage diagram Port usage diagram SSH TCP 22 SNMP UDP 162 SAL UDP 8162 SAL Gateway INADS TCP 5107 SAL TCP 7443 Security Devices SNMP UDP 161 SNMP UDP 162 Syslog UDP 514 Avaya Aura Communication Managet Session Mgr TCP HTTP 80 TCP HTTPS 443 HTTPS 7443 Syslog Server System Mer AES MM SBC Ete SIP TCP 5061 LDAP TCP 389 B5800 TCP 50802 50804 50808 50812 Network Admin NTP UDP 123 TFTP UDP 69 range Network Utilities Servers Monitor UDP 50794 RTP RTCP UDP 49152 53247 Avaya Gateway Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 285 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 2 way 286 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Appendix B B5800 Branch Gateway call flows Calls from local extensions i e deployed in the distributed branch user model 1 Local phone to loca
132. RI trunk card This card allows the base card to support up to 4 BRI trunk connections each trunk providing 2B D digital channels The card is available in 2 port 4 channels and 4 port 8 channels variants A maximum of 4 BRI trunk cards are allowed per control unit For S Bus connection the card can be switched from To trunk mode to So mode This mode requires additional terminating resistors and an ISDN crossover cable connection PRI trunk card This card allows the base card to support up to 2 PRI trunk connections The card is available in single and dual port variants The card can be configured for E1 PRI T1 robbed bit T1 PRI or E1R2 PRI trunks A maximum of 4 PRI trunk cards are allowed per control unit The B5800 Branch Gateway system supports 8 unlicensed B channels on each IP500 PRI U port fitted Additional B channels up to the capacity of ports installed and PRI mode selected require Universal PRI Additional Channels licenses added to the configuration These additional channels consume the licenses based on which additional channels are configured as in service from port 9 of slot 1 upwards D channels are not affected by licensing e Combination cards Combination cards are pre paired base and trunk daughter cards They provide 6 digital station ports 2 analog phone ports 10 VCM channels and either Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 21 B5800 Branch Gateway o
133. Rate 128kbps Audio sample size 16 bit 58 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Base and trunk card installation Property Value Channels 1 mono Audio Sample Rate 8 kHz Audio Format PCM Length Up to 90 seconds Procedure 1 Rename the music file holdmusic wav 2 Using a card reader copy the file into the system primary folder on the System SD memory card 3 Ifthe 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 9600 series phones screen saver file When idle 9600 Series phones can timeout and display a screen saver image A file 96xxiposs jpg is present on the cards by default You can replace this file with your own branded file The file should be smaller than the screen size on 9600 Series phones in order for the image to move around the screen Base and trunk card installation The base cards and trunk daughter cards should be fitted before power is applied to the control unit Ensure that cards are inserted in the order that matches the planned or pre built configuration In general the following applies to card installation e Cards can be fitted in any order into any available slots The only exce
134. Reception Breakout DTMF 0 drop down box Note You can also enter an external number in this field For the Breakout DTMF 2 drop down box repeat step 9 For the Breakout DTMF 3 drop down box repeat step 9 In the SIP Name field enter the appropriate name In the SIP Display Name Alias field enter the appropriate name In the Contact field enter the appropriate name Configure the Anonymous check box as appropriate This feature is enabled when this check box is selected Note For more information about the fields in the SIP Settings section see the IP Office Manager on line help Standalone Voice Mail About this task The B5800 Branch Gateway system can be configured to use Standalone Voice Mail Standalone Voice Mail provides additional port capacity provided on a Linux server Before you perform this procedure Standalone Voice Mail must be installed and configured on the Linux server The Standalone Voice Mail server and required Linux operating system 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 For more information see Editing a B5800 Branch Gateway system configuration f
135. SNMP As described above SNMP information can either be polled by the SNMP application or received as the result of the B5800 Branch Gateway sending SNMP trap information While the MIB files should not be edited they can be read using a text editor and contain descriptions of all the various information objects that can be polled or sent and the information that each object will include For a list of the MIB files see Installing the B5800 Branch Gateway MIB files on page 225 The NOTIFICATION TYPE objects are those used for SNMP traps The other types of objects are those that can be polled Installing the B5800 Branch Gateway MIB files To allow full communication between an SNMP agent and an SNMP manager the SNMP manager must load MIB files Management Information Base specific to the SNMP agent device and the features it supports These MIB files contain details of the information the agent can provide and the traps that it can send The MIB files for B5800 Branch Gateway operation are included on the B5800 Branch Gateway DVD in the folder AdminCD smnp_mibs The actual files required and the method of loading depend on the SNMP manager application being used The details below cover the two SNMP manager applications supported Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 225 Additional system procedures HP OpenView Network Node Manager Procedure 1 Copy the following MIB files
136. System Manager See Discovering B5800 Branch Gateways on page 126 In this task you add the branch to System Manager by identifying the subnet IP address in which the branch is located This task must be performed for each B5800 Branch Gateway that you want to manage from System Manager As an alternative you can also use one of the following methods to add the B5800 Branch Gateways to System Manager e Bulk importing of devices on page 128 This method requires that you first add each B5800 Branch Gateway to an xml file The xml file is then used to import the devices to System Manager e Adding the B5800 Branch Gateways to System Manager on page 129 In this task you manually add each branch to System Manager by identifying the IP address of the B5800 Branch Gateway This task must be performed for each B5800 Branch Gateway that you want to manage from System Manager Confirm that WebLM licensing for the branch is enabled See Enabling WebLM licensing for the branch on page 130 Create a system template Optional See Creating a system template on page 131 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration Comments infodev avaya com October 2012 Configuration checklist Description Section Uploading an auto attendant audio file Optional See Uploading an auto attendant audio file on page 132 10 Apply the s
137. THORIZED AVAYA RESELLER AS APPLICABLE UNDER A COMMERCIAL AGREEMENT WITH AVAYA OR AN AUTHORIZED AVAYA RESELLER UNLESS OTHERWISE AGREED TO BY AVAYA IN WRITING AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWARE WAS OBTAINED FROM ANYONE OTHER THAN AVAYA AN AVAYA AFFILIATE OR AN AVAYA AUTHORIZED RESELLER AVAYA RESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOU AND ANYONE ELSE USING OR SELLING THE SOFTWARE WITHOUT A LICENSE BY INSTALLING DOWNLOADING OR USING THE SOFTWARE OR AUTHORIZING OTHERS TO DO SO YOU ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE INSTALLING DOWNLOADING OR USING THE SOFTWARE HEREINAFTER REFERRED TO INTERCHANGEABLY AS YOU AND END USER AGREE TO THESE TERMS AND CONDITIONS AND CREATE A BINDING CONTRACT BETWEEN YOU AND AVAYA INC OR THE APPLICABLE AVAYA AFFILIATE AVAYA 2 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration Avaya grants you a license within the scope of the license types described below with the exception of Heritage Nortel Software for which the scope of the license is detailed below Where the order documentation does not expressly identify a license type the applicable license will be a Designated System License The applicable number of licenses and units of capacity for which the license is granted will be one 1 unless a different number of licenses or units of capacity is specified in the documentation or other materials available to you
138. Warning e A shutdown must always be used to switch off the system Simply removing the power cord or switching off the power input may cause errors e This is not a polite shutdown any users calls and services in operation will be stopped Once shutdown the system cannot be used to make or receive any calls until restarted e The shutdown process takes up to a minute to complete When shutdown the CPU LED and the base card LEDs 1 and 9 if trunk daughter card fitted will flash red rapidly The memory card LEDs are extinguished Do not remove power from the system or remove any of the memory cards until the system is in the this state e To restart a system when shutdown indefinitely or to restart a system before the timed restart switch power to the system off and on again Shutting down the system using Manager Procedure 1 Start Manager 2 Select File gt Advanced gt System Shutdown The Select IP Office window appears 3 Select the B5800 Branch Gateway system you want to shut down The System Shutdown Mode window appears 4 Do one of the following e To shut down the system for an indefinite period of time select Indefinite To restart the system you must switch the power off and then on e To shut down the system for a specific period of time select Timed and then specify the duration in hours and minutes The system will automatically reboot after the set time has elapsed 206 Implementing the Avaya B5800
139. a B5800 Branch Gateway restore This feature allows you to restore a saved B5800 Branch Gateway system configuration onto a B5800 Branch Gateway from System Manager a backup of a B5800 Branch Gateway system configuration onto a B5800 Branch Gateway from the device SD card users from System Manager to the B5800 Branch Gateway a saved B5800 Branch Gateway system configuration and user from System Manager onto a B5800 Branch Gateway e View events and alarms regarding various operations that occur on the B5800 Branch Gateway Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 15 B5800 Branch Gateway overview Avaya B5800 Branch Gateway R6 2 Management gt System Manager R6 2 TrustManagement r via SCEP User Template lt Editor View Management based bulk System Discovery rf configuration Configuration of selected or Security Backup amp Restore B5800s Configuration SWUpgrade N ofa apocinc Alarms Av B5800 m lt Manager SSA SysMon SMGR launches B5800 Manager in appropriate mode 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 connec
140. a aeania 219 SEEE AE E a i ss A EATE T AA T AAT E E EN EEN A ETE 220 Example of BRI S08 module coniguraNON sssrini iii aa 221 Etampes T CORN eA a SE S 221 Example 2 video CONTIGS csi teiccarsissisdocsamretslesemnmssneionaminaiancnanerneisersaaniaciceamnmmicinnaemmetteenenm 222 SNE rssh rss a a a TE 224 installing the B5800 Branch Gateway MIB MOS siicsscscctsssctanisarsenesiuiecciatnsnsreredadscacersoariiasiennearovartecds 225 Enabling SNMP and polling Suppor annia a a dan Aaa 228 Praning SNMF Tap Sendika N a 229 DTE parn RANI Eisini e ERA E E Aaa 230 Roro cad UTE pEr S n AON 230 ABOU erasing ME ENP sieni a a L eta eme a 231 Resetting the security settings to the default settingS iinisnsrsiisruniirenenriensiinnrcesrieaininirienriasnnris 234 Resetting the configuration and security settings to the default settings via the boot loader 234 ABOUT erasing ihe operational MMMNANG ss israse aaa aa 235 Rosel DUNG cenins nA 238 Cs RUN a SAN IR aa a aS 239 Chapter 16 SD card management sicacisaccssscsarinancnsrnsucaracnincccnsonsesinabienvienenenencdibanacabiawansuns 241 Bopa tonbe SLEA E a a Dated sael Use saad sinediacoe de eat igy Set aecenyspeet palates dtaniusaeacanbiies 244 About creating a BS800 Branch Gateway SD Caid aociras 246 Fometig an D e an A AS 246 Formatting a System SD card using the System Status application eeeeeeeeeeeeeeeeereernereen 247 R creating an SD Oair a E daar a ianiai 247 Venna Me Ca EOE aa Pre rer ry
141. ace 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 HTTP server Any supported HTTP server installation Note The HTTPS protocol is not supported for a B5800 Branch Gateway device to pull files from the external server Protocols for downloading the firmware upgrade files to the external server from the PLDS web site via System Manager An FTP SCP or SFTP server running on default ports Use SFTP or SCP for secure file transfer Setting up the external server to work as a remote software library for B5800 upgrades Procedure 1 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration Install the operating system 2 Install any supported HTTP server 3 4 Configure users for the FTP or SFTP or SCP access These users should have Install any one of the supported servers FTP SFTP or SCP read write and delete permissions for the directories configured to function as the storage location for the upgrade files Configure the HTTP server such that the location where the upgrade files are downloaded is accessible using an HTTP URL This URL is used to configure the external server as a software library on System Manager As B5800 elements use this HTTPS URL to pull the firmware files during upgrade the URL must be reachable to the B5800 elements Octo
142. address IP address and bin file used by the system An entry is normally automatically created when a configuration has been loaded from the B5800 Branch Gateway system 3 If an entry is not present do the following a Create a new entry manually The MAC address and IP address can be found in the control unit settings in the configuration file b Close Manager c Restart Manager 4 Under File gt Preferences ensure that Manager is set to 255 255 255 255 Also check that Enable BootP Server is checked 5 Select View gt TFTPLog 6 Check that the required bin file is present in Manager s working directory 7 Attach the serial cable between the PC and the DTE port on the control unit 8 Start the terminal program on your PC Note 236 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com 10 DTE port maintenance Ensure that the DTE port settings are configured as described in RS232 DTE port settings on page 230 Within a HyperTerminal session the current settings are summarized across the base of the screen Enter AT upper case An OK response appears Enter AT DEBUG The time and date and then the He110 gt prompt appears to show the system is ready to accept commands To erase the current configuration in RAM memory enter upgrade The B5800 Branch Gateway system erases the current software and then sends out a BOOTP
143. adernasiudedenter Waddenensduieadeameiaeccceaneniega 97 Remote Software Library for B5800 Branch Gateway upgrades essssssssinessrressseesssnrssssnnnrrnesssennsens 98 System requirements for the external SCrVel c ccccecceseeceececceeeeecceeeeeeeaeeeeeeeeeeseeeaaeeeseaaaeeeseaaeees 98 Setting up the external server to work as a remote software library for B5800 upgrades 99 EM TTI E A E E racine Anau alain E E E A etd vad A E E E AEE EE 100 Setting B5800 Branch Gateway SNMP attriDUIE Serii aan neces 100 Coniounng oser PLOS ICO E neuan ia a S 101 Geamg a OPA WON nicsen oaeee eraa AE AAEE AAE EA Ear EES 102 6 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Upgrading the B5800 Branch Gateway using System ManagQel cccccccscceeeseeeeeeneeeeeeaeeeeeeeesesaeeeeeaees 103 Chapter 7 Administration software Suite ccccsssseeeeeeeeeeeeeeeeeeeeeeeeeeseeeeeeeeeeeeeeeeeseeeenees 105 Sarma ce POSTON oo UARUIS 31 5 sacces aaseasuaaes ce eacacae E A 105 Sn eevee hc MOG goer ney Per Eee oer atee pe ergs AA tr errr E rent Tee ray ent werent yee re 106 Chapter 8 Initial branch CONfiQUIratiON eeeeeeeeeeeeeeeeeeeeeeeeeeeneeeeeeeeeeeeeeeeneeeeeeneees 109 C nigurat n GHOCKISE iccicsscvisce cis xcsvacdat vc iseantisasctanyiemnnaniedlineticalsinet rarer eaaa 109 Setting up System Manager to launch IP Office Managel ceccceseecsseeeeeeeeeeeeeeeee
144. age click New to create a new SIP Entity entity In the FQDN or IP Address field enter the IP address of the B5800 Branch Gateway system LAN interface configured for the Session Manager line operation Inthe Type drop down box select SIP Trunk SIP Trunk is the correct selection for branches deployed in the distributed branch user model Inthe Notes field enter a description to help identify this SIP entity as appropriate Inthe Adaptation drop down box select the adaptation that contains the digit conversions to apply to calls to and from the location Inthe Location drop down box select the location that matches the location you configured in Creating locations on page 166 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 167 Session Manager Configuration 10 11 12 13 14 15 16 In the Time Zone drop down box select the time zone for the location For the Override Port amp Transport with DNS SRV check box accept the default setting unchecked 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 In the Credential Name field accept the default setting blank In the Call Detail Recording field accept the default setting In the SIP Link Monitoring drop down box accept the default Use Session Manager Configuration
145. age 140 Use this procedure to set the prefix number for the B5800 Branch Gateway and the required extension length e See Changing the default codec selection on page 143 Use this procedure to set the preferred order for codec negotiation This can be done as a system default and also for each individual SIP and Avaya Aura Session Manager line e See Adding an Avaya Aura Session Manager line on page 145 Use this procedure to create a Session Manager line for calls to the Avaya Aura Session Manager e See Setting up outgoing call routing on page 151 Use this procedure to create short codes for routing calls to the Avaya Aura Session Manager line when the required destination or resource is on another branch of the Avaya Aura network e See How the B5800 Branch Gateway uses a configured Session Manager line_on page 153 e See Avaya Aura Session Manager line redundancy on page 150 Enabling SIP trunk support About this task Before adding any SIP trunks including Avaya Aura Session Manager lines the B5800 Branch Gateway system must be configured for SIP trunk operation The system has 2 LAN Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 139 Initial branch configuration interfaces LAN1 and LAN2 the Physical ports are labeled LAN and WAN respectively Either can be used for the Avaya Aura Session Manager line operation Important The configuratio
146. ager on this PC IP Office Manager will automatically launch Procedure 1 From the System Manager console under Elements select B5800 Branch Gateway 2 In the left navigation pane click System Configuration 3 On the B5800 Branch Gateway System Configuration page select the B5800 Branch Gateway device whose system configuration you want to view or edit 4 Atthe prompt Do you want to download Avaya B5800 Branch Gateway Manager from the server now click Yes 5 In the File Download dialog box click Save 6 Save the file to an appropriate directory for example C Program Files Avaya B5800 7 After the download completes in the Download complete dialog box click Run 8 In the Internet Explorer Security Warning dialog box where you are prompted Are you sure you want to run this software click Run 9 In the WinZip Self Extractor dialog box where you are prompted Do you want to install IP Office Manager click Setup 10 In the IP Office Manager Lite InstallShield Wizard dialog box do the following a Inthe Welcome dialog box click Next In the Customer Information dialog box click Next In the Destination Folder dialog box click Next In the Custom Setup dialog box click Next Click Install In the InstallShield Wizard Completed dialog box click Finish 11 Restart your PC 12 To verify your PC is configured correctly select My Computer gt System Properties gt Advanced tab gt Environment Variables
147. ail Instructions Using DTMF 12 Click OK 13 Select File gt Save Configuration The Send Configuration window appears and the Configuration Reboot Mode is set to Immediate Do not change the reboot mode Configuring B5800 Branch Gateway to use Modular Messaging over SIP for voicemail About this task The B5800 Branch Gateway system can be configured to use Modular Messaging as its voicemail server Note If Modular Messaging over SIP is used as the central voicemail system you are able to still use the local Embedded Voicemail or Standalone Voice Mail for auto attendant operation and for announcements to waiting calls 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 157 2 In the left navigation pane click System 3 Click the Voicemail tab 4 In the Voicemail Type drop down box select Modular Messaging over SIP Note Fields applicable to this mode of voicemail support remain enabled 178 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Configuring B5800 Branch Gateway to use Modular Messaging over SIP for voicemail 5 To enable the local B5800 Branch Gateway system features for E
148. al MNANE ridere r i 56 Gading a CTU PAU iE n iana EEA EEA AENA D 57 Adomo a coniguranon TUG co cainicedscnanpnsdedaca teansdedscnteanidedsent eiia ee a e a AERA 58 Aadma musitonhod HoE anonra A a eee ent ee eer rer eee rere rrr 58 9600 series phones screen savar TG lt csercccsecsiuidccennsedunndentanadeccss be nbasadddsnansusddeas runeavadstavanbuledseeranindeds 59 Basc andiunk eard me aN Peeeeer epee mentee eee rete mre tren er eer te eerste peer er er rere r tert ater tee treter ett tet r ree 59 Ton aie rel gies ae sire lt pc 4 s io O Rene erRtnen rer rertee erence rte mere rer rr rrr er tnt errerrr rte rer errrrte er errrrtr rn ecrtrt rte 60 legacy camner gard Wenara casi ccccnass ve sccadcadearbelciatacinede isis shaimseeehaieivetna EEA A Laa AOA 61 EC PAO A E E E A E I EA TE EE E 63 Wal MOUNINO anin a i eee ea 65 Mack I O oi A 67 Exierialerpancion FNS eia aaeain a Ea EE AEO EES 69 Connecting external expansion Modules aessa aada aad aiaa 70 Ee inea a E A E E E E A E E E A T 71 Out or Bullding cannections lightning GROIGCHON yas sicesssend oiarcen eased aie 72 Deponie ES WAS aU Os oc anerccciassceescednpstaceacstuieedere neat sacs npaiaeadeeapeascdocenanidacetemeat E A 74 Amao PHOS DANS DO aaa aaa roarasdo a asenens tera 75 FoC Mounir o panor DO aa 76 Admmietauon Sotya e SE aa a E N a EE rere rt rer ree 77 PEIEE Lola heen eee aA aaa aiaiai 78 installing the administration ON NING ssie rcn aeaa a 79 el e aE e E A A E AE EN EEN A A N E E A
149. alized management for single provisioning of native local users in distributed branch deployments System Manager replaces the Network Management applications that were used for centralized management in B5800 Branch Gateway R6 1 See Management on page 14 for more information e Licensing support for centralized licensing by WebLM server A single license file is generated in PLDS for multiple branches License entitlements are shared among multiple B5800 Branch Gateways e Heritage Nortel branch migration to B5800 Branch Gateway support for Norstar and BCM digital T amp M Series phones and 11xx 12xx phones running SIP 4 3 Support for B5800 Branch Gateway with CS 1000 R7 5 core in distributed branch deployments Note Integration of B5800 Branch Gateway with Communication Server 1000 is provided in a separate document See Implementing the Avaya B5800 Branch Gateway for a Communication Server 1000 Configuration e Voicemail support for Avaya Aura Messaging Standalone Voice Mail and CallPilot Avaya Aura Messaging or CallPilot can be configured as the central voicemail system With this option you are still able to use Embedded Voicemail or Standalone Voice Mail at each branch to provide auto attendant operation and announcements for waiting calls Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 29 B5800 Branch Gateway overview Note Release 6 2 does not support VMPro
150. an End Entity 9 In the left navigation pane click Public Web 12 13 14 15 16 17 On the Welcome to the public EJBCA page in the left navigation pane click Create Keystore On the EJBCA Certificate Enrollment page in the Username field enter the same username you entered when you created the End Entity in Step 4 In the Password field enter the same password you entered when you created the End Entity in Step 4 Click OK In the Options section accept the default settings for the Key length and Certificate profile fields and click OK The certificate is installed in your browser In the Alert dialog box click OK From your Firefox browser to view the certificate do the following Select Tools gt Options In the Options window click Advanced Click the Encryption tab Click the View Certificates button In the Certificate Management window click the Your Certificates tab eoa2900 8 From your Firefox browser to save the certificate in the X 509 PEM format do the following a Inthe Certificate Management window click the View button b Inthe Certificate Viewer window click the Details tab c Click Export d Inthe Save Certificate to File window in the Filename field change the file name suffix to cer The cer format is required for B5800 Branch Gateway e Click Save 120 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012
151. ansion modules are still applicable inside the rack cabinet Barrier box rack mounting kit 50 The barrier box rack mounting kit must be used for out of building analog phone extensions This bracket allows up to 8 barrier boxes to be rack mounted and simplifies the number of connections to the protective ground point in the rack This kit must be used when more than 3 barrier boxes are in use and supports a maximum of 16 barrier boxes for a single external expansion module Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com 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 e 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 e When connecting to expansion ports on a 4 port expansion card a yellow 2 meter 6 6 expansion interconnect cable can be used in place of the standard blue cable Four yellow cables are supplied with the 4 port expansion card Ed G C e OC N Li EE Ses ee aa ae sk EE I il O o wW n O N oo nN oOo AA A O w e O N Implementing the Avaya B5800 Branch Ga
152. ard by adding the trunk daughter cards or legacy carrier cards the base card can be inserted into the control unit Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 63 Hardware and software installation A Warning e Correct anti static protection steps should be taken before handling circuit boards e Cards must never be added or removed from the control unit while it has power connected Tools required e 5mm Flat blade screwdriver e Anti static wrist strap and ground point Installing a base card Procedure 1 Check that there is no power to the control unit 2 Using a flat bladed screwdriver remove the cover from the slot on the front of the control unit that will be used for each card being installed This cover is no longer required but should be retained until installation has been completed 3 Allowing the card to rest against the bottom of the slot begin sliding it into the control unit 4 When half inserted check that the card rails have engaged with the slot edges by trying to gently rotate it If the card rotates remove it and begin inserting it again The card should slide in freely until almost fully inserted 64 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Wall mounting 5 At this point apply pressure at the base of the front of the card to complete insertion 6 Using a flat
153. asisivesaccsomrtvecedssnsersacaddronavisentcenierseceds sersbocedlaiuariouniends 253 Restoring a configuration file from the Optional SD card using Managet cccceeeeeeteeeeeeeeees 254 Restoring a configuration file from the Optional SD card using a system phone cceeeeeeeees 254 Restoring software files from the Optional SD card using Managet cccecceeseeeeeeeeeeeeeeeeeeees 255 Restoring software files from the Optional SD card using a system phone ccc eeeeeeeeeeetees 255 System upgrade using Te a VSS SD Car aseni adaa NE ten aes 256 Upgrading ramoilaly using Managol soicisssriiisriiie tne Nawesmecnandiedeenctanianetd 257 Upgrading the SO card cai naasna A E 257 Upgrading using an Opional SD Car cisarina aa 258 Memar card C7 1H 24 s Bape eee pen nee mT DE AN Perrys 259 Shutting down a memory card using MANaGE ee ceecseeeeeceeeeteeneeeneeeceneeeeeeseeeeeneeesenessenereneeeseee 259 Shutting dawn a memory card using a system PRONE cisiicccccsisssccaimmeresnccinmrersecineeteccersnirrveneannes 260 Shutting down a memory card using System StAtUs asii 260 Memary card STATING cs iosiccicacdiahattcarsthamiiadantantacndininteeanianaincediaiats candapsiyauitanetianiaandscdiioevaenleeme 261 Slating Up a memory Card using Managert ciassa a aaa iaai 261 Starting upa memory card using System Stats acneei arainn aeaa aaa 261 Stanno upa card usina SY STON PHONE reiia a caren E a da 262 Chapter
154. at is initiating a connection request Ingress Connections or receiving a connection request Egress Connections Ext to Branch External to Branch this indicates whether traffic to this layer 4 port is needed between the branch and other sites requiring this port to be open on firewalls if any between the branch and the rest of the customer s network Note that this depends on the customer s deployment Valid Values are e Yes meaning typically needed e No meaning not expected to be needed Depends on customer deployment Notes Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 283 Avaya port matrix for B5800 Branch Gateway and SIP phones e Email will not flow through the B5800 Branch Gateway in this example See optional section for port 25 e An off site DHCP server is used to supply IP addresses to phones and PCs Otherwise add ports 67 and 68 in optional sections e The B5800 Branch Gateway IP address will be manually configured and not need a DHCP server e TFTP service begins using port 69 but eventually uses the source ports from both sides e Ports 80804 and 80812 are unsecure communications but have optional port 80805 and 80813 as secure options e For B5800 Branch Gateway R6 1 the TFTP UDP port selection is an issue IP Office Manager ENM and SysMonitor do not constrain the selection of TFTP UDP source port B5800 Branch Gateway
155. ation 7 Inthe Service Details tab click the check box for Under SMGR Administration to deselect this option Note This check box is checked by default and you are not able to administer the branch through IP Office Manager To be able to use IP Office Manager to administer the branch this check box must be unchecked 8 Click OK 9 Select File gt Save Security Settings Enabling the Security Settings option for the branch About this task To disable the System Manager administration feature for a branch that is centrally managed by System Manager you must have access to the Security Settings for that branch If the branch configuration has not yet been opened from IP Office Manager the Security Settings option is not available To enable the Security Settings option you must de select the Set Simplified View as default option in the IP Office Manager Preferences window Once that is done the Security Settings option becomes available for that branch Note This task needs to be performed only one time Procedure 1 Start IP Office Manager 2 Select File gt Preferences Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 161 Managing B5800 Branch Gateways from System Manager 3 In the Preferences tab click the Set Simplified View as default check box to de select this option 4 Click OK 5 Close IP Office Manager 6 See Disabling the System Manager admin
156. ation ACSS 1 Available Manager Administration Proctored Now Exam Exam Existing 5U00040I Avaya Aura Communication ILT 40 Available Manager Maintenance and Now Troubleshooting Existing 5M000501 V Avaya Aura Communication vILT ILT 40 Available Manager Messaging Now Embedded Administration Maintenance and Troubleshooting 304 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Recommended courses Type Code Course title Delivery Duration First hours offering Existing 3101 Avaya Aura Communication ACSS 1 75 Available Manager and CM Messaging Proctored Now Embedded Maintenance Exam and Troubleshooting Exam Update ATI02348IE Avaya Aura Communication vILT ILT 40 March N VEN Manager Implementation 2012 Existing ATI01731V Avaya Aura Communication vILT 16 Available EN Manager Messaging Now Embedded Implementation New 4U00115I V Avaya Aura Communication vILT ILT 16 March Manager Implementation 2012 Upgrade R5 X to R6 X Existing 6002 Avaya Aura Communication ACIS 2 Available Manager and CM Messaging Proctored Now R6 X Implementation Exam Exam New 4U00121W Avaya Aura Communication WBT 2 Available Manager 6 2 Technical Delta course Now Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 305 Recommended courses for Avaya
157. ation Exam Administration Maintenance and Troubleshooting Exam Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 303 Recommended courses for Avaya B5800 Branch Gateway training Table 2 Avaya Aura Session Manager and System Manager Type Code Course title Delivery Duration First hours offering New 5U00106W Avaya Aura System WBT 1 Available Manager Overview course now New 5U00105W Avaya Aura Session WBT 4 5 Available Manager Overview course now New 5U00095V Avaya Aura System vILT 16 April Manager Implementation 2012 Administration Maintenance and Troubleshooting New 5U00096V Avaya Aura Session vILT 64 April Manager Implementation 2012 Administration Maintenance and Troubleshooting New 5U00097 1 AvayaAura Session Manger ILT 80 April and System Manager 2012 Implementation Administration Maintenance and Troubleshooting New 5U00104W Avaya Aura Session WBT 1 Available Manager 6 2 Delta Overview course now New 5U00103W Avaya Aura System WBT 1 Available Manager 6 2 Delta Overview course now Table 3 Avaya Aura Communication Manager and CM Messaging Embedded Type Code Course title Delivery Duration First hours offering New 5U000411 Avaya Aura Communication ILT 40 Available Manager Administration Now Existing 3100 Avaya Aura Communic
158. ave Configuration Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 297 Branch PSTN call routing examples 298 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com 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 This allows authorized users to make otherwise restricted calls from any extension without first having to log in to that extension and then log out after the call How authorization codes work e A user dials a number that matches a short code set to Force Authorization Code e The user is prompted to enter an authorization code e They dial their authorization code If a matching entry is found in Authorization Codes entries the system checks the corresponding user or user rights in that order Note that the user or user rights checked does not necessarily need to be connected with the user dialing or the user whose extension is being used to make the call The dial s
159. b About this task Once you have changed the B5800 Branch Gateway system default settings to those that match the customer requirements use this task to connect the B5800 Branch Gateway control unit to the customer s network Procedure 1 Disconnect the LAN cable from the installer PC 2 Connect the LAN cable to the customer network 3 If you want to use the administration PC for on going administration connect the PC to the customer network Connecting phones Procedure 1 Connect the analog phones to the phone ports 2 Ensure that the analog phones that are connected to power failure ports are clearly labeled as such 3 Connect the Avaya digital phones to the appropriate DS ports When the control unit is started after loading its own firmware and the firmware for its external expansion modules it will upload the appropriate firmware to the digital phones Avaya H 323 phones do not need to be connected at this stage They will go through a firmware upgrade process when connected to a B5800 Branch Gateway system that is already running Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 87 Hardware and software installation 88 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Chapter 5 Upgrading an R6 1 system to R6 2 This chapter provides the procedures to upgrade a B5800 Branch Gateway deployed in
160. backup folder you copy the contents of the backup folder on the System SD card to the primary folder on the System SD card Files with matching file names are replaced A Warning This procedure will cause the B5800 Branch Gateway system to be restarted disconnecting any current calls and services in progress Restoring from the backup folder using Manager Procedure 1 Start Manager 2 Select File gt 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 gt 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 The process takes approximately 6 minutes When 250 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com 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 Inthe 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 The process takes approximately 6 minutes When
161. ber 2012 291 Branch PSTN call routing examples ARS ARS Route Id Route Name Dial Delay Time In Service Time Profile Code 11 911 ON 1N xN XRARRXXXAAN ON iN N N 9 Click OK Telephone Number 911 911 50 Secondary Dial tone System Default 4 SystemTone Check User Call Barring l Out of Service Route lt None gt Out of Hours Route lt None gt I Remove Line Group Id 0 0 99999 99999 0 0 Feature Dial Emergency Dial Emergency Dial 3K1 Dial 3K1 Dial 3K1 Dial 3K1 Edit 10 Select File gt Save Configuration Branch PSTN override In the example described in Centralized call control on page 289 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 One example is the Avaya Aura Messaging or Modular Messaging PSTN number that can be configured for access to voicemail when the branch s Avaya Aura Session Manager line is out of service Another might be to provide a maintenance number to the headquarters site to report suspected loss of the Avaya Aura Session Manager line connection Adding an overriding short code Procedure 1 From the System Manager console select the B5800 Branch Gateway device and c
162. ber 2012 99 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 125 for more information The B5800 Branch Gateway devices to be discovered for upgrades should be SNMP enabled and the corresponding SNMPv1 communities must be set correctly in System Manager See Setting B5800 Branch Gateway SNMP attributes on page 100 for more information About this task Use this task to collect the components of a B5800 Branch Gateway that has been added on System Manager Note This task does not automatically find the new B5800 Branch Gateways The B5800 Branch Gateway must first be added to System Manager Then this task will collect the components for the B5800 Branch Gateway that was added to System Manager B5800 Branch Gateways that are added to System Manager using the discovery method described in Discovering B5800 Branch Gateways on page 126 already have their inventory details collected You do not need to perform this task to upgrade those B5800 Branch Gateways Procedure 1 From the System Manager console under Elements click Inventory 2 On the Inventory page on the left navigation
163. binary file to load It does this using the possible source below in the order shown skipping to the next source if the file is not present or is not valid 1 System SD card primary folder 2 The control unit s own internal non volatile memory Once a system has been installed it uses its non volatile memory to keep copies of the configuration and system binary files it is using These can be used to restore operation during a system reboot Note that though a system can boot from non volatile memory a System SD card must still be present for correct system operation System SD card backup folder Optional SD card primary folder Optional SD card backup folder O a A O If no file is found the control unit will fallback to making BOOTP requests to the network Manager can respond to the BOOTP request See About erasing the operational firmware on page 235 for more information Once a valid bin file is found the control unit loads that firmware The source from which the control unit binary file was loaded is then used to load further files Configuration file loading After the system firmware files are installed a configuration file must be installed on the control unit e If the control unit booted using binary files from an SD card location it looks for a valid configuration file in the same location If a configuration file is present and valid it is loaded If a configuration file is present but is no
164. ble on the network Important Once the control unit has obtained IP address and DHCP mode settings it retains those settings even if rebooted without a configuration file present on the System SD card To fully remove the existing IP address and DHCP mode setting the B5800 Branch Gateway must be defaulted using Manager Connecting the control unit to the network Before you begin The system default settings must be changed to match the customer requirements before the control unit is connected to the network Use the Initial Installation Utility to assist in configuring the system settings To run the Initial Installation Utility see Using the Initial Installation Utility on page 121 The Initial Installation Utility is run using IP Office Manager from a PC or laptop that is connected directly to the B5800 Branch Gateway LAN 1 port The Initial Installation Utility will 86 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com 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 e UDP discovery and 255 255 255 255 File gt Preferences gt Discovery tab e Auto Connect on start up File gt Preferences gt Preferences ta
165. box if there is an available extension that you want to assign to this user When you select this check box if there are unassigned extensions a drop down box appears from which you can select an unassigned extension to assign to this user c Inthe Extension field enter the appropriate extension d Inthe Template drop down box select the appropriate template 186 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com 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 The changes are not reflected in the template Note Parameters for this user can also be configured using the endpoint template See Creating an endpoint template on page 133 for more information f For the Delete Extension On User Delete check box do one of the following e Accept the default unchecked if you are using an analog or digital set type template and this feature is checked for other set types e Select this check box if you want the extension to be deleted when
166. c ccsscccceceessssneeeeeesessnaees 44 CONPIQUIATION ecsrrsieiraideieni iiaeie 57 231 create NEW cssccvedeiedasetectieetele aadeesiadsdin n ae nE e 57 NSO a Er a a a 231 configuration checklist cccecceeeeeeeeeeeeeeeeeeeeeeeeees 109 Configuring Avaya Aura Messaging ce 176 configuring Embedded Voicemail ceeeee 173 Configuring Modular Messaging eeeeeeeeees 178 configuring Standalone Voice Mail ccccccceeeees 174 configuring the B5800 Branch Gateway for certificates side seeonetaammuanemnusoud E 123 configuring user PLDS ACCESS s e 101 Connecting the control unit to the network 86 CONNECTIONS 0 0 ee ceccccccceccecaeeeeeeeeeeeeeeeceeeeeeaeaeaaeeenes 44 72 QFOUNGING serrer ected 44 out of building 2 e eee eeceteeee cee eeteeeeeeseeeeeneteaeees 72 Control Uniteam a ia 44 Rack mounting sssssesseeseerennssnssenssesssresrrerrennnenne 44 Wall MOUNTING nasccinreracrmna 44 COUNTY aorin EEE EEEN 27 languages erna etek yale ies 27 Supported locales eeeeceeeeceeeeeeeeeeeeeeeeeetteeeteeees 27 Create configuration file 0 0 0 0 ccccccceeeeeeseeesesttteeeeees 57 creating a backup of the system configuration using System Manager ecceeeeeeeeeeeeeeeeeeeeeeees 215 Creating a software library cccseeeeeeeeeeteeeeeeees 102 creating a system template iessen 131 creating a user template 0 ccccceeeeeeeeeeeeeeeee
167. 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 To search license entitlements by group name enter the appropriate information in the Group name or Group ID fields Group Names or IDs are specific to Functional Locations and Sold To s that define the actual location of equipment and software Tip You can use a wildcard character if you do not know the exact name of the group you are searching for For example if you enter Gr the system searches for all the groups starting with the characters Gr You can enter a wildcard character at any position in the search criteria 6 To search license entitlements by LAC enter the specific LAC in the LAC field Tip You can use a wildcard character if you do not know the exact LAC you are searching for For example if you enter ASO the system searches for all the LACs starting with ASO You can enter a wildcard character at any position in the search criteria You will receive LACs in an e mail if you have supplied the e mail address to your sales order If you do not have this code search by using one of the other search criteria 7 To search license entitlements by application product or license status select the appropriate application
168. cases these only work with loop start analog trunks Any phones connected to these ports should be clearly labeled as power fail extensions in accordance with the appropriate national and local regulatory requirements Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com 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 e Temperature 0 C to 40 C 32 F to 104 F e Humidity 10 to 95 non condensing e Check there are no flammable materials in the area e Check there is no possibility of flooding e Check that no other machinery or equipment needs to be moved first e Check that it is not an excessively dusty atmosphere Check that the area is unlikely to suffer rapid changes in temperature and humidity e Check for the proximity of strong magnetic fields sources of radio frequency and other electrical interference e Check there are no corrosive chemicals or gasses e Check there is no excessive vibration or potential of excessive vibration especially of any mounting surface e Check that where telephones are installed in another building that the appropriate protectors and protective grounds are fitted see Out of Building Telephone Installation on page 72 e Check there is suitable lighting for installation
169. ceeeeeeseteeeeeeteees 201 standalone gateway c ccccesseeeeeeesseees 199 200 searching for license entitlements ee 193 sending the system template to multiple B5800 Branch Gateways 2 cicccasseetevicvancecstuedeacaeatenedanacdeecesticn 132 Session Manager tab field descriptions 2 146 Setting B5800 Branch Gateway SNMP attributes 100 setting up external Server eee eeeteteeeeeeeeeeentaeees 99 Setting up System Manager to launch IP Office Manager wustivenealedecuvuewedsadvantee dd aWeatnadwonedatduananesdevecsseynes a 112 setting up the external server as remote software library ana a a a a aa aaa aaea aa 99 Short Code tab field descriptions ccscceeeee 153 SIP domain eonia n 166 SIP eni eeo naa E 168 SIP Link MOnitoring sesser 167 SIP Registrar tab field descriptions 00cee 155 SIP trunk support eee eee eeeeeeeeceeeeeeeeeeeeeeeeteeeetenees 139 SM line redundancy ccccecececceesseceeeeeessseeeeeeeees 150 SNMP aatar 127 224 225 228 229 EnabliN Gis iscestcdeccebensantdsagecnpuessaats sinecdaztsan cheers 127 228 INSTA ATION aarin aa NN 225 0101n E E T E E TN 127 228 ESPON sceedeccccnerevies duaeysetiecadesbednaecceenbesuveedeavs 127 228 TAD Sendi oiiire aa 229 SOG a E E E E E 221 222 example ISDN terminal cccccccccccsesesssteeees 221 Example video Conference ccccccsessssteeeees 222 SOCKETS sai seisivinticdscaatevssside
170. cking up to the Optional SD card takes at least 90 minutes and may take much longer depending on the amount of data to be copied For example it will take longer if embedded voicemail is being used by the B5800 Branch Gateway system to take messages Backing up to the Optional SD card using Manager Procedure 1 Start Manager 2 Select File gt 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 gt Copy System Card The contents of the System SD card are copied to the Optional SD card This takes at least 90 minutes and can take much longer Backing up to the Optional SD card using the System Status application Procedure 1 Start the System Status application and access the B5800 Branch Gateway status output 2 In the navigation panel select System 3 Select Memory Cards 4 Select System Card 252 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com 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
171. click Manage Users 3 On the User Management page click New 4 On the New User Profile page in the Identity section do the following a Inthe Last Name field enter the user s last name Note Depending on how the branches and stations in your system are named and organized you could enter a location name in this field for example Chicago 25 Then in the next field First Name you could enter a location within that branch for example cashier In the First Name field enter the user s first name In the Middle Name field enter the user s middle name In the Description field enter a description of this user profile In the Login Name field enter the extension user login in the format username domainname com or extension domainname com For example nsmith avaya com or 5002432 avaya com For survivability mode operation with a B5800 Branch Gateway system the user name without the domain name should match the user name configured in the branch system f Inthe Authentication Type drop down box accept the default setting Basic g Inthe Password field enter the password required to log into System Manager for personal web configuration papp Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 185 User administration h Inthe Confirm Password field enter the password again i Inthe Localized Display Name field enter the name to be used as the calling party In the Endpoint Di
172. 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 Creating a configuration file About this task Manager can be used to create a new configuration file without connecting to a B5800 Branch Gateway system This allows the creation of a configuration prior to installing the system The configuration file can be loaded on the System SD card before the card is installed The configuration file specifies the system s location trunk cards control unit and expansion modules e The configuration created must match the physical equipment in the B5800 Branch Gateway system for which the configuration will be loaded If they do not match the system may reset and experience other problems e The configuration creation tool includes all control units external expansion modules and trunk cards supported by B5800 Branch Gateway It is your responsibility to confirm the B5800 Branch Gateway equipment that is supported in your location Procedure 1 Start Manager with no configuration loaded into Manager 2 Click on Create an Offline Configuration in the simplified view 3 Select the type of configuration that you want to create 4 When completed click OK Manager will create and load the configuration Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 57 Hardware and
173. core SIP router See Configuring B5800 Branch Gateway to use Modular Messaging over SIP for voicemail on page 178 for more information When Modular Messaging over SIP is used as the central voicemail system at each branch you have the option to still use the local Embedded Voicemail for auto attendant operation and for Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 37 Planning announcements to waiting calls Note that for this configuration Embedded Voicemail licenses are required For more information about licensing see Licensing on page 16 The Park and Page feature is supported when the system voicemail type is configured as Embedded Voicemail or Standalone Voice Mail Park and Page is also supported on systems where Avaya Aura Messaging or Modular Messaging over SIP is configured as the central voicemail system and the local Embedded Voicemail provides auto attendant operation The Park and Page feature allows a call to be parked while a page is made to a hunt group or extension See Configuring Embedded Voicemail on page 173 for more information Branch PSTN call routing considerations 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 For examples of some of the options
174. d go Note See Branch PSTN call routing examples on page 289 for information on routing back to the branch for fallback alternate routes Note If using Avaya Aura Conferencing 7 0 the B5800 Branch Gateway short code should include routing to Session Manager any call that is made to the Avaya Aura Conferencing 7 0 number Ideally the number of such system short codes should be kept to a minimum and the same short codes used on all branches in order to ease maintenance This is where using a uniform Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 151 Initial branch configuration dial plan for all branches helps as explained in Dial plan considerations on page 36 For our example the uniform dial plan allows the same single short code to be used at all branches See the Manager context based help for more information on creating short codes Note In the Distributed branch user model when a short code match occurs and the telephone number to be sent to the Avaya Aura Session Manager line begins with the B5800 Branch Gateway system s own branch prefix the prefix is removed and the call is re targeted locally on the B5800 Branch Gateway system 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 Edi
175. d on the device Accept the default settings in the Timeout ms and Retries fields Click Commit On the Configuration page click the Subnets tab Click New On the Add Subnet Configuration page in the Subnet IP field enter the IP address of the subnet in which the branch is located In the Subnet Mask field enter the subnet mask in which the branch is located In the Use SNMP V3 drop down box accept the default setting No Under SNMP Access click the check box es to select the appropriate SNMP access configuration s Click Commit The new network appears in the list on the Configuration page On the left navigation page under Inventory Management click Collect Inventory 126 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com 18 19 20 21 About adding B5800 Branch Gateways to System Manager Under Select Network Subnet s click the check box es for the network subnets on which you want to discover B5800 Branch Gateways Under Select Device Types click the check box for B5800 Branch Gateway Do one of the following e Click Now to run the inventory discovery job now e Click Schedule to run the inventory discovery job at a scheduled date and time When the job is completed the B5800 Branch Gateway device s appear on the Collected Inventory page and on the Upgrade Management gt Manage Software page Repeat steps
176. ding connection must be via earthed ducting preferable underground The cable must not be exposed externally at any point Analog trunks ITWLinx towerMAX CO 4x4 Supports up to 4 two wire lines This device was previously referred to as the Avaya 146C For installations in the Republic of South Africa the fitting of surge protection on analog trunks is a requirement For other locations where the risk of lightning strikes is felt to be high additional protection of incoming analog trunks is recommended Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 73 Hardware and software installation Connection type Protection device type Requirement External output switch ITWLinx towerMAX SCL 8 This device was previously referred to as the Avaya 146G 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 DS phone IROB installation When digital phone extensions are required in another building additional In Range Out Of Building IROB protective equipment must be used For phones connected to B5800 Branch Gateway DS ports the supported device supplied by ITWLinx is a towerMAX DS 2 module This IROB device was previously referred to by Avaya as the 146E IROB The protection device should be installed as pe
177. drop down box select INBOUND_OUTBOUND_TLS b Inthe Username field enter the name of the B5800 Branch Gateway system c Inthe Password field enter a certificate password Note This password will be used as the Simple Certificate Enrollment Protocol SCEP password d Inthe Confirm Password field enter the password again e Inthe 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 f Inthe Certificate Profile drop down box accept the default setting ID_CLIENT_SERVER In the CA drop down box accept the default setting tmdefaultca In the Token drop down box accept the default setting User Generated ze Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 119 Initial branch configuration i Click the Add End Entity button The page refreshes and a message appears at the top of the page stating the End Entity was added successfully 5 In the left navigation pane click List Edit End Entities 6 On the List Edit End Entities page in the Or with status drop down box select All 7 Click the List button 8 Confirm the B5800 Branch Gateway End Entity that you just added is listed Note that New appears in the Status column for this End Entity This indicates System Manager has prepared the certificate for exchange with
178. e 9 In the Warning dialog box click OK 12 13 Inthe Default Certificate Name box enter the appropriate name This is the same name you used when you created the certificate for the End Entity in System Manager See Generating a certificate on System Manager on page 119 for more information Inthe Received Certificate Checks Management Interfaces drop down box accept the default setting None In the Received Certificate Checks Telephony Endpoints drop down box accept the default setting None In the SCEP Settings section do the following a Click the Active check box to select that option b Inthe Request Interval Seconds box accept the default setting 120 c Inthe 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 567 89 124 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com 14 15 16 17 18 19 20 g About adding B5800 Branch Gateways to System Manager In the SCEP Server Port field accept the default setting 443 In the SCEP URI field accept the default setting In the SCEP Password field enter the appropriate password This is the same password you used when you created the certificate for the End Entity in System Manager See Generating a certificate on System Manager on page 119 for
179. e 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 176 for more information When Avaya Aura Messaging is used as the central voicemail system at each branch you have the option to still use the local Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 171 Voicemail configuration Embedded Voicemail for auto attendant operation and for announcements to waiting calls Note that for this configuration Embedded Voicemail licenses are required e Modular Messaging over SIP The B5800 Branch Gateway system can be configured to use Modular Messaging over SIP as its voicemail server when Session Manager is used as the core SIP router See Configuring B5800 Branch Gateway to use Modular Messaging over SIP for voicemail on page 178 for more information When Modular Messaging over SIP is used as the central voicemail system at each branch you have the option to still use the local Embedded Voicemail for auto attendant operation and for announcements to waiting calls Note that for this configuration Embedded Voicemail licenses are required For more information about licensing see Licensing on page 16 About the Park and Page feature Beginning with Release 6 2 B5800 Branch Gateway supports the Park and Page feat
180. e 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 Therefore if one IP address octet changes or one port number changes the data flow is unique Socket example showing ingress and egress data flows from a PC to a web server Socket Example Diagram Client HTTP Get Source 192 168 1 10 1369 Destination 10 10 10 47 80 Web Server N TCP info Destination 192 168 1 10 1369 Source 10 10 10 47 80 14 Notice the client egress stream includes the client s source IP and socket 1369 and the destination IP and socket 80 The ingress stream has the source and destination information reversed because the ingress is coming from the server Firewall types There are three basic firewall types described below Packet filtering Packet Filtering is the most basic form of the firewalls Each packet that arrives or leaves the network has its header fields examined against criterion to either drop the packet or let it through Routers configured with Access Control Lists ACL use packet filtering An example of packet filtering is preventing any source device on the Engineering subnet to telnet into any device in the Accounting subnet Application level gateways Application level gateways ALG act as a proxy preventing a direct connection between the foreign device and the internal destination device ALGs filter each
181. e System Manager WebLM See Installing the shared PLDS license file on the System Manager WebLM server on server page 117 Note If you are using the individual licensing method see Using Manager to deliver license files to the branches on page 117 Note Steps 1 through 3 only need to be performed one time They do not need to be performed for each new B5800 Branch Gateway 4 Generate a certificate on Avaya Aura System Manager See Generating a certificate on System Manager on page 119 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 109 Initial branch configuration 110 Description Section Run the Initial Installation Utility The Initial Installation utility provides configuration and security settings that minimize initial installation activities and maximize security See Using the Initial Installation Utility on page 121 Note When you run the Initial Installation Utility a security certificate is automatically installed on the B5800 Branch Gateway If you do not run the Initial Installation Utility you must manually configure the SCEP and security settings on the B5800 Branch Gateway This is not the preferred method but can be used as an alternative For more information see Configuring the B5800 Branch Gateway for certificates on page 123 Add the B5800 Branch Gateways to
182. e and reboot This will cause them to recheck whether the firmware they currently have loaded matches that on their configured file server Use this option if the B5800 Branch Gateway system is the file server and the upgrade included new IP phone firmware 9 Click Upgrade The system password for each system is requested 10 Enter the system password and click OK Restoring the system configuration using System Manager Procedure 1 From the System Manager console under Elements select B5800 Branch Gateway 2 In the left navigation pane click Backup and Restore 3 Onthe B5800 Branch Gateway Backup and Restore page select the B5800 Branch Gateway device whose backup configuration you want to restore You can select multiple devices 218 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com External output port EXT O P 4 Click Restore 5 On the B5800 Branch Gateway Restore page do one of the following e 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 e Click User to restore the respective users from System Manager to the B5800 Branch Gateway device e Click System Configuration and Users to restore the respective system configurations and users from System Manager to the B58
183. e 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 e 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 Manager is also used to upgrade the system software files e System Status The IP Office System Status application is a monitoring and reporting tool that provides a wide range of information about the current status of the system It can report the available resources and components within the system and details of calls in progress Details of the number of alarms are recorded and the time and date of the most recent alarms e 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 Installers and maintainers must understand how to run System Monitor when necessary as Avaya may request copies of System Monitor traces to resolve support issues Starting System Status About this task The IP Office System Status application is a monitoring and reporting tool that provides a wide range of information about the current status of the syst
184. e 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 Inthe Community field enter the community that will be used by the agent and the SNMP manager 13 In the Events section click the check boxes for the events you want to send See the Manager on line help for a description of the events 14 Click OK 15 Select File gt Save Configuration to send the configuration back to the B5800 Branch Gateway and then select reboot DTE port maintenance The DTE port on the back of control unit is not normally used when configuring an B5800 Branch Gateway system However in extreme cases the DTE port can be used to default the system s configuration or to erase the core software if necessary A Warning The procedures in this section should only be performed if absolutely necessary to return a system back to working order In all cases you must have a backup copy of the system configuration before you perform these procedures See Creating a backup of the system configuration using IP Office Manager on page 215 The DTE ports on B5800 Branch Gateway expansion modules are not used for any maintenance or diagnostics RS232 DTE port settings The RS232 DTE ports are located on the rear of all control units and external expansion modules The DTE ports on external expansion modules are not used The RS232 DTE ports 230 Implementing the A
185. e synced back to System Manager For more information about the two management methods that is central management from System Manager or local management from IP Office Manager see Management on page 14 Do not use both of these management methods to configure and manage users and extensions on a B5800 Branch Gateway system System Manager does not support the configuration of User Rights on B5800 Branch Gateway systems Similar functionality of applying selected user settings to groups of users is available from the System Manager user template capability About disabling the System Manager administration feature for a B5800 Branch Gateway If the B5800 Branch Gateway is centrally managed by System Manager and you want to administer the B5800 Branch Gateway using IP Office Manager that is directly connected to the branch for example to install an individual PLDS license file you must first disable the System Manager administration feature for the branch Disabling the System Manager administration feature for a branch can be performed from System Manager or from IP Office Manager if the network connection to System Manager is not available After you disable the System Manager administration feature for a branch and administer the branch using IP Office Manager you must synchronize the B5800 Branch Gateway with System Manager to synchronize the changes and return the System Manager administration feature for the branch to the enabled state
186. e used to authorize calls made by users currently associated with that set of user rights e User This field is used to select a user with which the authorization code is associated The authorization code can then be used to authorize calls made by that user 302 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com 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 First hours offering Existing 2U000210 Avaya Branch Gateway eLearning 0 5 Available What Sales needs to know for now the first conversation Existing 2U000220 Avaya Branch Gateway eLearning 0 5 Available What Sales needs to know to now continue the conversation Existing 4U00112V PA Implement Avaya B5800 vILT 16 Available Branch Gateway now Implementation Existing 4U00112A PA Implement Avaya B5800 Online 1 Available Branch Gateway Assessme now Implementation Assessment nt New 5U00005V ACSS Avaya B5800 VILT 40 May Branch Gateway 2012 Implementation Administration Maintenance and Troubleshooting New TBD ACSS Avaya B5800 ACSS 2 May Branch Gateway Proctored 2012 Implement
187. ect the appropriate SIP domains that should be matched or select All to allow calls from all SIP domains to be routed Inthe Notes field enter notes to describe this dial pattern as appropriate 10 11 In the Originating Locations and Routing Policies section click Add In the Originating Location section click the check box for Apply The Selected Routing Policies to All Originating Locations In the Routing Policies section click the check box for the routing policy that was created for the branch Click Select If you need to specify that calls from certain locations be denied do the following a In the Denied Originating Locations section click Add b Do one of the following e Click the Apply to All Originating Locations check box e Click the check box es for the locations that should be denied c Click Select On the Dial Patterns Detail page click Commit 170 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Chapter 11 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 e Implementing Embedded Voicemail for B5800 Branch Gateway Release 6 2 document number 18 6
188. ection options for menus displayed by the phone s own software 28 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com New in this release e 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 itis running otherwise it defaults to UK English If required the language used within the Manager screens can be overridden e Embedded Voicemail Indicates that the locale is recognized by Embedded Voicemail and appropriate language prompts are then used If an unsupported locale is used Embedded Voicemail will attempt the best match using the first two characters of the locale The system locale can be overridden by setting a different user locale e Standalone Voice Mail Indicates that the locale is recognized by Standalone Voice Mail and appropriate language prompts are then used If an unsupported locale is used Standalone Voice Mail will attempt the best match using the first two characters of the locale The system locale can be overridden by setting a different user locale New in this release Avaya B5800 Branch Gateway Release 6 2 provides the following new features e Centralized management provided by Avaya Aura System Manager provides centr
189. ectivity to other B5800 Branch Gateway systems to centralized trunking and to centralized applications such as conferencing and Modular Messaging This term describes the scenario where each branch retains and uses its own PSTN trunks for incoming and outgoing external calls See Native extension This term is used to describe managing a B5800 Branch Gateway device using the local IP Office Manager application The flexibility of Avaya Aura Session Manager is such that both centralized and distributed trunking can be used For example routing all national and international calls via centralized trunking at the headquarters site while still allowing local calls via the branch sites 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 This term refers to a loss of network connectivity from the branch to the core data center This term refers to full network connectivity from the branch to the core data center October 2012 307 Tail End Hop Off Tail End Hop Off Part of mixed mode trunking this describes scenarios where certain calls at other branches or the headquarters site are routed to the PSTN of another branch 308 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Index A About adding B5800 Branch
190. ed for a voice compression channel If disabled or not supported at one end of the call the call is routed via the B5800 Branch Gateway However RTP relay support allows calls between devices using the same audio codec to not require a voice compression channel Re Invite Supported Default On When enabled Re Invite can be used during a session to change the characteristics of the session for example when the target of an incoming call or a transfer does not support the codec originally negotiated on the trunk Use Offerer s Preferred Default Off Normally for SIP calls the Codec 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 Codec Lockdown Default Off Supports RFC 3264 Section 10 2 when Re Invite Supported and Codec Lockdown are enabled In response to a SIP offer with a list of codecs supported some SIP user agents supply a SDP answer that also lists multiple codecs This means Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 149 Initial branch configuration Name Range or Default Description that the user agent may switch to any of those codecs during the session without further negotiation The system does not support multiple concurrent codecs for a session so loss of speech path will occur if the codec is changed during the
191. ee Licensing on page 16 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com 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 gt Regeneration from the Home page 4 Search License Activations to Regenerate oO ON OD O 10 You can search the activation records by the Company name license host Group name or ID using the Search Activation Records functionality Click Regenerate from the appropriate record Validate the Registration Detail and click Next Validate the items that will regenerate and click Next Accept the Avaya Legal Agreement Perform the following steps to send an activation notification e mail message a Inthe E mail to field enter e mail addresses for any additional activation notification recipients b Enter any comments or special instructions in the Comments field c Click Finish Click View Activation Record e The Overview tab displays a summary of the license activation information e The Ownership tab displays the registration
192. eeeeeeenee 197 TOQISLQMIAG Aiei er ETE 190 reNoOStNg masnica iiA ETA 195 related documents ccccccecceececseeeseeeeeeeeeeeeeeeeeeees 31 related FESOUICES iiias 31 Avaya Mentor videos ceseeeeeeeeeeeeeeeeeeeeees a1 remote software library cccccccseeeceeeeteeeteeees 98 99 remote software library for B5800 upgrades 98 Renumber extensions ccceesecceceseeeseeeeeeeneeeeeeees 213 Requirements cceeceeeeceeeeeececeeeeeeeeeeeeeaeeeaeeaaaeeea 47 48 Cable actes S innri a a 48 Cable clearance cccccccesssseeeceeeeeeeeeeaeaeeeeeeeeees 48 Enviromental snenia 47 SPACE porsia ees e E N E 48 Wall MOUNTING carecia a 47 reset DUTION 2 0 cece ccc ce esecececaneesceeeeaeenseeeeeeeasseseeeeenees 238 restoring the system configuration using System MAN AGEN vescaeced cacacccecedcceseepabatnueaececssenaseaid dante 218 October 2012 311 Restrictions when editing a B5800 Branch Gateway system configuration from System Manager 158 revision history cceeeceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeteeeteeeteeess 33 Routing B5800 Branch Gateway calls 00008 290 Roung POO sese 169 S Safety instructions cccccccssesssccceeeeeeesseesneeeeeeeess 263 Safety statements cccccccccesesseeeeesesessteeeeeesessaees 263 hy 2 ERE p ree meer eee ee errr rere cee e eer 199 201 AAMIIN ee 201 registrato rasionini ii aiaa 201 registration request form cc
193. eees 133 D Default codec selection ssssserisereserirrrerrrrrrrersrnne 143 deleting license files from the branches 0 95 Deliver activated license files to the branches i7 October 2012 309 Dial PATON scaks si dvesinsadacassanteuntAuses saectadetites caunsadcomnanse 176 Disabling the System Manager administration feature for a prane Nereuse e eaaa 159 discovering branches in the network and adding them to System Manager ecceeeeeeeeeeeeeeeeeeeeeaees 126 DOMAIN rroetan nendra a EE a d 166 DS estes eg oh ae a a a es 74 ROB usapan anna eon a a aan aaie E aE 74 DONG irane a E 74 DITE DOM airasia E aaa 230 Cable requirement ccccccceesceceesessteeeeseseeeees 230 RS292 rreken rinine aAa a a ENRE AAT EUNE 230 SOMIMOS E E E E essere 230 E editing a B5800 Branch Gateway from System Manager A EAEE E E ls nmacielasieseides 157 editing the B5800 Branch Gateway Endpoint profile for a USET a ct caiatteeue ianahe tagesauvanansateonsueasuceayet 187 editing the xml file containing the users 92 egress ports for B5800 Branch Gateway and SIP phones P P EE ET A A EA A 281 EMG CaUtONS assisia 266 Canadian Department of Communications 266 EMC Caution for China ccccccccesseeeeeeeeeeeees 266 Federal Communications Commission 266 Enabling authorization codes in Manager 300 Enabling branch SIP extension support 0
194. eeneeeseaeeeeesensseeeeanee 112 Installing IP Office Manager from the System Manager server to a PC eee eeeeeeeeenneeeeeeees 114 POTS EI e ee NERS UNS sta ccna Dace scar gros E yu nc dads Sasa E E san E TAEA E ENE 115 Installing the shared PLDS license file on the System Manager WebLM server 117 Using Manager to deliver license files to the branches cccecccesseecenneeeeeeeeseeteaeeeeeneeeeeeeeeneeneaeees 117 Using Embedded File Management to install a PLDS license eeeceesseeeeneeeseeeeeeeeeeeneeeeeeeees 118 Genersiing a cermlitate on System MENSESl iis ateriavetinavien N 119 Using he Mmalinstalatorn CRY fects genres eegagares teas A i 121 Additional features configured by the Initial Installation Utility 0 ccc ceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeees 123 Configuring the B5800 Branch Gateway for Certificates cecsesenneeseneeeseeeeeeeeeneneseeeeessaeeeneseeteneteaaee 123 About adding B5800 Branch Gateways to System Managet eccecseesseeeseeeeeeeeeneeeeeeseeeeneaeesaeesaneees 125 Discovering B5800 Branch Gateway S sciiicet aeaa eaaa 126 Bulk importing of OOO Siruna A yianid ecards 128 Adding the B5800 Branch Gateways to System Manager e seesssssrsesrieriierirserrsrrrsrirsrrrerrnerresrns 129 Enabling WebLM icensmg for the Drane Ii cesserit ei 130 CPE eE e e TEE s A E E A E E E E E deaceetnins 131 Uploading an auto attendant audio flessie is 132 Apo inig ME Sse Lem pines a a E EA AA E A 132 Glean aneno pani E
195. em It can report the available resources and components within the system and details of calls in progress Details of the number of alarms are recorded and the time and date of the most recent alarms Procedure 1 To start the System Status application choose one of the following e On the PC where System Status has been installed select Start gt Programs gt Avaya B5800 Branch Gateway Admin Suite gt System Status Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 105 Administration software suite e If Manager is also installed and is running select File gt Advanced gt System Status e 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 Inthe Control Unit IP Address drop down box select the appropriate address or enter the IP address of the control unit b Inthe Services Base TCP Port field enter the Services Base TCP Port setting that was set in the system s security settings The default is 50804 c Inthe Local IP Address field enter the appropriate local IP address If the PC has more than one IP address assigned to its network card or multiple network cards the address to use can be selected if necessary d Inthe User Name field enter a
196. em Manager See Generating a certificate on System Manager on page 119 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 123 Initial branch configuration 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 When you run the Initial Installation Utility the SCEP and security settings are automatically configured for the B5800 Branch Gateway See Using the Initial Installation Utility on page 121 for more information Procedure 1 Select File gt Advanced gt Security Settings Start Manager and connect to the B5800 Branch Gateway system 2 3 In the Select IP Office window click the check box for the appropriate system 4 5 Inthe Security Service User Login window enter a user name and password of Click OK an account that has security configuration access to the B5800 Branch Gateway system The defaults are security and securitypwd 6 In the Security Settings pane click System 7 Click the Certificates tab The certificate settings are set to the default values The Issued to field shows the default certificate that resides on the B5800 Branch Gateway The default value is the MAC address of the B5800 Branch Gateway system 8 In the Identity Certificate section click Delete to delete the default certificat
197. em Monitor when Avaya requests copies of System Monitor traces to resolve support issues SNMP MIBs Not an application as such the SNMP MIB files can be used by 3rd party SNMP applications to monitor the B5800 Branch Gateway system Supported country locales When a new or defaulted system s configuration is first opened in Manager the value set in the Locale field System gt System gt Locale should always be checked and changed if necessary The system s locale sets factors such as the default ringing patterns and caller display settings The locale also controls the language that a voicemail server will use for prompts The following table indicates locale settings supported for different functions Note that this does not necessarily indicate support availability or approval for B5800 Branch Gateway within that country Locale Language Telephony Phone Applications EVM and Display Manager Soft SVM Console Argentina Latin lt lt 4 4 v 4 Spanish Australia UK English v lt lt lt J Belgium Dutch 4 lt lt lt 4 Belgium French 4 lt lt i 4 Brazil Brazilian 4 4 lt 4 J 4 Canada Canadian y i 4 French Chile Latin PF e v 4 Spanish China Mandarin J i f Colombia Latin lt lt v J J Spanish Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 27 B5800 Branch Gateway overview
198. enting the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Setting the trunk prefixes 7 Select File gt Save 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 e 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 e On outgoing calls the short codes used to route the call to a trunk must remove the dialing prefix 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 157 2 In the left navigation pane click Line 3 For each line enter the prefix The location of the relevant setting varies for each trunk type e For analog trunks select the Line Settings tab and enter the prefix in the Prefix field e For T1 and T1 PRI trunks select the PRI 24 Line tab and enter the prefix in the Prefix field e For BRI E1 PRI and QSIG trunks select the PRI Line tab and enter the appropriate prefix in the following fields Prefix National
199. er 600MB for the full B5800 Branch Gateway Admin suite Display 800 x 600 256 Colors 1024 x 768 16 bit High Color Operating System Supported on Windows XP Pro Windows Vista Windows 7 Windows 2003 and Windows 2008 e 32 bit and 64 bit versions are supported e Vista support is only on Business Enterprise and Ultimate versions e Windows 7 support is only on Professional Enterprise and Ultimate versions 78 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Installer PC connection Installing the administration applications Procedure 1 a Aa O N Oo oOo N QO 10 12 13 14 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 Insert the B5800 Branch Gateway Administrator Applications DVD Select B5800 Branch Gateway Administration Suite Double click on setup exe Select the language you want to use for the installation process This does not affect the language used by Manager when running Click Next Select who should be able to run the Administration Suite applications Click Next If required select the destination to which the applications should be installed It is recommended that you accept the default destination Click Nex
200. er Services select Templates 2 On the Templates page click B5800 System Configuration 3 On the B5800 Branch Gateway System Configuration Templates page under Templates List select More Options gt Manage Audio 4 Onthe Manage Audio page click the Browse button to locate the wav file you want to upload 182 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration Comments infodev avaya com October 2012 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 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 183 Voicemail configuration 184 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Chapter 12 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
201. erasing the configuration on page 231 for more information 30 to 40 Red Erase all Erase configuration alarm log and core software See About 238 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration Comments infodev avaya com October 2012 DTE port maintenance Press Duration CPU LED Action Summary seconds erasing the operational firmware on page 235 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 The service name can be any text and is used to identify this particular service The account name and password entered for the service are presented to the remote end therefore must match the user name and password configured at Site B The Encrypted Password option can only be used if the remote end also supports CHAP Create a user Under the Dial In tab select Dial In On This User account is used to authenticate the connection from the Site B Note that if the service and user have the same name these two configuration forms are automatically linked and become an Intranet service The user password is displayed at the bottom of the Service tab as the Incoming Pass
202. ere 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 In some cases such as ground start trunks in addition to being a protective measure this is a functional requirement for the equipment to operate In other cases it may be a locale regulatory requirement and or a necessary protective step for example areas of high lightning risk For more information about grounding including the location of the ground points on the control unit and external expansion modules see Grounding on page 71 Wall and rack mounting The B5800 Branch Gateway control unit is designed to be freestanding When external expansion modules are used the control unit and expansion modules are intended to be stacked With optional mounting kits the system can be wall or rack mounted See Wall mounting on page 65 and Rack mounting on page 67 for more information Voice compression channels Calls to and from IP devices can require conversion to the audio codec format being used by the IP device For B5800 Branch Gateway systems this conversion is done by voice compression channels These support the common IP audio codecs G711 G723 and G729a For the B5800 Branch Gateway control uni
203. ere possible when an authorization code is required the user can enter it through their phone s display However this is not possible for all types of phones For example it is not possible with analog phones and Avaya XX01 or XX02 phones The users of these devices must enter the authorization code by using a short code set to the Set Authorization Code feature immediately before making the call When entry of an authorization code is triggered the user can enter any authorization code with which they are either directly associated or associated through their current user rights Note e If account code entry is setup for a particular number calls forwarded or transferred to that number will also trigger account code entry e On systems using line appearances to BRI trunk channels to make outgoing calls account code entry may not be triggered This can be resolved by adding a short code such as 9 XN Dial XN 0 adjusting the prefix and line group as necessary Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 301 Authorization codes Authorization code configuration settings e 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 e User Rights This field is used to select the user right with which the authorization code is associated The authorization code can then b
204. es B5800 Branch Gateway supports SNMP communication This communication can be e Polling Some SNMP applications called managers send out polling messages to the network They then record the responses of any SNMP enabled devices called agents Comments infodev avaya com October 2012 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 For example an B5800 Branch Gateway control unit s response includes the control unit type level of software routing table information up time etc e Traps When certain events occur a devices SNMP agent can send details of the event to the SNMP manager This is called an SNMP trap These appear in the event log of the SNMP manager Most SNMP managers can be configured to give additional alerts in response to particular traps Management Some SNMP agents support device management and configuration changes through the SNMP manager interface This is not supported by B5800 Branch Gateway B5800 Branch Gateway SNMP operation has been tested against Castle Rock SNMPc EE 5 1 6c and HP OpenView Network Node Manager 6 41 What information is available via
205. es on page 23 for more information Access to and from the rest of the Avaya Aura network is via the B5800 Branch Gateway system s Avaya Aura Session Manager link across the enterprise WAN This connection allows for VoIP connectivity to other B5800 Branch Gateway systems to centralized PSTN trunking and to centralized applications such as conferencing and Avaya Aura Messaging The centralization capability is based primarily on the infrastructure at the enterprise core The local B5800 Branch Gateway can be accessed as a SIP gateway connected to the core Avaya Aura Session Manager to provide access to local PSTN trunks and services when required Beginning in R6 2 B5800 Branch Gateway is supported in an Avaya Communication Server 1000 CS 1000 configuration B5800 Branch Gateway can be deployed as a new branch in an existing CS 1000 configuration or as a replacement for Business Communications Manager BCM as a branch office in a CS 1000 branch office model In these deployments B5800 Branch Gateway operates as a distributed branch Note Integration of B5800 Branch Gateway with Communication Server 1000 is provided in a separate document See Implementing the Avaya B5800 Branch Gateway for a Communication Server 1000 Configuration document number 03 604053 PSTN trunking configurations With the ability to administer call control at both the B5800 Branch Gateway and the Avaya Aura Session Manager there are many ways you can
206. etting the PC to be a DHCP client could be used this is not recommended for performing more advanced functions such as firmware upgrades 2 Connect the LAN cable from the PC LAN port to the LAN or LAN1 port on the control unit 3 Check that the orange LED lamp on the control unit LAN port is on The green LED may also be flickering This indicates traffic across the LAN connection 4 To test the connection before running Manager or the System Status application do the following a Select Start gt Run b Enter cmd c Inthe command window that appears enter ping 192 168 42 1 80 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com 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 Ifthe IP address settings of the Manager PC are displayed enter exit and check the cable connection Applying power to the system Procedure 1 With the power off on the control unit insert the B5800 Branch Gateway System SD card into the System SD slot on the rear of the control unit Ensure that you have the correct card The B5800 Branch Gateway System SD card is required for branch operation
207. eway for an Avaya Aura Configuration October 2012 313
208. f available RAM memory for transfer of bin files If the Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 217 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 Each module being upgraded will delete its existing core software restart and load the new software file that was transferred This process may take several minutes for each unit 8 Select the following options as appropriate e Click the check box for Backup System Files if before upgrading to the new software you want the current files in the System SD cards primary folder copied to a backup folder e Click the check box for Upload System Files if you want the full set of software files that Manager has to be copied to the primary folder on the System SD card In addition to control unit and module software this will include phone software files Following the reboot the phone will upgrade using those files if necessary e Click the check box for Restart IP Phones if you want all Avaya IP phones to be restarted following the upgrad
209. feature for the branch from System Manager 160 Disabling the System Manager administration feature for the branch from IP Office Manager 160 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 7 Enabling the Security Settings option for the Dranch ccscceceecceeeseeeecceeeeeeereeneesseeeeennerseeneeeeneees 161 Synchronizing B5800 Branch Gateway with System Managet 0 cccecceeeeeeeeceeeeeeeeseaeeseeseneeneaeeeaaes 162 Configuration changes performed through Manager that cannot be synced with System Manager 162 Chapter 10 Session Manager Configuration ececcccessseeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeees 165 Lewn E SF aom eee Reece Pentre Perel err tt re ocer ene tere er ener tester A ret errr rrerre rrr cetetenr erect re 166 Creed OCA ONS arena ER a ee 166 RUS NUNN APE N GS cede cases ses otras cece dasa E Se aS aE ORS 167 OPEATING SIF GHTINOS cnccinnannana ai ia 167 CEMO Sy MK Sa a Chnentn a haleaiad telat 168 Greakng ime rge Socr eE Rarer aA EEan EEr Aaa 169 Sie epo tilre pos e soe ies E E A E NT 169 Greating dial PARSING cainnean A aaa a 170 Chapter 11 Voicemail CONfiQUIraTION eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeneeeeeeeeeeeeeeeeeseeeennees 171 SPOUT ANN ORION sritan E E E 171 Abou the Pat and Page Tedi Ecetia aaaneN 172 Canig EmMPEdOed Vocem aeon RRRA 173 Contouring stnmdalne Voice MAW irssssdssini a ie a 174 Configuring B5800 Branch Gateway
210. files from System Manager to the external server This file transfer from PLDS to System Manager and then to the external server is a single operation for the administrator Note The HTTPS protocol is not supported for a B5800 Branch Gateway device to pull files from the external server Downloading the firmware files from PLDS to the B5800 elements through System Manager 1 Download the B5800 firmware from PLDS to the System Manager cache using the credentials provided in User Settings in System Manager 2 Upload the firmware to the external server from the System Manager cache using the FTP or SCP or SFTP protocol and the configuration information in the software library 3 After the file is on the external server B5800 elements use this file during upgrade using HTTP protocol Note Steps 1 and 2 happen simultaneously The file download to System Manager is transparent System requirements for the external server Component Requirement Recommendation Operating System Any standalone or virtualized Windows or Linux Distribution 98 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Remote Software Library for B5800 Branch Gateway upgrades B5800 Branch Gateway elements to download files from the external server Component Requirement Recommendation Hard Drive 20GB free space There should be enough free sp
211. folder on the System SD card This 254 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com 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 2 3 4 Start Manager Select File gt Embedded File Management From the Select IP Office window select the appropriate system The file contents of the memory cards are displayed Select File gt Upgrade Binaries All files in the primary folder on the Optional SC card except the configuration file config cfg and licenses file keys txt are copied to the primary folder on the System SD card This takes approximately 5 minutes When the process has been completed the B5800 Branch Gateway system is restarted Restoring software files from the Optional SD card using a system phone About this task Auser 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 gt Phone User gt System Admin 2 Enter your B5800 Branch Gateway user login code 3 4 Select Upgrade Binaries From the menu select Memory Card Al
212. for an Avaya Aura Configuration October 2012 281 Avaya port matrix for B5800 Branch Gateway and SIP phones 282 Dest Network En Default Remote Ext to Description Port App or Port Device Branch Protocol Dis State 7 514 UDP Yes Open Syslog No but Log files transmitted Syslog Server could be from IP phones to Cli server 8 5005 C RTCP Yes Open NMS Yes RTCP collector HP Openview AIM etc 9 5060 TCP SIP No Open Yes SIP signaling 10 49152 UDP Yes Open IP Phones Yes Dynamically allocated 53247 C RTP RTCP ports used during VoIP RTCP Collector calls for RTP and RTCP traffic The port range can be adjusted through the System gt Gatekeeper tab 11 50794 UDP No Open Manager Yes Event trace and TCP diagnostic outputs Monitor OPTIONAL E 1 25 TCP Yes Open Mail Server Depend SMTP S E 2 37 UDP Yes Closed Manager Yes TIME RFC868 Time Service supported by Manager and VMPro Requested by B5800 Branch Gateway This service is an option to NTP port 123 E 3 67 UDP Yes IP Clients No DHCP service to IP DHCP phones PCs and other Srv clients E 4 1720 TCP Yes Open H323 No Offering H 323 service H323 Server to IP phones E 5 5061 TCP Yes Closed Session Yes Encrypted SIP TLS Manager signaling For a description of the column headings see Table column heading definitions on page 283
213. for connections between the SIP entity and the Session Manager See Creating entity links on page 168 Create time ranges to control when different routing policies are used See Creating time ranges on page 169 Add a routing policy A routing policy consists of a selected SIP entity as its destination and a number of time ranges that define when the policy can be used See Creating routing policies on page 169 Add dial patterns Dial patterns are used to match digits received to a destination Each dial pattern has an associated routing policy that defines the target entity for matched calls and when the match should be used See Creating dial patterns on page 170 You must complete fields marked with an asterisk Fields not marked with an asterisk are optional For more information about administering Session Manager see Chapter 5 Managing Session Manager routing in Administering Avaya Aura Session Manager document number 03 603324 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 165 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 145 should match one of the entr
214. g PSTN Fallback on page 180 for more information Inthe Maximum Record Time field use the up and down arrows to set the maximum recording length in seconds for recorded announcement and auto attendant prompts Note You can set a number in this field only if you selected one of the two embedded voicemail options in the Use embedded for AA and Announcements drop down box Inthe VoiceMail Ports field use the up and down arrows to set the number of licensed voicemail ports Note You can set a number in this field only if you selected one of the two voicemail options in the Use embedded for AA and Announcements drop down box Modular Messaging over SIP requires SIP Trunk Session configuration and uses SIP Trunk Sessions licenses Accept the default setting on that is check box is checked for Enable Voicemail Instructions Using DTMF Click OK Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 179 Voicemail configuration 12 Select File gt Save Configuration The Send Configuration window appears and the Configuration Reboot Mode is set to Immediate Do not change the reboot mode 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 fol
215. g an Avaya Aura Session Manager line on page 145 This procedure includes the steps to configure TLS transport for the Session Manager line Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 111 Initial branch configuration Description Section 20 Add a second Session Manager line for redundancy See Avaya Aura Session Manager line redundancy on page 150 21 Set up outgoing call routing e See Setting up outgoing call routing on page 151 e For information on routing back to the branch for fallback alternate routes see Branch PSTN call routing examples on page 289 22 Configure the type of voicemail system the branch will use See Voicemail options on page 171 23 Enable branch SIP extension support See Enabling branch SIP extension support on page 154 Note Steps 24 through 31 are performed to configure Avaya Aura Session Manager 24 View a list of the SIP domains See Viewing the SIP domains on page 166 25 Create a location See Creating locations on page 166 26 Create a digit adaptation See Creating adaptations on page 167 27 Create a SIP entity See Creating SIP entities on page 167 28 Create an entity link See Creating entity links on page 168 29 Create a time range See Creating time ranges on page 169
216. g kits The control unit can be used free standing with external expansion modules stacked above it With optional rack mounting kits the control unit and external expansion modules can also be rack mounted Alternatively with an optional wall mounting kit the control unit can be wall mounted However the control unit cannot support any external expansion modules when wall mounted Surge protectors and barrier boxes Where the installation includes extensions in other buildings additional protective equipment is required This equipment may also be required in areas where the lightning risk is high e Phones B5800 Branch Gateway systems support a variety of Avaya digital and IP phones plus analog phones Application DVDs The B5800 Branch Gateway applications can be ordered ona number of DVDs In addition they can be downloaded from the B5800 Branch Gateway section of the Avaya support web site http support avaya com 22 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Supported telephones Supported telephones Telephone Native extensions local extensions operating in the distributed branch user model Analog Ca 1120E SIP 1140E SIP 1220 SIP 1230 SIP 1403 digital 1408 digital 1416 digital 1603 1603SW 1608 1616 1603SW 1608 1616 1 BM32 DSS 2402D 2410D 2420 QVPNESPS SES
217. g the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com About adding B5800 Branch Gateways to System Manager 8 Click Import About the xml file containing the B5800 Branch Gateway devices To use the bulk import method to add the B5800 Branch Gateways to System Manager you must first manually add each B5800 Branch Gateway device to an xml file The following sample shows the contents of an xml file for one B5800 Branch Gateway device lt xml version 1 0 gt lt RTSElements xmlns http www avaya com rts xmlns xsi http www w3 org 2001 XMLSchema instance gt lt ApplicationSystems gt lt ApplicationSystem name B5800_2 isTrusted false gt lt Host ipaddress 192 168 42 2 gt lt Host gt lt ApplicationSystemType name B5800 Branch Gateway version 0 gt lt ApplicationSystemType gt lt Attributes gt lt Attribute name Is B5800 for Linux value false gt lt Attribute gt lt Attribute name Service Login value SMGRB5800Admin gt lt Attribute gt lt Attribute name Service Password value SMGRB5800Admin gt lt Attribute gt lt Attribute name Device version value 6 2 gt lt Attribute gt lt Attributes gt lt ApplicationSystem gt lt ApplicationSystems gt lt RTSElements gt 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
218. ge 800 to 899 This allows us up to 100 branches yet keeps call routing simple Any dialing at a branch that being with an 8 can be assumed to be a call to a branch number and can be routed to the Avaya Aura Session Manager for routing to the correct branch e 3 digit extension numbers beginning with 2 3 digit extension numbers for all native extensions and hunt groups starting from 200 This is the default numbering used by B5800 Branch Gateway Dial plan example To describe a dial plan example we have created Acme Travel a travel agency with a growing number of branches Each branch follows the same pattern with extensions for a branch manager and a small team of travel consultants in a sales group Given the nature of the business branch users need to make national and international calls The company has taken advantage of a bulk call contracts from it headquarters site so wants such calls routed via the headquarters site wherever possible In addition the branch staff want to keep their branch phone numbers e 3 digit branch numbers beginning with 8 ie 800 to 899 e 3 digit native extension numbers beginning with 2 ie 200 to 299 e Dial 9 prefix for outgoing PSTN calls e National and international calls allowed but routed via the headquarters site s PSTN trunks e Where a national call matches a branch location it should be routed to the PSTN via that branch e Local calls allowed from each branch using its own PSTN
219. generating a certificate on System Manager 119 Getting inventory ssssssssssesssssssesssrrrresrreessssrnnerrennsent 100 ggeneral information 0 0 0 eeececeeeeeeeneeeeeeeentteeeeetenaaees 32 WED SITCS dsan aeiae aaaea saaa EEE EARE 32 Grounding control units eee eeeeeeeeeeeeeeeeeessteaeeees 44 H Hazard Symbols sisssscsscdeeeedivvsdeadecneesddevsieadeetaciiecsuetead 264 Homologation Statement ccccccccceessessnseeeeees 263 FOP O perenna EEEE 38 289 how ports are used ccc cceceecececeeeeeeeeeeeeeeeeeeteeeeeeees 275 HP OpenView ressos eronate h n REEE AKKE A 224 l ingress ports for B5800 Branch Gateway and SIP PHONES suretas nate aaas aaie aE a 279 initial branch configuration sssessesseeeenneenesenssessee 109 Initial Installation Utility seeeeeeeeeee eeaeee 421 Initial Installation Utility features automatically CONTQUICD csccctvencnsssancetencen hanced decknnadavdxeeeen pian 123 instalation sieri inaki an 53 Installation cccceeseeseceeeeeeeeees 54 55 59 65 67 71 79 admin applications sseeseeeeeeeeesseeernrnssssrrerenes 79 CANO PAIP A AE E A E E E 59 CFOUN ONIN Jere a Fal installer PC connection cccccceeeeseeeeeeeeeeeeeeaes 79 rack MOUNTING ssis aini aaia iaaa 67 ROOMS PAEAN PEE AAE E E EA 54 UII DECKING eea aatedvteeesteceievesg 55 wall MOUNTING icssssssccausantiaaseacccecepansaxtves teareRaraeecdesss 65 installation checklist
220. ger line should be infrequent and temporary the loss of some services may be tolerable until the Avaya Aura Session Manager line issue is resolved However even if that is the case it may be recommended to configure 294 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com 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 292 for more information e Provide PSTN trunk fallback within the branch configuration See Configuring PSTN trunk fallback on page 295 Note however that PSTN fallback will also occur when the number of external calls exceeds the available SIP trunk licenses Note If you want to have long distance routing on local trunks be sure that the appropriate trunks have been ordered from the local provider Do not create a route for international phone calls if you do not have that service Configuring PSTN trunk fallback About this task Use this procedure to provide PSTN trunk fallback with the branch configuration Procedure Start Manager and connect to the B5800 Branch Gateway system In the left navigation pane click ARS Click the New icon and select ARS Enter a Route Name for example PSTN To add a short code click the Add button A short code is required that will send the national calls to the branch s own PST
221. gits b To require the caller to dial the user s voicemail mail box to send the required DTMF digits do not select this check box that is the check box is not checked The capability to turn this feature off is provided because there may be networks where the DTMF digits may not correctly reach the messaging system due to a provider s network characteristics When this feature is turned off the DTMF 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 Note You can set a number in this field only if you selected one of the two voicemail options in the Use embedded for AA and Announcements drop down box Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 177 Voicemail configuration 10 In the VoiceMail Ports field use the up and down arrows to set the number of licensed voicemail ports Note You can set a number in this field only if you selected one of the two voicemail options in the Use embedded for AA and Announcements drop down box Avaya Aura Messaging requires SIP Trunk Session configuration and uses SIP Trunk Sessions licenses 11 Accept the default setting on that is check box is checked for Enable Voicem
222. guration sub tab in the SNMP Agent section ensure the SNMP Click the System Events tab Enabled check box is selected Inthe Community read only field enter the SNMP community name to which the system belongs This community name must match that used by the SNMP manager application when sending requests to the device The community public is frequently used to establish communication and then changed at both the SNMP agent and manager ends for security 6 In the SNMP Port field accept the default 7 Inthe Device ID field enter the alarm ID or PID of the registered system Note This enables product alarming back to Avaya via the Secure Access Link SAL The unique alarm ID is included in the var bind of all SNMP trap notifications sent by the system The alarm ID or PID is parsed out of the alarm and used for automatic case creation by matching the registered system s customer record with the alarm event Inthe Contact field enter contact information as appropriate Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 229 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 Inthe IP Address field enter the IP address of the PC running the SNMP manager application c Inthe Port field enter th
223. hat every item of supported equipment has its own supply socket The web site http www avayaups com provides a calculator into which you can enter the equipment you want supported on a UPS It will then display various UPS options The site uses VA values for typical B5800 Branch Gateway systems However if more specific values are required for a particular system the table below can be used to enter values Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 41 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 WANS 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 The B5800 Branch Gateway system is designed primarily for use within an RJ45 structured cabling system using CAT3 unshielded twisted pair UTP cabling and RJ45 sockets A structured cabling system is one where cables are run from a central RJ45 patch panel in the communications data room to individual RJ45 sockets at user locations All wires in each cable between the patch panel and the desk socket are connected straight through This arrangement allows devices connected at t
224. he Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 261 SD card management 4 At the bottom of the window click Startup Starting up a card using a system phone About this task Auser 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 gt Phone User gt System Admin 2 Enter your B5800 Branch Gateway user login code 3 From the menu select Memory Card 4 Choose one of the following e Select System for the System SD card e Select Option for the Optional SD card 5 Select Startup 262 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Chapter 17 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 CE The CE mark affixed to this equipment means that the module complies with the 1999 5 EC R amp TTE 89 336 EEC EMC and 72 23EEC LVD Directives e The Declarations of Conformity DoC for the B5800 Branch Gateway p
225. he community to which the device belongs for write access In the Service Password field enter the service password The default service password is the same as the Service Login SMGRB5800Admin In the Confirm Service Password field enter the service password again Click Commit 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 2 3 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 157 In the left navigation pane click PLDS license Click the check box for Enable WebLM to select this option 130 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Creating a system template Inthe Domain Name URL field enter the IP address or fully qualified domain name of the System Manager WebLM server or other WebLM server that is being used In the URN field enter the name of the WebLM server The default is WebLM LicenseServer Inthe Port Number field
226. he following error configuration options Abort on first error e Continue processing other records 5 Select Complete as the import type 6 Select one of the following import options e To skip users in the import file that match the existing user records in the database click Skip To update and merge the user attributes data from the imported file to the existing data click Merge e To replace the users in the database with the new users from the imported file click Replace Use this option to import new users and retain the existing users To delete the user records in the database that match the records in the imported file click Delete 7 To run the job in the Job Schedule section select one of the following options e To import the users immediately click Run immediately e To import the users at a specified time click Schedule later and set the date and time 8 Click Import Note The operations Communication Manager Synchronization and Bulk Import of users must not overlap in time If Bulk Import of users is in progress and Communication Manager Synchronization is started the current records under process fail After the synchronization is complete the remaining bulk import records process successfully You must reimport the records that fail during synchronization About migrating individual PLDS license files to a WebLM server After you upgrade the B5800 Branch Gateway R6 1 system to R6 2
227. he patch panel to be swapped to match the type of device that needs to be connected at the user socket For example making one user socket a phone port and another user socket a computer LAN port without requiring any rewiring of the cables between the patch panel and the user location Patch Panel 869899898 Line Provider s Building Structured Network Termination Cabling e Traditional IDC punchdown wiring installations Where necessary the far end RJ45 plug can be stripped from B5800 Branch Gateway cables and wired into traditional wiring 42 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com 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 RJ11 to RJ11 cables RJ11 plugs can be inserted into RJ45 sockets and in many case the connection will work However this is not recommended or supported as the connection lock is not truly positive and may become disconnected An RJ45 to RJ11 cable is available for these connections Standard B
228. he port numbers identify which application each data mini stream belongs Every IP device has incoming Ingress and outgoing Egress data streams Ports are used in TCP and UDP to name the ends of logical connections which carry data flows TCP and UDP streams have an IP address and port number for both source and destination IP devices The pairing of an IP address and a port number is called a socket discussed later Therefore each data stream is uniquely identified with two sockets Source and destination sockets must be known by the source before a data stream can be sent to the destination Some destination ports are open to receive data streams and are called listening ports Listening ports actively wait for a source client to make contact to a destination server using a specific port that has a known protocol associate with that port number HTTPS as an example is assigned port number 443 When a destination IP device is contacted by a source device using port 443 the destination uses the HTTPS protocol for that data stream conversation Port type ranges Port numbers are divided into the following three ranges Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 275 Avaya port matrix for B5800 Branch Gateway and SIP phones e Well known ports are those numbered from 0 through 1023 e Registered ports are those numbered from 1024 through 49151 e Dynamic ports are those numbe
229. hen click the Yes button Note After you select this check box for the first time this warning page will no longer appear when you launch IP Office Manager On the Request Authentication page click the OK button Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 133 Initial branch configuration Note You do not need to provide a certificate on this page This page will always appear when you launch IP Office Manager 11 Complete the appropriate fields The only fields you can edit in the user template are e Locale e Priority e System Phone Rights e Profile All other fields in the user template are non editable because they are not applicable to multiple users 12 When finished select File gt Save Template and Exit The template is saved in System Manager and listed in the Template List table 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 Important Failure to do this will cause problems with outgoing calls Procedure 1 From the System Manager co
230. hen you select System gt System B5800 Branch Gateway licenses The B5800 Branch Gateway licenses are described below Avaya Branch Gateway System Software license This license is required for operation of the B5800 Branch Gateway system This license does not include any implicit entitlements and therefore is not sufficient by itself for branch operation without additional Station and or SIP Trunk Session licences One Avaya Branch Gateway System Software license is required Native Station licenses All users on a B5800 Branch Gateway system must be licensed by the addition of Native Station licenses Native Station licenses are required for all configured users with analog digital H 323 or DECT extensions for users without any extension and for all users with SIP extensions set as native or local that is extensions operating in the distributed branch user model A Warning Unlicensed extensions will display No License Available but will be able to make emergency calls i e calls that match B5800 Branch Gateway Dial Emergency short codes Embedded Messaging Ports license This license is required if you are using the B5800 Branch Gateway voicemail options Embedded Voicemail or Standalone Voice Mail The Embedded Messaging Ports license is also used to control the number of ports on systems where Avaya Aura Messaging or Modular Messaging over SIP is configured as the central voicemail system and the local Embedded Voicemai
231. i ciel E A E nett A trees T A EE S E ny teri A nt rr ertr tree T rent 33 Ghapter 2 PLANNING rsa a aaa iaaa raii 35 aE E o E A E E E E E E E A E A E T 35 Dial plan consideran Sessa E E OE aane 36 Eo Ua BAND E AT AE EAA AITA AA AAA A AA AA 36 eoma C ON a O a aa E 37 Branch PSTN gall routing CO Ms sinense i EN EAEEREN EA 38 Network assessment tor VoIP roguirem MiS sasisssniiisssididrinsisiisninoii aa 39 Chapter 3 Installation requirements srccccccetccssesessecsccccccscssisasasanssssanenntenssndnananananenanciacnunaaua 41 Power sitan DOCKUM UPE ence eran Creare eere tree eer aia iret mere a a ar eee tre 41 Ple a EE sce senaueasdacdauuedescuidaaneuciciapancesaietesaede E E EE E E E A 42 E eNe Ti o AARE A E A E E A E E E A E E E E E E AE ETE 44 Wak and tack iON sia E E ee 44 vore compes On eha E aia a aiia 44 Emergeney and power alwe POS conii eea Aaaa aa AAO Aa raS 46 EnV rOnMo mal Fe CMTS INNS e E EE RRENENE 47 eere dus IE e a E E A E E 48 Contate 48 EAOa a o aaa N 49 Wall mouniing BRACE requirem S renin niaaa aes taees 50 gee gsr e deel o E a E A E E E 50 Chapter 4 Hardware and software installation ccsccceeeeeeeeeeeeeeeeeeeeeeeeeeeseeeeseeeeess 53 ere e EE E A E S E NA EA NA E E A ET 53 Tools and eguipment regte d sirenerne S yaaa ae aA Kaa aar en AA 54 Unpacking eoun a a iaia AE 55 EDE o Eio a e E E A E E A E E 56 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 5 Upgrading Me e
232. icenses 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 Searching for license entitlements About this task Use this functionality to search for an entitlement by using any one or all of the following search criteria e Company name e Group name e Group ID e License activation code In addition to these search criteria PLDS also provides other additional advanced search criteria for searching license entitlements Note Avaya associate or Avaya Partners can only search license entitlements by company name Procedure 1 Type http plds avaya com in your Web browser to access the Avaya PLDS Web site 2 Enter your Login ID and password to log on to the PLDS Web site 3 Click Assets gt View Entitlements The system displays Search Entitlements page 4 To search license entitlements by company name enter the company name in the Company field To see a complete list of companies before searching for their corresponding entitlements do the following a Click the magnifying glass icon Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 193 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
233. ies that is listed on the Domain Management page 1 2 On the System Manager console under Elements click Routing In the left navigation pane click Domains The SIP domains are listed on the Domain Management page Creating locations Locations are used to identify logical and or physical locations where SIP entities reside The location entries in Session Manager allow bandwidth management and call control to be applied for connections to and from those locations Typically locations are added for each B5800 Branch Gateway branch site 1 On the System Manager console under Elements click Routing 2 In the left navigation pane click Locations 3 On the Location page click New to add a new location 4 On the Location Details page in the Name field enter a name to identify the location 5 In the Notes field enter notes about the location as appropriate 6 In the Managed Bandwidth Units field accept the default setting 7 Inthe Total Bandwidth field accept the default setting blank 8 In the Multimedia Bandwidth field accept the default setting blank 9 For the Audio Calls Can Take Multimedia Bandwidth check box accept the default setting checked 10 In the Per Call Bandwidth Parameters section accept the default settings 11 In the Alarm Threshold section accept the default settings 12 In the Location Pattern section click Add to add a location pattern 13 In the IP Address Pattern field e
234. il notification from PLDS This e mail notification includes a license activation code LAC Using the LAC you can quickly find and activate the newly purchased license entitlements in PLDS You can then download the license file Important You must provide the WebLM host ID to activate the license file in PLDS The primary WebLM host ID is the MAC address of a physical network interface card NIC on the server If you are not using WebLM to manage the licenses you must provide the host ID of each B5800 Branch Gateway in your network to generate a license for each branch The host ID is the Feature Key Serial Number printed on the B5800 Branch Gateway System SD card For more information see Licensing on page 16 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 189 Managing license files with PLDS Examples of license management tasks that you can perform in PLDS include e Adding more license entitlements to an existing activation e Upgrading a license file to a new major release e Moving license entitlement activations between license hosts e 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 The PLDS Web site redirects you to the Avaya single sign on SSO Web page 2 Log in to SSO with your SSO ID and password The PLDS registration page is displayed
235. ill 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 You cannot perform this task from Manager that is accessed from System Manager If the B5800 Branch Gateway is centrally managed by System Manager you must disable the System Manager administration feature for the branch by disabling Under SMGR Administration in Security Settings before you perform this task For more information see Disabling the System Manager administration feature for the branch in Implementing the B5800 Branch Gateway for an Avaya Aura Configuration document number 18 603853 Procedure _ Open IP Office Manager and receive the B5800 Branch Gateway configuration 2 Select File gt Advanced gt Memory Card Command gt Startup 3 In the Select IP Office window click the check box for the appropriate system 4 Click OK Starting up a memory card using System Status About this task Use this task to restart a memory card without removing and reinserting it Procedure 1 Open System Status and access the status output 2 In the navigation pane select System gt Memory Cards 3 Click System SD or Optional SD Implementing t
236. information e The License Key tab displays the license files resulting from the license activation In general a single license file will be generated for each application From the License Key tab you can view and download the license 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 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 197 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 198 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Chapter 14 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 Administrat
237. ing cceeee eee eeeeeeeeeeettetteeaeeeeeees 169 TPAIMING eenn naa a a aE EAA 303 Training COUISES cecceeceecceeceeceeeeeeeeeeeeeeeteeeeeeeeeees Bt TUK Pallb ACK asirni nann n 294 Trunk Interface Modules ccccseseeeceesseeeeeeaeeeees 265 UStd a A A N 168 TYDE piripa eE EEE EE EEEE 167 types of activation PrOCeSSs cceeeeeetteeeeeeetees 190 U Upgrade installation sssini 89 upgrade installation Checklist cceeeceeeeeeeeeeeees 89 upgrading the administration applications 90 upgrading the B5800 Branch Gateway device 103 Uploading an auto attendant audio file 132 182 using Embedded File Management to install a PLDS CENSO nienie aaaea Ea EKRE aA 118 V VIJES paueger eaaa aa aa a 31 Avaya Mentor 20 0 ccecccceceeceeeeeeeeeeeeeeeeteeeeeeneeeaeea 31 Voice compression channels 0e eeseeeeeeees 44 Voicemail considerations ccceeseseceeceeeeseeeeeeeeaeaees 37 Voicemail operation cce cece ee ee ee eeeeeeeeeeeeeeeeeeees bead Voicemail Support Options ceeeeeeeeeeetteeeeeeeeteeees 14 VoIP tab field descriptions eecceeeeetetceeeeeeeeees 147 WwW Wall mounting control units 0 ceeeeeeeeeeeeeeeeeeeeeeees 44 Wall mountingrequirement s es 47 WAN eesi hea deceuatiecunsaeeediaiinindssaqaeativagledibcacedesiviaates 239 October 2012 Implementing the Avaya B5800 Branch Gat
238. ing a staged Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 55 Hardware and software installation installation the original packaging will also assist when repacking equipment to be moved to the final install site 4 Ensure that anti static protection measures areobserved Ensure that anti static protection measures are observed at all times when handling equipment with exposed electrical circuit boards 5 Check all parts Visually inspect each item and check that all the necessary documentation and accessory items have been included Report any errors or omissions to the dealer who supplied the equipment 6 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 When first powered up the control unit loads and installs the necessary firmware from the B5800 Branch Gateway System SD card that has been installed in the control unit A default configuration is then created that matches the cards installed in the control unit and external expansion modules attached You can perform the following tasks prior to installing the B5800 Branch Gateway System SD card in order to pre configure the system See Upgrade the Card Firmware on page 56 e See Creating a configuration file on page 57 e See Adding a configuration file on
239. ing on page 71 external expansion modules to a functional ground 10 Install the B5800 Branch Gateway See Installing the administration administration applications on the applications on page 79 installer PC 11 Connect the PC to the control See Installer PC connection on page 79 unit 12 Apply power to the system See Applying power to the system on page 81 13 Use the initial installation utility to See Using the Initial Installation Utility on configure a default configuration page 121 and security settings 15 Connect the control unit to the See Connecting the control unit to the network network on page 86 18 Connect the phones See Connecting phones on page 87 Tools and equipment required Following is a general summary of the tools required Additional tools and equipment are required for wall and or rack mounting and to fashion ground cable connections suitable to local requirements Tools required 5mm Flat blade screwdriver Crosshead screwdriver 54 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Unpacking equipment Anti static wrist strap and ground point RJ45 RJ45 ethernet LAN cable M4 cross head screwdriver Tools suitable for crimping a cable spade If wall mounting drills and tools for wall mounting fixtures Additional parts required I
240. ing resources are managed by the conference devices chip which is on the B5800 Branch Gateway TDM bus Therefore a voice compression channel is required for each IP device involved in a conference This includes services that use conference resources such as call listen intrusion call recording and silent monitoring Page calls to IP dDevice B5800 Branch Gateway only uses G729a for page calls therefore only requiring one channel but also only supporting pages to G729a capable devices Voicemail services and IP Calls to the B5800 Branch Gateway voicemail servers are devices treated as data calls from the TDM bus Therefore calls from an IP device to voicemail require a voice compression channel T38 fax calls In order to use T38 fax connection B5800 Branch Gateway performs fax tone detection if the analog extension connected to the fax machine is set as Standard telephone If the fax machine does not include an attached handset that is used to make receive voice calls then the Equipment Classification of an analog extension connected to the fax machine can be set to Fax Machine which will result in T38 fax connection without fax tone detection and respective signaling renegotiation Additionally a new short code feature Dial Fax is available Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 45 Installation requirements Measuring channel usage The IP Office S
241. ing the port numbers used by Avaya products so effective firewall policies can be created without disrupting business communications or opening unnecessary access into the network Knowing that the source column in the port usage tables provided below is the socket initiator is key in building some types of firewall policies Some firewalls can be configured to automatically create a return path through the firewall if the initiating source is allowed through This option removes the need to enter two firewall rules one for each stream direction but can also raise security concerns Another feature of some firewalls is to create an umbrella policy that allows access for many independent data flows using a common higher layer attribute Finally many firewall policies can be avoided by placing endpoints and the servers that serve those endpoints in the same firewall zone TFTP port usage IP Office upgrade wizard and VM Pro all use TFTP for commands and data transfer B5800 Branch Gateway implements a version of the TFTP Transfer Identifier mechanism TID defined by RFC 1350 The general mechanism is each has a TFTP listener on port 69 any received command READ request is responded to with a TFTP response WRITE request to port 69 Any subsequent data transfer uses the source ports from both request and response IP Office Manager upgrade wizard B5800 Branch Gateway TFTP Read src port 2421 dst port 69 gt lt TFTP
242. ion SELV Analog telephone ports Telephone Extension ports TNV2 Digital telephone ports Telephone Extension ports SELV WAN port WAN connection NET SELV LAN ports 10 100 BaseT attachment to SELV LAN Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 265 Safety and regulatory information Port Name Port Description Port Classification Expansion ports Expansion Module SELV connector Audio port Connector for Music on SELV Hold External control port Connector for Controlling SELV Ancillary circuits DC input port Connector for DC input SELV power Interconnection circuits shall be selected to provide continued conformance with the requirements of EN 609050 1992 A3 1995 clause 2 3 for SELV circuits and with the requirements of clause 6 for TNV circuits after connections between equipment EMC cautions 889 336 EEC EMC Directive CISPR 22 1993 including A1 A2 AS NZ 3548 1995 ROW A Warning This is a class A product In a domestic environment this product may cause radio interference in which case the user may be required to take adequate measures Federal communications commission FCC This equipment has been tested and found to comply with the limits for a Class A digital device pursuant to Part 15 of the FCC Rules These limits are designed to provide reasonable protection against harmful interference when the equipment is o
243. ion of terminal equipment is controlled by qualified installation personnel e To conform with the Receive Objective Loudness Rating at distances greater than 2 7km from the central office on analog trunks a receive gain of 1 5dB must be set Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 273 Safety and regulatory information 274 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com 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 Consider your desktop PC Multiple applications may be simultaneously receiving information In this example email may use destination TCP port 25 a browser may use destination TCP port 80 and a telnet session may use destination TCP port 23 These logical ports allow the PC to de multiplex a single incoming serial data packet stream into three mini streams inside the PC Furthermore each of the mini streams is directed to the correct high level application because t
244. ion software suite on page 77 for a description of these applications SAL Gateway R2 1 or higher software must be installed on a customer provided server in the enterprise at a central location that allows for network connectivity to each deployed branch The SAL Gateway manages the B5800 Branch Gateways in multiple branches relaying alarms from the B5800 Branch Gateways back to Avaya and proxying connection requests for support engineers The SAL solution is fully customer controlled through the deployment and use of the optional SAL policy server Note System Platform s Virtual SAL Gateway VSALGW is not supported in managing each individual branch The VSALGW is only officially supported by Avaya in management of system platform on board devices such as System Platform Session Manager and System Manager Each B5800 Branch Gateway branch is considered an off board device Use of SAL to access the B5800 Branch Gateway administration tools and System Manager You are able to access the B5800 Branch Gateway administration tools and Avaya Aura System Manager through SAL e Manager Manager is an administration tool used to configure and upgrade the B5800 Branch Gateway system You can use Manager to administer each branch individually You are able to use SAL to access the Manager application for local or remote configuration management of the B5800 Branch Gateway system Note For B5800 Branch Gateway upgrades
245. ipment for repair or warranty information please contact the Technical Service Center at 1 800 242 2121 or contact your local Avaya representative If the equipment is causing harm to the telephone network the telephone company may request that you disconnect the equipment until the problem is resolved A plug and jack used to connect this equipment to the premises wiring and telephone network must comply with the applicable FCC Part 68 rules and requirements adopted by the ACTA Connection to party line service is subject to state tariffs Contact the state public utility commission public service commission or corporation commission for information Equipment with Direct Inward Dialing DID Allowing this equipment to be operated in such a manner as to not provide proper answer supervision is a violation of Part 68 of the FCC s rules Proper answer supervision is when e This equipment returns answer supervision to the public switched telephone network PSTN when DID calls are Answered by the called station Answered by the attendant Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 271 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 e This equipment returns answer supervision signals on all DID calls forwarded back to the PSTN Permissible exceptions are
246. is used to transfer the software to the System SD card Method Description Location Software Embedded Files Voicemail Upgrading Using Manager the contents Local or remotely using of the card are compared to Remote Manager on the files that Manager has page 257 available and are upgraded if necessary System SD Card In this method the System Local 4 Upgrade on SD card is shut down and page 257 removed from the control unit The card s contents are upgraded using Manager Upgrade from This method uses an SD card Local 4 256 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration Comments infodev avaya com October 2012 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 gt 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 gt Backup System Files The contents of the primary folder on the System SD card are copied to the backup folder This process takes approximately 6 minutes 5 Select File gt Upload System Files Manager uploads the system files to the primary folder on the System SD card This includes B5800 Branch Gateway softwa
247. istration feature for the branch from System Manager on page 160 Synchronizing B5800 Branch Gateway with System Manager About this task Some configuration changes cannot be synced with System Manager See Restrictions when editing a B5800 Branch Gateway system configuration from System Manager on page 158 for more information Procedure 1 On the System Manager console under Elements click Inventory 2 In the left navigation pane click Synchronization gt B5800 Branch Gateway 3 Click the check box for the B5800 Branch Gateway system whose configuration you want to sync with System Manager 4 Do one of the following e Click System Configuration to sync only system configuration data with System Manager e Click User to sync only user data with System Manager e Click System Configuration and Users to sync system configuration and user data with System Manager 5 Do one of the following a Click Now to run the synchronization job now b Click Schedule to run the synchronization job at a scheduled date and time Configuration changes performed through Manager that cannot be synced with System Manager You are able to disable System Manager administration for a B5800 Branch Gateway and configure the B5800 Branch Gateway device locally through IP Office Manager To do this you 162 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com
248. it 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 157 2 In the left navigation pane click System 3 Click the System tab 4 Set the following fields as appropriate e Branch Prefix optional e Local Number Length optional e Proactive e Reactive These 4 fields are the key settings for B5800 Branch Gateway operation See System tab field descriptions on page 141 for more information 5 Click OK 6 Select File gt Save Configuration The Send Configuration window appears and the Configuration Reboot Mode is set to Immediate Do not change the reboot mode System tab field descriptions Name Range or Default Description Branch Prefix Range 0 to 999999999 This number is used to identify the B5800 Branch Gateway system within the Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 141 Initial branch configuration 142 Name Range or Default Description Avaya Aura network The branch prefix of each B5800 Branch Gateway system must be unique and must not overlap For example 85 861 and 862 are okay but 86 and 861 overlap 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
249. ite http Avww avaya learning com The site can be used to check course availability and to book courses It also includes on line courses and on line course assessments The site requires users to setup a user name and password in order to track their personal training record For a list of recommended courses available for the B5800 Branch Gateway see Recommended courses for Avaya B5800 Branch Gateway training on page 303 Web sites Information to support B5800 Branch Gateway can be found on a number of web sites e Avaya http www avaya com The official web site for Avaya The front page also provides access to individual Avaya web sites for different countries e Avaya Enterprise Portal http oartner 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 e Avaya Support http support avaya com Contains documentation and other support materials for Avaya products e Avaya University http www avaya learning com This site provides access to the full range of Avaya training courses That includes both on line courses course assessments and access to details of classroom based courses The site requires users to register in order to provide the user with access to details of their
250. ity Mode Changing the security settings Procedure 1 Start Manager and connect to the B5800 Branch Gateway system 2 Select File gt Advanced gt Security Settings 3 In the Select IP Office window click the check box for the appropriate system 4 5 In the Security Service User Login window enter a user name and password of an Click OK account that has security configuration access to the B5800 Branch Gateway system The defaults are security and securitypwd 6 In the left navigation pane click System 7 Click the Unsecured Interfaces tab The password in the System Password field is used by Manager for remote software upgrade of the B5800 Branch Gateway system The default password is password Next to the System Password field click the Change button Enter a new password and click OK 10 11 Click OK Click on Service Users 204 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com 12 13 14 15 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 For each of these service users a Click on the service user name b Inthe Service User Details tab click on Change and enter a new password c Click OK d
251. k of the barrier box 4 The rack mounting strip has threaded M4 earthing pillars Connect the other end of the barrier box ground wire using M4 washers and nuts to the earthing pillar on that side of the rack mounting strip 76 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com 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 e Earth lead from the barrier box to the phone module e Internal wires e g wires going directly to the phone module e Wires from external telephone going directly to the barrier boxes 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 e 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 Manager is also used to upgrade the system software files e System
252. l in this model one WebLM server is used This model is used for enterprises where the System Manager WebLM server is able to manage all B5800 Branch Gateway licenses required for the enterprise e WebLM enterprise licensing model in this model multiple WebLM servers are used This model is used for enterprises where the licenses required for all branches in the enterprise exceed the System Manager WebLM server capacity One WebLM server acts as a master WebLM server and hosts the license file from PLDS The other WebLM servers s act as a local WebLM server and host allocation license files from the master WebLM server Each B5800 Branch Gateway must be configured with the IP address of one of the WebLM servers Note The expected System Manager WebLM server capacity is about 400 branches on a loaded System Manager The capacity would be higher on a lightly loaded System Manager The expected WebLM capacity on a standalone Linux server is about 1 100 branches Large deployments that exceed the System Manager WebLM capacity require additional standalone WebLM server s and configuration of the WebLM servers as master and local in the WebLM enterprise licensing model Note The correct expiration time of licenses for a B5800 Branch Gateway that uses a local WebLM server is provided on the corresponding master WebLM server The local WebLM server shows the licenses as having an expiration time of 30 days or less However periodical
253. l Time Profile Out of Hours Route lt None gt v Code Telephone Number Feature Line Group Id 11 911 Dial Emergency 0 Sane 911 911 Dial Emergency o SETI ON oN Dial 3K1 99999 Edit 1N 1N Dial 3K1 99999 xN N Dial 3K1 0 RARKARKAAAN N Dial 3K1 0 Alternate Route Priority Level Alternate Route Wait Time 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 This works as follows e The Alternate Route Priority Level controls which users are able to use the alternate route immediately ie those user s whose priority is equal or higher than this setting The default priority for users is 5 296 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com 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 e 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 gt S
254. l files in the primary folder on the Optional SC card except the configuration file config cfg and licenses file keys txt are copied to the primary folder on the System SD card This takes approximately 5 minutes When the process has been completed the B5800 Branch Gateway system is restarted Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 255 SD card management System upgrade using the System SD card In addition to using the upgrade wizard see Using the upgrade wizard on page 217 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 Note e Check the latest B5800 Branch Gateway Technical Bulletin for the B5800 Branch Gateway software release before proceeding any further It may contain information relating to changes that occurred after this document was completed Bulletins are available from http support avaya com e Some upgrades may require entry of upgrade licenses A Warning This procedure will cause the system to be restarted disconnecting any current calls and services in progress Optional SD Card on page 258 loaded with the required version of B5800 Branch Gateway software The card is inserted into the control unit and then Manager System Status or a system phone
255. l phone Local phone A gt B5800 Branch Gateway local phone B 2 Local phone to PSTN using local trunking Local phone gt B5800 Branch Gateway B5800 Branch Gateway trunk e g FXO ISDN SP SIP Trunk gt PSTN 3 Local phone to PSTN using centralized trunking Local phone gt B5800 Branch Gateway Session Manager gt central gateway SBC PSTN 4 Local phone to headquarters or other enterprise site Local phone B5800 Branch Gateway gt Session Manager gt target phone s controller target phone Calls to local extensions i e deployed in distributed branch user model 1 From PSTN to local extension via IP Office auto attendant branch auto attendant LDN is associated with local B5800 Branch Gateway trunk PSTN gt B5800 Branch Gateway trunk e g FXO ISDN SP SIP trunk gt B5800 Branch Gateway auto attendant caller enters extension number gt local phone 2 From PSTN direct to Local phone s DID LDN is associated with local B5800 Branch Gateway trunk PSTN gt B5800 Branch Gateway trunk e g FXO ISDN SP SIP trunk gt B5800 Branch Gateway local phone 3 From headquarters or other enterprise site to local phone s enterprise number Originating phone gt originating phone s controller gt Session Manager gt B5800 Branch Gateway local phone 4 From headquarters or other enterprise site to local extension via IP Office auto attendant Originating phone gt originating phone s cont
256. l provides auto attendant operation For Embedded Voicemail up to 6 ports can be licensed For Standalone Voice Mail up to 40 ports can be licensed At least one Embedded Messaging Port license must be purchased to enable this service SIP Trunk Sessions license This license refers to the total number of concurrent sessions allowed on all SIP connections to the B5800 Branch Gateway The maximum number of SIP trunk sessions is 128 SIP trunks provide the SIP connections between Avaya Aura Session Manager and B5800 Branch Gateway SIP trunk sessions are used for connectivity to the telephone company that provides the SIP trunks 18 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com License modes Additional channels licenses The PRI Universal PRI U trunk card can be used in the B5800 Branch Gateway system The PRI U ports can be configured to support E1 E1R2 or T1 line types Each port supports 8 B channels which do not require a license Additional B channels beyond these 8 require a license 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 For trunk types on which channels can be set as in service the licenses are consumed by those cha
257. lick 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 configuratio n from System Manager on page 157 2 In the left navigation pane click ARS 292 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration Comments infodev avaya com October 2012 Branch PSTN override 3 Click 50 Main ARS ARS Route Id Secondary Dial tone Route Name SystemTone v Dial Delay Time System Default 4 Check User Call Barring In Service Out of Service Route lt None gt v Time Profile Out of Hours Route lt None gt v Code Telephone Number Feature Line Group Id 11 911 Dial Emergency 0 Remove 911 911 Dial Emergency 0 ON ON Dial 3K1 99999 Edit 1N 1N Dial 3K1 99999 XN N Dial 3K1 0 AXAXARARAAN N Dial 3K1 0 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 Make the changes as follows a Inthe Code field set this to match the external PSTN number for Modular Messaging
258. ll as a civil offense under the applicable law Third party components Certain software programs or portions thereof included in the Software may contain software including open source software distributed under third party agreements Third Party Components which may contain terms that expand or limit rights to use certain portions of the Software Third Party Terms Information regarding distributed Linux OS source code for those product that have distributed Linux OS source code and identifying the copyright holders of the Third Party Components and the Third Party Terms that apply is available in the Documentation or on Avaya s website at http support avaya com Copyright You agree to the Third Party Terms for any such Third Party Components Preventing Toll Fraud Toll fraud is the unauthorized use of your telecommunications system by an unauthorized party for example a person who is not a corporate employee agent subcontractor or is not working on your company s behalf Be aware that there can be a risk of Toll Fraud associated with your system and that if Toll Fraud occurs it can result in substantial additional charges for your telecommunications services Avaya Toll Fraud Intervention If you suspect that you are being victimized by Toll Fraud and you need technical assistance or support call Technical Service Center Toll Fraud Intervention Hotline at 1 800 643 2353 for the United States a
259. ll not appear If you want the B5800 Branch Gateway to be managed by System Manager check the Under Centralized Management check box Then complete the following fields a Inthe SMGR Address field enter the IP address of the System Manager server b Inthe SNMP Community field enter the appropriate SNMP community This is the SNMP community for System Manager Note This field must be configured correctly in order for the centralized management functionality to work c Inthe SNMP Device ID field enter the alarm ID you receive from a registration d Inthe Trap Community field enter the appropriate trap community This is the SNMP community for the Secure Access Link SAL gateway Note This field must be configured correctly in order for the centralized management functionality to work The SNMPv1 trap community string can be set from the System Manager console in under Services gt Configurations gt Settings gt SMGR gt TrapListener The trap community string in System Manager should match the trap community string set on the device so that System Manager receives the device alarms properly e Inthe Device Certificate Name field enter the appropriate certificate authority name Note The device certificate name cannot contain spaces f Inthe Certificate Enrollment SCEP Password field enter the appropriate password Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration
260. lowing example for calls to Modular Messaging or Avaya Aura Messaging which are automatically routed via the Session Manager line An additional Modular Messaging or Avaya Aura Messaging PSTN number can also be configured for use when the Session Manager line is not in service 915553800701 for the following example However it may also require additional configuration to ensure that this number is correctly routed to a branch PSTN trunk That could be done using a system short code but doing it in the ARS form keeps all the branch PSTN call routing in one place for ease of maintenance Adding an overriding short code 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 157 2 In the left navigation pane click ARS 180 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Adding an overriding short code 3 Click 50 Main ARS ARS Route Id Secondary Dial tone Route Name SystemTone v Dial Delay Time System Default 4 Check User Call Barring In Service Out of Service Route lt None gt v Time Profile Out of Hours Route lt None gt v Code Telephone Number Feature Line Group Id 1
261. ly the license expiration time on the local WebLM server is automatically refreshed and extended when the master WebLM server pushes a refreshed Allocation License File to the local WebLM For more information about WebLM licensing see Administering Avaya WebLM standalone and Avaya WebLM Administration Guide Separate PLDS license for each branch In B5800 Branch Gateway R6 1 an individual PLDS license file was required for each branch and installed on each branch directly AWebLM server was not required This licensing method is supported in B5800 Branch Gateway R6 2 for branches that cannot be connected via an enterprise WAN to a central WebLM server or for migration of installed B5800 Branch Gateway R6 1 systems Using the WebLM licensing method is recommended but does not have to be done as part of an R6 1 to R6 2 upgrade Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 17 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 In the IP Office Manager application this number appears in the PLDS Host ID field on the System page w
262. ly circuit and the effect that overloading of the circuits might have on overcurrent protection and supply wiring Appropriate consideration of equipment nameplate ratings should be used when addressing this concern e Reliable earthing Reliable earthing of rack mounted equipment should be maintained Particular attention should be given to supply connections other than direct connections to the branch circuit e g use of power strips Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 67 Hardware and software installation unuunu KG 2 ipo 500 Rack Mounting Kit KE 700429202 important Only the screws M3 x 6mm provided with the mounting kit should used to attach the 68 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com 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 Each module is supplied with an expansion interconnect cable and a power supply unit An a
263. mbedded 10 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 Note You must also enable the announcements Do this by selecting the check box for Announcements On which appears when you select Hunt Group gt Announcements tab and Users gt Announcements tab Inthe MM Number field enter the extension number configured for mailbox access to the Modular Messaging system Note that this number is automatically routed via the active Avaya Aura Session Manager line It does not need to be routed through the normal branch call routing Inthe MM PSTN Number field enter the PSTN number to which you want to reroute attempts to access mailboxes when the Avaya Aura Session Manager line s are out of service This field is optional This number needs to be a valid DID number from the branch to the Modular Messaging system When calls to access voicemail are routed by this method the caller will be prompted by Modular Messaging to indicate the action they are performing leaving or collecting messages and the target mailbox Depending on the call routing being used by the branch system for external PSTN calls you may need to do additional configuration to ensure that this number is routed via a branch PSTN trunk See Modular Messaging and Avaya Aura Messagin
264. mbers and contact addresses go to the Avaya Support website http support avaya com scroll to the bottom of the page and select Contact Avaya Support Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 3 4 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Contents Chapter 1 B5800 Branch Gateway OVErVieW ssssseeeeeeeeeeeeeeeeeeeeseeeeeeeeeeeeeeeeeeeeeeeeenees 13 PorN UII caniao S anani a i e aidia 13 VOLCOM NG ON aa aasernnues es aanecineada emreadask eeeerecaan oandeaae ed erreur 14 Pilea Peaches e a co tic A E E E E N 14 About upgrading B5800 Branch GalewWay Ssni iar eina aA SE EAAS AAE EAR ENa 16 Macao i EA eee tear E T E E E E Treen A A T 16 B5800 Branch Gateway Enges oiana ae a EE AAO AE AES Nia ESE 18 Bacin ee A E T E E E EEN A T E OA O A A TS 19 Sysem Onone isi a dain eae E EE 20 Sup Pored tel ohon S iei aaa a aaa aA 23 Sotware applica OG esris roaraa ear EERI EE EENE AREFE RaT PAETA rE Eas 26 Sppe d County OC o E E AEE AE ENA 27 He An e a E A A E E E 29 paG PII E e pease esr padagasied coetaataled Sutduaus ea panaseaatadp elas au ui niaetaa nena Ranta ea aaaS 31 Frio ucak eT 1 FINS nz E e E E E ennieslua E E E 31 E E E A OAA AAEE A A O A err er 31 C aaa eer cr et Ger ey errr ener Ter een ery mr retary err rrratenr tree ener emery y err errr err rrr 31 MOP I ace E E E E aed nace buen E meee Fae 32 g
265. minal equipment indicates only that Telecom has accepted that the item complies with minimum conditions for connection to its network It indicates no endorsement of the product by Telecom nor does it provide any sort of warranty Above all it provides no assurance that any item will work correctly in all respects with another item of Telepermitted equipment of a different make or model nor does it imply that any product is compatible with all of Telecom s network services FCC notification This equipment complies with Part 68 of the FCC rules and the requirements adopted by the Administrative Council on Terminal Attachments ACTA On the rear of this equipment is a label that contains among other information a product identifier in the format US AAAEQ TXXX If requested this number must be provided to the telephone company The REN is used to determine the quantity of devices that may be connected to the telephone line Excessive RENs on the telephone line may result in devices not ringing in response to an incoming call In most but not all areas the sum of RENs should not exceed 5 0 To be certain of the number of devices that may be connected to a line as determined by the total RENs contact the local telephone company For products approved after July 23 2001 the REN for this product is part of the product identifier that has the format US AAAEQ TXXX The digits represented by are the REN without a decimal point for example 0
266. more information Click OK Click File gt Save to save the security configuration From the System Manager console do the following a b c Go to the List End Entities page See Steps 1 to 2 in Generating a certificate on System Manager on page 119 In the left navigation pane click List End Entities Click the Reload button to reload the End Entity After the page refreshes the status of the End Entity changes from New to Generated This indicates the End Entity certificate exchange has occurred In Manager return to the Certificates tab See Steps 1 to 7 above In the Received Certificate Checks Management Interfaces drop down box select Medium This ensures the B5800 Branch Gateway will enforce the use of certificates Click OK Click File gt Save to save the security configuration Perform a synchronization See Synchronizing B5800 Branch Gateway with System Manager on page 162 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 e 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 e Bulk importing of devices on page 128 This method requires you to manually add each B58
267. mpa Engana R 133 Disabling unused TANKE siraan A A a 134 Digital Nune cek SIE E vereinen aaao 135 EIR a runkElock guality SoM erinit aA AA ANA 136 Senne TUNK O snieni ias 137 E L GG E E E E E A E T 138 Administering a Session Manager line for each Dranch csseeesceseeeeseceeeeeeeseneeteeessaeeeeeeseaaeeneeeeenetses 139 Enabling SIP unk Suppa icini e a eaa 139 Setting the branch prefix and local number length for extension nuMbering ccceeeeeeeeeeeeees 140 Changing ihe default codot Se ECHO ecis oen a 143 Changing the mamam SIF BOS STIS siaina a aiai E EER ANNS 144 Adding an Avaya Aura Session Manager lin c cecccccseseseeeeeeeeeeeeeeeeseeeeeceeesaeeenseeeeeseeeetaseenaeees 145 Avaya Aura Session Manager line redundancy ccccecceseceeseeeeeceeeceeeesaeeeeeecetseeeteesaneeeseeeatees 150 vert EL fy MNT Ah eal WMI acanna iR S 151 How the B5800 Branch Gateway uses a configured Session Manager line 153 Enabling baneh SIP exreneioi SUPPO cecco E E R 154 SiP Registrar AG field description N NEN 155 Chapter 9 Managing B5800 Branch Gateways from System Manager sssssssssssss 157 Editing a B5800 Branch Gateway system configuration from System Manager 157 Restrictions when editing a B5800 Branch Gateway system configuration from System Manager 158 About disabling the System Manager administration feature for a B5800 Branch Gateway 065 159 Disabling the System Manager administration
268. must update the version of IP Office Manager in the System Manager file To update the version in the System Manager file update the parameter abg_b5800_mgr_version in the file opt Avaya ABG tools ManagerSFXVersion properties with the version of IP Office Manager that is installed on the administration PC To use IP Office Manager Lite to manage the B5800 Branch Gateways download the B5800AdminLite exe file to the System Manager server as follows Note This task is not required if you have downloaded the B5800AdminLite exe file using the Upgrade Management link in System Manager Procedure 1 Download the B5800AdminLite exe file from http plds avaya com 2 Transfer the downloaded B5800AdminLite exe file to the System Manager server to the directory opt Avaya ABG lt version gt tools For example opt Avaya ABG 6 2 12 tools Use any SCP or SFTP protocol to connect to the server and transfer the file You may use any client to perform this step 3 Change this file into an executable file using the command chmod x lt file name gt 4 Create a soft link using the name ManagerSFX exe for the uploaded file as follows a Goto ABG_HOME tools by entering cd SABG_HOME tools b Use the command In sf lt target gt lt inkname gt to create the soft link For example if the file name uploaded to ABG_HOME tools is B5800AdminLite exe then enter In sf B5800AdminLite exe ManagerSFX exe 5 Using any
269. n to upgrade the B5800 Branch Gateway To determine if there is a new software version available Avaya PLDS uses the file versions _sp xml that is available from the Avaya Support Site to compare the current installed software on the device with the latest available on Avaya PLDS The file versions_sp xml is regularly updated with the latest firmware software releases available for upgrade Procedure 1 o From the System Manager console under Elements select Inventory 2 On the Inventory page click Upgrade Management gt Manage Software 3 4 When the analyze job is finished running refresh the table On the Manage Software page click More Actions gt Analyze Now A red x indicates there is a newer firmware version available that has not been downloaded to the software library Select the control unit for upgrade and click Download 6 On the File Download Manager page do the following a Inthe Library drop down box select the appropriate library b Inthe Protocol drop down box accept the protocol displayed Note The appropriate protocol is automatically selected based on the selected library c Expand the tree to show a list of the upgrade packages that are available d Under the Device Type B5800 select the latest package Do one of the following e Click Now to download the software e Click Later to schedule the download at a specified time Click Download Implementing the Avaya
270. n R6 2 service pack on page 97 Note Check the latest B5800 Branch Gateway Technical Bulletin for the B5800 Branch Gateway software release before proceeding any further It may contain information relating to changes that occurred after this document was completed Bulletins are available from http support avaya com e Multiple Managers If more than one copy of Manager is running it is possible for the B5800 Branch Gateway system to request BIN files from a different Manager from the 216 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com 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 e 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 However for each B5800 Branch Gateway core software release there may be exceptions See the Technical Bulletin for the B5800 Branch Gateway core software release for more information Using the upgrade wizard About this task Before using the upgrade wizard be sure you have a current backup of the system configuration See Creating a backup of the system configuration using IP
271. n Section Y 1 Create a backup of the system See Creating a backup of the system configuration configuration using System Manager on page 215 2 Synchronize the B5800 Branch See Synchronizing B5800 Branch Gateway Gateway with System Manager with System Manager on page 162 3 Set up an external server to act as See Remote Software Library for B5800 a remote software library Branch Gateway upgrades on page 98 4 Get the inventory See Getting inventory on page 100 5 Configure PLDS access See Configuring user PLDS access on page 101 6 Create a software library See Creating a software library on page 102 7 Upgrade the B5800 Branch See Upgrading the B5800 Branch Gateway Gateway using System Manager on page 103 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 97 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 The FTP SCP or SFTP protocols are then used to copy the firmware
272. n 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 5mm diameter fixtures and fittings suitable for the wall type Cable ties and labels for tidying and identifying cables e PC requirements Windows PC with the administration software installed See PC requirements on page 78 SD card reader Unpacking equipment About this task Use the following procedure when unpacking any equipment supplied by Avaya or an Avaya reseller or distributor Have the equipment order checklist available as you unpack the equipment to ensure you have all parts and equipment ordered Procedure 1 Check for package damage Before unpacking any equipment check for any signs of damage that may have occurred during transit If any damage exists bring it to the attention of the carrier 2 Check the correct parts have been delivered Check all cartons against the packing slip and ensure that you have the correct items Report any errors or omissions to the equipment supplier 3 Retain all packaging and documentation While unpacking the equipment retain all the packaging material Fault returns are accepted only if repackaged in the original packaging If perform
273. n changes in the following procedure will require the B5800 Branch Gateway system to be rebooted 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 157 2 In the left navigation pane click System 3 Click the LAN1 or LAN2 tab as appropriate depending on which branch site LAN interface will be used for the data connection to the Avaya Aura network 4 Confirm that the IP address and IP Mask fields are set correctly for the site 5 Click the VoIP tab 6 Select the SIP Trunks Enable option This is required for Avaya Aura Session Manager trunk support Note The SIP Registrar Enable setting and settings in the SIP Registrar tab relate to SIP extension support and therefore do not affect Avaya Aura Session Manager lines The settings in the Network Topology tab relate to external SIP trunks Those settings are not used by Avaya Aura Session Manager lines which use open internet across the customer WAN 7 Click OK 8 Select File gt Save Configuration The Send Configuration window appears and the Configuration Reboot Mode is set to Immediate Do not change the reboot mode Setting the branch prefix and local number length for extension numbering About this task
274. n i nessa irre 200 B5800 Branch Gateway registration and SAL Gateway on boarding sesssesseesrierrisrrrrrrrrrrerrreerieernses 201 B5800 Branch Gateway SAL based SlSriMiNnGiccciscccicenctssisnstictecsctammivieontuarsenvieseensannniiionerctenuiviensdanaie 201 Universal Install SAL Registration Request Forim ccccsccsscceecrsencceseeeeseeeeeeceeaneeseneseeneseeeeseeaeeneeeseaees 201 Chapter 15 Additional system PproCeCures ssseeececeeeeeeeeeeeeeeeeeeeeseseeneneeeeeeeseeeeennees 203 Changing We IF address SOMME cscs rac cccceepspecdence tie padetea ep debited sanehusiehcencaans 203 Pelant ASSIS cirese sa a AE E 204 Changing he sscurity seing usasse o E 204 Changing ihe remote user passwd ccnn E 205 A S AEN oL r A E E E EE E T E E doe OO as 206 Shutting down the system usnog Managalenisinicedininaeiii ai ia 206 8 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Shutting down the system using the System Status application eee eeeeeeeseeeeeseeeeneeeeaes 207 Shutting down the system using a SYSTEM PNONGE eececeseeeesneeeseeeseeeceseneceeneeecesessaneseaseneeneeeees 207 Shutting down the system usino the AUX DUHOM cscisccacnssasdudaccmsaosnisoceitnmasorcrannarasonsosancansntarondadnnes 207 PROC CIE ihe SY SIGN ede secs siciedestur sinters E viaersunsderdaaenie 208 Abou chanding Companen eioen aS 209 Replacing a component with one of the SAME yp inssniniinsiiiin an
275. n pairs of digits to provide the number in MAC address format nn nn nn nn nn nn You can also get the Host ID from Manager For more information see Licensing on page 16 Enter the number of Licenses to move in the QTY column field and click Next 10 11 Accept the Avaya Legal Agreement Perform the following steps to send an activation notification e mail message a Inthe E mail to field enter e mail addresses for any additional activation notification recipients b Enter any comments or special instructions in the Comments field c Click Finish Click View Activation Record e The Overview tab displays a summary of the license activation information e The Ownership tab displays the registration information e The License Key tab displays the license files resulting from the license activation In general a single license file will be generated for each application From the License Key tab you can view and download the license 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 For more information s
276. n the same position 3 Install the replacement using the appropriate procedure for the type of component See Base and trunk card installation on page 59 or Connecting external expansion modules on page 70 for more information 210 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com 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 See Permanently removing a component on page 212 Note Be sure to reboot the system and edit the configuration after you remove the component 2 Install the new component See Adding a new component on page 211 Adding a new component About this task If you are adding a new component to an available slot or port when restarted the B5800 Branch Gateway system will automatically create configuration entries for the new trunks or extensions users Procedure 1 Turn the B5800 Branch Gateway system off See System shutdown on page 206 2 Install the new component using
277. nable System Manager administration of the B5800 Branch Gateway For more information see Using the Initial Installation Utility on page 121 Installation checklist Use this checklist to monitor your progress as you install a B5800 Branch Gateway system Description Section v 1 Review the prerequisites See Prerequisites on page 35 2 Review the Installation See Installation requirements on page 41 requirements 3 Review the required tools and See Tools and equipment required on equipment page 54 4 Unpack the equipment See Unpacking equipment on page 55 5 If you want to pre configure the See SD card preparation on page 56 system there are several tasks you can perform to configure the Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 53 Hardware and software installation Description Section Y SD card before it is installed in the control unit 6 Prepare the base and trunk cards See Base and trunk card installation on and install them in the control page 59 unit 7 Do one of the following See one of the following e Install the control unit on the e Wall mounting on page 65 wall e Rack mounting on page 67 Install the control unit in a rack 8 Connect the external expansion See External expansion modules on modules page 69 9 Connect the control unit and See Ground
278. nager 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 If you need to add or adjust a time range see Creating Time Ranges in Administering Avaya Aura Session Manager document number 03 603324 Creating routing policies A routing policy is a collection of multiple time ranges and a destination SIP entity For each dial pattern configured to route calls received by the Session Manager the routing policy associated with that dial pattern defines when and where matching calls are directed Separate routing policies are required for each B5800 Branch Gateway entity to which the Session Manager routes calls 1 o On the System Manager console under Elements click Routing 2 In the left navigation pane click Routing Policies 3 4 On the Routing Policies Details page in the Name field enter a name to describe On the Routing Policies page click New to create a new routing policy this routing policy For the Disabled check box accept the default unchecked 6 In the Notes field enter notes about this routing policy as appropriate 7 Inthe SIP Entity as Destination section do the following a Click Select b On the SIP
279. nager R6 2 Avaya Aura System Manager is a central management system that delivers a set of shared management services and a common console for different components of the Avaya Aura solution System Manager provides a single access interface to administer multiple branch locations and multiple distributed B5800 Branch Gateway users System Manager also launches IP Office Manager in the appropriate mode where you can remotely administer individual B5800 Branch Gateways As an alternative to System Manager you can use IP Office Manager that is directly connected to the B5800 Branch Gateway to configure a branch locally when you need to administer an isolated branch or System Manager is not available IP Office Manager is an application for viewing and editing a B5800 Branch Gateway system s configuration It is included in the B5800 Branch Gateway administration software suite Manager is an off line editor It receives a copy of the system s current configuration settings After changes are made to that copy and the file is saved Manager automatically sends the file back to the system for those changes to become active Avaya Aura System Manager Using Avaya Aura System Manager R6 2 you are able to e Upgrade B5800 Branch Gateway systems e Add B5800 Branch Gateway devices from the network to System Manager e Create B5800 Branch Gateway endpoint templates that are used to create B5800 Branch Gateway users These templates can be edited du
280. nd Canada For additional support telephone numbers see the Avaya Support website http support avaya com Suspected security vulnerabilities with Avaya products should be reported to Avaya by sending mail to securityalerts avaya com Trademarks Avaya is a registered trademark of Avaya Inc Aura is a registered trademark of Avaya Inc October 2012 Comments infodev avaya com 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 Nothing contained in this site the Documentation and Product s should be construed as granting by implication estoppel or otherwise any license or right in and to the Marks without the express written permission of Avaya or the applicable third party Downloading Documentation For the most current versions of Documentation see the Avaya Support website http support avaya com Contact Avaya Support See the Avaya Support website http support avaya com for product notices and articles or to report a problem with your Avaya product For a list of support telephone nu
281. nd alarms but continues to provide normal operation as in License Normal Mode Calls are allowed and or blocked based on current configuration parameters and configured users can register regardless of licensing status The license errors must be fixed either by installing a valid license file with the appropriate licenses or by changing the configuration so that it does not exceed any license capacities License Restricted Mode One or more license errors are present and the 30 day license grace period has expired B5800 Branch Gateway prevents any administrative changes except those that fix the licensing Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 19 B5800 Branch Gateway overview errors While administration is restricted dynamic system operation Such as making calls continues based on the current configuration parameters regardless of licensing status 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 It includes 4 slots for optional base cards to support trunk and phone extension ports The slots are numbered 1 to 4 fr
282. ne Group Id Set the Line Group ID to match the Outgoing Group settings used in the SM lines URI setting 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 How the B5800 Branch Gateway uses a configured Session Manager line Once configured and in operation the Avaya Aura Session Manager line is used as follows Outgoing calls from a branch In the Distributed branch user model if the outgoing call begins with the branch s own prefix the prefix is removed and the call is targeted locally to the matching native user or hunt group Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 153 Initial branch configuration extension number If there is no matching extension number the call is targeted to any matching system short code Incoming calls to a branch Incoming calls on an Avaya Aura Session Manager line are treated as being internal calls and do not go through the B5800 Branch Gateway system s Incoming Call Route settings e If the destination of the incoming call on the Avaya Aura Sessi
283. ng the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 215 Additional system procedures Manager See Synchronizing B5800 Branch Gateway with System Manager on page 162 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 Onthe 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 e Click Schedule to run the backup job at a scheduled date and time Upgrades using IP Office Manager IP Office Manager includes software files for control units external expansion modules and phones appropriate to the system s software level The B5800 Branch Gateway system can be upgraded in two ways using IP Office Manager that is connected directly to the B5800 Branch Gateway system These methods are e Using the IP Office Manager upgrade wizard See Using the upgrade wizard on page 217 e Using the System SD card See System upgrade using the System SD card on page 256 B5800 Branch Gateway systems can also be upgraded using Avaya Aura System Manager This method is used for systems that have already been upgraded from R6 1 to R6 2 and is used when multiple branches require upgrades For more information see Upgrading an R6 2 system with a
284. ng the SIP domains on page 166 for a list of SIP domains defined in Session Manager SM Address Enter the IP address of the Session Manager that the line should use in the Avaya Aura network The same Session Manager should be used for the matching Entity Link entry in the Avaya Aura configuration 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 146 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Administering a Session Manager line for each branch Name Description 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 This value sets the number of simultaneous calls allowed between B5800 Branch Gateway and Session Manager using this connection Each call uses one of the available licenses that are shared by all SIP trunks configured in the system URI Type When SIP or SIPS is selected in the drop down box the SIP URI format is used for example name example com This affects the From field of outgoing calls The To field for outgoing calls will always use the format specified by the short codes used for outgoing call routing Recommendation When SIP Secured UR
285. nks atic a ctgercosvale dain E R 134 upgrade software eee ceeeeeeeeeeeeeeeteeeeeeeeeeeeeeeeees 216 Managing B5800 Branch Gateways from System Manager eee eee ceeeceeceeeeeeeeeceeeeeeeeneeeeeaeeeaaeeea 157 manually adding B5800 Branch Gateways to System VE 0 2 129 Maximum SIP SESSIONS c ccececceeeeeeeeeeeeeeeeeeeanees 144 migrating individual PLDS license files to a WebLM SENE savisiacasaraahiiitl nadiaaniaatensiendisisaworeversas 94 Mod le sida vacivaersaatevesgecasatvaevantteidcnesaeanndtueueauntucatientendees 222 Polycom VideO eee 222 MOGUIES friciussinecbicadcicecvensasaatagerdundibosdercinieredteredeannan 265 Trunk INtEfACE niinen nnie 265 MONItOFING 2c eee eeeeceeeeeeeeeceeeeceeeeeeeeeeeeeeeteeeeteeeeeeeees 167 N network assessment for VoIP requirements 39 New configuration cccccccecceceeeeeeeeeeeeencaeaeeeeeeeeeeeeeees 57 new in this release ceeeeccceeeeeseeeeeeceasseseeeeeseeeeeeees 29 O Operation iN eerren 267 270 PAUSU PANG aaea e E A tise 267 Canada senne AN E 268 GMINA eitan a a aa 269 European UNION cccccccccceeeceeeceeeeeeeeeeeeeeeeess 270 NeW zealand imanin nanai 270 Out Of DUIIGING occire a ve COMNMEGHOMNS iana e E NE 72 outgoing Call routing 2 2 ee eee eect eee teteeteeeeeeeeeeeees 151 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration P Park and Page c cccccceeceeceeeeeeeeeeeeeeeee
286. nnels The card also includes 10 VCM channels This card has a pre installed BRI trunk daughter card Amaximum of 2 BRI combination cards of any type are allowed per control unit ATM combination card This card provides 6 digital station ports 1 6 2 analog extension ports 7 8 and 4 analog trunk ports 9 12 The card also includes 10 VCM channels This card has a pre installed analog trunk daughter card A maximum of 2 ATM combination cards of any type are allowed per control unit The analog phone ports do not include a ringing capacitor Where this is a requirement connection should be via a Master socket containing ringing capacitors If fitted with an analog trunk daughter card during power failure phone port 8 is connected to analog trunk port 12 TCM 8 card This card provides 8 digital station ports 1 8 e Trunk daughter cards Most base cards can be fitted with a trunk daughter card to support the connection of trunks to the base card The following trunk daughter cards are supported Analog trunk card This card allows the base card to support 4 analog loop start trunks The analog phone ports do not include a ringing capacitor Where this is a requirement connection should be via a Master socket containing ringing capacitors If fitted with an analog trunk daughter card during power failure phone port 8 is connected to analog trunk port 12 A maximum of 4 analog trunk cards are allowed per control unit B
287. nnels which are configured as being in service Manager will block attempts to configure PRI channels as in service if they exceed the 8 per port allowed by default on that card and if there are no Additional T1 Channels or Additional E1 Channels licenses available 120 day trial license This license provides a 120 day trial period during which you have access to the features functions and capabilities available in B5800 Branch Gateway After the expiration of the 120 day trial license the 30 day grace period is activated At the end of the 30 day grace period if no other license is installed or available system administration is blocked except for administration that fixes the licensing errors License modes The B5800 Branch Gateway system can be in one of three license modes License Normal Mode License Error Mode and License Restricted Mode The license mode as well as any license errors are displayed in IP Office Manager License Normal Mode No license errors are present The B5800 Branch Gateway can access the WebLM server and obtain the required license entitlements If the licensing method is used where an individual PLDS license file is required for each branch a valid license file is installed on the B5800 Branch Gateway with sufficient entitlements License Error Mode One or more license errors are present The B5800 Branch Gateway initiates a 30 day license grace period during which time the system issues errors a
288. no software e Flashing Red error shutdown Base card LEDs Base Card LEDs 1 to 8 Usage All cards LED1 is used for base card status e Red on error e Red slow flash initializing e Red flash every 5 seconds card okay e Red fast flash system shutdown Analog phone No status LEDs are used for analog phone extensions Digital station Green on phone detected VCM LEDs 1 to 8 are unlabelled They are used to indicate voice compression channel usage Each LED lit represents 12 5 of the available voice compression channel capacity in use total card capacity rather than licensed capacity 4 port expansion LEDs 1 to 8 are used for the expansion ports on the rear of the control unit LEDs 9 to 12 are used for the card s own expansion ports Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 83 Hardware and software installation Base Card LEDs 1 to 8 Usage e Green on expansion module present e Red flashing initializing e Red on error e Orange regular flash base card okay Combination LEDs 1 to 6 Green on phone detected Trunk daughter card LEDs Trunk Daughter Card LEDs 9 to 12 Usage All cards LED 9 is used for daughter card status e Red on error e Red slow flash initializing e Red flash every 5 seconds card okay e Red fast flash system shutdown Analog tr
289. nouncements Embedded Messaging Port licenses must be purchased with sufficient quantity to support the configured number of ports Standalone Voice Mail Standalone Voice Mail provides the same features as Embedded Voicemail but with additional port capacity provided on a Linux server You must have a Linux server installed to use this option When you select this option you must enter the IP address of the Linux server where Standalone Voice Mail is installed This option provides a maximum capacity of 40 ports while the Embedded Voicemail option provides a maximum capacity of 6 ports Embedded Messaging Port licenses must be purchased with sufficient quantity to support the configured number of ports 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 176 for more information When Avaya Aura Messaging is used as the central voicemail system at each branch you have the option to still use the local Embedded Voicemail for auto attendant operation and for announcements to waiting calls Note that for this configuration Embedded Voicemail licenses are required Modular Messaging over SIP The B5800 Branch Gateway system can be configured to use Modular Messaging over SIP as its voicemail server when Session Manager is used as the
290. nsole 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 157 2 In the left navigation pane click Line 3 For each line set those lines or channels that are not connected or not being used as Out of Service The location of the relevant setting varies for each trunk type 134 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Digital trunk clock source 4 For Analog Trunks set the Trunk Type to Out of Service 5 For BRI E1 PRI SO and QSIG Trunks set the channels quantities to match the actual subscribed channels 6 For T1 T1 PRI and E1R2 Trunks select the Channels tab Then do the following Select those channels that are not used and click Edit e For T1 set the Type to Out of Service e For T1 PRI set the Admin field to Out of Service e For E1R2 trunks set the Line Signalling Type to Out of Service 7 Select File gt Save Configuration Digital trunk clock source About this task Digital trunks require the telephone system at each end of the trunk to share a clock signal to ensure synchronization of call signalling The B5800 Branch Gateway can obtain and use the clock signal from any of its digital trunks Typically the clock signal pro
291. nstallation utility is launched See Using the Initial Installation Utility on page 121 Control unit LEDs startup sequence The LEDs on the rear of the control unit go through the following sequence during a normal start up Note that the times are approximate only LED 4s 4s 12s 5s 2s 5s 5s 10s 10s Finished CPU Orng Grn Grn Grn Grn Grn Grn Grn Grn Grn Red System Orng Off Grn Grn Grn Off Grn Grn Grn Grn SD Flash Optional Orng Off Grn Grn Grn Off Off Grn Grn Grn SD if present Orng Orange Grn Green On the front of the control unit LED1 on any IP500 base cards fitted is used as follows LED9 is also used for any trunk daughter cards fitted LED 30s 30s Finished Optional SD Red Red Red Fast Flash Flash every 5 seconds 82 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Applying power to the system About the LEDs Control unit LEDs LED Description Optional SD System SD e Off card shutdown e Green on card present e Green flashing card in use e Orange steady reset imminent e Red flashing card initializing or shutting down e Red fast flashing card full e Red steady card failure wrong type CPU e Alternate red green starting up e Green on okay e Red on
292. nter AT upper case An OK response appears 4 Enter AT DEBUG The time and date and then the Hello gt prompt appears to show the system is ready to accept commands 5 To erase the current configuration in RAM memory enter eraseconfig The Hello gt prompt reappears 6 To erase the backup configuration stored in non volatile Flash memory enter erasenvconfig The Hello gt prompt reappears 7 To reboot the system enter reboot The system reboots and restarts with a defaulted configuration 8 Close the terminal program session 232 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com 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 See Creating a backup of the system configuration using IP Office Manager on page 215 for more information Procedure _h Attach the serial cable between the PC and the DTE port on the control unit N Start the terminal program on your PC Note Ensure that the DTE port settings are c
293. nter an IP address pattern that matches the IP LAN address range 166 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com 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 This is done using a set of digit conversions stored by the digit adaptation associated with the SIP entity Adaptations are optional and are deployment specific For more information see Adaptations in Chapter 5 Managing Session Manager routing in Administering Avaya Aura Session Manager document number 03 603324 Creating SIP entities ASIP entity is required for each branch system This is in addition to the SIP entities that should already exist for Session Manager and Communication Manager or Communication Manager Feature Server or Evolution Server 1 On the System Manager console under Elements click Routing 2 In the left navigation pane click SIP Entities 3 4 On the SIP Entity Details page in the Name field enter the name of the SIP On the SIP Entities p
294. ntrol unit boots up using software other than that in its System SD primary folder e An alarm will be shown in the System Status application It will also generate an alarm if the card in any slot is not compatible These alarms are also output as SNMP Syslog or email alarms e The Manager Select IP Office window will display an icon indicating that the system is running using software other than from the System SD card s primary folder e The configuration can be read but will be read only Attempting to send a configuration to the system will cause the error message Failed to save configuration data Internal error Bypassing the System SD card primary folder The control unit can be forced to bypass the System SD card s primary folder and non volatile memory when starting This is done by pressing the AUX button while applying power to the control unit This may be necessary if following an upgrade of the B5800 Branch Gateway system it is determined that a roll back to the previously backed up firmware and configuration is required Using the AUX button should restore system operation using the backup folder files while the installer then restores the contents of the primary folder to a previous release Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 245 SD card management About creating a B5800 Branch Gateway SD card The procedures in this section are for B5800 Branch Gateway S
295. number in MAC address format nn nn nn nn nn nn You can also get the Host ID from Manager For more information see Licensing on page 16 7 Enter the number of licenses to activate 8 Review the Avaya License Agreement and accept the agreement if you agree 9 Perform the following steps to send an activation notification e mail message a Inthe E mail to field enter e mail addresses for any additional activation notification recipients b Enter any comments or special instructions in the Comments field c Click Finish 10 Click View Activation Record e The Overview tab displays a summary of the license activation information e The Ownership tab displays the registration information e The License Key tab displays the license files resulting from the license activation In general a single license file will be generated for each application From the License Key tab you can view and download the license 192 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com 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 l
296. o Video Restricted Digital Information If unknown type of number is used in calling party number the network will use the default CLI The system must be configured for Point to Multi point connection to comply with Austel requirements for connecting to TS013 circuits As the B5800 Branch Gateway does not support emergency dialing after loss of power the following warning notice should be recognized A Warning This equipment will be inoperable when main power fails PRI interface Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 267 Safety and regulatory information During the configuration ensure 000 emergency number is not barred by performing the following e Short Code 000 Telephone No 000 e Function DialEmergency Canada This equipment meets the applicable Industry Canada Terminal Equipment Technical Specifications This is confirmed by the registration number The abbreviation IC before the registration number signifies that registration was performed based on a Declaration of Conformity indicating that Industry Canada technical specifications were met It does not imply that Industry Canada approved the equipment NOTICE The Ringer Equivalence Number REN for this terminal equipment is 1 The REN assigned to each terminal equipment provides an indication of the maximum number of terminals allowed to be connected to a telephone interface The termination
297. of an Uninterrupted Power Supply UPS with any telephone system is strongly recommended Even at sites that rarely lose electrical power that power may occasionally have to be switched off for maintenance of other equipment In addition most UPSs also provide an element of power conditioning reducing spikes and surges The capacity of UPS systems and the total equipment load the UPS is expected to support are usually quoted in VA Where equipment load is quoted in Watts multiply by 1 4 to get the VA load The calculation of how much UPS capacity is required depends on several choices e What equipment to place on the UPS Remember to include server PCs such as the voicemail It is recommended that the total load on a new UPS is never greater than 75 capacity thus allowing for future equipment How many minutes of UPS support is required Actual UPS runtime is variable it depends on what percentage of the UPSs capacity the total equipment load represents For example a 1000VA capacity UPS may only support a 1000VA 100 load for 5 minutes This relationship is not linear the same UPS would support a 500VA 50 load for 16 minutes Therefore the lower the percentage of capacity used the increasingly longer the UPS runtime typically up to 8 hours maximum Remember also that for most UPS s the ratio of discharge to full recharge time is 1 10 How many output sockets does the UPS provide Multiple UPS units may be required to ensure t
298. om left to right They can be used in any order however if the capacity for a particular type of card is exceeded the card in the right most slot will be disabled B5800 Branch Gateway System SD card The B5800 Branch Gateway System SD card is a specific Avaya SD card that is required It determines the system operation as B5800 Branch Gateway It is uniquely numbered and has a serial number that must be used as the Host ID in the PLDS license file if the B5800 Branch Gateway is operating with an individual license file and not with WebLM licensing The B5800 Branch Gateway System SD card also provides Embedded Voicemail support and storage for system software files The card fits into a slot in the rear of the control unit e Base cards The control unit has slots for up to 4 base cards The base cards are used to add analog extension ports digital extension ports and voice compression channels Each base card includes an integral front panel with ports for cable connections The following base cards are supported Digital station base card This card provides 8 digital station DS ports for the connection of Avaya digital phones other than IP phones The card can be fitted with a trunk daughter card which uses the base card ports for trunk connection A maximum of 3 digital station base cards are allowed per control unit Analog phone base card This card is available in two variants supporting either 2 or 8 analog phone p
299. omatic codec negotiation See Automatic codec preference settings on page 144 for more information 5 Click OK 6 Select File gt Save Configuration Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 143 Initial branch configuration The Send Configuration window appears and the Configuration Reboot Mode is set to Immediate Do not change the reboot mode Automatic codec preference settings Setting Selected 2nd Preference 3rd Preference 4th Preference Preference G 729 G729 a 8K CS G711 U Law G711 A Law G723 1 6K3 MP ACELP 64K 64K MLQ G 723 G723 1 6K3 MP G729 a 8K CS G711 U Law G711 A Law MLQ ACELP 64K 64K G 711 U Law G711 U Law G711 A Law G729 a 8K CS G723 1 6K3 MP 64K 64K ACELP MLQ G 711 A Law G711 A Law G711 U Law G729 a 8K CS G723 1 6K3 MP 64K 64K ACELP MLQ G 722 64K codec is also supported on systems with IP500 VCM or IP500 Combo cards By default the G 722 64K codec is not used Changing the maximum SIP sessions About this task The Maximum SIP Sessions setting determines the number of concurrent sessions allowed across all SIP trunks SM line and public SIP trunks Setting Maximum SIP Sessions to a specific value requires a corresponding quantity of B5800 Branch Gateway SIP Trunk Session licenses If B5800 Branch Gateway cannot obtain the required license quantity then the configuration change will be rejected
300. on Manager line starts with the system s branch prefix the prefix is removed The call is then targeted to the matching native user or hunt group extension number If there is no matching extension number the call is targeted to any matching system short code e If the destination of the incoming call on the Avaya Aura Session Manager line does not start with the system s branch prefix the whole number is checked for a match against system short codes Line status detection The B5800 Branch Gateway system sends regular OPTION messages to any Avaya Aura Session Manager lines in its configuration The Proactive and Reactive settings on the B5800 Branch Gateway system s System tab set how often the OPTION messages are sent in seconds The Proactive setting is used for an Avaya Aura Session Manager line currently thought to be in service The Reactive setting is used for an Avaya Aura Session Manager line currently thought to be out of service e 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 e If the line is out of service and call comes from the trunk the trunks status is changed back to in service e If the line is in service a call may fail due to either being unable to deliver the message or receive a 100 response within a configured timeout The line will not go out of service because this
301. on October 2012 289 Branch PSTN call routing examples Routing B5800 Branch Gateway calls example 290 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 For calls in other locales or between branches in different locals the example would be adjusted to ensure that the resulting number received at the remote branch would be routed to an external PSTN trunk and is suitable for external dialing At each B5800 Branch Gateway we need to ensure that calls starting with 90 the external and then international number prefixes are routed to the branch s Avaya Aura Session Manager line rather than direct to an external PSTN line In the B5800 Branch Gateway system configuration the default system short code 9N is used to match calls prefixed with a 9 The short code removes the 9 prefix and routes the call to the branch s ARS form 50 Main Short Code Code Feature Telephone Number Line Group Id Force Account Code Procedure R Locale 1 Start Manager and connect to the B5800 Branch Gateway system 2 In the left navigation pane click ARS Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Centralized call control 3 Click 50 Main ARS ARS Rou
302. on an interface may consist of any combination of devices subject only to the requirement that the sum of the Ringer Equivalence Numbers of all the devices does not exceed five 268 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Regulatory Instructions for Use China A V N A 700433220 February 2007 Copyright 2007 Avaya Inc All Rights Reserved PAEPHKARAA RRA ONAN SHES ROAM LRH Include this document with all Electronic Information Products imported or sold in the People s Republic of China Awe 5 EF Wh RS Hazardous Substance R Mt Metal Parts BEM ER Circuit Modules BERERA EIES o Cables amp Cable Assemblies ARARA MA Plastic and Polymeric parts Petre Tt Circuit Switch Breakers emat gt Power Assemblies 278 o LCD Monitor eg gt e Glass RABABASMAL BS tH ASARA S BIZ SIT 11363 2006 THEMEN RMR RAT Indicates that the concentration of the hazardous substance in all homogeneous materials in the parts is below the relevant threshold of the SJ T 11363 2006 standard o o o o RABABA SMALE SMAOR SAAAS WS EHH SIT 11363 2006 RAMEOREER Indicates that the concentration of the hazardous substance of at least one of all homogeneous materials in the parts is above the relevant threshold of the SJ T 11363 2006 standard ERIR PROLEDSFSer A gt MEF ARR TRASKAR ER Hr ATeTeRt SALARY This table shows whe
303. on page 191 Procedure 1 On the System Manager console under Services click Licenses 2 In the left navigation pane click Install License 3 Click the Browse button and navigate to the appropriate license file 4 Click the Install button Using Manager to deliver license files to the branches Before you begin License files have been activated with the Host ID that is the Feature Key Serial Number printed on the B5800 Branch Gateway System SD card See Activating license entitlements on page 191 About this task You can use Manager to distribute activated license files to B5800 Branch Gateway sites This procedure explains how to distribute the license files to a single branch at a time If the B5800 Branch Gateway is centrally managed by System Manager you must first disable the System Manager administration feature for the branch After you download the license file you must then enable the System Manager administration feature for the branch See Disabling the System Manager administration feature for the branch from System Manager on page 160 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 Manager copies the license file to the B5800 Branch Gateway SD card where it is valida
304. on you want to edit 4 Click Edit The IP Office Manager application is launched Note If the B5800AdminLite exe file has not been downloaded to the System Manager server an error message appears that says The system cannot find the file specified If you receive this message click OK Then see Setting up System Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 157 Managing B5800 Branch Gateways from System Manager Manager to launch IP Office Manager on page 112 for the procedure to install the B5800AdminLite exe file on the System Manager server Note If this is the first time you are attempting to edit a B5800 Branch Gateway device through System Manager from this PC and IP Office Manager has not yet been installed on this PC the following message appears B5800 Branch Gateway Manager not installed Avaya B5800 Branch Gateway Manager is not installed on this machine To complete the current task you must download and install Avaya B5800 Branch Gateway Manager After you complete this installation restart the machine Refer to the Release Notes Online help Do you want to download Avaya B5800 Branch Gateway Manager from the server now If you receive this message click Yes Then go to step 4 in Installing IP Office Manager from the System Manager server to a PC on page 114 for the procedure to install IP Office Manager on the PC Restrictions when editing a B580
305. one of the following a To configure Park and Page for this DTMF breakout select Park amp Page and then do the following i In the Paging Number drop down box select the appropriate hunt group or user extension ii In the Retries field use the up and down arrows to set the number of times to repeat the page 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 Toconfigure Centrex Transfer for this DTMF breakout select Centrex Transfer and then enter the transfer number in the Transfer Number field c To configure an extension number for this DTMF breakout select the appropriate extension number from the Reception Breakout DTMF 0 drop down box 11 For the Breakout DTMF 2 drop down box repeat step 10 12 For the Breakout DTMF 3 drop down box repeat step 10 13 In the SIP Name field enter the appropriate name Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 175 Voicemail configuration 14 In the SIP Display Name Alias field enter the appropriate name 15 In the Contact field enter the appropriate name 16 Configure the Anonymous check box as appropriate This feature is enabled when this check box is selected Note For more information about the fields in the SIP Settings section see the IP Office Manager on line help Configuring B580
306. onfigured as described in RS232 DTE port settings on page 230 Within a HyperTerminal session the current settings are summarized across the base of the screen 3 Arrange the program windows so that the terminal program and Manager TFTP log are visible at the same time 4 Switch off power to the control unit 5 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 6 Enter AT upper case An OK response appears If OK does not appear check the settings of your terminal program 7 To erase the alarm log enter AT X1 8 To erase the backup configuration stored in non volatile memory enter AT X2 An OK response appears 9 To erase the current configuration in RAM memory enter AT X3 A series of OK responses appear 10 Switch power to the control unit off and then back on Messages appear as the control unit performs the start up tasks 11 Close the terminal program session Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 233 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
307. only e VCM 24 VCM 30 A Warning Correct anti static protection steps should be taken while handling circuit boards Parts and equipment required e Legacy carrier card e VCM card e 2 plastic stand off pillars per card e Trunk cards are supplied with a replacement blanking plate which is not required 62 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Base and trunk card installation Tools required 5mm Flat blade screwdriver e Anti static wrist strap and ground point Installing a legacy carrier card Procedure 1 2 Check that correct cards have been supplied Ensure that you are wearing an anti static wrist strap connected to a suitable ground point 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 If fitting an IP400 trunk card identify which of the plastic snap off panels on the front of the carrier card need to be removed to allow the trunk cable connections i Single PRI l i Dual PRI ATM4 Quad BRI 5 Carefully remove those panels 6 Fit the stand off pillars to the legacy carrier card 7 Using minimal force and checking that the pins are correctly located push the IP400 card onto its jumper and the stand off pillars Base card insertion Having prepared each base c
308. ork Unsuitable Network When multiple trunks with the same setting are providing clock signals trunks are used in the order of slots 1 to 4 and then by port on each slot The current clock source being used by an B5800 Branch Gateway system is shown on the Resources page within the IP Office System Status Application 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 157 2 In the left navigation pane click Line 3 For each digital line do the following a Select the line b On the Line tab select whether that trunk should provide the clock source for the network or whether the trunk is unsuitable Note For E1R2 trunks the Clock Quality setting is on the Advanced tab 4 Ensure that only one trunk is set to Network This should preferably be a direct digital trunk to the central office exchange 5 Set one other trunk to Fallback in case the selected network trunk connection is lost Note If possible this should be a trunk from a different provider since that reduces the chances of both sources failing at the same time 6 Ensure that all other digital trunks are set as Unsuitable 136 Implem
309. orts The card can be fitted with a trunk daughter card which uses the base card ports for trunk connection A maximum of 4 analog phone base cards are allowed per control unit The analog phone ports do not include a ringing capacitor Where this is a requirement connection should be via a Master socket containing ringing capacitors If fitted with an analog trunk daughter card during power failure phone port 8 is connected to analog trunk port 12 VCM base card This card is available in variants supporting either 32 or 64 Voice Compression Channels VCM for use with VoIP calls A maximum of 2 VCM base cards are allowed per control unit The card can be fitted with a trunk daughter card which uses the base card ports for trunk connection 4 port expansion base card This card adds an additional 4 expansion ports for external expansion modules The card is supplied with four 2m yellow interconnect 20 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com System components cables This card does not accept any trunk daughter cards Amaximum of 1 4 port expansion base card is allowed per control unit right hand slot 4 only See External 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 cha
310. ory 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 259 and System shutdown on page 206 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 This allows retention of the user settings and association of the user with a different extension by changing that extension s Base Extension number to match the user s Extension ID In the following procedures the term component refers to a card fitted into the control unit or an external expansion module Replacing a component with one of the same type About this task If you are replacing a component with one of the same type and capacity no configuration changes are required Procedure 1 Turn the B5800 Branch Gateway system off See System shutdown on page 206 2 Remove the card or external expansion module Note The card slot or expansion port used as the replacement must be installed in the same position 3 Install the replacement using the appropriate procedure for the type of component See Base and trunk card installation on page 59 or Connecting external expansion modules _ on page 70 for more information 4 Restart the B5800 Branch Gateway system Implementing the Avaya B5800
311. ou begin Each B5800 Branch Gateway device has been added to an xml file For information about the xml file containing the devices see About the xml file containing the B5800 Branch Gateway devices on page 129 About this task Use this task to import the B5800 Branch Gateway devices from an xml file to System Manager Procedure 1 From the System Manager console under Elements select Inventory 2 In the left navigation pane click Manage Elements 3 On the Manage Elements page click More Actions gt Import 4 On the Import Elements page in the Select File field enter the complete path of the xml file Or click Browse to locate the xml file o Select one of the following error configuration options e Abort on first error e Continue processing other records 6 Select one of the following import options e To skip a matching record that already exists in the system during an import operation click Skip e To replace all data for an application click Replace e To merge application data so that you simultaneously perform an add and update operation of the application data click Merge e To delete the application data from the database that match the records in the xml file click Delete 7 Select one of the following schedule job options e Click Run immediately to run the job now e Click Schedule later and then select the date and time to run the job ata scheduled date and time 128 Implementin
312. ou must enable the secure communication feature in IP Office Manager Procedure 1 Start IP Office Manager 2 Select File gt Preferences 3 4 Click the Secure Communications check box to select this option check box is Click the Security tab checked Click OK Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 91 Upgrading an R6 1 system to R6 2 Exporting users to an xml file About this task Be sure to perform this task before you launch the Initial Installation Utility After you launch the Initial Installation Utility the System Manager administration feature for the branch is enabled and the users on the B5800 Branch Gateway are deleted so they will not be available for export Procedure 1 Start Manager and connect to the B5800 Branch Gateway system 2 Select Tools gt Export gt Users o Inthe Export Users dialog box click the check boxes for the users you want to export Inthe Domain Name field enter the appropriate domain name Browse to the folder where you want to save the xml file Click OK Inthe Export Users dialog box click OK N OO A Editing the xml file containing the users About this task Use this task to edit several fields in the xml file so that the data matches the requirements for the corresponding fields in System Manager Procedure 1 Using a text editor open the xml file that contains the exported users
313. ou wish to assign 7325551000 19 to port 1 and 7325551020 20 to port 2 etc Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 221 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 e Line Group ID 701 e Incoming Number 100x e Destination c Repeat for Line Group ID 702 etc d Create short codes for example e Short Code 100x Telephone Number e Line Group ID 701 e Feature Dial SO calls dialed without the area code are handled locally without network charges Calls with area calls will go via the network Example 2 video conference About this task In this example calls are routed to a Polycom Viewstation module connected to a SO port of the B5800 Branch Gateway system The following settings were used on 4 incoming data channels of a PRI line e Line Number 5 e Channel Allocation 23 gt 1 e Switch Type 5ESS e Line Sub Type PRI e Provider AT amp T e Channels 1 4 e Incoming Line Group 95 e Outgoing Line Group 95 e Direction Bothway e Bearer Data e Service Accunet this is a important e Admin In Service 222 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Example of BRI So8 module configuration To
314. out how to perform this process you should not proceed It is your responsibility to ensure that the registry is correctly backed up before any changes are made Procedure 1 Close Manager 2 Locate the registry key HKEY_CURRENT_USER Software Avaya IP400 Manager EnableAuthorisationCodes and change its value from 0 to 1 300 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com 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 gt Telephony gt Supervisor Settings To Force Authorization Codes on Specific Calls To require entry of an authorization code on a particular call or call type the Force Authorization Code option should be selected in the short code settings This can be used in user user rights or system short codes in order to apply its effect to a user group of users or all users respectively You need to ensure that the user cannot dial the same number by any other method that would by pass the short code for example with a different prefix About entering an authorization code Wh
315. owing this the B5800 Branch Gateway will restart with a default configuration Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 231 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 O 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 gt Advanced gt Erase Configuration command Erasing the configuration via debug About this task This procedure erases the system s configuration settings but does not alter the security settings It is easier to use than the boot loader method Before you perform this procedure be sure you have a current backup of the system configuration See Creating a backup of the system configuration using IP Office Manager on page 215 for more information Procedure 1 Attach the serial cable between the PC and the DTE port on the control unit 2 Start the terminal program on your PC Note Ensure that the DTE port settings are configured as described in RS232 DTE port settings on page 230 Within a HyperTerminal session the current settings are summarized across the base of the screen 3 E
316. page 58 e See Adding music on hold files on page 58 See Add a 9600 Screen Saver Image File on page 59 For more information about SD cards see SD Card Management on page 241 Upgrading the card firmware About this task This process creates the folder structure on the SD card and copies the firmware files from those installed with Manager onto the SD card This includes the binary files for the B5800 Branch Gateway system and any external expansion modules and phones It also includes the prompt files for embedded voicemail operation 56 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com SD card preparation This process can be used to upgrade an existing SD card to match the file set installed with Manager The card installed in the System SD slot must be an Avaya SD Feature Key card The card must be correctly formatted If the card contains any dynamic system files for example SMDR records they are temporarily backed up by Manager and then restored after the card is recreated Procedure 1 Insert the SD card into a card reader on the Manager PC Note Do not remove the SD card Removing the SD card will interrupt the upgrade 2 Using Manager select File gt Advanced gt 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
317. perated in a commercial environment This equipment generates uses and can radiate radio frequency energy and if not installed and used in accordance with the instruction manual may cause harmful interference to radio communications Operation of this equipment in a residential area is likely to cause harmful interference in which case the user will be required to correct the interference at his or her own expense Canadian department of communications DOC NOTICE This equipment meets the applicable Industry Canada Terminal Equipment Technical Specifications This is confirmed by the registration number The abbreviation IC before the registration number signifies that registration was performed based on a Declaration of Conformity indicating that Industry Canada technical specifications were met It does not imply that Industry Canada approved the equipment 266 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Regulatory Instructions for Use EMC caution for china am B AMA EERIE aS MAKATI ERMA Dam eA AMAT FARRIS ATA EE MEAFAR Regulatory Instructions for Use Australia BRI interface During the configuration ensure 000 emergency number is not barred by performing the following e Short Code 000 e Telephone No 000 e Function DialEmergency Connections to TS013 the following bearer capabilities shall not be used 7kHz Audi
318. plementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Creating an endpoint template Under Supported B5800 Branch Gateway Types click the check box for B5800 Click Show List All templates appear in the Templates List 5 Select the template you want to apply and then click Apply 6 From the B5800 Branch Gateway Devices list select the B5800 Branch Gateway s to which you want to apply the template Do one of the following e Click Now to run the job now e Click Schedule to run the job at a scheduled date and time Creating an endpoint template Procedure 1 2 From the System Manager console under Services select Templates On the Templates page in the left navigation pane click B5800 Endpoint 3 On the B5800 Branch Gateway Endpoint Templates page do the following o N DO OO A 10 a Under Supported B5800 Branch Gateway Types click the check box for B5800 b Under Templates List click New Inthe Name field enter a name for this endpoint Inthe System Type drop down box select B5800 Inthe Set Type drop down box select the appropriate set type Inthe Version drop down box select 6 2 To configure more details for this endpoint click the Details button The IP Office Manager applet is launched On the Warning Security page click the check box to Always trust content from this publisher and t
319. plicated or deleted 14 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Management e 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 e Upload and convert audio files to System Manager to be used in the B5800 Branch Gateway System Configuration Auto Attendant feature e Manage B5800 Branch Gateway system configurations From System Manager you are able to launch IP Office Manager to view or edit a system configuration With this feature you make changes to the B5800 Branch Gateway device through System Manager You are able to apply the changes immediately or schedule the changes to run at a specified time e Manage B5800 Branch Gateway security configuration From System Manager you are able to launch IP Office Manager to view or edit a system security configuration With this feature you make changes directly to the B5800 Branch Gateway device e Create B5800 Branch Gateway user templates These templates can be edited or deleted e Perform a B5800 Branch Gateway backup with the option of storing the backup output in System Manager or creating a local backup where the system stores the backup output on the local storage attached to the B5800 Branch Gateway device e Perform
320. ppropriate local specific power cord for the power supply unit must be ordered separately e 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 e When connecting to expansion ports on a 4 port expansion card a yellow 2 meter 6 6 expansion interconnect cable can be used in place of the standard blue cable Four yellow cables are supplied with the 4 port expansion card Installation requirements e Installation space either on or under the control unit e Switched power outlet socket Available EXPANSION port on the control unit e Functional grounding requirements connection of a functional ground is recommend for all modules mandatory for analog trunk modules e Protective grounding requirements connection of a protective ground via surge protection equipment is mandatory for analog trunk modules in the Republic of South Africa mandatory for digital station and phone modules connected to out of building extensions mandatory for digital station V2 and phone V2 modules Tools required e Manager PC e Tools for rack mounting optional Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 69 Hardware and software installation Parts and equipment required e External expansion module each module is supplied with a suitable external power
321. ption is the 4 port expansion card which can only be installed in right hand slot 4 e It is recommended that cards are fitted from left to right e There are restrictions to the number of supported cards of some types When a limit is exceed the right most card of that type will not function e Ensure that you use the labels supplied to identify the card fitted into the control unit Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 59 Hardware and software installation A Warning e Correct anti static protection steps should be taken before handling circuit boards e Cards must never be added or removed from the control unit while it has power connected Trunk daughter card preparation Trunk daughter cards can be fitted to any base card except the legacy card carrier For combination cards the trunk daughter card is pre installed and cannot be changed A Warning Correct anti static protection steps should be taken while handling circuit boards 60 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Base and trunk card installation Parts and equipment required e Base card except the legacy card carrier e Trunk daughter card e 3 stand off pillars these are supplied with the trunk daughter card Tools required e 5mm Flat blade screwdriver e Anti static wrist strap and ground point Installing a
322. r R6 2 must be installed and configured at the headquarters location e If you are going to centrally manage the B5800 Branch Gateways Avaya Aura System Manager R6 2 must be installed and configured at the headquarters location e If you are going to use centralized licensing by WebLM an Avaya Aura System Manager WebLM server or a standalone WebLM server must be installed and configured The WebLM server can be located at the headquarters location or anywhere in the network as long as the B5800 Branch Gateways can access it on the network A stand alone Secure Access Link SAL Gateway R2 0 or higher must be deployed Note System Platform s virtual SAL gateway is not supported Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 35 Planning Dial plan considerations A uniform dial plan greatly simplifies configuration management and phone calls within the network branch sites For example if each branch has similar roles such as reception manager and warehouse using the same extension number for each role and a unique prefix for each branch allows calls between sites with little need for directory lookups It also means a standard configuration can be used at branches simplifying installation user training and maintenance For our examples we have used the following dial plan for each branch site e 3 digit branch prefixes beginning with 8 A 3 digit branch prefix in the ran
323. r an Avaya Aura Configuration October 2012 Firewall policie S ornon na snuatbarinten Ta a 278 TF POTO I aa T 278 Ingress ports for B5800 Branch Gateway and SIP phones iisiicicseirisassinireicindidisernnniienniiiidiaraiieindaiiiai 279 Egress ports for B5800 Branch Gateway and SIP phomes ccs cescessseseneeeeseeesneseeceeseneeesneeeenenseaeess 281 Table Col riny heading Jeimition Sessea EAN rR 283 ee cigMh ciate Bo i osa OO 285 Appendix B B5800 Branch Gateway Call flOWS ccssseeeeeeeeeeeeeneeeeeeeeeeeeeeeeeneeeeeenees 287 Appendix C Branch PSTN call routing CXamMples cccccssseeeeeeeeeeeeeeeeeeeeeeeeeseeeeeeeeenenees 289 eo e a ekal Bass Ue EAA tere mtr tater E E A nea teen renin T mney IN ttre rere Teen reer NT 289 Routing B5800 Branch Gateway calls example sc i ccs coecticcecssertccsesescy cactieneuetan aiai 290 ESPINER E siai S 292 POAN SAA Pra HAUT ona oe neva od em tnpaeecpne eked edocs dense pita duoke dans deuetnnked beakeehash Staeepnbideaoiebnnt ees 292 Peel IN ANAC Kea E EAE ames 294 CITES FOIN Tunk AMICK 2 sacs c 22 etecenccesesnaddesst E ER aia 295 Appendix D Authorization COMES oivcsiniccresaasccaiasasssasecananumanneicadsonicnsacdaddaadadniasasnonbcsananubenne 299 knabino authorization codes in WITS acsiicscccinsdudcceedeuiaddacneseusadeactntieisadsetuaneninddeteoneuidsmeewaneddaierteninlesa 300 Fore authonzalo n COE Eiin a a 301 About entering an authorization COE sissie i aat ie aian 301
324. r install telephone jacks in wet locations unless the jack is specifically designed for wet locations e Never touch uninsulated telephone wires or terminals unless the telephone line has been disconnected at the network interface e Always use caution when working with telephone lines 264 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com 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 PRI E1 PRI T1 ATM4 WAN BRI Single Dual Single Dual Control x x x J J J x unit Rest of World Product Quad PRI E1 E1R2 PRI T1 ATM4 WAN BRI Single Dual Single Dual Control vi vi x x J x unit Note E1R2 trunks are only supported in CALA and Korea Port safety classification The B5800 Branch Gateway systems have the following ports which are classified as follows Port Name Port Description Port Classification PRI port PRI ISDN connection NET TNV Operating within the limits of SELV BRI ports BRI ISDN connection NET TNV Operating within the limits of SELV Analog ports Two wire analog trunk TNV3 Power fail ports Two wire analog trunk TNV3 DTE port Async Data connect
325. r the instructions supplied with the device The ground points on the control unit and the DS modules must be connected to a protective ground using 18AWG wire with a green and yellow sleeve Typically the IROBs 2 RJ45 EQUIPMENT ports are straight through connected to the 2 RJ45 LINE ports This allows existing RJ45 structured cabling using pins 4 and 5 to be used without rewiring for up to two DS connections However each of these ports can be used to connect a second extension using pins 3 and 6 Main Building Primary _ Protection Boxes DS Module a Earthed Ducted Approved Ground Paint Cabling eh ee Secondary Building DS 2 co Approved Ground Point A Digital Station LINE Signal EQUIPMENT athe 1 Not used 1 ides t 2 Not used eran E 2 4 3 Ring Il u 3 Optional p E 4 Ring 2 4 Tip 6 Tip Il 6 Optional 7 Not used 7 8 Not used 8 74 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration Comments infodev avaya com October 2012 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 A Warning PHONE POT ports on the front of control units must not be used for extensions that are ex
326. ra Configuration October 2012 219 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 A Caution In installations where this port is connected to a device external to the building connection must be via a towerMAX SCL 8 Surge Protector and a protective ground connection must be provided on the B5800 Branch Gateway control unit EXT O P Pin Description Switch2 1 Switch 1 EXT o P 2 Switch 2 2 3 O E 3 Sni s tereo i Jack Plug 3 0 Volts Ground Chassis Switch 1 e Switching Capacity 0 7A e Maximum Voltage 55V d c e On state resistance 0 7 ohms e Short circuit current 1A e Reverse circuit current capacity 1 4A Ensure that pins 1 and 2 are always at a positive voltage with respect to pin 3 3 5mm stereo audio jack plugs are frequently sold as pre wired sealed modules It may be necessary to use a multi meter to determine the wiring connections from an available plug Typically 3 common to both relays is the cable screen 220 Implementing the
327. rate a default configuration file See Booting from the SD Cards on page 244 for more information e Once each day approximately between 00 00 and 00 30 the B5800 Branch Gateway will copy the current configuration running in its RAM memory to the primary folder on the card e Configuration changes made using Manager are first written to the copy of the configuration file on the card and then merged with the configuration running in the system s RAM memory e The write lock setting on cards in the System SD card slot is ignored Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 241 SD card management Optional SD card slot e Acard does not have to be present in this slot for normal B5800 Branch Gateway operation The slot can be used for various maintenance actions e Acard 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 e The full contents of the System SD card can be copied to the Optional SD card while the B5800 Branch Gateway system is running e The write lock setting on cards in the Optional SD card slot is honored A 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
328. ration October 2012 Comments infodev avaya com Network assessment for VoIP requirements Network assessment for VoIP requirements B5800 Branch Gateway is a converged telephony system that is it combines aspects of traditional PABX telephone systems and IP data and telephony systems This works at various levels e Individual phone users can control the operation of their phone through applications running on their PC e Data traffic can be routed from the LAN interface to a telephony trunk interface for example a dial up ISP connection e Voice traffic can be routed across internal and external data links This option is referred to as voice over IP VoIP The VoIP mode of operation can include IP trunks between customer systems and or SIP telephones for users In either case the following factors must be considered e The B5800 Branch Gateway control unit must be fitted with voice compression channels These channels are used whenever an IP device trunk or extension needs to communicate with a non IP device trunk or extension or a device that uses a different codec e Anetwork assessment is a mandatory requirement for all systems using VoIP For support issues with VoIP Avaya may request access to the network assessment results and may refuse support if those are not available or satisfactory A network assessment includes a determination of the following e A network audit to review existing equipment and evaluate its
329. re files and embedded voicemail prompt files Depending on the files that need to be updated this can take up to40 minutes Upgrading the SD card locally About this task You can upgrade the SD card locally if you have physical access to the control unit This method should be used with a timed reboot allowing the card upgrade to be done during normal operation hours followed by a reboot outside of normal operation hours See Rebooting the system on page 208 for more information If the card is being used for embedded voicemail that service is not available while the card is shutdown Licensed features however will continue running for up to 2 hours while the card is shutdown Procedure 1 Shutdown the System SD card and remove it from the control unit See Memory card removal on page 259 for more information 2 Create the SD card See About creating a B5800 Branch Gateway SD card on page 246 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 257 SD card management O oa A O 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 Reinsert the card into the System SD card slot on the control unit Using Manager select File gt Advanced gt Reboot Inthe Select IP Office window select the appropriate system and click OK
330. re these substances may be found in Avaya s electronic information products as of the date of manufacture of the enclosed product Note that some of the component types listed above may or may not be a part of the enclosed product eee ee ee NAR Fe AY GR AE A MU BRN FER EB m ba RRA mE 505 an At PPR TE REP EA The Environmentally Friendly Use Period EFUP for all enclosed products and their parts are per the symbol shown here unless otherwise marked Certain products have a different EFUP for example telephones and so are marked to reflect such The Environmentally Friendly Use Period is valid only when the product is operated under the conditions defined in the product manual Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration ong yoy Part Name Pb Hg Cd Cr PBB PBDE October 2012 269 Safety and regulatory information European Union e 999 and 112 calls must not be barred Doing so will invalidate the approval e All connections at the MDF shall be identifiable by suitable labeling e The CE mark displayed on B5800 Branch Gateway equipment indicates the systems compliance with the EMC LVD and R amp TTE Directives and common technical regulations for Primary Rate and Basic Rate ISDN All ports for the connection of other non telecommunications apparatus have a Safety Extra Low Voltage SELV safety status New Zealand The grant of a Telepermit for any item of ter
331. red from 49152 through 65535 The well known and registered ports are assigned by IANA Internet Assigned Numbers Authority and are found at http Awww iana org assignments port numbers Well known ports For the purpose of providing services to unknown clients a service listen port is defined This port is used by the server process as its listen port Common services often use listen ports in the well known port range A well known port is normally active meaning that it is listening for any traffic destined for a specific application For example well known port 23 on a server is actively waiting for a data source to contact the server IP address using this port number to establish a Telnet session Well known port 25 is waiting for an email session etc These ports are tied to a well understood application and range from 0 to 1023 In UNIX and Linux operating systems only root may open or close a well known port Well known ports are also commonly referred to as privileged ports Registered ports Unlike well known ports these ports are not restricted to the root user Less common services register ports in this range Avaya uses ports in this range for call control Some but not all ports used by Avaya in this range include 1719 1720 for H 323 5060 5061 for SIP 2944 for H 248 and others The registered port range is 1024 49151 Even though a port is registered with an application name industry often uses these ports for
332. rent cerrentce tres encetr errr cere errr Temes et 248 About backing up the System SD Cat sccicisccccsscssctccacnsmssdacaemsmetasaesadhaanyscinns cammestenesdanminncoagaanmarenenecnsams 248 Backing up the primary folder using MANAGE aossriisnsiisneneiaaae 249 Backing up the primary folder using the System Status application eee eee eee eeeeeeeeeeneees 249 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 9 Backing up the primary folder using a system PhONe ecceeceeccceeeeeeeeeeeenereeeeeenereeeeneneneeeeetenees 250 About restoring ren Tie Backup folde ssicnrisnodinle nial abo a ise 250 Restoring rom the backup folder USING MaMa Glo ccccciacc ccc sessccodstcdearuiaseasevacdearaianneuisdddernawannnoiaudes 250 Restoring from the backup folder using the System Status application cccceeeeeeeeereeeeeeeees 251 Restoring from the backup folder using a system PhONe csccceeeeeeeeeseeceeeeeeeeenseneeeeeeeeeeseeenane 251 About baching up te The Opional SD ea assinar ies ana mensin iene 252 Backing up to the Optional SD card using MAN BGG siccicusnissssvecncexarssesneencsnddnertrcovauduiduateinennondadecie 252 Backing up to the Optional SD card using the System Status application cccceeeeeeeeeeeeeeeees 252 Backing up to the Optional SD card using a system PhONe eee eeeeeeeeeeeeeeaeeseeeesenaeeeeeeee 253 About restoring from the Optional SD Gare hssvaccccc
333. rning appears it is most likely due to a conflict with an existing use of that extension number Do one of the following e Click Cancel to return the user to their original extension number e If you are planning to change the other extension number click OK and then edit the other entry Manager automatically propagates the number change to any hunt groups incoming call routes user buttons bridged appearance buttons and call coverage appearance buttons associated with the user s original extension number If the user has an extension with which they are associated by being the extension s Base Extension setting that setting is not automatically updated If the user should still be associated with that extension by default the extension must be updated manually to match the user s new extension number 5 To update the user s Base Extension setting select Extension 6 On the Extn tab in the Base Extension field change the base extension number to match the user extension who should now be associated with that extension port by default 7 Click OK Note If a validation error message appears due to a user being associated with two extensions ignore the message until all the user moves have been completed 8 Repeat steps 2 through 7 for each user whose extension number you need to change 214 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com 10
334. roducts are available on the B5800 Branch Gateway Application DVD i A Warning This warning symbol is found on the base of B5800 Branch Gateway modules e Refer to Trunk Interface Modules on page 265 for information concerning which trunk interface module variants are fitted in which country In Finland Norway and Sweden a protective earthing conductor must be attached to the protective earth point on the rear of the servers See Grounding on page 71 for more information In addition the server must be located in a restricted access location where equipotential bonding has been applied for example in a telecommunication center Important safety instructions when using your telephone equipment When using your telephone equipment basic safety precautions should always be followed to reduce the risk of fire electric shock and injury to persons including the following e Do not use this product near water for example near a bath tub wash bowl kitchen sink or laundry tub in a wet basement or near a swimming pool e Avoid using a telephone other than a cordless type during an electrical storm There may be a remote risk of electric shock from lightning Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 263 Safety and regulatory information Do not use the telephone to report a gas leak in the vicinity of the leak e Use only the power cord and batteries indicated in this manual
335. roller gt Session Manager B5800 Branch Gateway B5800 Branch Gateway auto attendant caller enters extension number gt local phone Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 287 B5800 Branch Gateway call flows 288 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com 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 e Centralized call control on page 289 External calls at a branch site can be rerouted to be dialed out at another site This can be done for reasons of call cost and call control For example the central site may have a bulk call tariff for national and international calls that would benefit all branches e Branch PSTN Override on page 292 Having configured the branch to send outgoing external calls to the Avaya Aura Session Manager for onward routing there may be cases where a specific number should still be routed via the branches own PSTN trunks e PSTN Fallback on page 294 The B5800 Branch Gateway can be configured to allow some calls that would normally u
336. rom System Manager on page 157 174 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Configuring Standalone Voice Mail 2 In the left navigation pane click System 3 Click the Voicemail tab 4 In the Voicemail Type drop down box select Standalone Voice Mail Note Fields applicable to this mode of voicemail support are enabled If the field is not applicable the field is disabled 5 If you want the users to be presented with a display menu for access to their mailbox check the Messages Button Goes to Visual Voice check box For more information see the IP Office Manager on line help 6 In the Voicemail IP Address field enter the IP address of the Linux server where Standalone Voice Mail is installed 7 Inthe Minimum Password Length field use the up and down arrows to set the appropriate minimum password length 8 In the Maximum Record Time field use the up and down arrows to set the maximum record time in seconds for recorded announcement and auto attendant prompts 9 In the VoiceMail ports field use the up and down arrows to set the number of voicemail ports This field must match the number of voicemail ports that are licensed for the system 10 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
337. s and allows them to quickly see the status of the callers required destination and transfer the call The SoftConsole user is able to access a range of details about the status of users and groups on the B5800 Branch Gateway system Up to 4 simultaneous SoftConsole users can be configured This application does not require a license e Installer maintainer applications The following B5800 Branch Gateway applications are used to program and maintain a B5800 Branch Gateway system These applications do not require a license Manager a configuration application 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 Manager is also used to upgrade the software files used by a B5800 Branch Gateway system 26 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com 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 installers and maintainers must run Syst
338. s 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 1 Note Perform the following procedures View the SIP domains for which the Session Manager provides call management Multiple domains can be listed See Viewing the SIP domains on page 166 Identify logical and or physical locations where SIP entities reside IP address patterns can be used to define different locations within the Avaya Aura network for example the IP address range of each B5800 Branch Gateway system The creation of locations allows features such as bandwidth management to be applied to connections from those locations See Creating locations on page 166 Create a set of digit adaptations in order to ensure correct routing If the digits to or from a branch need alteration in order to be routed correctly at either end this can be done using a table of digit adaptations Each SIP entity branch is associated with its own set of digit adaptations See Creating adaptations on page 167 Add each B5800 Branch Gateway system to the list of SIP entities that send calls to and from the Avaya Aura network See Creating SIP entities on page 167 Add an entity link for each SIP entity including each B5800 Branch Gateway An entity link must be added to define the ports and transport method used
339. se 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 these examples can be combined to match the customer s needs However the main aim should be as follows e To keep the branch configuration as generic as possible i e to use the same PSTN call control in all branch configurations This simplifies maintenance of multiple branches e To centralize as much of the PSTN call control in the Avaya Aura Session Manager as possible Again this simplifies maintenance and control Centralized call control External calls at a branch site can be rerouted to be dialed out at another site typically the headquarters site This can be done for reasons of call cost and control and to reduce the external PSTN capacity required at the individual branch sites For example we can route all national and international calls to the headquarters site to benefit from a bulk cost reduction available for calls from that site The Avaya Aura Session Manager there routes the calls out via PSTN services at that site Note however that the Avaya Aura Session Manager could alternately use the trunks at a branch for some calls For example if the national call is to an area code that is local to a particular branch the call could be routed to that branch for dialing on its PSTN trunks Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configurati
340. sendstnqonadiehuseceniecvaansiesnduanaveds 276 SOMWANC sanii naa O ONN 235 erasecore SOf Ware essesesssissssrrrrrrrrrirrrirresesesee 235 Software applications c cecccseeeeeseeeeeeeeteeeseetaeees 26 Space requirements cceeeecseeeeeeeseeeeeeeteeeeeeessnaeess 48 Statement srra nu 263 Homologation 1 0 ceecseeeeseeeeeeeeseeeeeeeesesseeeeeeeess 263 SGU LY I A I E canetewete A E A 263 SUPPOMEG sciuird easain aaia ianea 27 language enna heshatieeeeaatinivieseneacnets 27 localo S onanoi aade a eaae 27 312 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration supported telephones ceceeeeeeeeeeeeeeeeeeteeaeeeeeeees 23 Synchronizing B5800 Branch Gateway with System Managen sistic nean aa nia 162 System components eceeeeeeeeeeeeeeeeeeeeceeeeeeeeeeetaeees 20 System Manager administration feature disabling from IP Office Manager ccccseeessceeeesseetteeeeees 160 System Manager administration feature disabling using System Manager cecceeeceeeeeeeeeeeeeeeeeaees 160 system requirements 00 00 eee eee eeeeeeeeenteeeeeeeeeeeeaaeees 98 system requirements for the external server 98 System shutdown using Manager seeeeees 206 System tab field descriptions cccceeeesssseeeeeees 141 T Tail ENd HOp Off ccceccceeeesseceeeeeeeeeeesesnenaaees 38 289 TET P port USAQ 6i sinceniscerndiet teeters 278 Time range add
341. session If codec lockdown is enabled when the system receives an SDP answer with more than one codec from the list of offered codecs it sends an extra re INVITE using just a single codec from the list and resubmits a new SDP offer with just the single chosen codec 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 Prioritization of the Session Manager lines is determined by the line number configured for a particular Session Manager line For example if the first Session Manager line is configured with line number 17 and the second Session Manager line is configured with line number 18 then line number 17 has the higher priority and is considered the primary Session Manager line If for some reason you want to designate the secondary Session Manager line as the primary line you must change one or both of the line numbers associated with the Session Manager lines so that the secondary Session Manager line number is lower than that of the primary line The redundancy operation of the Session Manager lines is based on line prioritiza
342. splay Name field enter the user s full name In the Title field enter the user s title if applicable In the Language Preference drop down box select the appropriate language In the Time Zone drop down box select the user s time zone In the Employee ID field enter the user s employee ID In the Department field enter the user s department In the Company field enter the name of the user s company To add a postal address for this user do the following oP 223 i Expand the Address section ii Click New iii On the Add Address page complete the fields as appropriate r To add multiple phone numbers for this user do the following i Expand the Phone Details section ii Complete the fields as appropriate iii Click Add To specify a localized language expand the Localized Names section and do the following a Inthe Language drop down box select the language for displaying the user name b Inthe Display Name field enter the user s name c Click Add To add a TDM or IP endpoint or a distributed SIP endpoint such as an 11xx 12xx SIP phone click the Communication Profile tab Accept the default values for the Communication Profile Password field Confirm Password field Name field and Default check box Click the B5800 Branch Gateway Endpoint Profile check box and do the following a Inthe System drop down box select the appropriate system b Check the Use Existing Extension check
343. t a A O N Double click on setup exe Insert the B5800 Branch Gateway R6 2 Administrator Applications DVD Select B5800 Branch Gateway Administration Suite Select the language you want to use for the installation process This does not affect the language used by Manager when running 90 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration Comments infodev avaya com 12 13 14 Upgrading the administration applications Click Next Select who should be able to run the Administration Suite applications Click Next If required select the destination to which the applications should be installed It is recommended that you accept the default destination Click Next The Custom Setup window appears Select the applications that you want to install Ata minimum select System Monitor and Manager When you select an application a description of the application appears Click on the next to each application to change the installation selection Click Next Click Install Installation of Windows Net2 components may be required If dialogs for this appear follow the prompts to install Net If requested reboot the PC Enabling secure communication after upgrading IP Office Manager About this task If an older version of IP Office Manager is installed and you cannot connect to the B5800 Branch Gateway after IP Office Manager has been upgraded y
344. t The Custom Setup window appears Select the applications that you want to install Ata minimum select System Monitor and Manager When you select an application a description of the application appears Click on the next to each application to change the installation selection Click Next Click Install Installation of Windows Net2 components may be required If dialogs for this appear follow the prompts to install Net If requested reboot the PC Installer PC connection During installation it is recommended that the B5800 Branch Gateway control unit be started without it being connected to any network That ensures that the B5800 Branch Gateway defaults to a known set of IP address settings Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 79 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 Change the TCP IP properties of the LAN port on the PC to the following e Fixed IP address 192 168 42 203 e Subnet mask 255 255 255 0 e Default gateway 192 168 42 1 Note While s
345. t channels can be added using VCM base cards BRI combination cards and ATM combination cards See System components on page 20 for more information about these cards The voice compression channels are used as follows 44 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com 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 IP device to IP device Call progress tones for example dial tone secondary dial tone etc do not require voice compression channels with the following exceptions Short code confirmation ARS camp on and account code entry tones require a voice compression channel e Devices using G723 require a voice compression channel for all tones except call waiting When a call is connected If the IP devices use the same audio codec no voice compression channel is used If the devices use differing audio codecs a voice compression channel is required for each Non IP device to non IP No voice compression channels are required device Music on Hold This is provided from the B5800 Branch Gateway TDM bus and therefore requires a voice compression channel when played to an IP device Conference resources and IP Conferenc
346. t also enable the announcements Do this by selecting the check box for Announcements On which appears when you select Hunt Group gt Announcements tab and Users gt Announcements tab 6 In the AAM Number field enter the extension number configured for mailbox access to the Avaya Aura Messaging system Note that this number is automatically routed via the active Avaya Aura Session Manager line It does not need to be routed through the normal branch call routing 7 Inthe AAM PSTN Number field enter the PSTN number to which you want to reroute attempts to access mailboxes when the Avaya Aura Session Manager line s are out of service This field is optional When calls to access voicemail are routed by this method the calls go through the PSTN trunk that is configured on the B5800 Branch Gateway Note The PSTN voicemail number requires a corresponding Short Code entry so that the calls are routed to the correct line during rainy day operation 8 For the Enable Voicemail Instructions Using DTMF check box do one of the following a To send the voicemail instructions as DTMF tones ensure the Enable Voicemail Instructions Using DTMF check box is selected that is checked When this check box is selected the voicemail mail box number of the recipient and the appropriate digit s such as or that are used to leave or collect a message are automatically sent as DTMF tones so the caller does not need to enter those di
347. t to listen for and respond to SNMP traffic The default is 161 Inthe 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 The community public is frequently used to 228 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com SNMP establish communication and then changed at both the SNMP agent and manager ends for security 7 Click OK 8 Select File gt 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 Amaximum of 5 SNMP management stations can be configured as B5800 trap destinations System Manager must be configured as a trap destination When the Initial Installation Utility is used System Manager is automatically configured as a trap destination See Using the Initial Installation Utility on page 121 for more information Procedure 1 Start Manager and connect to the B5800 Branch Gateway system 2 In the left navigation pane click System 3 4 In the Confi
348. t using a power cord with an earth lead the power outlet must be connected to a protective earth In some cases such as ground start trunks in addition to being a protective measure this is a functional requirement for the equipment to operate In other cases it may be a locale regulatory requirement and or a necessary protective step for example areas of high lightning risk A Warning During installation do not assume that ground points are correctly connected to ground Test ground points before relying on them to ground connected equipment Additional protective equipment In addition to grounding additional protective equipment is required in the following situations e On any digital station or phones external expansion module connected to an extension located in another building See Out of Building Telephone Installations on page 72 e In the Republic of South Africa on all analog trunk external expansion modules ATM16 and on any control units containing an analog trunk cards ATM4 ATM4U Tools required e M4 cross head screwdriver e Tools suitable for crimping a cable spade Parts and equipment required e 14AWG solid copper wire for ground connection Cable sleeve matching local regulator requirements Typically green for a functional ground and green yellow for a protective ground The ground point on control units and expansion modules are marked with a rhor symbol Ground connections to these points should use a
349. t valid load the configuration copy in its non volatile memory if present Otherwise the control unit will have a default configuration 244 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com 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 e 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 The normal boot up process of upgrading expansion module firmware does not occur If the File gt Advanced gt Upgrade command is used only external expansion modules actually present in the system are listed for upgrade Post boot operation During normal operation configuration and binary files sent to the System SD card primary folder using Manager are also written to the non volatile memory If the system has booted from its non volatile memory due to an SD card problem it is still possible to upgrade the bin file using the B5800 Branch Gateway upgrade wizard See System upgrade using the System SD card on page 256 for more information Boot alarms The following apply if the co
350. te Id Secondary Dial tone Route Name SystemTone v Dial Delay Time System Default 4 Check User Call Barring In Service Out of Service Route lt None gt v Time Profile Out of Hours Route lt None gt v i Code Telephone Number Feature Line Group Id 11 911 Dial Emergency 0 i Remove 911 911 Dial Emergency 0 ON oN Dial 3K1 o Edit tae 1N 1N Dial 3K1 0 XN N Dial 3K1 o AXAXARARAAN N Dial 3K1 0 Within the ARS window the default ON 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 Inthe Code field leave this set to ON b Inthe Feature field change this to Dial c Inthe Telephone Number field change this to 90N The 9 has been added back as it matches the dial pattern typically used at the Avaya Aura site for matching a call that needs routing to the PSTN d Inthe Line Group ID field change this to match the Avaya Aura Session Manager line Outgoing Group ID The default is 99999 7 Click OK 8 Repeat Steps 4 through 7 for the 1N short code which is used for national calls The branch system s default ARS form is now set to route all national and international calls to the Session Manager line and thus to the Avaya Aura Session Manager Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration Octo
351. ted and stored for persistent use Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 117 Initial branch configuration 5 Select File gt Close Configuration 6 To view the license select File gt Open Configuration Using Embedded File Management to install a PLDS license Before you begin License files have been activated See Activating license entitlements on page 191 About this task Use this procedure to install an individual PLDS license on a B5800 Branch Gateway that is centrally managed by System Manager To use this feature you must rename the PLDS license file to PLDStemp xml The B5800 Branch Gateway will validate the PLDStemp xml file and if the validation succeeds the B5800 Branch Gateway will automatically rename the file to PLDSkeys xml and save it overriding the previous valid license file if any was installed Note When you use Manager to install the license file you do not need to rename the PLDS license file The Manager application automatically renames the PLDS license file to PLDStemp xml See Using Manager to deliver license files to the branches on page 117 Procedure 1 Start Manager 2 Select File gt Advanced gt Embedded File Management 3 Inthe Select B5800 window click the check box next to the B5800 Branch Gateway system 4 Click OK Inthe B5800 Embedded File Management dialog box enter the Service User Password Click OK
352. ted directly to the system You can perform an upgrade from IP Office Manager using the upgrade wizard or the System SD card For more information about these upgrade methods see the following topics e Upgrading the B5800 Branch Gateway using System Manager on page 103 e Using the upgrade wizard on page 217 e System upgrade using the System SD card on page 256 Licensing B5800 Branch Gateway supports centralized licensing by WebLM where a single license file is generated in Avaya Product Licensing and Delivery System PLDS for multiple branches 16 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com 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 This license file contains the host ID of the WebLM server and is managed by the WebLM server Each B5800 Branch Gateway communicates with the WebLM server to request the required license entitlements B5800 Branch Gateway uses the Avaya Aura System Manager WebLM server Two configuration models are supported e WebLM standard licensing mode
353. teeeeeeeeeneeea 172 Paterne a A cet 170 Planning eerirsiseceenainitinsneini iniaiaiai 35 PEDS aiotun a aa 189 190 el01010 UPEAA E E EAE A NEET E 189 PONCY senivideo a i a 169 Polycom video module ccceeeeeeeeeeeeeeeeeeeeeeeaeeees 222 POM aras 168 219 220 230 265 01010 1 AE EA EEEE TA E E E E 219 EXT O P ianen a 220 RS329 DTE oireeni ea aiaa 230 Safety Classification ccccccceesesssteeeeeeessnaees 265 port matrix for B5800 Branch Gateway and SIP phones PEIEE E E E A A AE 275 port type range S sinsi ikinen iin 275 port usage diagram 0 0 ceeeeeeeeeeeteeeeeeeeeeaeeeeeeeeaees 285 Power Supplies 0 cccccceeeeescceeeeeecceeeeeeteaeeeeensaaeees 41 Uninterrupted Power Supply ceeeseeeeeeeee 41 prereg isleS 2 0 eeeecceceeeeesecceeeeeeeeeeeeeeeeeeseeceeeeeenenseeees 35 PFEleQuiSiteS encuen iina inii iia aA AEEA i 35 Protocol onise arae AENA 168 PSTN trunk fallback ccecsessseseeceeeeeeeeeeeaeeaneeees 294 PSTN trunk fallback configuring cccceeeeeeeee 295 PSTN trunking configurations 0 ccccceeeeeeeeeees 13 R R6 2 service pack installation checklist 05 97 Rack mounting Control units cceeeeeesssteeeeeeeeees 44 Recommended COUISES csseseceeeeeeesseeeeeeeeeeeeeeees 303 Red ndanGy cinese iiai e ia 150 regenerate license files nnnosnnnnneeenn eneee ennnen ennenen 197 regenerating a license file 0 2 eeeteeeeeeeente
354. tem Name field enter the appropriate system name 4 For the WAN Interface select LAN1 to connect to the enterprise network A 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 275 5 In the IP Address field enter the appropriate IP address 6 In the IP Mask field enter the appropriate IP mask 7 Inthe Gateway field enter the appropriate gateway Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 121 Initial branch configuration 122 IP Office Manager will create an IP route using this gateway with the selected WAN as the destination 8 In the DHCP Mode section click the radio button for Disabled 9 In the New Administrator Password field enter a new administrator password Inthe New Security Password field enter a new security password Note The New Administrator Password and New Security Password fields appear only when these passwords are set to the default Once you change the default passwords the next time you run the Initial Installation Utility these fields wi
355. tension section of the window select the extension for User A Note If Manager is set to validate edits a warning appears that says this change conflicts with the existing Base Extension setting of another extension Ignore the warning at this stage Click OK 5 In the Extension section of the window select the extension for User B 6 In the Base Extension field change the extension to User A s extension 7 Save the configuration back to the B5800 Branch Gateway system 212 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com 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 An extension entry is created in the configuration and also an associated user entry A similar process occurs when a new extension expansion module is detected Important Extension versus User It is important to understand that extension number is a user setting that belongs to and moves with the user For example a user can login at any phone and
356. ternal to the main building e The correct B5800 Branch Gateway barrier boxes must be used These modules have been designed specifically for the signalling voltages used by the B5800 Branch Gateway system e Only the B5800 Branch Gateway phone barrier box should be used with phone V1 modules e Only the B5800 Branch Gateway phone barrier box V2 should be used with phone V2 modules e No other type of analog phone barrier box should be used e Where more than 3 barrier boxes are required in a building they must be rack mounted using a barrier box rack mounting kit See Rack mounting barrier boxes on page 76 A maximum of 16 barrier boxes can be used with any phone module e The phone barrier box does not connect the ringing capacitor in phone V1 modules Main Building Secondary Building Control Unit fa s C L oon Phone Module f a Barrier Box a o 7 Approved Ground Point Main Building Secondary Building e RJ11 Connect to PHONE POT port on the Phone module using cable supplied with the barrier box e RJ11 Connect to analog phone Cable not supplied e RJ45 From main building v via primary protection in e RJ45 Connect to the both buildings secondary building barrier box via primary protection in both buildings Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 75 Hardware and software installa
357. teway for an Avaya Aura Configuration October 2012 51 Installation requirements 52 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Chapter 4 Hardware and software installation This chapter addresses new installations If you are upgrading a B5800 Branch Gateway system see Upgrading an R6 1 system to R6 2 on page 89 or Upgrading an R6 2 system with an R6 2 service pack on page 97 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 This ensures that the control unit will default to known default IP address settings unless you have pre loaded the System SD card with a configuration file with different settings B5800 Branch Gateway R6 2 provides the B5800 Branch Gateway Initial Installation utility This utility provides a default configuration and security settings that minimize initial installation activities and maximize security The system must be configured with the default settings before the system can be administered by Avaya Aura System Manager This utility is used for new installations and after an R6 1 to R6 2 upgrade to e
358. that phone then temporarily assumes the user s extension number and settings until they log off The Base Extension value set for extensions in the B5800 Branch Gateway configuration indicates the default associated user of the extension It is not the extension number of that port Renumbering all extensions and users About this task Use this procedure to shift all user extension numbers up or down by a set amount Any settings linked to those numbers are adjusted including extension Base Extension settings It does not affect hunt group extension numbers A Warning This procedure alters extension settings and therefore requires a system reboot when the configuration is sent to the B5800 Branch Gateway Procedure 1 Select Tools gt Extension Renumber 2 In the Renumber window in the Value field enter the amount by which you want to shift the current extension numbering of extensions and users 3 Click Add or Subtract as appropriate 4 Click OK Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 213 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 On the User tab in the Extension field change the extension number to the new number Click on another field If an error wa
359. the extension is unassigned or the communication profile is deleted 9 Click Commit A distributed user is added on the B5800 Branch Gateway and is associated with a user in System Manager 10 Repeat this procedure for each distributed user you want to add Editing the B5800 Branch Gateway Endpoint Profile for a user About this task Use this procedure to edit a B5800 Branch Gateway Endpoint Profile for a distributed user Procedure 1 On the System Manager console under Users click User Management 2 In the left navigation pane click Manage Users 3 From the list of users on the User Management page select the user you want to edit 4 Click Edit Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 187 User administration 188 oN O O 10 11 12 13 Click the Communication Profile tab to expand that section Expand the Communication Address section Expand the B5800 Branch Gateway Endpoint Profile To change the extension for this user in the Extension field enter the appropriate extension To apply a different template to this user in the Template drop down box select the appropriate template To change other parameters for this user click the Endpoint Editor button IP Office Manager is launched where you can edit data for this user Update the fields as appropriate Click Save You return to the edit user window in System Manager
360. the branch s PSTN trunks The default is 0 Click OK The ARS now has two short codes that will potentially match external national calls However one is a more exact match for certain calls and therefore will be applied Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 181 Voicemail configuration to those calls ARS ARS Route Id Route Name Dial Delay Time System Default 4 gt Secondary Dial tone SystemTone Vv Check User Call Barring In Service Out of Service Route lt None gt v l Time Profile Out of Hours Route lt None gt v Code Telephone Number Feature Line Group Id 11 911 Dial Emergency 0 i Remove 911 911 Dial Emergency 0 ON ON Dial 3K1 0 Edit 1N 1N Dial 3K1 99999 XN N Dial 3K1 0 ARRKARARASN N Dial 3K1 0 15553800701 N Dial a 7 Click OK 8 Select File gt 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 Note If you are using a system template you can add the audio file to the template to push the audio file down to multiple B5800 Branch Gateway systems Procedure 1 From the System Manager console und
361. this library server as appropriate d Inthe Server Path field enter the full path of the software library location e To use this software library as the default click the Default Library check box f If this software library is remote click the Remote Library check box g Inthe Default Protocol drop down box select the appropriate protocol h Click the HTTP HTTS check box i Inthe HTTP HTTS URL field enter the appropriate URL to the firmware files in Software Library j Depending on the default protocol you selected in step g click on the corresponding tab FTP Configuration SCP Configuration or SFTP Configuration and configure the authentication parameters as required Note Configuring the authentication parameters for the default protocol is mandatory k Click Commit 102 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com 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 e download the firmware files from Avaya PLDS Avaya PLDS will automatically determine if a newer software version than what is currently installed is available If there is a newer version available you can download the newer versio
362. ting a B5800 Branch Gateway system configuration from System Manager on page 157 2 In the left navigation pane click Short Code 3 Click the New icon and select Short Code Short Code Code BXXXXX Feature Dial v Telephone Number 8N Line Group Id 99999 v Locale v Force Account Code C 4 Configure the settings as appropriate See Short Code tab field descriptions on page 153 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 gt Save Configuration 152 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Short Code tab field descriptions Administering a Session Manager line for each branch Name Description Code Enter the number dialed by users that should be matched to this short code Use X wildcards for any single digit Feature Leave this field set as Dial Telephone Number Set this field to match a number that should be passed to the Avaya Aura Session Manager for routing against its dialing pattern matches The N wildcard can be used to match any wildcards in the Code Note Add SS to the entry in this field to have the caller ID passed to the Session Manager line For example if you are entering 8N in the Telephone Number field enter 8NSS Li
363. ting on page 67 for more information If there are no external expansion modules used in the installation the control unit can be wall mounted using a wall mounting kit See Wall mounting on page 65 for more information Cable clearance Clearance must be provided at the front and rear of all modules for cable access Allow a minimum clearance of 90mm 3 5 inches Additional clearance Care should be taken to ensure that the positioning of the modules does not interrupt air flow and other environmental requirements The control unit has ventilation slots at the side that must not be blocked See Environmental requirements on page 47 and Rack space requirements on page 50 for more information Cable access Power cords must not be attached to the building surface or run through walls ceilings floors and similar openings Installation measures must be taken to prevent physical damage to the power supply cord including proper routing of the power supply cord and provision of a socket outlet near the fixed equipment or positioning of the equipment near a socket outlet Control unit When wall mounted a clearance of 500mm is required on all sides The ventilation slots on the rear and sides should not be covered or blocked 48 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Space requirements 445mm 17 5 Clearance 90mm 3 Unit 36
364. tion Main Building Barrier Box Secondary Building e Center screw Connect to main building protective ground Use 18AWG minimum wire with a green and yellow sleeve e 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 e Right hand screw Not used e Right hand screw Connect to ground point on Phone module using ground cable supplied with barrier box The following wires must be kept apart that is the wires cannot be routed in the same bundle e Earth leads from the barrier box to the phone modules e Internal wires for example extension leads going directly to the phone modules e Wires from external telephone going directly to the barrier boxes Rack mounting barrier boxes About this task Where more than 3 phone barrier boxes are used they must be rack mounted The Barrier Box Rack Mounting Kit SAP Code 700293905 supports up to 8 phone barrier boxes Procedure 1 Unscrew the two screws arranged diagonally at the front of each barrier box and use these same screws to reattach the barrier box to the rack mounting strip 2 Each barrier box is supplied with a solid green ground wire connected to its functional ground screw Remove and discard this wire 3 Connect a green yellow ground wire to the protective earth screw in the center of the point on the bac
365. tion The active line to which B5800 Branch Gateway sends all calls is always the highest priority Session Manager line in service If the primary Session Manager line is in service it is the active line for sending calls If the connection to the primary Session Manager line is lost causing B5800 Branch Gateway to switch to the secondary Session Manager line when the primary line comes back up B5800 Branch Gateway will switch back to the primary B5800 Branch Gateway line If all available channels of the current Avaya Aura Session Manager line are in use the B5800 Branch Gateway will not overflow calls to the other Avaya Aura Session Manager line 150 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Administering a Session Manager line for each branch However if PSTN trunk fallback has been configured the other Avaya Aura Session Manager line will be used See PSTN trunk fallback on page 294 for more information Avaya Aura Session Manager line service status checks The B5800 Branch Gateway system sends regular SIP OPTIONS messages to any Avaya Aura Session Manager lines in its configuration The Proactive and Reactive settings on the B5800 Branch Gateway system s System tab set how often the SIP OPTIONS messages are sent in seconds The Proactive setting is used for an Avaya Aura Session Manager line currently thought to be in service The Reactive setting
366. to the B5800 Branch Gateway system In the left navigation pane click System 3 On the System tab in the Name field enter a distinctive name for this B5800 Branch Gateway system 4 Click OK 5 Click the LAN1 tab 6 On the LAN Settings sub tab do the following a Change the IP Address to match the customer requirements b Change IP Mask to match the customer requirements c Change DHCP Mode setting to match the customer requirements These settings are used for the LAN port on the back of the control unit 7 Click OK 8 Click the LAN2 tab On the LAN Settings sub tab do the following a Change the IP Address to match the customer requirements b Change IP Mask to match the customer requirements c Change DHCP Mode setting to match the customer requirements These settings are used for the WAN port on the back of the control unit Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 203 Additional system procedures 10 11 12 Click OK Select File gt Save Configuration 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 lower right section of the window Then in the left navigation pane in the Contents tab select Secur
367. 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 mib AdminCD snmp_mibs Standard folder on B5800 Branch Gateway Admin DVD rfc2213 integrated services mib mib AdminCD snmp_mibs standard folder on OpenView Install CD diffserv dscp tc mib AdminCD snmp_mibs Standard folder on B5800 Branch Gateway Admin DVD diffserv mib hpov mib AdminCD snmp_mibs Standard folder on B5800 Branch Gateway Admin DVD ipo phones mib mib AdminCD snmp_mibs IPOffice folder on B5800 Branch Gateway Admin DVD 2 Start the OpenView Network Node Manager console 3 Select Options and then Load Unload MIBs SNMP 4 Select Load and select all the MIB files listed above 5 Select Compile 226 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Castlerock SNMPc 5 1 6c and earlier Procedure SNMP 1 Copy the following MIB files to the application s MIB folder This folder is typically C Program Files SGNMPc Network Manager mibfiles MIB file Source ENTITY MIB AdminCD
368. to use Avaya Aura Messaging for voicemail 176 Configuring B5800 Branch Gateway to use Modular Messaging over SIP for voicemail 0008 178 Modular Messaging and Avaya Aura Messaging PSTN Falllb ck cee eeceeseeeeeeeeeeeeneeeeneeeneeeeeeeeneees 180 Adding an OVERICINIG SHO COE erreseina erro aaa E E EE SEa 180 Uplbading an su atendant NN Eaa a a a S 182 Chapter 12 User admimistrati Ni sensin 185 Adding distributed users to System Maragal oc aseedesecss sid ea a a a 185 Editing the B5800 Branch Gateway Endpoint Profile for USCM ee eeeeesneeeeeeeeeeeteeeeeeeoneeeeeeeeeeeneess 187 Chapter 13 Managing license files with PLDS c cccsseeeeeeeeeeeeeeeeeeeeeeeeeeseeeeeeeeneeees 189 gE CN one re eee ere Pec ree ere Pee er meen err ere errr erecer ect Terre trrnrrer st netrere err reee recrr reece rere rer 189 Registering for PLO Seireniconndsannsia a aa a aa 190 Aopo eeno ae a S a a a e 190 AENVATING license entie menice nana EEE 191 Searching To license enmtiemernis nicissarii ia aAA NAA iA aA N a EEDE 193 Moving activated license entifemeniS enie Ai 195 Regenerate License eSa a E iE 197 Peer AIG a censa MB Y 3 2s veces eacradesenrccteateduen a ea ERa 197 Chapter 14 Standalone SAL Gateway for remote SCrviCe ccccceceeeeeeeeeeeeeeeeeeeeeeeeeees 199 Use of SAL to access the B5800 Branch Gateway administration tools and System Managet 199 SAL Galeway Installation and registral ihesea
369. tring is checked against the short codes with the matching user or user rights If it matches a dial short code or no short code the call is allowed Otherwise it is blocked Note that the short code is not processed it is just checked for a match If multi tier authorization codes are required there must be blocking busy short codes or a wild card Example A restaurant has a number of phones in publicly accessible areas and wants to control what calls can be made from these phones They want these phones to allow anyone to make local calls restrict restaurant staff to local and cell phone numbers 044 and allow the manager to also be able to call long distance numbers 01 The following table shows how this is configured ARS Table Authorization Codes In the Main 50 ARS table the following short codes The following two authorization codes are are added configured 044XXXXXXXXXX 044N Dial Force Auth Code 2008 is associated with a set of User Rights called Cell O1XXXXXXXXXX 01N Dial Force Auth Code e 1983 is associate with a set of User Rights called LDandCell User Rights Cell LCandCell Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 299 Authorization codes ARS Table Authorization Codes e 044N Dial e 044N Dial Allows calls to cell phone numbers Allows calls to cell phone numbers e O1N Bus
370. trunk daughter card Procedure 1 Check that correct cards have been supplied 2 Ensure that you are wearing an anti static wrist strap connected to a suitable ground point 3 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 Using minimal force and checking that the pins are correctly located push the trunk card onto its connector block and the stand off pillars 7 Check that the card connector has snapped into position 8 Using the washers and screws provided secure the metal stand off pillars to the base card 9 From the set of labels that are supplied with the trunk daughter card fit the appropriate label to the front of the base card Legacy carrier card preparation A legacy carrier card can be used to fit VCM cards into the B5800 Branch Gateway control unit Up to 2 legacy carrier cards can be inserted The following trunk and VCM cards are supported Cards not listed are not supported Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 61 Hardware and software installation PRIT1 e PRI 30 E1R2 RJ45 VCM4 Dual PRI T1 Dual PRI E1R2 RJ45 VCM 8 e PRI 30 E1 1 4 BRI 8 UNI e VCM 16 Dual PRI E1 ANLG 4 UNI US
371. trunks 36 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Voicemail considerations Modular Messaging at the headquarters site provides voicemail services to all employees The LAN on each branch has a unique IP address 192 168 42 1 192 168 44 1 and so on National calls are made via the branch s PSTN trunks when the branch data connection to the headquarters site is not available or at maximum capacity 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 For calls in other locales or between branches in different locals the example will need to be adjusted to ensure that the resulting number received at the remote branch will be routed to an external PSTN trunk and is suitable for external dialing Voicemail considerations The B5800 Branch Gateway system uses its Embedded Voicemail by default However a number of other voicemail options are supported Embedded Voicemail Embedded Voicemail uses the system SD card in the B5800 Branch Gateway system control unit for storage of prompts and messages Embedded Voicemail supports mailboxes for all local extension numbers announcements to waiting callers and auto attendants up to 40 for external calls Its capacity is limited to 15 hours of recorded messages prompts and an
372. unk e Green on card fitted e Green flashing trunk in use BRI trunk e Off no trunk present e Green on trunk present e Green flashing trunk in use PRI trunk e Off no trunk present e Green on trunk present e Green flashing trunk in use e Red green fast flash port 9 or greenfast flash port 10 alarm indication signal AIS from the trunk remote end e Red with green blink port 9 or green blink port 10 port in loopback mode set through System Monitor 84 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com External expansion module LEDs Default configuration External expansion module All modules e Green on module okay e 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 1 192 168 43 1 IP mask 255 255 255 0 255 255 255 0 DHCP mode server server Number of DHCP IP 200 200 addresses e Extensions and users An extension is automatically created for each physical extension port detected in the system Extension numbers start from
373. ura Configuration October 2012 Comments infodev avaya com B5800 Branch Gateway SD card on page 246 card and copy a set of B5800 Branch Gateway software files into those folders Procedure Description Manage System System Minut r Status Phone es Manager on page 257 Viewing the card View the folders and files on the control unit v contents on memory cards page 248 The following procedures can be performed on cards in an SD card reader on a PC running Manager Formatting an SD Reformat a card for B5800 Branch lt 4 v 1 card on page 246 Gateway use without removing the Feature Key serial number A Caution This process will erase all existing files on the card About creatinga Create the folder structure on a memory J 15 Card specification Non Avaya cards can be used in the Optional SD card slot as long as they match or exceed the following standard SDHC 4GB minimum Class 2 Single partition FAT32 format SD card folders The System SD card contains the following folders primary contains the firmware files for the control unit external expansion modules and supported phones The folder can also contain music on hold files and license key files This is the main set of files used by the B5800 Branch Gateway system when booting up It also contains the stored copy of the B5800 Branch Gateway configuration
374. ura Configuration October 2012 253 SD card management A 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 gt 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 gt Upgrade Configuration The configuration file config cfg and licenses file keys txt in the primary folder on the Optional SD card are copied to the primary folder on the System SD card This takes a few seconds When the process has been completed the B5800 Branch Gateway system is restarted Restoring a configuration file from the Optional SD card using a system phone About this task A user configured as a system phone user can perform this procedure using a 1400 1600 or 9600 Series phone excluding XX01 XX02 and XX03 models The user s login code is used to restrict access to system administration functions on the phone Procedure 1 Select Features gt Phone User gt System Admin 2 Enter your B5800 Branch Gateway user login code 3 From the menu select Memory Card 4 Select Upgrade Config The configuration file config cfg and licenses file keys txt in the primary folder on the Optional SD card are copied to the primary
375. ure Park and Page can be configured for a user s voicemail mailbox or for calls answered by the auto attendant The Park and Page feature is available with Embedded Voicemail and Standalone Voice Mail If Avaya Aura Messaging or Modular Messaging over SIP the two central voice mail systems are configured as the voicemail system with Embedded Voicemail or Standalone Voice Mail configured for auto attendant operation the Park and Page feature can be configured for calls answered by the auto attendant The Park and Page feature allows a call to be parked while a page is made to a hunt group or extension A caller can press a digit and the call is parked while an announcement is made to a paging zone overhead paging system or both The page is repeated based on how the feature is configured until the parked call is picked up or the park timeout occurs If the park timeout occurs the caller hears the Park and Page error prompt and is then returned to the call flow that initiated the Park and Page and hears either the subscriber s personal greeting or the auto attendant main menu prompt The called party can use a short code or a programmed button on their phone to park and unpark incoming calls For more information about short codes and button programming see the Manager on line help The called party can also use the Conference button or the Answer soft key on their phone while the Page is occurring The procedure to configure Park and Page is pro
376. vaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com 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 gt Emulation TTY DTE cables These cables are used for system maintenance and diagnostics under Avaya guidance They can also be used for connection of RS232 serial terminal adaptor equipment to the control unit This cable is a Straight through DB9 female to DB9 male serial cable IP Office Ss DTE Port g 9 VWWay 9 VWay 3 D Type Plug D Type Socket 2 Meters 6 57 Feet 9 Way RS232 DTE Port Signal PC Terminal Adaptor 3 Receive data 3 2 Transmit Data 2 7 RTS Request To Send 7 8 CTS Clear To Send 8 6 DSR Data Set Ready 6 5 Ground 5 1 DCD Data Carrier Detect 1 4 DTR Data Terminal Ready 4 9 RI Ring Indicator 9 About erasing the configuration The following procedures erase the B5800 Branch Gateway configuration stored in the control unit This includes both the current configuration being used in RAM memory and the backup configuration stored in non volatile memory Foll
377. vaya com d Ifthe lt surname gt field does not contain an entry edit the field lt surname gt ast name lt surname gt where last name is the user s last name Note The entry for this field is derived from the Full Name field that is configured when a user is added to the system The Full Name field is configured in IP Office Manager under User gt User tab If the Full Name field was not completed when the user was added to the system the lt surname gt field for the user will be blank when the user is exported to the xml file The lt surnames gt field must contain a value Do not use punctuation characters such as or Do not begin the entry with a space e Edit the field lt userPassword gt password for the user lt userPassword gt so that the password complies with the System Manager user password constraints The System Manager user password cannot be only numeric This is the password used to log into System Manager 3 Save and close the xml file Bulk importing of users Procedure 1 From the System Manager console under Services select Bulk Import and Export 2 Click Import gt User Management gt Users 3 On the Import users page in the Select File field enter the complete path of the file Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 93 Upgrading an R6 1 system to R6 2 Also you can click Browse to locate and select a file 4 Select one of t
378. ve been marked as upgradeable When you activate these license entitlements you can generate License Key for either the current version or the old version Activating upgrade license entitlements which are purchased to upgrade other existing license entitlements When users activate these license entitlements they select the license entitlements to upgrade Activating license entitlements Before you begin You know the Host ID of the License Host if you are activating license entitlements on a new License Host About this task Use the License Activation Code LAC to activate one or more license entitlements You can activate all of the licenses or you can specify a number of licenses to activate from the quantity available Upon successful activation of the license entitlements PLDS creates an Activation Record and sends an Activation Notification e mail message to the customer who is registered with the entitlements The Activation Record and Activation Notification provide details on the number of activated licenses and the License Host The license file can be accessed on the License Keys tab of the Activation Record in PLDS and is also an attachment to the Activation Notification e mail message You must install the license file on WebLM to use the licenses Note If you are not using WebLM to manage the licenses you must install the license file on each B5800 Branch Gateway to use the licenses For more information see
379. verview 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 e 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 The following external expansion modules are supported Analog trunk module This module rovides an additional 16 analog ports for connection of analog trunks It supports both loop start and ground start trunks BRI So8 module This module provides 8 ETSI BRI So ports for the connection of ISDN devices This module is not intended to support BRI trunks Digital station module This module provides depending on variant an additional 16 or 30 DS ports for supported Avaya digital phones Phone module This module provides depending on variant an additional 16 or 30 phone ports for analog phones e Power supplies The control unit has an internal power supply unit Each external expansion module is supplied with an external power supply unit Additional power supply units may also be required for IP phones and some phone add ons e Power cords Depending on the locale different power cords need to be ordered for each control unit external expansion module and any phones or devices using external power supply units e Mountin
380. vided by a digital trunk from the central office exchange is used as this will be the most accurate and reliable clock source To do this the Clock Quality setting on each line in the B5800 Branch Gateway configuration is set to one of the following e Network If available the clock signal from this trunk should be used as the B5800 Branch Gateway clock source for call synchronization If several trunk sources are set as Network the B5800 Branch Gateway will default to using one as detailed below e Fallback If available the clock signal from this trunk can be used as the clock source if none of the trunks set as Network are providing a clock source Unsuitable The clock source from this trunk will never be used as the B5800 Branch Gateway clock source If no clock source is available the B5800 Branch Gateway can use its own internal clock if necessary In the example below the first B5800 Branch Gateway is set to use the public network trunk as its clock source and ignoring the possible clock source from the QSIG trunk The other B5800 Branch Gateway system is using the clock signal received from the first B5800 Branch Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 135 Initial branch configuration Gateway on its QSIG trunk as its clock source Thus both systems are using the same clock source and that clock source is the public network exchange Public Network PRI Netw
381. vided in the following documents Implementing Embedded Voicemail for B5800 Branch Gateway Release 6 2 document number 18 604098 e Implementing Standalone Voice Mail for B5800 Branch Gateway Release 6 2 document number 18 604088 172 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Configuring Embedded Voicemail Configuring Embedded Voicemail About this task Embedded Voicemail is the default voicemail configuration for B5800 Branch Gateway 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 157 In the left navigation pane click System 3 Click the Voicemail tab 4 In the Voicemail Type drop down box select Embedded Voicemail Note Fields applicable to this mode of voicemail support are enabled If the field is not applicable the field is disabled Ifyou want the users to be presented with a display menu for access to their mailbox check the Messages Button Goes to Visual Voice check box For more information see the IP Office Manager on line help Inthe Minimum Password Length field use the up and down arrows to set the appropriate minimum password length Inthe
382. word Setup RAS If CHAP is to be used on this link then the Encrypted Password option must be checked in the service and in the RAS service The name of the RAS service must match the name of the service at Site B Note that if the RAS settings are given the same name as the service and user they are automatically linked and become a WAN service Ensure that the Encrypted Password option is not checked when using a WAN service Edit the WAN port Do not create a new WAN port The WAN port is automatically detected If a WAN port is not displayed connect the WAN cable reboot the control unit and receive the configuration The WAN port configuration form should now be added Create an IP Route In the IP address field enter the network address of the remote end not the IP address of the control unit Under Destination select the service created above Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 239 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 240 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Chapter 16 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
383. y 0O1N Busy Blocks calls to long distance numbers Allows calls to long distance numbers e Busy e Busy Block any other calls that require an authorization Block any other calls that require an code authorization code It is recommended to use short codes that use X characters to match the full number of characters to be dialed That ensures that authorization code entry is not triggered until the full number has been dialed rather than mid dialing For example 09 numbers are premium rate in the UK so you would create a OOXXXXXXXXX N Dial short code set to Forced Authorization In the associated user or user right short code it is recommended to use 09N type short codes A Warning Changing PC registry settings Avaya accepts no liability for any issues arising from editing PC registry settings If you are in any doubt about how to perform this process you should not proceed It is your responsibility to ensure that the registry is correctly backed up before any changes are made Enabling authorization codes in Manager About this task Achange to the Manager PC registry settings is required to enable support for authorization codes within Manager Once this change is made various authorization code related features are visible when Manager is restarted A Warning Changing PC registry settings Avaya accepts no liability for any issues arising from editing PC registry settings If you are in any doubt ab
384. y Implementation Guide document number 146775 which is available on the Avaya support Web site http support avaya com The Secure Access Link 2 1 Gateway software download is also available on the Avaya support Web site Registering a product with Avaya is a process that uniquely identifies the device so that Avaya can service it ASAL Gateway registration form is provided with your software download See Universal Install SAL Registration Request Form on page 201 for more information To register the SAL Gateway complete Step 1 on the form and send it to salreg avaya com The following information is requested in Step 1 e Your company name e Avaya Sold to Number customer number e Your contact information so that Avaya can contact you if there are questions Avaya uses this information to register your gateway When the registration is complete Avaya will send you an e mail that provides the following information e The Solution Element ID and Product ID numbers A list of the devices currently registered at this location A list of other locations for your company 200 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com B5800 Branch Gateway registration and SAL Gateway on boarding Note Optional If you want to get Solution Element IDs SEID from other locations complete the Step 2 tab of the registration sheet and send it to salreq avaya com using
385. y the System Manager administration feature for the branch is enabled and the users on the B5800 Branch Gateway are deleted so they will not be available for export Manager 6 Edit fields in the xml file so that the data matches the requirements for the corresponding fields in System See Editing the xml file containing the users on page 92 Utility 7 Launch the Initial Installation See Using the Initial Installation Utility on page 121 8 Add the B5800 Branch Gateways to System Manager See About adding B5800 Branch Gateways to System Manager on page 125 Manager 9 Import users from B5800 Branch Gateway to Avaya Aura System See Bulk importing of users on page 93 greeting files 10 Upgrade the auto attendant See Uploading an auto attendant audio file on page 132 Upgrading the administration applications About this task Use this procedure to upgrade the B5800 Branch Gateway administration applications from R6 1 to R6 2 The B5800 Branch Gateway administration applications are Manager System Status and System Monitor For more information about the administration applications see Administration software suite on page 77 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 It there is uninstall i
386. y Code 44 Following rule 2 above they are replaced with the National Prefix 90 00441 707362200 Following rule 2 above the 90107362200 International Prefix 900 and the Country Code 44 are replaced with the National Prefix 90 441707362200 Following rule 2 above the 901707362200 Country Code 44 is 138 Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 Comments infodev avaya com Administering a Session Manager line for each branch Number Received Processing Resulting Number replaced with the National Prefix 90 6494770557 Following rule 3 above the 9006494770557 International Prefix 900 is added 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 e See Enabling SIP trunk support on page 139 Use this procedure to configure the IP Office LAN interface which will be used for the Session Manager line connection to the Avaya Aura Session Manager e See Setting the branch prefix and local number length for extension numbering on p
387. ya Aura Configuration October 2012 Comments infodev avaya com Memory card removal e See Restoring software files from the Optional SD card using a system phone on page 255 Memory card removal A Warning Memory cards should always be shut down before being removed when the system is running Though the card slot LEDs indicate when data is being written to a card lack of flashing LEDs is not a sufficient safeguard Shutting down the card will disable embedded voicemail if being used If the System SD card is removed features licensed by the card s Feature Key serial number will continue operating for up to 2 hours Card services can be restarted by either reinserting the card or using a Start Up command Shutting down a memory card using Manager Procedure 1 O a A O 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 157 Select File gt Advanced gt Memory Card Command gt Shutdown The following prompt appears Shutting down a memory card may cause service loss Continue Click Yes Inthe Select IP Office window click the check box for the appropriate system Click OK At the back of the control unit confirm that the appropriate memory card LED is off
388. 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 gt Rehost Move from the Home page 4 Click View Activation Record information to find and select licenses to rehost or move You can search the activation records by the Company name license host Group name or ID using the Search Activation Records functionality Note If you are an Avaya associate or Avaya Partner enter the search criteria and click Search Activation Records 5 Select Rehost Move for the License Host from which you are moving license entitlements 6 In the Search License Hosts field enter the License Host to which you are moving license entitlements Implementing the Avaya B5800 Branch Gateway for an Avaya Aura Configuration October 2012 195 Managing license files with PLDS 196 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 12 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 This is the Feature Key Serial Number printed on the System SD card You must add dashes betwee
389. ype 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 The process below is done separately for both the LAN port LAN1 in the configuration and the WAN port LAN2 in the configuration on the back of the control unit e The B5800 Branch Gateway makes a DHCP request for what IP address information it should use e If a DHCP server responds within approximately 10 seconds the control unit defaults to being a DHCP client and uses the IP address information supplied by the DHCP server Note For this installation we have not yet connected the control unit to the network so a DHCP server will not respond Ifa DHCP server does not respond the control unit defaults to being the DHCP server for the LAN using the following settings For its LAN1 it allocates the IP address 192 168 42 1 and IP Mask 255 255 255 0 It supports 200 DHCP clients using the addresses range 192 168 42 2 and 192 168 42 201 the IP Mask 255 255 255 0 and default gateway address 192 168 42 1 the control unit LAN1 address For its LAN2 if supported it allocates the IP address 192 168 43 1 and IP Mask 255 255 255 0 Note that the B5800 Branch Gateway does not check that these addresses are valid and or availa
390. ystem 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 Emergency and power failure ports 46 B5800 Branch Gateway systems can provide 2 types of analog extension power failure ports as described in the following table Type Description Provided By Switching power failure During normal B5800 Branch Analog phone 8 card ports Gateway operation these ports When an analog phone 8 can be used for normal analog base card is fitted with an phone connection analog trunk daughter card During power failure the port is during power failure directly connected to an analog extension port 8 is connected trunk port to analog trunk port 12 ATM combination card On this card during power failure extension port 8 is connected to analog trunk port 12 Emergency only power During normal B5800 Branch Analog trunk daughter failure ports Gateway operation these ports card cannot be used Regardless of the card During power failure the port is hosting it during power directly connected to ananalog failure pins 4 and 5 of port 12 trunk port are connected to pins 7 and 8 In all
391. ystem template to one or more branches Optional See Applying the system template on page 132 11 Create an endpoint template See Creating an endpoint template on page 133 Note You must create a B5800 Branch Gateway endpoint template You cannot add a user in System Manager unless an endpoint template has been created Note e Steps 12 through 23 are performed to modify a B5800 Branch Gateway configuration as needed e Steps 24 through 12 are performed to configure Avaya Aura Session Manager e Step 32 is performed to configure B5800 Branch Gateway users from User Management within System Manager 12 Disable unused trunks See Disabling unused trunks on page 134 13 Set a trunk clock quality setting See Setting a trunk clock quality setting on page 136 14 Set trunk prefixes See Setting the trunk prefixes on page 137 15 Enable SIP trunk support See Enabling SIP trunk support on page 139 16 Set the branch prefix and local number length for the extension numbering See Setting the branch prefix and local number length for extension numbering on page 140 17 Change the default codec selection See Changing the default codec selection on page 143 18 Change the maximum SIP sessions See Changing the maximum SIP sessions on page 144 19 Add a Session Manager line See Addin

Avaya B5800 Configuration manual

Contents

Download Pdf Manuals

Related Search

Related Contents