Avaya B5800 User Manual Page 167
- Page / 324
- Table of contents
- BOOKMARKS
Rated. / 5. Based on customer reviews
Chapter 11: Session Manager
Configuration
This chapter provides procedures to configure Avaya Aura
®
Session Manager to support calls to and from
B5800 Branch Gateway systems. Avaya Aura
®
System Manager R6.2 is used to administer Session
Manager. Perform the following procedures:
1. View the SIP domains for which the Session Manager provides call management. Multiple
domains can be listed. See
Viewing the SIP domains on page 168.
2. Identify logical and/or physical locations where SIP entities reside. 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 168.
3. 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 169.
4. 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 169.
5. 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 for connections between the SIP entity
and the Session Manager. See Creating entity links on page 170.
6. Create time ranges to control when different routing policies are used. See
Creating time
ranges on page 171.
7. Add a routing policy. A routing policy consists of a selected SIP entity as its destination and a
number of time ranges that define when the policy can be used. See Creating routing
policies on page 171.
8. Add dial patterns. Dial patterns are used to match digits received to a destination. Each dial
pattern has an associated routing policy that defines the target entity for matched calls and
when the match should be used. See
Creating dial patterns on page 172.
Note:
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 B5800 Branch Gateway for a CS 1000 Configuration October 2012 167
- Configuration 1
- PSTN trunking configurations 13
- Voicemail support options 14
- Management 14
- Licensing 16
- WebLM license management 17
- B5800 Branch Gateway licenses 18
- License modes 19
- System components 20
- B5800 Branch Gateway overview 22
- Supported telephones 23
- Software applications 26
- Supported country locales 27
- Related resources 29
- Avaya Mentor videos 30
- Training 30
- Web sites 30
- Revision history 31
- Gateway deployments 33
- Option 1 34
- Option 2 35
- Configuration considerations 35
- Chapter 3: Planning 37
- Dial plan considerations 38
- Dial plan example 38
- Voicemail considerations 39
- Planning 40
- Power supply backup (UPS) 43
- Grounding 46
- Wall and rack mounting 46
- Voice compression channels 46
- Measuring channel usage 48
- Environmental requirements 49
- Space requirements 50
- External expansion modules 51
- Rack space requirements 52
- Rack module positioning 53
- Installation requirements 54
- Installation checklist 55
- Tools and equipment required 56
- Unpacking equipment 57
- SD card preparation 58
- Creating a configuration file 59
- Adding a configuration file 60
- Adding music-on-hold files 60
- Base card insertion 65
- Installing a base card 66
- Wall mounting 67
- Rack mounting 69
- Important: 70
- DS phone IROB installation 76
- Analog phone barrier boxes 77
- Rack mounting barrier boxes 78
- PC requirements 80
- Installer PC connection 81
- Applying power to the system 83
- About the LEDs 85
- Trunk daughter card LEDs 86
- Default configuration 87
- Connecting phones 89
- Other DCP short codes 93
- Getting inventory 98
- Configuring user PLDS access 99
- Creating a software library 100
- About this task 101
- Procedure 101
- Comments? [email protected] 102
- Starting System Status 103
- Starting System Monitor 104
- Administration software suite 106
- Configuration checklist 107
- Initial branch configuration 112
- Before you begin 113
- Activating license files 114
- WebLM server 115
- Session Manager 117
- Bulk importing of devices 128
- Creating a system template 131
- Applying the system template 133
- Creating an endpoint template 133
- Disabling unused trunks 135
- Digital trunk clock source 136
- Setting the trunk prefixes 138
- Enabling SIP trunk support 140
- System tab field descriptions 142
- Adding an Avaya Aura 146
- Session Manager line 146
- VoIP tab field descriptions 149
- Avaya Aura 152
- Secondary Avaya Aura 153
- Manager line 155
- Gateways from System 159
- Chapter 11: Session Manager 167
- Viewing the SIP domains 168
- Creating locations 168
- Creating adaptations 169
- Creating SIP entities 169
- Creating entity links 170
- Creating time ranges 171
- Creating routing policies 171
- Creating dial patterns 172
- Voicemail options 173
- Messaging for voicemail 177
- Voicemail configuration 178
- Fallback 182
- 5. Click the Upload button 185
- User administration 188
- PLDS Overview 191
- Registering for PLDS 192
- About license activation 192
- Types of license activation 193
- Regenerate License files 199
- Licensing on page 16 200
- Default passwords 206
- System shutdown 208
- Rebooting the system 210
- About changing components 211
- Adding a new component 213
- Swapping extension users 214
- Office Manager 217
- System Manager 217
- Using the upgrade wizard 219
- State Switch 1 Switch 2 221
- Closed *39 *42 221
- EXT O/P connections 222
- Example 1: ISDN terminal 223
- Example 2: video conference 224
- Castlerock SNMPc V5.0.1 229
- Enabling SNMP trap sending 231
- DTE port maintenance 232
- Reset button 240
- Creating a WAN link 241
- Additional system procedures 242
- Card maintenance 244
- Card specification 245
- SD card folders 245
- Booting from the SD cards 246
- Post boot operation 247
- Boot alarms 247
- Formatting an SD card 248
- Recreating an SD card 249
- Viewing the card contents 250
- Upgrading the SD card locally 259
- Memory card removal 261
- Memory card startup 263
- Safety statements 265
- Lithium batteries 266
- Trunk interface modules 267
- Port safety classification 267
- EMC cautions 268
- Australia 269
- European Union 272
- New Zealand 272
- FCC notification 272
- Compliance with FCC rules 274
- Branch Gateway and SIP 277
- Well known ports 278
- Registered ports 278
- Dynamic ports 278
- Firewall types 279
- Firewall policies 280
- TFTP port usage 280
- Port usage diagram 287
- Centralized call control 291
- Branch PSTN override 294
- PSTN trunk fallback 296
- How authorization codes work 301
- Force authorization codes 303
- Authorization codes 304
- Avaya B5800 Branch Gateway 305
- Table 2: Avaya Aura 306
- Table 3: Avaya Aura 306
- Deskphones 309
- 4.3 phones 314
- Glossary 317
- Native extension 318
- Numerics 319
Related products and manuals for Gateways/controllers Avaya B5800
Gateways/controllers Avaya Mobile Communication 3100 Planning and Engineering User Manual
(52 pages)
(52 pages)
Gateways/controllers Avaya 3.6/SRG Notice
(14 pages)
(14 pages)
Gateways/controllers Avaya Configuring BayRS Routers and Protocols (308665-14.20 Rev 00) User Manual
(26 pages)
(26 pages)
Gateways/controllers Avaya B5800 User Manual
(342 pages)
(342 pages)
Gateways/controllers Avaya B5800 Notice
(12 pages)
(12 pages)
© 2020, manymanuals.com. All rights reserved. | 2.031 s |
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Comments to this Manuals