Manager - Batphone.us

Manager
Manager Manager 8.1
15-601011 Issue 25l - (11 February 2011)
© 2011 AVAYA All Rights Reserved.
Notices
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
Avaya shall not be responsible for any modifications, additions, or deletions
to the original published version of this documentation unless such
modifications, additions, or deletions were performed by Avaya.
End User agree 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 Web sites
referenced within this site or documentation(s) 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 this product. 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 Web site: http://www.avaya.com/support.
Please note that if you acquired the product 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.
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 AUTHORIZED
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, AND
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”).
Avaya grants End User a license within the scope of the license types
described below. 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 End User. "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. "Software"
means the computer programs in object code, originally licensed by Avaya
and ultimately utilized by End User, whether as stand-alone products or
pre-installed on Hardware. "Hardware" means the standard hardware
originally sold by Avaya and ultimately utilized by End User.
Manager Manager 8.1
Manager
License types
Designated System(s) License (DS). End User may install and use each copy
of the Software on only one Designated Processor, unless a different number
of Designated Processors is indicated in the Documentation or other materials
available to End User. Avaya may require the Designated Processor(s) to be
identified 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(s) and Product(s) provided by Avaya. All
content on this site, the documentation(s) and the product(s) 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. Unauthorized reproduction,
transmission, dissemination, storage, and or use without the express written
consent of Avaya can be a criminal, as well as a civil, offense under the
applicable law.
Third Party Components
Certain software programs or portions thereof included in the Product may
contain software distributed under third party agreements ("Third Party
Components"), which may contain terms that expand or limit rights to use
certain portions of the Product ("Third Party Terms"). Information regarding
distributed Linux OS source code (for those Products that have distributed the
Linux OS source code), and identifying the copyright holders of the Third
Party Components and the Third Party Terms that apply to them is available
on the Avaya Support Web site: http://support.avaya.com/Copyright.
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 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 and Canada.
For additional support telephone numbers, see the Avaya Support Web site:
http://support.avaya.com
Suspected security vulnerabilities with Avaya products should be reported to
Avaya by sending mail to: securityalerts@avaya.com.
Trademarks
Avaya and Aura are trademarks of Avaya, Inc.
The trademarks, logos and service marks (“Marks”) displayed in this site, the
documentation(s) 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(s) 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.
Avaya is a registered trademark of Avaya Inc. All non-Avaya trademarks are
the property of their respective owners.
Downloading documents
For the most current versions of documentation, see the Avaya Support Web
site: http://www.avaya.com/support
Contact Avaya Support
Avaya provides a telephone number for you to use to report problems or to
ask questions about your product. The support telephone number is
1-800-242-2121 in the United States. For additional support telephone
numbers, see the Avaya Web site: http://www.avaya.com/support
Page 2
15-601011 Issue 25l (11 February 2011)
Contents
Contents
1. Manager
1.1 Installing Manager
.....................................................................
.....................................................................
1.2 Starting Manager
1.3 Opening a .....................................................................
Configuration
1.4 Changing the
.....................................................................
Manager Language
1.5 Backward Compatibility
.....................................................................
1.6 What's New.....................................................................
in Release 6.1
16
18
19
23
23
24
2. Configuration Mode
2.1 The Configuration
.....................................................................
Mode Interface
2.2 Security Settings
.....................................................................
2.3 Title Bar .....................................................................
2.4 The Menu Bar
.....................................................................
2.5 Toolbars .....................................................................
2.6 Using the Navigation
Pane
.....................................................................
2.7 Using the Group
.....................................................................
Pane
2.8 Using the Details
.....................................................................
Pane
.....................................................................
2.9 Using the Error
Pane
2.10 Altering the
Interface
.....................................................................
2.11 The Status
.....................................................................
Bar
2.12 Editing Configuration
Settings
.....................................................................
2.12.1............................................................................
Mergeable Settings
2.12.2............................................................................
Configuration Sizes
2.12.3............................................................................
Setting the Discovery Addresses
2.12.4............................................................................
Opening a Configuration from a System
2.12.5............................................................................
Opening a Configuration Stored on PC
2.12.6............................................................................
Known System Discovery
2.12.7............................................................................
Creating a Offline Configuration
2.12.8............................................................................
Importing and Exporting Settings
2.12.9............................................................................
Copying and Pasting
2.12.10
Saving a Configuration Offline
............................................................................
............................................................................
2.12.11
Sending a Configuration
2.12.12
Erasing the Configuration
............................................................................
2.12.13
............................................................................
Default Settings
33
34
36
37
38
40
41
43
45
46
48
49
51
51
53
55
58
59
60
61
63
63
64
65
65
3. Security Mode
3.1 Security Settings
.....................................................................
3.2 Default Security
Users
.....................................................................
.....................................................................
3.3 The Security
Mode Interface
3.4 Security Administration
.....................................................................
3.5 Editing Security
.....................................................................
Settings
3.5.1 General
............................................................................
Settings
3.5.2 System
............................................................................
3.5.3 Services
............................................................................
Settings
3.5.4 Rights
............................................................................
Groups
3.5.5 Service
............................................................................
User Settings
69
71
72
74
83
85
87
92
94
99
4. Menu Bar Commands
4.1 Configuration
.....................................................................
Mode
4.1.1............................................................................
File Menu
4.1.2............................................................................
View
4.1.3............................................................................
Tools Menu
4.2 Security Mode
.....................................................................
4.2.1............................................................................
Open Security Settings
4.2.2............................................................................
Close Security Settings
4.2.3............................................................................
Save Security Settings
Manager Manager 8.1
Manager
104
104
128
130
134
134
134
134
4.2.4............................................................................
Reset Security Settings
4.2.5............................................................................
Preferences
4.2.6............................................................................
Exit
4.2.7............................................................................
Configuration
4.3 Embedded
File Management
.....................................................................
4.3.1............................................................................
Open File Settings
4.3.2............................................................................
Close File Settings
4.3.3............................................................................
Refresh File Settings
4.3.4............................................................................
Upload File
4.3.5............................................................................
Upload System Files
4.3.6............................................................................
Backup System Files
4.3.7............................................................................
Restore System Files
4.3.8............................................................................
Upgrade Binaries
4.3.9............................................................................
Upgrade Configuration
4.3.10
............................................................................
Upload Voicemail Files
............................................................................
4.3.11
Upload Phone Files
4.3.12
Copy System Card
............................................................................
4.3.13
............................................................................
Configuration
134
134
134
134
135
135
135
135
135
135
135
135
135
135
136
136
136
136
5. Configuration Settings
5.1 BOOTP .....................................................................
5.2 Operator .....................................................................
5.3 System .....................................................................
5.3.1............................................................................
System
5.3.2............................................................................
LAN1
5.3.3............................................................................
LAN2
5.3.4............................................................................
DNS
5.3.5............................................................................
Voicemail
5.3.6............................................................................
Telephony
5.3.7............................................................................
Directory Services
5.3.8............................................................................
System Events
5.3.9............................................................................
SMTP
............................................................................
5.3.10
Twinning
5.3.11
SMDR
............................................................................
5.3.12
............................................................................
VCM
5.3.13
CCR
............................................................................
.....................................................................
5.4 Line Settings
5.4.1............................................................................
Analog Line
5.4.2............................................................................
BRI Line
5.4.3............................................................................
E1 Line
5.4.4............................................................................
E1R2 Line
5.4.5............................................................................
T1 Line
5.4.6............................................................................
T1 PRI Line
5.4.7............................................................................
S0 Line
5.4.8............................................................................
H323 Line
5.4.9............................................................................
IP DECT Line
5.4.10
............................................................................
SIP Line
5.4.11
............................................................................
SES Line
5.5 Control Unit
.....................................................................
5.6 Extension.....................................................................
Settings
5.6.1............................................................................
Extn
5.6.2............................................................................
Analog
5.6.3............................................................................
VoIP
5.6.4............................................................................
T38 Fax
5.6.5............................................................................
IP DECT
5.7 User Settings
.....................................................................
5.7.1............................................................................
User
5.7.2............................................................................
Voicemail
140
141
142
143
148
155
156
157
160
166
172
177
177
179
181
184
185
187
192
196
202
206
211
217
220
227
230
243
250
251
252
254
256
260
261
262
264
267
Page 3
15-601011 Issue 25l (11 February 2011)
5.7.3............................................................................
DND
5.7.4............................................................................
Short Codes
5.7.5............................................................................
Source Numbers
5.7.6............................................................................
Telephony
5.7.7............................................................................
Forwarding
5.7.8............................................................................
Dial In
5.7.9............................................................................
Voice Recording
............................................................................
5.7.10
Coverage
5.7.11
Button Programming
............................................................................
5.7.12
............................................................................
Menu Programming
5.7.13
............................................................................
Phone Manager Options
............................................................................
5.7.14
Hunt Group Memberships
5.7.15
Mobility (Twinning)
............................................................................
5.7.16
............................................................................
Announcements
5.7.17
............................................................................
Personal Directory
............................................................................
5.7.18
SIP
5.8 Hunt Group
Settings
.....................................................................
5.8.1............................................................................
Hunt Group
5.8.2............................................................................
User List/Select Members
5.8.3............................................................................
Voicemail
5.8.4............................................................................
Fallback
5.8.5............................................................................
Queuing
5.8.6............................................................................
Voice Recording
5.8.7............................................................................
Announcements
5.8.8............................................................................
SIP
5.8.9............................................................................
Hunt Group Operation
5.9 Short Code
.....................................................................
5.10 Service Settings
.....................................................................
5.10.1
Service
............................................................................
............................................................................
5.10.2
Bandwidth
5.10.3
IP
............................................................................
5.10.4
............................................................................
Autoconnect
5.10.5
Quota
............................................................................
............................................................................
5.10.6
Fallback
5.10.7
DialIn
............................................................................
5.11 RAS
.....................................................................
5.11.1
PPP
............................................................................
5.12 Incoming.....................................................................
Call Route Settings
5.12.1
Standard
............................................................................
5.12.2
............................................................................
Voice Recording
5.12.3
Destinations
............................................................................
.....................................................................
5.13 WAN Port
Settings
5.13.1
............................................................................
WAN Port
5.13.2
............................................................................
Frame Relay
5.13.3
............................................................................
DLCIs
5.13.4
Advanced
............................................................................
5.13.5
............................................................................
PPP
5.14 Directory.....................................................................
5.15 Time Profile
.....................................................................
5.16 Firewall Profile
Settings
.....................................................................
5.16.1
............................................................................
Standard
5.16.2
............................................................................
Custom
5.16.3
............................................................................
Static NAT
5.17 IP Route.....................................................................
Settings
5.17.1
............................................................................
IP Route
5.17.2
............................................................................
RIP
5.18 Least Cost
.....................................................................
Routing Settings
5.18.1
............................................................................
LCR
Manager Manager 8.1
Manager
270
271
272
274
281
283
284
286
288
289
291
292
293
299
301
303
304
306
309
311
314
316
319
320
322
323
330
331
332
333
335
336
337
338
339
340
341
342
344
348
349
350
351
352
353
355
356
358
360
362
363
364
366
367
368
369
370
372
............................................................................
5.18.2
Main Route
5.18.3
............................................................................
Alternate Route 1
5.18.4
............................................................................
Alternate Route 2
5.19 Account .....................................................................
Code Settings
5.19.1
Account Code
............................................................................
5.19.2
............................................................................
Voice Recording
5.20 License .....................................................................
.....................................................................
5.21 Tunnel Settings
5.21.1
L2TP Tunnel
............................................................................
5.21.2
............................................................................
IP Security Tunnel
5.22 Logical LAN
.....................................................................
5.23 Wireless.....................................................................
Settings
5.23.1
SSID
............................................................................
5.23.2
............................................................................
Security
5.24 User Restrictions
.....................................................................
Settings
............................................................................
5.24.1
User Restrictions
5.24.2
Short Codes
............................................................................
5.25 User Rights
.....................................................................
Settings
5.25.1
............................................................................
User
............................................................................
5.25.2
Short Codes
5.25.3
Telephony
............................................................................
5.25.4
............................................................................
Button Programming
5.25.5
Menu Programming
............................................................................
5.25.6
............................................................................
Phone Manager
5.25.7
Twinning
............................................................................
............................................................................
5.25.8
User Rights Membership
5.25.9
Voicemail
............................................................................
5.26 Auto Attendant
.....................................................................
Settings
5.26.1
Auto Attendant
............................................................................
............................................................................
5.26.2
Actions
5.27 Authorization
Codes
.....................................................................
5.28 ARS
.....................................................................
5.28.1
ARS
............................................................................
............................................................................
5.28.2
Cause Codes and ARS
5.28.3
ARS Operation
............................................................................
5.29 E911 System
.....................................................................
Settings
5.29.1
E911 Adjunct
............................................................................
............................................................................
5.29.2
Zones
372
373
374
375
376
376
378
380
381
383
385
386
386
386
387
388
388
389
391
391
392
395
395
396
398
398
399
400
402
403
404
407
409
411
412
421
422
423
6. Short Codes
6.1 Short Code
.....................................................................
Fields and Characters
6.2 User Dialing
.....................................................................
6.3 Application
.....................................................................
Dialing
6.4 Secondary.....................................................................
Dial Tone
6.5 ? Short Codes
.....................................................................
6.6 Short Code
.....................................................................
Matching Examples
6.7 Default System
.....................................................................
Short Code List
6.8 Short Code
.....................................................................
Features
6.8.1............................................................................
Acquire Call
6.8.2............................................................................
AOC Previous Call
6.8.3............................................................................
AOC Reset Total
6.8.4............................................................................
AOC Total
6.8.5............................................................................
Auto Attendant
6.8.6............................................................................
Break Out
6.8.7............................................................................
Barred
6.8.8............................................................................
Busy On Held
6.8.9............................................................................
Call Intrude
6.8.10
............................................................................
Call Listen
427
430
431
432
433
434
437
439
440
440
440
440
440
441
441
441
442
443
Page 4
15-601011 Issue 25l (11 February 2011)
Contents
6.8.11
............................................................................
Call Pickup Any
6.8.12
............................................................................
Call Pickup Extn
6.8.13
............................................................................
Call Pickup Group
............................................................................
6.8.14
Call Pickup Line
6.8.15
Call Pickup Members
............................................................................
6.8.16
............................................................................
Call Pickup User
6.8.17
............................................................................
Call Queue
............................................................................
6.8.18
Call Record
6.8.19
Call Steal
............................................................................
6.8.20
............................................................................
Call Waiting On
6.8.21
............................................................................
Call Waiting Off
............................................................................
6.8.22
Call Waiting Suspend
6.8.23
Cancel All Forwarding
............................................................................
6.8.24
............................................................................
Cancel Ring Back When Free
6.8.25
............................................................................
Channel Monitor
............................................................................
6.8.26
Change Login Code
6.8.27
Clear After Call Work
............................................................................
6.8.28
............................................................................
Clear Call
6.8.29
............................................................................
Clear CW
............................................................................
6.8.30
Clear Hunt Group Night Service
6.8.31
Clear Hunt Group Out Of Service
............................................................................
6.8.32
............................................................................
Clear Quota
6.8.33
Conference Add
............................................................................
6.8.34
............................................................................
Conference Meet Me
6.8.35
CW
............................................................................
............................................................................
6.8.36
Dial
6.8.37
Dial 3K1
............................................................................
6.8.38
............................................................................
Dial 56K
6.8.39
Dial 64K
............................................................................
............................................................................
6.8.40
Dial CW
6.8.41
Dial Direct
............................................................................
6.8.42
............................................................................
Dial Direct Hot Line
6.8.43
Dial Emergency
............................................................................
............................................................................
6.8.44
Dial Extn
6.8.45
Dial Fax
............................................................................
6.8.46
............................................................................
Dial Inclusion
6.8.47
Dial Paging
............................................................................
............................................................................
6.8.48
Dial Physical Extension By Number
6.8.49
Dial Physical Number By ID
............................................................................
6.8.50
............................................................................
Dial Speech
6.8.51
Dial V110
............................................................................
............................................................................
6.8.52
Dial V120
6.8.53
............................................................................
Dial Video
6.8.54
............................................................................
Disable ARS Form
6.8.55
............................................................................
Disable Internal Forwards
6.8.56
Disable Internal Forward Unconditional
............................................................................
6.8.57
............................................................................
Disable Internal Forward Busy or No Answer
6.8.58
............................................................................
Display Msg
6.8.59
............................................................................
Do Not Disturb Exception Add
6.8.60
Do Not Disturb Exception Delete
............................................................................
6.8.61
............................................................................
Do Not Disturb On
6.8.62
............................................................................
Do Not Disturb Off
6.8.63
............................................................................
Enable ARS Form
6.8.64
............................................................................
Enable Internal Forwards
6.8.65
............................................................................
Enable Internal Forward Unconditional
6.8.66
............................................................................
Enable Internal Forward Busy or No Answer
6.8.67
............................................................................
Extn Login
6.8.68
............................................................................
Extn Logout
Manager Manager 8.1
Manager
444
444
445
445
446
446
447
447
448
449
449
449
450
450
450
451
452
452
452
453
453
454
454
454
454
455
456
456
456
456
457
457
458
458
459
459
459
461
461
462
462
462
462
463
463
463
464
464
465
465
466
466
466
467
467
467
468
468
............................................................................
6.8.69
Flash Hook
6.8.70
............................................................................
FNE
6.8.71
............................................................................
Follow Me Here
............................................................................
6.8.72
Follow Me Here Cancel
6.8.73
Follow Me To
............................................................................
6.8.74
............................................................................
Forward Hunt Group Calls On
6.8.75
............................................................................
Forward Hunt Group Calls Off
............................................................................
6.8.76
Forward Number
6.8.77
Forward On Busy Number
............................................................................
6.8.78
............................................................................
Forward On Busy On
6.8.79
............................................................................
Forward On Busy Off
............................................................................
6.8.80
Forward On No Answer On
6.8.81
Forward On No Answer Off
............................................................................
6.8.82
............................................................................
Forward Unconditional On
6.8.83
............................................................................
Forward Unconditional Off
............................................................................
6.8.84
Group Listen Off
6.8.85
Group Listen On
............................................................................
6.8.86
............................................................................
Headset Toggle
6.8.87
............................................................................
Hold Call
............................................................................
6.8.88
Hold CW
6.8.89
Hold Music
............................................................................
6.8.90
............................................................................
Hunt Group Disable
6.8.91
Hunt Group Enable
............................................................................
6.8.92
............................................................................
Last Number Redial
6.8.93
MCID Activate
............................................................................
............................................................................
6.8.94
Mobile Twinned Call Pickup
6.8.95
Off Hook Station
............................................................................
6.8.96
............................................................................
Outgoing Call Bar Off
6.8.97
Outgoing Call Bar On
............................................................................
............................................................................
6.8.98
Park Call
6.8.99
Private Call
............................................................................
6.8.100
............................................................................
Private Call Off
6.8.101
Private Call On
............................................................................
............................................................................
6.8.102
Priority Call
6.8.103
Record Message
............................................................................
6.8.104
............................................................................
Relay On
6.8.105
Relay Off
............................................................................
............................................................................
6.8.106
Relay Pulse
6.8.107
Resume Call
............................................................................
6.8.108
............................................................................
Retrieve Call
6.8.109
Ring Back When Free
............................................................................
............................................................................
6.8.110
Secondary Dial Tone
6.8.111
............................................................................
Set Absent Text
6.8.112
............................................................................
Set Account Code
6.8.113
............................................................................
Set Authorization Code
6.8.114
Set Hunt Group Night Service
............................................................................
6.8.115
............................................................................
Set Hunt Group Out Of Service
6.8.116
............................................................................
Set Inside Call Seq
6.8.117
............................................................................
Set Mobile Twinning Number
6.8.118
Set Mobile Twinning On
............................................................................
6.8.119
............................................................................
Set Mobile Twinning Off
6.8.120
............................................................................
Set No Answer Time
6.8.121
............................................................................
Set Outside Call Seq
6.8.122
............................................................................
Set Ringback Seq
6.8.123
............................................................................
Set Wrap Up Time
6.8.124
............................................................................
Shutdown Embedded Voicemail
6.8.125
............................................................................
Startup Embedded Voicemail
6.8.126
............................................................................
Suspend Call
469
469
470
471
471
472
472
473
473
474
474
475
475
476
476
477
477
478
478
479
479
480
480
481
481
481
482
483
483
484
484
485
485
486
486
487
487
488
488
489
489
489
491
492
492
493
493
494
495
495
495
496
496
497
497
498
498
499
Page 5
15-601011 Issue 25l (11 February 2011)
6.8.127
............................................................................
Suspend CW
6.8.128
............................................................................
Start After Call Work
6.8.129
............................................................................
Toggle Calls
............................................................................
6.8.130
Unpark Call
6.8.131
Voicemail Collect
............................................................................
6.8.132
............................................................................
Voicemail Node
6.8.133
............................................................................
Voicemail On
............................................................................
6.8.134
Voicemail Off
6.8.135
Voicemail Ringback On
............................................................................
6.8.136
............................................................................
Voicemail Ringback Off
499
500
500
500
501
502
502
502
503
503
7. Button Programming
7.1 Programming
.....................................................................
Buttons
7.1.1............................................................................
Programming Buttons with Manager
7.1.2............................................................................
Programming Button via the Menu Key
7.1.3............................................................................
Programming Button via an Admin Button
7.1.4............................................................................
T3 Self-Administration
7.1.5............................................................................
Customizing Text Labels
7.1.6............................................................................
Interactive Button Menus
7.1.7............................................................................
Label Templates
7.2 Phone Details
.....................................................................
7.2.1............................................................................
Phone Add-Ons
7.2.2............................................................................
Button Types
7.2.3............................................................................
Status Lamps
7.2.4............................................................................
1000 Series
7.2.5............................................................................
1100 Series
7.2.6............................................................................
1200 Series
7.2.7............................................................................
1400 Series
7.2.8............................................................................
1600 Series
7.2.9............................................................................
20 Series
7.2.10
............................................................................
2400 Series
7.2.11
3600 Series
............................................................................
............................................................................
7.2.12
3700 Series
7.2.13
3800 Series
............................................................................
7.2.14
............................................................................
3900 Series
7.2.15
4400 Series
............................................................................
............................................................................
7.2.16
4600 Series (Old Style)
7.2.17
4600 Series (New Style)
............................................................................
7.2.18
............................................................................
5400 Series
7.2.19
5600 Series
............................................................................
............................................................................
7.2.20
6400 Series
7.2.21
9000 Series
............................................................................
7.2.22
............................................................................
9600 Series
7.2.23
............................................................................
T3 Series
7.3 Actions .....................................................................
7.3.1............................................................................
Abbreviated Dial
7.3.2............................................................................
Abbreviated Dial Pause
7.3.3............................................................................
Abbreviated Dial Program
7.3.4............................................................................
Abbreviated Dial Stop
7.3.5............................................................................
Account Code Entry
7.3.6............................................................................
ACD Agent Statistics
7.3.7............................................................................
ACD Stroke Count
7.3.8............................................................................
Acquire Call
7.3.9............................................................................
AD Special Functions
7.3.10
............................................................................
AD Special Function Mark
7.3.11
............................................................................
AD Special Function Wait
7.3.12
............................................................................
AD Suppress
7.3.13
............................................................................
After Call Work
Manager Manager 8.1
Manager
507
507
509
511
512
514
515
516
516
518
520
521
523
524
525
526
528
530
532
536
538
538
539
540
544
547
551
555
559
561
562
566
569
573
573
574
574
575
576
576
577
577
577
578
578
579
............................................................................
7.3.14
Appearance
7.3.15
............................................................................
Automatic Callback
7.3.16
............................................................................
Automatic Intercom
............................................................................
7.3.17
Break Out
7.3.18
Bridged Appearance
............................................................................
7.3.19
............................................................................
Busy
7.3.20
............................................................................
Busy On Held
............................................................................
7.3.21
Call Forwarding All
7.3.22
Call Intrude
............................................................................
7.3.23
............................................................................
Call List
7.3.24
............................................................................
Call Listen
............................................................................
7.3.25
Call Park
7.3.26
Call Park To Other Extension
............................................................................
7.3.27
............................................................................
Call Pickup
7.3.28
............................................................................
Call Pickup Any
............................................................................
7.3.29
Call Pickup Group
7.3.30
Call Pickup Members
............................................................................
7.3.31
............................................................................
Call Queue
7.3.32
............................................................................
Call Record
............................................................................
7.3.33
Call Steal
7.3.34
Call Waiting Off
............................................................................
7.3.35
............................................................................
Call Waiting On
7.3.36
Call Waiting Suspend
............................................................................
7.3.37
............................................................................
Cancel All Forwarding
7.3.38
Cancel Leave Word Calling
............................................................................
............................................................................
7.3.39
Cancel Ring Back When Free
7.3.40
Channel Monitor
............................................................................
7.3.41
............................................................................
Clear Call
7.3.42
Clear CW
............................................................................
............................................................................
7.3.43
Clear Hunt Group Night Service
7.3.44
Clear Hunt Group Out Of Service
............................................................................
7.3.45
............................................................................
Clear Quota
7.3.46
Conference Add
............................................................................
............................................................................
7.3.47
Conference Meet Me
7.3.48
Consult
............................................................................
7.3.49
............................................................................
Coverage Appearance
7.3.50
Dial
............................................................................
............................................................................
7.3.51
Dial 3K1
7.3.52
Dial 56K
............................................................................
7.3.53
............................................................................
Dial 64K
7.3.54
Dial CW
............................................................................
............................................................................
7.3.55
Dial Direct
7.3.56
............................................................................
Dial Emergency
7.3.57
............................................................................
Dial Inclusion
7.3.58
............................................................................
Dial Intercom
7.3.59
Dial Paging
............................................................................
7.3.60
............................................................................
Dial Physical Extn by Number
7.3.61
............................................................................
Dial Physical Extn by ID
7.3.62
............................................................................
Dial Speech
7.3.63
Dial V110
............................................................................
7.3.64
............................................................................
Dial V120
7.3.65
............................................................................
Display Msg
7.3.66
............................................................................
Dial Video
7.3.67
............................................................................
Directed Call Pickup
7.3.68
............................................................................
Directory
7.3.69
............................................................................
Do Not Disturb Exception Add
7.3.70
............................................................................
Do Not Disturb Exception Delete
7.3.71
............................................................................
Do Not Disturb Off
579
580
581
581
583
584
584
585
586
586
587
588
589
590
590
591
591
592
592
593
594
594
595
595
596
596
597
598
598
599
599
600
600
601
602
603
604
604
605
605
606
606
607
607
608
609
610
610
611
611
612
612
613
614
615
616
616
617
Page 6
15-601011 Issue 25l (11 February 2011)
Contents
7.3.72
............................................................................
Do Not Disturb On
7.3.73
............................................................................
Drop
7.3.74
............................................................................
Extn Login
............................................................................
7.3.75
Extn Logout
7.3.76
Flash Hook
............................................................................
7.3.77
............................................................................
Follow Me Here
7.3.78
............................................................................
Follow Me Here Cancel
............................................................................
7.3.79
Follow Me To
7.3.80
Forward Hunt Group Calls Off
............................................................................
7.3.81
............................................................................
Forward Hunt Group Calls On
7.3.82
............................................................................
Forward Number
............................................................................
7.3.83
Forward On Busy Number
7.3.84
Forward On Busy Off
............................................................................
7.3.85
............................................................................
Forward On Busy On
7.3.86
............................................................................
Forward On No Answer Off
............................................................................
7.3.87
Forward On No Answer On
7.3.88
Forward Unconditional Off
............................................................................
7.3.89
............................................................................
Forward Unconditional On
7.3.90
............................................................................
Group
............................................................................
7.3.91
Group Listen On
7.3.92
Group Paging
............................................................................
7.3.93
............................................................................
Headset Toggle
7.3.94
Hold Call
............................................................................
7.3.95
............................................................................
Hold CW
7.3.96
Hold Music
............................................................................
............................................................................
7.3.97
Hunt Group Enable
7.3.98
Hunt Group Disable
............................................................................
7.3.99
............................................................................
Inspect
7.3.100
Internal Auto-Answer
............................................................................
............................................................................
7.3.101
Leave Word Calling
7.3.102
Line Appearance
............................................................................
7.3.103
............................................................................
Manual Exclude
7.3.104
MCID Activate
............................................................................
............................................................................
7.3.105
Off Hook Station
7.3.106
Park
............................................................................
7.3.107
............................................................................
Park Call
7.3.108
Priority Call
............................................................................
............................................................................
7.3.109
Priority Calling
7.3.110
Private Call
............................................................................
7.3.111
............................................................................
Relay Off
7.3.112
Relay On
............................................................................
............................................................................
7.3.113
Relay Pulse
7.3.114
............................................................................
Resume Call
7.3.115
............................................................................
Retrieve Call
7.3.116
............................................................................
Ring Back When Free
7.3.117
Ringer Off
............................................................................
7.3.118
............................................................................
Self-Administer
7.3.119
............................................................................
Send All Calls
7.3.120
............................................................................
Set Absent Text
7.3.121
Set Account Code
............................................................................
7.3.122
............................................................................
Set Hunt Group Night Service
7.3.123
............................................................................
Set Hunt Group Out Of Service
7.3.124
............................................................................
Set Inside Call Seq
7.3.125
............................................................................
Set Night Service Group
7.3.126
............................................................................
Set Out of Service Group
7.3.127
............................................................................
Set No Answer Time
7.3.128
............................................................................
Set Outside Call Seq
7.3.129
............................................................................
Set Ringback Seq
Manager Manager 8.1
Manager
617
618
619
619
620
621
621
622
623
623
624
624
626
626
627
627
628
628
629
630
631
632
632
633
633
634
635
636
637
638
639
640
640
641
642
643
644
644
645
646
646
647
648
648
649
650
651
652
653
654
654
656
657
657
658
659
659
659
............................................................................
7.3.130
Set Wrap Up Time
7.3.131
............................................................................
Stored Number View
7.3.132
............................................................................
Suspend Call
............................................................................
7.3.133
Suspend CW
7.3.134
Time of Day
............................................................................
7.3.135
............................................................................
Timer
7.3.136
............................................................................
Toggle Calls
............................................................................
7.3.137
Twinning
7.3.138
Unpark Call
............................................................................
7.3.139
............................................................................
User
7.3.140
............................................................................
Visual Voice
............................................................................
7.3.141
Voicemail Collect
7.3.142
Voicemail Off
............................................................................
7.3.143
............................................................................
Voicemail On
7.3.144
............................................................................
Voicemail Ringback Off
............................................................................
7.3.145
Voicemail Ringback On
660
660
661
661
662
662
663
663
665
666
668
669
670
670
671
671
8. Key and Lamp Operation
8.1 Appearance
.....................................................................
Button Features
8.2 Call Appearance
Buttons
.....................................................................
8.2.1............................................................................
Example 1
8.2.2............................................................................
Example 2
8.2.3............................................................................
How are Call Appearance Buttons Treated?
8.2.4............................................................................
Button Indication
.....................................................................
8.3 Bridged Appearance
Buttons
8.3.1............................................................................
Example 1
8.3.2............................................................................
Example 2
8.3.3............................................................................
Example 3
8.3.4............................................................................
How are Bridged Appearances Treated?
8.3.5............................................................................
Button Indication
8.4 Call Coverage
.....................................................................
Buttons
8.4.1............................................................................
Example 1
8.4.2............................................................................
Example 2
8.4.3............................................................................
How is Call Coverage Treated?
8.4.4............................................................................
Button Indication
8.5 Line Appearance
Buttons
.....................................................................
8.5.1............................................................................
Example 1
8.5.2............................................................................
Example 2
8.5.3............................................................................
How are Line Appearances Treated?
8.5.4............................................................................
Button Indication
8.5.5............................................................................
T3 Phone Line Appearances
8.6 Other Appearance
Controls
.....................................................................
8.6.1............................................................................
Selected Button Indication
8.6.2............................................................................
Idle Line Preference
8.6.3............................................................................
Ringing Line Preference
8.6.4............................................................................
Answer Pre-Select
8.6.5............................................................................
Auto Hold
8.6.6............................................................................
Ring Delay
8.6.7............................................................................
Delayed Ring Preference
8.6.8............................................................................
Collapsing Appearances
8.6.9............................................................................
Joining Other Calls (Bridging)
8.6.10
............................................................................
Multiple Alerting Buttons
8.6.11
Twinning
............................................................................
8.6.12
............................................................................
Busy on Held
8.6.13
............................................................................
Reserving a Call Appearance Button
8.6.14
............................................................................
Logging Off and Hot Desking
8.6.15
............................................................................
Applications
8.7 Programming
.....................................................................
Appearance Buttons
674
675
676
677
678
679
680
681
682
683
684
685
686
687
687
688
689
690
691
692
693
694
695
696
696
697
700
703
704
705
707
709
710
712
713
713
713
714
714
715
Page 7
15-601011 Issue 25l (11 February 2011)
8.7.1............................................................................
System Settings
8.7.2............................................................................
User Settings
8.7.3............................................................................
Line Appearance ID Numbers
8.7.4............................................................................
Outgoing Line Programming
8.8 Upgrading.....................................................................
from Pre-3.0 Systems
8.8.1............................................................................
Call Handling Changes
8.8.2............................................................................
Twin LED Button Users
717
718
719
720
721
721
723
9. Telephone Features
9.1 Date and .....................................................................
Time
.....................................................................
9.2 User Directory
Access
9.3 Mobile Call
Control
.....................................................................
9.3.1............................................................................
Mobile Direct Access (MDA)
9.3.2............................................................................
Mobile Callback
.....................................................................
9.4 one-X Mobile
Client
9.5 Advice of .....................................................................
Charge
9.6 Centralized
.....................................................................
System Directory
9.7 Centralized
.....................................................................
Personal Directory
.....................................................................
9.8 Centralized
Call Log
9.9 Coverage.....................................................................
Groups
9.10 Fax Relay
.....................................................................
9.11 Dial Tone
.....................................................................
Transfer
9.12 Malicious.....................................................................
Call Tracing (MCID)
9.13 Call Barring
.....................................................................
.....................................................................
9.14 Caller Display
9.15 Call Intrusion
.....................................................................
9.16 Call Tagging
.....................................................................
9.17 Private Calls
.....................................................................
.....................................................................
9.18 Call Pickup
9.19 Call Waiting
.....................................................................
9.20 Parking Calls
.....................................................................
9.21 Ring Back
When Free
.....................................................................
9.22 Message.....................................................................
Waiting Indication
9.23 Ring Tones
.....................................................................
9.24 Music On
.....................................................................
Hold (MOH)
9.25 System Phone
Features
.....................................................................
9.26 The 'No .....................................................................
User' User
9.27 Forwarding
Calls
.....................................................................
9.27.1
............................................................................
Do Not Disturb
9.27.2
Follow Me
............................................................................
............................................................................
9.27.3
Forward Unconditional
9.27.4
Forward on Busy
............................................................................
9.27.5
............................................................................
Forward on No Answer
9.27.6
............................................................................
Determining a User's Busy Status
9.27.7
Chaining and Loops
............................................................................
9.28 Transferring
.....................................................................
Calls
9.28.1
............................................................................
Off-Switch Transfer Restrictions
9.28.2
............................................................................
Centrex Transfer
9.28.3
Handsfree Announced Transfers
............................................................................
9.28.4
............................................................................
One Touch Transferring
9.29 Conferencing
.....................................................................
9.29.1
............................................................................
Default Conference Handling
9.29.2
Using Conference Meet Me
............................................................................
9.30 Hot Desking
.....................................................................
9.30.1
............................................................................
Remote Hot Desking
9.30.2
............................................................................
Call Center Agents
9.30.3
............................................................................
Hot Desking Examples
9.30.4
............................................................................
Automatic Log Off
Manager Manager 8.1
Manager
727
729
730
732
733
734
740
741
744
745
748
749
751
753
754
755
756
756
757
757
758
759
760
761
762
763
765
767
768
769
771
773
775
777
779
780
781
782
783
784
786
787
788
788
789
790
790
791
792
9.31 Paging ..................................................................... 793
9.31.1
............................................................................
Paging Via Voicemail Pro
795
10. Data Routing
10.1 Network .....................................................................
Address Translation (NAT)
10.2 DHCP .....................................................................
.....................................................................
10.3 Examples
10.3.1
Simple ISDN Internet Connection
............................................................................
10.3.2
............................................................................
ISDN Link Between IP Offices
10.3.3
............................................................................
Using a Dedicated T1/PRI ISP Link
............................................................................
10.3.4
Logical LAN Connection
10.3.5
Remote Access
............................................................................
10.3.6
............................................................................
WAN PPP
10.3.7
............................................................................
WAN Frame Relay
798
798
799
799
800
801
803
804
807
808
11. Small Community Networking
11.1 Supported
.....................................................................
SCN Network Layouts
.....................................................................
11.2 Supported
SCN Features
11.3 Voicemail
Support
.....................................................................
11.4 Enabling.....................................................................
Small Community Networking
11.5 SCN Management
.....................................................................
............................................................................
11.5.1
Enabling SCN Discovery
11.5.2
Creating a Common Admin Account
............................................................................
11.5.3
............................................................................
Loading an SCN Configuration
11.5.4
Editing an SCN Configuration
............................................................................
11.5.5
............................................................................
Using the Network Viewer
11.5.6
System Inventory
............................................................................
.....................................................................
11.6 SCN Remote
Hotdesking
11.7 SCN Fallback
.....................................................................
11.8 SCN Short
.....................................................................
Code Programming
811
812
814
815
817
817
818
819
820
822
825
826
826
828
12. Licences
12.1 System Edition
.....................................................................
Licenses
12.2 Trunk Licensing
.....................................................................
.....................................................................
12.3 Telephone/Endpoint
Licenses
12.4 User Licenses
.....................................................................
12.5 Voicemail
.....................................................................
Pro Licenses
12.6 Customer
Call Reporter Licenses
.....................................................................
.....................................................................
12.7 Trial Licenses
12.8 Other Licenses
.....................................................................
832
833
834
835
837
839
841
842
13. Appendix: Locale Settings
13.1 Locale Defaults
.....................................................................
13.2 Phone Display
.....................................................................
Language Sets and Fallback
13.3 Argentina
.....................................................................
13.4 Australia.....................................................................
13.5 Bahrain .....................................................................
13.6 Belgium .....................................................................
- Flemish
13.7 Belgium .....................................................................
- French
13.8 Brazil .....................................................................
13.9 Canada .....................................................................
- French
13.10 Chile .....................................................................
13.11 China .....................................................................
13.12 Colombia
.....................................................................
13.13 Customize
.....................................................................
13.14 Denmark
.....................................................................
13.15 Egypt .....................................................................
13.16 Finland.....................................................................
13.17 France .....................................................................
846
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
Page 8
15-601011 Issue 25l (11 February 2011)
Contents
13.18 Greece.....................................................................
13.19 Germany
.....................................................................
13.20 Hong Kong
.....................................................................
.....................................................................
13.21 Hungary
13.22 Iceland.....................................................................
13.23 India .....................................................................
13.24 Italy .....................................................................
13.25 Korea .....................................................................
13.26 Kuwait .....................................................................
13.27 Mexico.....................................................................
13.28 Morocco
.....................................................................
.....................................................................
13.29 Netherlands
13.30 New Zealand
.....................................................................
13.31 Norway.....................................................................
13.32 Oman .....................................................................
.....................................................................
13.33 Pakistan
13.34 Peru .....................................................................
13.35 Poland .....................................................................
13.36 Portugal
.....................................................................
13.37 Qatar .....................................................................
13.38 Russia .....................................................................
13.39 Saudi Arabia
.....................................................................
13.40 Singapore
.....................................................................
13.41 South Africa
.....................................................................
13.42 Spain .....................................................................
13.43 Sweden.....................................................................
13.44 Switzerland
.....................................................................
13.45 Taiwan.....................................................................
13.46 Turkey .....................................................................
.....................................................................
13.47 United Arab
Emirates
13.48 United Kingdom
.....................................................................
13.49 United States
.....................................................................
13.50 Venezuela
.....................................................................
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
............................................................................
931
15.3.18
Unformatted (Enhanced)
16. Appendix: Release History
16.1 What was
.....................................................................
New in Release 6.1
16.2 What was
.....................................................................
New in Release 6.0
16.3 What was
.....................................................................
New in Release 5.0
.....................................................................
16.4 What was
New in 4.2
16.5 What was
New in 4.1
.....................................................................
16.6 What was
.....................................................................
New in 4.0 May 2007
16.7 What was
.....................................................................
New in 4.0
934
939
951
960
969
974
975
17. Ports
18. Single Server Support
Index
...............................................................................989
14. Appendix: SMDR
14.1 SMDR Fields
..................................................................... 900
..................................................................... 903
14.2 SMDR Examples
15. Appendix: CDR Records
15.1 CDR Record
.....................................................................
Fields
15.2 Call Splitting
.....................................................................
15.3 Record Formats
.....................................................................
15.3.1
59 Character (Normal)
............................................................................
15.3.2
............................................................................
Expanded (Normal)
15.3.3
............................................................................
Expanded (Enhanced)
15.3.4
............................................................................
INT-Direct (Normal)
15.3.5
............................................................................
INT-ISDN (Normal)
15.3.6
INT-Process (Normal)
............................................................................
15.3.7
............................................................................
LSU (Normal)
15.3.8
............................................................................
LSU (Enhanced)
15.3.9
............................................................................
LSU (ISDN)
15.3.10
LSU-Expanded
............................................................................
15.3.11
............................................................................
Printer (Normal)
15.3.12
............................................................................
Printer (Enhanced)
15.3.13
............................................................................
Printer (ISDN)
15.3.14
............................................................................
Teleseer (Normal)
15.3.15
............................................................................
Teleseer (Enhanced)
15.3.16
............................................................................
Teleseer (ISDN)
15.3.17
............................................................................
Unformatted (Normal)
Manager Manager 8.1
Manager
911
913
914
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
Page 9
15-601011 Issue 25l (11 February 2011)
Chapter 1.
Manager
Manager Manager 8.1
Manager
Page 11
15-601011 Issue 25l (11 February 2011)
Manager:
1. Manager
Manager is an application for viewing and editing an Manager system's configuration. It is a tool for system installers and
maintainers.
This documentation covers the use of the Avaya IP Office R6.1 Manager to configure an Manager system. For a summary
of the new features in Release 6.1 refer to the Appendix 939 .
IP Office systems can run in several modes. Unless specifically mentioned, details within this documentation are for
systems running in IP Office standard mode.
Manager runs on a Windows PC and connects to the system via Ethernet LAN or WAN connections.
·
WARNING - Password Changes Required
New systems use default security settings. These settings must be changed to make the system secure. As a
minimum, you must change the default passwords of the Security Administrator, the default Service Users and
the Unsecured Interfaces System Password. Failure to do so will render the system potentially unsecure. See
the Security Mode 68 section for details.
·
IMPORTANT - Manager is an Off-Line Editor
Manager is an off-line editor. It receives a copy of the system's current configuration settings. Changes are made to
that copy and it is then sent back to the system for those changes to become active. This means that changes to
the active configuration in the system that occur between Manager receiving and sending back the copy may be
overwritten. For example this may affect changes made by users through their phone or voicemail mailbox after the
copy of the configuration is received by Manager.
Manager is part of the IP Office Admin suite of programs. It is important to note that the software level of Manager
application is 2 higher than the software level of the system core software with which it is released. For example Manager
8.1 was released with Manager 6.1 core software. The Manager application can be used to manage configurations from
systems running IP Office 2.1 core software upwards. See Backward Compatibility 23 .
Manager Manager 8.1
Manager
Page 13
15-601011 Issue 25l (11 February 2011)
Manager Modes
The menus and options displayed by Manager vary depending on the actions you are performing. Manager can run in the
following modes.
Simplified View
This is Managers default mode when no IP Office
configuration has been opened.
Advanced Configuration Mode
32
When the configuration from a system running in IP Office
Standard Version mode is opened in Manager, it displays
options for this mode.
SCN Management Mode
817
Manager 8.1+ supports loading the combined
configurations from systems in a Small Community
Network. For more details see SCN Management 817 .
Manager Manager 8.1
Manager
Page 14
15-601011 Issue 25l (11 February 2011)
Manager:
Simplified Administration Mode
When the configuration from a system running in IP Office
Essential Edition - PARTNER® Version or IP Office
Essential Edition - Norstar Version mode is opened in
Manager, Manager switches to this alternate management
mode.
Embedded File Management
119
For systems with a memory card installed, Manager can
be used to view and manage the files stored on the card.
This is accessed through the File | Advanced |
Embedded File Management.. 119 . .
Upgrade Wizard
115
The Upgrade Wizard is a component of Manager used to
upgrade the firmware run by the control unit and
expansion modules within a system.
Security Configuration Mode
68
Manager can be used to edit the security settings of
systems running in IP Office Standard Version mode.
Manager Manager 8.1
Manager
Page 15
15-601011 Issue 25l (11 February 2011)
1.1 Installing Manager
Manager is a component of the IP Office Admin suite of applications. This suite is supplied on the IP Office Release 6.1
DVD. Alternatively, the Admin Suite can be downloaded from Avaya's support website http://support.avaya.com.
In addition to Manager, the IP Office Admin suite includes options to install the following applications:
· System Monitor
This is a tool for system installers and maintainers. Interpreting the information output by System Monitor requires
detailed data and telecoms knowledge.
· System Status Application
This is a Java application that can be used to monitor the status of the system such as extension, trunks and other
resources. It displays current alarms and most recent historical alarms.
· Call Status
This application is for pre-4.0 systems. For IP Office 4.0 and higher use the System Status Application. Manager
6.2+ is backwards compatible and can be used to manage systems running software from IP Office 2.1 upwards.
PC Requirements
Minimum PC Requirements
Operating System Support
RAM
256MB
Server OS:
Hard Disk Free Space
1GB*
2003 Server
Processor:
2008 Server
- Pentium
PIII 800MHz
Client OS:
- Celeron
Celeron 3 800Mhz
XP Professional
- AMD
Athlon Opteron, Athlon64/XP
Vista Business/Enterprise
Additional Apps:
- .NET2
Vista Ultimate
Installed with Manager if not
already present.
Windows 7
*Includes disk space required for .NET2 component.
· Language Support
The Manager application can run in English, French, German, Brazilian Portuguese, Dutch, Italian and Latin Spanish. By
default this determined by the best match to the PC's regional setting. The online help is only provided in English,
French and German. To change the language used see Changing the Manager Language 23 .
Ports
Component
Location - %ProgramFiles%\Avaya\IP Office\
Ports
Manager
Manager\manager.exe
TCP Port 50802.
TCP Port 50804.
TCP Port 50812.
UDP Port 50798.
IP Office Upgrade Wizard
Manager\upgradewiz.exe
UDP Port 50798.
Manager Manager 8.1
Manager
Page 16
15-601011 Issue 25l (11 February 2011)
Manager: Installing Manager
Installing Manager
If applications in the IP Office Admin Suite other than Manager are required, we strongly recommend that you refer to the
Manager Installation Manual.
· Note: This installation process will install Windows .NET2 if not already present. The installation of .NET2 may
require some systems to restart and the installation process to then be restarted.
1. If a pre-4.0 version of the IP Office Admin Suite is installed it must be removed. This is done using the Add or
Remove Programs option in the Windows Control Panel and selecting IP Office Admin Suite and then Remove.
2. If installing from the IP Office Admin DVD, insert the DVD and when the page is displayed click on the link for the IP
Office Admin suite. This will open a file windows showing the installation files for the suite. Locate and double-click
on the setup.exe file.
3. Select the language you want to use for the installation process. This does not affect the language used by Manager
when it is run. Click Next >.
4. If the following appears it indicates that a previous installation of the IP Office Admin suite has been detected.
Select Yes to upgrade the existing installed applications.
5. If required select the destination to which the applications should be installed. We recommend that you accept the
default destination. Click Next >.
6. The next screen is used to select which applications in the suite should be installed. Clicking on each will display a
description of the application. Click on the
next to each application to change the installation selection. When you
have selected the installations required, click Next >.
7. The applications selected are now ready to be installed. Click Next >.
8. Following installation, you will be prompted whether you want to run the IP Office Admin Suite. Selecting Yes runs
Manager.
9. On some versions of Windows, you may be required to restart the PC. Allow this to happen if required.
Changing the Installed Applications
The Add or Remove Programs option can be used to change the selection of IP Office Admin suite applications that are
installed. Locate IP Office Admin Suite in the list of programs and select Change.
Manager Manager 8.1
Manager
Page 17
15-601011 Issue 25l (11 February 2011)
1.2 Starting Manager
No operator name or password is required to start Manager. A name and password is only required when performing an
action that requires communication with a system.
When started, by default Manager will attempt discover any systems on the network. If it finds any it will display a list
from which you can select
1. Select Start and then Programs or All Programs depending on the version of Windows. Select the IP Office
program group.
2. Select
Manager. If a Windows Security Alert appears select Unblock to allow Manager to run.
3. By default Manager will scan the network for any systems. What appears next depends on whether it finds any
systems.
· If it finds multiple systems, it will display a list of those systems from which you can select the one whose
configuration you want to edit. If you want to open a configuration go to Opening a Configuration 19 . If you
don't want to load a configuration click on Cancel.
· If it finds a single system, it will attempt to open the configuration of that system by displaying the user name
and password request. If you want to open a configuration go to Opening a Configuration 19 . If you don't want
to load a configuration click on Cancel.
· If no systems are found or you cancel the steps above, the Manager simplified view is displayed.
4. Use the view to select the action you want to do.
· Create an Offline Configuration
60
· Open a Configuration from a System
19
· Read a Configuration from a File
Manager Manager 8.1
Manager
Page 18
15-601011 Issue 25l (11 February 2011)
Manager: Starting Manager
1.3 Opening a Configuration
The initial IP address ranges in which Manager searches for systems are set through the Manager preferences (File |
Preferences | Discovery 108 ). By default it scans the local network of the Manager PC.
1. Start Manager. If Manager is already started and a configuration is open in it, that configuration must be closed
first.
· If Manager is set to Auto Connect on start up 106 , it will scan for systems automatically and either display
the list of systems discovered or automatically start login to the only system discovered.
· Otherwise, click on
or select File | Open Configuration.
2. The Select IP Office window appears, listing those systems that responded.
· If Manager has been set with SCN Discovery 108 enabled, systems in a Small Community Network may be
grouped and can be loaded into Manager's SCN management 817 mode.
· If the system required was not found, the Unit/Broadcast Address used for the search can be changed.
Either enter an address or use the drop-down to select a previously used address. Then click Refresh to
perform a new search.
· The address ranges used by Manager for searching can be configured through the File | Preferences |
Discover 108 tab.
· A list of known systems can be stored and used. See Known System Discovery
· Manager can be configured to search using DNS names. See the Use DNS
108
59
option.
· Systems found but not supported by the version of Manager being used will be listed as Not Supported.
· If the IP500v2 system detected is running software other than from its primary folder, a
be shown next to it. The configuration can still be opened but only as a read-only file.
warning icon will
3. When you have located the system required, check the box next to the system and click OK.
4. The system name and password request is displayed. Enter the required details and click OK.
· IP Office 3.2 and higher systems:
The name and password used must match a Service User account configured within the system's security
settings.
Manager Manager 8.1
Manager
Page 19
15-601011 Issue 25l (11 February 2011)
· Pre-3.2 IP Office Systems:
The name must match a Manager operator and the password must match the system's system password. If the
name does not match a Manager operator, the config will still be loaded by using the Guest (read-only)
operator.
5. Additional messages will inform you about the success or failure of opening the configuration from the system.
6. Following a successful log in, the configuration is opened in Manager. The menus and options displayed will depend
on the type of system configuration loaded.
· PARTNER Version/Norstar Version Configuration
This Manager mode is used for configurations from systems running in PARTNER Version or Norstar Version
modes.
· IP Office Configuration
This Manager mode is used for configurations for systems running in IP Office Standard Version mode.
Manager Manager 8.1
Manager
Page 20
15-601011 Issue 25l (11 February 2011)
Manager: Opening a Configuration
Manager Manager 8.1
Manager
Page 21
15-601011 Issue 25l (11 February 2011)
Login Messages
While attempting to login to a system, various additional messages may be displayed.
Configuration Not Loaded Messages
· Access Denied
This is displayed as the cause if the service user name/password were incorrect, or the service user has insufficient
rights to read the configuration. The Retry option can be used to log in again but multiple rejections in a 10 minute
period may trigger events, such as locking the user account, set by the Password Reject Limit and Password Reject
Action options in the systems security settings.
· Failed to communicate with system
This is displayed as the cause if the network link fails, or the secure communication mode is incorrect (for example
Manager is set to unsecured, but the system is set to secure only).
· Account Locked
The account of the Service User name and password being used is locked. This can be caused by a number of
actions, for example too many incorrect password attempts, passing a fixed expiry date, etc. The account lock may
be temporary (10 minutes) or permanent until manually unlocked. An account can be enabled again through the
system's security settings.
Additional Messages
· Your service user account will expire in X days
This message indicates that an Account Expiry date has been set on the system service user account and that date
is approaching. Someone with access to the system's security settings will be required unlock the account and set a
new expiry date.
· Your password will expire in X days. Do you wish to change it now?
This message indicates that password ageing has been configured in the system's security settings. If your
password expires, someone with access to the system's security settings will be required to unlock the account.
· Change password
Through the system's security settings, a service user account can be required to change their password when
logging in. The menu provides fields for entering the old password and new password.
· Contact Information Check - This configuration is under special control
This message will appear if a Manager user with administrator rights has entered their contact information into the
configuration. For example to indicate that they do not want the configuration altered while a possible problem is
being diagnosed. The options available are:
· Cancel
Select this option to close the configuration without making any changes.
· Set configuration alteration flag
Select this option if the configuration is being opened because some urgent maintenance action. When the
configuration is next opened, the fact that it has been altered will be indicated on the System | System 143 tab.
· Delete Contact Information
Select this option to take the system out of special control.
· Leave contact information and flags unchanged (Administrators only)
This option is only available to service users logging in with administrator rights.
Manager Manager 8.1
Manager
Page 22
15-601011 Issue 25l (11 February 2011)
Manager: Opening a Configuration
1.4 Changing the Manager Language
The Manager application can run in US English, UK English, French, German, Brazilian Portuguese, Dutch, Italian
and Mexican Spanish. By default it tries to use the best match to the PC's regional location settings, otherwise it will use
UK English.
The process below can be used to run Manager in one of its supported languages. However it does not change the
language used for help file content.
1. Create a Windows shortcut to the Manager application .exe file. By default this file is located in C:\Program
Files\Avaya\IP Office\Manager\Manager.exe.
2. Right-click on the shortcut and select Properties.
3. The Target field can be used to specify the locale setting that Manager should use.
· For example, for Italian the Target should have -locale:it-IT added to the end. For example: "C:\Program
Files\Avaya\IP Office\Manager\Manager.exe" -locale:it-IT
4. The available locales for Manager are:
Manager Language
Shortcut Locale Setting
Brazilian Portuguese
-locale:pt-Br
Dutch
-locale:nl-NL
French
-locale:fr-FR
German
-locale:de-DE
Italian
-locale:it-IT
Mexican Spanish
-locale:es-MX
US English
-locale:en-US
5. Click OK.
6. Manager should now run in the selected language when launched using the updated shortcut.
1.5 Backward Compatibility
Manager is part of the IP Office Admin Suite of programs. It is important to note that the software level of Manager
application is 2 higher than the software level of the system core software with which it is released. For example Manager
6.2 was released with Manager 4.2 core software. The Manager application can be used to manage configurations from
systems running IP Office 2.1 core software.
When an IP Office 2.1 or higher configuration is loaded, Manager adjusts the settings and fields that it shows to match the
core software level of the system. If you attempt to load a pre-2.1 IP Office configuration, Manager will display an error
message and does not load the configuration.
· To receive a pre-3.2 IP Office configuration requires entry of an operator name and the system password.
· To receive a 3.2 or higher IP Office configuration requires entry of a service user name and password stored by that
system.
For IP Office 4.2+, Manager is able display systems with software levels it does not support in the Select IP Office
discovery menu, however those systems are indicated as not supported.
· Backwards compatibility is only supported for General Availability releases of <IP Office software. It is not
supported for private builds.
Manager Manager 8.1
Manager
Page 23
15-601011 Issue 25l (11 February 2011)
1.6 What's New in Release 6.1
IP Office 6.1 is supported on IP406v2, IP412, IP500 and IP500v2 systems.
· Phone Support
934
· Small Community Network Management
· one-X Portal for IP Office
934
· IP Office Customer Call Reporter
· Embedded Voicemail
934
935
935
· IP Office Essential Edition - PARTNER® Version
· IP Office Essential Edition - Norstar Version
· Voicemail Pro
937
· Music on Hold
937
935
937
Phones
The following additional phones and phone features are supported by IP Office 6.1:
· 1000 Series
The 1010 and 1040 SIP devices are HD video softphone devices. The main units provided connections for a variety
of video and audio inputs and outputs.
· 1100/1200 Series
The following phones from the Avaya range of SIP phones are supported: 1120E, 1140E, 1220 and 1230.
· Automatic Call Log Expiry
For call log entries written into a user's centralized call log, a expiry time can be set after which the call log entry is
automatically deleted from the user's call log.
· Mobile Twinning Handover (IP Office Release 6.1)
When on a call on the primary extension, pressing the Twinning button will make an unassisted transfer to the
twinning destination. This feature can be used even if the user's Mobile Twinning setting was not enabled.
· During the transfer process the button will wink.
· Pressing the twinning button again will halt the transfer attempt and reconnect the call at the primary
extension.
· The transfer may return if it cannot connect to the twinning destination or is unanswered within the user's
configured Transfer Return Time (if the user has no Transfer Return Time configured, a enforced time of
15 seconds is used).
· Show Last Call Duration
1400, 1600 and 9600 phones will briefly display the duration of a call after it is ended. This setting is a user
accessible option through the phone menu Features | Call Settings | Show Last Call Duration (except on 1403
and 1603 phones where it is on by default).
Small Community Network Management
Manager 8.1 is able to load and display the configuration of all systems in a Small Community Network. The configurations
can be edited and saved. When working in SCN management mode, Manager can also display a graphic view of the
network and allow the adding of additional systems and SCN lines between systems.
one-X Portal for IP Office
IP Office 6.1 supports one-X Portal for IP Office 6.1. one-X Portal for IP Office 6.1 provides the following new features:
· Adjustable Layout
The gadgets provided on the one-X Portal for IP Office's main page can now be moved, resized and minimized by
the user. The users positioning of the gadgets is retained between one-X Portal for IP Office sessions.
· Multi Directory Search
It is now possible to display results for a search across all directories (System, Personal and External).
· Call Assistant
The one-X Portal for IP Office Call Assistant is now supported for Windows based users of one-X Portal for IP Office.
The Call Assistant provides pop up messages about calls even when not logged into one-X Portal for IP Office,
screen popping to Outlook and hot key dialing of numbers.
Manager Manager 8.1
Manager
Page 24
15-601011 Issue 25l (11 February 2011)
Manager: What's New in Release 6.1
IP Office Customer Call Reporter
· Microsoft SQL 2008 Support
IP Office Customer Call Reporter is now supported using Microsoft SQL 2008.
· Visual Redesign
Some elements of the browser display have been redesigned.
· Many of the tabs used by Supervisors to move between the available pages have been replaced by icons.
· The color used for warnings has been changed from yellow to orange.
· New Supervisor Pages
Supervisors are able to access two new pages of call information in addition to the views that they share with their
agents.
· Dashboard Display
The dashboard display is the default page displayed to a supervisor when they login. They can customize it to
display a combination of up to three graphs and data display elements.
· Customer Map
Supervisors can display and configure a map that will plot calls based on caller ID numbers. The map can be
used to show a combination of historical and realtime calls and can be overlayed onto Google or Yahoo maps.
· Force Agent State
Supervisors can now force force a change to an agent's status. For example log an agent out or enable/disable an
agents queue membership. The IP Office Customer Call Reporter administrator configures which supervisors have
this function. This feature requires the IP Office Customer Call Reporter server to have access to a one-X Portal for
IP Office server.
· New Statistics
The following new statistics are available for use in views.
· Agent Productivity Factor · Talk Inbound
· Talk Average
· Talk Inbound Average
· Talk Internal
· Talk Outbound
· Talk Outbound Average
· Talk Total
· Report Templates
The follow changes have been made for historical reporting.
· The Call Summary Report now includes Average Answer Time when reporting on agents (previously this
value was blank when reporting on an agent or agents).
· A new template called the Agent Report Card template has been added. It provides historical reporting on
the Talk Time statistics.
· Message Color
When scheduling a wallboard message, supervisors can now select the color for the message.
· IP Office Customer Call Reporter Help
IP Office Customer Call Reporter help is now also available in French and Latin Spanish.
· Wallboard Controls
The wallboard Background and Content Settings now include options to adjust the animation effect applied to
changing statistic values and the aspect ratio used for the display of the wallboard elements.
Embedded Voicemail
· Skip Your Mailbox Greeting
Caller's can skip your mailbox greeting by pressing 1. Instead they immediately hear the tone for the start of
recording.
IP Office Essential Edition - PARTNER® Version
· Phantom Users
Previously user settings were only created and configurable for the physical extensions present in the system (and
excluding ports 7 and 8 on ETR6 cards). User settings are now created for all possible user extensions regardless
of whether a matching physical extension port is present or not.
· Calls to a phantom extension number go directly to that user's mailbox. This applies for normal dialing, DDI
call routing, line coverage, transfers and routing from an auto-attendant.
· Auto Attendant Enhancements
The following changes have been made to auto attendant support for IP Office Essential Edition - PARTNER®
Version 6.1.
· 9 Auto Attendants
Up to 9 auto attendants are now supported. Where a line is associated with an auto attendant the auto
attendant required can be selected.
Manager Manager 8.1
Manager
Page 25
15-601011 Issue 25l (11 February 2011)
· Transfer to Auto Attendant Action
This additional menu action allows calls to be routed from one auto attendant to another. When this
occurs, only the menu prompt of the new auto attendant is played.
· Language Selection
Each auto attendant can be configured with a language selection. The selected language controls the prompts
used by the auto attendant actions where applicable.
· Time Profile Dependant Menu Actions
In addition to controlling with initial greeting is played to callers, each auto attendants time profiles now also
control which set of menu actions are available to the callers with the appropriate time dependant menu
actions greeting.
· Selectable Night Service Mode
Previously when the system was put into night service, the auto attendant switched to its out of hours
greeting. Each auto attendant now has a Follow Night Service setting. If selected, the previously behavior
still applies. If not selected, when the system is put into night service, the auto attendant continues to follow
its own time profile settings.
· Picking Up Auto Attendant Calls
Bridging into a call being handled by an auto attendant drops the auto attendant from the call.
· Emergency Greeting
Each auto attendant can have a recorded emergency greeting and a setting for whether that greeting is active
or not. When active, the emergency greeting is played before any of the other auto attendant greetings. When
an emergency greeting is active, a warning is displayed on extensions 10 and 11.
· Transfer to Greeting Action
This additional menu action allows the caller to play and record the emergency greeting. It also allows
them to select whether the greeting is active or not. If a system password has been set, it is used to
restrict access to this option.
· Line Enhancements
· Unique Line Ringing
Each incoming line, channel or DID can be assigned a ringing pattern. That pattern is then used for incoming
calls on that line unless overridden by the user's setting.
· Assigning Lines to Auto Attendants
Previously assignment of a line to an auto attendant could only be done through the Manager. This option can
now be selected through the administrator menus on extensions 10 and 11.
· User Setting Enhancements
The following changes have been made to user support for IP Office Essential Edition - PARTNER® Version 6.1.
· Immediate Voicemail
The user setting for VMS Cover Ring can now be set to 0 for immediate voicemail.
· Transfer Return Extension
For users who have transfer return enabled, a different extension destination for the return calls can now be
specified.
· Override Line Ringing
For selected users the new Unique Line Ringing can be overridden.
· Language Control
Previously only individual users could be configured with a language selection. For IP Office Essential Edition PARTNER® Version 6.1 the default language selection can now be done at the system level. In addition a language
setting can be applied to each auto attendant.
· Embedded Voicemail Enhancements
The following changes have been made to the embedded voicemail provided to IP Office Essential Edition PARTNER® Version 6.1 users.
· Caller Post Message Options
After leaving a mailbox message, callers can now press # rather than hanging up immediately. The caller will
hear a prompt informing them whether the message has been saved or whether the messages was too short
(less than 3 seconds) and so was not saved.
· Skip Your Mailbox Greeting
Caller's can skip your mailbox greeting by pressing 1. Instead they immediately hear the tone for the start of
recording.
· Mark Messages as New
You can now change an old or saved message's status back to new while it is being played or just after it has
played by dialing *06. The message waiting light is relit. However if voicemail email is being used no new
message email is sent.
Manager Manager 8.1
Manager
Page 26
15-601011 Issue 25l (11 February 2011)
Manager: What's New in Release 6.1
IP Office Essential Edition - Norstar Version
To replace Avaya Norstar systems in the middle eastern market, IP500v2 systems can be configured to run in IP Office
Essential Edition - Norstar Version mode. This is done using a IP Office Essential Edition - Norstar Version System SD card.
Operation is similar to IP Office Essential Edition - PARTNER® Version except with no support for ETR phones.
· The locales supported for IP Office Essential Edition - Norstar Version are: Bahrain, Egypt,, Kuwait, Morocco, Oman,
Pakistan, Qatar and the United Arab Emirates.
· Automatic impedance matching is also available for the locales above.
· For embedded voicemail, Arabic language prompts are supported.
Voicemail Pro
The following features have been added to Voicemail Pro 6.1.
· Additional Generic Action String Manipulation Options
The String Manipulation command has two additional options. They are:
· Copy
This action can be used to copy the value of one variable to another variable. The command can copy the
whole value or can, treating the value as a string, copy a section to or from a specified matching character.
· Length
This action can be used to return the length of variable. It can return the full length or the length from or to a
specified matching character.
· Post Call Completion Call Flows
Call flows can be configured to continue running even after the caller has disconnected. If the current action which
the call had reached has a Timeout or Next result, the connection from that result is followed immediately until
the call flow either reaches a Disconnect action or an unconnected result.
· Automatic Call Recording for Internal Calls
The user and hunt group options for call recording can now be set to work for internal calls. Previously they only
applied to external calls.
Music on Hold
The following changes have been made for hold music support:
· Analog Extension Source
For alternate music on hold sources 2 to 4, the audio input to an analog extension port can be specified as the
source.
· Short Code Music on Hold Selection
For calls routed by short codes, including outgoing external calls, the hold music source for the call can be specified
using the h character in the short code telephone number.
IP Office Application Server
The IP Office Application Server is a Linux based server running server applications, currently Voicemail Pro and one-X
Portal for IP Office. It does not require Linux knowledge to install. The sever and the applications are managed remotely
via web browser and the existing Voicemail Pro client.
Miscellaneous Features
· Restrict Analog Extension Ringer Voltage
If this system setting is selected, the available message waiting lamp indication settings for analog extensions are
restricted to None and Line Reversal.
· Time Support
A number of changes have been made to the way that the systems time and date can be set.
· The existing RFC868 Time method using the Voicemail Pro server or Manager as the source is still supported.
Use of other RFC868 server sources is not supported.
· Using SNTP requests to a NTP server is now supported. When using SNTP, additional fields for the local time
offset and for daylight savings time (DST) settings are also available.
· If the time is being set manually through a system phone, the system can be configured with a manually
adjustable offset and or with automatic daylight savings time settings.
· The time settings, including the time server being used and whether DST is in use or not, can be viewed
through system phones.
Manager Manager 8.1
Manager
Page 27
15-601011 Issue 25l (11 February 2011)
· Restart IP Phones on System Upgrade
The Manager Upgrade Wizard now includes an option to restart all connected IP phones following a system
upgrade. This will cause those phones to check and, if necessary, upgrade their phone firmware following the
system upgrade.
· Multiple SIP Proxies
The use of multiple SIP proxy servers in SIP line settings is now supported. The multiple proxies can be specified by
IP address or obtained through DNS response (RFC3263). When specified by IP address, weighting can be applied
to each address.
Manager Manager 8.1
Manager
Page 28
15-601011 Issue 25l (11 February 2011)
Manager: What's New in Release 6.1
Manager Manager 8.1
Manager
Page 29
15-601011 Issue 25l (11 February 2011)
Chapter 2.
Configuration Mode
Manager Manager 8.1
Manager
Page 31
15-601011 Issue 25l (11 February 2011)
2. Configuration Mode
This section of the documentation covers the operation of Manager when being used to edit the configuration of a system
running in Manager mode.
This section is divided as follows.
The Configuration Mode Interface 33
This part details the screen elements of
Manager's configuration mode interface.
Editing Configuration Settings 49
This part details how Manager's configuration
mode can be used for the following tasks.
· The Menu Bar
· How the Configuration is Used
· Toolbars
37
· Loading a Configuration
38
· Using the Navigation Pane
· Using the Group Pane
41
· Using the Details Pane
· Using the Error Pane
· Altering the Interface
Manager Manager 8.1
Manager
43
45
46
40
49
55
· Creating a New Configuration
60
· Importing and Exporting Settings
· Sending a Configuration
61
64
· Saving a Configuration Offline
· Erasing the Configuration
63
65
Page 32
15-601011 Issue 25l (11 February 2011)
Configuration Mode: The Configuration Mode Interface
2.1 The Configuration Mode Interface
When Manager is in configuration mode, the screen elements shown are available. Some of these elements can be
customized, moved and hidden.
Manager Configuration Mode Screen Elements
· Title Bar 36
In addition to the application name, when configuration settings are loaded from a system, the title bar displays the
user name used to load the settings and the operator view applied.
· Menu Bar 37
The options available with the drop down menus provided here change according to whether Manager has a set of
configuration or security settings loaded or not.
· Main Toolbar 38
This toolbar provides icon shortcuts to the most frequently required configuration setting actions.
· Navigation Toolbar 38
This toolbar provides a set of drop downs which can be used to navigate to particular entries in the configuration
settings. The selected options in the navigation pane, the group pane and the details pane are synchronized with the
navigation toolbar and vice versa. This toolbar is particularly useful if you want to work with the group pane and or
navigation pane hidden in order to maximize the display space for the details pane.
· Navigation Pane 40
This pane shows icons for the different types of entry that the configuration can contain. Each type is followed by the
number of entries of that type already in the configuration. Selecting an icon displays the matching entries in the group
pane and navigation toolbar.
· Group Pane 41
This pane lists all the entries that match the type selected in the navigation pane or navigation toolbar. The list can be
sorted by clicking on column heading. Selecting an entry in this pane displays its details in the details pane.
· Details Pane 43
This pane shows the configuration settings for a particular entry within the configuration. The entry is selected using the
navigation toolbar or using the navigation pane and group pane.
· Error Pane 45
This pane shows errors and warnings about the configuration settings. Selecting an item here loads the corresponding
entry into the details pane.
· Status Bar 48
This bar display messages about communications between Manager and systems. It also displays the security level of
the communications by the use of a padlock icon.
Manager Manager 8.1
Manager
Page 33
15-601011 Issue 25l (11 February 2011)
2.2 Security Settings
The following applies for IP Office 3.2 and higher. Access to system settings is controlled by Service Users and Rights
Groups. stored in the control unit's security settings. These are stored separately from the system's configuration
settings. All actions involving communications between Manager and the system require a Service User name and
password. That Service User must be a member of a Rights Group with permissions to perform the required action.
In the example illustrated above:
· Service User X can read and write the configuration. However they can only edit Operator settings and can only
make changes that can be merged.
· Service User Y can read and write the configuration, edit all settings and make changes that require reboots.
· Service User Z can read and write the configuration, edit all settings and make changes that require reboots. They
can also access the security settings.
· The Security Administrator can only access the security settings.
Security Administrators
By default the security administrator is the only user who can access the system's security settings using Manager's
security mode.
Service Users
Each Service User has a name, a password and is a member of one or more Rights Groups.
Rights Groups
The Rights Groups to which a Service User belongs determine what actions they can perform. Actions available to Rights
Groups include configuration actions, security actions and system status actions:
Configuration
Security
System Status
· Read the configuration.
· Read all security settings.
· System Status Access.
· Write the configuration.
· Write all security settings.
· Read All Configuration.
· Merge the configuration.
· Reset all security settings.
(Manager 4.1+)
· Default the configuration.
· Reboot immediately.
· Write own password.
(Manager 4.1+)
· Reboot when free.
· Reboot at time of day.
Where a Service User has been configured as a member of more than one Rights Group, they combine the functions
available to the separate Rights Groups.
Manager Manager 8.1
Manager
Page 34
15-601011 Issue 25l (11 February 2011)
Configuration Mode: Security Settings
Operator Rights
Each Rights Group has a Manager Operator Rights setting. This setting controls what types of configuration entries
Manager will allow members of the Rights Group to view and what actions they can perform with those types of entries.
Operator
Administrator
Manager
View/Edit/
New/Delete
All
View all except WAN Port.
Edit
Extension, User, Hunt Group, Short Code, Service, RAS, Incoming
Call Route, Directory, Time Profile, Firewall Profile, IP Route, Least
Cost Route, Account Code, ARS, E911 System.
Delete
As edit except Short Code.
View
View all except WAN Port.
Edit
Extension, User, Hunt Group, Short Code, Service, RAS, Incoming
Call Route, Time Profile, Firewall Profile, IP Route, Least Cost Route,
Account Code, License, ARS, E911 System.
New
None.
Delete
User & Group Edit
View, edit create and delete all configuration entries.
View
New
Operator
Configuration Entry Types
View
Delete Incoming Call Route and Directory.
User and Hunt Group entries only.
Edit
New
None
Delete
User & Group Admin
All
User and Hunt Group entries only.
Dir & Account Admin
All
Directory and Account Code entries only.
Time & Attendant Admin
All
Time Profile and Auto Attendant entries only.
ICR & User Rights Admin
All
Incoming Call Route and User Rights entries only.
Read Only
View
View all configuration entries.
Edit
None.
New
Delete
Manager Manager 8.1
Manager
Page 35
15-601011 Issue 25l (11 February 2011)
2.3 Title Bar
The Manager title bar shows several bits of information.
· The Manager application version.
· The system name of the system from which the currently loaded configuration was received.
· The software level of the system's control unit.
· For IP Office 3.2+ systems, the service user name used to receive the configuration and that user's associated
operator rights. For pre-3.2 systems this is replaced with just the operator name.
Manager Manager 8.1
Manager
Page 36
15-601011 Issue 25l (11 February 2011)
Configuration Mode: Title Bar
2.4 The Menu Bar
Details of all the options that may be available within the Menu Bar drop downs
are contained in the section Menu Bar Commands 102 .
The commands are context sensitive. Commands are grayed out when not
useable.
For some commands, an symbol indicates that there are sub-commands from
which a selection can be made.
File
Open Configuration... 104
Close Configuration 104
Save Configuration 104
Save Configuration As... 104
Change Working Directory...
Preferences 106
105
Offline
Create New Config 112
Open File... 112
Send Config... 112
Receive Config... 112
Advanced
Erase Configuration (Default) 113
Reboot 113
System Shutdown... 114
Upgrade.. 115
Change Mode... 116
Audit Trail... 118
Security Settings... 119
Erase Security Settings... 119
Embedded File Management 119
Format IP Office SD Card 121
Recreate IP Office SD Card 122
Memory Card Command
125
Shutdown...
125
Start Up...
Voicemail Pro 124
System Status 124
LVM Greeting Utility
Manager Manager 8.1
Manager
124
Backup/Restore
Backup Binaries and Configurations 125
Restore Binaries and Configurations 125
Import/Export
Import 127
Export 126
Exit
125
127
View
Toolbars 128
Navigation Pane 128
Group Pane 128
Details Pane 128
Error Pane 128
Simplified View 128
TFTP Log 129
Tools
Extension Renumber 130
Line Renumber 130
Connect To 130
SCN Service User Management
Busy on Held Validation 131
MSN 132 Configuration 132
Print Button Labels 133
130
Page 37
15-601011 Issue 25l (11 February 2011)
2.5 Toolbars
The following toolbars are described here:
· Main Toolbar.
· Navigation Toolbar.
· Details Toolbar.
The Main Toolbar
This toolbar is also available when Manager is in security mode. However many of the controls will not function in security
mode.
·
Open Configuration from a System 55
Advertises to the address currently shown in the Manager's title bar for any available systems. A list of responding
systems is then displayed. When a system is selected from this list, a valid user name and password must be
entered. Equivalent to File | Open Configuration.
·
Open Configuration File 55
Open a configuration file stored on a PC. The button can be clicked to display a browse window. Alternatively the
adjacent
arrow can be used to drop-down a list of the last 4 previously opened configuration files. Equivalent to
File | Offline | Open File.
·
Save Configuration File 64
The action of this icon depends on whether the currently loaded configuration settings were received from a system
or opened from a file stored on PC. If the former applies, the menu sending the configuration back to the system is
displayed. In the latter case, the file changes are saved to the original file. Equivalent to File | Save
Configuration.
·
Collapse All Groups 40
Causes all
symbols in the navigation pane to be collapsed to
·
Show/Hide the Navigation Pane
·
Show/Hide the Group Pane
·
Show/Hide the Error Pane
symbols.
40
41
45
·
Validate Configuration 45
Runs a validation on all the currently loaded configuration settings. The results appear in the error pane. By default
the configuration is automatically validated when loaded and changes are validated when made, however the
validation preferences can be changed through File | Preferences | Validation 112 .
·
Create New Configuration 60
Runs a series of dialogs that create a new configuration from scratch.
·
Connect To 130
For a standalone system, start the process of adding it to a Small Community Network.
·
Voicemail Pro Client 124
Launch the Voicemail Pro client if also installed on the Manager PC.
Manager Manager 8.1
Manager
Page 38
15-601011 Issue 25l (11 February 2011)
Configuration Mode: Toolbars
The Navigation Toolbar
This toolbar provides drop down lists which can be used to navigate to particular entries in the configuration settings. The
selected options in the navigation pane, group pane and the details pane are synchronized with the navigation toolbar and
vice versa. This toolbar is particularly useful if you want to work with the group pane and or navigation pane hidden in
order to maximize the display space for the details pane.
This toolbar is not available when Manager is in security mode
68
.
Details Toolbar
This toolbar is shown in the top-right of the details pane.
·
Create New Record
The
arrow is used to select the entry type to be created. For example; when adding an extension clicking
allow selection of a VoIP Extension or IP DECT Extension.
·
Delete Entry
·
Validate Entry
may
· < > Show Previous/Next Entry
Moving to the Previous or Next Entry
1. Click < or > at the top-right to move to the previous or next entry.
Altering the Toolbars
Showing or Hiding Toolbars
The different toolbars can be hidden if not required.
1. Select View and then Toolbars. Those toolbars currently shown are indicated by a tick mark.
2. To show or hide a toolbar, click on its name.
Moving Toolbars
The position of the Manager toolbars can be moved. Note that when moving a toolbar, the other toolbars and panes may
adjust their size or position to ensure that all the toolbar icons remain visible.
1. Place the cursor over the end of the toolbar.
2. When the cursor changes to a four-way arrow, click and hold the cursor.
3. Move the toolbar to the required position and release the cursor.
Manager Manager 8.1
Manager
Page 39
15-601011 Issue 25l (11 February 2011)
2.6 Using the Navigation Pane
This pane shows icons for the different types of entry that the configuration
can contain. Each type is followed by the number of entries of that type
already in the configuration.
Selecting an icon displays the matching entries in the group pane and
navigation toolbar.
Where
or
icons appear in the pane, they allow the structure to be
expanded or collapsed. When the group pane is hidden,
and
icons are
shown for each entry type and allow the entry type to be expanded to
display all the existing entries of that type.
icon in the main toolbar can also be used to collapse all the
The
expanded entry types shown in the navigation pane.
The BOOTP and Operator icons are special. They represent settings stored
on the Manager PC rather than configuration settings received from a
system.
When Manager is used in security mode, this pane is also used by Manager
in security mode 68 to display entries for security settings.
Navigation Pane Actions
Moving the Border Between the Panes
The border between the visible panes can be adjusted. Note that this is a
proportional rather than exact position. If the whole window size is altered,
the border position may also move.
1. Place the cursor over the border between two panes.
2. When the cursor changes to a double headed arrow with a bar
through it, click and hold the cursor.
3. Drag the border to the required position and release the cursor.
Showing or Hiding Panes
The navigation pane can be shown or hidden. To do this use either of the
following methods.
icon or select View. Those panes
1. From the main toolbar, use the
currently shown are indicated by a tick mark.
2. To show or hide the navigation pane, click on its name.
Changing the Size of Configuration Icons
The size of the icons used on the navigation pane and details pane can be
adjusted.
1. Select File and then Preferences.
2. Select the Visual Preferences tab.
3. Select the required icon size from Small, Medium or Large.
4. Click OK.
Manager Manager 8.1
Manager
Page 40
15-601011 Issue 25l (11 February 2011)
Configuration Mode: Using the Navigation Pane
2.7 Using the Group Pane
This pane lists all the entries that match the type selected in the navigation pane or navigation toolbar. The list can be
sorted by clicking on a column heading. Selecting an entry in this pane displays its details in the details pane.
The icons used in the pane may vary according to the state of the entry. For example, some of the users shown in this
example have been configured for hot desking. This pane is also used by Manager in security mode 68 to display entries
for security settings.
Group Pane Actions
Sorting the List
The entries shown in the group pane can be sorted using any of the columns displayed.
1. To sort the list using the details in a particular column, click on the column header.
2. Clicking on the same column header again reverses the sort order.
Customizing the Columns Displayed
For each entry type, which details are shown in the group pane can be customized. Also the order of the column can be
adjusted. For details of the options available for each type of entry see Appendix D: Miscellaneous.
1. Right-click on the pane and select Customize Columns.
2. To add a column, selects its name in the left-hand Available Columns list and click >> to move it to the right-hand
Selected Columns list.
3. To remove a column, select its name in the right-hand Selected Columns list and click << to move it to the left-hand
Available Columns list.
4. To change the order of the Selected Columns, click on a column name and use the ^ and V controls.
5. Click OK.
Changing the Column Widths
1. In the column headers, place the cursor over the border between two columns.
2. When the cursor changes to a double headed arrow with a bar through it, click and hold the cursor.
3. Drag the border to the required position and release the cursor.
Manager Manager 8.1
Manager
Page 41
15-601011 Issue 25l (11 February 2011)
Adding a New Entry
The group pane can be used to add a new entry of the type currently displayed.
1. Right-click on the pane and select New.
· A arrow symbol next to New indicates that you can select a particular type of new entry to create. Click the arrow
and select an option from the list.
2. Use the details pane to configure the new entry.
3. Click OK in the details pane.
Deleting an Entry
1. Select the entry to be deleted by clicking on it.
2. Right-click on the pane and select Delete.
Validating an Entry
1. Select the entry to be validated by clicking on it.
2. Right-click on the pane and select Validate.
Show in Groups
This command groups the items shown in the group pane. The grouping method will vary depending on the entry type
being listed. For example, short codes are grouped based on short code feature type such as all forwarding short codes
together.
1. Right-click on the pane and select Show In Groups.
Moving the Border Between the Panes
The border between the visible panes can be adjusted. Note that this is a proportional rather than exact position. If the
whole window size is altered, the border position may also move.
1. Place the cursor over the border between two panes.
2. When the cursor changes to a double headed arrow with a bar through it, click and hold the cursor.
3. Drag the border to the required position and release the cursor.
Showing or Hiding Panes
The group pane can be shown or hidden. To do this use either of the following methods.
1. From the main toolbar, use the
icon.
or
1. Select View. Those panes currently shown are indicated by a tick mark.
2. To show or hide the group pane, click on its name.
Changing the Size of Configuration Icons
The size of the icons used on the navigation pane and details pane can be adjusted.
1. Select File and then Preferences.
2. Select the Visual Preferences tab.
3. Select the required icon size from Small, Medium or Large.
4. Click OK.
Manager Manager 8.1
Manager
Page 42
15-601011 Issue 25l (11 February 2011)
Configuration Mode: Using the Group Pane
2.8 Using the Details Pane
Whenever a selection is made through the group pane or the navigation toolbar, the settings for the matching entry are
shown in the details pane. This pane is also used by Manager in security mode 68 to display entries for security settings.
The details are grouped into tabs. The tabs available may vary depending on what particular type of entry is being viewed.
For example, for extension entries the Analog tab is only shown for analog extensions.
Individual settings may also be grayed out. This indicates that they are either for information only or that they cannot be
used until another setting is enabled.
The top-left icon indicates the following:
Locked
Indicates that you can view the settings but cannot change them.
Editable
Indicates that you can change the settings if required.
Changed
Indicates that the settings have been changed since the tab was opened. Click OK to save the changes or Cancel to
undo.
Various icons may appear adjacent to settings:
Locked Setting
The setting cannot be changed through this tab. This icon appears on user settings where the user is associated
with User Rights that controls the setting.
Information
Indicates a value which does not have to be set but may be useful if set.
Warning
A warning indicates a configuration setting value that is not typical and may indicate misconfiguration.
Error
An error indicates a configuration setting value that is not supported by the system. Such settings may cause the
system to not operate as expected.
Manager Manager 8.1
Manager
Page 43
15-601011 Issue 25l (11 February 2011)
Details Pane Actions
Editing an Entry
1. The method of entering an entry varies as different fields may use different methods. For example text entry boxes or
drop down lists.
2. By default when changes are made, they are validated once another field is selected. See File | Preferences | Validation
112 .
3. Clicking on OK at the base of the details pane to accept the changes or click on Cancel to undo the changes.
Adding a New Entry
1. Click
at the top-right of the details pane.
2. Select the type of entry required. For example, with services you can select from Normal, WAN or Intranet.
Deleting an Entry
1. Click
at the top-right of the details pane.
Validating an Entry
1. Click
at the top-right of the details pane.
Moving to the Previous or Next Entry
1. Click < or > at the top-right to move to the previous or next entry.
Selecting a Tab
1. To view the detail stored on a particular tab, click on the name of that tab.
controls if shown on the right to scroll through the available tabs. The
2. If the tab required is not shown, use the
tabs available may vary depending on what particular type of entry is being viewed.
Changing the Position of the Details Pane
When the group pane is visible, the details pane is shown either below it or to its right. This position can be adjusted.
1. Select View and then Details Pane.
2. The current position setting is indicated by a tick mark.
3. To select a position, click on it.
Changing How the Tabs Display
For entries with more than two tabs, you can select whether Manager should use
multiple rows when necessary.
controls or arrange the tabs as
1. Select Files | Preferences | Visual Preferences.
2. Select Multi-Line Tabs.
3. Click OK.
Manager Manager 8.1
Manager
Page 44
15-601011 Issue 25l (11 February 2011)
Configuration Mode: Using the Details Pane
2.9 Using the Error Pane
Validation is a process where Manager checks configuration entries for errors or for values for which it regards as requiring
a warning. The results of this checking are shown by icons next to the field that caused the error or warning, All errors and
warnings are also listed in the Error Pane.
By default validation is performed automatically whenever a configuration file is opened and when any field is edited.
However, if required, the use of automatic validation can be controlled through the settings on the File | Preference |
Validation 112 tab.
The validation process can be run manually using the
entry.
icon for the whole configuration or the
icon for a particular
The icons used for errors and warnings are:
Error
An error indicates a configuration setting value that is not supported by the system. Such settings are likely to
cause the system to not operate as expected.
Warning
A warning indicates a configuration setting value that is not typical and may indicate misconfiguration.
Information
Typically indicates a setting which may be useful to set.
Error Pane Actions
Revalidating Configuration Settings
By default, the configuration is validated when loaded and individual entries are revalidated when changed.
1. To validate the whole configuration, click
2. For a particular entry, click
in the main toolbar.
in the details pane.
Jumping to an Error or Warning
1. Clicking on an error or warning in the error pane will load the matching entry tab into the details pane.
2. The < and > can be used to move to the next error or warning in the error pane.
Showing or Hiding Panes
The error pane is automatically displayed if a configuration containing errors or warnings is loaded into Manager. However
it can be manually shown or hidden using either of the following methods.
1. From the main toolbar, use the
icon.
or
1. Select View. Those panes currently shown are indicated by a tick mark.
2. To show or hide the error pane, click on its name.
Manager Manager 8.1
Manager
Page 45
15-601011 Issue 25l (11 February 2011)
2.10 Altering the Interface
The Manager configuration settings interface can be customized in a number of ways. These changes are remembered the
next time Manager is started.
Resizing the Manager Window
When the Manager window is not maximized or minimized, it size can be adjusted.
1. Place the cursor over the edge of the current window.
2. When the cursor changes to a double-headed arrow, click and hold the cursor.
3. Drag the edge to the required position and then release the cursor.
Moving the Border Between the Panes
The border between the visible panes can be adjusted. Note that this is a proportional rather than exact position. If the
whole window size is altered, the border position may also move.
1. Place the cursor over the border between two panes.
2. When the cursor changes to a double headed arrow with a bar through it, click and hold the cursor.
3. Drag the border to the required position and release the cursor.
Showing or Hiding Toolbars
The different toolbars can be hidden if not required.
1. Select View and then Toolbars. Those toolbars currently shown are indicated by a tick mark.
2. To show or hide a toolbar, click on its name.
Moving Toolbars
The position of the Manager toolbars can be moved. Note that when moving a toolbar, the other toolbars and panes may
adjust their size or position to ensure that all the toolbar icons remain visible.
1. Place the cursor over the end of the toolbar.
2. When the cursor changes to a four-way arrow, click and hold the cursor.
3. Move the toolbar to the required position and release the cursor.
Showing or Hiding Panes
The details pane cannot be hidden. The navigation pane, group pane and error pane can be shown or hidden. To do this
use either of the following methods.
1. From the main toolbar, use the following icons:
·
Hide/Show Navigation Pane.
·
Hide/Show Group Pane.
·
Hide/Show Error Pane.
or
1. Select View. Those panes currently shown are indicated by a tick mark.
2. To show or hide a pane, click on its name.
Manager Manager 8.1
Manager
Page 46
15-601011 Issue 25l (11 February 2011)
Configuration Mode: Altering the Interface
Changing the Position of the Details Pane
When the group pane is visible, the details pane is shown either below it or to its right. This position can be adjusted.
1. Select View and then Details Pane.
2. The current position setting is indicated by a tick mark.
3. To select a position, click on it.
Changing the Size of Configuration Icons
The size of the icons used on the navigation pane and details pane can be adjusted.
1. Select File and then Preferences.
2. Select the Visual Preferences tab.
3. Select the required icon size from Small, Medium or Large.
4. Click OK.
Changing How the Tabs Display
For entries with more than two tabs, you can select whether Manager should use
multiple rows when necessary.
controls or arrange the tabs as
1. Select Files | Preferences | Visual Preferences.
2. Select Multi-Line Tabs.
3. Click OK.
Manager Manager 8.1
Manager
Page 47
15-601011 Issue 25l (11 February 2011)
2.11 The Status Bar
The status bar at the base of the Manager screen is used to display icons and messages about communications between
Manager and systems. If the Manager is also acting as a BOOTP and TFTP server it will also show BOOTP and TFTP
messages.
A padlock icon is displayed whenever the Manager communications settings are set to secure. This indicates all attempted
configuration and security settings exchanged will be attempted over a secure TLS link:
Status bar messages display information about communications the Manager application receives. Some typical status bar
messages are listed below.
· Ready
This message is normally seen when Manager has just started and no configuration has been received.
· Received BOOTP request for 001125465ab2, unable to process
Manager is acting as a BOOTP server. It has received a BOOTP request that does not match a system listed in its
BOOTP entries. The cause may be a device or application, other than an Manager, that also uses BOOTP.
· TFTP: Received TFTP Error "NotFound" from 192.168.42.1
An attempt to receive settings from or send settings to the system failed. The most probable cause is a name or
password error.
· TFTP: Received 17408 bytes for Marks_Test
Manager has received configuration settings from the named system using TFTP.
· Sent 100% of C:\Program Files\Avaya\IP Office\Manager\b10d01b2_3.bin
Manager has sent the indicated file in response to a BOOTP request.
Manager Manager 8.1
Manager
Page 48
15-601011 Issue 25l (11 February 2011)
Configuration Mode: The Status Bar
2.12 Editing Configuration Settings
Before editing the system's configuration settings, it is important to understand how those settings are stored and used by
the system.
· The control unit holds copies of its configuration in both its internal non-volatile and RAM memory. A copy is also
held on the System SD card (IP500v2).
· The copies in non-volatile memory and System SD card, are retained even if power to the control unit is removed.
· During power up, the system loads the configuration file stored on the System SD card into its RAM memory. Other
systems load the configuration stored in non-volatile memory into RAM memory. The copy in RAM memory is then
used to control the system's operation.
· If the system encounters a problem using the configuration file in its System SD card's /primary folder, it
attempt to use the copy in its non-volatile memory. For fully details of the IP500v2 boot process and SD card
usage refer to the Manager Installation Manual.
· Users actions such as changing their forward destinations or mailbox passcode are written to the configuration in
RAM memory.
· Changes made using Manager are written to the configuration in non-volatile memory and then copied into the RAM
memory and System SD.
· Between 00:00 and 00:30, a daily backup occurs which copies the configuration in the system's operation RAM
memory back into its non-volatile memory and, on IP500v2 system's, the System SD card. For IP Office Release
6.1 and higher: On IP500v2 system, the contents of the system memory cards /primary folder can then also be
automatically copied to the /backup folder by enabling System | System | Automatic Backup Command 143 .
· When the system is shutdown using the correct shutdown method
to the non-volatile memory and System SD card.
Manager Manager 8.1
Manager
114 ,
the configuration in RAM memory is copied
Page 49
15-601011 Issue 25l (11 February 2011)
Using Manager
When using Manager to edit the configuration settings, the following need to be remembered:
· Manager receives the current configuration settings from RAM memory. Therefore the configuration is receives
includes any changes made by users up to that time. However it will not contain any subsequent changes made by
users.
· When sending the configuration settings back to the system, Manager allows two choices, reboot or merge.
· Reboot sends the configuration to the system's non-volatile memory along with an instruction to reboot.
Following the reboot, the new configuration in non-volatile memory is copied to the RAM memory and used.
· Merge sends the configuration to the system's non-volatile memory without rebooting. The system then copies
those changes that are mergeable into the RAM memory. A key point here is that not all configuration settings
are mergeable, see the Mergeable Settings 51 list.
As a result of the above, it is important to bear the follow scenarios in mind:
· Changes made by users after a configuration is received by Manager may be lost when the configuration is sent
back from Manager. Therefore it is preferable to always edit a recently received copy of the configuration rather
than one that has been open for a period of time.
· If a merge is attempted with non-mergeable changes, those items will be written to the non-volatile memory but
will not be copied to RAM memory. If a daily backup occurs, they will then be overwritten by the RAM. If a power
loss reboot occurs, they will be written to RAM memory.
Manager Manager 8.1
Manager
Page 50
15-601011 Issue 25l (11 February 2011)
Configuration Mode: Editing Configuration Settings
2.12.1 Mergeable Settings
The table below shows the configuration entries for which changes can be merged and those that require a system reboot.
The Send Configuration menu shown when sending a configuration to the system automatically indicates when the
configuration is mergeable.
Mergeable
3.2+
System
142
- System
148
156
350
Directory
358
360
Firewall Profile
*3
160
IP Route
169
- System Events
- CDR/SMDR
- Twinning
172
370
Account Code
185
License
Extension
367
Least Cost Route
179
177
Control Unit
250
Tunnel
*4
251
378
380
Logical LAN
Wireless
262
375
385
386
Hunt Group
304
User Rights
Short Code
330
Auto Attendant
Service
RAS
362
150
- LDAP
User
WAN Port
Pre-3.2
*2
157
- Telephony
Line
3.2+
Time Profile
- Voicemail
- VoIP
Mergeable
*1
143
- LAN1/LAN2
- DNS
Pre-3.2
400
Authorization Code
331
404
ARS
340
Incoming Call Route
389
407
E911 System
342
421
· *1 - 3.2+ | System | System
Changes to Locale, License Server IP Address and Favor RIP Routes over Static require a reboot.
· *2 - 3.2+ | System | Voicemail
Changes to Voicemail Type require a reboot.
· *3 - 3.2+ | System | Telephony
Changes to Companding LAW and Busy Tone Detection require a reboot.
· *4 - 4.1+ | Extension
Base Extension and Disable Speakerphone are mergeable.
2.12.2 Configuration Sizes
There are maximum size limits to the configuration file that can be loaded into a control unit. They are:
Control Unit
Manager Manager 8.1
Manager
Maximum
Configuration File
Size
Small Office Edition
192KB
IP403
192KB
IP406 V1
192KB
IP406 V2
384KB
IP412
1.0MB
Page 51
15-601011 Issue 25l (11 February 2011)
IP500
1.0MB
IP500v2
2.0MB
· When you attempt to save a configuration that is too large, you will be prompted and the save is canceled.
· During normal operation, additional configuration entries can be added to the configuration without using Manager
(for example call log entries and directory entries made from phones). If, during the overnight backup to flash
memory 49 , the configuration if found to be too large, entries will be removed until the configuration is sufficiently
small to be backed up. The entries removed are call log records, system directory records and then personal
directory in that order. Note that those entries will still exist in the configuration running the system in its RAM
memory, however if the system is restarted they will disappear as the configuration is reloaded from the Flash
memory.
Figures for all individual entries in the configuration cannot be given as they vary. The list below gives typical values, in
bytes, for common entries:
Physical Extension: 70.
Intranet Service: 240.
Firewall Profile: 40.
IP Extension: 70.
WAN Service: 400.
Custom Firewall Entry: 80.
User: 170.
RAS Service: 110.
IP Route (Static): 30.
User Short Code: 40.
Incoming Call Route: 30.
License Key: 40.
DSS Button: 20.
WAN Port (PPP): 70.
Account Code: 40.
Hunt Group: 100.
WAN Port (FR): 120.
Logical LAN: 60.
Hunt Group member: 10.
Directory Entry: 70.
Tunnel (L2TP): 200.
System Short Code: 10.
Time Profile: 40.
Tunnel (IPSec): 110.
Normal Service: 220.
Time Profile Entry: 20.
Manager Manager 8.1
Manager
Page 52
15-601011 Issue 25l (11 February 2011)
Configuration Mode: Editing Configuration Settings
2.12.3 Setting the Discovery Addresses
or File | Open configuration is selected, Manager's Select IP Office menu appears. It performs a
By default, when
UDP broadcast to the address 255.255.255.255. This broadcast will only locate systems that are on the same network
subnet as the PC running Manager.
The process above is called discovery. A UDP broadcast will not be routed to other networks and subnets. Therefore to find
systems not located on the same subnet as the Manager PC, the following other options are supported.
· Specific Addressing
The Unit/Broadcast Address shown on the Select IP Office menu can be changed to the specific IP address of
the required system. A single address is routable and so can be used to discover a system on another subnet.
· TCP Discovery Address Ranges
IP Office 3.2+ systems support discovery by TCP as well as UDP. A set of TCP addresses and address ranges can be
specified for use by the Select IP Office discovery process.
· Known System Discovery 59
Manager can write the details of systems it discovers to a file. The list of systems in that file can then be used for
access to those systems. See Known System Discovery 59 .
· DNS Lookup
Manager can be configured to locate systems using DNS name lookup. This requires the systems on a customer
network to be added as names on the customer's DNS server and the Manager PC to be configured to use that
server for DNS name resolution. The use of DNS is configured through File | Preferences | Discovery 108 .
Manager Manager 8.1
Manager
Page 53
15-601011 Issue 25l (11 February 2011)
Changing the Initial Discovery Settings
The Discovery tab of the Manager Preferences menu can be used to set the UDP and TCP addresses used by the discovery
process run by the Select IP Office menu.
1. Select File | Preferences menu.
2. Select the Discovery tab.
· TCP Discovery: Default = On. Software level = 3.2+.
This setting controls whether Manager uses TCP to discover systems. The addresses used for TCP discovery are set
through the IP Search Criteria field below.
· NIC IP/NIC Subnet
This area is for information only. It shows the IP address settings of the LAN network interface cards (NIC) in
the PC running Manager. Double-click on a particular NIC to add the address range it is part of to the IP Search
Criteria. Note that if the address of any of the Manager PC's NIC cards is changed, the Manager application
should be closed and restarted.
· IP Search Criteria
This section is used to enter TCP addresses to be used for the TCP discovery process. Individual addresses can
be entered separated by semi-colons, for example 135.164.180.170; 135.164.180.175. Address ranges can be
specified using dashes, for example 135.64.180.170 - 135.64.180.175.
· UDP Discovery: Default = On
This settings controls whether Manager uses UDP to discover systems. Pre-3.2 systems only respond to UDP
discovery. By default IP Office 3.2 and higher systems also respond to UDP discovery but that can be disabled
through the system's security settings.
· Enter Broadcast IP Address: Default = 255.255.255.255
The broadcast IP address range that Manager should used during UDP discovery. Since UDP broadcast is not
routable, it will not locate systems that are on different subnets from the Manager PC unless a specific address
is entered.
· Use DNS: Software level = Manager 6.2+.
Selecting this option allows Manager to use DNS name (or IP address) lookup to locate a system. Note that this
overrides the use of the TCP Discovery and UDP Discovery options above. This option requires the system IP
address to be assigned as a name on the users DNS server. When selected, the Unit/Discovery Address field on
the Select IP Office 55 dialogue is replaced by a Enter Unit DNS Name or IP Address field.
· SCN Discovery: Software level = Manager 8.1+.
If enabled, when discovering systems, the list of discovered systems will group systems in the same Small
Community Network and allow them to be loaded as a single configuration. At least one of the systems in the SCN
must be running Release 6.0 or higher software. See SCN Management 817 . This does not override the need for
each system in the SCN to also be reachable by the TCP Discovery and or UDP Discovery settings above and
accessible by the router settings at the Manager location.
Manager Manager 8.1
Manager
Page 54
15-601011 Issue 25l (11 February 2011)
Configuration Mode: Editing Configuration Settings
2.12.4 Opening a Configuration from a System
The initial IP address ranges in which Manager searches for systems are set through the Manager preferences (File |
Preferences | Discovery 108 ). By default it scans the local network of the Manager PC.
1. Start Manager. If Manager is already started and a configuration is open in it, that configuration must be closed
first.
· If Manager is set to Auto Connect on start up 106 , it will scan for systems automatically and either display
the list of systems discovered or automatically start login to the only system discovered.
· Otherwise, click on
or select File | Open Configuration.
2. The Select IP Office window appears, listing those systems that responded.
· If Manager has been set with SCN Discovery 108 enabled, systems in a Small Community Network may be
grouped and can be loaded into Manager's SCN management 817 mode.
· If the system required was not found, the Unit/Broadcast Address used for the search can be changed.
Either enter an address or use the drop-down to select a previously used address. Then click Refresh to
perform a new search.
· The address ranges used by Manager for searching can be configured through the File | Preferences |
Discover 108 tab.
· A list of known systems can be stored and used. See Known System Discovery
· Manager can be configured to search using DNS names. See the Use DNS
108
59
option.
· Systems found but not supported by the version of Manager being used will be listed as Not Supported.
· If the IP500v2 system detected is running software other than from its primary folder, a
be shown next to it. The configuration can still be opened but only as a read-only file.
warning icon will
3. When you have located the system required, check the box next to the system and click OK.
4. The system name and password request is displayed. Enter the required details and click OK.
· IP Office 3.2 and higher systems:
The name and password used must match a Service User account configured within the system's security
settings.
Manager Manager 8.1
Manager
Page 55
15-601011 Issue 25l (11 February 2011)
· Pre-3.2 IP Office Systems:
The name must match a Manager operator and the password must match the system's system password. If the
name does not match a Manager operator, the config will still be loaded by using the Guest (read-only)
operator.
5. Additional messages will inform you about the success or failure of opening the configuration from the system.
6. Following a successful log in, the configuration is opened in Manager. The menus and options displayed will depend
on the type of system configuration loaded.
· PARTNER Version/Norstar Version Configuration
This Manager mode is used for configurations from systems running in PARTNER Version or Norstar Version
modes.
· IP Office Configuration
This Manager mode is used for configurations for systems running in IP Office Standard Version mode.
Manager Manager 8.1
Manager
Page 56
15-601011 Issue 25l (11 February 2011)
Configuration Mode: Editing Configuration Settings
Manager Manager 8.1
Manager
Page 57
15-601011 Issue 25l (11 February 2011)
Login Messages
While attempting to login to a system, various additional messages may be displayed.
Configuration Not Loaded Messages
· Access Denied
This is displayed as the cause if the service user name/password were incorrect, or the service user has insufficient
rights to read the configuration. The Retry option can be used to log in again but multiple rejections in a 10 minute
period may trigger events, such as locking the user account, set by the Password Reject Limit and Password Reject
Action options in the systems security settings.
· Failed to communicate with system
This is displayed as the cause if the network link fails, or the secure communication mode is incorrect (for example
Manager is set to unsecured, but the system is set to secure only).
· Account Locked
The account of the Service User name and password being used is locked. This can be caused by a number of
actions, for example too many incorrect password attempts, passing a fixed expiry date, etc. The account lock may
be temporary (10 minutes) or permanent until manually unlocked. An account can be enabled again through the
system's security settings.
Additional Messages
· Your service user account will expire in X days
This message indicates that an Account Expiry date has been set on the system service user account and that date
is approaching. Someone with access to the system's security settings will be required unlock the account and set a
new expiry date.
· Your password will expire in X days. Do you wish to change it now?
This message indicates that password ageing has been configured in the system's security settings. If your
password expires, someone with access to the system's security settings will be required to unlock the account.
· Change password
Through the system's security settings, a service user account can be required to change their password when
logging in. The menu provides fields for entering the old password and new password.
· Contact Information Check - This configuration is under special control
This message will appear if a Manager user with administrator rights has entered their contact information into the
configuration. For example to indicate that they do not want the configuration altered while a possible problem is
being diagnosed. The options available are:
· Cancel
Select this option to close the configuration without making any changes.
· Set configuration alteration flag
Select this option if the configuration is being opened because some urgent maintenance action. When the
configuration is next opened, the fact that it has been altered will be indicated on the System | System 143 tab.
· Delete Contact Information
Select this option to take the system out of special control.
· Leave contact information and flags unchanged (Administrators only)
This option is only available to service users logging in with administrator rights.
2.12.5 Opening a Configuration Stored on PC
A configuration file previously saved on the PC can be reopened in Manager. This method of access does not require entry
of a Service User name and password. All parts of the configuration are visible.
Use either of the following processes to load a saved configuration file:
1. Click
the main toolbar or select File | Offline | Open File from the menu bar. If the files is one that has
previously been opened offline, click the
symbol next to
in the main toolbar
2. An Open configuration file window appears. Use this to browse to the required configuration file.
3. Select the file and click Open.
Manager Manager 8.1
Manager
Page 58
15-601011 Issue 25l (11 February 2011)
Configuration Mode: Editing Configuration Settings
2.12.6 Known System Discovery
The Manager Select IP Office menu normally displays systems discovered by Manager using either UDP broadcast and or
TCP requests (see Setting the Discovery Addresses 53 ). Manager can be configured to also record details of discovered
units and then display a list of those previously discovered ('known') systems.
Configuring Manager for Known System Discovery
Use of known systems discovery is not enabled by default. The Manager must be configured for the feature with a file
location to which it can store and retrieve know system details.
1. Select File | Change Working Directory.
2. In the Known IP Office File field, enter the directory path and file name for a CSV file into which Manager can
write details of the systems it discovers. If the file specified does not exist it will be created by Manager.
3. Click OK.
Using Know System Discovery
1. When the Select IP Office screen is displayed click on Know Units.
2. The screen displays the list of systems previously discovered and stored in the CSV file.
· To select an control unit, highlight the row containing unit data and click OK. The selected unit will appear in
the Select IP Office window.
· To filter displayed units, type the first few characters of the unit name in the Filter field. Any unit whose name
does not match the filter will be temporarily hidden.
· Each discovery appends data to the known unit list. It is possible that details of some entries in the list may be
out of date. Right clicking on the leftmost (grey) column of any row will bring up a floating menu offering the
options of Refresh and Delete.
· A new entry may be manually added without having to access the system first through normal discovery. Enter
the IP address of the new system in the IP Address column of the blank row shown with a * and select
Refresh from the floating menu. This will update the Known Units file with data relating to the unit with the
specified address.
· Select Cancel to return to the Select IP Office menu.
Note:
· The key used by the Known Systems CSV file is the IP address. The file cannot contain entries for separate systems that
use the same IP address for access.
· The file can be made read only. In that case any attempts using Manager to update the file will be ignored.
Manager Manager 8.1
Manager
Page 59
15-601011 Issue 25l (11 February 2011)
2.12.7 Creating a Offline Configuration
Manager can be used to create a new configuration without connecting to a system. This allows the creation of a
configuration prior to installation of the real system and so can be used to speed up installation.
· The configuration created must match the physical equipment in the system into which the configuration will be
loaded. Doing otherwise may cause the system to reset and experience other problems.
· The Create Configuration tool includes all control units, external expansion modules and trunk cards supported. It
is you responsibility to confirm what equipment is supported in your locale.
Creating a New Configuration
1. Click
in the main toolbar or select File | Offline | Create New Config from the menu bar.
2. Select the Locale for the system. This defines a range of features such as default telephony settings. Click Next.
3. Fixed Length Numbering is supported for Manager 4.1+. The value can be None or 3 to 9. Click Next.
· If a value is selected, all default extension, user and hunt group extension numbers created by Manager will be
that length. in addition Manager will display a warning if an extension number of a different length is entered
when editing the configuration.
4. Select the type of control unit. Click Next.
5. Select the additional cards to include in the control unit. The number and type of cards selectable will depend on the
control unit type. Click Next.
6. Select the external expansion modules to also include in the system. Click Next.
7. Click Finish.
8. The configuration is created and loaded into Manager.
9. Once this configuration has been edited as required it can be saved on the PC. In order to send it to the matching
system, File | Offline | Send Configuration has to be used.
Manager Manager 8.1
Manager
Page 60
15-601011 Issue 25l (11 February 2011)
Configuration Mode: Editing Configuration Settings
2.12.8 Importing and Exporting Settings
Manager can import configuration settings created elsewhere. This can be useful when setting up a new system or sharing
common settings such as a directory between systems.
· The system supports LDAP
records.
169
(System | Directory Services | LDAP
· IP Office Release 5.0+: The system also supports HTTP
importation of directory records.
171
169 )
for automatic importation of directory
(System | Directory Services HTTP
171 )
for automatic
Settings are imported and exported in the following formats:
· Binary Files (.exp)
These are non-editable files. During import and export it is possible to select what types of entries should be
included in the file. During import the whole file is imported.
· Comma Separated Variable Text Files (.csv)
These are plain text files. In addition to being exported from a system these files can be created and edited using
programs such as WordPad or Excel.
· When opening a .csv file in Excel it will alter the way some data is displayed, automatically changing the
display format of dates and long numbers such as phone numbers.
· UTF-8 Character Encoding
Manager imports and exports CSV files using UTF-8 character encoding which uses a multiple bytes to support
characters with diacritic marks such as ä. Other applications, such as Excel, may, depending on the user PC
settings, use different encoding which will cause such characters to be removed or corrupted. Care should be
taken to ensure that any tool used to create or edit the CSV supports all the characters expected and uses
UTF-8 format.
· Importing into Manager from Excel
From Excel save the file as a .csv. This file will use ANSI character encoding. Open the file in Notepad and
use the Save As option to rename the file and select UTF-8 encoding. Import the UTF-8 version of the file
into Manager.
· Exporting from Manager into Excel
Do not double-click on the file exported from Manager. Start Excel and use File | Open to select the file.
Excel will recognize that the file uses UTF-8 encoding and will start its text file importation wizard. Follow
the wizard instructions and select comma as the field delimiter.
CSV File Formats
The format is CSV using commas as field separator, no text delimiters and no header row. The simplest way to check the
required format for a CSV file prior to import, is to export and a file from an existing system configuration.
File Name
Fields in Order
Directory
Name, Number.
Hunt Group
Name, Extension, Group, Hunt, Rotary, Longest Waiting, Queuing On, Voicemail On, Broadcast,
Voicemail Email.
Short Code
Code, Telephone Number, Feature.
User
Name, Extension, User Restriction/Rights, Voicemail Email address, Full Name (IP Office Release 5.0+)
.
Configuration
Proprietary format. Note that this does not contain all configuration fields.
License
License (ignored on import), License Key
Notes:
· Hunt Group: Apart from Name, Extension and Voicemail Email, the fields use a 1 or 0 value for on or off.
· License:
· The License field is for information only and is ignored during import.
· Following import the License name will appear as invalid with Manager. To resolve this save and then reload the
configuration file.
· The format of the system CSV is too complex to be described. It is a full export of all the system's configuration
settings. This file format should only be used for export and import between systems and not for any offline editing.
Manager Manager 8.1
Manager
Page 61
15-601011 Issue 25l (11 February 2011)
Exporting Settings
1. Select File | Import/Export... from the menu bar.
2. Select Export.
3. Select the type of file. The list of exportable entry types will change to match the file type.
4. Select the types of items that should be exported.
5. Use the Save In path to select the location for the exported files. The default location used is sub-directory of the
Manager application directory based on system name of the currently loaded system.
6. Click OK.
Importing Settings
Importing settings will overwrite any existing entries that match an entry being imported.
1. Select File | Import/Export... from the menu bar.
2. Select Import.
3. Select the type of file. The list of items will change to match the type of file selected and whether a matching file or
files is found in the current file path.
4. Use Look In to adjust the file path. The default location used is sub-directory of the Manager application directory
based on system name of the currently loaded system.
5. Select the types of items that should be imported.
6. Click OK.
Manager Manager 8.1
Manager
Page 62
15-601011 Issue 25l (11 February 2011)
Configuration Mode: Editing Configuration Settings
2.12.9 Copying and Pasting
Manager supports the normal Windows methods of cutting, copying, pasting and deleting entries and settings. These can
be accessed through the Edit menu in the menu bar or using the standard Windows keyboard shortcuts for those actions.
They can also be accessed by selecting an entry or text field and then right-clicking.
Copy and paste can be used with the navigation and group panes to create a new entry with the same settings as the
original. The copy will be renamed as Copy of ... to avoid conflicting with the original.
When using copy and paste between individual settings fields, whether on the same entry or a different entry, care should
be taken to ensure that the fields use the same type of data. Similarly copying an entry in the navigation or group pane
and then pasting it into the details pane will prompt Manager to paste the copied entries data into the first field of the
current entry in the details pane. As a general rule, cut and paste actions should be used with the same pane and within
similar entry types.
For users and user rights, a number of controls have been provided to copy settings between a user and a user right or
vice versa. See User Rights Overview 389 in the Configuration Settings section.
2.12.10 Saving a Configuration Offline
The system configuration settings shown within Manager can be saved as a .cfg file on the Manager PC. These files can be
used as backups or sent to other persons to aid problem diagnostics. Note however that an offline configuration file does
not include the Audit Trail records for the system.
Automatically Saving Sent Configurations
By default, Manager creates a file copy of the configuration before it is sent to the system. This copy is stored in Manager's
Working Directory using the system name and .cfg. This behavior is controlled by the Backup File on Send (File |
Preferences | Security) 110 option.
The number of backups of each systems configuration can be limited to a set number of the most recent copies.
Saving a Configuration Received from a System
1. Select File | Save Configuration as from the menu bar.
Saving a Configuration opened on the PC
1. Click
in the main toolbar or select File | Save Configuration from the menu bar.
Manager Manager 8.1
Manager
Page 63
15-601011 Issue 25l (11 February 2011)
2.12.11 Sending a Configuration
The current configuration settings open within Manager can be sent to the system.
1. The first steps of this process depend on whether you are sending a configuration received from the system or
sending one opened offline/created new.
· A Configuration Opened from a System
Click
in the main toolbar or select File | Save Configuration from the menu bar.
· A Configuration Created Offline or Opened from a PC File
Select File | Offline | Send Config from the menu bar.
2. The Send Configuration menu is displayed.
· Password - Pre-3.2 Systems Only
This field appears for pre-3.2 system. The system password should be entered. If sending the configuration to
an IP Office 3.2+ system, a Service User name and password are requested when OK is clicked.
· Configuration Reboot Mode
If Manager thinks the changes made to the configuration settings are mergeable, it will select Merge by default,
otherwise it will select Immediate.
· Merge
Send the configuration settings without rebooting the system. This mode should only be used with settings
that are mergeable. Refer to Mergeable Settings 51 .
· Immediate
Send the configuration and then reboot the system.
· When Free
Send the configuration and reboot the system when there are no calls in progress. This mode can be
combined with the Call Barring options.
· Timed
The same as When Free but waits for a specific time after which it then wait for there to be no calls in
progress. The time is specified by the Reboot Time. This mode can be combined with the Call Barring
options.
· Reboot Time
This setting is used when the reboot mode Timed is selected. It sets the time for the system reboot. If the
time is after midnight, the system's normal daily backup is canceled.
· Call Barring
These settings can be used when the reboot mode When Free is selected. They bar the sending or receiving of
any new calls.
3. Click OK. A Service User name and password may be requested.
· If the service user name or password used do not valid, "Access Denied" is displayed.
· If the service user name used does not have rights to send a configuration or to request a reboot or merge,
"Insufficient service user rights" is displayed.
· If the service user name used does not have operator rights to make the changes that have been made to the
configuration, "Insufficient operator rights. Operator cannot modify xxxx records" is displayed.
· The warning will appear if the configuration being sent contain any errors indicated by a
pane. The configuration can still be sent by selected Yes.
icon in the error
· IP500v2: The message Failed to save the configuration data. (Internal error) may indicate that the
IP500v2 system has booted using software other than that in its System SD card's primary folder.
Manager Manager 8.1
Manager
Page 64
15-601011 Issue 25l (11 February 2011)
Configuration Mode: Editing Configuration Settings
2.12.12 Erasing the Configuration
The system configuration settings can be erased. During this process, the system is rebooted and starts with a set of
default settings 65 .
This process does not erase the security settings of the system. Those can only be reset by a separate process detailed in
the Manager Installation Manual.
1. Select File | Advanced | Erase Configuration (Default).
2. Enter a valid user name and password.
3. The system will be rebooted.
2.12.13 Default Settings
The following applies to new control units and those defaulted using the Erase Configuration 65 command. It also applies
to IP500 and IP500v2 control units defaulted using the reset button on the rear of the unit (refer to the Manager
Installation manual for details of using the reset button).
Mode
IP500v2 control units can operate in a number of modes. The initial mode is determined by the type of System SD card
fitted and the level of software.
· IP Office A-Law
A system fitted with this type of card will default to A-Law telephony. The system will default to IP Office
Standard Version mode.
· IP Office U-Law
A system fitted with this type of card will default to U-Law telephony. The system will default to IP Office
Standard Version mode.
· IP Office Partner Edition
A system fitted with this type of card will default to A-Law telephony and IP Office Essential Edition PARTNER® Version mode operation.
· IP Office Norstar Edition
A system fitted with this type of card will default to U-Law telephony and IP Office Essential Edition - Norstar
Version mode operation.
· Avaya Branch Gateway
Use this option for an SD card intended to be used with a system running in Avaya Branch Gateway mode.
There is a separate SD card for Avaya Branch Gateway. The Avaya Branch Gateway SD card can only be used
for Avaya Branch Gateway operation and cannot be used to change modes to IP Office. The label on the SD
card includes BRANCH GW to indicate it is an Avaya Branch Gateway SD card. You also cannot use or change
an IP Office SD card for use with an Avaya Branch Gateway system.
·
! Warning
Do not re-purpose an Avaya Branch Gateway SD card for use with any other IP Office mode. Doing so may
damage the SD card and make it unusable for your Avaya Branch Gateway system.
· A-Law or U-Law
PCM (Pulse Code Modulation) is a method for encoding voice as data. In telephony, two methods of PCM encoding
are widely used, A-Law and U-Law (also called Mu-Law or µ-Law). Typically U-Law is used in North America and a
few other locations while A-Law is used elsewhere. As well as setting the correct PCM encoding for the region, the
A-Law or U-Law setting of a system when it is first started affects a wide range of regional defaults relating to line
settings and other values.
· For IP400 systems, each control units was manufactured as either an A-Law variant or a U-Law variant.
· For IP500 and IP500v2 systems, the encoding default is set by the type of Feature Key installed when the
system is first started. The cards are either specifically A-Law or U-Law. PARTNER Version cards are U-Law.
Norstar Version cards are A-Law.
Default Short Codes
IP400 control units are manufactured as A-Law and U-Law variants. For IP500 and IP500v2 control units, A-Law or U-Law
variant operation is determined by the Feature Key dongle installed in the system. Depending on the variant, a default
standard mode system will use different sets of default short codes. See the Default System Short Code List 437 .
Manager Manager 8.1
Manager
Page 65
15-601011 Issue 25l (11 February 2011)
Default Data Settings
When a new or defaulted 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.
· 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.
· If no DHCP Server responds, the control unit still defaults to being the DHCP client but assumes the following
default LAN addresses:
· For its LAN1 it allocates the IP address 192.168.42.1 and IP Mask 255.255.255.0.
· For its LAN2 if supported, it allocates the IP address 192.168.43.1 and IP Mask 255.255.255.0.
·
! Once an IP500v2 control unit has obtained IP address and DHCP mode settings, it will retain 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 system must be defaulted using Manager.
Default Security Settings
Security settings are held separately from the configuration settings and so are not defaulted by actions that default the
configuration. To return the security settings to their default values the separate Erase Security Settings 119 command
should be used.
Manager Manager 8.1
Manager
Page 66
15-601011 Issue 25l (11 February 2011)
Chapter 3.
Security Mode
Manager Manager 8.1
Manager
Page 67
15-601011 Issue 25l (11 February 2011)
3. Security Mode
These menus are used to edit the security settings of a system. They are not used for systems running in IP Office
Essential Edition - PARTNER® Version or IP Office Essential Edition - Norstar Version mode.
The security settings are stored on the system and are separate from the system's configuration settings. To change a
system's security settings, Manager must first be switched to security mode by selecting File | Advanced | Security
Settings from the menu bar.
Manager Manager 8.1
Manager
Page 68
15-601011 Issue 25l (11 February 2011)
Security Mode:
3.1 Security Settings
The following applies for IP Office 3.2 and higher. Access to system settings is controlled by Service Users and Rights
Groups. stored in the control unit's security settings. These are stored separately from the system's configuration
settings. All actions involving communications between Manager and the system require a Service User name and
password. That Service User must be a member of a Rights Group with permissions to perform the required action.
In the example illustrated above:
· Service User X can read and write the configuration. However they can only edit Operator settings and can only
make changes that can be merged.
· Service User Y can read and write the configuration, edit all settings and make changes that require reboots.
· Service User Z can read and write the configuration, edit all settings and make changes that require reboots. They
can also access the security settings.
· The Security Administrator can only access the security settings.
Security Administrators
By default the security administrator is the only user who can access the system's security settings using Manager's
security mode.
Service Users
Each Service User has a name, a password and is a member of one or more Rights Groups.
Rights Groups
The Rights Groups to which a Service User belongs determine what actions they can perform. Actions available to Rights
Groups include configuration actions, security actions and system status actions:
Configuration
Security
System Status
· Read the configuration.
· Read all security settings.
· System Status Access.
· Write the configuration.
· Write all security settings.
· Read All Configuration.
· Merge the configuration.
· Reset all security settings.
(Manager 4.1+)
· Default the configuration.
· Reboot immediately.
· Write own password.
(Manager 4.1+)
· Reboot when free.
· Reboot at time of day.
Where a Service User has been configured as a member of more than one Rights Group, they combine the functions
available to the separate Rights Groups.
Manager Manager 8.1
Manager
Page 69
15-601011 Issue 25l (11 February 2011)
Operator Rights
Each Rights Group has a Manager Operator Rights setting. This setting controls what types of configuration entries
Manager will allow members of the Rights Group to view and what actions they can perform with those types of entries.
Operator
Administrator
Manager
View/Edit/
New/Delete
All
View all except WAN Port.
Edit
Extension, User, Hunt Group, Short Code, Service, RAS, Incoming
Call Route, Directory, Time Profile, Firewall Profile, IP Route, Least
Cost Route, Account Code, ARS, E911 System.
Delete
As edit except Short Code.
View
View all except WAN Port.
Edit
Extension, User, Hunt Group, Short Code, Service, RAS, Incoming
Call Route, Time Profile, Firewall Profile, IP Route, Least Cost Route,
Account Code, License, ARS, E911 System.
New
None.
Delete
User & Group Edit
View, edit create and delete all configuration entries.
View
New
Operator
Configuration Entry Types
View
Delete Incoming Call Route and Directory.
User and Hunt Group entries only.
Edit
New
None
Delete
User & Group Admin
All
User and Hunt Group entries only.
Dir & Account Admin
All
Directory and Account Code entries only.
Time & Attendant Admin
All
Time Profile and Auto Attendant entries only.
ICR & User Rights Admin
All
Incoming Call Route and User Rights entries only.
Read Only
View
View all configuration entries.
Edit
None.
New
Delete
Manager Manager 8.1
Manager
Page 70
15-601011 Issue 25l (11 February 2011)
Security Mode: Security Settings
3.2 Default Security Users
This section lists the default Rights Groups and Service Users.
·
WARNING: Change Passwords
These settings must be changed to make the system secure. At minimum you must change the default passwords of the
Security Administrator and the default Service Users. Failure to do so will render the system unsecure.
Unique Security Control Unit
Enabled
Name
security
Password
securitypwd
Default Service Users
Name
Administrator
Manager
Operator
Password
Administrator
Manager
Operator
EnhTcpaService IPDECTService
EnhTcpaPwd1
–
Rights Group Membership
- Administrator Group
- Manager Group
- Operator Group
- System Status Group
- TCPA Group
- IPDECT Group
Default Rights Groups
Administr
ator
Group
Manager
Group
Operator
Group
System
Status
Group
TCPA
Group
IPDECT
Group
Operator
Rights
Administrat
or
Manager
Operator
–
–
–
Operator View
Service Rights Read Configuration
Write Configuration
Default Configuration
Merge
Reboot Immediately
Reboot When Free
Reboot at Time of Day
Security
Read All Security Settings
Administratio Write All Security Settings
n
Reset All Security Settings
(IP Office 4.1+)
Write own service user
password
(IP Office 4.1+)
System Status System Status Access
(IP Office 4.0+)
Read all configuration
System Control
(IP Office 6.0+)
Enhanced
Enhanced TSPI Access
TSPI
(IP Office 5.0+)
HTTP
DECT R4 Provisioning
Manager Manager 8.1
Manager
Page 71
15-601011 Issue 25l (11 February 2011)
3.3 The Security Mode Interface
Manager can be switched to security mode. This mode it is used to load and edit the security settings of a system. How
the controls operate is similar to Manager in configuration mode.
Switching Manager to Security Mode
1. Select File | Advanced | Security Settings.
Switching Manager Back to Configuration Mode
1. Select File | Configuration.
Manager Manager 8.1
Manager
Page 72
15-601011 Issue 25l (11 February 2011)
Security Mode: The Security Mode Interface
Manager Security Mode Screen Elements
· Menu Bar
Provides commands for loading and saving security settings. See the Menu Bar Commands
102
section.
· Main Toolbar
The toolbar icons perform the following actions:
·
Get the Security Settings.
·
Save the Security Settings.
·
Not Used in security mode.
·
Show/Hide the Navigation Pane.
·
Show/Hide the Group Pane.
·
Not used in security mode.
·
Not used in security mode.
· Security Settings Pane
This pane is used to select the type of security entries that should be displayed in the group pane or details pane.
·
General
Defines general security controls for the system. When selected, the settings are displayed in the details pane.
·
System
Defines security settings for the system such as application access. When selected, the settings are displayed in the
details pane.
·
Services
Secure services supported by the system. Currently these are access to security settings and access to configuration
settings.
·
Rights Groups
Create groups with different access rights. When selected, the existing Rights Groups are displayed in the group
pane.
·
Service Users
Sets the name and password for an administrator. Also allows selection of the Rights Groups to which the user
belongs. When selected, the existing Service Users are displayed in the group pane.
· Group Pane
This pane is used to display the existing Right Groups or Service Users when those options are selected in the security
settings pane.
· Details Pane
This pane shows the settings selected in the security settings pane or the group pane.
· Status Bar
This bar display messages about communications between Manager and systems.
the communications by the use of a padlock icon.
Manager Manager 8.1
Manager
It also displays the security level of
Page 73
15-601011 Issue 25l (11 February 2011)
3.4 Security Administration
IP Office 4.1 added support for the use of certificates if required. This section also covers a basic introduction to security
principles and the security mechanisms.
· NOTE: If administration security is of no concern, the default settings allow modification of all Manager features
without restriction. It is recommended as a minimum that default passwords are changed.
1. Introduction
Administration security is achieved using a number of optional cryptographic elements:
· Access control to prevent unauthorized use.Supported in version 3.2+.
· Encryption to guarantee data remains private. Supported in version 4.1+.
· Message Authentication ensures data has not been tampered with. Supported in version 4.1+.
· Identity assures the source of the data. Supported in version 4.1+.
2. Access Control
Access to configuration, security settings and SSA is controlled by the use of Service Users, passwords and Rights Groups.
All actions involving communications between the Manager user and the system require a Service User name and
password. That Service User must be a member of a Rights Group configured to perform the required action.
In the example illustrated above:
· Service User X can read and write the configuration. However they can only edit Operator settings and can only
make changes that can be merged.
· Service User Y can read and write the configuration, edit all settings and make changes that require reboots.
· Service User Z can read and write the configuration, edit all settings and make changes that require reboots. They
can also access the security settings.
· The Security Administrator can only access the security settings.
Security Administrator
By default the security administrator is the only user who can access the system's security settings using Manager's
security mode.
Service Users
Each Service User has a name, a password and is a member of one or more Rights Groups.
Rights Groups
The Rights Groups to which a Service User belongs determine what actions they can perform. Actions available to Rights
Groups include configuration actions, security actions and system status actions.
Where a Service User has been configured as a member of more than one Rights Group, they combine the functions
available to the separate Rights Groups.
Manager Manager 8.1
Manager
Page 74
15-601011 Issue 25l (11 February 2011)
Security Mode: Security Administration
3. Encryption
Encryption ensures that all data sent by either the system or Manager cannot be ‘read’ by anyone else, even another copy
of Manager. Encryption is the application of a complex mathematical process at the originating end, and a reverse process
at the receiving end. The process at each end uses the same ‘key’ to encrypt and decrypt the data:
Any data sent may be optionally encrypted using a number of well known and cryptographically secure algorithms:
Algorithm
Effective key size (bits)
Use
DES-40
40
Not recommended.
DES-56
56
‘Minimal’ security.
3DES
112
‘Strong’ security.
RC4-128
128
‘Strong’ security.
AES-128
128
‘Very strong’ security.
AES-256
256
‘Very strong’ security.
In general the larger the key size, the more secure the encryption. However smaller key sizes usually incur less
processing. The system supports encryption using the Transport Layer Security (TLS) v1.0 protocol. In addition, many
cryptographic components of the TLS module have been FIPS 140-2 certified, indicating the accuracy of implementation.
Manager Manager 8.1
Manager
Page 75
15-601011 Issue 25l (11 February 2011)
4. Message Authentication
Message authentication ensures that all data sent by either the system or Manager cannot be tempered with (or
substituted) by anyone else without detection. This involves the originator of the data producing a signature (termed a
hash) of the data sent, and sending that as well. The receiver gets the data and the signature and check both match.
Any data sent may be optionally authenticated using a number of well known and cryptographically secure algorithms:
Algorithm
Effective hash size (bits)
Use
MD5
128
‘Minimal’ security.
SHA-1
160
‘Strong’ security.
In general the larger the hash size, the more secure the signature. However smaller hash sizes usually incur less
processing.
Manager supports message authentication using the Transport Layer Security (TLS) v1.0 protocol. In addition, many
cryptographic components of the TLS module have been FIPS 140-2 certified, indicating the accuracy of implementation.
Manager Manager 8.1
Manager
Page 76
15-601011 Issue 25l (11 February 2011)
Security Mode: Security Administration
5. Identity
The identity of the equipment or person at each end of the link is achieved by the used of digital certificates – more
specifically X.509 v3 certificates. Digital certificates are the preferred mechanism for the majority of internet-based
applications including e-commerce and email, and can be thought of as a credential, just like a passport or drivers’ license.
A digital certificate contains at least three things:
· A public key.
· Certificate information (Identity information about the user, such as name, user ID, and so on.)
· One or more digital signatures
The purpose of the digital signature on a certificate is to state that the certificate information has been verified to by some
other person or entity. The digital signature does not verify authenticity of the certificate as a whole; it vouches only that
the signed identity information goes along with, or is bound to, the public key: A certificate essentially is a public key with
one or two forms of ID attached, plus a stamp of approval from some other ‘trusted individual’.
Trusted individuals (also termed Certificate Authorities) themselves have publicly available certificates, which can contain
signatures from their trusted authorities. These can be verified all the way up to a ‘self-signed’ root certificate from a root
certificate authority.
Examples of root certificate authorities’ certificates can be found in every web browsers’ certificate store.
Manager Manager 8.1
Manager
Page 77
15-601011 Issue 25l (11 February 2011)
6. Windows Certificate Store Usage
The certificate store that is used by the Manager to save X509 certificates to and retrieve certificates from is the default
one provided by the Windows operating system. This may be accessed for maintenance purposes by a user with sufficient
permission via the use of a ‘snap-in’.
· WARNING
Avaya accept no responsibility for changes made by users to the Windows operating system. Users are responsible
for ensure that they have read all relevant documentation and are sufficiently trained for the task being performed.
If not installed already, the Microsoft Management Console (MMC) Certificates snap-in can be installed by following the
relevant instructions. Both ‘user account’ and ‘computer’ options should be installed.
· For Windows XP Professional:
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/sag_cm_addsnap.mspx
· For Windows Server 2003:
http://technet2.microsoft.com/windowsserver/en/library/4fa4568e-16de-4a64-b65e-12ee14b31dc21033.mspx?
mfr=true
· For Windows Vista:
http://technet2.microsoft.com/WindowsVista/f/?en/library/a8b21b9b-d102-4045-9f36-e4b3430d2f381033.mspx
7. Windows Certificate Store Organization
By default, certificates are stored in the following structure:
Each of the sub folders has differing usage. The Certificates - Current User area changes with the currently logged-in
windows user. The Certificate(Local Computer) area does not change with the currently logged-in windows user.
Manager Manager 8.1
Manager
Page 78
15-601011 Issue 25l (11 February 2011)
Security Mode: Security Administration
Manager only accesses some of the certificate sub folder:
Certificates (Local
Computer) Folder
Manager Use
Personal | Certificates
· Folder searched by Manager 1st for matching certificate to send to the system when
requested. Certificate matched by the subject name contained in File | Preferences |
Security | Certificate offered to the system.
· Folder accessed whenever ‘Local Machine certificate store’ used for Security
Settings.
· Folder searched by Manager for matching certificate when certificate received from the
system, and File | Preferences | Security | Manager Certificate Checks = Medium
or High.
Trusted Root Certification
Authorities | Certificates
· Folder searched by Manager for matching parent certificates when non-self signed
certificate received from the system, and File | Preferences | Security | Manager
Certificate Checks = Medium or High.
Certificates – Current User Manager Use
Folder
Personal | Certificates
· Folder searched by Manager 2nd for matching certificate (subject name) to send to the
system when requested. Certificate matched by the subject name contained in File |
Preferences | Security | Certificate offered to the system.
· Folder accessed whenever ‘Current User certificate store’ used for Security Settings.
· Folder searched by Manager for matching certificate when certificate received from
Manager, and File | Preferences | Security | Manager Certificate Checks =
Medium or High.
Trusted Root Certification
Authorities | Certificates
· Folder searched by Manager for matching parent certificates when non-self signed
certificate received from the system, and File | Preferences | Security | Manager
Certificate Checks = Medium or High.
Other People | Certificates · Folder searched by Manager for matching parent certificates when non-self signed
certificate received from the system, and File | Preferences | Security | Manager
Certificate Checks = Medium or High.
Manager Manager 8.1
Manager
Page 79
15-601011 Issue 25l (11 February 2011)
8. Windows Certificate Store Import
In order to use certificates – either for security settings or Manager operation – they must be present in the windows
certificate store. Certificates may be placed in the store by the Certificate Import Wizard or the Certificate MMC snap-in
The Certificate Import Wizard can be used whenever a certificate is viewed. In order for Manager to subsequently access
this certificate the Place all certificate in the following store option must be selected:
· If the certificate is to subsequently identify the system, the Other People folder should be used.
· If the certificate is to subsequently identify the Manager, the Personal folder should be used, and the associated
private key saved as well.
If the saved certificate is to be used by other windows users, the MMC certificate snap-in must be used to move it to the
Certificates (Local Computer) folder.
9. Certificate Store Export
Any certificate required outside of the Manager PC required to be first saved in the Certificate store, then exported using
the MMC snap-in.
If the certificate is to be used for identity checking (i.e. to check the far entity of a link) the certificate alone is sufficient,
and should be saved in PEM or DER format.
If the certificate is to be used for identification (i.e. to identify the near end of a link) the certificate and private key is
required, and should be saved in PKCS#12 format, along with a password to access the resultant .pfx file.
10. Implementing Administration Security
This section suggests system security settings that could implement possible security requirements. This section does not
cover the general aspects of security policy analysis or definition, or how the system administration security interacts with
other security mechanism.
10.1. Negligible Security
If all Manager and system security settings are left at default, no security mechanisms are active, other than the use of
default service user names and passwords. In addition, all legacy interfaces are active, and all configuration and security
data is sent unencrypted.
It is recommended that at the very least, the default service user passwords are changed.
Manager Manager 8.1
Manager
Page 80
15-601011 Issue 25l (11 February 2011)
Security Mode: Security Administration
10.2. Minimum Security
A minimum security scenario could be where configuration data is open, but the security settings are constrained: Any
individual with the correct service user name and password can access the configuration from any PC installation of
Manager, no logging of access: Passwords can be simple, and will never age.
· Change all default passwords of all service users and Security Administrator
· Set the system Security Administration service security level to Secure, Low.
· Set the system Service User Password Reject Action to None.
· Set the system Client Certificate Checks level to None (default).
· Set the system Minimum Password Complexity to Low (default).
· Set the system Previous Password Limit to zero (default).
· Set the system Password Change Period to zero (default).
· Set the system Account Idle Time to zero (default).
· Set certificate check level to low in Manager Security Preferences (default).
In addition, any PC installation of Manager can manage any Manager.
10.3. Medium Security
A medium security scenario could be where both configuration and security settings are constrained and a level of logging
is required: Any individual with the correct service user name and password can access the configuration from any PC
installation of Manager: Passwords cannot be simple, and will age.
· Change all default passwords of all service users and Security Administrator
· Set the system Security Administration service security level to Secure, Medium.
· Set the system Configuration service security level to Secure, Medium.
· Set the system Service User Password Reject Action to Log to Audit Trail (default).
· Set the system Client Certificate Checks level to None (default).
· Set the system Minimum Password Complexity to Medium.
· Set the system Previous Password Limit to non zero.
· Set the system Password Change Period to non zero.
· Set the system Account Idle Time to zero (default).
· Disable all the system Unsecured Interfaces.
· Set certificate check level to low in Manager Security Preferences (default).
Manager Manager 8.1
Manager
Page 81
15-601011 Issue 25l (11 February 2011)
10.4. Maximum Security
A maximum security scenario could be where both configuration and security settings are constrained and a full level of
logging is required: Certified individuals with the correct service user name and password can access the configuration
from specific PC installations of Manager: Passwords cannot be simple, and will age: Manager can managed specific
systems.
· Change all default passwords of all service users and Security Administrator
· Set the system Security Administration service security level to Secure, High.
· Set the system Configuration service security level to Secure, High.
· Set the system Service User Password Reject Action to Log and Disable Account.
· Set the system Client Certificate Checks level to High.
· Set the system Minimum Password Complexity to High.
· Set the system Minimum Password Length to >8.
· Set the system Previous Password Limit to non zero (>5).
· Set the system Password Change Period to non zero.
· Set the system Account Idle Time to non zero.
· Set the system Session ID Cache to zero.
· Install valid, 1024 bits+, non self signed certificates (+private key) in all Manager server certificates, derived from
a trusted certificate authority.
· Install the corresponding trusted CA certificate in each of the Manager’s windows certificate stores.
· Install valid, 1024 bits+, non self signed certificate (+ private key) in all Manager Certificate Stores.
· Install the corresponding certificates in all the system Certificate Stores of all permissible Manager entities, and the
trusted CA certificate.
· Disable all the system Unsecured Interfaces.
· Set Manager Certificate Checks level to high in Manager Security Preferences.
· Set Certificate offered to the system in Manager Security Preferences.
The above essentially locks the systems and corresponding Managers together. Only recognized (by strong certificate)
entities may communicate successfully on the service interfaces. All services use strong encryption and message
authentication.
The use of intermediate CA certificates can be used to overcome the limit of 6 maximum certificates in each system
Certificate Store.
Manager Manager 8.1
Manager
Page 82
15-601011 Issue 25l (11 February 2011)
Security Mode: Security Administration
3.5 Editing Security Settings
Security settings can only be loaded directly from a system. These settings cannot be saved as a file on the local PC, nor
do they appear as a temporary file at any time.
For IP Office 4.1 and higher, you can optionally secure the link between the system and Manager for configuration and
security settings exchanges. By default Manager and the system will always attempt to use the original, unsecured link.
The control of which mechanism is used by Manager is determined Manager preferences.
When secure communications mode is selected a
padlock icon is present on the Manager status bar.
Loading Security Settings
The address ranges in which Manager searches for systems are set through the Manager preferences (File | Preferences
| Discovery 106 ). The security mechanism used for security settings transfer between Manager and a system are set
through the Secure Communications attribute of Manager preferences (File | Preferences | Security).
1. If not already done, switch Manager to security mode by selecting File | Advanced | Security Settings.
· Note: If the system's configuration settings have already been loaded using a Service User name and Password
that also has security access, then the security settings are automatically loaded when Manager is switched to
security mode.
2. If already in security mode, click
bar.
in the main toolbar or select File | Open Security Settings from the menu
3. The Select IP Office window appears, listing those systems that responded. The list can be sorted by clicking on
the column names.
4. If the system required was not found, the address used for the search can be changed. Enter or select the required
address in the Unit/Broadcast Address field and then click Refresh to perform a new search.
5. When the system required is located, check the box next to the system and click OK.
6. The user name and password request for the system is then displayed. Enter the required details and click OK. By
default this is a different user name and password from those that can be used for configuration access.
7. If the security settings are received successfully, they appear within Manager.
· If the service user name/password is incorrect, or the service user has insufficient rights to read the security
settings, "Access Denied" is displayed.
· If the network link fails, or the secure communication mode is incorrect (for example Manager is set to
unsecured, but the system is set to secure only), "Failed to communicate with IP Office" is displayed.
Editing Security Settings
Editing security settings differ from editing configuration settings in a number of ways:
1. Editing of security settings may only be done online to a system. No offline saving or editing is allowed for security
purposes.
2. No errors in the security settings are allowed to persist. This prevents the system becoming inaccessible through
operator error.
3. Sets of changes to security objects may be made without the need for the OK button to be selected every time.
This allows a coordinated set of changes to be accepted or canceled by the operator.
Saving Security Settings
in the Main Toolbar or select File | Save Security Settings from the menu bar. These options are only
1. Click
available when some change has been made.
2. The user name and password request for the system is then displayed. Enter the required details and click OK. By
default this is a different user name and password from those that can be used for configuration access.
Resetting a System's Security Settings (IP Office 4.1+)
Manager Manager 8.1
Manager
Page 83
15-601011 Issue 25l (11 February 2011)
1. Select File | Reset Security Settings (if in security mode), or File | Advanced | Erase Security Settings (if in
configuration mode).
2. The Select IP Office window appears, listing those systems that responded. The list can be sorted by clicking on
the column names.
3. When the system required is located, check the box next to the system and click OK.
4. The user name and password request for the system is then displayed. Enter the required details and click OK. By
default this is a different user name and password from those that can be used for configuration access.
5. Manager will indicate if the security settings are reset successfully.
Manager Manager 8.1
Manager
Page 84
15-601011 Issue 25l (11 February 2011)
Security Mode: Editing Security Settings
3.5.1 General Settings
These settings are displayed when
General is selected in the navigation pane.
· Security Administrator
The security administrator is a special service user who does not belong to any Rights Groups. The security
administrator is able to access the system's security settings but cannot access its configuration settings. By default
they are the only service user able to access to the security settings.
· Unique Security Administrator: Default = Off
When selected, only the Security Administrator is able to access the system's security settings. When this is selected,
the security options for Rights Groups are disabled. When not selected, the ability to access security settings can also
be assigned to Rights Groups.
· Name: Default = 'security'. Range = 6 to 31 characters.
The name for the Security Administrator.
· Password: Default = 'securitypwd'. Range = 6 to 31 characters.
The password for the Security Administrator. In order to change the Security Administrator password, the current
password must be known.
· Minimum Password Complexity: Default = Low. Software level = 4.1+.
The password complexity requirements for the Security Administrator. This setting is active for attempted password
changes on both Security Manager and the system.
· Low
Any password characters may be used without constraint.
· Medium
The password characters used must include characters from at least 2 of the 'code point sets' listed below. For
example a mix of lower case and upper case. In addition, there should not be any adjacent repeated characters of
any type.
1. Lower case alphabetic characters.
2. Upper case alphabetical character.
3. Numeric characters.
4. Non-alphanumeric characters, for example # or *.
Manager Manager 8.1
Manager
Page 85
15-601011 Issue 25l (11 February 2011)
· High
The password characters used must include characters from at least 3 of the 'code point sets' listed above. For
example a mix of lower case, upper case and numbers. In addition, there should not be any adjacent repeated
characters of any type.
· Previous Password Limit (Entries): Default = 0. Range = 0 (Off) to 10 entries. Software level = 4.1+.
The number of previous password to check for duplicates against when changing the password. When set to 0, no
checking of previous passwords takes place. This setting is active for attempted password changes on both Security
Manager and the system.
· Service User Details
These settings control Service User names and password/account policies.
· Minimum Name Length: Default = 6, Range 1 to 31 characters.
This field sets the minimum name length for Service User names.
· Minimum Password Length: Default = 6, Range 1 to 31 characters.
This field sets the minimum password length for Service User passwords.
· Password Reject Limit: Default = 3, Range 0 to 255 failures.
Sets how many times an invalid name or password is allowed within a 10 minute period before the Password Reject
Action is performed. Selecting 0 indicates never perform the Password Reject Action.
· Password Reject Action: Default = Log to Audit Trail
The action performed when a user reaches the Password Reject Limit. Current options are:
· No Action
· Log to Audit Trail
Log to Audit Trail creates an entry indicating the service user account name and time of last failure.
· Log and Disable Account: Software level = 4.1+.
Log and Disable Account creates an audit trail entry and additionally permanently disables the service user account.
This account may only be enabled using the Security Manager Service User settings.
· Log and Temporary Disable: Software level = 4.1+.
Log and Temporary Disable creates an audit trail entry and additionally temporarily disables the service user
account for 10 minutes. This account may additionally be enabled using the Security Manager Service User
settings.
· Minimum Password Complexity: Default = Low. Software level = 4.1+.
The password complexity requirements for all Service Users. This setting is active for attempted password changes on
both Security Manager and the system.
· Low
Any password characters may be used without constraint.
· Medium
The password characters used must cover two 'code point sets'. For example lower case and upper case. In
addition, Medium and High do not allow more than 2 repeated characters of any type.
· High
The password characters used must cover three 'code point sets'. For example lower case plus upper case and
numbers.
· Password Change Period: Default = 0 (Off), Range 0 to 999 days. Software level = 4.1+.
Sets how many days a newly changed password is valid. Selecting 0 indicates any password is valid forever. This
setting is active for password changes through this form or prompted by Manager. Note that the user must be a
member of a Rights Group that has the Security Administration 97 option Write own service user password
enabled. If this timer expires, the service user account is locked. The account may only be re-enabled using the
Service User Settings 99 . To prompt the user a number of days before the account is locked set a Expiry Reminder
Time (see below).
· Whenever this setting is changed and the OK button is clicked, the Security Manager recalculates all existing
service user password timers.
· Account Idle Time: Default = 0 (Off), Range 0 to 999 days. Software level = 4.1+.
Sets how many days a service user account may be inactive before it becomes disabled. Selecting 0 indicates an
account may be idle forever. If this timer expires, the service user account is permanently disabled. The account
may only be re-enabled using the Service User Settings 99 . The idle timer is reset whenever a service user
successfully logs in.
· Whenever this setting is changed and the OK button is clicked, the Security Manager recalculates all existing
service user idle timers.
· Expiry Reminder Time: Default = 28, Range 0 (Off) to 999 days. Software level = 4.1+.
Sets the period before password or account expiry during which a reminder indication if the service user logs in.
Selecting 0 prevents any reminders. Reminders are sent, for password expiry due to the Password Change Period
(above) or due to the Account Expiry date (see Service User 99 setting) – whichever is the sooner. Currently
Manager displays reminders but System Status does not.
Manager Manager 8.1
Manager
Page 86
15-601011 Issue 25l (11 February 2011)
Security Mode: Editing Security Settings
3.5.2 System
3.5.2.1 System Details
This tab is accessible when
System is selected in the navigation pane.
· Base Configuration
· Base TCP Port: Default = 50804, Range = 49152 to 65526.
This is the base TCP port for services provided by the system. It sets the ports on which the system listens for
requests to access those services, using its LAN1 IP address. Each service uses a port offset from the base port value.
If this value is changed from its default, the Manager application must be set to the same Base TCP Port through its
Services Base TCP Port setting (File | Preferences 106 ).
Service
Method
Port Used
Default
Configuration
Unsecure (IP Office 3.2+)
Base TCP Port
50804
Secure (IP Office 4.1+)
Base TCP Port plus 1.
50805
System Status Interface
Unsecure (IP Office 4.0+)
Base TCP Port plus 4.
50808
Security Administration
Unsecure (IP Office 3.2+)
Base TCP Port plus 8.
50812
Secure (IP Office 4.1+)
Base TCP Port plus 9.
50813
Unsecure (IP Office 5.0+)
Base TCP Port plus 10.
50814
Enhanced TSPI
· When changing the base port, exercise caution that the selected port and those offset from it do not conflict with
any ports already in use by other applications.
· Maximum Service Users: Default = 16.
This is a fixed value for indication purposes only. This value is the maximum number of Service Users that can be stored
in a system's security settings.
· Maximum Rights Groups: Default = 8.
This is a fixed value for indication purposes only. This value is the maximum number of Rights Groups that can be
stored in a system's security settings.
Manager Manager 8.1
Manager
Page 87
15-601011 Issue 25l (11 February 2011)
· System Discovery
System discovery is the processes used by applications to locate and list available systems. The Manager can be
disabled from responding to this process if required. If this is done, access to the Manager requires its specific IP
address to be used.
· TCP Discovery Active: Default = On. Software level = IP Office 5.2+.
Selecting TCP Discovery Active allows the system to respond to those requests.
· UDP Discovery Active: Default = On.
Selecting UDP Discovery Active allows the system to respond to those requests.
· Security: Software level = 4.1+.
These settings cover the per-system security aspects, primarily TLS settings.
· Session ID Cache: Default = 10 hours, Range 0 to 100 hours.
This sets how long a TLS session ID is retained by the system. If retained, the session ID may be used to quickly
restart TLS communications between the system and a re-connecting application. When set to 0, no caching takes
place and each TLS connection must be renegotiated.
· Allow HTTPS: Default = Off. Software level = 6.0-6.1.
Allow HTTPS connection to the system for applications such as the IP Office Softphone.
· Offer Server Certificate: Default = On.
This is a fixed value for indication purposes only. This sets whether the system will offer a certificate in the TLS
exchange when the Manager is acting as a TLS server, which occurs when accessing a secured service.
· Server Private Key: Default = None.
This is a fixed value for indication purposes only. This indicate whether the system has a private key associated with
the Server Certificate.
· Server Certificate: Default = None.
The Server Certificate is an X.509v3 certificate that identifies the system to a connecting client device (usually a PC
running a application). This certificate is offered in the TLS exchange when the system is acting as a TLS server,
which occurs when accessing a secured service. By default the system's own self-generated certificate is used (see
note below), but set can be used to replace this with another certificate.
· The Server Certificate may be generated by the system itself, and can take up to 5 minutes to generate. This
occurs when any of the Service Security Level 92 is set to a value other than Unsecure Only. During this time,
normal system operation is suspended.
· Set
Sets the current Server Certificate and associated private key. The certificate and key must be a matching pair.
The source may be:
· Current User Certificate Store.
· Local Machine Certificate Store.
· File in PKCS#12 (.pfx), DER (.cer), or password protected DER (.cer) format.
· Pasted from clipboard in PEM format, including header and footer text.
· View
View the current Server Certificate. The certificate (not the private key) may also be installed into the local PC
certificate store for export or later use when running the manager in secured mode.
· Delete
Delete the current Server Certificate. When sent to the system will generate a new Server Certificate when next
required. This can take up to 5 minutes to generate. During this time, normal system operation is suspended.
· Client Certificate Checks: Default = None.
When a Service Security Level is set to High, a certificate is requested of Manager.The received certificate is tested
according to the Client Certificate Checks level:
· None
No extra checks are made (The certificate must be in date).
· Low
Certificate minimum key size 512 bits, in date.
· Medium
Certificate minimum key size 1024 bits, in date, match to store, no reflected.
· High
Certificate minimum key size 1024 bits, in date, match to store, no self signed, no reflected.
· Client IP Office Certificate Store: Default = Empty.
The certificate store contains a set of trusted certificates used to evaluate received client certificates. Up to six
X.509v3 certificates may be installed. The source may be:
· Current User Certificate Store.
· Local Machine Certificate Store.
Manager Manager 8.1
Manager
Page 88
15-601011 Issue 25l (11 February 2011)
Security Mode: Editing Security Settings
· File in PKCS#12 (.pfx), DER (.cer), or password protected DER (.cer) format.
· Pasted from clipboard in PEM format, including header and footer text.
Manager Manager 8.1
Manager
Page 89
15-601011 Issue 25l (11 February 2011)
3.5.2.2 Unsecured Interfaces
This tab is accessible when
System is selected in the navigation pane. These features relate to applications that
access the system configuration settings using older security methods.
· System Password: Default = 'password', Range = 0 to 31 characters.
This password is required by some legacy applications such as Monitor and Call Status. It is also used for control unit
software upgrades.
· VM Pro Password: Default = '', Range = 0 to 31 characters.
This password is required if a matching password is also set through the Voicemail Pro client application. Typically no
password is set.
· Monitor Password: Default = '', Range = 0 to 31 characters.
This password, if set, is used by the System Monitor and Call Status applications. If this password is not set, those
applications use the system password. If changing this password with no previous password set, enter the system
password as the old password.
· Applications Controls: Default = All selected except TFTP Configuration Write.
These check boxes control which actions the system will support for legacy applications. Different combinations are
used by the different applications. A summary of the applications affected by changes is listed in the Application
Support list.
· TFTP Configuration Read: Default = On.
· TFTP Configuration Write: Default = Off.
· Voicemail: Default = On.
· EConf: Default = On.
Manager Manager 8.1
Manager
Page 90
15-601011 Issue 25l (11 February 2011)
Security Mode: Editing Security Settings
· Program Code: Default = On.
· Real Time Interface: Default = On.
If disabled, IP Office Delta Server and related applications cannot change the status of agents.
· TAPI: Default = On.
· HTTP Directory Read: Default = On. Software level = 5.0+.
Allow the system's current directory records to be accessed using HTTP.
· HTTP Directory Write: Default = On. Software level = 5.0+.
Allow HTTP import 171 to be used to place temporary directory entries into the directory.
· Application Support
This panel is shown for information only. It indicates the effect on various applications of the Application Controls
selections.
Manager Manager 8.1
Manager
Page 91
15-601011 Issue 25l (11 February 2011)
3.5.3 Services Settings
This tab is accessible when
Service is selected in the navigation pane. It shows details of the services that the
system runs to which Service Users can communicate.
· Name
The name of the service. This is a fixed value for indication purposes only.
· Host System
This field shows the system's name. This is a fixed value for indication purposes only.
· TCP Base Port
This is the TCP port on which the system listens for attempts to access the service. The routing of traffic to this port
may need to be enabled on firewalls and network devices between the Service Users and the system. The TCP Base Port
for each service is offset by a fixed amount from the Base TCP Port set in System Settings.
Service
Method
Port Used
Default
Configuration
Unsecure (IP Office 3.2+)
Base TCP Port
50804
Secure (IP Office 4.1+)
Base TCP Port plus 1.
50805
System Status Interface
Unsecure (IP Office 4.0+)
Base TCP Port plus 4.
50808
Security Administration
Unsecure (IP Office 3.2+)
Base TCP Port plus 8.
50812
Secure (IP Office 4.1+)
Base TCP Port plus 9.
50813
Unsecure (IP Office 5.0+)
Base TCP Port plus 10.
50814
Enhanced TSPI
· Service Security Level: Default = ‘Unsecure Only’. Software level = 4.1+.
Sets the minimum security level the service will support. See File | Preferences | Security 110 for the corresponding
Manager application setting, which must be changed to match the appropriate service access security settings.
· WARNING
If the system does not already have an X509 security certificate, selecting a setting other than Unsecure Only
will cause the system to stop responding for a period (less than a minute) while the system generates its own
unique security certificate.
· Unsecure Only
This option allows only unsecured access to the service. The service's secure TCP port is disabled.
· Unsecure + Secure
This option allows both unsecured and secure (Low) access. In addition, TLS connections are accepted without
encryption, just authentication.
· Secure, Low
This option allows secure access to that service using TLS, and demands weak (for example DES_40 + MD5)
encryption and authentication or higher. The service's unsecured TCP port is disabled.
· Secure, Medium
This option allows secure access to that service using TLS, and demands moderate (for example DES_56 + SHA-1)
encryption and authentication or higher. The service's unsecured TCP port is disabled.
· Secure, High
This option allows secure access to that service using TLS and demands strong (for example 3DES + SHA-1)
encryption and authentication, or higher. In addition, a certificate is required from the client (usually Manager). See
System Details | Client Certificate Checks 87 for tests made on the received certificate. The service's unsecured TCP
port is disabled.
Manager Manager 8.1
Manager
Page 92
15-601011 Issue 25l (11 February 2011)
Security Mode: Editing Security Settings
Services
The different services are used as follows:
· Configuration
This service is used access to control unit configuration settings by the Manager application. If set to a mode other
than secure, the Manager's Security preferences 110 also need to changed to match.
· System Status Interface
This service is used by connections to the System Status Application and the IP Office Customer Call Reporter
applications.
· Security Administration
This service is used for access to control unit security settings by the Manager applications.
· Enhanced TSPI
This service is used by connections to the one-X Portal for IP Office application.
· HTTP
The HTTP service affects all HTTP connections provided by the system. Changing its setting will affect applications
other than just the DECT R4. The default Service Security Level is Secure + Unsecure, meaning both http and
https can be used.
· Unsecure = HTTP port 80 available.
This is used for phone files, embedded file manager, system file upgrade, one-X Portal directory services, DECT
R4 provisioning, IPO softphone provisioning.
· Secure = HTTPS port 443 available.
This can be used for DECT R4 provisioning, IPO softphone provisioning.
Manager Manager 8.1
Manager
Page 93
15-601011 Issue 25l (11 February 2011)
3.5.4 Rights Groups
The Rights Groups to which a service user belongs define what the service user is able to do after that login to the
system.
Default Rights Groups
Administr
ator
Group
Manager
Group
Operator
Group
System
Status
Group
TCPA
Group
IPDECT
Group
Operator
Rights
Administrat
or
Manager
Operator
–
–
–
Operator View
Service Rights Read Configuration
Write Configuration
Default Configuration
Merge
Reboot Immediately
Reboot When Free
Reboot at Time of Day
Security
Read All Security Settings
Administratio Write All Security Settings
n
Reset All Security Settings
(IP Office 4.1+)
Write own service user
password
(IP Office 4.1+)
System Status System Status Access
(IP Office 4.0+)
Read all configuration
System Control
(IP Office 6.0+)
Enhanced
Enhanced TSPI Access
TSPI
(IP Office 5.0+)
HTTP
DECT R4 Provisioning
· Administrator Group/Manager Group/ Operator Group:
These default groups are used for configuration access. They differ only in the level of rights to view and amend
configuration 96 settings.
· System Status Group:
This is the default group intended for use with the System Status Application (SSA). It is also used by the Customer
Call Reporter application unless a separate rights group is created for that application.
· TCPA Group: Software level = 5.0+
This rights group is used by the one-X Portal for IP Office application for connection to the system.
Some of the groups above have been added in different software releases. For new systems and systems with default
security settings, the new rights groups are created automatically when the system is upgraded to the new release. For
systems which have customized (non default) security settings, these rights groups may have to be created manually.
Manager Manager 8.1
Manager
Page 94
15-601011 Issue 25l (11 February 2011)
Security Mode: Editing Security Settings
3.5.4.1 Group Details
These settings are displayed when
Rights Group.
Rights Groups is selected in the navigation pane. This tab sets the name of the
· Name: Range = Up to 31 characters
The name for the Rights Group should be unique.
Manager Manager 8.1
Manager
Page 95
15-601011 Issue 25l (11 February 2011)
3.5.4.2 Configuration
These settings are displayed when
Rights Groups is selected in the navigation pane. This tab sets the configuration
settings access for Service User's who are members of this Rights Group.
· IP Office Service Rights
This setting controls what action on the system can be performed by members of the Rights Group.
· Manager Operator Rights
This setting controls what types of configuration entries Manager will allow members of the Rights Group to viewed
and what actions they can perform with those types of entries.
Operator
Administrator
Manager
View/Edit/
New/Delete
All
View all except WAN Port.
Edit
Extension, User, Hunt Group, Short Code, Service, RAS, Incoming
Call Route, Directory, Time Profile, Firewall Profile, IP Route, Least
Cost Route, Account Code, ARS, E911 System.
Delete
As edit except Short Code.
View
View all except WAN Port.
Edit
Extension, User, Hunt Group, Short Code, Service, RAS, Incoming
Call Route, Time Profile, Firewall Profile, IP Route, Least Cost Route,
Account Code, License, ARS, E911 System.
New
None.
Delete
User & Group Edit
View, edit create and delete all configuration entries.
View
New
Operator
Configuration Entry Types
View
Delete Incoming Call Route and Directory.
User and Hunt Group entries only.
Edit
New
None
Delete
User & Group Admin
All
User and Hunt Group entries only.
Dir & Account Admin
All
Directory and Account Code entries only.
Time & Attendant Admin
All
Time Profile and Auto Attendant entries only.
ICR & User Rights Admin
All
Incoming Call Route and User Rights entries only.
Read Only
View
View all configuration entries.
Edit
None.
New
Delete
Manager Manager 8.1
Manager
Page 96
15-601011 Issue 25l (11 February 2011)
Security Mode: Editing Security Settings
3.5.4.3 Security Administration
These settings are displayed when
Rights Groups is selected in the navigation pane. This tab sets the security
settings access for Service user's who are members of this Rights Group. These settings are ignored and greyed out if a
Unique Security Administrator has been enabled in General Settings 85 .
· Read all security settings
Members of the Rights Group can view the system's security settings.
· Write all security settings
Members of the Rights Group can edit and return changes to the system's security settings.
· Reset all security settings: Software level = 4.1+.
If selected, members of the Rights Group can reset the security settings to default values.
· Write own service user password: Software level = 4.1+.
If selected, members of the Rights Group can change their own password when requested to do so by the system.
That request may be the result of a Password Change Period 85 , Force new password 99 or Account Expiry
99 . The new password change is requested automatically at login time.
Manager Manager 8.1
Manager
Page 97
15-601011 Issue 25l (11 February 2011)
3.5.4.4 System Status
These settings are displayed when
Rights Groups is selected in the navigation pane. This tab sets whether members
of the group can access the system using the System Status Application (SSA). That application is only supported by
Manager 4.0 and higher systems.
· System Status Access
If selected, members of the Rights Group can view the system's current status and resources using the System
Status Application (SSA).
· Read all configuration
The System Status application includes tools to take a snapshot of the system for use by Avaya for diagnostics.
That snapshot can include a full copy of the system's configuration settings. This setting must be enabled for the
SSA user to include a copy of the configuration in the snapshot.
· System Control: Software level = 6.0+
If enabled, the SSA user is able to use SSA to initiate system shutdowns and memory card shutdown/restarts.
Manager Manager 8.1
Manager
Page 98
15-601011 Issue 25l (11 February 2011)
Security Mode: Editing Security Settings
3.5.4.5 Enhanced TSPI
These settings are displayed when
Rights Groups is selected in the navigation pane. This tab sets whether members
of the group can access the system using the Enhanced TSPI application interface. This interface is only supported by IP
Office Release 5.0 and higher systems.
· Enhanced TSPI Access
If selected, applications in this rights group are able to uses the system's Enhanced TSPI interface. This interface is
currently used by the one-X Portal for IP Office application server for its connection to the system.
3.5.5 Service User Settings
These settings are displayed when
selected in the group pane.
Service Users is selected in the navigation pane and a particular Service User is
Users can be created and deleted using the
Service Users is 16.
and
icons at the top-right of the details pane. The maximum number of
· Name: Range = Up to 31 characters.
Sets the Service User's name. The minimum name length is controlled through
General settings
85
.
· Note: If changing the user name and/or password of the current service user used to load the security settings,
after saving the changes Manager should be closed. Not closing Manager will cause error warnings when attempting
to send any further changes.
· Password: Range = Up to 31 characters.
Sets the Service User's password. The minimum password length and complexity is controlled through
settings 85 .
General
· Account Status: Default = 'Enabled'. Software level = 4.1+.
Displays the current service user account status (correct at the time of reading from the system).
· Enabled
This status is the normal non-error state of a service user account. This setting can be selected manually to re-enable
an account that has been disabled or locked. Note that re-enabling a locked account will reset all timers relating to
the account such as Account Idle Time.
· Force New Password
This status can be selected manually. The service user is then required to change the account password when they
next log in. Until a password change is successful, no service access is allowed. Note that the user must be a
member of a Rights Group that has the Security Administration 97 option Write own service user password
enabled.
· Disabled
This status prevents all service access. This setting can be selected manually. The account can be enabled manually
by setting the Account Status back to Enabled.
Manager Manager 8.1
Manager
Page 99
15-601011 Issue 25l (11 February 2011)
· Locked – Password Error
This status indicates the account has been locked by the Password Reject Action option Log and Disable Account
on the security General Settings 85 tab. The account can be enabled manually by setting the Account Status back
to Enabled.
· Locked - Temporary
This status indicates the account is currently locked temporarily by the Password Reject Action option Log and
Temporary Disable on the security General Settings 85 tab. The account can be enabled manually by setting the
Account Status back to Enabled, otherwise the service user must wait for the 10 minute period to expire.
· Locked - Idle
This status indicates the account has been locked by passing the number of days set for the Account Idle Time on the
security General Settings 85 tab without being used. The account can be enabled manually by setting the Account
Status back to Enabled.
· Locked - Expired
This status indicates the account has been locked after passing the Account Expiry date set below. The account can
be enabled manually by setting Account Status back to Enabled, and resetting the Account Expiry date to a
future date or to No Account Expiry.
· Locked – Password Expired
This status indicates the account has been locked after having not been changed within the number of days set by the
Password Change Period option on the security General Settings 85 tab. The account can be enabled manually by
setting the Account Status back to Enabled.
· Account Expiry: Default = <None> (No Expiry). Software level = 4.1+.
This option can be used to set a calendar date after which the account will become locked. The actual expiry time is
23:59:59 on the selected day. To prompt the user a number of days before the expiry date, set an Expiry Reminder
Time on the security General Settings 85 tab.
· Rights Group Membership
The check boxes are used to set the Rights Groups to which the user belongs. The user's rights will be a combination
of the rights assigned to the groups to which they belong.
Manager Manager 8.1
Manager
Page 100
15-601011 Issue 25l (11 February 2011)
Chapter 4.
Menu Bar Commands
Manager Manager 8.1
Manager
Page 101
15-601011 Issue 25l (11 February 2011)
4. Menu Bar Commands
The commands available through the Manager's menu bar change according to the mode in which Manager is running.
Commands may also be grayed out if not currently applicable. The following sections outline the functions of each
command. The Edit and Help menus are not included.
Configuration Mode
File
Open Configuration... 104
Close Configuration 104
Save Configuration 104
Save Configuration As... 104
Change Working Directory...
Preferences 106
105
Offline
Create New Config 112
Open File... 112
Send Config... 112
Receive Config... 112
Advanced
Erase Configuration (Default) 113
Reboot 113
System Shutdown... 114
Upgrade.. 115
Change Mode... 116
Audit Trail... 118
Security Settings... 119
Erase Security Settings... 119
Embedded File Management 119
Format IP Office SD Card 121
Recreate IP Office SD Card 122
Memory Card Command
125
Shutdown...
125
Start Up...
Voicemail Pro
System Status 124
LVM Greeting Utility
125
124
124
Backup/Restore
Backup Binaries and Configurations 125
Restore Binaries and Configurations 125
Import/Export
Import 127
Export 126
Exit
127
View
Toolbars 128
Navigation Pane 128
Group Pane 128
Details Pane 128
Error Pane 128
Simplified View 128
TFTP Log 129
Tools
Extension Renumber 130
Line Renumber 130
Connect To 130
SCN Service User Management
Busy on Held Validation 131
MSN 132 Configuration 132
Print Button Labels 133
Manager Manager 8.1
Manager
130
Page 102
15-601011 Issue 25l (11 February 2011)
Menu Bar Commands:
Security Mode
File
Open Security Settings 134
Close Security Settings 134
Save Security Settings 134
Reset Security Settings 134
Preferences 134
Configuration 134
Exit 134
View
Toolbars 128
Navigation Pane
Group Pane 128
Details Pane 128
128
Embedded File Management
File
Open File Settings 119
Close File Settings 119
Refresh File Settings 135
Upload File 119
Upload System Files 135
Backup System Files 135
Restore System Files 135
Upgrade Binaries 135
Upgrade Configuration 135
Upload Voicemail Files 136
Upload Phone Files 136
Copy System Card 136
Preferences 106
Configuration 104
Exit 127
View
Toolbars 128
Tiles 119
Icons 119
List 119
Details 119
Manager Manager 8.1
Manager
Page 103
15-601011 Issue 25l (11 February 2011)
4.1 Configuration Mode
These commands are available when the Manager is in configuration mode.
4.1.1 File Menu
4.1.1.1 Open Configuration
This command displays the Select IP Office menu used to receive a systems configuration settings. See Loading a
Configuration 55 .
The same action is performed by the
icon in the Main Toolbar.
The Select IP Office menu is also used for other actions such as reboot and sending a configuration. If the unit required
is not found, the Unit/Broadcast Address can be changed and then Refresh clicked. To change the TCP addresses scanned,
select File | Preferences | Discovery 106 and enter the required addresses in the IP Search Criteria.
Known Units is not available unless configured, see Known System Discovery
59
.
4.1.1.2 Close Configuration
This command closes the currently loaded configuration without saving it.
4.1.1.3 Save Configuration
The File | Save command saves the amended configuration.
If the configuration has been received from a system, the Send Config menu is displayed. See Sending a Configuration
.
64
If the configuration file has been opened offline or created from new, the file is saved to disk only.
4.1.1.4 Save Configuration As
The File | Save As command allows you to save a configuration a file on the Manager computer. The command displays
the Save File As dialog box. You can enter the new file name, including the drive and directory.
Configurations saved onto the PC in this way can be reopened using the
command.
icon or the File | Offline | Open File
112
Note that dynamic configuration data, for example advertised hunt groups on other systems, is not included in a
configuration file saved onto PC and then reopened.
Manager Manager 8.1
Manager
Page 104
15-601011 Issue 25l (11 February 2011)
Menu Bar Commands: Configuration Mode
4.1.1.5 Change Working Directory
This command allows you to change the default locations where Manager looks for and saves files.
These fields set the default location where Manager will look for and save files. This tab is also accessed by the File |
Change Working Directory command.
· Working Directory (.cfg files)
Sets the directory into which Manager saves .cfg files. By default this is the Manager application's program
directory.
· This folder location is also used for the Recreate IP Office SD Card command. It uses sub-folders of
the \Memory Cards folder at the specified locations. If the Working Directory is changed to a location without
an appropriate set of \Memory Cards sub-folders, the required set of files will not be copied onto the SD
card.
· Binary Directory (.bin files)
Sets the directory in which the Manager upgrade wizard, HTTP, TFTP and BOOTP functions look for firmware files
requested by phones, expansion module, control units and other hardware components. That includes .bin file, .scr
files and .txt files. By default this is the Manager application's program directory.
· Note that in the Upgrade Wizard
115 ,
right-clicking and selecting Change Directory also changes this setting.
· Known IP Office File: Software level = 4.0 Q2 2007 maintenance release+.
Sets the file and directory into which Manager can record details of the systems it has discovered. Once a file
location has been specified, a Known Units 59 button becomes available on the discovery menu used for loading
system configuration. Pressing that button displays the known units file as a list from which the required system
can be selected. It also allows sorting of the list and entries to be removed.
Manager Manager 8.1
Manager
Page 105
15-601011 Issue 25l (11 February 2011)
4.1.1.6 Preferences
This command displays a menu for configuring various aspects of Manager's operation. The menu is divided into a number
of tabs.
· Preferences
· Directories
106
107
· Visual Preferences
· Discovery
108
· Validation
112
· Security
109
110
4.1.1.6.1 Preferences
This tab is accessed through File | Preferences and then selecting the Preferences sub-tab.
· Edit Services Base TCP Port: Default = On.
This field shows or hides the Service Base TCP Port setting.
· Service Base TCP Port: Default = 50804. Software level = 3.2+.
Access to the configuration and security settings on a system requires Manager to send its requests to specific
ports. This setting allows the TCP Base Port used by Manager to be set to match the TCP Base Port setting of
the system. The system's TCP Base Port is set through its security settings.
· Enable Time Server: Default = On.
This setting allows Manager to respond to RFC868 Time requests from systems. It will provide the system with both
the UTC time value and the local time value of the PC on which it is running. See Date and Time 727 .
· Enable BootP and TFTP Servers: Default = On.
This setting allows Manager to respond to BOOTP request from systems for which it also has a matching BOOTP
entry. It also allows Manager to respond to TFTP requests for files.
· Enable Port for Serial Communication
Not used. This is a legacy feature for some older control units that were managed via the serial port rather than the
LAN.
· Enter Port Number to be used for Serial Communication
Used with the setting above to indicate which serial port Manager should use.
· Auto Connect on start up: Default = On
If on, when Manager is started it will automatically launch the Select IP Office menu and display any discovered
systems. If only one system is discovered, Manager will automatically display the login request for that system or
load its configuration if the security settings are default.
· Simplified View: Default = On
If on, the Manager will start in simplified view
Manager Manager 8.1
Manager
18
mode if no configuration is loaded.
Page 106
15-601011 Issue 25l (11 February 2011)
Menu Bar Commands: Configuration Mode
4.1.1.6.2 Directories
This tab is accessed through File | Preferences and then selecting the Directories sub-tab.
These fields set the default location where Manager will look for and save files. This tab is also accessed by the File |
Change Working Directory command.
· Working Directory (.cfg files)
Sets the directory into which Manager saves .cfg files. By default this is the Manager application's program
directory.
· This folder location is also used for the Recreate IP Office SD Card command. It uses sub-folders of
the \Memory Cards folder at the specified locations. If the Working Directory is changed to a location without
an appropriate set of \Memory Cards sub-folders, the required set of files will not be copied onto the SD
card.
· Binary Directory (.bin files)
Sets the directory in which the Manager upgrade wizard, HTTP, TFTP and BOOTP functions look for firmware files
requested by phones, expansion module, control units and other hardware components. That includes .bin file, .scr
files and .txt files. By default this is the Manager application's program directory.
· Note that in the Upgrade Wizard
115 ,
right-clicking and selecting Change Directory also changes this setting.
· Known IP Office File: Software level = 4.0 Q2 2007 maintenance release+.
Sets the file and directory into which Manager can record details of the systems it has discovered. Once a file
location has been specified, a Known Units 59 button becomes available on the discovery menu used for loading
system configuration. Pressing that button displays the known units file as a list from which the required system
can be selected. It also allows sorting of the list and entries to be removed.
Manager Manager 8.1
Manager
Page 107
15-601011 Issue 25l (11 February 2011)
4.1.1.6.3 Discovery
This tab is accessed through File | Preferences and then selecting the Discovery sub-tab.
These settings affect the Select IP Office menu used by Manager to discovery systems. By default IP Office 3.2 systems
respond to both UDP and TCP discovery. Pre-3.2 systems only support UDP discovery.
· TCP Discovery: Default = On. Software level = 3.2+.
This setting controls whether Manager uses TCP to discover systems. The addresses used for TCP discovery are set
through the IP Search Criteria field below.
· NIC IP/NIC Subnet
This area is for information only. It shows the IP address settings of the LAN network interface cards (NIC) in
the PC running Manager. Double-click on a particular NIC to add the address range it is part of to the IP Search
Criteria. Note that if the address of any of the Manager PC's NIC cards is changed, the Manager application
should be closed and restarted.
· IP Search Criteria
This section is used to enter TCP addresses to be used for the TCP discovery process. Individual addresses can
be entered separated by semi-colons, for example 135.164.180.170; 135.164.180.175. Address ranges can be
specified using dashes, for example 135.64.180.170 - 135.64.180.175.
· UDP Discovery: Default = On
This settings controls whether Manager uses UDP to discover systems. Pre-3.2 systems only respond to UDP
discovery. By default IP Office 3.2 and higher systems also respond to UDP discovery but that can be disabled
through the system's security settings.
· Enter Broadcast IP Address: Default = 255.255.255.255
The broadcast IP address range that Manager should used during UDP discovery. Since UDP broadcast is not
routable, it will not locate systems that are on different subnets from the Manager PC unless a specific address
is entered.
· Use DNS: Software level = Manager 6.2+.
Selecting this option allows Manager to use DNS name (or IP address) lookup to locate a system. Note that this
overrides the use of the TCP Discovery and UDP Discovery options above. This option requires the system IP
address to be assigned as a name on the users DNS server. When selected, the Unit/Discovery Address field on
the Select IP Office 55 dialogue is replaced by a Enter Unit DNS Name or IP Address field.
· SCN Discovery: Software level = Manager 8.1+.
If enabled, when discovering systems, the list of discovered systems will group systems in the same Small
Community Network and allow them to be loaded as a single configuration. At least one of the systems in the SCN
must be running Release 6.0 or higher software. See SCN Management 817 . This does not override the need for
each system in the SCN to also be reachable by the TCP Discovery and or UDP Discovery settings above and
accessible by the router settings at the Manager location.
Manager Manager 8.1
Manager
Page 108
15-601011 Issue 25l (11 February 2011)
Menu Bar Commands: Configuration Mode
4.1.1.6.4 Visual Preferences
This tab is accessed through File | Preferences and then selecting the Visual Preferences sub-tab.
· Icon size
Sets the size for the icons in the navigation pane between Small, Medium or Large.
· Multiline Tabs: Default = Off.
In the details pane, for entry types with more than two tabs, Manager can either use
buttons to scroll the
tabs horizontally or arrange the tabs into multiple rows. This setting allows selection of which method Manager
uses.
Manager Manager 8.1
Manager
Page 109
15-601011 Issue 25l (11 February 2011)
4.1.1.6.5 Security
This tab is accessed through File | Preferences and then selecting the Security sub-tab.
Controls the various security settings of Manager. To control the security settings of the system, see Security Mode
68
.
All settings, except Secure Communications, can only be changed when a configuration has been opened using a user
name and password with Administrator rights or security administration rights.
· Request Login on Save: Default = On
By default a valid user name and password is required to receive a configuration from a system and also to send that
same configuration back to the system. Deselecting this setting allows Manager to send the configuration back without
having to renter user name and password details. This does not apply to a configuration that has been saved on PC and
then reopened. This setting can only be changed when a configuration has been opened using a user name and
password with Administrator rights or security administration rights.
· Close Configuration/Security Settings After Send: Default = On.
When selected, the open configuration file or security settings are closed after being sent back to the system. This
setting does not affect SCN management mode which always closes the configuration after saving.
· Save Configuration File After Load: Default = On.
When selected, a copy of the configuration is saved to Manager's working directory 107 . The file is named using the
system name and the suffix .cfg. This setting can only be changed when a configuration has been opened using a user
name and password with Administrator rights or security administration rights.
· Backup Files on Send: Default = On.
If selected, whenever a copy of a configuration is sent to a system, a backup copy is saved in Manager's working
directory 107 . The file is saved using the system name, date and a version number followed by the Backup File
Extension as set below. This setting can only be changed when a configuration has been opened using a user name
and password with Administrator rights or security administration rights.
· Backup File Extension: Default = .BAK
Sets the file extension to use for backup copies of system configurations generated by the Backup Files on Send
option above.
· Number of Backup Files to keep: Default = Unlimited. Software level = 4.2+.
This option allows the number of backup files kept for each system to be limited. If set to a value other then Unlimited,
when that limit would be exceeded, the file with the oldest backup file is deleted.
· Enable Application Idle Timer (5 minutes): Default = Off. Software level = 4.1+.
When enabled, no keyboard or mouse activity for 5 minutes will cause the Manager to grey out the application and rerequest the current service user password. This setting can only be changed when a configuration has been opened
using a user name and password with Administrator rights or security administration rights.
· Secure Communications: Default = Off. Software level = 4.1+.
When selected, any service communication from Manager to the system uses the TLS protocol. This will use the ports
set for secure configuration and secure security access. It also requires the configuration and or security service within
the system's security configuration settings to have been set to support secure access. Depending on the level of that
secure access selected, it may be necessary for the Manager Certificate Checks below to be configured to match those
expected by the system for configuration and or security service. See Security Administration 74 .
· When Secure Communications is set to On, a
status field.
Manager Manager 8.1
Manager
padlock icon is displayed at all times in the lower right Manager
Page 110
15-601011 Issue 25l (11 February 2011)
Menu Bar Commands: Configuration Mode
· Manager Certificate Checks: Software level = 4.1+.
When the Secure Communications option above is used, Manager will process and check the certificate received from
the system. This setting can only be changed when a configuration has been opened using a user name and password
with Administrator rights or security administration rights.
· Low
Any certificate sent by the system is accepted without question.
· Medium
Any certificate sent by the system is accepted if it has previously been previously saved in the Windows' certificate
store. If the certificate has not been previously saved, the user has the option to review and either accept or reject
the certificate.
· High
Any certificate sent by the system is accepted if it has previously been previously saved in the Windows' certificate
store. Any other certificate cause a log in failure.
· Certificate Offered to IP Office: Default = none
Specifies the certificate used to identify Manager when the Secure Communications option is used and the system
requests a certificate. Use the Set button to change the selected certificate. Any certificate selected must have an
associated private key held within the store:
· Select from Current User certificate store - Display certificates currently in the currently logged-in user store.
· Select from Local Machine certificate store.
· Remove Selection – do not offer a Manager certificate.
Security – Registry Settings
· WARNING: Changing Windows Registry Settings
Avaya accept no liability for any issues arising from the editing of a PC’s 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.
NOTE: Before manually editing any registry entry, the following Microsoft support articles should be read:
· http://support.microsoft.com/kb/256986
· http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/regedit_permit_key.mspx
Manager stores it’s security preferences in the Windows Registry. The following key affects manager security operation;
it’s values may only be changed by a configuration or security administrator:
· HKEY_CURRENT_USER\Software\Avaya\IP400\Manager\Security\
In order to prevent circumvention by manual editing of the Windows Registry, Regedt32.exe, the native registry editor,
allows an operator user (with Full Control permissions) to edit permissions on a per key basis.
To prevent a user from manually editing the security preferences, the HKEY_USERS\User GUID\Software\Avaya\IP400
\Manager\Security key permission should be set to ‘Read’ only for that user. Ensure that all child object permissions are
replaced as well by using the ‘Advanced’ button.
To allows the security policy of all local PC users to be fixed, a set of values in the key
HKEY_CURRENT_USER\Software\Avaya\IP400\Manager\Security\ may be created. This is tested and used in preference
to any value found under HKEY_CURRENT_USER\Software\Avaya\IP400\Manager\Security\.
This key is not created by the manager application.
Manager Manager 8.1
Manager
Page 111
15-601011 Issue 25l (11 February 2011)
4.1.1.6.6 Validation
This tab is accessed through File | Preferences and then selecting the Validation sub-tab.
By default Manager validates the whole configuration when it is loaded and individual fields whenever they are edited. This
tab allows selection of when automatic validation should be applied to configuration files loaded into Manager.
· Validate configuration on open
Automatically validate configuration files when they are opened in Manager.
· Validate configuration on edit
Validate the whole configuration when OK is clicked after editing a record. For large configurations, disabling this
option removes the delay caused by validating the configuration after every edit.
· Prompt for configuration validation on save or send
If selected, when saving or sending a configuration, a prompt is displayed asking whether the configuration should
be validated. If validation is selected and error are found, the send or save process is canceled. This option is
disabled if Validate configuration on edit is selected.
4.1.1.7 Offline
4.1.1.7.1 Create New Config
This command starts a dialog that allows you to create a default offline configuration by specifying the system locales, the
type of control unit and expansion modules and the trunk cards fitted. See Creating a New Configuration 60 .
The same action is performed by the
icon in the Main Toolbar.
4.1.1.7.2 Open File
This command allows a configuration file stored on PC to be opened in Manager.
4.1.1.7.3 Send Config
This command is used to send an offline configuration to a system. See Sending a Configuration
64
.
4.1.1.7.4 Receive Config
This command displays the Select IP Office menu used to receive a systems configuration settings. See Loading a
Configuration 55 .
Once the configuration has been received, you are prompted to save it on the PC.
Manager Manager 8.1
Manager
Page 112
15-601011 Issue 25l (11 February 2011)
Menu Bar Commands: Configuration Mode
4.1.1.8 Advanced
4.1.1.8.1 Erase Configuration
This command returns the configuration settings of a system back to their default values
system's security settings or audit trail record.
65
. It does not affect the
When this command is used, the Select IP Office menu is displayed. Once a system is selected, a valid configuration user
name and password are required to complete the action.
4.1.1.8.2 Reboot
When this command is used, the Select IP Office menu is displayed. Once a system is selected, a valid user name and
password are required. The type of reboot can then be selected.
· Reboot
If Manager thinks the changes made to the configuration settings are mergeable, it will select Merge by default,
otherwise it will select Immediate.
· Immediate
Send the configuration and then reboot the system.
· When Free
Send the configuration and reboot the system when there are no calls in progress. This mode can be combined
with the Call Barring options.
· Timed
The same as When Free but waits for a specific time after which it then wait for there to be no calls in
progress. The time is specified by the Reboot Time. This mode can be combined with the Call Barring
options.
· Reboot Time
This setting is used when the reboot mode Timed is selected. It sets the time for the Manager reboot. If the time is
after midnight, the system's normal daily backup is canceled.
· Call Barring
These settings can be used when the reboot mode When Free is selected. They bar the sending or receiving of any
new calls.
Manager Manager 8.1
Manager
Page 113
15-601011 Issue 25l (11 February 2011)
4.1.1.8.3 System Shutdown
IP Office Release 6.0+: This command can be used to shutdown systems. The shut down can be either indefinite or for a
set period of time after which the system will reboot.
! WARNINGS
· 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.
· 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.
· The shutdown process takes up to a minute to complete. When shutdown, the CPU LED and the control unit 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 this state.
· To restart a system when shutdown indefinitely, or to restart a system before the timed restart, switch power to
the system off and on again.
1. Once you have selected the system from the Select IP Office menu, the System Shutdown Mode menu is
displayed.
2. Select the type of shutdown required. If Indefinite is used, the system can only be restarted by having its power
switched off and then on again. If a Timed shutdown is selected, the system will reboot after the set time has
elapsed.
Manager Manager 8.1
Manager
Page 114
15-601011 Issue 25l (11 February 2011)
Menu Bar Commands: Configuration Mode
4.1.1.8.4 Upgrade
This command starts the Upgrade Wizard tool. This tool is used to compare the software level of the control unit and
expansion modules within systems against the software level of the .bin binary files Manager has available. The Upgrade
Wizard can then be used to select which units to upgrade.
·
WARNING
Incorrect use of the upgrade command can halt system operation and render units in the system unusable. You
must refer to the Technical Bulletins for a specific release for full details of performing software upgrades to that
release.
· Performing any other actions on a system during an upgrade or closing the upgrade wizard and Manager during an
upgrade may render systems unusable.
· During an upgrade the system may restrict calls and services. It will reboot and disconnect all current calls and
services.
· The Validate option must remain selected wherever possible. Use of unvalidated upgrades is subject to a number
of conditions outlined in the Manager Installation Manual and Technical Bulletins.
The list area shows details of systems found by the Upgrade Wizard and the software currently held by that system.
· The check boxes are used to select which units should be upgraded. Upgrading will require entry of a valid name
and password for the selected system.
· The Version column details the current software each unit in the systems is running.
· The Available column shows the version of .bin file Manager has available for that type of unit (a – indicates no file
available).
· The Mode column indicates the operation mode of the system.
· The Licensed column indicates the highest value software upgrade license present in the systems configuration.
The Required License column indicates the software upgrade license required for the current level of software it is
running. It does not refer to the software upgrade license required for the level of software which is available for
upgrade. IP500v2 systems, a value of 255 indicates that the control unit is still in its initial 90 days where it can be
upgraded to a higher level without requiring a license.
· The Validate option should remain selected wherever possible. When selected, the upgrade process is divided as
follows: transfer new software, confirm transfer, delete old software, restart with new software. If Validate is not
selected, the old software is deleted before the new software is transferred.
· For any IP500v2 systems being upgraded, the Backup system files option will cause the system to backup its
memory card files as part of the upgrade.
· For any IP500v2 system being upgraded, the Upload system files option will upload copies of the new system
binaries to the units memory card.
Manager Manager 8.1
Manager
Page 115
15-601011 Issue 25l (11 February 2011)
· IP Office Manager 8.1+: The Restart IP Phones option can be used. This will cause those phone to load any
upgrade phone firmware included in the system upgrade (if using the system's memory card as their firmware file
source).
Search for Particular Systems
The default address used by the Upgrade Wizard is the address shown in the Manager title bar, which is selected through
File | Preferences 108 . If the unit required is not found, the address used can be changed.
1. Enter or select the required address in the Unit/Broadcast Address field.
2. Click Refresh to perform a new search.
Changing the .bin File Directory Used
The directory in which the Upgrade Wizard looks for .bin files is set through Manager's Binary Directory setting. This can
be changed using Files | Change Working Directory 105 or File | Preferences | Directories 107 . It can also be
changed directly from the Upgrade Wizard as follows.
1. Right-click on the list area.
2. Select Select Directory.
3. Browse to and highlight the folder containing the .bin files. Click OK.
4. The list in the Available column will be updated to show the .bin files in the selected directory that match units or
modules listed.
4.1.1.8.5 Change Mode
This command can be used to change the operating mode of an IP500v2 System SD card and thus of the system.
· Using this command will default the existing configuration. Therefore ensure that you have a backup copy of the
configuration before using this command in case it is necessary to return to the previous mode.
· Do not use this command if the system includes components not supported by the mode to which you want to
switch, the system may not restart correctly if that is the case. For example BRI cards are not supported in IP
Office Essential Edition - PARTNER® Version mode.
· In order to use this command, the system security settings must first be defaulted. This can be done using the
Erase Security Settings (Default) 119 command.
· Follow the command, the system is restarted.
The menu displayed after selecting a system depends on the current mode of that system:
· This menu is displayed for switching a non-IP Office Standard Version mode system to IP Office Standard Version
mode.
· This menu is displayed for switching a IP Office Standard Version mode system to one of the non-IP Office Standard
Version modes.
Manager Manager 8.1
Manager
Page 116
15-601011 Issue 25l (11 February 2011)
Menu Bar Commands: Configuration Mode
Manager Manager 8.1
Manager
Page 117
15-601011 Issue 25l (11 February 2011)
4.1.1.8.6 Audit Trail
The audit trail lists the last 16 actions performed on the system from which the configuration loaded into Manager was
received. It includes actions by Service Users such as getting the configuration, sending a configuration back, reboots,
upgrades and default the system. The audit trail is not available for systems running pre-3.2 Manager software.
IP Office 4.1+: Audit trail events can be output to a Syslog server through the system's System | System Events
settings.
The last failed action is always recorded and shown in red. It is kept even if there have been 16 subsequent successful
actions.
· The Audit Trail is part of the system configuration file received from the system. If the configuration is kept open
between send and reboot operations (ie. if Close Configuration/Security Setting After Send 110 is not
selected), the Audit Trail will not show details of those operations. It will only show details of those operations if the
configuration is closed and then a new copy of the configuration is received from the system.
· Audit Details
When a specific access event is selected from the list, the following information is shown in the Audit Details
section:
· The Security User shows the service user name used for the access action.
· The Data and Time of Access indicate the local system time when the recorded event occurred.
· The PC Login is the computer name of the PC used for the access.
· The PC IP Address and PC MAC Address are the IP address and MAC address of the PC used for access.
· The Access Type details the type of action that was performed.
· The Outcome shows the system's response to the access. The outcome Success (Warning) refers to the
sending of a configuration that contains fields marked as errors or warnings by Manager's validation function.
Success (Clean) refers to the sending of a configuration that does not contain any validation errors or
warnings.
· Items Changed
The Items Changed area summarizes the changes contained in a sent configuration. Where changes to a single
entry of a particular type are made, the Item Name field lists the individual entry changed. Where changes are
made to several entries of the same type, the Item Name field displays Multiple items.
Manager Manager 8.1
Manager
Page 118
15-601011 Issue 25l (11 February 2011)
Menu Bar Commands: Configuration Mode
4.1.1.8.7 Security Settings
This command is used to switch the Manager application to security mode. In that mode, Manager is used to edit the
security settings of a system (3.2 or higher only). Refer to the section Security Mode 68 .
4.1.1.8.8 Erase Security Settings (Default)
IP Office 4.1+: This command returns the security settings of a system back to their default values. This action does not
affect the system's configuration or audit trail record.
When this command is used, the Select IP Office menu is displayed. Once a system is selected, a valid user name and
password are required to complete the action.
4.1.1.8.9 Embedded File Management
IP Office 4.2+: For control units (except Small Office Edition) with an memory card installed, the contents of the card can
be viewed through Manager. This view can also be used to add and remove files from the card. This may be useful when
the memory card is being used to store Music on Hold or IP phone firmware files.
· Embedded Voicemail Files
When viewing the memory card, the files related to Embedded Voicemail are visible, however these files are greyed
out (ie. cannot be deleted, downloaded or overwritten).
· Mailbox greetings and messages are shown as .clp files.
· The language prompts for Embedded Voicemail functions are stored in separate language sub-folders of lvmail
. These are either .c11 (IP500/IP500v2 and IP406 V2) or .c23 (Small Office Edition) files.
· Named prompt files for use by Embedded Voicemail auto attendants are stored in the lvmail\AAG folder and
use the same .c11 or .c23 file formats as the language prompts. These files can be created from standard .
wav files before being downloaded to the memory card by using the LVM Greeting Utility 124 .
· IP Office Release 5.0+: The Manager menu option File | Upload Voicemail Files will automatically select and
transfer all Embedded Voicemail language prompts onto the card.
· Avaya IP Phone Files
The memory card can be used as the source of files requested by IP Phones when rebooting. For phones using
system DHCP, once the files are loaded onto the card, the TFTP Server IP Address 143 and HTTP Server IP
Address 143 on the System | System 143 tab must be set to match the system's LAN address.
· IP Office Release 5.0+: The Manager menu option File | Upload Phone Files will automatically select and
transfer all DS phone, H323 phone and IP DECT binary files from the Manager folder to the embedded memory
card.
Manager Manager 8.1
Manager
Page 119
15-601011 Issue 25l (11 February 2011)
· Viewing a Memory Card
When Advanced | Embedded File Management is selected, the Manager will go through normal system
discovery but will only allow selection of systems which can support a memory card. When a system is selected, a
valid service user name and password for configuration access to that system is requested. If the system selected
does not have a memory card installed, the files view remains blank and the message TFTP:Received TFTP Error
"Not Found" appears in Manager's status bar.
· Changing the Files View
The type of display used in the Files pane can be changed by selecting from the View menu in the toolbar.
· Adding Files
Files can be added to the card by dragging and dropping or by right-clicking on the Files pane and selecting Upload
or by using File | Upload File.... The system will ask for confirmation if the file already exists on the memory card.
The progress of the file upload is then indicated.
· Deleting Files
Existing files can be deleted by right-clicking on them and selecting Delete.
· Downloading Files
Files can also be copied from the card by right-clicking on the file and selecting Download. Manager will prompt for
the download location. Existing files are overwritten if present.
· To exit this mode of Manager back to normal configuration operation, select File | Configuration from the menu
bar. Alternatively to view the card in another system, select File | Close File Settings and then File | Open File
Settings.
Manager Manager 8.1
Manager
Page 120
15-601011 Issue 25l (11 February 2011)
Menu Bar Commands: Configuration Mode
4.1.1.8.10 Format IP Office SD Card
This command allows suitable SD cards to be formatted by the Manager PC. The system supports SD cards with the
following format: SDHC minimum 4GB FAT32 format (Single partition, SDHC, class2+, FAT32, SPI & SD bus). Non-Avaya
supplied cards of the same format can be used a system's Optional SD slot for additional actions such as backup.
·
! Warning
Do not re-purpose an Avaya Branch Gateway SD card for use with any other IP Office mode. Doing so may damage
the SD card and make it unusable for your Avaya Branch Gateway system.
·
! WARNING: All File Will Be Erased
Note that this action will erase any existing files and folders on the card. If the requirement is just to update the
card, use Recreate IP Office SD Card 122 without reformatting. Once a card has been formatted, the folders and
files required for operation can be loaded onto the card from the Manager PC using the Recreate IP Office SD Card
122 command.
·
! WARNING:
Avaya supplied SD cards should not be formatted using any other method than the format commands within
Manager and System Status Application. Formatting the cards using any other method will remove the feature key
used for system licensing from the card.
1. Insert the SD card into a reader slot on the Manager computer.
2. Using Manager, select File | Advanced | Format IP Office SD Card.
3. Select the type of card. This selection just sets the card label shown when viewing the card details. It does not
affect the actual formatting. Select the label that matches the file set you will be placing on the card.
· IP Office A-Law
A system fitted with this type of card will default to A-Law telephony. The system will default to IP Office
Standard Version mode.
· IP Office U-Law
A system fitted with this type of card will default to U-Law telephony. The system will default to IP Office
Standard Version mode.
· IP Office Partner Edition
A system fitted with this type of card will default to A-Law telephony and IP Office Essential Edition PARTNER® Version mode operation.
· IP Office Norstar Edition
A system fitted with this type of card will default to U-Law telephony and IP Office Essential Edition - Norstar
Version mode operation.
· Avaya Branch Gateway
Use this option for an SD card intended to be used with a system running in Avaya Branch Gateway mode.
There is a separate SD card for Avaya Branch Gateway. The Avaya Branch Gateway SD card can only be used
for Avaya Branch Gateway operation and cannot be used to change modes to IP Office. The label on the SD
card includes BRANCH GW to indicate it is an Avaya Branch Gateway SD card. You also cannot use or change
an IP Office SD card for use with an Avaya Branch Gateway system.
·
! Warning
Do not re-purpose an Avaya Branch Gateway SD card for use with any other IP Office mode. Doing so may
damage the SD card and make it unusable for your Avaya Branch Gateway system.
4. Browse to the card location and click OK.
5. The status bar at the bottom of Manager will display the progress of the formatting process.
6. When the formatting is complete, you can use the Recreate IP Office SD Card
folders and files onto the card from the Manager PC.
122
command to load the system
· A-Law or U-Law
PCM (Pulse Code Modulation) is a method for encoding voice as data. In telephony, two methods of PCM encoding
are widely used, A-Law and U-Law (also called Mu-Law or µ-Law). Typically U-Law is used in North America and a
few other locations while A-Law is used elsewhere. As well as setting the correct PCM encoding for the region, the
A-Law or U-Law setting of a system when it is first started affects a wide range of regional defaults relating to line
settings and other values.
· For IP400 systems, each control units was manufactured as either an A-Law variant or a U-Law variant.
· For IP500 and IP500v2 systems, the encoding default is set by the type of Feature Key installed when the
system is first started. The cards are either specifically A-Law or U-Law. PARTNER Version cards are U-Law.
Norstar Version cards are A-Law.
Manager Manager 8.1
Manager
Page 121
15-601011 Issue 25l (11 February 2011)
4.1.1.8.11 Recreate IP Office SD Card
This command can be used with a read-writeable SD card on the Manager PC. It copies the files and folders used by an
IP500v2 system when starting. It updates the card with the version of those files installed with the Manager application. It
includes the binary files for the system, external expansion modules and phones. It also includes the prompt files for
embedded voicemail operation.
This process just replaces existing files and adds new files. It does not delete files, so for example, any existing embedded
voicemail messages and greetings are retained. If the card contains dynamic system files such as SMDR records, they are
temporarily backed up by Manager and then restored after the card is recreated.
For the card to be used in a system's System SD slot the card must be Avaya SD Feature Key card. The card must be
correctly formatted (see Format IP Office SD card 121 ), however a reformat of an existing working card is not necessary
before using recreate to update the card contents.
· The source for the files copied to the SD card are the sub-folders of the \Memory Cards folder under Manager's
Working Directory 107 (normally C:\Program Files Avaya\IP Office\Manager). However, if the Working
Directory is changed to a location without an appropriate set of \Memory Cards sub-folders, the required set of
files will not be copied onto the SD card.
·
! Warning
Do not re-purpose an Avaya Branch Gateway SD card for use with any other IP Office mode. Doing so may damage
the SD card and make it unusable for your Avaya Branch Gateway system.
1. Note: This process can take up to 20 minutes depending on the PC. Once started, the process should not be
interrupted.
2. Insert the SD card into a reader slot on the Manager computer.
3. Using Manager, select File | Advanced | Recreate IP Office SD Card.
4. Select the type of system for which the card is intended. This selection will affect how the systems operates when
defaulted with this card present in its System SD card slot.
· IP Office A-Law
A system fitted with this type of card will default to A-Law telephony. The system will default to IP Office
Standard Version mode.
· IP Office U-Law
A system fitted with this type of card will default to U-Law telephony. The system will default to IP Office
Standard Version mode.
· IP Office Partner Edition
A system fitted with this type of card will default to A-Law telephony and IP Office Essential Edition PARTNER® Version mode operation.
· IP Office Norstar Edition
A system fitted with this type of card will default to U-Law telephony and IP Office Essential Edition - Norstar
Version mode operation.
· Avaya Branch Gateway
Use this option for an SD card intended to be used with a system running in Avaya Branch Gateway mode.
There is a separate SD card for Avaya Branch Gateway. The Avaya Branch Gateway SD card can only be used
for Avaya Branch Gateway operation and cannot be used to change modes to IP Office. The label on the SD
card includes BRANCH GW to indicate it is an Avaya Branch Gateway SD card. You also cannot use or change
an IP Office SD card for use with an Avaya Branch Gateway system.
·
! Warning
Do not re-purpose an Avaya Branch Gateway SD card for use with any other IP Office mode. Doing so may
damage the SD card and make it unusable for your Avaya Branch Gateway system.
5. Browse to the card location and click OK.
6. Manager will start creating folders on the SD card and copying the required files into those folders.
7. Do not remove the card until the process is completed and Manager displays a message that the process has been
completed.
· A-Law or U-Law
PCM (Pulse Code Modulation) is a method for encoding voice as data. In telephony, two methods of PCM encoding
are widely used, A-Law and U-Law (also called Mu-Law or µ-Law). Typically U-Law is used in North America and a
few other locations while A-Law is used elsewhere. As well as setting the correct PCM encoding for the region, the
A-Law or U-Law setting of a system when it is first started affects a wide range of regional defaults relating to line
settings and other values.
· For IP400 systems, each control units was manufactured as either an A-Law variant or a U-Law variant.
Manager Manager 8.1
Manager
Page 122
15-601011 Issue 25l (11 February 2011)
Menu Bar Commands: Configuration Mode
· For IP500 and IP500v2 systems, the encoding default is set by the type of Feature Key installed when the
system is first started. The cards are either specifically A-Law or U-Law. PARTNER Version cards are U-Law.
Norstar Version cards are A-Law.
Manager Manager 8.1
Manager
Page 123
15-601011 Issue 25l (11 February 2011)
4.1.1.8.12 LVM Greeting Utility
This command launches a utility that can be used to convert .wav files to the formats used by embedded voicemail (.c23
for Small Office Edition and .c11 for others). The source file must be in the standard format used for all system
applications: PCM, 8kHz 16-bit, mono.
The resulting named greeting files can then be transferred to the embedded voicemail memory card and selected as auto
attendant greetings. That is done using the Recording Name 402 field on the Auto Attendant | Auto Attendant 402
tab. The same named greeting file can be used in several auto attendants.
The utility can be run separately using the file LVMGreeting.exe found in the LVMGreeting sub-folder of the Manager
application.
4.1.1.8.13 Voicemail Pro
If the Voicemail Pro client is installed on the same PC and Manager, this link can be used to launch the Voicemail Pro
client. This can also be done by clicking on the
icon in the Manager toolbar.
4.1.1.8.14 System Status
IP Office 4.0+: System Status is an application that can be used to monitor and report on the status of a system.
This is a separate application from Manager but if installed on the same PC, it can be started using the File | Advanced |
System Status link within Manager. Use of the application requires a service user name and password configured on the
system for System Status Access within the system's security settings.
Manager Manager 8.1
Manager
Page 124
15-601011 Issue 25l (11 February 2011)
Menu Bar Commands: Configuration Mode
4.1.1.8.15 Memory Card Command
These commands are used with the memory cards installed in IP500/IP500v2 control units.
4.1.1.8.15.1 Shutdown
This command can be used to shutdown operation of IP500/IP500v2 memory cards.
This action or a system shutdown 114 must be performed before a memory card is removed from the unit. Removing a
memory card while the system is running may cause file corruption.
Shutting down the memory card will disable all services provided by the card including embedded voicemail. For IP500v2
systems, features licensed by the memory card will continue to operate for up to 2 hours.
Card services can be restarted by either reinserting the card or using the Start Up
125
command.
4.1.1.8.15.2 Start Up
This command can be used to restart operation of an IP500/IP500v2 memory card that has been shut down
125 .
The command will start the Select IP Office discovery process for selection of the system.
4.1.1.9 Backup/Restore
4.1.1.9.1 Backup Binaries and Configuration
This command copies of all configuration files (.cfg) and software files (.bin) stored in Manager's working directory to a
selected folder.
4.1.1.9.2 Restore Binaries and Configuration
This command copies all configuration files (.cfg) and software files (.bin) stored in a selected folder to the Manager's
working directory.
Manager Manager 8.1
Manager
Page 125
15-601011 Issue 25l (11 February 2011)
4.1.1.10 Import/Export
4.1.1.10.1 Export
This command allows you to export the selected parts of the configuration to either a set of CSV text files (.csv) or a
single binary file (.exp). See Importing and Exporting Settings 61 .
The display shows those exportable entry types for which the configuration contains entries. The File Type and the Save In
path can be selected at the base. The default location used is sub-directory of the Manager application directory based on
system name of the currently loaded system.
Manager imports and exports CSV files using UTF8 character encoding which uses a double byte to support characters with
diacritic marks such as ä. Other applications such as Excel, depending on the user PC settings, may use different singlebyte encoding which will cause such characters to be removed. Care should be taken to ensure that any tool used to
create or edit a CSV supports all the characters expected and is compatible with UTF8.
Manager Manager 8.1
Manager
Page 126
15-601011 Issue 25l (11 February 2011)
Menu Bar Commands: Configuration Mode
4.1.1.10.2 Import
This command allows you to import configuration settings. Two formats are supported. Binary files (.exp) are settings
previously exported from a system using File | Import /Export | Export 126 . CSV text files (.csv) can also be exported
from a system or can be created using a plain text editor. See Importing and Exporting Settings 61 .
For the selected File Type and the Look In path, the window displays the file or files found. The default location used is
sub-directory of the Manager application directory based on system name of the currently loaded system.
Manager imports and exports CSV files using UTF8 character encoding which uses a double byte to support characters with
diacritic marks such as ä. Other applications such as Excel, depending on the user PC settings, may use different singlebyte encoding which will cause such characters to be removed. Care should be taken to ensure that any tool used to
create or edit a CSV supports all the characters expected and is compatible with UTF8.
4.1.1.11 Exit
The File | Exit command exits the Manager application.
Manager Manager 8.1
Manager
Page 127
15-601011 Issue 25l (11 February 2011)
4.1.2 View
4.1.2.1 Toolbars
This command allows selection of which toolbars should be shown or hidden in configuration mode. A tick mark is
displayed next to the name of those toolbars that are currently shown.
4.1.2.2 Tooltip
This setting control whether additional tooltips are displayed when Manager is running in Partner Version mode.
4.1.2.3 Navigation Pane
This command shows or hides the Navigation Pane. A tick mark appears next to the command when the pane is shown.
4.1.2.4 Group Pane
This command shows or hides the Group Pane. A tick mark appears next to the command when the pane is shown.
4.1.2.5 Details Pane
This command set the location of the Details Pane when the Group Pane is also shown. The Details Pane can be placed
either below or to the right of the Group Pane.
4.1.2.6 Error Pane
This command shows or hides the Error Pane. A tick mark appears next to the command when the pane is shown.
4.1.2.7 Advance View
This command causes Manager to switch from its simplified view to advanced view mode. Manager automatically switches
to advanced view mode if an IP Office Standard Version configuration is loaded.
4.1.2.8 Hide Admin Tasks
This settings shows or hides the Admin Tasks List available when Manager has a IP Office Essential Edition - PARTNER®
Version or IP Office Essential Edition - Norstar Version configuration loaded.
4.1.2.9 Simplified View
If Manager has no configuration loaded, this command switches it from advanced view to simplified view.
Manager Manager 8.1
Manager
Page 128
15-601011 Issue 25l (11 February 2011)
Menu Bar Commands: Configuration Mode
4.1.2.10 TFTP Log
This command displays the TFTP Log window. This window shows TFTP traffic between Manager and devices that uses
TFTP to send and receive files. For example, the TFTP Log below shows an Avaya IP phone requesting and then being sent
its software files.
Manager Manager 8.1
Manager
Page 129
15-601011 Issue 25l (11 February 2011)
4.1.3 Tools Menu
4.1.3.1 Extension Renumber
This command allows the extension numbering of user extensions to be raised or lowered by a specified amount. The
command does not alter the extension number used for hunt groups but does adjust the extension numbers of hunt group
members.
4.1.3.2 Line Renumber
On external trunks Line appearance ID numbers can be assigned to each channel supported in order to allow that channel
or line to be associated with a Line Appearance button on phones that support button programming. By default all lines
are automatically numbered from 701 upwards when added to the system. This command allows the lines to be
renumbered from a different starting point.
4.1.3.3 Connect To
This option can be used to create Small Community Network connections between two systems, one being the system with
its configuration currently loaded in Manager, the other being selected from a discovery dialog.
·
! IMPORTANT
This process will require the systems to be rebooted.
1. With the configuration of the first system received from that system and displayed in Manager, clicking on
Tools | Connect To
or
2. A discovery menu is displayed and will list any other systems discovered.
3. Select the system to which an SCN connection is required.
4. Enter the login name and password for configuration access to that system.
5. Manager will switch to SCN management
6. Click
817
mode, displaying the configuration of both systems.
to save the new configuration back to each system.
4.1.3.4 SCN Service User Management
When managing multiple systems, it may be useful to create a common user name and password on all the systems for
configuration access. This tool can be used to create a new service user account, SCN_Admin, for configuration access.
This process requires you to have a user name and password for security configuration access to each of the systems.
Manager Manager 8.1
Manager
Page 130
15-601011 Issue 25l (11 February 2011)
Menu Bar Commands: Configuration Mode
1. Select Tools | SCN Service User Management.
· The option is not shown if a IP Office Essential Edition - PARTNER® Version or IP Office Essential Edition Norstar Version system configuration is loaded. If no configuration is load, and the option is not shown, select
View | Advanced View.
2. The Select IP Office menu will display the list of discoverable systems.
3. Select the systems for which you want to create a common configuration account. Click OK.
4. A user name and password for security configuration access to each system is request. Enter the values and click
OK. If the same values can be used for all systems enter those values, select Use above credentials for all
remaining, selected IPOs. If each system requires a different security user names and password, deselect Use
above credentials for all remaining, selected IPOs.
5. The systems will be listed and whether they already have an SCN_Admin account is shown.
6. To create the SCN_Admin account on each system and set the password for those account click on Create
Service User.
7. Enter the common password and click OK.
8. The password can be changed in future using the Change Password option.
9. Click Close.
4.1.3.5 Busy on Held Validation
Busy on Held is a user feature where, when the user has a call on hold, the system indicate the user as being busy to
any further calls.
The use of Busy on Held in conjunction with multiple call appearance buttons is deprecated. This command can be used
to identify those users who have multiple call appearance buttons and for whom Busy on Held is currently set.
When run, it shows a list of the users affected and if selected their Busy on Held setting will be switched off.
Manager Manager 8.1
Manager
Page 131
15-601011 Issue 25l (11 February 2011)
4.1.3.6 MSN/DID Configuration
This menu can be used to populate the Incoming Call Route table with a range of MSN or DID numbers.
In the example above, the customer has ten DID numbers starting at 01505392201 with the central office exchange
passing through 3 digits for each. Having selected the number of presentation digits (3), set the range (10) and selected
the first destination (201); clicking Add created the ten incoming call routes (201 to 210).
· MSN/DID
The first number in the set of MSN numbers for which you have subscribed. Note: If you require to find an exact match
between the MSN numbers and the destination numbers, enter a minus (-) sign before the first MSN number.
· Destination
Where incoming calls with matching digits should be routed. The drop-down list contains the extensions and groups on
the system.
· Line Group ID
Specifies the incoming line group ID of the trunks to which the DID routing is applied.
· Presentation Digits
Set to match the number of digits from the MSN/DID number that the central office exchange will actually present to
the system.
· Range
How many MSN or DID number routes to create in sequence using the selected MSN/DID and Destination as start
points. Only routing to user extensions is supported when creating a range of entries.
· Add
Adds the appropriate entries to the Incoming Call Route table using the value entered above.
· Delete
Removes a specific entry.
Manager Manager 8.1
Manager
Page 132
15-601011 Issue 25l (11 February 2011)
Menu Bar Commands: Configuration Mode
4.1.3.7 Print Button Labels
This option is only enabled if a version of DESI software is also installed on the same PC as Manager. It can then be used
when a system configuration is loaded in Manager.
DESI software can be obtained from the Avaya support web site (http://support.avaya.com) or from DESI (http//www.
desi.com). Currently, though all users are shown, only ETR, 1400 and 1600 phones are supported by DESI templates.
The text used on the labels:
· If a text label has been added in the user's Button Programming settings, that text label is passed to the DESI
application.
· Note that the DESI application cannot import non-ASCII characters and may render them incorrectly.
· Manager will display a warning if it estimates that the user's current text for some buttons may exceed the label
space of the phone type.
· If no text label has been set, the default label for the action currently assigned to the button is passed to the DESI
application.
· Once the labels are shown in the DESI application, the label text can be changed.
1. Load the configuration of the system for which you want to print button labels.
2. Select Tools and then Print Button Labels.
· Name / Extn
These are the user name and extension number details of the users in the system configuration currently
loaded in Manager.
· Phone Type
This field shows the type of phone, if known, that the user is currently associated with. The drop down can be
used to change the selection if required.
· Expansion Modules
If the phone type supports additional button modules, this drop down can be used to select the type and
number of button modules.
· Print Extn
This check box is used to select whether the phone button details should be included in the output passed to
the DESI software. These button will only be selectable if the user's current Phone Type is set to an ETR,
1400 and 1600 Series phone.
· Print BM1 / Print BM2 / Print BM3
These check boxes are used to select whether button module button details should be included in the output
passed to the DESI software. These button will only be selectable if the user's Expansion Modules is set to
the number of button modules.
3. Click Print DESI to transfer the information to the DESI application. Within DESI, edit the labels as required and
then print the labels.
Manager Manager 8.1
Manager
Page 133
15-601011 Issue 25l (11 February 2011)
4.2 Security Mode
These commands are available when the Manager is in security configuration mode.
4.2.1 Open Security Settings
This command displays the Select IP Office menu to select and load a system's security settings. This requires entry of a
user name and password with rights to access security settings of the selected system.
This behavior changes when configuration settings have already be received from a system using a Service User name and
password that also has security access rights for that system. In that case, the system's security settings are
automatically loaded without requiring name and password entry.
4.2.2 Close Security Settings
Close the currently open set of security settings received from a system without saving those settings.
4.2.3 Save Security Settings
Send edited security settings back to the system. Requires re-entry of a Service User name and password with access
rights for security settings.
4.2.4 Reset Security Settings
IP Office 4.1+: Reset the security settings of the selected syste, to defaults. Requires entry of a Service User name and
password with access rights for resetting the security settings. This option is not useable while a set of security
configuration settings is loaded.
The command File | Advanced | Erase Security Settings (Default)
configuration mode.
119
performs the same action from Manager
4.2.5 Preferences
See Preferences
106
in the Menu Bar Commands | Configuration Mode | File Menu section.
4.2.6 Exit
This command closes Manager.
4.2.7 Configuration
This command returns the Manager application to configuration mode.
Manager Manager 8.1
Manager
Page 134
15-601011 Issue 25l (11 February 2011)
Menu Bar Commands: Security Mode
4.3 Embedded File Management
These commands are available when the Manager is in embedded file management mode.
4.3.1 Open File Settings
Select a system and display the contents of its memory cards if any are present and in use.
4.3.2 Close File Settings
Close the current memory card contents listing without exiting embedded file management mode.
4.3.3 Refresh File Settings
This command can be used to request a file update from the system.
4.3.4 Upload File
This command can be used to select and upload a file to the memory card in the system.
4.3.5 Upload System Files
This command is available with IP500v2 systems. When this command is selected, Manager will upload the software files
for operation to the System SD card. It includes all Manager software, phone software and embedded voicemail prompts
not already present on the System SD card.
·
! WARNING
After this command is completed, the system is rebooted. This will end all calls and services in progress.
4.3.6 Backup System Files
This command is available with IP500v2 systems. When selected, Manager copies the folders and files from the System
SD card's /primary folder to its /backup folder. Any matching files and folders already present are overwritten. This
action can be included as part of the system's automatic daily backup process (System | System | Automatic Backup
Command 143 ).
4.3.7 Restore System Files
This command is available with IP500v2 systems.
When selected, Manager copies the folders and files from the System SD card's /backup folder to its /primary folder.
Any matching files and folders already present are overwritten.
·
! WARNING
After this command is completed, the system is rebooted. This will end all calls and services in progress.
4.3.8 Upgrade Binaries
This command is available for IP500v2 systems that have a system SD card and Option SD card installed.
When this command is selected, all files except config.cfg and keys.txt files in the Optional SD card's \primary folder
are copied to the System SD card.
·
! WARNING
After this command is completed, the system is rebooted. This will end all calls and services in progress.
4.3.9 Upgrade Configuration
This command is available for IP500v2 systems that have a system SD card and Option SD card installed.
When this command is selected, any config.cfg and keys.txt files in the Optional SD card's \primary folder are copied
to the System SD card.
·
! WARNING
After this command is completed, the system is rebooted. This will end all calls and services in progress.
Manager Manager 8.1
Manager
Page 135
15-601011 Issue 25l (11 February 2011)
4.3.10 Upload Voicemail Files
This command is useable with IP500 and IP406 V2 control units. When this command is selected, Manager copies the
prompts necessary for embedded voicemail to the memory card.
For IP500v2 control units, use Upload System Files
135 .
4.3.11 Upload Phone Files
This command is available for IP500 and IP406 V2 control units. When this command is selected, Manager copies the
software files relating to phone firmware to the memory card.
For IP500v2 control units, use Upload System Files
135 .
4.3.12 Copy System Card
This command is available for systems that have a system SD card and Option SD card. When this command is selected,
the system will copy the folders and files on its System SD card to the Optional SD card. Any matching files and folders
already present on the Optional SD card are overwritten.
This process takes at least 90 minutes and can take longer.
4.3.13 Configuration
This command will exit Embedded File Management and return Manager to configuration editing mode.
Manager Manager 8.1
Manager
Page 136
15-601011 Issue 25l (11 February 2011)
Chapter 5.
Configuration Settings
Manager Manager 8.1
Manager
Page 137
15-601011 Issue 25l (11 February 2011)
5. Configuration Settings
This following sections detail the various configuration settings provided for different entry types within the system
configuration. Depending on the type and locale of the system some settings and tabs may be hidden as they are not
applicable. Other settings may be grayed out. This indicates that the setting is either for information only or that another
setting needs to be enabled first.
The different entry types are:
·
BOOTP 140
Manager settings for the support of systems requesting software.
·
Operator 141
Manager settings for the editing of configuration settings from pre-IP Office 3.2 systems.
·
System 142
Overall settings for the data and telephony operation of the system.
·
Line 185
Settings for trunks and trunk channels within the system including VoIP trunks.
·
Control Unit 250
Information summary of the control and expansion units in the system.
·
Extension 251
Settings for extension ports including IP extensions.
·
User 262
Settings for system users. They may or may not be associated with an extension.
·
Hunt Group 304
Collections of users to which calls can be directed for answer by any one of those users.
·
Short Code 330
These are numbers which when dialed trigger specific features or are translated for external dialing.
·
Service 331
Configuration settings such as user names and passwords needed for connections to data services such as the Internet.
·
RAS 340
Remote Access Service settings for connecting incoming data calls.
·
Incoming Call Route 344
Entries here are used to match incoming call details to destinations on the system.
·
WAN Port 351
Configuration settings for the WAN ports provided on some units.
·
Directory 358
External names and numbers. Used for matching names to incoming calls and for dialing from user applications.
·
Time Profile 360
Used to control when various functions are active.
·
Firewall Profile 363
Use to control the types of data traffic that can cross into or out of the system.
·
IP Route 368
These entries are used to determine where data traffic on the system LAN and WAN interfaces should be routed.
Manager Manager 8.1
Manager
Page 138
15-601011 Issue 25l (11 February 2011)
Configuration Settings:
·
Least Cost Routing 370
On pre-4.0 systems LCR is used to rerouted or block outgoing external calls. For IP Office 4.0+ this has been replace by
ARS.
·
Account Code 375
Used for call logging and to control the dialing of certain numbers.
·
License 378
License keys are used to enable system features and applications.
·
Tunnel 380
Used to created IPSec and L2TP data tunnels.
·
Logical LAN 385
Used to allow two subnets to be run and routed on the same physical LAN.
·
Wireless 386
Used to provide wireless services on the Small Office Edition.
·
User Rights 389
Provide templates to control which settings users can change.
·
Auto Attendant 400
Used when an Avaya memory card is installed in the control unit (Small Office Edition, IP406 V2, IP500 or IP500v2
system).
·
ARS 407
Automatic Route Selection is used by to control outgoing external calls.
·
Authorization Codes 404
Authorization codes are similar to account codes. However, unlike account codes which are useable by any user, each
authorization code is only useable by a specific user or users associated with a specific set of user rights.
·
E911 System 421
Available of US systems to support E911 services.
Manager Manager 8.1
Manager
Page 139
15-601011 Issue 25l (11 February 2011)
5.1 BOOTP
BOOTP is protocol used by devices to request software when restarting. It is used when upgrading the control unit
within a system or when the core software within the control unit has been erased. When running, Manager can
respond to BOOTP requests and, if it finds a matching BOOTP entry for the system, provide the software file
indicated by that entry.
BOOTP entries are not part of a system's configuration settings; instead they are saved on the Manager PC. Normally
Manager automatically creates a BOOTP entry for each system with which it has communicated, up to a maximum of 50
entries. However BOOTP entries can be added and edited manually when necessary.
· File Location
The location from which Manager provides files in response to BOOTP is its binaries directory. This can be changed
using File | Change Working Directory 105 or File | Preferences | Directories 107 . This directory is also the
directory used by Manager when providing files by TFTP.
· Disabling BOOTP
Manager can be disabled from providing BOOTP support for any systems. Select File | Preferences | Preferences |
Enable BOOTP and TFTP Server 106 .
Settings
· Enabled: Default = Enabled
If unticked, BOOTP support for the matching system from this Manager PC is disabled.
· System Name
This field is not changeable. It shows the system name.
· MAC Address
The MAC address of the system's control unit. The address can be obtained and or verified in a number of ways:
· When a system's configuration settings are loaded into Manager, it is shown as the Serial Number on the Unit
form. On defaulted systems, it is also used as the system name.
250
· If the system is requesting software, the MAC address is shown as part of the request in the status bar at the base of
the Manager screen.
· If the system can be pinged, it may be possible to obtain its MAC address using the command arp -a <ip address>.
· IP Address
The IP address of the system's LAN1.
· Filename
The name of the .bin software file used by that type of control unit. For full details refer to the Manager Installation
Manual. To be transferred to the system this file must exist in the Manager applications Working Directory.
· Time Offset: Default = 0.
In addition to performing BOOTP support for systems the Manager application can also act as a time server (RFC868).
This field sets the offset between the time on the PC running Manager and the time sent to the system in response to its
time requests. The field is not used if a specific Time Server IP Address is set through the System form in the system's
configuration settings.
· Manager can be disabled from acting as an Internet Time (RFC868) server. Select File | Preferences | Preferences
106 and untick Enable time server.
Manager Manager 8.1
Manager
Page 140
15-601011 Issue 25l (11 February 2011)
Configuration Settings: BOOTP
5.2 Operator
Operator entries are not part of a system's configuration settings. They are used when a pre-3.2 IP Office
configuration is loaded to control what parts of a configuration can be edited.
The table below lists the settings for the default operators provided.
Operator
View
Edit
New
Delete Configuration Entry Types
Administrato
r
All configuration entries.
Manager
View all. Other actions Extension, User, Hunt Group, Short Code,
Service, RAS, Incoming Call Route, Directory, Time Profile, Firewall
Profile, IP Route, Least Cost Route, Account Code, ARS.
Operator
View all configuration entries. Edit all except System, Line, Control Unit
and Authorization Codes.
If when receiving a configuration from a pre-3.2 system an invalid operator is specified, the settings will be loaded using
the Guest operator. This additional operator allows a read-only view.
Manager Manager 8.1
Manager
Page 141
15-601011 Issue 25l (11 February 2011)
5.3 System
There is only one System entry for each system. When working in SCN Management 817 mode, clicking on the
System icon for a particular system displays a system inventory 825 page for that system.
The following tabs are part of the System form:
· System 143
General settings for the system.
· LAN1 148
Network settings for the RJ45 Ethernet LAN port on the control unit. Includes DHCP and RIP settings.
· LAN2 155
Network settings for the RJ45 Ethernet WAN port on the control unit. LAN2 is not supported by all control units.
· On the Small Office Edition, IP500 and IP500v2 control units the LAN2 settings are used for the RJ45 Ethernet port
labeled WAN.
· On the IP412 control units LAN2 settings are used for the RJ45 ethernet port labeled LAN2.
· For IP406 V2 control units running IP Office 4.1+, the RJ45 LAN port 8 can be selected to act be LAN2 if required.
· DNS 156
Specify the Domain Name Server addresses to use for address resolution.
· Voicemail 157
Details the type and location of the voicemail server.
· Telephony 160
System-wide telephony settings.
· H.323 Gatekeeper
Settings used for VoIP end points registering with the system and for DiffServ QoS settings applied to VoIP traffic. This
tab is only shown on pre-4.0 systems. For IP Office 4.0+, separate LAN1 and LAN2 VoIP settings are shown on the
LAN1 and LAN2 tabs respectively.
· LDAP 169
Settings to allow the system to include Lightweight Directory Access Protocol database records in its directory.
· System Events 172
Simple Network Management Protocol (SNMP), email (SMTP), and Syslog settings for the sending of system events.
· Twinning 177
System wide controls for the use of Mobile Twinning.
· SMDR 179
Settings for the sending of call records to a specified IP address.
· VCM 181
This form allows adjustment of the echo control applied by VCM cards.
· CCR 184
This form is used for settings specific to the Customer Call Reporter (CCR) application.
Manager Manager 8.1
Manager
Page 142
15-601011 Issue 25l (11 February 2011)
Configuration Settings: System
5.3.1 System
System | System
Control Unit
SOE
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
Software Level 1.0+.
Mergeable
Changes to Locale, License Server IP Address and Favor RIP Routes over Static Routes require a
reboot..
· Name: Default: = System MAC Address.
A name to identify this system. This is typically used to identify the configuration by the location or customer's company
name. Some features such as Gatekeeper require the system to have a name. This field is case sensitive and within any
network of systems must be unique. Do not use punctuation characters such as #, ?, /, -,. and ,.
· Contact Information: Default = Blank. Software level = 4.1+.
This field is only be edited by service user with administrator rights. If Contact Information is entered, it will set the
system under 'special control'.
· If the contact information is set using a standalone version of Manager, warnings that "This configuration is under
special control" are given when the configuration is opened again. This can be used to warn other users of Manager
that the system is being monitored for some specific reason and provide them with contact details of the person
doing that monitoring. See Loading a Configuration 55 .
· Locale
This setting sets default telephony and language settings based on the selection. It also sets various external line
settings and so must be set correctly to ensure correct operation of the system. See Supported Country and Locale
Settings 844 . For individual users the system settings can be overridden through their own locale setting (User | User |
Locale).
· When the system routes a call to the voicemail server it indicates the locale for which matching prompts should be
provided if available. The locale sent to the voicemail server by the system is determined as follows:
Locale Source
Usage
Short Code
The short code locale, if set, is used if the call is routed to voicemail using the short
code.
System
If no user or incoming call route locale is set system locale is used unless overridden by
a short code locale.
Incoming Call Route
The incoming call route locale, if set, is used if caller is external.
User
The user locale, if set, is used if the caller is internal.
· Customize Locale Settings: Software level = IP Office 4.0 Q2 2007 Maintenance Release +
The Customize locale matches the Saudi Arabia 885 locale but with the following additional controls:
· Tone Plan: Default = Tone Plan 1
The tone plan control tones and ringing patterns. The options are:
· Tone Plan 1: United States
895 .
· Tone Plan 2: United Kingdom
· Tone Plan 3: France
863 .
· Tone Plan 4: Germany
· Tone Plan 5: Spain
894 .
865 .
888 .
· CLI Type: Default = FSK V23
This should match the method CLI signalling being received by the system.
· Busy Tone Detection: Default = Off.
Enables or disables the use of busy tone detection for call clearing. This is a system wide setting.
· Password: Default = password. Software level = 2.1 to 3.1.
A password for controlling access to the operation of the Control Unit. This is required to upgrade and reboot and to
send or receive configurations from the Control Unit. This is a required option and a prompt is given if left blank. For IP
Office 3.2+ systems this setting has become part of the security settings.
· Monitor Password: Default = blank. Software level = 2.1 to 3.1.
This password is used by the Monitor and Call Status applications to allow communication with the main unit. If left
blank these applications will use the System Password above. For IP Office 3.2+ systems, this setting has become part
of the security settings.
Manager Manager 8.1
Manager
Page 143
15-601011 Issue 25l (11 February 2011)
· Time Offset: Default = 00:00. Software level = 1.0 to 6.0.
This setting can be used if the system is in a different time zone from its time server. For example, if the system is 5
hours behind the time server, this field should be configured with -5:00 to make the adjustment. The time offset can be
adjusted in 15 minute increments. Note: If the time server is a Manager PC, the adjustment can also be done through
the Manager BOOTP entry for the system.
· TFTP Server IP Address: Default = 0.0.0.0 (Broadcast).
For Avaya IP phones using DHCP, the address set here is used for their TFTP requests for software and settings files.
· While running, Manager can act as a TFTP server and provides files from its configured binaries directory
Manager can be disabled from doing TFTP through the Enable BootP and TFTP Servers 106 command.
107 .
· On systems with an Avaya memory card (Small Office Edition, IP406 V2, IP500 and IP500v2), the LAN1 IP Address
can be entered to specify that memory card as the TFTP file source. The files required for download must be
transferred onto the card using either TFTP from the PC command line (see File Writer IP Address below) or
through Embedded File Management 119 .
· 1100, 1200, 1600 and 9600 Series IP phones do not support TFTP and require an HTTP Server IP Address (see
below) to be specified.
· IP Office Release 5.0+: This address is used in DHCP responses if the Phone File Server Type is set to Custom.
· HTTP Server IP Address: Default = 0.0.0.0 (Disabled). Software level = 4.2+.
If an address is entered here, Avaya IP phones using DHCP will use that address to request software and settings files.
The files for download should be placed in the HTTP server's root directory.
· IP Office 4.2: Using the Embedded Voicemail memory card is also supported for HTTP file. This is done by setting
the TFTP Server IP Address and HTTP Server IP Address to match the control unit IP address. This is
supported for up to 50 IP phones total.
· IP Office 4.2 Q4 2008 maintenance release: HTTP-TFTP Relay is support using Manager as the TFTP server. This is
done by setting the TFTP Server IP Address to the address of the Manager PC and the HTTP Server IP Address
to the control unit IP address. This method is supported for up to 5 IP phones total.
· IP Office Release 5.0+: This address is used in DHCP responses if the Phone File Server Type is set to Custom.
· Phone File Server Type: Default = Custom. Software level = 5.0+.
For IP (H323 and SIP) phones using the system as their DHCP server, the DHCP response can include the address a file
server from which the phone should request files. The setting of this field control which address in used in the DHCP
response.
Phone File
Server Type
DHCP Response uses...
HTTP Source
TFTP Source
Custom
HTTP Server IP Address
TFTP Server IP Address
Memory Card
LAN IP Address
LAN IP Address
Manager
LAN IP Address
Manager PC IP Address
· Custom
The system will respond to all HTTP file requests from H323 phones. The H323 phone DHCP response contains the
TFTP Address from the TFTP Server IP Address above and the HTTP Address from the HTTP Server IP Address
above.
· Memory Card
The system will respond to all HTTP file requests from H323 phones using files from the systems embedded
memory card. The DHCP response for H323 phones contains the LAN address of the system for both TFTP and HTTP
Address.
· Manager
The system will forward any H323 phone file request to the configured Manager PC IP address below. HTTP-TFTP
relay is used for HTTP requests. The DHCP response for H323 phones contains the LAN address of the system for
the HTTP Address.
· Manager PC IP Address: Default = 0.0.0.0 (Broadcast). Software level = 5.0+.
This address is used when the Phone File Server Type is set to Manager.
· Avaya HTTP Clients Only: Default = On. Software level = 5.0+.
If selected, the system will only respond to HTTP requests from sources it identifies as another system, an Avaya phone
or application.
· Enable SoftPhone HTTP Provisioning: Default = Off. Software level = 6.0+.
This option must be enabled if the Avaya IP Office SoftPhone is being supported.
· Automatic Backup Command: Default = On. Software level = 6.1+.
This command is available with IP500v2 systems. When selected, as part of its daily backup process, the system
automatically copies the folders and files from the System SD card's /primary folder to its /backup folder. Any
matching files and folders already present in the /backup folder are overwritten.
Manager Manager 8.1
Manager
Page 144
15-601011 Issue 25l (11 February 2011)
Configuration Settings: System
· Branch Prefix: Default = Blank, Range = 0 to 999999999. Software level = 4.1+.
Used to identify the system within an Avaya SIP for Branch network linked via an SES server. The branch prefixes of
each systems within the network must unique and must not overlap. For example 85, 861 and 862 are okay, but 86 and
861 overlap.
· Local Number Length: Default = Blank (Off), Range = Blank (Off) or 3 to 9. Software level = 4.1+.
Set the default length for extension numbers for extensions, users and hunt groups. Entry of an extension number of a
different length will cause an error warning within Manager.This field is intended for systems being used in an Avaya SIP
for Branch network linked via an SES server, where fixed extension lengths must be used. Note that the Branch Prefix
and the Local Number Length must not exceed 15 digits.
· Time Server IP Address: Default = 0.0.0.0 (Default), Software level = 1.0 to 6.0.
For pre-IP Office Release 6.1 systems, the time is either set manually (see Date and Time 727 ) or obtained using Time
protocol (RFC868) requests. Both the Voicemail Pro server and the Manager application can respond to Time requests.
Entering 0.0.0.1 disables requesting time server updates. The system makes a request to the specified address
following a reboot and every 8 hours afterwards.
· This setting is replaced for IP Office Release 6.1 systems by the Time Setting Config Source and Time Settings
detailed below.
· 0.0.0.0 means default operation. In this mode, following a reboot the control unit will send out a time request on its
LAN interfaces. It first makes the request to the Voicemail Server IP address in its configuration if set and, if it
receives no reply, it then makes a broadcast request.
· If you are running Manager when the voicemail server starts, voicemail does not start as a time server. It is therefore
recommended that you have no copy of Manager running when you start or restart the voicemail server. Manager can
be disabled from acting as a RFC868 time server by deselecting the Enable Time Server option (File | Preferences
| Edit | Preferences 106 ).
· Time Setting Config Source: Default = Voicemail Pro/Manager
The time is either set manually (see Date and Time 727 ), obtained using Time protocol (RFC868) requests or obtained
using Network Time Protocol (RFC958) request. This field is used to select which method is used and to apply ancillary
settings based on the selected method.
· None
Set the system to not make any time requests. The system time and date needs to be set using a phone with
System Phone Rights (User | User 264 ). The system can then automatically apply daylight saving settings to the
manually set time.
· Automatic DST: Default = Off
If enabled, the system will apply daylight saving time (DST) changes to the displayed local time. Manager will
initially apply default values based on the system locale. However these should be checked to ensure that they
match the expected values and any recent changes to local DST requirements.
· DST Offset
Set the amount by by which the time should be changed when DST is applied of removed.
· Local Time to Go Forward
Set the time at which the DST Offset should be added to the local time when DST is started.
· Local Time to Go Back
Set the time at which the DST offset should be removed from the local time when DST is removed.
· Clock Forward/Back Settings
This drop down can be used to set the paired dates for the start (go forward) and end (go back) of the
daylight saving. To add a pair of dates, select <Add New Entry> in the drop down and click Edit.
· Select Clock Forward and double clicking on the required date. Then select Clock Backward and
double click on the required date.
· If necessary multiple pairs can be created to cover a number of years.
· Voicemail Pro/Manager
Both the Voicemail Pro service and the Manager program can act as RFC868 Time servers for the system. Use of
other RFC868 server sources is not supported. They provide both the UTC time value and the local time as set on
the PC. The system makes a request to the specified address following a reboot and every 8 hours afterwards.
· IP Address: Default = 0.0.0.0 (Broadcast)
The address to which the RFC868 request is sent. 0.0.0.0 means default operation. In this mode, following
a reboot the control unit will send out a time request on its LAN interfaces. It first makes the request to
the Voicemail Server IP address in its configuration if set and, if it receives no reply, it then makes a
broadcast request.
· Time Offset: Default = 00:00
This value is not normally set as any time changes, including daylight saving changes, that occur on the PC
will be matched by the system.
· If you are running Manager when the voicemail server starts, voicemail does not start as a time server. It is
therefore recommended that you have no copy of Manager running when you start or restart the voicemail
server. Manager can be disabled from acting as a RFC868 time server by deselecting the Enable Time Server
option (File | Preferences | Edit | Preferences 106 ).
Manager Manager 8.1
Manager
Page 145
15-601011 Issue 25l (11 February 2011)
· SNTP (Release 6.1+)
Use a list of SNTP servers to obtain the UTC time. The entries in the list are used one at a time in order until there
is a response. The system makes a request to the specified addresses following a reboot and every hour
afterwards.
· Time Server Address: Default = Blank
Enter a list of IP addresses or names for the SNTP servers. Separate each entry with a space. The use of
broadcast addresses is not supported. The list is used in order of the entries until a response is received.
· Time Zone: Default = Match to system Locale
The value is defaulted to match the system locale.
· Local Time Offset from UTC: Default = 00:00
This setting is used to set the local time difference from the UTC time value provided by an SNTP server. For
example, if the system is 5 hours behind UTC, this field should be configured with -5:00 to make the
adjustment. The time offset can be adjusted in 15 minute increments. If also using the daylight time saving
settings below, use this offset to set the non-DST local time.
· Automatic DST: Default = Off
If enabled, the system will apply daylight saving time (DST) changes to the displayed local time. Manager will
initially apply default values based on the system locale. However these should be checked to ensure that they
match the expected values and any recent changes to local DST requirements.
· DST Offset
Set the amount by by which the time should be changed when DST is applied of removed.
· Local Time to Go Forward
Set the time at which the DST Offset should be added to the local time when DST is started.
· Local Time to Go Back
Set the time at which the DST offset should be removed from the local time when DST is removed.
· Clock Forward/Back Settings
This drop down can be used to set the paired dates for the start (go forward) and end (go back) of the
daylight saving. To add a pair of dates, select <Add New Entry> in the drop down and click Edit.
· Select Clock Forward and double clicking on the required date. Then select Clock Backward and
double click on the required date.
· If necessary multiple pairs can be created to cover a number of years.
· File Writer IP Address: Default = 0.0.0.0 (Disabled)
On systems with an Avaya memory card (Small Office Edition, IP406 V2, IP500 and IP500v2), this field sets the address
of the PC allowed to send files to the memory card in their PCMCIA or CF TII slot.
· License Server IP Address: Default = 255.255.255.255
This is the IP address of the server providing license key validation for the system. The serial number of the Feature Key
dongle at that address must match the serial number used to generate the licenses in the system's configuration. See
License 378 for more details.
· For parallel and USB Feature Key dongles this address should be the IP address of a PC running the Feature Key
server software. Note that separate systems cannot use the same Feature Key server for license validation, nor can a
system validate its licenses against more than one address.
· For a serial port Feature Key dongle, the address should be set to 0.0.0.0.
· For IP500 and IP500v2 systems, this field is hidden as those systems must use a Feature Key dongle inserted into the
control unit.
· Dongle Serial Number
This field is for information only. It shows the serial number of the feature key dongle against which the system last
validated its licenses. Local is shown for a serial port or Smart Card feature key plugged directly into the control unit.
Remote is shown for a parallel or USB feature key connected to a feature Key Server PC. For IP400 and IP500 systems,
the serial number is also printed on the feature key dongle and prefixed with SN. For IP500v2 systems, the serial
number is printed on the System SD card and prefixed with FK.
· AVPP IP Address: Default = 0.0.0.0 (Disabled)
Where Avaya 3600 Series SpectraLink wireless handsets are being used with the system, this field is used to specify the
IP address of the Avaya Voice Priority Processor (AVPP).
· Conferencing Center URL: Default = Blank (Disabled).
This is the root URL of the web server being used to support Conferencing Center, for example http://server/. This
address is then used by the Phone Manager and SoftConsole applications to launch Conferencing Center functions. For
Phone Manager, setting this value enables use of the join conference controls.
· DSS Status:
This setting has been moved to the System | Telephony | Telephony
160
sub-tab.
· Beep on Listen: Default = On (USA)/On (Rest of World)
This setting has been moved to the System | Telephony | Tones & Music
Manager Manager 8.1
Manager
163
sub-tab.
Page 146
15-601011 Issue 25l (11 February 2011)
Configuration Settings: System
· Hide auto record: Default = On (USA)/Off (Rest of World)
During call recording by Voicemail Pro, some Avaya phones display REC or similar to show that the call is being
recorded. When on, Hide auto record suppresses this recording indication.
· Favour RIP Routes over Static Routes: Default = Off
RIP 369 can be enabled on the system LAN1 148 and LAN2 155 interfaces, and on specific Services 331 . When this setting
is on, the RIP route to a destination overrides any static route to the same destination in the system's IP Routes 368 ,
regardless of the RIP route's metric. The only exception is RIP routes with a metric of 16 which are always ignored.
Note: If a previously learnt RIP route fails, the system applies a metric of 16 five minutes after the failure. When off,
any RIP route to a destination for which a static route has been configured is ignored.
Manager Manager 8.1
Manager
Page 147
15-601011 Issue 25l (11 February 2011)
5.3.2 LAN1
This tab is used to configure the behavior of the services provided by the system LAN's. Depending in the control unit, up
to 2 LAN's (LAN1 and LAN2) can be configured.
Depending on the type of control unit, the relationship between the physical RJ45 Ethernet ports and LAN1 and LAN2
within the system configuration varies as follows:
· IP500/IP500v2
The control unit has 2 RJ45 Ethernet ports, marked as LAN and WAN. These form a full-duplex managed layer-3
switch. Within the system configuration, the physical LAN port is LAN1, the physical WAN port is LAN2.
· IP460 V2
The control unit has 8 RJ45 Ethernet ports marked as LAN 1 to 8. These form a full-duplex unmanaged layer-2 LAN
switch. Ports are auto-MDI/MDIX. Within the system configuration the physical LAN ports are LAN1.
· For IP Office 4.1+, port 8 can be configured to act as LAN2 using the Use Port 8 as LAN2 option on the LAN1
LAN Settings tab.
· IP412
The control unit has 2 RJ45 Ethernet ports marked as LAN 1 to 2. These form a half-duplex managed layer-3
switch. Both ports are fixed MDI crossover ports. Within the system configuration, physical port 1 is LAN1, physical
port 2 is LAN2.
· Small Office Edition
The control unit has 4 RJ45 Ethernet ports marked LAN 1 to 4. These form a full-duplex unmanaged layer-2 switch.
An addition RJ45 Ethernet socket marked as WAN exists. With the LAN ports this acts as a managed layer-3 switch.
Within the system configuration, the physical LAN ports are LAN1, the physical WAN port is LAN2.
Manager Manager 8.1
Manager
Page 148
15-601011 Issue 25l (11 February 2011)
Configuration Settings: System
5.3.2.1 LAN Settings
System | LAN1 | LAN Settings
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· IP Address: Default = 192.168.42.1 or DHCP client. See Default Settings 65 .
This is the IP address of the Control Unit on LAN1. If the control unit is also acting as a DHCP server on LAN1 then this
address is the starting address of the DHCP address range.
· IP Mask: Default = 255.255.255.0 or DHCP client. See Default Settings
This is the IP subnet mask used with the IP address.
65
.
· Use Port 8 as LAN2: Default = Off. Software level = 4.1+.
This option is provided for IP406 V2 control units with IP Office 4.1 or higher software only. When selected, LAN port 8
on the control unit acts as LAN2 155 for the control unit. Note that this setting is retained by the Manager even if the
system is defaulted. To change the setting, the value in the configuration should be changed and the configuration sent
back to the system for an immediate reboot.
· Primary Trans. IP Address: Default = 0.0.0.0 (Disabled)
This setting is only available on control units that support a LAN2. Any incoming IP packets without a service or session
are translated to this address if set.
· RIP Mode: Default = None
Routing Information Protocol (RIP) 369 is a method by which network routers can exchange information about device
locations and routes. Routes learnt using RIP are known as 'dynamic routes'. The system also supports 'static routes'
though its IP Route 367 entries.
· None
The LAN does not listen to or send RIP messages.
· Listen Only (Passive)
Listen to RIP-1 and RIP-2 messages in order to learn RIP routes on the network.
· RIP1
Listen to RIP-1 and RIP-2 messages and send RIP-1 responses as a sub-network broadcast.
· RIP2 Broadcast (RIP1 Compatibility)
Listen to RIP-1 and RIP-2 messages and send RIP-2 responses as a sub-network broadcast.
· RIP2 Multicast
Listen to RIP-1 and RIP-2 messages and send RIP-2 responses to the RIP-2 multicast address.
· Enable NAT: Default = Off
This setting controls whether NAT 798 should be used for IP traffic from LAN1 to LAN2.It is only available on Small Office
Edition, IP412, IP500 and IP500v2 systems. This setting should not be used on the same LAN interface as a connected
WAN3 expansion module.
· Number of DHCP IP Addresses: Default = 200 or DHCP client. See Default Settings
This defines the number of sequential IP addresses available for DHCP clients.
65
, Range = 1 to 999.
· DHCP Mode: Default = DHCP Client. See Default Settings 65 .
This controls the control unit's DHCP mode for LAN1. When doing DHCP; LAN devices are allocated addresses from the
bottom of the available address range upwards, Dial In users are allocated addresses from the top of the available
range downwards. If the control unit is acting as a DHCP server on LAN1 and LAN2, Dial in users are allocated their
address from the LAN1 pool of addresses first.
· Server
When this option is selected, the system will act as a DHCP Server on LAN1, allocating address to other devices on
the network and to PPP Dial in users.
· Disabled
When this option is selected, the system will not use DHCP. It will not act as a DHCP server and it will not request an
IP address from a DHCP server on this LAN.
· Dial In
When this option is selected, the system will allocate DHCP addresses to PPP Dial In users only. On IP500/IP500v2
systems using DHCP pools, only addresses from a pool on the same subnet as the system's own LAN address will be
used.
· Client
When this option is selected, the system will request its IP Address and IP Mask from a DHCP server on the LAN.
· Advanced: Software level = 4.2+ (IP500/IP500v2 only).
IP500/IP500v2 control units can be configured with a number of DHCP pools from which the system can then issue
addresses. See DHCP Pools 154 .
Manager Manager 8.1
Manager
Page 149
15-601011 Issue 25l (11 February 2011)
5.3.2.2 VoIP
These settings are only shown on IP Office 4.0+ systems. On pre-4.0 systems the H.323 settings were located on a
separate System | H.323 Gatekeeper tab for the whole system.
System | LAN1 | VoIP
Control Unit
SOE
, IP403
Software Level
4.0+.
Mergeable
Pre-3.2
, 3.2+
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· H323 Gatekeeper Enable: Default = On
This settings enables gatekeeper operation.
· SIP Trunks Enable: Default = On
This settings enables support of SIP trunks. It also requires entry of SIP Trunk Channels licenses.
· SIP Registrar Enable: Default = On. Software level = 5.0+.
This setting enables support for SIP extensions.When selected, the SIP Endpoints
require IP End Point license.
155
tab if visible. These are also
· H323 Auto-create Extn: Default = On
When this option is on, an extension entry is automatically created for H.323 phones registering themselves with the
system as their gatekeeper. SIP Extensions use a separate setting on the SIP Endpoints 155 tab.
· H323 Auto-create User: Default = Off
When this option is on and H323 Auto-create Extn is also on, when a new H.323 extension is created a matching user
record is also created.
· Enable RTCP Monitor On Port 5005: Default = On. Software level = 5.0+.
For 1600, 4600, 5600 and 9600 Series H323 phones, the system can collect VoIP QoS (Quality of Service) data from
the phones. For other phones, including non-IP phones, it can collect QoS data for calls if they use a VCM channel. The
QoS data collected by the system is displayed by the System Status Application.
· This setting is mergeable. However it only affects H323 phones when the register with the system. therefore any
change to this setting requires H323 phones that have already been registered to be rebooted. Avaya H323 phones
can be remotely rebooted using the System Status Application.
· The QoS data collected includes: RTP IP Address, Codec, Connection Type, Round Trip Delay, Receive Jitter,
Receive Packet Loss.
· This setting is not the same as the RTCPMON option within Avaya H323 phone settings. The system does not
support the RTCPMON option.
· RTP Port Number Range: Software level = 3.0+.
For each VoIP call, a receive port for incoming Real Time Protocol (RTP) traffic is selected from a defined range of
possible ports, using the even numbers in that range. The Real Time Control Protocol (RTCP) traffic for the same call
uses the RTP port number plus 1, that is the odd numbers. For control units and Avaya H.323 IP phones, the default
port range used is 49152 to 53246. On some installations, it may be a requirement to change or restrict the port range
used. It is recommended that only port numbers between 49152 and 65535 are used, that being the range defined by
the Internet Assigned Numbers Authority (IANA) for dynamic usage.
· Port Range (minimum): Default = 49152. Range = 1024 to 64510.
This sets the lower limit for the RTP port numbers used by the system.
· Port Range (maximum): Default = 53246. Range = 2048 to 65534.
This sets the upper limit for the RTP port numbers used by the system. The gap between the minimum and the
maximum must be at least 1024.
· DiffServ Settings
When transporting voice over low speed links it is possible for normal data packets (1500 byte packets) to prevent or
delay voice packets (typically 67 or 31 bytes) from getting across the link. This can cause unacceptable speech quality.
Therefore it is important that all traffic routers and switches in a network to have some form of Quality of Service
mechanism (QoS). QoS routers are essential to ensure low speech latency and to maintain sufficient audible quality.
· The system supports the DiffServ (RFC2474) QoS mechanism. This uses a Type of Service (ToS) field in the IP
packet header. The system uses this field to prioritize voice and voice signaling packets on its WAN interfaces.
Note that the system does not perform QoS for its Ethernet ports including the WAN Ethernet port on the Small
Office Edition.
· The hex and decimal entry fields for the following values are linked, the hex value being equal to the decimal
multiplied by 4.
· DSCP (Hex): Default = B8 (Hex)/46 (decimal), Range = 00 to FC (Hex)/0 to 63 (decimal)
The DiffServ Code Point (DSCP) setting applied to VoIP calls. For correct operation, especially over WAN links, the
same value should be set at both ends.
Manager Manager 8.1
Manager
Page 150
15-601011 Issue 25l (11 February 2011)
Configuration Settings: System
· DSCP Mask (Hex): Default = FC (Hex)/63 (decimal), Range = 00 to FC (Hex)/0 to 63 (decimal)
Allows a mask to be applied to packets for the DSCP value.
· SIG DSCP (Hex): Default = 88 (Hex)/34 (decimal), Range = 00 to FC (Hex)/0 to 63 (decimal)
This setting is used to prioritize VoIP call signaling.
· DHCP Settings
· Primary Site Specific Option Number (SSON): Default = 176, Range = 128 to 254.
A site specific option number (SSON) is used as part of DHCP to request additional information. For system it is
used by Avaya IP Phones being supported by DHCP. 176 is the default SSON used by 4600 Series and 5600 Series
IP phones.
· Secondary Site Specific Option Number (SSON): Default = 242, Range = 128 to 254.
Similar to the primary SSON. 242 is the default SSON used by 1600 and 9600 Series IP phones requesting
installation settings via DHCP.
· VLAN: Default = Not present. Software level = Release 5+.
This option is applied to H323 phones using the system for DHCP support. If set to Disabled, the L2Q value
indicated to phones in the DHCP response is 2 (disabled). If set to Not Present, no L2Q value is included in the
DHCP response.
· 1100 Voice VLAN Site Specific Option Number (SSON): Default = 232. Software level = 6.1
This is the SSON used for responses to 1100/1200 Series phones using the system for DHCP.
· 1100 Voice VLAN IDs: Default = blank. Software level = 6.1
For 1100/1200 phone being supported by DHCP, this field sets the VLAN ID that should be provided if necessary.
Multiple IDs (up to 10) can be added, each separated by a + sign.
· RTP keepalives: Software level = 6.1+
These settings can be used with SIP trunks associated with the LAN through their Use Network Topology Info
setting (Line | Transport 236 ). For some scenarios, with frequent call forwarding on the same SIP trunk, speech path
may be lost during the connection. The use of periodic keepalive packets may prevent the issue.
· Scope: Default = Disabled
Select whether the sending of keepalive packets should be disabled or sent for RTP or for both RTP and RTCP.
· Periodic timeout: Default = 0 (Off), Range = 0 to 180 seconds.
Sets how long the system will wait before sending a keepalive if no other packets of the select SCOPE are seen.
· Initial keepalives: Default = Disabled.
If enabled, keepalives can also been sent during the initial connection setup.
Manager Manager 8.1
Manager
Page 151
15-601011 Issue 25l (11 February 2011)
5.3.2.3 Network Topology
These settings are used for SIP trunk connections from the LAN. Use of SIP requires entry of SIP Trunk Channels licenses.
For further details of system SIP operation refer to the SIP Line 230 section.
STUN (Simple Traversal of UDP through NAT) is a mechanism used with UDP SIP to overcome the effect of NAT firewalls.
Test SIP packets are sent to a STUN server. The STUN server replies and includes copies of the packets it received in the
reply. By comparing the packet sent to the STUN server and the copies of the packets it received, it is possible to
determine the type of NAT firewall and to then modify future SIP packets to overcome negative effects of NAT.
The use of STUN is unnecessary if the SIP ITSP uses a Session Border Controller (SBC).
System | LAN1 | Network Topology Settings
Control Unit
SOE
, IP403
Software Level
4.0+.
Mergeable
Pre-3.2
, 3.2+
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
The following fields can be completed either manually or the system can attempt to automatically discover the appropriate
values. To complete the fields automatically, only the STUN Server IP Address is required. STUN operation is then tested
by clicking Run STUN. If successful the remaining fields are filled with the results.
· STUN Server IP Address: Default = Blank
This is the IP address of the SIP ITSP's STUN server. The system will send basic SIP messages to this destination and
from data inserted into the replies can try to determine the type NAT changes being applied by any firewall between it
and the ITSP.
· STUN Port: Default = 3478. Software level = 4.1+.
Defines the port to which STUN requests are sent if STUN is used.
· Firewall/NAT Type: Default = Unknown
The settings here reflect different types of network firewalls. Options include Blocking Firewall, Symmetric Firewall,
Open Internet, Symmetric NAT, Full Cone NAT, Restricted Cone NAT, Port Restricted Cone NAT, Static Port
Block and Unknown.
· Open Internet
No action required. If this mode is selected, settings obtained by STUN lookups are ignored. The IP address used is
that of the system LAN interface.
· Symmetric Firewall
SIP packets are unchanged but ports need to be opened and kept open with keep-alives. If this type of NAT is
detected or manually selected, a warning ‘Communication is not possible unless the STUN server is supported on
same IP address as the ITSP’ will be displayed as part of the manager validation.
· Full Cone NAT
A full cone NAT is one where all requests from the same internal IP address and port are mapped to the same
external IP address and port. Furthermore, any external host can send a packet to the internal host, by sending a
packet to the mapped external address. SIP packets need to be mapped to NAT address and Port; any Host in the
internet can call in on the open port, that is the local info in the SDP will apply to multiple ITSP Hosts. No warning will
be displayed for this type of NAT because the system has sufficient information to make the connection).
· Symmetric NAT
A symmetric NAT is one where all requests from the same internal IP address and port, to a specific destination IP
address and port, are mapped to the same external IP address and port. If the same host sends a packet with the
same source address and port, but to a different destination, a different mapping is used. Furthermore, only the
external host that receives a packet can send a UDP packet back to the internal host. SIP Packets need to be mapped
but STUN will not provide the correct information unless the IP address on the STUN server is the same as the ITSP
Host. If this type of NAT/Firewall is detected or manually selected, a warning ‘Communication is not possible unless
the STUN server is supported on same IP address as the ITSP’ will be displayed as part of the manager validation.
· Restricted Cone NAT
A restricted cone NAT is one where all requests from the same internal IP address and port are mapped to the same
external IP address and port. Unlike a full cone NAT, an external host (with IP address X) can send a packet to the
internal host only if the internal host had previously sent a packet to IP address X. SIP packets needs to be mapped.
Responses from hosts are restricted to those that a packet has been sent to. So if multiple ITSP hosts are to be
supported, a keep alive will need to be sent to each host. If this type of NAT/Firewall is detected or manually
selected, no warning will be displayed for this type of NAT.
Manager Manager 8.1
Manager
Page 152
15-601011 Issue 25l (11 February 2011)
Configuration Settings: System
· Port Restricted Cone NAT
A port restricted cone NAT is like a restricted cone NAT, but the restriction includes port numbers. Specifically, an
external host can send a packet, with source IP address X and source port P, to the internal host only if the internal
host had previously sent a packet to IP address X and port P. SIP packets needs to be mapped. Keep-alives must be
sent to all ports that will be the source of a packet for each ITSP host IP address. If this type of NAT/Firewall is
detected or manually selected, no warning will be displayed for this type of NAT. However, some Port Restricted NAT's
have been found to be more symmetric in behavior, creating a separate binding for each opened Port, if this is the
case the manager will display a warning ‘Communication is not possible unless the STUN server is supported on same
IP address as the ITSP’ as part of the manager validation.
· Static Port Block: Software level = 4.1+.
Use the RTP Port Number Range specified on the VoIP
open on any NAT firewall involved.
150
tab without STUN translation. Those ports must be fixed as
· Binding Refresh Time (seconds): Default = 0 (Never), Range = 0 to 3600 seconds.
Having established which TCP/UDP port number to use, through either automatic or manual configuration, the system
can send recurring ‘SIP Options requests’ to the remote proxy terminating the trunk. Those requests will keep the port
open through the firewall. Requests are sent every x seconds as configured by this field.
· Note: If a binding refresh time has not been set you may experience problems receiving inbound SIP calls as they
are unable to get through the Firewall. In these circumstances make sure that this value has been configured.
· Public IP Address: Default = 0.0.0.0
This value is either entered manually or discovered by the Run STUN process. If no address is set, the system LAN1
address is used.
· Public Port: Default = 0
This value is either entered manually or discovered by the Run STUN process.
· Run STUN
This button tests STUN operation between the system LAN and the STUN Server IP Address set above. If successful the
results are used to automatically fill the remaining fields with appropriate values discovered by the system. Before using
Run STUN the SIP trunk must be configured.
information icon is shown against the fields to indicate that the values were
· When this option is used, a
automatically discovered rather than manually entered.
· Run STUN on startup: Default = Off
This option is used in conjunction with values automatically discovered using Run STUN. When selected, the system will
rerun STUN discovery whenever the system is rebooted or connection failure to the SIP server occurs.
Manager Manager 8.1
Manager
Page 153
15-601011 Issue 25l (11 February 2011)
5.3.2.4 DHCP Pools
DHCP pools allows the configuration of up to 8 ranges of IP addresses for allocation by the Manager when acting as a
DHCP server. By default the DHCP settings (IP Address, IP Mask and Number of DHCP IP Addresses) set on the LAN
Settings 149 tab are reflected by the first pool here.
· For support of PPP Dial In address requests, at least one of the pools must be on the same subnet as the system's
LAN. Only addresses from a pool on the same subnet as the system's own LAN address will be used for PPP Dial In.
System | LAN1 | DHCP Pools
Control Unit
SOE
Software Level
4.2+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Apply to Avaya IP Phones Only: Default = Off.
If this option is selected, the DHCP addresses are only used for requests from Avaya IP phones. Other devices
connected to the system LAN will have to use static addresses or obtain their address from another DHCP server.
· In addition to the above control, Avaya IP phones will only complete DHCP against a DHCP server configured to
supports a Site Specific Option Number (SSON) that matches that set on the phone. The SSON numbers supported
by the system DHCP are set on the VoIP 150 sub-tab.
· DHCP Pool
Up to 8 pools can be added. The first pool matches the IP Address, IP Mask and Number of DHCP IP Addresses on the
LAN Settings 149 sub-tab. When adding or editing pools, Manager will attempt to warn about overlaps and conflicts
between pools.
· Start Address
Sets the first address in the pool.
· Subnet Mask: Default = 255.255255.0
Sets the subnet mask for addresses issued from the pool.
· Default Router: Default = 0.0.0.0
For pools issuing IP addresses on the same subnet as the system LAN's, 0.0.0.0 instructs the system to
determined the actual default router address to issue by matching the IP address/subnet mask being issued in the
IP Routing 368 table. This matches the default behaviour used by systems without multiple pools. For pools issuing
addresses not on the same subnet as the system LAN's, the default router should be set to the correct value for
devices on that subnet.
· Pool Size: Default = 0
Set the number of DHCP client addresses available in the pool.
Manager Manager 8.1
Manager
Page 154
15-601011 Issue 25l (11 February 2011)
Configuration Settings: System
5.3.2.5 SIP Registrar
This tab is used to set the system parameters for the system acting as a SIP Registrar to which SIP endpoint devices can
register. Separate SIP registrars can be configured on LAN1 and LAN2.
Registration of a SIP endpoint requires an available IP Endpoints license. SIP endpoints are also still subject to the
extension capacity limits of the system.
System | LAN1 | SIP Endpoints
Control Unit
SOE
Software Level
5.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Domain Name: Default = Blank
This is the local SIP registrar domain name that will be needed by SIP endpoints in order to register with the system. If
this field is left blank, registration is against the LAN IP address.
· Layer 4 Protocol: Default = Both TCP & UDP.
Both TCP and UDP SIP endpoints are supported. This field can be used to restrict the system to just TCP or UDP if
required.
· TCP Port: Default = 5060.
The port to use for TCP support.
· UDP Port: Default = 5060.
The port to use for UDP support.
· Challenge Expiry Time (secs): Default = 10.
The challenge expiry time is used during SIP extension registration. When a device registers, the system SIP Registrar
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.
· Auto-create Extn/User: Default = On.
If on, a new extension and user entries are created by the registration of a new SIP endpoint. If off, SIP endpoint can
only register against existing configuration entries.
5.3.3 LAN2
LAN2 is not supported by all control units.
· On the Small Office Edition and IP500/IP500v2 control units the LAN2 settings are used for the RJ45 Ethernet port
labeled WAN.
· On the IP412 control units LAN2 settings are used for the RJ45 ethernet port labeled LAN2.
· For IP406 V2 control units running IP Office 4.1+, the RJ45 LAN port 8 can be selected to act be LAN2 if required. This
is done using the Use Port 8 as LAN2 option on the LAN1 | LAN Settings 149 tab.
System | LAN2
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
*, IP412
, IP500
, IP500v2
.
.
*Optional on IP Office 4.1+.
The fields available for LAN2 are the same as for LAN1
148
except for the following additional field:
· Firewall: Default = <None> (No firewall)
Allows the selection of a system firewall to be applied to traffic routed from LAN2 to LAN1.
Manager Manager 8.1
Manager
Page 155
15-601011 Issue 25l (11 February 2011)
5.3.4 DNS
DNS is a mechanism through which the URL's requested by users, such as www.avaya.com, are resolved into IP
addresses. These requests are sent to a Domain Name Server (DNS) server, which converts the URL to an IP address.
Typically the internet service provider (ISP) will specify the address of the DNS server their customers should use.
WINS (Windows Internet Name Service) is a similar mechanism used within a Windows network to convert PC and server
names to IP addresses via a WINS server.
If the system is acting as a DHCP server, in addition to providing clients with their own IP address settings for LAN1
LAN2 155 it can also provide them with their DNS and WINS settings if requested by the client
148
or
System | DNS
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· DNS Service IP Address: Default = 0.0.0.0 (Do not provide DNS/Use DNS forwarding)
This is the IP address of an DNS Server. Your Internet service provider or network administrator provides this
information. If this field is left blank, the system uses its own address as the DNS server for DHCP client and forward
DNS requests to the service provider when Request DNS is selected in the service being used (Service | IP 335 ).
· Backup DNS Server IP Address: Default = 0.0.0.0 (No backup)
· DNS Domain: Default = Blank (No domain)
This is the domain name for your IP address. Your Internet service provider or network administrator provides this.
Typically this field is left blank.
· WINS Server IP Address: Default = 0.0.0.0 (Do not provide WINS)
This is the IP address of your local WINS server. This is only used by Windows PCs, and normally points to an NT server
nominated by your network administrator as your WINS server. Setting a value will result in also sending a mode of
"hybrid".
· Backup WINS Server IP Address: Default = 0.0.0.0 (No backup)
· WINS Scope: Default = Blank (no scope)
This is provided by your network administrator or left blank.
Manager Manager 8.1
Manager
Page 156
15-601011 Issue 25l (11 February 2011)
Configuration Settings: System
5.3.5 Voicemail
The following settings are used to set the system's voicemail server type and location. The fields are enabled or grayed
out as appropriate to the selected voicemail type. Refer to the appropriate voicemail system installation manual for full
details.
System | Voicemail
Control Unit
SOE
, IP403
Software Level
1.0+.
Mergeable
Pre-3.2
, 3.2+
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
*Changes to Voicemail Type require a reboot.
· Voicemail Type: Default = Embedded Voicemail
Sets the type of voicemail system being used.
· None
No voicemail operation.
· Centralized Voicemail
Select this option when using a Voicemail Pro system installed and licensed on another system in a Small Community
Network. The outgoing line group for connection to the system with the Voicemail Pro should be entered as the
Voicemail Destination.
· Distributed Voicemail: Software level = 6.0+.
This option can be used when additional Voicemail Pro voicemail servers are installed in a Small Community Network
and configured to exchange messages with the central voicemail server using email. This option is used if this system
should use one of the additional servers for its voicemail services rather than the central sever. When selected, the
Voicemail Destination field is used for the outgoing SCN line to the central system and the Voicemail IP Address
is used for the IP address of the distributed voicemail server the system should use.
· Embedded Voicemail
On systems with an Avaya memory card (Small Office Edition, IP406 V2, IP500 and IP500v2), select this option to
run embedded voicemail which stores messages and prompts on the memory card. It also supports internal Auto
Attendant 400 configuration through the IP Office system configuration. The IP500/IP500v2 supports 2 simultaneous
embedded voicemail calls by default but can be licensed for up to 6. The licensed limit applies to total number of
callers leaving messages, collecting messages and or using an auto attendant.
· Group Voicemail
This option is used to support third-party voicemail systems attached by extension ports in the group specified as the
Voicemail Destination.
· Remote Audix Voicemail
Select this option if using a remote Avaya Intuity Audix or MultiMessage voicemail system. Requires entry of an
Audix Voicemail license in Licenses.
· Voicemail Lite/Pro
Select this option when using Voicemail Lite or Voicemail Pro. The IP address of the PC being used should be set as
the Voicemail IP Address. Use of Voicemail Pro requires licenses for the number of simultaneous calls to be
supported. Note that Voicemail Lite is not supported with IP Office Release 5+.
· Voicemail Destination: Default = blank
This setting is used when the Voicemail Type is set to Remote Audix Voicemail, Centralized Voicemail or
Distributed Voicemail. It is used to enter the outgoing line group of the lines configured for connection to the phone
system hosting the central voicemail server. It is also used for Group Voicemail to specify the group whose user
extensions are connected to the 3rd party voicemail system.
· Voicemail IP Address: Default = 255.255.255.255
This setting is used when the Voicemail Type is set to Voicemail Pro or Distributed Voicemail. It is the IP address
of the PC running the voicemail server that the system should use for its voicemail services. If set as 255.255.255.255,
the control unit broadcasts on the LAN for a response from a voicemail server. If set to a specific IP address, the system
connects only to the voicemail server running at that address.
· Backup Voicemail IP Address : Default = 0.0.0.0 (Off). Software level = 6.0+.
This option is supported with Voicemail Pro. An additional voicemail server can be setup but left unused. If contact to
the voicemail server specified by the Voicemail IP Address is lost, responsibility for voicemail services is temporarily
transferred to this backup server address.
· Messages Button Goes to Visual Voice: Default = On. Software level = 4.2+
Visual Voice allows phone users to check their voicemail mailboxes and perform action such as play, delete and forward
messages through menus displayed on their phone. By default, on phones with a MESSAGES button, the navigation is
via spoken prompts. This option allows that to be replaced by Visual Voice on phones that support Visual Voice menus.
For further details see Visual Voice 668 .
Manager Manager 8.1
Manager
Page 157
15-601011 Issue 25l (11 February 2011)
· Voicemail Password : Default = blank. Software level = 2.1 to 3.1.
This password is used by the main unit to confirm connection has been made to the correct Voicemail Pro Server. The
password entered must correspond to the password set on the Voicemail Pro server. This entry should be left blank
when using the any other voicemail server application. For Manager 3.2 and higher this value is set through the
Manager security settings.
· Audix UDP
Available if the voicemail type Remote Audix Voicemail is selected. Needs to be completed with a four digit number from
the Universal Dial Plan of the Avaya Communication Manager system.
· Maximum Record Time: Default = 120 seconds, Range = 30 to 180 seconds. Software level = 3.0+.
This field is only available when Embedded Voicemail is selected as the Voicemail Type. The value sets the maximum
record time for messages and prompts.
· Voicemail Channel Reservation: Software level = 4.0+
These settings allow the channels between the system and Voicemail Pro to be reserved for particular functions.
Unreserved channels can be used for any function but reserved channels cannot be used for any function other than
that indicated. These settings are not available unless the configuration includes validated licenses for the total number
of voicemail channels.
· Note that the voicemail server also restricts the maximum number of channels that can be used for some
services that would be taken from the Unreserved Channels pool. Alarms and callbacks are each limited to
up to 2 channels at any time. Outcalling and conference invites are each limited to up to 5 channels at any
time.
· Unreserved Channels
This setting cannot be changed and by default will show the total number of licensed voicemail channels. This number
will decrease as channels are reserved for the following functions.
· Mailbox Access: Default = 0
This setting sets the number of channels reserved for users accessing mailboxes to collect messages.
· Auto-Attendant: Default = 0
This setting sets the number of channels reserved for users directed to Voicemail Pro short code and module start
points.
· Voice Recording: Default = 0
This setting sets the number of channels reserved for voice recording other than mandatory voice recording (see
below). If no channels are available recording does not occur though recording progress may be indicated.
· Mandatory Voice Recording: Default = 0
This setting sets the number of channels reserved for mandatory voice recording. When no channels are available for
a call set to mandatory recording, the call is barred and the caller hears busy tone.
· Announcements: Default = 0
This setting sets the number of channels reserved for announcements. When no channels are available calls continue
without announcements.
· DTMF Breakout: Software level = 5.0+
Allows system defaults to be set. These are then applied to all user mailboxes unless the users own settings differ.
· Reception / Breakout (DTMF 0)
The number to which a caller is transferred if they press 0 while listening to the mailbox greeting rather than
leaving a message (*0 on embedded voicemail).
· For systems set to Intuity emulation mode, the mailbox user can also access this option when collecting their
messages by dialing *0.
· If the mailbox has been reached through a call flow containing a Leave Mail action, the option provided when
0 is pressed are:
· For IP Office mode, the call follows the Leave Mail action's Failure or Success results connections
depending on whether the caller pressed 0 before or after the record tone.
· For Intuity mode, pressing 0 always follows the Reception / Breakout (DTMF 0) setting.
· Breakout (DTMF 2)
The number to which a caller is transferred if they press 2 while listening to the mailbox greeting rather than
leaving a message (*2 on embedded voicemail). Pre-IP Office 5 this option is not support for Voicemail Pro running
in IP Office mailbox mode.
· Breakout (DTMF 3)
The number to which a caller is transferred if they press 3 while listening to the mailbox greeting rather than
leaving a message (*3 on embedded voicemail). Pre-IP Office 5 this option is not support for Voicemail Pro running
in IP Office mailbox mode.
· SIP Settings
For Voicemail Pro, for calls made or received on a SIP line where any of the line's SIP URI fields are set to Use Internal
Data, that data is taken from these settings. These options are hidden if there are no system SCN lines in the
configuration or no SIP lines with a URI set to Use Internal Data.
Manager Manager 8.1
Manager
Page 158
15-601011 Issue 25l (11 February 2011)
Configuration Settings: System
· SIP Name: Default = User name.
The value from this field is used when the From field of the SIP URI being used for a SIP call is set to Use Internal
Data.
· SIP Display Name (Alias): Default = User name.
The value from this field is used when the Display Name field of the SIP URI being used for a SIP call is set to Use
Internal Data.
· Contact: Default = User name.
The value from this field is used when the Contact field of the SIP URI being used for a SIP call is set to Use Internal
Data.
· Anonymous: Default = Off.
If the From field in the SIP URI is set to Use Internal Data, selecting this option inserts Anonymous into that field
rather than the SIP Name set above.
Manager Manager 8.1
Manager
Page 159
15-601011 Issue 25l (11 February 2011)
5.3.6 Telephony
This tab is used to set the default telephony operation of the system. Some settings shown here can be overridden for
individual users through their User | Telephony 274 tab. The settings are split into a number of sub-tabs.
5.3.6.1 Telephony
System | Telephony | Telephony
Control Unit
SOE
, IP403
Software Level
1.0+.
Mergeable
Pre-3.2
, 3.2+
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
*
*Changes to Companding LAW and Automatic Codec Preference require a reboot.
· Analog Extensions
These settings apply only to analog extension ports provided by the system.
· Default Outside Call Sequence: Default = Normal
This setting is only used with analog extensions. It sets the ringing pattern used for incoming external calls. For
details of the ring types see Ring Tones 762 in the Telephone Features section. This setting can be overridden by a
user's User | Telephony | Call Settings | Outside Call Sequence 274 setting. Note that changing the pattern
may cause fax and modem device extensions to not recognize and answer calls.
· Default Inside Call Sequence: Default = Ring Type 1
This setting is only used with analog extensions. It sets the ringing pattern used for incoming internal calls. For
details of the ring types see Ring Tones 762 in the Telephone Features section. This setting can be overridden by a
user's User | Telephony | Call Settings | Inside Call Sequence 274 setting.
· Default Ring Back Sequence: Default = Ring Type 2
This setting is only used with analog extensions. It sets the ringing pattern used for ringback calls such as hold
return, park return, voicemail ringback, and Ring Back when Free. For details of the ring types see Ring Tones 762
in the Telephone Features section. This setting can be overridden by a user's User | Telephony | Call Settings |
Ringback Call Sequence 274 setting.
· Restrict Analog Extension Ringer Voltage: Default = Off. Software level = 6.1+
Supported on IP500v2 systems only. If selected, the ring voltage on analogue extension ports on the system is
limited to a maximum of 40V Peak-Peak. Also when selected, the message waiting indication (MWI) settings for
analog extension 254 are limited to Line Reversal A, Line Reversal B or None. Any analog extension already set
to another MWI setting is forced to Line Reversal A.
· Dial Delay Time (secs): Default = 4 (USA/Japan) or 1 (ROW), Range = 1 to 99 seconds.
This setting sets the time the system waits following a dialed digit before it starts looking for a short code match. In
situations where there are potential short codes matches but not exact match, it also sets the delay following the dialing
of a digit before dialing complete is assumed. See the Short Codes 426 section.
· Dial Delay Count: Default = 0 digits (USA/Japan) or 4 digits (ROW), Range = 0 to 30 digits.
This setting sets the number of digits dialed after which the system starts looking for a short code match regardless of
the Dial Delay Time.
· Default No Answer Time (secs): Default = 15 seconds, Range = 6 to 99999 seconds.
This setting controls the amount of time before an alerting call is considered as unanswered. How the call is treated
when this time expires depends on the call type.
· For calls to a user, the call follows the user's Forward on No Answer settings if enabled. If no forward is set, the call
will go to voicemail if available or else continues to ring. This timer is also used to control the duration of call
forwarding if the forward destination does not answer. It also controls the duration of ringback call alerting. This
setting is overridden by the User | Telephony | Call Settings | No Answer Time 274 setting for a particular user if
different.
· For calls to hunt groups, this setting controls the time before the call is presented to the next available hunt group
member. This setting is overridden by the Hunt Group | Hunt Group | No Answer Time 306 setting for a particular
hunt group if different.
· Hold Timeout (secs): Default = 120 (US) or 15 (Rest of World), Range = 0 (Off) to 99999 seconds.
This setting controls how long calls remain on hold before recalling to the user who held the call. Note that the recall
only occurs if the user has no other connected call. Recalled calls will continue ringing and do not follow forwards or go
to voicemail.
· Park Timeout (secs): Default = 300 seconds, Range 0 (Off) to 99999 seconds.
This setting controls how long calls remain parked before recalling to the user who parked the call. Note that the recall
only occurs if the user has no other connected call. Recalled calls will continue ringing and do not follow forwards or go
to voicemail.
Manager Manager 8.1
Manager
Page 160
15-601011 Issue 25l (11 February 2011)
Configuration Settings: System
· Ring Delay: Default = 5 seconds, Range = 0 to 98 seconds. Software level = 3.2+.
This setting is used when any of the user's programmed appearance buttons is set to Delayed ringing. Calls received on
that button will initially only alert visually. Audible alerting will only occur after the ring delay has expired. This setting
can be overridden by a ring delay set for an individual user (User | Telephony | Multi-line Options | Ring Delay 278 ).
· Call Priority Promotion Time (secs): Default = Disabled, Range = Disabled, 10 to 999 seconds. Software level = 4.2
+.
When calls are queued for a hunt group, higher priority calls are placed ahead of lower priority calls, with calls of the
same priority sort by time in queue. External calls are assigned a priority (1-Low, 2-Medium or 3-High) by the
Incoming Call Route that routed the call. Internal calls are assigned a priority of 1-Low. This option can be used to
increase the priority of a call each time it has remained queued for longer than this value. The calls priority is increased
by 1 each time until it reaches 3-High.
· In situations where calls are queued, high priority calls are placed before calls of a lower priority. This has a number
of effects:
· Mixing calls of different priority is not recommended for destinations where Voicemail Pro is being used to
provided queue ETA and queue position messages to callers since those values will no longer be accurate when
a higher priority call is placed into the queue. Note also that Voicemail Pro will not allow a value already
announced to an existing caller to increase.
· If the addition of a higher priority call causes the queue length to exceed the hunt group's Queue Length
Limit 316 , the limit is temporarily raised by 1. This means that calls already queued are not rerouted by the
addition of a higher priority call into the queue.
· Companding LAW
These settings should not normally be changed for their defaults. They should only be used where 4400 Series phones
(U-Law) are installed on systems which have A-Law digital trunks. Note that U-Law is also called Mu-Law or µ-Law.
· A-Law or U-Law
PCM (Pulse Code Modulation) is a method for encoding voice as data. In telephony, two methods of PCM encoding
are widely used, A-Law and U-Law (also called Mu-Law or µ-Law). Typically U-Law is used in North America and a
few other locations while A-Law is used elsewhere. As well as setting the correct PCM encoding for the region, the
A-Law or U-Law setting of a system when it is first started affects a wide range of regional defaults relating to line
settings and other values.
· For IP400 systems, each control units was manufactured as either an A-Law variant or a U-Law variant.
· For IP500 and IP500v2 systems, the encoding default is set by the type of Feature Key installed when the
system is first started. The cards are either specifically A-Law or U-Law. PARTNER Version cards are U-Law.
Norstar Version cards are A-Law.
· Default Currency: Default = Locale specific 844 . Software level = 4.0+.
This setting is used with ISDN Advice of Charge (AOC) services. Note that changing the currency clears all call costs
stored by the system except those already logged through SMDR 898 . The currency is displayed in Phone Manager Pro
and included in the system SMDR output.
· DSS Status: Default = Off
This setting affects Avaya display phones with programmable buttons. It controls whether pressing a DSS key set to
another user who has a call ringing will display details of the caller. When off, no caller information is displayed.
· Auto Hold: Default = On. Software level = 3.0+.
Used for users with multiple appearance buttons. When on, if a user presses another appearance button during a call,
their current call is placed on hold. When off, if a users presses another appearance button during a call, their current
call is disconnected.
· Dial By Name: Default = On
When on, allows the directory features on various phones to match the dialing of full names. When off, the directory
features use first character match only. See User Directory Access 729 . For IP Office Release 5+ this option is fixed as
On and is not adjustable.
· Show Account Code: Default = On
This setting controls the display and listing of system account codes:
· When on:
· When entering account codes through Phone Manager, users can select from a drop-down list of available
account codes.
· When entering account codes through a phone, the account code digits are shown while being dialed.
· When off:
· Within Phone Manager the drop-down list of available account codes is not useable, instead account codes must
be entered using the Phone Managers PIN Code features.
· When entering account codes through a phone, the account code digits are replaced by s characters on the
display.
Manager Manager 8.1
Manager
Page 161
15-601011 Issue 25l (11 February 2011)
· Allow Outgoing Transfer: Default = Off. Software level = 3.0 to 3.2.
When not enabled, users are only able to transfer or forward off-switch incoming external calls. When enabled, users
can forward both incoming and outgoing external calls. For pre-3.0 system the default behaviour is to bar outgoing
transfers. For IP Office 4.0 and higher the default behaviour is to always allow outgoing transfers.
· Inhibit Off-Switch Forward/Transfer: Default = Off (Italy = On)
When enabled, this setting stops any user from transferring or forwarding calls externally. See Off-Switch Transfer
Restrictions 782 .
· Restrict Network Interconnect: Default = Off. Software Level = 4.2+.
When this option is enabled, each trunk is provided with a Network Type option that can be configured as either
Public or Private. The system will not allow calls on a public trunk to be connected to a private trunk and vice versa,
returning number unobtainable indication instead.
· Due to the nature of this feature, its use is not recommended on systems also using any of the following other
system features: Small Community Networks 810 , VPNremote, Phone Manager telecommuter mode.
· WAN Mode Override: Default = Off. Software level = 3.2/4.0 Q2 2007 Maintenance Release.
Alters the configuration of the WAN interface from the default to that required for BT X25 link inter-working. Used with
IP406 V2 systems only.
· Automatic Codec Preference: Default = G.729(a) 8K CS-ACELP. Software level = 5.0+.
This setting is used by all IP lines and extensions where the Compression Mode has been set to Automatic Select.
The codec selected here will be the first codec the line or extension uses codec negotiation. Note that the G.711 codecs
are treated as a pair, so if one is selected as the first preference, the other will be second in the list.
Setting
Preference Order
G.729
G729(a) 8K CS-ACELP / G711 U-Law 64K / G711 A-Law 64K / G723.1 6K3 MP-MLQ.
G.723
G723.1 6K3 MP-MLQ / G729(a) 8K CS-ACELP / G711 U-Law 64K / G711 A-Law 64K.
G.711 U-Law
G711 U-Law 64K / G711 A-Law 64K / G729(a) 8K CS-ACELP / G723.1 6K3 MP-MLQ.
G.711 A-Law
G711 A-Law 64K / G711 U-Law 64K / G729(a) 8K CS-ACELP / G723.1 6K3 MP-MLQ.
· Drop External Only Impromptu Conference: Default = Off. Software level = 5.0+.
If selected, when the last remaining internal user in a conference exits the conference, the conference is ended,
regardless of whether it contains any external callers. The Inhibit Off-Switch Forward/Transfer option above is no
longer applied to conference calls. If not selected, the conference is automatically end when the last internal party or
trunk that supports reliable disconnect exits the conference.
· Visually Differentiate External Call: Default = Off. Software level = 5.0+.
This setting is applied to the lamp flashing rate used for bridged appearance and call coverage appearance buttons on
1400, 1600 and 9600 Series phones and on SMB24, BM32 and DBM32 button modules. When selected, external calls
alerting on those buttons will use a slow flash (200ms on/50ms off). If not selected or if the call is internal, normal
flashing (500ms on/500ms off) is used.
Manager Manager 8.1
Manager
Page 162
15-601011 Issue 25l (11 February 2011)
Configuration Settings: System
5.3.6.2 Tones and Music
System | Telephony | Tones and Music
Control Unit
SOE
, IP403
Software Level
2.1+.
Mergeable
Pre-3.2
, 3.2+
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
*
*Changes to Busy Tone Detection and the hold music System Source requires a reboot. Deleting any of the hold
music Alternate Sources also requires a reboot.
· Conferencing Tone: Default = Entry & Exit Tones.
This settings controls how conference tones are used. It can be set to either Entry & Exit Tones or Repeating Tone.
With Entry & Exit Tones a single tone is heard when a new party joins a conference and double-tone is heard when a
party leaves the conference. With Repeating Tone a conference tone is heard every 10 seconds by all conference
parties.
· Disconnect Tone: Default = Default (Use locale setting 846 ). Software level = 4.0+.
For digital and IP phones, when the system detects that the far end of a call has disconnected, it can make the near end
either go idle or play disconnect tone. By default the chosen behaviour depends on the system locale 844 . This field can
be used to override the locale's default action and force either disconnect tone or go idle.
· Default: Use the system locale specific action for disconnected calls.
· On: Play disconnect tone when far end disconnection is detected.
· Off: Go idle when far end disconnection is detected.
· Local Dial Tone: Default = On
For all normal operation this setting should be left enabled as it allows the system to provide dial tone to users
(essential for MSN working).
· Local Busy Tone: Default = Off
This setting should only be used when the local exchange gives a busy signal via Q.931 but does not provide busy tone.
· Beep on Listen: Default = On (USA)/On (Rest of World)
This setting controls whether call parties hear a repeating tone when their call is monitored by another party using the
Call Listen 443 feature.
· GSM Silence Suppression: Default = Off. Software level = 3.0+.
This setting should only be selected if voice quality problems are experienced with calls to voicemail or while recording
calls. When on, the system signals silence by generating silence data packets in periods when the voicemail system is
not playing prompts. Note that use of this option may cause some timeout routing options in voicemail to no longer
work.
· Busy Tone Detection: Default = System Frequency (Tone defined by system locale)
Allows configuration of the system's busy tone detection settings. These are on lines that do not provide reliable
disconnect signalling. In that case, the system will uses tone disconnect clearing to disconnect such lines after 6 seconds
of continuous tone. The default tone (frequency and on/off cadence) detection used is defined by the system locale 844 .
The settings should not be adjusted unless advised by Avaya Technical Support. Changes to this setting require a reboot
rather than a merge when the new configuration is sent to the system.
· Hold Music
This section is used to define the source for the system's music on hold source. You must ensure that any MOH source
you use complies with copyright, performing rights and other local and national legal requirements. For full details of
music on hold configuration, see Music on Hold 763 .
· System Source: Default = WAV File.
Selects the default hold music source for most uses of music on hold. Changes to this setting require a reboot
rather than a merge when the new configuration is sent to the system.
· WAV File:
Use the WAV file holdmusic.wav. This file is loaded via TFTP.
· External: Software level = 3.1+.
Use the audio source connected to the back of the control unit. This causes the system to not load the
holdmusic.wav file via TFTP when rebooted. Previous the presence of a holdmusic.wav file loaded onto the
system automatically overrode the use of the control units external source.
· Tone: Software level = 4.2+.
The use of a double beep tone (425Hz, 02./0.2/0.2/3.4 seconds on/off) can be selected as the system source.
· IP Office 4.0+: The hold music tone is automatically used if the system source is set to WAV File but the
holdmusic.wav file has not been successfully downloaded.
Manager Manager 8.1
Manager
Page 163
15-601011 Issue 25l (11 February 2011)
· Alternate Sources: Software level = 4.2+ (Not Small Office Edition).
Up to three additional hold music source can be specified. These are wav files loaded and stored in the same way
as holdmusic.wav. Note that adding and changing a source can be done using a merge but deleting a source
requires a reboot.
· Number
Assigned automatically by the system. The alternate sources are numbered 2, 3 and 4.
· Name: Up to 31 characters
This field is used to associate a name with the alternate source. That name is then used in the Hold Music
Source field on Incoming Call Routes and Hunt Groups.
· Source: Up to 31 characters
Defines the source for the music on hold.
· For a wav file, enter WAV: followed by the file name. For example, for the file holdmusic2.wav, enter
WAV:holdmusic2.wav. The system will automatically attempt to load that file via TFTP following a
reboot.
· IP Office Release 6.1+: Any analog extension with its Equipment Classification 254 set as MOH Source
can be entered as the alternate source. Enter XTN: followed by the extension's Base Extension number.
For example XTN:224.
Manager Manager 8.1
Manager
Page 164
15-601011 Issue 25l (11 February 2011)
Configuration Settings: System
5.3.6.3 Call Log
IP Office 5.0+: The system can store a centralized call log 745 for users. Each users' centralized call log can contain up to
30 call records for user calls (10 on IP412 and IP406 V2 systems). When this limit is reached, new call records replace the
oldest record.
On 1400, 1600 and 9600 Series phones with a Call Log or History button, that button can be used to display the user's
centralized call log. The user can use the call log to make calls or to store as a personal speed dial. They can also edit the
call log to remove records. The same call log is also if the user logs into one-X Portal for IP Office application.
The centralized call log moves with the user if they log on and off from different phones. This includes if they hot desk
within a Small Community Network.
System | Telephony | Call Log
Control Unit
SOE
Software Level
5.0+.
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
Mergeable
· Default Centralized Call Log On: Default = On.
When selected, each user is defaulted to have the system store a call log of their calls. This call log will be displayed on
the phone when the user is using a 1400, 1600 or 9600 Series phone. The use of centralized call logging can be
enabled/disabled on a per user basis using the Centralized Call Log 280 user setting (User | Telephony | Call Log 280 ).
· Logged Missed Calls Answered at Coverage: Default = Off.
This setting controls how calls to a user, that are answered by a covering user should be logged in the centralized call
log. This option applies for calls answered elsewhere (covered) by pickup, call coverage (call coverage 686 buttons or
coverage group 748 ), bridged appearance button, user BLF, voicemail, etc.
Setting
Off (Default)
On
Targeted User
Covering User
Nothing
Answered Call
Missed Call
Answered Call
· Log Missed Hunt Group Calls: Default = Off.
By default, hunt group calls are not included in any user's centralized call log unless answered by the user. If this option
is selected, a separate call log is kept for each hunt group of calls that are not answered by anyone. It includes hunt
group calls that go to voicemail.
· If missed hunt group calls are also being logged, the system stores up to 10 call records for each hunt group. When
this limit is reached, new call records replace the oldest record.
· Within the user call log setting (User | Telephony | Call Log 280 ) the list of hunt groups allows selection of which
hunt groups' missed call records should be displayed as part of the centralized call log when a user is using a 1608
or 1616 phone.
Manager Manager 8.1
Manager
Page 165
15-601011 Issue 25l (11 February 2011)
5.3.7 Directory Services
Directory services can be used to import directory entries (names and numbers) from external sources. These sets of
entries are regularly re-imported.
For systems, the directory records can come from the following sources:
· LDAP Import 169
The system can import up to 5000 LDAP records for use within directories shown by user phones and applications.
LDAP import is configured through the System | Directory Services | LDAP 169 form. For pre-IP Office Release 5.0+
system, LDAP was restricted to 500 records and only displayed within user applications.
· HTTP Import 171 (IP Office Release 5.0+)
Systems are able to import the directory entries from another system using HTTP. HTTP import is configured
through the System | Directory Services | HTTP 171 form by specifying an IP address (or SCN connection). The
records imported can be any or all of the following record types held by the system from which the records are
being imported: LDAP imported entries, HTTP imported entries, configuration entries.
· System Directory Records 358 (Configuration entries)
Up to 2500 records can be entered directly into the system configuration through the Directory 358 menu. System
directory records override matching LDAP/HTTP imported records. For pre-IP Office Release 5.0+ system, the
number of system directory records was 1000.
· IP Office Release 5+: 1400, 1600 and 9600 Series phones with a CONTACTS button and System Phone 765
privileges, can add, delete and edit the system directory records of the system at which they are logged in.
They cannot edit LDAP or HTTP imported entries.
System
Configuration
LDAP Import
HTTP Import
Total Number
of Directory
Records
IP500/
IP500v2
2500
5000
5000
5000
IP412
2500
2500
2500
2500
IP406 V2
2500
2500
2500
2500
Manager Manager 8.1
Manager
Number of Directory Records
Page 166
15-601011 Issue 25l (11 February 2011)
Configuration Settings: System
Directory entries are used for two types of function:
· Directory Dialing
Directory numbers are displayed by user applications such as Phone Manager and SoftConsole. Directory numbers
are viewable through the Dir 615 function on many Avaya phones (Contacts or History). They allow the user to
select the number to dial by name. The directory will also contain the names and numbers of users and hunt groups
on the system.
· The Dir function groups directory entries shown to the phone user into the following categories. Depending on
the phone, the user may be able to select the category currently displayed. In some scenarios, the categories
displayed may be limited to those supported for the function being performed by the user:
· External
Directory entries from the system configuration. IP Office 5.0+: This includes HTTP and LDAP imported
entries.
· Groups
Groups on the system. If the system is in a Small Community Network it will also include groups on other
systems in the network (For pre-IP Office 5 systems, this feature requires the systems to have Advanced
Small Community Networking licenses).
· Users or Index
Users on the system. If the system is in a Small Community Network it will also include users on other
systems in the network (For pre-IP Office 5 systems, this feature requires the systems to have Advanced
Small Community Networking licenses).
· Personal
Available for T3 phones, T3 IP phones, 1400, 1600 and 9600 Series phones. These are the user's personal
directory entries stored within the system configuration.
· Name Matching
Directory entries are also used to associate a name with the dialled number on outgoing calls or the received CLI on
incoming calls. When name matching is being done, a match in the users personal directory overrides any match in
the system directory. Note that some user applications also have their own user directory.
· The IP Office Phone Manager and SoftConsole applications have their own user directories which are also used
by the applications name matching. Matches in the application directory may lead to the application displaying
a different name from that shown on the phone.
· Name matching is not performed when a name is supplied with the incoming call, for example QSIG trunks.
· Directory name matching is not supported for DECT handsets.
The following characters (IP Office Release 5.0+) are supported in directory entries. They are supported in both system
configuration entries and in HTTP/LDAP imported entries.
· ? = Any Digit
Directory entries containing a ? are only used for name matching against the dialed or received digits on outgoing or
incoming. They are not included in the directory of numbers to dial available to users through their phones or
applications. The wildcard can be used in any position but typically would be used at the end of the number.
· In the following example, any calls where the dialed or received number is 10 digits long and starts 732555 will
have the display name Homdel associated with them.
· Name: Holmdel
· Number: 9732555????
· ( and ) brackets = Optional Digits
These brackets are frequently used to enclose an optional portion of a number, typically the area code. Only one
pair of brackets are supported in a number. Entries containing digits inside ( ) brackets are used for both name
matching or user dialling. When used for name matching, the dialed or received digits are compared to the
directory number with and without the ( ) enclosed digits. When used for dialling from a phone or application
directory, the full string is dialed with the ( ) brackets removed.
· The following example is a local number. When dialed by users they are likely to dial just the local number.
However on incoming calls, for the CLI the telephony provider includes the full area code. Using the ( ) to
enclose the area code digits, it is possible for the single directory entry to be used for both incoming and
outgoing calls.
· Name: Raj Garden
· Number: 9(01707)373386
· Space and - Characters
Directory entries can also contain spaces and - characters. These will be ignored during name matching and dialing
from the directory.
Manager Manager 8.1
Manager
Page 167
15-601011 Issue 25l (11 February 2011)
Imported Records
· Imported directory records are temporary until the next import refresh. They are not added to the system's
configuration.
· They cannot be viewed or edited using Manager or edited by a System Phone user.
· The temporary records are lost if the system is restarted. However the system will request a new set of imported
directory records after a system restart.
· The temporary records are lost if a configuration containing Directory changes is merged. The system will then
import a new set of temporary records without waiting for the Resync Interval.
· If an configuration record is edited by a System Phone user to match the name or number of a temporary record,
the matching temporary record is discarded.
Importation Rules
When a set of directory records is imported by HTTP or LDAP, the following rules are applied to the new records:
· Imported records with a blank name or number are discarded.
· Imported records that match the name or number of any existing record are discarded.
· When the total number of directory records has reached the system limit, any further imported records are
discarded.
System
Configuration
LDAP Import
HTTP Import
Total Number
of Directory
Records
IP500/
IP500v2
2500
5000
5000
5000
IP412
2500
2500
2500
2500
IP406 V2
2500
2500
2500
2500
Manager Manager 8.1
Manager
Number of Directory Records
Page 168
15-601011 Issue 25l (11 February 2011)
Configuration Settings: System
5.3.7.1 LDAP
LDAP (Lightweight Directory Access Protocol) is a software protocol for enabling anyone to locate organizations,
individuals, and other resources such as files and devices in a network, whether on the Internet or on a corporate intranet.
LDAP is a "lightweight" (smaller amount of code) version of DAP (Directory Access Protocol), which is part of X.500, a
standard for directory services in a network. LDAP is lighter because in its initial version, it did not include security
features.
· IP Office 5.0+: The system supports the import of directory records from one system to another using HTTP. That
includes using HTTP to import records that another system has learnt using LDAP. HTTP import 171 , which is
simpler to configure, can be used to relay LDAP records with LDAP configured on just one system.
· LDAP records can contain several telephone numbers. Each will be treated as a separate directory entry when
imported into the system directory.
· The NoUser source number setting ExtendLDAPDirectLimit usable with IP Office 4.1-4.2 systems is no longer
supported for IP Office 5+.
In a network, a directory tells you where in the network something is located. On TCP/IP networks, including the Internet,
the Domain Name System (DNS) is the directory system used to relate the domain name to a specific network address.
However, you may not know the domain name. LDAP allows you to search for an individual without knowing where they're
located (although additional information will help with the search).
An LDAP directory is organized in a simple "tree" hierarchy consisting of the following levels:
· The "root" directory (the starting place or the source of the tree), which branches out to
· Countries, each of which branches out to
· Organizations, which branch out to
· Organizational units (divisions, departments, and so forth), which branches out to (includes an entry for)
· Individuals (which includes people, files, and shared resources such as printers)
An LDAP directory can be distributed among many servers. Each server can have a replicated version of the total directory
that is synchronized periodically. An LDAP server is called a Directory System Agent (DSA). An LDAP server that receives a
request from a user takes responsibility for the request, passing it to other DSA's as necessary, but ensuring a single
coordinated response for the user.
LDAP Directory Synchronization allows the telephone number Directory held in the Control Unit to be synchronized with
the information on an LDAP server.The feature can be configured to interoperate with any server that supports LDAP
version 2 or higher.
System | Directory Services | LDAP
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· LDAP Enabled: Default = Off
This option turns LDAP support on or off.
· User Name: Default = blank
Enter the user name to authenticate connection with the LDAP database. To determine the domain-name of a particular
Windows 2000 user look on the "Account" tab of the user's properties under "Active Directory Users and Computers".
Note that this means that the user name required is not necessarily the same as the name of the Active Directory entry.
There should be a built-in account in Active Directory for anonymous Internet access, with prefix "IUSR_" and suffix
server_name (whatever was chosen at the Windows 2000 installation). Thus, for example, the user name entered is this
field might be: IUSR_CORPSERV@example.com
· Password: Default = blank
Enter the password to be used to authenticate connection with the LDAP database. Enter the password that has been
configured under Active Directory for the above user. Alternatively an Active Directory object may be made available for
anonymous read access. This is configured on the server as follows:
· In "Active Directory Users and Computers" enable "Advanced Features" under the "View" menu. Open the properties
of the object to be published and select the "Security" tab. Click "Add" and select "ANONYMOUS LOGON", click "Add",
click "OK", click "Advanced" and select "ANONYMOUS LOGON", click "View/Edit", change "Apply onto" to "This object
and all child objects", click "OK", "OK", "OK".
Manager Manager 8.1
Manager
Page 169
15-601011 Issue 25l (11 February 2011)
Once this has been done on the server, any entry can be made in the User Name field in the System configuration
form (however this field cannot be left blank) and the Password field left blank. Other non-Active Directory LDAP
servers may allow totally anonymous access, in which case neither User Name nor Password need be configured.
· Server IP Address: Default = blank
Enter the IP address of the server storing the database.
· Server Port: Default = 389
This setting is used to indicate the listening port on the LDAP server.
· Authentication Method: Default = Simple
Select the authentication method to be used.
· Simple: clear text authentication
· Kerberos: Kerberos 4 LDAP and Kerberos 4 DSA encrypted authentication (for future use).
· Resync Interval (secs): Default = 3600 seconds, Range = 1 to 99999 seconds.
The frequency at which the system should resynchronize the directory with the server. This value also affects some
aspects of the internal operation.
· The LDAP search inquiry contains a field specifying a time limit for the search operation and this is set to 1/16th of
the resync interval. So by default a server should terminate a search request if it has not completed within 225
seconds (3600/16).
· The client end will terminate the LDAP operation if the TCP connection has been up for more than 1/8th of the resync
interval (default 450 seconds). This time is also the interval at which a change in state of the "LDAP Enabled"
configuration item is checked.
· Search Base / Search Filter: Default = blank
These 2 fields are used together to refine the extraction of directory entries. Basically the Base specifies the point in the
tree to start searching and the Filter specifies which objects under the base are of interest. The search base is a
distinguished name in string form (as defined in RFC1779).
The Filter deals with the attributes of the objects found under the Base and has its format defined in RFC2254 (except
that extensible matching is not supported).
If the Search Filter field is left blank the filter defaults to "(objectClass=*)", this will match all objects under the
Search Base.
The following are some examples applicable to an Active Directory database:
· To get all the user phone numbers in a domain:
Search Base: cn=users,dc=acme,dc=com
Search Filter: (telephonenumber=*)
· To restrict the search to a particular Organizational Unit (eg office) and get cell phone numbers also:
Search Base: ou=holmdel,ou=nj,DC=acme,DC=com
Search Filter: (|(telephonenumber=*)(mobile=*))
· To get the members of distribution list "group1":
Search Base: cn=users,dc=acme,dc=com
Search Filter: (&(memberof=cn=group1,cn=users,dc=acme,dc=com)(telephonenumber=*))
· Number Attributes: Default = see below
Enter the number attributes the server should return for each entry that matches the Search Base and Search Filter.
Other entries could be ipPhone, otherIpPhone, facsimileTelephoneNumber, otherfacsimileTelephone Number, pager or
otherPager. The attribute names are not case sensitive. Other LDAP servers may use different attributes.
· By default the entry is "telephoneNumber,otherTelephone,homePhone=H,otherHomePhone=H,mobile=M,
otherMobile=M", as used by Windows 2000 Server Active Directory for Contacts.
· The optional "=string" sub-fields define how that type of number is tagged in the directory. Thus, for example, a cell
phone number would appear in the directory as: John Birbeck M 7325551234
Manager Manager 8.1
Manager
Page 170
15-601011 Issue 25l (11 February 2011)
Configuration Settings: System
5.3.7.2 HTTP
IP Office 5+: The system can use HTTP to import the directory records held by another system.
Note that support for HTTP can be disabled. The Avaya HTTP Clients Only 143 setting (System | System 143 ) can restrict
a system from responding to HTTP requests. The system's Unsecured Interface 90 security settings also included
controls for HTTP access (HTTP Directory Read and HTTP Directory Write).
System | Directory Services | HTTP
Control Unit
SOE
Software Level
5.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Directory Type: Default = None (No HTTP import)
Set whether HTTP import should be used and the method of importation.
· None
Do not use HTTP import.
· IP Office
Import from the system at the IP address set in the Source field.
· IP Office SCN
Import from a system in a Small Community network. The Source field is used to select the Outgoing Line ID
that matches the H323 SCN line to the remote system.
· Source: Default = Blank
The form of this field changes according to the Directory Type selection above.
· List: Default = All
This field sets what types of directory record should be imported.
· All
Import the full set of directory records from the remote system.
· Config Only
Import just directory records that are part of the remote system's configuration. Note that these will be treated as
imported records and will not be added to the local systems own configuration records.
· LDAP Only
Import just directory records that the remote system has obtained as the result of its own LDAP import. This allows
LDAP directory records to be relayed from one system to another.
· HTTP Only
Import just directory records that the remote system has obtained as the result of its own HTTP import. This allows
HTTP directory records to be relayed from one system to another.
· URI: Default = /system/dir/complete_dir_list
This field is for information only and cannot be adjusted. The path shown changes to match the List setting above.
· Resync Interval (secs): Default = 3600 seconds.
Set how often the system should request an updated import. When a new import is received, all previously imported
records are discarded and the newly imported records are processed.
Manager Manager 8.1
Manager
Page 171
15-601011 Issue 25l (11 February 2011)
5.3.8 System Events
The system supports a number of methods by which events occurring on the system can be reported. These are in
addition to the real-time and historical reports available through the System Status Application (SSA).
· SNMP Reporting (IP Office 2.1+)
Simple Network Management Protocol (SNMP) allows SNMP clients and servers to exchange information. SNMP
clients are built into devices such as network routers, server PC's, etc. SNMP servers are typically PC application
which receive and/or request SNMP information. The system SNMP client allows the system to respond to SNMP
polling and to send alarm information to SNMP servers.
· In order for an SNMP server application to interact with a system, the IP Office MIB files, provided on the IP
Office Admin Suite DVD, must be compiled into the SNMP server's applications database. For full details, refer
to the Manager Installation Manual.
· SMTP Email Reporting (IP Office 3.2+)
The system can send alarms to an SMTP email server. Using SMTP requires details of a valid SMTP email account
user name and password and server address. If SMTP email alarms are configured but for some reason the system
cannot connect with the SMTP server, only the last 10 alarms are stored for sending when connection is successful.
· Use of SMTP alarms requires the SMTP server details to be entered in the SMTP
177
tab.
· Syslog Reporting (IP Office 4.1+)
The system can also send alarms to a Syslog server (RFC 3164) without needing to configure an SNMP server. In
addition Syslog output can include audit trail events.
Multiple event destinations can be created, each specifying which events and alarms to include, the method of reporting to
use (SNMP, Syslog or Email) and where to send the events. Up to 2 alarm destinations can be configured for SNMP, 2 for
Syslog and 3 for SMTP email.
Enabling SNMP Alarms
1. Select
System.
2. Select the System Events tab.
3. Select SNMP Enabled.
4. Complete the information in the SNMP Info section by entering the SNMP port and community details to match
those expected by your SNMP server. Details of installing the MIB files required for SNMP are included in the
Manager Installation manual.
5. Click OK.
Editing Alarm Destinations
The Alarms section of the System Events tab displays the currently created alarm traps. It shows the event destinations
and the types of alarms that will trigger the send of event reports. Up to 2 alarm destinations can be configured for SNMP,
2 for Syslog and 3 for SMTP email.
1. Select the Alarms sub-tab.
2. Use the Add, Remove and Edit controls to alter the traps.
3. Click Add or select the alarm to alter and then click Edit.
4. For a new alarm, set the Destination to either Trap (SNMP) or Syslog or Email (SMTP). Note that once a
destination has been saved by clicking OK it cannot be changed to another sending mode.
5. The remaining details will indicate the required destination information and allow selection of the alarm events to
include.
6. When completed, click OK.
7. Click OK again.
Manager Manager 8.1
Manager
Page 172
15-601011 Issue 25l (11 February 2011)
Configuration Settings: System
5.3.8.1 Configuration
System | System Events | Configuration
Control Unit
SOE
Software Level
2.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· SNMP Enabled: Default = Off
Enables support for SNMP. This option is not required if using SMTP or Syslog.
· Community (Read-only): Default = public
The SNMP community name to which the system belongs.
· SNMP Port: Default = 161, Range = 0 to 65534.
The port on which the system listens for SNMP polling.
· Device ID
This is a text field used to add additional information to alarms.
· Contact
This is a text field used to add additional information to alarms.
· Location
This is a text field used to add additional information to alarms.
· QoS Parameters: Software level = 5.0+.
These parameters are used if Enable RTCP Monitor on Port 5005 150 is selected (Systems | LAN1 | VoIP 150 ). They
are used as alarm thresholds for the QoS data collected by the system for calls made by Avaya H323 phones and for
phones using VCM channels. If a monitored call exceeds any of the threshold an alarm is sent to the System Status
application. Quality of Service alarms can also be sent from the system using Alarms 174 .
· The alarm occurs at the end of a call. If a call is held or parked and then retrieved, an alarm can occur for each
segment of the call that exceeded a threshold.
· Where a call is between two extensions on the system, it is possible that both extensions will generate an
alarm for the call.
· An alarm will not be triggered for the QoS parameters recorded during the first 5 seconds of a call.
· Round Trip Delay (msec): Default = 350.
Less than 160ms is high quality. Less than 350ms is good quality. Any higher delay will be noticeable by those
involved in the call. Note that, depending on the compression codec being used, some delay stems from the signal
processing and cannot be removed: G711 = 40ms, G723a = 160ms, G729 = 80ms.
· Jitter (msec): Default =20.
Jitter is a measure of the variance in the time for different voice packets in the same call to reach the destination.
Excessive jitter will become audible as echo.
· Packet Loss (%): Default = 3.0.
Excessive packet loss will be audible as clipped words and may also cause call setup delays.
Round Trip Delay
Good Quality
High Quality
Round Trip Delay
< 350ms
< 160ms
< 20ms
< 20ms
< 3%
< 1%
Jitter
Packet Loss
Manager Manager 8.1
Manager
Page 173
15-601011 Issue 25l (11 February 2011)
5.3.8.2 Alarms
This form is used to configure what can cause alarms to be sent using the different alarm methods.
· Up to 2 alarm traps can be configured for use with the SNMP settings on the System | System Events |
Configuration 173 tab.
· Up to 3 email alarms can be configured for the sending using the systems System | SMTP
destination is set as part of the alarm configuration below.
177
settings. The email
· Up to 2 alarms can be configured for sending to a Syslog destination that is included in the alarm settings.
System | System Events | Alarms
Control Unit
SOE
Software Level
2.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Events
This section is used to show and edit the alarm.
· Destination
The options are Trap (SNMP), Syslog or Email (SMTP). To use SNMP or Email the appropriate settings must be
configured on the Configuration sub-tab. Note that the Destination type will also be grayed out if the maximum
number of configurable alarms destinations of that type has been reached. Up to 2 alarm destinations can be
configured for SNMP, 2 for Syslog and 3 for SMTP email.
· Trap:
If selected, the details required in addition to the selected Events are:
· IP Address: Default = 0.0.0.0
The IP address of the SNMP server to which trap information is sent.
· Port: Default = 162, Range = 0 to 65534.
The SNMP transmit port
· Community: Default = Blank
The SNMP community for the transmitted traps. Must be matched by the receiving SNMP server.
· Email: Software level = 3.2+.
If selected, the details required in addition to the selected Events are:
· Email:
The destination email address.
· Syslog: Software level = 4.1+.
If selected, the details required in addition to the selected Events are:
· IP Address: Default = 0.0.0.0
The IP address of the Syslog server to which trap information is sent.
· Port: Default = 516, Range = 0 to 65534.
The Syslog destination port.
Manager Manager 8.1
Manager
Page 174
15-601011 Issue 25l (11 February 2011)
Configuration Settings: System
· Events: Default = None
Sets which types of system events should be collected and sent. The table below lists the alarms associated with each
type of event. Text in italics in the messages is replaced with the appropriate data. Items in [] brackets are included
in the message if appropriate. The subject line of SMTP email alarms takes the form "System name: IP address System Alarm".
Type
Events
Event State
Message
Entity
Application
Voicemail operation
The Voicemail server is now operational.
Voicemail Failure
The Voicemail server is down.
Voicemail Event - storage OK
The Voicemail server storage is OK.
Voicemail Event - storage
nearly full
The Voicemail server storage is nearly
full.
Voicemail Event - storage full
The Voicemail server storage is full.
Compact Flash Card
Change
The PC card in name has changed.
Expansion Module
Operational
Expansion module name link is up.
Failure
Expansion module name link is down.
Error
Expansion module name link has a link
error.
Change
Expansion module name link has
changed.
Operational
Trunk number (name) [on expansion
module number] is now operational.
Failure
Trunk number (name) [on expansion
module number] is down.
Operational
VCM module name is now operational.
Failure
VCM module name has failed.
Non-primary location boot
alarm
System running backup software.
Invalid SD Card
Incompatible or Invalid (System or
Optional) SD Card fitted.
Network link failure
Network Interface name (ip address)
has been disconnected.
Network link operational
Network Interface name (ip address)
has been connected.
System warm start
System has been restarted (warm
start).
System cold start
System has restarted from power fail
(cold start).
SNMP Invalid community
Invalid community specified in SNMP
request.
Server operational
The license server is now operational.
Server failure
The license server is no longer
operational.
Trunk
VCM
Memory Card
Invalid Card
Free Capacity
Generic
Licence
Loopback
Phone Change
Generic
Licence Server
Licence Key Failure
Licence Key Failure
Loopback
Near end line loopback
Trunk number (name) [on expansion
module number] is in near end
loopback.
Near end payload loopback
Trunk number (name) [on expansion
module number] is in near end loopback
with payload.
Loopback off
Trunk number (name) [on expansion
module number] has no loopback.
Phone has been unplugged
The phone with id n has been removed
from extension extension (unit, port
number).
Phone has been plugged in
The phone with type type (id number)
has been plugged in for extension
extension (unit, port number).
Phone Change
Quality of Service QoS Monitoring
Manager Manager 8.1
Manager
If Enable RTCP Monitor on Port 5005 150 is selected, any monitored
calls that exceeds the set QoS Parameters 173 will cause an alarm.
Page 175
15-601011 Issue 25l (11 February 2011)
Type
Events
Event State
Message
Syslog
Basic Audit
Events as written to the system Audit Trail. Available on Syslog output
only.
System Shutdown
Running Backup
· Voicemail Pro Storage Alarms
The alarm threshold is adjustable through the Voicemail Pro client.
· Embedded Voicemail Storage Alarms
A disk full alarm is generated when the embedded voicemail memory card reaches 90% full. In addition a critical
space alarm is generated at 99% full (98% for the Small Office) and an OK alarm is generated when the disk space
returns to below 90% full.
· Loopback
This type of alarm is only available for systems with a United States locale.
Manager Manager 8.1
Manager
Page 176
15-601011 Issue 25l (11 February 2011)
Configuration Settings: System
5.3.9 SMTP
· IP Office 3.2+: SMTP can be used as the method of sending system alarms. The email destination is set as part of
the email alarms configured in System | System Events | Alarms 174 .
· IP Office 4.2+: SMTP can be used with Embedded Voicemail for Voicemail Email
by the user's Voicemail Email 267 address.
267 .
The voicemail destination is set
System | System Events | SMTP Configuration
Control Unit
SOE
Software Level
3.2+.
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
Mergeable
· IP Address: Default = 0.0.0.0
This field sets the IP address of the SMTP server being used to forward SNMP alarms sent by email.
· Port: Default = 25, Range = 0 to 65534.
This field set the destination port on the SMTP server.
· Email From Address: Default = Blank
This field set the sender address to be used with mailed alarms. Depending of the authentication requirements of the
SMTP server this may need to be a valid email address hosted by that server. Otherwise the SMTP email server may
need to be configured to support SMTP relay.
· Server Requires Authentication: Default = On
This field should be selected if the SMTP server being used requires authentication to allow the sending of emails. When
selected, the User Name and Password fields become available.
· User Name: Default = Blank
This field sets the user name to be used for SMTP server authentication.
· Password: Default = Blank
This field sets the password to be used for SMTP server authentication.
· Use Challenge Response Authentication (CRAM-MD5): Default = Off.
This field should be selected if the SMTP uses CRAM-MD5.
5.3.10 Twinning
These settings are used with Mobile Twinning, see the User | Mobility
twinning requires entry of a Mobility Features license.
293
tab for further details. The use of mobile
· Outgoing CLI Warning
Changing the outgoing CLI for calls requires the line provider to support that function. You must consult with
your line provider before attempting to change the outgoing CLI, failure to do so may result in loss of service.
If changing the outgoing CLI is allowed, most line providers required that the outgoing CLI used matches a
number valid for return calls on the same trunks. Use of any other number may cause calls to be dropped or
the outgoing CLI to be replaced with a valid number.
· On mobile twinned calls, if the original party information is used or a specific calling party information CLI is
set, that number overrides setting the outgoing CLI using short codes.
System | Twinning
Control Unit
SOE
Software Level
3.2+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Send Original Party Information for Mobile Twinning: Default = On
When on, the system will attempt to send the ICLID information provided with the incoming call to the twinning
destination.
· IP Office 5.0+: The SIP line Send Caller ID setting takes priority.
· IP Office 6.0+: The values on the System | Twinning
Manager Manager 8.1
Manager
177
tab override the SIP lines Send Caller ID setting.
Page 177
15-601011 Issue 25l (11 February 2011)
· Calling Party Information for Mobile Twinning: Default = Blank (Disabled), Range = Up to 32 digits.
This field is useable when Send Original Party Information for Mobile Twinning is off. Note that the number
entered here for use as the CLI must be a valid number for return calls to the same site. Some line providers may reject
calls that use a number that is not valid for return calls to the same site. In addition depending on the line type and line
provider settings the maximum number of digits may be limited.
Manager Manager 8.1
Manager
Page 178
15-601011 Issue 25l (11 February 2011)
Configuration Settings: System
5.3.11 SMDR
Using a specified IP address, the system can send a call record for each completed call.
IP Office 4.2+: The system can be configured to send SMDR call log records rather than CDR records. This removes the
need to have a the Manager Delta Server application installed on a PC.
IP Office 5+: Support for CDR format records has been dropped.
System | CDR
Control Unit
SOE
, IP403
Software Level
3.1 to 4.2.
Mergeable
Pre-3.2
, IP406 V1
, 3.2+
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Output: Default = No Output.
Select the type of call record that the Manager should output via IP.
· No Output
· CDR Only: Software level = 3.2 to 4.2 only.
Send call records using the CDR setting below.
· SMDR Only: Software level = 4.2+.
Send call records using the SMDR settings below.
SMDR Settings
These settings are shown if SMDR Only is selected as the Output. For further details refer to Appendix: SMDR
898 .
· IP Address: Default = 0.0.0.0 (Listen).
The destination IP address for SMDR records.
· The address 0.0.0.0 puts the control unit in listen mode on the specified TCP port. When a connection is made on
that port, all SMDR records in the buffer are provided.
· TCP Port: Default = 0.
The destination IP port for SMDR records.
· Records to Buffer: Default = 500, Range = 10 to 3000.
The system can cache up to 3000 SMDR records if it detects a communications failure with destination address. If the
cache is full, the system will begin discarding the oldest records for each new record. Pre-IP Office 4.2+ the maximum
number of records that can be buffered was 1500.
· Call Splitting for Diverts: Default = Off.
When enabled, for calls forwarded off-switch using an external trunk, the SMDR produces separate initial call and
forwarded call records. This applies for calls forwarded by forward unconditional, forward on no answer, forward on
busy, DND or mobile twinning. It also applies to calls forwarded off-switch by an incoming call route. The two sets of
records will have the same Call ID. The call time fields of the forward call record are reset from the moment of
forwarding on the external trunk. For full details see SMDR Call Records 898 .
CDR Settings
These settings are shown if CDR Only is selected as the Output. CDR is not supported for IP Office 5 and higher.
A number of different CDR formats can be selected to match the requirements of the call logging/accounting software
being used at the destination address. For further details refer to Appendix: CDR Records 910 .
· Enable intra-switch CDRs: Default = Off.
When on, includes CDR records for internal calls.
· Formatting Options
These fields are used to select the format and type of CDR records required. They must match the records expected by
the call logging application receiving the CDR records.
· Record Format: Default = Unformatted.
Allows selection from a number of common CDR record formats
910 .
· Record Options: Default = Enhanced.
Sets the options to include in the CDR record.
· Date Format: Default = Day\Month.
Sets the date format used in the CDR records.
· Call Detail Recorder Communications
This section sets the destination and method for sending of the CDR data.
Manager Manager 8.1
Manager
Page 179
15-601011 Issue 25l (11 February 2011)
· IP Address: Default = 0.0.0.0.
The destination IP address for CDR records.
· IP Port: Default = 0.
The destination IP port for CDR records.
· Max CDRs: Default = 500. Range = 0 to 1500.
The system can cache up to 1500 CDR records if it detects a communications failure with destination address. If the
cache is full, the system will begin discarding the oldest records for each new record. For system 4.2+ the maximum
number of records that can be buffered has been increased to 3000 for all systems other than the Small Office Edition.
· Use UDP: Default = Off (Use TCP)
When selected, this field switches the sending of CDR record packets to use UDP instead of TCP.
· If off, TCP is used. In this mode the system will resend missed or corrupted records using the standard TCP
protocol. Records are buffered until successfully sent.
· If on, UDP is used. In this mode the system will not resend missed or corrupt records. Also when using UDP, the
system is less likely to detect a communications failure which would triggered record caching.
Manager Manager 8.1
Manager
Page 180
15-601011 Issue 25l (11 February 2011)
Configuration Settings: System
5.3.12 VCM
This form allows adjustment of the operation of Voice Compression Modules (VCM's) installed in the control unit.
· The options for IP400 VCM controls are supported on IP400 systems from the IP Office 3.2/4.0 Q2 2007
Maintenance Releases onwards.
· The same controls are supported for IP400 VCM cards in IP500 systems from IP Office 4.1 Q1 2008
Maintenance Release onwards.
· The options for IP500 VCM controls are supported from IP Office 4.2 onwards.
Calls to and from IP devices can require conversion to the audio codec format being used by the IP device. For systems
this conversion is done by voice compression channels. These support the common IP audio codecs G711, G723 and
G729a. For details of how to add voice compression resources to a system, refer to the Manager Installation Manual.
When are Voice Compression Channels Used
The voice compression channels are used as follows.
· 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.
· 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 Device
No voice compression channels are required except for Small Office Edition Embedded Voicemail access.
· Music on Hold
This is provided from the system's TDM bus and therefore requires a voice compression channel when played to an
IP device.
· Conference Resources and IP Devices
Conferencing resources are managed by the conference chip which is on the system's 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 Device
Page calls require 1 voice compression channel per audio codec being used by any IP devices involved. The system
only uses G729a for page calls, therefore only requiring one channel but also only supporting pages to G729a
capable devices.
· Voicemail Services and IP Devices
Calls to the system voicemail servers are treated as data calls from the TDM bus. Therefore calls from an IP device
to voicemail require a voice compression channel.
· On the Small Office Edition, embedded voicemail uses voice compression channels for audio conversion.
Therefore all calls to Small Office Edition embedded voicemail require a voice compression channel and calls
from IP devices require two voice compression channels.
· Fax Calls
These are voice calls but with a slightly wider frequency range than spoken voice calls. The system only supports
fax across IP between systems with the Fax Transport option selected.
· SIP Calls
· SIP Line Call to/from Non-IP Devices
Voice compression channel required.
· Outgoing SIP Line Call from IP Device
No voice compression channel required.
· Incoming SIP Line Call to IP Device
Voice compression channel reserved until call connected.
· T38 Fax Calls (IP Office 5.0+)
The system supports T38 fax on SIP trunks and SIP extensions. Each T38 fax call uses a VCM channel.
Manager Manager 8.1
Manager
Page 181
15-601011 Issue 25l (11 February 2011)
· Within a Small Community Network, an T38 fax call can be converted to a call across across an H323 SCN lines
using the Fax Transport Support protocol. This conversion uses 2 VCM channels.
· In order use T38 Fax connection, the Equipment Classification of an analog extension connected to a fax
machine can be set Fax Machine. Additionally, a new short code feature Dial Fax is available.
Note: T3 IP devices must be configured to 20ms packet size for the above conditions to apply. If left configured for 10ms
packet size, a voice compression channel is needed for all tones and for non-direct media calls.
Measuring Channel Usage
The System Status Application can be used to display voice compression channel usage. Within the Resources section it
displays the number of channel in use. It also displays how often there have been insufficient channels available and the
last time such an event occurred.
Manager Manager 8.1
Manager
Page 182
15-601011 Issue 25l (11 February 2011)
Configuration Settings: System
These settings should only be adjusted under the guidance of Avaya support.
System | VCM
Control Unit
SOE
Software Level
3.2+ (Manager 3.2/4.0 Q2 2007 Maintenance Releases).
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
Echo
Echoes are typically generated by impedance mismatches when a signal is converted from one circuit type to another,
most notably from analog to IP. To resolve this issue, an estimated echo signal can be created from one output and then
subtracted from the input to hopefully remove any echo of the output.
· Echo Return Loss (dB): Default = 6dB. IP400 and IP500 VCM's.
This control allows adjustment of expected echo loss that should be used for the echo cancellation process. The options
are 0dB, 3dB, 6dB and 9dB.
Comfort Noise/NLP
A low level of comfort noise is required on digital lines during periods where there would normally be just silence. This is
necessary to reassure users that the call is still connected. These controls allow adjustment of the comfort noise generated
by the nonlinear processor (NLP) component of the VCM.
· Nonlinear Processor Mode: Default = Adaptive. IP400 and IP500 VCM's.
Allows selection of one of the following options:
· Adaptive
Adaptive means the comfort noise generated by the NLP will try to match background noise.
· Silence
Silence means the NLP will not generate comfort noise at all
· Disabled
Nonlinear processing is not applied, in which case some residual echo may be heard.
· NLP Comfort Noise Attenuation: Default = -9dB. IP500 VCM's only.
Options are -3dB, -6dB and -9dB.
· NLP Comfort Noise Ceiling: Default =-30dB. IP500 VCM's only.
Options are -30dB and -55dB.
Modem: Software level = 5.0+. IP500 VCM only.
For Fax relay, these settings allow adjustment of the TDM side operation applied to fax calls using VCM channels.
· Tx Level (dB): Default = -9dB, Range = 0 to -13dB.
· CD Threshold: Default = -43dB, Options = -26dB, -31dB or -43dB.
· No Activity Timeout (secs): Default = 30 seconds, Range = 10 to 600 seconds.
Manager Manager 8.1
Manager
Page 183
15-601011 Issue 25l (11 February 2011)
5.3.13 CCR
Customer Call Reporter (CCR) is an application that collects and displays information on the current status of hunt groups
and users that have been configured for Customer Call Reporter operation.
System | CCR
Control Unit
SOE
Software Level
4.2+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Busy Not Available Reason Codes
Agents who indicate that they are in a 'busy not available' state can be prompt to also indicate the reason for being in
that state. This menu allows descriptions for the possible reasons to be entered. The descriptions are then used in
menus from which the Agent's make selections when setting themselves into busy not available state and in reports on
Agent status.
· Code/Reason
Rows 1 to 8 can be used to contain descriptions of up to 31 characters each. Rows 0 and 9 are fixed as
Unsupported and Busy Not Available.
· For Customer Call Reporter 6.1, the reason codes are used to categorize calls in the Agent Time Card report.
Reason 1 is used to define lunch. All other reason codes are reported as breaks.
· Default After Call Work Time (seconds): Default = 10, Range = 10 to 999 seconds.
If an agent goes into the After Call Work (ACW) state, either automatically or manually, this field sets the duration of
that state after which it is automatically cleared. This duration can be overridden by the Agent's own setting (User |
Telephony | Supervisor Settings | After Call Work Time 276 ). During ACW state, hunt group calls are not presented to
the user.
Manager Manager 8.1
Manager
Page 184
15-601011 Issue 25l (11 February 2011)
Configuration Settings: System
5.4 Line Settings
The line settings shown in the system configuration will change according to the types of trunk cards installed
in the control unit or added using external expansion modules.
·
WARNING: Changing Trunk Cards
Changing the trunk card installed in an control unit will result in line settings for both the previous trunk card and
the currently installed trunk card. In order to change the trunk card type in a particular card slot, the configuration
must be defaulted. This does not apply if replacing an existing card with one of a higher capacity or fitting a trunk
card into a previously unused slot.
Trunk Incoming Call Routing
Each trunk type can be categorized as either an external trunk or internal trunk. The trunk type affects how the system
routes calls received on that trunk and the routing of calls to the trunk.
External Trunks
Trunk Types
Internal Trunks
· Analog trunks
· QSIG (T1, E1 or H323)
· T1 Robbed Bit
· BRI So
· E1R2
· H323
· ISDN BRI (excluding So)
· SCN
· ISDN PRI T1
· SES
· ISDN PRI E1
· SIP
Incoming Calls
Routed by
All incoming calls are routed by comparison
of call details for matches within the system
Incoming Call Routes 342 .
Line short codes are not used.
Incoming calls are routed by looking for a match
to the incoming digits in the following order:
· Extension number (including remote
numbers in a Small Community Network).
· Trunk short codes (excluding ? short code).
· System short codes (excluding ? short
code).
· Trunk ? short code.
· System ? short code.
Line Groups
Each system trunk (or in some cases individual trunk channels) can be configured with an Incoming Group ID and an
Outgoing Group ID. These group IDs are used as follows:
·
Incoming Call Routes 342
For incoming calls on external trunks, the Incoming Group ID of the trunk is one of the factors used to match the call
to one of the configured incoming call routes.
·
Short Codes - Routing Outgoing Calls 330
For dialing which matches a short code set to a Dial feature, the short codes Line Group ID can indicate either an
ARS form or to use a trunk from set to the same Outgoing Group ID. If the call is routed to an ARS form, the short
codes in the ARS form will specify the trunks to use by matching Outgoing Group ID.
Removing Unused Trunks
In cases where a trunk is not connected, it is important to ensure that the trunk is set as being Out of Service within the
configuration. This is especially important with analog trunks.
Failure to do this may cause the system to attempt to present outgoing calls to that trunk. Similarly, where the number of
channels subscribed is less than those supportable by the trunk type, the unsubscribed channels should be disabled.
· Clock Quality
Calls between systems using digital trunks (for example E1, E1R2, T1 PRI and BRI) require an common clock signal. The
system will try to obtain this clock signal from an exchange through one of its digital trunks. This is done by setting the
Clock Quality setting of that Line to Network. If there are multiple trunks to public exchanges, another trunk can be set
as Fallback should the primary clock signal fail. Other trunks should be set as Unsuitable.
Manager Manager 8.1
Manager
Page 185
15-601011 Issue 25l (11 February 2011)
Manager Manager 8.1
Manager
Page 186
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Line Settings
5.4.1 Analog Line
Analog trunks can be provided within the systems in the following ways. In all cases the physical ports are
labeled as Analog. For full details of installation refer to the Manager Installation manual.
· Using ICLID
The system can route incoming calls using the ICLID received with the call. However ICLID is not sent instantaneously.
On analog trunks set to Loop Start ICLID, there will be a short delay while the system waits for any ICLID digits before
it can determine where to present the call.
· Line Status
Analog line do not indicate call status other than whether the line is free or in use. Some system features, for example
retrieving unanswered forwards and making twinned calls make use of the call status indicated by digital lines. This is
not possible with analog lines. Once an analog line has been seized, the system has to assume that the call is connected
and treats it as having been answered.
· Dialing Complete
The majority of North-American telephony services use en-bloc dialing. Therefore the use of a ; is recommended at the
end of all dialing short codes that use an N. This is also recommended for all dialing where secondary dial tone short
codes are being used.
· Ground Start
This type of analog trunk is only supported through the Analog Trunk external expansion module.
Manager Manager 8.1
Manager
Page 187
15-601011 Issue 25l (11 February 2011)
5.4.1.1 Line
This tab covers general settings for an analog line.
Line | Line (Analog)
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Line Number
This parameter is not configurable, it is allocated by the system.
· Card/Module: Software level = 4.1+.
Indicates the card slot or expansion module being used for the trunk device providing the line.
· For IP400 control units: SLOT A on the control unit is shown as 1, SLOT B is shown as 2. Expansion modules are
numbered from 4 upwards, for example trunks on the module in Expansion Port 1 are shown as 4.
· For IP500 and IP500v2 control units: 1 to 4 match the slots on the front of the control unit from left to right.
Expansion modules are numbered from 5 upwards, for example trunks on the module in Expansion Port 1 are shown
as 5.
· Port: Software level = 4.1+.
Indicates the port on the Card/Module above to which the configuration settings relate.
· Network Type: Default = Public. Software level = 4.2+.
This option is available if Restrict Network Interconnect 160 (System | Telephony | Telephony 160 ) is enabled. It
allows the trunk to be set as either Public or Private. The system will return number unobtainable indication to any
attempt to connect a call on a Private trunk to a Public trunk or vice versa. This restriction includes transfers,
forwarding and conference calls.
· Due to the nature of this feature, its use is not recommended on systems also using any of the following other
system features: Small Community Networks 810 , VPNremote, Phone Manager telecommuter mode.
· Telephone Number
Used to remember the external telephone number of this line to assist with loop-back testing. For information only.
· Incoming Group ID: Default = 0, Range 0 to 99999.
The Incoming Group ID to which a line belongs is used to match it to incoming call routes in the system configuration.
The matching incoming call route is then used to route incoming calls. The same ID can be used for multiple lines.
· Outgoing Group ID: Default = 0, Range 0 to 99999.
Short codes that specify a number to dial also specify the line group to be used. The system will then seize a line with a
matching Outgoing Group ID. The same ID can be used for multiple lines.
· Outgoing Channels: Default = 1 (not changeable)
· Voice Channels: Default = 1 (not changeable)
· Prefix: Default = Blank
Enter the number to prefix to all incoming numbers for callback. This is useful if all users must dial a prefix to access an
outside line. The prefix is automatically placed in front of all incoming numbers so that users can dial the number back.
· For outgoing calls: Pre-IP Office 4.0: When a outgoing call is presented to the line with a leading digit to dial that
matches the Prefix, that digit is stripped from the number. IP Office 4.0+: The system does not strip the prefix,
therefore any prefixes not suitable for external line presentation should be stripped using short codes.
· National Prefix: Default = 0 (not changeable)
· Line Appearance ID: Default = Auto-assigned, Range = 2 to 9 digits. Software level = 3.0+.
Allows a number to be assigned to the line to identify it. On phone's that support call appearance buttons, a Line
Appearance button with the same number will show the status of the line and can be used to answer calls on the line.
The line appearance ID must be unique and not match any extension number.
· Admin: Default = In Service. Software level = 6.1.
This field allows a trunk to be taken out of service if required for maintenance or if the trunk is not connected.
Manager Manager 8.1
Manager
Page 188
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Line Settings
5.4.1.2 Analog Options
This tab covers analog line specific settings.
Line | Analog Options
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Channel:
Set by the system. Shown for information only.
· Trunk Type: Default = Loop Start
Sets the analog line type (Ground Start, Loop Start, Loop Start ICLID).
· Ground Start
Ground Start is only supported on trunks provided by the Analog Trunk 16 expansion module. It requires that the
module and the control unit are grounded. Refer to the Manager installation manual.
· Delay Waiting for Caller ID Information.
As the system can use ICLID to route incoming calls, on analog Loop Start ICLID trunks there is a few seconds delay
while ICLID is received before the call routing can be determined.
· Signaling Type: Default = DTMF Dialing
Sets the signaling method used on the line (DTMF Dialing or Pulse Dialing).
· Direction: Default = Both Directions
Sets the allowed direction of operation of the line (Incoming, Outgoing or Both Directions).
· Flash Pulse Width: Default = 500ms, Range = 0 to 2550ms.
Set the time interval for the flash pulse width.
· Await Dial Tone: Default = 3000ms, Range = 0 to 25500ms.
Sets how long the system should wait before dialing out.
· Echo Cancellation: Default = 16ms.
Allows settings of Off, 8, 16, 32, 64 and 128 milliseconds. The echo cancellation should only be adjusted as high as
required to remove echo problems. Setting it to a higher value than necessary can cause other distortions. Not used
with external expansion module trunks.
· Mains Hum Filter: Default = Off. Software level = IP500 4.2+.
If mains hum interference on the lines is detected or suspected, this settings can be used to attempt to remove that
interference. Useable with ATM16 trunks and IP500 ATM4U trunks. Options are Off, 50Hz or 60Hz.
· Impedance
Set the impedance used for the line. This field is only available for certain system locales. The range of values available
will depend on the system locale. The value used for Default is set by the system Locale.
· Brazil: Default = 900R
Adjustable between 600R and 900R as required by the line provider.
· Korea: Default = Default. Software level = 3.2 and 4.0 Q2 2007+.
In addition to the default impedance settings, an alternate set of impedance values can be selected.
· United States: Default = Default. Software level = 3.2 and 4.0 Q2 2007+.
In addition to the default impedance setting, the following alternate sets of impedance values Alternate1,
Alternate2 and Alternate3 can be selected.
· The following values used for Automatic Impedance Matching: 600+2150nF, 600, 900+2150nF, 900, 220+820||
115nF, 370+620||310nF, 270+750||150nF, 320+1050||230nF, 350+1000||210nF, 800+100||210nF.
· Quiet Line: IP500/IP500v2 only. Default = Off. Software level = 4.2+.
This field is only available for certain system locales (see below). The setting may be required to compensate for signal
loss on long lines.
· Automatic Balance Impedance Match: IP500/IP500v2. Software level = 4.2+.
These controls can be used to test the impedance of a line and to then display the best match resulting from the test.
Testing should be performed with the line connected but the system otherwise idle. To start testing click Start. The
systemwill then send a series of signals to the line and monitor the response, repeating this at each possible impedance
setting. Testing can be stopped at any time by clicking Stop. When testing is complete, Manager will display the best
match and ask whether that match should be used for the line. If Yes is selected, Manager will also ask whether the
match should be applied to all other analog lines provided by the same analog trunk card or module.
· IP Office 4.2+: Automatic Balance Impedance Matching and Quiet Line are only available for North American
locales.
Manager Manager 8.1
Manager
Page 189
15-601011 Issue 25l (11 February 2011)
· IP Office 6.0+: Automatic Balance Impedance Matching and Quiet Line are available for North American
locales and for the Bahrain 851 , Egypt 861 , Kuwait 872 , Morocco 874 , Oman 878 , Pakistan 879 , Qatar 883 , Saudi Arabia
885 , South Africa 887 , Turkey 892 , United Arab Emirates 893 and Customize 859 locales.
· Allow Analog Trunk to Trunk Connect: Default = Not selected (Off).
When not enabled, users cannot transfer or forward external calls back off-switch using an analog trunk if the calls was
originally made or received on another analog trunk. This prevents transfers to trunks that do not support disconnect
clear.
· BCC: Default = Not selected [Brazil locale only]
A collect call is a call at the receiver's expense and by his permission. If supported by the line provider, BCC (Block
Collect Call) can be used to bar collect calls.
· Secondary Dial Tone: Default = Off
Configures the use of secondary dial tone on analog lines. This is a different mechanism from secondary dial tone using
short codes. This method is used mainly within the Russian locale. When selected, the following additional settings are
accessible:
· Await time: Default = 3000ms, Range = 0 to 25500ms.
Used when secondary dial tone (above) is selected. Sets the delay.
· After n Digits: Default = 1, Range = 0 to 10.
Sets where in the dialing string, the delay for secondary dial tone, should occur.
· Matching Digit: Default =8, Range = 0 to 9.
The digit which, when first matched in the dialing string, will cause secondary dial tone delay.
· Long CLI Line: Default = Off
The CLI signal on some analog lines can become degraded and is not then correctly detected. If you are sure that CLI is
being provided but not detected, selecting this option may resolve the problem.
· Modem Enabled: Default = Off
The first analog trunk in a control unit can be set to modem operation (V32 with V42 error correction). This allows the
trunk to answer incoming modem calls and be used for system maintenance. When on, the trunk can only be used for
analog modem calls. The default system short code *9000* can be used to toggle this setting. For the Small Office
Edition control unit, when on, the control unit status LED flashes alternate red/green.
· Pulse Dialing
These settings are used for pulse dialing.
· Mark: Default = 80 (80ms), Range = 0 to 255.
Interval when DTMF signal is kept active during transmission of DTMF signals.
· Space: Default = 80 (80ms), Range = 0 to 255.
Interval of silence between DTMF signal transmissions.
· Inter-Digit Pause: Default = 500ms, Range = 0 to 2550ms.
Sets the pause between digits transmitted to the line.
· Ring Detection
· Ring Persistency: Default = Set according to system locale, Range = 0 to 2550ms.
The minimum duration of signal required to be recognized.
· Ring Off Maximum: Default = Set according to system locale, Range = 0 to 25500ms.
The time required before signaling is regarded as ended.
· Disconnect Clear
Disconnect clear (also known as Line Break or Reliable Disconnect) is a method used to signal from the line provider
that the call has cleared. The system also uses Tone Disconnect, which clears an analog call after 6 seconds of
continuous busy or NU tone, configured through the Busy Tone Detection 163 (System | Telephony | Tones & Music
163 ) settings.
· Enable: Default = On
Enables the use of disconnect clear.
· Units: Default = 500ms, Range = 0 to 2550ms.
This time must be less than the actual disconnect time period used by the line provider by at least 150ms.
· DTMF
These settings are used for DTMF dialing.
· On: Default = 40ms, Range = 0 to 255ms.
The width of the on pulses generated during DTMF dialing.
· Off: Default = 60ms, Range = 0 to 255ms.
The width of the off pulses generated during DTMF dialing.
· BCC Flash Pulse Width: [Brazil locale only] Default = 100 (1000ms), Range = 0 to 255.
Sets the BCC (Block collect call) flash pulse width.
· Gains:
These settings are used to adjust the perceived volume on all calls.
Manager Manager 8.1
Manager
Page 190
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Line Settings
· A -> D: Default = 0dB
Sets the analog to digital gain applied to the signal received from the trunk by the system. Range -4.0dB to +3.5dB
in 0.5dB steps. 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.
· D -> A: Default = 0dB
Sets the digital to analog gain applied to the signal from the system to the trunk. Range -4.0dB to +3.5dB in 0.5dB
steps.
· Voice Recording: Default = Low
Used to adjust the volume level of calls recorded by voicemail. Options are Low, Medium and High.
Manager Manager 8.1
Manager
Page 191
15-601011 Issue 25l (11 February 2011)
5.4.2 BRI Line
BRI trunks are provided by the installation of a BRI trunk card into the control unit. The cards are available in
different variants with either 2 or 4 physical ports. Each port supports 2 B-channels for calls. For full details of
installation refer to the Manager Installation manual.
Point-to-Point or Multipoint
BRI lines can be used in either Point-to-Point or Point-to-Multipoint mode. Point-to-Point lines are used when only one
device terminates a line in a customer's office. Point-to-Multipoint lines are used when more than one device may be used
on the line at the customer's premises. There are major benefits in using Point-to-Point lines:1. The exchange knows when the line/terminal equipment is down/dead, thus it will not offer calls down that line. If the
lines are Point-to-Multipoint, calls are always offered down the line and fail if there is no response from the terminal
equipment. So if you have two Point-to-Multipoint lines and one is faulty 50% of incoming calls fail.
2. You get a green LED on the Control Unit when the line is connected. With Point-to-Multipoint lines some exchanges will
drop layer 1/2 signals when the line is idle for a period.
3. The timing clock is locked to the exchange. If layer 1/2 signals disappear on a line then the Control Unit will switch to
another line, however this may result in some audible click when the switchover occurs.
The system's default Terminal Equipment Identifier (TEI) will normally allow it to work on Point-to-Point or Point-toMultipoint lines. However if you intend to connect multiple devices simultaneously to an BRI line, then the TEI should be
set to 127. With a TEI of 127, the control unit will ask the exchange to allocate a TEI for operation.
Note: When connected to some manufactures equipment, which provides an S0 interface (BRI), a defaulted Control Unit
will not bring up the ISDN line. Configuring the Control Unit to a TEI of 127 for that line will usually resolve this.
Manager Manager 8.1
Manager
Page 192
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Line Settings
5.4.2.1 BRI Line
Settings
Line | BRI Line
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Card/Module: Software level = 4.1+.
Indicates the card slot or expansion module being used for the trunk device providing the line.
· For IP400 control units: SLOT A on the control unit is shown as 1, SLOT B is shown as 2. Expansion modules are
numbered from 4 upwards, for example trunks on the module in Expansion Port 1 are shown as 4.
· For IP500 and IP500v2 control units: 1 to 4 match the slots on the front of the control unit from left to right.
Expansion modules are numbered from 5 upwards, for example trunks on the module in Expansion Port 1 are shown
as 5.
· Port: Software level = 4.1+.
Indicates the port on the Card/Module above to which the configuration settings relate.
· Line Number
This parameter is not configurable; it is allocated by the system.
· Line Sub Type: Default = ETSI
Select to match the particular line type provided by the line provider.
· S-Bus: Software level = 4.2+ (IP500 BRI daughter card only).
IP500 BRI daughter cards can be configured for So (S-Bus) operation for connection to ISDN terminal devices. Note
that this requires the addition of terminating resistors at both the system and remote ends, and the use of a suitable
cross-over cable. For full details refer to the Manager Installation manual.
· Network Type: Default = Public. Software level = 4.2+.
This option is available if Restrict Network Interconnect 160 (System | Telephony | Telephony 160 ) is enabled. It
allows the trunk to be set as either Public or Private. The system will return number unobtainable indication to any
attempt to connect a call on a Private trunk to a Public trunk or vice versa. This restriction includes transfers,
forwarding and conference calls.
· Due to the nature of this feature, its use is not recommended on systems also using any of the following other
system features: Small Community Networks 810 , VPNremote, Phone Manager telecommuter mode.
· Telephone Number:
Used to remember the external telephone number of this line to assist with loop-back testing. For information only.
· Incoming Group ID: Default = 0, Range 0 to 99999.
The Incoming Group ID to which a line belongs is used to match it to incoming call routes in the system configuration.
The matching incoming call route is then used to route incoming calls. The same ID can be used for multiple lines.
· Outgoing Group ID: Default = 0, Range 0 to 99999.
Short codes that specify a number to dial also specify the line group to be used. The system will then seize a line with a
matching Outgoing Group ID. The same ID can be used for multiple lines.
· Prefix: Default = Blank.
The prefix is used in the following ways:
· For incoming calls
The ISDN messaging tags indicates the call type (National, International or Unknown). If the call type is unknown,
then the number in the Prefix field is added to the ICLID.
· For outgoing calls
Pre-IP Office 4.0: When a outgoing call is presented to the line with a leading digit to dial that matches the Prefix,
that digit is stripped from the number. IP Office 4.0+: The prefix is not stripped, therefore any prefixes not suitable
for external line presentation should be stripped using short codes.
· National Prefix: Default = 0
This indicates the digits to be prefixed to a incoming national call. When a number is presented from ISDN as a
"national number" this prefix is added. For example 1923000000 is converted to 01923000000.
· International Prefix: Default = 00
This indicates the digits to be prefixed to an incoming international call. When a number is presented from ISDN as an
"international number" this prefix is added. For example 441923000000 is converted to 00441923000000.
· TEI: Default = 0
The Terminal Equipment Identifier. Used to identify each device connected to a particular ISDN line. For Point-to-Point
lines this is 0. It can also be 0 on a Point to Multipoint line, however if multiple devices are sharing a Point-to-Multipoint
line it should be set to 127 which results in the exchange allocating the TEI's to be used.
Manager Manager 8.1
Manager
Page 193
15-601011 Issue 25l (11 February 2011)
· Number of Channels: Default = 2. Range = 0 to 2.
Defines the number of operational channels that are available on this line.
· Outgoing Channels: Default = 2. Range = 0 to 2.
This defines the number of channels available, on this line, for outgoing calls. This should normally be the same as
Number of Channels field, but can be reduced to ensure incoming calls cannot be blocked by outgoing calls.
· Voice Channels: Default = 2. Range = 0 to 2.
The number of channels available for voice use.
· Data Channels: Default = 2. Range = 0 to 2.
The number of channels available for data use. If left blank, the value is 0.
· Clock Quality: Default = Network
Refer to the Manager Installation Manual for full details. This option sets whether the system should try to take its clock
source for call synchronization and signalling from this line. Preference should always be given to using the clock source
from a central office exchange if available by setting at least one exchange line to Network.
· If multiple lines are set as Network, the order in which those lines are used is described in the Manager
Installation Manual. If additional lines are available, Fallback can be used to specify a clock source to use should
the Network source not be available.
· Lines from which the clock source should not be taken should be set as Unsuitable.
· If no clock source is available, the system uses its own internal 8KHz clock source.
· In scenarios where several systems are network via digital trunk lines, care must be taken to ensure that all the
systems use the same clock source. The current source being used by a system is reported within the System
Status Application.
· Add 'Not-end-to-end ISDN' Information Element: Default = Never*. Software level = 4.2+.
Sets whether the optional 'Not end-to-end ISDN' information element should be added to outgoing calls on the line. The
options are Never, Always or POTS (only if the call was originated by an analog extension). *The default is Never
except for the following locales; for Italy the default is POTS, for New Zealand the default is Always.
· Supports Partial Rerouting: Default = Off. Software level = 4.0+.
Partial rerouting (PR) is an ISDN feature. It is supported on external (non-network and QSIG) ISDN exchange calls.
When an external call is transferred to another external number, the transfer is performed by the ISDN exchange and
the channels to the system are freed. Use of this service may need to be requested from the line provider and may
incur a charge.
· Force Number Plan to ISDN: Default = Off. Software level = 4.2+.
This option is only configurable when Support Partial Rerouting is also enabled. When selected, the plan/type
parameter for Partial Rerouting is changed from Unknown/Unknown to ISDN/Unknown. For IP Office 4.0 and
4.1 the plan/type is fixed as Unknown/Unknown. The use of this setting will depend on line provider
requirements for partial rerouting.
· Send Redirecting Number: Default = Off. Software level = 6.0+, IP500/IP500v2 only.
This option can be used on ISDN trunks where the redirecting service is supported by the trunk provider. Where
supported, on twinned calls the caller ID of the original call is passed through to the twinning destination. This option is
only used for twinned calls.
· Support Call Tracing: Default = Off. Software level = 4.0+.
The system supports the triggering of malicious caller ID (MCID) tracing at the ISDN exchange. Use of this feature
requires liaison with the ISDN service provider and the appropriate legal authorities to whom the call trace will be
passed. The user will also need to be enabled for call tracing and be provider with either a short code or programmable
button to activate MCID call trace. Refer to Malicious Call Tracing 753 in the Telephone Features section for full details.
· Active CCBS Support: Default = Off. Software level = 4.0+.
Call completion to a busy subscriber (CCBS). It allows automatic callback to be used on outgoing ISDN calls when the
destination is busy. This feature can only be used on point-to-point trunks. Use of this service may need to be requested
from the line provider and may incur a charge.
· Passive CCBS: Default = Off. Software level = 4.0+.
· Cost Per Charging Unit: Software level = 4.0+.
Advice of charge (AOC) information can be display on T3/T3IP phones and output in SMDR 898 . The information is
provided in the form of charge units. This setting is used to enter the call cost per charging unit set by the line provider.
The values are 1/10,000th of a currency unit. For example if the call cost per unit is £1.07, a value of 10700 should be
set on the line. Refer to Advice of Charge 740 in the Telephone Features section.
Manager Manager 8.1
Manager
Page 194
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Line Settings
5.4.2.2 Channels
This tab allows settings for individual channels within the trunk to be adjusted. To edit a channel either double-click on it
or click the channel and then select Edit.
To edit multiple channels at the same time, select the required channels using Ctrl or Shift and then click Edit. When
editing multiple channels, fields that must be unique such as Line Appearance ID are not shown.
Line | Channels (BRI)
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Line Appearance ID: Default = Auto-assigned, Range = 2 to 9 digits. Software level = 3.0+.
Used for configuring Line Appearances with button programming. The line appearance ID must be unique and not match
any extension number. Line appearance is not supported for trunks set to QSIG operation and is not recommended for
trunks be used for DID.
Manager Manager 8.1
Manager
Page 195
15-601011 Issue 25l (11 February 2011)
5.4.3 E1 Line
PRI trunks are provided by the installation of a PRI trunk card into the control unit. IP400 PRI cards are available
in E1, E1R2 and T1/US PRI variants. The IP500 PRI-U trunk card can be configured (see below) to one of those
line types. The cards are also available with either 1 or 2 physical ports. The number of B-channels supported by
each physical port depends on the line type of the card.
· E1: 30 B-channels and 1 D-channel per port.
· T1: 24 B-channels per port.
· US PRI: 23 B-channels and 1 D-channel per port.
· E1-R2: 30 B-channels and 1 D-channel per port.
The Small Office Edition control unit only supports a 1 single port IP400 T1 PRI trunk card. For an IP406 V2
control unit, dual port PRI trunk cards are only supported in Slot A. For full details of installation refer to the
Manager Installation manual.
· Calls received on IP, S0 and QSIG trunks do not use incoming call routes. Routing for these is based on
incoming number received as if dialed on-switch. Line short codes on those trunks can be used to modify the
incoming digits.
IP500 PRI-U Trunk Card Line Type
The IP500 PRI-U card can be configured to support either E1, T1 or E1-R2 PRI line types. To select the line type required,
right-click on the line in the group or navigation pane and select Change Universal PRI Card Line Type.
The IP500/IP500v2 supports 8 B-channels on any IP500 PRI-U card fitted. Additional B-channels up to the full capacity of
IP500 PRI-U ports installed require licenses added to the configuration. D-channels are not affected by licensing.
· For ETSI and QSIG trunks, license instances are consumed by the number of calls in progress on B-channels.
· For T1, E1R2 and ETSI CHI trunks, licenses instances are consumed by the channels set as in service.
Manager Manager 8.1
Manager
Page 196
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Line Settings
5.4.3.1 PRI Line
· Calls received on IP, S0 and QSIG trunks do not use incoming call routes. Routing for these is based on incoming
number received as if dialed on-switch. Line short codes on those trunks can be used to modify the incoming digits.
Line | PRI Line (E1)
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Line Number
This parameter is not configurable; it is allocated by the system.
· Line Sub Type:
Select to match the particular line type provided by the line provider. E1 PRI trunks support ETSI, ETSI CHI, QSIG A
or QSIG B.
· ETSI CHI is used to send the channel allocation ID (CHI) in the call setup signalling. This is a request to use a
particular B-channel rather than use any B-channel allocated by the central office exchange.
· QSIG trunks and H323 IP trunks are not supported on IP500 and IP500v2 systems without IP500 Voice
Networking 833 licenses.
· Card/Module: Software level = 4.1+.
Indicates the card slot or expansion module being used for the trunk device providing the line.
· For IP400 control units: SLOT A on the control unit is shown as 1, SLOT B is shown as 2. Expansion modules are
numbered from 4 upwards, for example trunks on the module in Expansion Port 1 are shown as 4.
· For IP500 and IP500v2 control units: 1 to 4 match the slots on the front of the control unit from left to right.
Expansion modules are numbered from 5 upwards, for example trunks on the module in Expansion Port 1 are shown
as 5.
· Port: Software level = 4.1+.
Indicates the port on the Card/Module above to which the configuration settings relate.
· Network Type: Default = Public. Software level = 4.2+.
This option is available if Restrict Network Interconnect 160 (System | Telephony | Telephony 160 ) is enabled. It
allows the trunk to be set as either Public or Private. The system will return number unobtainable indication to any
attempt to connect a call on a Private trunk to a Public trunk or vice versa. This restriction includes transfers,
forwarding and conference calls.
· Due to the nature of this feature, its use is not recommended on systems also using any of the following other
system features: Small Community Networks 810 , VPNremote, Phone Manager telecommuter mode.
· Telephone Number:
Used to remember the external telephone number of this line to assist with loop-back testing. For information only.
· Channel Allocation: Default = 30->1. Software level = 4.2+.
For lines set to ETSI CHI, this option allows the system to select the default order in which channels should be used for
outgoing calls. Typically this is set as the opposite of the default order in which the central office exchange uses
channels for incoming calls.
· Incoming Group ID: Default = 0, Range 0 to 99999.
The Incoming Group ID to which a line belongs is used to match it to incoming call routes in the system configuration.
The matching incoming call route is then used to route incoming calls. The same ID can be used for multiple lines.
· Outgoing Group ID: Default = 0, Range 0 to 99999.
Short codes that specify a number to dial also specify the line group to be used. The system will then seize a line with a
matching Outgoing Group ID. The same ID can be used for multiple lines.
· IP Office 4.2+: For lines set to the Line Sub Type of ETSI CHI, the Incoming Group ID is set as part of the
individual channel 201 settings.
· Prefix: Default = Blank.
The prefix is used in the following ways:
· For incoming calls
The ISDN messaging tags indicates the call type (National, International or Unknown). If the call type is unknown,
then the number in the Prefix field is added to the ICLID.
· For outgoing calls
Pre-IP Office 4.0: When a outgoing call is presented to the line with a leading digit to dial that matches the Prefix,
that digit is stripped from the number. IP Office 4.0+: The prefix is not stripped, therefore any prefixes not suitable
for external line presentation should be stripped using short codes.
Manager Manager 8.1
Manager
Page 197
15-601011 Issue 25l (11 February 2011)
· National Prefix: Default = 0
This indicates the digits to be prefixed to a incoming national call. When a number is presented from ISDN as a
"national number" this prefix is added. For example 1923000000 is converted to 01923000000.
· International Prefix: Default = 00
This indicates the digits to be prefixed to an incoming international call. When a number is presented from ISDN as an
"international number" this prefix is added. For example 441923000000 is converted to 00441923000000.
· TEI: Default = 0
The Terminal Equipment Identifier. Used to identify each Control Unit connected to a particular ISDN line. For Point to
Point lines this is typically (always) 0. It can also be 0 on a Point to Multi-Point line, however if multiple devices are
sharing a Point to Multi-Point line it should be set to 127 which results in the exchange deciding on the TEI's to be used.
· Number of Channels
Defines the number of operational channels that are available on this line. Up to 30 for E1 PRI, 23 for T1 PRI.
· Outgoing Channels
This defines the number of channels available, on this line, for outgoing calls. This should normally be the same as
Number of Channels field, but can be reduced to ensure incoming calls cannot be blocked by outgoing calls. Only
available when the Line Sub Type is set to ETSI.
· Voice Channels
The number of channels available for voice use. Only available when the Line Sub Type is set to ETSI.
· Data Channels
The number of channels available for data use. Only available when the Line Sub Type is set to ETSI.
· CRC Checking: Default = On
Switches CRC on or off.
· Line Signalling: Default = CPE
This option is not used for lines where the Line SubType is set to QSIG. Select either CPE (customer premises
equipment) or CO (central office). The CO feature is intended to be used primarily as a testing aid. It allows PRI lines to
be tested in a back-to-back configuration, using crossover cables.
· The CO feature operates on this line type by modifying the way in which incoming calls are disconnected for system
configuration in Brazil and Argentina. In these locales, the CO setting uses Forced-Release instead of Clear-Back to
disconnect incoming calls. The Brazilian Double-Seizure mechanism, used to police Collect calls, is also disabled in CO
mode.
· Clock Quality: Default = Network
Refer to the Manager Installation Manual for full details. This option sets whether the system should try to take its clock
source for call synchronization and signalling from this line. Preference should always be given to using the clock source
from a central office exchange if available by setting at least one exchange line to Network.
· If multiple lines are set as Network, the order in which those lines are used is described in the Manager
Installation Manual. If additional lines are available, Fallback can be used to specify a clock source to use should
the Network source not be available.
· Lines from which the clock source should not be taken should be set as Unsuitable.
· If no clock source is available, the system uses its own internal 8KHz clock source.
· In scenarios where several systems are network via digital trunk lines, care must be taken to ensure that all the
systems use the same clock source. The current source being used by a system is reported within the System
Status Application.
· Add 'Not-end-to-end ISDN' Information Element: Default = Never*. Software level = 4.2+.
Sets whether the optional 'Not end-to-end ISDN' information element should be added to outgoing calls on the line. The
options are Never, Always or POTS (only if the call was originated by an analog extension). *The default is Never
except for the following locales; for Italy the default is POTS, for New Zealand the default is Always.
· Supports Partial Rerouting: Default = Off. Software level = 4.0+.
Partial rerouting (PR) is an ISDN feature. It is supported on external (non-network and QSIG) ISDN exchange calls.
When an external call is transferred to another external number, the transfer is performed by the ISDN exchange and
the channels to the system are freed. Use of this service may need to be requested from the line provider and may
incur a charge.
· Force Number Plan to ISDN: Default = Off. Software level = 4.2+.
This option is only configurable when Support Partial Rerouting is also enabled. When selected, the plan/type
parameter for Partial Rerouting is changed from Unknown/Unknown to ISDN/Unknown. For IP Office 4.0 and
4.1 the plan/type is fixed as Unknown/Unknown. The use of this setting will depend on line provider
requirements for partial rerouting.
· Send Redirecting Number: Default = Off. Software level = 6.0+, IP500/IP500v2 only.
This option can be used on ISDN trunks where the redirecting service is supported by the trunk provider. Where
supported, on twinned calls the caller ID of the original call is passed through to the twinning destination. This option is
only used for twinned calls.
Manager Manager 8.1
Manager
Page 198
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Line Settings
· Support Call Tracing: Default = Off. Software level = 4.0+.
The system supports the triggering of malicious caller ID (MCID) tracing at the ISDN exchange. Use of this feature
requires liaison with the ISDN service provider and the appropriate legal authorities to whom the call trace will be
passed. The user will also need to be enabled for call tracing and be provider with either a short code or programmable
button to activate MCID call trace. Refer to Malicious Call Tracing 753 in the Telephone Features section for full details.
· Active CCBS Support: Default = Off. Software level = 4.0+.
Call completion to a busy subscriber (CCBS). It allows automatic callback to be used on outgoing ISDN calls when the
destination is busy. This feature can only be used on point-to-point trunks. Use of this service may need to be requested
from the line provider and may incur a charge.
· Passive CCBS: Default = Off. Software level = 4.0+.
· Cost Per Charging Unit: Software level = 4.0+.
Advice of charge (AOC) information can be display on T3/T3IP phones and output in SMDR 898 . The information is
provided in the form of charge units. This setting is used to enter the call cost per charging unit set by the line provider.
The values are 1/10,000th of a currency unit. For example if the call cost per unit is £1.07, a value of 10700 should be
set on the line. Refer to Advice of Charge 740 in the Telephone Features section.
· Admin: Default = In Service. Software level = 6.1.
This field allows a trunk to be taken out of service if required for maintenance or if the trunk is not connected.
The following fields are shown for a US T1 trunk card set to ETSI or QSIG operation. These cards have the same settings
E1 PRI trunk cards set to ETSI or QSIG but only support 23 channels.
· CSU Operation
Tick this field to enable the T1 line to respond to loop-back requests from the line.
· Haul Length: Default = 0-115 feet
Sets the line length to a specific distance.
· Channel Unit: Default = Foreign Exchange
This field should be set to match the channel signaling equipment provided by the Central Office. The options are
Foreign Exchange, Special Access or Normal.
Manager Manager 8.1
Manager
Page 199
15-601011 Issue 25l (11 February 2011)
5.4.3.2 Short Codes
Line short codes can be applied to the digits received with incoming call. The stage at which they are applied also varies
depending on the trunk type.
The line Short Code tab is shown for internal trunk types: QSIG (T1, E1, H323), BRI S0, H323, SCN, SES. Incoming
calls are routed by looking for a match to the incoming digits in the following order:
· Extension number (including remote numbers in a Small Community Network).
· Line short codes (excluding ? short code).
· System short codes (excluding ? short code).
· Line ? short code.
· System ? short code.
Line | Short Codes
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
Short codes can be added and edited using the Add, Remove and Edit buttons. Alternatively you can right-click on the
list of existing short code to add and edit short codes.
Manager Manager 8.1
Manager
Page 200
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Line Settings
5.4.3.3 Channels
This tab allows settings for individual channels within the trunk to be adjusted. To edit a channel either double-click on it
or click the channel and then select Edit.
To edit multiple channels at the same time, select the required channels using Ctrl or Shift and then click Edit. When
editing multiple channels, fields that must be unique such as Line Appearance ID are not shown.
Line | Channels (E1 PRI)
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Line Appearance ID: Default = Auto-assigned, Range = 2 to 9 digits. Software level = 3.0+.
Used for configuring Line Appearances with button programming. The line appearance ID must be unique and not match
any extension number. Line appearance is not supported for trunks set to QSIG operation and is not recommended for
trunks be used for DID.
· IP Office 4.2+: If the trunk Line Sub Type is set to ETSI CHI, outgoing line appearance calls must use the
correspond channel.
IP Office 4.2+: The following additional fields are shown for lines where the Line Sub Type is set to ETSI CHI.
· Incoming Group ID: Default = 0, Range 0 to 99999.
The Incoming Group ID to which a line belongs is used to match it to incoming call routes in the system configuration.
The matching incoming call route is then used to route incoming calls. The same ID can be used for multiple lines.
· Outgoing Group ID: Default = 0, Range 0 to 99999.
Short codes that specify a number to dial also specify the line group to be used. The system will then seize a line with a
matching Outgoing Group ID. The same ID can be used for multiple lines.
· Direction: Default = Bothways
Controls the direction of calls allowed on the channel. Options are Bothways, Incoming or Outgoing.
· Bearer: Default = Any.
Allows selection of the type of call that can use the channel. Options are Any, Data or Voice.
· Admin: Default = Out of Service.
This field can be used to indicate whether the channel is in use or not. On trunks where only a limited number of
channels have been requested from the trunk provider (known as sub-equipped trunks), those channels not provided
should be set as Out of Service. For channels that are available but are temporarily not being used select
Maintenance.
· Tx Gain: Default = 0dB, Range = -10dBb to +5dB.
The transmit gain in dB.
· Rx Gain: Default = 0dB, Range = -10dBb to +5dB.
The receive gain in dB.
Manager Manager 8.1
Manager
Page 201
15-601011 Issue 25l (11 February 2011)
5.4.4 E1R2 Line
PRI trunks are provided by the installation of a PRI trunk card into the control unit. IP400 PRI cards are available
in E1, E1R2 and T1/US PRI variants. The IP500 PRI-U trunk card can be configured (see below) to one of those
line types. The cards are also available with either 1 or 2 physical ports. The number of B-channels supported by
each physical port depends on the line type of the card.
· E1: 30 B-channels and 1 D-channel per port.
· T1: 24 B-channels per port.
· US PRI: 23 B-channels and 1 D-channel per port.
· E1-R2: 30 B-channels and 1 D-channel per port.
The Small Office Edition control unit only supports a 1 single port IP400 T1 PRI trunk card. For an IP406 V2
control unit, dual port PRI trunk cards are only supported in Slot A. For full details of installation refer to the
Manager Installation manual.
· Calls received on IP, S0 and QSIG trunks do not use incoming call routes. Routing for these is based on
incoming number received as if dialed on-switch. Line short codes on those trunks can be used to modify the
incoming digits.
IP500 PRI-U Trunk Card Line Type
The IP500 PRI-U card can be configured to support either E1, T1 or E1-R2 PRI line types. To select the line type required,
right-click on the line in the group or navigation pane and select Change Universal PRI Card Line Type.
The IP500/IP500v2 supports 8 B-channels on any IP500 PRI-U card fitted. Additional B-channels up to the full capacity of
IP500 PRI-U ports installed require licenses added to the configuration. D-channels are not affected by licensing.
· For ETSI and QSIG trunks, license instances are consumed by the number of calls in progress on B-channels.
· For T1, E1R2 and ETSI CHI trunks, licenses instances are consumed by the channels set as in service.
Manager Manager 8.1
Manager
Page 202
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Line Settings
5.4.4.1 E1-R2 Options (Line)
Line | Line (E1-R2)
Control Unit
SOE
Software Level
1.4+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Card/Module: Software level = 4.1+.
Indicates the card slot or expansion module being used for the trunk device providing the line.
· For IP400 control units: SLOT A on the control unit is shown as 1, SLOT B is shown as 2. Expansion modules are
numbered from 4 upwards, for example trunks on the module in Expansion Port 1 are shown as 4.
· For IP500 and IP500v2 control units: 1 to 4 match the slots on the front of the control unit from left to right.
Expansion modules are numbered from 5 upwards, for example trunks on the module in Expansion Port 1 are shown
as 5.
· Port: Software level = 4.1+.
Indicates the port on the Card/Module above to which the configuration settings relate.
· Network Type: Default = Public. Software level = 4.2+.
This option is available if Restrict Network Interconnect 160 (System | Telephony | Telephony 160 ) is enabled. It
allows the trunk to be set as either Public or Private. The system will return number unobtainable indication to any
attempt to connect a call on a Private trunk to a Public trunk or vice versa. This restriction includes transfers,
forwarding and conference calls.
· Due to the nature of this feature, its use is not recommended on systems also using any of the following other
system features: Small Community Networks 810 , VPNremote, Phone Manager telecommuter mode.
· Line Number:
Allocated by the system.
· Line SubType: Default = E1-R2
Supported options are E1-R2, ETSI, QSIGA or QSIGB.
· QSIG trunks and H323 IP trunks are not supported on IP500 and IP500v2 systems without IP500 Voice
Networking 833 licenses.
· Channel Allocation: Default = 30 -> 1
The order, 30 -> 1 or 1 -> 30, in which channels are used.
· Country (Locale): Default = Mexico.
Select the locale that matches the area of usage. Note that changing the locale will return the MFC Group settings to the
defaults for the selected locale. Currently supported locales Argentina, Brazil, China, India, Korea, Mexico and
None.
· Admin: Default = In Service. Software level = 6.1.
This field allows a trunk to be taken out of service if required for maintenance or if the trunk is not connected.
The table at the base of the form displays the settings for the individual channels provided by the line. For details of the
channel settings see Edit Channel (E1-R2) 204 .
To edit a channel, either double-click on it or right-click and select Edit. This will display the Edit Channel 204 dialog box.
To edit multiple channels at the same time select the channels whilst pressing the Shift or Ctrl key. Then right-click and
select Edit.
Manager Manager 8.1
Manager
Page 203
15-601011 Issue 25l (11 February 2011)
5.4.4.2 Channels
This tab allows settings for individual channels within the trunk to be adjusted. To edit a channel, select the required
channel or channels and click Edit.
Line | Channels (E1-R2)
Control Unit
SOE
Software Level
1.4+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
The channel settings are split into two sub-tabs, E1R2 Edit Channel and Timers.
E1R2 Edit Channel Settings
· Channel
The channel or channels being edited.
· Incoming Group ID: Default = 0, Range 0 to 99999.
The Incoming Group ID to which a line belongs is used to match it to incoming call routes in the system configuration.
The matching incoming call route is then used to route incoming calls. The same ID can be used for multiple lines.
· Outgoing Group ID: Default = 0, Range 0 to 99999.
Short codes that specify a number to dial also specify the line group to be used. The system will then seize a line with a
matching Outgoing Group ID. The same ID can be used for multiple lines.
· Direction: Default = Both Directions
The direction of calls on the channel (Incoming, Outgoing or Both Directions).
· Bearer: Default = Any
The type of traffic carried by the channel (Voice, Data or Any).
· Line Signaling Type: Default = R2 Loop Start
The signaling type used by the channel. Current supported options are: R2 Loop Start, R2 DID, R2 DOD, R2 DIOD,
Tie Immediate Start, Tie Wink Start, Tie Delay Dial, Tie Automatic, WAN Service and Out of Service.
· Dial Type: Default = MFC Dialing
The type of dialing supported by the channel; MFC Dialing, Pulse Dialing or DTMF Dialing.
Timers Settings
This sub-tab displays the various timers provided for E1-R2 channels. These should only be adjusted when required to
match the line provider's settings.
Manager Manager 8.1
Manager
Page 204
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Line Settings
5.4.4.3 MFC Group
These tabs show the parameter assigned to each signal in an MFC group. The defaults are set according to the Country
(Locale) on the Line tab. All the values can be returned to default by the Default All button on the Advanced tab.
To change a setting either double-click on it or right-click and select Edit.
Line | MFC Group (E1-R2)
Control Unit
SOE
Software Level
1.4+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
5.4.4.4 Advanced
Line | Advanced (E1-R2)
Control Unit
SOE
Software Level
1.4+.
Mergeable
.
· Zero Suppression: Default = HDB3
Selects the method of zero suppression used (HDB3 or AMI).
· Clock Quality: Default = Network
Refer to the Manager Installation Manual for full details. This option sets whether the system should try to take its clock
source for call synchronization and signalling from this line. Preference should always be given to using the clock source
from a central office exchange if available by setting at least one exchange line to Network.
· If multiple lines are set as Network, the order in which those lines are used is described in the Manager
Installation Manual. If additional lines are available, Fallback can be used to specify a clock source to use should
the Network source not be available.
· Lines from which the clock source should not be taken should be set as Unsuitable.
· If no clock source is available, the system uses its own internal 8KHz clock source.
· In scenarios where several systems are network via digital trunk lines, care must be taken to ensure that all the
systems use the same clock source. The current source being used by a system is reported within the System
Status Application.
· Pulse Metering Bit: Default = A Bit
Sets which bit should be used to indicate the pulse metering signal; A Bit, B Bit or C Bit.
· Line Signaling: Default = CPE
Select either CPE or CO. The CO feature is intended to be used primarily as a testing aid. It allows T1 and E1 lines to be
tested in a back-to-back configuration, using crossover (QSIG) cables.
· The CO feature operates by modifying the way in which incoming calls are disconnected for system configuration in
Brazil and Argentina. In these locales, the CO setting uses Forced-Release instead of Clear-Back to disconnect
incoming calls. The Brazilian Double-Seizure mechanism used to police Collect calls, is also disabled in CO mode.
· Incoming Routing Digits: Default = 4
Sets the number of incoming digits used for incoming call routing.
· CRC Checking: Default = Ticked (On)
Switches CRC on or off.
· Default All Group Settings
Default the MFC Group tab settings.
· Line Signaling Timers:
To edit one of these timers, either double-click on the timer or right-click on a timer and select the action required.
Manager Manager 8.1
Manager
Page 205
15-601011 Issue 25l (11 February 2011)
5.4.5 T1 Line
PRI trunks are provided by the installation of a PRI trunk card into the control unit. IP400 PRI cards are available
in E1, E1R2 and T1/US PRI variants. The IP500 PRI-U trunk card can be configured (see below) to one of those
line types. The cards are also available with either 1 or 2 physical ports. The number of B-channels supported by
each physical port depends on the line type of the card.
· E1: 30 B-channels and 1 D-channel per port.
· T1: 24 B-channels per port.
· US PRI: 23 B-channels and 1 D-channel per port.
· E1-R2: 30 B-channels and 1 D-channel per port.
The Small Office Edition control unit only supports a 1 single port IP400 T1 PRI trunk card. For an IP406 V2
control unit, dual port PRI trunk cards are only supported in Slot A. For full details of installation refer to the
Manager Installation manual.
· Calls received on IP, S0 and QSIG trunks do not use incoming call routes. Routing for these is based on
incoming number received as if dialed on-switch. Line short codes on those trunks can be used to modify the
incoming digits.
IP500 PRI-U Trunk Card Line Type
The IP500 PRI-U card can be configured to support either E1, T1 or E1-R2 PRI line types. To select the line type required,
right-click on the line in the group or navigation pane and select Change Universal PRI Card Line Type.
The IP500/IP500v2 supports 8 B-channels on any IP500 PRI-U card fitted. Additional B-channels up to the full capacity of
IP500 PRI-U ports installed require licenses added to the configuration. D-channels are not affected by licensing.
· For ETSI and QSIG trunks, license instances are consumed by the number of calls in progress on B-channels.
· For T1, E1R2 and ETSI CHI trunks, licenses instances are consumed by the channels set as in service.
· Dialing Complete
The majority of North-American telephony services use en-bloc dialing. Therefore the use of a ; is recommended at the
end of all dialing short codes that use an N. This is also recommended for all dialing where secondary dial tone short
codes are being used.
Manager Manager 8.1
Manager
Page 206
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Line Settings
5.4.5.1 Line
Line | Line (T1)
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Line Number:
Allocated by the system.
· Card/Module: Software level = 4.1+.
Indicates the card slot or expansion module being used for the trunk device providing the line.
· For IP400 control units: SLOT A on the control unit is shown as 1, SLOT B is shown as 2. Expansion modules are
numbered from 4 upwards, for example trunks on the module in Expansion Port 1 are shown as 4.
· For IP500 and IP500v2 control units: 1 to 4 match the slots on the front of the control unit from left to right.
Expansion modules are numbered from 5 upwards, for example trunks on the module in Expansion Port 1 are shown
as 5.
· Port: Software level = 4.1+.
Indicates the port on the Card/Module above to which the configuration settings relate.
· Network Type: Default = Public. Software level = 4.2+.
This option is available if Restrict Network Interconnect 160 (System | Telephony | Telephony 160 ) is enabled. It
allows the trunk to be set as either Public or Private. The system will return number unobtainable indication to any
attempt to connect a call on a Private trunk to a Public trunk or vice versa. This restriction includes transfers,
forwarding and conference calls.
· Due to the nature of this feature, its use is not recommended on systems also using any of the following other
system features: Small Community Networks 810 , VPNremote, Phone Manager telecommuter mode.
· Line Sub Type: Default = T1
Set to T1 for a T1 line. For PRI see Line Form (US PRI)
211 .
If set to ETSI, QSIG A or QSIG B see Line (E1)
197 .
· Channel Allocation: Default = 24 -> 1
The order, 24 to 1 or 1 to 24, in which channels are used.
· Prefix: Default = Blank
Enter the number to prefix to all incoming numbers for callback. This is useful if all users must dial a prefix to access an
outside line. The prefix is automatically placed in front of all incoming numbers so that users can dial the number back.
· Framing: Default = ESF
Selects the type of signal framing used (ESF or D4).
· Zero Suppression: Default = B8ZS
Selects the method of zero suppression used (B8ZS or AMI ZCS).
· Clock Quality: Default = Network
Refer to the Manager Installation Manual for full details. This option sets whether the system should try to take its clock
source for call synchronization and signalling from this line. Preference should always be given to using the clock source
from a central office exchange if available by setting at least one exchange line to Network.
· If multiple lines are set as Network, the order in which those lines are used is described in the Manager
Installation Manual. If additional lines are available, Fallback can be used to specify a clock source to use should
the Network source not be available.
· Lines from which the clock source should not be taken should be set as Unsuitable.
· If no clock source is available, the system uses its own internal 8KHz clock source.
· In scenarios where several systems are network via digital trunk lines, care must be taken to ensure that all the
systems use the same clock source. The current source being used by a system is reported within the System
Status Application.
· Haul Length: Default = 0-115 feet
Sets the line length to a specific distance.
· Channel Unit: Default = Foreign Exchange
This field should be set to match the channel signaling equipment provided by the Central Office. The options are
Foreign Exchange, Special Access or Normal.
· CRC Checking: Default = On
Turns CRC on or off.
Manager Manager 8.1
Manager
Page 207
15-601011 Issue 25l (11 February 2011)
· Line Signaling: Default = CPE
This field affects T1 channels set to Loop-Start or Ground-Start. The field can be set to either CPE (Customer Premises
Equipment) or CO (Central Office). This field should normally be left at its default of CPE. The setting CO is normally
only used in lab back-to-back testing.
· Incoming Routing Digits: Default=0 (present call immediately)
Sets the number of routing digits expected on incoming calls. This allows the line to present the call to the system once
the expected digits have been received rather than waiting for the digits timeout to expire. This field only affects T1 line
channels set to E&M Tie, E&M DID, E&M Switched 56K and Direct Inward Dial.
· CSU Operation:
Tick this field to enable the T1 line to respond to loop-back requests from the line.
· Enhanced Called Party Number: Default = Off
This option is not supported for systems set to the United States locale. Normally the dialed number length is limited to
15 digits. Selecting this option increases the allowed dialed number length to 30 digits.
· Admin: Default = In Service. Software level = 6.1.
This field allows a trunk to be taken out of service if required for maintenance or if the trunk is not connected.
Manager Manager 8.1
Manager
Page 208
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Line Settings
5.4.5.2 Channels
The settings for each channel can be edited. Users have the option of editing individual channels by double-clicking on the
channel or selecting and editing multiple channels at the same time. Note that the Line Appearance ID cannot be updated
when editing multiple channels.
When editing a channel or channels, the settings available are displayed on two sub-tabs; T1 Edit Channel and Timers.
Line | Channels (T1)
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
T1 Edit Channel Sub-Tab Settings
· Channel
Allocated by the system.
· Incoming Group ID: Default = 0, Range 0 to 99999.
The Incoming Group ID to which a line belongs is used to match it to incoming call routes in the system configuration.
The matching incoming call route is then used to route incoming calls. The same ID can be used for multiple lines.
· Outgoing Group ID: Default = 0, Range 0 to 99999.
Short codes that specify a number to dial also specify the line group to be used. The system will then seize a line with a
matching Outgoing Group ID. The same ID can be used for multiple lines.
· Line Appearance ID: Default = Auto-assigned, Range = 2 to 9 digits. Software level = 3.0+.
Used for configuring Line Appearances with button programming. The line appearance ID must be unique and not match
any extension number. Line appearance is not supported for trunks set to QSIG operation and is not recommended for
trunks be used for DID.
· Direction: Default = Bothway
The direction of calls on the channel (Incoming, Outgoing or Bothway).
· Bearer: Default = Any
The type of traffic carried by the channel.
· Type: Default = Out of Service
The T1 emulates the following connections (Ground-Start, Loop-Start, E&M - TIE, E&M - DID, E&M Switched 56K,
Direct Inward Dial, Clear Channel 64K or Out of Service). Trunks set to E&M - DID will only accept incoming
calls.
· If E&M - TIE is selected and the Outgoing Trunk Type is set to Automatic, no secondary dial tone is provided for
outgoing calls on this line/trunk.
· Dial Type: Default = DTMF Dial
Select the dialing method required (DTMF Dial or Pulse Dial).
· Incoming Trunk Type: Default = Wink-Start
Used for E&M types only. The handshake method for incoming calls (Automatic, Immediate, Delay Dial or WinkStart).
· Outgoing Trunk Type: Default = Wink-Start
Used for E&M types only. The handshake method for outgoing calls (Automatic, Immediate, Delay Dial or WinkStart).
· If the line Type is set to E&M-TIE and the Outgoing Trunk Type is set to Automatic, no secondary dial tone is
provided for outgoing calls on this line/trunk.
· Tx Gain: Default = 0dB
The transmit gain in dB.
· Rx Gain: Default = 0dB
The receive gain in dB.
Manager Manager 8.1
Manager
Page 209
15-601011 Issue 25l (11 February 2011)
Timers Sub-Tab Settings
This sub-tab allows various timers relating to operation of an individual channel to be adjusted. These should only be
adjusted to match the requirements of the line provider. The following is a list of the default values. To reset a value, click
on the current value and then right click and select from the default, minimize and maximize options displayed.
· Outgoing Seizure: 10.
· Wink Signal: 200.
· Wink Start: 5000.
· Incoming Dial Guard: 50.
· Wink Validated: 80.
· First Incoming Digit: 15000.
· Wink End: 350.
· Incoming Inter Digit: 5000.
· Delay End: 5000.
· Maximum Inter Digit: 300.
· Outgoing Dial Guard: 590.
· Flash Hook Detect: 240.
· Outgoing IMM Dial Guard: 1500.
· Incoming Disconnect: 300.
· Outgoing Pulse Dial Break: 60.
· Incoming Disconnect Guard: 800.
· Outgoing Pulse Dial Make: 40.
· Disconnected Signal Error: 240000.
· Outgoing Pulse Dial Inter Digit: 720.
· Outgoing Disconnect: 300.
· Outgoing Pulse Dial Pause: 1500.
· Outgoing Disconnect Guard: 800.
· Flash Hook Generation: 500.
· Ring Verify Duration: 220.
· Outgoing End of Dial: 1000.
· Ring Abandon: 6300.
· Answer Supervision: 300.
· Ping Verify: 600.
· Incoming Confirm: 20.
· Long Ring Time: 1100.
· Incoming Automatic Delay: 410.
· Silent Interval: 1100.
· Incoming Wink Delay: 100.
Manager Manager 8.1
Manager
Page 210
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Line Settings
5.4.6 T1 PRI Line
PRI trunks are provided by the installation of a PRI trunk card into the control unit. IP400 PRI cards are available
in E1, E1R2 and T1/US PRI variants. The IP500 PRI-U trunk card can be configured (see below) to one of those
line types. The cards are also available with either 1 or 2 physical ports. The number of B-channels supported by
each physical port depends on the line type of the card.
· E1: 30 B-channels and 1 D-channel per port.
· T1: 24 B-channels per port.
· US PRI: 23 B-channels and 1 D-channel per port.
· E1-R2: 30 B-channels and 1 D-channel per port.
The Small Office Edition control unit only supports a 1 single port IP400 T1 PRI trunk card. For an IP406 V2
control unit, dual port PRI trunk cards are only supported in Slot A. For full details of installation refer to the
Manager Installation manual.
· Calls received on IP, S0 and QSIG trunks do not use incoming call routes. Routing for these is based on
incoming number received as if dialed on-switch. Line short codes on those trunks can be used to modify the
incoming digits.
IP500 PRI-U Trunk Card Line Type
The IP500 PRI-U card can be configured to support either E1, T1 or E1-R2 PRI line types. To select the line type required,
right-click on the line in the group or navigation pane and select Change Universal PRI Card Line Type.
The IP500/IP500v2 supports 8 B-channels on any IP500 PRI-U card fitted. Additional B-channels up to the full capacity of
IP500 PRI-U ports installed require licenses added to the configuration. D-channels are not affected by licensing.
· For ETSI and QSIG trunks, license instances are consumed by the number of calls in progress on B-channels.
· For T1, E1R2 and ETSI CHI trunks, licenses instances are consumed by the channels set as in service.
Each physical trunk port supports up to 24 channels in T1 mode, 23 channels in PRI and QSIG modes.
· Dialing Complete
The majority of North-American telephony services use en-bloc dialing. Therefore the use of a ; is recommended at the
end of all dialing short codes that use an N. This is also recommended for all dialing where secondary dial tone short
codes are being used.
· AT&T Provider Settings
For AT&T operation two information elements, TNS (Transit Network Selector) and NSF (Network Specific Facility), are
sent in the call setup to the service provider. The values for TNS, NSF and the actual phone number presented to the
line are determined by parsing the number dialed through, in sequence, the TNS, Special and Call by Call tabs. These
tabs appear when the Provider setting on the Line tab is set to AT&T. Note also that B-channels within the same line can
be brought from different service providers. Additionally some B-channels can be used 'call by call', that is, use a
different service provider for each call.
Manager Manager 8.1
Manager
Page 211
15-601011 Issue 25l (11 February 2011)
5.4.6.1 Line
Line | Line (T1 PRI)
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Line Number:
Allocated by the system.
· Card/Module: Software level = 4.1+.
Indicates the card slot or expansion module being used for the trunk device providing the line.
· For IP400 control units: SLOT A on the control unit is shown as 1, SLOT B is shown as 2. Expansion modules are
numbered from 4 upwards, for example trunks on the module in Expansion Port 1 are shown as 4.
· For IP500 and IP500v2 control units: 1 to 4 match the slots on the front of the control unit from left to right.
Expansion modules are numbered from 5 upwards, for example trunks on the module in Expansion Port 1 are shown
as 5.
· Port: Software level = 4.1+.
Indicates the port on the Card/Module above to which the configuration settings relate.
· Network Type: Default = Public. Software level = 4.2+.
This option is available if Restrict Network Interconnect 160 (System | Telephony | Telephony 160 ) is enabled. It
allows the trunk to be set as either Public or Private. The system will return number unobtainable indication to any
attempt to connect a call on a Private trunk to a Public trunk or vice versa. This restriction includes transfers,
forwarding and conference calls.
· Due to the nature of this feature, its use is not recommended on systems also using any of the following other
system features: Small Community Networks 810 , VPNremote, Phone Manager telecommuter mode.
· Line SubType: Default = PRI
Set to PRI. If set to T1 see Line Form (T1)
(E1) 197 .
206 .
If set to ETSI, ETSI CHI (IP Office 4.2+), QSIG A or QSIG B see Line
· QSIG trunks and H323 IP trunks are not supported on IP500 and IP500v2 systems without IP500 Voice
Networking 833 licenses.
· Channel Allocation: Default = 23 -> 1
The order, 23 to 1 or 1 to 23, in which channels are used.
· Switch Type: Default = NI2
Options 4ESS, 5ESS, DMS100 and NI2.
· Provider: Default = Local Telco
Select the PSTN service provider (AT&T, Sprint, WorldCom or Local Telco).
· Prefix: Default = Blank
Enter the number to prefix to all incoming numbers for callback. This is useful if all users must dial a prefix to access an
outside line. The prefix is automatically placed in front of all incoming numbers so that users can dial the number back.
· Add 'Not-end-to-end ISDN' Information Element: Default = Never*. Software level = 4.2+.
Sets whether the optional 'Not end-to-end ISDN' information element should be added to outgoing calls on the line. The
options are Never, Always or POTS (only if the call was originated by an analog extension). *The default is Never
except for the following locales; for Italy the default is POTS, for New Zealand the default is Always.
· Send Redirecting Number: Default = Off. Software level = 6.0+, IP500/IP500v2 only.
This option can be used on ISDN trunks where the redirecting service is supported by the trunk provider. Where
supported, on twinned calls the caller ID of the original call is passed through to the twinning destination. This option is
only used for twinned calls.
· Send Names: Software level = 6.0+
This option is available when the Switch Type above is set to DMS100. If set, names are sent in the display field. The
Z shortcode character 427 can be used to specify the name to be used.
· Names Length: Software level = 6.0+
Set the allowable length for names, up to 15 characters, when Send Names is set above.
· Test Number:
Used to remember the external telephone number of this line to assist with loop-back testing. For information only.
· Framing: Default = ESF
Selects the type of signal framing used (ESF or D4).
· Zero Suppression: Default = B8ZS
Selects the method of zero suppression used (B8ZS or AMI ZCS).
Manager Manager 8.1
Manager
Page 212
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Line Settings
· Clock Quality: Default = Network
Refer to the Manager Installation Manual for full details. This option sets whether the system should try to take its clock
source for call synchronization and signalling from this line. Preference should always be given to using the clock source
from a central office exchange if available by setting at least one exchange line to Network.
· If multiple lines are set as Network, the order in which those lines are used is described in the Manager
Installation Manual. If additional lines are available, Fallback can be used to specify a clock source to use should
the Network source not be available.
· Lines from which the clock source should not be taken should be set as Unsuitable.
· If no clock source is available, the system uses its own internal 8KHz clock source.
· In scenarios where several systems are network via digital trunk lines, care must be taken to ensure that all the
systems use the same clock source. The current source being used by a system is reported within the System
Status Application.
· CSU Operation
Tick this field to enable the T1 line to respond to loop-back requests from the line.
· Haul Length: Default = 0-115 feet
Sets the line length to a specific distance.
· Channel Unit: Default = Foreign Exchange
This field should be set to match the channel signaling equipment provided by the Central Office. The options are
Foreign Exchange, Special Access or Normal.
· CRC Checking: Default = On
Turns CRC on or off.
· Line Signaling:
The field can be set to either CPE (Customer Premises Equipment) or CO (Central Office). This field should normally be
left at its default of CPE. The setting CO is normally only used in lab back-to-back testing.
· Incoming Routing Digits: Default=0 (present call immediately)
Sets the number of routing digits expected on incoming calls. This allows the line to present the call to the system once
the expected digits have been received rather than waiting for the digits timeout to expire. This field only affects T1 line
channels set to E&M Tie, E&M DID, E&M Switched 56K and Direct Inward Dial.
· Admin: Default = In Service. Software level = 6.1.
This field allows a trunk to be taken out of service if required for maintenance or if the trunk is not connected.
Manager Manager 8.1
Manager
Page 213
15-601011 Issue 25l (11 February 2011)
5.4.6.2 Channels
This tab allows settings for individual channels within the trunk to be adjusted. This tab is not available for trunks sets to
ETSI or QSIG mode.
Line | Channels (T1 PRI)
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Channel
Allocated by the system.
· Incoming Group ID: Default = 0, Range 0 to 99999.
The Incoming Group ID to which a line belongs is used to match it to incoming call routes in the system configuration.
The matching incoming call route is then used to route incoming calls. The same ID can be used for multiple lines.
· Outgoing Group ID: Default = 0, Range 0 to 99999.
Short codes that specify a number to dial also specify the line group to be used. The system will then seize a line with a
matching Outgoing Group ID. The same ID can be used for multiple lines.
· Line Appearance ID: Default = Auto-assigned, Range = 2 to 9 digits. Software level = 3.0+.
Used for configuring Line Appearances with button programming. The line appearance ID must be unique and not match
any extension number.
· Direction: Default = Both Directions
The direction of calls on the channel (Incoming, Outgoing or Both Directions).
· Bearer: Default = Any
The type of traffic carried by the channel (Voice, Data or Any).
· Service: Default = None.
If the line provider is set to AT&T, selects the type of service provided by the channel from Call by Call, SDN (inc
GSDN), MegaCom800, MegaComWats, Accunet, NLDS, I800, ETN, Private Line, AT&T Multiquest. For other
providers the service options are None or No Service.
· Admin: Default = Out of Service
Used to indicate the channel status (In Service, Out of Service or Maintenance).
· Tx Gain: Default = 0dB
The transmit gain in dB.
· Rx Gain: Default = 0dB
The receive gain in dB.
Manager Manager 8.1
Manager
Page 214
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Line Settings
5.4.6.3 TNS
This tab is shown when the line Provider is set to AT&T. It allows the entry of the Network Selection settings. These are
prefixes for alternative long distance carriers. When a number dialed matches an entry in the table, that pattern is
stripped from the number before being sent out. This table is used to set field in the TNS (Transit Network Selection)
information element for 4ESS and 5ESS exchanges. It is also used to set fields in the NSF information element.
Line | TNS (T1 PRI)
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· TNS Code:
The pattern for the alternate long distance carrier. For example: The pattern 10XXX is added to this tab. If 10288 is
dialed, 10 is removed and 288 is placed in the TNS and NSF information.
5.4.6.4 Special
This tab is shown when the line Provider is set to AT&T. This table is used to set additional fields in the NSF information
element after initial number parsing by the TNS tab. These are used to indicate the services required by the call. If the
channel is set to Call by Call, then further parsing is done using the entries in the Call by Call tab.
Line | Special (T1 PRI)
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Short code:
The number which results from the application of the rules specified in the User or System Short code tables and the
Network Selection table and the Call-by-call table to the number dialed by the user.
· Number:
The number to be dialed to line.
· Special: Default = No Operator
(No Operator, Local Operator or Presubscribed Operator).
· Plan: Default = National
(National or International).
Typical values are:
Short Code
Number
Service
011N
N
No Operator, International
010N
N
Local Operator, International
01N
N
Local Operator, National
00N
N
Presubscribed Operator, National
0N
N
Presubscribed Operator, National
1N
1N
No operator, National
Manager Manager 8.1
Manager
Page 215
15-601011 Issue 25l (11 February 2011)
5.4.6.5 Call By Call
This tab is shown when the line Provider is set to AT&T. Settings in this tab are only used when calls are routed via a
channel which has its Service set to Call by Call.
It allows short codes to be created to route calls to a different services according to the number dialed. Call By Call
reduces the costs and maximizes the use of facilities. Call By Call chooses the optimal service for a particular call by
including the Bearer capability in the routing decision. This is particularly useful when there are limited resources.
Line | Call By Call (T1 PRI)
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Short Code:
The number which results from the application of the rules specified in the User or System Short code tables and the
Network Selection table to the number dialed by the user.
· Number:
The number to be dialed to line.
· Bearer: Default = Any
The type of channel required for the call (Voice, Data or Any).
· Service: Default = AT&T
The service required by the call (SDN (inc GSDN), MegaCom800, MegaCom, Inwats, Wats, Accunet, NLDS, I800,
ETN, Private Line, AT&T Multiquest).
Manager Manager 8.1
Manager
Page 216
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Line Settings
5.4.7 S0 Line
These settings are used for S0 ports provided by an S08 expansion module connected to the control unit.
Though displayed as lines, these BRI ports are used for connection of ISDN2 devices such as video
conferencing units or ISDN PC cards. For full details of installation refer to the Manager Installation manual.
· Calls received on IP, S0 and QSIG trunks do not use incoming call routes. Routing for these is based on
incoming number received as if dialed on-switch. Line short codes on those trunks can be used to modify
the incoming digits.
5.4.7.1 Line
· Calls received on IP, S0 and QSIG trunks do not use incoming call routes. Routing for these is based on incoming
number received as if dialed on-switch. Line short codes on those trunks can be used to modify the incoming digits.
Line | Line (S0)
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Line Number
This parameter is not configurable. It is allocated by the system.
· Telephone Number:
Used to remember the telephone number of this line. For information only.
· Prefix: Default = Blank.
The prefix is used in the following ways:
· For incoming calls
The ISDN messaging tags indicates the call type (National, International or Unknown). If the call type is unknown,
then the number in the Prefix field is added to the ICLID.
· For outgoing calls
Pre-IP Office 4.0: When a outgoing call is presented to the line with a leading digit to dial that matches the Prefix,
that digit is stripped from the number. IP Office 4.0+: The prefix is not stripped, therefore any prefixes not suitable
for external line presentation should be stripped using short codes.
· National Prefix: Default = 0
This indicates the digits to be prefixed to a incoming national call. When a number is presented from ISDN as a
"national number" this prefix is added. For example 1923000000 is converted to 01923000000.
· International Prefix: Default = 00
This indicates the digits to be prefixed to an incoming international call. When a number is presented from ISDN as an
"international number" this prefix is added. For example 441923000000 is converted to 00441923000000.
· Incoming Group ID: Default = 0, Range 0 to 99999.
The Incoming Group ID to which a line belongs is used to match it to incoming call routes in the system configuration.
The matching incoming call route is then used to route incoming calls. The same ID can be used for multiple lines.
· Outgoing Group ID: Default = 0, Range 0 to 99999.
Short codes that specify a number to dial also specify the line group to be used. The system will then seize a line with a
matching Outgoing Group ID. The same ID can be used for multiple lines.
· TEI: Default = 0
Not used. The Control Unit will ignore any entry.
· Number of Channels: Default = 2
Defines the number of operational channels that are available on this line. 2 for BRI and up to 30 for PRI - depending
upon the number of channels subscribed.
· Outgoing Channels: Default = 2
This defines the number of channels available, on this line, for outgoing calls. This should normally be the same as
Number of Channels field, but can be reduced to ensure incoming calls cannot be blocked by outgoing calls.
· Voice Channels: Default = 2
The number of channels available for voice use.
· Data Channels: Default = 2
The number of channels available for data use. If left blank the value is 0.
Manager Manager 8.1
Manager
Page 217
15-601011 Issue 25l (11 February 2011)
5.4.7.2 Short Codes
Line short codes can be applied to the digits received with incoming call. The stage at which they are applied also varies
depending on the trunk type.
The line Short Code tab is shown for internal trunk types: QSIG (T1, E1, H323), BRI S0, H323, SCN, SES. Incoming
calls are routed by looking for a match to the incoming digits in the following order:
· Extension number (including remote numbers in a Small Community Network).
· Line short codes (excluding ? short code).
· System short codes (excluding ? short code).
· Line ? short code.
· System ? short code.
Line | Short Codes
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
Short codes can be added and edited using the Add, Remove and Edit buttons. Alternatively you can right-click on the
list of existing short code to add and edit short codes.
Manager Manager 8.1
Manager
Page 218
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Line Settings
5.4.7.3 Channels
This tab allows settings for individual channels within the trunk to be adjusted. For So channels this form is not used.
Line | Channels (S0)
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Line Appearance ID
Not used with So lines.
Manager Manager 8.1
Manager
Page 219
15-601011 Issue 25l (11 February 2011)
5.4.8 H323 Line
These lines are added manually. They allow voice calls to be routed over data links within the system. They are
therefore dependent on the IP data routing between the system and the destination having being configured
and tested.
· Calls received on IP, S0 and QSIG trunks do not use incoming call routes. Routing for these is based on
incoming number received as if dialed on-switch. Line short codes on those trunks can be used to modify the
incoming digits.
Network Assessments
Not all data connections are suitable for voice traffic. A network assessment is required for internal network connections.
For external network connections a service level agreement is required from the service provider. Avaya cannot control or
be held accountable for the suitability of a data connection for carrying voice traffic. Refer to the Manager Installation
Manual for further details of Network Assessments and VoIP requirements.
· QSIG trunks and H323 IP trunks are not supported on IP500 and IP500v2 systems without IP500 Voice
Networking 833 licenses.
Manager Manager 8.1
Manager
Page 220
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Line Settings
5.4.8.1 Line
· QSIG trunks and H323 IP trunks are not supported on IP500 and IP500v2 systems without IP500 Voice
Networking 833 licenses.
Line | H323 Line | VoIP Line
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Line Number: Default = 0, Range = 1 to 249.
Enter the line number that you wish. Note that this must be unique.
· Telephone Number:
Used to remember the telephone number of this line. For information only.
· Network Type: Default = Public. Software level = 4.2+.
This option is available if Restrict Network Interconnect 160 (System | Telephony | Telephony 160 ) is enabled. It
allows the trunk to be set as either Public or Private. The system will return number unobtainable indication to any
attempt to connect a call on a Private trunk to a Public trunk or vice versa. This restriction includes transfers,
forwarding and conference calls.
· Due to the nature of this feature, its use is not recommended on systems also using any of the following other
system features: Small Community Networks 810 , VPNremote, Phone Manager telecommuter mode.
· Incoming Group ID: Default = 0, Range 0 to 99999.
The Incoming Group ID to which a line belongs is used to match it to incoming call routes in the system configuration.
The matching incoming call route is then used to route incoming calls. The same ID can be used for multiple lines.
· Outgoing Group ID: Default = 0, Range 0 to 99999.
Short codes that specify a number to dial also specify the line group to be used. The system will then seize a line with a
matching Outgoing Group ID. The same ID can be used for multiple lines.
· Prefix: Default = Blank.
The prefix is used in the following ways:
· For incoming calls
The ISDN messaging tags indicates the call type (National, International or Unknown). If the call type is unknown,
then the number in the Prefix field is added to the ICLID.
· For outgoing calls
Pre-IP Office 4.0: When a outgoing call is presented to the line with a leading digit to dial that matches the Prefix,
that digit is stripped from the number. IP Office 4.0+: The prefix is not stripped, therefore any prefixes not suitable
for external line presentation should be stripped using short codes.
· National Prefix: Default = 0
This indicates the digits to be prefixed to a incoming national call. When a number is presented from ISDN as a
"national number" this prefix is added. For example 1923000000 is converted to 01923000000.
· International Prefix: Default = 00
This indicates the digits to be prefixed to an incoming international call. When a number is presented from ISDN as an
"international number" this prefix is added. For example 441923000000 is converted to 00441923000000.
· Number of Channels: Default = 20, Range 0 to 128.
Defines the number of operational channels that are available on this line.
· Outgoing Channels: Default = 20, Range 0 to 128.
This defines the number of channels available, on this line, for outgoing calls. This should normally be the same as
Number of Channels field, but can be reduced to ensure incoming calls cannot be blocked by outgoing calls.
· Data Channels: Default = 20, Range 0 to 128.
The number of channels available for data use. If left blank the value is 0.
· Voice Channels: Default = 20, Range 0 to 128.
The number of channels available for voice use.
· TEI: Default = 0, Range = 0 to 127.
The Terminal Equipment Identifier. Used to identify each Control Unit connected to a particular ISDN line. For Point to
Point lines this is typically (always) 0. It can also be 0 on a Point to Multi-Point line, however if multiple devices are
actually sharing a Point to Multi-Point line it should be set to 127 which will result in the exchange deciding on the TEI's
to be used by this Control Unit.
Manager Manager 8.1
Manager
Page 221
15-601011 Issue 25l (11 February 2011)
5.4.8.2 Short Codes
Line short codes can be applied to the digits received with incoming call. The stage at which they are applied also varies
depending on the trunk type.
The line Short Code tab is shown for internal trunk types: QSIG (T1, E1, H323), BRI S0, H323, SCN, SES. Incoming
calls are routed by looking for a match to the incoming digits in the following order:
· Extension number (including remote numbers in a Small Community Network).
· Line short codes (excluding ? short code).
· System short codes (excluding ? short code).
· Line ? short code.
· System ? short code.
Line | Short Codes
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
Short codes can be added and edited using the Add, Remove and Edit buttons. Alternatively you can right-click on the
list of existing short code to add and edit short codes.
Manager Manager 8.1
Manager
Page 222
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Line Settings
5.4.8.3 VoIP
Line | H323 Line | VoIP Settings (IP)
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
H323 Trunk (Non SCN)
The following settings are applicable to trunks with their Supplementary Services set to other than IP Office SCN or IP
Office SCN - Fallback.
· Gateway IP Address: Default = Blank
Enter the IP address of the gateway device at the remote end. This address must not be shared by any other IP line
(H323, SIP, SES or IP DECT).
· Compression Mode: Default = Automatic Selection
This field defines the compression mode (codec) or modes offered during call setup. The supported codecs are G.711
ALAW 64K, G.711 ULAW 64K, G.729(a) 8K CS-ACELP, G.723.1 6K3 MP-MLQ.
· Automatic Select
This setting is used as follows:
· Pre-IP Office 5.0: Automatic Select uses the codecs in the order of preference G729a, G711 ALAW, G711 ULAW
and G.723.1.
· IP Office 5.0+: The Automatic Codec Preference 160 setting (System | Telephony | Telephony 160 ) can be used to set
which codec should be first in the list of preferred codecs. The remaining codecs are used in the order as above. Note
that the G711 codecs are treated as a pair, so if one is selected as the first preference, the other will automatically be
second in the list.
· If required, a specific codec can be selected. However, if during call setup negotiation with a specific codec, connect
fails, the system will fallback to using automatic selection.
· Codecs not selected for a SIP connection are not used in codec negotiation. For H.323 it is not possible to exclude
codecs from negotiation, only to change the order of codec preference.
· Supplementary Services: Default = IP Office SCN
Selects the supplementary service signaling method for use across the H323 trunk. The remote end of the trunk must
support the same option. Options are:
· None
No supplementary services are supported.
· H450
Use for H323 lines connected to another PBX or device that uses H450.
· QSIG
Use for H323 lines connected to another PBX or device that uses QSIG.
· IP Office SCN
This option is used for H323 trunks within a Small Community Network (SCN). The systems with an SCN
automatically exchange information about users and extensions, allowing remote users to be called without any
additional configuration on the local system. For full details of SCN operation see Small Community Networking 810
.
· IP Office SCN - Fallback (IP Office 5+ only)
This option is used for an SCN trunk connection as above, where the system at the end of the trunk will try to take
over the selected SCN Backup Options if this system is not visible within the Small Community Network for a
period of more than 3 minutes. Only one H323 trunk per system can be set as IP Office SCN - Fallback. See SCN
Fallback 826 .
· Call Initiation Timeout: Default = 4 seconds, Range = 1 to 99 seconds. Software level = 4.2+.
This option sets how long the system should wait for a response to its attempt to initiate a call before following the
alternate routes set in an ARS 409 form.
· 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. This feature is not used on IP lines using G711 between systems.
· Enable FastStart for non-Avaya IP Phones: Default = Off
A fast connection procedure. Reduces the number of messages that need to be exchanged before an audio channel is
created.
· Fax Transport Support: Off (Fixed)
This option is only supported on trunks with their Supplementary Services set to IP Office SCN or IP Office SCN Fallback.
Manager Manager 8.1
Manager
Page 223
15-601011 Issue 25l (11 February 2011)
· IP Office 5.0+: IP500 and IP500 v2 systems with an IP500 VCM are able to support fax relay 749 across H323 SCN
lines with Fax Transport Support selected. This will use 2 VCM channels in each of the systems.
· Local Tones: Default = Off
When selected, the tones are generated by the local system to which the phone is registered. This option should not be
used with lines being used for Small Community Networking. For the Small Office Edition control unit, this field should
not be enabled.
· DTMF Support: Default = Out of Band
DTMF tones can be sent to the remote end either as DTMF tones within the calls audio path (In Band) or a separate
signals (Out of Band). Out of Band is recommended for compression modes such as G.729 and G.723 compression
modes where DTMF in the voice stream could become distorted.
· For trunks with Supplementary Services set to IP Office SCN or IP Office SCN - Fallback, this option is fixed
to Out of Band.
· Allow Direct Media Path: Default = On
This settings controls whether H323 calls must be routed via the H323 gatekeeper (the system) or can be routed
alternately if possible within the network structure.
· If enabled, H323 calls can take routes other than through the system. This removes the need for a voice compression
channel. Both ends of the calls must support Direct Media. Enabling this option may cause some vendors problems
with changing the media path in mid call. Pre-IP Office 4.0, when using direct media path, it is not always possible for
the extension to be recorded or monitored.
· If disabled or not supported at on one end of the call, the call is routed via the system.
· On pre-4.0 these calls would then require a voice compression channel even if the IP devices use the same audio
codec.
· On IP Office 4.0 and higher, RTP relay support allows calls between devices using the same audio codec to not
require a voice compression channel.
· Progress Ends Overlap Send: Default = Off. Software level = 3.2+.
Some telephony equipment, primarily AT&T switches, over IP trunks send a H323 Progress rather than H323 Proceeding
message to signal that they have recognized the digits sent in overlap state. By default the system expects an H323
Proceeding message. This option is not available by default. If required, the value ProgressEndsOverlapSend must be
entered into the Source Numbers 272 tab of the NoUser 767 user.
· Default Name for Display IE: Default = Off. Software level = 4.2+.
H323 Trunk (SCN)
The following settings are applicable to trunks with their Supplementary Services set to IP Office SCN or IP Office
SCN - Fallback.
· Gateway IP Address: Default = Blank
Enter the IP address of the gateway device at the remote end. This address must not be shared by any other IP line
(H323, SIP, SES or IP DECT).
· Compression Mode: Default = Automatic Selection
This field defines the compression mode (codec) or modes offered during call setup. The supported codecs are G.711
ALAW 64K, G.711 ULAW 64K, G.729(a) 8K CS-ACELP, G.723.1 6K3 MP-MLQ.
· Automatic Select
This setting is used as follows:
· Pre-IP Office 5.0: Automatic Select uses the codecs in the order of preference G729a, G711 ALAW, G711 ULAW
and G.723.1.
· IP Office 5.0+: The Automatic Codec Preference 160 setting (System | Telephony | Telephony 160 ) can be used to set
which codec should be first in the list of preferred codecs. The remaining codecs are used in the order as above. Note
that the G711 codecs are treated as a pair, so if one is selected as the first preference, the other will automatically be
second in the list.
· If required, a specific codec can be selected. However, if during call setup negotiation with a specific codec, connect
fails, the system will fallback to using automatic selection.
· Codecs not selected for a SIP connection are not used in codec negotiation. For H.323 it is not possible to exclude
codecs from negotiation, only to change the order of codec preference.
· Supplementary Services: Default = IP Office SCN
Selects the supplementary service signaling method for use across the H323 trunk. The remote end of the trunk must
support the same option. Options are:
· None
No supplementary services are supported.
· H450
Use for H323 lines connected to another PBX or device that uses H450.
Manager Manager 8.1
Manager
Page 224
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Line Settings
· QSIG
Use for H323 lines connected to another PBX or device that uses QSIG.
· IP Office SCN
This option is used for H323 trunks within a Small Community Network (SCN). The systems with an SCN
automatically exchange information about users and extensions, allowing remote users to be called without any
additional configuration on the local system. For full details of SCN operation see Small Community Networking 810
.
· IP Office SCN - Fallback (IP Office 5+ only)
This option is used for an SCN trunk connection as above, where the system at the end of the trunk will try to take
over the selected SCN Backup Options if this system is not visible within the Small Community Network for a
period of more than 3 minutes. Only one H323 trunk per system can be set as IP Office SCN - Fallback. See SCN
Fallback 826 .
· SCN Backup Options: Software level = 5.0+.
These options are only available on when the Supplementary Services option is set to IP Office - Fallback. The
system to which the trunk connects must be an IP Office 5+ system. The intention of this feature is to attempt to
maintain a minimal level of operation while problems with the local system are resolved.
· Backs up my IP Phones: Default = On.
This option is used for Avaya 1600, 4600, 5600 and 9600 Series phones registered with the system. When
selected, it will share information about the registered phones and users on those phones with the other system.
· If the local system is no longer visible to the phones, the phones will reregister with the other system. The
users who were currently on those phones will appear on the other system as if they had hot desked.
· Note that when the local system is restored to the SCN, the phones will not automatically re-register with it. A
phone reset via either a phone power cycle or using the System Status Application is required.
· When phones have registered with the other system, they will show an R on their display.
· Backs up my Hunt Groups: Default = On.
When selected, any hunt groups the local system is advertising to the SCN are advertised from the other system
when fallback is required. The trigger for this occurring is Avaya H323 phones registered with the local system
registering with the other system, ie. Backs up my IP Phones above must also be enabled.
· When used, the only hunt group members that will be available are as follows:
· If the group was a distributed hunt group, those members who were remote members on other systems
still visible within the SCN.
· Any local members who have hot desked to another system still visible within the SCN.
· When the local system becomes visible to the other system again, the groups will return to be advertised from
the local system.
· Backs up my Voicemail: Default = On.
This option can be used if the local system is hosting the Voicemail Pro server being used by the SCN. If selected,
when the local system is no longer visible to the voicemail server, the other system will act as host for the
voicemail server.
· This option requires the other system to have licenses for the Voicemail Pro features that are required to
operated during any fallback period.
· This option requires Voicemail Pro 5.0+.
· Call Initiation Timeout: Default = 4 seconds, Range = 1 to 99 seconds. Software level = 4.2+.
This option sets how long the system should wait for a response to its attempt to initiate a call before following the
alternate routes set in an ARS 409 form.
· 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. This feature is not used on IP lines using G711 between systems.
· Fax Transport Support: Off (Fixed)
This option is only supported on trunks with their Supplementary Services set to IP Office SCN or IP Office SCN Fallback.
· For IP Office 5+, IP500 and IP500v2 systems with an IP500 VCM are able to support fax relay 749 across H323 SCN
lines with Fax Transport Support selected. This will use 2 VCM channels in each of the systems.
· Local Tones: Default = Off
When selected, the tones are generated by the local system to which the phone is registered. This option should not be
used with lines being used for Small Community Networking. For the Small Office Edition control unit, this field should
not be enabled.
· DTMF Support: Default = Out of Band
DTMF tones can be sent to the remote end either as DTMF tones within the calls audio path (In Band) or a separate
signals (Out of Band). Out of Band is recommended for compression modes such as G.729 and G.723 compression
modes where DTMF in the voice stream could become distorted.
Manager Manager 8.1
Manager
Page 225
15-601011 Issue 25l (11 February 2011)
· For trunks with Supplementary Services set to IP Office SCN or IP Office SCN - Fallback, this option is fixed
to Out of Band.
· Allow Direct Media Path: Default = On
This settings controls whether H323 calls must be routed via the H323 gatekeeper (the system) or can be routed
alternately if possible within the network structure.
· If enabled, H323 calls can take routes other than through the system. This removes the need for a voice compression
channel. Both ends of the calls must support Direct Media. Enabling this option may cause some vendors problems
with changing the media path in mid call. Pre-IP Office 4.0, when using direct media path, it is not always possible for
the extension to be recorded or monitored.
· If disabled or not supported at on one end of the call, the call is routed via the system.
· On pre-4.0 these calls would then require a voice compression channel even if the IP devices use the same audio
codec.
· On IP Office 4.0 and higher, RTP relay support allows calls between devices using the same audio codec to not
require a voice compression channel.
Manager Manager 8.1
Manager
Page 226
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Line Settings
5.4.9 IP DECT Line
This type of line can be manually added. They are used to route voice calls over an IP data connection to an
Avaya IP DECT system. Only one IP DECT line can be added to a system. Refer to the Manager IP DECT
Installation manual for full details.
For North American locales, an IP DECT line is only supported with the IP Office 4.0 Q2 2007 maintenance release and
higher.
5.4.9.1 Line
Currently only one IP DECT line is supported on a system. For North American locales, an IP DECT line is only supported
with the IP Office 4.0 Q2 2007 maintenance release and higher.
Line | Line (IP DECT)
Control Unit
SOE
Software Level
3.1+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Line Number
This number is allocated by the system and is not adjustable.
· Associated Extensions
Lists all the DECT extensions associated with the IP DECT line.
Manager Manager 8.1
Manager
Page 227
15-601011 Issue 25l (11 February 2011)
5.4.9.2 Gateway
Line | Gateway (IP DECT)
Control Unit
SOE
Software Level
3.1+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Auto-Create Extension: Default = Off. Software level = 4.0+.
If enabled, subscription of a handset with the DECT system causes the auto-creation of a matching numbered extension
within the system configuration if one does not already exist.
· Enable DHCP Support: Default = Off
This option is not supported for use with Avaya IP DECT R4. The IP DECT base stations require DHCP and TFTP support.
Enable this option if the system is being used to provide that support, using IP addresses from its DHCP range (LAN1 or
LAN2) and its TFTP server setting. If not enabled, alternate DHCP and TFTP options must be provided during the IP
DECT installation.
· If it is desired to use the system for DHCP support of the ADMM and IP DECT base stations only, the system
address range should be set to match that number of addresses. Those addresses are then taken during the
system restart and will not be available for other DHCP responses following the restart.
· For Small Office Edition and IP406V2 control units, use of the embedded voicemail memory card slot for the
TFTP server is recommended for small IP DECT installations. See System | TFTP IP Server Address 143 . For
other control units, or larger IP DECT installations, the use of a non-embedded TFTP software option other than
Manager is recommended.
· Boot File: Default = ADMM_RFP_1_0_0.tftp, Range = Up to 31 characters.
The name and path of the ADMM software file. The path is relative to the TFTP server root directory.
· ADMM MAC Address: Default = 00:00:00:00:00:00
This field must be used to indicate the MAC address of the IP DECT base station that should load the ADMM software
file and then act as the IP DECT system's ADMM. The address is entered in hexadecimal format using comma, dash,
colon or period separators.
· VLAN ID: Default = Blank, Range = 0 to 4095.
If VLAN is being used by the IP DECT network, this field sets the VLAN address assigned to the base stations by the
system if Enable DHCP Support is selected.
· The system itself does not apply or use VLAN marking. It is assumed that the addition of VLAN marking and routing
of VLAN traffic is performed by other switches within the customer network.
· An ID of zero is not recommended for normal VLAN operation.
· When blank, no VLAN option is sent to the IP DECT base station.
· Base Station Address List: Default = Empty
This box is used to list the MAC addresses of the IP DECT base stations, other than the base station being used as the
ADMM and entered in the ADMM MAC Address field. Right-click on the list to select Add or Delete. or use the Insert
and Delete keys. The addresses are entered in hexadecimal format using comma, dash, colon or period separators.
Manager Manager 8.1
Manager
Page 228
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Line Settings
5.4.9.3 VoIP
· Gateway IP Address: Default = Blank
Enter the IP address of the gateway device at the remote end. This address must not be shared by any other IP line
(H323, SIP, SES or IP DECT).
· Compression Mode: Default = Automatic Selection
This field defines the compression mode (codec) or modes offered during call setup. The supported codecs are G.711
ALAW 64K, G.711 ULAW 64K, G.729(a) 8K CS-ACELP, G.723.1 6K3 MP-MLQ.
· Automatic Select
This setting is used as follows:
· Pre-IP Office 5.0: Automatic Select uses the codecs in the order of preference G729a, G711 ALAW, G711 ULAW
and G.723.1.
· IP Office 5.0+: The Automatic Codec Preference 160 setting (System | Telephony | Telephony 160 ) can be used to set
which codec should be first in the list of preferred codecs. The remaining codecs are used in the order as above. Note
that the G711 codecs are treated as a pair, so if one is selected as the first preference, the other will automatically be
second in the list.
· If required, a specific codec can be selected. However, if during call setup negotiation with a specific codec, connect
fails, the system will fallback to using automatic selection.
· Codecs not selected for a SIP connection are not used in codec negotiation. For H.323 it is not possible to exclude
codecs from negotiation, only to change the order of codec preference.
· Gain: Default = Default. Software level = 3.0 to 4.1.
Allows adjustment of the volume. The gain is selectable from -31dB to +31dB in 1dB increments.
· TDM->IP Gain: Default = Default (0dB). Range = -31dB to +31dB. Software level = 4.1 Q1 2008+.
Allows adjustment of the gain on audio from the system TDM interface to the IP connection.
· IP->TDM Gain: Default = Default (0dB). Range = -31dB to +31dB. Software level = 4.1 Q1 2008+.
Allows adjustment of the gain on audio from the IP connection to the system TDM interface.
· 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. This feature is not used on IP lines using G711 between systems.
· Allow Direct Media Path: Default = On
This settings controls whether H323 calls must be routed via the H323 gatekeeper (the system) or can be routed
alternately if possible within the network structure.
· If enabled, H323 calls can take routes other than through the system. This removes the need for a voice compression
channel. Both ends of the calls must support Direct Media. Enabling this option may cause some vendors problems
with changing the media path in mid call. Pre-IP Office 4.0, when using direct media path, it is not always possible for
the extension to be recorded or monitored.
· If disabled or not supported at on one end of the call, the call is routed via the system.
· On pre-4.0 these calls would then require a voice compression channel even if the IP devices use the same audio
codec.
· On IP Office 4.0 and higher, RTP relay support allows calls between devices using the same audio codec to not
require a voice compression channel.
Manager Manager 8.1
Manager
Page 229
15-601011 Issue 25l (11 February 2011)
5.4.10 SIP Line
IP Office 4.0 and higher supports SIP voice calls through the addition of SIP trunks to the system configuration. This
approach allows users with non-SIP phones to make and receive SIP calls.
Use of SIP requires the following:
1. SIP Service Account
An account or accounts with a SIP internet service provider (ITSP). The method of operation and the information
provided will vary. The key requirement is a SIP URI, a web address of the form name@example.com. This is the
equivalent of a SIP telephone number for making and receiving calls via SIP.
2. Voice Compression Channels
SIP calls use system voice compression channels in the same way as used for standard IP trunks and extensions. These
are provided by the installation of VCM modules within the control unit. RTP relay is applied to SIP calls where
applicable.
3. Licensing
SIP trunks require licenses in the system configuration. These set the maximum number of simultaneous SIP calls
supported by the system.
4. Firewall Traversal
Routing traditional H323 VoIP calls through firewalls often fails due to the effects of NAT (Network Address Translation).
For SIP a number of ways of ensuring successful firewall traversal have been created.
· STUN (Simple Traverse of UDP NAT)
UDP SIP can use a mechanism called STUN to cross firewalls between the switch and the ITSP. This requires the
ITSP to provide the IP address of their STUN server and the system to then select from various STUN methods how
to connect to that server. The system can attempt to auto-detect the required settings to successfully connect.
These settings are part of the System | LAN1 148 and System | LAN2 155 forms. STUN is not required is the ITSP
used Session Border Control (SBC).
· TURN (Traversal Using Relay NAT)
TCP SIP can use a mechanism called TURN (Traversal Using Relay NAT). This is not currently supported.
· Firewall
The firewall between LAN1 and LAN2 is not applied to SIP calls.
5. SIP Trunks
These trunks are manually added to the system configuration. Typically a SIP trunk is required for each SIP ITSP being
used. As the configuration provides methods for multiple URI's from that ITSP to use the same trunk. For each trunk at
least one SIP URI entry is required, up to 150 SIP URI's are supported on the same trunk. Amongst other things this
sets the incoming and outgoing groups for call routing.
6. Outgoing Call Routing
The initial routing uses any standard short code with a dial feature. The short code's Line Group ID should be set to
match the Outgoing Group ID of the SIP URI 238 channels to use. However the short code must also change the number
dialed into a destination SIP URI suitable for routing by the ITSP. In most cases, if the destination is a public telephone
network number, a URI of the form 123456789@example.com is suitable. For example:
· Code: 9N#
· Feature: Dial
· Telephone Number: N"@example.com"
· Line Group ID: 100
7. Incoming Call Routing
Incoming SIP calls are routed in the same way as other incoming external calls. The caller and called information in the
SIP call header can be used to match Incoming CLI and Incoming Number settings in normal system Incoming Call
Route 344 entries.
8. DiffServ Marking
DiffServ marking is applied to calls using the DiffServer Settings on the System | LAN | VoIP
LAN2 as set by the line's Use Network Topology Info setting.
Manager Manager 8.1
Manager
150
tab of either LAN1 or
Page 230
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Line Settings
SIP URIs
Calls across SIP require URI's (Uniform Resource Identifiers), one for the source and one for the destination. Each SIP URI
consists of two parts, the user part (for example name) and the domain part (for example example.com) to form a full
URI (in this case name@example.com). SIP URI's can take several forms:
· name@117.53.22.2
· name@example.com
· 012345678@example.com
Typically each account with a SIP service provider will include a SIP URI or a set of URI's. The domain part is then used for
the SIP trunk configured for routing calls to that provider. The user part can be assigned either to an individual user if you
have one URI per user for that ITSP, or it can also be configured against the line for use by all users who have calls routed
via that line.
· IP Office 5.0+: If the wildcard * is used in the SIP trunk's Local URI, Contact and Display fields, that SIP trunk
will accept any incoming SIP call. The incoming call routing is still performed by the system incoming call routes
based on matching the values received with the call or the URI's incoming group setting. Outgoing calls using the
trunk will need to use another URI set against the trunk.
Resource Limitation
A number of limits can affect the number of SIP calls. When one of these limits is reached the following occurs: any
further outgoing SIP calls are blocked unless some alternate route is available using ARS; any incoming SIP calls are
queued until the required resource becomes available. Limiting factors are:
· the number of licensed SIP channels.
· the number of SIP channels configured for a SIP URI.
· the number of voice compression channels.
· SIP Line Call to/from Non-IP Devices
Voice compression channel required.
· Outgoing SIP Line Call from IP Device
No voice compression channel required.
· Incoming SIP Line Call to IP Device
If using the same codec, voice compression channel reserved until call connected. If using differing codecs then
2 channels used.
SIP Information Display
The full from and to SIP URI will be recorded for use by SMDR, CBC and CCC. For all other applications and for telephone
devices, the SIP URI is put through system directory matching the same as for incoming CLI matching. First a match
against the full URI is attempted, then a match against the user part of the URI. Directory wildcards can also be used for
the URI matching.
SIP Standards
The system implementation of SIP conforms to the following SIP RFC's.
RFC
Description
2833 [7]
RTP Payload for DTMF digits, telephony tones and telephony signals.
3261 [8]
SIP Session Initiation Protocol.
3263
Locating SIP Services (IP Office 6.1+)
3264 [11]
An Offer/Answer Model with Session Description Protocol (SDP).
3323 [14]
A Privacy Mechanism for SIP
3489 [18]
STUN - Simple Traversal of User Datagram Protocol (UDP) Through Network Address Translators
(NAT's).
3824 [24]
Using E.164 Numbers with the Session Initiation Protocol (SIP). E.164 is the ITU-T recommendation for
international public telecommunication numbering plans.
Manager Manager 8.1
Manager
Page 231
15-601011 Issue 25l (11 February 2011)
5.4.10.1 Incoming Call Routing
Incoming SIP calls are routed using Incoming Call Routes 342 in the same way as call arriving on other external trunks.
The following Incoming Call Route fields are used to determine which route is the best match for a call.
· Line Group ID
This field is matched against the Incoming Group settings of the SIP URI (Line | SIP URI). This must be an exact match.
· Incoming Number
This field can be used to match the called details (TO) in the SIP header of incoming calls. It can contain a number, SIP
URI or Tel URI. For SIP URI's the domain part of the URI is removed before matching by incoming call routing occurs.
For example, for the SIP URI mysip@example.com , only the user part of the URI, ie. mysip, is used for matching.
· Incoming CLI
This field can be used to match the calling details (FROM) in the SDP header of incoming SIP calls. It can contain a
number, SIP URI, Tel URI or IP address received with SIP calls. For all types of incoming CLI except IP addresses a
partial entry can be used to achieve the match, entries being read from left to right. For IP addresses only full entry
matching is supported.
The fields Bearer Capability and Incoming Sub Address are not used for matching of incoming SIP calls. The remain
Incoming Call Route fields, including those voice recording, as used as for all call types.
· IP Office 5.0+: If the wildcard * is used in the SIP trunk's Local URI, Contact and Display fields, that SIP trunk
will accept any incoming SIP call. The incoming call routing is still performed by the system incoming call routes
based on matching the values received with the call or the URI's incoming group setting. Outgoing calls using the
trunk will need to use another URI set against the trunk.
Manager Manager 8.1
Manager
Page 232
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Line Settings
5.4.10.2 SIP Line
Line | SIP Line
Control Unit
SOE
Software Level
4.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Line Number: Default = Automatically assigned.
By default a value is assigned by the system. This value can be changed but it must be unique.
· Network Type: Default = Public. Software level = 4.2+.
This option is available if Restrict Network Interconnect 160 (System | Telephony | Telephony 160 ) is enabled. It
allows the trunk to be set as either Public or Private. The system will return number unobtainable indication to any
attempt to connect a call on a Private trunk to a Public trunk or vice versa. This restriction includes transfers,
forwarding and conference calls.
· Due to the nature of this feature, its use is not recommended on systems also using any of the following other
system features: Small Community Networks 810 , VPNremote, Phone Manager telecommuter mode.
· ITSP Domain Name: Default = Blank.
This field is used to enter the domain part of the SIP URI provided by the ITSP. For example, in the SIP URI
name@example.com, the domain part of the URI is example.com. For outgoing calls the user part of the SIP URI is
determined in a number of ways:
· For the user making the call, the user part of the FROM SIP URI is determined by the settings of the SIP URI
channel entry being used to route the call. This will use one of the following:
238
· a specific name entered in Local URI field of the channel entry.
· or specify using the primary or secondary authentication name set for the line below
· or specify using the SIP Name set for the user making the call (User | SIP | SIP Name
303 ).
· For the destination of the call, the user part of the TO SIP URI is determined by the dialing short codes of the form 9N
/ N"@example.com" where N is the user part of the SIP URI.
· ITSP IP Address: Default = 0.0.0.0. Software level = 4.0 to 6.0.
This value is provided by the SIP ITSP. This address must not be shared by any other IP, IP DECT or SIP line in the
system configuration.
· IP Office 6.0+: Domain name resolution using the ITSP Domain Name value can be used instead. This requires a
DNS server and the system to be acting as a DHCP client. If that is the case, leaving the ITSP IP Address as 0.0.0.0
will cause the system to attempt to resolve the domain name using DNS.
· IP Office 6.1+: This setting has replaced by ITSP Proxy Address on the Transport
236
tab.
· Prefix: Default = Blank. Software level = 6.0.
This prefix is removed from the called number on outgoing calls if present. See SIP Prefix Operation
235
below.
· National Prefix: Default = 0. Software level = 6.0.
This prefix is added to calls identified as not being international.
· Country Code: Default = Blank. Software level = 6.0.
Set to match the local country code of the system location.
· International Prefix: Default = 00. Software level = 6.0.
This prefix is added to calls identified as not being national.
· Send Caller ID: Default = None. Software level = 5.0+.
Select which value the SIP line should use for the original calling party ID when routing twinned calls.
· IP Office 6.1: This setting is also used for forwarded calls. Note that the values on the System | Twinning 177
tab override this if set. For incoming calls to a hunt group, the hunt group details will be provided and not the
details of the answering agent. This setting is mergeable.
· IP Office 5.0+: The SIP line Send Caller ID setting takes priority.
· IP Office 6.0+: The values on the System | Twinning
177
tab override the SIP lines Send Caller ID setting.
· Diversion Header (Software level = 6.0+)
· Remote Party ID
· P Asserted ID
This is the default setting for new SIP lines.
Manager Manager 8.1
Manager
Page 233
15-601011 Issue 25l (11 February 2011)
· None
This option corresponds to the ISDN withheld setting. This is the default setting for existing SIP lines in
configurations upgraded to IP Office 5+.
· Refer Support: Default = On. Software level = 6.1+
REFER is the method used by many SIP device, including SIP trunks, to transfer calls. These settings can be used to
control whether REFER is used as the method to transfer calls on this SIP trunk to another call on the same trunk. If
supported, once the transfer has been completed, the system is no longer involved in the call. If not supported, the
transfer may still be completed but the call will continue to be routed via the system.
· Incoming: Default = Auto
Select whether REFER can or should be used when an attempt to transfer an incoming call on the trunk results in
an outgoing call on another channel on the same trunk. The options are:
· Always
Always use REFER for call transfers that use this trunk for both legs of the transfer. If REFER is not supported,
the call transfer attempt is stopped.
· Auto
Request to use REFER if possible for call transfers that use this trunk for both legs of the transfer. If REFER is
not supported, transfer the call via the system as for the Never setting below.
· Never
Do not use REFER for call transfers that use this trunk for both legs of the transfer. The transfer can be
completed but will use 2 channels on the trunk.
· Outgoing: Default = Auto
Select whether REFER can or should be used when attempt to transfer an outgoing call on the trunk results in an
incoming call on another channel on the same trunk. This uses system resources and may incur costs for the
duration of the transferred call. The options available are the same as for the Incoming setting.
· In Service: Default = On.
When this field is not selected, the SIP trunk is unregistered and not available to incoming and outgoing calls.
· Registration Required: Default = Off. Software level = 4.0 to 6.0.
If selected, the SIP trunk will register with the ITSP using the value in the ITSP Domain Name field. For IP Office 6.1
this setting has moved to the SIP Credentials 242 tab.
· Use Tel URI: Default = Off.
Use Tel URI format (for example TEL: +1-425-555-4567) rather than SIP URI format (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.
· Check OOS: Default = On. Software level = 6.0+.
If enabled, the system will regularly check if the trunk is in service. Checking that SIP trunks are in service ensures that
outgoing call routing is not delayed waiting for response on a SIP trunk that is not currently useable.
· For both UDP and TCP trunks, the OPTIONS message is regularly sent. If no reply is received the trunk is taken out
of service.
· For TCP trunks, if the TCP connection is disconnected the trunk will be taken out of service.
· For trunks using DNS, if the IP address is not resolved or the DNS resolution has expired, the trunk is taken out of
service.
· Call Routing Method: Default = Request URI. Software level = 6.0+.
This field allows selection of which incoming SIP information should be used for incoming number matching by the
system's incoming call routes. The options are to match either the Request URI or the To Header element provided
with the incoming call.
· Originator number for forwarded and twinning calls: Default = Blank. Software level = 6.1+.
The field can be used to set a originator number for forwarded and twinned calls when using any of the Send Caller ID
options above other than None.
For IP Office 6.1 and higher, the following fields have been replaced by those on the Transport
236
tab.
· Network Configuration: Software level = 4.0 to 6.0.
· Layer 4 Protocol: Default = UDP
This field sets whether the line uses UDP SIP or TCP SIP.
· Use Network Topology Info: Default = LAN1
This field associates the SIP line with the System | LAN1 | Network Topology 152 settings of either LAN1 or
LAN2. If None is selected, STUN lookup is not applied and routing is determined by the system routing tables.
· Send Port: Default = 5060
This field sets the port to which the system sends outgoing SIP calls.
· Listen Port: Default = 5060
This field sets the port on which the system listens for incoming SIP calls.
Manager Manager 8.1
Manager
Page 234
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Line Settings
For IP Office 6.0 and higher, the following fields have been replaced by those on the SIP Credentials
242
tab.
· Primary Authentication Name: Default = Blank.
This value is provided by the SIP ITSP. Depending on the settings on the Local URI tab associated with the SIP call it
may also be used as the user part of the SIP URI.
· If the From field on the Local URI 238 being used for the call is set to Use Authentication Name and the Registration is
set to Primary, this value is used as the user part of the SIP URI for calls.
· Primary Authentication Password: Default = Blank.
This value is provided by the SIP ITSP.
· Primary Registration Expiry: Default = 60 minutes.
This setting defines how often registration with the SIP ITSP is required following any previous registration.
· Secondary Authentication Name: Default = Blank.
This value is provided by the SIP ITSP. Depending on the settings on the Local URI tab associated with the SIP call it
may also be used as the user part of the SIP URI.
· If the From field on the Local URI 238 being used for the call is set to Use Authentication Name and the Registration is
set to Secondary, this value is used as the user part of the SIP URI for calls.
· Secondary Authentication Password: Default = Blank.
This value is provided by the SIP ITSP.
· Secondary Registration Expiry: Default = 60 minutes.
This setting defines how often registration with the SIP ITSP is required following any previous registration.
SIP Prefix Operation
IP Office 6.0+: 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 prefixes as follows:
· Line Prefix: 9
· National Prefix: 90
· International Prefix: 900
· Country Code: 44
Number Received
Processing
Resulting Number
+441707362200
Following rule 1 above, the + is replace with the International Prefix
(900), resulting in 900441707362200.
901707362200
The number now matches the International Prefix (900) and Country
Code (44).Following rule 2 above they are replace with the National
Prefix (90).
00441707362200
Following rule 2 above the International Prefix (900) and the Country 90107362200
Code (44) are replaced with the National Prefix (90).
441707362200
Following rule 2 above, the Country Code (44) is replace with the
National Prefix (90).
901707362200
6494770557
Following rule 3 above the International Prefix (900) is added.
9006494770557
Manager Manager 8.1
Manager
Page 235
15-601011 Issue 25l (11 February 2011)
5.4.10.3 Transport
Line | SIP Line
Control Unit
SOE
Software Level
6.1+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
(ITSP Proxy Address and Calls Route via Registrar are mergeable).
· ITSP Proxy Address: Default = Blank
This is the SIP Proxy address used for outgoing SIP calls.
· The address can be specified in the following ways:
· If left blank, the ITSP Domain Name is used and is resolved by DNS resolution in the same way as if a DNS
address had been specified as below.
· An IP address.
· A list of up to 4 IP addresses, with each address separated by a comma or space.
· The addresses can include an indication of the relative call weighting of each address compared to the
others. This is done by adding a wN suffix to the address where N is the weighting value. For example, in
the list 213.74.81.102w3 213.74.81.100w2, the weighting values assigns 1.5 times the weight of calls to
the first address. The default weight if not specified is 1. A weight of 0 can be used to disable an address.
Weight is only applied to outgoing calls.
· If the Calls Route via Registrar setting below is enabled, the weighting is applied to registrations rather
than calls.
· A DNS address, for example sbc.example.com.
· The DNS response may return multiple proxy addresses (RFC 3263). If that is the case, the system will
resolve the address to use based on priority, TTL and weighting information included with each address.
· A load balancing suffix can be added to specify that multiple proxy results should be returned if possible,
for example sbc.example.com(N). where N is the required number of addresses from 1 to 4.
· This field is mergeable. However no more than 4 IP Addresses should be in use at any time. So, if the combined
new and old address settings exceed 4, the new addresses are only phased into use as transactions in progress on
the previous addresses are completed.
· Network Configuration
These settings are applied to all calls using this SIP line.
· Layer 4 Protocol: Default = UDP
This field sets whether the line uses UDP SIP or TCP SIP.
· Use Network Topology Info: Default = LAN1
This field associates the SIP line with the System | LAN1 | Network Topology 152 settings of either LAN1 or
LAN2. If None is selected, STUN lookup is not applied and routing is determined by the system routing tables.
· Send Port: Default = 5060
This field sets the port to which the system send outgoing SIP calls.
· Listen Port: Default = 5060
This field sets the port on which the system listens for incoming SIP calls.
· Explicit DNS Server(s): Default = 0.0.0.0 (Off)
If specific DNS servers should be used for SIP trunk operation rather than the general DNS server specified or obtained
for the system, the server addresses can be specified here.
· Calls Route via Registrar: Default = On
If selected, all calls are routed via the same proxy as used for registration. If multiple ITSP proxy addresses have been
specified, the weighting for those addresses is applied to the registrations.
· Separate Registrar: Default = Blank
This field allows the SIP registrar address to be specified if it is different from that of the SIP proxy. The address can be
specified as an IP address or DNS name.
Manager Manager 8.1
Manager
Page 236
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Line Settings
Behaviour during Service unavailable
A proxy server is considered Active once the system has received a response to an INVITE, REGISTER or OPTIONS.
In the case of the proxy server responding with 503 - Service Unavailable, it should be considered Active - In Maintenance
. In this case, the following should occur:
· If the response 503 - Service Unavailable was in response to an INVITE request:
· If calls are tied to registrations (Calls Route via Registrar enabled) and there are other proxies available, the
tied registrations should issue an Un-REGISTER and try to REGISTER with a different proxy. The call should fail
with cause = Temporary Fail.
· If calls are not tied, the INVITE should be immediately tried to a different proxy.
· If the response 503 - Service Unavailable was in response to a REGISTER request:
· If there are other proxies available, this registration only should issue an Un-REGISTER and try to REGISTER
with a different proxy.
· If Explicit DNS Server(s) are configured, a DNS request should be sent out to see whether the proxy server has
disappeared from those being offered.
· An Active-InMaintenance proxy server should not be used for a new transactions (INVITE or REGISTER) until:
· There is a change in DNS responses indicating the proxy has become active.
· The configuration does not leave any better option available. In this case, there should be a throttle so that no
more than 5 failures (without successes) in 1 minute should be allowed.
· A config merge has occurred where the proxy string is changed.
· 10 minutes has expired.
Behaviour during Not Responding
A proxy server that is not-responding (UDP) is indicated when 3 requests are sent and no replies are received. This would
normally occur during a single INVITE transaction.
Consideration should be given whether this is caused by a local network fault or is caused by the Proxy being out of
service. Since it is likely to be local, no action should be taken unless traffic is received from an alternative proxy while this
proxy is actually not responding. The state should be "Possibly non responding".
If explicit DNS servers are configured, a DNS request should be sent out to see whether this Proxy server has disappeared
from those being offered.
If possible, an alternative proxy should be stimulated simultaneously with stimulating the suspect server.
The server should be considered non-responding if it is persistently nonresponding while other proxies are responding or if
it is non-responding and has disappeared from the DNS advertisement.
While in the "possibly not responding" state, it would be better to send an INVITE to an alternative proxy while
simultaneously sending any appropriate message to this proxy. This will help to resolve whether it is really not responding
rather than there being local network problems. However, there is no requirement to blacklist the proxy.
Once in the "definitely not responding" state:
· If there are other proxies available: this registration only should issue an Un-REGISTER, and try to REGISTER with
a different proxy. Calls should not automatically clear.
· If a SIP message is received from it, the state should immediately go"Active".
· This proxy should be blacklisted unless there are no better options available. While blacklisted, only one transaction
per 10 minutes is allowed.
· Even if not blacklisted, there should be a throttle so that no more than 5 failures (without successes) in 1 minute
should be alowed.
Manager Manager 8.1
Manager
Page 237
15-601011 Issue 25l (11 February 2011)
5.4.10.4 SIP URI
Having setup the SIP trunk to the SIP ITSP, the SIP URI's registered with that ITSP are entered on this tab. A SIP URI
(Uniform Resource Identifier) is similar to an internet email address, for example name@example.com, or
01555326978@example.com and represents the source or destination for SIP connection. The URI consists of two parts,
the user part (eg. name) and the host part (eg. example.com).
· IP Office 5.0+: If the wildcard * is used in the SIP trunk's Local URI, Contact and Display fields, that SIP trunk
will accept any incoming SIP call. The incoming call routing is still performed by the system incoming call routes
based on matching the values received with the call or the URI's incoming group setting. Outgoing calls using the
trunk will need to use another URI set against the trunk.
For the system, each SIP URI acts as a set of trunk channels. Outgoing calls can then be routed to the required URI by
short codes that match that URI's Outgoing Group setting. Incoming calls can be routed by incoming call routes that
match the URI's Incoming Group setting.
Note that the system only supports up to 150 URI entries on a SIP line.
Line | SIP URI
Control Unit
SOE
Software Level
4.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Via
This field is for information only and cannot be edited. It shows the IP address of the system LAN interface with which
the SIP trunk is associated.
· Local URI: Default = Use Authentication Name
This field sets the 'From' field for outgoing SIP calls using this URI. The value can either be entered manually or one of
the following options can be selected.
· Use Authentication Name: Software level = 4.0 to 5.0.
Use the appropriate Authentication Name on the SIP Line tab as indicated by the Registration setting below.
· Use Credentials User Name: Software level = 6.0+.
Use the User Name from the SIP Credentials entry used for the call.
· Use Internal Data
Use the SIP Name value from the User | SIP 303 tab of the user making the call. IP Office 6.0: The system can also
use SIP URI information configured for a hunt group (Hunt Group | SIP 322 ) or for the voicemail (System |
Voicemail 157 ).
· Contact: Default = Use Authentication Name
This field sets the 'Contact' field for SIP calls using this URI. The value can either be entered manually or one of the
following options can be selected.
· Use Authentication Name: Software level = 4.0 to 5.0.
Use the appropriate Authentication Name on the SIP Line tab as indicated by the Registration setting below.
· Use Credentials User Name: Software level = 6.0+.
Use the User Name from the SIP Credentials entry used for the call.
· Use Internal Data
Use the SIP Name value from the User | SIP 303 tab of the user making the call. IP Office 6.0: The system can also
use SIP URI information configured for a hunt group (Hunt Group | SIP 322 ) or for the voicemail (System |
Voicemail 157 ).
· Display Name: Default = Use Authentication Name
This field sets the 'Name' value for SIP calls using this URI. The value can either be entered manually or one of the
following options can be selected.
· Use Authentication Name: Software level = 4.0 to 5.0.
Use the appropriate Authentication Name on the SIP Line tab as indicated by the Registration setting below.
· Use Credentials User Name: Software level = 6.0+.
Use the User Name from the SIP Credentials entry used for the call.
· Use Internal Data
Use the SIP Name value from the User | SIP 303 tab of the user making the call. IP Office 6.0: The system can also
use SIP URI information configured for a hunt group (Hunt Group | SIP 322 ) or for the voicemail (System |
Voicemail 157 ).
· PAI: Default = None. Software level = 6.1
Select whether the PAI should be set and if so, the source of the value to use in the PAI field. The value can either be
entered manually or one of the following options can be selected.
Manager Manager 8.1
Manager
Page 238
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Line Settings
· None
Do not use the PAI field.
· Use Authentication Name: Software level = 4.0 to 5.0.
Use the appropriate Authentication Name on the SIP Line tab as indicated by the Registration setting below.
· Use Credentials User Name: Software level = 6.0+.
Use the User Name from the SIP Credentials entry used for the call.
· Use Internal Data
Use the SIP Name value from the User | SIP 303 tab of the user making the call. IP Office 6.0: The system can also
use SIP URI information configured for a hunt group (Hunt Group | SIP 322 ) or for the voicemail (System |
Voicemail 157 ).
· Registration: Default = Primary
Pre-IP Office 6.0: This field sets whether the primary or secondary authentication name values set on the SIP Line tab
should be used for calls by this SIP URI. IP Office 6.0: This field is used to select from a list of the account credentials
configured on the line's SIP Credentials tab.
· Incoming Group ID: Default = 0, Range 0 to 99999.
The Incoming Group ID to which a line belongs is used to match it to incoming call routes in the system configuration.
The matching incoming call route is then used to route incoming calls. The same ID can be used for multiple lines.
· Outgoing Group ID: Default = 0, Range 0 to 99999.
Short codes that specify a number to dial also specify the line group to be used. The system will then seize a line with a
matching Outgoing Group ID. The same ID can be used for multiple lines.
· Max Calls per Channel: Default =10
This field sets the maximum number of simultaneous calls that can use the URI before the system returns busy to any
further calls.
Manager Manager 8.1
Manager
Page 239
15-601011 Issue 25l (11 February 2011)
5.4.10.5 VoIP
· Compression Mode: Default = Automatic Selection
This field defines the compression mode (codec) or modes offered during call setup. The supported codecs are G.711
ALAW 64K, G.711 ULAW 64K, G.729(a) 8K CS-ACELP, G.723.1 6K3 MP-MLQ.
· Automatic Select
This setting is used as follows:
· Pre-IP Office 5.0: Automatic Select uses the codecs in the order of preference G729a, G711 ALAW, G711 ULAW
and G.723.1.
· IP Office 5.0+: The Automatic Codec Preference 160 setting (System | Telephony | Telephony 160 ) can be used to set
which codec should be first in the list of preferred codecs. The remaining codecs are used in the order as above. Note
that the G711 codecs are treated as a pair, so if one is selected as the first preference, the other will automatically be
second in the list.
· If required, a specific codec can be selected. However, if during call setup negotiation with a specific codec, connect
fails, the system will fallback to using automatic selection.
· Codecs not selected for a SIP connection are not used in codec negotiation. For H.323 it is not possible to exclude
codecs from negotiation, only to change the order of codec preference.
The Advanced button can be used to display a list of the codecs in their current order of preference. Codecs can be
dragged up or down the list or deselected from the list. Note that once a list has been edited in this way, clicking
Advanced again will return it to Automatic Select.
· Call Initiation Timeout: Default = 4 seconds, Range = 1 to 99 seconds. Software level = 4.2+.
This option sets how long the system should wait for a response to its attempt to initiate a call before following the
alternate routes set in an ARS 409 form.
· DTMF Support: Default = RFC2833.
This setting is used to select the method by which DTMF key presses are signalled to the remote end. The supported
options are In Band, RFC2833 or Info.
· VoIP Silence Suppression: Default = Off
When selected, this option will detect periods of silence on any call over the line and will not send any data during those
silent periods. This feature is not used on IP lines using G711 between systems.
· Fax Transport Support: Default = Off. Software level = 5.0+. IP500 and IP500v2 SIP lines.
This option is only available if Re-Invite Supported is selected. When enabled, the system performs fax tone detection
on calls routed via the line and, if fax tone is detected, renegotiates the call codec as configured below. The SIP line
provider must support the selected fax method and Re-Invite. The system must have available VCM resources using an
IP500 VCM base card. For systems in a Small Community Network, fax relay 749 is supported for fax calls between the
systems.
· None
Select this option if fax is not supported by the line provider.
· T38 (IP Office 6.0+)
T38 is supported for the sending and receiving of faxes on a SIP line if also supported for fax by the line provider.
· RE-Invite Supported: Default = Off.
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. Requires the
ITSP to also support Re-Invite.
· Use Offerer's Codec: Default = Off. Software level = 4.2+.
Normally for SIP calls, the initiator of the calls sends a SIP offer which includes the codecs that they support in order of
preference. The SIP response includes the codec they want to use for the call. This option can be used to override that
behaviour and use the codec preference offered by the caller.
Manager Manager 8.1
Manager
Page 240
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Line Settings
5.4.10.6 T38 Fax
The setting on this tab are only accessible if Re-invite Supported and Fax Transport Support are selected on the VoIP
240 tab. Fax relay 749 is only supported on IP500/IP500v2 systems with an IP500 VCM card.
SIP Line | T38 Fax
Control Unit
SOE
Software Level
5.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Use Default Values: Default = On.
If selected, all the fields are set to their default values and greyed out.
· T38 Fax Version: Default = 3.
The system can support Versions 0, 1, 2 and 3. During fax relay, the two gateways will negotiate to use the highest
version which they both support.
· Transport: Default = UDPTL (fixed).
Currently only UDPTL is supported. TCP and RTP transport are not supported.
· For UDPTL, redundancy error correction is supported. Forward Error Correction (FEC) is not supported.
· Redundancy:
Redundancy sends additional fax packets in order to increase the reliability. However increased redundancy increases
the bandwidth required for the fax transport.
· Low Speed: Default = 0 (No redundancy), Range = 0 to 5.
Sets the number of redundant T38 fax packets that should be sent for low speed V.21 T.30 fax transmissions.
· High Speed: Default = 0 (No redundancy). Range = 0 to 5.
Sets the number of redundant T38 fax packets that should be sent for V.17, V.27 and V.28 fax transmissions.
· TCF Method: Default = Trans TCF.
TCF = Training Check Frame.
· Max Bit Rate (bps): Default = 14400.
Lower rates can be selected if the current rate is not supported by the fax equipment or is found to not be reliable.
· EFlag Start Timer (msecs): Default = 2600.
· EFlag Stop Timer (msecs): Default = 2300.
· Tx Network Timeout (secs): Default = 150.
· Scan Line Fix-up: Default = On.
· TFOP Enhancement: Default = On.
· Disable T30 ECM: Default = Off.
When selected, disabled the T.30 Error Correction Mode used for fax transmission.
· Disable EFlags For First DIS: Default = Off.
· Disable T30 MR Compression: Default = Off.
· NSF Override: Default = Off.
If selected, the NSF (Non-Standard Facility) information sent by the T38 device can be overridden using the values in
the fields below.
· Country Code: Default = 0.
· Vendor Code: Default = 0.
Manager Manager 8.1
Manager
Page 241
15-601011 Issue 25l (11 February 2011)
5.4.10.7 SIP Credentials
IP Office 6.0+. It is used to enter the ITSP username and password for the SIP account with the ITSP. If you have several
SIP accounts going to the same ITSP IP address or domain name, you can enter up to 30 sets of ITSP account names and
passwords on this tab.
Line | SIP Line
Control Unit
SOE
Software Level
6.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
(Mergeable for Release 6.1+.
Use the Add..., Edit... and Remove buttons to manage the set of credentials for the SIP trunk accounts. The settings for
each account are:
· Index
This number is assigned automatically and cannot be edited. If the From field on the SIP URI 238 being used for the
call is set to Use Authentication Name , the registration field of the SIP URI will indicate the index number of the
SIP credentials to use for calls by that SIP URI.
· User Name
This name must be unique and is used to identify the trunk. The name can include the domain if necessary.
· Authentication Name: Default = Blank.
This field can be blank but must be completed is a Password is also specified. This value is provided by the SIP
ITSP . Depending on the settings on the Local URI tab associated with the SIP call, it may also be used as the user
part of the SIP URI. The name can include the domain if necessary.
· Contact: Default = Blank. Software level = 6.1.
This field is used to enter a contact and can include the domain if necessary.
· Password: Default = Blank.
This value is provided by the SIP ITSP. If a password is specified the matching Authentication Name must also be
set.
· Expiry: Default = 60 minutes.
This setting defines how often registration with the SIP ITSP is required following any previous registration.
· Registration Required: Default = On. Software level = 6.1
If selected, the fields above above are used for registration when making calls.
Manager Manager 8.1
Manager
Page 242
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Line Settings
5.4.11 SES Line
SES lines are used for connection to an Avaya SIP Enablement Service (SES) server within an Avaya SIP for Branch
network. This is a variant of TCP SIP line and requires SIP Trunk Channels licenses in the system configuration for the
number of simultaneous SIP and or SES calls. The SES server supports up to 1000 branches arranged in a star network
configuration.
With an Avaya SIP for Branch network, all extensions are reachable from any branch. Using short codes, the system
should be configured to route calls for other branches in the network to the SES server via a SES line. The SES server
acts as a SIP proxy. It holds a table of all branch prefixes and uses that table to reroute each call to the appropriate
destination branch. The SES server will only route calls to the branch if the number match both the branch prefix and the
expected extension number length.
Related Fields
There are a number of fields in the system configuration which are used with SES lines but are not on the SES Line form.
The following are located on the System | System 143 tab:
· Branch Prefix: Default = Blank, Range = 0 to 999999999. Software level = 4.1+.
Used to identify the system within an Avaya SIP for Branch network linked via an SES server. The branch prefixes of
each systems within the network must unique and must not overlap. For example 85, 861 and 862 are okay, but 86 and
861 overlap.
· Local Number Length: Default = Blank (Off), Range = Blank (Off) or 3 to 9. Software level = 4.1+.
Set the default length for extension numbers for extensions, users and hunt groups. Entry of an extension number of a
different length will cause an error warning within Manager.This field is intended for systems being used in an Avaya SIP
for Branch network linked via an SES server, where fixed extension lengths must be used. Note that the Branch Prefix
and the Local Number Length must not exceed 15 digits.
Short Codes
Calls are routed to the SES line using short codes in the same was as for other line types. The short codes can route calls
directly to the SES line's Outgoing Group ID or to an ARS form configured for the SES line. If at all possible, requiring a
short code for each branch within the SIP for Branch Network should be avoided.
· Common Branch Prefix Leading Digit Routing
If a common digit has been used at the start of all branch prefixes, that digit can be used as the key for a single
SES routing short code. For example, first use a single range for branch prefixes, ie. 80 to 89 in a small network,
800 to 899 in a medium network or 8000 to 8999 in a large network. At each branch a single short code of the
form 8N could then be used to start SES routing.
· Common Branch Prefix and Extension Length Routing
If the above method cannot be used, maintaining a common branch prefix and local number length throughout the
network is another option to simplify routing. For example, if all branches have a two digit branch prefixes and then
4 digit extension numbers, a short code of the form XXXXXX; could be used to only match dialed six digit numbers.
Longer dialing is still possible so long as the first additional digit is dialed within the Dial Delay Time setting of the
system.
· SES Line Prefix
The SES line includes a prefix field that can be added to any calling number information supplied with calls received
on a SES line. That prefix can then be used as the mechanism to route return calls back to the SES line. For
example, if the line prefix is 3, a short code of the form 3N/N can be used.
Manager Manager 8.1
Manager
Page 243
15-601011 Issue 25l (11 February 2011)
Additional Notes
1. Voice Compression Channels
SES calls use system voice compression channels in the same way as used for standard IP trunks and extensions.
These are provided by the installation of VCM modules within the control unit. RTP relay is applied to SES calls
where applicable.
2. Licensing
SIP Trunk Channels licenses is required in the system configuration. These set the maximum number of
simultaneous SIP and SES calls supported by the system. Multiple licenses can be added to achieve a cumulative
maximum number of channels supported.
3. Firewall
The system firewall between LAN1 and LAN2 is not applied to SES calls.
4. Incoming Call Routing
Incoming SES calls are routed as if being internal calls. The dialed branch prefix is removed and the remaining
extension number is used as if dialed on switch.
5. DiffServ Marking
DiffServ marking is applied to calls using the DiffServ Settings on the System | LAN | VoIP
or LAN2 as set by the line's Use Network Topology Info setting.
150
tab of either LAN1
Resource Limitation
A number of limits can affect the number of SES calls. When one of these limits is reached the following occurs: any
further outgoing SES calls are blocked unless some alternate route is available using ARS; any incoming SES calls are
queued until the required resource becomes available.
Limiting factors are:
· the number of licensed SIP channels.
· the Max Calls setting of the SES line.
· the number of voice compression channels.
· SES Line Call to/from Non-IP Devices
Voice compression channel required.
· Outgoing SES Line Call from IP Device
No voice compression channel required.
· Incoming SIP Line Call to IP Device
Voice compression channel reserved until call connected.
· If the system also used SIP trunks, the same resources are shared between SES and SIP calls.
Manager Manager 8.1
Manager
Page 244
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Line Settings
5.4.11.1 SES Line
Line | SES Line
Control Unit
SOE
Software Level
4.1+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Line Number: Default = Automatically assigned.
By default a value is assigned by the system. This value can be changed but it must be unique.
· Network Type: Default = Public. Software level = 4.2+.
This option is available if Restrict Network Interconnect 160 (System | Telephony | Telephony 160 ) is enabled. It
allows the trunk to be set as either Public or Private. The system will return number unobtainable indication to any
attempt to connect a call on a Private trunk to a Public trunk or vice versa. This restriction includes transfers,
forwarding and conference calls.
· Due to the nature of this feature, its use is not recommended on systems also using any of the following other
system features: Small Community Networks 810 , VPNremote, Phone Manager telecommuter mode.
· SES Domain Name: Default = Blank.
This field is used to enter the domain part of the SIP URI provided by the ITSP. For example, in the SIP URI
mysip@example.com, the domain part of the URI is example.com. For outgoing calls the user part of the SIP URI is the
Branch Prefix and the extension number.
· SES Address: Default = 0.0.0.0
This value is the public IP address of the SES server. This address must not be shared by any other IP, IP DECT or SIP
line in the system configuration.
· Inactivity Timeout (seconds): Default = 120, Range = 0 to 99999 seconds.
If no SIP messages or signalling have been sent or received during this period the system will close the connection.
· Outgoing Group: Default = 0, Range 0 to 99999.
Short codes that specify a number to dial also specify the line group to be used. The Manager will then seize a line with
a matching Outgoing Group ID.
· Prefix: Default = Blank.
This prefix will be added to any source number received with incoming calls. Normally this should match a dialing short
code configured to route matching calls to the SES line's Outgoing Group ID number.
· Max Calls: Default =10
This field sets the maximum number of simultaneous calls that can use the URI before the system returns busy to any
further calls.
· In Service: Default = On.
When this field is not selected, the SIP trunk is unregistered and not available to incoming and outgoing calls.
· Network Configuration
· Layer 4 Protocol: Default = TCP
This field cannot be changed.
· Use Network Topology Info: Default = LAN1
For various settings, this field indicates whether the SES line uses the System | LAN | Network Topology 152 settings
of either LAN1 or LAN2. For instance the DiffServ Settings applied to outgoing SES calls and the IP address (see
description of Via Nat below).
· Send Port: Default = 5060
This field cannot be changed.
· Listen Port: Default = 5060
This field cannot be changed.
· Via NAT: Default = Off.
This option controls which address should be used as the IP address of the system that is entered into the SES server
configuration.
· If disabled, the address used is the IP Address 149 of the system as set on the LAN Settings sub-tab of LAN1 or
LAN2. The selection of LAN1 or LAN2 is determined by the Use Network Topology field above.
· If enabled, the address used is the Public IP Address 149 as set on the Network Topology sub-tab of LAN1 or LAN2.
The selection of LAN1 or LAN2 is determined by the Use Network Topology field above.
Manager Manager 8.1
Manager
Page 245
15-601011 Issue 25l (11 February 2011)
Prefix Allocation Check
As SES lines are configured within each system in the SIP for Branch network, details of the system can be written to a
CSV file. This file can then be used to ensure the following:
1. Check branch allocation
Check that the settings of the system and SES line being added are both complete and do not conflict with those of
other systems already added to the CSV file. Select this option and click Execute , then select the CSV file
containing details of the other systems with SES lines.
2. List branch allocations
Provide the source of the details that need to be entered in the SES server configuration for each system. Select
this option and click Execute to select and display the CSV file containing details of existing system SES line
settings. This file provides the information necessary for matching line entries in the SES server configuration.
Manager Manager 8.1
Manager
Page 246
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Line Settings
5.4.11.2 VoIP
Line | SES Line
Control Unit
SOE
Software Level
4.1+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Gateway IP Address: Default = Blank
Enter the IP address of the gateway device at the remote end. This address must not be shared by any other IP line
(H323, SIP, SES or IP DECT).
· Compression Mode: Default = Automatic Selection
This field defines the compression mode (codec) or modes offered during call setup. The supported codecs are G.711
ALAW 64K, G.711 ULAW 64K, G.729(a) 8K CS-ACELP, G.723.1 6K3 MP-MLQ.
· Automatic Select
This setting is used as follows:
· Pre-IP Office 5.0: Automatic Select uses the codecs in the order of preference G729a, G711 ALAW, G711 ULAW
and G.723.1.
· IP Office 5.0+: The Automatic Codec Preference 160 setting (System | Telephony | Telephony 160 ) can be used to set
which codec should be first in the list of preferred codecs. The remaining codecs are used in the order as above. Note
that the G711 codecs are treated as a pair, so if one is selected as the first preference, the other will automatically be
second in the list.
· If required, a specific codec can be selected. However, if during call setup negotiation with a specific codec, connect
fails, the system will fallback to using automatic selection.
· Codecs not selected for a SIP connection are not used in codec negotiation. For H.323 it is not possible to exclude
codecs from negotiation, only to change the order of codec preference.
The Advanced button can be used to display a list of the codecs in their current order of preference. Codecs can be
dragged up or down the list or deselected from the list. Note that once a list has been edited in this way, clicking
Advanced again will return it to Automatic Select.
· Call Initiation Timeout: Default = 4 seconds, Range = 1 to 99 seconds. Software level = 4.2+.
This option sets how long the system should wait for a response to its attempt to initiate a call before following the
alternate routes set in an ARS 409 form.
· DTMF Support: Default = RFC2833.
This setting is used to select the method by which DTMF key presses are signalled to the remote end. The supported
options are In Band, RFC2833 or Info.
· VoIP Silence Suppression: Default = Off
When selected, this option will detect periods of silence on any call over the line and will not send any data during those
silent periods. This feature is not used on IP lines using G711 between systems.
· Local Tones: On (Fixed)
Indicates that the system will generate tones when required.
· Allow Direct Media Path: Default = On
This settings controls whether H323 calls must be routed via the H323 gatekeeper (the system) or can be routed
alternately if possible within the network structure.
· If enabled, H323 calls can take routes other than through the system. This removes the need for a voice compression
channel. Both ends of the calls must support Direct Media. Enabling this option may cause some vendors problems
with changing the media path in mid call. Pre-IP Office 4.0, when using direct media path, it is not always possible for
the extension to be recorded or monitored.
· If disabled or not supported at on one end of the call, the call is routed via the system.
· On pre-4.0 these calls would then require a voice compression channel even if the IP devices use the same audio
codec.
· On IP Office 4.0 and higher, RTP relay support allows calls between devices using the same audio codec to not
require a voice compression channel.
· RE-Invite Supported: Default = Off.
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. Requires the
ITSP to also support Re-Invite.
Manager Manager 8.1
Manager
Page 247
15-601011 Issue 25l (11 February 2011)
· Use Offerer's Codec: Default = Off. Software level = 4.2+.
Normally for SIP calls, the initiator of the calls sends a SIP offer which includes the codecs that they support in order of
preference. The SIP response includes the codec they want to use for the call. This option can be used to override that
behaviour and use the codec preference offered by the caller.
Manager Manager 8.1
Manager
Page 248
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Line Settings
5.4.11.3 T38 Fax
The setting on this tab are only accessible if Re-invite Supported and Fax Transport Support are selected on the VoIP
247 tab. Fax relay 749 is only supported on IP500/IP500v2 systems with an IP500 VCM card.
SIP Line | T38 Fax
Control Unit
SOE
Software Level
5.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Use Default Values: Default = On.
If selected, all the fields are set to their default values and greyed out.
· T38 Fax Version: Default = 3.
The system can support Versions 0, 1, 2 and 3. During fax relay, the two gateways will negotiate to use the highest
version which they both support.
· Transport: Default = UDPTL (fixed).
Currently only UDPTL is supported. TCP and RTP transport are not supported.
· For UDPTL, redundancy error correction is supported. Forward Error Correction (FEC) is not supported.
· Redundancy:
Redundancy sends additional fax packets in order to increase the reliability. However increased redundancy increases
the bandwidth required for the fax transport.
· Low Speed: Default = 0 (No redundancy), Range = 0 to 5.
Sets the number of redundant T38 fax packets that should be sent for low speed V.21 T.30 fax transmissions.
· High Speed: Default = 0 (No redundancy). Range = 0 to 5.
Sets the number of redundant T38 fax packets that should be sent for V.17, V.27 and V.28 fax transmissions.
· TCF Method: Default = Trans TCF.
TCF = Training Check Frame.
· Max Bit Rate (bps): Default = 14400.
Lower rates can be selected if the current rate is not supported by the fax equipment or is found to not be reliable.
· EFlag Start Timer (msecs): Default = 2600.
· EFlag Stop Timer (msecs): Default = 2300.
· Tx Network Timeout (secs): Default = 150.
· Scan Line Fix-up: Default = On.
· TFOP Enhancement: Default = On.
· Disable T30 ECM: Default = Off.
When selected, disabled the T.30 Error Correction Mode used for fax transmission.
· Disable EFlags For First DIS: Default = Off.
· Disable T30 MR Compression: Default = Off.
· NSF Override: Default = Off.
If selected, the NSF (Non-Standard Facility) information sent by the T38 device can be overridden using the values in
the fields below.
· Country Code: Default = 0.
· Vendor Code: Default = 0.
Manager Manager 8.1
Manager
Page 249
15-601011 Issue 25l (11 February 2011)
5.5 Control Unit
The Control Unit configuration form gives details for devices connected to the system. This includes some
modules within the control unit as well as external expansion modules.
For most units, this information is allocated by the system and is not configurable.
The New and Delete actions on this form have special functions.
· New
This action is used to added a WAN3 expansion module. If when a WAN3 is added to the system, the WAN3 is not
recognized following a system reboot, New on this form can be used to scan for the WAN3 module.
· Delete
This action can only be used with external expansion modules. It cannot be applied to the control unit. The action
should used with caution as deleting a module will also delete any extensions or lines associated with that module.
If the module is physically present, those entries will be recreated following a reboot but with default settings.
Control Unit | Control Unit
Control Unit
SOE
, IP403
Software Level
1.0+.
Mergeable
Pre-3.2
, 3.2+
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Device Number
This is automatically allocated by the system.
· Unit Type
The name of the device.
· Version
The version of software running on each unit.
· Serial Number
This is the number the system uses to tie a physical Control Unit to a device configuration (device number). For the
control unit and WAN3 modules this is the MAC address. For a device connected to an Expansion port it is the Expansion
port number plus 1.
· Unit IP Address
This field shows the IP address for the control unit (LAN1) and if present, WAN3 expansion module.
· Interconnect Number
For external expansion modules this is the control unit expansion port used for connection. For other devices this is 0.
· Module Number
For external expansion modules this is the control unit expansion port used for connection. For internal devices in the
control unit, Control Unit is displayed.
Manager Manager 8.1
Manager
Page 250
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Control Unit
5.6 Extension Settings
The system supports both physical extensions and IP extensions.
By default, each extension is normally associated with a user and uses that user's directory number and
other setting. Users with a log in code can move between extensions by logging in and out, so the directory
number is not a fixed property of the extension.
· Physical Extensions
Physical extension ports are either integral to the control unit or added by the installation of an analog or digital phone
expansion module. Extension entries are automatically created for each physical extension port within the system.
These ports cannot be added or deleted manually.
·
Standard Telephone
An analog extension port (PHONE or POT) or an Avaya digital station port (DS) within the system.
·
Quiet Headset
Used for analog extension devices that are permanently off-hook.
·
IVR Port
Used for analog ports connected to devices that require a specific disconnect clear signal at the end of each call.
·
Paging Speaker
An analog extension port set to be used as a paging speaker connection.
·
FAX Machine
Indicates that the extension is connected to a FAX machine.
·
MOH Source
Indicates that the extension is being used as a music on hold source.
· IP Extensions
These are used for IP phone devices or applications.
·
H323 or SIP Extension
This icon indicates an IP extension. For Avaya IP hardphones the IP extensions is either added manually or by the
automatic detection the phone being connected, refer to the Manager IP Phone Installation Manual. IP extensions can
also be added manually to support a Phone Manager Pro PC Softphone or a third-party IP phone device. Note that
third-party IP phone devices require entry of an IP End-Points license.
·
IP DECT
An extension port manually added to match extensions within an Avaya IP DECT system connected to the system via
an IP DECT line.
For systems with users using the IP Office Video Softphone, an extension entry is created while the user is logged into the
application. This entry is not editable. The softphone extension entry is automatically deleted within a few minutes of the
user closing the softphone application.
Manager Manager 8.1
Manager
Page 251
15-601011 Issue 25l (11 February 2011)
5.6.1 Extn
This tab contains settings applicable to most types of extension.
Extension | Extn
Control Unit
SOE
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
Software Level
1.0+.
Mergeable
. For Manager 4.1+, Base Extension, Disable Speakerphone and Reset Volume After
Calls are mergeable.
· Extension ID
The physical ID of the extension port. Except for IP extensions, this settings is allocated by the system and is not
configurable.
· Base Extension: Range = 2 to 9 digits.
This is the directory number of the extension's default associated user.
· Following a restart, the system will attempt to log in the user with the same extension number (if they are not
already logged in elsewhere in the Small Community Network). This does not occur it that user is set to Force Login
(User | Telephone 274 ).
· If another user logs onto an extension, when they log out, the extension returns to its default associated user unless
they have logged in elsewhere or are set to Force Login.
· In the US the Base Extension number is used for E911 calls. Any change to an extension's base extension must be
matched by changes to the E911 adjunct database, see E911 Overview 421 . The extensions default associated user
should not be deleted.
· Extensions associated with IP phones should not be given extension numbers greater than 7 digits.
· For pre-IP Office 6.0, extension numbers in the range 8897 to 9999 are reserved for use by the Delta Server.
· Users for Delta Server, CBC and CCC should only use up to 4 digit extension numbers.
· Caller Display Type: Default = On.
Controls the presentation of caller display information for analog extensions, see Caller Display 755 . For digital and IP
extensions, this value is fixed as On. The table below lists the supported options, all others are currently not used and
default to matching UK.
Type
Description
Off
Disables caller display.
On
Enables caller display using the caller display type appropriate to the System Locale, see Supported
Country and Locale Settings 844 . If a different setting is required it can be selected from the list of
supported options. For an analog extension connected to a fax server or other device that requires the
pass through of DTMF tones, select DTMFF.
UK
FSK before the first ring conforming to BT SIN 227. Name and number.
UK20
As per UK but with a maximum length of 20 characters. Name and number.
DTMFA
Caller ID in the DTMF pattern A<caller ID>C. Number only.
DTMFB
Caller ID in DTMF after call connection. Number only.
DTMFC
Caller ID in the DTMF pattern A<caller ID>#. Number only.
DTMFF
Sends the called number in DTMF after call connection. Number only. Used for fax servers. When calls are
delivered via a hunt group it is recommended that hunt group queuing is not used. If hunt group queuing is
being used, set the Queue Type to Assign Call on Agent Alert.
DTMFD Caller ID in the DTMF pattern D<caller ID>C. Number only.
FSKA
Variant of UK used for BT Relate 1100 phones. Name and number.
FSKB
ETSI specification with 0.25 second leading ring. Name and number.
FSKC
ETSI specification with 1.2 second leading ring. Name and number.
FSKD
Conforms to Belcore specification. Name and number.
· Reset Volume after Calls: Default = Off.
Resets the phone's handset volume after each call. This option is supported on Avaya 1400, 1600, 2400, 4400, 4600,
5400, 5600, 6400 and 9600 Series phones.
· Device Type
This field indicates, the last known type of phone connected to the extension port.
· Analogue extension ports always report as Analog Handset since the presence or absence of actual analog phone
cannot be detected.
Manager Manager 8.1
Manager
Page 252
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Extension Settings
· Digital extension ports report the type of digital phone connected or Unknown digital handset if no phone is
detected.
· H323 extensions report the type of IP phone registered or Unknown H323 handset if no phone is currently
registered as that extension.
· SIP extensions report the type of SIP phone registered or Unknown SIP device if no SIP device is currently
registered as that extension.
· For some types of phone, the phone can only report its general type to the system but not the specific model.
When that is the case, the field acts as a drop-drown to allow selection of a specific model. The value selected here
is also reported in other applications such as the System Status Application, SNMP, etc.
Default Type
Possible Phone Models
T7100
M7100, M7100N, T7100, Audio Conferencing Unit.
T7208
M7208, M7208N, T7208.
M7310
M7310, M7310N, T7406, T7406E.
M7310BLF
M7310BLF, T7316.
M7324
M7324, M7324N.
· Module
This field indicates the external expansion module on which the port is located. BP indicates an analog phone extension
port on the base or control unit. BD indicates a digital station (DS) port on the control unit. For an IP500/IP500v2
control unit, BD and BP is also followed by the slot number. VoIP extensions report as 0.
· Port
This field indicates the port number on the Module indicated above. VoIP extensions report as 0.
· Disable Speakerphone: Default = Off (Speakerphone enabled). Software level = 4.1+.
When selected, disables the fixed SPEAKER button if present on the phone using this extension port. Only supported on
Avaya DS, TCM and H323 IP phones. An audible beep is sounded when a disabled SPEAKER button is pressed.
Incoming calls such as pages and intercom calls are still connected but the speech path is not audible until the user
goes off-hook using the handset or headset. Similarly calls made or answered using other buttons on the phone are not
audible unless the user goes off-hook using the handset or headset. Currently connected calls are not affected by
changes to this setting.
· Force Authorization: Default = On. Software level = 5.0+, SIP Extensions only.
This setting is used with SIP extension devices.
·
Manager Manager 8.1
Manager
Page 253
15-601011 Issue 25l (11 February 2011)
5.6.2 Analog
This tab contains settings that are applicable to analog extensions. These extensions are provided by ports marked as POT
or PHONE on control units and expansion modules.
Extension | Analog
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
. For IP Office 6.1+, Equipment Classification is mergeable.
· Equipment Classification: Default = Standard Telephone
Only available for analog extension ports. Note that changing this settings should be followed by a system reboot. For IP
Office 6.1 changes to this setting are mergeable.
· Quiet Headset
On extensions set to Quiet Headset, the audio path is disabled when the extension is idle. Ringing is presented in
the audio path. Caller ID is not supported on the phone. This option can be used with analog extensions where the
handset is replaced by a headset since in such a scenario audio is only desired when a call is connected. Since the
audio path is disabled when idle, the Quiet Headset extension cannot dial digits to make calls. Therefore to make
and answer calls this option is typically used with the user Offhook Station 274 (User | Telephony | Call Settings 274 )
setting which allows the extension user to make and answer calls using applications.
· Paging Speaker
Used for analog ports connected to a paging amplifier. This extension will present busy and cannot be called or be
used to make calls. It can only be accessed using Dial Paging 459 features.
· IP Office 4.0+: When using a UPAM connected to an analog extension port, the extension's Equipment
Classification 254 (Extension | Analog) 254 should be set to IVR Port and not Paging Speaker.
· Standard Telephone
Use for normal analog phones.
· Door Phone 1/Door Phone 2
These two options are currently not used and so are grayed out.
· IVR Port
Used for analog ports connected to devices that require a disconnect clear signal (ie. a break in the loop current) at
the end of each call. When selected the Disconnect Pulse Width is used. For pre-3.2 systems, this option was only
supported on systems with the locale set to United States or Saudi Arabia.
· FAX Machine (IP Office 5+)
If fax Relay 749 is being used, this setting should be selected on any analog extension connected to an analog fax
machine.
· MOH Source (IP Office 6.1+)
If selected, the port can be used as a music on hold source in the Tones and Music 163 settings. An extension set as
a music on hold source cannot make or receive calls. The audio input can be monitored through the extension music
on hold 763 controls. A suitable interface device is required to provide the audio input to the extension port. It must
look to the system like an off-hook analog phone. For example a transformer with a 600 Ohm winding (such as a
Bogen WMT1A) or a dedicated MoH device with a 600Ohm output designed for connection to a PBX extension port
which is providing loop current can be used.
· Message Waiting Lamp Indication Type: Default = None
Allows the selection of the message waiting indication (MWI) mode for analog and IP DECT extensions.
· For control unit and Phone V1 module analog extensions, the options None, On, 51V Stepped, 81V, Line
Reversal A and Line Reversal B are available.
· For Phone V2 external module extensions and IP500 Phone base cards, the additional option 101V is available.
· On defaults the message waiting indication as follows using the system locale.
Locale
'On' =
Argentina, Australia, Brazil, Canada, Chile, China, Colombia, Japan,
Korea, Mexico, New Zealand, Peru, Russia, Saudi Arabia, South Africa,
Spain, United States, Venezuela.
51V Stepped
Bahrain, Belgium, Denmark, Egypt, Finland, France, Germany, Greece,
Hong Kong, Hungary, Iceland, Italy, India, Kuwait, Morocco,
Netherlands, Norway, Oman, Pakistan, Poland, Portugal, Qatar,
Singapore, Sweden, Switzerland, Taiwan, Turkey, United Arab
Emirates, United Kingdom.
On = 101V on Phone V2
modules and IP500 Phone
cards, otherwise 81V.
Manager Manager 8.1
Manager
Page 254
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Extension Settings
· IP500v2: If the option Restrict Analog Extension Ringer Voltage is selected (System | Telephony | Telephony
160 ), the MWI options are restricted to Line Reversal A, Line Reversal B or None. Any extensions set to another
option are forced to Line Reversal A.
· Hook Persistency: Default = 100ms, Range = 50 to 255ms.
Defines the time frame (in milliseconds) in which the system will wait before determining that the phone is off-hook.
· Flash Hook Pulse Width
The following options are only available for analog extension ports. They define the length of loop break that will be
considered a time break recall (TBR) signal.
· Use System Defaults: Default = Selected (On)
Use the default values appropriate to the system's locale. See Appendix A: Locale Settings
844 .
· Minimum Width: Range = 0 to 2540 milliseconds.
Minimum hook flash length used if Use System Defaults is not selected. Shorter breaks are ignored a glitches.
· Maximum Width: Range = 0 to 2550 milliseconds.
Maximum hook flash length used if Use System Defaults is not selected. Longer breaks are treated as clearing.
· Disconnect Pulse Width: Default = 0ms, Range = 0 to 2550ms
This setting is used with analog extensions where the Equipment Classification above has been set to IVR Port. It
sets the length of loop current break used to indicate call clearing.
Manager Manager 8.1
Manager
Page 255
15-601011 Issue 25l (11 February 2011)
5.6.3 VoIP
This tab is only available for H323 and SIP extensions. The settings available will vary depending on the extension type:
· H323 IP Extension
· SIP Extension
256
258
H323 IP Extension
Extension | VoIP
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· IP Address: Default = 0.0.0.0
The IP address of the phone. The default entry accepts connection from any address. For phones using DHCP, the field
is not updated to show the IP address being used by the phone except for T3 IP phones.
· MAC Address: Default = 0000000000000 (Grayed out)
This field is grayed out and not used.
· Compression Mode: Default = Automatic Selection
This field defines the compression mode (codec) or modes offered during call setup. The supported codecs are G.711
ALAW 64K, G.711 ULAW 64K, G.729(a) 8K CS-ACELP, G.723.1 6K3 MP-MLQ.
· Automatic Select
This setting is used as follows:
· Pre-IP Office 5.0: Automatic Select uses the codecs in the order of preference G729a, G711 ALAW, G711 ULAW
and G.723.1.
· IP Office 5.0+: The Automatic Codec Preference 160 setting (System | Telephony | Telephony 160 ) can be used to set
which codec should be first in the list of preferred codecs. The remaining codecs are used in the order as above. Note
that the G711 codecs are treated as a pair, so if one is selected as the first preference, the other will automatically be
second in the list.
· If required, a specific codec can be selected. However, if during call setup negotiation with a specific codec, connect
fails, the system will fallback to using automatic selection.
· Codecs not selected for a SIP connection are not used in codec negotiation. For H.323 it is not possible to exclude
codecs from negotiation, only to change the order of codec preference.
· Gain: Default = Default. Software level = 3.0 to 4.1.
Allows adjustment of the volume. The gain is selectable from -31dB to +31dB in 1dB increments.
· TDM->IP Gain: Default = Default (0dB). Range = -31dB to +31dB. Software level = 4.1 Q1 2008+.
Allows adjustment of the gain on audio from the system TDM interface to the IP connection.
· IP->TDM Gain: Default = Default (0dB). Range = -31dB to +31dB. Software level = 4.1 Q1 2008+.
Allows adjustment of the gain on audio from the IP connection to the system TDM interface.
· Supplementary Services: Default = H450. Software level = 4.0+.
Selects the supplementary service signaling method for use with non-Avaya IP devices. Options are None, QSIG and
H450. For H450, hold and transfer are supported. Note that the selected method must be supported by the remote
end.
· 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. This feature is not used on IP lines using G711 between systems.
· Enable FastStart for non-Avaya IP Phones: Default = Off
A fast connection procedure. Reduces the number of messages that need to be exchanged before an audio channel is
created.
· Out of Band DTMF: Default = On
When on, DTMF is sent as a separate signal ("Out of Band") rather than as part of the encoded voice stream ("In
Band"). The "Out of Band" signaling is inserted back into the audio by the remote end. This is recommended for low bitrate compression modes such as G.729 and G.723 where DTMF in the voice stream can become distorted. Switch off for
T3 IP extensions.
· For Avaya 1600, 4600, 5600 and 9600 Series phones the system will enforce the appropriate setting for the phone
type.
· For Avaya T3 IP phones, when Out-Of-Band is unchecked, the Allow Direct Media Path option is ignored and
calls are via the system in order to provide tones.
Manager Manager 8.1
Manager
Page 256
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Extension Settings
· Local Tones: Default = Off
When selected, the H.323 phones generate their own tones. This option is not supported by Avaya IP phones and Phone
Manager Pro PC Softphone.
· Allow Direct Media Path: Default = On
This settings controls whether H323 calls must be routed via the H323 gatekeeper (the system) or can be routed
alternately if possible within the network structure.
· If enabled, H323 calls can take routes other than through the system. This removes the need for a voice compression
channel. Both ends of the calls must support Direct Media. Enabling this option may cause some vendors problems
with changing the media path in mid call. Pre-IP Office 4.0, when using direct media path, it is not always possible for
the extension to be recorded or monitored.
· If disabled or not supported at on one end of the call, the call is routed via the system.
· On pre-4.0 these calls would then require a voice compression channel even if the IP devices use the same audio
codec.
· On IP Office 4.0 and higher, RTP relay support allows calls between devices using the same audio codec to not
require a voice compression channel.
· T3 IP phones must be configured to 20ms packet size to use RTP relay. With the IP Office 4.0 Q2 2007
maintenance release, previous restrictions on T3 IP phones using direct media were removed. The phone must
have firmware T246 or higher.
· VPN Phone Allowed: Default = Off. Software level = 4.1 - 5.0.
Indicates that the extension can be used with Avaya VPNremote Phone firmware. The phones must be licensed using a
VPN IP Extensions licenses added to the system configuration for the number of VPN IP phones required. Note that
the field is grayed out if there are no available licenses. Note that this license is no longer used for IP Office 6.0, phones
using VPNremote being licensed through standard Avaya IP Phone licenses.
· Reserve Avaya IP Endpoint License: Software level = 6.0+.
Avaya IP phones require an Avaya IP Endpoint license 834 . Normally licenses are issued in the order that devices
register. This option allows this extension to be pre-licensed before the device has registered.
· Reserve 3rd Party IP Endpoint License: Software level = 6.0+.
Non-Avaya IP phones require an 3rd Party IP Endpoint license 834 . Normally licenses are issued in the order that devices
register. This option allows this extension to be pre-licensed before the device has registered.
Manager Manager 8.1
Manager
Page 257
15-601011 Issue 25l (11 February 2011)
SIP Extension
Extension | VoIP (SIP)
Control Unit
SOE
Software Level
5.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· IP Address: Default = 0.0.0.0
The IP address of the phone. The default entry accepts connection from any address. If an address is entered,
registration is only accepted from a device with that address.
· Compression Mode: Default = Automatic Selection
This field defines the compression mode (codec) or modes offered during call setup. The supported codecs are G.711
ALAW 64K, G.711 ULAW 64K, G.729(a) 8K CS-ACELP, G.723.1 6K3 MP-MLQ.
· Automatic Select
This setting is used as follows:
· Pre-IP Office 5.0: Automatic Select uses the codecs in the order of preference G729a, G711 ALAW, G711 ULAW
and G.723.1.
· IP Office 5.0+: The Automatic Codec Preference 160 setting (System | Telephony | Telephony 160 ) can be used to set
which codec should be first in the list of preferred codecs. The remaining codecs are used in the order as above. Note
that the G711 codecs are treated as a pair, so if one is selected as the first preference, the other will automatically be
second in the list.
· If required, a specific codec can be selected. However, if during call setup negotiation with a specific codec, connect
fails, the system will fallback to using automatic selection.
· Codecs not selected for a SIP connection are not used in codec negotiation. For H.323 it is not possible to exclude
codecs from negotiation, only to change the order of codec preference.
· Fax Transport Support: Default = Off. Software level = 5.0+. IP500 and IP500v2 SIP lines.
This option is only available if Re-Invite Supported is selected. When enabled, the system performs fax tone detection
on calls routed via the line and, if fax tone is detected, renegotiates the call codec as configured below. The SIP line
provider must support the selected fax method and Re-Invite. The system must have available VCM resources using an
IP500 VCM base card. For systems in a Small Community Network, fax relay 749 is supported for fax calls between the
systems.
· None
Select this option if fax is not supported by the line provider.
· T38 (IP Office 6.0+)
T38 is supported for the sending and receiving of faxes on a SIP line if also supported for fax by the line provider.
· Gain: Default = Default. Software level = 3.0 to 4.1.
Allows adjustment of the volume. The gain is selectable from -31dB to +31dB in 1dB increments.
· TDM->IP Gain: Default = Default (0dB). Range = -31dB to +31dB. Software level = 4.1 Q1 2008+.
Allows adjustment of the gain on audio from the system TDM interface to the IP connection.
· IP->TDM Gain: Default = Default (0dB). Range = -31dB to +31dB. Software level = 4.1 Q1 2008+.
Allows adjustment of the gain on audio from the IP connection to the system TDM interface.
· DTMF Support: Default = RFC2833.
This setting is used to select the method by which DTMF key presses are signalled to the remote end. The supported
options are In Band, RFC2833 or Info.
· VoIP Silence Suppression: Default = Off
When selected, this option will detect periods of silence on any call over the line and will not send any data during those
silent periods. This feature is not used on IP lines using G711 between systems.
· Local Hold Music: Default = Off
· Allow Direct Media Path: Default = On
This settings controls whether H323 calls must be routed via the H323 gatekeeper (the system) or can be routed
alternately if possible within the network structure.
· If enabled, H323 calls can take routes other than through the system. This removes the need for a voice compression
channel. Both ends of the calls must support Direct Media. Enabling this option may cause some vendors problems
with changing the media path in mid call. Pre-IP Office 4.0, when using direct media path, it is not always possible for
the extension to be recorded or monitored.
· If disabled or not supported at on one end of the call, the call is routed via the system.
· On pre-4.0 these calls would then require a voice compression channel even if the IP devices use the same audio
codec.
Manager Manager 8.1
Manager
Page 258
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Extension Settings
· On IP Office 4.0 and higher, RTP relay support allows calls between devices using the same audio codec to not
require a voice compression channel.
· RE-Invite Supported: Default = Off.
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. Requires the
ITSP to also support Re-Invite.
· Use Offerer's Codec: Default = Off. Software level = 4.2+.
Normally for SIP calls, the initiator of the calls sends a SIP offer which includes the codecs that they support in order of
preference. The SIP response includes the codec they want to use for the call. This option can be used to override that
behaviour and use the codec preference offered by the caller.
· Reserve Avaya IP Endpoint License: Software level = 6.0+.
Avaya IP phones require an Avaya IP Endpoint license 834 . Normally licenses are issued in the order that devices
register. This option allows this extension to be pre-licensed before the device has registered.
· Reserve 3rd Party IP Endpoint License: Software level = 6.0+.
Non-Avaya IP phones require an 3rd Party IP Endpoint license 834 . Normally licenses are issued in the order that devices
register. This option allows this extension to be pre-licensed before the device has registered.
Manager Manager 8.1
Manager
Page 259
15-601011 Issue 25l (11 February 2011)
5.6.4 T38 Fax
The setting on this tab are only accessible if Re-invite Supported and Fax Transport Support are selected on the VoIP
256 tab. Fax relay 749 is only supported on IP500/IP500v2 systems with an IP500 VCM card.
SIP Extension | T38 Fax
Control Unit
SOE
Software Level
5.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Use Default Values: Default = On.
If selected, all the fields are set to their default values and greyed out.
· T38 Fax Version: Default = 3.
The system can support Versions 0, 1, 2 and 3. During fax relay, the two gateways will negotiate to use the highest
version which they both support.
· Transport: Default = UDPTL (fixed).
Currently only UDPTL is supported. TCP and RTP transport are not supported.
· For UDPTL, redundancy error correction is supported. Forward Error Correction (FEC) is not supported.
· Redundancy:
Redundancy sends additional fax packets in order to increase the reliability. However increased redundancy increases
the bandwidth required for the fax transport.
· Low Speed: Default = 0 (No redundancy), Range = 0 to 5.
Sets the number of redundant T38 fax packets that should be sent for low speed V.21 T.30 fax transmissions.
· High Speed: Default = 0 (No redundancy). Range = 0 to 5.
Sets the number of redundant T38 fax packets that should be sent for V.17, V.27 and V.28 fax transmissions.
· TCF Method: Default = Trans TCF.
TCF = Training Check Frame.
· Max Bit Rate (bps): Default = 14400.
Lower rates can be selected if the current rate is not supported by the fax equipment or is found to not be reliable.
· EFlag Start Timer (msecs): Default = 2600.
· EFlag Stop Timer (msecs): Default = 2300.
· Tx Network Timeout (secs): Default = 150.
· Scan Line Fix-up: Default = On.
· TFOP Enhancement: Default = On.
· Disable T30 ECM: Default = Off.
When selected, disabled the T.30 Error Correction Mode used for fax transmission.
· Disable EFlags For First DIS: Default = Off.
· Disable T30 MR Compression: Default = Off.
· NSF Override: Default = Off.
If selected, the NSF (Non-Standard Facility) information sent by the T38 device can be overridden using the values in
the fields below.
· Country Code: Default = 0.
· Vendor Code: Default = 0.
Manager Manager 8.1
Manager
Page 260
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Extension Settings
5.6.5 IP DECT
This tab is displayed for IP DECT extensions. These are created manually after an IP DECT
configuration or added automatically as DECT handsets subscribe to the DECT system.
227
line has been added to the
Extension | IP DECT
Control Unit
SOE
Software Level
3.1+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· DECT Line ID
Use the drop-down list to select the IP DECT line
227
from the system to the Avaya IP DECT system.
· Message Waiting Lamp Indication Type: Default = On
Allows selection of the message waiting indication to use with the IP DECT extension. Options are: None, On.
· Reserve Avaya IP Endpoint License: Software level = 6.0+.
Avaya IP phones require an Avaya IP Endpoint license in order to register with the system. Normally licenses are issued
in the order that devices register. This option allows this extension to be pre-licensed before the device has registered.
Manager Manager 8.1
Manager
Page 261
15-601011 Issue 25l (11 February 2011)
5.7 User Settings
Users are the people who use the system. They do not necessary have to be an extension user, for example
users are used for RAS dial in data access. In addition, more users can be created than there are extensions,
with users logging in to an extension when they want to receive calls.
By default, a user is automatically created to match each extension. They are numbered from 201 upwards and the first
16 are placed in the hunt group Main (200), which is the default destination for incoming calls.
·
Standard User: A standard user.
·
No User: Used to apply settings for extensions which currently have no associated user.
·
Remote Manager: Used as the default settings for dial in user connections.
·
Hot Desking User: Users with a Login Code can move between extensions by logging in and off.
When a user is deleted
When a user is deleted, any calls in progress continue until completed. The ownership of the call is shown as the NoUser
user. Merging the deletion of a user causes all references to that deleted user to be removed from the system.
Changing a user's extension
Changing a user's extension number automatically logs the user in on the matching base extension if available and the
user doesn't have Forced Login 274 enabled. If Forced Login is enabled, then the user remains on the current extension
being used until they log out and log in at the new extension.
Note that changing a user's extension number affects the user's ability to collect Voicemail messages from their own
extension. Each user's extension is set up as a "trusted location" under the Source Numbers tab of the User configuration
form. This "trusted location" allows the user to dial *17 to collect Voicemail from his own extension. Therefore if the
extension number is changed so must the "trusted location".
The following related configuration items are automatically updated when a user extension is changed:
· User, Coverage and Bridged Appearance buttons associated with the user.
· Hunt group membership (disabled membership state is maintained).
· Forwards and Follow Me's set to the user as the destination.
· Incoming call routes to this destination.
· Dial in source numbers for access to the user's own voicemail.
· Direct call pickup buttons are updated.
· The extension number of an associated extension is updated.
Manager Manager 8.1
Manager
Page 262
15-601011 Issue 25l (11 February 2011)
Configuration Settings: User Settings
Creating a User Rights Based on an Existing User
1. Select
User Rights.
2. In the group pane, right-click and select New User Rights from a User.
3. Select the user and click OK.
Associating User Rights to a User
1. Select
User Rights or
User.
2. In the group pane, right-click and select Apply User Rights to Users.
3. Select the user rights to be applied.
4. On the Members of this User Rights sub tab select the users to which the user rights should be applied as their
Working Hours User Rights.
5. On the Members when out of hours sub tab select which users should use the selected user rights as their out of
hours user rights.
6. Click OK.
or
1. Select the required user to display their settings in the details pane.
2. Select the User tab.
3. Use Working Hours User Rights drop-down to select the user rights required.
4. If required a Working Hours Time Profile and Out of Hours User Rights can be selected.
5. Click OK.
Copy User Rights Settings over a User's Settings
This process replaces a user's current settings with those that are part of the selected user rights. It does not associate
the user with the user rights.
1. Select
User Rights.
2. In the group pane, right-click and select Copy user rights values to users.
3. Select the user rights to be applied.
4. Click OK.
Manager Manager 8.1
Manager
Page 263
15-601011 Issue 25l (11 February 2011)
5.7.1 User
Users are the people who use the system or are Dial In users for data access. A system User may or may not have an
Extension Number that physical exists - this is useful if users do not require a physical extension but wish to use system
features, for example voicemail, forwarding etc.
· NoUser is used to apply settings to extensions which have no associated user.
· Remote Manager is used as the default settings for dial in connections.
User | User
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
A
symbol indicates that the setting can also be set and locked within a set of user rights 389 with which the user is
associated using the Working Hour User Rights 264 and Out of Hours User Rights 264 settings. The user rights applied
can be controlled by a time profile 360 selected as the user's Working Hours Time Profile 264 setting. The effect of the
user rights can be displayed using the User Right View 264 control.
· Name: Range = Up to 15 characters
This is the user's account name used for RAS Dial In, Caller Display and voicemail mailbox. As the display on Caller
Display telephones is normally only 16 digits long it is useful to keep the name short. Only alphanumeric characters and
space are supported in this field. Do not use punctuation characters such as #, ?, /, -, _ and ,. Start names with a
alphabetic character. This field is case sensitive and must be unique.
· Voicemail uses the name to match a user to their mailbox. Changing a user's name will route their voicemail calls to a
new mailbox. Note however that Voicemail Pro is not case sensitive and will treat names such as "Steve Smith",
"steve smith" and "STEVE SMITH" as being the same.
· Password: Default = Blank, Range = Up to 31 alphanumeric characters.
This password is used by user applications such as Phone Manager, SoftConsole and TAPI. It is also used for user's with
Dial In access. Note that this is not the user's voicemail mailbox password (see User | Voicemail | Voicemail Code 267 )
or their phone log in code (see User | Telephony | Supervisor Settings | Login Code 276 ).
· IP Office 4.2+: Users can change their Password using the File | Change Password option within Phone Manager.
· Full Name: Default = Blank
Use this field to enter the user's full name. The recommended format is <first name><space><last name> in order for
this value to be used correctly by voicemail dial by name features. When set, the Full Name is used in place of the
Name for display by phones and user applications. Only alphanumeric characters and spaces are supported in this field.
Do not use punctuation characters such as #, ?, /, -, _ , ^, > and ,. The entry in this field also cannot start with either a
space or a numeral.
· Extension: Range = 2 to 9 digits.
Any number up to 9 digits. In general all extensions should have the same number of digits. This setting can be left
blank for users used just for dial in data connections.
· Users for Delta Server, CBC and CCC should only use up to 4 digit extension numbers.
· Users associated with IP phones or who may log in as such devices should not be given extension numbers greater
than 7 digits.
· For pre-IP Office 6.0, extension numbers in the range 8897 to 9999 are reserved for use by the Delta Server.
· Locale: Default = Blank (Use system locale 143 )
Configures the language used for voicemail prompts played to the user, assuming the language is available on the
voicemail server. See Supported Country and Locale Settings 844 . On a digital extension it also controls the display
language used for messages from the system. Note however that some phones have their own menu options for the
selected language for the phone menus.
· When the system routes a call to the voicemail server it indicates the locale for which matching prompts should be
provided if available. The locale sent to the voicemail server by the system is determined as follows:
Locale Source
Usage
Short Code
The short code locale, if set, is used if the call is routed to voicemail using the short
code.
System
If no user or incoming call route locale is set system locale is used unless overridden by
a short code locale.
Incoming Call Route
The incoming call route locale, if set, is used if caller is external.
User
The user locale, if set, is used if the caller is internal.
Manager Manager 8.1
Manager
Page 264
15-601011 Issue 25l (11 February 2011)
Configuration Settings: User Settings
· Priority: Default = 5, Range = 1 (Lowest) to 5 (Highest)
Pre-IP Office 4.0: This setting is used by Least Cost Routing
370 .
IP Office 4.0+: This setting is used by ARS
407 .
· System Phone Rights: Default = None.
This option replaces the System Phone 274 option used on pre-IP Office 6.0 systems. Users set as a system phone user
are able to access additional functions 765 .
· None
The user cannot access any system phone options.
· Level 1
The user can access all system phone options supported on the type of phone they are using except system
management and memory card commands.
· Level 2
The user can access all system phone options supported on the type of phone they are using including system
management and memory card commands. Due to the nature of the additional commands a login code should
be set for the user to restrict access.
· Profile : Default = Basic User. Software level = 6.0+.
A user's configured profile controls whether they can be configured for a number of features. The table below lists the
different user profiles and the settings accessible by each profile. Setting a user to a particular profile will enable those
settings by default, however they can still be manually disabled if required. The number of users that can be configured
for each profile other than Basic User is controlled by the user licenses 835 present in the configuration.
one-X Portal for IP Office
Basic User
Office
Worker
Teleworker
Mobile
Worker
Power User
Yes[1]
Yes
Yes
–
Yes
[1]
" Telecommuter options
Yes
–
Yes
–
Yes
UMS Web Services
Yes[1]
Yes
Yes
–
Yes
Mobility Features
Yes[1]
–
–
Yes
Yes
TTS for Email Reading
–
–
–
Yes
Yes
IP Office SoftPhone
–
–
Yes
–
Yes
1. These features are supported for Basic User users on systems with the appropriate pre-IP Office 6.0
legacy licenses.
· Receptionist : Default = Off. Software level = 6.0+.
This settings allows the user to use the SoftConsole application. This requires the Manager configuration to contain
Receptionist licenses 830 . Up to 4 users can be licensed.
· Enable Softphone : Default = Off. Software level = 6.0+.
This option can be enabled for users whose Profile 265 is set to Teleworker or Power User. If selected, the user is
able to use the IP Office Softphone application.
· Enable one-X Portal Services: Default = Off. Software level = 5.0+.
This option can be enabled for users whose Profile 265 is set to Office Worker, Teleworker or Power User. If
selected, the user is able to use the one-X Portal for IP Office application to access their phone settings and to control
phone calls.
· For systems upgraded to IP Office 6.0 with existing licenses for one-X Portal for IP Office, those licenses can be
used with users whose Profile is set to Basic User.
· Enable one-X TeleCommuter: Software level = 6.0+.
This option can be enabled for users whose Profile 265 is set to Teleworker or Power User. If selected, the user
is able to use the telecommuter mode features of the one-X Portal for IP Office application.
· Ex Directory: Default = Off
When on, the user does not appear in the directory list shown by the user applications and on phones with a directory
function.
· Restrictions: Default = None. Software level = Up to 3.1.
Sets which set of User Restrictions 387 applies to the user.
· Phone Manager Type: Default = Lite. Software level = Up to 3.1.
Determines the mode in which the user's copy of the Phone Manager application will operate. Modes are Lite, Pro and
VoIP (Phone Manager Pro PC Softphone). Note that the number of users able to simultaneously use Pro and VoIP modes
is controlled by licenses entered into the system configuration. *In IP Office 3.2 configurations this option has moved to
the Phone Manager Options tab.
Manager Manager 8.1
Manager
Page 265
15-601011 Issue 25l (11 February 2011)
· Book a Conferencing Center in Phone Manager: Default = Off. Software level = Up to 3.1.
When enabled, displays links in the user's Phone Manager application for access to the Conferencing Center application
if installed. Note that to book a conference requires the user to have a Conferencing Center user ID and password. This
feature also requires the Conferencing Center IP Address and Conferencing Center URL to be set (System | System).
*In IP Office 3.2 configurations, this option has moved to the Phone Manager Options tab.
· Device Type:
This field shows the type of phone at which the user is current logged in. If the user is logged out but is associated with
a Base Extension, the device type for that extension port is shown. If the user has been logged out and is not
associated with a Base Extension, the device type is listed as Device Type Unknown.
· User Rights View: Software level = 3.2+.
This field affects Manager only. It allows you to switch between displaying the user settings as affected by their
associated Working Hours User Rights or Out of Hours User Rights.
· Working Hours Time Profile: Default = <None> (Continuous). Software level = 3.2+.
If set, the selected time profile defines when the user's Working Hours User Rights are applied. Outside the time
profile, the user's Out of Hours User Rights are applied.
· Working Hours User Rights: Default = Blank (No rights restrictions). Software level = 3.2+.
This field allows selection of user rights which may set and lock some user settings. If a Working Hours Time Profile
has been selected, the Working Hours User Rights are only applied during the times defined by that time profile,
otherwise they are applied at all times.
· Out of Hours User Rights: Default = Blank (No rights restrictions). Software level = 3.2+.
This field allows selection of alternate user rights that are used outside the times defined by the user's Working Hours
Time Profile.
Manager Manager 8.1
Manager
Page 266
15-601011 Issue 25l (11 February 2011)
Configuration Settings: User Settings
5.7.2 Voicemail
If a voicemail server application is being used on your system, each user has use of a voicemail mailbox. You can use this
form to enable this facility and various user voicemail settings.
User | Voicemail
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
symbol indicates that the setting can also be set and locked within a set of user rights 389 with which the user is
A
associated using the Working Hour User Rights 264 and Out of Hours User Rights 264 settings. The user rights applied
can be controlled by a time profile 360 selected as the user's Working Hours Time Profile 264 setting. The effect of the
user rights can be displayed using the User Right View 264 control.
· Voicemail Code: Default = Blank, Range = 0 (no code) to 15 digits.
A code (1-15 digits) used by the voicemail server to validate access to this mailbox. If remote access is attempted to a
mailbox that has no voicemail code set, the prompt "Remote access is not configured on this mailbox" is played.
Whether the caller will be prompted to enter this code varies as follows:
· Embedded Voicemail
The voicemail code is used if set.
· Trusted Source Access
The voicemail code is required when accessing the mailbox from a location that is not set as a trusted number in the
user's Source Numbers 272 list. Also Voicemail Pro call flows containing an action where the action's PIN code set to $
will prompt the user for their voicemail code.
· Users can set their own code through the mailbox telephone user interface. In this case the user is forced to
enter at least 4 digits.
· Codes set through the Voicemail Pro telephone user interface are restricted to valid sequences. For example,
attempting to enter a code that matches the mailbox extension, repeat the same number (1111) or a sequence
of numbers (1234) are not allowed. If these types of code are required they can be entered through Manager.
· Changing the Code
All of the voicemail interfaces, except IMS and IMAP, provide options for the user to change the voicemail code
themselves. In addition, Voicemail Pro running in Intuity emulation mode will request that the user sets a code
when they first log in to their mailbox using the phone.
· Voicemail On Default = On
When on, the mailbox is used by the system to answer the user's unanswered calls or calls when the user's extension
returns busy. Note that selecting off does not disable use of the user's mailbox. Messages can still be forward to their
mailbox and recordings can be placed in it. The mailbox can also still be accessed to collect messages.
· When a caller is directed to voicemail to leave a message, the system indicates the target user or hunt group
mailbox.
· Pre-IP Office 4.0: The mailbox of the user or hunt group whose settings have caused the call to go to voicemail
is used.
· For IP Office 4.0+: The mailbox of the originally targeted user or hunt group is used. This applies even if the
call has been forwarded to another destination. It also includes scenarios where a hunt group call overflows or
is in fallback to another group.
· Voicemail Pro can be used to customize which mailbox is used separately from the mailbox indicated by the
system.
· Voicemail Help Default = Off
For voicemail systems running IP Office mailbox mode, this option controls whether users retrieving messages are
automatically given an additional prompt "For help at any time press 8." If switched off, users can still press 8 for help.
For voicemail systems running in Intuity emulation mode, this option has no effect. On those systems the default access
greeting always includes the prompt "For help at any time, press *4" (*H in the US locale).
· Voicemail Ringback: Default = Off
When enabled and a new message has been received, the voicemail server calls the user's extension to attempt to
deliver the message each time the telephone is put down. Voicemail will not ring the extension more than once every 30
seconds.
· Voicemail Email Reading: Default = Off
This option can be enabled for users whose Profile 265 is set to Mobile Worker or Power User. If enabled, when you
log into you voicemail box, it will detect your email messages and read them to you. This email text to speech feature is
set-up through Voicemail Pro.
Manager Manager 8.1
Manager
Page 267
15-601011 Issue 25l (11 February 2011)
· UMS Web Services: Default = Off. Software level = 4.2+.
This option can be enabled for users whose Profile 265 is set to Teleworker, Office Worker or Power User. If
selected, the user can use either any of the Voicemail Pro UMS services to access the voicemail messages (IMAP email
client, web browser or Exchange 2007 mailbox). Note that the user must have a voicemail code set in order to use the
UMS services.
· For systems upgraded to IP Office 6.0 with existing UMS Web Service licenses, those licenses can be used
with users whose Profile is set to Basic User.
· Voicemail Email: Default = Blank (No voicemail email features)
This field is used to set the user or group email address used by the voicemail server for voicemail email operation.
When an address is entered, the additional Voicemail Email control below are selectable to configure the type of
voicemail email service that should be provided.
· Use of voicemail email requires the Voicemail Pro server to have been configured to use either a local MAPI email
client or an SMTP email server account. For embedded voicemail, voicemail email is supported with IP Office 4.2+
(except not on Small Office Edition) and uses the system's SMTP 177 settings.
· The use of voicemail email for the sending (automatic or manual) of email messages with wav files attached should
be considered with care. A one-minute message creates a 1MB .wav file.
· Voicemail Email Default = Off
If an email address is entered for the user or group, the following options become selectable. These control the mode of
automatic voicemail email operation provided by the voicemail server whenever the voicemail mailbox receives a new
voicemail message.
· Users can change their voicemail email mode using visual voice. If the voicemail server is set to IP Office
mode, user can also change their voicemail email mode through the telephone prompts. The ability to change
the voicemail email mode can also be provided in a call flow using a Play Configuration Menu action or a
Generic action.
· If the voicemail server is set to IP Office mode, users can manually forward a message to email.
· Off
If off, none of the options below are used for automatic voicemail email. Users can also select this mode by dialing
*03 from their extension.
· Copy
If this mode is selected, each time a new voicemail message is received in the voicemail mailbox, a copy of the
message is attached to an email and sent to the email address. There is no mailbox synchronization between the
email and voicemail mailboxes. For example reading and deletion of the email message does not affect the
message in the voicemail mailbox or the message waiting indication provided for that new message.
· Forward
If this mode is selected, each time a new voicemail message is received in the voicemail mailbox, that message is
attached to an email and sent to the email address. No copy of the voicemail message is retained in the voicemail
mailbox and their is no message waiting indication. As with Copy, their is no mailbox synchronization between the
email and voicemail mailboxes. Users can also select this mode by dialing *01 from their extension.
· UMS Exchange 2007 (IP Office 5.0+)
With Voicemail Pro, the system supports voicemail email to an Exchange 2007 server email account. For users
and groups also enabled for UMS Web Services this significantly changes their mailbox operation. The
Exchange Server inbox is used as their voicemail message store and features such as message waiting
indication are set by new messages in that location rather than the voicemail mailbox on the voicemail server.
Telephone access to voicemail messages, including Visual Voice access, is redirected to the Exchange 2007
mailbox.
· Alert
If this mode is selected, each time a new voicemail message is received in the voicemail mailbox, a simple email
message is sent to the email address. This is an email message announcing details of the voicemail message but
with no copy of the voicemail message attached. Users can also select this mode by dialing *02 from their
extension.
· DTMF Breakout
When a caller is directed to voicemail to leave a message, they can be given the option to be transferred to a different
extension. The greeting message needs to be recorded telling the caller the options available. The extension numbers
that they can be transferred to are entered in the fields below. IP Office 5+: System default values can be set for these
numbers and are used unless a different number is set within these user settings. The values can be set using User
Rights 399 .
· Reception / Breakout (DTMF 0)
The number to which a caller is transferred if they press 0 while listening to the mailbox greeting rather than
leaving a message (*0 on embedded voicemail).
· For systems set to Intuity emulation mode, the mailbox user can also access this option when collecting their
messages by dialing *0.
· If the mailbox has been reached through a call flow containing a Leave Mail action, the option provided when
0 is pressed are:
Manager Manager 8.1
Manager
Page 268
15-601011 Issue 25l (11 February 2011)
Configuration Settings: User Settings
· For IP Office mode, the call follows the Leave Mail action's Failure or Success results connections
depending on whether the caller pressed 0 before or after the record tone.
· For Intuity mode, pressing 0 always follows the Reception / Breakout (DTMF 0) setting.
· Breakout (DTMF 2)
The number to which a caller is transferred if they press 2 while listening to the mailbox greeting rather than
leaving a message (*2 on embedded voicemail). Pre-IP Office 5 this option is not support for Voicemail Pro running
in IP Office mailbox mode.
· Breakout (DTMF 3)
The number to which a caller is transferred if they press 3 while listening to the mailbox greeting rather than
leaving a message (*3 on embedded voicemail). Pre-IP Office 5 this option is not support for Voicemail Pro running
in IP Office mailbox mode.
Manager Manager 8.1
Manager
Page 269
15-601011 Issue 25l (11 February 2011)
5.7.3 DND
Do not disturb prevents the user from receiving hunt group and page calls. Direct callers hear busy tone or are diverted to
voicemail if available. It overrides any call forwarding, follow me and call coverage settings. A set of exception numbers
can be added to list numbers from which the user still wants to be able to receive calls when they have do not disturb in
use. See Do Not Disturb 769 in the Telephone Features section for full details of Do Not Disturb operation.
User | DND
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
A
symbol indicates that the setting can also be set and locked within a set of user rights 389 with which the user is
associated using the Working Hour User Rights 264 and Out of Hours User Rights 264 settings. The user rights applied
can be controlled by a time profile 360 selected as the user's Working Hours Time Profile 264 setting. The effect of the
user rights can be displayed using the User Right View 264 control.
· Do Not Disturb: Default = Off
When checked the user's extension is considered busy, except for calls coming from sources listed in their Do Not
Disturb Exception List. When a user has do not disturb in use, their normal extension will give alternate dialtone 846
when off hook. IP Office 4.2+: Users with DND on are indicated as 'busy' on any BLF indicators set to that user.
· Do Not Disturb Exception List: Default = Blank
This is the list of telephone numbers that are still allowed through when Do Not Disturb is set. For example this could be
an assistant or an expected phone call. Internal extension numbers or external telephone numbers can be entered. If
you wish to add a range of numbers, you can either enter each number separately or make use of the wildcards "N" and
"X" in the number. For example, to allow all numbers from 7325551000 to 7325551099, the DND Exception number
can be entered as either 73255510XX or 73255510N. Note that this list is only applied to direct calls to the user.
· Calls to a hunt group of which the user is a member do not use the Do Not Disturb Exceptions list.
Manager Manager 8.1
Manager
Page 270
15-601011 Issue 25l (11 February 2011)
Configuration Settings: User Settings
5.7.4 Short Codes
Short codes entered in this list can only be dialed by the user. They will override any matching user rights or system short
code. See Short Codes 426 for details.
User and User Rights short codes are only applied to numbers dialed by that user. For example they are not applied to
calls forwarded via the user.
· WARNING
User dialing of emergency numbers must not be blocked by the addition of short codes. If short codes are added, the
users ability to dial emergency numbers must be tested and maintained.
User | Short Codes
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
A
symbol indicates that the setting can also be set and locked within a set of user rights 389 with which the user is
associated using the Working Hour User Rights 264 and Out of Hours User Rights 264 settings. The user rights applied
can be controlled by a time profile 360 selected as the user's Working Hours Time Profile 264 setting. The effect of the
user rights can be displayed using the User Right View 264 control.
Short codes can be added and edited using the Add, Remove and Edit buttons. Alternatively you can right-click on the
list of existing short code to add and edit short codes.
· *FWD
Short codes of this form are inserted by the system. They are used in conjunction with the User | Forwarding settings
to remember previously used forwarding numbers. They can be accessed on that tab by using the drop-down selector
on the forwarding fields.
Manager Manager 8.1
Manager
Page 271
15-601011 Issue 25l (11 February 2011)
5.7.5 Source Numbers
This form is used to enter values that have special usages. These are entered using the Add, Edit and Remove buttons.
User | Source Numbers
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
The following types of entry can be added to a user's source numbers.
· V<Caller's ICLID>
For systems using Voicemail Lite, Voicemail Pro or Embedded Voicemail, strings prefixed with a V indicate numbers from
which access to the users mailbox is allowed without requiring entry of the mailbox's voicemail code. This is referred to
as "trusted source".
· For Voicemail Pro running in Intuity mode, trusted source is used for calls from programmable buttons set to
Voicemail Collect and Visual Voice. Other controls are prompted for the mailbox number and then password.
· R<Caller's ICLID>
To allow Dial In/RAS call access only from a specified number prefix the number with a "R", for example R7325551234
.
· H<Group Name>
Allows the user to receive message waiting indication of new group messages. Enter H followed by the group name, for
example HMain.
· On suitable display extensions, the hunt group name and number of new messages is displayed. Refer to the
appropriate telephone user guide.
· If the user is using Phone Manager, the Messages tab shows the hunt group name and number of new messages.
· If the user is not a member of the group, a voicemail code must be set for the group's mailbox. See Voicemail Code
on the Hunt Group | Voicemail 311 tab.
· P<Telephone Number>
This entry sets the destination for callback (outbound alert) calls from voicemail. Enter P followed by the telephone
number including any necessary external dialing prefix, for example P917325559876. This facility is only available when
using Voicemail Pro through which a default Callback or a user specific Callback start point has been configured. Refer to
the Voicemail Pro documentation. This feature is separate from voicemail ringback and Voicemail Pro outcalling.
· RESERVE_LAST_CA= Software level = Up to 3.2.
Used for users with multiple call appearance buttons. When present, this string stops the users last call appearance
button from being used to receive incoming calls. This ensures that the user always has a call appearance button
available to make outgoing calls and to initiate transfers and conferences. For IP Office 4.0 and higher this option has
been replaced by Reserve Last CA 278 (User | Telephony | Multi-line Options 278 ).
· AT<string>
Strings beginning with AT can be used with a user called DTEDefault to configure the default settings of the control
unit's DTE port.
· Enable_OTT
Enable one touch transfer
786
operation for the user.
NoUser User Source Numbers
The following source numbers can also be used on the Source Numbers tab of the NoUser 767 user. These affect all
users on the system. Note that changes to these source numbers require a reboot of the system to become effective.
· ACD_QUEUE_DELAY=nn Software level = Up to 3.2.
Used to change the timeout for still queued messages. The parameter nn can be replace with a time in seconds
between 20 and 180. For IPOffice 4.0+ this has been replaced by Hunt Group | Announcements 320 .
· ALLOW_5410_UPGRADES Software level - 4.1 Q1 2008 Maintenance Release+.
Previously the only control over the upgrading of 5410 phones was controlled by the use of the turn_on.bat and
turn_off.bat batch files installed with the Manager application. Now in addition this option must be present for 5410
phones to update their firmware. Refer to the Manager Installation manual for full details.
· DISTINCT_HOLD_RINGBACK (Software level = 4.1+)
Used to display a specific message about the call type for calls returning after timing out from being parked or held. If
set, such calls display Return Call - Held or Return Call – Parked rather than connected party name or line name.
Manager Manager 8.1
Manager
Page 272
15-601011 Issue 25l (11 February 2011)
Configuration Settings: User Settings
· ExtendDirectLimit <optional limit> (Software level = 4.1 – 4.2)
This command allows the number of directory entries that can be added to the configuration to be controlled. By default
Manager imposes a limit of 1000 directory entries. If this command is used without specifying an optional limit, the limit
set is determined by the type of control unit; refer to the table below. Note that specifying or allowing a large directory
limit may affect the performance of applications that use and display the directory, for example Phone Manager.
·
! Warning
Specifying a large directory limit may affect the performance of applications that use and display the directory, for
example Phone Manager, SoftConsole and phones with access to the directory. It may also delay the inward routing
of calls as the system attempts to match ICLID's received to names using the directory entries.
· ExtendLDAPDirectLimit <optional limit> (Software level = 4.1 – 4.2)
This command allows the number of LDAP directory entries that the system will read to be controlled. By default the
system will only support up to 500 LDAP directory entries. If this command is used without specifying an optional limit,
the limit set is determined by the type of control unit; refer to the table below. Note that specifying or allowing a large
directory limit may affect the performance of applications that use and display the directory, for example Phone
Manager.
Control Unit
Small Office Edition
IP406 V2
Directory Entries
LDAP Entries
100
1000
2500
10000
IP412
10000
10000
IP500
10000
10000
· FORCE_HANDSFREE_TRANSFER (Software level = 4.2 Q4 Maintenance release+)
If set, when using the handsfree announced transfer 784 process, both the transfer enquiry and transfer completion calls
are auto-answered. Without this setting only the transfer enquiry call is auto-answered.
· H323SetupTimerNoLCR (Software level = 3.2 only)
Used to set the fallback time from VoIP trunks to non-VoIP trunks within LCR. See IP Trunk Fallback. For IP Office 4.2+
the setting Call Initiation Timeout is available on SIP and IP trunks.
· HIDE_CALL_STATE
Used to hide the call status information, for example Dial, Conn, etc, on DS phones. Used in conjunction with the
LONGER_NAMES option. Not supported for 1600 and 9600 Series phones.
· LONGER_NAMES
Used to increase the length of names sent for display on DS phones. See Caller Display
9600 Series phones.
755 .
Not supported for 1600 and
· ProgressEndsOverlapSend
See Line | VoIP 223 .
· VM_TRUNCATE_TIME=X (Range X = 0 to 7 seconds. Software level = 3.2 Maintenance Releases and 4.0+)
On analog trunks, call disconnection can occur though busy tone detection. When such calls go to voicemail to be
recorded or leave a message, when the call ends the system indicates to the voicemail system how much to remove
from the end of the recording in order to remove the busy tone segment. This amount varies by system locale 844 , the
defaults being listed below. For some systems it may be necessary to override the default if analog call recordings are
being clipped or include busy tone. That can be done by adding a VM_TRUNCATE_TIME= setting with the required
value in the range 0 to 7 seconds.
· New Zealand, Australia, China, Saudi Arabia and Custom: 5 seconds.
· Korea: 3 seconds.
· Italy, Mexico, Chile, Colombia and Brazil: 2 seconds.
· Argentina, United States, Canada and Turkey: 0 seconds.
· All other locales: 7 seconds.
· VMAIL_WAIT_DURATION=X (Software level = 4.2 2Q09+)
The number of milliseconds to wait before cutting through the audio to Voicemail. Some delay is required to allow for
codec negotiation.
Manager Manager 8.1
Manager
Page 273
15-601011 Issue 25l (11 February 2011)
5.7.6 Telephony
This form allows you to set telephony related features for the user. These override any matching setting in the System |
Telephony 160 tab. The settings are grouped into a number of sub-tabs.
5.7.6.1 Call Settings
For details of the ringing tones, see Ring Tones
Telephony 160 tab.
762 .
DefaultRing uses the system default setting set through the System |
User | Telephony | Call Settings
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
A
symbol indicates that the setting can also be set and locked within a set of user rights 389 with which the user is
associated using the Working Hour User Rights 264 and Out of Hours User Rights 264 settings. The user rights applied
can be controlled by a time profile 360 selected as the user's Working Hours Time Profile 264 setting. The effect of the
user rights can be displayed using the User Right View 264 control.
· Outside Call Sequence: Default = Default Ring (Use system setting 160 )
Applies only to analog phones. Sets the ring pattern used for external calls to the user. The distinctive ring patterns
used for other phones are fixed. Note that changing the pattern for users associated with fax and modem device
extensions may cause those devices to not recognize and answer calls.
· Inside Call Sequence: Default = Default Ring (Use system setting 160 )
Applies only to analog phones. Sets the ring pattern used for internal calls to the user. The distinctive ring patterns used
for other phones are fixed.
· Ring Back Sequence: Default = Default Ring (Use system setting 160 )
Applies only to analog phones. Sets the ring pattern used for ringback calls to the user. The distinctive ring patterns
used for other phones are fixed.
· No Answer Time: Default = Blank (Use system setting 160 ), Range = 6 to 99999 seconds.
Sets how long a call rings the user before following forwarded on no answer if set or going to voicemail. Leave blank to
use the system default setting.
· Wrap-up Time (secs): Default = 2 seconds, Range 0 to 99999 seconds.
Specifies the amount of time after ending one call before another call can ring. During this interval the user is treated
as still being on a call. You may wish to increase this in a "call center" environment where users may need time to log
call details before taking the next call. It is recommended that this option is not set to less than the default of 2
seconds. 0 is used to allow immediate ringing.
· For users set as an CCR Agent, the After Call Work Time
is also used.
276
(User | Telephony | Supervisor Settings
276 )
setting
· Transfer Return Time (secs): Default = Blank (Off), Range 1 to 99999 seconds.
Sets the delay after which any call transferred by the user, which remains unanswered, should return to the user. A
return call will continue ringing and does not follow any forwards or go to voicemail.
· Pre-3.2 IP Office: The transfer return only occurs if the user has no other connected call.
· IP Office 3.2+: Transfer return will occur if the user has an available call appearance button.
· Transfer return is not applied if the transfer is to a hunt group that has queuing enabled.
· Call Cost Mark-Up: Default = 100. Software level = 4.0+.
This setting is used for ISDN advice of charge (AOC). The markup is applied to the cost calculations based on the
number of units and the line base cost per charging unit. The field is in units of 1/100th, for example an entry of 100 is
a markup factor of 1. This value is included in the system SMDR output.
· Call Waiting On: Default = Off
For users on phones without appearance buttons, if the user is on a call and a second call arrives for them, an audio
tone can be given in the speech path to indicate a waiting call (the call waiting tone varies according to locale). The
waiting caller hears ringing rather than receiving busy. There can only be one waiting call, any further calls receive
normal busy treatment. If the call waiting is not answered within the no answer time, it follows forward on no answer or
goes to voicemail as appropriate. User call waiting is not used for users on phones with multiple call appearance
buttons. Call waiting can also be applied to hunt group calls, see Hunt Group | Hunt Group | Call Waiting 306 . Call
waiting should not be used for fax and modem devices.
· Answer Call Waiting on Hold (Analog): Default = On
Applies to analog and IP DECT extension users only. If the user has a call waiting and places their current call on hold,
the waiting call is automatically connected.
Manager Manager 8.1
Manager
Page 274
15-601011 Issue 25l (11 February 2011)
Configuration Settings: User Settings
· Busy on Held: Default = On
If on, when the user has a call on hold, new calls receive busy treatment. They will follow the users forward on busy
setting or are diverted to voicemail. Otherwise busy tone (ringing for incoming analog calls) is played. This overrides call
waiting when the user has a call on hold. The use of Busy on Held for users with multiple call appearance buttons is
deprecated and Manager will prompt whether it should switch off busy on held for such a user.
· Offhook Station: Default = Off
Off-hook station allows an analog extension to be left permanently off-hook, with calls being made and answered using
an application or TAPI. When enabled, the analog extension user is able to control calls using the application in the
following ways:
· Offhook station does not disable the physical off-hook on the phone. When starting with the phone on-hook,
making and answering calls is the same as normal analog extension operation. Additionally however calls can be
initiated from the application. After entering the required number and making the call, the on-hook analog
extension receives a ringback showing the users own caller ID and when answered the outgoing call leg to the
dialed number is started.
· Pre-IP Office 4.0: Calls to a busy destination are cleared immediately without hearing busy tone.
· IP Office 4.0+: Calls to a busy destination present busy tone before being cleared. Except Phone Manager PC
Softphone.
· The application can be used to end a call with the analog extension still off-hook. Instead of hearing disconnect
tone the user hears silence and can use the application to make another call. Though off-hook the user is indicated
as idle on BLF indicators. Without off-hook Station set the user would be indicated as busy when off-hook, whether
on a call or not.
· If off-hook and idle (having cleared a previous call), incoming call alerts by presenting ringing through the audio
path. The call can be answered using the application or going on-hook/off-hook or by pressing recall. Note that if
the phone normally displays call ID, any caller ID displayed on the phone is not updated in this mode, however the
call ID in the application will be that of the current call.
· If on-hook, an incoming call alerts as normal using the phone's ringer and is answered by going off-hook. The
answer call option in the application cannot be used to answer calls to an on-hook analog extension.
· While off-hook and idle, the analog extension user will receive page calls.
· If the analog extension handset is replaced with a headset, changing the Extension Classification
Analog) 254 to Quiet Handset is recommended.
254
(Extn |
· Offhook Station is not intended for non-analog phone extension. However, since it enables the answer calls control
in Phone Manager it is recommended that the option is selected for non-analog extension users.
· System Phone: Default = Off
Users set as a system phone user are able to access additional functions 765 . For IP Office 6.0 and higher systems, the
setting has been replaced by the System Phone Rights 264 setting on the User | User 264 tab.
· Remote Homeworker/Agent: Default = Off. Software level = Up to 3.2 only.
Select if the user has been configured as a remote extension on an Avaya INDeX telephone system. Refer to the INDeX
Level 10 documentation for full details. Only available in Locales where the Avaya INDeX switch is supported.
Manager Manager 8.1
Manager
Page 275
15-601011 Issue 25l (11 February 2011)
5.7.6.2 Supervisor Settings
User | Telephony | Supervisor Settings
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
A
symbol indicates that the setting can also be set and locked within a set of user rights 389 with which the user is
associated using the Working Hour User Rights 264 and Out of Hours User Rights 264 settings. The user rights applied
can be controlled by a time profile 360 selected as the user's Working Hours Time Profile 264 setting. The effect of the
user rights can be displayed using the User Right View 264 control.
· Login Code: Default = Blank, Range = Up to 31 digits.
The code that has to be entered, as part of a log in sequence, to allow a user to make use of an extension as if it was
their own phone. This log in code can be used for hot desking as well as logging back onto your phone after it has been
used by a hot desking user. This entry must be at least 4 digits for DS port users. Login codes of up to 15 digits are
supported with Extn Login 619 buttons 619 . Login codes of up to 31 digits are supported with Extn Login 468 short
codes 468 .
· For IP phone users, the login code should be limited to 13 digits. The user's login code is used by IP phones during
registration with the system.
· IP Office 4.0+: Users can hot desking between systems. To log in at a pre-IP Office 5 system requires that Manager
to have a Advanced Small Community Networking license.
· IP Office 4.0+: Users can only log out if they have a Login Code set.
· IP Office 4.1 2008 Q2 maintenance release+: Supports the short code feature Change Login Code
451 .
· IP Office 4.2+: Users can log out without having a Login Code set if they are currently logged in at an extension
whose Base Extension Number 252 (Extension | Extn) 252 no longer matches their own Extension 264 (User | User)
264 .
· If the user has a login code set, it is used by the Outgoing Call Bar Off
483
short code feature.
· If the user has a login code set, access to a range of programmable button features will require entry of the login
code. For example access Self Admin 651 and System Phone features.
· Login Idle Period (secs): Default = Blank (Off), Range = 0 (Off) to 99999.
If the telephone is not used for this period; the user currently logged in is automatically logged out. This option should
be used only in conjunction with Force Login (see below).
· Monitor Group: Default = <None>
Sets the hunt group whose members the user can monitor if silent monitoring is setup. See Call Listen
443 .
· Coverage Group: Default = <None>. Software level = 5.0+
If a group is selected, then in scenarios where an external call would normally have gone to voicemail, it instead
continues ringing and also starts alerting the members of the coverage group. For further details refer to Coverage
Groups 748 .
· Status on No Answer: Default = Logged On. Software level = 4.0+.
Hunt groups can change the status of call center agents (users with a log in code and set to forced log in) who do not
answer a hunt group call presented to them before it is automatically presented to the next agent. Use of this is
controlled by the Agent's Status on No Answer Applies To 306 setting of the hunt group. This option is not used for
calls ringing the agent because the agent is in another group's overflow group.
· Logged On
If this option is selected, the user's status is not changed.
· Busy Wrap-Up
If this option is selected the user's membership status of the hunt group triggering the action is changed to disabled.
The user can still make and receive calls and will still continue to receive calls from other hunt groups to which they
belong.
· Busy Not Available
If this option is selected the user's status is changed to do not disturb. This is the equivalent of DND and will affect all
calls to the user.
· Logged Off
If this option is selected the users status is changed to logged out. In that state they cannot make calls or receive
calls. Hunt group calls go to the next available agent and personal calls treat the user as being busy.
· Reset Longest Idle Time: Default = All Calls. Software level = 4.0+.
This setting is used in conjunction with hunt groups set to Longest Waiting (also known as Idle and Longest Waiting). It
defines what type of calls reset the idle time of users who are members of these hunt groups. Options are All Calls and
External Incoming.
Manager Manager 8.1
Manager
Page 276
15-601011 Issue 25l (11 February 2011)
Configuration Settings: User Settings
· Force Login: Default = Off
If checked, the user must log in using their Login Code to use any extension including an extension to which they are
the default associated user (Base Extension). For example, if Force Login is ticked for user A and user B has logged onto
A's phone, when B logs off user A is not automatically associated with their normal phone and instead must log back on.
If Force Login was not ticked, A would be automatically logged back in.
· For users set as CCR Agents, Forced Login is automatically enabled and cannot be switched off.
· Note that users with a Login Code and set to Forced Login are treated as call center agents. These users consume
CCC agents licenses and their status is reported within CBC and CCC applications.
· Force Account Code: Default = Off
If checked, the user must enter a valid account code to make an external call.
· Force Authorization Code: Default = Off. Software level = 3.2+.
If checked, the user must enter a valid authorization code to make an external call. That authorization code must be
one associated with the user or the user rights to which the user belongs. See Authorization Codes 404 .
· Outgoing Call Bar: Default = Off
When enabled, this setting stops a user from making any external calls except those that use dial emergency features.
On many Avaya display phones, this causes a B to be displayed. The following features can be used with outgoign call
bar: Outgoing Call Bar On 483 , Outgoing Call Bar Off 483 and Change Login Code 451 .
· Inhibit Off-Switch Forward/Transfers: Default = Off. Software level = 3.2+.
When enabled, this setting stops the user from transferring or forwarding calls externally. This does not stop another
user transferring the restricted users calls off-switch on their behalf. Note that a number of other controls may inhibit
the transfer operation, see Off-Switch Transfer Restriction 782 .
· Can Intrude: Default = Off
Check this option if the User can interrupt other user's calls. This setting and the setting below are used to control the
use of the following short code and button features: Call Intrude, Call Listen, Call Steal and Dial Inclusion.
· Cannot be Intruded: Default = On (Pre-4.0 - Off in Italy)
If checked, this user's calls cannot be interrupted or acquired. In addition to the features listed above, this setting also
affects whether other users can use their appearance buttons to bridge into a call to which this user has been the
longest present user.
· Can Trace Calls: Default = Off. Software level = 4.0+.
This settings controls whether the user is able to make used of ISDN MCID controls.
· Can Accept Collect Calls: Default = Off [Brazil Only]
Determines whether the user is able to receive and accept collect calls.
· CCR Agent: Default = Off. Software level = 4.2+.
This field is used by the CCR application to indicate which users are Agents monitored by that application. It also
indicate to the system those users who can use other CCR features within the system configuration. If a user is set as
an CCR Agent, Forced Login is enabled and greyed out from being changed and a warning is given if the user does not
have a log in code set.
· The number of simultaneous logged in CCR Agents supported by the system is controlled by licenses 839 entered
into the configuration. If all agent licenses on a system have been used, additional agents are prevented from
logging in.
· Automatic After Call Work: Default = Off. Software level = 4.2.
CCR Agents (see above) can be automatically put into After Call Work (ACW) state after ending a hunt group call.
During ACW state, further hunt group calls are not presented to the agent. Unless ended manually, the After Call Work
state is automatically cleared after the agent's After Call Work Time setting. Automatic after call work is only supported
when the agent is using a phone that supports an After Call Work 579 button.
· After Call Work Time (secs): Default = System Default, Range = 0 (No ACW) to 999 seconds. Software level = 4.2
+.
For CCR Agents with Automatic After Call Work enabled, this value sets the duration of the ACW period. If set to
System Default, the value set in System | CCR | Default After Call Work Time 184 is used. A value of 0 disables
the user from using ACW.
Manager Manager 8.1
Manager
Page 277
15-601011 Issue 25l (11 February 2011)
5.7.6.3 Multi-line Options
User | Telephony | Multi-line Options
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
A
symbol indicates that the setting can also be set and locked within a set of user rights 389 with which the user is
associated using the Working Hour User Rights 264 and Out of Hours User Rights 264 settings. The user rights applied
can be controlled by a time profile 360 selected as the user's Working Hours Time Profile 264 setting. The effect of the
user rights can be displayed using the User Right View 264 control.
· Individual Coverage Time (secs): Default = 10 seconds, Range 1 to 99999 seconds. Software level 3.0+.
This function sets how long the phone will ring at your extension before also alerting at any call coverage users. This
time setting should not be equal to or greater than the No Answer Time applicable for the user.
· Ring Delay: Default = Blank (Use system setting), Range = 0 (use system setting 160 ) to 98 seconds. Software level =
3.2+.
This setting is used when any of the user's programmed appearance buttons is set to Delayed ringing. Calls received on
that button will initially only alert visually. Audible alerting will only occur after the ring delay has expired.
· Coverage Ring: Default = Ring. Software level = 5.0+.
This field selects the type of ringing that should be used for calls alerting on any the user's call coverage and bridged
appearance buttons. Ring selects normal ringing. Abbreviated Ring selects a single non-repeated ring. No Ring
disables audible ringing. Note that each button's own ring settings (Immediate, Delayed Ring or No Ring) are still
applied.
· The ring used for a call alerting on a call coverage or bridged appearance button will vary according to whether the
user is currently connected to a call or not.
· If not currently on a call, the Coverage Ring setting is used.
· If currently on a call, the quieter of the Coverage Ring and Attention Ring settings is used.
Attention Ring
Setting
Coverage Ring Setting
Ring
Abbreviated
Off
Ring
Ring
Abbreviated
Off
Abbreviated
Abbreviated
Abbreviated
Off
· Attention Ring: Default = Abbreviated Ring. Software level = 4.1+.
This field selects the type of ringing that should be used for calls alerting on appearance buttons when the user already
has a connected call on one of their appearance buttons. Ring selects normal ringing. Abbreviated Ring selects a
single ring. Note that each button's own ring settings (Immediate, Delayed Ring or No Ring) are still applied.
· Ringing Line Preference: Default = On. Software level = 3.0+.
For users with multiple appearance buttons. When the user is free and has several calls alerting, ringing line preference
assigns currently selected button status to the appearance button of the longest waiting call. Ringing line preference
overrides idle line preference.
· Idle Line Preference: Default = On. Software level = 3.0+.
For users with multiple appearance buttons. When the user is free and has no alerting calls, idle line preference assigns
the currently selected button status to the first available appearance button.
· Delayed Ring Preference: Default = Off. Software level = 4.0+.
This setting is used in conjunction with appearance buttons set to delayed or no ring. It sets whether ringing line
preference should use or ignore the delayed ring settings applied to the user's appearance buttons.
· When on, ringing line preference is only applied to alerting buttons on which the ring delay has expired.
· When off, ringing line preference can be applied to an alerting button even if it has delayed ring applied. This is the
same as pre-4.0 ringing line preference operation.
· Answer Pre-Select: Default = Off. Software level = 4.0+.
Normally when a user has multiple alerting calls, only the details of the call on current selected button are shown.
Pressing any of the alerting buttons will answer the call on that button, going off-hook will answer the current selected
button. Enabling Answer Pre-Select allows the user to press any alerting button to make it the current selected button
and displaying its call details without answering that call until the user either presses that button again or goes offhook. Note that when both Answer Pre-Select and Ringing Line Preference are enabled, once current selected
status is assigned to a button through ringing line preference it is not automatically moved to any other button.
Manager Manager 8.1
Manager
Page 278
15-601011 Issue 25l (11 February 2011)
Configuration Settings: User Settings
· Reserve Last CA: Default = Off. Software level = 4.0+.
Used for users with multiple call appearance buttons. When selected this option stops the user's last call appearance
button from being used to receive incoming calls. This ensures that the user always has a call appearance button
available to make an outgoing call and to initiate actions such as transfers and conferences. For pre-4.0 IP Office, this
option is set by adding the RESERVE_LAST_CA= option on the User | Source Numbers 272 tab.
· Abbreviated Ring:
This option has been replaced by the Attention Ring setting above.
Manager Manager 8.1
Manager
Page 279
15-601011 Issue 25l (11 February 2011)
5.7.6.4 Call Log
IP Office 5.0+: The system can store a centralized call log 745 for users. Each users' centralized call log can contain up to
30 call records for user calls (10 on IP412 and IP406 V2 systems). When this limit is reached, new call records replace the
oldest record.
On 1400, 1600 and 9600 Series phones with a Call Log or History button, that button can be used to display the user's
centralized call log. The user can use the call log to make calls or to store as a personal speed dial. They can also edit the
call log to remove records. The same call log is also if the user logs into one-X Portal for IP Office application.
The centralized call log moves with the user if they log on and off from different phones. This includes if they hot desk
within a Small Community Network.
User | Telephony | Call Log
Control Unit
SOE
Software Level
5.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
A
symbol indicates that the setting can also be set and locked within a set of user rights 389 with which the user is
associated using the Working Hour User Rights 264 and Out of Hours User Rights 264 settings. The user rights applied
can be controlled by a time profile 360 selected as the user's Working Hours Time Profile 264 setting. The effect of the
user rights can be displayed using the User Right View 264 control.
· Centralized Call Log: Default = System Default (On)
This setting allows the use of centralized call logging to be enabled or disabled on a per user basis. The default is to
match the system setting Default Centralized Call Log On 165 (System | Telephony | Call Log 165 ). The other options
are On or Off for the individual user. If off is selected, the call log shown on the users phone is the local call log stored
by the phone.
· Delete entries after (hours:minutes): Default = 00:00 (Never). Software level = 6.1+.
If a time period is set, entries in the user's call log are automatically deleted after this period.
· Groups: Default = System Default (On).
This section contains a list of hunt groups on the system. If the system setting Log Missed Huntgroup Calls 160
(System | Telephony | Call Log) 160 has been enabled, then missed calls for those groups selected are shown as part of
the users call log. The missed calls are any missed calls for the hunt group, not just group calls presented to the user
and not answered by them.
Manager Manager 8.1
Manager
Page 280
15-601011 Issue 25l (11 February 2011)
Configuration Settings: User Settings
5.7.7 Forwarding
This form can be used to check and adjust a user's call forwarding and follow me settings.
Follow Me is intended for use when the user is present to answer calls but for some reason is working at another
extension. For example; temporarily sitting at a colleague's desk or in another office or meeting room. As a user, you
would use Follow Me instead of Hot-Desking if you don't have a log in code or you don't want to interrupt you colleague
also receiving their own calls. Multiple users can use follow me to the same phone.
Forwarding is intended for use when, for some reason, the user is unable to answer a call. They may be busy on other
calls, unavailable or simply don't answer. Calls may be forwarded to internal or, subject to the user's call barring controls,
external numbers.
To bar a user from forwarding calls to an external number, the Inhibit Off-Switch Forward/Transfers 276 (User |
Telephony | Supervisor Settings 276 ) option should be selected. To bar all users from forwarding calls to external numbers
the Inhibit Off-Switch Forward/Transfers 160 (System | Telephony | Telephony 160 ) option should be selected.
Note that analog lines doe not provide call progress signalling. Therefore calls forwarded off-switch via an analog line are
treated as answered and are not recalled.
· Calls Forwarded
Once a call has been forwarded to an internal destination, it will ignore any further Forward No Answer or Forward
on Busy settings but may follow additional Forward Unconditional settings.
User | Forwarding
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
A
symbol indicates that the setting can also be set and locked within a set of user rights 389 with which the user is
associated using the Working Hour User Rights 264 and Out of Hours User Rights 264 settings. The user rights applied
can be controlled by a time profile 360 selected as the user's Working Hours Time Profile 264 setting. The effect of the
user rights can be displayed using the User Right View 264 control.
· Follow Me Number: Default = Blank. Range = Internal extension number.
Redirects the user's calls to the internal extension number entered. If the redirected call receives busy or is not
answered, it follows the user's forwarding and or voicemail settings as if it had been presented to their normal
extension. When a user has follow me in use, their normal extension will give alternate dialtone 846 when off hook. For
further details see Follow Me 771 .
· Calls targeting longest waiting type hunt groups ignore Follow Me.
· Calls triggered by actions at the user's original extension, for example voicemail ringback, ignore Follow Me.
· Park, hold and transfer return calls will go to the extension at which the user initiated the park, hold or transfer
action.
· Forward Unconditional: Default = Off
This option, when checked and a Forward Number is also set, forwards all external calls immediately. Additional
options allow this forwarding to also be applied to internal calls and to hunt group calls if required. Using Follow Me
overrides Forward Unconditional. When a user has forward unconditional in use, their normal extension will give
alternate dialtone 846 when off hook. If the destination is an internal user on the same system, they are able to transfer
calls back to the user, overriding the Forward Unconditional.
· To Voicemail: Default = Off. Software level = 5.0+.
If selected and forward unconditional is enabled, calls are forwarded to the user's voicemail mailbox. The Forward
Number and Forward Hunt Group Calls settings are not used. This option is not available if the system's
Voicemail Type is set to None. 1400, 1600 and 9600 Series phone users can select this setting through the
phone menu. Note that if the user disables forward unconditional, for example using Phone Manager or a short
code, the To Voicemail setting is cleared.
· Forward Number: Default = Blank. Range = Internal or External number. Up to 32 characters.
This option sets the destination number to which calls are forwarded when Forward Unconditional is checked.
The number can be an internal or external number. This option is also used for Forward on Busy and Forward on
No Answer if no separate Forward Number is set for those features. If a user forwards a call to a hunt group of
which they are a member, the group call is not presented to them but is presented to other members of the hunt
group.
· Forward Internal Calls: Default = On. Software level = 3.2+.
This option, when checked, sets that internal calls should be also be forwarded immediately when forward
unconditional is active.
Manager Manager 8.1
Manager
Page 281
15-601011 Issue 25l (11 February 2011)
· Forward Hunt Group Calls: Default = Off
Hunt group calls (internal and external) are not normally presented to a user who has forward unconditional active.
Instead they are presented to the next available member of the hunt group. This option, when checked, sets that
hunt group calls (internal and external) are also forwarded when forward unconditional is active. The group's Ring
Type must be Sequential or Rotary, not Collective or Longest Waiting. The call is forwarded for the period
defined by the hunt group's No Answer Time after which it returns to the hunt group if unanswered. Note also
that hunt group calls cannot be forwarded to another hunt group.
· Forward On Busy: Default = Off
When checked and a forward number is set, external calls are forwarded when the user's extension is busy. The number
used is either the Forward Number set for Forward Unconditional or if set, the separate Forward Number set
under Forward On Busy. Having Forward Unconditional active overrides Forward on Busy.
· If the user has Busy on Held selected, if forward on busy is active it is applied when the user is free to receive
calls but already has a call on hold.
· If the user's phone has multiple call appearance buttons, the system will not treat them as busy until all the call
appearance buttons are in use unless the last appearance button has been reserved for outgoing calls only.
· Forward On No Answer: Default = Off
When checked and a forward number is set, calls are forwarded when the user does not answer within their set No
Answer Time 274 (User | Telephony | Call Settings 274 ). Having Forward Unconditional active overrides Forward on
No Answer.
· Forward Number: Default = Blank. Range = Internal or External number. Up to 32 characters.
If set, this number is used as the destination for Forward On Busy and Forward On No Answer when on. If not
set, the Forward Number set for Forward Unconditional is used. If a user forwards a call to a hunt group of
which they are a member, the group call is not presented to them but is presented to other members of the hunt
group.
· Forward Internal Calls: Default = On. Software level = 3.2+.
When checked, this option sets that internal calls should be also be forwarded when forward on no answer or
forward on busy is active.
Manager Manager 8.1
Manager
Page 282
15-601011 Issue 25l (11 February 2011)
Configuration Settings: User Settings
5.7.8 Dial In
Use this dialogue box to enable dial in access for a remote user. An Incoming Call Route and RAS service must also be
configured.
User | Dial In
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Dial In On: Default = Off
When enabled, dial in access into the system is available via this User account.
· Dial In Time Profile: Default = <None>
Select the Time Profile 360 applicable to this User account. A Time Profile can be used to set time restrictions on dial in
access via this User account. Dial In is allowed during the times set in the Time Profile form. If left blank, then there are
no restrictions.
· Dial In Firewall Profile: Default = <None>
Select the Firewall Profile 362 to restrict access to the system via this User account. If blank, there are no Dial In
restrictions.
Manager Manager 8.1
Manager
Page 283
15-601011 Issue 25l (11 February 2011)
5.7.9 Voice Recording
This tab is used to activate the automatic recording of user's external calls. IP Office 6.1: The recording of internal calls as
well is also supported.
Call recording requires Voicemail Pro to be installed and running. Call recording also requires available conference
resources similar to a 3-way conference.
· IP Office 4.0+ introduces the following changes to recording:
· Calls to and from IP devices, including those using Direct media, can be recorded.
· Calls parked or held pause recording until the unparked or taken off hold.
· Recording is stopped if:
· User recording stops if the call is transferred to another user.
· User account code recording stops if the call is transferred to another user.
· Hunt group recording stops if the call is transferred to another user who is not a member of the hunt
group.
· Incoming call route recording continues for the duration of the call on the system.
User | Voice Recording
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Record Outbound: Default = None
Select whether automatic recording of outgoing calls is enabled. The Auto Record Calls option sets whether just
external calls or external and internal calls are included. Options for recording are:
· None: Do not automatically record calls.
· On: Record the call if possible. If not possible to record, allow the call to continue.
· Mandatory: Record the call if possible. If not possible to record, block the call and return busy tone.
· Percentages of calls: Record a selected percentages of the calls.
· Record Inbound: Default = None
Select whether automatic recording of incoming calls is enabled. Options for recording are:
· None: Do not automatically record calls.
· On: Record the call if possible. If not possible to record, allow the call to continue.
· Mandatory: Record the call if possible. If not possible to record, block the call and return busy tone.
· Percentages of calls: Record a selected percentages of the calls.
· Record Time Profile: Default = <None> (Any time)
Used to select a time profile 360 during which automatic call recording of incoming calls is applied. If no profile is
selected, automatic recording of incoming calls is active at all times.
· Recording (Auto): Default = Mailbox
Sets the destination for automatically triggered recordings.
· Mailbox
This option sets the destination for the recording to be a selected user or hunt group mailbox. The adjacent drop
down list is used to select the mailbox.
· Voice Recording Library: Software level = 3.0+.
This options set the destination for the recording to be a VRL folder on the voicemail server. The ContactStore
application polls that folder and collects waiting recordings which it then places in its own archive. Recording is still
done by the Voicemail Pro.
· Auto Record Calls: Default = External. Software level = 6.1
This setting allows selection of whether External or External & Internal calls are subject to automatic call recording.
· Recording (Manual): Default = Mailbox
Sets the destination for manually triggered recordings.
· Mailbox
This option sets the destination for the recording to be a selected user or hunt group mailbox. The adjacent drop
down list is used to select the mailbox.
Manager Manager 8.1
Manager
Page 284
15-601011 Issue 25l (11 February 2011)
Configuration Settings: User Settings
· Voice Recording Library: Software level = 3.0+.
This options set the destination for the recording to be a VRL folder on the voicemail server. The ContactStore
application polls that folder and collects waiting recordings which it then places in its own archive. Recording is still
done by the Voicemail Pro.
Manager Manager 8.1
Manager
Page 285
15-601011 Issue 25l (11 February 2011)
5.7.10 Coverage
Call coverage allows calls ringing at one extension (the 'Sender') to also be presented and answered at other defined
extensions (the 'Covering Extensions').
User | Coverage
Control Unit
SOE
Software Level
1.3 to 3.0DT only.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Covering Extension
The number of the extension that will be receiving the calls from the selected extension.
· Covering User
This is the user's account name associated with the covering extension.
To add a covering extension
1. Right-click within the Coverage window and select Add.
2. Choose from the list of extension/users.
3. Click OK.
Senders
Senders are extensions that share their alerting calls with other extensions, referred to as their covering extensions. The
only calls that are not shared are:
· Hunt Group calls that alert at the sender.
· Automatic Intercom calls.
· Calls that have been forwarded/diverted to the sender.
· Paging calls.
· Calls that are being covered for another station.
· Calls from one of their covering extensions.
Covering Extensions
When the sender's extension rings, the covering extensions also ring and show the call on a free call appearance button.
The display indicates that the call is from the sender by showing the incoming call's name or number and the sender's
name.
Covering Extensions can receive their own calls as well as calls for the Sender. A Covering Extension can receive a call
when:
· Send All Calls/Do Not Disturb is not active.
· Forwarding/Divert is not active.
· They have an available Call Appearance button to accept the call.
Manager Manager 8.1
Manager
Page 286
15-601011 Issue 25l (11 February 2011)
Configuration Settings: User Settings
Notes
To help covering extensions handle coverage calls efficiently it is suggested that the following buttons are programmed.
· Program additional Call Appearance buttons
Covering extensions must have enough call appearance buttons for their own calls and for the extensions they are
covering. By default each extension has three call appearance buttons. A suggested minimum extra is one less than the
number of call appearance buttons on the sender's extension.
· Program a Voicemail Collect button for the Sender
This will allow the covering extension to transfer a call directly to the sender's voicemail.
· Program an Automatic Intercom button for the Sender
This allows the covering extension to place a voice announcement. If you do not wish to make voice announcement
calls, use Dial Intercom instead.
· Program a Send All Calls button
· Program a Drop Button
This helps in transferring calls.
Call Alerting Scenarios
Listed below are examples of how calls to the sender's extension are handled in specific scenarios.
· Sender and Covering Extensions available
An incoming call alerts both the sender's and covering extension's on call appearance buttons. It alert the sender's
extension for their set No Answer Time and then alerts the covering extension only until the call is answered or the
caller hangs up.
· Sender available/Covering Extension not available
An incoming call alerts the sender only. The call remains alerting until it is answered or the caller hangs up.
· Sender not available/Covering Extension available
The call will alert the covering extension but not the sender. The call remains alerting until the call is answered or the
call hangs up.
· If voicemail is available and enabled for the sender, then in all the above scenarios, following the sender's No Answer
Time the call is redirected to the Sender's voicemail.
· Sender and Covering Extension not available
The caller hears busy tone or is redirected to the sender's voicemail.
Manager Manager 8.1
Manager
Page 287
15-601011 Issue 25l (11 February 2011)
5.7.11 Button Programming
This tab is used to assign functions to the programmable keys provided on many Avaya telephones. For full details of
button programming refer to the section Button Programming 506 .
· T3 Phones
T3 phone buttons have default functions. These are not shown in the configuration file but can be overridden by
settings added to the configuration file. Buttons left blank or set to call appearance will use the phone's default
function for that button.
User | Button Programming
Control Unit
SOE
Software Level
1.1+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
A
symbol indicates that the setting can also be set and locked within a set of user rights 389 with which the user is
associated using the Working Hour User Rights 264 and Out of Hours User Rights 264 settings. The user rights applied
can be controlled by a time profile 360 selected as the user's Working Hours Time Profile 264 setting. The effect of the
user rights can be displayed using the User Right View 264 control.
· Button No.
The number of the DSS key against which the function is being set. To set a function against a button double-click it or
select it and then click Edit.
· Label 514
This is a text label for display on the phone. If no label is entered, the default label for the selected action is used.
· Action 569
Defines the action taken by the menu item.
· Action Data
This is a parameter used by the selected action. The options here will vary according to the selected button action.
· Display All
The number of button displayed is based on the phone associated with the user when the configuration was loaded. This
can be overridden by selecting Display All Buttons. This may be necessary for users who switch between different
phones using hot desking or have an expansion unit attached to their phone.
Manager Manager 8.1
Manager
Page 288
15-601011 Issue 25l (11 February 2011)
Configuration Settings: User Settings
5.7.12 Menu Programming
These menus control a range of options that are specific to different types of phones. The functions become accessible
when the user logs in on the appropriate type of phone.
5.7.12.1 T3 Telephony
These settings are applied to the user when they are using a T3 phone.
User | Menu Programming | T3 Options
Control Unit
SOE
Software Level
3.1+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Third Party Forwarding
Avaya T3 phone users can be given menu options to change the forwarding settings of other users. In addition to the
following controls, this functionality is protected by the forwarding user's log in code.
· Allow Third Party Forwarding: Default = Off
Sets whether this user can change the forwarding settings of other users.
· Protect from Third Party Forwarding: Default = Off
Sets whether this user's forwarding settings can be changed by other users.
·
Advice of Charge
· Display Charges: Default = On. Software level = 4.0+.
This setting is used to control whether the user sees ISDN AOC information when using a T3 phone.
· Allow Self Administer: Default = Off. Software level = 5.0+.
If selected, this option allows the user to self-administer button programming.
5.7.12.2 Huntgroup
Avaya T3, 1400, 1600 and 9600 Series phone users can control various settings for selected hunt groups. These settings
are also used for one-X Portal for IP Office.
User | Menu Programming | Huntgroup
Control Unit
SOE
Software Level
3.1+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Can Change Membership: Default = Off
This list shows the hunt groups of which the user is a member. Up to 10 of these groups can be checked; those
group and the users current membership status are then displayed on the phone. The user can change their
membership status through the phone's menus.
· T3 Series Phones Pre-Manager 4.2: For the selected group, their status can be viewed and changed from the
phone by the user using Menu -> Settings -> Display/Audio ->Group Membership.
· T3 Series Phones - Manager 4.2+: The selected hunt groups and the user's current membership status are
displayed on the T3 phones status display. That display can be used to change the status.
· Can Change Service Status: Default = Off
This list shows all the hunt groups on the system. Up to 10 of these groups can be checked.
· T3 Series Phones: The user is then able to view and change the service status of the checked groups through
their T3 phones menus (Menu -> Group State).
· T3 Series Phones - Manager 4.2+: In addition to changing the status of the individual hunt groups displayed
via Menu -> Group State, the menu also displays option to change the status of all the groups; All in
service, All night service and All out service.
· Can Change Night Service Group: Default = Off. Software level = 5.0+.
If selected, the user can change the fallback group used when the hunt group is in Night Service mode.
· Can Change Out of Service Group: Default = Off. Software level = 5.0+.
If selected, the user can change the fallback group used when the hunt group is in Out of Service mode.
Manager Manager 8.1
Manager
Page 289
15-601011 Issue 25l (11 February 2011)
5.7.12.3 1400/1600
This menu applies to 1400, 1600 and 9600 Series phones.
User | Menu Programming | 1400/1600
Control Unit
SOE
Software Level
5.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Include Forwarding in Menu: Default = On. Software level = 5.0+.
This setting controls whether the user is able to view and use options to control their forwarding within the phone's
menus.
5.7.12.4 4400/6400
4412, 4424, 4612, 4624, 6408, 6416 and 6424 phones have a Menu key, sometimes marked with an
icon. When
Menu is pressed, a number of default functions are displayed. The < and > keys can be used to scroll through the
functions while the keys below the display can be used to select the required function.
The default functions can be overwritten by selections made within this tab.
User | Menu Programming
Control Unit
SOE
Software Level
3.2+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Menu No.
The menu position which the function is being set.
· Label 514
This is a text label for display on the phone. The label is limited to 5 characters. If no label is entered, the default label
for the selected action is used.
· Action 569
Defines the action taken by the menu button.
· Action Data
This is a parameter used by the selected action. The options here will vary according to the selected button action.
Manager Manager 8.1
Manager
Page 290
15-601011 Issue 25l (11 February 2011)
Configuration Settings: User Settings
5.7.13 Phone Manager Options
This tab is used to configure the user's Phone Manager application options.
User | Phone Manager Options
Control Unit
SOE
Software Level
3.2+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
A
symbol indicates that the setting can also be set and locked within a set of user rights 389 with which the user is
associated using the Working Hour User Rights 264 and Out of Hours User Rights 264 settings. The user rights applied
can be controlled by a time profile 360 selected as the user's Working Hours Time Profile 264 setting. The effect of the
user rights can be displayed using the User Right View 264 control.
· Allow user to modify Phone Manager settings: Default = On
This setting is used with the Phone Manager Status Options, Screen Pop Options and Hide Options below. It
controls whether those options are applied every time the user starts Phone Manager or only the first time the user
starts Phone Manager.
· If this setting is enabled, then the system configuration setting of those options are only applied the first time a user
starts Phone Manager on a PC. Those settings become part of the user's Phone Manager profile on that PC. They can
be changed by the user through Phone Manager. On subsequent Phone Manager starts the Manager settings are
ignored.
· If this setting is not enabled, the system configuration settings are applied every time the user starts Phone Manager
and cannot be overridden by the user.
· Agent Mode: Default = Off
This option controls the setting of the Agent Mode option on the Configure Preferences | Agent Mode tab within
Phone Manager Pro. When enabled, the user has additional toolbar controls for Busy Wrap Up, Busy Not Available and
Select Group. Note that the options on the Phone Manager Pro Agent Mode tab can be grayed out from user changes by
the Agent Mode setting in Configuration Options below.
· Phone Manager Type: Default = Lite
Determines the mode in which the user's copy of the Phone Manager application operates. Note that the number of
users able to simultaneously use modes other than Lite is controlled by licenses entered into the system configuration.
This setting cannot be changed by the user. For pre-3.2 systems this setting was located on the User | User 264 tab.
· Lite
Basic Phone Manager mode. This mode does not require any licenses.
· Pro
Advanced Phone Manager mode that enables a range of additional functions. This mode requires an available Phone
Manager Pro license, otherwise the application will run in Phone Manager Lite mode.
· Phone Manager PC Softphone
This is the VoIP IP phone mode of Phone Manager Pro. This mode requires both an available Phone Manager Pro
license and a Phone Manager Pro IP Audio Enabled license. The user must be associated with an VoIP extension within
the system configuration.
· Pro Telecommuter: Software level = 4.1+.
This version of Phone Manager Pro is supported with Phone Manager 4.1+. It allows the user to make and receive
calls via an external phone specified at Phone Manager log in. This mode requires an available Phone Manager Pro
license, otherwise the application will run in Phone Manager Lite mode.
· VoIP Mode: Default = On
This option only appears if the selected Phone Manager Type is set to Phone Manager PC Softphone. It sets the
Enable VoIP control within the user's Phone Manager PC Softphone. For IP Office 4.2+, this setting is automatically
enabled and greyed out.
· Book a Conference in Phone Manager: Default = Off
When enabled, displays links in the user's Phone Manager application for access to the Conferencing Center application
if installed. Note that to book a conference requires the user to have a Conferencing Center user ID and password. This
feature also requires the Conferencing Center URL 143 (System | System) 143 to be set. This setting cannot be
changed by the user. *For pre-3.2 systems this setting was located on the User | User 264 tab.
· Configuration Options
These options allow the user to changes the settings on the indicated configure preferences tabs within Phone Manager.
· The controllable tabs for Phone Manager Lite are Telephone and Do Not Disturb. For IP Office 4.0+, the Mobile
Twinning option on the Forwarding tab is also controllable (the twinning number remains editable even if the
Mobile Twinning option has been restricted).
Manager Manager 8.1
Manager
Page 291
15-601011 Issue 25l (11 February 2011)
· The additional controllable tabs for Phone Manager Pro and Phone Manager PC Softphone are Screen Pop, Compact
Mode, Agent Mode, Voicemail (Voicemail and Voicemail Ringback controls only).
· Screen Pop Options
These options allow selection of the Phone Manager Pro/Phone Manager PC Softphone screen pop options Ringing,
Answering, Internal, External and Outlook.
· The Allow user to modify Phone Manager setting controls whether these settings are applied only when Phone
Manager is first started or every time Phone Manager is started.
· Phone Manager Status Options
These options allow selection of the tabs to show within the call history area of the user's Phone Manager.
· The tabs selectable for Phone Manager are All, Missed, Status and Messages.
· The additional tabs selectable for Phone Manager Pro and PC Softphone are Incoming, Outgoing and Account
Codes.
· The Allow user to modify Phone Manager setting controls whether these settings are applied only when Phone
Manager is first started or every time Phone Manager is started.
· Hide Options
These options allow selection of the Phone Manager Pro/Phone Manager PC Softphone options Hide on close and Hide
on no calls.
· The Allow user to modify Phone Manager settings option controls whether these settings are applied only when Phone
Manager is first started or every time Phone Manager is started.
5.7.14 Hunt Group Memberships
This tab displays the hunt group of which the user has been made a member. The tick boxes indicate whether the user's
membership of each of those groups is currently enabled or disabled.
Manager Manager 8.1
Manager
Page 292
15-601011 Issue 25l (11 February 2011)
Configuration Settings: User Settings
5.7.15 Mobility (Twinning)
These settings relate to twinning features. These are where a user has a main or primary extension but also regularly
answer calls at a secondary or twinned phone. These features are intended for a single user, they are not aimed at two
users answering calls presented to a single primary extension.
Twinning
Twinning allows a user's calls to be presented to both their current extension and to another number. The system supports
two modes of twinning:
Internal
Mobile
Twinning Destination
Internal extensions only
External numbers only.
Supported in
All locales.*
All locales.
License Required
No
Yes
*IP Office 4.0 Q2 2007 maintenance release and higher only. Prior to IP Office 4.0 Q2 2007 maintenance release, Internal
twinning was not supported in North American locales.
Manager Manager 8.1
Manager
Page 293
15-601011 Issue 25l (11 February 2011)
5.7.15.1 Internal Twinning
IP Office 3.1+: Internal twinning can be used to link two system extensions to act as a single extension. Typically this
would be used to link a users desk phone with some form of wireless extension such as a DECT or WiFi handset.
Internal twinning is an exclusive arrangement, only one phone may be twinned with another. When twinned, one acts as
the primary phone and the other as the secondary phone. With internal twinning in operation, calls to the user's primary
phone are also presented to their twinned secondary phone. Other users cannot dial the secondary phone directly.
· If the primary or secondary phones have call appearance buttons, they are used for call alerting. If otherwise, call
waiting tone is used, regardless of the users call waiting settings. In either case, the Maximum Number of
Twinned Calls setting applies.
· Calls to and from the secondary phone are presented with the name and number settings of the primary.
· The twinning user can transfer calls between the primary and secondary phones.
· Logging out or setting do not disturb at the primary stops twinned calls alerting at the secondary also.
· Logging out or setting do not disturb at the secondary only affects the secondary.
· User buttons set to monitor the status of the primary also reflect the status of the secondary.
· Depending on the secondary phone type, calls alerting at the secondary but then answered at the primary may still
be logged in the secondary's call log. This occurs if the call log is a function of the phone rather than the system.
· Call alerting at the secondary phone ignoring any Ring Delay settings applied to the appearance button being used
at the primary phone. The only exception is buttons set to No Ring, in which case calls are not twinned.
· If the internal secondary extension is a Phone Manager Pro PC Softphone, it will only support basic call functions.
Advanced functions such as mailbox access to the primary mailbox are not supported.
For IP Office 5.0+, the following enhancements apply to internal twinned extensions:
· If using a T3, 1400, 1600 or 9600 Series phone as the secondary extension:
· The secondary extension's directory/contacts functions access the primary user's Centralized Personal Directory
744 entries in addition to the Centralized System Directory 741 .
· The secondary extension's call Log/call List functions access the primary user's Centralized Call Log
· The secondary extension's redial function uses the primary users Centralized Call Log
or single number mode setting is local to the phone.
745 .
745 .
Note: The list mode
· On 1400, 1600 and 9600 Series phones, twinned status is indicated by a T in the display of the secondary
extension.
· For all phone types, changing the following settings from either the primary or secondary extension, will apply the
setting to the primary user. This applies whether using a short code, programmable button or phone menu. The
status of the function will be indicated on both extensions if supported by the extension type.
· Forwarding settings.
· Group membership status and group service status.
· Voicemail on/off.
· Do Not Disturb on/off and DND Exceptions Add/Delete.
Manager Manager 8.1
Manager
Page 294
15-601011 Issue 25l (11 February 2011)
Configuration Settings: User Settings
Internal Twinning Settings
User | Mobility | Internal Twinning
Control Unit
SOE
Software Level
3.1+ (For North American locales, only supported from the IP Office 4.0 Q2 2007 maintenance
release).
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Internal Twinning: Software level = 3.1+.
Select this option to enable internal twinning for a user. Internal Twinning cannot be selected for a user if they
already have Mobility Features selected.
· Twinned Handset: Default = Blank.
For internal twinning, the drop-down list can be used to select an available user as the twinned calls destination.
Users not displayed in the list are already twinned with another user. If the list is grayed out, the user is a twinning
destination and the primary to which they are twinned is displayed. The secondary phone must be on the same
system.
· Maximum Number of Twinned Calls: Default = 1.
If set to one, when either the primary or secondary phone are in use, any additional incoming call receives busy
treatment. If set to two, when either phone is in use, it receives call waiting indication for any second call. Any
further calls above two receive busy treatment.
· Twin Bridge Appearances: Default = Off. Software level = 4.1+.
By default only calls alerting on the primary phone's call appearance buttons also alert at the secondary. When this
option is enabled, calls alerting on a bridged appearance button at the primary can also alert at the secondary.
· Twin Coverage Appearances: Default = Off. Software level = 4.1+.
By default only calls alerting on the primary phone's call appearance buttons also alert at the secondary. When this
option is enabled, calls alerting on a coverage appearance button at the primary can also alert at the secondary.
· Twin Line Appearances: Default = Off. Software level = 4.1+.
By default only calls alerting on the primary phone's call appearance buttons also alert at the secondary. When this
option is enabled, calls alerting on a line appearance button at the primary can also alert at the secondary.
Manager Manager 8.1
Manager
Page 295
15-601011 Issue 25l (11 February 2011)
5.7.15.2 Mobile Twinning
This method of twinning can be used with external numbers. Calls routed to the secondary remain under control of the
system and can be pulled back to the primary if required. If either leg of an alerting twinned call is answered, the other leg
is ended.
· IP Office 4.2+: The Mobile Twinning license is now called the Mobility Features license, reflecting the fact that it
can be used for Mobile Call Control and one-X Mobile Client support in addition to just mobile twinning. The mode of
license operation has also changed. Prior to IP Office 4.2, the license was only consumed by users who had Mobile
Twinning enabled. For IP Office 4.2, it is consumed by a user when they are configured for any of the mobility
features, including mobile twinning even if they have turned mobile twinning off.
· IP Office 6.0: Mobility options can be enabled for users whose Profile
265
is set to Mobile Worker or Power User.
· For systems upgraded to IP Office 6.0 with existing UMS Web Service licenses, those licenses can be used with
users whose Profile is set to Basic User.
A number of controls are available in addition to those on this tab.
· Button Programming Actions
The Emulation | Twinning action can be used to control use of mobile twinning. Set on the primary extension,
when that extension is idle the button can be used to set the twinning destination and to switch twinning usage on/
off. When a twinned call has been answered at the twinned destination, the button can be used to retrieve the call
at the primary extension.
· Mobile Twinning Handover (IP Office Release 6.1)
When on a call on the primary extension, pressing the Twinning button will make an unassisted transfer to the
twinning destination. This feature can be used even if the user's Mobile Twinning setting was not enabled.
· During the transfer process the button will wink.
· Pressing the twinning button again will halt the transfer attempt and reconnect the call at the primary
extension.
· The transfer may return if it cannot connect to the twinning destination or is unanswered within the user's
configured Transfer Return Time (if the user has no Transfer Return Time configured, a enforced time of
15 seconds is used).
· Short Code Features
The following short code actions are available for use with mobile twinning.
· Set Mobile Twinning Number.
· Set Mobile Twinning On.
· Set Mobile Twinning Off.
· Mobile Twinned Call Pickup.
· Caller ID
The options on the System | Twinning tab can be used to control which caller ID is sent with calls sent to the
twinned destination. The use of those options may be restricted by the trunk type carrying the twinned call and the
services provided by the line provider.
Mobile twinning is only applied to normal calls. It is not applied to:
· Intercom, dial direct and page calls.
· Calls alerting on line appearance, bridged appearance and call coverage buttons.
· Returning held, returning parked, returning transferred and automatic callback calls.
· Follow me calls.
· Forwarded calls (except in IP Office 4.2+ if the user's Forwarded Calls Eligible for Mobile Twinning setting is
enabled).
· Hunt group calls (except in IP Office 4.2+ if the user's Hunt Group Calls Eligible for Mobile Twinning setting is
enabled)
· Additional calls when the primary extension is active on a call or the twinning destination has a connected twinned
call.
Do Not Disturb and Twinning
· Mobile Twinning
Selecting DND disables mobile twinning.
· Internal Twinning
· Logging out or setting do not disturb at the primary stops twinned calls alerting at the secondary also.
Manager Manager 8.1
Manager
Page 296
15-601011 Issue 25l (11 February 2011)
Configuration Settings: User Settings
· Logging out or setting do not disturb at the secondary only affects the secondary.
· Do Not Disturb Exceptions List
For both types of twinning, while DND is selected calls from numbers entered in the user's Do Not Disturb
Exception List 270 are only presented to the primary phone.
User BLF indicators and application speed dials set to the primary user will indicate busy when they are connected to a
twinned call including twinned calls answered at the mobile twinning destination.
Analog Lines
These types of lines do not provide call progress signalling. Once a twinned call has been sent to an analog line, the
system assumes that it has been answered and stops ringing the primary extension.
Mobility Features Settings
User | Mobility | Mobility Features
Control Unit
SOE
Software Level
3.2+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
A
symbol indicates that the setting can also be set and locked within a set of user rights 389 with which the user is
associated using the Working Hour User Rights 264 and Out of Hours User Rights 264 settings. The user rights applied
can be controlled by a time profile 360 selected as the user's Working Hours Time Profile 264 setting. The effect of the
user rights can be displayed using the User Right View 264 control.
· Mobility Features:
If enabled this option allows any of the mobility features to be enabled for the user. This is subject to license
requirements of the system software release.
· For systems being upgraded to IP Office 4.2 where users have been previously enabled for Mobile Twinning,
this option will be off by default. This will disables the user's mobile twinning until their Mobility Features
option is also enabled.
· For IP Office 6.0, this option can be enabled for users whose Profile
265
is set to Teleworker or Power User.
· For systems upgraded to IP Office 6.0 with existing UMS Web Service licenses, those licenses can be
used with users whose Profile is set to Basic User.
· Mobile Twinning: Software level = 3.2+.
If selected, the user is enable for mobile twinning. The user can control this option through a Twinning
programmable button on their a phone.
663
· For user's setup for one-X Mobile Client, changes to their Mobile Twinning status made through the system
configuration or using a Twinning button are not reflected in the status of the Extension to Cellular icon
on their mobile client. However, changes to the Extension to Cellular status made from the mobile client
are reflected by the Mobile Twinning field in the system configuration. Therefore, for one-X Mobile Client
users, it is recommended that they control their Mobile Twinning status through the one-X Mobile Client
rather than through a Twinning button.
· Twinned Mobile Number: Default = Blank.
This field sets the external destination number for mobile twinned calls. It is subject to normal short code
processing and should include any external dialing prefix if necessary. For users of one-X Mobile Client 734 and
or Mobile Call Control 730 the number in this field is used to match the users setting to the incoming CLI.
· Twinning Time Profile: Default = <None> (Any time)
This field allows selection of a time profile during which mobile twinning will be used.
· Mobile Dial Delay: Default = 2 seconds
This setting controls how long calls should ring at the user's primary extension before also being routed to ring
at the twinning destination number. This setting may be used at the user's choice, however it may also be a
necessary control. For example, if the twinning number is a mobile device that has been switched off, the
mobile service provider may immediately answer the call with their own voicemail service. This would create a
scenario where the user's primary extension does not ring or ring only briefly.
· Mobile Answer Guard: Default = 0 (Off), Range = 0 to 99 seconds. Software level = 4.2+.
This control can be used in situations where calls sent to the twinned destination are automatically answered
by a voicemail service or automatic message if the twinned device is not available. If a twinned call is answered
before the Mobile Answer Guard expires, the system will drop the call to the twin.
· Hunt group calls eligible for mobile twinning: Default = Off
This setting controls whether hunt group calls ringing the user's primary extension should also be presented to
the mobile twinning number.
Manager Manager 8.1
Manager
Page 297
15-601011 Issue 25l (11 February 2011)
· Forwarded calls eligible for mobile twinning: Default = Off
This setting controls whether calls forwarded to the user's primary extension should also be presented to the
mobile twinning number.
· Twin When Logged Out: Default = Off. Software level = 4.2+.
If enabled, if the user logs off their primary extension, calls to that extension will still alert at their twinned
device rather than going immediately to voicemail or busy.
· When logged out but twinned, Mobile Dial Delay is not applied.
· Hunt group calls (all types) will be twinned if Hunt group calls eligible for mobile twinning is enabled.
When this is the case the user's idle time is reset for each externally twinned call answered (note that
calls twinned over analog and analog emulation trunks are automatically treated as answered).
· When the user's Mobile Time Profile, if configured, is not active they will not get twinning calls. Calls will
be treated the same as the user was logged out user with no twinning.
· Callback calls initiated by the user will mature to the Twinned Mobile Number. It will also be possible to
initiate Automatic Callback to the user with external twinning and their busy/free state will be tracked for
all calls via the system.
· Any Bridged Appearance set to the user will not alert. Coverage appearance buttons for the user will
continue to operate.
· The BLF/user button status shown for a logged out user with Logged Off Mobile Twinning is as follows:
· If there are any calls alerting or in progress through the system to the twin the user status is shown
as alerting or in-use as appropriate. This includes the user showing as busy/in-use if they have such a
call on hold and they have Busy on Held enabled.
· If the user enables DND through Mobile Call Control or one-X Mobile client their status will show as
DND/busy.
· Calls from the system dialed direct to the users twinned destination rather than directed by twinning
from their primary extension will not change the user's status.
· one-X Mobile Client: Default = Off. Software level = 4.2+ (IP500/IP500v2 digital trunks only).
one-X Mobile Client is a software application that can be installed on Windows Mobile and Symbian mobile cell
phones. It allows the user to access a number of system features. For details see one-X Mobile Client 734 .
· Mobile Call Control: Default = Off. Software level = 4.2+ (IP500/IP500v2 digital trunks only).
Mobile call control is only supported on digital trunks. It allows a user receiving a call on their twinned device to
access system dial tone and then perform dialing action including making calls and activating short codes. For
details see Mobile Call Control 730 .
· Mobile Callback : Default = Off. Software level = 6.0+ (IP500/IP500v2 digital trunks only).
Mobile callback 733 allows the user to call the system and then hang up. The system will then make a call to the
user's CLI and when answered, provide them with dial tone from the system to make calls.
Manager Manager 8.1
Manager
Page 298
15-601011 Issue 25l (11 February 2011)
Configuration Settings: User Settings
5.7.16 Announcements
Announcements are played to callers waiting to be answered. This includes callers being presented to hunt group
members, ie. ringing, and callers queued for presentation.
· The system supports announcements using Voicemail Pro, Voicemail Lite (pre-5.0 only) or Embedded Voicemail.
· If no voicemail channel is available for an announcement, the announcement is not played.
· In conjunction with Voicemail Pro, the system allows a number of voicemail channels to be reserved for
announcements. See System | Voicemail 157 .
· With Voicemail Pro, the announcement can be replaced by the action specified in a Queued (1st announcement) or
Still Queued (2nd announcement) start point call flow. Refer to the Voicemail Pro Installation and Maintenance
documentation for details.
· Calls can be answered during the announcement. If it is a mandatory requirement that announcements should be
heard before a call is answered, then a Voicemail Pro call flow should be used before the call is presented.
· Warning: Call Billing and Logging
Note that a call becomes connected when the first announcement is played to it. That connected state is
signaled to the call provider who may start billing at that point. The call will also be recorded as answered
within the SMDR 898 output once the first announcement is played.
· If a call is rerouted, for example forwarded, the announcement plan of the original user is still applied until the call
is answered. The exception is calls rerouted to a hunt group at which point the hunt group announcement settings
are applied.
· For announcements to be used effectively, either the user's no answer time must be extended beyond the default
15 seconds or Voicemail On should be deselected.
Recording Announcements
· Voicemail Pro
There is no mechanism within the telephony user interfaces (TUI) to record user announcements. To provide
custom announcements, user queued and still queued start points must be configured with Voicemail Pro with the
required prompts played by a generic action.
· Embedded Voicemail
Embedded Voicemail does not include any default announcement or method for recording an announcement. The
Record Message 486 short code feature is provided to allow the recording of announcements. The telephone
number field of short codes using this feature requires the extension number followed by either ".1" for
announcement 1 or ".2" for announcement 2. For example, for extension number 300, the short codes *91N# |
Record Message | N".1" and *92N# | Record Message | N".2" could be used to allow recording of the
announcements by dialing *91300# and *92300#.
Manager Manager 8.1
Manager
Page 299
15-601011 Issue 25l (11 February 2011)
Hunt Group | Announcements
Control Unit
SOE
Software Level
4.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Announcements On: Default = Off.
This setting enables or disables announcements.
· Wait before 1st announcement: Default = 10 seconds. Range = 0 to 9999 seconds.
This setting sets the time delay from the calls presentation, after which the first announcement should be played to the
caller. If Synchronize Calls is selected, the actual wait may differ, see below.
· Flag call as answered: Default = Off.
This setting is used by the CCC and CBC applications. By default they do not regarded a call as answered until it has
been answered by a person or by a Voicemail Pro action with Flag call as answered selected. This setting allows calls
to be marked as answered once the caller has heard the first announcement. This setting is not used by the Customer
Call Reporter application.
· Warning: Call Billing and Logging
Note that a call becomes connected when the first announcement is played to it. That connected state is
signaled to the call provider who may start billing at that point. The call will also be recorded as answered
within the SMDR 898 output once the first announcement is played.
· Post announcement tone: Default = Music on hold.
Following the first announcement, you can select whether the caller should hear Music on Hold
Silence until answered or played another announcement.
763 ,
Ringing or
· 2nd Announcement: Default = On.
If selected, a second announcement can be played to the caller if they have still not been answered.
· Wait before 2nd announcement: Default = 20 seconds. Range = 0 to 9999 seconds.
This setting sets the wait between the 1st and the 2nd announcement. If Synchronize Calls is selected, the actual wait
may differ, see below.
· Repeat last announcement: Default = On.
If selected, the last announcement played to the caller is repeated until they are answered or hang-up.
· Wait before repeat: Default = 20 seconds. Range = 0 to 9999 seconds.
If Repeat last announcement is selected, this setting sets is applied between each repeat of the last announcement.
If Synchronize Calls is selected, this value is grayed out and set to match the Wait before 2nd announcement
setting.
· Synchronize calls: Default = Off
This option can be used to restrict how many voicemail channels are required to provide the announcements.
· Off
When Synchronize calls is off, announcement are played individually for each call. This requires a separate voicemail
channel each time an announcement is played to each caller. While this ensures accurate following of the wait
settings selected, it does not make efficient use of voicemail channels.
· On
When Synchronize calls is on, if a required announcement is already being played to another caller, further callers
wait until the announcement been completed and can be restarted. In addition, when a caller has waited for the set
wait period and the announcement is started, any other callers waiting for the same announcement hear it even if
they have not waited for the wait period. Using this setting, the maximum number of voicemail channels ever needed
is 1 or 2 depending on the number of selected announcements.
· Note: Interaction with Voicemail Pro Queued and Still Queued Start Points
If either custom Queued or Still Queued start point call flows are being used for the announcements, when
Synchronize Calls is enabled those call flows will support the playing of prompts only. Voicemail Pro actions such
as Speak ETA, Speak Position, Menu, Leave Mail, Transfer and Assisted Transfer, etc. are not supported.
Manager Manager 8.1
Manager
Page 300
15-601011 Issue 25l (11 February 2011)
Configuration Settings: User Settings
5.7.17 Personal Directory
Each user is able to have up to 100 personal directory records, up to the overall system limit.
Manager
Total User Directory Records
IP500/IP500v2
10800
IP412
3600
IP406 V2
1900
These records are used as follows:
· Pre-IP Office 5
· When using a T3 phone, the user is able to view and call their personal directory numbers.
· Unlike system directory numbers, these entries are not used for name matching against the incoming ICLID of
calls the user received.
· IP Office 5+
· When using ETR, T3, 1400, 1600, or 9600 Series phones, the user is able to view and call their personal
directory numbers.
· When using a 1400, 1600, or 9600 Series phone, the user is also able to edit and add personal directory
entries.
· If the user hot desks to a T3, 1400, 1600, or 9600 Series phone on another system in a Small Community
Network, they can still access their personal directory.
Directory entries are used for two types of function:
· Directory Dialing
Directory numbers are displayed by user applications such as Phone Manager and SoftConsole. Directory numbers
are viewable through the Dir 615 function on many Avaya phones (Contacts or History). They allow the user to
select the number to dial by name. The directory will also contain the names and numbers of users and hunt groups
on the system.
· The Dir function groups directory entries shown to the phone user into the following categories. Depending on
the phone, the user may be able to select the category currently displayed. In some scenarios, the categories
displayed may be limited to those supported for the function being performed by the user:
· External
Directory entries from the system configuration. IP Office 5.0+: This includes HTTP and LDAP imported
entries.
· Groups
Groups on the system. If the system is in a Small Community Network it will also include groups on other
systems in the network (For pre-IP Office 5 systems, this feature requires the systems to have Advanced
Small Community Networking licenses).
· Users or Index
Users on the system. If the system is in a Small Community Network it will also include users on other
systems in the network (For pre-IP Office 5 systems, this feature requires the systems to have Advanced
Small Community Networking licenses).
· Personal
Available for T3 phones, T3 IP phones, 1400, 1600 and 9600 Series phones. These are the user's personal
directory entries stored within the system configuration.
· Name Matching
Directory entries are also used to associate a name with the dialled number on outgoing calls or the received CLI on
incoming calls. When name matching is being done, a match in the users personal directory overrides any match in
the system directory. Note that some user applications also have their own user directory.
· The IP Office Phone Manager and SoftConsole applications have their own user directories which are also used
by the applications name matching. Matches in the application directory may lead to the application displaying
a different name from that shown on the phone.
· Name matching is not performed when a name is supplied with the incoming call, for example QSIG trunks.
· Directory name matching is not supported for DECT handsets.
User | Personal Directory
Control Unit
Manager Manager 8.1
Manager
SOE
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
Page 301
15-601011 Issue 25l (11 February 2011)
Software Level
Mergeable
3.1+.
.
· Name: Range = Up to 31 characters.
Enter the text to be used to identify the number.
· Number: Range = Up to 31 digits plus * and #.
Enter the number, without spaces, to be dialed. Wildcards are not supported in user personal directory entries. Note
that if the system has been configured to use an external dialing prefix, that prefix should be added to directory
numbers.
Manager Manager 8.1
Manager
Page 302
15-601011 Issue 25l (11 February 2011)
Configuration Settings: User Settings
5.7.18 SIP
This tab is available when a SIP trunk with a SIP URI 238 entry has been added to the IP Office configuration. It is also
available when an H323 trunk 220 set to IP Office SCN or IP Office SCN - Fallback has been added to the IP Office
configuration.
Various fields within the URI settings used by SIP trunks can be set to Use Internal Data. When that is the case, the
values from this tab are used inserted into the URI when the user makes or receives a SIP call. Within a Small Community
Network, that includes calls which break out using a SIP trunk on another system within the SCN.
User | SIP
Control Unit
SOE
Software Level
4.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· SIP Name: Default = User name.
The value from this field is used when the From field of the SIP URI being used for a SIP call is set to Use Internal
Data.
· SIP Display Name (Alias): Default = User name.
The value from this field is used when the Display Name field of the SIP URI being used for a SIP call is set to Use
Internal Data.
· Contact: Default = User name.
The value from this field is used when the Contact field of the SIP URI being used for a SIP call is set to Use Internal
Data.
· Anonymous: Default = Off.
If the From field in the SIP URI is set to Use Internal Data, selecting this option inserts Anonymous into that field
rather than the SIP Name set above.
Manager Manager 8.1
Manager
Page 303
15-601011 Issue 25l (11 February 2011)
5.8 Hunt Group Settings
A hunt group is a collection of users accessible through a single directory number. Calls to that hunt group
can be answered by any available member of the group. The order in which calls are presented can be
adjusted by selecting different group types and adjusting the order in which group members are listed.
· Call Presentation
The order in which the available members of the hunt group are used for call presentation
is selectable.
· Availability
There are a range of factors which control whether hunt group calls are presented to a
user in addition to that user being a member of the hunt group.
· Queuing
This optional feature allows calls to be queued when the number of calls to be presented
exceeds the number of available hunt group members to which call can be presented.
· Announcements
On systems with a voicemail server (Voicemail Pro, Voicemail Lite (pre-IP Office Release 5)
or Embedded Voicemail), announcements can be played to callers waiting to be answered.
That includes calls that are ringing and calls that are queued.
· Overflow
This optional feature can be used to redirect calls to an overflow group or groups when not
answered within a set time.
· Fallback
A hunt group can be taken out of operation manually or using a time profile. During
fallback, calls can be redirected to a fallback group or sent to voicemail or just receive
busy tone. Two types of fallback are supported; night service and out of service.
· Voicemail
Calls can be redirected to voicemail. The system allows selection of whether hunt group
calls remain in the hunt group mailbox or are copied (broadcast) to the individual
mailboxes of the hunt group members. When messages are stored in the hunt group's
own mailbox, selection of who receives message waiting indication is possible.
Changing the name of a hunt group has the following effects:
· A new empty mailbox is created on voicemail with the new hunt group name.
· Entries in other groups' Overflow lists will be updated.
· Out-of-Service and Night-Service fallback references are updated.
Modifying the extension number of a hunt group updates the following:
· Group buttons.
· Overflow, Out of Service Fallback and Night Service Fallback group entries.
· Incoming call route entries.
When a hunt group is deleted, all references to the deleted group will be removed including:
· Entry in Incoming call routing table.
· Transfer target in internal auto-attendant.
· Overflow, Night-Service or Fallback-Service on other groups.
· DSS keys monitoring group status.
Manager Manager 8.1
Manager
Page 304
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Hunt Group Settings
Hunt Groups in a Small Community Network (SCN)
In a Small Community network, the extension numbers of users are automatically shared between IP Office systems and
become diallable from other systems without any further programming.
For IP Office 4.0+, the following features are available for hunt groups within a Small Community Network. For pre-IP
Office Release 5 systems, these features requires the IP Offices to have Advanced Small Community Networking
licenses.
· Advertised Hunt Groups
Each hunt group can be set as being 'advertised'. The hunt group can then be dialed from other systems within the
SCN. The hunt groups extension number and name must be unique within the network. Non-advertised hunt group
numbers remain local only to system hosting the hunt group.
· Distributed Hunt Groups
Hunt groups on a system can include users located on other IP Office systems within the SCN network. Distributed
hunt groups are automatically advertised to other systems within the SCN. Note that distributed hunt groups can
only be edited on the system on which they were created.
Manager Manager 8.1
Manager
Page 305
15-601011 Issue 25l (11 February 2011)
5.8.1 Hunt Group
Hunt Group | Hunt Group
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Name: Range = Up to 15 characters
The name to identify this hunt group. Only alphanumeric characters with no spaces should be used. Start names with a
alphabetic character. This field is case sensitive and must be unique.
· Voicemail uses the name to match a group and its mailbox. Changing a group's name will route its voicemail calls to a
new mailbox. Note however that Voicemail Pro will treat names such as "Sales", "sales" and "SALES" as being the
same.
· CCR Agent Group: Default = Off. Software level = 4.2+.
This option is used in conjunction with IP Office CCR application to indicate the groups for which it collects information.
CCR Agent Hunt Groups should only contain users who have been configured as CCR Agents 276 (User | Telephony |
Supervisor Settings 276 ) option. When selected, the menus to select hunt group members will only show users
configured as CCR Agents and a warning will be given if the group already contains any users who are not CCR Agents.
· Extension: Range = 2 to 9 digits.
This sets the directory number for calls to the hunt group.
· Groups for CBC and CCC should only use up to 4 digit extension numbers.
· Extension numbers in the range 8897 to 9999 are reserved for use by the IP Office Delta Server.
· Ring Mode: Default = Sequential
Sets how the system determines which hunt group member to ring first and the next hunt group member to ring if
unanswered. This is used in conjunction with the User List which list the order of group membership.
· Collective (previously known as Group)
All available phones in the User List ring simultaneously.
· Collective Call Waiting (Software level = 3.0+)
This is a Collective hunt group as above but with hunt group call waiting also enabled (previous versions of Manager
used a separate Call Waiting On control to select this option for a Collective group). When an additional call to the
hunt group call is waiting to be answered, users in the group who are already on a call will receive call waiting
indication. On phones with call appearance buttons, the call waiting indication takes the form of an alert on the next
available call appearance button. On other phones, call waiting indication is given by a tone in the speech path (the
tone is locale specific).
· Pre-IP Office 4.0: All the users in the group must also have their own Call Waiting On
274
setting enabled.
· IP Office 4.0+: The user's own Call Waiting On setting is overridden when they are using a phone with call
appearances. Otherwise the user's Call Waiting On setting is used in conjunction with the hunt group setting.
· Sequential (previously known as Linear and Hunt)
Each extension is rung in order, one after the other, starting from the first extension in the list each time.
· Rotary (previously known as Circular)
Each extension is rung in order, one after the other. However, the last extension used is remembered. The next call
received rings the next extension in the list.
· Longest Waiting (previously known as Idle and Most Idle)
The extension that has been unused for the longest period rings first, then the extension that has been idle second
longest rings, etc. For extensions with equal idle time, 'sequential' mode is used.
· IP Office 4.2+: Where hunt group calls are being presented to a twinned extension, the longest waiting status of
the user can be reset by calls answered at either their master or twinned extension.
· No Answer Time (secs): Default = System Default. Range = System Default or 6 to 99999 seconds.
The number of seconds an extension rings before the call is passed to another extension in the list. This applies to all
telephones in this group and the Overflow Groups (if used). For collective hunt groups, the idea of moving to the next
member when the No Answer Time expires does not apply, instead calls will continue ringing unless overflow or
voicemail is applied.
· Hold Music Source: Default = No Change. Software level =4.2+ (Not Small Office Edition).
The system can support up to 4 music on hold sources; the System Source (either an internal file or the external
source port or tones) plus up to 3 additional internal wav files, see System | Telephony | Tones & Music 163 . Before
reaching a hunt group, the source used is set by the system wide setting or by the Incoming Call Route 344 that
routed the call. If the system has several hold music sources available, this field allows selection of the source to
associate with calls presented to this hunt group or to leave it unchanged. The new source selection will then apply even
if the call is forwarded or transferred out of the hunt group unless changed again by another hunt group. If the call is
routed to another IP Office 4.2+ system in a Small Community Network, the matching source is used if available.
Manager Manager 8.1
Manager
Page 306
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Hunt Group Settings
· Calls overflowing from a hunt group will use the hold music source setting of the original hunt group and ignore the
setting of the overflow group.
· Calls going to night service or out of service fallback group use the hold music source setting of the original hunt
group and then, if different, the setting of the fallback group. The setting of further fallback groups from the first
are ignored.
· Voicemail Answer Time: Default = 45 seconds, Range = Off, 1 to 99999 seconds. Software level = 4.0+.
This setting sets how long a call should be presented to a hunt group, and its overflow groups if set, before going to
voicemail. When exceeded the call goes to voicemail (if available) regardless of any announcements, overflow, queuing
or any other actions. If set to Off, voicemail is used when all available members of the hunt group have been altered for
the no answer time.
· Agent's Status on No-Answer Applies To: Default = None (No status change). Software level = 4.0+.
For call center agents, that is hunt group members with a log in code and set to forced log in, the system can change
the agent's status if they do not answer a hunt group call presented to them before being automatically presented to
the next available agent.
· This setting defines what type of hunt group calls should trigger use of the agent's Status on No Answer setting.
The options are None, Any Call and External Inbound Calls Only.
· The new status is set by the agent's Status on No Answer
276
(User | Telephony | Supervisor Settings
276 )
setting.
· This action is only applied if the call is unanswered at the agent for the hunt group's No Answer Time or longer. It
does not apply if the call is presented and, before the No Answer Time expires, is answered elsewhere or the caller
disconnects.
· This option is not used for calls ringing the agent because the agent is in another group's overflow group.
· Central System: Software level = 4.0+.
The field is for information only. It displays the IP Office system where the hunt group was created and can be
configured. For pre-IP Office Release 5 systems, this field is only visible if the IP Office has an Advanced Small
Community Networking license.
· Advertise Group: Default = Off. Software level = 4.0+.
If selected, details of the hunt group are advertised to the other systems within a Small Community Network and the
hunt group can be dialled from those other systems without the need for routing short codes. For pre-IP Office Release
5 systems, this field is only visible if the IP Office has an Advanced Small Community Networking license.
· Advertised groups must have an extension number that is unique within the SCN. If an advertised hunt group's
extension number conflicts with a local groups extension number, the advertised group is ignored.
· Groups set as advertised will appear in the configuration of other IP Office systems. However an advertised group can
only be edited on the IP Office system on which it was created. Note that advertised groups are not saved as part of
the configuration file when File | Save Configuration As is used.
· Hunt groups that contain members from other IP Office systems are automatically advertised.
· Call Waiting On: Default = Off. Software level = 3.0+.
For Manager 6.2 and above, this control has been combined with the Ring Type option Collective. See the Ring Mode
setting Collective Call Waiting above.
· User List
This is an ordered list of the users who are members of the hunt group. For Sequential and Rotary groups it also sets
the order in which group members are used for call presentation.
· Repeated numbers can be used, for example 201, 202, 201, 203, etc. Each extension will ring for the number of
seconds defined by the No Answer Time before moving to the next extension in the list, dependent on the Hunt
Type chosen.
· The check box next to each member indicates the status of their membership. Checked boxes appear for members
whose membership is enabled. The order of the users can be changed by dragging the existing entries to the required
position.
· To add entries select Edit. A new menu is displayed that shows available users on the left and current group
members of the right. The lists can be sorted and filtered.
· Users on remote systems in a Small Community Network can also be included. Groups containing remote members
are automatically advertised within the SCN. For pre-IP Office Release 5 systems, this can only be done if the IP
Office has an Advanced Small Community Networking license.
· Overflow Group List
If a call cannot be answered by the extensions shown in the User List, it can be presented to available extensions in
the groups listed in this list. Each group is used in turn in order from the top of the list. The call is presented to each
overflow group member once, using the Ring Mode of the overflow group. If the call remains unanswered the next
overflow group listed is used. If the call remains unanswered at the end of the list of overflow groups, it is presented to
available members of the overflowing group again and then to those in its overflow list in a repeating loop.
· If Queuing is off and all members of the hunt group are busy, a call presented to the group will overflow
immediately, irrespective of the Overflow Time.
· If Queuing is on and all members of the hunt group are busy, a call presented to the group may queue for up to the
Overflow Time before overflowing.
Manager Manager 8.1
Manager
Page 307
15-601011 Issue 25l (11 February 2011)
· If the call is currently ringing a hunt group member when the Overflow Time expires, it will complete ringing using
the group's No Answer Time before overflowing.
· If no Overflow Time is set, a call will overflow when it has rung each available hunt group member without being
answered.
· The groups in the overflow list are only used to expand the set of users available to answer calls. The overflowing call
still belongs to the group that is overflowing and uses the settings of that group. For example:
· Calls that overflow use the announcement settings of the group from which they are overflowing.
· Calls that overflow use the Voicemail Answer Time of the original group from which are are overflowing.
· Calls that are overflowing are included in the overflowing group's Queue Length and Calls In Queue Threshold.
They are not included in those values for the hunt group to which they overflow.
· The only settings of the groups in the overflow list that are used is the Ring Mode.
· Overflow Time: Default = Blank, Range = Off or 1 to 99999 seconds.
Hunt groups with an Overflow Group List set support the use of overflow to expand the group. When also using
queueing 316 the Overflow Time can also be used to set how long calls queue before also overflowing.
· Overflow Mode: Default = Group. Software level = 4.2+.
This option allows selection of whether the overflow of queued calls is determined on a call by call basis or applied to all
calls for the hunt group once any one call overflows.
· Group
In this mode, once one call overflows all additional queued calls overflow immediately. This is equivalent to the
overflow mode used by IP Office 4.0-4.1 systems.
· Call
In this mode, each individual call will follow the groups overflow time settings before it overflows. This is equivalent
to the overflow mode used by pre-IP Office 4.0 system.
Manager Manager 8.1
Manager
Page 308
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Hunt Group Settings
5.8.2 User List/Select Members
The hunt group Select Members form is used to add and remove users from the hunt group. For hunt group's with a
Ring Mode of Sequential or Rotary it is also used to set the order of use for the members of the hunt group.
The filters section at the top of the form can be used to filter the users shown. Note for hunt groups set as a CCR Agent
Group, only users set as CCR Agent are shown.
The controls and data on the form vary depending on the hunt group's Ring Mode setting and on whether the system is
in a Small Community Network.
To sort either table, click on the column header that should be used for the sort the table. Sort changes the order of
display only, it does not change the actual order of hunt group membership.
For Sequential and Rotary hunt groups, an Order column is shown. To change the order position of a hunt group
member, select the member and then use the up and down arrow buttons.
During the actions below, the Shift and Ctrl keys can be used as normal to select multiple users. Note that that the list of
members has been sorted, the sort is updated after adding or moving members.
Manager Manager 8.1
Manager
Page 309
15-601011 Issue 25l (11 February 2011)
· Add Before
Using the Shift and/or Ctrl keys, select the users you want to add and then on the right select the existing
member that you want to add them before.
· Add After
Using the Shift and/or Ctrl keys, select the users you want to add and then on the left select the existing
member after which you want them added.
· Append
Add the selected users on the left to the hunt group members on the right as the last member in the group
order.
· Remove
Remove the selected users on the right from the list of hunt group members.
·
Move the selected member on the right up or down the membership order of the group.
Manager Manager 8.1
Manager
Page 310
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Hunt Group Settings
5.8.3 Voicemail
The system supports voicemail for hunt groups in addition to individual user voicemail mailboxes.
· When is voicemail used?
If voicemail is available and enabled for a hunt group, it is used in the following scenarios.
· Voicemail Answer Time (IP Office 4.0+)
The default timeout is 30 seconds. When exceeded the call goes to voicemail (if available) regardless of any
announcements, overflow, queuing or any other actions.
· Unanswered Calls
When a call has rung unanswered at all the available hunt group members. If overflow is being used that will include
being unanswered by the available overflow group members.
· Queue Limit Reached
If queuing is being used, it overrides use of voicemail prior to expiry of the Voicemail Answer Time, unless the
number of queued callers exceeds the set Queue Limit. By default there is no set limit.
· Night Service
When the hunt group is in night service with no Night Service Fallback Group set.
· Out of Service
When the hunt group is out of service with no Out of Service Fallback Group set.
· Automatic Call Recording
Incoming calls to a hunt group can be automatically recorded using the settings on the Hunt Group | Voice Recording
319 tab.
· Which Mailbox is Used
· When a caller is directed to voicemail to leave a message, the system indicates the target user or hunt group
mailbox.
· Pre-IP Office 4.0: The mailbox of the user or hunt group whose settings have caused the call to go to voicemail
is used.
· For IP Office 4.0+: The mailbox of the originally targeted user or hunt group is used. This applies even if the
call has been forwarded to another destination. It also includes scenarios where a hunt group call overflows or
is in fallback to another group.
· Voicemail Pro can be used to customize which mailbox is used separately from the mailbox indicated by the
system.
· Who Receives Message Waiting Indication?
By default no user is configured to receive message waiting indication when a hunt group voicemail mailbox contains
new messages. Message waiting indication is configured by adding a Hgroupname entry to a user's SourceNumbers
tab (User | Source Numbers 272 ).
· Accessing Hunt Group Messages
By default no mechanism is provided for access to specific hunt group mailboxes. Access needs to be configured using
either a short code, programmable button or source number.
· Phone Manager
User's with hunt group message waiting indication can access the hunt group mailbox through Phone Manager.
· Intuity Emulation Mailbox Mode
For systems using Intuity emulation mode mailboxes, the hunt group extension number and voicemail code can be
used during normal mailbox access.
· IP Office Mailbox Mode
For IP Office mode mailbox access, short codes are required to access the mailbox directly.
· Broadcast
The voicemail system (Voicemail Pro only) can be instructed to automatically forward messages to the individual
mailboxes of the hunt group members. The messages are not stored in the hunt group mailbox.
Manager Manager 8.1
Manager
Page 311
15-601011 Issue 25l (11 February 2011)
Hunt Group | Voicemail
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Voicemail Code: Default = Blank, Range = 0 to 15 digits
A code (1-15 digits) used by the voicemail server to validate access to this mailbox. If remote access is attempted to a
mailbox that has no voicemail code set, the prompt "Remote access is not configured on this mailbox" is played.
Whether the caller will be prompted to enter this code varies as follows:
· Embedded Voicemail
The voicemail code is used if set.
· Voicemail Lite/Voicemail Pro in IP Office mode
The voicemail code is required when accessing the mailbox from a location that is not set as a trusted number in
the user's Source Numbers 272 list. Also Voicemail Pro call flows containing an action where the action's PIN code
set to $ will prompt the user for their voicemail code.
· Voicemail Pro in Intuity Emulation mode
By default the voicemail code is required for all mailbox access. The first time the mailbox is accessed the user will
be prompted to change the password. Also if the voicemail code setting is left blank, the caller will be prompted to
set a code when they next access the mailbox. The requirement to enter the voicemail code can be removed by
adding a customized user or default collect call flow, refer to the Voicemail Pro manuals for full details. Also
Voicemail Pro call flows containing an action where the action's PIN code set to $ will prompt the user for their
voicemail code.
· Codes set through the Voicemail Pro telephone user interface are restricted to valid sequences. For example,
attempting to enter a code that matches the mailbox extension, repeat the same number (1111) or a sequence of
numbers (1234) are not allowed. If these types of code are required they can be entered through Manager.
· Voicemail On Default = On
When on, the mailbox is used by the system to answer the user's unanswered calls or calls when the user's extension
returns busy. Note that selecting off does not disable use of the user's mailbox. Messages can still be forward to their
mailbox and recordings can be placed in it. The mailbox can also still be accessed to collect messages.
· When a caller is directed to voicemail to leave a message, the system indicates the target user or hunt group
mailbox.
· Pre-IP Office 4.0: The mailbox of the user or hunt group whose settings have caused the call to go to voicemail
is used.
· For IP Office 4.0+: The mailbox of the originally targeted user or hunt group is used. This applies even if the
call has been forwarded to another destination. It also includes scenarios where a hunt group call overflows or
is in fallback to another group.
· Voicemail Pro can be used to customize which mailbox is used separately from the mailbox indicated by the
system.
· Voicemail Help Default = Off
For voicemail systems running IP Office mailbox mode, this option controls whether users retrieving messages are
automatically given an additional prompt "For help at any time press 8." If switched off, users can still press 8 for help.
For voicemail systems running in Intuity emulation mode, this option has no effect. On those systems the default access
greeting always includes the prompt "For help at any time, press *4" (*H in the US locale).
· Broadcast: Default = Off. Software level = 3.0+ (Voicemail Pro only).
If a voicemail message is left for the hunt group and Broadcast is enabled, copies of the message are forwarded to the
mailboxes of the individual group members. The original message in the hunt group mailbox is deleted unless it
occurred as the result of call recording.
· UMS Web Services: Default = Off. Software level = 5.0+.
This option is used with Voicemail Pro. If enabled, the hunt group mailbox can be accessed using either an IMAP email
client or a web browser. Note that the mailbox must have a voicemail code set in order to use either of the UMS
interfaces. UMS Web Service licenses are required for the number of users and groups configured.
License 378 section, double-clicking on the UMS Web Services license display a menu that allows you
· In the
to add and remove users and groups from the list of those enabled for UMS Web Services without having to open
the settings of each individual user or group.
· Voicemail Email: Default = Blank (No voicemail email features)
This field is used to set the user or group email address used by the voicemail server for voicemail email operation.
When an address is entered, the additional Voicemail Email control below are selectable to configure the type of
voicemail email service that should be provided.
Manager Manager 8.1
Manager
Page 312
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Hunt Group Settings
· Use of voicemail email requires the Voicemail Pro server to have been configured to use either a local MAPI email
client or an SMTP email server account. For embedded voicemail, voicemail email is supported with IP Office 4.2+
(except not on Small Office Edition) and uses the system's SMTP 177 settings.
· The use of voicemail email for the sending (automatic or manual) of email messages with wav files attached should
be considered with care. A one-minute message creates a 1MB .wav file.
· Voicemail Email Default = Off
If an email address is entered for the user or group, the following options become selectable. These control the mode of
automatic voicemail email operation provided by the voicemail server whenever the voicemail mailbox receives a new
voicemail message.
· Users can change their voicemail email mode using visual voice. If the voicemail server is set to IP Office
mode, user can also change their voicemail email mode through the telephone prompts. The ability to change
the voicemail email mode can also be provided in a call flow using a Play Configuration Menu action or a
Generic action.
· If the voicemail server is set to IP Office mode, users can manually forward a message to email.
· Off
If off, none of the options below are used for automatic voicemail email. Users can also select this mode by dialing
*03 from their extension.
· Copy
If this mode is selected, each time a new voicemail message is received in the voicemail mailbox, a copy of the
message is attached to an email and sent to the email address. There is no mailbox synchronization between the
email and voicemail mailboxes. For example reading and deletion of the email message does not affect the
message in the voicemail mailbox or the message waiting indication provided for that new message.
· Forward
If this mode is selected, each time a new voicemail message is received in the voicemail mailbox, that message is
attached to an email and sent to the email address. No copy of the voicemail message is retained in the voicemail
mailbox and their is no message waiting indication. As with Copy, their is no mailbox synchronization between the
email and voicemail mailboxes. Users can also select this mode by dialing *01 from their extension.
· UMS Exchange 2007 (IP Office 5.0+)
With Voicemail Pro, the system supports voicemail email to an Exchange 2007 server email account. For users
and groups also enabled for UMS Web Services this significantly changes their mailbox operation. The
Exchange Server inbox is used as their voicemail message store and features such as message waiting
indication are set by new messages in that location rather than the voicemail mailbox on the voicemail server.
Telephone access to voicemail messages, including Visual Voice access, is redirected to the Exchange 2007
mailbox.
· Alert
If this mode is selected, each time a new voicemail message is received in the voicemail mailbox, a simple email
message is sent to the email address. This is an email message announcing details of the voicemail message but
with no copy of the voicemail message attached. Users can also select this mode by dialing *02 from their
extension.
Manager Manager 8.1
Manager
Page 313
15-601011 Issue 25l (11 February 2011)
5.8.4 Fallback
Fallback settings can be used to make a hunt group unavailable and to set where the hunt group's calls should be
redirected at such times. Hunt groups can be manually placed In Service, Out of Service or in Night Service. Additionally
using a time profile, a group can be automatically placed in Night Service when outside the Time Profile settings.
Summary: Fallback redirects a hunt group's calls when the hunt group is not available, for example outside normal
working hours. It can be triggered either manually or using an associated time profile.
· Hunt Group Service States
A hunt group can be in one of three states; In Service, Out of Service and Night Service. When In service, calls are
presented as normal. In any other state calls are redirected.
· Call Redirection During Fallback
The following options are possible when a hunt group is either Out of Service or in Night Service.
· Fallback Group
If an Out of Service Fallback Group or Night Service Fallback Group has been set, calls are redirected to that group.
· Voicemail
If no fallback group has been set but voicemail is available, calls are redirected to voicemail.
· Busy Tone
If no fallback group has been set and voicemail is not available, busy tone is returned to calls.
· Manually Controlling the Service State
Manager and or short codes can be used to change the service state of a hunt group. The short code actions can also be
assigned to programmable buttons on phones.
· The
icon is used for a hunt group manually set to Night Service mode.
· The
icon is used for a hunt group manually set to Out of Service mode.
· Time Profile
A time profile can be associated with the hunt group. When outside the time profile, the hunt group is automatically
place into night service. When inside the time profile, the hunt group uses manually selected mode.
· When outside the time profile and therefore in night service, manual night service controls cannot be used to override
the night service. However the hunt group can be put into out of service.
· When a hunt group is in Night Service due to a time profile, this is not indicated within Manager.
· IP Office 4.0+: Time profile operation does not affect hunt groups set to Out of Service.
Hunt Group | Fallback
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Time Profile: Default = <None> (No automatic night service)
This field allows selection of a previously created Time Profile 360 . That profile then specifies the times at which it should
use the manually selected Service Mode settings. Outside the period defined in the time profile, the hunt group behaves
as if set to Night Service mode.
· Please note that when a hunt group is in Night Service due to it associated time profile, this is not reflected by the
Service Mode on this tab. Note also that the manual controls for changing a hunt group's service mode cannot be
used to take a hunt group out of time profile night service.
· Out of Service Fallback Group: Default = <None> (Voicemail or Busy Tone)
This field sets the alternate hunt group destination for calls when this hunt group is in Out of Service mode. If left blank,
calls are redirected to voicemail if available or otherwise receive busy tone.
· Night Service Fallback Group: Default = <None> (Voicemail or Busy Tone)
This field sets the alternate hunt group destination for calls when this hunt group is in Night Service mode. If left blank,
calls are redirected to voicemail if available or otherwise receive busy tone.
· Service Mode: Default = In Service
This field is used to manually select the current service mode for the hunt group.
Manager Manager 8.1
Manager
Page 314
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Hunt Group Settings
·
Out of Service
When selected, calls are redirected using the Out of Service Fallback Group setting. This setting can also be
manually controlled using the short code and button programming features Set Hunt Group Out of Service and Clear
Hunt Group Out of Service.
·
or
: In Service
When selected the hunt group is enabled. This is the default mode.
·
Night Service
When selected, calls are redirected using the Night Service Fallback Group setting. This setting can also be
manually controlled using the short code and button programming features Set Hunt Group Night Service and Clear
Hunt Group Night Service.
Hunt Group Fallback Controls
Hunt Group Fallback
Manager
Hunt group fallback selection is done through the Hunt Group | Fallback
314
tab.
A time profile if required is set through the Time Profile | Time Profile tab.
Controls
The following short code features/button programming actions can be used:
Short Code
Feature/Action
Set Hunt Group Night Service
Clear Hunt Group Night Service
Set Hunt Group Out of Service
Default
*20*N#
493
453
- Toggles.
*21*N#
- Toggles.
493
Clear Hunt Group Out of Service
Button
453
Note that for a hunt group using a time profile, these controls only are only applied when the hunt group is
within the specified time profile period. When outside its time profile, the hunt group is in night service
mode and cannot be overridden.
Phone
Manager
There are no specific controls for the operation of hunt group fallback.
SoftConsole There are no specific controls for the operation of hunt group fallback.
Voicemail
There are no specific controls for the operation of hunt group fallback.
Manager Manager 8.1
Manager
Page 315
15-601011 Issue 25l (11 February 2011)
5.8.5 Queuing
When is a Call Queued
The definition of when a call is in a queue can vary:
· Pre-IP Office 4.0: Calls to a hunt group were only queued when the number of calls waiting exceeded the number of
available hunt group members that could be ringing. Using that definition, calls that were actually ringing were not
regarded as queued.
· IP Office 4.0+: Any calls waiting to be answered at a hunt group are regarded as being queued. The Normalise
Queue Length control allows selection of whether features that are triggered by the queue length should include or
exclude ringing calls.
· Additional Calls
Once one call is queued, any further calls are also queued. When an available hunt group member becomes idle, the
first call in the queue is presented.
· How Many Calls Can be Queued?
Calls are added to the queue until the hunt group's Queue Limit, if set, is reached.
· When the queue limit is reached, any further calls are redirected to the hunt group's voicemail if available.
· If voicemail is not available excess calls receive busy tone. An exception to this are analog trunk and T1 CAS trunk
calls which will remain queued regardless of the queue limit if no alternate destination is available.
· If an existing queued call is displaced by a higher priority call, the displaced call will remain queued even if it now
exceeds the queue limit.
· Queue Announcements
The method of hunt group announcements depends on the system software level:
· Pre-IP Office 4.0: Systems with Voicemail Pro or Voicemail Lite, announcements are applied to queued calls.
· IP Office 4.0+: Hunt group announcements are separate from queuing. Announcements can be used even if queuing
is turned off and are applied to ringing and queued calls. See Hunt Group | Announcements 320 .
· Queue Monitoring
There are several methods of displaying a hunt group queue.
· Group Button
On phones, with programmable buttons, the Group function can be assigned to monitor a specified group. The
button indicates when there are calls ringing within the group and also when there are calls queued. The button can
be used to answer the longest waiting call.
· Phone Manager and SoftConsole
Both these applications can display queue monitors for selected hunt groups, 2 using Phone Manager, 7 using
SoftConsole. This requires the hunt group to have queuing enabled. These queues can be used to answer calls.
· What Happens When A Hunt Group Members Becomes Available
When a hunt group member becomes available, the first call in the queue is presented to that member. If several
members become available, the first call in the queue is simultaneously presented to all the free members.
· Overflow Calls
Calls that overflow are counted in the queue of the original hunt group from which they overflow and not that of the
hunt group to which they overflow. This affects the Queue Limit and Calls in Queue Threshold.
Settings
Hunt Group | Queuing
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Queuing On: Default = On
This settings allows calls to this hunt group to be queued. The normal
icon is replaced
.
· Queue Limit: Default = No Limit. Range = No Limit, 1 to 999 calls.
This setting can be used to limit the number of calls that can be queued. Calls exceeding this limit are passed to
voicemail if available or otherwise receive busy tone. This value is affected by Normalize Queue Length setting.
Manager Manager 8.1
Manager
Page 316
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Hunt Group Settings
· If voicemail is not available excess calls receive busy tone. An exception to this is analog trunk and T1 CAS trunk calls
which will remain queued regardless of the queue limit if no alternate destination is available. This is due to the
limited call status signalling supported by those trunks which would otherwise create scenarios where the caller has
received ringing from the local line provider and then suddenly gets busy from the system, creating the impression
that the call was answered and then hung up.
· If priority is being used with incoming call routes, high priority calls are place ahead of lower priority calls. If this
would exceed the queue limit the limit is temporarily increased by 1.
· If an existing queued call is displaced by a higher priority call, the displaced call will remain queued even if it now
exceeds the queue limit.
· Normalize Queue Length: Default = Off. Software level = 4.0+.
Pre-IP Office 4.0: The call queue only included calls waiting to ring and did not include calls actually ringing. IP Office
4.0+: Calls both waiting to ring and ringing are regarded as being queued. This therefore affects the use of the Queue
Limit and Calls in Queue Alarm thresholds. If Normalize Queue Length is enabled, the number of hunt group
members logged in and not on DND is added to those thresholds.
· Example: A customer has two products that it is selling through a call center with 10 available agents; one product
with a $10 margin and one with a $100 margin. Separate hunt groups with the same 10 members are created for
each product.
· The $100 product has a Queue Limit of 5 and Normalize Queue Length is on. The maximum number of $100 calls
that can be waiting to be answered will be 15 (10 ringing/connected + 5 waiting to ring).
· The $10 product has a Queue Limit of 5 and Normalize Queue Length is off. The maximum number of $10 calls that
can be waiting to be answered is 5 (5 ringing/connected).
· Queue Type: Default = Assign Call On Agent Answer. Software level = 4.2+.
When queuing is being used, the call that the agent receives when they answer can be assigned in one of two ways:
· Assign Call On Agent Answer
In this mode the call answered by the hunt group member will always be the longest waiting call of the highest
priority. The same call will be shown on all ringing phones in the group. At the moment of answering that may not
necessarily be the same call as was shown by the call details at the start of ringing. This is the default mode for IP
Office 4.0+.
· Assign Call on Agent Alert
In this mode, once a call has been presented to a hunt group member, that is the call they will answer if they go off
hook. This is similar to the method used for IP Office 3.2 and earlier. This mode should be used when calls are
being presented to applications which use the call details such as a fax server, CTI or TAPI.
· Queue Ring Time (secs): Default = 10 seconds. Range = 0 to 99999 seconds. Software level = Up to 3.2 only.
On systems with Voicemail Lite (pre-IP Office 5 only) or Voicemail Pro, the voicemail system can provide
announcements to queued callers. This setting controls the time before the first queued announcement is played to a
queued caller. For IP Office 4.0+ this has been replaced by the Hunt Group | Announcement 320 tab controls.
· Calls In Queue Alarm: Software Level = 4.1+.
The system can be set to send an alert to a specified extension when the number of calls queued for the hunt group
reaches the specified threshold.
· Calls In Queue Threshold: Default = Off. Range = 1 to 99. Software level = 4.1+.
Alerting is triggered when the number of queued calls reaches this threshold. Alerting will stop only when the number
of queued calls drops back below this threshold. This value is affected by Normalize Queue Length setting above.
· Analog Extension to Notify: Default = <None>. Software Level = 4.1+.
This should be set to the extension number of a user associated with an analog extension. The intention is that this
analog extension port should be connected to a loud ringer or other alerting device and so is not used for making or
receiving calls. The list will only shown analog extensions that are not members of any hunt group or the queuing
alarm target for any other hunt group queue. The alert does not follow user settings such as forwarding, follow me,
DND, call coverage, etc or receive ICLID information.
Hunt Group Queue Settings
Manager
Hunt group queuing is enabled using the Queuing On option on the Hunt Group | Queuing
enabled, the
Controls
316
tab. When
icon is used for the hunt group.
The following short code features/button programming actions can be used:
Feature/Action
Short Code
Default
Button
Group
Phone
Manager
Phone manager Pro can be used to monitor up to two hunt group queues. This is configured by clicking
and then on the Queue ID tab selecting the two hunt groups. During normal operation the Phone Manager
user then has access to a Queue tab which is automatically given focus when calls become queued.
Manager Manager 8.1
Manager
Page 317
15-601011 Issue 25l (11 February 2011)
SoftConsole
SoftConsole can display up to 7 hunt group queues (an eight queue is reserved for recall calls). They are
configured by clicking
and selecting the Queue Mode tab. For each queue alarm threshold can be set
based on number of queued calls and longest queued call time. Actions can then be selected for when a
queue exceeds its alarm threshold; Automatically Restore SoftConsole, Ask me whether to restore
SoftConsole or Ignore the Alarm.
Within the displayed queues, the number of queued calls is indicated and the time of the longest queued
call is shown. Exceeding an alarm threshold is indicated by the queue icons changing from white to red.
The longest waiting call in a queue can be answered by clicking on the adjacent button.
Manager Manager 8.1
Manager
Page 318
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Hunt Group Settings
5.8.6 Voice Recording
This tab is used to configure automatic recording of external calls handled by hunt group members. IP Office 6.1: The
recording of internal calls as well is also supported.
Call recording requires Voicemail Pro to be installed and running. Call recording also requires available conference
resources similar to a 3-way conference.
· IP Office 4.0+ introduces the following changes to recording:
· Calls to and from IP devices, including those using Direct media, can be recorded.
· Calls parked or held pause recording until the unparked or taken off hold.
· Recording is stopped if:
· User recording stops if the call is transferred to another user.
· User account code recording stops if the call is transferred to another user.
· Hunt group recording stops if the call is transferred to another user who is not a member of the hunt
group.
· Incoming call route recording continues for the duration of the call on the system.
· IP Office 4.1+: A destination mailbox other than the hunt group's own mailbox can be specified as the destination
for recordings.
Hunt Group | Voice Recording
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Record Inbound: Default = None
Select whether automatic recording of incoming calls is enabled. Options for recording are:
· None: Do not automatically record calls.
· On: Record the call if possible. If not possible to record, allow the call to continue.
· Mandatory: Record the call if possible. If not possible to record, block the call and return busy tone.
· Percentages of calls: Record a selected percentages of the calls.
· Record Time Profile: Default = <None> (Any time)
Used to select a time profile 360 during which automatic call recording of incoming calls is applied. If no profile is
selected, automatic recording of incoming calls is active at all times.
· Recording (Auto): Default = Mailbox
Sets the destination for automatically triggered recordings.
· Mailbox
This option sets the destination for the recording to be a selected user or hunt group mailbox. The adjacent drop
down list is used to select the mailbox.
· Voice Recording Library: Software level = 3.0+.
This options set the destination for the recording to be a VRL folder on the voicemail server. The ContactStore
application polls that folder and collects waiting recordings which it then places in its own archive. Recording is still
done by the Voicemail Pro.
· Auto Record Calls: Default = External. Software level = 6.1
This setting allows selection of whether External or External & Internal calls are subject to automatic call recording.
Manager Manager 8.1
Manager
Page 319
15-601011 Issue 25l (11 February 2011)
5.8.7 Announcements
This tab is new for IP Office 4.0 and higher. Unlike pre-4.0 systems, this method of using announcements is independent
of hunt group queuing.
Announcements are played to callers waiting to be answered. This includes callers being presented to hunt group
members, ie. ringing, and callers queued for presentation.
· The system supports announcements using Voicemail Pro, Voicemail Lite (pre-5.0 only) or Embedded Voicemail.
· If no voicemail channel is available for an announcement, the announcement is not played.
· In conjunction with Voicemail Pro, the system allows a number of voicemail channels to be reserved for
announcements. See System | Voicemail 157 .
· With Voicemail Pro, the announcement can be replaced by the action specified in a Queued (1st announcement) or
Still Queued (2nd announcement) start point call flow. Refer to the Voicemail Pro Installation and Maintenance
documentation for details.
· Calls can be answered during the announcement. If it is a mandatory requirement that announcements should be
heard before a call is answered, then a Voicemail Pro call flow should be used before the call is presented.
· Warning: Call Billing and Logging
Note that a call becomes connected when the first announcement is played to it. That connected state is
signaled to the call provider who may start billing at that point. The call will also be recorded as answered
within the SMDR 898 output once the first announcement is played.
· If a call is rerouted to a hunt group's Night Service Group or Out of Service Fallback Group, the announcements of
the new group are applied.
· If a call overflows, the announcements of the original group are still applied, not those of the overflow group.
· For announcements to be used effectively, the hunt group's Voicemail Answer Time must be extended or
Voicemail On must be unselected.
Recording the Hunt Group Announcement
Voicemail Pro provides the default announcement "I'm afraid all the operators are busy but please hold and you will be
transferred when somebody becomes available". This default is used for announcement 1 and announcement 2 if no
specific hunt group announcement has been recorded. Embedded Voicemail does not provide any default announcement.
Voicemail Lite also provides the default announcements.
The maximum length for announcements is 10 minutes. New announcements can be recorded using the following
methods:
· Voicemail Lite
Access the hunt group mailbox and press 3. Then press either 3 to record the 1st announcement for the hunt group
or 4 to record the 2nd announcement for the hunt group.
· Voicemail Pro - IP Office Mode
Access the hunt group mailbox and press 3. Then press either 3 to record the 1st announcement for the hunt group
or 4 to record the 2nd announcement for the hunt group.
· Voicemail Pro - Intuity Emulation Mode
There is no mechanism within the Intuity telephony user interface (TUI) to record hunt group announcements. To
provide custom announcements, hunt group queued and still queued start points must be configured with Voicemail
Pro with the required prompts played by a generic action.
· Embedded Voicemail
Embedded Voicemail does not include any default announcement or method for recording an announcement. The
Record Message 486 short code feature is provided to allow the recording of announcements. The telephone
number field of short codes using this feature requires the extension number followed by either ".1" for
announcement 1 or ".2" for announcement 2. For example, for extension number 300, the short codes *91N# |
Record Message | N".1" and *92N# | Record Message | N".2" could be used to allow recording of the
announcements by dialing *91300# and *92300#.
Manager Manager 8.1
Manager
Page 320
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Hunt Group Settings
Hunt Group | Announcements
Control Unit
SOE
Software Level
4.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Announcements On: Default = Off.
This setting enables or disables announcements.
· Wait before 1st announcement: Default = 10 seconds. Range = 0 to 9999 seconds.
This setting sets the time delay from the calls presentation, after which the first announcement should be played to the
caller. If Synchronize Calls is selected, the actual wait may differ, see below.
· Flag call as answered: Default = Off.
This setting is used by the CCC and CBC applications. By default they do not regarded a call as answered until it has
been answered by a person or by a Voicemail Pro action with Flag call as answered selected. This setting allows calls
to be marked as answered once the caller has heard the first announcement. This setting is not used by the Customer
Call Reporter application.
· Warning: Call Billing and Logging
Note that a call becomes connected when the first announcement is played to it. That connected state is
signaled to the call provider who may start billing at that point. The call will also be recorded as answered
within the SMDR 898 output once the first announcement is played.
· Post announcement tone: Default = Music on hold.
Following the first announcement, you can select whether the caller should hear Music on Hold
Silence until answered or played another announcement.
763 ,
Ringing or
· 2nd Announcement: Default = On.
If selected, a second announcement can be played to the caller if they have still not been answered.
· Wait before 2nd announcement: Default = 20 seconds. Range = 0 to 9999 seconds.
This setting sets the wait between the 1st and the 2nd announcement. If Synchronize Calls is selected, the actual wait
may differ, see below.
· Repeat last announcement: Default = On.
If selected, the last announcement played to the caller is repeated until they are answered or hang-up.
· Wait before repeat: Default = 20 seconds. Range = 0 to 9999 seconds.
If Repeat last announcement is selected, this setting sets is applied between each repeat of the last announcement.
If Synchronize Calls is selected, this value is grayed out and set to match the Wait before 2nd announcement
setting.
· Synchronize calls: Default = Off
This option can be used to restrict how many voicemail channels are required to provide the announcements.
· Off
When Synchronize calls is off, announcement are played individually for each call. This requires a separate voicemail
channel each time an announcement is played to each caller. While this ensures accurate following of the wait
settings selected, it does not make efficient use of voicemail channels.
· On
When Synchronize calls is on, if a required announcement is already being played to another caller, further callers
wait until the announcement been completed and can be restarted. In addition, when a caller has waited for the set
wait period and the announcement is started, any other callers waiting for the same announcement hear it even if
they have not waited for the wait period. Using this setting, the maximum number of voicemail channels ever needed
is 1 or 2 depending on the number of selected announcements.
· Note: Interaction with Voicemail Pro Queued and Still Queued Start Points
If either custom Queued or Still Queued start point call flows are being used for the announcements, when
Synchronize Calls is enabled those call flows will support the playing of prompts only. Voicemail Pro actions such
as Speak ETA, Speak Position, Menu, Leave Mail, Transfer and Assisted Transfer, etc. are not supported.
Manager Manager 8.1
Manager
Page 321
15-601011 Issue 25l (11 February 2011)
5.8.8 SIP
Each hunt group can be configured with its own SIP URI information. For calls received on a SIP line where any of the
line's SIP URI fields are set to Use Internal Data, if the call is presented to the hunt group that data is taken from these
settings.
This form is hidden if there are no system SCN lines in the configuration or no SIP lines with a URI set to Use Internal
Data.
Hunt Group | Voice Recording
Control Unit
SOE
Software Level
6.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· SIP Name: Default = User name.
The value from this field is used when the From field of the SIP URI being used for a SIP call is set to Use Internal
Data.
· SIP Display Name (Alias): Default = User name.
The value from this field is used when the Display Name field of the SIP URI being used for a SIP call is set to Use
Internal Data.
· Contact: Default = User name.
The value from this field is used when the Contact field of the SIP URI being used for a SIP call is set to Use Internal
Data.
· Anonymous: Default = Off.
If the From field in the SIP URI is set to Use Internal Data, selecting this option inserts Anonymous into that field
rather than the SIP Name set above.
Manager Manager 8.1
Manager
Page 322
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Hunt Group Settings
5.8.9 Hunt Group Operation
5.8.9.1 Hunt Types
At its most basic, a hunt groups settings consist of a hunt group name, an extension number, a list of hunt group
members and a hunt type selection. It is the last two settings which determine the order in which incoming calls are
presented to hunt group members.
The available hunt types are; Collective, Sequential, Rotary and Longest Waiting. These work are follows:
Collective Group (formerly Group Group)
An incoming call is presented
simultaneously to all the available hunt
group members.
Sequential Group (formerly Hunt or Linear Group)
An incoming call is presented to the first
available member in the list. If
unanswered, it is presented to the next
available member in the list.
The next incoming call uses the same
order. It is presented to the available
members starting again from the top of
the list.
Rotary Hunt Type (formerly Circular Group)
This hunt type operates similarly to
Sequential. However the starting point
for call presentation is the first available
member after the last member to answer
a call.
Longest Waiting Hunt Type (formerly Idle or Most Idle)
This hunt type does not present calls to hunt group members in the order that they are listed. It presents calls using the
order of how long the available hunt group members have been idle.
An incoming call is first presented to the available member who has been idle the longest. If unanswered it is presented
to the next longest idle member.
· IP Office 4.2+: Where hunt group calls are being presented to a twinned extension, the longest waiting status of the
user can be reset by calls answered at either their master or twinned extension.
Manager Manager 8.1
Manager
Page 323
15-601011 Issue 25l (11 February 2011)
5.8.9.2 Call Presentation
Summary: Calls are presented to each available hunt group member in turn. If having been presented to all the available
members, none answers, the call is redirected to voicemail if available, otherwise it continues to be presented to the next
available member.
In addition to the summary, options exist to have calls queued or to have calls redirected to overflow groups.
· First and Next Available Members
The first available member to which a call is presented and the order of the next available members to which a call is
presented are determined by the hunt group's Hunt Type 323 setting.
· Additional Calls
When additional calls are waiting to be presented, additional available hunt group members are alerted using the hunt
group type. The way additional calls are presented if there are available members depends on the system software
level.
· Pre-IP Office 4.0
Additional calls ring around the group separately. This means that additional calls may be answered ahead of the
first call.
· IP Office 4.0 and Higher
When any member answers a call it will be the first waiting call that is answered.
· No Available Members
If the number of incoming calls exceeds the number of available members to which calls can be presented, the following
actions are usable in order of precedence.
· Queuing
If queuing has been enabled for the hunt, it is applied to the excess calls up to the limits specified for the number
of queued calls or length of time queued.
· Voicemail
If voicemail has been enabled for the hunt group, excess calls are directed to voicemail.
· Busy Tone
Busy tone is returned to the excess calls (except analog and T1 CAS calls which remain queued).
· No Answer Time
This value is used to determine how long a call should ring at a hunt group member before being presented to the next
available hunt group member. The System | Telephony | Telephony | No Answer Time setting is used unless a
specific Hunt | Hunt Group | No Answer Time is set.
· Voicemail
If voicemail is being used, if having been presented to all the available group members the call is still not answered then
it goes to voicemail.
· IP Office 4.0+: The call will also go to voicemail when the hunt group's Voicemail Answer Time is exceeded. the
mailbox of the originally targeted hunt group is used even if the call has overflowed or gone to a night server hunt
group.
· Pre-IP Office 4.0: When voicemail was invoked, the mailbox of whichever hunt group was currently handling the call
was used, for example the mailbox of the overflow or night service hunt group might be used if the call had gone
from the original hunt group to an overflow or night server hunt group.
· Calls Not Being Answered Quick Enough - Overflow
In addition to ringing at each available member for the No Answer Time, a separate Overflow Time can be set. When a
calls total ring time against the group exceeds this, the call can be redirected to an overflow group or groups.
· No Available Member Answers
If a call has been presented unanswered to all the available members, either of two actions can be applied. If voicemail
is available, the call is redirected to voicemail. If otherwise, the call will continue being presented to hunt group
members until answered or, if set, overflow is used.
· Call Waiting
For hunt groups using the Group hunt type, call waiting can be used.
Manager Manager 8.1
Manager
Page 324
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Hunt Group Settings
5.8.9.3 Member Availability
Summary: Details when a hunt group member is seen as being available to be presented a hunt group call.
The Hunt Group settings within Manager list those users who are members of the hunt group and therefore may receive
calls directed to that hunt group. However there are a range of factors that can affect whether a particular hunt group
member is available to take hunt group calls at any time.
· Existing Connected Call
Users with an existing connected call are not available to further hunt group calls. This is regardless of the type of
connected call, whether the user has available call appearance buttons or is using call waiting.
· Hunt Group Call Waiting
For Collective hunt groups call waiting can be enabled using the Ring Type of Collective Call Waiting.
· Logged In/Logged Out
The system allows user's to log in and out extensions, a process known as 'hot desking'. Whilst a user is logged out they
are not available to receive hunt group calls.
· IP Office 4.2+: Mobile Twinning users with both Hunt group calls eligible for mobile twinning and Twin when
logged out selected will still receive hunt group calls unless they switch off twinning.
· Membership Enabled/Disabled
The system provides controls to temporarily disable a users' membership of a hunt group. Whilst disabled, the user is
not available to receive calls directed to that hunt group.
· Do Not Disturb
This function is used by users to indicate that they do not want to receive any calls. This includes hunt group calls. In
call center environments this state is also known as 'Busy Not Available'. See Do Not Disturb 769 .
· Busy on Held
When a user has a held call, they can receive other calls including hunt group calls. The Busy on Held settings can be
used to indicate that the user is not available to further calls when they have a held call.
· Forward Unconditional
Users set to Forward Unconditional are by default not available to hunt group calls. The system allows the forwarding of
hunt group calls to be selected as an option.
· Idle /Off Hook
The hunt group member must be idle in order to receive hunt group call ringing.
· No Available Members
If queuing has been enabled, calls will be queued. If queuing has not been enabled, calls will go to the overflow group if
set, even if the overflow time is not set or is set to 0. If queuing is not enabled and no overflow is set, calls will go to
voicemail. If voicemail is not available, external calls go to the incoming call routes fallback destination while internal
calls receive busy indication.
Manager Manager 8.1
Manager
Page 325
15-601011 Issue 25l (11 February 2011)
Hunt Group Member Availability Settings
Manager
Forwarding and do not disturb controls for a user are found on the User | Forwarding
270 tabs.
281
and User | DND
Enabling and disabling a users hunt group membership is done by ticking or unticking the user entry in
the hunt group's extensions list on the Hunt Group | Hunt Group 306 tab.
Controls
The following short code features/button programming actions can be used:
Short Code
Feature/Action
Hunt Group Enable
Hunt Group Disable
Button
HGEna - Toggles.
HGDis
480
Forward Hunt Group On
472
-*50
FwDH+ - Toggles
Forward Hunt Group Off
472
-*51
FwDH-
Busy on Held
BusyH
441
Do Not Disturb On
466
-*08
DNDOn - Toggles
Do Not Disturb Off
466
-*09
DNDOf
Extn Login
468
Extn Logout
Phone
Manager
Default
480
468
-*35*N#
Login
-*36
Logof
DND, Forwarding and Busy on Held can all be controlled through Phone Manager. They are accessed by
and then selecting the Do Not Disturb, Forwarding or Telephone tabs respectively.
clicking
Phone Manager Pro users can select agent mode by clicking , selecting the Agent Mode tab and
selecting Agent Mode. In this mode, Phone Manager provides icons for Busy Wrap Up (Hunt group disable)
and Busy Not Available (DND). It also allows individual selection of which group memberships are enabled.
Phone Manager can also be used to log in and log out when the application is started or stopped.
SoftConsole
A SoftConsole user can view and edit a user's settings. Through the directory, select the required user.
Their current status including DND, Logged In and hunt group membership states are shown and can be
changed. Forwarding settings can be accessed by then selecting Forwarding.
Manager Manager 8.1
Manager
Page 326
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Hunt Group Settings
5.8.9.4 Example Hunt Group
The follow are simple examples of how a department might use the facilities of a hunt group.
1. Basic Hunt Group
Scenario
The Sales department want all sales related calls to be presented first to Jane, then Peter and finally Anne.
Actions
1. Create a hunt group named Sales and assign it an extension number.
2. Set the Hunt Type to Sequential.
3. Add Jane, Peter and Ann to the User List in that order.
4. Turn off queuing on the Queuing tab and voicemail on the Voicemail tab.
5. Route relevant calls to the Sales group by selecting it as the destination in the appropriate Incoming Call
Routes.
Results
Any call received by the Sales hunt group is first presented to Jane if she is available. If Jane is not available
or does not answer within 15 seconds the call is presented to Peter. If Peter is not available or does not
answer within 15 seconds the call goes Anne. Since voicemail is not on, the call will continue to be
presented around the group members in that order until it is answered or the callers hangs up.
2. Adding Voicemail Support
Scenario
A voicemail server has now been added to the system. The Sales department wants to use it to take
messages from unanswered callers. When messages are left, they want Jane to receive message waiting
indication.
Actions
1. Open the Sales hunt group settings and select Voicemail On on the Voicemail tab.
2. Select the User settings for Jane. On the Source Numbers tab, add the entry HSales.
Results
Once a call to the Sales group has been presented to all the available members, if it is still unanswered then
the call will be redirected to the group's voicemail mailbox to leave a message. When a message has been
left, the message waiting indication lamp on Jane's phone is lit.
3. Using the Queuing Facility
Scenario
The Sales department now wants calls queued when no one is available to answer. However if the number
of queued calls exceeds 3 they then want any further callers directed to voicemail.
Actions
1. Open the Sales hunt group settings and select Queuing On on the Queuing tab.
2. Set the Queue Limit to 3.
Results
When the Sales group are all on calls or ringing, any further calls to the group are queued and receive
queuing announcements from the voicemail server. When the number of queued calls exceeds 3, any further
calls are routed to the group's voicemail mailbox.
4. Using Out of Service Fallback
Scenario
During team meetings, the Sales department want their calls redirected to another group, for this example
Support.
Actions
1. Open the Sales hunt group settings and select the Fallback tab. In the Out of Service Fallback Group field
select the Support group.
2. Create a system short code *98 / 300 / Set Hunt Group Out of Service.
3. Create a system short code *99 / 300 / Clear Hunt Group Out of Service.
Results
Prior to team meetings, dialing *98 puts the Sales group into out of service mode. Its calls are then
redirected to the Support group. Following the meeting, dialing *99 puts the Sales group back In Service.
Manager Manager 8.1
Manager
Page 327
15-601011 Issue 25l (11 February 2011)
5. Using a Night Service Time Profile
Scenario
Outside their normal business hours the Sales department want their group calls automatically sent to
voicemail. This can be done using a time profile and leaving the Night Service Fallback Group setting blank.
Actions
1. Create a Time Profile called Sales Hours and in it enter the time during which the Sales department are
normally available.
2. Open the Sales hunt group settings and select the Fallback tab.
3. In the Time Profile field select Sales Hours.
Results
Outside the normal business hours set in the time profile, the Sales hunt group is automatically put into
Night Service mode. Since no Night Service Fallback Group has been set, calls are redirected to voicemail.
Manager Manager 8.1
Manager
Page 328
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Hunt Group Settings
5.8.9.5 CBC/CCC Agents and Hunt Groups
The use of and reporting on hunt groups is a key feature of call center operation. For Manager, reporting is provided
through the Compact Business Center (CBC) or Compact Contact Center (CCC) applications.
In order for these applications to provide hunt group and hunt group user (agent) reports, the following rules apply:
· The hunt group names must be restricted to a maximum of 12 characters.
· The hunt group and user extension numbers should be a maximum of 4 digits.
· Hunt group members should be given a Login Code and set to Force Login.
· The agent state Busy Not Available is equivalent to Do Not Disturb. The agent state Busy Wrap Up is equivalent to
hunt group disable.
Manager Manager 8.1
Manager
Page 329
15-601011 Issue 25l (11 February 2011)
5.9 Short Code
This form is used to create System Short Codes. System short codes can be dialed by all system users.
However the system short code is ignored if the user dialing matches a user or user rights short code. For full
details on short code usage and parameter see the section Short Codes 426 .
Short Code | Short Code
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Short Code 427
The dialing digits used to trigger the short code. Maximum length 31 characters.
· Telephone Number 427
The number dialed by the short code or parameters for the short code feature. This field can contain numbers and
characters. For example, it can contain Voicemail Pro start point names, user names, hunt group names and telephone
numbers (including those with special characters). Maximum length 31 characters.
· Dialing Complete
The majority of North-American telephony services use 'en-bloc' dialing, ie. they expect to receive all the routing
digits for a call as a single simultaneous set of digits. Therefore the use of a ; is recommended at the end of all dialing
short codes that use an N. This is also recommended for all dialing where secondary dial tone short codes are being
used.
· Line Group ID: Default = 0
For short codes that result in the dialing of a number, that is short codes with a Dial feature, this field is used to enter
the initially routing destination of the call. The drop down can be used to select the following from the displayed list:
· Outgoing Group ID
The Outgoing Group ID's current setup within the system configuration are listed. If an Outgoing Group ID is
selected, the call will be routed to the first available line or channel within that group.
· ARS (IP Office 4.0+)
The ARS entries currently configured in the system are listed. If an ARS entry is selected, the call will be routed by
the setting within that ARS entry. Refer to ARS Overview 407 .
· Feature 439
Select the action to be performed by the short code.
· Locale 844 : Default = Blank
For short codes that route calls to voicemail, this field can be used to set the prompts locale that should be used if
available on the voicemail server.
· When the system routes a call to the voicemail server it indicates the locale for which matching prompts should be
provided if available. The locale sent to the voicemail server by the system is determined as follows:
Locale Source
Usage
Short Code
The short code locale, if set, is used if the call is routed to voicemail using the short
code.
System
If no user or incoming call route locale is set system locale is used unless overridden by
a short code locale.
Incoming Call Route
The incoming call route locale, if set, is used if caller is external.
User
The user locale, if set, is used if the caller is internal.
· Force Account Code: 375 Default = Off.
For short codes that result in the dialing of a number, this field trigger the user being prompted to enter a valid account
code before the call is allowed to continue.
· Force Authorization Code 404 : Default = Off
This option is only shown on systems where authorization codes have been enabled. If selected, then for short codes
that result in the dialing of a number, the user is required to enter a valid authorization code in order to continue the
call.
Manager Manager 8.1
Manager
Page 330
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Short Code
5.10 Service Settings
Services are used to configure the settings required when a user or device on the LAN needs to connect to a
off-switch data service such as the Internet or another network. Services can be used when making data
connections via trunk or WAN interfaces.
Once a service is created, it can be used as the destination for an IP Route entry. One service can also be set
as the Default Service. That service will then be used for any data traffic received by the system for which no
IP Route is specified.
The system supports three types of service:
·
Normal Service
This type of service should be selected when for example, connecting to an ISP.
·
WAN Service
This type of service is used when creating a WAN link. A User and RAS Service will also be created with the same
name. These three entries are automatically linked and each open the same form. Note however, that this type of
Service cannot be used if the Encrypted Password option is checked. In this case the RAS Service name must match
the Account Name. Therefore either create each entry manually or create an Intranet Service.
·
Intranet Service
This type of service can be selected to automatically create a User with the same name at the same time. These
two entries are linked and will each open the same form. The User's password is entered in the Incoming Password
field at the bottom on the Service tab. An Intranet Services shares the same configuration tabs as those available
to the WAN Service.
Manager Manager 8.1
Manager
Page 331
15-601011 Issue 25l (11 February 2011)
5.10.1 Service
Service | Service
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Name
The name of the service. It is recommended that only alphanumeric characters be used.
· Account Name
The User Name that is used to authenticate the connection. This is provided by the ISP or remote system.
· Password: Default = Blank
Enter the password that is used to authenticate the connection. This is provided by the ISP or remote system.
· Telephone Number: Default = Blank
If the connection is to be made via ISDN enter the telephone number to be dialed. This is provided by the ISP or remote
system.
· Firewall Profile: Default = Internet01 if present, otherwise <None>
From the list box select the Firewall Profile that is used to allow/disallow protocols through this Service.
· Encrypted Password: Default = Off
When enabled the password is authenticated via CHAP (this must also be supported at the remote end). If disabled, PAP
is used as the authentication method.
· Default Route: Default = Off
When enabled this Service is the default route for data packets unless a blank IP Route has been defined in the system
IP Routes 367 . A green arrow appears to the left of the Service in the Configuration Tree. Only one Service can be the
default route. If disabled, a route must be created under IP Route.
· Incoming Password: Default = Blank
Shown on WAN and Intranet services. Enter the password that will be used to authenticate the connection from the
remote Control Unit. (If this field has appeared because you have created a Service and User of the same name, this is
the password you entered in the User's Password field).
Manager Manager 8.1
Manager
Page 332
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Service Settings
5.10.2 Bandwidth
These options give the ability to make ISDN calls between sites only when there is data to be sent or sufficient data to
warrant an additional call. The calls are made automatically without the users being aware of when calls begin or end.
Using ISDN it is possible to establish a data call and be passing data in less that a second. Note: the system will check
Minimum Call Time first, then Idle Period, then the Active Idle Period.
Service | Bandwidth
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Minimum No of Channels: Default = 1. Range = 1 to 30.
Defines the number of channels used to connect for an outgoing connection. The initial channel must be established and
stable, before further calls are made.
· Maximum No of Channels: Default = 1. Range = 1 to 30.
Defines the maximum number of channels to can be used. This field should contain a value equal to or greater than the
Minimum Channels field.
· Extra BW Threshold: Default = 50%. Range = 0 to 100%.
Defines the utilization threshold at which extra channels are connected. The value entered is a %. The % utilization is
calculated over the total number of channels in use at any time, which may be one, two etc.
· For example, if Minimum Channels set to 1, Maximum Channels set to 2 and Extra Bandwidth set to 50 - once
50% of first channel has been used the second channel is connected.
· Reduce BW Threshold: Default = 10%. Range = 0 to 100%.
Defines the utilization threshold at which additional channels are disconnected. The value entered is a %. Additional
calls are only dropped when the % utilization, calculated over the total number of channels in use, falls below the %
value set for a time period defined by the Service-Idle Time. The last call (calls - if Minimum Calls is greater than 1) to
the Service is only dropped if the % utilization falls to 0, for a time period defined by the Service-Idle Time. Only used
when 2 or more channels are set above.
· For example, if Minimum Channels set to 1, Maximum Channels set to 2 and Reduce Bandwidth is set to 10 - once the
usage of the 2 channels drops to 10% the number of channels used is 1.
· Callback Telephone Number: Default = Blank
The number that is given to the remote service, via BAP, which the remote Control Unit then dials to allow the
bandwidth to be increased. Incoming Call routing and RAS Services must be appropriately configured.
· Idle Period (secs): Default = 10 seconds. Range = 0 to 999999 seconds.
The time period, in seconds, required to expire after the line has gone idle. At this point the call is considered inactive
and is completely closed.
· For example, the 'Idle Period' is set to X seconds. X seconds before the 'Active Idle Period' timeouts the Control Unit
checks the packets being transmitted/received, if there is nothing then at the end of the 'Active Idle Period' the
session is closed & the line is dropped. If there are some packets being transmitted or received then the line stays up.
After the 'Active Idle Period' has timed out the system performs the same check every X seconds, until there are no
packets being transferred and the session is closed and the line dropped.
· Active Idle Period (secs): Default = 180 seconds. Range = 0 to 999999 seconds.
Sets the time period during which time the line has gone idle but there are still active sessions in progress (for example
an FTP is in process, but not actually passing data at the moment). Only after this timeout will call be dropped.
· For example, you are downloading a file from your PC and for some reason the other end has stopped responding,
(the remote site may have a problem etc.) the line is idle, not down, no data is being transmitted/ received but the
file download session is still active. After the set time period of being in this state the line will drop and the sessions
close. You may receive a remote server timeout error on your PC in the Browser/FTP client you were using.
· Minimum Call Time (secs): Default = 60 seconds. Range = 0 to 999999 seconds.
Sets the minimum time that a call is held up after initial connection. This is useful if you pay a minimum call charge
every time a call is made, no matter the actual length of the call. The minimum call time should be set to match that
provided by the line provider.
· Extra BW Mode: Default = Incoming Outgoing
Defines the mode of operation used to increases bandwidth to the initial call to the remote Service.
· Outgoing Only
Bandwidth is added by making outgoing calls.
· Incoming Only
Bandwidth is added by the remote service calling back on the BACP number (assuming that BACP is successfully
negotiated).
Manager Manager 8.1
Manager
Page 333
15-601011 Issue 25l (11 February 2011)
· Outgoing Incoming
Uses both methods but bandwidth is first added using outgoing calls.
· Incoming Outgoing
Uses both methods but bandwidth is first added using incoming BACP calls.
Manager Manager 8.1
Manager
Page 334
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Service Settings
5.10.3 IP
The fields in this tab are used to configure network addressing for the services you are running. Depending on how your
network is configured, the use of Network Address Translation (NAT) 798 may be required.
Service | IP
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· IP Address: Default = 0.0.0.0 (address assigned by ISP)
An address should only be entered here if a specific IP address and mask have been provided by the Service Provider.
Note that if the address is in a different domain from the system then NAT is automatically enabled.
· IP Mask: Default = 0.0.0.0 (use NAT)
Enter the IP Mask associated with the IP Address if an address is entered.
· Primary Transfer IP Address: Default = 0.0.0.0 (No transfer)
This address acts as a primary address for incoming IP traffic. All incoming IP packets without a session are translated
to this address. This would normally be set to the local mail or web server address.
· For control units supporting a LAN1 and LAN2, the primary transfer address for each LAN can be set through the
System | LAN1 148 and System | LAN2 155 tabs.
· Request DNS: Default = Off
When selected, DNS information is obtained from the service provider. To use this, the DNS Server addresses set in the
system configuration (System | DNS 156 ) should be blank. The PC making the DNS request should have the system set
as its DNS Server. For DHCP clients the system will provide its own address as the DNS server.
· Forward Multicast Messages: Default = On
By default this option is on. Multicasting allows WAN bandwidth to be maximized through the reduction of traffic that
needs to be passed between sites.
· RIP Mode: Default = None
Routing Information Protocol (RIP) is a method by which network routers can exchange information about device
locations and routes. RIP can be used within small networks to allow dynamic route configuration as opposed to static
configuration using.
· None
The LAN does not listen to or send RIP messages.
· Listen Only (Passive)
Listen to RIP-1 and RIP-2 messages in order to learn RIP routes on the network.
· RIP1
Listen to RIP-1 and RIP-2 messages and send RIP-1 responses as a sub-network broadcast.
· RIP2 Broadcast (RIP1 Compatibility)
Listen to RIP-1 and RIP-2 messages and send RIP-2 responses as a sub-network broadcast.
· RIP2 Multicast
Listen to RIP-1 and RIP-2 messages and send RIP-2 responses to the RIP-2 multicast address.
Manager Manager 8.1
Manager
Page 335
15-601011 Issue 25l (11 February 2011)
5.10.4 Autoconnect
Fields in this tab enable you to set up automatic connections to the specified Service.
Service | Autoconnect
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Auto Connect Interval (mins): Default = 0 (disabled). Range = 0 to 99999 minutes.
This field defines how often this Service will automatically be called ("polled"). For example setting 60 means the
system will call this Service every hour in the absence of any normally generated call (this timer is reset for every call;
therefore if the service is already connected, then no additional calls are made). This is ideal for SMTP Mail polling from
Internet Service Providers.
· Auto Connect Time Profile: Default = <None>
Allows the selection of any configured Time Profiles. The selected profile controls the time period during which automatic
connections to the service are made. It does NOT mean that connection to that service is barred outside of these hours.
For example, if a time profile called "Working Hours" is selected, where the profile is defined to be 9:00AM to 6:00PM
Monday to Friday, then automatic connection to the service will not be made unless its within the defined profile. If
there is an existing connection to the service at 9:00AM, then the connection will continue. If there is no connection,
then an automatic connection will be made at 9:00AM.
Manager Manager 8.1
Manager
Page 336
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Service Settings
5.10.5 Quota
Quotas are associated with outgoing calls, they place a time limit on calls to a particular IP Service. This avoids excessive
call charges when perhaps something changes on your network and call frequency increases unintentionally.
Service | Quota
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Quota Time (mins): Default = 240 minutes. Range = 0 to 99999 minutes.
Defines the number of minutes used in the quota. When the quota time is used up no further data can be passed to this
service. This feature is useful to stop things like an internet game keeping a call to your ISP open for a long period.
· Warning: Setting a value here without selecting a Quota period below will stop all further calls after the Quota Time
has expired.
· Quota: Default = Daily, Range = None, Daily, Weekly or Monthly
Sets the period during which the quota is applied. For example, if the Quota Time is 60 minutes and the Quota is set
to Daily, then the maximum total connect time during any day is 60 minutes. Any time beyond this will cause the
system to close the service and prevent any further calls to this service. To disable quotas select None and set a Quota
Time of zero.
· Note: The ClearQuota
Manager Manager 8.1
Manager
454
feature can be used to create short codes to refresh the quota time.
Page 337
15-601011 Issue 25l (11 February 2011)
5.10.6 Fallback
These options allow you to set up a fallback for the Service. For example, you may wish to connect to your ISP during
working hours and at other times take advantage of varying call charges from an alternative carrier. You could therefore
set up one Service to connect during peak times and another to act as fallback during the cheaper period.
You need to create an additional Service to be used during the cheaper period and select this service from the Fallback
Service list box (open the Service form and select the Fallback tab).
If the original Service is to be used during specific hours and the Fallback Service to be used outside of these hours, a
Time Profile can be created. Select this Time Profile from the Time Profile list box. At the set time the original Service goes
into Fallback and the Fallback Service is used.
A Service can also be put into Fallback manually using short codes, for example:
· Put the service "Internet" into fallback:
· Short Code: *85
· Telephone Number: "Internet"
· Line Group ID: 0
· Feature: SetHuntGroupNightService
· Take the service "Internet" out of fallback:
· Short Code: *86
· Telephone Number: "Internet"
· Line Group ID: 0
· Feature: ClearHuntGroupNightService
Service | Fallback
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· In Fallback: Default = Off
This option indicates whether the Service is in Fallback or not. A service can be set into fallback using this setting.
Alternatively a service can be set into fallback using a time profile or short codes.
· Time profile: Default = <None> (No automatic fallback)
Select the time profile you wish to use for the service. The time profile should be set up for the hours that you wish this
service to be operational, out of these hours the Fallback Service is used.
· Fallback Service: <None>
Select the service that is used when this service is in fallback.
Manager Manager 8.1
Manager
Page 338
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Service Settings
5.10.7 DialIn
Only available for WAN and Intranet Services. This tab is used to define a WAN connection.
Service | Dial In
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
To define a WAN connection
1. Select Add.
2. Enter WAN if the service is being routed via a WAN port on a WAN3 expansion module.
Manager Manager 8.1
Manager
Page 339
15-601011 Issue 25l (11 February 2011)
5.11 RAS
A Remote Access Server (RAS) is a piece of computer hardware which sits on a corporate LAN and into which
employees dial on the public switched telephone network to get access to their email and to software and
data on the corporate LAN.
This form is used to create a RAS service that the system offers Dial In users. A RAS service is needed when configuring
modem dial in access, digital (ISDN) dial in access and a WAN link. Some systems may only require one RAS service since
the incoming call type can be automatically sensed.
RAS | RAS
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Name
A textual name for this service. If Encrypted Password (see below) is used this name must match the Account Name
entered in the Service Form.
· Extension
Enter an extension number if this service is to be accessed internally.
· COM Port
For future use.
· TA Enable: Default = Off
Select to enable or disable - if enabled RAS will pass the call onto a TA port for external handling.
· Encrypted Password: Default = Off
This option is used to define whether Dial In users are asked to use PAP or CHAP during their initial log in to the RAS
Service. If the Encrypted Password box is checked then Dial In users are sent a CHAP challenge, if the box is unchecked
PAP is used as the Dial In Authorization method.
Manager Manager 8.1
Manager
Page 340
15-601011 Issue 25l (11 February 2011)
Configuration Settings: RAS
5.11.1 PPP
PPP (Point-to-Point Protocol) is a Protocol for communication between two computers using a Serial interface, typically a
personal computer connected by phone line to a server.
RAS | PPP
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· CHAP Challenge Interval (secs): Default = 0 (disabled). Range = 0 to 99999 seconds.
The period between successive CHAP challenges. Blank or 0 disables repeated challenges. Some software, for example
Windows 95 DUN, does not support repeated CHAP challenges.
· Header Compression: Default = Off
Enables the negotiation and use of IP Header Compression as per RFC2507, RFC2508 and RFC2509.
· PPP Compression Mode: Default = MPPC
This option is used to negotiate compression (or not) using CCP. If set to MPPC or StacLZS the system will try to
negotiate this mode with the remote Control Unit. If set to Disable CCP is not negotiated.
· Disable
Do not use or attempt to use compression.
· StacLZS
Attempt to use and negotiate STAC compression (the standard, Mode 3)
· MPPC
Attempt to use and negotiate MPPC (Microsoft) compression. Useful for dialing into NT Servers.
· PPP Callback Mode: Default = Disable
· Disable:
Callback is not enabled
· LCP: (Link Control Protocol)
After authentication the incoming call is dropped and an outgoing call to the number configured in the Service will be
made to reestablish the link.
· Callback CP: (Microsoft's Callback Control Protocol)
After acceptance from both ends the incoming call is dropped and an outgoing call to the number configured in the
Service is made to reestablish the link.
· Extended CBCP: (Extended Callback Control Protocol)
Similar to Callback CP however the Microsoft application at the remote end will prompt for a telephone number. An
outgoing call will then be made to that number to reestablish the link.
· Data Pkt. Size: Default = 0, Range = 0 to 2048.
This is the number of data bytes contained in a Data Packet.
· BACP: Default = Off
Allows negotiation of the BACP/BCP protocols. These are used to control the addition of additional B channels to
simultaneously improve data throughput.
· Multilink: Default = Off
When enabled the system attempts to negotiate the use of the Multilink protocol (MPPC) on the link(s) into this Service.
Multilink must be enabled if the more than one channel is allowed to be Bundled/Multilinked to this RAS Service.
Manager Manager 8.1
Manager
Page 341
15-601011 Issue 25l (11 February 2011)
5.12 Incoming Call Route Settings
Incoming call routes are used to determine the destination of voice and data calls received by the system. On
systems where a large number incoming call routes need to be setup for DID numbers, the MSN/DID
Configuration 132 tool can be used. Select Tools | MSN Configuration.
· Calls received on IP, S0 and QSIG trunks do not use incoming call routes. Routing for these is based on
incoming number received as if dialed on-switch. Line short codes on those trunks can be used to modify
the incoming digits.
Determining which incoming call route is used is based on the call matching a number of possible criteria. In order of
highest priority first, these are:
1. The Bearer Capability indicated, if any, with the call. For example voice, data, video.
2. The Line Group ID of the trunk or trunk channel on which the call was received.
3. The Incoming Number received with the call.
4. The Incoming Sub Address received with the call.
5. The Incoming CLI of the caller.
Multiple Matches
If there is a match between more than one incoming call route entry, the one added to the configuration first is used.
Incoming Call Route Destinations
Each incoming route can include a fallback destination for when the primary destination is busy. It can also include a time
profile which control when the primary destination is used. Outside the time profile calls are redirected to a night service
destination.
· IP Office 4.1+: Multiple time profiles can be associated with an incoming call route. Each time profile used has its
own destination and fallback destination specified.
Incoming Call Routing Examples
Example 1
For this example, the customer has subscribes to receive two 2-digit DID numbers. They want calls on one routed to a
Sales hunt group and calls on the other to a Services hunt group. Other calls should use the normal default route to hunt
group Main. The following incoming call routes were added to the configuration to achieve this:
Line Group
Incoming Number
Destination
0
77
Sales
0
88
Services
0
blank
Main
Note that the incoming numbers could have been entered as the full dialed number, for example 7325551177 and
7325551188 respectively. The result would still remain the same as incoming number matching is done from right-to-left.
Line Group
Incoming Number
Destination
0
7325551177
Sales
0
7325551188
Services
0
blank
Main
Example 2
In the example below the incoming number digits 77 are received. The incoming call route entries 677 and 77 have the
same number of matching digit place and no non-matching places so both a potential matches. In this scenario the
systemwill use the incoming call route with the Incoming Number specified for matching.
Line Group
Incoming Number
Destination
0
677
Support
0
77
Sales
0
7
Services
Manager Manager 8.1
Manager
Page 342
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Incoming Call Route Settings
0
blank
Main
Example 3
In the following example, the 677 entry is used as the match for 77 as it has more matching digits than the 7 entry and no
non-matching digits.
Line Group
Incoming Number
Destination
0
677
Support
0
7
Services
0
blank
Main
Example 4
In this example the digits 777 are received. The 677 entry had a non-matching digit, so it is not a match. The entry 7 is
used as it has one matching digit and no non-matching digits.
Line Group
Incoming Number
Destination
0
677
Support
0
7
Services
0
blank
Main
Example 5
In this example the digits 77 are received. Both the additional incoming call routes are potential matches. In this case the
route with the shorter Incoming Number specified for matching is used and the call is routed to Services.
Line Group
Incoming Number
Destination
0
98XXX
Support
0
8XXX
Services
0
blank
Main
Example 6
In this example two incoming call routes have been added, one for incoming number 6XXX and one for incoming number
8XXX. In this case, any three digit incoming numbers will potential match both routes. When this occurs, potential match
that was added to the system configuration first is used. If 4 or more digits were received then an exact matching or nonmatching would occur.
Line Group
Incoming Number
Destination
0
6XXX
Support
0
8XXX
Services
0
blank
Main
Manager Manager 8.1
Manager
Page 343
15-601011 Issue 25l (11 February 2011)
5.12.1 Standard
Incoming call routes are used to match call received with destinations. Routes can be based on the incoming
line group, the type of call, incoming digits or the caller's ICLID. If a range of MSN/DID numbers has been
issued, this form can be populated using the MSN Configuration tool (see MSN Configuration 132 ).
· Default Blank Call Routes
By default the configuration contains two incoming calls routes; one set for Any Voice calls (including analog modem)
and one for Any Data calls. While the destination of these default routes can be changed, it is strongly recommended
that the default routes are not deleted.
· Deleting the default call routes, may cause busy tone to be returned to any incoming external call that does not
match any incoming call route.
· Setting any route to a blank destination field, may cause the incoming number to be checked against system short
codes for a match. This may lead to the call being rerouted off-switch.
· Calls received on IP, S0 and QSIG trunks do not use incoming call routes. Routing for these is based on incoming
number received as if dialed on-switch. Line short codes on those trunks can be used to modify the incoming digits.
· If there is no matching incoming call route for a call, matching is attempted against system short codes and finally
against voicemail nodes before the call is dropped.
· SIP Calls
For SIP calls, the following fields are used for call matching:
· Line Group ID
This field is matched against the Incoming Group settings of the SIP URI (Line | SIP URI
match.
233 ).
This must be an exact
· Incoming Number
This field can be used to match the called details (TO) in the SIP header of incoming calls. It can contain a number,
SIP URI or Tel URI. For SIP URI's the domain part of the URI is removed before matching by incoming call routing
occurs. For example, for the SIP URI mysip@example.com , only the user part of the URI, ie. mysip, is used for
matching.
· IP Office 6.0: The Call Routing Method 233 setting of the SIP line can be used to select whether the value used for
incoming number matching is taken from the To Header or the Request URI information provided with incoming
calls on that line.
· Incoming CLI
This field can be used to match the calling details (FROM) in the SDP header of incoming SIP calls. It can contain a
number, SIP URI, Tel URI or IP address received with SIP calls. For all types of incoming CLI except IP addresses a
partial entry can be used to achieve the match, entries being read from left to right. For IP addresses only full entry
matching is supported.
Manager Manager 8.1
Manager
Page 344
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Incoming Call Route Settings
Incoming Call Route | Standard
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
Incoming Call Matching Fields
The following fields are used to determine if the Incoming Call Route is a potential match for the incoming call. By default
the fields are used for matching in the order shown starting with Bearer Capability.
· Bearer Capability: Default = Any Voice
The type of call selected from the list of standard bearer capabilities: Any, Any Voice, Any Data, Speech, Audio 3K1,
Data 56K, Data 64K, Data V110, Video.
· Line Group ID: Default = 0, Range = 0 to 99999.
Matches against the Incoming Line Group to which the trunk receiving the call belongs.
· Incoming Number: Default = Blank (Match any unspecified)
Matches to the digits presented by the line provider. A blank entry matches all calls that do not match other entries. By
default this is a right-to-left matching.
· * = Incoming CLI Matching Takes Precedence
· – = Left-to-Right Exact Length Matching
Using a - in front of the number causes a left-to-right match. When left-to-right matching is used, the number match
must be the same length. For example -96XXX will match a DID of 96000 but not 9600 or 960000.
· X = Single Digit Wildcard
Use X's to enter a single digit wild card character. For example 91XXXXXXXX will only match DID numbers of at
least 10 digits and starting with 91, -91XXXXXXXX would only match numbers of exactly 10 digits starting with 91.
Other wildcard such as N, n and ? cannot be used.
· Where the incoming number potentially matches two incoming call routes with X wildcards and the number of
incoming number digits is shorter than the number of wildcards, the one with the shorter overall Incoming
Number specified for matching is used.
· i = ISDN Calling Party Number 'National'
The i character does not affect the incoming number matching. It is used for Outgoing Caller ID Matching, see notes
below.
· Incoming Sub Address: Default = Blank (Match all)
Matches any sub address component sent with the incoming call. If this field is left blank, it matches all calls.
· Incoming CLI: Default = Blank (Match all)
Enter a number to match the caller's ICLID provided with the call. This field is matched left-to-right. Number options
are:
· Full telephone number.
· Partial telephone number, for example just the area code.
· ! : Matches calls where the ICLID was withheld.
· ? : for number unavailable.
· Blank for all.
Manager Manager 8.1
Manager
Page 345
15-601011 Issue 25l (11 February 2011)
Call Setting Fields
For calls routed using this Incoming Call Route, the settings of the following fields are applied to the call regardless of the
destination.
· Locale: Default = Blank (Use system setting)
This option specifies the language prompts, if available, that voicemail should use for the call if it is directed to
voicemail.
· When the system routes a call to the voicemail server it indicates the locale for which matching prompts should be
provided if available. The locale sent to the voicemail server by the system is determined as follows:
Locale Source
Usage
Short Code
The short code locale, if set, is used if the call is routed to voicemail using the short
code.
System
If no user or incoming call route locale is set system locale is used unless overridden by
a short code locale.
Incoming Call Route
The incoming call route locale, if set, is used if caller is external.
User
The user locale, if set, is used if the caller is internal.
· Priority: Default = 1-Low, Range = 1-Low to 3-High.
This setting allows incoming calls to be assigned a priority. Other calls such as internal calls are assigned priority 1-Low
.
· In situations where calls are queued, high priority calls are placed before calls of a lower priority. This has a number
of effects:
· Mixing calls of different priority is not recommended for destinations where Voicemail Pro is being used to
provided queue ETA and queue position messages to callers since those values will no longer be accurate when
a higher priority call is placed into the queue. Note also that Voicemail Pro will not allow a value already
announced to an existing caller to increase.
· If the addition of a higher priority call causes the queue length to exceed the hunt group's Queue Length
Limit 316 , the limit is temporarily raised by 1. This means that calls already queued are not rerouted by the
addition of a higher priority call into the queue.
· IP Office 4.2+: A timer can be used to increase the priority of queued calls, see System | Telephony | Telephony |
Call Priority Promotion Time 160 .
· IP Office 4.2+: The current priority of a call can be changed through the use of the p short code character
short code used to transfer the call.
427
in a
· Tag: Default = Blank (No tag). Software level = 4.1+.
Allows a text tag to be associated with calls routed by this incoming call route. This tag is displayed with the call within
applications and on phone displays. See Call Tagging 756 .
· Hold Music Source: Default = System source. Software level = 4.2+ (Not Small Office Edition).
The system can support up to 4 music on hold source; the System Source (either an internal file or the external source
port or tones) plus up to 3 additional internal wav files, see System | Telephony | Tones & Music 163 . If the system has
several hold music sources available, this field allows selection of the source to associate with calls routed by this
incoming call route. The new source selection will then apply even if the call is forwarded or transferred away from the
Incoming Call Route destination. If the call is routed to another IP Office 4.2+ system in a Small Community Network,
the matching source is used if available. The hold music source associated with a call can also be changed by a hunt
group's Hold Music Source 306 setting.
· Destination: Default = Blank, Software Level = Up to 4.0 only.
For IP Office 4.1+, this option has moved to the Incoming Call Route | Destinations 349 tab. Select the destination for
the call from the drop-down list box which contains all available extensions, users, groups, RAS services and voicemail.
System short codes and dialing numbers can be entered manually. Once the incoming call is matched the call is passed
to that destination.
· Drop-Down List Options
The following options appear in the drop-down in the following order:
· Voicemail allows remote mailbox access with Embedded Voicemail, Voicemail Lite or Voicemail Pro. Callers are
asked to enter the extension ID of the mailbox required and then the mailbox access code.
· User Names
· Hunt Groups Names
· AA:Name directs calls to an Embedded Voicemail auto-attendant services.
· Manually Entered Options
The following options can be entered manually into the field.
· VM:Name Directs calls to the matching start point in Voicemail Pro.
Manager Manager 8.1
Manager
Page 346
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Incoming Call Route Settings
· A . matches the Incoming Number field. This can be used even when X wildcards are being used in the Incoming
Number field.
· A # matches all X wildcards in the Incoming Number field. For example, if the Incoming Number was 91XXXXXXXXXXX, the Destination would be XXXXXXXXXXX.
· Text and number strings entered here are passed through to system short codes, for example to direct calls into a
conference. Note that not all short code features are supported.
· Fallback Extension: Default = Blank (No fallback). Software level = Up to 4.0 only.
For IP Office 4.1+, this option has moved to the Incoming Call Route | Destinations 349 tab. Defines an alternate
destination which should be used when the current destination, set in the Destination or Night Service Destination field,
cannot be obtained. For example if the primary destination is a hunt group returning busy and without queuing or
voicemail.
· Night Service Profile: Default = <None> (No night service). Software level = Up to 4.0 only.
A time profile during which the Night Service Destination should be used rather than the Destination.
· Night Service Destination: Default = Blank. Software level = Up to 4.0 only.
Set the destination to be used during periods defined by the Night Service Profile. The same range of values can be
used as for the Destination field.
Outgoing Caller ID Matching
In cases where a particular Incoming Number is routed to a specific individual user, the system will attempt to use that
Incoming Number as the user's caller ID when they make outgoing calls if no other number is specified. This requires that
the Incoming Number is a full number suitable for user as outgoing caller ID and acceptable to the line provider.
When this is the case, the character i can also be added to the Incoming Number field. This character does not affect the
incoming call routing. However when the same Incoming Number is used for an outgoing caller ID, the calling party
number plan is set to ISDN and the type is set to National. This option may be required by some network providers.
Manager Manager 8.1
Manager
Page 347
15-601011 Issue 25l (11 February 2011)
5.12.2 Voice Recording
This tab is used to activate the automatic recording of incoming calls that match the incoming call route.
Call recording requires Voicemail Pro to be installed and running. Call recording also requires available conference
resources similar to a 3-way conference.
· IP Office 4.0+ introduces the following changes to recording:
· Calls to and from IP devices, including those using Direct media, can be recorded.
· Calls parked or held pause recording until the unparked or taken off hold.
· Recording is stopped if:
· User recording stops if the call is transferred to another user.
· User account code recording stops if the call is transferred to another user.
· Hunt group recording stops if the call is transferred to another user who is not a member of the hunt
group.
· Incoming call route recording continues for the duration of the call on the system.
Incoming Call Route | Voice Recording
Control Unit
SOE
Software Level
4.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Record Outbound: Default = None
Select whether automatic recording of outgoing calls is enabled. The Auto Record Calls option sets whether just
external calls or external and internal calls are included. Options for recording are:
· None: Do not automatically record calls.
· On: Record the call if possible. If not possible to record, allow the call to continue.
· Mandatory: Record the call if possible. If not possible to record, block the call and return busy tone.
· Percentages of calls: Record a selected percentages of the calls.
· Recording (Auto): Default = Mailbox
Sets the destination for automatically triggered recordings.
· Mailbox
This option sets the destination for the recording to be a selected user or hunt group mailbox. The adjacent drop
down list is used to select the mailbox.
· Voice Recording Library: Software level = 3.0+.
This options set the destination for the recording to be a VRL folder on the voicemail server. The ContactStore
application polls that folder and collects waiting recordings which it then places in its own archive. Recording is still
done by the Voicemail Pro.
Manager Manager 8.1
Manager
Page 348
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Incoming Call Route Settings
5.12.3 Destinations
IP Office 4.1+: The system allows multiple time profiles to be associated with an incoming call route. For each time profile,
a separate Destination and Fallback Extension can be specified.
When multiple entries are added, they are resolved from the bottom up. The entry used will be the first one, working from
the bottom of the list upwards, that is currently 'true', ie. the current day and time or date and time match those specified
by the Time Profile. If no match occurs the Default Value options are used.
Once a match is found, the system does not use any other destination set even if the intended Destination and Fallback
Extension destinations are busy or not available.
Incoming Call Route | Standard
Control Unit
SOE
Software Level
4.1+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Time Profile
This column is used to specify the time profiles 360 used by the incoming call routes. The entry displays a drop-down list
of existing time profiles from which a selection can be made. To remove an existing entry, select it by clicking on the
button on the left of the row, then right-click on the row and select Delete.
· Default Value
This entry is fixed and is used if no match to a time profile below occurs.
· Destination: Default = Blank
Either enter the destination manually or select the destination for the call from the drop-down list. The dr box which
contains all available extensions, users, groups, RAS services and voicemail. System short codes and dialing numbers
can be entered manually. Once the incoming call is matched the call is passed to that destination.
· Drop-Down List Options
The following options appear in the drop-down list:
· Voicemail allows remote mailbox access with Embedded Voicemail, Voicemail Lite or Voicemail Pro. Callers are
asked to enter the extension ID of the mailbox required and then the mailbox access code.
· Local user names.
· Local hunt groups names.
· AA:Name directs calls to an Embedded Voicemail auto-attendant services.
· Manually Entered Options
In addition to short codes, extension and external numbers, the following options can be also be entered manually:
· VM:Name Directs calls to the matching start point in Voicemail Pro.
· A . matches the Incoming Number field. This can be used even when X wildcards are being used in the Incoming
Number field.
· A # matches all X wildcards in the Incoming Number field. For example, if the Incoming Number was 91XXXXXXXXXXX, the Destination of "#" would match XXXXXXXXXXX. Note that the # should be enclosed in "
quotation marks.
· Text and number strings entered here are passed through to system short codes, for example to direct calls into a
conference. Note that not all short code features are supported.
· Fallback Extension: Default = Blank (No fallback)
Defines an alternate destination which should be used when the current destination, set in the Destination field cannot
be obtained. For example if the primary destination is a hunt group returning busy and without queuing or voicemail.
Manager Manager 8.1
Manager
Page 349
15-601011 Issue 25l (11 February 2011)
5.13 WAN Port Settings
These entries are used to configure the operation of system WAN ports and services.
Physical WAN ports are the 37-way D-type WAN ports found on the rear of IP403, IP406, IP406v2 and IP412
control unit. Additional WAN ports can be added by the installation of up to two WAN3 expansion modules,
each module providing 3 additional WAN ports. On the Small Office Edition control unit, a single WAN port can
be added by the installation of a WAN trunk card at the rear of the unit. Physical WAN ports are not supported
with IP500 and IP500v2 systems. For full details of installing additional WAN ports, refer to the Manager
Installation Manual.
Creating a Virtual WAN Port
WAN services can be run over a T1 PRI trunk connection. This requires creation of a virtual WAN port. For full details refer
to Using a Dedicated T1/PRI ISP Link 801 in Appendix A.
1. Select
2. Click
WAN Port.
and select PPP.
3. In the Name field, enter either LINEx.y where:
· LINE must be in uppercase.
· x is the line number. For a PRI/T1 module in Slot A, this will be 1. For a PRI/T1 module in Slot B, this will be 5.
· y is the lowest numbered channel number to be used by the WAN link minus 1. For example, if the lowest channel to
be used is channel 1 then y = 1 - 1 = 0.
4. In the Speed field, enter the total combined speed of the maximum number of channels sets in the Service. In this
example, 12 channels x 64000 bits = 76800.
· Note: The maximum number of channels that can be used will be limited by the number of data channels supported
by the system Control Unit and not already in use.
5. In the RAS Name field, select the RAS name created when the new Service of that name was created.
6. Click OK.
Manager Manager 8.1
Manager
Page 350
15-601011 Issue 25l (11 February 2011)
Configuration Settings: WAN Port Settings
5.13.1 WAN Port
Use this form to configure the leased line connected to the WAN port on the Control Unit. Normally this connection is
automatically detected by the control unit. 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.
WAN Port | WAN Port
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Name
The physical ID of the Extension port,. This parameter is not configurable; it is allocated by the system.
· Speed
The operational speed of this port. For example for a 128K connection, enter 128000. This should be set to the actual
speed of the leased line as this value is used in the calculation of bandwidth utilization. If set incorrectly, additional calls
may be made to increase Bandwidth erroneously.
· Mode: Default = SyncPPP
Select the protocol required:
· SyncPPP
For a data link.
· SyncFrameRelay
For a link supporting Frame Relay.
· RAS Name
If the Mode is SyncPPP, selects the RAS service to associate with the port. If the Mode is SyncFrameRelay, the RAS
Name is set through the DCLIs tab.
Manager Manager 8.1
Manager
Page 351
15-601011 Issue 25l (11 February 2011)
5.13.2 Frame Relay
This tab is only available for Frame Relay entries. These show SyncFrameRelay as the Mode on the WAN Port tab.
WAN Port | Frame Relay
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Frame Management Type
This must match the management type expected by the network provider. Selecting AutoLearn allows the system to
automatically determine the management type based on the first few management frames received. If a fixed option is
required the following are supported: Q933 AnnexA 0393, Ansi AnnexD , FRFLMI and None.
· Frame Learn Mode
This parameter allows the DLCIs that exist on the given WAN port to be provisioned in a number of different ways.
· None
No automatic learning of DLCIs. DLCIs must be entered and configured manually.
· Mgmt
Use LMI to learn what DLCIs are available on this WAN.
· Network
Listen for DLCIs arriving at the network. This presumes that a network provider will only send DLCIs that are
configured for this particular WAN port.
· NetworkMgmt
Do both management and network listening to perform DLCI learning and creation.
· Max Frame Length
Maximum frame size that is allowed to traverse the frame relay network.
· Fragmentation Method
Options are RFC1490 or RFC1490+FRF12.
Manager Manager 8.1
Manager
Page 352
15-601011 Issue 25l (11 February 2011)
Configuration Settings: WAN Port Settings
5.13.3 DLCIs
This tab is only available for Frame Relay entries. These show SyncFrameRelay as the Mode on the WAN Port
351
tab.
The tab lists the DLCIs created for the connection. These can be edited using the Add, Edit and Remove buttons.
WAN Port | DLCIs
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Frame Link Type: Default = PPP
Data transfer encapsulation method. Set to the same value at both ends of the PVC (Permanent Virtual Channel).
· None
· PPP
Using PPP offers features such as out of sequence traffic reception, compression and link level connection
management.
· RFC 1490
RFC 1490 encapsulation offers performance and ease of configuration and more inter-working with third party CPE.
· RFC1490 + FRF12
Alternate encapsulation to PPP for VoIP over Frame Relay. When selected all parameters on the Service | PPP tab
being used are overridden.
· DLCI: Default = 100
This is the Data Link Connection Identifier, a unique number assigned to a PVC end point that has local significance
only. Identifies a particular PVC endpoint within a user's physical access channel in a frame relay.
· RAS Name
Select the RAS Service you wish to use.
· Tc: Default = 10
This is the Time Constant in milliseconds. This is used for measurement of data traffic rates. The Tc used by the system
can be shorter than that used by the network provider.
· CIR: (Committed Information Rate) Default = 64000 bps
This is the Committed Information Rate setting. It is the maximum data rate that the WAN network provider has agreed
to transfer. The committed burst size (Bc) can be calculated from the set Tc and CIR as Bc = CIR x Tc. For links carrying
VoIP traffic, the Bc should be sufficient to carry a full VoIP packet including all its required headers. See the example
below.
· EIR: (Excess Information Rate) Default = 0 bps
This is the maximum amount of data in excess of the CIR that a frame relay network may attempt to transfer during the
given time interval. This traffic is normally marked as De (discard eligible). Delivery of De packets depends on the
network provider and is not guaranteed and therefore they are not suitable for UDP and VoIP traffic. The excess burst
size (Be) can be calculated as Be = EIR x Tc.
Manager Manager 8.1
Manager
Page 353
15-601011 Issue 25l (11 February 2011)
Example: Adjusting the Tc Setting
G.729 VoIP creates a 20 byte packet every 20ms. Adding typical WAN PPP headers results in a 33 byte packet every
20ms.
For a Committed Information Rate (CIR) of 14Kbps, with the Time Constant (Tc) set to 10ms; we can calculate the
Committed Burst size:
Bc = CIR x Tc = 14,000 x 0.01 = 140 bits = 17.5 bytes.
Using 10ms as the Tc, a full G.729 VoIP packet (33 bytes) cannot be sent without exceeding the Bc. The most likely result
is lost packets and jitter.
If the Tc is increased to 20ms:
Bc = CIR x Tc = 14,000 x 0.02 = 280 bits = 35 bytes.
The Bc is now sufficient to carry a full G.729 VoIP packet.
Notes
1. Backup over Frame Relay is not supported when the Frame Link Type is set to RFC1490.
2. When multiple DLCIs are configured, the WAN link LED is switched off if any of those DLCIs is made inactive, regardless
of the state of the other DLCIs. Note also that the WAN link LED is switched on following a reboot even if one of the
DLCIs is inactive. Therefore when multiple DLCIs are used, the WAN link LED cannot be used to determine the current
state of all DLCIs.
3. When the Frame Link Type is set to RFC1490, the WAN link LED is switched on when the WAN cable is attached
regardless other whether being connected to a frame relay network.
Manager Manager 8.1
Manager
Page 354
15-601011 Issue 25l (11 February 2011)
Configuration Settings: WAN Port Settings
5.13.4 Advanced
The settings on this tab are used for Frame Relay connections.
WAN Port | Advanced
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Address Length
The address length used by the frame relay network. The network provider will indicate if lengths other than two bytes
are to be used.
· N391: Full Status Polling Counter
Polling cycles count used by the CPE and the network provider equipment when bidirectional procedures are in
operation. This is a count of the number of link integrity verification polls (T391) that are performed (that is Status
Inquiry messages) prior to a Full Status Inquiry message being issued.
· N392: Error Threshold Counter
Error counter used by both the CPE and network provider equipment. This value is incremented for every LMI error that
occurs on the given WAN interface. The DLCIs attached to the given WAN interface are disabled if the number of LMI
errors exceeds this value when N393 events have occurred. If the given WAN interface is in an error condition then that
error condition is cleared when N392 consecutive clear events occur.
· N393: Monitored Events Counter
Events counter measure used by both the CPE and network provider equipment. This counter is used to count the total
number of management events that have occurred in order to measure error thresholds and clearing thresholds.
· T391: Link Integrity Verification Polling Timer
The link integrity verification polling timer normally applies to the user equipment and to the network equipment when
bidirectional procedures are in operation. It is the time between transmissions of Status Inquiry messages.
· T392: Polling Verification Timer
The polling verification timer only applies to the user equipment when bidirectional procedures are in operation. It is the
timeout value within which to receive a Status Inquiry message from the network in response to transmitting a Status
message. If the timeout lapses an error is recorded (N392 incremented).
Manager Manager 8.1
Manager
Page 355
15-601011 Issue 25l (11 February 2011)
5.13.5 PPP
Fields in this tab enable you to configure Point to Point Protocol (PPP) in relation to this particular service. PPP is a protocol
for communication between two computers using a Serial interface.
Service | PPP
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500 , IP500v2
.
.
· Chap Challenge Interval (secs): Default = 0 (disabled). Range = 0 to 99999 seconds.
The period between CHAP challenges. Blank or 0 disables repeated challenges. Some software such as Windows 95 DUN
does not support repeated CHAP challenges.
· Bi-Directional Chap: Default =Off.
· Header Compression: Default = None selected
Enables the negotiation and use of IP Header Compression. Supported modes are IPHC and VJ. IPHC should be used on
WAN links.
· PPP Compression Mode: Default = MPPC
Enables the negotiate and use of compression. Do not use on VoIP WAN links.
· Disable
Do not use or attempt to use compression.
· StacLZS
Attempt to use STAC compression (Mode 3, sequence check mode).
· MPPC
Attempt to use MPPC compression. Useful for NT Servers.
· PPP Callback Mode: Default = Disable
· Disable
Callback is not enabled
· LCP: (Link Control Protocol)
After authentication the incoming call is dropped and an outgoing call to the number configured in the Service is
made to re-establish the link.
· Callback CP: (Microsoft's Callback Control Protocol)
After acceptance from both ends the incoming call is dropped and an outgoing call to the number configured in the
Service is made to re-establish the link.
· Extended CBCP: (Extended Callback Control Protocol)
Similar to Callback CP except the Microsoft application at the remote end prompts for a telephone number. An
outgoing call is then made to that number to re-establish the link.
· PPP Access Mode: Default = Digital64
Sets the protocol, line speed and connection request type used when making outgoing calls. Incoming calls are
automatically handled (see RAS services).
· Digital64
Protocol set to Sync PPP, rate 64000 bps, call presented to local exchange as a "Data Call".
· Digital56
As above but rate 56000 bps.
· Voice56
As above but call is presented to local exchange as a "Voice Call".
· V120
Protocol set to Async PPP, rate V.120, call presented to local exchange as a "Data Call". This mode runs at up to 64K
per channel but has a higher Protocol overhead than pure 64K operation. Used for some bulletin board systems as it
allows the destination end to run at a different asynchronous speed to the calling end.
· V110
Protocol is set to Async PPP, rate V.110. This runs at 9600 bps, call is presented to local exchange as a "Data Call". It
is ideal for some bulletin boards.
· Modem
Allows Asynchronous PPP to run over an auto-adapting Modem to a service provider (requires a Modem2 card in the
main unit)
Manager Manager 8.1
Manager
Page 356
15-601011 Issue 25l (11 February 2011)
Configuration Settings: WAN Port Settings
· Data Pkt. Size: Default = 0, Range = 0 to 2048.
Sets the size limit for the Maximum Transmissible Unit.
· BACP: Default = Off
Enables the negotiation and use of BACP/BCP protocols. These are used to control the addition of B channels to increase
bandwidth.
· Incoming traffic does not keep link up: Default = On
When enabled, the link is not kept up for incoming traffic only.
· Multilink/QoS: Default = Off
Enables the negotiation and use of Multilink protocol (MPPC) on links into this Service. Multilink must be enabled if there
is more than one channel that is allowed to be Bundled/Multilinked to this RAS Service.
Manager Manager 8.1
Manager
Page 357
15-601011 Issue 25l (11 February 2011)
5.14 Directory
This section is used to edit directory records that are stored in the system's configuration. These directory
records can be manually imported or export using a CSV file 61 . The system can also use Directory Services
166 to automatically import directory entries from an LDAP server at regular intervals.
IP Office 5.0+: The systemcan also automatically import directory entries from another system. Automatically
imported entries are used as part of the system directory but are not part of the editable configuration.
Automatically imported entries cannot override manually entered entries.
Directory entries are used for two types of function:
· Directory Dialing
Directory numbers are displayed by user applications such as Phone Manager and SoftConsole. Directory numbers
are viewable through the Dir 615 function on many Avaya phones (Contacts or History). They allow the user to
select the number to dial by name. The directory will also contain the names and numbers of users and hunt groups
on the system.
· The Dir function groups directory entries shown to the phone user into the following categories. Depending on
the phone, the user may be able to select the category currently displayed. In some scenarios, the categories
displayed may be limited to those supported for the function being performed by the user:
· External
Directory entries from the system configuration. IP Office 5.0+: This includes HTTP and LDAP imported
entries.
· Groups
Groups on the system. If the system is in a Small Community Network it will also include groups on other
systems in the network (For pre-IP Office 5 systems, this feature requires the systems to have Advanced
Small Community Networking licenses).
· Users or Index
Users on the system. If the system is in a Small Community Network it will also include users on other
systems in the network (For pre-IP Office 5 systems, this feature requires the systems to have Advanced
Small Community Networking licenses).
· Personal
Available for T3 phones, T3 IP phones, 1400, 1600 and 9600 Series phones. These are the user's personal
directory entries stored within the system configuration.
· Name Matching
Directory entries are also used to associate a name with the dialled number on outgoing calls or the received CLI on
incoming calls. When name matching is being done, a match in the users personal directory overrides any match in
the system directory. Note that some user applications also have their own user directory.
· The IP Office Phone Manager and SoftConsole applications have their own user directories which are also used
by the applications name matching. Matches in the application directory may lead to the application displaying
a different name from that shown on the phone.
· Name matching is not performed when a name is supplied with the incoming call, for example QSIG trunks.
· Directory name matching is not supported for DECT handsets.
A maximum of 2500 directory entries (1000 in pre-IP Office 5 systems) are supported in the system configuration. Using a
1400, 1600 or 9600 Series phone, system phone users can also edit the configuration directory records.
System
Number of Directory Records
Configuration
LDAP Import
HTTP Import
Total Number
of Directory
Records
IP500/
IP500v2
2500
5000
5000
5000
IP412
2500
2500
2500
2500
IP406 V2
2500
2500
2500
2500
Directory | Directory Entry
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
Manager Manager 8.1
Manager
Page 358
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Directory
· Name
Enter the text, to be used to identify the number. Names should not begin with numbers.
· Number
Enter the number to be matched with the above name. Any brackets or - characters used in the number string are
ignored. The directory number match is done on reading from the left-hand side of the number string. Note that if the
system has been configured to use an external dialing prefix, that prefix should be added to directory numbers.
The following characters (IP Office Release 5.0+) are supported in directory entries. They are supported in both system
configuration entries and in HTTP/LDAP imported entries.
· ? = Any Digit
Directory entries containing a ? are only used for name matching against the dialed or received digits on outgoing or
incoming. They are not included in the directory of numbers to dial available to users through their phones or
applications. The wildcard can be used in any position but typically would be used at the end of the number.
· In the following example, any calls where the dialed or received number is 10 digits long and starts 732555 will
have the display name Homdel associated with them.
· Name: Holmdel
· Number: 9732555????
· ( and ) brackets = Optional Digits
These brackets are frequently used to enclose an optional portion of a number, typically the area code. Only one
pair of brackets are supported in a number. Entries containing digits inside ( ) brackets are used for both name
matching or user dialling. When used for name matching, the dialed or received digits are compared to the
directory number with and without the ( ) enclosed digits. When used for dialling from a phone or application
directory, the full string is dialed with the ( ) brackets removed.
· The following example is a local number. When dialed by users they are likely to dial just the local number.
However on incoming calls, for the CLI the telephony provider includes the full area code. Using the ( ) to
enclose the area code digits, it is possible for the single directory entry to be used for both incoming and
outgoing calls.
· Name: Raj Garden
· Number: 9(01707)373386
· Space and - Characters
Directory entries can also contain spaces and - characters. These will be ignored during name matching and dialing
from the directory.
Manager Manager 8.1
Manager
Page 359
15-601011 Issue 25l (11 February 2011)
5.15 Time Profile
Time Profiles are used by different services to change their operation when required. In most areas where
time profiles can be used, not setting a time profile is taken as meaning 24-hour operation.
· Time profiles consist of recurring weekly patterns of days and times when the time profile is in effect.
· Time profiles (IP Office 4.1+) can include time periods on specified calendar days when the time profile is in
effect. Calendar entries can be entered for the current and following calendar year.
Time profiles are used by the following entry types:
Hunt Group 304
A hunt group can use time profiles in the following ways:
· A time profile can be used to determine when a hunt group is put into night service mode 314 . Calls then go
to an alternate Night Service Fallback group if set, otherwise to voicemail if available or busy tone if not.
· For automatic voice recording
319 ,
a time profile can be used to set when voice recording is used.
Service 331
A Service can use time profiles in the following ways:
· A time profile can be used to set when a data service is available. Outside its time profile, the service is
either not available or uses an alternate fallback service if set.
· For services using auto connect, a time profile can be used to set when that function is used. See Service |
Autoconnect 336 .
User 262
A user can use time profiles in the following ways:
· Users being used for Dial In 283 data services such as RAS can have an associated time profile that defines
when they can be used for that service.
· Users can be associated with a working hours and an out of hours user rights. A time profile can then be
used to determine which user rights is used at any moment.
· For automatic voice recording
· For mobile twinning
296 ,
284 ,
a time profile can be used to set when that voice recording is used.
a time profile can be used to define when twinning should be used.
Incoming Call Route 342
Incoming call routes can also use time profiles to specify when calls should be recorded. Multiple time profiles
can be associate with an incoming call route, each profile specifying a destination and fall back destination.
Least Cost Route
A Least Cost Route uses time profiles to determine when the routes should be used.
ARS 407
ARS forms use time profile to determine when the ARS form should be used or calls rerouted to an out of hours
route.
Account Code 375
Account Codes can use automatic voice recording triggered by calls with particular account codes. A time profile
can be used to set when this function is used.
Auto Attendant 400
Embedded voicemail auto attendants can use time profiles to control the different greetings played to callers.
Manager Manager 8.1
Manager
Page 360
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Time Profile
For a time profile with multiple entries, for example a week pattern and some calendar entries, the profile is valid when
any entry is valid.
Time Profile | Time Profile
Control Unit
SOE
, IP403
Software Level
1.0+.
Mergeable
Pre-3.2
, 3.2+
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Name: Range = Up to 31 characters
This name is used to select the time profile from within other tabs.
· Time Entry List
This list shows the current periods during which the time profile is active. Clicking on an existing entry will display the
existing settings and allows them to be edited if required. To remove an entry, selecting it and then click on Remove or
right-click and select Delete.
· Recurrence Pattern (Weekly Time Pattern)
When a new time entry is required, click Add Recurring and then enter the settings for the entry using the fields
displayed. Alternately right-click and select Add Recurring Time Entry. This type of entry specific a time period and the
days on which it occurs, for example 9:00 - 12:00, Monday to Friday. A time entry cannot span over two days. For
example you cannot have a time profile starting at 18:00 and ending 8:00. If this time period is required two Time
Entries should be created - one starting at 18:00 and ending 11:59, the other starting at 00:00 and ending 8:00.
· Start Time
The time at which the time period starts.
· End Time
The time at which the time period ends.
· Days of Week
The days of the week to which the time period applies.
· Recurrence Pattern (Calendar Date): Software Level = 4.1+.
When a new calendar date entry is required, click Add Date and then enter the settings required. Alternately right-click
and select Add Calendar Time Entry. Calendar entries can be set for up to the end of the next calendar year.
· Start Time
The time at which the time period starts.
· End Time
The time at which the time period ends.
· Year
Select either the current year or the next calendar year.
· Date
To select or de-select a particular day, double-click on the date. Selected days are shown with a dark gray
background. Click and drag the cursor to select or de-select a range of days.
Manager Manager 8.1
Manager
Page 361
15-601011 Issue 25l (11 February 2011)
5.16 Firewall Profile Settings
The system can act as a firewall, allowing only specific types of data traffic to start a session across the
firewall and controlling in which direction such sessions can be started.
· Static NAT 366 (IP Office 4.2+)
The system supports Static NAT address translation by a firewall profiles. If the Firewall Profile
contains any Static NAT entries, all packets received by the firewall must match one of those static
NAT entries to not be blocked.
System firewall profiles can be applied in the following areas of operation:
·
System 155
A firewall profile can be selected to be applied to traffic between LAN1 and LAN2.
·
User 283
Users can be used as the destination of incoming RAS calls. For those users a firewall profile can be selected on the
user's Dial In 283 tab.
·
Service 332
Services are used as the destination for IP routes connection to off-switch data services such as the internet. A
Firewall Profile can be selected for use with a service.
·
Logical LAN 385
Where a logical LAN is created for use as an IP Route destination, a Firewall Profile can be selected for use with the
logical LAN.
If Network Address Translation (NAT) is used with the firewall (which it typically is), then you must also configure a
Primary Incoming Translation Address (see IP 335 tab of the Service configuration form) if you wish sessions to be started
into your site (typically for SMTP) from the Internet.
Manager Manager 8.1
Manager
Page 362
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Firewall Profile Settings
5.16.1 Standard
By default, any protocol not listed in the standard firewall list is dropped unless a custom firewall entry
for that protocol.
364
is configured
Firewall | Standard
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Name: Range = Up to 31 characters
Enter the name to identify this profile.
· Protocol Control
For each of the listed protocols, the options Drop, In (Incoming traffic can start a session), Out (Outgoing traffic can
start a session) and Both Directions can be selected. Once a session is started, return traffic for that session is also
able to cross the firewall.
Protocol
Default
Description
TELNET
Out
Remote terminal log in.
FTP
Out
File Transfer Protocol.
SMTP
Out
Simple Mail Transfer Protocol.
TIME
Out
Time update protocol.
DNS
Out
Domain Name System.
GOPHER
Drop
Internet menu system.
FINGER
Drop
Remote user information protocol.
RSVP
Drop
Resource Reservation Protocol.
HTTP
Out
Hypertext Transfer Protocol.
POP3
Out
Post Office Protocol.
NNTP
Out
Network News Transfer Protocol.
SNMP
Drop
Simple Network Management Protocol.
IRC
Out
Internet Relay Chat.
PPTP
Drop
Point to Point Tunneling Protocol.
IGMP
Drop
Internet Group Membership Protocol.
· Service Control: Software level = 4.0+.
For each of the listed services, the options Drop, In, Out and Both Directions can be selected. Once a session is
started, return traffic for that session is also able to cross the firewall.
Protocol
Default
Description
SSI
In
System Status Application access.
SEC
Drop
TCP security settings access.
CFG
Drop
TCP configuration settings access.
TSPI
In
TSPI service access.
Manager Manager 8.1
Manager
Page 363
15-601011 Issue 25l (11 February 2011)
5.16.2 Custom
The tab lists custom firewall settings added to the firewall profile. The Add, Edit and Remove controls can be used to
amend the settings in the list.
Firewall | Custom
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Notes
For information only. Enter text to remind you of the purpose of the custom firewall entry.
· Remote IP Address
The IP address of the system at the far end of the link. Blank allows all IP addresses.
· Remote IP Mask
The mask to use when checking the Remote IP Address. When left blank no mask is set, equivalent to 255.255.255.255
- allow all.
· Local IP Address
The address of devices local to this network (pre-translated). Blank allows all IP addresses.
· Local IP Mask
The mask to use when checking the Local IP Address. When left blank no mask is set, equivalent to 255.255.255.255 allow all.
· IP Protocol
The value entered here corresponds to the IP Protocol which is to be processed by this Firewall profile: 1 for ICMP, 6 for
TCP, 17 for UDP or 47 for GRE. This information can be obtained from the "pcol" parameter in a Monitor trace.
· Match Offset
The offset into the packet (0 = first byte of IP packet) where checking commences for either a specific port number, a
range of port numbers, or data.
· Match Length
The number of bytes to check in the packet, from the Match Offset point, that are checked against the Match Data and
Match Mask settings.
· Match Data
The values the data must equal once masked with the Match Mask. This information can be obtained from "TCP Dst"
parameter in a Monitor trace (the firewall uses hex so a port number of 80 is 50 in hex)
· Match Mask
This is the byte pattern, which is logically ANDed with the data in the packet from the offset point. The result of this
process is then compared against the contents of the "Match Data" field.
· Direction
The direction that data may take if matching this filter.
Drop
All matching traffic is dropped.
In
Incoming traffic can start a session.
Out
Outgoing traffic can start a session.
Both Directions
Both incoming and outgoing traffic can start sessions.
Manager Manager 8.1
Manager
Page 364
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Firewall Profile Settings
Example Custom Firewall Entries
Example: Dropping NetBIOS searches on an ISPs DNS
We suggest that the following filter is always added to the firewall facing the Internet to avoid costly but otherwise
typically pointless requests from Windows machines making DNS searches on the DNS server at your ISP.
· Direction: Drop
· IP Protocol: 6 (TCP)
· Match Offset: 20
· Match Length: 4
· Match Data: 00890035
· Match Mask: FFFFFFFF
Example: Browsing Non-Standard Port Numbers
The radio button for HTTP permits ports 80 and 443 through the firewall. Some hosts use non-standard ports for HTTP
traffic, for example 8080, 8000, 8001, 8002, etc. You can add individual filters for these ports as you find them.
You wish to access a web page but you cannot because it uses TCP port 8000 instead of the more usual port 80, use the
entry below.
· Direction: Out
· IP Protocol: 6 (TCP)
· Match Offset: 22
· Match Length: 2
· Match Data: 1F40
· Match Mask: FFFF
A more general additional entry given below allows all TCP ports out.
· Direction: Out
· IP Protocol: 6 (TCP)
· Match Offset: 0
· Match Length: 0
· Match Data: 00000000000000000000000000000000
· Match Mask: 00000000000000000000000000000000
Example: Routing All Internet Traffic through a WinProxy
If you wish to put WinProxy in front of all Internet traffic via the Control Unit. The following firewall allows only the
WinProxy server to contact the Internet : 1. Create a new Firewall profile and select Drop for all protocols
2. Under Custom create a new Firewall Entry
3. In Notes enter the name of the server allowed. Then use the default settings except in Local IP Address enter the IP
address of the WinProxy Server, in Local IP Mask enter 255.255.255.255 and in Direction select Both Directions.
Stopping PINGs
You wish to stop pings - this is ICMP Filtering. Using the data below can create a firewall filter that performs the following;
Trap Pings; Trap Ping Replies; Trap Both.
· Trap Pings: Protocol = 1, offset = 20, data = 08, mask = FF
· Trap Ping Replies: Protocol = 1, offset = 20, data = 00, mask = FF
· Trap Both: Protocol = 1, offset = 20, data = 00, mask = F7, Traps Both.
Manager Manager 8.1
Manager
Page 365
15-601011 Issue 25l (11 February 2011)
5.16.3 Static NAT
The Static NAT table allows the firewall to perform address translation between selected internal and external IP
addresses. Up to 64 internal and external IP address pairs can be added to the Static NAT section of a Firewall Profile.
This feature is intended for incoming maintenance access using applications such as PC-Anywhere, Manager and the
Voicemail Pro Client. The address translation is used for destinations such a Voicemail Pro server or the system's own
LAN1 address.
· If there are any entries in the Static NAT settings of a Firewall Profile, each packet attempting to pass through the
firewall must match one of the static NAT pairs or else the packet will be dropped.
· The destination address of incoming packets is checked for a matching External IP Address. If a match is found,
the target destination address is changed to the corresponding Internal IP Address.
· The source address of outgoing packets is checked for a matching Internal IP Address. If a match is found, the
source address is changed to the corresponding External IP Address.
· Even when a static NAT address match occurs, the other settings on the Firewall Profile Standard
364 tabs are still applied and may block the packet.
Manager Manager 8.1
Manager
363
and Custom
Page 366
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Firewall Profile Settings
5.17 IP Route Settings
The system acts as the default gateway for its DHCP clients. It can also be specified as the default gateway
for devices with static IP addresses on the same subnet as the system. When devices on LAN1 and LAN2 want
to send data to IP addresses on a different subnet, they will send that data to their default gateway for
onward routing.
The IP Route table is used by the system to determine where data traffic should be forwarded. This is done by matching
details of the destination IP address to IP Route entries and then using the Destination specified by the matching IP route.
These are referred to as 'static routes'.
· Automatic Routing (RIP)
The system can support RIP (Routing Information Protocol) on LAN1 and or LAN2. This is a method through which the
system can automatically learn routes for data traffic from other routers that also support matching RIP options, see RIP
369 . These are referred to as 'dynamic routes'.
· Dynamic versus Static Routes
By default, static routes entered into the system override any dynamic routes it learns by the use of RIP. This behavior
is controlled by the Favor RIP Routes over static routes option on the System | System 143 tab.
· Static IP Route Destinations
The system allows the following to be used as the destinations for IP routes:
· LAN1 148
Direct the traffic to the system's LAN1.
· LAN2 155
On Small Office Edition, IP412, IP500 and IP500v2 systems, traffic can be directed to LAN2. For Manager 4.1+, LAN
port 8 on IP406 V2 control units can be enabled as LAN2.
· Service 331
Traffic can be directed to a service. The service defines the details necessary to connect to a remote data service.
· Logical LAN 385
Traffic can be directed to a logical LAN already added to the configuration.
· Tunnel 380
Traffic can be directed to an IPSec or L2TP tunnel.
· Default Route
The system provides two methods of defining a default route for IP traffic that does not match any other specified
routes. Use either of the following methods:
· Default Service
Within the settings for services, one service can be set as the Default Route (Service | Service
332 ).
· Default IP Route
Create an IP Route entry with a blank IP Address and blank IP Mask set to the required destination for default traffic.
Manager Manager 8.1
Manager
Page 367
15-601011 Issue 25l (11 February 2011)
5.17.1 IP Route
This tab is used to setup static IP routes from the system. These are in addition to RIP if RIP is enabled on LAN1 and or
LAN2. Up to 100 routes are supported.
IP Route | IP Route
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· IP Address
The IP address to match for ongoing routing. Any packets meeting the IP Address and IP Mask settings are routed to
the entry configured in the Destination field. When left blank then an IP Address of 255.255.255.255 (all) is used.
· IP Mask
The Subnet Mask used to mask the IP Address for ongoing route matching. If blank the mask used is 255.255.255.255
(all).
· A 0.0.0.0 entry in the IP Address and IP Mask fields routes all packets for which there is no other specific IP Route
available. The Default Route option with Services 332 can be used to do this if a blank IP route is not added.
· Gateway IP Address: Default = Blank
The address of the gateway where packets for the above address are to be sent. If this field is set to 0.0.0.0 or is left
blank then all packets are just sent down to the Destination specified, not to a specific IP Address. This is normally only
used to forward packets onto another Router on the local LAN.
· Destination
Allows selection of LAN1, LAN2 (if supported) and any configured Service, Logical LAN or Tunnel (L2TP only).
· Metric: Default = 0
The number of "hops" this route counts as.
· Proxy ARP: Default = Off
This allows the system to respond on behalf of this IP address when receiving an ARP request.
Manager Manager 8.1
Manager
Page 368
15-601011 Issue 25l (11 February 2011)
Configuration Settings: IP Route Settings
5.17.2 RIP
Routing Information Protocol (RIP) is a protocol which allows routers within a network to exchange routes of which they
are aware approximately every 30 seconds. Through this process, each router adds devices and routes in the network to
its routing table.
Each router to router link is called a 'hop' and routes of up to 15 hops are created in the routing tables. When more than
one route to a destination exists, the route with the lowest metric (number of hops) is added to the routing table.
When an existing route becomes unavailable, after 5 minutes it is marked as requiring 'infinite' (16 hops). It is then
advertised as such to other routers for the next few updates before being removed from the routing table. The system
also uses 'split horizon' and 'poison reverse'.
RIP is a simple method for automatic route sharing and updating within small homogeneous networks. It allows alternate
routes to be advertised when an existing route fails. Within a large network the exchange of routing information every 30
seconds can create excessive traffic. In addition the routing table held by each system is limited to 100 routes (including
static and internal routes).
RIP is supported with system's from Level 2.0 upwards. The normal default is for RIP to be disabled. It can be enabled on
LAN1, LAN2 and individual services.
· Listen Only (Passive):
The system listens to RIP1 and RIP2 messages and uses these to update its routing table. However the system does not
respond.
· RIP1:
The system listens to RIP1 and RIP2 messages. It advertises its own routes in a RIP1 sub-network broadcast.
· RIP2 Broadcast (RIP1 Compatibility):
The system listens to RIP1 and RIP2 messages. It advertises its own routes in a RIP2 sub-network broadcast. This
method is compatible with RIP1 routers.
· RIP2 Multicast:
The system listens to RIP1 and RIP2 messages. It advertises its own routes to the RIP2 multicast address (249.0.0.0).
This method is not compatible with RIP1 routers.
Broadcast and multicast routes (those with addresses such as 255.255.255.255 and 224.0.0.0) are not included in RIP
broadcasts. Static routes (those in the IP Route table) take precedence over a RIP route when the two routes have the
same metric.
Manager Manager 8.1
Manager
Page 369
15-601011 Issue 25l (11 February 2011)
5.18 Least Cost Routing Settings
Summary: Least cost routes allow short code matching on the number being dialed from the system rather
than the number originally dialed by the user or application.
For IP Office 4.0, Least Cost Routes have been replaced by ARS 407 . When a system is upgraded to IP Office
4.0, the LCR entries are automatically replaced by ARS entries and appropriate short codes.
When a line, user, user rights or system short code results in a number to be dialed
off-switch, the resulting telephone number to be dialed can be further processed by
matching to Least Cost Route (LCR) short codes.
LCR short codes are grouped in sets. Within each set, the short codes are grouped
into tabs called Main Route, Alternate Route 1 and Alternate Route 2. Each tab also
has a priority and a timeout setting.
· Using a Time Profile
Each LCR set can have an associated time profile. LCR sets without a time profile
are active all the time. LCR sets with a time profile are only active within the times
defined by that profile.
· Which Number is Used For Matching
The telephone number output by the original matched short code is checked
against the Main Route tab short codes of the active LCR sets.
· If a match is found, that set is used for processing.
· If no match is found, the calls is dialed without LCR.
· Returning Busy
If the LCR short code match is set to the Busy feature:
· If the user's priority is higher than the LCR tabs, the system will immediately
look for a matching short code on the next tab and use that short code if
found.
· Otherwise the user receives busy tone.
· Switching Outgoing Line Groups
If the LCR short code match is a dial feature, the system will attempt to seize a
line from the outgoing line group specified by the LCR short code.
· If a line cannot be seized within the time specified on the LCR tab, the system
will look in the next tab for an alternate LCR short code match. If an alternate
match is found it is used.
Manager Manager 8.1
Manager
Page 370
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Least Cost Routing Settings
Least Cost Routing Example
Site A has two outgoing line groups. Outgoing line group 0 contains external lines to the public telephone network.
Outgoing line group 1 contains private lines to Site B.
Requirements
· Scenario 1
The external public number for Site B is 123456. The internal speed dial number is 600. When a user dials 600, the
administrator want the call to be routed by the private lines if possible.
· Scenario 2
The sales hot line at Site B has the public number 654321. The administrator only want high priority users at Site A to
be able to dial that number to test its performance.
Settings
· System Short Code 1: 600/123456/Dial/0.
· System Short Code 2: 654321/N/Dial/0.
· User 1: Priority 2. User 2: Priority 4.
Least Cost Route "SiteB"
Main Route
Alternate Route 1
Timeout
10
30
Priority
3
5
Short Codes
123456/N/Dial/1
123456/N/Dial/0
654321/N/Busy
654321/N/Dial/0
Effects
Scenario 1
When a user dials 123456, it matches system short code 1. That short code specifies dialing Site B via the public lines
(Outgoing line group 0).
The number to be dialed is checked against the least cost routing Main Route tabs for any match. In this example a match
occurs in the SiteB least cost route. The short code there specifies dialing the number using the private lines (Outgoing
line group 1).
If the system cannot seize a line for the call from that group within 10 seconds, it looks for an alternate short code match
in Alternate Route 1 tab of the Site B least cost route. In this example that match changes the call to using the public lines
(Outgoing line group 0).
Scenario 2
When a user dials 654321, it matches system short code 2. That short code specifies dialing the Site B sale hot line
number via the public lines (Outgoing line group 0).
Since this short code is set to a Dial feature, the number to be dialed is checked against the least cost routing Main Route
tabs for any match. In this example a match occurs in the SiteB least cost route. The short code there specifies Busy and
so returns busy to callers.
User 1 has a priority of 2. They will receive busy tone when they dial 654321.
User 2 has a priority of 4 which is higher than the Main Route tab in the Site B least cost route. Therefore the system will
immediately check for a further match in the Alternate Route 1 tab. In this example the short code match for 654321 in
the Alternate 1 tab allows the number to be dialed to the public lines.
Manager Manager 8.1
Manager
Page 371
15-601011 Issue 25l (11 February 2011)
5.18.1 LCR
Least Cost Routing | LCR
Control Unit
SOE
Software Level
1.0 to 3.2 only.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Name
The name to identify the LCR set.
· Time Profile: Default = Blank
Selects a time profile 360 that is used to define when this least cost route can be used. If no profile is selected the route
settings apply at all times.
5.18.2 Main Route
This tab is used for the initial short code matching. The match is performed on the telephone number outputs by a Line,
User, User Rights or System short code that resulted in a number to dial. If a match is found it is used, otherwise the call
is dialed using the original short code.
Least Cost Routing | Main Route
Control Unit
SOE
Software Level
1.0 to 3.2 only.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Timeout (secs): Default = 30 seconds. Range = 1 to 99999 seconds or 0 (No IP trunk fallback).
If an LCR short code match is found, the system will attempt to seize a line in the outgoing line group specified by that
short code. If, after this timeout period has expired, the system still cannot seize a line, it will look for a alternate short
code match in the Alternate Route 1 373 tab.
· Priority: Default = 5, Range 1 (lowest) to 5 (highest).
Normally, if the LCR short code match is a short code set to Busy, the user will receive busy tone. For users whose own
Priority 264 setting (User | User | Priority) is higher than the Main Route tab's, the system will look for an alternate short
code match in the Alternate Route 1 373 tab.
· Allow Bump: Default = Off
When a line indicated by the LCR short code match cannot be seized because lines in that outgoing line group are being
used for a multilink PPP data call, this options allows a line to be seized from the data call.
· Short Code List
These are the short codes used for matching against the telephone number output Line, User, User Right or System dial
short code.
· The only short code features that should be used in a Least Cost Route short code are: Dial, Dial3K1, Dial56K,
Dial64K, DialEmergency, DialSpeech, DialV110, DialV120, DialVideo and Busy.
· The ; character and [ ] characters cannot be used.
· Short codes can be added and edited using the Add, Remove and Edit buttons. Alternatively you can right-click on
the list of existing short code to add and edit short codes.
Manager Manager 8.1
Manager
Page 372
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Least Cost Routing Settings
5.18.3 Alternate Route 1
This tab of a Least Cost Route is used in the following cases:
· The short code match on the Main Route
372
tab is set to Busy but the user has a higher priority than that tab.
· The Main Route 372 tab timeout has expired while trying to seize a line from the outgoing line group specified by the
short code match on that tab.
In either case the system will look for an alternate short code match on this tab. The match is performed on the telephone
number outputs by a Line, User, User Rights or System short code that resulted in a number to dial. If a match is found it
is used, otherwise the call receives busy.
Least Cost Routing | Alternate Route 1
Control Unit
SOE
Software Level
1.0 to 3.2 only.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Timeout (secs): Default = 30 seconds. Range = 1 to 99999 seconds or 0 (No IP trunk fallback).
If an LCR short code match is found, the system will attempt to seize a line in the outgoing line group specified by that
short code. If, after this timeout period has expired, the system still cannot seize a line, it will look for a alternate short
code match in the Alternate Route 2 374 tab.
· Priority: Default = 5, Range 1 (lowest) to 5 (highest).
Normally, if the LCR short code match is a short code set to Busy, the user will receive busy tone. For users whose own
Priority 264 setting (User | User | Priority) is higher than the Main Route tab's, the system will look for an alternate short
code match in the Alternate Route 2 374 tab.
· Allow Bump: Default = Off
When a line indicated by the LCR short code match cannot be seized because lines in that outgoing line group are being
used for a multilink PPP data call, this options allows a line to be seized from the data call.
· Short Code List
These are the short codes used for matching against the telephone number output Line, User, User Right or System dial
short code.
· The only short code features that should be used in a Least Cost Route short code are: Dial, Dial3K1, Dial56K,
Dial64K, DialEmergency, DialSpeech, DialV110, DialV120, DialVideo and Busy.
· The ; character and [ ] characters cannot be used.
· Short codes can be added and edited using the Add, Remove and Edit buttons. Alternatively you can right-click on
the list of existing short code to add and edit short codes.
Manager Manager 8.1
Manager
Page 373
15-601011 Issue 25l (11 February 2011)
5.18.4 Alternate Route 2
This tab of a Least Cost Route is used in the following cases:
· The short code match on the Alternate Route 1
tab.
373
tab is set to Busy but the user has a higher priority than that
· The Alternate Route 1 373 tab timeout has expired while trying to seize a line from the outgoing line group specified
by the short code match on that tab.
In either case the system will look for an alternate short code match on this tab. The match is performed on the telephone
number outputs by a Line, User, User Rights or System short code that resulted in a number to dial. If a match is found it
is used, otherwise the call receives busy.
Least Cost Routing | Alternate Route 2
Control Unit
SOE
Software Level
1.0 to 3.2 only.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Timeout (secs)
Not used. This is the last tab within a Least Cost Route.
· Priority
Not used. This is the last tab within a Least Cost Route.
· Allow Bump: Default = Off
When a line indicated by the LCR short code match cannot be seized because lines in that outgoing line group are being
used for a multilink PPP data call, this options allows a line to be seized from the data call.
· Short Code List
These are the short codes used for matching against the telephone number output Line, User, User Right or System dial
short code.
· The only short code features that should be used in a Least Cost Route short code are: Dial, Dial3K1, Dial56K,
Dial64K, DialEmergency, DialSpeech, DialV110, DialV120, DialVideo and Busy.
· The ; character and [ ] characters cannot be used.
· Short codes can be added and edited using the Add, Remove and Edit buttons. Alternatively you can right-click on
the list of existing short code to add and edit short codes.
Manager Manager 8.1
Manager
Page 374
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Least Cost Routing Settings
5.19 Account Code Settings
Account codes are commonly used to control cost allocation and out-going call restriction. The account code
used on a call is included in the call information output by the system's call log. Incoming calls can also trigger
account codes automatically by matching the Caller ID stored with the account code.
Once a call has been completed using an account code, the account code information is removed from the user's call
information. This means that redial functions will not re-enter the account code. The maximum recommended number of
accounts codes is 1000.
Setting a User to Forced Account Code
1. Receive the system configuration if one is not opened.
2. In the left-hand panel, click
User. The list of existing user is shown in the right-hand panel.
3. Double-click the required user.
4. Select the Telephony tab.
5. Tick the Force Account Code option.
6. Click OK.
7. Merge the configuration.
Forcing Account Code Entry for Specific Numbers
Account code can be set a being required for any dialing that matches a particular short code. This is done by ticking the
Force Account Code option found in the short code settings. Note that the account code request happens when the short
code match occurs. Potentially this can be in the middle of dialing the external number, therefore the use of X wildcards in
the short code to ensure full number dialing is recommended.
Entering Account Codes
The method for entering account codes depends on the type of phone being used. Refer to the relevant telephone User's
Guide for details.
· Account Code Button
The Account Code Entry 575 action (User | Button Programming | Emulation | Account Code Entry) and Set
Account Code 492 action (User | Button Programming | Advanced | Set | Set Account Code) can be assigned to
a programmable button on some phones. They both operate the same. The button can be preset with a specific account
code or left blank to request account code entry when pressed. The button can then be used to specify an account code
before a call or during a call.
· Phone Manager
The Phone Manager application can be used to enter account codes before or during calls. For full details refer to the
Phone Manager documentation.
· To enter an account code before making a call or during a call select Actions | Account Code. A valid account code
can then be selected from the Account Code drop down.
· The Account Codes tab can be used to create icons to speed dial specific numbers and account codes that are
regularly used.
· Setting an Account Code using Short Codes
The Set Account Code feature allows short codes to be created that specify an account code before making a call.
· Show Account Code Setting 160 (System | Telephony | Telephony 160 )
This setting controls the display and listing of system account codes:
· When on:
· When entering account codes through Phone Manager, users can select from a drop-down list of available
account codes.
· When entering account codes through a phone, the account code digits are shown while being dialed.
· When off:
· Within Phone Manager the drop-down list of available account codes is not useable, instead account codes must
be entered using the Phone Managers PIN Code features.
· When entering account codes through a phone, the account code digits are replaced by s characters on the
display.
Manager Manager 8.1
Manager
Page 375
15-601011 Issue 25l (11 February 2011)
5.19.1 Account Code
This tab is used to define an individual account code.
Account Code | Account Code
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Account Code
Enter the account code required. The code can include alphabetic characters for users dialing via Phone Manager. It can
also include wildcards; ? matches a single digit and * matches any digits.
· Caller ID
A caller ID can be entered and used to automatically assign an account code to calls made to or received from caller ID.
5.19.2 Voice Recording
This tab is used to activate the automatic recording of external calls when the account code is entered at the start of the
call or automatically assigned by call ID matching when the call is received.
Call recording requires Voicemail Pro to be installed and running. Call recording also requires available conference
resources similar to a 3-way conference.
· IP Office 4.0+ introduces the following changes to recording:
· Calls to and from IP devices, including those using Direct media, can be recorded.
· Calls parked or held pause recording until the unparked or taken off hold.
· Recording is stopped if:
· User recording stops if the call is transferred to another user.
· User account code recording stops if the call is transferred to another user.
· Hunt group recording stops if the call is transferred to another user who is not a member of the hunt
group.
· Incoming call route recording continues for the duration of the call on the system.
· IP Office 4.1+: The destination mailbox for the recording can be specified.
Account Code | Voice Recording
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Record Outbound: Default = None
Select whether automatic recording of outgoing calls is enabled. The Auto Record Calls option sets whether just
external calls or external and internal calls are included. Options for recording are:
· None: Do not automatically record calls.
· On: Record the call if possible. If not possible to record, allow the call to continue.
· Mandatory: Record the call if possible. If not possible to record, block the call and return busy tone.
· Percentages of calls: Record a selected percentages of the calls.
· Record Inbound: Default = None
Select whether automatic recording of incoming calls is enabled. Options for recording are:
· None: Do not automatically record calls.
· On: Record the call if possible. If not possible to record, allow the call to continue.
Manager Manager 8.1
Manager
Page 376
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Account Code Settings
· Mandatory: Record the call if possible. If not possible to record, block the call and return busy tone.
· Percentages of calls: Record a selected percentages of the calls.
· Record Time Profile: Default = <None> (Any time)
Used to select a time profile 360 during which automatic call recording of incoming calls is applied. If no profile is
selected, automatic recording of incoming calls is active at all times.
· Recording (Auto): Default = Mailbox
Sets the destination for automatically triggered recordings.
· Mailbox
This option sets the destination for the recording to be a selected user or hunt group mailbox. The adjacent drop
down list is used to select the mailbox.
· Voice Recording Library: Software level = 3.0+.
This options set the destination for the recording to be a VRL folder on the voicemail server. The ContactStore
application polls that folder and collects waiting recordings which it then places in its own archive. Recording is still
done by the Voicemail Pro.
· Auto Record Calls: Default = External. Software level = 6.1
This setting allows selection of whether External or External & Internal calls are subject to automatic call recording.
Manager Manager 8.1
Manager
Page 377
15-601011 Issue 25l (11 February 2011)
5.20 License
This form is used to display the function, value and status of license keys entered into the system
configuration. License keys are 32 character strings uniquely based on the feature they active and the serial
number of a Feature Key dongle being used by the control unit.
The serial number is printed on the feature key dongle and prefixed with SN (FK for IP500v2 SD card
dongles). It can also be viewed in the system configuration by selecting System | System | Dongle Serial
Number.
Feature Key dongles are available in several types. Each system only supports license validation against a single dongle
and vice versa. The licenses in the systems configuration must match the serial number of the Feature Key dongle.
Depending on the dongle type, it is installed either directly on the control unit or onto a PC running the Feature Key Server
application.
· Each will only support license validation against one feature key dongle.
· If being used, a Feature Key Server PC will only validate licenses for the first system to which it connects after starting.
· For parallel and USB feature keys, the address of the PC hosting the dongle and running the Feature Key Server
software is set by the License Server IP Address setting on the System | System 143 tab. For serial key dongles, the
address is set to 0.0.0.0.
· Note that for IP500 and IP500v2 control units, a Feature Key dongle must be present even if no licensed features are
being used.
· The serial number and whether the control unit has an local (serial or smart card) or remote (parallel or USB) Feature
Key dongle are indicated by the Dongle Serial Number field on the System | System 143 tab.
· For IP Office 6.0and higher, feature key dongles using the Feature Key server application are not supported.
Feature Key Dongle
Serve License SOE IP40 IP40 IP40 IP412 IP500 IP500
r PC Server IP
3
6 V1 6 V2
v2
Address
143
Parallel
This type of feature key dongle is
plugged into the parallel port of a PC
running the Feature Key Server
software.
255.255.2
55.255 or
server PC
address.
–
–
USB
This type of feature key dongle is
plugged into the USB port of a PC
running the Feature Key Server
software.
255.255.2
55.255 or
server PC
address.
–
–
–
–
Serial
This type of feature key dongle is
plugged into the 9-pin serial port on the
back of Small Office Edition and IP406
V2 control units. No separate PC running
Feature Key software is required.
0.0.0.0
Smart Card
This type of feature key dongle, a creditcard sized memory card, is plugged into
IP500 control units.
Not used.
SD Memory Card
This type of feature key dongle is
plugged into IP500v2 control units.
Not used.
–
–
–
–
–
–
–
–
–
–
–
–
–
–
Importing License Keys
It is recommended that licenses are cut and pasted electronically. This removes the chances of errors due to mistyping
and misinterpretation of characters fonts. Where multiple licenses need to be added, the CSV import option can be used (
File | Import/Export | Import). Licenses imported this way may be listed as invalid until the configuration is saved and
then reloaded
Manager Manager 8.1
Manager
Page 378
15-601011 Issue 25l (11 February 2011)
Configuration Settings: License
License | License
Control Unit
SOE
Software Level
1.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· License Key
This field is used to enter the 32-character license key.
· License Type
For information only. If the key is recognized, its function will be listed here. Invalid indicates that the License Key has
not been recognized as enabling any feature, regardless of the Feature Key dongle serial number. For a list of licenses
and their purpose refer to the Manager Installation manual.
· License Status
For information only. This field indicates the current validation status of the license key against the serial number of the
Feature Key dongle being used by the system.
· Unknown is shown for newly entered licenses until the configuration is sent to the system and then retrieved again.
· Valid is shown if the license key matches the Feature Key dongle serial number.
· Invalid is shown if the license key does not match the Feature Key dongle serial number.
· Dormant is shown if the license key is valid but is conditional on another license that is not present.
· Obsolete is shown if the license key is valid but the license is no longer used by the version of software installed in
the system.
· Expired is shown if the license has passed its expiry date.
· Instances
For information only. Some licenses enable a number of port, channels or users. When that is the case, the number of
such is indicated here. Multiple licenses for the same feature are usually cumulative.
· Expiry Date
For information only. License can be set to expire within a set period from their issue by Avaya. The expiry date is
shown here.
Manager Manager 8.1
Manager
Page 379
15-601011 Issue 25l (11 February 2011)
5.21 Tunnel Settings
Tunneling allows additional security to be applied to IP data traffic. This is useful when sites across an unsecure
network such as the public internet. The system supports two methods of tunneling, L2TP and IPSec. Once a
tunnel is created, it can be used as the destination for selected IP traffic in the IP Route 368 table.
Two types of tunneling are supported:
·
L2TP - Layer 2 Tunneling Protocol 381
PPP (Point to Point Protocol) authentication normally takes place between directly connected routing devices. For
example when connecting to the internet, authentication is between the customer router and the internet service
provider's equipment. L2TP allows additional authentication to be performed between the routers at each end of the
connection regardless of any intermediate network routers. The use of L2TP does not require a license.
·
IPSec 383
IPSec allows data between two locations to be secured using various methods of sender authentication and or data
encryption. The use of IPSec requires entry of an IPSec Tunneling license into the system at each end.
Manager Manager 8.1
Manager
Page 380
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Tunnel Settings
5.21.1 L2TP Tunnel
5.21.1.1 Tunnel
Tunnel | Tunnel (L2TP)
Control Unit
SOE
Software Level
2.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Name: Default = Blank.
A unique name for the tunnel. Once the tunnel is created, the name can be selected as a destination in the IP Route
table.
· Local Configuration
The account name and password is used to set the PPP authentication parameters.
· Local Account Name
The local user name used in outgoing authentication.
· Local Account Password/Confirm Password
The local user password. Used during authentication.
· Local IP Address
The source IP address to use when originating an L2TP tunnel. By default (un-configured), the system uses the IP
address of the interface on which the tunnel is to be established as the source address of tunnel.
· Remote Configuration
The account name and password is used to set the PPP authentication parameters.
· Remote Account Name
The remote user name that is expected for the authentication of the peer.
· Remote Account Password/Confirm Password
The password for the remote user. Used during authentication.
· Remote IP Address
The IP address of the remote L2TP peer or the local VPN line IP address or the WAN IP address.
· Minimum Call Time (Mins): Default = 60 minutes, Range = 1 to 999.
The minimum time that the tunnel will remain active.
· Forward Multicast Messages: Default = On
Allow the tunnel to carry multicast messages when enabled.
· Encrypted Password: Default = Off
When enabled, the CHAP protocol is used to authenticate the incoming peer.
Manager Manager 8.1
Manager
Page 381
15-601011 Issue 25l (11 February 2011)
5.21.1.2 L2TP
Tunnel | L2TP
Control Unit
SOE
Software Level
2.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Shared Secret/Confirm Password
User setting used for authentication. Must be matched at both ends of the tunnel. This password is separate from the
PPP authentication parameters defined on the L2TP|Tunnel 381 tab.
· Total Control Retransmission Interval: Default = 0, Range = 0 to 65535.
Time delay before retransmission.
· Receive Window Size: Default = 4, Range = 0 to 65535.
The number of unacknowledged packets allowed.
· Sequence numbers on Data Channel: Default = On
When on, adds sequence numbers to L2TP packets.
· Add checksum on UDP packets: Default = On.
When on, uses checksums to verify L2TP packets.
· Use Hiding: Default = Off
When on, encrypts the tunnel's control channel.
5.21.1.3 PPP
Tunnel | PPP (L2TP)
Control Unit
SOE
Software Level
2.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· CHAP Challenge Interval (secs): Default = 0 (Disabled), Range = 0 to 99999 seconds.
Sets the period between CHAP challenges. Blank or 0 disables repeated challenges. Some software (such as Windows 95
DUN) does not support repeated challenges.
· Header Compression: Default = None
Select header compression. Options are: IPHC and/or VJ.
· PPP Compression Mode: Default = MPPC
Select the compression mode for the tunnel connection. Options are: Disable, StacLZS or MPPC.
· Multilink / QoS: Default = Off
Enable the use of Multilink protocol (MPPC) on the link.
· Incoming traffic does not keep link up: Default = On
When enabled, the link is not kept up when the only traffic is incoming traffic.
· LCP Echo Timeout (secs): Default = 6, Range = 0 to 99999 seconds.
When a PPP link is established, it is normal for each end to send echo packets to verify that the link is still connected.
This field defines the time between LCP echo packets. Four missed responses in a row will cause the link to terminate.
Manager Manager 8.1
Manager
Page 382
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Tunnel Settings
5.21.2 IP Security Tunnel
5.21.2.1 Main
Tunnnel | Main (IPSec)
Control Unit
SOE
Software Level
2.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Name: Default = Blank.
A unique name for the tunnel. Once the tunnel is created, the name can be selected as a destination for traffic in the IP
Route 368 table.
· Local Configuration
The IP Address and IP Mask are used in conjunction with each other to configure and set the conditions for this Security
Association (SA) with regard to inbound and outbound IP packets.
· IP Address
The IP address or sub-net for the start of the tunnel.
· IP Mask
The IP mask for the above address.
· Tunnel Endpoint IP Address
The local IP address to be used to establish the SA to the remote peer. If left un-configured, the system will use the
IP address of the local interface on which the tunnel is to be configured.
· Remote Configuration
The IP Address and IP Mask are used in conjunction with each other to configure and set the conditions for this Security
Association (SA) with regard to inbound and outbound IP packets.
· IP Address
The IP address or sub-net for the end of the tunnel.
· IP Mask
The IP mask for the above address.
· Tunnel Endpoint IP Address
The IP address of the peer to which a SA must be established before the specified local and remote addresses can be
forwarded.
5.21.2.2 IKE Policies
Tunnel | LKE Policies (IPSec)
Control Unit
SOE
Software Level
2.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Shared Secret/Confirm Password
The password used for authentication. This must be matched at both ends of the tunnel.
· Exchange Type: Default = ID Prot
Aggressive provides faster security setup but does not hide the ID's of the communicating devices. ID Prot is slower
but hides the ID's of the communicating devices.
· Encryption: Default = DES CBC
Select the encryption method used by the tunnel. The options are: DES CBC, 3DES or Any.
· Authentication: Default = MD5
The method of password authentication. Options are: MD5, SHA or Any.
· DH Group: Default = Group 1
· Life Type: Default = KBytes
Sets whether Life (below) is measured in seconds or kilobytes.
· Life: Range = 0 to 99999999.
Determines the period of time or the number of bytes after which the SA key is refreshed or re-calculated.
Manager Manager 8.1
Manager
Page 383
15-601011 Issue 25l (11 February 2011)
5.21.2.3 IPSec Policies
Tunnel | IPSec Policies
Control Unit
SOE
Software Level
2.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Protocol: Default = ESP
ESP (Encapsulated Security Payload) or AH (Authentication Header, no encryption).
· Encryption: Default = DES
Select the encryption method used by the tunnel. The options are: DES CBC, 3DES or Any.
· Authentication: Default = HMAC MD5
The method of password authentication. Options are: HMAC MD5, HMAC SHA or Any.
· Life Type: Default = KBytes
Sets whether Life (below) is measured in seconds or kilobytes.
· Life
Determines the period of time or the number of bytes after which the SA key is refreshed or re-calculated.
Manager Manager 8.1
Manager
Page 384
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Tunnel Settings
5.22 Logical LAN
A logical LAN can be used on control units with only a single LAN (LAN1) . A logical LAN allows these systems to
support a second separately addressed LAN on the same interface. Traffic between the system LAN1 and the
logical LAN can then be controlled by the system's IP route table and firewalls. Logical LAN settings are not
supported in IP Office 6.1+.
Logical LAN | Logical LAN
Control Unit
SOE
Software Level
2.0 to 6.0.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Name: Default = Blank. Range = Up to 31 characters.
A unique name for the logical LAN. This name becomes selectable as a destination in the IP Route table.
· IP Address: Default = 0.0.0.0
The IP address provided by the internet service provider for the logical LAN.
· IP Mask: Default = 0.0.0.0
The IP address mask provided by the internet service provider for the logical LAN.
· Gateway IP Address: Default = 0.0.0.0
The IP address of the router on the logical LAN.
· Gateway Mac Address: Default = 00:00:00:00:00:00
The MAC address of the router. If the MAC address isn't known, from a PC that can ping the router's IP address, use the
command arp -a <ip address>.
· Firewall Profile: Default = Blank
This field allows selection of an existing firewall profile that should be applied to traffic to and from the logical LAN.
· Enable NAT: Default = On (Grayed out).
NAT is applied to all traffic from the system LAN to the logical LAN. The use of NAT is not compatible with H.323 VoIP
operation, therefore a VPN tunnel should also be applied to traffic being routed
Manager Manager 8.1
Manager
Page 385
15-601011 Issue 25l (11 February 2011)
5.23 Wireless Settings
The Small Office Edition control unit can act as an 802.11b wireless access point. To do this requires the
insertion of an Avaya supplied wireless card into one of the control unit's PCMCIA slots and entry of a Small
Office Edition WiFi license into the configuration. The Manager Wireless settings can then be configured.
In order to connect to the Manager LAN, wireless devices must be configured to match the Manager Wireless settings.
Additionally the wireless device must match the control unit's LAN1 or LAN2 network settings unless using DHCP.
5.23.1 SSID
This tab is used to set the general identity of the wireless connection to the system LAN.
Wireless | SSID
Control Unit
SOE
Software Level
2.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Network Name: Default = IP Office Wireless.Net
A unique name used to identify and distinguish the system wireless LAN from other wireless LAN's. This is the wireless
LAN's Service Set Identifier (SSID).
· Wireless Mac Address
Displays a list of the MAC addresses of the devices currently connected to the wireless LAN.
· Frequency/Channel: Default = 6
The 802.11b wireless frequency band is sub-divided into a number of channels. In locations where there are multiple
wireless LAN's or multiple access points to the same wireless LAN, each access point should use a separate channel.
Devices connecting to a wireless LAN will automatically connect to the channel providing the strongest signal.
· The number of channels available is country specific. In the US channels 1 to 11 are available. In most of Europe,
channels 1 to 13 are available. In Japan only channel 14 is available.
· The channel frequencies overlap. For instance, channel 2 shares part of the same frequency band as channels 1 and
3. In areas with multiple access points or LAN, use widely spaced channels. For example uses channels 1, 6 and 11
on different access points.
· Accept Any: Default = Off
If on, allows any wireless device to connect to the wireless LAN without having to have a matching wireless network
name (SSID) set. When off, only devices configured with a matching wireless network name can connect to the wireless
LAN.
5.23.2 Security
This tab allows for additional security through the use of WEP wireless encryption keys. If enabled, in addition to
encrypting the wireless traffic, only devices using a matching encryption key can connect to the wireless LAN.
Wireless | Security
Control Unit
SOE
Software Level
2.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Encryption: Default = Disabled
Allows selection of 50/64 bit or 128 bit security. Note: 50/64 bit encryption is also know as 40/64 encryption in some
locales.
· Alpha/Hex: Default = Hex
Switch key entry between hexadecimal and alphabetic entry modes.
· Key 1/4
Allows entry of the security key and selection of which key is the current key to use.
Manager Manager 8.1
Manager
Page 386
15-601011 Issue 25l (11 February 2011)
Configuration Settings: Wireless Settings
5.24 User Restrictions Settings
User Restrictions are only available in pre-IP Office 3.2 configurations. For IP Office 3.2 and higher they have been
replaced by User Rights 389 .
Within Manager, users can be grouped by the types of numbers they are allowed to dial or not allowed to dial. For
example, those who are allowed to dial 1900 or international numbers.
The User Restriction form allows named groups of dialing short codes/restrictions to be created. These short codes can
then be applied to a user by associating them with the User Restriction name rather than having to recreate the short
codes for each user.
To set up a restriction within the User Restriction form
1. Click User Restriction form within the Configuration Tree.
2. Enter a name for the restriction.
3. Click the Short Code List tab and create a short code.
4. Merge the configuration.
To apply a User Restriction to a specific user
1. Click the User form within the Configuration Tree.
2. Double-click the user for whom you want this restriction applied.
3. Within the User tab, click the Restriction drop down box and select the User Restriction you want applied to this
user.
4. Merge the configuration.
Manager Manager 8.1
Manager
Page 387
15-601011 Issue 25l (11 February 2011)
5.24.1 User Restrictions
User Restrictions are only available in pre-IP Office 3.2 configurations. For IP Office 3.2 and higher, they have been
replaced by User Rights 389 .
User Restrictions | Restrictions
Control Unit
SOE
Software Level
2.0 to 3.1 only.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Name: Default = Blank
A name used to identify the set of user restrictions and allow its selection through the Restrictions field in each
individual user's User settings.
· Priority: Default = 5 (highest), Range 0 to 5
The priority that should be applied to user calls if routed via a Least Cost Route
individual user.
370 .
This overrides the priority of the
· Outgoing Call Bar: Default = Off.
When on, bars users making external calls.
5.24.2 Short Codes
User Restrictions are only available in pre-IP Office 3.2 configurations. For IP Office 3.2 and higher they have been
replaced by User Rights 389 .
· WARNING
User dialing of emergency numbers must not be blocked by the addition of short codes. If short codes are added, the
users ability to dial emergency numbers must be tested and maintained.
Allows entry of short codes for dialing by associated users. These short codes override any match system short codes but
not individual user short codes.
User Restrictions | Short Codes
Control Unit
SOE
Software Level
2.0 to 3.1 only.
Mergeable
Manager Manager 8.1
Manager
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
Page 388
15-601011 Issue 25l (11 February 2011)
Configuration Settings: User Restrictions Settings
5.25 User Rights Settings
User Rights act as templates for users, locking selected user settings to the template value. For most of the
settings within the user rights tabs, the following options can be selected from an adjacent drop down list. Note
that some settings are grouped and are set and locked as a group.
· Apply User Rights Value
Apply the value set in the user rights to all associated users.
· The matching user setting is grayed out and displays a
lock symbol.
· Users attempting to change the settings using short codes receive inaccessible tone.
· Within the user's Phone Manager the associated fields are grayed out or hidden.
· Not Part of User Rights
Ignore the setting.
Adding User Rights
1. Select
2. Click
User Rights.
and select User Rights.
3. Enter a name.
4. Configure the user rights as required.
5. Click OK.
Creating User Rights Based on an Existing User
1. Select
User Rights.
2. In the group pane, right-click and select New User Rights from User.
3. Select the user and click OK.
Associating User Rights to a User
1. Select
User Rights or
User.
2. In the group pane, right-click and select Apply User Rights to Users.
3. Select the user rights to be applied.
4. On the Members of this User Rights sub tab select the users to which the user rights should be applied as their
Working Hours User Rights.
5. On the Members when out of hours sub tab select which users should use the selected user rights as their out of
hours user rights.
6. Click OK.
or
1. Select the required user to display their settings in the details pane.
2. Select the User tab.
3. Use Working Hours User Rights drop-down to select the user rights required.
4. If required a Working Hours Time Profile and Out of Hours User Rights can be selected.
5. Click OK.
Manager Manager 8.1
Manager
Page 389
15-601011 Issue 25l (11 February 2011)
Copy User Rights Settings over a User's Settings
This process replaces a user's current settings with those that are part of the selected user rights. It does not associate
the user with the user rights.
1. Select
User Rights or
User.
2. In the group pane, right-click and select Copy user rights values to users.
3. Select the user rights to be applied.
4. Click OK.
Default User Rights
For defaulted systems, the following user rights are created as a part of the default configuration. Fields not listed are not
part of the user rights.
= Set to On.
= Set to Off.
User Rights
= Not part of the user rights.
Call Center Boss
Agent
Priority
Application Default
IP Hard
Phone
Mailbox
Paging
T3
5
5
5
5
5
5
5
5
No Answer Time
0
0
0
0
0
0
0
0
Transfer Return Time
0
0
0
0
0
0
0
0
Individual Coverage Time
10
10
10
10
10
10
10
10
Voicemail
Voicemail Ringback
Outgoing Call Bar
Busy on Held
Call Waiting
Can be Intruded
Cannot be Intruded
Force Login
Force Account Code
Button Programming
Manager Manager 8.1
Manager
1:
2:
4:
5:
6:
a=
b=
HGEna
DNDOn
Busy
1:
2:
3:
6:
7:
a=
b=
c=
DNDOn
Dial *17
1: a=
2: b=
3: c=
1:
2:
3:
6:
a=
b=
c=
Dial *17
Page 390
15-601011 Issue 25l (11 February 2011)
Configuration Settings: User Rights Settings
5.25.1 User
This tab is used to set and lock various user settings.
User Rights | User
Control Unit
SOE
Software Level
3.2+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Name
The name for the user rights . This must be set in order to allow the user rights to be selected within the User Rights
drop down list on the User | User 264 tab of individual users.
· Locale: Default = Blank
Sets and locks the language used for voicemail prompts to the user, assuming the language is available on the
voicemail server. On a digital extension it also controls the display language used for messages from the system to the
phone. See Supported Country and Locale Settings 844 .
· Priority: Default = 5, Range 1 (Lowest) to 5 (Highest)
Sets and locks the user's priority setting for least cost routing.
· Do Not Disturb: Default = Off
Sets and locks the user's DND status setting.
· Voicemail On: Default = On
Moved to the Voicemail 399 tab.
· Voicemail Ringback: Default = Off
Moved to the Voicemail 399 tab.
5.25.2 Short Codes
This tab is used to set and lock the user's short code set. The tab operates in the same way as the User | Short Codes
tab. Where the same short code exists in both the User | Short Codes tab and the associated User Rights | Short
Codes tab, the system will use the user short code.
User and User Rights short codes are only applied to numbers dialed by that user. For example they are not applied to
calls forwarded via the user.
· WARNING
User dialing of emergency numbers must not be blocked by the addition of short codes. If short codes are added, the
users ability to dial emergency numbers must be tested and maintained.
User Rights | Short Codes
Control Unit
SOE
Software Level
3.2+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
Short codes can be added and edited using the Add, Remove and Edit buttons. Alternatively you can right-click on the
list of existing short code to add and edit short codes.
Manager Manager 8.1
Manager
Page 391
15-601011 Issue 25l (11 February 2011)
5.25.3 Telephony
This tab allows various user telephony settings to be set and locked. These match settings found on the User |
Telephony 274 tab.
User Rights | Telephony
Control Unit
SOE
Software Level
3.2+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
These settings are divided in to a number of sub-tabs:
· Call Settings
392
· Supervisor Settings
· Multi-line Options
· Call Log
393
394
394
5.25.3.1 Call Settings
User Rights | Telephony
Control Unit
SOE
Software Level
3.2+.
Mergeable
, IP403
, IP406 V1
.
· No Answer Time: Default = Blank (Use system setting), Range = 6 to 99999 seconds.
Sets how long a call rings the user before following forwarded on no answer if set or going to voicemail. Leave blank to
use the system default setting.
· Transfer return Time (secs): Default = Blank (Off), Range 1 to 99999 seconds.
Sets the delay after which any call transferred by the user, which remains unanswered, should return to the user if
possible.
· Wrap up Time (secs): Default = 2 seconds, Range 0 to 99999 seconds.
Specifies the amount of time after ending one call before another call can ring. You may wish to increase this in a "call
center" environment where users may need time to log call details before taking the next call. It is recommended that
this option is not set to less than the default of 2 seconds. 0 is used for immediate ringing.
· Call waiting on/Enable call waiting: Default = Off
For users on phones without appearance buttons, if the user is on a call and a second call arrives for them, an audio
tone can be given in the speech path to indicate a waiting call (the call waiting tone varies according to locale). The
waiting caller hears ringing rather than receiving busy. There can only be one waiting call, any further calls receive
normal busy treatment. If the call waiting is not answered within the no answer time, it follows forward on no answer or
goes to voicemail as appropriate. User call waiting is not used for users on phones with multiple call appearance
buttons. Call waiting can also be applied to hunt group calls, see Hunt Group | Hunt Group | Call Waiting 306 .
· Busy on held/Enable busy on Held: Default = On
If on, when the user has a call on hold, new calls receive busy tone (ringing for incoming analog call) or are diverted to
voicemail if enabled, rather than ringing the user. Note this overrides call waiting when the user has a call on hold.
Manager Manager 8.1
Manager
Page 392
15-601011 Issue 25l (11 February 2011)
Configuration Settings: User Rights Settings
5.25.3.2 Supervisor Settings
User Rights | Telephony
Control Unit
SOE
Software Level
3.2+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Can Intrude: Default = Off
Check this option if the User can interrupt other user's calls. This setting and the setting below are used to control the
use of the following short code and button features: Call Intrude, Call Listen, Call Steal and Dial Inclusion.
· Cannot be Intruded: Default = On
If checked, this user's calls cannot be interrupted or acquired. In addition to the features listed above, this setting also
affects whether other users can use their appearance buttons to bridge into a call to which this user has been the
longest present user.
· Force Login: Default = Off
If checked, the user must log in using their Login Code to use an extension. For example, if Force Login is ticked for
User A and user B has logged into A's phone, after B logs off A must log back. If Force Login was not ticked, A would be
automatically logged back in.
· Force Account Code: Default = Off
If checked, the user must enter a valid account code to make an external call.
· Inhibit Off-Switch Forward/Transfer: Default = Off
When enabled, this setting stops the user from transferring or forwarding calls externally. Note that all user can be
barred from forwarding or transferring calls externally by the System | Telephony | Telephony | Inhibit Off-Switch
Forward/Transfers 160 setting.
· CCR Agent: Default = Off. Software level = 4.2+.
This field is used by the CCR application to indicate which users are Agents monitored by that application. It also
indicate to the system those users who can use other CCR features within the system configuration. If a user is set as
an CCR Agent, Forced Login is enabled and greyed out from being changed and a warning is given if the user does not
have a log in code set.
· WARNING
This setting should not be enabled/disabled for a user by using User Rights associated with a Time Profile. Do so
will cause invalid data to be recorded in the Customer Call Reporter applications database.
· The number of simultaneous logged in CCR Agents supported by the system is controlled by licenses entered into
the configuration. If all CCR Agent licenses on a system have been used, additional agents are prevented from
logging in.
· After Call Work Time: Default = System Default, Range = 10 to 999 seconds. Software level = 4.2+.
CCR Agents (see above) can be automatically put into After Call Work (ACW) state after ending a hunt group call.
During ACW state, hunt group calls are not presented to the user. If set to System Default, the value set in Default
After Call Work 184 (System | CCR) 184 is used.
· Automatic After Call Work: Default = Off. Software level = 4.2+.
For CCR Agents with Automatic After Call Work enabled, this value sets the duration of the ACW period.
· Outgoing Call Bar: Default = Off
When set, bars the user from making external calls.
· Coverage Group: Default = <None>. Software level = 5.0+
If a group is selected, the system will not use voicemail to answer the users unanswered calls. Instead the call will
continue ringing until either answered or the caller disconnects. For external calls, after the users no answer time, the
call is also presented to the users who are members of the selected Coverage Group. For further details refer to
Coverage Groups 748 .
Manager Manager 8.1
Manager
Page 393
15-601011 Issue 25l (11 February 2011)
5.25.3.3 Multi-line Options
User Rights | Telephony
Control Unit
SOE
Software Level
3.2+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Individual Coverage Time (secs): Default = 10 seconds, Range 1 to 99999 seconds.
This function sets how long the phone will ring at your extension before also alerting at any call coverage users. This
time setting should not be equal to or greater than the No Answer Time.
5.25.3.4 Call Log
User Rights | Telephony
Control Unit
SOE
Software Level
5.0+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Centralized Call Log: Default = System Default (On)
This setting allows the use of centralized call logging to be enabled or disabled on a per user basis. The default is to
match the system setting Default Centralized Call Log On 165 (System | Telephony | Call Log 165 ). The other options
are On or Off for the individual user. If off is selected, the call log shown on the users phone is the local call log stored
by the phone.
· Delete entries after (hours:minutes): Default = 00:00 (Never). Software level = 6.1+.
If a time period is set, entries in the user's call log are automatically deleted after this period.
· Groups: Default = System Default (On).
This section contains a list of hunt groups on the system. If the system setting Log Missed Huntgroup Calls 160
(System | Telephony | Call Log) 160 has been enabled, then missed calls for those groups selected are shown as part of
the users call log. The missed calls are any missed calls for the hunt group, not just group calls presented to the user
and not answered by them.
Manager Manager 8.1
Manager
Page 394
15-601011 Issue 25l (11 February 2011)
Configuration Settings: User Rights Settings
5.25.4 Button Programming
This tab is used to set and lock the user's programmable button set. When locked, the user cannot use Admin or Admin1
buttons on their phone to override any button set by their user rights.
Buttons not set through the user rights can be set through the user's own settings.
When Apply user rights value is selected, the tab operates in the same manner as the User | Button Programming
288 tab.
User Rights | Button Programming
Control Unit
SOE
Software Level
3.2+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
Adding Blank Buttons
There are scenarios where users are able to program their own buttons but you may want to force certain buttons to be
blank. This can be done through the user's associated User Rights as follows:
1. Assign the action Emulation | Inspect to the button. Enter some spaces as the button label.
2. When pressed by the user, this button will not perform any action. However it cannot be overridden by the user.
5.25.5 Menu Programming
This tab is used to set and lock the user's programmable button set.
When Apply User Rights value is selected, the tab operates in the same manner as the User | Menu Programming
tab.
289
User Rights | Menu Programming
Control Unit
SOE
Software Level
3.2-4.2.
Mergeable
Manager Manager 8.1
Manager
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
Page 395
15-601011 Issue 25l (11 February 2011)
5.25.6 Phone Manager
This tab is used to set and lock which parts of Phone Manager the associated users can use or adjust.
User Rights | Phone Manager
Control Unit
SOE
Software Level
3.2+.
Mergeable
, IP403
, IP406 V1
, IP406 V2
, IP412
, IP500
, IP500v2
.
.
· Allow user to modify Phone Manager settings: Default = On
This setting is used with the Phone Manager Status Options, Screen Pop Options and Hide Options. It controls whether
those options are applied every time the user starts Phone Manager or only the first time the user starts Phone
Manager.
· If this setting is enabled, then the system configuration setting of those options are only applied the first time a user
starts Phone Manager on a PC. Those settings become part of the user's Phone Manager profile on that PC. They can
be changed by the user through Phone Manager. On subsequent Phone Manager starts the Manager settings are
ignored.
· If this setting is not enabled, the system configuration settings are applied every time the user starts Phone Manager
and cannot be overridden by the user.
· Agent Mode: Default = Off
This option controls the setting of the Agent Mode option on the Configure Preferences | Agent Mode tab within
Phone Manager Pro. When enabled, the user has additional toolbar controls for Busy Wrap Up, Busy Not Available and
Select Group. Note that the options on the Phone Manager Pro Agent Mode tab can be grayed out from user changes by
the Agent Mode setting in Configuration Options below.
· Phone Manager Type: Default = Lite
Determines the mode in which the user's copy of the Phone Manager application operates. This setting cannot be
changed by the user.
· Lite
Basic Phone Manager mode. This mode does not require any licenses.
· Pro
Advanced Phone Manager mode that enables a range of additional functions. This mode requires an available Phone
Manager Pro license, otherwise the application will run in Phone Manager Lite mode.
· Phone Manager PC Softphone
This is the VoIP IP phone mode of Phone Manager Pro. This mode requires both an available Phone Manager Pro
license and a Phone Manager Pro IP Audio Enabled license. The user must be associated with an VoIP extension within
the system configuration.
· Pro Telecommuter: Software level = 4.1+.
This version of Phone Manager Pro is supported with Phone Manager 4.1+. It allows the user to make and receive
calls via an external phone specified at Phone Manager log in. This mode requires an available Phone Manager Pro
license, otherwise the application will run in Phone Manager Lite mode.
· Enable VoIP: Default = Off
This option only appears if the selected Phone Manager Type is Phone Manager PC Softphone. It enables or disables the
matching setting on the user's Phone Manager PC Softphone.
· Configuration Options
These options all