IP Office Manager - Avaya IP Office 500

IP Office Manager
Release 9.0
15-601011 Issue 9.01 (Monday, September 09, 2013)
© 2013 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.
Release 9.0
IP Office 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 9.01 (Monday, September 09, 2013)
Contents
Contents
1. IP Office Manager
1.1 Installing IP.....................................................................
Office Manager
1.2 Starting IP .....................................................................
Office Manager
1.3 Opening a .....................................................................
Configuration
1.4 Changing the
.....................................................................
IP Office Manager Language
1.5 Backward Compatibility
.....................................................................
13
15
16
18
18
2. Security Mode
2.1 Security Settings
..................................................................... 21
2.2 Default Security
.....................................................................
Users
22
2.3 Security Administration
..................................................................... 25
107
109
110
112
112
113
114
115
117
120
121
122
124
6. Network Telephone Features
3. Configuration Mode
3.1 The Configuration
.....................................................................
Mode Interface
3.2 Title Bar .....................................................................
3.3 The Menu Bar
.....................................................................
3.4 Toolbars .....................................................................
3.4.1 The
............................................................................
Main Toolbar
3.4.2 The
............................................................................
Navigation Toolbar
3.4.3 The
............................................................................
Details Toolbar
3.5 Using the Navigation
.....................................................................
Pane
3.6 Using the Group
.....................................................................
Pane
3.7 Using the Details
.....................................................................
Pane
3.8 Using the Error
.....................................................................
Pane
3.9 Altering the.....................................................................
Interface
3.10 The Status
.....................................................................
Bar
3.11 Editing Configuration
.....................................................................
Settings
3.11.1............................................................................
Mergeable Settings
3.11.2............................................................................
Configuration Size
3.11.3............................................................................
Setting the Discovery Addresses
3.11.4............................................................................
Opening a Configuration from a System
3.11.5............................................................................
Opening a Configuration Stored on PC
3.11.6............................................................................
Known System Discovery
3.11.7............................................................................
Creating New Records
3.11.8............................................................................
Creating an Offline Configuration
3.11.9............................................................................
Importing and Exporting Settings
3.11.10
............................................................................
Copying and Pasting
3.11.11
............................................................................
Saving a Configuration Offline
3.11.12
............................................................................
Sending a Configuration
3.11.13
............................................................................
Erasing the Configuration
3.11.14
............................................................................
Default Settings
5.2 Supported.....................................................................
SCN Features
5.3 Voicemail.....................................................................
Support
5.4 Enabling Small
.....................................................................
Community Networking
5.5 SCN Management
.....................................................................
5.5.1............................................................................
Enabling SCN Discovery
5.5.2............................................................................
Creating a Common Admin Account
5.5.3............................................................................
Loading an SCN Configuration
5.5.4............................................................................
Editing an SCN Configuration
5.5.5............................................................................
Using the Network Viewer
5.5.6............................................................................
System Inventory
5.6 SCN Remote
.....................................................................
Hotdesking
5.7 SCN Fallback
.....................................................................
5.8 SCN Short
.....................................................................
Code Programming
35
36
37
38
38
40
40
41
42
44
46
48
50
51
53
54
55
57
58
59
60
61
62
64
64
65
67
68
4. Server Edition Mode
4.1 Installing IP.....................................................................
Office Manager
72
4.2 Solution View
..................................................................... 74
4.3 System Inventories
..................................................................... 76
4.4 Record Consolidation
..................................................................... 77
4.5 Templates ..................................................................... 78
4.6 Telephony .....................................................................
Operation Configuration
80
4.6.1 Incoming
............................................................................
Call Routing
80
4.6.2 Outgoing
............................................................................
Call Routing
85
4.7 Default Settings
..................................................................... 102
4.8 IP500 V2 .....................................................................
Conversion
103
5. Small Community Networking
7. Shell Server Mode
8. Menu Bar Commands
8.1 Configuration
.....................................................................
Mode: File Menu
8.1.1............................................................................
Open Configuration
8.1.2............................................................................
Close Configuration
8.1.3............................................................................
Save Configuration
8.1.4............................................................................
Save Configuration As
8.1.5............................................................................
Change Working Directory
8.1.6............................................................................
Preferences
8.1.7............................................................................
Offline
8.1.8............................................................................
Advanced
8.1.9............................................................................
Backup/Restore
8.1.10
............................................................................
Import/Export
8.1.11
............................................................................
Exit
8.2 Configuration
.....................................................................
Mode: View Menu
8.2.1............................................................................
Toolbars
8.2.2............................................................................
Tooltip
8.2.3............................................................................
Navigation Pane
8.2.4............................................................................
Group Pane
8.2.5............................................................................
Details Pane
8.2.6............................................................................
Error Pane
8.2.7............................................................................
Advance View
8.2.8............................................................................
Hide Admin Tasks
8.2.9............................................................................
Simplified View
8.2.10
............................................................................
TFTP Log
8.3 Configuration
.....................................................................
Mode: Tools Menu
8.3.1............................................................................
Export | User
8.3.2............................................................................
Extension Renumber
8.3.3............................................................................
Line Renumber
8.3.4............................................................................
Connect To
8.3.5............................................................................
Service User Management
8.3.6............................................................................
Busy on Held Validation
8.3.7............................................................................
MSN/DID Configuration
8.3.8............................................................................
Print Button Labels
8.3.9............................................................................
Import Templates
8.4 Security Mode
.....................................................................
8.4.1............................................................................
Open Security Settings
8.4.2............................................................................
Close Security Settings
8.4.3............................................................................
Save Security Settings
8.4.4............................................................................
Reset Security Settings
8.4.5............................................................................
Preferences
134
134
134
134
134
135
136
143
145
162
163
164
165
165
165
165
165
165
165
165
165
165
166
167
167
167
167
167
169
170
170
171
172
173
173
173
173
173
173
5.1 Supported.....................................................................
SCN Network Layouts
106
Release 9.0
IP Office Manager
Page 3
15-601011 Issue 9.01 (Monday, September 09, 2013)
8.4.6............................................................................
Exit
8.4.7............................................................................
Configuration
8.5 Embedded
.....................................................................
File Management
8.5.1............................................................................
Open File Settings
8.5.2............................................................................
Close File Settings
8.5.3............................................................................
Refresh File Settings
8.5.4............................................................................
Upload File
8.5.5............................................................................
Upload System Files
8.5.6............................................................................
Backup System Files
8.5.7............................................................................
Restore System Files
8.5.8............................................................................
Upgrade Binaries
8.5.9............................................................................
Upgrade Configuration
8.5.10
............................................................................
Upload Voicemail Files
8.5.11
............................................................................
Upload Phone Files
8.5.12
............................................................................
Copy System Card
8.5.13
............................................................................
Configuration
173
173
174
175
175
175
175
175
175
175
175
175
176
176
176
176
9. Security Mode Field Descriptions
9.1 Configuring
.....................................................................
Security Settings
9.2 General Settings
.....................................................................
9.3 System .....................................................................
9.3.1............................................................................
System Details
9.3.2............................................................................
Unsecured Interfaces
9.3.3............................................................................
Certificates
9.4 Services Settings
.....................................................................
9.5 Rights Groups
.....................................................................
9.5.1............................................................................
Group Details
9.5.2............................................................................
Configuration
9.5.3............................................................................
Security Administration
9.5.4............................................................................
System Status
9.5.5............................................................................
Enhanced TSPI
9.5.6............................................................................
HTTP
9.5.7............................................................................
Web Services
9.5.8............................................................................
External
9.6 Service Users
.....................................................................
179
180
183
183
183
184
187
188
188
188
188
189
189
189
189
190
191
10. Configuration Mode Field Descriptions
10.1 BOOTP .....................................................................
10.2 Operator.....................................................................
10.3 System .....................................................................
10.3.1
............................................................................
System
10.3.2
............................................................................
LAN1
10.3.3
............................................................................
LAN2
10.3.4
............................................................................
DNS
10.3.5
............................................................................
Voicemail
10.3.6
............................................................................
Telephony
10.3.7
............................................................................
Directory Services
10.3.8
............................................................................
System Events
10.3.9
............................................................................
SMTP
10.3.10
............................................................................
SMDR
10.3.11
............................................................................
Twinning
10.3.12
............................................................................
VCM
10.3.13
............................................................................
CCR
10.3.14
............................................................................
Codecs
10.3.15
............................................................................
Dialer
10.4 Line
.....................................................................
10.4.1
............................................................................
Trunk Templates
10.4.2
............................................................................
Analog Line
Release 9.0
IP Office Manager
198
199
200
201
204
212
213
214
219
230
238
244
245
246
247
250
251
252
254
256
261
10.4.3
............................................................................
BRI Line
10.4.4
............................................................................
E1 Line
10.4.5
............................................................................
E1R2 Line
10.4.6
............................................................................
T1 Line
10.4.7
............................................................................
T1 PRI Line
10.4.8
............................................................................
S0 Line
10.4.9
............................................................................
H323 Line
10.4.10
............................................................................
IP DECT Line
10.4.11
............................................................................
SIP Line
10.4.12
............................................................................
SIP DECT Line
10.4.13
............................................................................
SM Line
10.5 Control Unit
.....................................................................
10.6 Extension
.....................................................................
10.6.1
............................................................................
Extn
10.6.2
............................................................................
Analog
10.6.3
............................................................................
VoIP
10.6.4
............................................................................
T38 Fax
10.6.5
............................................................................
IP DECT
10.6.6
............................................................................
SIP DECT Base
10.7 User
.....................................................................
10.7.1
............................................................................
User
10.7.2
............................................................................
Voicemail
10.7.3
............................................................................
DND
10.7.4
............................................................................
Short Codes
10.7.5
............................................................................
Source Numbers
10.7.6
............................................................................
Telephony
10.7.7
............................................................................
Forwarding
10.7.8
............................................................................
Dial In
10.7.9
............................................................................
Voice Recording
10.7.10
............................................................................
Button Programming
10.7.11
............................................................................
Menu Programming
10.7.12
............................................................................
Mobility (Twinning)
10.7.13
............................................................................
Hunt Group Memberships
10.7.14
............................................................................
Announcements
10.7.15
............................................................................
SIP
10.7.16
............................................................................
Personal Directory
10.8 Group .....................................................................
10.8.1
............................................................................
Group
10.8.2
............................................................................
User List/Select Members
10.8.3
............................................................................
Queuing
10.8.4
............................................................................
Overflow
10.8.5
............................................................................
Fallback
10.8.6
............................................................................
Voicemail
10.8.7
............................................................................
Voice Recording
10.8.8
............................................................................
Announcements
10.8.9
............................................................................
SIP
10.8.10
............................................................................
Hunt Group Operation
10.9 Short Code
.....................................................................
10.10 Service.....................................................................
10.10.1
............................................................................
Normal, WAN or Intranet Services
10.10.2
............................................................................
SSL VPN Service
10.11 RAS .....................................................................
10.11.1
............................................................................
PPP
10.12 Incoming
.....................................................................
Call Route
10.12.1
............................................................................
Standard
10.12.2
............................................................................
Voice Recording
10.12.3
............................................................................
Destinations
10.13 WAN Port
.....................................................................
267
272
278
282
288
295
299
308
312
328
330
335
336
337
339
341
345
346
347
348
350
354
357
358
359
361
369
371
372
374
375
377
383
384
386
387
389
391
394
395
398
400
403
406
407
409
410
417
418
419
427
431
432
433
435
438
439
440
Page 4
15-601011 Issue 9.01 (Monday, September 09, 2013)
Contents
10.13.1
............................................................................
WAN Port
10.13.2
............................................................................
Frame Relay
10.13.3
............................................................................
DLCIs
10.13.4
............................................................................
Advanced
10.13.5
............................................................................
PPP
10.14 Directory
.....................................................................
10.14.1
............................................................................
Directory
10.15 Time Profile
.....................................................................
10.15.1
............................................................................
Time Profile
10.16 Firewall.....................................................................
Profile
10.16.1
............................................................................
Standard
10.16.2
............................................................................
Custom
10.16.3
............................................................................
Static NAT
10.17 IP Route
.....................................................................
10.17.1
............................................................................
IP Route
10.17.2
............................................................................
RIP
10.18 Account.....................................................................
Code
10.18.1
............................................................................
Account Code
10.18.2
............................................................................
Voice Recording
10.19 License.....................................................................
10.19.1
............................................................................
License
10.19.2
............................................................................
Remote Server
10.20 Tunnel .....................................................................
10.20.1
............................................................................
L2TP Tunnel
10.20.2
............................................................................
IP Security Tunnel
10.21 Auto Attendant
.....................................................................
10.21.1
............................................................................
Auto Attendant
10.21.2
............................................................................
Actions
10.22 Authorization
.....................................................................
Codes
10.23 User Rights
.....................................................................
10.23.1
............................................................................
User
10.23.2
............................................................................
Short Codes
10.23.3
............................................................................
Button Programming
10.23.4
............................................................................
Telephony
10.23.5
............................................................................
Menu Programming
10.23.6
............................................................................
Twinning
10.23.7
............................................................................
User Rights Membership
10.23.8
............................................................................
Voicemail
10.24 ARS .....................................................................
10.24.1
............................................................................
ARS
10.24.2
............................................................................
Cause Codes and ARS
10.24.3
............................................................................
ARS Operation
10.25 Location
.....................................................................
441
442
443
445
446
448
450
451
452
453
454
455
457
458
459
460
461
462
463
464
465
467
468
469
472
475
476
477
479
482
484
485
486
487
490
490
490
491
492
494
496
497
506
11. Configuring IP Office
11.1 Date and.....................................................................
Time
11.2 User Directory
.....................................................................
Access
11.3 Mobile Call
.....................................................................
Control
11.3.1
............................................................................
Mobile Direct Access (MDA)
11.3.2
............................................................................
Mobile Callback
11.4 Advice of.....................................................................
Charge
11.5 Centralized
.....................................................................
System Directory
11.6 Centralized
.....................................................................
Personal Directory
11.7 Centralized
.....................................................................
Call Log
11.8 Coverage
.....................................................................
Groups
11.9 Emergency
.....................................................................
Call
11.10 Fax Relay
.....................................................................
11.11 Malicious
.....................................................................
Call Tracing (MCID)
Release 9.0
IP Office Manager
509
511
512
514
515
516
517
521
522
525
526
528
530
11.12 Call Barring
.....................................................................
11.13 Caller Display
.....................................................................
11.14 Call Intrusion
.....................................................................
11.15 Call Tagging
.....................................................................
11.16 Private.....................................................................
Calls
11.17 Call Pickup
.....................................................................
11.18 Call Waiting
.....................................................................
11.19 Parking.....................................................................
Calls
11.20 Call Access
.....................................................................
Control
11.21 Ring Back
.....................................................................
When Free
11.22 Message
.....................................................................
Waiting Indication
11.23 Ring Tones
.....................................................................
11.24 Media Connection
.....................................................................
Preservation
11.25 Music On
.....................................................................
Hold (MOH)
11.26 System.....................................................................
Phone Features
11.27 The 'No.....................................................................
User' User
11.28 Automatic
.....................................................................
Intercom Calls
11.29 Forwarding
.....................................................................
Calls
11.29.1
............................................................................
Do Not Disturb
11.29.2
............................................................................
Follow Me
11.29.3
............................................................................
Forward Unconditional
11.29.4
............................................................................
Forward on Busy
11.29.5
............................................................................
Forward on No Answer
11.29.6
............................................................................
Determining a User's Busy Status
11.29.7
............................................................................
Chaining and Loops
11.30 Transferring
.....................................................................
Calls
11.30.1
............................................................................
Off-Switch Transfer Restrictions
11.30.2
............................................................................
Context Sensitive Transfer
11.30.3
............................................................................
Dial Tone Transfer
11.30.4
............................................................................
Handsfree Announced Transfers
11.30.5
............................................................................
One Touch Transferring
11.30.6
............................................................................
Centrex Transfer
11.31 Conferencing
.....................................................................
11.31.1
............................................................................
Conference Phones
11.31.2
............................................................................
Ad-Hoc Conferencing
11.31.3
............................................................................
Meet Me Conferencing
11.31.4
............................................................................
Routing External Callers
11.31.5
............................................................................
Context Sensitive Conferencing
11.32 Hot Desking
.....................................................................
11.32.1
............................................................................
Remote Hot Desking
11.32.2
............................................................................
Call Center Agents
11.32.3
............................................................................
Hot Desking Examples
11.32.4
............................................................................
Automatic Log Off
11.33 Paging.....................................................................
11.33.1
............................................................................
Paging Via Voicemail Pro
11.34 Voice over
.....................................................................
IP Features
11.34.1
............................................................................
Wide Band Audio Support
11.34.2
............................................................................
Remote H323 Extensions
11.34.3
............................................................................
Secure VoIP (SRTP)
531
532
533
535
536
536
537
538
539
541
542
543
544
545
547
549
550
551
552
554
556
558
560
562
563
564
565
566
567
569
571
572
573
575
576
577
579
580
581
582
582
583
584
585
587
589
589
590
593
12. Configuring Server Edition
12.1 Opening.....................................................................
the System Configurations
12.2 Configuring
.....................................................................
the Systems
12.3 Saving Configuration
.....................................................................
Changes
12.4 Starting .....................................................................
System Status
12.5 Voicemail
.....................................................................
Administration
12.6 Setting Up
.....................................................................
Resilience
12.7 Adding a.....................................................................
Secondary Server
597
599
600
601
602
603
605
Page 5
15-601011 Issue 9.01 (Monday, September 09, 2013)
12.8 Adding an
.....................................................................
Expansion System
12.9 Displaying
.....................................................................
the System Inventories
12.10 Removing
.....................................................................
an Expansion/Secondary Server
12.11 Synchronizing
.....................................................................
the Configurations
12.12 Displaying
.....................................................................
the Solution View
12.13 Starting.....................................................................
Web Control
12.14 On-boarding
.....................................................................
12.15 Shared.....................................................................
Administration
606
607
607
607
607
608
608
608
13. Supported Phones
13.1 Phone Add-Ons
.....................................................................
13.2 Status Lamps
.....................................................................
13.3 1000 Series
.....................................................................
13.4 1100 Series
.....................................................................
13.5 1200 Series
.....................................................................
13.6 1400 Series
.....................................................................
13.6.1
............................................................................
1403
13.6.2
............................................................................
1408
13.6.3
............................................................................
1416
13.7 1600 Series
.....................................................................
13.7.1
............................................................................
1603
13.7.2
............................................................................
1608
13.7.3
............................................................................
1616
13.8 20 Series
.....................................................................
13.8.1
............................................................................
2030
13.8.2
............................................................................
2050 and 20CC
13.8.3
............................................................................
20DS
13.9 2400 Series
.....................................................................
13.9.1
............................................................................
2402D
13.9.2
............................................................................
2410
13.9.3
............................................................................
2420
13.10 3600 Series
.....................................................................
13.10.1
............................................................................
3616, 3620, 3626
13.10.2
............................................................................
3641, 3645
13.11 3700 Series
.....................................................................
13.12 3800 Series
.....................................................................
13.13 3900 Series
.....................................................................
13.14 4100 Series
.....................................................................
13.15 4400 Series
.....................................................................
13.15.1
............................................................................
4406D+
13.15.2
............................................................................
4412D+
13.15.3
............................................................................
4424D+
13.15.4
............................................................................
4450
13.16 4600 Series
.....................................................................
(New Style)
13.16.1
............................................................................
4601
13.16.2
............................................................................
4602, 4602SW
13.16.3
............................................................................
4610SW
13.16.4
............................................................................
4620, 4620SW, 4621, 4625
13.17 5400 Series
.....................................................................
13.17.1
............................................................................
5402D
13.17.2
............................................................................
5410
13.17.3
............................................................................
5420
13.18 5600 Series
.....................................................................
13.18.1
............................................................................
5601
13.18.2
............................................................................
5602, 5602SW
13.18.3
............................................................................
5610SW
13.18.4
............................................................................
5620, 5620SW, 5621
13.19 7400 Series
.....................................................................
Release 9.0
IP Office Manager
615
617
620
621
622
623
623
623
624
625
625
625
626
627
627
627
628
629
629
630
631
633
633
634
635
635
636
637
638
638
639
640
641
642
642
643
644
645
646
646
647
648
650
650
651
652
653
654
13.20 9500 Series
.....................................................................
13.20.1
............................................................................
9504
13.20.2
............................................................................
9508
13.21 9600 Series
.....................................................................
13.21.1
............................................................................
9608
13.21.2
............................................................................
9611
13.21.3
............................................................................
9620C, 9620L
13.21.4
............................................................................
9621
13.21.5
............................................................................
9630G
13.21.6
............................................................................
9640, 9640G
13.21.7
............................................................................
9641
13.21.8
............................................................................
9650, 9650C
13.22 B100 Series
.....................................................................
13.23 D100 .....................................................................
13.24 M-Series
.....................................................................
13.24.1
............................................................................
M7100
13.24.2
............................................................................
M7100N
13.24.3
............................................................................
M7208
13.24.4
............................................................................
M7208N
13.24.5
............................................................................
M7310
13.24.6
............................................................................
M7310N
13.24.7
............................................................................
M7324
13.24.8
............................................................................
M7324N
13.24.9
............................................................................
KLM Module
13.25 T-Series
.....................................................................
13.25.1
............................................................................
T7000
13.25.2
............................................................................
T7100
13.25.3
............................................................................
T7208
13.25.4
............................................................................
T7316
13.25.5
............................................................................
T7316E
13.25.6
............................................................................
T7316 KEM Module
13.25.7
............................................................................
T7406, T7406e
13.25.8
............................................................................
Audio Conferencing Unit
13.26 T3 Series
.....................................................................
13.26.1
............................................................................
T3 Compact/T3 IP Compact
13.26.2
............................................................................
T3 Classic/T3 IP Classic
13.26.3
............................................................................
T3 Comfort/T3 IP Comfort
655
655
655
656
656
657
658
659
660
661
662
663
664
665
666
670
671
673
674
675
677
679
681
682
683
687
688
690
691
693
695
695
697
698
698
699
700
14. Short Code Overview
14.1 Short Code
.....................................................................
Fields and Characters
14.2 User Dialing
.....................................................................
14.3 Application
.....................................................................
Dialing
14.4 Secondary
.....................................................................
Dial Tone
14.5 ? Short Codes
.....................................................................
14.6 Short Code
.....................................................................
Matching Examples
14.7 Default System
.....................................................................
Short Code List
704
707
708
709
710
711
714
15. Short Code Features
15.1 Acquire .....................................................................
Call
15.2 AOC Previous
.....................................................................
Call
15.3 AOC Reset
.....................................................................
Total
15.4 AOC Total
.....................................................................
15.5 Auto Attendant
.....................................................................
15.6 Break Out
.....................................................................
15.7 Barred .....................................................................
15.8 Busy On.....................................................................
Held
15.9 Call Intrude
.....................................................................
15.10 Call Listen
.....................................................................
720
720
720
720
720
721
721
721
722
723
Page 6
15-601011 Issue 9.01 (Monday, September 09, 2013)
Contents
15.11 Call Park
.....................................................................
15.12 Call Park
.....................................................................
and Page
15.13 Call Pickup
.....................................................................
Any
15.14 Call Pickup
.....................................................................
Extn
15.15 Call Pickup
.....................................................................
Group
15.16 Call Pickup
.....................................................................
Line
15.17 Call Pickup
.....................................................................
Members
15.18 Call Pickup
.....................................................................
User
15.19 Call Queue
.....................................................................
15.20 Call Record
.....................................................................
15.21 Call Steal
.....................................................................
15.22 Call Waiting
.....................................................................
On
15.23 Call Waiting
.....................................................................
Off
15.24 Call Waiting
.....................................................................
Suspend
15.25 Cancel.....................................................................
All Forwarding
15.26 Cancel.....................................................................
Ring Back When Free
15.27 Channel
.....................................................................
Monitor
15.28 Change.....................................................................
Login Code
15.29 Clear After
.....................................................................
Call Work
15.30 Clear Call
.....................................................................
15.31 Clear CW
.....................................................................
15.32 Clear Hunt
.....................................................................
Group Night Service
15.33 Clear Hunt
.....................................................................
Group Out Of Service
15.34 Clear Quota
.....................................................................
15.35 Coaching
.....................................................................
Intrusion
15.36 Conference
.....................................................................
Add
15.37 Conference
.....................................................................
Meet Me
15.38 CW .....................................................................
15.39 Dial .....................................................................
15.40 Dial 3K1
.....................................................................
15.41 Dial 56K
.....................................................................
15.42 Dial 64K
.....................................................................
15.43 Dial CW
.....................................................................
15.44 Dial Direct
.....................................................................
15.45 Dial Direct
.....................................................................
Hot Line
15.46 Dial Emergency
.....................................................................
15.47 Dial Extn
.....................................................................
15.48 Dial Fax
.....................................................................
15.49 Dial Inclusion
.....................................................................
15.50 Dial Paging
.....................................................................
15.51 Dial Physical
.....................................................................
Extension By Number
15.52 Dial Physical
.....................................................................
Extension By Id
15.53 Dial Speech
.....................................................................
15.54 Dial V110
.....................................................................
15.55 Dial V120
.....................................................................
15.56 Dial Video
.....................................................................
15.57 Disable.....................................................................
ARS Form
15.58 Disable.....................................................................
Internal Forwards
15.59 Disable.....................................................................
Internal Forward Unconditional
15.60 Disable.....................................................................
Internal Forward Busy or No Answer
15.61 Display.....................................................................
Msg
15.62 Do Not.....................................................................
Disturb Exception Add
15.63 Do Not.....................................................................
Disturb Exception Delete
15.64 Do Not.....................................................................
Disturb On
15.65 Do Not.....................................................................
Disturb Off
15.66 Enable.....................................................................
ARS Form
15.67 Enable.....................................................................
Internal Forwards
15.68 Enable.....................................................................
Internal Forward Unconditional
Release 9.0
IP Office Manager
724
724
725
725
726
726
727
727
728
728
729
730
730
730
731
731
731
732
733
733
733
734
734
735
735
735
736
737
738
739
739
739
739
740
740
741
741
742
742
743
744
744
745
745
745
745
746
746
746
747
747
748
748
749
749
749
750
750
15.69 Enable.....................................................................
Internal Forward Busy or No Answer
15.70 Extn Login
.....................................................................
15.71 Extn Logout
.....................................................................
15.72 Flash Hook
.....................................................................
15.73 FNE Service
.....................................................................
15.74 Follow .....................................................................
Me Here
15.75 Follow .....................................................................
Me Here Cancel
15.76 Follow .....................................................................
Me To
15.77 Forward
.....................................................................
Hunt Group Calls On
15.78 Forward
.....................................................................
Hunt Group Calls Off
15.79 Forward
.....................................................................
Number
15.80 Forward
.....................................................................
On Busy Number
15.81 Forward
.....................................................................
On Busy On
15.82 Forward
.....................................................................
On Busy Off
15.83 Forward
.....................................................................
On No Answer On
15.84 Forward
.....................................................................
On No Answer Off
15.85 Forward
.....................................................................
Unconditional On
15.86 Forward
.....................................................................
Unconditional Off
15.87 Group Listen
.....................................................................
Off
15.88 Group Listen
.....................................................................
On
15.89 Headset
.....................................................................
Toggle
15.90 Hold Call
.....................................................................
15.91 Hold CW
.....................................................................
15.92 Hold Music
.....................................................................
15.93 Hunt Group
.....................................................................
Disable
15.94 Hunt Group
.....................................................................
Enable
15.95 Last Number
.....................................................................
Redial
15.96 MCID Activate
.....................................................................
15.97 Mobile .....................................................................
Twinned Call Pickup
15.98 Off Hook
.....................................................................
Station
15.99 Outgoing
.....................................................................
Call Bar Off
15.100 Outgoing
.....................................................................
Call Bar On
15.101 Private
.....................................................................
Call
15.102 Private
.....................................................................
Call Off
15.103 Private
.....................................................................
Call On
15.104 Priority
.....................................................................
Call
15.105 Record
.....................................................................
Message
15.106 Relay.....................................................................
On
15.107 Relay.....................................................................
Off
15.108 Relay.....................................................................
Pulse
15.109 Resume
.....................................................................
Call
15.110 Retrieve
.....................................................................
Call
15.111 Ring Back
.....................................................................
When Free
15.112 Secondary
.....................................................................
Dial Tone
15.113 Set Absent
.....................................................................
Text
15.114 Set Account
.....................................................................
Code
15.115 Set Authorization
.....................................................................
Code
15.116 Set Hunt
.....................................................................
Group Night Service
15.117 Set Hunt
.....................................................................
Group Out Of Service
15.118 Set Inside
.....................................................................
Call Seq
15.119 Set Mobile
.....................................................................
Twinning Number
15.120 Set Mobile
.....................................................................
Twinning On
15.121 Set Mobile
.....................................................................
Twinning Off
15.122 Set No.....................................................................
Answer Time
15.123 Set Outside
.....................................................................
Call Seq
15.124 Set Ringback
.....................................................................
Seq
15.125 Set Wrap
.....................................................................
Up Time
15.126 Shutdown
.....................................................................
Embedded Voicemail
750
751
751
753
753
754
755
755
756
756
757
757
758
758
759
759
760
760
761
761
762
762
763
763
764
764
765
765
765
766
767
767
768
769
769
770
770
771
771
772
772
773
773
773
775
776
776
777
778
779
780
780
780
781
781
782
782
783
Page 7
15-601011 Issue 9.01 (Monday, September 09, 2013)
15.127
15.128
15.129
15.130
15.131
15.132
15.133
15.134
15.135
15.136
15.137
15.138
15.139
15.140
Stamp.....................................................................
Log
Startup
.....................................................................
Embedded Voicemail
Suspend
.....................................................................
Call
Suspend
.....................................................................
CW
Start After
.....................................................................
Call Work
Toggle.....................................................................
Calls
Unpark
.....................................................................
Call
Voicemail
.....................................................................
Collect
Voicemail
.....................................................................
Node
Voicemail
.....................................................................
On
Voicemail
.....................................................................
Off
Voicemail
.....................................................................
Ringback On
Voicemail
.....................................................................
Ringback Off
Whisper
.....................................................................
Page
783
784
784
784
785
785
785
786
788
788
788
790
790
790
16. Button Programming Overview
16.1 Programming
.....................................................................
Buttons with Manager
16.2 Programming
.....................................................................
Button via the Menu Key
16.3 Programming
.....................................................................
Button via an Admin Button
16.4 BST Button
.....................................................................
Programming
16.5 T3 Self-Administration
.....................................................................
16.6 Interactive
.....................................................................
Button Menus
16.7 Label Templates
.....................................................................
794
795
797
798
799
801
802
17. Button Programming Actions
17.1 Abbreviated
.....................................................................
Dial
17.2 Abbreviated
.....................................................................
Dial Pause
17.3 Abbreviated
.....................................................................
Dial Program
17.4 Abbreviated
.....................................................................
Dial Stop
17.5 Account .....................................................................
Code Entry
17.6 ACD Agent
.....................................................................
Statistics
17.7 ACD Stroke
.....................................................................
Count
17.8 Acquire .....................................................................
Call
17.9 AD Special
.....................................................................
Functions
17.10 AD Special
.....................................................................
Function Mark
17.11 AD Special
.....................................................................
Function Wait
17.12 AD Suppress
.....................................................................
17.13 After Call
.....................................................................
Work
17.14 Appearance
.....................................................................
17.15 Automatic
.....................................................................
Callback
17.16 Automatic
.....................................................................
Intercom
17.17 Break Out
.....................................................................
17.18 Bridged.....................................................................
Appearance
17.19 Busy .....................................................................
17.20 Busy On
.....................................................................
Held
17.21 Call Forwarding
.....................................................................
All
17.22 Call Intrude
.....................................................................
17.23 Call List.....................................................................
17.24 Call Listen
.....................................................................
17.25 Call Log
.....................................................................
17.26 Call Park
.....................................................................
17.27 Call Park
.....................................................................
and Page
17.28 Call Park
.....................................................................
To Other Extension
17.29 Call Pickup
.....................................................................
17.30 Call Pickup
.....................................................................
Any
17.31 Call Pickup
.....................................................................
Group
17.32 Call Pickup
.....................................................................
Members
17.33 Call Queue
.....................................................................
Release 9.0
IP Office Manager
810
810
811
811
812
813
813
814
814
814
815
815
816
817
819
820
821
822
823
823
824
825
825
826
827
828
829
830
831
831
833
833
835
17.34 Call Record
.....................................................................
17.35 Call Screening
.....................................................................
17.36 Call Steal
.....................................................................
17.37 Call Waiting
.....................................................................
Off
17.38 Call Waiting
.....................................................................
On
17.39 Call Waiting
.....................................................................
Suspend
17.40 Cancel.....................................................................
All Forwarding
17.41 Cancel.....................................................................
Leave Word Calling
17.42 Cancel.....................................................................
Ring Back When Free
17.43 Channel
.....................................................................
Monitor
17.44 Clear Call
.....................................................................
17.45 Clear CW
.....................................................................
17.46 Clear Hunt
.....................................................................
Group Night Service
17.47 Clear Hunt
.....................................................................
Group Out Of Service
17.48 Clear Quota
.....................................................................
17.49 Coaching
.....................................................................
Intrusion
17.50 Conference
.....................................................................
17.51 Conference
.....................................................................
Add
17.52 Conference
.....................................................................
Meet Me
17.53 Consult.....................................................................
17.54 Coverage
.....................................................................
Appearance
17.55 Dial .....................................................................
17.56 Dial 3K1
.....................................................................
17.57 Dial 56K
.....................................................................
17.58 Dial 64K
.....................................................................
17.59 Dial CW
.....................................................................
17.60 Dial Direct
.....................................................................
17.61 Dial Emergency
.....................................................................
17.62 Dial Inclusion
.....................................................................
17.63 Dial Intercom
.....................................................................
17.64 Dial Paging
.....................................................................
17.65 Dial Physical
.....................................................................
Extn by Number
17.66 Dial Physical
.....................................................................
Extn by Id
17.67 Dial Speech
.....................................................................
17.68 Dial V110
.....................................................................
17.69 Dial V120
.....................................................................
17.70 Display.....................................................................
Msg
17.71 Dial Video
.....................................................................
17.72 Directed
.....................................................................
Call Pickup
17.73 Directory
.....................................................................
17.74 Do Not.....................................................................
Disturb Exception Add
17.75 Do Not.....................................................................
Disturb Exception Delete
17.76 Do Not.....................................................................
Disturb Off
17.77 Do Not.....................................................................
Disturb On
17.78 Drop .....................................................................
17.79 Extn Login
.....................................................................
17.80 Extn Logout
.....................................................................
17.81 Flash Hook
.....................................................................
17.82 Follow .....................................................................
Me Here
17.83 Follow .....................................................................
Me Here Cancel
17.84 Follow .....................................................................
Me To
17.85 Forward
.....................................................................
Hunt Group Calls Off
17.86 Forward
.....................................................................
Hunt Group Calls On
17.87 Forward
.....................................................................
Number
17.88 Forward
.....................................................................
On Busy Number
17.89 Forward
.....................................................................
On Busy Off
17.90 Forward
.....................................................................
On Busy On
17.91 Forward
.....................................................................
On No Answer Off
835
836
838
839
839
840
840
841
841
842
843
843
844
845
846
846
848
848
849
851
852
853
853
854
854
855
855
856
856
858
859
860
860
861
861
862
862
863
864
865
866
866
867
867
868
869
870
871
872
872
873
874
874
876
877
878
879
880
Page 8
15-601011 Issue 9.01 (Monday, September 09, 2013)
Contents
17.92 Forward
.....................................................................
On No Answer On
17.93 Forward
.....................................................................
Unconditional Off
17.94 Forward
.....................................................................
Unconditional On
17.95 Group .....................................................................
17.96 Group Listen
.....................................................................
On
17.97 Group Paging
.....................................................................
17.98 Headset
.....................................................................
Toggle
17.99 Hold Call
.....................................................................
17.100 Hold CW
.....................................................................
17.101 Hold Music
.....................................................................
17.102 Hunt Group
.....................................................................
Enable
17.103 Hunt Group
.....................................................................
Disable
17.104 Inspect
.....................................................................
17.105 Internal
.....................................................................
Auto-Answer
17.106 Last Number
.....................................................................
Redial
17.107 Leave.....................................................................
Word Calling
17.108 Line Appearance
.....................................................................
17.109 Manual
.....................................................................
Exclude
17.110 MCID.....................................................................
Activate
17.111 Off Hook
.....................................................................
Station
17.112 Pause.....................................................................
Recording
17.113 Priority
.....................................................................
Call
17.114 Priority
.....................................................................
Calling
17.115 Private
.....................................................................
Call
17.116 Relay.....................................................................
Off
17.117 Relay.....................................................................
On
17.118 Relay.....................................................................
Pulse
17.119 Resume
.....................................................................
Call
17.120 Request
.....................................................................
Coaching Intrusion
17.121 Retrieve
.....................................................................
Call
17.122 Ring Back
.....................................................................
When Free
17.123 Ringer.....................................................................
Off
17.124 Self-Administer
.....................................................................
17.125 Send .....................................................................
All Calls
17.126 Set Absent
.....................................................................
Text
17.127 Set Account
.....................................................................
Code
17.128 Set Hunt
.....................................................................
Group Night Service
17.129 Set Hunt
.....................................................................
Group Out Of Service
17.130 Set Inside
.....................................................................
Call Seq
17.131 Set Night
.....................................................................
Service Group
17.132 Set No.....................................................................
Answer Time
17.133 Set Out
.....................................................................
of Service Group
17.134 Set Outside
.....................................................................
Call Seq
17.135 Set Ringback
.....................................................................
Seq
17.136 Set Wrap
.....................................................................
Up Time
17.137 Speed.....................................................................
Dial
17.138 Stamp.....................................................................
Log
17.139 Stored.....................................................................
Number View
17.140 Suspend
.....................................................................
Call
17.141 Suspend
.....................................................................
CW
17.142 Time of
.....................................................................
Day
17.143 Timer.....................................................................
17.144 Transfer
.....................................................................
17.145 Toggle.....................................................................
Calls
17.146 Twinning
.....................................................................
17.147 Unpark
.....................................................................
Call
17.148 User .....................................................................
17.149 Visual.....................................................................
Voice
Release 9.0
IP Office Manager
880
881
882
883
884
885
886
886
887
887
888
889
890
891
892
892
893
893
894
895
896
896
897
898
899
899
900
901
901
903
904
905
906
908
909
910
911
912
913
913
914
914
915
915
916
916
918
919
920
920
921
922
923
923
924
925
926
928
17.150
17.151
17.152
17.153
17.154
17.155
Voicemail
.....................................................................
Collect
Voicemail
.....................................................................
Off
Voicemail
.....................................................................
On
Voicemail
.....................................................................
Ringback Off
Voicemail
.....................................................................
Ringback On
Whisper
.....................................................................
Page
930
931
932
933
934
935
18. Apperance Button Operation
18.1 Appearance
.....................................................................
Button Features
18.2 Call Appearance
.....................................................................
Buttons
18.2.1
............................................................................
Example 1
18.2.2
............................................................................
Example 2
18.2.3
............................................................................
How are Call Appearance Buttons Treated?
18.2.4
............................................................................
Button Indication
18.3 Bridged .....................................................................
Appearance Buttons
18.3.1
............................................................................
Example 1
18.3.2
............................................................................
Example 2
18.3.3
............................................................................
Example 3
18.3.4
............................................................................
How are Bridged Appearances Treated?
18.3.5
............................................................................
Button Indication
18.4 Call Coverage
.....................................................................
Buttons
18.4.1
............................................................................
Example 1
18.4.2
............................................................................
Example 2
18.4.3
............................................................................
How is Call Coverage Treated?
18.4.4
............................................................................
Button Indication
18.5 Line Appearance
.....................................................................
Buttons
18.5.1
............................................................................
Example 1
18.5.2
............................................................................
Example 2
18.5.3
............................................................................
How are Line Appearances Treated?
18.5.4
............................................................................
Button Indication
18.5.5
............................................................................
T3 Phone Line Appearances
18.6 Other Appearance
.....................................................................
Controls
18.6.1
............................................................................
Selected Button Indication
18.6.2
............................................................................
Idle Line Preference
18.6.3
............................................................................
Ringing Line Preference
18.6.4
............................................................................
Answer Pre-Select
18.6.5
............................................................................
Auto Hold
18.6.6
............................................................................
Ring Delay
18.6.7
............................................................................
Delayed Ring Preference
18.6.8
............................................................................
Collapsing Appearances
18.6.9
............................................................................
Joining Other Calls (Bridging)
18.6.10
............................................................................
Multiple Alerting Buttons
18.6.11
............................................................................
Twinning
18.6.12
............................................................................
Busy on Held
18.6.13
............................................................................
Reserving a Call Appearance Button
18.6.14
............................................................................
Logging Off and Hot Desking
18.6.15
............................................................................
Applications
18.7 Programming
.....................................................................
Appearance Buttons
18.7.1
............................................................................
System Settings
18.7.2
............................................................................
User Settings
18.7.3
............................................................................
Line Appearance ID Numbers
18.7.4
............................................................................
Outgoing Line Programming
938
939
940
941
942
943
944
945
946
947
948
949
950
951
951
952
953
954
955
956
957
958
959
960
960
961
964
967
968
969
971
973
974
976
977
977
977
978
978
979
981
982
983
984
19. Data Routing
19.1 Network.....................................................................
Address Translation (NAT)
19.2 DHCP .....................................................................
19.3 Examples
.....................................................................
19.3.1
............................................................................
Simple ISDN Internet Connection
987
987
988
988
Page 9
15-601011 Issue 9.01 (Monday, September 09, 2013)
19.3.2
............................................................................
ISDN Link Between IP Offices
19.3.3
............................................................................
Using a Dedicated T1/PRI ISP Link
19.3.4
............................................................................
Remote Access
19.3.5
............................................................................
WAN PPP
19.3.6
............................................................................
WAN Frame Relay
989
990
992
995
996
Release 9.0
IP Office Manager
21. Appendix: SMDR
21.1 SMDR .....................................................................
Fields
1056
21.2 SMDR .....................................................................
Examples
1059
20. Appendix: Locale Settings
20.1 Locale .....................................................................
Defaults
20.2 Phone .....................................................................
Display Language Sets and Fallback
20.3 Argentina
.....................................................................
20.4 Australia
.....................................................................
20.5 Bahrain.....................................................................
20.6 Belgium
.....................................................................
- Flemish
20.7 Belgium.....................................................................
- French
20.8 Brazil .....................................................................
20.9 Canada.....................................................................
20.10 Chile .....................................................................
20.11 China.....................................................................
20.12 Colombia
.....................................................................
20.13 Customize
.....................................................................
20.14 Denmark
.....................................................................
20.15 Egypt.....................................................................
20.16 Finland
.....................................................................
20.17 France
.....................................................................
20.18 France2
.....................................................................
20.19 Greece
.....................................................................
20.20 Germany
.....................................................................
20.21 Hong .....................................................................
Kong
20.22 Hungary
.....................................................................
20.23 Iceland
.....................................................................
20.24 India .....................................................................
20.25 Ireland
.....................................................................
20.26 Italy .....................................................................
20.27 Japan.....................................................................
20.28 Korea.....................................................................
20.29 Kuwait.....................................................................
20.30 Malaysia
.....................................................................
20.31 Mexico
.....................................................................
20.32 Morocco
.....................................................................
20.33 Netherlands
.....................................................................
20.34 New Zealand
.....................................................................
20.35 Norway
.....................................................................
20.36 Oman.....................................................................
20.37 Pakistan
.....................................................................
20.38 Peru .....................................................................
20.39 Poland
.....................................................................
20.40 Portugal
.....................................................................
20.41 Qatar .....................................................................
20.42 Russia
.....................................................................
20.43 Saudi.....................................................................
Arabia
20.44 Singapore
.....................................................................
20.45 South.....................................................................
Africa
20.46 Spain.....................................................................
20.47 Sweden
.....................................................................
20.48 Switzerland
.....................................................................
20.49 Taiwan
.....................................................................
20.50 Turkey.....................................................................
20.51 United.....................................................................
Arab Emirates
20.52 United.....................................................................
Kingdom
1051
20.53 United.....................................................................
States
1052
20.54 Venezuela
..................................................................... 1053
1000
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
22. IP Office Software Compatibility
23. Ports
24. Single Server Support
Index ...............................................................................1078
Page 10
15-601011 Issue 9.01 (Monday, September 09, 2013)
Chapter 1.
IP Office Manager
Release 9.0
IP Office Manager
Page 11
15-601011 Issue 9.01 (Monday, September 09, 2013)
1. IP Office Manager
This documentation covers the use of the Avaya IP Office Manager. Manager runs on a Windows PC and connects to the
IP Office system via Ethernet LAN or WAN connections.
·
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 a user through their phone or voicemail mailbox after
the copy of the configuration is received by Manager.
Manager Modes
The menus and options displayed by Manager vary depending on the actions you are performing. Manager runs in the
following modes.
Simplified View
This is the default mode when no system configuration has been opened.
Simplified Administration Mode
This is the mode used when a Basic Edition configuration is opened. Basic Mode includes systems running Partner,
Norstar, or Quick Mode. For information on administering a Basic Edition system, see the IP Office Basic Edition Manager
book for the specific mode.
Security Configuration Mode
Manager can be used to edit the security settings of IP Office systems.
Advanced Configuration Mode
This is the mode used when a Standard Mode configuration is opened. Standard Mode includes systems running
Standard, Preferred, or Advanced Edition.
Server Edition Mode
This is the mode used when a Server Edition network configuration is opened.
Small Community Network Management Mode
Manager supports loading the combined configurations from systems in a Small Community Network.
IP Office Shell Server Mode
The IP Office Shell Server is a single installation of selected IP Office applications running on Linux. You can use Manager
to administer an IP Office Shell Server.
Embedded File Management
For systems with a memory card installed, Manager can be used to view and manage the files stored on the card.
Embedded File Management can be accessed by selecting File | Advanced | Embedded File Management.
Upgrade Wizard
The Upgrade Wizard is a component of Manager used to upgrade the firmware run by the system.
Release 9.0
IP Office Manager
Page 12
15-601011 Issue 9.01 (Monday, September 09, 2013)
IP Office Manager:
1.1 Installing IP Office Manager
Manager is a component of the IP Office Admin suite of applications. This suite is supplied on the Release 8.1 FP1 DVD
(Disk 1). Alternatively, the IP Office Admin Suite can be downloaded from Avaya's support website http://support.avaya.
com.
This section covers the installation of Manager for the administration and maintenance of non-Server Edition systems. For
installation of a version of Manager suitable for administration of just Server Edition systems, see Server Edition Mode 72
.
In addition to Manager, the 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.
IP Office Manager 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 IP Office Manager if
not already present.
Windows 7
· *Includes disk space required for .NET2 component.
· Language Support
The IP Office Manager application can run in Brazilian Portuguese, Simplified Chinese, Dutch, French, German,
Italian, Mexican Spanish, Russian, UK English and US English. By default the language used is determined by the
best match to the PC's regional setting. To change the language used see Changing the IP Office Manager
Language 18 .
Ports
The Manager application uses the following ports for access to the telephone system. These ports may need to be allowed
within the configuration of any firewall software being run on the PC hosting the Manager application. Note that the ports
used by a particular system can be adjusted through its security settings 183 .
Component
Location - %ProgramFiles%\Avaya\IP
Office\Manager
Ports
Manager
manager.exe
TCP Port 50802. Configuration access
TCP Port 50804.
TCP Port 50805.
TCP Port 50812. Security configuration
TCP Port 50813. access
Upgrade Wizard
Release 9.0
IP Office Manager
upgradewiz.exe
UDP Port 50798. System upgrade access.
Page 13
15-601011 Issue 9.01 (Monday, September 09, 2013)
Installing Manager
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 Admin DVD, insert the DVD and when the page is displayed click on the link for the 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 an upgrade menu appears, it indicates that a previous installation 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 Manager. 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 Admin suite applications that are installed.
Locate IP Office Admin Suite in the list of programs and select Change.
Release 9.0
IP Office Manager
Page 14
15-601011 Issue 9.01 (Monday, September 09, 2013)
IP Office Manager: Installing IP Office Manager
1.2 Starting IP Office Manager
No name or password is required to start Manager. A name and password is only required when connecting with a
system.
When started, by default Manager will attempt to discover any systems on the network. If it finds any it will display a list
from which you can select the system required.
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 16 . 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 16 . 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
61
· Open a Configuration from a System
· Read a Configuration from a File
Release 9.0
IP Office Manager
16
58
Page 15
15-601011 Issue 9.01 (Monday, September 09, 2013)
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 139 ). 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 136 , 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 Server Edition systems are detected, they are grouped together. By default the configuration of those
systems cannot be opened using Manager in Advanced View mode and the configuration of a Primary Server
can only be opened if the Open with Server Edition Manager option is also selected. See Server Edition
Mode 597 .
· If Manager has been set with SCN Discovery 139 enabled, systems in a Small Community Network are
grouped together. The checkbox next to the network name can be used to load the configurations of all the
configurations into Small Community Network management 112 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 |
Discovery 139 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
139
59
option.
· Systems found but not supported by the version of Manager being used will be listed as Not Supported.
· If the system detected is running software other than from its primary folder, a
warning icon will be
shown next to it. The configuration can still be opened but only as a read-only file.
3. When you have located the system required, check the box next to the system and click OK.
· If the system selected is a Server Edition system and Manager is not running in Server Edition mode, an
Open with Server Edition Manager checkbox is shown and pre-selected. Clicking OK will switch Manager to
its Server Edition mode before loading the configuration.
4. The system name and password request is displayed. Enter the required details and click OK.
The name and password used must match a service user account configured within the system's security
settings.
5. Additional messages will inform you about the success or failure of opening the configuration from the system.
· The method of connection, secure or insecure, attempted by Manager is set the applications Secure
Communications 141 preferences setting.
· When Secure Communications is set to On, a
Manager status field.
padlock icon is displayed at all times in the lower right
· New installations of Manager default to having Secure Communications enabled. This means Manager by
default attempts to use secure communications when opening a configuration.
· For Server Edition systems, Manager will always attempt to use secure communications regardless of the
Secure Communications setting.
· If no response to the use of secure communication is received after 5 seconds, Manager will offer to fallback
to using unsecured communications.
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.
Release 9.0
IP Office Manager
Page 16
15-601011 Issue 9.01 (Monday, September 09, 2013)
IP Office Manager: Opening a Configuration
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 201 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.
Release 9.0
IP Office Manager
Page 17
15-601011 Issue 9.01 (Monday, September 09, 2013)
1.4 Changing the IP Office Manager Language
The Manager application can run in US English, UK English, Chinese (Simplified), French, German, Brazilian
Portuguese, Dutch, Italian, Russian 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
Chinese (Simplified)
-locale:zh-Hans
Dutch
-locale:nl-NL
French
-locale:fr-FR
German
-locale:de-DE
Italian
-locale:it-IT
Mexican Spanish
-locale:es-MX
Russian
-locale:ru-RU
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. The Manager application can be used to manage configurations
from systems running earlier software releases. When an Release 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.
· To receive a pre-Release 3.2 configuration requires entry of an operator name and the system password.
· To receive a Release 3.2 or higher configuration requires entry of a service user name and password stored by
that system.
For Release 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.
Note that this document describes the current release. If you are running an earlier software release, obtain the Manager
document for the specific release from the Avaya support site.
Backwards compatibility is only supported for General Availability releases of IP Office software. It is not supported for
private builds.
Release 9.0
IP Office Manager
Page 18
15-601011 Issue 9.01 (Monday, September 09, 2013)
IP Office Manager: Backward Compatibility
Release 9.0
IP Office Manager
Page 19
15-601011 Issue 9.01 (Monday, September 09, 2013)
Chapter 2.
Security Mode
Release 9.0
IP Office Manager
Page 20
15-601011 Issue 9.01 (Monday, September 09, 2013)
Security Mode:
2. Security Mode
These menus are used to edit the security settings of a system. They are not used for systems running in Basic Edition.
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.
2.1 Security Settings
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.
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. 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.
Release 9.0
IP Office Manager
Page 21
15-601011 Issue 9.01 (Monday, September 09, 2013)
2.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
Password
Role
Rights Group Memberships
Administrat Administrator These are the default accounts used for system
or
configuration using the IP Office Manager application.
Administrator, Business
Partner, System Status Group.
Manager
Manager
Customer Admin, Manager,
System Status.
Operator
Operator
Customer Admin, Operator,
System Status.
EnhTcpaSer EnhTcpaPwd1 This account is used for one-X Portal for IP Office
vice
connections to the system.
TCPA Group.
SCN_Admin
This account is used for multiple system configuration
using the Small Community Network Management 112
features.
Administrator Group, System
Status Group.
IPDECTServ –
ice
This account is used for DECT R4 system provisioning via
an IP DECT trunk 308 .
IPDECT Group.
SMGRB580
0Admin
SMGRB5800A This account is used for web based configuration services.
dmin
SGMR Admin
BusinessPa BusinessPartn
rtner
er
Business Partner
Maintainer
Maintainer
Maintainer
Default Rights Groups
The Rights Groups to which a service user 191 belongs define what the service user is able to do after that login to the
system. The maximum number of rights groups that can be created is 32.
Rights
Administra Manager
tor Group
Group
Description
These groups are intended for users
using the Manager application to
configure the system.
Service Rights
Operator
Group
Business
Partner
Read Configuration
Write Configuration
Default Configuration
Merge
Reboot Immediately
Reboot When Free
Reboot at Time of Day
Release 9.0
IP Office Manager
Page 22
15-601011 Issue 9.01 (Monday, September 09, 2013)
Security Mode: Default Security Users
Operator Rights Operator View
Web Service
Administrat
or
Manager
Operator
Security Read All
–
–
–
Security Write All
–
–
–
Security Write Own Password
–
–
–
Config Read All
–
–
–
Config Write All
–
–
–
Backup
–
–
–
Restore
–
–
–
Upgrade
–
–
–
Business Partner Role
–
–
–
Service Provider Role
–
–
–
Administrator Role
–
–
–
End User Role
–
–
–
Rights
System Status
Group
Description
This group is
This group is
intended for
used by the
users using the one-X Portal for
System Status
IP Office
application.
application.
Note that
System Status
Access is also
used by the IP
Office Customer
Call Reporter
application.
System Status
TCPA Group
–
IPDECT Group
This group is
used for IP
DECT R4
provisioning
services.
System Status Access
–
–
Read all configuration
–
–
System Control
–
–
Enhanced TSPI
Enhanced TSPI Access
–
–
HTTP
DECT R4 Provisioning
–
–
Web Service
Security Read All
–
–
–
Security Write All
–
–
–
Security Write Own Password
–
–
–
–
–
–
Business Partner Role
–
–
–
Service Provider Role
–
–
–
Administrator Role
–
–
–
End User Role
–
–
–
Config Read All
Config Write All
Backup
Restore
Upgrade
Rights
SMGR
Admin
Description
Security
Admin
Backup
Admin
Upgrade
Admin
System
Admin
Main
Admin
Business Custome Maintain
Partner r Admin
er
These groups are intended for users using web services to configure and manage the system.
For IP Office Branch Environment deployments, these groups are used by SMGR users for web
service access to the system.
Web
Security
Services Read All
–
–
–
–
–
–
Security
Write All
–
–
–
–
–
–
–
–
–
–
–
–
Security
Write
Own
Passwor
d
Release 9.0
IP Office Manager
–
Page 23
15-601011 Issue 9.01 (Monday, September 09, 2013)
Config
Read All
–
–
–
–
Config
Write All
–
–
–
–
Backup
–
–
–
Restore
–
–
–
Upgrade
–
–
–
–
· 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 188 settings.
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.
Release 9.0
IP Office Manager
Page 24
15-601011 Issue 9.01 (Monday, September 09, 2013)
Security Mode: Default Security Users
2.3 Security Administration
This section also covers a basic introduction to security principles and the security mechanisms.
· NOTE: If security administration is of no concern, the default settings allow modification of all system features
without restriction. It is recommended as a minimum that default passwords are changed.
Introduction
Administration security is achieved using a number of optional cryptographic elements:
· Access control to prevent unauthorized use.
· Encryption to guarantee data remains private.
· Message Authentication ensures data has not been tampered with.
· Identity assures the source of the data.
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.
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:
Release 9.0
IP Office Manager
Page 25
15-601011 Issue 9.01 (Monday, September 09, 2013)
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.
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.
IP Office 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.
Release 9.0
IP Office Manager
Page 26
15-601011 Issue 9.01 (Monday, September 09, 2013)
Security Mode: Security Administration
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.
Windows Certificate Store Usability
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
Release 9.0
IP Office Manager
Page 27
15-601011 Issue 9.01 (Monday, September 09, 2013)
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 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
Release 9.0
IP Office Manager
Page 28
15-601011 Issue 9.01 (Monday, September 09, 2013)
Security Mode: Security Administration
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 IP
Office, 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.
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.
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.
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.
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.
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).
Release 9.0
IP Office Manager
Page 29
15-601011 Issue 9.01 (Monday, September 09, 2013)
· 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 IP Office.
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).
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 IP Office 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.
Release 9.0
IP Office Manager
Page 30
15-601011 Issue 9.01 (Monday, September 09, 2013)
Security Mode: Security Administration
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.
Release 9.0
IP Office Manager
Page 31
15-601011 Issue 9.01 (Monday, September 09, 2013)
Release 9.0
IP Office Manager
Page 32
15-601011 Issue 9.01 (Monday, September 09, 2013)
Chapter 3.
Configuration Mode
Release 9.0
IP Office Manager
Page 33
15-601011 Issue 9.01 (Monday, September 09, 2013)
3. Configuration Mode
This section of the documentation covers the operation of Manager when being used to edit the configuration of a system
running in IP Office Essential Edition, IP Office Preferred Edition or IP Office Advanced Edition modes. Much of it is also
applicable for when also editing the configuration of systems running in Server Edition mode, for which addition functions
are detailed in the Server Edition Mode 71 chapter.
This section is divided as follows.
The Configuration Mode Interface 35
This part details the screen elements of
Manager's configuration mode interface.
Editing Configuration Settings 51
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
42
· Using the Details Pane
· Using the Error Pane
· Altering the Interface
Release 9.0
IP Office Manager
44
46
48
41
51
57
· Creating a New Configuration
61
· Importing and Exporting Settings
· Sending a Configuration
62
65
· Saving a Configuration Offline
· Erasing the Configuration
64
67
Page 34
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode:
3.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 records 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 41
This pane shows icons for the different types of record that the configuration can contain. Each type is followed by the
number of records of that type already in the configuration. Selecting an icon displays the matching records in the
group pane and navigation toolbar.
· Group Pane 42
This pane lists all the records that match the type selected in the navigation pane or navigation toolbar. The list can be
sorted by clicking on column heading. Selecting a record in this pane displays its details in the details pane.
· Details Pane 44
This pane shows the configuration settings for a particular record within the configuration. The record is selected using
the navigation toolbar or using the navigation pane and group pane.
· Error Pane 46
This pane shows errors and warnings about the configuration settings. Selecting an item here loads the corresponding
record into the details pane.
· Status Bar 50
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.
Release 9.0
IP Office Manager
Page 35
15-601011 Issue 9.01 (Monday, September 09, 2013)
3.2 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.
· The service user name used to receive the configuration and that user's associated operator rights.
Release 9.0
IP Office Manager
Page 36
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode: Title Bar
3.3 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 131 .
The commands are context sensitive. Commands are grayed out when not
usable.
For some commands, an symbol indicates that there are sub-commands
from which a selection can be made.
The following menu options are available:
File
Open Configuration... 134
Close Configuration 134
Save Configuration 134
Save Configuration As... 134
Change Working Directory...
Preferences 136
135
Offline
Create New Config 143
Open File... 143
Open File Set... 143
Send Config... 144
Receive Config... 144
Advanced
Erase Configuration (Default) 145
Reboot 145
System Shutdown... 146
Upgrade.. 147
Change Mode... 149
Audit Trail... 151
Security Settings... 153
Erase Security Settings... 153
Embedded File Management 153
Format IP Office SD Card 154
Recreate IP Office SD Card 155
Memory Card Command
162
Shutdown...
162
Start Up...
Launch Voicemail Pro Client
System Status 156
LVM Greeting Utility 157
Initial Configuration 157
Add/Display VM Locales 161
Release 9.0
IP Office Manager
156
Backup/Restore
Backup Binaries and Configurations 162
Restore Binaries and Configurations 162
Import/Export
Import 164
Export 163
Exit
162
164
View
Toolbars 165
Navigation Pane 165
Group Pane 165
Details Pane 165
Error Pane 165
Simplified View 165
TFTP Log 166
Tools
Extension Renumber 167
Line Renumber 167
Connect To 167
SCN Service User Management 169
Server Edition Service User Management
Busy on Held Validation 170
MSN 170 Configuration 170
Print Button Labels 171
Import Templates 172
169
Page 37
15-601011 Issue 9.01 (Monday, September 09, 2013)
3.4 Toolbars
A number of toolbars can be displayed by Manager. These are:
· Main Toolbar
38
· Navigation Toolbar
· Details Toolbar
40
40
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.
3.4.1 The Main Toolbar
This toolbar is displayed at the top of the Manager window, just below the menu bar. 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 57
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 57
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 65
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 41
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.
41
42
46
·
Validate Configuration 46
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 142 .
·
Create New Configuration 61
Runs a series of dialogs that create a new configuration from scratch.
Release 9.0
IP Office Manager
Page 38
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode: Toolbars
·
Connect To 167
For a standalone system, start the process of adding it to a multi-site network. Not available in Server Edition
mode.
·
Voicemail Pro Client 156
Launch the Voicemail Pro client if also installed on the Manager PC.
·
Server Edition Solution View 74
Switch to the solution view 74 . This option is only shown when Manager is running in Server Edition mode.
Release 9.0
IP Office Manager
Page 39
15-601011 Issue 9.01 (Monday, September 09, 2013)
3.4.2 The Navigation Toolbar
This toolbar provides drop down lists which can be used to navigate to particular records 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 42 and or navigation
pane 41 hidden in order to maximize the display space for the details pane.
This toolbar is not available when Manager is in security mode
21
.
3.4.3 The Details Toolbar
This toolbar is shown in the top-right of the details pane. The options within the toolbar may vary or be greyed out
depending on the actions allowed for a particular configuration record.
·
Create a New Record
The
arrow is used to select the record type to be created. For example; when adding an extension clicking
may allow selection of a VoIP Extension or IP DECT Extension.
·
Export as Template (Binary)
This option is shown for Server Edition mode. It allows certain types of records to be saved as templates
These can then be used to create new records.
78
.
·
Delete Current Record
Delete the currently displayed record.
·
Validate Current Record
By default records are validated when opened and when edited. This is set through the Manager application's
validation settings 142 .
· < > Previous Record/Next Record
Click < or > at the top-right to move to the previous or next record.
Release 9.0
IP Office Manager
Page 40
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode: Toolbars
3.5 Using the Navigation Pane
This pane shows icons 194 for the different types of record that the
configuration can contain. Each type is followed by the number of records
of that type already in the configuration. When Manager is used in security
mode, this pane is also used by Manager in security mode 21 to display
records for security settings.
Selecting an icon displays the matching records in the group pane,
navigation toolbar and details pane. Note that Manager is used to configure
different types of system. Therefore the icons shown may vary depending
on the type of system you are configuring. For descriptions of the different
icons refer to Configuration Settings 194 .
The information in the pane also depends on whether the group pane 42 is
visible or not. If the group pane is visible, the navigation pane just shows
icons for accessing which types of records should be shown in the group
pane. The group pane can then be used to select which of those records is
currently shown in the details pane. If the group pane is not visible, the
navigation pane shows icons for each type of records and under those icons
for each individual record. The navigation pane can then be used to select
which of those records is currently shown in the details pane.
Expanding/Collapsing the Navigation Tree
· 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 record type and allow the record type to be
expanded to display all the existing records of that type.
· The
icon in the main toolbar can also be used to collapse all the
expanded record types shown in the navigation pane.
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 the Navigation Pane
The navigation pane can be shown or hidden. To do this use either of the
following methods.
1. From the main toolbar, use the
icon or select View. Those panes
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.
Release 9.0
IP Office Manager
Page 41
15-601011 Issue 9.01 (Monday, September 09, 2013)
3.6 Using the Group Pane
This pane lists all the records that match the type selected in the navigation pane or navigation toolbar. The list can be
sorted by clicking on a column heading. Selecting a record in this pane displays its details in the details pane.
The icons used in the pane may vary according to the state of the record. 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 21 to display records
for security settings.
Sorting the List
The records 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 record type, which details are shown in the group pane can be customized. Also the order of the column can be
adjusted.
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 righthand 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 lefthand 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.
Release 9.0
IP Office Manager
Page 42
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode: Using the Group Pane
Adding a New Record
The group pane can be used to add a new record 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 record to create. Click
the arrow and select an option from the list.
2. Use the details pane to configure the new record.
3. Click OK in the details pane.
Deleting an Record
1. Select the record to be deleted by clicking on it.
2. Right-click on the pane and select Delete.
Validating an Record
1. Select the record 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 record 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.
Release 9.0
IP Office Manager
Page 43
15-601011 Issue 9.01 (Monday, September 09, 2013)
3.7 Using the Details Pane
Whenever a selection is made through the group pane or the navigation toolbar, the settings for the matching record are
shown in the details pane. This pane is also used by Manager in security mode 21 to display records for security settings.
The details are grouped into tabs. The tabs available may vary depending on what particular type of record is being
viewed.
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.
Release 9.0
IP Office Manager
Page 44
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode: Using the Details Pane
Editing an Record
1. The method of entering a record varies as different fields may use different methods. For example text record
boxes or drop down lists.
2. By default when changes are made, they are validated once another field is selected. See File | Preferences |
Validation 142 .
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 Record
1. Click
at the top-right of the details pane.
2. Select the type of record required. For example, with extensions you can select from H.323 Extension or SIP
Extension.
Deleting an Record
1. Click
at the top-right of the details pane.
Validating an Record
1. Click
at the top-right of the details pane.
Moving to the Previous or Next Record
1. Click < or > at the top-right to move to the previous or next record.
Selecting a Tab
1. To view the detail stored on a particular tab, click on the name of that tab.
2. If the tab required is not shown, use the
controls if shown on the right to scroll through the available tabs.
The tabs available may vary depending on what particular type of record 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 records 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 Multiline Tabs.
3. Click OK.
Release 9.0
IP Office Manager
Page 45
15-601011 Issue 9.01 (Monday, September 09, 2013)
3.8 Using the Error Pane
Validation is a process where Manager checks configuration records 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 142 tab.
Icons
The icons used for errors and warnings are as follows. These are shown in the error pane and also next to the related
field in the details pane. In the details pane, the error or warning description is shown when the cursor is hovered over
the icon.
·
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.
Altering the Automatic Validation Settings
The settings for automatic validation by IP Office Manager are adjustable.
1. Select File | Preferences.
2. Select the Validation tab. Select the options required.
· Validate configuration on open
Automatically validate configuration files when they are opened in IP Office 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.
3. Click OK.
Revalidating Configuration Settings
If necessary, you can force a validation check of the whole configuration or of the current record shown in the details
pane.
1. To validate the whole configuration, click
2. For a particular record, 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 record tab into the details pane.
2. The < and > can be used to move to the next error or warning in the error pane.
Release 9.0
IP Office Manager
Page 46
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode: Using the Error Pane
Showing or Hiding the Error Pane
The error pane is automatically displayed if a configuration containing errors or warnings is loaded into IP Office 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.
Release 9.0
IP Office Manager
Page 47
15-601011 Issue 9.01 (Monday, September 09, 2013)
3.9 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.
Release 9.0
IP Office Manager
Page 48
15-601011 Issue 9.01 (Monday, September 09, 2013)
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 records 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 Multiline Tabs.
3. Click OK.
Release 9.0
IP Office Manager
Page 49
15-601011 Issue 9.01 (Monday, September 09, 2013)
3.10 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 records. The cause may be a device or application, other than an IP Office, 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
IP Office 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.
Release 9.0
IP Office Manager
Page 50
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode: The Status Bar
3.11 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 (IP500 V2).
· 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 IP500 V2 boot process and SD card
usage refer to the IP Office 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 IP500 V2 system's, the System SD card.On IP500 V2 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 201 .
· When the system is shutdown using the correct shutdown method
to the non-volatile memory and System SD card.
146 ,
the configuration in RAM memory is copied
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 it 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 53 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.
Release 9.0
IP Office Manager
Page 51
15-601011 Issue 9.01 (Monday, September 09, 2013)
· 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.
Release 9.0
IP Office Manager
Page 52
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode: Editing Configuration Settings
3.11.1 Mergeable Settings
The table below shows the configuration records 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
200
- System
204
213
Directory
450
452
Firewall Profile
*3
219
IP Route
234
- System Events
- CDR/SMDR
- Twinning
453
238
Account Code
License
254
Tunnel
Extension
335
461
*4
336
Hunt Group
389
Short Code
417
464
468
User Rights
348
Service
458
245
246
Control Unit
RAS
440
206
- LDAP
User
WAN Port
Pre-3.2
*2
214
- Telephony
Line
3.2+
Time Profile
- Voicemail
- VoIP
Mergeable
*1
201
- LAN1/LAN2
- DNS
Pre-3.2
482
Auto Attendant
475
Authorization
Code 479
ARS
492
418
431
Incoming Call Route
433
· *1 - 3.2+ | System | System
Changes to Locale 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.
Release 9.0
IP Office Manager
Page 53
15-601011 Issue 9.01 (Monday, September 09, 2013)
3.11.2 Configuration Size
There are maximum size limits to the configuration file that can be loaded into a control unit. They are:
Control Unit
Maximum
Configuration File
Size
IP500
1.0MB
IP500 V2
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 records can be added to the configuration without using Manager
(for example call log records and directory records made from phones). If, during the overnight backup to flash
memory 51 , the configuration if found to be too large, records will be removed until the configuration is
sufficiently small to be backed up. The recordsremoved are call log records, system directory records and then
personal directory in that order. Note that those records 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 records in the configuration cannot be given as they vary. The list below gives typical values, in
bytes, for common records:
Physical Extension: 70.
Intranet Service: 240.
Firewall Profile: 40.
IP Extension: 70.
WAN Service: 400.
User: 170.
RAS Service: 110.
Custom Firewall Record:
80.
User Short Code: 40.
Incoming Call Route: 30.
DSS Button: 20.
WAN Port (PPP): 70.
Hunt Group: 100.
WAN Port (FR): 120.
Hunt Group member: 10.
Directory Record: 70.
System Short Code: 10.
Time Profile: 40.
Normal Service: 220.
Time Profile Record: 20.
Release 9.0
IP Office Manager
IP Route (Static): 30.
License Key: 40.
Account Code: 40.
Logical LAN: 60.
Tunnel (L2TP): 200.
Tunnel (IPSec): 110.
Page 54
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode: Editing Configuration Settings
3.11.3 Setting the Discovery Addresses
By default, when
or File | Open configuration is selected, Manager's Select IP Office menu appears. It performs a
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.
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
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 139 .
Release 9.0
IP Office Manager
Page 55
15-601011 Issue 9.01 (Monday, September 09, 2013)
Changing the Initial Discovery Settings
The Discovery tab of the 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.
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.
· 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:
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 57 dialogue is replaced by a Enter Unit DNS Name or IP Address field.
· SCN Discovery:
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
Small Community Network must be running Release 6.0 or higher software. See Small Community Network
Management 112 . This does not override the need for each system in the Small Community Network to also be
reachable by the TCP Discovery and or UDP Discovery settings above and accessible by the router settings at
the Manager location.
Release 9.0
IP Office Manager
Page 56
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode: Editing Configuration Settings
3.11.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 139 ). 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 136 , 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 Server Edition systems are detected, they are grouped together. By default the configuration of those
systems cannot be opened using Manager in Advanced View mode and the configuration of a Primary Server
can only be opened if the Open with Server Edition Manager option is also selected. See Server Edition
Mode 597 .
· If Manager has been set with SCN Discovery 139 enabled, systems in a Small Community Network are
grouped together. The checkbox next to the network name can be used to load the configurations of all the
configurations into Small Community Network management 112 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 |
Discovery 139 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
139
59
option.
· Systems found but not supported by the version of Manager being used will be listed as Not Supported.
· If the system detected is running software other than from its primary folder, a
warning icon will be
shown next to it. The configuration can still be opened but only as a read-only file.
3. When you have located the system required, check the box next to the system and click OK.
· If the system selected is a Server Edition system and Manager is not running in Server Edition mode, an
Open with Server Edition Manager checkbox is shown and pre-selected. Clicking OK will switch Manager to
its Server Edition mode before loading the configuration.
4. The system name and password request is displayed. Enter the required details and click OK.
The name and password used must match a service user account configured within the system's security
settings.
5. Additional messages will inform you about the success or failure of opening the configuration from the system.
· The method of connection, secure or insecure, attempted by Manager is set the applications Secure
Communications 141 preferences setting.
· When Secure Communications is set to On, a
Manager status field.
padlock icon is displayed at all times in the lower right
· New installations of Manager default to having Secure Communications enabled. This means Manager by
default attempts to use secure communications when opening a configuration.
· For Server Edition systems, Manager will always attempt to use secure communications regardless of the
Secure Communications setting.
· If no response to the use of secure communication is received after 5 seconds, Manager will offer to fallback
to using unsecured communications.
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.
Release 9.0
IP Office Manager
Page 57
15-601011 Issue 9.01 (Monday, September 09, 2013)
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 201 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.
3.11.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.
Release 9.0
IP Office Manager
Page 58
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode: Editing Configuration Settings
3.11.6 Known System Discovery
The Select IP Office menu normally displays systems discovered by Manager using either UDP broadcast and or TCP
requests (see Setting the Discovery Addresses 55 ). 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 known system details.
1. Select File | Change Working Directory.
2. In the Known Units 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 Known System Discovery
1. When the Select IP Office screen is displayed click on Known 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 records 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 record 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 records 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.
Release 9.0
IP Office Manager
Page 59
15-601011 Issue 9.01 (Monday, September 09, 2013)
3.11.7 Creating New Records
There are a number of ways in which you can add new records to the configuration currently loaded in Manager.
Adding a New Record Using the Details Pane
1. Use the navigation pane, groups pane or navigation toolbar, select an existing record of the type required.
2. Click
at the top-right of the details pane.
3. Select the type of record required. For example, with extensions you can select from H.323 Extension or SIP
Extension.
4. Complete the settings for the new record and click OK.
Adding a New Record Using the Group Pane
1. Using the navigation pane or navigation toolbar, select the type of record required.
2. Right-click on the group pane and select
New.
3. If a list is displayed, select the specific type of record required.
4. Complete the settings for the new record and click OK.
Adding a New Record Using the Navigation Pane
1. In the navigation pane, right-click on the type of record required and select
New.
2. If a list is displayed, select the specific type of record required.
3. Complete the settings for the new record and click OK.
Importing Records
New records can be created for users, hunt groups, short codes and directory entries by importing files. See Importing
and Exporting Settings 62 .
Automatic Creation of Records
There are scenarios where new records are automatically added to the configuration:
· Certain default records
configuration is erased
68
are added to the configuration when a new system is started or when a system
145 .
· New records for extensions and lines are automatically added to match the hardware present when a system is
started or rebooted.
· For telephones connected via IP links (H.323, SIP and DECT), the system can be configured to automatically
create extension and or user records to match the telephone.
Using Templates to Create Records
Manager supports a number of methods by which new records can be created from templates.
· Trunk Templates 256
SIP trunks can be created from templates. For analog trunks, records are automatically created by the presence of
the trunk hardware, however a template can then be applied to an analog trunk.
· Server Edition 78
When being used to edit the configuration of Server Edition systems, Manager has a number of additional options
to export existing records as templates and to create new records from those templates.
Release 9.0
IP Office Manager
Page 60
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode: Editing Configuration Settings
3.11.8 Creating an 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 the installation process.
· 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 your responsibility to confirm what equipment is supported in your locale.
Creating a New Configuration
1. Close or save any configuration currently open.
2. Click
in the main toolbar or select File | Offline | Create New Config.
3. You should set the Configuration, Locale, Extension Number Length and System Unit first. Changing any of
these after you start selecting other system hardware will reset the hardware selections.
a. Select the type of Configuration you want to create. The other options available will change depending on
the selection. If the menu has been started from Manager running in Server Edition mode, the only option is
Server Edition Edition.
b. Select the Locale for the system. This defines a range of features such as default telephony settings.
c. The Extension Number Length setting value can be None or 3 to 9 (3 to 15 for Enterprise Branch
deployments). 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.
d. Select the type of System Unit.
4. Select the hardware components for the system. For a Server Edition system this is only necessary if a Expansion
System (V2) is selected as the System Units option.
a. Select the additional cards to include in the control unit. The number and type of cards selectable will depend
on the control unit type.
b. Select the external expansion modules to also include in the system.
c. Click OK.
5. For non-Server Edition systems, the configuration is created and loaded into Manager. For Server Edition systems,
the Initial Configuration 157 menu for the selected type of system unit is displayed. Complete the menu and click
Save.
6. Once this configuration has been edited as required it can be saved on the PC or sent to a system.
a. To Save a Configuration File on the PC
Use File | Save Configuration.
b. To Send the Configuration to a System
If the system which you want to use the configuration is available, use File | Offline | Send Configuration
143 to send the configuration to it.
·
! WARNING: This action will cause the system to reboot and will disconnect all current calls and service.
· Ensure that you have a copy of the systems existing configuration before overwriting it with the off-line
configuration.
· After sending the configuration, you should receive the configuration back from the system and note any
new validation errors shown by Manager. For example, if using Embedded Voicemail, some sets of prompt
languages may need to be updated to match the new configurations locale setting using the Add/
Display VM Locales 161 option.
Release 9.0
IP Office Manager
Page 61
15-601011 Issue 9.01 (Monday, September 09, 2013)
3.11.9 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 (LDAP Version 2).
234
(System | Directory Services | LDAP
· The system also supports HTTP
records.
237
234 )
(System | Directory Services HTTP
for automatic importation of directory
237 )
for automatic importation of directory
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 records 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 (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.
Release 9.0
IP Office Manager
Page 62
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode: Editing Configuration Settings
Exporting Settings
1. Select File | Import/Export... from the menu bar.
2. Select Export.
3. Select the type of file. The list of exportable record 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 records that match a record 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.
Release 9.0
IP Office Manager
Page 63
15-601011 Issue 9.01 (Monday, September 09, 2013)
3.11.10 Copying and Pasting
Manager supports the normal Windows methods of cutting, copying, pasting and deleting records 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 a record or text field and then right-clicking.
Copy and paste can be used with the navigation and group panes to create a new record 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 record or a different record, care
should be taken to ensure that the fields use the same type of data. Similarly copying a record in the navigation or group
pane and then pasting it into the details pane will prompt Manager to paste the copied records data into the first field of
the current record in the details pane. As a general rule, cut and paste actions should be used with the same pane and
within similar record 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 482 in the Configuration Settings section.
3.11.11 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) 141 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.
Release 9.0
IP Office Manager
Page 64
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode: Editing Configuration Settings
3.11.12 Sending a Configuration
The current configuration settings open within Manager can be sent to the system. The method depends on whether
Manager is being used to edit the configuration of a single system or a network of systems.
Sending an Individual System Configuration
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.
· 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 53 .
· 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 or Timed 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
· The message Failed to save the configuration data. (Internal error) may indicate that the IP500 V2
system has booted using software other than that in its System SD card's primary folder.
Sending Multiple Configurations
When Manager is running in Server Edition mode
the same time.
1. Click
71
or SCN Management mode
112 ,
it loads multiple configurations at
in the main toolbar or select File | Save Configuration from the menu bar.
Release 9.0
IP Office Manager
Page 65
15-601011 Issue 9.01 (Monday, September 09, 2013)
2. The menu displayed only shows details for those systems where the system configuration has been changed and needs
to be sent back to the system.
· Select
By default all systems with configuration changes are selected. If you want to exclude a system from having
its configuration updated, either deselect it or cancel the whole process.
· Change Mode
If IP Office 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 53 .
· 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 Incoming Call Barring and Outgoing Call Barring options.
· Store Offline
It is possible to add a reference for a Server Edition Secondary Server or for an expansion server and
used create offline configuration to create a configuration file for that system even though it is not
physically present. Store Offline saves that configuration on the Server Edition Primary Server in its file
store. The same file is retrieved from there until such time as the physical server is present at which time
you are prompted whether to use the stored file or the actual servers current configuration.
· 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 Incoming Call
Barring and Outgoing 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.
· Incoming Call Barring
This setting can be used when the reboot mode When Free or Timed is selected. It bars the receiving of any
new calls.
· Outgoing Call Barring
This setting can be used when the reboot mode When Free or Timed is selected. It bars the making of any
new calls.
3. Click OK. The progress of the sending of each configuration is displayed.
Release 9.0
IP Office Manager
Page 66
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode: Editing Configuration Settings
3.11.13 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 68 . This process does not erase the security settings of the system.
Erasing the Configuration
1. Select File | Advanced | Erase Configuration (Default).
2. Enter a valid user name and password.
3. The system will be rebooted.
Release 9.0
IP Office Manager
Page 67
15-601011 Issue 9.01 (Monday, September 09, 2013)
3.11.14 Default Settings
The following applies to new systems and those defaulted using the Erase Configuration 67 command. They also apply to
IP500 V2 control units defaulted using the reset button on the rear of the unit (refer to the Installation manual for details
of using the reset button).
Mode
IP500 V2 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 Basic
Edition - Quick Mode PBX System operation.
· 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 Basic
Edition - Quick Mode Key System operation.
· IP Office Partner Edition
A system fitted with this type of card will default to A-Law telephony and IP Office Basic Edition - PARTNER®
Mode operation.
· IP Office Norstar Edition
A system fitted with this type of card will default to U-Law telephony and IP Office Basic Edition - Norstar®
Mode operation.
· Enerprise Branch
Use this option for an SD card intended to be used with an IP Office system running in Enterprise Branch
Mode. There is a separate SD card for Enterprise Branch. The Enterprise Branch SD card can only be used
for IP Office operation and cannot be used to change modes to IP Office. You also cannot use or change
an IP Office SD card for use with an IP Office Enterprise Branch system.
·
! Warning
Do not re-purpose a Enerprise Branch card for use with any other IP Office mode. Doing so may damage
the SD card and make it unusable for your Enterprise Branch system.
Default Short Codes
IP400 control units are manufactured as either A-Law or U-Law variants. For IP500 and IP500 V2 control units, A-Law or
U-Law operation is determined by the Feature Key dongle installed in the system. Depending on the variant, a default
system will use different sets of default short codes. See the Default System Short Code List 714 .
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 a 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 153 command
should be used.
Release 9.0
IP Office Manager
Page 68
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode: Editing Configuration Settings
Default Standard Mode Telephony Configuration Settings
· A hunt group Main is created with extension number 200. The first 16 extensions on the systems are added to the
group.
· All physical extensions ports are numbered from extension number 201 upwards. A matching user record for each
extension is also created.
· A default incoming call route for all voice calls is created, with the default hunt group Main as its destination.
· A default incoming call route for data calls is created with the default RAS record DialIn as its destination.
· All lines are defaulted to Incoming Group ID and Outgoing Group ID of 0.
· Default short codes are created based on whether the system's locale is A-Law or U-Law. See Default Short Codes
714 .
Default Server Edition Telephony Configuration Settings
· No users except NoUser.
· All extensions are unnumbered.
· No default hunt group or incoming calls routes are created.
· All auto-create options are off by default.
Release 9.0
IP Office Manager
Page 69
15-601011 Issue 9.01 (Monday, September 09, 2013)
Chapter 4.
Server Edition Mode
Release 9.0
IP Office Manager
Page 70
15-601011 Issue 9.01 (Monday, September 09, 2013)
Server Edition Mode:
4. Server Edition Mode
When the configuration from a Server Edition solution is loaded into Manager, Manager switches to Server Edition mode
operation.
Release 9.0
IP Office Manager
Page 71
15-601011 Issue 9.01 (Monday, September 09, 2013)
4.1 Installing IP Office Manager
Manager is used to load and edit the telephony configuration of Server Edition systems, ie. the configuration used by the
IP Office services hosted on the servers. It is a Windows PC application. The file store on the Primary Server includes the
installation files for installing Manager and for installing the Voicemail Pro Client.
· Note that the Manager install is a minimal install just for the administration and maintenance of Server Edition
systems. It does not include all the files found in the IP Office Administrator Applications installation that is
required for non-Server Edition systems.
IP Office Manager 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 IP Office Manager if
not already present.
Windows 7
· *Includes disk space required for .NET2 component.
· Language Support
The IP Office Manager application can run in Brazilian Portuguese, Simplified Chinese, Dutch, French, German,
Italian, Mexican Spanish, Russian, UK English and US English. By default the language used is determined by the
best match to the PC's regional setting. To change the language used see Changing the IP Office Manager
Language 18 .
Installing Manager
1. Using a web browser, enter the https:// followed by the IP address of the server and then :7070.
2. Enter the Logon and Password details for the server and click Login. The defaults are Administrator and
Administrator.
3. On the Home menu, click on Manage. If a useable version of Manager is not already installed or an incorrect
version is installed, a menu similar to the following is displayed. The presence of a suitable Voicemail Pro Client,
used to administer the voicemail server, is also checked.
4. Click on the link or links to download the installation files.
Release 9.0
IP Office Manager
Page 72
15-601011 Issue 9.01 (Monday, September 09, 2013)
Server Edition Mode: Installing IP Office Manager
5. Once the files are downloaded to the PC, click on the files to run the installation for the applications.
Release 9.0
IP Office Manager
Page 73
15-601011 Issue 9.01 (Monday, September 09, 2013)
4.2 Solution View
When the configuration of a Server Edition solution is loaded into Manager, Manager starts with the Server Edition
Solution View menu. This menu includes the system inventory of the servers, links for launching various functions and a
summary table of the servers and the links between the servers.
Displaying the Server Edition Solution View
Manager normally starts with the Server Edition Solution View when the configuration for a Server Edition network is
loaded. However, there are a number of ways to return to the solution view at any time.
1. Click on the
Server EditionSolution View icon in the toolbar.
or
1. Click on the
Solution icon in the navigation pane.
Using the Solution View
The solution view can be used to perform a range of functions.
· Configuring the Systems
· Starting System Status
599
601
· Voicemail Administration
602
· Adding a Secondary Server
605
· Adding an Expansion System
606
· Showing the System Inventories
· Remove an expansion system
· Displaying the Solution View
· On-boarding
607
607
608
607
· Setting Up Resilience
· Starting Web Control
603
· Synchronize configurations
608
607
Interpreting and Using the Network Table
The table at the bottom of the solution view give a quick overview of all the servers and whether their configuration was
loaded into Manager.
· Description
This column describes the type of server being detailed by the row. It also includes a status indicator for the
configuration file that Manager has loaded for the server.
Release 9.0
IP Office Manager
Page 74
15-601011 Issue 9.01 (Monday, September 09, 2013)
Server Edition Mode: Solution View
·
Green - Configuration Loaded
The configuration of the server has been successfully retrieved and can be edited in Manager.
·
Yellow - Offline Configuration Loaded
The configuration loaded is an offline configuration. This will appear for a server that has been added to the
solution when the physical server is not currently connected on the network and Create Offline
Configuration was selected. The offline configuration file is stored on and retrieved from the primary server
until it can be replaced by or replace the actual server configuration.
·
Red - Configuration Not Loaded
There is no configuration for the system loaded even though the solution configuration includes an entry for
the server. This will appear for a server that has been added to the network when the physical server is not
currently connected on the network and Create Offline Configuration was not selected. If may also appear
if the server is currently not contactable.
·
Grey - No Connection
This icon is used in conjunctions with the others to indicate that there is no current connection to the server.
For example:
· In conjunction with a green icon, it indicates that the server for which a configuration has been loaded
cannot be detected on the network. This may be a temporary issue caused by that particular server
rebooting following a configuration change.
· In conjunction with a red icon, it indicates that the server for which a configuration has not been loaded
has now been detected on the network. Saving and reloading the solution configuration may resolve the
issue.
· Name
This is the server name as taken from its configuration file. Offline is shown if no configuration file is available.
· Address
The IP address of the server. This is the address that is used when Manager attempts to retrieve the servers
configuration when loading the solution configuration.
· Primary Link
This value indicates the configuration settings of the H.323 IP trunk between the primary server and the server
indicated by the row. It should state Bothway. If it states anything other, that indicates a mismatch in H.323 IP
trunk configuration between the system and the primary server. To correct this, right-click on the row and select
Connect to Primary.
· Secondary Link
This column is only shown after a secondary server has been added 605 to the configuration of the solution. The
value indicates the configuration settings of the H.323 IP trunk between the secondary server and the server
indicated by the row. It should state Bothway. If it states anything other, that indicates a mismatch in H.323 IP
trunk configuration between the system and the secondary server. To correct this, right-click on the row and
select Connect to Secondary.
· Users Configured
This column summarizes the number of users (other than NoUser) configured on the server. A total for the whole
network is shown in the Solution row.
· Extensions Configured
This column summarizes the number of extensions configured on the server. A total for the whole network is
shown in the Solution row.
Right-clicking on a server in the table may present a number of action. The actions available vary with the current state
of the network configuration.
· Remove
Remove the server from the solution configuration.
· Connect to Primary
Repair the configuration of the H.323 IP trunks between the server and the primary server.
· Connect to Secondary
Repair the configuration of the H.323 IP trunks between the server and the secondary server.
· Create Offline Configuration
Create an offline configuration file for a server for which no actual configuration has been loaded. The Offline
Configuration 61 menu will be displayed followed by the Initial Configuration 157 menu for the server type. The
offline configuration file is saved on the primary server.
Release 9.0
IP Office Manager
Page 75
15-601011 Issue 9.01 (Monday, September 09, 2013)
4.3 System Inventories
Manager can be used to display a system inventory for any of the servers in the Server Edition solution. The system
inventory is a quick summary of key settings and information about the server. It can also display an overview system
inventory for the whole Server Edition solution.
Displaying a Server's System Inventory
The method for displaying the system inventory depends on what is currently being displayed by Manager.
1. In the Server Edition Solution View 74 , using the table at the bottom of the menu, click on the server for which
you want to display the system inventory. Click on Network for the inventory of the Server Edition network.
or
1. In the navigation pane, click on the
Click on the
Release 9.0
IP Office Manager
icon of the server for which you want to display the system inventory.
Network icon for the inventory of the Server Edition network.
Page 76
15-601011 Issue 9.01 (Monday, September 09, 2013)
Server Edition Mode: System Inventories
4.4 Record Consolidation
By default, when Manager is being used to maintain the configurations of the systems in a Server Edition solution, certain
types of configuration records are treated differently. Short Code, Incoming Call Route, Time Profile, Account Code
and User Rights records are only shown at the solution level and cannot be edited in individual system configurations.
However, Managerinvisibly replicates these records, adding a copy to the configuration of each system in the solution
and updating those copies when necessary.
Operation of record consolidation is controlled by the Manager Preferences 136 setting Consolidate Solution to Primary
Settings. By default that setting is selected. The setting has the following effects:
· If Consolidate Network to Primary Settings is selected:
· Entry and administration of Short Code, Incoming Call Route, Time Profile, Account Code and User
Rights records is performed only at the solution level.
· Those records are then automatically replicated in the configurations of all the systems in the solution but
are still only visible and editable at the solution level.
· When the configurations are loaded into Manager or when this setting is changed to become selected, if
any inconsistency between records are found, a Consolidation Report is displayed. This report allows
selection of whether to update the system to match the primary or to update the primary to match.
· If Consolidate Network to Primary Settings is not selected:
· Entry and administration of Short Code, Incoming Call Route, Time Profile, Account Code and User
Rights records can be performed at both the solution and individual system levels.
· Records entered and edited at the solution level are automatically replicated in the configurations of all
the systems in the solution. IP Office Manager displays a label on the record indicating that it is a record
that is shared across the solution.
· If a shared record is edited at the individual system level, that copy of the record is no longer shared with
the other systems. It will not be updated by any changes to the solution level version of the same
record.
· No consolidation checking for inconsistencies is done by Manager when the configurations are loaded.
Release 9.0
IP Office Manager
Page 77
15-601011 Issue 9.01 (Monday, September 09, 2013)
4.5 Templates
When running in Server Edition mode, Manager supports a number of template options. The settings for the following
types of configuration items can be saved as template files. New records of those types can then also be created from a
template file.
· User
· Firewall Profile
· Extension
(H.323, SIP, IP DECT)
· Time Profile
· IP Route
· Hunt Group
· ARS
· Service
· Line
(H.323, SIP, IP DECT)
· Tunnel
· Notes
· These template options are in addition to the existing trunk template 256 options useable for SIP and analog
trunks. The access to the controls detailed below is not affected by the Managerapplication's Enable
Template Options setting.
· Templates exported using Manager in Server Edition mode are saved by default on the Primary Server. This
means they are available to other administrators regardless of from which PC they are using Server Edition
Manager. This is different from Manager in non-Server Edition mode which exports templates to a local folder
on the PC on which Manager is being run.
Exporting Records as Templates
Each template file is given a file extension that indicates the template type. For example .usr for a user and .lne for a
line. By default the export dialog offers to save a template in the Manager application's \manager_files\template subfolder (typically C:\Program Files\Avaya\IP Office\Manager\manager_files\template). It is recommended that
you use this folder as Managerautomatically lists the available templates in that folder when creating a new record from
a template.
Exporting an Record as a Template from the Detail Pane
You can save a record shown in the details pane as a template. This method cannot be used with Tunnel and Service
records, for those use the alternate method shown further below.
1. Locate and display in the details pane the record that you want to use as a template.
2. Click on the
Export as Template (Binary) icon in the top-right.
3. Use the Save As dialog to name and save the template file on the PC. The file extension indicates the type of
template.
Exporting an Record as a Template from the Navigation Pane
You can save a record shown in the navigation pane as a template.
1. Locate the record in the navigation pane.
2. Right-click on the record and select Export as Template (Binary).
3. Use the Save As dialog to name and save the template file on the PC. The file extension indicates the type of
template.
Creating New Records from Templates
Once templates are available, they can be used to create new records in the configuration. This can be done via the
details pane or the navigation pane. Up to a maximum of 50 new entries can be created from a template at any time.
Creating a New Record from a Template from the Details Pane
While in the details pane you can use a template to create a new record of the same type as that currently shown. This
method cannot be used with Tunnel and Service records, for those use the alternate method shown further below.
1. In the details pane, click on the
Create a New Record icon.
2. Select New from Template (Binary).
Release 9.0
IP Office Manager
Page 78
15-601011 Issue 9.01 (Monday, September 09, 2013)
Server Edition Mode: Templates
3. The names of the available templates of the correct type for the record being created and available in Manager's
template folder are listed. Alternatively, the Open from file option can be used to browse to a template file stored
in another location.
4. You may be prompted for the number of new configuration entries to create using the selected template. In this
case up to 50 new configuration entries can be created at a time.
5. Some template settings may match existing records and will cause immediate validation errors or warnings.
Correct the fields showing
Error or
Warning icons and click OK.
Creating a New Record from a Template from the Navigation Pane
Using the navigation pane you can create new records from templates.
1. In the navigation pane, right-click on the type of record that you want to create.
2. Select New from Template (Binary).
3. The names of the available templates of the correct type for the record being created and available in Manager's
template folder are listed. Alternately, the Open from file option can be used to browse to a template file stored
in another location.
4. You may be prompted for the number of new configuration entries to create using the selected template. In this
case up to 50 new configuration entries can be created at a time.
5. Some template settings may match existing records and will cause immediate validation errors or warnings.
Correct the fields showing
Release 9.0
IP Office Manager
Error or
Warning icons and click OK.
Page 79
15-601011 Issue 9.01 (Monday, September 09, 2013)
4.6 Telephony Operation Configuration
Each server in the network acts as a separate telephone system and supports most of the features detailed for
standalone IP Office systems in the Configuration Settings 194 , Button Programming 793 , Appearance Button Operation
938 and Telephone Features 509 sections of this documentation. For features that are supported between systems in the
network, refer to Network Telephony Features 126 .
· Each system in the network automatically shares the extension numbers of users and hunt groups. These can be
dialed by any user regardless of which system they are hosted on and appear in the internal directories on Avaya
phones and applications.
· The external system directory held by the primary server is shared with all systems on the network. It is
accessible by all users through the directory on their Avaya phones and applications.
4.6.1 Incoming Call Routing
The routing of incoming external calls is controlled by Incoming Call Route
network.
433
entries added to the configuration of the
Determining which incoming call route is used is based on the call matching a number of possible criteria. In order of
highest priority first, the criteria, which if set must be matched by the call in order for the call to use that route are:
1. The Bearer Capability indicated, if any, with the call. For example whether the call is a voice, data or video call.
2. The Incoming 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.
The entries are shared by all systems in the network. If a specific route is required for a particular system, it should be
recalled that the Incoming Group ID assigned to a trunk or trunks can be used as one of the criteria that must be
matched on an incoming call route for calls to use that route.
Examples
The following are a number of examples that summarize the configuration changes necessary for incoming call routing.
These are simple examples and cannot cover all possible scenarios.
· Example 1: Routing All Calls to an Operator
81
· Example 2: Routing All Calls to an Operator Group
82
· Example 3: Routing DID Calls to Matching Extensions
Release 9.0
IP Office Manager
84
Page 80
15-601011 Issue 9.01 (Monday, September 09, 2013)
Server Edition Mode: Telephony Operation Configuration
4.6.1.1 Example 1: Routing All Calls to an Operator
In this scenario, all incoming external calls are routed to a single user extension number. Depending on the system
licensing, that user can be configured as a receptionist, using the IP Office SoftConsole application in parallel with their
phone to answer and distribute the incoming calls.
1. Setup the Trunk Incoming Group IDs
The Incoming Group setting of the external line on the Primary Server has been set to 8. The same incoming
group ID can be used on multiple lines and on lines on different systems.
· The location of the Incoming Group field varies depending on the type of trunk. For SIP trunks, it is set as
part of the SIP URI settings used by the trunk.
2. Configure the Call Destinations
A new user with extension number 201 is added to the configuration of the primary, along with a matching
extension for their IP phone.
· If the user is to use the IP Office SoftConsole application, they must be added to the configuration of the
primary server. Receptionist users are not supported on other systems in the network. If the user is not
intending to use IP Office SoftConsole, they could be located on any system in the network. External calls
would be routed to the system hosting the user.
3. Create an Incoming Call Route to Match the Calls
A new Incoming Call Route record is added to the configuration settings. The key settings used in this scenario
are listed below. All other fields are left at their defaults:
a. On the Standard tab:
The fields on this tab are used to set the criteria that are used to match incoming calls to call routes.
· Bearer Capability: Any Voice
This will match the incoming voice calls.
· Line Group ID: 8
This will match only calls on trunks where the trunk has its Incoming Group setting also set to 8.
· Incoming Number: blank
This will match any call.
b. On the Destination tab:
This tab is used to set the destination for calls that are matched to the incoming call route. If necessary
multiple destinations can be set, with Time Profiles used to set when the different destinations are used. For
this scenario we only have one destination we want to use.
· Using the Destination drop-down list, the 201 Receptionist user has been selected as the destination
for all calls. If they do not answer, the calls will go to their voicemail mailbox. This is the simplest form of
call routing. If required options such as a fallback destination could be specified and different destinations
to be automatically used outside the operators known hours of work.
4. Save the configuration.
Result
All incoming voice calls on the primary system's SIP trunks are now matched to the new incoming call route and are
directed to the receptionist to be answered or to leave a message.
Since the Incoming Call Route entry is by default replicated as part of the configuration used by all the servers,
applying the same Incoming Group setting to any trunk hosted by any other system in the network will route calls to
the same destination without any further configuration.
Release 9.0
IP Office Manager
Page 81
15-601011 Issue 9.01 (Monday, September 09, 2013)
4.6.1.2 Example 2: Routing All Calls to an Operator Group
In this scenario, all incoming external calls are routed to a single hunt group extension number. That hunt group can be
used to contain a number of user extension numbers and to specify the order in which new calls should be presented to
available users, whether calls should queue for an available user and a range of other features. This is an ideal solution
for scenarios where you have several receptionists who can answer incoming external calls.
The configuration is very similar to that used in Example 1. Once the additional users have been added and the hunt
group created, the hunt group extension number automatically becomes available as a selectable destination for
Incoming Call Routes.
1. Setup the Trunk Incoming Group IDs
The Incoming Group setting of the external line on the Primary Server has been set to 8. The same incoming
group ID can be used on multiple lines and on lines on different systems.
· The location of the Incoming Group field varies depending on the type of trunk. For SIP trunks, it is set as
part of the SIP URI settings used by the trunk.
2. Configure the Call Destinations
Any existing receptionist user plus any new receptionists need to be added as members of a hunt group.
· New extension users with extension numbers 201, 202 and 203 are added to the configuration of the
primary, along with a matching extension for their IP phones.
· A new hunt group with extension number 200 is added to the configuration of the primary and users 201,
202 and 203 are specified as members of the group.
3. Create an Incoming Call Route to Match the Calls
A new Incoming Call Route record is added to the configuration settings. The key settings used in this scenario
are listed below. All other fields are left at their defaults:
a. On the Standard tab:
The fields on this tab are used to set the criteria that are used to match incoming calls to call routes.
· Bearer Capability: Any Voice
This will match the incoming voice calls.
· Line Group ID: 8
This will match only calls on trunks where the trunk has its Incoming Group setting also set to 8.
· Incoming Number: blank
This will match any call.
b. On the Destination tab:
This tab is used to set the destination for calls that are matched to the incoming call route. If necessary
multiple destinations can be set, with Time Profiles used to set when the different destinations are used. For
this scenario we only have one destination we want to use.
· Using the Destination drop-down list, the 200 Reception group has been selected as the destination for
all calls. If they do not answer, the calls will go to their voicemail mailbox. This is the simplest form of call
routing. If required options such as a fallback destination could be specified and different destinations to
be automatically used outside the operators known hours of work.
4. Save the configuration.
Result
All incoming voice calls on the primary system's SIP trunks are now matched to the new incoming call route and are
directed to the receptionist to be answered or to leave a message.
Release 9.0
IP Office Manager
Page 82
15-601011 Issue 9.01 (Monday, September 09, 2013)
Server Edition Mode: Telephony Operation Configuration
Since the Incoming Call Route entry is by default replicated as part of the configuration used by all the servers,
applying the same Incoming Group setting to any trunk hosted by any other system in the network will route calls to
the same destination without any further configuration.
Release 9.0
IP Office Manager
Page 83
15-601011 Issue 9.01 (Monday, September 09, 2013)
4.6.1.3 Example 3: Routing DID Calls to Matching Extensions
In this scenario, the customer has subscribed to receive incoming number digits in the range 300 to 399 on certain calls.
They want those calls routed to match extension numbers on the system, ie. to users and hunt groups with the extension
numbers in the range 300 to 399.
1. Setup the Trunk Incoming Group IDs
The Incoming Group setting of the external line on the Primary Server has been set to 8. The same incoming
group ID can be used on multiple lines and on lines on different systems.
· The location of the Incoming Group field varies depending on the type of trunk. For SIP trunks, it is set as
part of the SIP URI settings used by the trunk.
2. Configure the Call Destinations
New extension users and hunt groups with extension numbers in the range 300 to 399 have been added to the
configurations of the systems as required to meet the customers needs.
3. Create an Incoming Call Route to Match the Calls
A new Incoming Call Route record is added to the configuration settings. The key settings used in this scenario
are listed below. All other fields are left at their defaults:
a. On the Standard tab:
The fields on this tab are used to set the criteria that are used to match incoming calls to call routes.
· Bearer Capability: Any Voice
This will match the incoming voice calls.
· Line Group ID: 8
This will match only calls on trunks where the trunk has its Incoming Group setting also set to 8.
· Incoming Number: 3XX
This will match any call where the incoming number received with the call ends in 300 to 399. If no
Incoming Number match occurs, the call will be matched to a default incoming call route with a blank
Incoming Number field as setup in examples 1 and 2.
· Note that this is acting of digits supplied by the line provider, it is not caller ID (ICLID) matching.
Caller ID matching can be done using the Incoming CLI field.
b. On the Destination tab:
This tab is used to set the destination for calls that are matched to the incoming call route. If necessary
multiple destinations can be set, with Time Profiles used to set when the different destinations are used. For
this scenario we only have one destination we want to use.
· In the Destination field, manually enter 3#. When this route is matched by a call, the # in the
destination is replaced by the incoming digits that matched the XX wildcards in the Incoming Number
field.
4. Save the configuration.
Result
Any incoming voice calls on the primary system's SIP trunks that now include 3XX at the end of an incoming number
supplied with the call are matched to this call route rather than to the route previously setup (Example 1 81 or Example
2 82 ) and are routed to the matching extension number. Calls where no incoming number match occurs are still matched
to the previous incoming call route with a blank Incoming Number field.
Release 9.0
IP Office Manager
Page 84
15-601011 Issue 9.01 (Monday, September 09, 2013)
Server Edition Mode: Telephony Operation Configuration
4.6.2 Outgoing Call Routing
When a user dials a number, it is checked in a number of ways:
· The number dialed is always checked first for a match to an extension number. If a match occurs, the call is
routed to the matching user or hunt group. This matching is against any extension number in the network, not just
local system extension numbers.
· If the dialing does not match an extension number, it is checked for a matching short code. Depending on the
source of the dialing, the checking is made against user short codes, user rights short codes and finally against
system short codes. See Short Codes 703 for full details.
· Dialing that is matched to a short code that uses the Dial feature is assumed to potentially be an outgoing
external call. The matching short code defines which where the call should be sent and what number to dial should
be sent.
· The normal practice is to route calls that match a Dial feature short code to an ARS form. The ARS form can
contain additional short codes to determine to which lines particular numbers are routed. Doing this also helps
keep external call short codes separate from short codes for other functions and thus easier to maintain.
Call Routing Recommendations
Calls can be routed to a trunk using short codes set in the configuration of a particular user, users (using User Rights),
system (using system short codes) or ARS short codes. The following are recommendations for the configuration on
external call routing in a network:
1. Use ARS short codes wherever possible. This simplifies configuration and maintenance by keeping call routing
short codes separate from any other short codes, making the configuration easier to implement and to understand.
It also means that the full range of other ARS features such as overflow and fallback routing can be used.
2. By default all calls are routed to the primary server and then fallback to the secondary. Implementing as much call
routing in the ARS settings of the primary as possible saves on having to implement multiple matching settings on
all the expansion servers in the network. This eases maintenance and the addition of new expansion servers.
Examples
The following are a number of examples that summarize the configuration changes necessary for outgoing call routing.
These are simple examples and cannot cover all possible scenarios. There are additional examples of how the settings in
the ARS forms can be used in the ARS section 497 of this documentation.
· Example 1: Using SIP Trunks Hosted by the Primary Server
· Example 2: Primary Trunk Fallback to Secondary Trunks
88
90
· Example 3: Using Trunks Hosted on a Expansion System (V2)
· Example 4: Local Branch Override
· Example 5: PSTN Tail-End-Hop-Off
94
97
99
Short Codes and ARS Forms
Outgoing call routing relies on short codes and ARS records in the system configuration. Refer to the relevant chapters
on Short Codes 703 and ARS 492 to understand how those types of configuration records are used.
The short method for describing short codes in this manual, for example 9N/Dial/./0, indicates the settings of the
following fields of a short code: Code/Feature/Telephone Number/Line Group ID. For a description of the individual
fields see Short Code 417 .
Release 9.0
IP Office Manager
Page 85
15-601011 Issue 9.01 (Monday, September 09, 2013)
4.6.2.1 Default Call Routing
For outgoing call routing, a combination of system short codes and ARS entries are used. The default operation is listed
below. The default configuration is not sufficient to complete call routing, additional configuration is required to route the
calls from the Primary Server to the external trunks hosted by the network.
· Summary
The default settings send all potential external calls to the Primary Server where it is assumed those calls will be
routed to SIP trunks hosted by the primary. Additional configuration is necessary to complete the routing from the
Primary Server. The configuration to do that will vary depending on which system is hosting the external trunk or
trunks. Examples of typical configuration changes required are given below.
· Detail
The above default operation is achieved by the following defaults:
1. Primary Server
The following external call routing is configured by default on the Primary Server:
a. Default System Short Code
The server has a default system short code that is used as a match for any dialing that does not match an
extension number or any other short code. This default system short code is also used for matching to
digits received on calls from other systems in the network. The default system short code used depends
on the server's companding (A-Law or U-Law) setting:
· A-Law
On A-Law systems, a default ? short code is used to route any external dialing to ARS record 50:
Main. This will include matching any digits received on calls from other servers in the network that
don't match extension numbers.
· U-Law
On U-Law systems, it is assumed that external calls are indicated by a 9 prefix. A default short code
9N is used to route the digits N to ARS record 50:Main.
b. Default ARS 50:Main
A first ? short code in the ARS form routes calls to the H.323 line that goes to the Primary Server server
by using the Line Group ID of 0.
2. All Other Servers
On all other server types, the system and ARS defaults are set to route all potential external calls to the
Primary Server.
a. Default System Short Code
A default system ? short code is present in the configuration. This routes any dialing that has no other
match to the ARS record 50:Main in the configuration of the system where the dialing occurred.
b. Default ARS 50:Main
A default ? short code in the ARS record is used to route all calls to the Primary Server. On expansion
systems, an additional ? short code is used to route calls to the Secondary Server if the Primary Server is
not available for some reason.
Release 9.0
IP Office Manager
Page 86
15-601011 Issue 9.01 (Monday, September 09, 2013)
Server Edition Mode: Telephony Operation Configuration
Default Settings Summary
The table below summarizes the settings described above.
A-Law
Description
Server
System Short Code
ARS 50:Main Short Codes
Primary Server
?/Dial/./50:Main
?/Dial/./0
Send all calls with no other match to
any trunks in with the Outgoing
Group setting of 0. Since 0 is not a
valid value, this needs to be
changed to match the Outgoing
Group setting actually used for the
external trunks hosted by the
Primary Server.
Secondary Server
?/Dial/./50:Main
?/Dial/./99999
Send all calls with no other match to
the Primary Server.
Expansion
?/Dial/./50:Main
?/Dial/./99999
?/Dial/./99998
Send all calls with no other match to
the Primary Server if available, else
to the Secondary Server.
Primary Server
9N/Dial/N/50:Main
?/Dial/./0
Send all calls with no other match to
any trunks in with the Outgoing
Group setting of 0. Since 0 is not a
valid value, this needs to be
changed to match the Outgoing
Group setting actually used for the
external trunks hosted by the
Primary Server.
Secondary Server
?/Dial/./50:Main
?/Dial/./99999
Send all calls with no other match to
the Primary Server.
Expansion
?/Dial/./50:Main
?/Dial/./99999
?/Dial/./99998
Send all calls with no other match to
the Primary Server if available, else
to the Secondary Server.
U-Law
The short method for describing short codes in this manual, for example 9N/Dial/./0, indicates the settings of the
following fields of a short code: Code/Feature/Telephone Number/Line Group ID. For a description of the individual
fields see Short Code 417 .
The different destinations used for the dialing short codes in the Line Group ID field are:
· 50:Main
Route the call to the ARS record 50:Main on the system where the short code match has occurred. If additional
ARS records are created on a system they can also be selected as the destination for calls to be routed.
· 99999
Route the call to the Primary Server.
· 99998
Route the call to the Secondary Server.
· 999901 to 999930
Route the call to one of the expansion systems. These destinations can only be used on short codes on the Primary
Server and Secondary Server.
· 0
Seize a trunk from those trunks on the system that have their Outgoing Group setting set to 0. Since 0 is not a
valid value, this needs to be changed to match the Outgoing Group setting actually used for the external trunks
hosted by the Primary Server.
Release 9.0
IP Office Manager
Page 87
15-601011 Issue 9.01 (Monday, September 09, 2013)
4.6.2.2 Example 1: Using SIP Trunks Hosted by the Primary
This is the simplest example. It assumes that a SIP trunk has been added to the configuration of the Primary Server,
along with the necessary licenses.
A.In the Primary Server configuration:
1. In the configuration of the SIP trunk on the Primary Server, the SIP URI form includes a field for setting the
Outgoing Group. Set this to a unique ID, by default it is set to 1.
2. In the ARS record 50:Main on the Primary Server, select and edit the exist ? short code to change it from
Line Group ID of 0 to a Line Group ID of 1.
· Code: ?
The ? short code character matches any digits for which no other short code match is present in this
ARS form.
· Feature: Dial
· Telephone Number: .
The . short code character
field.
704
matches all the digits dialled, not just those that matched the Code
· Line Group ID: 1 (or whichever number was set for the SIP trunk Outgoing Group on the Primary
Server)
This field is used to match outgoing calls (ie. calls using the Dial feature) to an available trunk on the
system with the matching number as its Outgoing Group setting. Multiple trunks on the same
system can have the same Outgoing Group setting.
B.Save the configurations.
Release 9.0
IP Office Manager
Page 88
15-601011 Issue 9.01 (Monday, September 09, 2013)
Server Edition Mode: Telephony Operation Configuration
Results: A-Law Systems
For systems operating in A-Law, it is assumed that no dialing prefix is used for external calls.
If a user hosted on an expansion system dials 555 123 4567:
Server
Event
Digits
Expansion
System
A user dials 555 123 4567.
555 123 4567
The digits are matched to the ?/Dial/. system short code. This routes the call to
ARS 50:Main.
555 123 4567
The digits are matched to the first ?/Dial/. short code in the ARS form. This
routes the call to the primary.
555 123 4567
Primary Server The call is received on the H.323 line.
555 123 4567
The digits are matched to the ?/Dial/. system short code. This routes the call to
ARS 50:Main.
555 123 4567
The digits are matched to the first ?/Dial/. short code in the ARS form. This
routes the call to an available SIP trunk channel.
555 123 4567
If a user hosted on the primary system dials 555 123 4567:
Server
Event
Digits
Primary Server A user dials 555 123 4567.
555 123 4567
The digits are matched to the ?/Dial/. system short code. This routes the call to
ARS 50:Main.
555 123 4567
The digits are matched to the first ?/Dial/. short code in the ARS form. This
routes the call to an available SIP trunk channel.
555 123 4567
Results: U-Law Systems
For systems operating in U-Law, it is assumed that a 9 prefix is used for external calls.
If a user hosted on an expansion system dials 9 555 123 4567:
Server
Event
Digits
Expansion
System
A user dials 9 555 123 4567.
9 555 123 4567
The digits are matched to the ?/Dial/. system short code. This routes the call to
ARS 50:Main.
9 555 123 4567
The digits are matched to the first ?/Dial/. short code in the ARS form. This
routes the call to the primary.
9 555 123 4567
Primary Server The call is received on the H.323 line.
9 555 123 4567
The digits are matched to the 9N/Dial/N system short code. This routes the call
to ARS 50:Main. having removed the 9 prefix.
555 123 4567
The digits are matched to the first ?/Dial/. short code in the ARS form. This
routes the call to an available SIP trunk channel.
555 123 4567
If a user hosted on the primary system dials 9 555 123 4567:
Server
Event
Digits
Primary Server A user dials 9 555 123 4567.
Release 9.0
IP Office Manager
9 555 123 4567
The digits are matched to the 9N/Dial/N system short code. This routes the call
to ARS 50:Main. having removed the 9 prefix.
555 123 4567
The digits are matched to the first ?/Dial/. short code in the ARS form. This
routes the call to an available SIP trunk channel.
555 123 4567
Page 89
15-601011 Issue 9.01 (Monday, September 09, 2013)
4.6.2.3 Example 2: Primary Trunk Fallback to Secondary Trunks
This example is builds on example 1 88 . In this case the network has also has a Secondary Server and SIP trunks have
been added to the Secondary Servers configuration using the Outgoing Group setting of 2.
A.In the Primary Server configuration:
1. Configure the Primary Server as per example 1
the Primary Server.
88
. This will route all outgoing calls to the SIP trunk hosted by
B.In the Secondary Server configuration:
1. In the configuration of the SIP trunk on the Secondary Server, the SIP URI form includes a field for setting
the Outgoing Group. Set this to a unique ID, for this example we assume it is 2.
2. Select ARS and click on the
icon to add a new ARS record.
a. Set the Route Name to something suitable descriptive such as Fallback.
b. Add a short code that will route calls that use this ARS record to the SIP trunk hosted by the secondary.
The short code depends on whether we need to remove a dial 9 prefix or not:
· If no dialing prefix is being used, add a ?/Dial/./2 short code.
· If a dial 9 prefix is being used, add a 9N/Dial/N/2 short code.
c. Click OK.
3. In the ARS record 50:Main on the Secondary Server, we need to set the record to fallback to using the new
ARS form when a route to the primary cannot be seized.
Release 9.0
IP Office Manager
Page 90
15-601011 Issue 9.01 (Monday, September 09, 2013)
Server Edition Mode: Telephony Operation Configuration
a. In the Alternate Route drop down select the fallback ARS.
b. Set the Alternate Route Priority Level to 1. This is the lowest level of priority so no users will need to
wait to use the alternate ARS is the connection to the primary is not available.
C.Save the configurations.
Release 9.0
IP Office Manager
Page 91
15-601011 Issue 9.01 (Monday, September 09, 2013)
Results: A-Law Systems
For systems operating in A-Law, it is assumed that no dialing prefix is used for external calls.
If a user hosted on an expansion system dials 555 123 4567:
Server
Event
Digits
Expansion
System
A user dials 555 123 4567.
555 123 4567
The digits are matched to the ?/Dial/. system short code. This routes the call to
ARS 50:Main.
555 123 4567
The digits are matched to the first ?/Dial/. short code in the ARS form. This tries
to route the call to the primary (99999).
555 123 4567
A trunk to the primary cannot be seized. The digits are matched to the next ?/
555 123 4567
Dial/. short code in the ARS form. This routes the call to the secondary (99998).
Secondary
Server
The call is received on the H.323 line.
555 123 4567
The digits are matched to the ?/Dial/. system short code. This routes the call to
ARS 50:Main.
555 123 4567
The ARS cannot seize a trunk to the primary so fallback to its alternate ARS, 51:
Fallback.
555 123 4567
The digits are matched to the first ?/Dial/. short code in the ARS form. This
routes the call to an available SIP trunk channel.
555 123 4567
If a user hosted on the secondary system dials 555 123 4567:
Server
Event
Digits
Secondary
Server
A user dials 555 123 4567.
555 123 4567
The digits are matched to the ?/Dial/. system short code. This routes the call to
ARS 50:Main.
555 123 4567
The ARS cannot seize a trunk to the primary so fallback to its alternate ARS, 51:
Fallback.
555 123 4567
The digits are matched to the first ?/Dial/. short code in the ARS form. This
routes the call to an available SIP trunk channel.
555 123 4567
Release 9.0
IP Office Manager
Page 92
15-601011 Issue 9.01 (Monday, September 09, 2013)
Server Edition Mode: Telephony Operation Configuration
Results: U-Law Systems
For systems operating in U-Law, it is assumed that a 9 prefix is used for external calls.
If a user hosted on an expansion system dials 555 123 4567:
Server
Event
Digits
Expansion
System
A user dials 555 123 4567.
9 555 123 4567
The digits are matched to the ?/Dial/. system short code. This routes the call to
ARS 50:Main.
9 555 123 4567
The digits are matched to the first ?/Dial/. short code in the ARS form. This tries
to route the call to the primary (99999).
9 555 123 4567
A trunk to the primary cannot be seized. The digits are matched to the next ?/
9 555 123 4567
Dial/. short code in the ARS form. This routes the call to the secondary (99998).
Secondary
Server
The call is received on the H.323 line.
9 555 123 4567
The digits are matched to the ?/Dial/. system short code. This routes the call to
ARS 50:Main.
9 555 123 4567
The ARS cannot seize a trunk to the primary so fallback to its alternate ARS, 51:
Fallback.
9 555 123 4567
The digits are matched to the first 9N/Dial/N short code in the ARS form. This
routes the call to an available SIP trunk channel having removed the 9 prefix.
555 123 4567
If a user hosted on the secondary system dials 555 123 4567:
Server
Event
Digits
Secondary
Server
A user dials 555 123 4567.
9 555 123 4567
The digits are matched to the ?/Dial/. system short code. This routes the call to
ARS 50:Main.
9 555 123 4567
The ARS cannot seize a trunk to the primary so fallback to its alternate ARS, 51:
Fallback.
9 555 123 4567
The digits are matched to the first 9N/Dial/N short code in the ARS form. This
routes the call to an available SIP trunk channel having removed the 9 prefix.
555 123 4567
Release 9.0
IP Office Manager
Page 93
15-601011 Issue 9.01 (Monday, September 09, 2013)
4.6.2.4 Example 3: Using Trunks on an Server Edition Expansion System (V2)
Primary Server, Secondary Server and Linux Expansion systems only support SIP trunks for external trunk connections.
An Expansion System (V2) must be used for other trunk types such as analog, BRI or PRI. In this example we assume
that the Expansion System (V2) is being used for all outgoing external calls from the network.
A.In the Expansion A configuration:
No changes are required, this and other expansion systems still send their calls to the primary which then routes
the calls to the system which is hosting the external trunks.
B.In the Primary Server configuration:
1. In the configuration of the Primary Server, identify the H.323 IP trunk that is used for calls to the Expansion
System (V2) and note the Outgoing Group ID setting, it will be in the range 99901 to 999930. The trunk
can be recognized by the Gateway IP Address on the VoIP Settings tab matching the IP address of the
Expansion System (V2).
2. In the ARS record 50:Main on the Primary Server, select and edit the default ? short code to route calls to
the expansion system:
· Code: ?
· Feature: Dial
· Telephone Number: .
· Line Group ID: 99901 (or whichever number was set for the Outgoing Group ID to the Expansion
System (V2)).
C.In the configuration of the system hosting the external trunk:
1. Set the Outgoing Group ID of the external trunks to a unique value. For this example we assume 3 is used.
The field where this is set depends on the trunk type but always has the same name.
2. [Optional] If the network expects a dial 9 prefix on external calls, we need to add a new system short code
that matches and removes that prefix from calls dialed on the local system as for call made on other systems
this prefix is removed by the primary. Add a system short code similar to the following:
· Code: 9N
· Feature: Dial
· Telephone Number: N
· Line Group ID: 50:Main
3. In the ARS record 50:Main, select and edit the first default ? short code to use the Line Group ID of 3.
· Code: ?
· Feature: Dial
· Telephone Number: .
· Line Group ID: 3 (or whichever number was set for the Outgoing Group ID on the system's
external trunks).
D.Save the configurations.
Release 9.0
IP Office Manager
Page 94
15-601011 Issue 9.01 (Monday, September 09, 2013)
Server Edition Mode: Telephony Operation Configuration
Results: A-Law
For systems operating in A-Law, it is assumed that no dialing prefix is used for external calls.
If a user hosted on other expansion systems dials 555 123 4567:
Server
Event
Digits
Expansion
System A
A user dials 555 123 4567.
555 123 4567
The digits are matched to the ?/Dial/. system short code. This routes the call to
ARS 50:Main.
555 123 4567
The digits are matched to the first ?/Dial/. short code in the ARS form. This
routes the call to the primary.
555 123 4567
Primary Server The call is received on the H.323 line.
Expansion
System B
555 123 4567
The digits are matched to the ?/Dial/. system short code. This routes the call to
ARS 50:Main.
555 123 4567
The digits are matched to the first ?/Dial/. short code in the ARS form. This
routes the call to expansion system B.
555 123 4567
The call is received on the H.323 line.
555 123 4567
The digits are matched to the ?/Dial/. system short code. This routes the call to
ARS 50:Main.
555 123 4567
The digits are matched to the first ?/Dial/. short code in the ARS form. This
routes the call to an available trunk.
555 123 4567
If a user hosted on the primary server dials 555 123 4567:
Server
Event
Digits
Primary Server A user dials 555 123 4567.
Expansion
System B
555 123 4567
The digits are matched to the ?/Dial/. system short code. This routes the call to
ARS 50:Main.
555 123 4567
The digits are matched to the first ?/Dial/. short code in the ARS form. This
routes the call to expansion system B.
555 123 4567
The call is received on the H.323 line.
555 123 4567
The digits are matched to the ?/Dial/. system short code. This routes the call to
ARS 50:Main.
555 123 4567
The digits are matched to the first ?/Dial/. short code in the ARS form. This
routes the call to an available trunk.
555 123 4567
If a user hosted on expansion system B dial 555 123 4567:
Server
Event
Digits
Expansion
System B
A user dials 555 123 4567.
555 123 4567
The digits are matched to the ?/Dial/. system short code. This routes the call to
ARS 50:Main.
555 123 4567
The digits are matched to the first ?/Dial/. short code in the ARS form. This
routes the call to an available trunk.
555 123 4567
Release 9.0
IP Office Manager
Page 95
15-601011 Issue 9.01 (Monday, September 09, 2013)
Results: U-Law
For systems operating in U-Law, it is assumed that a 9 prefix is used for external calls.
If a user hosted on other expansion systems dials 9 555 123 4567:
Server
Event
Digits
Expansion
System A
A user dials 9 555 123 4567.
9 555 123 4567
The digits are matched to the ?/Dial/. system short code. This routes the call to
ARS 50:Main.
9 555 123 4567
The digits are matched to the first ?/Dial/. short code in the ARS form. This
routes the call to the primary.
9 555 123 4567
Primary Server The call is received on the H.323 line.
Expansion
System B
9 555 123 4567
The digits are matched to the 9N/Dial/N system short code. This routes the call
to ARS 50:Main. having removed the 9 prefix.
555 123 4567
The digits are matched to the first ?/Dial/. short code in the ARS form. This
routes the call to expansion system B.
555 123 4567
The call is received on the H.323 line.
555 123 4567
The digits are matched to the ?/Dial/. system short code. This routes the call to
ARS 50:Main.
555 123 4567
The digits are matched to the first ?/Dial/. short code in the ARS form. This
routes the call to an available trunk.
555 123 4567
If a user hosted on the primary server dials 9 555 123 4567:
Server
Event
Digits
Primary Server A user dials 9 555 123 4567.
Expansion
System B
9 555 123 4567
The digits are matched to the 9N/Dial/N system short code. This routes the call
to ARS 50:Main. having removed the 9 prefix.
555 123 4567
The digits are matched to the first ?/Dial/. short code in the ARS form. This
routes the call to expansion system B.
555 123 4567
The call is received on the H.323 line.
555 123 4567
The digits are matched to the ?/Dial/. system short code. This routes the call to
ARS 50:Main.
555 123 4567
The digits are matched to the first ?/Dial/. short code in the ARS form. This
routes the call to an available trunk.
555 123 4567
If a user hosted on expansion system B dial 9 555 123 4567:
Server
Event
Digits
Expansion
System B
A user dials 9 555 123 4567.
9 555 123 4567
The digits are matched to the 9N/Dial/N system short code. This routes the call
to ARS 50:Main. having removed the 9 prefix.
9 555 123 4567
The digits are matched to the first ?/Dial/. short code in the ARS form. This
routes the call to an available trunk.
9 555 123 4567
Release 9.0
IP Office Manager
Page 96
15-601011 Issue 9.01 (Monday, September 09, 2013)
Server Edition Mode: Telephony Operation Configuration
4.6.2.5 Example 4: Local Branch Override
This example builds on Example 1
88
where all external calls are routed to SIP trunks hosted by the primary server.
There may be cases where an expansion system (Expansion System (L) and Expansion System (V2)) can route calls
through its own local trunks more cheaply than through trunks located on another system such as the primary. For
example, if the site where the expansion system is located can make local calls free of charge or at a much lower cost. If
that is the case, then for certain dialing we would want to have those calls use the local trunk rather than following the
default routing to the primary server.
Suppose for this example, expansion system A is in national area code 444. The customer wants any dialing of numbers
prefixed with 444 by the users hosted on that system to be routed out on the external trunks connected to that
expansion system. All other external dialing should continue to follow the defaults of being routed to the primary.
A.In the expansion system configuration:
1. In the configuration of the expansion system, set the Outgoing Group ID of the external trunks to a unique
value. For this example we assume 4 is used. The field where this is set depends on the trunk type but always
has the same name.
2. In the ARS record 50:Main on the expansion system we need to add a new short code that matches and
routes calls that include the 444 area code. The short code required depend on whether an external dialing
prefix is used or not.
a. Add a new short code:
· Code: 444N (A-Law) or 9444N (U-Law)
· Feature: Dial
· Telephone Number: N
· Line Group ID: 4 (or whichever number was set for the Outgoing Group ID on the system's
external trunks).
3. The new code will match any dialing sent to the ARS prefixed with 444. Depending on local dialing patterns it
may also be necessary to add similar codes to match dialing prefixed with a national prefix before the local
area code. For example short codes for dialing prefixed 1444N or dialing of a particular length that would
imply its a local number, eg. XXXXXXX.
B.Save the configuration.
Release 9.0
IP Office Manager
Page 97
15-601011 Issue 9.01 (Monday, September 09, 2013)
Results: A-Law Systems
For systems operating in A-Law, it is assumed that no dialing prefix is used for external calls.
If a user hosted on expansion system A dials 555 123 4567:
This routing matches the example setup in Example 1 where the main trunks and call routing settings for external calls
by any system are configured on the primary server.
Server
Event
Digits
Expansion
System A
A user dials 555 123 4567.
555 123 4567
The digits are matched to the ?/Dial/. system short code. This routes the call to
ARS 50:Main.
555 123 4567
The digits are matched to the first ?/Dial/. short code in the ARS form. This
routes the call to the primary.
555 123 4567
Primary Server The call is received on the H.323 line.
555 123 4567
The digits are matched to the ?/Dial/. system short code. This routes the call to
ARS 50:Main.
555 123 4567
The digits are matched to the first ?/Dial/. short code in the ARS form. This
routes the call to an available SIP trunk channel.
555 123 4567
If a user hosted on expansion system A dials 444 123 4567:
Server
Event
Digits
Expansion
System A
A user dials 444 123 4567.
444 123 4567
The digits are matched to the ?/Dial/. system short code. This routes the call to
ARS 50:Main.
444 123 4567
The digits are matched to the first 444N/Dial/N short code in the ARS form. This 444 123 4567
routes the call to the external trunk on the system.
Results: U-Law
For systems operating in U-Law, it is assumed that a 9 prefix is used for external calls.
If a user hosted on expansion system A dials 9 555 123 4567:
This routing matches the example setup in Example 1 where the main trunks and call routing settings for external calls
by any system are configured on the primary server.
Server
Event
Digits
Expansion
System A
A user dials 9 555 123 4567.
9 555 123 4567
The digits are matched to the ?/Dial/. system short code. This routes the call to
ARS 50:Main.
9 555 123 4567
The digits are matched to the first ?/Dial/. short code in the ARS form. This
routes the call to the primary.
9 555 123 4567
Primary Server The call is received on the H.323 line.
9 555 123 4567
The digits are matched to the 9N/Dial/N system short code. This routes the call
to ARS 50:Main. having removed the 9 prefix.
555 123 4567
The digits are matched to the first ?/Dial/. short code in the ARS form. This
routes the call to an available SIP trunk channel.
555 123 4567
If a user hosted on expansion system A dials 9 444 123 4567:
Server
Event
Digits
Expansion
System A
A user dials 9 444 123 4567.
9 444 123 4567
The digits are matched to the ?/Dial/. system short code. This routes the call to
ARS 50:Main.
9 444 123 4567
The digits are matched to the first 9444N/Dial/N short code in the ARS form.
This routes the call to the external trunk on the system.
444 123 4567
Release 9.0
IP Office Manager
Page 98
15-601011 Issue 9.01 (Monday, September 09, 2013)
Server Edition Mode: Telephony Operation Configuration
4.6.2.6 Example 5: PSTN Tail-End-Hop-Off
This example builds on Example 4 97 where calls local to a particular expansion system are routed to external trunks
hosted by that expansion system. Having setup routing similar to that example, it may be advantageous to route any
dialing of the same are code on other systems in the network to the trunks on the local expansion system.
Suppose for this example, we want users on any system in the network that dial a call prefixed with national area code
444 to have that call routed to external trunks on expansion system A which is in that local area. We can do this by
adding additional short codes to the ARS on the primary system as the default routing on all systems already sends all
calls to the primary.
· Important: Check Local and National Call Routing Regulations
This type of operation may be subject to nation restrictions, especially where the expansion system trunks are
being used to make calls in a different country code to other systems in the network. Such operation is not
allowed by the telecommunications regulations in some countries.
A.In the primary server configuration:
1. In the configuration of the Primary Server, identify the H.323 IP trunk that is used for calls to the expansion
system and note the Outgoing Group ID setting, it will be in the range 99901 to 999930. The trunk can be
recognized by the Gateway IP Address on the VoIP Settings tab matching the IP address of the expansion
system.
2. In the ARS record 50:Main on the primary server:
a. Add a new short code:
· Code: 444N (A-Law) or 9444N (U-Law)
· Feature: Dial
· Telephone Number: .
· Line Group ID: 99901 (or whichever number was set for the Outgoing Group ID to the expansion
system).
3. The new code will match any dialing sent to the ARS prefixed with 444. Again, as in Example 4 97 , it may also
be necessary to add similar codes to match dialing prefixed with a national prefix before the local area code.
For example short codes for dialing prefixed 1444N or dialing of a particular length that would imply its a
local number, eg. XXXXXXX.
B.In the expansion system configuration:
1. Apply the same short codes as used for Example 4 to route dialing to area code 444 dialed by users on that
system. Those short codes are also applied to calls received on the network trunks that arrive with those
digits.
C.Save the configuration.
Release 9.0
IP Office Manager
Page 99
15-601011 Issue 9.01 (Monday, September 09, 2013)
Results: A-Law Systems
Any dialing prefixed with 444 on any system is routed to the primary server from where it is rerouted to the expansion
system hosting trunks local to that area code.
If a user hosted on expansion system A dials 444 123 4567:
Server
Event
Digits
Expansion
System A
A user dials 444 123 4567.
444 123 4567
The digits are matched to the ?/Dial/. system short code. This routes the call to
ARS 50:Main.
444 123 4567
The digits are matched to the first 444N/Dial/N short code in the ARS form. This 444 123 4567
routes the call to the external trunk on the system.
If a user hosted on the primary server dials 444 123 4567:
Server
Event
Digits
Primary Server A user dials 444 123 4567.
Expansion
System A
444 123 4567
The digits are matched to the ?/Dial/. system short code. This routes the call to
ARS 50:Main.
444 123 4567
The digits are matched to the first 444N/Dial/. short code in the ARS form. This
routes the call to expansion system A.
444 123 4567
The call is received on the H.323 line.
444 123 4567
The digits are matched to the ?/Dial/. system short code. This routes the call to
ARS 50:Main.
444 123 4567
The digits are matched to the first 444N/Dial/N short code in the ARS form. This 123 4567
routes the call to the external trunk on the system.
If a user hosted on other expansion systems dials 444 123 4567:
Server
Event
Digits
Expansion
System B
A user dials 444 123 4567.
444 123 4567
The digits are matched to the ?/Dial/. system short code. This routes the call to
ARS 50:Main.
444 123 4567
The digits are matched to the first ?/Dial/. short code in the ARS form. This
routes the call to the primary.
444 123 4567
Primary Server The call is received on the H.323 line.
Expansion
System A
444 123 4567
The digits are matched to the ?/Dial/. system short code. This routes the call to
ARS 50:Main.
444 123 4567
The digits are matched to the first 444N/Dial/. short code in the ARS form. This
routes the call to expansion system A.
444 123 4567
The call is received on the H.323 line.
444 123 4567
The digits are matched to the ?/Dial/. system short code. This routes the call to
ARS 50:Main.
444 123 4567
The digits are matched to the first 444N/Dial/N short code in the ARS form. This 123 4567
routes the call to the external trunk on the system.
Release 9.0
IP Office Manager
Page 100
15-601011 Issue 9.01 (Monday, September 09, 2013)
Server Edition Mode: Telephony Operation Configuration
Results: U-Law Systems
Any dialing prefixed with 9444 on any system is routed to the primary server from where it is rerouted to the expansion
system hosting trunks local to that area code.
If a user hosted on expansion system A dials 9 444 123 4567:
Server
Event
Digits
Expansion
System A
A user dials 9 444 123 4567.
9 444 123 4567
The digits are matched to the ?/Dial/. system short code. This routes the call to
ARS 50:Main.
9 444 123 4567
The digits are matched to the first 9444N/Dial/N short code in the ARS form.
This routes the call to the external trunk on the system.
123 4567
If a user hosted on the primary server dials 9 444 123 4567:
Server
Event
Digits
Primary Server A user dials 9 444 123 4567.
9 444 123 4567
The digits are matched to the ?/Dial/. system short code. This routes the call to
ARS 50:Main.
9 444 123 4567
The digits are matched to the first 9444N/Dial/. short code in the ARS form. This 9 444 123 4567
routes the call to expansion system A.
Expansion
System A
The call is received on the H.323 line.
9 444 123 4567
The digits are matched to the ?/Dial/. system short code. This routes the call to
ARS 50:Main.
9 444 123 4567
The digits are matched to the first 9444N/Dial/N short code in the ARS form.
This routes the call to the external trunk on the system.
123 4567
If a user hosted on other expansion systems dials 9 444 123 4567:
Server
Event
Digits
Expansion
System B
A user dials 9 444 123 4567.
9 444 123 4567
The digits are matched to the ?/Dial/. system short code. This routes the call to
ARS 50:Main.
9 444 123 4567
The digits are matched to the first ?/Dial/. short code in the ARS form. This
routes the call to the primary.
9 444 123 4567
Primary Server The call is received on the H.323 line.
9 444 123 4567
The digits are matched to the ?/Dial/. system short code. This routes the call to
ARS 50:Main.
9 444 123 4567
The digits are matched to the first 9444N/Dial/. short code in the ARS form. This 9 444 123 4567
routes the call to expansion system A.
Expansion
System B
Release 9.0
IP Office Manager
The call is received on the H.323 line.
9 444 123 4567
The digits are matched to the ?/Dial/. system short code. This routes the call to
ARS 50:Main.
9 444 123 4567
The digits are matched to the first 9444N/Dial/N short code in the ARS form.
This routes the call to the external trunk on the system.
123 4567
Page 101
15-601011 Issue 9.01 (Monday, September 09, 2013)
4.7 Default Settings
Most of the defaults for systems in a Server Edition solution match those of individual IP Office systems as detailed in
the Configuration Settings 194 section. However, there are some some differences.
Settings
System
Server Edition Primary
Server
Time
Settings
Voicemail
Alarms
Physical
IP Lines
Expansion System
Hidden. Time taken from
host server.
SNTP from the primary server.
Voicemail Pro
Centralized Voicemail to the primary server
Syslog relay all alarms to
the local host.
Syslog relay all alarms to the primary server.
IP Address
Lines
Server Edition Secondary
Server
Specified during initial configuration menu.
–
–
Auto-created
H.323 line to the secondary H.323 line to the primary
and each expansion system. and each expansion system.
Backup to secondary.
Backup to primary.
H.323 line to the primary
and to the secondary if
present.
No backup.
Extension
Physical
–
–
Auto-created but no base
extension setting.
None
None
None
User
None
None
None
Hunt Group
None
Not allowed
Not allowed
Incoming Call Route
None
Replicated from primary.
Stored on the primary
Configured to obtain system directory from the primary
server.
None
Replicated from primary.
IP
Directory
User Rights
ARS
50:Main
Short code to secondary
Short code to primary
Short code to primary and
to secondary if present.
· All auto-create extension and auto-create user settings for IP devices are set to off.
Release 9.0
IP Office Manager
Page 102
15-601011 Issue 9.01 (Monday, September 09, 2013)
Server Edition Mode: Default Settings
4.8 IP500 V2 Conversion
When an IP500 V2 is added to a Server Edition solution as a Expansion System (V2), those parts of its configuration that
do not match the default settings 102 for an expansion system are overwritten. Settings are only retained where they
don't conflict with those default settings. Beyond that, the range of settings retained depends on:
· Whether the Manager Preferences
136
option Consolidate Solution to Primary Settings is selected.
· Whether Retain Configuration Data is selected in the Initial Configuration menu when the expansion system
is added.
Consolidate Solution to Primary
On
Off
Retain Configuration Data
Off
On[1]
Off
On
Lines
Physical
Yes
Yes
Yes
Yes
IP Lines
IP DECT only
Yes
IP DECT only
Yes
Physical
Yes
Yes
Yes
Yes
IP
Yes
Yes
Yes
Yes
User
–
Yes
–
Yes
Hunt Group
–
–
–
–
Yes
Yes
Yes
Yes
–
Yes
–
Yes
Service
Yes
Yes
Yes
Yes
RAS
Yes
Yes
Yes
Yes
–
Yes
–
Yes
WAN Port
Yes
Yes
Yes
Yes
Directory
–
–
–
–
Time Profile
–
–
–
Yes
Firewall Profile
Yes
Yes
Yes
Yes
IP Route
Yes
Yes
Yes
Yes
Account Code
–
–
–
Yes
Licence
–
Yes
–
Yes
Tunnel
Yes
Yes
Yes
Yes
User Rights
–
–
–
Yes
Auto Attendant
–
–
–
–
Yes
Yes
Yes
Yes
Extension
Short Code
Dial, Dial
Emergency
Other features
Incoming Call Route
ARS
1. This action retains more records than are actually visible in Manager due to the action of the Consolidate
Solution to Primary setting. When the configuration is next loaded, the extra records cause reconsolidation
warnings.
Release 9.0
IP Office Manager
Page 103
15-601011 Issue 9.01 (Monday, September 09, 2013)
Chapter 5.
Small Community
Networking
Release 9.0
IP Office Manager
Page 104
15-601011 Issue 9.01 (Monday, September 09, 2013)
Small Community Networking:
5. Small Community Networking
Systems linked by H.323 IP trunks can enable voice networking across those trunks to form a multi-site network. Within
a multi-site network, the separate systems automatically learn each other's extension numbers and user names. This
allows calls between systems and support for a range of internal call features, see Supported Small Community Network
Features 107 .
Capacity
The following are the supported capacity limits for a Small Community Network system.
Software Level
Maximum Number of Systems
Maximum Number of Users
Maximum H.323 Line Hops Between Systems
Pre-5.0
5.0+
6.0+
16
32
32
500
500
1000
5
5
5
Star H.323 Line Layout
Serial H.323 Line Layout
Mesh H.323 Line Layout
Configuration Summary
To set up a Small Community Network, the following are required:
· A working H.323 trunk between the systems, that has been tested for correct voice and data traffic routing.
· The arrangement the H.323 trunks must meet the requirements detailed in Supported Small Community
Network Layouts 106 .
· Within a particular system, all SCN trunks should be on the same LAN interface.
· On IP500 and IP500 V2 systems, H.323 trunks require the entry of IP500 Voice Networking licenses.
· VCM channels are required in all systems.
· The extension, user and group numbering on each system must be unique.
· The user and group names on each system must be unique.
· We also recommend that all names and numbers (line, services, etc) on the separate systems are kept unique.
This will reduce potential maintenance confusion.
· The Outgoing Group ID on the Small Community Network lines should be changed to a number other than the
default 0.
· All systems should use the same set of telephony timers, especially the Default No Answer Time.
· Only one system should have its Voicemail Type set to Voicemail Pro/Lite. All other systems must be set to
either Centralized Voicemail or Distributed Voicemail. No other settings are supported.
Software Level Interoperation
Small Community Networks is supported between systems with the same major software level or one level of difference
in major software level. For example between 6.1 and 6.0 (same major level) and between 7.0 and 6.0 (one major level
of difference).
This option is intended mainly to allow the phased upgrading of sites within a Small Community Network. It is still
recommended that all systems within a network are upgraded to the same level where possible. Within a Small
Community Network including differing levels of software, the network features and capacity will be based on the lowest
level of software within the network.
Release 9.0
IP Office Manager
Page 105
15-601011 Issue 9.01 (Monday, September 09, 2013)
5.1 Supported SCN Network Layouts
The allowed arrangement of H.323 Small Community Network lines between the systems depends on the lowest software
level of any system in the network. Note that we are referring to H.323 Small Community Network lines configured in the
system configurations. The actual IP network configuration, including IP routes in the system configurations, can differ as
per the customer network requirements.
Software Level
Maximum Number of Systems
Maximum Number of Users
Maximum H.323 Line Hops Between Systems
Pre-5.0
5.0+
6.0+
16
32
32
500
500
1000
5
5
5
Star H.323 Line Layout
Serial H.323 Line Layout
Mesh H.323 Line Layout
Star/Serial Layouts
The following are examples of star and serial layouts. These are the only types of layouts supported for a Small
Community Network> containing any pre-Release 5 systems.
---- = IP network, | = H.323 Small Community Network Line.
Mesh Layout
The use of 'mesh' layouts connections is only supported for a Small Community Network of Release 5.0 or higher
systems. A mesh layout is one where there is more than one possible H.323 Small Community Network Line route
between any two systems. The following are examples of mesh layouts. Mesh, star and serial layouts can be combined.
Small Community Network Signalling
Small Community Network uses a signalling similar to RIP is order to update each other of there presence. This traffic
can be seen in the System Monitor application as AVRIP packets. This traffic is is sent to port 50795 on which each
system listens.
Each system in the Small Community Network transmits an update every 30 seconds. Additionally BLF updates are
transmitted when applicable up to a maximum of every 0.5 seconds. Typically the volume is less than 1Kbps per system.
Release 9.0
IP Office Manager
Page 106
15-601011 Issue 9.01 (Monday, September 09, 2013)
Small Community Networking: Supported SCN Network Layouts
5.2 Supported SCN Features
Each system running IP Office in a multi-site network acts as a self-contained IP Office telephone system. In addition to
the remote systems sharing knowledge of user and hunt group extension numbers, the following additional telephony
features are supported between systems in a multi-site network. Features not listed are not supported across the multisite network.
Feature
Description
Minimum
Software
Level
Extension Dialing
Each system automatically learns the user extension numbers available on other –
systems and allows routes calls to those numbers.
Absence Text
Calling a remote user with absence text set will display the absence text.
–
Call Tagging
Call tag text added to a call is retained by calls routed across the Small
Community Network.
–
Anti-tromboning
Calls routed across the multi-site network and back to the originating system
are turned back into internal calls on the originating system only.
–
Hold
Hold and held calls are signalled across the multi-site network.
–
Transfer
Calls can be transferred to multi-site network extension numbers.
–
Forwarding
Calls can be forwarded to multi-site network extension numbers.
–
Paging
Page calls can be made to multi-site network extension numbers.
–
Call Pick-Up Extension
The directed call pickup feature can use multi-site network extension numbers
as its target for the call pickup.
–
Callback When Free
When calling a busy or unanswered extension across themulti-site network, the –
callback when free function can be used to set a callback.
Conference
Meet Me conference IDs are now shared across a multi-site network. For
–
example, if a conference with the ID 500 is started on one system, anyone else
joining conference 500 on any system will join the same conference. Each
conference still uses the conference resources of the system on which it was
started and is limited by the available conference capacity of that system.
Previously separate conferences, each with the same conference ID, could be
started on each system in a multi-site network.
User DSS/BLF
Monitoring of user status only. The ability to use additional features such as call –
pickup via a USER button will differ depending on whether the monitored user is
local or remote. Indication of new voicemail messages provided by SoftConsole
user speed dial icon is not supported across a multi-site network.
Advertised Hunt Groups A hunt group can be set to be 'advertised'. Hunt groups that are advertised can 4.0
be dialed by users on other systems within the multi-site network without the
need for short codes.
Distributed Hunt
Groups
Hunt groups on a system can include users located on remote systems within
the multi-site network. A distributed hunt group can only be edited on the
system on which they were created.
4.0
Remote Hot Desking
Users can hot desk between systems within the network. The system on which
the user configured is termed their 'home' system, all other systems are
'remote' systems. When a user logs in to a remote system;
4.0
· The user's incoming calls are rerouted across the multi-site network.
· The user's outgoing calls use the settings of the remote system at which
they are logged in.
· The user's own settings are transferred. However some settings may
become unusable or may operate differently.
· Users settings are transferred but user rights are not. However if user
rights with the same name exist on the remote system then they will be
used. The same applies for user rights applied by time profiles, if a time
profile with the same name also exists on the remote system .
· Appearance buttons configured for users on the home system will no
longer operate.
Release 9.0
IP Office Manager
Page 107
15-601011 Issue 9.01 (Monday, September 09, 2013)
Feature
Description
Minimum
Software
Level
· Various other settings may either no longer work or may work differently
depending on the configuration of the remote system at which the user
has logged in. For example T3 phones, the personal directory is not
transferred with the user.
· If a remote user's home system is no longer visible within the multi-site
network, they are automatically logged out after 24 hours.
Break Out Dialing
This feature allows the user to select a system in the network from a displayed 4.0
list and then dial a subsequent number as if dialing locally on the select system.
This feature is triggered either by a programmable button 821 or short code 721 .
Music on Hold Source
Selection
The 4 possible music on hold sources are numbered 1 to 4, with 1 being the
System Source. Where the source number to associate with a call is changed,
that number is retained when the call is rerouted across the Small Community
Network. If the receiving switch has a matching numbered alternate source,
that source is used.
4.2
Mobile Call Control
Licensed mobile call control users who remote hot desk to another system
within the multi-site network take their licensed status with them rather than
consuming (if available) a license on the system to which they hot desk.
4.2
Fallback
Systems can provide fallback support for Avaya H.323 phones, advertised hunt 5.0
groups and centralized voicemail.
Centralized Personal
Directory
If the user hot desks to another system in the multi-site network, their personal 5.0
directory is still available.
Centralized Call Log
The centralized call log features include support for users hot desking within a
multi-site network.
5.0
· The user's call log records are stored by the system that is their home
system, ie. the one on which they are configured. When the user is
logged in on another system, new call log records are sent to the user's
home system, but using the time and date on the system where the user
is logged in.
· Hunt group call log records are stored on the system on which the hunt
group is configured.
Fax Relay
Fax relay can be configured on SIP lines and extensions. Within a multi-site
5.0
network, fax calls can transition from a trunk or extension with T38 support to a
system Small Community Network line with Fax Transport Support enabled.
Fax Relay is only supported on IP500/IP500 V2 systems with IP500 VCM, IP500
VCM V2 and or IP500 Combo cards. Fax Relay is supported on Server Edition
Linux servers.
User Profile Resilience
When a user hot desks to another switch in the multi-site network, they retain
their Profile settings and rights as validated by the licenses in their home
switch's configuration. They do not use a license on the remote switch. This
applies even if their home switch is temporarily removed from the multi-site
network.
Distributed Voicemail
Server Support
When using Voicemail Pro 6.0 or higher, each system can support its own
6.0
Voicemail Pro server in addition to the central Voicemail Pro server. The
distributed severs can provide call recording and auto attendant functions to
their local system. The central Voicemail Pro server is still used as the message
store for all messages. For full details refer to the Voicemail Pro Installation
Manual. This option is not supported for Server Edition multi-site networks.
Intrusion Features
Call intrusion 533 features are supported across a multi-site network. This
8.0
applies to new intrusion features added in Release 8.0 and to existing intrusion
features which were not previously supported across the multi-site network.
Release 9.0
IP Office Manager
6.0
Page 108
15-601011 Issue 9.01 (Monday, September 09, 2013)
Small Community Networking: Supported SCN Features
5.3 Voicemail Support
Within a Small Community Network, a single Voicemail Pro can be used to provide voicemail services for all the systems.
For full details of installation and setup refer to the Voicemail Pro documentation. The Voicemail Pro is licensed and
hosted by a chosen central system and provides full operation for that system. The voicemail features supported for the
other remote systems are listed below:
· The use of additional Voicemail Pro servers is supported. The distributed severs provide call recording and
auto attendant functions to their local system. The central Voice Pro server is still used as the message store
for all messages. Refer to the Voicemail Pro documentation.
· User mailboxes.
· Call recording.
Recording of incoming call routes is only supported for destinations on the same system, not for remote Small
Community Network destinations.
· Dial by Name.
· Auto Attendants.
· Breakout
Requires that the numbers used are routable by the system hosting the voicemail server.
· Announcements
· UMS Web Services
Users for UMS Web Services (IMAP and or web voicemail) are licensed through the UMS Web Services license on
their host system. This applies even if the user remote hot desks to another system in the Small Community
Network.
Release 9.0
IP Office Manager
Page 109
15-601011 Issue 9.01 (Monday, September 09, 2013)
5.4 Enabling Small Community Networking
The process below adds an H.323 Small Community Network Line to the system configuration. It is assumed that data
routing between the systems has already been configured and tested. For Manager 8.1, adding Small Community
Network connections between systems can also be done using Manager's Small Community Network Management 112
mode.
· A working H.323 trunk between the systems, that has been tested for correct voice and data traffic routing.
· The arrangement the H.323 trunks must meet the requirements detailed in Supported Small Community
Network Layouts 106 .
· Within a particular system, all SCN trunks should be on the same LAN interface.
· On IP500 and IP500 V2 systems, H.323 trunks require the entry of IP500 Voice Networking licenses.
· VCM channels are required in all systems.
· The extension, user and group numbering on each system must be unique.
· The user and group names on each system must be unique.
· We also recommend that all names and numbers (line, services, etc) on the separate systems are kept unique.
This will reduce potential maintenance confusion.
· The Outgoing Group ID on the Small Community Network lines should be changed to a number other than the
default 0.
· All systems should use the same set of telephony timers, especially the Default No Answer Time.
· Only one system should have its Voicemail Type set to Voicemail Pro/Lite. All other systems must be set to
either Centralized Voicemail or Distributed Voicemail. No other settings are supported.
A. Setup the VoIP Line from System A to System B
1. Receive the system configuration for System A. Prepare the system for addition to the Small Community Network:
a. For IP500 and IP500 V2 systems, check that the Voice Networking license is present and valid.
b. Change all extensions numbers and names to values that will be unique within the multi-site network.
· For users and extensions this can be done using the Extension Renumber tool. That will adjust all users
and extension and all items using those numbers, for example hunt group memberships and incoming call
routes.
· For hunt groups, each hunt group must be change individually.
2. Click Line to display a list of existing lines.
3. Right-click on the displayed list and select New and then H.323 Line.
4. Select the Line tab and set the following:
· In the Telephone Number field, enter a description of the link. For example System B Small Community
Network.
· Set the Outgoing Group ID to a unique value. For example match the automatically assigned Line Number
value shown above.
5. Select the VoIP Settings tab and set the following:
· For the Gateway IP Address, enter the IP address of the remote System B.
· In the Supplementary Services field select IP Office SCN. Use of IP Office SCN - Fallback is detailed in
Small Community Network Fallback 122 .
· Select the preferred Compression Mode. The same mode must be used by all VoIP lines and extensions
within the network.
· The other option can be configured as required but must be matched by the other H.323 Small Community
Network lines in the network. For example the Silence Suppression settings on all the network trunks must
match.
6. Select System | Voicemail.
a. Only one system should have its Voicemail Type set to Voicemail Pro/Lite. The Voicemail IP Address
will be the IP address of the central voicemail server PC.
Release 9.0
IP Office Manager
Page 110
15-601011 Issue 9.01 (Monday, September 09, 2013)
Small Community Networking: Enabling Small Community Networking
b. Any other system with its own Voicemail Pro server PC should have its Voicemail Type set to Distributed
Voicemail. The Voicemail IP Address should be the IP address of the distributed voicemail server PC. The
Voicemail Destination should be set to the Outgoing Group ID used for the Small Community Network
line to the system that is set as Voicemail Pro/Lite.
c. All other systems should have their Voicemail Type set to Centralized Voicemail. The Voicemail Destination
should be set to the Outgoing Group ID used for the Small Community Network line to the system that is
set as Voicemail Pro/Lite.
7. Save the configuration and reboot System A.
B. Setup the VoIP Line from System B to System A
1. On the remote system, repeat the previous steps to create an H.323 Small Community Network line to System A.
As stated above, where possible the line settings, especially the VoIP settings, must match those used for other
H.323 SCN lines in the network.
2. Load the configuration and reboot the remote system.
C. Test Small Community Networking
1. Test by making calls between extensions on the different systems.
Release 9.0
IP Office Manager
Page 111
15-601011 Issue 9.01 (Monday, September 09, 2013)
5.5 SCN Management
Manager 8.1 and higher supports the ability to load and manage the configurations of the systems in a Small Community
Network at the same time. This requires Manager to be enabled for Small Community Network discovery and at least one
system in the Small Community Network to have 6.0 or higher software.
When the configurations of the systems in a Small Community Network are loaded, Manager switched to Small
Community Network management mode. This differs from normal system configuration mode in a number of ways:
· A network viewer is available. In addition to giving a graphical view of the Small Community Network, the view
can be used to add and remove links between the systems in the Small Community Network.
· In the configuration tree, the records for users and hunt groups on all systems are grouped together.
· Time Profiles and User Right common to all systems are grouped together.
· The configuration settings for each system in the Small Community Network can be accessed and edited.
5.5.1 Enabling SCN Discovery
In order for the Select IP Office menu to groups systems in a Small Community Network and allow loading of all the
Small Community Network configurations, Manager must be enabled for SCN discovery.
1. Select File | Preferences.
2. Select the Discovery tab.
3. Select the SCN Discovery option.
4. Check that the other discovery setting are sufficient to discover all the systems in the Small Community Network.
5. Click OK.
Release 9.0
IP Office Manager
Page 112
15-601011 Issue 9.01 (Monday, September 09, 2013)
Small Community Networking: SCN Management
5.5.2 Creating a Common Admin Account
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.
1. Select Tools | SCN Service User Management.
· The option is not shown if a Basic Mode system configuration is loaded. If no configuration is loaded, and the
option is not shown, select View | Advanced View.
2. The Select IP Office menu displays the list of discovered 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 requested. 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.
Release 9.0
IP Office Manager
Page 113
15-601011 Issue 9.01 (Monday, September 09, 2013)
5.5.3 Loading an SCN Configuration
If Manager is configured with SCN Discovery
1. With no configuration loaded, click on
112
enabled, the Select IP Office menu will display any SCNs it discovers.
or select File | Open Configuration.
2. The Select IP Office menu is displayed. Any systems in a Small Community Network will be grouped together.
3. To load the configuration of all the systems in the network, click the check box next to the network name and then
click OK.
· If a
warning icon is displayed next to the SCN check box, it indicates that not all the systems known to be
in the Small Community Network were discovered. Hovering the cursor over the icon will display details of the
missing systems. Loading the network configuration at this time would not include the configuration of the
missing system or systems. The missing systems:
· May be disconnected
· The discovery settings
139
for the Manager PC may be incorrect.
· The data routing between the Manager PC and the missing systems may be incorrect or blocked.
4. Enter the name and password for configuration access to each system. If the systems all have a common user
name and password (see Common Administrator Access 113 below), select Use above credentials for all
remaining selected IPOs. Click OK.
5. Manager will load and display the combined configurations in Small Community Network Management mode.
Release 9.0
IP Office Manager
Page 114
15-601011 Issue 9.01 (Monday, September 09, 2013)
Small Community Networking: SCN Management
5.5.4 Editing an SCN Configuration
When the configuration of a Small Community Network is loaded, Manager displays the configuration in a different way
from when the configuration of a single system is loaded. The main differences are in how configuration records are
grouped in the configuration tree.
· Clicking on the
Small Community Network icon displays the Network Viewer
between the systems in the Small Community Network.
117
which shows the lines
· Small Community Network Configuration Records
Certain records from each of the systems in the Small Community Network are grouped together in the
configuration tree differently from when just a single system configuration is loaded. There are two types, unique
Small Community Network records and shared Small Community Network records:
· Unique Records
They can be edited here and the system to which they belong is indicated in the group pane and in the title
bar of the details pane. However, to add or delete these types of record must be done within the configuration
records of the particular system that will host the entry's configuration details.
· All user in the Small Community Network are shown under the
User icon.
· All hunt groups in the Small Community Network are shown under the
Hunt Group icon.
· Shared Records
Shared records are configuration items that exist on all systems in the Small Community Network, having the
same name and settings on each system. Editing the shared record updates the matching copy in the
configuration of each system. Similarly, adding or deleting a shared record adds or deletes from the individual
system configurations. If the copy of the shared record within an individual configuration is edited, it is no
longer a shared record for the Small Community Network though the individual records on other system will
remain. Changing the individual records back to matching will turn the records back into a shared record.
· Shared time profiles are shown under the
· Shared user rights are shown under the
Time Profile icon.
User Rights icon.
· Individual System Configurations
The full configuration for each system in the Small Community Network can be accessed and edited as required. It
is possible to copy and paste configuration records between systems using the configuration tree.
Release 9.0
IP Office Manager
Page 115
15-601011 Issue 9.01 (Monday, September 09, 2013)
Saving Changes
When the
save icon or File | Save Configuration is selected, the menu for multiple configuration saves is displayed.
It provides similar options are for a normal single configuration save. Note that when working in Small Community
NetworkManagement mode, after saving configuration changes the Manager will always close the displayed
configuration.
· Change Mode
If Manager thinks the changes made to the configuration settings are mergeable, it will select Merge by default,
otherwise it will select Reboot.
· Merge
Send the configuration settings without rebooting the system. This mode should only be used with settings
that are mergeable. Refer to Mergeable Settings 53 .
· Reboot
Send the configuration and then immediately reboot the system.
· Reboot 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 Reboot When Free is selected. They bar the sending or
receiving of any new calls.
· Error Status
The warning will appear if the configuration being sent contains any validation errors indicated by a
error pane. The configuration can still be sent if required.
Release 9.0
IP Office Manager
icon in the
Page 116
15-601011 Issue 9.01 (Monday, September 09, 2013)
Small Community Networking: SCN Management
5.5.5 Using the Network Viewer
Clicking on Small Community Network in the configuration tree displays the Network Viewer. This shows each of the
systems in the Small Community Network and the links between each of the systems. Systems with attached Voicemail
Pro servers are also indicated.
· Green
System with Voicemail Pro system.
· Black
Small Community Network line between two systems.
· Red
Incorrect Small Community Network line between systems (probably one-way connection). Right-click on the line
and select Repair.
You can use the Network Viewer to perform a range of functions:
· Arrange the View
· Launch System Status
· Launch Voicemail Pro
· Add a Small Community Network Line
· Add a system
· Remove a Small Community Network Line
· Remove a system from the Small Community Network
· Repairing a Small Community Network Line
· Add a Background Image
Release 9.0
IP Office Manager
Page 117
15-601011 Issue 9.01 (Monday, September 09, 2013)
Arranging the View
You can click and drag items around in order to position them where required. Alternatively if you right click on the view
you can select Auto Arrange.
Note that the position of elements in the network view are stored as part of the system configuration. Therefore changes
to the view will require the configuration to be saved.
Adding a Line Within the Small Community Network
You can use the network viewer to add a Small Community Network link between two systems in the Small Community
Network that are currently linked. This process will add new H.323 Small Community Network line records to the
configurations of each of the systems.
1. Note that adding a line between systems will require those systems to reboot when the changes are saved.
2. Right click on the starting system for the link. Select Connect To and select the name of the other system in the
Small Community Network to which you want to link.
3. Select the type of line, IP Office SCN or IP Office SCN-Fallback. Click OK.
· If Small Community Network-Fallback is selected, the actual backup function
122
still need to be configured.
4. The newly added line is displayed in the network viewer.
5. Click OK.
Repairing a Line Within the Small Community Network
A red line in the network viewer indicates a incorrectly configured line between two systems in the Small Community
Network. Typically this will be a line configured in one of the systems but not matched by a line configured in the other
system. The network viewer can be used to correct this error.
1. Note that adding a line between systems will require those systems to reboot when the changes are saved.
2. Right click on the red line and select Repair Line.
3. The line is changed to black.
4. Click OK.
Adding a System to the Small Community Network
You can use the network viewer to add a Small Community Network line to a system not yet in the Small Community
Network. This process will add new H.323 Small Community Network line records to the configurations of each of the
systems.
1. Note that adding a line between systems will require those systems to reboot when the changes are saved.
2. Right click on the starting system for the link. Select Connect To and select Discovery.
3. The Select IP Office menu will display any discoverable systems not already in the Small Community Network.
· If the discovery includes systems already in another Small Community Network it will not indicate such. If you
want to add such a system in order to join the SCNs you can do so. However after adding the system, you
should immediately save the configuration and reload the Small Community Network.
4. Select the required system and click OK.
5. Enter the name and password for configuration access to the selected system and click OK.
6. The newly added system is displayed in the network viewer.
7. Click OK. The configuration of the newly added system is now included in the configuration tree.
8. If the Error List is visible (View | Error Pane), check that none of the error are Small Community Network
specific errors, for example duplicate names or extension numbers.
Removing a Small Community Network Line
You can use the network viewer to remove the Small Community Network lines between two systems in the Small
Community Network.
1. Note that removing a link between systems will require those systems to reboot when the changes are saved.
2. Right click on the link and select Delete Line.
3. The line is removed from the network viewer.
Release 9.0
IP Office Manager
Page 118
15-601011 Issue 9.01 (Monday, September 09, 2013)
Small Community Networking: SCN Management
4. Click OK.
Removing a System
You can use the network viewer to remove a system from the Small Community Network.
1. Note that removing a system will require previous linked systems to reboot when the changes are saved.
2. Right click on the system and select Remove From Small Community Network.
3. Any lines to other system in the Small Community Network are removed.
4. Click OK.
Start System Status
If the System Status Application is also installed on the Manager PC, you can start it for a particular system.
1. Right click on the system and select System Status.
2. The application is started and the login form pre filled with the IP address of the system.
Start Voicemail Pro
If the Voicemail Pro client is also installed on the Manager PC, you can start it for the any system with an associated
Voicemail Pro server.
1. Right click on the voicemail server icon and select Launch VMPro Client.
Add a Background Image
You can select an image file to be displayed in the background of the Network Viewer display. This file is not saved as
part of the configuration in any way, ie. if the image file is moved or deleted it is not longer used by Manager.
1. Right click on the general background area of the network viewer and select Background Image.
2. Select Set Background Image to browse to the location of the file to be used.
3. The Visible option can be used to switch the display of the background image on or off.
Release 9.0
IP Office Manager
Page 119
15-601011 Issue 9.01 (Monday, September 09, 2013)
5.5.6 System Inventory
When working in Small Community Network Management
displays a system inventory 120 page for that system.
Release 9.0
IP Office Manager
112
mode, clicking on the System icon for a particular system
Page 120
15-601011 Issue 9.01 (Monday, September 09, 2013)
Small Community Networking: SCN Management
5.6 SCN Remote Hotdesking
The system supports hot desking
581
between systems within a network.
In the descriptions below, the system on which the user is configured is termed their 'home' system, all other systems
are 'remote' systems.
When a user logs in to a remote system:
· The user's incoming calls are rerouted to that system.
· The user's outgoing calls uses the settings of the remote system.
· The user's license privileges move with them, for example their user profile setting is retained. The host system
does not need to be licensed for the user.
· The user's own settings are transferred. However, some settings may become unusable or may operate
differently.
· User rights are not transferred to the remote system but the name of any user rights associated with the user
are transferred. If user rights with the same name exist on the remote system, then they will be used. The
same applies for user rights applied by time profiles, if time profiles with the same name exist on the remote
system .
· Appearance buttons configured for users on the home system will no longer operate.
· Various other settings may either no longer work or may work differently depending on the configuration of
the remote system at which the user has logged in. For example: For T3 phones, the personal directory is not
transferred with the user.
· The rights granted to the user by their Profile settings are retained by the user. There is no requirement for
the remote system to have the appropriate licenses for the Profile.
· If the user's home system is disconnected while the user is remotely hot desked, the user will remain remotely hot
desked. They can remain in that state unless the current host system is restarted. They retain their license
privileges as if they were on their home system. Note however that when the user's home system is reconnected,
the user may be automatically logged back onto that system.
· Break Out Dialing
In some scenarios a hot desking user logged in at a remote system will want to dial a number using the system
short codes of another system. This can be done using either short codes with the Break Out feature or a
programmable button set to Break Out. This feature can be used by any user within the multi-site network but is
of most use to remote hot deskers.
Release 9.0
IP Office Manager
Page 121
15-601011 Issue 9.01 (Monday, September 09, 2013)
5.7 SCN Fallback
Each system in the Small Community Network can include one H.323 line where the Supplementary Services is set to
IP Office SCN - Fallback rather than IP Office SCN. The system to which the H.323 line connects is then requested to
provide fallback support for selected options for the local system.
· Note that both ends of the SCN trunk connection must be set to fallback.
· On the system requesting backup, the required SCN Backup Options are selected, indicating that it is
requesting backup. A single system can only request backup from one other system.
· A system providing backup can provide backup for up to 7 other systems.
Important
· Fallback handover takes approximately 3 minutes. This ensure that fallback is not invoked when it is not required,
for example when the local system is simply being rebooted to complete a non-mergeable configuration change.
· Fallback is only intended to provide basic call functionality while the cause of fallback occurring is investigated and
resolved. If users make changes to their settings while in fallback, for example changing their DND mode, those
changes will not apply after fallback.
· If the fallback system is rebooted while it is providing fallback services, the fallback services are lost.
· Fallback features require that the IP devices local to each system are still able to route data to the fallback system
when the local system is not available. This will typically require each system site to be using a separate data
router from the system.
· When an IP Phone re-registers to a secondary IP Office on the failure of the primary control unit, the second
system will allow it to operate indefinitely as a “guest”, but only until the system resets. Licenses will never be
consumed for a guest IP phone.
· Remote hot desking users on H323 extensions are automatically logged out.
· If using resilience backup 603 to support Avaya IP phones, Auto-create Extn and Auto-create User should
not be left enabled after initial configuration or any subsequent addition of new extensions and users. Leaving
auto-create options enabled on a system that is a failover target may cause duplicate extension/user records
on the multi-site network under multiple failure scenarios.
Fallback Options
Once a line is set to IP Office SCN - Fallback, the following options are available:
SCN Backup Options:
These options are only available on when the Supplementary Services option is set to IP Office - Fallback. 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 network, 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.
· If using resilience backup 603 to support Avaya IP phones, Auto-create Extn and Auto-create User should
not be left enabled after initial configuration or any subsequent addition of new extensions and users. Leaving
auto-create options enabled on a system that is a failover target may cause duplicate extension/user records
on the multi-site network under multiple failure scenarios.
· Backs up my Hunt Groups: Default = On.
When selected, any hunt groups the local system is advertising to the network are advertised from the other
system when fallback is required. The trigger for this occurring is Avaya H.323 phones registered with the local
system registering with the other system, ie. Backs up my IP Phones above must also be enabled. In a Server
Edition network this option is only available on the H.323 trunk from the Primary Server to the Secondary Server.
· 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 network.
· Any local members who have hot desked to another system still visible within the network.
· When the local system becomes visible to the other system again, the groups will return to be advertised from
the local system.
Release 9.0
IP Office Manager
Page 122
15-601011 Issue 9.01 (Monday, September 09, 2013)
Small Community Networking: SCN Fallback
· 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 network. 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. In a Server Edition network this option is only available on the H.323 trunk from the Primary
Server to the Secondary Server. It is assumed as being on an is automatically set by the Resilience Administration
tool.
· This option requires the other system to have licenses for the Voicemail Pro features that are required to
operate during any fallback period.
· This option requires Voicemail Pro 5.0+.
Release 9.0
IP Office Manager
Page 123
15-601011 Issue 9.01 (Monday, September 09, 2013)
5.8 SCN Short Code Programming
In a multi-site network, the systems automatically learn each others extension numbers and route calls appropriately.
However the same does not apply to dialing of other numbers. Using short codes it is possible to have the dialing of
numbers on one system to be redirected to another system and dialed there. The dialing is then matched against the
short codes available on the remote system.
Scenario
We want a short code on System A which will correctly route any 3000 range number to System B. This will allow System
B group numbers to be dialed from System A. To achieve the above scenario, we will add a new system short code. By
using a system short code it becomes available to all users.
Example Short Code
1. In the configuration for System A.
a. Click Short code to display a list of existing system short codes.
b. Right-click on the displayed list and select New.
c. Enter the short code settings as follows:
· Short Code: 3XXX
This will match any four-digit number beginning with 3.
· Telephone Number: .
The . indicates that the short code should output the digits as dialed.
· Line Group ID: 99999
This should match the Outgoing Group ID given to the system H.323 IP line connected to System B.
· Feature: Dial
d. Click OK.
2. A similar system short code can be added to System B's configuration to route 2XXX dialing to System A.
Release 9.0
IP Office Manager
Page 124
15-601011 Issue 9.01 (Monday, September 09, 2013)
Chapter 6.
Network Telephone Features
Release 9.0
IP Office Manager
Page 125
15-601011 Issue 9.01 (Monday, September 09, 2013)
6. Network Telephone Features
Each system running IP Office in a multi-site network acts as a self-contained IP Office telephone system. In addition to
the remote systems sharing knowledge of user and hunt group extension numbers, the following additional telephony
features are supported between systems in a multi-site network. Features not listed are not supported across the multisite network.
· Absence Text
· Follow Me Here / Follow Me To
775
· Advertised Hunt Groups
Hunt groups set to advertised can be dialed by users
on other systems
· Anti-tromboning
Calls routed across the multi-site network and back to
the originating system are turned back into internal
calls on the originating system only.
· Break Out Dialing
· Call Pick-up Extension
· Call Tagging
724
· Internal Twining
378
· Intrusion Features
533
· Music On Hold Source Selection
545
535
· Relay On / Relay Off / Relay Pulse
773
· Centralized Call Log
522
· Remote Hot Desking
· Centralized Personal Directory
521
573
· Distributed Hunt Groups
410
· Distributed Voicemail Server Support
When using Vociemail Pro, each system can support
its own Voicemail Pro server. See the Voicemail Pro
Installation Manual.
· Enable ARS / Disable ARS
749
· Extension Dialing
Each system automatically learns the user extension
numbers available on other systems and routes calls
to those numbers.
· Fallback
Server Edition Fallback
SCN Fallback 122
· Fax Relay
· Hold
Held calls are signalled across the network.
725
· Callback When Free
· Conference
369
· Mobile Call Control
Licensed mobile call control users who remote hot
desk to another system take their licensed status with
them.
582
· Call Park / Unpark Call
· Forwarding
554
771
582
· Set Hunt Group Out of Service / Clear Hunt Group Out
of Service 778
· Transfer
Calls can be transferred to network extensions.
· User DSS/BLF
Monitoring of user status only. The ability to use
additional features such as call pickup via a USER
button will differ depending on whether the monitored
user is local or remote. Indication of new voicemail
messages provided by SoftConsole user speed dial
icon is not supported.
· User Profile Resilence
When a user hot desks to another system, they retain
their Profile settings and rights.
603
528
Release 9.0
IP Office Manager
Page 126
15-601011 Issue 9.01 (Monday, September 09, 2013)
Network Telephone Features:
Release 9.0
IP Office Manager
Page 127
15-601011 Issue 9.01 (Monday, September 09, 2013)
Chapter 7.
Shell Server Mode
Release 9.0
IP Office Manager
Page 128
15-601011 Issue 9.01 (Monday, September 09, 2013)
Shell Server Mode:
7. Shell Server Mode
An IP Office Shell Server is a single installation of selected IP Office applications running on Linux. You can use Manager
to configure and administer a Shell Server. Since a Shell Server does not provide telephony, when you open a Shell
Server configuration in Manager, all telephony functions are disabled.
The following Manager functions are supported for Shell Servers:
· Discovery
· Initial configuration utility.
· System status.
· Load, edit and save security settings.
· Load, edit, and save the configuration.
· Erase configuration and security settings.
· Audit trail display.
· Web Control.
For more information on the management of an IP Office Shell Server, see IP Office Application Server Installation and
Maintenance.
Release 9.0
IP Office Manager
Page 129
15-601011 Issue 9.01 (Monday, September 09, 2013)
Chapter 8.
Menu Bar Commands
Release 9.0
IP Office Manager
Page 130
15-601011 Issue 9.01 (Monday, September 09, 2013)
Menu Bar Commands:
8. 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.
Simplified View
File
Open Configuration... 134
Close Configuration 134
Save Configuration 134
Save Configuration As... 134
Preferences 136
Offline
Send Config...
Advanced
Erase Configuration (Default) 145
Reboot 145
System Shutdown... 146
Upgrade.. 147
Switch to Standard Mode 150
Embedded File Management 153
Format IP Office SD Card 154
Recreate IP Office SD Card 155
144
Memory Card Command
System Status
Exit
View
Shutdown... 162
Start Up... 162
162
156
164
Toolbars 165
Tooltip 165
Advanced View 34
Hide Admin Tasks
TFTP Log 166
165
Advanced View Configuration Mode
The following menu options are available:
File
Open Configuration... 134
Close Configuration 134
Save Configuration 134
Save Configuration As... 134
Change Working Directory...
Preferences 136
135
Offline
Create New Config 143
Open File... 143
Open File Set... 143
Send Config... 144
Receive Config... 144
Advanced
Erase Configuration (Default) 145
Reboot 145
System Shutdown... 146
Upgrade.. 147
Change Mode... 149
Audit Trail... 151
Security Settings... 153
Erase Security Settings... 153
Embedded File Management 153
Format IP Office SD Card 154
Recreate IP Office SD Card 155
Memory Card Command
162
Shutdown...
162
Start Up...
Launch Voicemail Pro Client
System Status 156
Release 9.0
IP Office Manager
162
156
Page 131
15-601011 Issue 9.01 (Monday, September 09, 2013)
LVM Greeting Utility 157
Initial Configuration 157
Add/Display VM Locales
161
Backup/Restore
Backup Binaries and Configurations 162
Restore Binaries and Configurations 162
Import/Export
Import 164
Export 163
Exit
164
View
Toolbars 165
Navigation Pane 165
Group Pane 165
Details Pane 165
Error Pane 165
Simplified View 165
TFTP Log 166
Tools
Extension Renumber 167
Line Renumber 167
Connect To 167
SCN Service User Management 169
Server Edition Service User Management
Busy on Held Validation 170
MSN 170 Configuration 170
Print Button Labels 171
Import Templates 172
Release 9.0
IP Office Manager
169
Page 132
15-601011 Issue 9.01 (Monday, September 09, 2013)
Menu Bar Commands:
Security Mode
File
Open Security Settings 173
Close Security Settings 173
Save Security Settings 173
Reset Security Settings 173
Preferences 173
Configuration 173
Exit 173
View
Toolbars 165
Navigation Pane
Group Pane 165
Details Pane 165
165
Embedded File Management
File
Open File Settings 153
Close File Settings 153
Refresh File Settings 175
Upload File 153
Upload System Files 175
Backup System Files 175
Restore System Files 175
Upgrade Binaries 175
Upgrade Configuration 175
Upload Voicemail Files 176
Upload Phone Files 176
Copy System Card 176
Preferences 136
Configuration 134
Exit 164
View
Toolbars 165
Tiles 153
Icons 153
List 153
Details 153
TFTP Log 166
Release 9.0
IP Office Manager
Page 133
15-601011 Issue 9.01 (Monday, September 09, 2013)
8.1 Configuration Mode: File Menu
8.1.1 Open Configuration
This command displays the Select IP Office menu used to receive a systems configuration settings. See Loading a
Configuration 57 .
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 136 and enter the required addresses in the IP Search Criteria.
Known Units is not available unless configured, see Known System Discovery
59
.
8.1.2 Close Configuration
This command closes the currently loaded configuration without saving it.
8.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
65 .
If the configuration file has been opened offline or created from new, the file is saved to disk only.
8.1.4 Save Configuration As
The File | Save As command allows you to save a configuration a file on the Manager computer. Note that dynamic
configuration data, for example hunt groups advertised from other systems in a network, are not included in a
configuration file saved onto PC and then reopened.
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
143
Server Edition
When Manager is running in Server Edition mode, this command operates different. When used, multiple files are saved.
One .cfg file is saved for each server in the network plus a single .cfi file for the whole network.
The .cfi file can be used with the File | Offline | Open File Set
action.
Release 9.0
IP Office Manager
143
command to open the whole set of files in a single
Page 134
15-601011 Issue 9.01 (Monday, September 09, 2013)
Menu Bar Commands: Configuration Mode: File Menu
8.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.
Note
On Windows 7 systems, the default folder for Manager .cfg files is
C:\Program Files (x86)\Avaya\IP Office\Manager.
On some Windows 7 systems, the file is saved to the user's profile folder at
C:\Users\<user_name>\AppData\Local\VirtualStore\Program Files (x86)\Avaya\IP Office\Manager.
You must turn on Show hidden files to access this folder. Alternatively, you can set the working directory to an
alternate location.
· 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 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
·
147 ,
right-clicking and selecting Change Directory also changes this setting.
! WARNING
Historically, by default the Working Directory and Binary Directory are the same. This is deprecated as it
potentially allows remote TFTP/HTTP file access to the folder containing copies of configuration files. Therefore
it is recommended that either of the folders is changed to an alternate location.
· Known Units File
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 records to be removed.
Release 9.0
IP Office Manager
Page 135
15-601011 Issue 9.01 (Monday, September 09, 2013)
8.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
136
138
· Visual Preferences
· Discovery
139
· Validation
142
· Security
140
141
8.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 base communication port settings.
· Service Base TCP Port: Default = 50804.
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.
· Service Base HTTP Port: Default = 80.
Access to the HTTP server on a system requires Manager to send its requests to specific ports. This setting
allows the HTTP Base Port used by Manager to be set to match the HTTP Base Port setting of the system. The
system’s HTTP 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 509 .
· 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
record. 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.
· Set Simplified View as default: Default = On
If on, the Manager will start in simplified view 15 mode if no configuration is loaded.
Release 9.0
IP Office Manager
Page 136
15-601011 Issue 9.01 (Monday, September 09, 2013)
Menu Bar Commands: Configuration Mode: File Menu
· Default to Standard Mode: Default = Off
If on, when a configuration from a new or defaulted system running in IP Office Basic Edition - Quick Mode is
loaded, Manager will automatically convert the configuration to IP Office Essential Edition. Sending the
configuration back to the system will restart it in IP Office Essential Edition mode. Only select this option if the only
systems you expect to install are IP Office Essential Edition systems.
·
This setting does not affect existing systems with non-default configurations.
· For an IP500 V2 system to run in Standard Mode, its configuration must include an Essential Edition license.
A IP Office Essential Edition system without this license will not allow any telephony functions.
· Use Remote Access for Multi-Site: Default = Off. Release 8.1 FP1
If selected, access to all the configurations of a multi-site network is allowed via remote access to the primary
server on the multi-site network. When selected, an additional Use Remote Access check box option is displayed
on the Select IP Office menu when the Open with Server EditionManager checkbox option is selected or if
Manager is already running in Server Edition mode.
· Consolidate Solution to Primary Settings: Default = On. Release 8.1 FP1
This setting is used by Manager when in Server Edition mode.
· If Consolidate Network to Primary Settings is selected:
· Entry and administration of Short Code, Incoming Call Route, Time Profile, Account Code and User
Rights records is performed only at the solution level.
· Those records are then automatically replicated in the configurations of all the systems in the solution but
are still only visible and editable at the solution level.
· When the configurations are loaded into Manager or when this setting is changed to become selected, if
any inconsistency between records are found, a Consolidation Report is displayed. This report allows
selection of whether to update the system to match the primary or to update the primary to match.
· If Consolidate Network to Primary Settings is not selected:
· Entry and administration of Short Code, Incoming Call Route, Time Profile, Account Code and User
Rights records can be performed at both the solution and individual system levels.
· Records entered and edited at the solution level are automatically replicated in the configurations of all
the systems in the solution. IP Office Manager displays a label on the record indicating that it is a record
that is shared across the solution.
· If a shared record is edited at the individual system level, that copy of the record is no longer shared with
the other systems. It will not be updated by any changes to the solution level version of the same
record.
· No consolidation checking for inconsistencies is done by Manager when the configurations are loaded.
Release 9.0
IP Office Manager
Page 137
15-601011 Issue 9.01 (Monday, September 09, 2013)
8.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.
· 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 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
·
147 ,
right-clicking and selecting Change Directory also changes this setting.
! WARNING
Historically, by default the Working Directory and Binary Directory are the same. This is deprecated as it
potentially allows remote TFTP/HTTP file access to the folder containing copies of configuration files. Therefore
it is recommended that either of the folders is changed to an alternate location.
· Known Units File
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 records to be removed.
Release 9.0
IP Office Manager
Page 138
15-601011 Issue 9.01 (Monday, September 09, 2013)
Menu Bar Commands: Configuration Mode: File Menu
8.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.
· TCP Discovery: Default = On.
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.
· 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:
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 57 dialogue is replaced by a Enter Unit DNS Name or IP Address field.
· SCN Discovery:
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
Small Community Network must be running Release 6.0 or higher software. See Small Community Network
Management 112 . This does not override the need for each system in the Small Community Network to also be
reachable by the TCP Discovery and or UDP Discovery settings above and accessible by the router settings at
the Manager location.
Release 9.0
IP Office Manager
Page 139
15-601011 Issue 9.01 (Monday, September 09, 2013)
8.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 record 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.
· Enable Template Options: Default = Off.
When enabled, the Manager can be used to apply trunk templates 256 . SIP trunk templates can be used to add SIP
trunks. Analog trunk templates can also be applied to existing analog trunks. This option does not affect the
additional template options 78 used for Server Edition mode.
Release 9.0
IP Office Manager
Page 140
15-601011 Issue 9.01 (Monday, September 09, 2013)
Menu Bar Commands: Configuration Mode: File Menu
8.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
21
.
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 is
the normal default. This setting does not affect multi-site network modes of Manager which always close the
configuration after saving.
· Before disabling this setting, you should recall that the configuration held by a running system can be changed by
actions other than Manager, for example changes made by users through their phone. Keeping a configuration
open in Manager for longer than necessary increases the chances that that copy of the configuration differs from
the current configuration of the running system and will overwrite those changes when sent back to the system.
· Save Configuration File After Load: Default = On.
When selected, a copy of the configuration is saved to Manager's working directory 138 . 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 138 . 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.
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.
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 = On (Off pre-8.1 FP1).
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 25 .
Release 9.0
IP Office Manager
Page 141
15-601011 Issue 9.01 (Monday, September 09, 2013)
· When Secure Communications is set to On, a
Manager status field.
padlock icon is displayed at all times in the lower right
· New installations of Manager default to having Secure Communications enabled. This means Manager by
default attempts to use secure communications when opening a configuration.
· For Server Edition systems, Manager will always attempt to use secure communications regardless of the
Secure Communications setting.
· If no response to the use of secure communication is received after 5 seconds, Manager will offer to fallback
to using unsecured communications.
· Manager Certificate Checks:
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.
· 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.
8.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.
Release 9.0
IP Office Manager
Page 142
15-601011 Issue 9.01 (Monday, September 09, 2013)
Menu Bar Commands: Configuration Mode: File Menu
· Validate configuration on open
Automatically validate configuration files when they are opened in IP Office 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.
8.1.7 Offline
8.1.7.1 Create New Config
The Manager simplified view is used to create an offline configuration
61
for an IP Office Enterprise Branch system.
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 61 . The
same action is performed by the
icon in the Main Toolbar.
8.1.7.2 Open File
This command allows a configuration file stored on PC to be opened in Manager.
8.1.7.3 Open File Set
This command is only available when manager is running in Server Edition mode. It can be used to load a set of files
previously saved offline using the File | Save Configuration As 134 command.
When selected, browse to the location of the saved .cfi file and associated .cfg files and select the .cfi file.
Release 9.0
IP Office Manager
Page 143
15-601011 Issue 9.01 (Monday, September 09, 2013)
8.1.7.4 Send Config
This command is used to send an offline configuration to a system. See Sending a Configuration
65
.
! WARNING
After this command is completed, the system is rebooted. This will end all calls and services in progress.
· After sending the configuration, you should receive the configuration back from the system and note any new
validation errors shown by Manager. For example, if using Embedded Voicemail, some sets of prompt languages
may need to be updated to match the new configurations locale setting using the Add/Display VM Locales 161
option.
8.1.7.5 Receive Config
This command displays the Select IP Office menu used to receive a systems configuration settings. See Loading a
Configuration 57 .
Once the configuration has been received, you are prompted to save it on the PC.
Release 9.0
IP Office Manager
Page 144
15-601011 Issue 9.01 (Monday, September 09, 2013)
Menu Bar Commands: Configuration Mode: File Menu
8.1.8 Advanced
8.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.
68
. 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.
IP500 V2 systems using IP Office A-Law or IP Office U-Law System SD cards will default to Basic Edition Quick mode.
Loading the configuration will switch Manager to simplified view 165 . To change the system back to operating in IP Office
Essential Edition use either of the following methods:
· Change Mode 149
This will change the operating mode of the system and create a default configuration appropriate to that mode.
For example, this method can be used to change a IP Office Essential Edition system to a IP Office Basic Edition Quick Mode system.
· Switch to Standard Mode 150
This option (only shown in Manager simplified view) will change the operating mode of a Quick mode system to
Standard mode.
For systems running in Server Edition mode, this command can normally only be used when Manager is also running in
Server Edition mode.
8.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
When the reboot occurs can be selected as follows:
· 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 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.
Release 9.0
IP Office Manager
Page 145
15-601011 Issue 9.01 (Monday, September 09, 2013)
8.1.8.3 System Shutdown
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. For Linux based telephone systems, the shutdown command is applied to the telephony
service on the server and not to the whole sever. In that case, if the system is shutdown indefinitely, it can be restarted
using the server's web control pages to either restart the service or to restart the whole server.
! 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 the loss of configuration data.
· This is not a polite shutdown, any user 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 shutting down a system with a Unified
Communications Module installed, the shutdown can take up to 3 minutes while the card safely closes all open
files and closes down its operating system. During this period the module's LED 1 remains green.
· When shutdown, the LEDs shown on the system are as follows. Do not remove power from the system or
remove any of the memory cards until the system is in this state:
· LED1 on each IP500 base card installed will also flash red rapidly plus LED 9 if a trunk daughter card
is fitted to the base card.
· The CPU LED on the rear of the system will flash red rapidly.
· The System SD and Optional SD memory card LEDs on the rear of the system are extinguished.
· 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 a Timed shutdown is selected, the system will reboot after the set time has elapsed.
· If Indefinite is used, the system can only be restarted by having its power switched off and then on again.
For Linux based telephone systems, the telephony service must be restarted through the server's web control
pages.
Release 9.0
IP Office Manager
Page 146
15-601011 Issue 9.01 (Monday, September 09, 2013)
Menu Bar Commands: Configuration Mode: File Menu
8.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
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.
This command is not used with Linux based systems. Those systems are updated through the server's webcontrol menus.
That includes Server Edition systems.
·
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. There may be additional steps required such as defaulting the security settings.
· 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 IP Office Installation Manual and Technical Bulletins.
The list area shows details of systems found by the Upgrade Wizard and the software currently held by those systems.
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.
· Name
The name of the system as set in its configuration (System | System | Name
201 )
.
· IP Address
The IP address of the system.
· Type
This column indicates the type of system and the names of the various firmware files used by external expansion
systems supported by the system type.
· Version
The Version column details the current software each unit in the systems is running.
· Edition
The Edition column indicates the operation mode of the system.
· Licensed
The Licensed column indicates the highest value software upgrade license present in the system's configuration.
For Release 8.1 FP1+, the IP Office Release that is supported by that license is also indicated in brackets.
· Required License
The Required License column indicates the software upgrade license required for the current level of software
the system is running. For Release 8.1 FP1+, the IP Office Release that is supported by that license is also
indicated in brackets.
· It does not refer to the software upgrade license required for the level of software which is available for
upgrade.
· For IP500 V2 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 an upgrade license.
Release 9.0
IP Office Manager
Page 147
15-601011 Issue 9.01 (Monday, September 09, 2013)
· Available
The Available column shows the version of the matching firmware files that Manager has available (a – indicates
no file available) in its current working directory 138 . Upgrading to a release higher than that supported by the
current Licensed level will leave the system unable to support any functions until the appropriate upgrade license
is added to the system configuration.
The menu includes a number of check boxes that can be used to include other actions as part of the upgrade process:
· Validate
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.
· Backup System Files
For any IP500 V2 systems being upgraded, the Backup system files option will cause the system to backup its
memory card files as part of the upgrade.
· Upload System File
For any IP500 V2 system being upgraded, the Upload system files option will upload various files:
· It copies the binary files for the system control unit and possible external expansion modules.
· It copies the firmware files used by phones supported by the system.
· For systems configured to running in IP Office Basic Edition - Quick Mode, IP Office Basic Edition - PARTNER®
Mode or IP Office Basic Edition - Norstar Mode mode, the files for IP Office Web Manager are copied.
· For systems configured to run Embedded Voicemail, the Embedded Voicemail prompts for those supported
languages set as the system locale, user locales, incoming call route locales and short code locales are
upgraded. In addition the English language prompts are upgraded as follows: IP Office A-Law/Norstar SD
Cards - UK English, IP Office U Law/PARTNER SD Cards - US English.
· Restart IP Phones
For Manager 8.1 and higher 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).
Searching 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 139 . 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 135 or File | Preferences | Directories 138 . 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.
Release 9.0
IP Office Manager
Page 148
15-601011 Issue 9.01 (Monday, September 09, 2013)
Menu Bar Commands: Configuration Mode: File Menu
8.1.8.5 Change Mode
This command can be used to change the operating mode of an IP500 V2 System SD card and thus of the system. For
example, it can be used to switch a system currently running Standard Mode to Basic Mode.
·
! IMPORTANT
Using this command will default the 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. If that is the case, the system may not restart correctly. For example, BRI cards are not supported by IP
Office Basic Edition - PARTNER® Mode.
· In order to use this command, the system security settings must be at their default settings. The current setting
can be defaulted using the Erase Security Settings (Default) 153 command.
· Follow the command, the system is restarted.
· For an IP500 V2 system to run in Standard Mode, its configuration must include an Essential Edition license.
A Standard Mode system without this license will not allow any telephony functions.
· For the mode change, you should perform a system upgrade 147 or upload system files 153 action as the files
included in any previous upgrade or upload will have been based on the system's previous mode setting and
configuration settings.
The menu displayed after selecting a system will indicate the modes available. This menu is displayed for switching a IP
Office Essential Edition system to one of the other modes.
1. Select File | Advanced | Change Mode.
2. From the Select IP Office menu select the system.
3. The Change Mode menu is displayed. The options displayed will depend on the current mode of the system.
· IP Office Essential Edition/IP Office Preferred Edition/IP Office Advanced Edition:
Select the mode required for the defaulted configuration.
· Mode selection is only possible for systems fitted with IP Office A-Law or IP Office U-Law SD cards.
For systems fitted with IP Office Partner Edition or IP Office Norstar Edition SD cards, the systems
will default to the respective mode of that card regardless of the mode selection.
· Note that this process does not change the formatted type of the System SD card. For example, if a
system fitted with an IP Office A-Law card has its mode changed to IP Office Basic Edition - PARTNER®
Mode mode, if that system is then defaulted again it will restart as a IP Office Basic Edition - Quick Mode
system as appropriate to the card type.
· IP Office Basic Edition - Quick Mode/IP Office Basic Edition - PARTNER® Mode/IP Office Basic
Edition - Norstar Mode
There is no mode selection. The system will be changed to a defaulted IP Office Essential Edition mode
configuration.
4. Click OK. After a short delay of a few seconds the system is restarted.
· If the system does not restart, the most likely cause is that the systems security settings were not at their
default settings.
Release 9.0
IP Office Manager
Page 149
15-601011 Issue 9.01 (Monday, September 09, 2013)
8.1.8.6 Switch to Standard Mode
This option will change the operating mode of the configuration loaded in Manager to that of a Standard Mode system.
Manager will automatically switch to its advanced view mode. When the configuration is sent back to the system, it will
restart in Standard Mode.
· For an IP500 V2 system to run in Standard Mode, its configuration must include an Essential Edition license.
A Standard Mode system without this license will not allow any telephony functions.
The command provides two options:
· Default
Using this method will default the configuration. It is the recommended method for installation of a new installation
or for when a Standard Mode system has been defaulted and needs to be returned to IP Office Essential Edition
operation.
· Best Match
Using this method will attempt to preserve configuration settings; for examples user names, extension numbers,
licenses, SIP trunks, etc. However, many settings will be flagged as errors by Manager. These errors should then
be resolved before sending the configuration to the system.
· If this is an existing system, it is recommended that you first use IP Office Manager to receives and save a copy of
the current configuration locally using Save Configuration As 134 .
· This process does not default the security settings of the system.
· Do not use this command if the system includes components not supported by the IP Office Essential Edition
(currently IP500 ETR6 base cards for ETR phones). The system may not restart correctly if that is the case.
When this command is selected, IP Office Manager will first browse for available systems. When a system is selected
from those found, load its configuration. If this cannot be done using the default password (password) it may not be
possible to complete the process.
·
! Automatic Conversion to IP Office Essential Edition
This process can be applied automatically when a configuration for a new or defaulted system running in IP Office
Basic Edition - Quick Mode is loaded. This is done by selecting the Default to Standard Mode option in the
Manager Preferences 136 . Only select this option if the only systems you expect to install are IP Office Essential
Edition systems.
Release 9.0
IP Office Manager
Page 150
15-601011 Issue 9.01 (Monday, September 09, 2013)
Menu Bar Commands: Configuration Mode: File Menu
8.1.8.7 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 IP Office software.
Release 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 141 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
record of a particular type are made, the Item Name field lists the individual record changed. Where changes are
made to several records of the same type, the Item Name field displays Multiple items.
Release 9.0
IP Office Manager
Page 151
15-601011 Issue 9.01 (Monday, September 09, 2013)
Release 9.0
IP Office Manager
Page 152
15-601011 Issue 9.01 (Monday, September 09, 2013)
Menu Bar Commands: Configuration Mode: File Menu
8.1.8.8 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 21 .
8.1.8.9 Erase Security Settings (Default)
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 security user name and password are required to complete the action.
· The system's security settings are returned to their defaults as indicated in the Security Mode
179
chapter.
· Note that any security certificates stored and being used by the system are deleted. Any services currently using
those certificates are disconnected and disabled until the appropriate certificates are added back to the system's
security configuration. That includes SSL VPN connections being used to perform system maintenance.
For Standard mode and Server Edition systems, the name and password used for this command are those required for
security configuration 21 access which are different from those used for normal configuration access.
For Basic Edition systems, the name and password required are those of the Administrator account used for
configuration access.
For IP500 and IP500 V2 control units, if the security settings cannot be defaulted using this command, they can be
defaulted using a DTE cable connection to the system. Refer to the IP Office Installation manual for details.
8.1.8.10 Embedded File Management
For control units with a memory card installed, the contents of the card can be viewed using 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.
For Linux based systems, the folder /opt/ipoffice are used as the file repository for embedded file management actions.
For further details refer to Embedded File Management
Release 9.0
IP Office Manager
174 .
Page 153
15-601011 Issue 9.01 (Monday, September 09, 2013)
8.1.8.11 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 a Enterprise Branch SD card for use with any other IP Office mode. Doing so may damage the
SD card and make it unusable for your Enterprise Branch 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 155 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
155 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 Basic
Edition - Quick Mode PBX System operation.
· 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 Basic
Edition - Quick Mode Key System operation.
· IP Office Partner Edition
A system fitted with this type of card will default to A-Law telephony and IP Office Basic Edition - PARTNER®
Mode operation.
· IP Office Norstar Edition
A system fitted with this type of card will default to U-Law telephony and IP Office Basic Edition - Norstar®
Mode operation.
· Enerprise Branch
Use this option for an SD card intended to be used with an IP Office system running in Enterprise Branch
Mode. There is a separate SD card for Enterprise Branch. The Enterprise Branch SD card can only be used
for IP Office operation and cannot be used to change modes to IP Office. You also cannot use or change
an IP Office SD card for use with an IP Office Enterprise Branch system.
·
! Warning
Do not re-purpose a Enerprise Branch card for use with any other IP Office mode. Doing so may damage
the SD card and make it unusable for your Enterprise Branch 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.
Release 9.0
IP Office Manager
155
command to load the system
Page 154
15-601011 Issue 9.01 (Monday, September 09, 2013)
Menu Bar Commands: Configuration Mode: File Menu
8.1.8.12 Recreate IP Office SD Card
This command can be used with the System SD cards used by IP500 V2 control units. It allows Manager to copy all the
files and folders used by a system when starting onto the card that has been place into the card slot of the PC running
Manager. 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. The command also copies all language prompt sets used by
Embedded Voicemail.
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 154 ), 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 138 (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 a Enterprise Branch SD card for use with any other IP Office mode. Doing so may damage the
SD card and make it unusable for your Enterprise Branch 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 system 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 Basic
Edition - Quick Mode PBX System operation.
· 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 Basic
Edition - Quick Mode Key System operation.
· IP Office Partner Edition
A system fitted with this type of card will default to A-Law telephony and IP Office Basic Edition - PARTNER®
Mode operation.
· IP Office Norstar Edition
A system fitted with this type of card will default to U-Law telephony and IP Office Basic Edition - Norstar®
Mode operation.
· Enerprise Branch
Use this option for an SD card intended to be used with an IP Office system running in IP Office
Enterprise Branch mode. There is a separate SD card for IP Office. The IP Office Enterprise Branch SD
card can only be used for IP Office operation and cannot be used to change modes to IP Office. You also
cannot use or change an IP Office SD card for use with an IP Office Enterprise Branch system.
·
! Warning
Do not re-purpose a Enerprise Branch card for use with any other IP Office mode. Doing so may damage
the SD card and make it unusable for your IP Office Enterprise Branch system.
5. Browse to the card location and click OK.
6. Manager will prompt whether you want to include Avaya IP Office Web Manager files as part of the recreate
process.
· For systems that will be running in IP Office Basic Edition - Quick Mode mode, these files are necessary if you
want to use IP Office Web Manager to configure the system.
· For all systems, these files are necessary if you want to go through the process of on-boarding registration.
7. Manager will start creating folders on the SD card and copying the required files into those folders.
8. Do not remove the card until the process is completed and Manager displays a message that the process has been
completed.
Release 9.0
IP Office Manager
Page 155
15-601011 Issue 9.01 (Monday, September 09, 2013)
8.1.8.13 Launch Voicemail Pro Client
If the Voicemail Pro client is installed on the same PC as 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.
8.1.8.14 System Status
Release 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.
Release 9.0
IP Office Manager
Page 156
15-601011 Issue 9.01 (Monday, September 09, 2013)
Menu Bar Commands: Configuration Mode: File Menu
8.1.8.15 LVM Greeting Utility
This command launches a utility that can be used to convert .wav files to the formats used by Embedded Voicemail (c11
). 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 476 field on the Auto Attendant | Auto Attendant 476
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.
· Note: The LVM Greeting Utility option is not selectable (grayed out) when Voicemail Pro is selected as the system's
voicemail type.
8.1.8.16 Initial Configuration
Basic Mode and Standard Mode Initial Configuration
The Initial Configuration menu is displayed for all new or fully defaulted IP500 V2 systems. It allows the required
operating mode for the system to be selected.
· For Quick Mode, Partner Mode and Norstar Mode, leave the selection set to Basic Mode.
· For a system that you want to run in Essential Edition, Preferred Edition or Advanced Edition modes, select IP
Office Standard Mode.
· For an IP500 V2 system to run in Standard Mode, its configuration must include an Essential Edition license.
A Standard Mode system without this license will not allow any telephony functions.
· For a system that is being installed as an expansion server for a Server Edition solution, select Server Edition
Expansion. See below.
Server Edition Initial Configuration
On a Basic or Standard Mode system, use the Initial Confguration option to convert the existing system configuration into
a Server Edition system configuration. It will effectively default the configuration and reload it in Manager in Server
Edition mode. Once Server Edition Expansion is selected as the System Type, the Initial Configuration menu is
displayed. If Server Edition Expansion is selected in that menu, following selection of the various menu options, the
system is rebooted as a Expansion System (V2) for a Server Edition network.
For systems being configured for operation in a Server Edition solution, the Initial Configuration menu is used to set or
confirm a range of settings. The field shown and accessible in the form depend on the selected System Type.
Release 9.0
IP Office Manager
Page 157
15-601011 Issue 9.01 (Monday, September 09, 2013)
Once the menu is completed and Save is clicked, the values entered are written into the system configuration and the
system is restarted. The menu is also displayed when creating an offline configuration 61 for a Server Editionsystem.
The configuration of an existing non-Server Edition system can be converted to a Server Edition configuration, invoking
this menu, using the File | Advanced | Initial Configuration menu option.
· System Type
Indicate the type of sever role the system will perform.
· Retain Configuration Data
This option is shown for IP500 V2 units being converted to become Expansion System (V2)s in a Server Edition
solution.
· If left unselected, the default, the existing configuration of the system is defaulted as per a standard Server
Edition expansion system.
· If selected, the existing configuration is retained. However, some elements of that configuration may be invalid or
ignored in a Server Edition solution. It is the installers responsibility to ensure that the final configuration is valid
for use in the solution. See IP500 V2 Conversion 103 .
· Name:
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 <, >, |, \0, :, *, ?, . or /.
· 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 998 . For individual users the system settings can be overridden through their own locale setting (User | User
| Locale).
· Services Device ID
Set a Device ID for the system. This ID is displayed on the Solution View and System Inventory pages and on the
System | System tab in the configuration. The value can be changed using the Device ID field on the System |
System Events | Configuration 239 tab.
If an SSL VPN is configured, , Avaya recommends that the Device ID match an SSL VPN service Account Name.
Each SSL VPN service account name has an associated SSL VPN tunnel IP address. Having the displayed Device ID
match an SSL VPN service account name helps identify a particular SSL VPN tunnel IP address to use for remotely
managing IP Office.
· LAN Interface
This IP Address, IP Mask, Gateway and DHCP Mode settings can be set for the systems two LANs, LAN1 and LAN2.
These radio buttons are used to switch between displaying the LAN1 details or the LAN2 details.
· IP Address: LAN1 Default = 192.168.42.1. LAN2 Default = 192.168.43.1.
This is the IP address of the Control Unit on LAN1. If the control unit is also acting as a DHCP server on the LAN, this
address is the starting address for the DHCP address range.
· IP Mask: Default = 255.255.255.0.
This is the IP subnet mask used with the IP address.
· Gateway
The address of the default gateway for routing traffic not in the same subnet address range of the IP Address/IP
Mask set above. A default IP Route for this address is added to the systems configuration.
Release 9.0
IP Office Manager
Page 158
15-601011 Issue 9.01 (Monday, September 09, 2013)
Menu Bar Commands: Configuration Mode: File Menu
· DHCP Mode: Default = Server.
This controls the control unit's DHCP mode for the LAN. 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 this LAN, 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 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.
· Server Edition Primary Server
The IP address of the Primary Server. This address is used to add an IP line to the Primary Server to the
configuration.
· Server Edition Secondary Server
The IP address of the Secondary Server. This address is used to add an IP line to the Secondary Server to the
configuration.
· DNS Server
This is the IP address of a DNS Server. If this field is left blank, the system uses its own address as the DNS server for
DHCP client and forwards DNS requests to the service provider when Request DNS is selected in the service being
used (Service | IP 422 ).
Enterprise Branch Initial Configuration
The Initial Installation utility provides a default configuration and security settings that minimize initial installation
activities and maximize security. The system must be configured with the default settings before the system can be
administered by System Manager. This utility is used for new installations and after an upgrade to enable System
Manager administration of the IP Office.
Launching the Initial Installation Utility
1. Select File > Advanced > Launch Initial Installation Utility.
2. In the System Name field, enter the appropriate system name.
3. For the WAN Interface, select LAN1 or LAN2. If you select LAN1, the DHCP Mode is disabled.
4. In the IP Address field, enter the appropriate IP address.
5. In the IP Mask field, enter the appropriate IP mask.
6. In the Gateway field, enter the appropriate gateway. Manager will create an IP route using this gateway with the
selected WAN as the destination.
7. In the DHCP Mode section, if you selected LAN1, select the appropriate DHCP option. If you selected LAN2, DHCP
Mode is disabled.
8. Select the Under Centralized Management? check box if you want the IP Office system to be managed by
System Manager.
9. If you selected the Under Centralized Management? check box, a number of additional fields are shown,
configure these additional fields as appropriate:
· SMGR Address - the IP address of the server running System Manager
· SNMP Community
· SNMP Device ID
· Trap Community
· SCEP Domain Certificate Name
· Certificate Enrollment (SCEP) Password
Release 9.0
IP Office Manager
Page 159
15-601011 Issue 9.01 (Monday, September 09, 2013)
10. Select Save.
When you run the Initial Installation Utility, the Initial Installation utility also configures the following:
· System Status Interface (SSA) service security level – Unsecure only
· Configuration service security level –Secure, Medium
· Security Administration service security level – Secure, Medium
· OAMP Web Services service security level – Secure, Low (if locally administered)
· OAMP Web Services service security level – Secure, High (if administered by System Manager)
· Admin Client Certificate checks:-- High (if administered by System Manager)
· SCEP client active (if administered by System Manager)
· SCEP server IP address from SMGR IP address (if administered by System Manager)
· Legacy Program Code – Active (if locally administered)
If the system is administered by System Manager, the following is automatically configured:
· SNMP enabled
· SNMP trap destination 1 from System Manager IP address
· All SNMP traps active
· WebLM client active
· WebLM service address from System Manager IP address
· Remove all default extension users, leaving “NoUser” and “RemoteManager”
Release 9.0
IP Office Manager
Page 160
15-601011 Issue 9.01 (Monday, September 09, 2013)
Menu Bar Commands: Configuration Mode: File Menu
8.1.8.17 Add/Display VM Locales
This option is only displayed displayed when the configuration from an IP500 V2 systems with its Voicemail Type set to
Embedded Voicemail is received in Manager. It is not shown for off-line configuration or configurations loaded from a
PC file.
Selecting this option displays a list of the Embedded Voicemail prompt languages. Those languages already present on
the System SD card or not supported are greyed out. Additional languages can be selected and then uploaded from
Manager to the system.
When editing the system configuration in Manager, if the locale language selected for the system, a user, a short code or
an incoming call route is not already present on the System SD card, Manager will display an error. Add/Display VM
locales can then be used to upload the prompts for the required language in order to correct the error.
You can reload languages that are already installed on the System SD card. For example, you may want to reload the
languages if new prompts have been added in a maintenance release. To reload existing languages, upgrade the system
(File | Advanced | Upgrade 147 ) with the Upload System Files option checked. You can also choose Upload System
Files from the Embedded File Management utility (File | Advanced | Embedded File Management 153 ).
The Recreate IP Office SD Card
Release 9.0
IP Office Manager
155
command can be used to locally load all available languages onto an SD card.
Page 161
15-601011 Issue 9.01 (Monday, September 09, 2013)
8.1.8.18 Memory Card Command
These commands are used with the memory cards installed in IP500/IP500 V2 control units.
8.1.8.18.1 Shutdown
This command can be used to shutdown the operation of IP500 and IP500 V2 unit memory cards.
This action or a system shutdown 146 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. Card services can be restarted by either reinserting
the card or using the Start Up 162 command.
Shutting down the memory card will disable all services provided by the card including Embedded Voicemail if being
used. For IP500 V2 systems, features licensed by the memory card will continue to operate for up to 2 hours.
8.1.8.18.2 Start Up
This command can be used to restart operation of an IP500 or IP500 V2 memory card that has been shut down
command will start the Select IP Office discovery process for selection of the system.
162 .
The
8.1.9 Backup/Restore
8.1.9.1 Backup Binaries and Configuration
This command copies all configuration files (.cfg) and software binary files (.bin) stored in Manager's working directory to
a selected folder.
8.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.
Release 9.0
IP Office Manager
Page 162
15-601011 Issue 9.01 (Monday, September 09, 2013)
Menu Bar Commands: Configuration Mode: File Menu
8.1.10 Import/Export
8.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 62 .
The display shows those exportable record types for which the configuration contains records. 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
single-byte 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.
Release 9.0
IP Office Manager
Page 163
15-601011 Issue 9.01 (Monday, September 09, 2013)
8.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 163 . 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 62 .
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
single-byte 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.
8.1.11 Exit
The File | Exit command exits the Manager application.
Release 9.0
IP Office Manager
Page 164
15-601011 Issue 9.01 (Monday, September 09, 2013)
Menu Bar Commands: Configuration Mode: File Menu
8.2 Configuration Mode: View Menu
8.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.
8.2.2 Tooltip
This setting control whether additional tooltips are displayed when Manager is running in simplified view
165
mode.
8.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.
8.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.
8.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.
8.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.
8.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 a Standard Edition configuration is loaded.
8.2.8 Hide Admin Tasks
This settings shows or hides the Admin Tasks List available when Manager has a IP Office Basic Edition - PARTNER®
Mode, IP Office Basic Edition - Norstar Mode or IP Office Basic Edition - Quick Mode configuration loaded.
8.2.9 Simplified View
If Manager has no configuration loaded, this command switches it from advanced view to simplified view.
Release 9.0
IP Office Manager
Page 165
15-601011 Issue 9.01 (Monday, September 09, 2013)
8.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.
Release 9.0
IP Office Manager
Page 166
15-601011 Issue 9.01 (Monday, September 09, 2013)
Menu Bar Commands: Configuration Mode: View Menu
8.3 Configuration Mode: Tools Menu
8.3.1 Export | User
When performing an upgrade from B5800 Branch Gateway 6.2 or IP Office 8.1 to IP Office 9.0, users are not
automatically created in System Manager. Before an upgrade, IP Office users must be exported to a file and then the file
must be imported to System Manager. This feature allows you to export all users or selected users from a loaded
configuration to an XML file that is then imported in System Manager. The default filename is
<SystemName>_Users.xml.
· User Name – select this checkbox to export all users.
· User Name/Extension – select the appropriate checkboxes to export those users.
8.3.2 Extension Renumber
This command allows the extension numbering of user extensions to be changed. The existing extension number range to
be adjusted can be specified followed by the new start point for the range after renumbering.
The command does not alter the extension number used for hunt groups but does adjust the extension numbers of hunt
group members.
8.3.3 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.
8.3.4 Connect To
This option can be used to create H.323 IP line connections between two systems in a multi-site network, one being the
system with its configuration currently loaded in Manager, the other being selected from a discovery dialog. This option is
not available for Server Edition mode.
·
! 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.
Release 9.0
IP Office Manager
Page 167
15-601011 Issue 9.01 (Monday, September 09, 2013)
3. Select the system to which connection is required.
4. Enter the login name and password for configuration access to that system.
5. Manager will switch to Small Community Network management
systems.
6. Click
112
mode, displaying the configuration of both
to save the new configuration back to each system.
Release 9.0
IP Office Manager
Page 168
15-601011 Issue 9.01 (Monday, September 09, 2013)
Menu Bar Commands: Configuration Mode: Tools Menu
8.3.5 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.
1. Select Tools | SCN Service User Management.
· The option is not shown if a Basic Mode system configuration is loaded. If no configuration is loaded, and the
option is not shown, select View | Advanced View.
2. The Select IP Office menu displays the list of discovered 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 requested. 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.
Release 9.0
IP Office Manager
Page 169
15-601011 Issue 9.01 (Monday, September 09, 2013)
8.3.6 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.
8.3.7 MSN/DID Configuration
This menu can be used to populate the Incoming Call Route table with a range of MSN or DID numbers. This option is
not available when Manager is running in Server Edition mode.
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 records.
· Add
Adds the appropriate records to the Incoming Call Route table using the value entered above.
· Delete
Removes a specific record.
Release 9.0
IP Office Manager
Page 170
15-601011 Issue 9.01 (Monday, September 09, 2013)
Menu Bar Commands: Configuration Mode: Tools Menu
8.3.8 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, M Series, T-Series, 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.
· 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 via DESI to transfer the information to the DESI application. Within DESI, edit the labels as required
and then print the labels.
Release 9.0
IP Office Manager
Page 171
15-601011 Issue 9.01 (Monday, September 09, 2013)
8.3.9 Import Templates
Manager can be used to import and use trunk templates 256 . SIP trunk templates can be used to add SIP trunks. Analog
trunk templates can also be applied to existing analog trunks. This option does not affect the additional template options
78 used for Server Edition mode.
The templates need to be stored in a specific Manager sub-folder \Templates.
Some templates may be supplied with the Manager application and will be automatically installed to the correct location.
This command can be used to select a folder containing other template files and will copy those files into the correct
Manager sub-folder.
Release 9.0
IP Office Manager
Page 172
15-601011 Issue 9.01 (Monday, September 09, 2013)
Menu Bar Commands: Configuration Mode: Tools Menu
8.4 Security Mode
These commands are available when the Manager is in security configuration mode.
8.4.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.
8.4.2 Close Security Settings
Close the currently open set of security settings received from a system without saving those settings.
8.4.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.
8.4.4 Reset Security Settings
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 usable while a set of security configuration settings is
loaded.
The command File | Advanced | Erase Security Settings (Default)
configuration mode.
153
performs the same action from Manager
8.4.5 Preferences
See Preferences
136
in the Menu Bar Commands | Configuration Mode | File Menu section.
8.4.6 Exit
This command closes Manager.
8.4.7 Configuration
This command returns the Manager application to configuration mode.
Release 9.0
IP Office Manager
Page 173
15-601011 Issue 9.01 (Monday, September 09, 2013)
8.5 Embedded File Management
For control units with a memory card installed, the contents of the card can be viewed using 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. For Linux based systems access to the /opt/ipoffice folder is provided.
· 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 .c11 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 157 .
· 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 201 and HTTP Server IP
Address 201 on the System | System 201 tab must be set to match the system's LAN address.
· 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.
Release 9.0
IP Office Manager
Page 174
15-601011 Issue 9.01 (Monday, September 09, 2013)
Menu Bar Commands: Embedded File Management
8.5.1 Open File Settings
Select a system and display the contents of its memory cards if any are present and in use.
8.5.2 Close File Settings
Close the current memory card contents listing without exiting embedded file management mode.
8.5.3 Refresh File Settings
This command can be used to request a file update from the system.
8.5.4 Upload File
This command can be used to select and upload a file to the memory card in the system.
8.5.5 Upload System Files
This command is available with IP500 V2 systems. When this command is selected, Manager will upload the software files
for operation to the System SD card.
·
! WARNING
After this command is completed, the system is rebooted. This will end all calls and services in progress.
· It copies the binary files for the system control unit and possible external expansion modules.
· It copies the firmware files used by phones supported by the system.
· For systems configured to running in IP Office Basic Edition - Quick Mode, IP Office Basic Edition - PARTNER®
Mode or IP Office Basic Edition - Norstar Mode mode, the files for IP Office Web Manager are copied.
· For systems configured to run Embedded Voicemail, the Embedded Voicemail prompts for those supported
languages set as the system locale, user locales, incoming call route locales and short code locales are
upgraded. In addition the English language prompts are upgraded as follows: IP Office A-Law/Norstar SD
Cards - UK English, IP Office U Law/PARTNER SD Cards - US English.
8.5.6 Backup System Files
This command is available with IP500 V2 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 201
).
8.5.7 Restore System Files
This command is available with IP500 V2 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.
8.5.8 Upgrade Binaries
This command is available for IP500 V2 systems that have a system SD card and Optional 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.
8.5.9 Upgrade Configuration
This command is not used with IP Office systems. This command is available for IP500 V2 systems that have a system
SD card and Optional 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.
Release 9.0
IP Office Manager
Page 175
15-601011 Issue 9.01 (Monday, September 09, 2013)
·
! WARNING
After this command is completed, the system is rebooted. This will end all calls and services in progress.
8.5.10 Upload Voicemail Files
This command is available 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 IP500 V2 control units, use Upload System Files 175
.
8.5.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 IP500 V2 control units, use Upload System Files 175 .
8.5.12 Copy System Card
This command is available for IP500 V2 systems that have an Optional SD card installed in addition to the mandatory
System 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.
8.5.13 Configuration
This command will exit Embedded File Management and return Manager to configuration editing mode.
Release 9.0
IP Office Manager
Page 176
15-601011 Issue 9.01 (Monday, September 09, 2013)
Chapter 9.
Security Mode Field
Descriptions
Release 9.0
IP Office Manager
Page 177
15-601011 Issue 9.01 (Monday, September 09, 2013)
9. Security Mode Field Descriptions
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 Security Mode Screen Elements
· Menu Bar
Provides commands for loading and saving security settings. See the Menu Bar Commands
131
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 records 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. It also displays the security level of
the communications by the use of a padlock icon.
Release 9.0
IP Office Manager
Page 178
15-601011 Issue 9.01 (Monday, September 09, 2013)
Security Mode Field Descriptions: Configuring Security Settings
9.1 Configuring 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. 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.
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 136 ). 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
1. Click
in the Main Toolbar or select File | Save Security Settings from the menu bar. These options are only
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
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.
Release 9.0
IP Office Manager
Page 179
15-601011 Issue 9.01 (Monday, September 09, 2013)
9.2 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.
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 *.
· 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 records.
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. This setting is active for attempted password
changes on both Security Manager and the system.
· 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 a record indicating the service user account name and time of last failure.
· Log and Disable Account:.
Log and Disable Account creates an audit trail record and additionally permanently disables the service user
account. This account can only be enabled using the Security Manager Service User settings.
· Log and Temporary Disable:
Log and Temporary Disable creates an audit trail record and additionally temporarily disables the service user
account for 10 minutes. This account can only be enabled using the Security Manager Service User settings.
Release 9.0
IP Office Manager
Page 180
15-601011 Issue 9.01 (Monday, September 09, 2013)
Security Mode Field Descriptions: General Settings
· Minimum Password Complexity: Default = Low.
The password complexity requirements for all users.
· 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.
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 188 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 191 . 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.
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 191 . 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.
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 191 setting) – whichever is the sooner. Currently
Manager displays reminders but System Status does not.
· IP Office User Details
These settings control IP Office user password/account policies.
· Password Enforcement: Default = On.
When enabled, password settings are enforced. When disabled, password requirements are not enforced and the
remaining settings are not editable.
· Minimum Password Length: Default = 6, Range 1 to 31 characters.
This field sets the minimum password length for user passwords.
· Minimum Password Complexity: Default = Low.
The password complexity requirements for all users.
· 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, more than 2 repeated characters of any type is not allowed and the password cannot contain the user
name (case insensitive).
· High
The password characters used must cover three 'code point sets'. For example lower case plus upper case and
numbers. In addition, more than 2 repeated characters of any type is not allowed and the password cannot
contain the user name (case insensitive).
· 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 a record indicating the user account name and time of last failure.
· Log and Disable Account:.
Log and Disable Account creates an audit trail record and additionally permanently disables the user account. The
account can be enabled using the Account Status field on the User | User page.
Release 9.0
IP Office Manager
Page 181
15-601011 Issue 9.01 (Monday, September 09, 2013)
· Log and Temporary Disable:
Log and Temporary Disable creates an audit trail record and additionally temporarily disables the user account for
10 minutes. The account can be enabled using the Account Status field on the User | User page.
Release 9.0
IP Office Manager
Page 182
15-601011 Issue 9.01 (Monday, September 09, 2013)
Security Mode Field Descriptions: General Settings
9.3 System
9.3.1 System Details
This tab is accessible when
System is selected in the navigation pane.
· Base Configuration
· Services Base TCP Port: Default = 50804. Range = 49152 to 65526.
This is the base TCP port for services 187 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 136 ).
For information on port usage see the IP Office Avaya Port Matrix document on the Avaya support site at
https://support.avaya.com/helpcenter/getGenericDetails?detailId=C201082074362003
· Maximum Service Users: Default = 64.
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 = 32.
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.
· System Discovery
System discovery is the processes used by applications to locate and list available systems. The IP Office can be
disabled from responding to this process if required. If this is done, access to the IP Office requires its specific IP
address to be used.
· TCP Discovery Active: Default = On.
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:
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.
· HTTP Challenge Timeout (Seconds): Default = 10.
For HTTP/HTTPS connection attempts, this field sets the timeout for connection validation responses.
· RFC2617 Session Cache (Minutes): Default = 10.
For HTTP/HTTPS sessions, this field sets the allowed duration for successful logins as per RFC2617. Allow HTTPS:
Default = Off. Release 6.0-6.1.
Allow HTTPS connection to the system for applications such as the IP Office Softphone. For Release 7.0+, this
setting is part of the HTTP service 187 .
· Server Certificate
For Manager 10.0 and higher, security certificate settings have been moved to the separate Certificate
184
tab.
· HTTP Ports: Release 8.0+.
· HTTP Port: Default = 80.
· HTTPS Port: Default = 443.
· Web Services Port: Default =8443.
9.3.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.
Release 9.0
IP Office Manager
Page 183
15-601011 Issue 9.01 (Monday, September 09, 2013)
· VM Pro Password: Default = Blank. 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 = Blank. Range = 0 to 31 characters.
This password, if set, is used by the System Monitor application. 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.
· TFTP Directory Read: Default = On.
· Voicemail: Default = On.
· EConf: Default = On.
· Program Code: Default = On.
· Real Time Interface: Default = On.
If disabled, IP Office Delta Server and related applications cannot change the status of agents.
· Sys Monitor: Default = On.
· TAPI: Default = On.
· HTTP Directory Read: Default = On.
Allow the system's current directory records to be accessed using HTTP.
· HTTP Directory Write: Default = On.
Allow HTTP import 237 to be used to place temporary directory records into the directory.
· Application Support
This panel is shown for information only. It indicates the effect on various applications of the Application Controls
selections.
9.3.3 Certificates
Services 187 between the system and applications may, depending on the settings of the service being used for the
connection, require the exchange of security certificates. The system can either generate its own certificate or certificates
provided from a trusted source can be loaded.
·
! WARNING
The process of 'on-boarding' (refer to the IP Office Installation manual and the IP Office SSL VPN Solutions
Guide) automatically adds a certificate for the SSL VPN to the system's security settings when the on-boarding
file is uploaded to the system. Care should be taken not to delete such certificates except when advised to by
Avaya.
· Identity Certificate: Default = None.
The Identity 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 notes
below), but Set can be used to replace this with another certificate.
· The certificate may be generated by the system itself, and can take up to 5 minutes to generate. This occurs
when the Service Security Level 187 is set to a value other than Unsecure Only. During this time, normal system
operation is suspended.
· Set
Set the current 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 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.
Release 9.0
IP Office Manager
Page 184
15-601011 Issue 9.01 (Monday, September 09, 2013)
Security Mode Field Descriptions: System
· Delete
Delete the current certificate. When sent to the system, the system will generate a new certificate when next
required. This can take up to 5 minutes to generate. During this time, normal system operation is suspended.
· Offer 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 IP Office is acting as a TLS server, which occurs when accessing a secured service.
· 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 certificate.
· Issued to: Default = IP Office identity certificate.
Common name of issuer in the certificate.
· Default Certificate Name: Default = None.
· Use Different Identity Certificate for Telephony: Default = None.
A telephony certificate can be used instead of the identity certificate and is offered in a TLS exchange when the system
is acting as a TLS server for secure SIP signalling and connections to an HTTPS port by telephone endpoints.
· Set
Set the current 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 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 certificate.
· Offer 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 IP Office is acting as a TLS server, which occurs when accessing a secured service.
· 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 certificate.
· Issued to: Default = None.
Common name of issuer in the certificate.
· Received Certificate Checks (Management Interface): Default = None.
This setting is used configuration administration connections to the system by applications such as Manager. When the
Service Security Level of the service 187 being used is set to High, a certificate is requested by the system. The
received certificate is tested as follows:
· 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.
· Received Certificate Checks (Telephony Endpoints): Default = None.
This setting is used with IP telephony endpoints connecting to the system.
· 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.
· Trusted Certificate Store: Default = Empty.
The certificate store contains a set of trusted certificates used to evaluate received client certificates. Up to 25 X.509v3
certificates may be installed. 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.
Release 9.0
IP Office Manager
Page 185
15-601011 Issue 9.01 (Monday, September 09, 2013)
· Pasted from clipboard in PEM format, including header and footer text.
· Add
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 selected 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 selected certificate.
· SCEP Settings: Release 8.0+.
The Simple Certificate Enrollment Protocol is a protocol intended to ease the issuing of certificates in a network where
numerous devices are using certificates. Rather than having to individually administer the certificate being used by
each device, the devices can be configured to request a certificate using SCEP. These settings are not used in IP Office
Standard mode.
· Activity: Default = Off.
· Request Interval: Default = 120 seconds. Range = 5 to 3600 seconds.
· SCEP Server IP/Name: Default = Blank.
· SCEP Server Port: Default = 80 for HTTP and 443 for HTTPS.
· SCEP URI: Default = /ejbca/publicweb/apply/scep/pkiclient.exe
· SCEP Domain Cert Name: Default = Blank.
· SCEP Password: Default = Blank.
Release 9.0
IP Office Manager
Page 186
15-601011 Issue 9.01 (Monday, September 09, 2013)
Security Mode Field Descriptions: System
9.4 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.
· Service Port
This is the 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 base port (TCP or
HTTP) for each service is offset by a fixed amount from the ports set in System Settings.
For information on port usage see the IP Office Avaya Port Matrix document on the Avaya support site at
https://support.avaya.com/helpcenter/getGenericDetails?detailId=C201082074362003
· Service Security Level: Default = ‘Unsecure Only’.
Sets the minimum security level the service will support. See File | Preferences | Security 141 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, if any, is disabled. This or
disabled are the only options supported for the System Status Interface and Enhanced TSPI services.
· 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 183 for tests made on the received certificate. The service's unsecured TCP
port is disabled.
· Disabled
This option is available for the System Status Interface and Enhanced TSPI services. If selected, access to the
service is disabled.
· Service Access Source
For Server Edition systems, it is defaulted to Business Edition Manager. When set to Business Edition Manager,
the system can only be configured using Manager in its Server Edition mode. When set to Unrestricted, the system can
be configure using Manager in its normal Simplified View or Advanced View modes.
·
! WARNING
Opening the configuration of a Server Edition system in Manager running in any mode other than Server Edition
mode should be avoided unless absolutely necessary for system recovery. Even in that case, Manager will not
allow renumbering, changes to the voicemail type and changes to H.323 lines.
Release 9.0
IP Office Manager
Page 187
15-601011 Issue 9.01 (Monday, September 09, 2013)
9.5 Rights Groups
9.5.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
The maximum number of rights groups is 32.
· Name: Range = Up to 31 characters
The name for the Rights Group should be unique.
9.5.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 records Manager will allow members of the Rights Group to
viewed and what actions they can perform with those types of records.
Operator
View/Edit/
New/Delete
Administrator
Manager
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.
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.
New
None.
Delete
User & Group Edit
View, edit create and delete all configuration records.
View
New
Operator
Configuration Record Types
View
Delete Incoming Call Route and Directory.
User and Hunt Group records only.
Edit
New
None
Delete
User & Group Admin
All
User and Hunt Group records only.
Dir & Account Admin
All
Directory and Account Code records only.
Time & Attendant Admin
All
Time Profile and Auto Attendant records only.
ICR & User Rights Admin
All
Incoming Call Route and User Rights records only.
Read Only
View
View all configuration records.
Edit
None.
New
Delete
9.5.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 180 .
· Read all security settings
Members of the Rights Group can view the system's security settings.
Release 9.0
IP Office Manager
Page 188
15-601011 Issue 9.01 (Monday, September 09, 2013)
Security Mode Field Descriptions: Rights Groups
· Write all security settings
Members of the Rights Group can edit and return changes to the system's security settings.
· Reset all security settings:
If selected, members of the Rights Group can reset the security settings to default values.
· Write own service user password:
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 180 , Force new password 191 or Account
Expiry 191 . The new password change is requested automatically at login time.
9.5.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 IP Office 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:
If enabled, the SSA user is able to use SSA to initiate system shutdowns and memory card shutdown/restarts.
9.5.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 Release 5.0 and higher systems.
· Enhanced TSPI Access
If selected, applications in this rights group are able to use 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.
9.5.6 HTTP
These settings are displayed when
Rights Groups is selected in the navigation pane. This tab sets the HTTP
services supported for members of the group.
· DECT R4 Provisioing
This service is used to allow the system to configure the DECT R4 master base station and to respond to handsets
subscribing to the DECT R4 system. It requires both the system and DECT R4 master base station to be configured
to enable provisioning. For full details refer to the DECT R4 Installation Manual.
9.5.7 Web Services
These settings are displayed when
Rights Groups is selected in the navigation pane. They are used by users in
rights groups using web services to configure and manager the system. These are currently not used on Standard Mode
systems
IP Office Service Rights
· Security Read All
If selected, the rights group members can view system security settings.
· Security Write All
If selected, the rights group members can change system security settings.
· Security Write Own Password
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 180 , Force new password 191 or Account
Expiry 191 . The new password change is requested automatically at login time.
Release 9.0
IP Office Manager
Page 189
15-601011 Issue 9.01 (Monday, September 09, 2013)
· Config Read All
If selected, the rights group members can view system configuration settings.
· Config Write All
If selected, the rights group members can change system configuration settings.
· Backup
If selected, the rights group members can initiate the system backup process.
· Restore
If selected, the rights group members can initiate the system restore process.
· Upgrade
If selected, the rights group members can initiate the system upgrade process.
Web Manager Rights
These rights are used with web service access to a system such as the IP Office web manager used with IP Office Basic
Edition systems.
9.5.8 External
These settings are displayed when
Rights Groups is selected in the navigation pane. They are used by users in
rights groups for external components using web services to configure and manage the system.
IP Office Service Rights
· Voicemail Pro Basic
If selected, the rights group members can read the configuration and perform backup, restore, and upgrade.
· Voicemail Pro Standard
If selected, the rights group members can update the configuration and perform backup, restore, and upgrade.
· Voicemail Pro Administrator
If selected, the rights group members can update the configuration and security settings.
· one-X Portal Administrator
If selected, the rights group members can update the configuration and security settings. Does not include backup
and restore.
· one-X Portal Super User
If selected, the rights group members can perform backup and restore.
· Web Control Administrator
If selected, the rights group members can update the configuration and security settings.
Release 9.0
IP Office Manager
Page 190
15-601011 Issue 9.01 (Monday, September 09, 2013)
Security Mode Field Descriptions: Rights Groups
9.6 Service Users
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 64.
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
180 .
· 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.
· To change the current password click Change. Enter and confirm the new password. Note that an error will be
indicated if the password being entered does not meet the password rules set through General settings 180 .
· To clear the cache of previous password details used by the password rules setting, click Clear Cache. For
example, if the rule restricting the reuse of old passwords has been enabled, clearing the cache allows a previous
password to be used again.
· Account Status: Default = 'Enabled'.
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 reenable 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 188 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.
· 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 180 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 180 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 180 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 180 tab. The account can be enabled manually
by setting the Account Status back to Enabled.
· Account Expiry: Default = <None> (No Expiry).
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 180 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.
Release 9.0
IP Office Manager
Page 191
15-601011 Issue 9.01 (Monday, September 09, 2013)
Release 9.0
IP Office Manager
Page 192
15-601011 Issue 9.01 (Monday, September 09, 2013)
Chapter 10.
Configuration Mode Field
Descriptions
Release 9.0
IP Office Manager
Page 193
15-601011 Issue 9.01 (Monday, September 09, 2013)
10. Configuration Mode Field Descriptions
This following sections detail the various configuration settings provided for different record 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.
Manager Settings
The BOOTP and Operator settings are used by the Manager application itself. They are not system configuration settings.
·
BOOTP 198
Manager settings for the support of systems requesting software.
·
Operator 199
Manager settings for the editing of configuration settings from pre-Release 3.2 systems.
The way that the system configuration settings are grouped and displayed in navigation pane depends on whether
Manager is running in its normal Advanced View mode or in Server Edition mode.
Standalone System Settings
This order of display of different types of configuration record is used for IP Office Essential Edition, IP Office Preferred
Edition and IP Office Advanced Edition systems.
·
System 200
Overall settings for the data and telephony operation of the system.
·
Line 254
Settings for trunks and trunk channels within the system.
·
Control Unit 335
Information summary of the system.
·
Extension 336
Settings for extension ports.
·
User 348
Settings for each system user. They may or may not be associated with an extension.
·
Hunt Group 389
Collections of users to which calls can be directed for answer by any one of those users.
·
Short Code 417
These are numbers which when dialed trigger specific features or are translated for external dialing. Short codes
can be set at both the system wide level and locally for a particular system.
·
Service 418
Configuration settings such as user names and passwords needed for connections to data services such as the
Internet.
·
RAS 431
Remote Access Service settings for connecting incoming data calls.
·
Incoming Call Route 435
Records here are used to match incoming call details on external trunks to destinations on the system.
·
WAN Port 441
Configuration settings for the WAN ports provided on some units.
Release 9.0
IP Office Manager
Page 194
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions:
·
Directory 450
External names and numbers. Used for matching names to incoming calls and for dialing from user applications.
·
Time Profile 452
Used to control when various functions are active.
·
Firewall Profile 454
Use to control the types of data traffic that can cross into or out of the system.
·
IP Route 459
These records are used to determine where data traffic on the system should be routed.
·
Account Code 461
Used for call logging and to control the dialing of certain numbers.
·
License 464
License keys are used to enable system features and applications.
·
Tunnel 468
Used to created IPSec and L2TP data tunnels.
·
User Rights 482
Provide templates to control the settings applied to associated users.
·
Auto Attendant 475
Used when an Avaya memory card is installed in the control unit.
·
ARS 492
Automatic Route Selection is used by to control outgoing external calls.
·
Authorization Codes 479
Authorization codes are similar to account codes. However, unlike account codes which are usable by any user,
each authorization code is only usable by a specific user or users associated with a specific set of user rights.
Server Edition Settings
When Manager is being used in Server Edition mode, the navigation pane works in the same way as normal. However,
the different types of configuration records are ordered and grouped differently. This reflects the fact that some types of
record are automatically shared across all systems in the network.
Solution Settings
The first 8 types are records have special behaviors that are different from normal records stored in the configurations of
individual systems in the network.
·
User 348
These records show settings for system users. Each user may or may not be associated with an extension. All the
users configured on all systems are grouped here to allow easy configuration access. The individual user records
are still stored in the configuration of the particular system on which the user was created and can also be
accessed through that system's configuration settings. New users are created through the User settings of the
system that hosts the user.
·
Hunt Group 389
These records are groups of users to which calls can be directed for answering by any one of those users. Hunt
group records are stored in the configuration of the Primary Server but those hunt groups are advertised for use
by all systems in the network.
·
Directory 450
External names and numbers. These records are used to match names to incoming calls and for making calls by
name selection from the directory on phones or in applications. These directory records are stored in the
configuration of the Primary Server. By default all other systems in the network automatically import a copy of the
Primary Server system directory at regular intervals.
Release 9.0
IP Office Manager
Page 195
15-601011 Issue 9.01 (Monday, September 09, 2013)
By default, the following types of records are all shared and replicated by each system in the network and cannot be set
at an individual system level. That operation can be changed using the consolidation settings 77 .
·
Short Code 417
These are numbers which when dialed trigger specific features or are translated for external dialing. These short
codes are common to all systems in the network.
·
Incoming Call Route 435
Records set here are used to match incoming call details on external trunks to destinations. These incoming call
routes are shared by all systems in the network.
·
Time Profile 452
Used to control when various functions are active. The time profiles set here are shared by all systems in the
network.
·
Account Code 461
Used for call logging and to control the dialing of certain numbers. The account codes set here are shared by all
systems in the network.
·
User Rights 482
Provide templates to control the settings applied to users associated with a particular set of user rights. These user
rights are shared and replicated on all systems in the network.
Individual System Settings
In addition to the settings above, a range of other types of record can be configured for each individual system in the
network. Visibility and configuration of Short Code, Incoming Call Route, Time Profile, Account Code and User
Rights records (see above) is dependent on the consolidation settings 77 of Manager.
·
System 200
A system icon is shown for each system in the network. That is, one for the Primary Server, one for the the
Secondary Server if installed and one for each Expansion System (L) and Expansion System (V2) systems. Each
can be expanded to allow configuration of records that are particular to that system.
·
Line 254
Settings for trunks and trunk channels within the system.
·
Control Unit 335
Information summary of the system.
·
Extension 336
Settings for extension ports.
·
User 348
Settings for each system user. They may or may not be associated with an extension.
·
Short Code 417
These are numbers which when dialed trigger specific features or are translated for external dialing.
·
Service 418
Configuration settings such as user names and passwords needed for connections to data services such as the
Internet.
·
RAS 431
Remote Access Service settings for connecting incoming data calls.
·
WAN Port 441
Configuration settings for the WAN ports provided on some units.
·
Firewall Profile 454
Use to control the types of data traffic that can cross into or out of the system.
Release 9.0
IP Office Manager
Page 196
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions:
·
IP Route 459
These records are used to determine where data traffic on the system should be routed.
·
License 464
License keys are used to enable system features and applications.
·
Tunnel 468
Used to created IPSec and L2TP data tunnels.
·
ARS 492
Automatic Route Selection is used by to control outgoing external calls.
·
Authorization Codes 479
Authorization codes are similar to account codes. However, unlike account codes which are usable by any
user, each authorization code is only usable by a specific user or users associated with a specific set of user
rights.
Release 9.0
IP Office Manager
Page 197
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.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 record for the system, provide the software file
indicated by that record.
BOOTP records are not part of a system's configuration settings, they are items saved on the Manager PC. Normally
Manager automatically creates a BOOTP record for each system with which it has communicated, up to a maximum of 50
records. However BOOTP records 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 135 or File | Preferences | Directories 138 . 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 136 .
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. 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.
335
· 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. 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 136 and untick Enable time server.
Release 9.0
IP Office Manager
Page 198
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: BOOTP
10.2 Operator
Operator records are not part of a system's configuration settings. They are used when a pre-Release 3.2
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 Record Types
Administrato
r
All configuration records.
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 Routing, Account Code, ARS.
Operator
View all configuration records. 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.
Release 9.0
IP Office Manager
Page 199
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.3 System
There is one System record for each system being managed. When using Manager in Server Edition or Small
Community Network Management 112 modes, clicking on the System icon for a particular system displays a
system inventory 120 page for that system.
The following tabs are part of the System form:
· System 201
General settings for the system.
· LAN1 204
Network settings for the RJ45 Ethernet LAN port on the control unit.
· LAN2 212
Network settings for the RJ45 Ethernet WAN port on the control unit.
· DNS 213
Specify the Domain Name Server addresses to use for address resolution.
· Voicemail 214
Details the type and location of the voicemail server.
· Telephony 219
System-wide telephony settings.
· Directory Services 230
Settings to allow the system to import directory numbers from other sources.
· System Events 238
Simple Network Management Protocol (SNMP), email (SMTP), and Syslog settings for the sending of system events.
· SMTP 244
Settings for SMTP email sending from the system.
· Twinning 246
System wide controls for the use of Mobile Twinning.
· SMDR 245
Settings for the sending of call records to a specified IP address.
· CCR 250
This form is used for settings specific to the Customer Call Reporter (CCR) application. Not supported in multi-site
networks.
Release 9.0
IP Office Manager
Page 200
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: System
10.3.1 System
Usability
· These settings are mergeable. However, changes to Locale or Favor RIP Routes over Static Routes require a
reboot.
Configuration Settings
· 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 <, >, |, \0, :, *, ?, . or /.
· Contact Information: Default = Blank.
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 57 .
· 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 998 . For individual users the system settings can be overridden through their own locale setting (User | User
| Locale).
· Location: Default = None.
Specify a location to associate the system with a physical location. Associating a system with a location allows
emergency services to identify the source of an emergency call. The drop down list contains all locations that have
been defined in the Location 506 page.
· Customize Locale Settings:
The Customize locale matches the Saudi Arabia 1042 locale but with the following additional controls shown below. For
other locales, these are set through the System | Telephony | Tones and Music 223 form.
· Tone Plan: Default = Tone Plan 1
The tone plan control tones and ringing patterns. The options are:
· Tone Plan 1: United States
1052
· Tone Plan 2: United Kingdom
· Tone Plan 3: France
1017
· Tone Plan 4: Germany
· Tone Plan 5: Spain
1045
.
1051
.
.
1020
.
.
· CLI Type:
This field is used to set the CLI detection used for incoming analogue trunks. The options are DTMF, FSK V23 and
FSK BELL202.
· Device ID: Server Edition Only.
Displays the value set for Device ID on the System | System Events | Configuration 239 tab.
If an SSL VPN is configured, , Avaya recommends that the Device ID match an SSL VPN service Account Name.
Each SSL VPN service account name has an associated SSL VPN tunnel IP address. Having the displayed Device ID
match an SSL VPN service account name helps identify a particular SSL VPN tunnel IP address to use for remotely
managing IP Office.
· TFTP Server IP Address: Default = 0.0.0.0 (Disabled).
While running, Manager can act as a TFTP server and provides files from its configured binaries directory 138 . To set
the address to broadcast, use the value 255.255.255.255. TFTP can also be disabled through the Enable BootP and
TFTP Servers 136 command.
· On Server Edition Systems, the default setting on the Primary Server is 0.0.0.0 (disabled). The default setting on
Secondary and Expansion servers is the address of the Primary Server.
· For Avaya IP phones using the system for DHCP, the address set here is used when they make TFTP requests for
software and settings files.
· On systems with an Avaya memory card, 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 153 .
· 1100, 1200, 1600 and 9600 Series IP phones do not support TFTP and require an HTTP Server IP Address (see below)
to be specified.
Release 9.0
IP Office Manager
Page 201
15-601011 Issue 9.01 (Monday, September 09, 2013)
· This address is only used in DHCP responses if the Phone File Server Type is set to Custom.
· HTTP Server IP Address: Default = 0.0.0.0 (Disabled).
For Avaya IP phones using the system for DHCP, the address set here is used when they make HTTP requests for
software and settings files. The files for download should be placed in the HTTP server's root directory.
· Using the system's own memory card is supported as the source for HTTP files. This is supported for up to 50 IP
phones total. This is done by setting the TFTP Server IP Address and HTTP Server IP Address to match the
system IP address.
· HTTP-TFTP Relay is support using Manager as the TFTP server (not supported by Linux based systems). 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.
· This address is only used in DHCP responses if the Phone File Server Type (see below) is set to Custom.
· Phone File Server Type: Default = Memory Card (Disk on a Linux system).
For IP (H.323 and SIP) phones using the system as their DHCP server, the DHCP response can include the address of a
file server from which the phone should request files. The setting of this field control which address is 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
Disk
LAN IP Address
LAN IP Address
Manager
LAN IP Address
Manager PC IP Address
· Custom
The DHCP response provided to phones it is supporting contains the TFTP Address from the TFTP Server IP
Address above and the HTTP Address from the HTTP Server IP Address above.
· Memory Card (Disk on a Linux system)
The system will respond to file requests from phones using files on its own memory card. The DHCP response
provided to phones it is supporting contains the LAN address of the system for both TFTP and HTTP address.
· Manager
The system will forward any H.323 phone file request to the configured Manager PC IP Address set below.
HTTP-TFTP relay is used for HTTP requests. The DHCP response provided to phones the system is supporting
contains the LAN address of the system for the HTTP Address. This option is not supported for Linux based systems.
· HTTP Redirection: Default = Off.
Allows for the use of an alternate HTTP file server for the download of large binary files. This field is available when
the Phone File Server Type is set to Memory Card (or Disk on a Linux system).
When this field is set to Phone Binaries, 96x1 H.323 phones requesting their binary files are redirected to the HTTP
server defined in the HTTP Server IP Address field.
· Manager PC IP Address: Default = 0.0.0.0 (Broadcast).
This address is used when the Phone File Server Type is set to Manager.
· Avaya HTTP Clients Only: Default = Off.
When selected, the system only responds to HTTP requests from sources it identifies as another system, an Avaya
phone or application.
· Enable SoftPhone HTTP Provisioning: Default = Off.
This option must be enabled if the IP Office Video Softphone is being supported.
· Favour RIP Routes over Static Routes: Default = Off
RIP 460 can be enabled on the system LAN1 204 and LAN2 212 interfaces, and on specific Services 418 . 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 459 ,
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. This option is not supported on
Linux based systems.
· Automatic Backup: Default = On.
This command is available with IP500 V2 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.
· Provider: Default = Not visible.
This field is visible only if the system has been branded by addition of a special license for a specific equipment
provider. The branding is fixed, that is it remains even if the license is subsequently removed. The number shown is a
unique reference to the particular equipment provider for whom the system has been branded. When branded, the
equipment provider's name is displayed on idle phone displays and other provider related features are enabled.
Release 9.0
IP Office Manager
Page 202
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: System
· Time Setting Config Source: Default = See below.
The time is either set manually (see Date and Time 509 ), 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.
· For Server Edition networks, the Primary Server is defaulted to use SNTP to 0.pool.ntp.org to obtain its time
and date. The Secondary Server and expansion servers are defaulted to use SNTP to obtain their time from
the Primary Server.
· For other IP Office systems the default is Voicemail Pro/Manager. This option should not be used with
Server Edition systems and systems with a Unified Communication Module as in those scenarios the voicemail
server is being hosted by and getting its time from the same server as the IP Office.
· 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 350 ). The system can then automatically apply daylight saving settings to the
manually set time.
· 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.
This option should not be used with Server Edition systems and systems with a Unified Communication Module as
in those scenarios the voicemail server is being hosted by and getting its time from the same server as the IP
Office.
· 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 136 ).
· SNTP
Use a list of SNTP servers to obtain the UTC time. The records 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 Settings
· Time Server Address: Default = Blank
Enter a list of IP addresses for the SNTP servers. Separate each record with a space. The use of broadcast
addresses is not supported. The list is used in order of the records until a response is received.
· Time Offset: 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 -05: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.
· File Writer IP Address: Default = 0.0.0.0 (Disabled)
This field set the address of the PC allowed to send files to the System SD card installed in the system using HTTP or
TFTP methods other than embedded file management.On systems with an Avaya memory card, this field sets the
address of the PC allowed to send files to the memory card using HTTP or TFTP methods other than embedded file
management. For Linux based systems it is applied to non-embedded file management access to the /opt/ipoffice
folder on the server. An address of 255.255.255.255 allows access from any address. If embedded file management
174 is used, this address is overwritten by the address of the PC using embedded file management (unless set to
255.255.255.255).
· 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, Smart Card or System SD 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 IP500 V2
systems, the serial number is printed on the System SD card and prefixed with FK. For Linux based telephone systems
this field is replaced by the System Identification field below.
· 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).
Release 9.0
IP Office Manager
Page 203
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.3.2 LAN1
This tab is used to configure the behavior of the services provided by the system's first LAN interface.
Up to 2 LAN's (LAN1 and LAN2) can be configured. 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.
Release 9.0
IP Office Manager
Page 204
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: System
10.3.2.1 LAN Settings
This form is used to set the general LAN settings for the LAN interface such as the IP address mode.
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
Configuration Settings
· IP Address: Default = 192.168.42.1 or DHCP client. See Default Settings 68 .
This is the IP address of the Control Unit on LAN1. If the control unit is also acting as a DHCP server on the LAN, this
address is the starting address for 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.
68
.
· 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) 460 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 458 records. For Server Edition systems this setting is only available on Expansion System (V2)
systems.
· 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 987 should be used for IP traffic from LAN1 to LAN2. 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. Range =
This defines the number of sequential IP addresses available for DHCP clients.
68
1 to 999.
· DHCP Mode: Default = DHCP Client. See Default Settings 68 .
This controls the control unit's DHCP mode for the LAN. 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 this LAN, 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 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: (IP500/IP500 V2 only).
The system can be configured with a number of DHCP Pools
Release 9.0
IP Office Manager
211
from which it can issue IP addresses.
Page 205
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.3.2.2 VoIP
This form is used to set the system defaults for VoIP operation on the LAN interface.
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
Configuration Settings
· H.323 Gatekeeper Enable: Default = On
This settings enables gatekeeper operation.
· H.323 Auto-create Extn: Default = On (Off on Server Edition and on Enterprise Branch deployments under Avaya
Aura System Manager management)
When this option is on, an extension record is automatically created for H.323 phones registering themselves with
the system as their gatekeeper. SIP Extensions use a separate setting.
· If using resilience backup 603 to support Avaya IP phones, Auto-create Extn and Auto-create User should
not be left enabled after initial configuration or any subsequent addition of new extensions and users. Leaving
auto-create options enabled on a system that is a failover target may cause duplicate extension/user records
on the multi-site network under multiple failure scenarios.
· H.323 Auto-create User: Default = Off
When this option is on and H.323 Auto-create Extn is also on, when a new H.323 extension is created a matching
user record is also created.
· H.323 Remote Extn Enable: Default = Off.
The system can be configured to support remote H.323 extensions 590 in the case where NAT is used in the
connection path. This could be the case where the IP Office is located behind a corporate NAT/Firewall router and/or
the H.323phone is located behind residential NAT enable router.
· The use of this option and the interaction and configuration of external third party elements is beyond the scope
this help file.
· When this setting is enabled, the Allow Remote Extn option is available on the Extension | VoIP
H.323 Extensions.
341
form of all
· In the case where the public IP address of the corporate router is unknown, the LAN's Network Topology 209
settings should be used to configure a STUN Server. Enabling the Allow Remote Extn option also makes visible
the configuration of the RTP Port number Range (Remote Exten) settings below.
· This option is not supported if the Firewall/NAT Type (System | LAN1 | Network Topology
Symmetric Firewall or Open Internet.
209 )
is set to
· Currently, only 9600 Series phones are supported as H.323 remote extensions.
· 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.
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.
· Auto-create Extn/User: Default = On (Off on Server Edition and on Enterprise Branch deployments under Avaya
Aura System Manager management).
If on, a new extension and user records are created by the registration of a new SIP endpoint. If off, SIP endpoint
can only register against existing configuration records. If a password is requested by a SIP device during
registration to create a new user and extension records in the system configuration, 0000 should be used. If
registering against an existing user record, the user Login Code should be used if set or 0000 if the user does not
have a Login Code set.
Note: This setting is not applicable to the Avaya A175 Desktop Video Device with the Avaya Flare® Experience.
· Domain Name: Default = Blank. Range = Maximum 33 characters.
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 = TCP and UDP.
This field is used to select which protocosl are supported for SIP connections: TCP, UDP, or TLS.
· TCP Port: Default = 5060.
The port to use for SIP TCP support if TCP is selected as the Layer 4 Protocol above.
· UDP Port: Default = 5060.
The port to use for SIP UDP support if UDP is selected as the Layer 4 Protocol above.
· TLS Port: Default = 5061.
The port to use for SIP TLS support.
Release 9.0
IP Office Manager
Page 206
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: System
· 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.
· RTP
· Port Number Range:
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.
·
!Important
The minimum and maximum settings of the port range should only be adjusted after careful consideration of
the customer network configuration and existing port usage. For pre-Release 8.1 FP1 systems, the gap between
the minimum and maximum port values must be at least 1024. For Release 8.1 FP1 and higher, the gap
between the minimum and maximum port values must be at least 254.
· Port Range (minimum): Default = 49152. Range = 1024 to 65280.
This sets the lower limit for the RTP port numbers used by the system.
· Port Range (maximum): Default = 53246. Range = 1278 to 65534.
This sets the upper limit for the RTP port numbers used by the system.
· Port Number Range (NAT):
· Port Range (minimum): Default = 49152. Range = 1024 to 65280.
· Port Range (maximum): Default = 53246. Range = 1278 to 65534.
· Enable RTCP Monitor On Port 5005: Default = On.
For 1600, 4600, 5600 and 9600 Series H.323 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 H.323 phones when the register with the system. therefore any
change to this setting requires H.323 phones that have already been registered to be rebooted. Avaya H.323
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 H.323 phone settings. The system does not
support the RTCPMON option.
· Keepalives: These settings can be used with SIP trunks associated with the LAN through their Use Network
Topology Info setting (Line | Transport 320 ). 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.
· 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 applies the DiffServ settings to outgoing traffic on any SIP lines which have their User Network
Topology Info setting (Line | Transport 320 ) set to match the LAN interface. DiffServ settings are not applied to any
other traffic on the systems LAN interface.
· The system does not use DiffServ markings used to prioritize traffic on its LAN interface.
· 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.
· The hex and decimal entry fields for the following values are linked, the hex value being equal to the decimal
multiplied by 4.
Release 9.0
IP Office Manager
Page 207
15-601011 Issue 9.01 (Monday, September 09, 2013)
· 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. By default, the same setting is used for audio and
video. If desired, you can configure separate values for audio and video. For correct operation, especially over WAN
links, the same value should be set at both ends.
· Video DSCP (Hex): Default = B8 (Hex)/46 (decimal). Range = 00 to FC (Hex)/0 to 63 (decimal)
The DiffServ Code Point (DSCP) setting applied to video VoIP calls. For correct operation, especially over WAN links,
the same value should be set at both ends.
· 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. 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.
This option is applied to H.323 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.
This is the SSON used for responses to 1100/1200 Series phones using the system for DHCP.
· 1100 Voice VLAN IDs: Default = Blank.
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.
Release 9.0
IP Office Manager
Page 208
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: System
10.3.2.3 Network Topology
STUN (Simple Traversal of UDP through NAT) is a mechanism used with overcome the effect of NAT firewalls. The
network address translation (NAT) action performed by this type of firewall can have negative effects on VoIP calls.
Test packets are sent by the system to the address of the external STUN server, those packets crossing the firewall in
the process. The STUN server replies and includes copies of the packets it received in the reply. By comparing the packet
sent and received, it is possible for the system to determine the type of NAT firewall and to modify future packets to
overcome the effects of the firewall.
· These settings are used for SIP trunk connections from the LAN. For further details of system SIP operation refer
to the SIP Line 312 section. The use of STUN is unnecessary if the SIP ITSP uses a Session Border Controller
(SBC). Use of SIP requires entry of SIP Trunk Channels licenses.
· For Release 8.0+, the network topology settings are also used for H.323 remote extensions supported on the LAN.
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
Configuration Settings
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
Enter the IP address or fully qualified domain name (FQDN) 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.
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.
Release 9.0
IP Office Manager
Page 209
15-601011 Issue 9.01 (Monday, September 09, 2013)
· 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
Use the RTP Port Number Range specified on the VoIP
as open on any NAT firewall involved.
206
tab without STUN translation. Those ports must be fixed
· 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
The public port value for UDP, TCP, and TLS. For each protocol, 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.
· When this option is used, a
information icon is shown against the fields to indicate that the values were
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.
Release 9.0
IP Office Manager
Page 210
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: System
10.3.2.4 DHCP Pools
DHCP pools allows for the configuration of of IP address pools for allocation by the system when acting as a DHCP server.
On an IP500 V2 system, you can configure up to 8 pools. On Server Edition Linux systems, you can configure up to 64
pools.
By default the DHCP settings (IP Address, IP Mask and Number of DHCP IP Addresses) set on the LAN Settings 205 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.
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
Configuration Settings
· 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 206 sub-tab.
· DHCP Pool
The first pool matches the IP Address, IP Mask and Number of DHCP IP Addresses on the LAN Settings 205 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.255.255.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 459 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.
Release 9.0
IP Office Manager
Page 211
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.3.3 LAN2
This set of tabs is used to configure the system's second LAN interface.
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
Configuration Settings
The fields available for LAN2 are the same as for LAN1
204
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.
Release 9.0
IP Office Manager
Page 212
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: System
10.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 it can also
provide them with their DNS and WINS settings if requested by the client.
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
Configuration Settings
· DNS Service IP Address: Default = 0.0.0.0 (Do not provide DNS/Use DNS forwarding)
This is the IP address of a 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 422 ).
· 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". For Server Edition this field is only available on Expansion System (V2) servers.
· 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. For Server Edition this field is only available on Expansion
System (V2) servers.
Release 9.0
IP Office Manager
Page 213
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.3.5 Voicemail
The following settings are used to set the system's voicemail server type and location. Fields are enabled or grayed out
as appropriate to the selected voicemail type. Refer to the appropriate voicemail installation manual for full details.
Usability
· Changes to Voicemail Type require a reboot.
Configuration Settings
Voicemail Type:
Defaults: Non-Server Edition = Embedded Voicemail, Primary Server = Voicemail Pro, Server Edition Secondary Server
with independent voicemail or for Outbound Contact Express = Voicemail Pro, Server Edition Others: Centralized
Voicemail.
Sets the type of voicemail system being used.
· None
No voicemail operation.
· Avaya Aura Messaging
Select this option if you want to configure the system to use Avaya Aura Messaging as the central voicemail system.
If you choose this option, you are still able to use Embedded Voicemail or Voicemail Pro at each branch to provide
auto-attendant operation and announcements for waiting calls. When selected, access to voicemail is routed via an
SM line to the numbers specified in the AAM Number field. The optional AAM PSTN Number can be configured for
use when the SM Line is not in service.
· For a setup where the voicemail box numbers configured on Avaya Aura Messaging or Modular Messaging
are same as the caller's DID, the short code to route the PSTN call should be such that the caller-id is
withheld ( "W" in the telephone-number of the shortcode ). This is to make sure that, during rainy day the voicemail system does not automatically go to the voicemail box of the caller based on the caller id.
· CallPilot
Select this option if you want to configure the system to use CallPilot over SIP as the central voicemail system. If
you choose this option, you are still able to use Embedded Voicemail or Voicemail Pro at each branch to provide
auto-attendant operation and announcements for waiting calls. When selected, access to voicemail is routed via SM
line to the numbers specified in the CallPilot Number field. The optional CallPilot PSTN Number can be
configured for use when the SM Line is not in service.
· NOTE: The CallPilot PSTN Number field and associated Enable Voicemail Instructions Using DTMF
check box are not supported. IP Office cannot access the CallPilot system over the PSTN when the Session
Manager line is down.
· Centralized Voicemail
Select this option when using a Voicemail Pro system installed and licensed on another system in a multi-site
network. The outgoing line group of the H.323 IP line connection to the system with the Voicemail Pro should be
entered as the Voicemail Destination. In a Server Editionnetwork this option is used on the Secondary Server
and expansion systems to indicate that they use the Primary Server for as their voicemail server.
· Distributed Voicemail:
This option can be used when additional Voicemail Pro voicemail servers are installed in a multi-site 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 H.323 IP 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. This option is not
supported by Server Edition systems.
· Embedded Voicemail
On systems with an Avaya memory card, select this option to run Embedded Voicemail which stores messages and
prompts on the memory card. It also supports internal Auto Attendant 475 configuration through the system
configuration. The IP500/IP500 V2 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. This option is not supported by Server Edition systems.
· Group Voicemail
This option is used to support third-party voicemail systems attached by extension ports in the group specified as
the Voicemail Destination. This option is not supported by Server Edition systems.
· Modular Messaging over SIP
Select this option if you want to configure the system to use Modular Messaging over SIP as the central voicemail
system. If you choose this option, you are still able to use Embedded Voicemail or Voicemail Pro at each branch to
provide auto-attendant operation and announcements for waiting calls. When selected, access to voicemail is routed
via an SM line to the numbers specified in the MM Number field. The optional MM PSTN Number can be
configured for use when the SM Line is not in service.
Release 9.0
IP Office Manager
Page 214
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: System
NOTE: Embedded Voicemail and Voicemail Pro are available only in Distributed branch deployments. They are not
available when there are centralized users configured for a IP Office system that is deployed as either a Centralized
branch or a mixed branch.
The Embedded Voicemail option uses the Essential Edition and the Additional Voicemail Ports licenses to control the
number of ports that can be used. These licenses are also used to control the number of ports on systems where
Embedded Voicemail is configured to provide local Auto Attendant and announcements while the selected option for
voicemail is one of the central voicemail options through the Session Manager (i.e. Avaya Aura Messaging, Modular
Messaging, or CallPilot).
Similarly, the Voicemail Pro option uses the Preferred Edition and the Incremental Voicemail Ports licenses to control
the number of ports that can be used. These licenses are also used to control the number of ports on systems where
Voicemail Pro is configured to provide local Call Flow processing while the selected option for voicemail is Avaya Aura
Messaging, Modular Messaging or CallPilot.
· 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 show
below. If the required set of prompts is not available, the voicemail will fallback to another appropriate
language and finally to English (refer to the appropriate voicemail installation manual for details).
· Short Code Locale: The short code locale, if set, is used if the call is routed to voicemail using the short
code.
· Incoming Call Route Locale: The incoming call route locale, if set, is used if caller is external.
· User Locale: The user locale, if set, is used if the caller is internal.
· System Locale: If no user or incoming call route locale is set, the system locale is used unless
overridden by a short code locale.
· Systems using Embedded Voicemail, if the required set of upgraded language prompts to match the locale is
not present on the system SD card, Manager will display an error. The required prompt set can be uploaded
from Manager using the Add/Display VM Locales 161 option.
· 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. This option is not supported by Server Edition systems.
· Voicemail Pro
Select this option when using Voicemail Pro. The IP address of the PC being used should be set as the Voicemail IP
Address. In a Server Editionnetwork this option is used on the Primary Server. It can also be used on the IP
Office Server Edition Secondary Server if the Secondary server is connected to its own voice mail server or if the
Secondary Server is part of an Outbound Contact Express deployment.
Use of Voicemail Pro requires licenses for the number of simultaneous calls to be supported. Licenses are not
required for an Outbound Contact Express deployment.
· Voicemail Mode: Default = IP Office Mode.
Embedded Voicemail on IP500 V2 systems can use either IP Office Mode or Intuity Mode key presses for mailbox
functions. End users should be provided with the appropriate mailbox user guide for the mode selected. IP500 and preRelease 8.0 systems use IP Office Mode only. You can switch between modes without losing user data, such as
passwords, greetings, or messages.
The following user guides are available from the Avaya support web site:
· IP Office Basic Edition - Embedded Voicemail User Guide (Intuity Mode)
· IP Office Basic Edition - Embedded Voicemail User Guide (IP Office Mode)
· IP Office Basic Edition Norstar Mode - Embedded Voicemail User Guide (Intuity Mode)
· IP Office Basic Edition Norstar Mode - Embedded Voicemail User Guide (IP Office Mode)
· IP Office Basic Edition Partner Mode - Embedded Voicemail User Guide (Intuity Mode)
· IP Office Basic Edition Partner Mode - Embedded Voicemail User Guide (IP Office Mode)
· IP Office Essential Edition - Embedded Voicemail User Guide (Intuity Mode)
· IP Office Essential Edition - Embedded Voicemail User Guide (IP Office Mode)
· IP Office Voicemail Pro Mailbox User Guide (Intuity Mode)
· IP Office Voicemail Pro Mailbox User Guide (IP Office Mode)
· Add/Display VM Locales
For new IP500 V2 SD cards and cards recreated using Manager, the following Embedded Voicemail languages set are
placed onto cards by default. Using this option displays the list of languages that can be uploaded from Manager. Those
languages already present or not supported are greyed out. If a locale is selected for the system, a user, a short code
or an incoming call route which is not present on the SD card, Manager will display an error. This command can be
used to upload the required language prompts to correct the error.
Release 9.0
IP Office Manager
Page 215
15-601011 Issue 9.01 (Monday, September 09, 2013)
· Voicemail Destination: Defaults: Non-Server Edition = Blank, Server Edition = IP trunk connection to the Primary
Server.
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 line 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: Defaults: Non-Server Edition = 255.255.255.255, Primary Server = Primary Server IP
Address.
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. If the system is fitted with an
Unified Communication Module hosting Voicemail Pro, the field should be set to 169.254.0.2.
· Backup Voicemail IP Address : Defaults: Primary Server = Secondary Server IP Address, All others = 0.0.0.0 (Off).
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.
· 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.
· Voicemail Channel Reservation:
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.
· Call Recording
These setting relate to call recording. Call recording is only supported when using a Voicemail Pro voicemail
server.
· Auto Restart Paused Recording (secs): Default = 15 seconds. Range = Never or 5 to 999 seconds.
If recording, manual or automatic, of a call is halted using a Pause Recording 896 button, this timer determines
when recording is restarted if the button is not pressed again.
· Hide Auto Recording: 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 recording suppresses this recording indication.
· Maximum Record Time: Default = 120 seconds. Range = 30 to 180 seconds. Release 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.
· Messages Button Goes to Visual Voice: Default = On.
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 928 .
· DTMF Breakout:
Allows system defaults to be set. These are then applied to all user mailboxes unless the users own settings differ.
Release 9.0
IP Office Manager
Page 216
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: System
· The Park & Page feature is supported when the system voicemail type is configured as Embedded Voicemail
or Voicemail Pro. Park & Page is also supported on systems where Avaya Aura Messaging, Modular
Messaging over SIP, or CallPilot (for IP Office Aura Edition with CS 1000 deployments) is configured as the
central voice mail system and the local Embedded Voicemail or Voicemail Pro provides auto attendant
operation. The Park & Page feature allows a call to be parked while a page is made to a hunt group or
extension. This feature can be configured for Breakout DTMF 0, Breakout DTMF 2, or Breakout DTMF 3.
· 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 in IP Office mode).
· For voicemail systems set to Intuity emulation mode, the mailbox owner can also access this option when
collecting their messages by dialing *0.
· If the mailbox has been reached through a Voicemail Pro 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.
· When Park & Page is selected for a DTFM breakout, the following drop-down boxes appear:
· Paging Number – displays a list of hunt groups and users (extensions). Select a hunt group or
extension to configure this option.
· Retries – the range is 0 to 5. The default setting is 0.
· Retry Timeout – provided in the format M:SS (minute:seconds). The range can be set in 15-second
increments. The minimum setting is 15 seconds and the maximum setting is 5 minutes. The default
setting is 15 seconds
· 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 in IP Office 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 in IP Office mode).
· SIP Settings
For Enterprise Branch deployments, these settings are used for calls made or received on a SIP line where any of the
line’s SIP URI fields are set to use internal data.
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 shown if the system has SIP trunks or is set
to use Voicemail Lite/Pro, Centralized Voicemail or Distributed Voicemail.
· SIP Name: Default = Blank on Voicemail tab/Extension number on other tabs.
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 = Blank on Voicemail tab/Name on other tabs.
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 = Blank on Voicemail tab/Extension number on other tabs.
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 = On on Voicemail tab/Off on other tabs.
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.
Voicemail Language Prompts
· 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 show
below. If the required set of prompts is not available, the voicemail will fallback to another appropriate
language and finally to English (refer to the appropriate voicemail installation manual for details).
· Short Code Locale: The short code locale, if set, is used if the call is routed to voicemail using the short
code.
· Incoming Call Route Locale: The incoming call route locale, if set, is used if caller is external.
· User Locale: The user locale, if set, is used if the caller is internal.
· System Locale: If no user or incoming call route locale is set, the system locale is used unless
overridden by a short code locale.
Release 9.0
IP Office Manager
Page 217
15-601011 Issue 9.01 (Monday, September 09, 2013)
· Systems using Embedded Voicemail, if the required set of upgraded language prompts to match the locale is
not present on the system SD card, Manager will display an error. The required prompt set can be uploaded
from Manager using the Add/Display VM Locales 161 option.
Release 9.0
IP Office Manager
Page 218
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: System
10.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 361 tab. The settings are split into a number of sub-tabs.
10.3.6.1 Telephony
This page is used to configure a wide range of general purpose telephony settings for the whole system.
Usability
· These settings are mergeable. However, changes to Companding LAW and Automatic Codec Preference
require a reboot.
Configuration Settings
· Analog Extensions
These settings apply only to analog extension ports provided by the system. For Server Edition this field is only
available on Expansion System (V2) systems.
· 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 543 . This setting can be overridden by a user's User | Telephony | Call
Settings | Outside Call Sequence 361 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. 543 This setting can be overridden by a user's User | Telephony | Call
Settings | Inside Call Sequence 361 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.
This setting can be overridden by a user's User | Telephony | Call Settings | Ringback Call Sequence 361
setting.
543
· Restrict Analog Extension Ringer Voltage: Default = Off. Release 6.1+
Supported on IP500 V2 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 339 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 30 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 703 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 361 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 391 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.
Release 9.0
IP Office Manager
Page 219
15-601011 Issue 9.01 (Monday, September 09, 2013)
· Ring Delay: Default = 5 seconds. Range = 0 to 98 seconds.
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
365 ).
· Call Priority Promotion Time (secs): Default = Disabled. Range = Disabled, 10 to 999 seconds. Release 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 395 , 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.
· Default Currency: Default = Locale specific 998 . Release 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 1055 . The currency is displayed in the system SMDR
output.
· Default Name Priority: Default = Favour Trunk. Release 8.0+.
For SIP trunks, the caller name displayed on an extension can either be that supplied by the trunk or one obtained by
checking for a number match in the extension user's personal directory 387 and the system directory 450 . This setting
determines which method is used by default. For each SIP line, this setting can be overridden by the line's own Name
Priority setting if required. Select one of the following options:
· Favour Trunk
Display the name provided by the trunk. For example, the trunk may be configured to provide the calling number
or the name of the caller. The system should display the caller information as it is provided by the trunk. If the
trunk does not provide a name, the system uses the Favour Directory method.
· Favour Directory
Search for a number match in the extension user's personal directory and then in the system directory. The first
match is used and overrides the name provided by the SIP line. If no match is found, the name provided by the
line, if any, is used.
· Media Connection Preservation: Default = Disabled.
When enabled, attempts to maintain established calls despite brief network failures. Call handling features are no
longer available when a call is in a preserved state. When enabled, Media Connection Preservation applies to SCN links
and Avaya H.323 phones that support connection preservation.
· Companding LAW
These settings should not normally be changed from their defaults. They should only be used where 4400 Series
phones (U-Law) are installed on systems which have A-Law digital trunks.
· 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 IP500 V2 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 Mode cards are U-Law. Norstar Mode cards are
A-Law.
· 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.
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. This option is fixed as On
and is not adjustable.
Release 9.0
IP Office Manager
Page 220
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: System
· Show Account Code: Default = On
This setting controls the display and listing of system account codes:
· When on: When entering account codes through a phone, the account code digits are shown while being dialed.
· When off: When entering account codes through a phone, the account code digits are replaced by s characters on
the display.
· 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 565 .
· Restrict Network Interconnect: Default = Off.
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: multi-site networks, VPNremote, application telecommuter mode.
· Drop External Only Impromptu Conference: Default = Off. Release 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. If not selected, the conference is automatically ended when the
last internal party or trunk that supports reliable disconnect exits the conference. The Inhibit Off-Switch Forward/
Transfer option above is no longer applied to conference calls.
· Visually Differentiate External Call: Default = Off.
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 their 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.
· Unsupervised Analog Trunk Disconnect Handling: Default = Off.
When using analog trunks, various methods are used for trunk supervision, ie. to detect when the far end of the trunk
has disconnected and so disconnect the local end of the call. Depending on the locale, the system uses Disconnect
Clear signalling and or Busy Tone Detection. This setting should only be enabled if it is know that the analog trunks do
not provide disconnect clear signalling or reliable busy tone. For Server Edition this field is only available on Expansion
System (V2) systems. When enabled:
· Disconnect Clear
266
signalling detection is disabled. Busy tone detection
224
remains on.
· Unsupervised transfers and trunk-to-trunk transfers of analog trunk calls are not allowed. The Allow Analog
Trunk to Trunk Connect setting on analog trunks (Line | Analog Options 264 ) is disabled.
· If Voicemail Pro is being used for external call transfers, Supervised Transfer actions should be used in call flows
rather than Transfer actions.
· All systems in the network must have this setting set to match each other.
· High Quality Conferencing: Default = On. Release 8.0+
Supports the use of the G.722 codec 589 . IP lines and extensions using G.722 are provided with wide band audio. If
High Quality Conferencing is enabled, when several wide band audio devices are in the same conference, the
system will ensure that the audio between them remains wide band, even if the conference also contains other lines
and devices using narrow band audio (analog devices, digital devices and IP devices using codecs other than G.722).
· Strict SIPS: (Enterprise Branch deployments) Default = Off.
This option provides a system-wide configuration for call restrictions based on SIPS URI.
· When this option is off (unchecked), calls are not rejected due to SIPS. A call is sent according to the configuration
of the outgoing trunk or line that it is routed to, regardless of the way the call came in, even if the call came in as
a SIP invite with SIPS URI and is being sent with a SIP URI onto a non-secure SIP trunk.
· When this option is on (checked), an incoming SIP invite with SIPS URI if targeted to a SIP trunk (SM line or SIP
line) is rejected if the target trunk is not configured with SIPS in the URI Type field.
· Digital/Analogue Auto Create User: Default = On.
Description required.
Release 9.0
IP Office Manager
Page 221
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.3.6.2 Park and Page
The Park and Page tab allows for simple configuration of the of the short code and the programmable button for the park
and page function.
Usability
· Mergeable:
These settings are mergeable. Changes to these settings do not require a reboot of the system.
Configuration Settings
· Central Park Range: Default = Blank. Range = nX to nnnnnnnXX
The park slot ID range definition, where n is a digit sequence from 1 to 9999999 and X represents a park slot value
from 0 to 99. The Central Park Range cannot exceed 9 characters total length.
Examples:
· 1X defines range 10-19
· 3XX defines range 300-399
· 9876543XX defines range 987654300-987654399
· Page Target Group List: Default = Blank.
The list of paging group targets that are presented on supported phones if the Page action is requested after the Call
Park.
On some phones, only the first three groups can be presented as Page options (via the Softkeys on the phone). On
phones that support scrolling lists, a larger list of possible Page targets can be presented.
Release 9.0
IP Office Manager
Page 222
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: System
10.3.6.3 Tones and Music
This page is used to configure the various tones and music on hold sources used by the system.
Usability
· Changes to Busy Tone Detection requires a reboot.
· For Hold Music, changes to the System Source requires a reboot. Deleting any of the hold music Alternate
Sources also requires a reboot.
Configuration Settings
· 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.
Note that no conference tones are played in an a conference initiated by an Outbound Contact Express agent.
· Disconnect Tone: Default = Default (Use locale setting 1000 ).
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 998 . 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.
· The following settings are shown for locales other than Customize. For the Customize locale they are set through
the System | System 201 form.
· Tone Plan: Default = Tone Plan 1
The tone plan control tones and ringing patterns. The options are:
· Tone Plan 1: United States
1052
· Tone Plan 2: United Kingdom
· Tone Plan 3: France
1017
· Tone Plan 4: Germany
· Tone Plan 5: Spain
1045
.
1051
.
.
1020
.
.
· Busy Tone Detection: Default = Off.
Enables or disables the use of busy tone detection for call clearing. This is a system wide setting.
· CLI Type:
This field is used to set the CLI detection used for incoming analogue trunks. The options are DTMF, FSK V23 and
FSK BELL202.
· 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
This setting controls whether call parties hear a repeating tone when their call is monitored by another party using the
Call Listen 723 feature.
·
! WARNING
The use of features to listen to a call without the other call parties being aware of that monitoring may be subject
to local laws and regulations. Before enabling the feature you must ensure that you have complied with all
applicable local laws and regulations. Failure to do so may result in severe penalties.
· GSM Silence Suppression: Default = Off. .
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.
Release 9.0
IP Office Manager
Page 223
15-601011 Issue 9.01 (Monday, September 09, 2013)
· Busy Tone Detection: Default = System Frequency (Tone defined by system locale)
Allows configuration of the system's busy tone detection settings on lines that do not provide reliable disconnect
signalling. In that case, the system will use 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 998 .
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. .For Server Edition this field is only
available on Expansion System (V2) systems. .
· 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 545 .
Server Edition deployments support centralized music on hold, where the Primary Server streams music to the
Secondary Server and all expansion servers.
· System Source: Default = WAV File.
Selects the default hold music source for most uses of music on hold.
Note that changes to the System Source requires a reboot.
Variable
Description
WAV
Use the WAV file HoldMusic.wav. This file is loaded via TFTP.
Note that on Linux systems, the file name is case sensitive.
WAV (restart) Identical to WAV except that for each new listener, the file plays from the beginning.
Not supported on IP500 V2 systems. Cannot be used as a centralized source.
External
Use the audio source connected to the back of the control unit.
Use the first available USB audio source.
Not applicable to Server Edition IP500 V2 expansion systems.
Tone
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. The hold music tone is automatically used if the system source is set to WAV
File but the holdmusic.wav file has not yet been successfully downloaded.
· Alternate Sources:
Up to three additional hold music source can be specified. 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.
Variable
Description
WAV:
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.
XTN:
Any analog extension with its Equipment Classification 339 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.
WAVDIR:
Multiple WAV file source. The WAV files must be stored in the /opt/ipoffice/tones/mohwavdir/
directory. The directory can contain up to 255 files and each file can be up to 10 minutes in
length.
Not applicable to Server Edition IP500 V2 expansion systems.
USB:
Supports multiple USB inputs. Enter USB:<number>.
USB:1 is the first source found and is treated as External when the System Source is set
to External. Additional devices are numbered sequentially. For example USB:2, USB:3.
LINE:
In Server Edition networks, setting the Secondary Server and Expansion Server Alternate
Source to Line allows the server to receive streamed audio from a source on the Primary
Server. On the Secondary Server and Expansion Server, enter Line:x,y where x is the line
number to the Primary Server and y is the MOH source number on the Primary Server.
Release 9.0
IP Office Manager
Page 224
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: System
10.3.6.4 Ring Tones
This page is used to configure ring tones. You can configure distinct ring tones for different hunt groups and for internal
calls.
Ring Tone configuration is only supported on 1400 series and 9500 series phones.
Usability
· Mergeable:
These settings are mergeable. Changes to these settings do not require a reboot of the system.
Configuration Settings
· Available Ring Tones
In this table, the Number, Name, and Source values are system supplied. The Name value is used to create a ring
tone plan.
· Ring Tone Plan
Use this table to specify available ring tones. Ring tones in this table can be applied to hunt groups and incoming call
routes.
· Number
System supplied.
· Name
A descriptive name for where this ring tone is used. For example, the name of a hunt group. Each name in the table
must be unique. Once configured in this table, ring tone names can be selected from the Ring Tone Override field
on the Hunt Group | Hunt Group tab and on the Incoming Call Route | Standard tab.
· Ring Tone
The list of ring tone names from the Available Ring Tones table.
Release 9.0
IP Office Manager
Page 225
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.3.6.5 SM
This page is used to configure settings that apply to both SM lines.
Usability
· Mergeable:
These settings are mergeable. Changes to these settings do not require a reboot of the system.
Configuration Settings
· Short Form Dialing Length: Default = 0. Ranage = 0 to 14.
This number specifies the short-form dialing length for all Centralized users and Groups. Configuration of this field
allows IP Office to treat the last N digits (where N is the number entered in this field) of each Centralized user’s
extension number as an alias to that user’s extension number. For example, if a Centralized user’s extension number is
5381111 and the Short Form Dialing Length is 4, the system will match calls to 1111 with this extension. When 1111 is
dialed by another user on the system, entered from the autoattendant, or comes from the ICR, then in sunny-day that
call will be sent to Session Manager with the number converted to 5381111 and in rainy-day it will target the extension
5381111 locally.
· Branch Prefix: Default = Blank. Maximum range = 15 digits.
This number is used to identify the IP Office system within the Avaya Aura® network. The branch prefix of each IP
Office system must be unique and must not overlap. For example 85, 861 and 862 are okay, but 86 and 861 overlap.
On calls routed via an SM Line, the branch prefix is added to the caller's extension number. You have the option to
leave the Branch Prefix field blank. If you do not configure the branch prefix, the IP Officeuser extensions must be
defined with the full enterprise number.
· Local Number Length: Default = Blank (Off). Range = Blank (Off) or 3 to 9.
This field sets the default length for extension numbers for extensions, users, andhunt groups added to the IP Office
configuration. Entry of an extension number of a different length will cause an error warning by Manager.
The number entered in the Branch Prefix field plus the number entered in the Local Number Length field must not
exceed 15 digits. You have the option to leave the Local Number Length field blank.
· Proactive Monitoring: Default = 60 seconds. Range = 60 seconds to 100000 seconds.
The Enterprise Branch system sends regular SIP OPTIONS messages to the SM line in order to check the status of line.
This setting controls the frequency of the messages when the SM line is currently in service. Centralized SIP phones
use their own settings.
· Monitoring Retries: Default = 1. Range = 0 to 5.
The number of times the Enterprise Branch system retrys sending an OPTIONS request to Session Manager before the
SM Line is marked out-of-service.
· Reactive Monitoring: Default 60 seconds. Range = 10 to 3600 seconds.
The Enterprise Branch system sends regular SIP OPTIONS messages to the SM line in order to check the status of line.
This setting controls the frequency of the messages when the SM line is currently out of service. Centralized SIP
phones use their own settings.
· Failback Policy: Default = Auto.
This field allows the administrator to choose between an automatic or manual failback policy on the IP Office. In
deployments with Centralized phones, this field must be set consistently with the Failback Policy of the phones, which
is configured via the Session Manager global settings in System Manager.
· Auto: IP Office automatically brings the SM Line to ‘In Service’ status as soon as it detects via the Reactive
Monitoring that the Session Manager is reachable
· Manual: When an SM line is in "Out of Service" state, IP Office does not bring it back to "In Service" status based
on automatic detection. IP Office keeps the SM Line in "Out of Service" state until the administrator manually
initiates Failback of IP Office from Session Manager.
· .
· Media Security: Default = Disable.
Secure RTP (SRTP) can be used between IP devices to add additional security. These setting control whether SRTP is
used for this device and the setting used for the SRTP. For further details of SRTP refer to Secure VoIP (SRTP) 593 .
These settings apply only to centralized phones.
· Disable – Media security is not required. All media sessions (audio, video, and data) will be enforced to use
RTP only.
· Enforce – Media security is required. All media sessions (audio, video, and data) will be enforced to use SRTP
only.
· Best Effort – Media security is preferred. Attempt to use secure media first and if unsuccessful, fall back to
non-secure media.
· Media Security Options
Not displayed if Media Security is disabled
Release 9.0
IP Office Manager
Page 226
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: System
· Encryptions: Default = RTP
This setting allows selection of which parts of a media session should be protected using encryption. The
default is to encrypt just the RTP stream (the speech).
· Authentication: Default = RTP and RTCP
This setting allows selection of which parts of the media session should be protected using authentication. The
default is authenticate just the RTCP stream (call control signals).
· Replay Protection SRTP Window Size: Default = 64.
Currently not adjustable.
· Crypto Suites: Default = SRTP_AES_CM_128_SHA1_80 and SRTP_AES_CM_128_SHA1_32.
Release 9.0
IP Office Manager
Page 227
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.3.6.6 Call Log
The system can store a centralized call log 522 for users. Each users' centralized call log can contain up to 30 call records
for user calls. When this limit is reached, each new call records replaces the oldest previous record.
On Avaya phones with a fixed Call Log or History button (1400, 1600, 9500 and 9600 Series), that button can be used
to display the user's centralized call log. The centralized call log is also used for M-Series and T-Series phone. 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 used if the user logs into one-X Portal for IP Office.
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 network.
Usability
· Mergeable:
These settings are mergeable. Changes to these settings do not require a reboot of the system.
Configuration Settings
· 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 is accessible on the
phone when the user is using a phone with a Call Log or History button. The use of centralized call logging can be
enabled/disabled on a per user basis using the Centralized Call Log 367 user setting (User | Telephony | Call Log 367
).
· Log 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 950 buttons or
coverage group 525 ), 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 367 ), the list of hunt groups allows selection of which
hunt groups' missed call records should be displayed as part of the user's centralized call log.
Release 9.0
IP Office Manager
Page 228
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: System
10.3.6.7 TUI
This page is used to configure system wide telephony user interface (TUI) options.
Usability
· Mergeable:
These settings are mergeable.
Configuration Settings
· Default Phone Display Options
Use these settings to define the default phone display when feature menus are disabled. Note that for new users, the
default phone display options are set to the system default values.
Feature menus can be disabled in one of two ways.
· On System | Telephony | TUI, set the Features Menu to off.
On User | Telephony | TUI, set the User Setting to Same as System.
· On User | Telephony | TUI, set the User Setting to Custom and set the Features Menu to off.
Phone Type
· 1400
Variable
Display Name Preference
· 1600
Description
Defines the default value of the User’s Features > Phone User >
Phone Screen Settings > Display Name setting.
Default = Off
When enabled, displays the user name.
· 9500
Column View Preference
· 9608
Defines the default value of the User’s Features > Phone User >
Phone Screen Settings > Display Mode setting.
Default = Dual
· 9611
Column view can be Single or Dual.
· 9621
Quick Touch Panel Lines
· 9641
Defines the default value of the User’s Features > Phone User >
Phone Screen Settings > Quick Touch Lines setting.
Default = Optimize
Sets the Quick Touch Panel number. The options are 1, 2, and
Optimize. When set to Optimize:
· 9621 = 1
· 9641 = 2
· Time Format: Default = Locale Defined.
Set the system time format display. The default time format is defined by the Locale setting. You can override the
default and set the time format to a 12- hour or 24-hour clock.
· Features Menu Controls
· Features Menu: Default = On
When set to off, TUI feature menus are not available.
When set to on, you can select to turn individual feature menus off or on. The following feature menus are listed:
· Basic Call Functions (Transfer to Mobile, Pickup, Park)
· Advanced Call Functions (Do Not Disturb, DNS Exceptions, Account Code)
· Forwarding
· Hot Desk Functions
· Passcode Change
· Phone Lock
· Self Administration
· Voicemail Controls
For information on telephony features, see the IP Office Product Description.
Release 9.0
IP Office Manager
Page 229
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.3.7 Directory Services
Directory services can be used to import directory records (names and numbers) from external sources. These sets of
records are regularly re-imported. For systems, the directory records can come from the following sources:
· LDAP Import 234
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 234 form. The LDAP used is LDAP
Version 2.
· HTTP Import 237
Systems are able to import the directory records from another system using HTTP. HTTP import is configured
through the System | Directory Services | HTTP 237 form by specifying an IP address or multi-site network
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 records, HTTP imported records, configuration records.
· System Directory Records 450 (Configuration records)
Up to 2500 records can be entered directly into the system configuration through the Directory
directory records override matching LDAP/HTTP imported records.
450
menu. System
· Phones with a CONTACTS button and System Phone Rights 547 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
records.
System
Number of Directory Records
Configuration
LDAP Import
HTTP Import
Total Number of
Directory
Records
5000
5000
Standalone
Systems
IP500/IP500 V2
2500
5000
Server
Edition
Primary Server
2500
5000
–
5000
Secondary Server
–
–
5000
5000
Expansion System (L)
–
–
5000
5000
Expansion System (V2)
–
–
5000
5000
Server Edition Directory Operation
In a Server Edition network, all system directory records are entered into the configuration of the Primary Server. Any
LDAP importation is also done by the Primary Server. All other systems are configured by default to import the central
directory from the Primary Server.
Release 9.0
IP Office Manager
Page 230
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: System
Use of Directory Records
Directory records are used for two types of function:
· Directory Dialing
Directory numbers are displayed by user applications such as SoftConsole. Directory numbers are viewable
through the Dir 865 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 records 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 records from the system configuration. This includes HTTP and LDAP imported records.
· Groups
Groups on the system. If the system is in a multi-site network, it will also include groups on other
systems in the network. For pre-Release 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 multi-site network it will also include users on other systems in
the network. For pre-Release 5 systems, this feature requires the systems to have Advanced Small
Community Networking licenses.
· Personal
Available on T3, T3 IP, 1400, 1600, 9500 and 9600 Series phones. These are the user's personal
directory records stored within the system configuration.
· Speed Dialing
On M-Series and T-Series phones, a Speed Dial 916 button or dialing Feature 0 can be used to access
personal directory records with an index number.
· Personal: Dial Feature 0 followed by * and the 2-digit index number in the range 01 to 99.
· System: Dial Feature 0 followed by 3-digit index number in the range 001 to 999.
·
The Speed Dial 916 short code feature can also be used to access a directory speed dial using its index
number from any type of phone.
· Caller Name Matching
Directory records 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 user's personal directory overrides any
match in the system directory. Note that some user applications also have their own user directory.
· 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.
Release 8.0+: On SIP trunks the use of the name matching or the name supplied by the trunk can be selected
using the Default Name Priority setting (System | Telephony | Telephony 219 ). This setting can also be
adjusted on individual SIP lines to override the system setting.
· Directory name matching is not supported for DECT handsets.
Release 9.0
IP Office Manager
Page 231
15-601011 Issue 9.01 (Monday, September 09, 2013)
Directory Special Characters
The following characters are supported in directory records. They are supported in both system configuration records and
in imported records.
· ? = Any Digit
Directory records 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. Records 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 record to be used for both incoming and
outgoing calls.
· Name: Raj Garden
· Number: 9(01707)373386
· Space and - Characters
Directory records can also contain spaces and - characters. These will be ignored during name matching and
dialing from the directory.
Release 9.0
IP Office Manager
Page 232
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: System
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
547
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
Number of Directory Records
Configuration
LDAP Import
HTTP Import
Total Number of
Directory
Records
5000
5000
Standalone
Systems
IP500/IP500 V2
2500
5000
Server
Edition
Primary Server
2500
5000
–
5000
Secondary Server
–
–
5000
5000
Expansion System (L)
–
–
5000
5000
Expansion System (V2)
–
–
5000
5000
Release 9.0
IP Office Manager
Page 233
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.3.7.1 LDAP
The system supports LDAP Version 2. 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.
· 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 237 , 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 record when
imported into the system directory.
· The NoUser source number setting ExtendLDAPDirectLimit usable with Release 4.1-4.2 systems is no longer
supported for Release 5.0+.
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.
Release 9.0
IP Office Manager
Page 234
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: System
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
Configuration Settings
· LDAP Enabled: Default = Off
This option turns LDAP support on or off. The system uses LDAP Version 2. If the server being queried is an LDAP
Version 3 server, support for LDAP Version 2 requests may need to be enabled on that server (all LDAP Version 3
servers support LDAP Version 2 but do not necessarily have it enabled by default).
· 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
record. 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".
Once this has been done on the server, any record 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 records. 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=*))
Release 9.0
IP Office Manager
Page 235
15-601011 Issue 9.01 (Monday, September 09, 2013)
· Number Attributes: Default = see below
Enter the number attributes the server should return for each record that matches the Search Base and Search Filter.
Other records 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 record 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
Release 9.0
IP Office Manager
Page 236
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: System
10.3.7.2 HTTP
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 201 setting (System | System 201 ) can restrict a system from responding to
HTTP requests. The system's Unsecured Interface 183 security settings also included controls for HTTP access (HTTP
Directory Read and HTTP Directory Write).
Usability
· Mergeable:
These settings are mergeable. Changes to these settings do not require a reboot of the system.
Configuration Settings
For Server Edition, on Secondary Server, Expansion System (L) and Expansion System (V2) systems, the HTTP settings
are automatically defaulted to obtain the system directory from the Primary Server.
· Directory Type: Default = None (No HTTP import)/IP Office SCN on Server Edition.
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 multi-site network. The Source field is used to select the Outgoing Line ID that
matches the H.323 line to the remote system.
· Source: Default = Blank/9999 on Server Edition.
The form of this field changes according to the Directory Type selection above. For IP Office this field requires the IP
address of the other system. For IP Office SCN, the outgoing group ID of the line to the remote system is used.
· 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.
Release 9.0
IP Office Manager
Page 237
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.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.
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 MIB files provided with the Manager
installation software must be compiled into the SNMP server's applications database.
·
! WARNING
The process of 'on-boarding' (refer to the IP Office Installation manual and the IP Office SSL VPN Solutions
Guide) may automatically configure SNMP and create a number of SNMP alarm traps. These will override any
existing SNMP configuration settings.
· SMTP Email Reporting.
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 244 tab.
· Syslog Reporting.
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.
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.
Release 9.0
IP Office Manager
Page 238
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: System
10.3.8.1 Configuration
This form is used for general configuration related to system alarms. For email alarms the SMTP
244
tab is also used.
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
Configuration Settings
· 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.
If an SSL VPN is configured, Avaya recommends that the Device ID match an SSL VPN service Account Name.
Each SSL VPN service account name has an associated SSL VPN tunnel IP address. Having the displayed Device ID
match an SSL VPN service account name helps identify a particular SSL VPN tunnel IP address to use for remotely
managing IP Office.
· 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:
These parameters are used if Enable RTCP Monitor on Port 5005 is selected (Systems | Lan1 | VoIP). They are
used as alarm thresholds for the QoS data collected by the system for calls made by Avaya H.323 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 240 .
· 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: G.711 = 40ms, G.723a = 160ms, G.729 = 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
Release 9.0
IP Office Manager
Page 239
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.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 239 tab. 5 for Server Edition systems.
· 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.
244
settings. The email
· Up to 2 alarms can be configured for sending to a Syslog destination that is included in the alarm settings.
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
Configuration Settings
· New Alarm
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. For Server Edition, 5 SNMP alarms can be configured.
· 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.
· Format: Default = IP Office.
· Syslog:
When selected, you have the option of selecting System Monitor in the Events field. Only select System
Monitor for centralized System Monitor syslog alarms in a Server Edition deployment.
When Syslog is 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.
· Protocol: Default = UDP.
Select UDP or TCP.
· Format: Default = IP Office.
· Email:
If selected, the details required in addition to the selected Events are:
· Email:
The destination email address.
· Minimum Severity Level: Default = Warnings.
The possible values are:
· Warnings
All events, from Warnings to Critical, are sent.
· Minor
Minor, major, and critical events are sent. Warnings are not sent.
· Major
Major and critical events are sent. Warnings and minor events will not be sent.
· Critical
Only critical events are sent.
Release 9.0
IP Office Manager
Page 240
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: System
The SYSLOG destination will send all alarms, regardless of the severity level.
· 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.
Feature license missing
Attempt to use a feature for which no
license is installed. License Type:
<name>.
All licenses in use
The following licenses are all in use.
License Type: <name>.
Clock source changed
8kHz clock source changed. Details will
be provided.
Logon failed
Logon failure reason will be provided.
No free channels available
No free channels were available.
Outgoing group ID: <number>.
Hold music file failure
Failed to load Hold Music source file.
All resources in use
The following system resources are all
in use: <resource type> will be
provided.
OEM card slot error
System running secondary software or
error description with OEM card will be
provided.
Network interconnect failure
Details of the network interconnection
failure will be
provided.
SIP message too large
SIP message Rx error - too large ignored.
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.
Trunk seize failure
Seize failure: Channel [number] or Port
[number].
Incoming call outgoing trunk
failure
Incoming call outgoing trunk: Channel
[number] or Port [number].
CLI not delivered
CLI not delivered: Channel [number] or
Port [number].
DDI incomplete
DDI incomplete. Expected Number of
digits: <number>.
LOS
LOS
OOS
OOS
Red Alarm
Red Alarm
Blue Alarm
Blue Alarm
Yellow Alarm
Yellow Alarm
Service
Trunk
Trunk
Release 9.0
IP Office Manager
Page 241
15-601011 Issue 9.01 (Monday, September 09, 2013)
Type
Events
Link
VCM
Memory Card
Event State
Message
IP connection failure
IP connection failure. IP Trunk Line
Number: <number> or Remote end IP
address: <IP address>.
Small Community Network
invalid connection
Small Community Network invalid
connection. IP trunk line number:
<number> or remote end IP address:
<IP address>.
Device changed
Device changed. Home Extension
Number: <number>.
LDAP server communication
failure
LDAP server communication failure
Resource down
Link/resource down. Module type,
number and name
will be provided.
SMTP server communication
failure
SMTP server communication failure
Voicemail Pro connection
failure
Voicemail Pro connection failure
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.
Invalid Card
Free Capacity
Generic
License
Loopback
Phone Change
Generic
License Server
License Key Failure
License 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
If Enable RTCP Monitor on Port 5005 is selected, any monitored
calls that exceeds the set QoS Parameters 239 will cause an alarm.
Syslog
Basic Audit
Events as written to the system Audit Trail. Available on Syslog output
only.
System
Configuration
CCR group agent not targeted CCR Group agent not targeted as it is
not an CCR Agent. Group : <name>
Agents: <name1, ..., name n>.
Small Community Network dial Small Community Network dial plan
plan conflict
conflict
Release 9.0
IP Office Manager
Page 242
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: System
Type
Events
Event State
Message
No incoming call route for call The following line had no Incoming Call
Route for a call. Line: <number> or
Line Group ID: <number>.
Installed hardware failure
Installed hardware failure details will be
provided.
Emergency call successful
Successful Emergency Call | Emergency
call! Location:location Dialled:dialled
number Called:number sent on the line
CallerID:ID Usr:user Extn:extension
Emergency call failure
Failed Emergency Call | Emergency call!
Location:location Dialled:dialled number
FailCause:cause Usr:user Extn:
extension
System Shutdown
Running Backup
Emergency Calls
· 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 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.
Release 9.0
IP Office Manager
Page 243
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.3.9 SMTP
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 240 .
SMTP can be used with Embedded Voicemail for Voicemail Email
Voicemail Email 354 address.
354 .
The voicemail destination is set by the user's
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
Configuration Settings
· IP Address: Default = 0.0.0.0
The IP address or fully qualified domain name (FQDN) 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.
Release 9.0
IP Office Manager
Page 244
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: System
10.3.10 SMDR
Using a specified IP address, the system can send a call record for each completed call.
Usability
· Mergeable:
These settings are mergeable. Changes to these settings do not require a reboot of the system.
The Outbound Contact Express does not generate SMDR records.
Configuration Settings
· Output: Default = No Output.
Select the type of call record that the system should output via IP.
· No Output
· SMDR Only:
Send call records using the SMDR settings below.
SMDR Configuration Settings
These settings are shown if SMDR Only is selected as the Output. For further details refer to Appendix: SMDR
1055
.
· 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.
· 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 1055 .
Release 9.0
IP Office Manager
Page 245
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.3.11 Twinning
These settings are used with Mobile Twinning, see the User | Mobility
377
tab for further details.
· 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.
Usability
· Mergeable:
These settings are mergeable. Changes to these settings do not require a reboot of the system.
Configuration Settings
· Send Original Party Information for Mobile Twinning: Default = Off
When on, the system will attempt to send the ICLID information provided with the incoming call to the twinning
destination.
· The SIP line Send Caller ID setting takes priority.
· The values on the System | Twinning
246
tab override the SIP lines Send Caller ID setting.
· Calling Party Information for Mobile Twinning: Default = Blank (Disabled). Range = Up to 32 digits.
This field is usable 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.
Release 9.0
IP Office Manager
Page 246
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: System
10.3.12 VCM
This form allows adjustment of the operation of any Voice Compression Modules (VCM's) installed in a control unit.
· The options for IP400 VCM controls are supported on IP400 systems from the Release 3.2/4.0 Q2 2007
Maintenance Releases onwards.
· The same controls are supported for IP400 VCM cards in IP500 systems from Release 4.1 Q1 2008
Maintenance Release onwards.
· The options for IP500 VCM controls are supported from Release 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 G.711, G.723 and
G.729a. For details of how to add voice compression resources to a system, refer to the IP Office 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 G.723 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.
· 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 and silent monitoring. They also apply to call recording.
· 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 G.729a for page calls, therefore only requiring one channel but also only supporting pages to G.729a
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.
· 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
The system supports T38 fax on SIP trunks and SIP extensions. Each T38 fax call uses a VCM channel.
Release 9.0
IP Office Manager
Page 247
15-601011 Issue 9.01 (Monday, September 09, 2013)
· Within a multi-site network, an T38 fax call can be converted to a call across across an H.323 line between
systems 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, the 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.
Release 9.0
IP Office Manager
Page 248
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: System
Measuring Channel Usability
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.
These settings should only be adjusted under the guidance of Avaya support.
Usability
· Mergeable:
These settings are mergeable. Changes to these settings do not require a reboot of the system.
Configuration Settings
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 VCM, IP500 VCM, IP500 VCM V2 and IP500 Combination Cards.
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 VCM, IP500 VCM, IP500 VCM V2 and IP500 Combination
Cards.
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, IP500 VCM V2 and IP500 Combination Cards.
Options are -3dB, -6dB and -9dB.
· NLP Comfort Noise Ceiling: Default =-30dB. IP500 VCM, IP500 VCM V2 and IP500 Combination Cards.
Options are -30dB and -55dB.
Modem
For Fax relay, these settings allow adjustment of the TDM side operation applied to fax calls using VCM channels.
IP500 VCM, IP500 VCM V2 and IP500 Combination Cards.
· 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.
Release 9.0
IP Office Manager
Page 249
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.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. IP Office Customer Call Reporter is not
currently supported by Server Edition.
Usability
· Mergeable:
These settings are mergeable. Changes to these settings do not require a reboot of the system.
Configuration Settings
· 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 363 ). During ACW state, hunt group calls are not presented to
the user.
Release 9.0
IP Office Manager
Page 250
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: System
10.3.14 Codecs
This tab is used to set the codecs available for use with all IP (H.323 and SIP) lines and extensions and the default order
of codec preference.
· Avaya H.323 telephones do not support G.723 and will ignore it if selected.
· For systems with H.323 lines and extensions, one of the G.711 codecs must be selected and used.
· G.723 is not supported by Linux based systems.
· The number of channels provided by an IP500 VCM 32 or IP500 VCM 64 card, up to a maximum of 32 or 64
respectively, depends on the actual codecs being used. This also applies to IP500 VCM 32 V2 and IP500 VCM 64
V2 cards. The following table assumes that all calls using the VCM use the same codec.
Codec
IP500 VCM 32
IP500 VCM 32 V2
IP500 VCM 64
IP500 VCM 64 V2
G.711
32
64
G.729a
30
60
G.723
22
44
G.722
30
60
When paging, always use only one codec (the preferred). It is the system administrator's responsibility to ensure all the
phones in the paging group support the codec.
Usability
· Mergeable:
These settings are mergeable. Changes to these settings do not require a reboot of the system.
Configuration Settings
· Available Codecs
This list shows the codecs supported by the system and those selected as usable. Those codecs selected in this list
are then available for use in other codec lists shown in the configuration settings. For example the adjacent
Default Selection list and the individual custom selection list on IP lines and extensions.
·
! WARNING:
Removing a codec from this list automatically removes it from the codec lists of any individual lines and
extensions that are using it.
· The available codecs in default preference order are: G.711 A-Law, G.711 U-Law, G.729 and G.723.1.
Note that the default order for G.711 codecs will vary to match the system's default companding setting.
G.723.1 is not supported on Linux based systems.
· The G.722 64K codec is also supported on IP500/IP500 V2 systems with IP500 VCM, IP500 VCM V2 or IP500
Combo cards. For Server Edition it is supported on Primary Server, Secondary Serverand Expansion System
(L) systems and on Expansion System (V2) systems fitted with IP500 VCM, IP500 VCM V2 or IP500 Combo. It
is not supported on any systems that include any IP400 VCM cards.
Default Codec Selection
By default, all IP (H.323 and SIP) lines and extensions added to the system have their Codec Selection setting set to
System Default. That setting matches the codec selections made in this list. The buttons between the two lists can be
used to move codecs between the Unused and the Selected parts of the list and to change the order of the codecs in
the selected codecs list.
Release 9.0
IP Office Manager
Page 251
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.3.15 Dialer
Use this tab to configure the functions required for an Outbound Contact Express deployment.
Usability
· Mergeable:
These settings are mergeable. However, changes to the Operation field or to the Trunk Range /
IP Office table require a reboot.
It is recommended that you do not change the mergeable settings while the system is in use.
Configuration Settings
· Operation: Default = Off
On the primary IP Office Server Edition server, set this field to Primary. For all other IP Office servers, set this
field to Child.
When set to Off or Child, no other fields are displayed.
· Record Mode: Default = Off
Defines the automatic call recording function on VMPro. When set to Whole Call, the entire call is recorded. When
set to Agent Connected, recording starts once the conversation begins.
· Record Controls: Default = Full
Defines what functions an agent can perform from WebAgent or from the handset. The options are Full, Pause,
or Off.
Record Mode and Record Controls are related. The combined configuration settings are listed below.
Record Mode
Record Controls Result
Off
Off
Calls are not recorded.
Agent Connected
Off
All calls are always recorded from the time the agent joins the call.
Agent Connected
Pause
All calls are always recorded but the Agent can pause and resume
recording.
Agent Connected
Full
All calls are always recorded from the time the Agent joins the call. Agent
has full control on when calls get recorded.
Whole Call
Off
All calls are always recorded from the time the customer answers.
Whole Call
Pause
All calls are always recorded from the time the customer answers but the
Agent can pause and resume the recording.
Whole Call
Full
Call recording starts before the agent is connected. All calls are always
recorded but the Agent can pause and resume the recording
· Agent Call Back Time: Default = 60. Range = 30 - 300.
The number of seconds an agent has to make a manual call after a customer hang up. Used when a customer
wants to be called on a different number.
· Remote Agent Display Text: Default = Blank. Maximum length = 33.
Specify the text string displayed on the remote agent extension if that extension supports displays and the
protocol allows it to be transmitted.
· Remote Agent Confirmation Voice Prompt: Default = Blank. Maximum length = 31.
Specify the Call Flow Entry point name used to play a greeting to the remote agent when they log in. The actual
Entry Point is added as a Modules Entry point using the VMPro Client. The entry point cannot be added as a short
code, user or group entry point.
· Remote Agent First Extension Number: Default = 0.
The first extension number allocated to a remote agent. It must not conflict with the existing dialing plan. If the
range contains existing user extensions, they are used when assigning extensions to remote users.
· Remote Agent Number of Extensions: Default = 0. Maximum = 500.
The range of extensions starting from the one above. A user is created for every extension.
If the field is edited and the number of extensions is reduced, the number of remote agents that can log in is
reduced to the new setting. However, reducing the range does not automatically delete previously created users.
Users can only be deleted manually.
· Use Custom Hold Treatment: Default = unchecked.
Defines system behavior when a call is placed on hold. When unchecked the the system Hold Music setting is
used for the system's music on hold source. When checked, the music on hold source is VMPro.
Release 9.0
IP Office Manager
Page 252
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: System
· Record while on Hold: Default = unchecked.
When the Use Custom Hold Treatment box is checked, the Record while on Hold setting can be enabled.
When unchecked, recording is paused when the call is on hold. When checked, recording continues when the call
is on hold.
· Trunk Range / IP Office:
The number of trunks used by Outbound Contact Express. The default entry is Trunk Range: 1-250 for the
Primary (Local) server. 250 is the maximum number of trunks configured on a single server. Use this table to
define the number of trunks managed by the Primary and Secondary systems.
The trunk range must match the line numbers used by the Proactive Contact Dialer. Enter only one range per
server.
Release 9.0
IP Office Manager
Page 253
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.4 Line
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 H.323)
· T1 Robbed Bit
· BRI So
· E1R2
· H.323
· ISDN BRI (excluding So)
· SCN
· ISDN PRI T1
· SES
· ISDN PRI E1
· SM Line
· SIP
Incoming Calls
Routed by
All incoming calls are routed by comparison
of call details for matches within the system
Incoming Call Routes 433 .
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.
· 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 433
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 417
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 card is installed but the trunk is not physically connected, it is important to ensure that the trunk
is disabled in the configuration.
· Pre-Release 6.1: This can be done by setting the trunk or trunk channels to Out of Service.
· Release 6.1+: This can be done on most trunks using by setting the line's Admin setting to Out of Service.
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.
Release 9.0
IP Office Manager
Page 254
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: Line
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.
Release 9.0
IP Office Manager
Page 255
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.4.1 Trunk Templates
The system supports the use of trunk templates. You can use SIP trunk templates to create new SIP trunks. You can use
analog trunk templates to update the settings of existing analogue trunks.
Avaya service providers can create templates from existing trunks. These templates are stored in a specific Manager subfolder \Templates.
· Tested SIP Trunk Templates
The SIP trunk services from selected SIP providers are tested as part of the Avaya DevConnect program. The
results of such testing are published as Avaya Application Notes available from the Avaya DevConnect web site (
https://devconnect.avaya.com).
Working with Templates
This following sections provide information about the following tasks:
· Enabling Template Support
· Importing Templates
256 .
256 .
· Creating a New SIP Trunk from a Template
· Applying a Template to an Analogue Trunk
256 .
257 .
SIP Template Parameters
SIP trunk templates can be used with IP Office systems running all IP Office Essential Edition/IP Office Preferred
Edition/IP Office Advanced Edition and IP Office Basic Edition - PARTNER® Mode modes. However, it is important to
understand that some trunk parameters used by IP Office Essential Edition/IP Office Preferred Edition/IP Office Advanced
Edition mode systems are not used by IP Office Basic Edition - Quick Mode/IP Office Basic Edition - Norstar Mode/IP
Office Basic Edition - PARTNER® Mode mode systems and vice versa.
For a summary of the differences see SIP Trunk Template Notes
259 .
10.4.1.1 Enabling Template Support
By default, template support is not enabled. To enable template support do the following:
1. Select File | Preferences.
2. Select the Visual Preferences tab.
3. Select the Enable Template Options checkbox.
4. Click OK.
10.4.1.2 Importing Templates
Having enabled template support 256 , before you can use templates from another source they must be placed in the
Manager applications \Templates directory. Use the following procedure to import a template from another source:
1. Select Tools | Import Templates in Manager.
2. Browse to the current folder containing the templates that you want to import and select that folder.
3. Click OK.
4. Any template files in the folder will be copied to the correct Manager sub-folder.
10.4.1.3 Creating a New SIP Trunk from a Template
A SIP trunk template can be used to create a new SIP trunk record in the system configuration.
1. In the navigation or group pane, right click on the any existing line.
2. Click the
New icon and select New SIP Trunk from Template.
3. The template selection menu is displayed.
4. Use the Country and Service Provider drop-downs to select the required template. If Display All is selected,
the Country selection changes to All Countries.
5. Click on Create New SIP Trunk.
Release 9.0
IP Office Manager
Page 256
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: Line
10.4.1.4 Applying a Template to an Analog Trunk
You can apply an analogue trunk template to existing analogue trunks.
· Note: This process will require the system to be rebooted for any changes to the trunk settings to be applied.
1. In the navigation or group pane, right click on the analogue trunk.
2. Select
Copy Setting from Template.
3. The template and trunk selection menu is displayed.
4. Use the Country and Service Provider drop-downs to select the required template. If Display All is selected,
the Country selection changes to All Countries.
5. Select the trunks to which you want the template to be applied.
6. Click on Copy Settings.
Release 9.0
IP Office Manager
Page 257
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.4.1.5 Exporting Trunk Templates
In addition to being used to import and apply templates, Manager can be used to export the setting of an existing trunk
as a template.
· Templates exported using Manager in Server Edition mode are saved by default on the Primary Server. This
means they are available to other administrators regardless of from which PC they are using Server Edition
Manager. This is different from Manager in non-Server Edition mode which exports templates to a local folder
on the PC on which Manager is being run.
Enabling Template Creation
Template creation is enabled by changing a registry key.
1. Using the Windows Registry Editor, change the value of TemplateProvisioning registry key (
HKEY_CUURRENT_USER | Software | Avaya | IP400 | Manager) to 1. Restart Manager.
Creating a Trunk Template
1. Select the trunk on which you want to base your template.
· SIP Trunk
In the navigation or group pane, right click on the SIP trunk and select
· Analog Trunk
In the navigation or group pane, right click on the analog trunk and select
Template.
Generate SIP Trunk Template.
Generate Analogue Trunk
2. The trunk settings are displayed. Adjust the trunk settings if required and then click on Export.
3. Select the line provider's country and enter a name.
4. Click on Generate Template.
5. Click on OK to save the template.
Release 9.0
IP Office Manager
Page 258
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: Line
10.4.1.6 SIP Trunk Template Notes
SIP trunk templates can be used with IP Office systems running all IP Office Essential Edition/IP Office Preferred
Edition/IP Office Advanced Edition and IP Office Basic Edition - PARTNER® Mode modes. However, it is important to
understand that some trunk parameters used by IP Office Essential Edition/IP Office Preferred Edition/IP Office Advanced
Edition mode systems are not used by IP Office Basic Edition - Quick Mode/IP Office Basic Edition - Norstar Mode/IP
Office Basic Edition - PARTNER® Mode mode systems and vice versa.
The configuration parameters available depend on the mode that you use. The table below lists the configuration
parameters available in each mode.
SIP Trunk Parameters
Standard Mode
Basic Edition
Descriptive Name
Yes
Yes
ITSP Domain Name
Yes
Yes
Prefix
—
—
National Prefix
—
—
Country Code
—
—
International Prefix
—
—
Send Caller ID
Yes
Yes
REFER Support
Yes
Yes
REFER Support Incoming
Yes
Yes
REFER Support Outgoing
Yes
Yes
In Service
—
—
Registration Required
Yes
—
Use Tel URI
Yes
Yes
Check OOS
Yes
—
Call Routing Method
Yes
—
Originator Number
Yes
—
Association Method
Yes
—
Name priority
Yes
Yes
ITSP Proxy
Yes
Yes
Layer Four Protocol
Yes
Yes
Send Port
Yes
Yes
Listen Port
Yes
Yes
DNS Server One
Yes
Yes
DNS Server Two
Yes
—
Calls Route Via Registrar
Yes
Yes
Separate Registrar
Yes
Yes
Compression Mode
Yes
Yes
Call Initiation Timeout
Yes
—
DTMF Support
Yes
Yes
Voip Silence Suppression
Yes
Yes
Reinvite Supported
Yes
Yes
Fax Transport Support
Yes
—
Codec Lockdown
Yes
Yes
Rel100 Supported
Yes
Yes
—
—
Yes
—
SIP Line
315
Transport
VoIP
320
324
SIP URI
322
Managed SIP Channel
T38 Fax
326
T38 Fax Version
Release 9.0
IP Office Manager
Page 259
15-601011 Issue 9.01 (Monday, September 09, 2013)
Transport
Yes
—
Low Speed
Yes
—
High Speed
Yes
—
TCF Method
Yes
—
Max Bit Rate
Yes
—
Eflag Start Timer
Yes
—
Eflag Stop Timer
Yes
—
Use Default Values
Yes
—
Scan Line Fixup
Yes
—
TFOP Enhancement
Yes
—
Disable T30ECM
Yes
—
Disable Eflags For First DIS
Yes
—
DisableT30MR Compression
Yes
—
NSF Override
Yes
—
User Name
—
—
Authentication Name
—
—
Contact
—
—
Password
—
—
Expiry
Yes
—
Registration Required
Yes
—
SIP Credentials
327
When you export a template, Manager displays a warning message if you have configured parameters that are not
supported in Basic mode. The warning message provides information about which parameters are not available.
Release 9.0
IP Office Manager
Page 260
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: Line
10.4.2 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 IP Office 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.
Release 9.0
IP Office Manager
Page 261
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.4.2.1 Line
This tab covers general settings for an analog line.
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
Configuration Settings
· Line Number
This parameter is not configurable, it is allocated by the system.
· Card/Module:
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 IP500 V2 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:
Indicates the port on the Card/Module above to which the configuration settings relate.
· Network Type: Default = Public.
This option is available if Restrict Network Interconnect 219 (System | Telephony | Telephony 219 ) 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: multi-site networks, VPNremote, application 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.
· For Basic Edition and Standard Edition deployments, the same ID can be used for multiple lines.
· In a Server Edition network, the Outgoing Group ID used on a system must also be unique within the network, ie.
the same ID cannot be used in the configuration of any lines on another server system in the network.
Reserved Group ID
numbers
Description
90000 - 99999
Reserved for system use (not enforced).
99999 and 99998
In a Server Edition network, reserved for the H.323 lines to the Primary Server and
Secondary Server respectively.
999901 to 99930
In a Server Edition network, reserved for the H.323 lines from the Primary Server to each
expansion system in the network.
0
In a Server Edition network, the ID 0 cannot be used.
98888
For IP Office deployed in an Enterprise Branch environment, reserved for the SM line.
· 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.
Release 9.0
IP Office Manager
Page 262
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: Line
· For outgoing calls: 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.
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.
This field allows a trunk to be taken out of service if required for maintenance or if the trunk is not connected.
Release 9.0
IP Office Manager
Page 263
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.4.2.2 Analog Options
This tab covers analog line specific settings. The system wide setting CLI Type (System | Telephony | Tones & Music
223 ) is used for to set the incoming CLI detection method for all analogue trunks.
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
Configuration Settings
· 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 IP Office 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.
· Echo Reduction: Default = On. (ATM4Uv2 card only)
Used when impedance matching is not required but echo reduction is. Options are On or Off.
· Mains Hum Filter: Default = Off.
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 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 (600ohms).
In addition to the default impedance settings, an alternate set of impedance values can be selected.
· United States: Default = Default (600 ohms).
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:
This field is only available for certain system locales (see above). The setting may be required to compensate for signal
loss on long lines.
· Digits to break dial tone: Default = 2. Range = Up to 3 digits.
During automatic impedance testing (see below), once the system has seized a line, it dials this digit or digits to the
line. In some cases it may be necessary to use a different digit or digits. For example, if analog trunk go via another
PBX system or Centrex, it will be necessary to use the external trunk dialing prefix of the remote system plus another
digit, for example 92.
Release 9.0
IP Office Manager
Page 264
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: Line
· Automatic: Default = Yes. (ATM4Uv2 card only)
When set to Yes, the Default value is used. The value used for Default is set by the system Locale.
When set to No, the Impedance value can be manually selected from the list of possible values:
600
900
270+(750R || 150nF) and 275R + (780R || 150nF)
220+(820R || 120nF) and 220R+ (82R || 115nF)
370+(620R || 310nF)
320+(1050R || 230nF)
370+(820R || 110nF)
275+(780R || 115nF)
120+(820R || 110nF)
350+(1000R || 210nF)
200+(680R || 100nF)
600+2.16µF
900+1µF
900+2.16µF
600+1µF
Global Impedance
· Automatic Balance Impedance Match:
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
system will 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.
Note that on the Analog Trunk Module (ATM16), there are four control devices, each supporting four channels. The
impedance is set by the control device for all four channels under its control. Consequently, the impedance match tool
only functions on lines 1, 5, 9, and 13.
· Before testing, ensure that the system Locale setting (System | System 201 ) is correctly set. Also check that the
system Companding Law settings (System | Telephony | Telephony 219 ) are set correctly. If either needs to be
changed, make the required change and save the setting to the system before proceeding with impedance
matching.
· Due to hardware differences, the impedance matching result will vary slightly depending on which type of trunk
card or expansion module is being used.
· Automatic Balance Impedance Matching, Quiet Line and Digits to break dial tone are available for the
Bahrain 1005 , Egypt 1015 , French Canadian 1009 , Kuwait 1028 , Morocco 1031 , Oman 1035 , Pakistan 1036 , Qatar 1040 , Saudi
Arabia 1042 , South Africa 1044 , Turkey 1049 , United Arab Emirates 1050 , United States 1052 and Customize 1013 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 call was
originally made or received on another analog trunk. This prevents transfers to trunks that do not support disconnect
clear.
· If the Unsupervised Analog Trunk Disconnect Handling setting (System | Telephony | Telephony 221 ) is
enabled, this setting is greyed out and trunk to trunk connections to any analog trunks are not allowed.
· 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.
Release 9.0
IP Office Manager
Page 265
15-601011 Issue 9.01 (Monday, September 09, 2013)
· IP500 ATM4 Uni Trunk Card Modem Support
It is not required to switch the card's modem port on/off. The trunk card's V32 modem function can be accessed
simply by routing a modem call to the RAS service's 431 extension number. The modem call does not have to use
the first analog trunk, instead the port remains available for voice calls.
· 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 tone, configured through the Busy Tone Detection 223 (System | Telephony | Tones & Music 223 )
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.
· If the Unsupervised Analog Trunk Disconnect Handling setting (System | Telephony | Telephony
enabled, this setting is greyed out and disconnect clear disabled..
221 )
is
· 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.
· A | D: Default = 0dB. Range =-10.0dB to +6.0dB in 0.5dB steps.
Sets the analog to digital gain applied to the signal received from the trunk by the system. 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. Range =-10.0dB to +6.0dB in 0.5dB steps.
Sets the digital to analog gain applied to the signal from the system to the trunk.
· Voice Recording: Default = Low
Used to adjust the volume level of calls recorded by voicemail. Options are Low, Medium and High.
Release 9.0
IP Office Manager
Page 266
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: Line
10.4.3 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 IP Office 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.
Release 9.0
IP Office Manager
Page 267
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.4.3.1 BRI Line
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
Configuration Settings
· Card/Module:
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 IP500 V2 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:
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:
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 IP Office Installation manual.
· Network Type: Default = Public.
This option is available if Restrict Network Interconnect 219 (System | Telephony | Telephony 219 ) 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: multi-site networks, VPNremote, application 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.
· For Basic Edition and Standard Edition deployments, the same ID can be used for multiple lines.
· In a Server Edition network, the Outgoing Group ID used on a system must also be unique within the network, ie.
the same ID cannot be used in the configuration of any lines on another server system in the network.
Reserved Group ID
numbers
Description
90000 - 99999
Reserved for system use (not enforced).
99999 and 99998
In a Server Edition network, reserved for the H.323 lines to the Primary Server and
Secondary Server respectively.
999901 to 99930
In a Server Edition network, reserved for the H.323 lines from the Primary Server to each
expansion system in the network.
0
In a Server Edition network, the ID 0 cannot be used.
98888
For IP Office deployed in an Enterprise Branch environment, reserved for the SM line.
· Prefix: Default = Blank.
The prefix is used in the following ways:
Release 9.0
IP Office Manager
Page 268
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: Line
· 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
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.
· 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 IP Office 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 IP Office
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*.
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.
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.
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.
· Send Redirecting Number: Default = Off.
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.
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 530 in the Telephone Features section for full details.
· Active CCBS Support: Default = Off.
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.
Release 9.0
IP Office Manager
Page 269
15-601011 Issue 9.01 (Monday, September 09, 2013)
· Passive CCBS: Default = Off.
· Cost Per Charging Unit:
Advice of charge (AOC) information can be display on T3/T3IP phones and output in SMDR 1055 . 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. 516
Release 9.0
IP Office Manager
Page 270
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: Line
10.4.3.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.
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
Configuration Settings
· Line Appearance ID: Default = Auto-assigned. Range = 2 to 9 digits.
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.
Release 9.0
IP Office Manager
Page 271
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.4.4 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.
For full details of installation refer to the IP Office Installation manual.
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 control unit supports 8 B-channels on each 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.
Release 9.0
IP Office Manager
Page 272
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: Line
10.4.4.1 PRI Line
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
Configuration Settings
· 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 trunks are not supported on IP500 and IP500 V2 systems without IP500 Voice Networking
licenses.
· Card/Module:
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 IP500 V2 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:
Indicates the port on the Card/Module above to which the configuration settings relate.
· Network Type: Default = Public.
This option is available if Restrict Network Interconnect 219 (System | Telephony | Telephony 219 ) 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: multi-site networks, VPNremote, application 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.
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.
· For Basic Edition and Standard Edition deployments, the same ID can be used for multiple lines.
· In a Server Edition network, the Outgoing Group ID used on a system must also be unique within the network, ie.
the same ID cannot be used in the configuration of any lines on another server system in the network.
Reserved Group ID
numbers
Description
90000 - 99999
Reserved for system use (not enforced).
99999 and 99998
In a Server Edition network, reserved for the H.323 lines to the Primary Server and
Secondary Server respectively.
999901 to 99930
In a Server Edition network, reserved for the H.323 lines from the Primary Server to each
expansion system in the network.
0
In a Server Edition network, the ID 0 cannot be used.
Release 9.0
IP Office Manager
Page 273
15-601011 Issue 9.01 (Monday, September 09, 2013)
98888
For IP Office deployed in an Enterprise Branch environment, reserved for the SM line.
· For lines set to the Line Sub Type of ETSI CHI, the Incoming Group ID is set as part of the individual channel
277 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
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 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 IP Office 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 IP Office
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*.
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.
Release 9.0
IP Office Manager
Page 274
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: Line
· Supports Partial Rerouting: Default = Off.
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.
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.
· Send Redirecting Number: Default = Off.
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.
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 530 in the Telephone Features section for full details.
· Active CCBS Support: Default = Off.
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.
· Cost Per Charging Unit:
Advice of charge (AOC) information can be display on T3/T3IP phones and output in SMDR 1055 . 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. 516
· Admin: Default = In Service.
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.
Release 9.0
IP Office Manager
Page 275
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.4.4.2 Short Codes
For some types of line, Line short codes can be applied to any digits received with incoming calls.
The line Short Code tab is shown for the following trunk types which are treated as internal or private trunks: QSIG (T1,
E1, H.323), BRI S0, H.323, SCN. Incoming calls on those types of trunk are not routed using Incoming Call Route
settings. Instead the digits received with incoming calls are checked for a match as follows:
· Extension number (including remote numbers in a multi-site network).
· Line short codes (excluding ? short code).
· System short codes (excluding ? short code).
· Line ? short code.
· System ? short code.
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.
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
Release 9.0
IP Office Manager
Page 276
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: Line
10.4.4.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.
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
Configuration Settings
· Line Appearance ID: Default = Auto-assigned. Range = 2 to 9 digits.
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.
· If the trunk Line Sub Type is set to ETSI CHI, outgoing line appearance calls must use the correspond channel.
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.
· For Basic Edition and Standard Edition deployments, the same ID can be used for multiple lines.
· In a Server Edition network, the Outgoing Group ID used on a system must also be unique within the network, ie.
the same ID cannot be used in the configuration of any lines on another server system in the network.
Reserved Group ID
numbers
Description
90000 - 99999
Reserved for system use (not enforced).
99999 and 99998
In a Server Edition network, reserved for the H.323 lines to the Primary Server and
Secondary Server respectively.
999901 to 99930
In a Server Edition network, reserved for the H.323 lines from the Primary Server to each
expansion system in the network.
0
In a Server Edition network, the ID 0 cannot be used.
98888
For IP Office deployed in an Enterprise Branch environment, reserved for the SM line.
· 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.
Release 9.0
IP Office Manager
Page 277
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.4.5 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.
For full details of installation refer to the IP Office Installation manual.
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 control unit supports 8 B-channels on each 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.
Release 9.0
IP Office Manager
Page 278
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: Line
10.4.5.1 E1-R2 Options (Line)
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
Configuration Settings
· Card/Module:
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 IP500 V2 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:
Indicates the port on the Card/Module above to which the configuration settings relate.
· Network Type: Default = Public.
This option is available if Restrict Network Interconnect 219 (System | Telephony | Telephony 219 ) 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: multi-site networks, VPNremote, application telecommuter mode.
· Line Number:
Allocated by the system.
· Line SubType: Default = E1-R2
Supported options are E1-R2, ETSI, QSIGA or QSIGB.
· QSIG trunks trunks are not supported on IP500 and IP500 V2 systems without IP500 Voice Networking
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.
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) 280 .
To edit a channel, either double-click on it or right-click and select Edit. This will display the Edit Channel 280 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.
Release 9.0
IP Office Manager
Page 279
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.4.5.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.
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
Configuration Settings
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.
· For Basic Edition and Standard Edition deployments, the same ID can be used for multiple lines.
· In a Server Edition network, the Outgoing Group ID used on a system must also be unique within the network, ie.
the same ID cannot be used in the configuration of any lines on another server system in the network.
Reserved Group ID
numbers
Description
90000 - 99999
Reserved for system use (not enforced).
99999 and 99998
In a Server Edition network, reserved for the H.323 lines to the Primary Server and
Secondary Server respectively.
999901 to 99930
In a Server Edition network, reserved for the H.323 lines from the Primary Server to each
expansion system in the network.
0
In a Server Edition network, the ID 0 cannot be used.
98888
For IP Office deployed in an Enterprise Branch environment, reserved for the SM line.
· 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.
Release 9.0
IP Office Manager
Page 280
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: Line
10.4.5.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.
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
10.4.5.4 Advanced
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
Configuration Settings
· Zero Suppression: Default = HDB3
Selects the method of zero suppression used (HDB3 or AMI).
· Clock Quality: Default = Network
Refer to the IP Office 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 IP Office
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.
Release 9.0
IP Office Manager
Page 281
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.4.6 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.
For full details of installation refer to the IP Office Installation manual.
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 control unit supports 8 B-channels on each 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.
Release 9.0
IP Office Manager
Page 282
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: Line
10.4.6.1 Line
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
Configuration Settings
· Line Number:
Allocated by the system.
· Card/Module:
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 IP500 V2 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:
Indicates the port on the Card/Module above to which the configuration settings relate.
· Network Type: Default = Public.
This option is available if Restrict Network Interconnect 219 (System | Telephony | Telephony 219 ) 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: multi-site networks, VPNremote, application telecommuter mode.
· Line Sub Type: Default = T1
Set to T1 for a T1 line. For PRI see Line Form (US PRI)
288 .
If set to ETSI, QSIG A or QSIG B see Line (E1)
273 .
· 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 IP Office 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 IP Office
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.
Release 9.0
IP Office Manager
Page 283
15-601011 Issue 9.01 (Monday, September 09, 2013)
· 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.
This field allows a trunk to be taken out of service if required for maintenance or if the trunk is not connected.
Release 9.0
IP Office Manager
Page 284
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: Line
10.4.6.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.
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
Configuration Settings
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.
· For Basic Edition and Standard Edition deployments, the same ID can be used for multiple lines.
· In a Server Edition network, the Outgoing Group ID used on a system must also be unique within the network, ie.
the same ID cannot be used in the configuration of any lines on another server system in the network.
Reserved Group ID
numbers
Description
90000 - 99999
Reserved for system use (not enforced).
99999 and 99998
In a Server Edition network, reserved for the H.323 lines to the Primary Server and
Secondary Server respectively.
999901 to 99930
In a Server Edition network, reserved for the H.323 lines from the Primary Server to each
expansion system in the network.
0
In a Server Edition network, the ID 0 cannot be used.
98888
For IP Office deployed in an Enterprise Branch environment, reserved for the SM line.
· Line Appearance ID: Default = Auto-assigned. Range = 2 to 9 digits. Release 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).
Release 9.0
IP Office Manager
Page 285
15-601011 Issue 9.01 (Monday, September 09, 2013)
· 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.
Release 9.0
IP Office Manager
Page 286
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: Line
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.
Release 9.0
IP Office Manager
Page 287
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.4.7 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.
For full details of installation refer to the IP Office Installation manual.
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 control unit supports 8 B-channels on each 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.
Release 9.0
IP Office Manager
Page 288
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: Line
10.4.7.1 Line
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
Configuration Settings
· Line Number:
Allocated by the system.
· Card/Module:
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 IP500 V2 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:
Indicates the port on the Card/Module above to which the configuration settings relate.
· Network Type: Default = Public.
This option is available if Restrict Network Interconnect 219 (System | Telephony | Telephony 219 ) 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: multi-site networks, VPNremote, application telecommuter mode.
· Line SubType: Default = PRI
Set to PRI. If set to T1 see Line Form (T1)
282 .
If set to ETSI, ETSI CHI, QSIG A or QSIG B see Line (E1)
273 .
· QSIG trunks trunks are not supported on IP500 and IP500 V2 systems without IP500 Voice Networking
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*.
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.
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:
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 704 can be used to specify the name to be used.
· Names Length:
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).
Release 9.0
IP Office Manager
Page 289
15-601011 Issue 9.01 (Monday, September 09, 2013)
· Clock Quality: Default = Network
Refer to the IP Office 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 IP Office
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.
This field allows a trunk to be taken out of service if required for maintenance or if the trunk is not connected.
Release 9.0
IP Office Manager
Page 290
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: Line
10.4.7.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.
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
Configuration 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.
· For Basic Edition and Standard Edition deployments, the same ID can be used for multiple lines.
· In a Server Edition network, the Outgoing Group ID used on a system must also be unique within the network, ie.
the same ID cannot be used in the configuration of any lines on another server system in the network.
Reserved Group ID
numbers
Description
90000 - 99999
Reserved for system use (not enforced).
99999 and 99998
In a Server Edition network, reserved for the H.323 lines to the Primary Server and
Secondary Server respectively.
999901 to 99930
In a Server Edition network, reserved for the H.323 lines from the Primary Server to each
expansion system in the network.
0
In a Server Edition network, the ID 0 cannot be used.
98888
For IP Office deployed in an Enterprise Branch environment, reserved for the SM line.
· Line Appearance ID: Default = Auto-assigned. Range = 2 to 9 digits.
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, select the type of service provided by the channel. The options are:
· Call by Call
· SDN (inc GSDN)
· MegaCom 800
· MegaCom
· Wats
· Accunet
· ILDS
· I800
· ETN
· Private Line
· AT&T Multiquest
Release 9.0
IP Office Manager
Page 291
15-601011 Issue 9.01 (Monday, September 09, 2013)
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.
Release 9.0
IP Office Manager
Page 292
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: Line
10.4.7.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.
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
Configuration Settings
· 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.
10.4.7.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 records in the Call by Call tab.
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
Configuration Settings
· 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
Release 9.0
IP Office Manager
Page 293
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.4.7.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.
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
Configuration Settings
· 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. The options are:
· Call by Call
· SDN (inc GSDN)
· MegaCom 800
· MegaCom
· Wats
· Accunet
· ILDS
· I800
· ETN
· Private Line
· AT&T Multiquest
Release 9.0
IP Office Manager
Page 294
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: Line
10.4.8 S0 Line
These settings are used for S0 ports provided by an S08 expansion module connected a control unit. For full
details of installation refer to the IP Office Installation manual.
Though displayed as lines, these BRI ports are used for connection of ISDN2 devices such as video
conferencing units or ISDN PC cards.
· 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.
10.4.8.1 Line
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
Configuration Settings
· 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
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.
· For Basic Edition and Standard Edition deployments, the same ID can be used for multiple lines.
· In a Server Edition network, the Outgoing Group ID used on a system must also be unique within the network, ie.
the same ID cannot be used in the configuration of any lines on another server system in the network.
Reserved Group ID
numbers
Description
90000 - 99999
Reserved for system use (not enforced).
99999 and 99998
In a Server Edition network, reserved for the H.323 lines to the Primary Server and
Secondary Server respectively.
999901 to 99930
In a Server Edition network, reserved for the H.323 lines from the Primary Server to each
expansion system in the network.
0
In a Server Edition network, the ID 0 cannot be used.
98888
For IP Office deployed in an Enterprise Branch environment, reserved for the SM line.
Release 9.0
IP Office Manager
Page 295
15-601011 Issue 9.01 (Monday, September 09, 2013)
· 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.
Release 9.0
IP Office Manager
Page 296
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: Line
10.4.8.2 Short Codes
For some types of line, Line short codes can be applied to any digits received with incoming calls.
The line Short Code tab is shown for the following trunk types which are treated as internal or private trunks: QSIG (T1,
E1, H.323), BRI S0, H.323, SCN. Incoming calls on those types of trunk are not routed using Incoming Call Route
settings. Instead the digits received with incoming calls are checked for a match as follows:
· Extension number (including remote numbers in a multi-site network).
· Line short codes (excluding ? short code).
· System short codes (excluding ? short code).
· Line ? short code.
· System ? short code.
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.
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
Release 9.0
IP Office Manager
Page 297
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.4.8.3 Channels
This tab allows settings for individual channels within the trunk to be adjusted. For So channels this form is not used.
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
Configuration Settings
· Line Appearance ID
Not used with So lines.
Release 9.0
IP Office Manager
Page 298
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: Line
10.4.9 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.
· QSIG trunks trunks are not supported on IP500 and IP500 V2 systems without IP500 Voice Networking
licenses.
Release 9.0
IP Office Manager
Page 299
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.4.9.1 Line
QSIG trunks trunks are not supported on IP500 and IP500 V2 systems without IP500 Voice Networking licenses.
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
Configuration Settings
· 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.
This option is available if Restrict Network Interconnect 219 (System | Telephony | Telephony 219 ) 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: multi-site networks, VPNremote, application telecommuter mode.
· 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.
· In a Server Edition network, the Outgoing Group ID used on a system must also be unique within the network,
ie. the same ID cannot be used in the configuration of any lines on another server system in the network. The IDs
99999 and 99998 which are reserved for the H.323 lines to the Primary Server and Secondary Server
respectively. The IDs 999901 to 99930 are reserved for the H.323 lines from the Primary Server to each
expansion system in the network. The ID 0 cannot be used in a Server Edition network.
· 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
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 250.
Defines the number of operational channels that are available on this line.
· Outgoing Channels: Default = 20, Range 0 to 250.
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 = 20, Range 0 to 250.
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.
Release 9.0
IP Office Manager
Page 300
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: Line
10.4.9.2 Short Codes
For some types of line, Line short codes can be applied to any digits received with incoming calls.
The line Short Code tab is shown for the following trunk types which are treated as internal or private trunks: QSIG (T1,
E1, H.323), BRI S0, H.323, SCN. Incoming calls on those types of trunk are not routed using Incoming Call Route
settings. Instead the digits received with incoming calls are checked for a match as follows:
· Extension number (including remote numbers in a multi-site network).
· Line short codes (excluding ? short code).
· System short codes (excluding ? short code).
· Line ? short code.
· System ? short code.
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.
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
Release 9.0
IP Office Manager
Page 301
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.4.9.3 VoIP
This form is used to configure the VoIP setting applied to calls on the H.323 line.
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
Configuration Settings
The VoIP settings available for an H.323 trunk depend on the Supplementary Services setting:
· Standard H.323 Line VoIP Settings 303
The following settings are applicable to trunks with their Supplementary Services set to H450, QSIG or None.
· SCN H.323 Line VoIP Settings 305
The following settings are applicable to H.323 trunks with their Supplementary Services set to IP Office SCN or
IP Office SCN - Fallback.
Release 9.0
IP Office Manager
Page 302
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: Line
10.4.9.3.1 Standard H323
The following settings are applicable to trunks with their Supplementary Services set to other than IP Office SCN or
IP Office Small Community Network - Fallback.
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
Configuration Settings
· Gateway IP Address: Default = Blank
Enter the IP address of the gateway device at the remote end.
· Port: Default = 1720
The H.323 line is identified by the IP Address:Port value. Specifying a unique port value for this IP address allows
multiple lines to use the same IP address.
· Codec Selection: Default = System Default
This field defines the codec or codecs offered during call setup.
· The available codecs in default preference order are: G.711 A-Law, G.711 U-Law, G.729 and G.723.1.
Note that the default order for G.711 codecs will vary to match the system's default companding setting.
G.723.1 is not supported on Linux based systems.
· The G.722 64K codec is also supported on IP500/IP500 V2 systems with IP500 VCM, IP500 VCM V2 or IP500
Combo cards. For Server Edition it is supported on Primary Server, Secondary Serverand Expansion System
(L) systems and on Expansion System (V2) systems fitted with IP500 VCM, IP500 VCM V2 or IP500 Combo. It
is not supported on any systems that include any IP400 VCM cards.
· The codecs available to be used are set through the System Codec list (System | System Codec
drop-down selector options are:
251 ).
The
· System Default
This is the default setting. When selected, the codec list below show matches the codecs set in the system
wide Default Selection list (System | Codecs 251 ).
· Custom
This option allows specific configuration of the codec preferences to be different from the system Default
Selection list. When Custom is selected, the list can be used to select which codecs are in the Unused list
and in the Selected list and to change the order of the selected codecs.
· Supplementary Services: Default = IP Office SCN
Selects the supplementary service signaling method for use across the H.323 trunk. The remote end of the trunk must
support the same option. Options are:
· None
No supplementary services are supported.
· H450
Use for H.323 lines connected to another PBX or device that uses H450.
· QSIG
Use for H.323 lines connected to another PBX or device that uses QSIG.
· IP Office SCN
This option is used for H.323 trunks within a multi-site network. The systems within a multi-site network
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 Small Community Network operation see Small
Community Networking 105 . For full details of a Server Edition network, see Server Edition Mode 71 .
· IP Office SCN - Fallback
This option is used for a multi-site network 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 multi-site network
for a period of more than 3 minutes. See Small Community Network Fallback 122 .
· Note that both ends of the SCN trunk connection must be set to fallback.
· On the system requesting backup, the required SCN Backup Options are selected, indicating that it is
requesting backup. A single system can only request backup from one other system.
· A system providing backup can provide backup for up to 7 other systems.
· Location: Default = Cloud
Specify a location to associate the extension with a physical location. Associating an extension with a location
· Allows emergency services to identify the source of an emergency call.
· Allows you to configure call access control settings for the location.
Release 9.0
IP Office Manager
Page 303
15-601011 Issue 9.01 (Monday, September 09, 2013)
The drop down list contains all locations that have been defined in the Location
506
page.
· Call Initiation Timeout: Default = 4 seconds. Range = 1 to 99 seconds.
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 494 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 G.711 between systems. On trunk's between networked
systems, the same setting should be set at both ends.
· 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
This option is only supported on trunks with their Supplementary Services set to IP Office SCN or IP Office Small
Community Network - Fallback. Fax relay 528 is supported across H.323 multi-site network lines with Fax
Transport Support selected. This will use 2 VCM channels in each of the systems. Fax relay 528 is only supported on
IP500/IP500 V2 systems with IP500 VCM, IP500 VCM V2 and or IP500 Combo cards. Fax relay 528 is supported on
Server Edition Linux servers.
· 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 a multi-site network.
· 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 IP calls must be routed via the system or can be routed alternately if possible within the
network structure.
· If enabled, IP 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 and be using the same protocol (H.323 or SIP). Enabling
this option may cause some vendors problems with changing the media path mid call.
· If disabled or not supported at on one end of the call, the call is routed via the system. 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.
Some telephony equipment, primarily AT&T switches, over IP trunks send a H.323 Progress rather than H.323
Proceeding message to signal that they have recognized the digits sent in overlap state. By default the system expects
an H.323 Proceeding message. This option is not available by default. If required, the value
ProgressEndsOverlapSend must be entered into the Source Numbers 359 tab of the NoUser 549 user.
· Default Name From Display IE: Default = Off.
When set, the Display IE is used as the default source for the name.
Release 9.0
IP Office Manager
Page 304
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: Line
10.4.9.3.2 SCN
The following settings are applicable to H.323 trunks with their Supplementary Services set to IP Office SCN or IP
Office SCN - Fallback.
Server Edition Network Usage
In a Server Edition network, all systems are linked in a star topography to the the Primary Server, using an H.323 IP
trunk with its Outgoing Group ID set to 99999. If the network also includes a Secondary Server, all systems are also
linked to the Secondary Server using an H.323 IP trunk with its Outgoing Group IP set to 99998.
These are the only H.323 IP trunks supported within the Server Edition network.
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
Configuration Settings
· 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
(H.323, SIP, SES or IP DECT).
· Codec Selection: Default = System Default
This field defines the codec or codecs offered during call setup.
· The available codecs in default preference order are: G.711 A-Law, G.711 U-Law, G.729 and G.723.1.
Note that the default order for G.711 codecs will vary to match the system's default companding setting.
G.723.1 is not supported on Linux based systems.
· The G.722 64K codec is also supported on IP500/IP500 V2 systems with IP500 VCM, IP500 VCM V2 or IP500
Combo cards. For Server Edition it is supported on Primary Server, Secondary Serverand Expansion System
(L) systems and on Expansion System (V2) systems fitted with IP500 VCM, IP500 VCM V2 or IP500 Combo. It
is not supported on any systems that include any IP400 VCM cards.
· The codecs available to be used are set through the System Codec list (System | System Codec
drop-down selector options are:
251 ).
The
· System Default
This is the default setting. When selected, the codec list below show matches the codecs set in the system
wide Default Selection list (System | Codecs 251 ).
· Custom
This option allows specific configuration of the codec preferences to be different from the system Default
Selection list. When Custom is selected, the list can be used to select which codecs are in the Unused list
and in the Selected list and to change the order of the selected codecs.
· Supplementary Services: Default = IP Office SCN
Selects the supplementary service signaling method for use across the H.323 trunk. The remote end of the trunk must
support the same option. Options are:
· None
No supplementary services are supported.
· H450
Use for H.323 lines connected to another PBX or device that uses H450.
· QSIG
Use for H.323 lines connected to another PBX or device that uses QSIG.
· IP Office SCN
This option is used for H.323 trunks within a multi-site network. The systems within a multi-site network
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 Small Community Network operation see Small
Community Networking 105 . For full details of a Server Edition network, see Server Edition Mode 71 .
· IP Office SCN - Fallback
This option is used for a multi-site network 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 multi-site network
for a period of more than 3 minutes. See Small Community Network Fallback 122 .
· Note that both ends of the SCN trunk connection must be set to fallback.
· On the system requesting backup, the required SCN Backup Options are selected, indicating that it is
requesting backup. A single system can only request backup from one other system.
· A system providing backup can provide backup for up to 7 other systems.
SCN Backup Options:
These options are only available on when the Supplementary Services option is set to IP Office - Fallback. The
intention of this feature is to attempt to maintain a minimal level of operation while problems with the local system are
resolved.
Release 9.0
IP Office Manager
Page 305
15-601011 Issue 9.01 (Monday, September 09, 2013)
· 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 network, 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.
· If using resilience backup 603 to support Avaya IP phones, Auto-create Extn and Auto-create User should
not be left enabled after initial configuration or any subsequent addition of new extensions and users. Leaving
auto-create options enabled on a system that is a failover target may cause duplicate extension/user records
on the multi-site network under multiple failure scenarios.
· Backs up my Hunt Groups: Default = On.
When selected, any hunt groups the local system is advertising to the network are advertised from the other
system when fallback is required. The trigger for this occurring is Avaya H.323 phones registered with the local
system registering with the other system, ie. Backs up my IP Phones above must also be enabled. In a Server
Edition network this option is only available on the H.323 trunk from the Primary Server to the Secondary Server.
· 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 network.
· Any local members who have hot desked to another system still visible within the network.
· 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 network. 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. In a Server Edition network this option is only available on the H.323 trunk from the Primary
Server to the Secondary Server. It is assumed as being on an is automatically set by the Resilience Administration
tool.
· This option requires the other system to have licenses for the Voicemail Pro features that are required to
operate during any fallback period.
· This option requires Voicemail Pro 5.0+.
· Call Initiation Timeout: Default = 4 seconds. Range = 1 to 99 seconds.
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 494 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 G.711 between systems. On trunk's between networked
systems, the same setting should be set at both ends.
· Fax Transport Support: Off
This option is only supported on trunks with their Supplementary Services set to IP Office SCN or IP Office Small
Community Network - Fallback. Fax relay 528 is supported across H.323 multi-site network lines with Fax
Transport Support selected. This will use 2 VCM channels in each of the systems. Fax relay 528 is only supported on
IP500/IP500 V2 systems with IP500 VCM, IP500 VCM V2 and or IP500 Combo cards. Fax relay 528 is supported on
Server Edition Linux servers.
· 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 a multi-site network.
· 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 IP calls must be routed via the system or can be routed alternately if possible within the
network structure.
· If enabled, IP 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 and be using the same protocol (H.323 or SIP). Enabling
this option may cause some vendors problems with changing the media path mid call.
Release 9.0
IP Office Manager
Page 306
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: Line
· If disabled or not supported at on one end of the call, the call is routed via the system. RTP relay support allows
calls between devices using the same audio codec to not require a voice compression channel.
Release 9.0
IP Office Manager
Page 307
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.4.10 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 IP DECT R4
Installation manual for full details.
10.4.10.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 Release 4.0 Q2 2007 maintenance release and higher.
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
Configuration Settings
· 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.
Release 9.0
IP Office Manager
Page 308
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: Line
10.4.10.2 Gateway
This form is used to configure aspects of information exchange between the IP Office and IP DECT systems.
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
Configuration Settings
· Auto-Create Extension: Default = Off.
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.
· Auto-Create User: Default = Off.
This option is only usable if Auto-Create Extension is also enabled. If enabled, subscription of a handset with the
DECT system causes the auto-creation of a matching user 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 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.
· Enable Provisioning:
This option can be used with DECT R4 systems. It allows the setting of several values in the system configuration that
previously needed to be set separately in the master base stations configuration. For full details refer to the DECT R4
Installation manual. The use of provisioning requires the system security settings to include an IPDECT Group.
· SARI/PARK: Default = 0
Enter the PARK (Portable Access Rights Key) license key of the DECT R4 system. DECT handset users enter this
key when subscribing to the DECT system.
· Subscriptions: Default = Disabled
Select the method of subscription supported for handsets subscribing to the DECT R4 system.
· Disabled
Disables subscription of handsets.
· Auto-Create
Allow anonymous subscription of handsets. Once subscribed, the handset is assigned a temporary extension
number. That extension number can be confirmed by dialing *#. A new extension number can be specified by
dialing <Extension Number>*<Login Code>#. The Auto-Create Extension and Auto-Create User settings
above should also be enabled. While configured to this mode, Manager will not allow the manual addition of
new IP DECT extensions.
Release 9.0
IP Office Manager
Page 309
15-601011 Issue 9.01 (Monday, September 09, 2013)
· Preconfigured
Allow subscription only against existing IP DECT extensions records in the system configuration. The handset
IPEI number is used to match the subscribing handset to a system extension.
· Authentication Code: Default = Blank.
Set an authentication code that DECT handset users should enter when subscribing to the DECT system.
Release 9.0
IP Office Manager
Page 310
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: Line
10.4.10.3 VoIP
This form is used to configure the VoIP setting applied to calls on the IP DECT line.
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
· 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
(H.323, SIP, SES or IP DECT).
· Codec Selection: Default = System Default
This field defines the codec or codecs offered during call setup.
· The available codecs in default preference order are: G.711 A-Law, G.711 U-Law, G.729 and G.723.1.
Note that the default order for G.711 codecs will vary to match the system's default companding setting.
G.723.1 is not supported on Linux based systems.
· The G.722 64K codec is also supported on IP500/IP500 V2 systems with IP500 VCM, IP500 VCM V2 or IP500
Combo cards. For Server Edition it is supported on Primary Server, Secondary Serverand Expansion System
(L) systems and on Expansion System (V2) systems fitted with IP500 VCM, IP500 VCM V2 or IP500 Combo. It
is not supported on any systems that include any IP400 VCM cards.
· The codecs available to be used are set through the System Codec list (System | System Codec
drop-down selector options are:
251 ).
The
· System Default
This is the default setting. When selected, the codec list below show matches the codecs set in the system
wide Default Selection list (System | Codecs 251 ).
· Custom
This option allows specific configuration of the codec preferences to be different from the system Default
Selection list. When Custom is selected, the list can be used to select which codecs are in the Unused list
and in the Selected list and to change the order of the selected codecs.
· TDM | IP Gain: Default = Default (0dB). Range = -31dB to +31dB.
Allows adjustment of the gain on audio from the system TDM interface to the IP connection. This field is not shown on
Linux based platforms.
· IP | TDM Gain: Default = Default (0dB). Range = -31dB to +31dB.
Allows adjustment of the gain on audio from the IP connection to the system TDM interface. This field is not shown on
Linux based platforms.
· 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 G.711 between systems. On trunk's between networked
systems, the same setting should be set at both ends.
· Allow Direct Media Path: Default = On
This settings controls whether IP calls must be routed via the system or can be routed alternately if possible within the
network structure.
· If enabled, IP 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 and be using the same protocol (H.323 or SIP). Enabling
this option may cause some vendors problems with changing the media path mid call.
· If disabled or not supported at on one end of the call, the call is routed via the system. RTP relay support allows
calls between devices using the same audio codec to not require a voice compression channel.
Release 9.0
IP Office Manager
Page 311
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.4.11 SIP Line
IP Office 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. For
an Expansion System (V2) 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 H.323 VoIP calls through firewalls often fails due to the effects of NAT (Network Address
Translation). For SIP a number of ways to ensure successful firewall traversal can be used. The system does not apply
any firewall between LAN1 and LAN2 to SIP calls.
· 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. To use STUN, the line must be linked to the Network Topology 209 settings of a LAN interface using the
line's Use Network Topology Info 320 setting.
· TURN (Traversal Using Relay NAT)
TCP SIP can use a mechanism called TURN (Traversal Using Relay NAT). This is not currently supported.
· Session Border Control
STUN is not required is the ITSP if a Session Border Controller (SBC) is used between the system and the ITSP.
The system does not perform its own SBC.
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 322 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 435 records.
8. DiffServ Marking
DiffServ marking is applied to calls using the DiffServer Settings on the System | LAN | VoIP
interface as set by the line's Use Network Topology Info setting.
Release 9.0
IP Office Manager
206
tab of the LAN
Page 312
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: Line
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.
· 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. For outgoing calls using this SIP
URI, all valid short code CLI manipulations are used (transforming calling party number to ISDN will be ignored).
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
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.
Release 9.0
IP Office Manager
Page 313
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.4.11.1 Incoming Call Routing
Incoming SIP calls are routed using Incoming Call Routes 433 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, records 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.
· 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. For outgoing calls using this SIP
URI, all valid short code CLI manipulations are used (transforming calling party number to ISDN will be ignored).
Release 9.0
IP Office Manager
Page 314
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: Line
10.4.11.2 SIP Line
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
Configuration Settings
· Line Number: Default = Automatically assigned.
By default a value is assigned by the system. This value can be changed but it must be unique.
· 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 record being used to route the call. This will use one of the following:
322
· a specific name entered in Local URI field of the channel record.
· 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
386 ).
· 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. Release 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.
· Release 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.
· Release 6.1+: This setting has replaced by ITSP Proxy Address on the Transport
320
tab.
· Prefix: Default = Blank.
This prefix is removed from the called number on outgoing calls if present. See SIP Prefix Operation
319
below.
· National Prefix: Default = 0.
This prefix is added to calls identified as not being international.
· Country Code: Default = Blank.
Set to match the local country code of the system location.
· International Prefix: Default = 00.
This prefix is added to calls identified as not being national.
· Send Caller ID: Default = None.
Select which value the SIP line should use for the original calling party ID when routing twinned calls.
· This setting is also used for forwarded calls. Note that the values on the System | Twinning 246 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.
· The SIP line Send Caller ID setting takes priority.
· The values on the System | Twinning
246
tab override the SIP lines Send Caller ID setting.
· Diversion Header
Use the information from the Diversion Header.
· Remote Party ID
Use the Remote Part ID.
· P Asserted ID
Use the contact information from the P Asserted ID.
· None
This option corresponds to the ISDN withheld setting.
· Network Type: Default = Public.
This option is available if Restrict Network Interconnect 219 (System | Telephony | Telephony 219 ) 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.
Release 9.0
IP Office Manager
Page 315
15-601011 Issue 9.01 (Monday, September 09, 2013)
· Due to the nature of this feature, its use is not recommended on systems also using any of the following other
system features: multi-site networks, VPNremote, application telecommuter mode.
· Association Method: Default = By Source IP Address.
This setting sets the method by which a SIP line is associated with an incoming SIP request.
· The match criteria used for each line can be varied. The search for a line match for an incoming request is
done against each line in turn using each lines Association Method. The order of line matching uses the
configured Line Number settings until a match occurs. If no match occurs the request is ignored. This
method allows multiple SIP lines with the same address settings. This may be necessary for scenarios where it
may be required to support multiple SIP lines to the same ITSP. For example when the same ITSP supports
different call plans on separate lines or where all outgoing SIP lines are routed from the system via an
additional on-site system.
· By Source IP Address
This option uses the source IP address and port of the incoming request for association. The match is against the
configured remote end of the SIP line, using either an IP address/port or the resolution of a fully qualified domain
name.
· "From" header hostpart against ITSP domain
This option uses the host part of the From header in the incoming SIP request for association. The match is
against the ITSP Domain Name above.
· R-URI hostpart against ITSP domain
This option uses the host part of the Request-URI header in the incoming SIP request for association. The match is
against the ITSP Domain Name above.
· "To" header hostpart against ITSP domain
This option uses the host part of the To header in the incoming SIP request for association. The match is against
the ITSP Domain Name above.
· "From" header hostpart against DNS-resolved ITSP domain
This option uses the host part of the FROM header in the incoming SIP request for association. The match is found
by comparing the FROM header against a list of IP addresses resulting from resolution of the ITSP Domain Name
above or, if set, the ITSP Proxy Address on the Transport 320 tab.
· "Via" header hostpart against DNS-resolved ITSP domain
This option uses the host part of the VIA header in the incoming SIP request for association. The match is found
by comparing the VIA header against a list of IP addresses resulting from resolution of the ITSP Domain Name
above or, if set, the ITSP Proxy Address on the Transport 320 tab.
· "From" header hostpart against ITSP proxy
This option uses the host part of the “From” header in the incoming SIP request for association. The match is
against the ITSP Proxy Address on the Transport 320 tab.
· "To" header hostpart against ITSP proxy
This option uses the host part of the From header in the incoming SIP request for association. The match is
against the ITSP Proxy Address on the Transport 320 tab.
· R-URI hostpart against ITSP proxy
This option uses the host part of the Request-URI in the incoming SIP request for association. The match is against
the ITSP Proxy Address on the Transport 320 tab.
· REFER Support: Default = On.
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.
Release 9.0
IP Office Manager
Page 316
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: Line
· Method for Session Refresh: Default = Auto.
The SIP UPDATE method (RFC 3311) allows a client to update parameters of a session (such as the set of media
streams and their codecs) but has no impact on the state of a dialog.
· RE-INVITE
Re-Invite messages are sent for session refresh.
· UPDATE
UPDATE messages are sent for session refresh if the other end indicates support for UPDATE in the allow header.
· Auto
UPDATE messages are sent for session refresh if the other end indicates support for UPDATE in the allow header.
If UPDATE is not supported, RE-INVITE messages are sent.
· Session Timer: Default = On Demand. Range = 90 to 64800
This field specifies the session expiry time. At the half way point of the expiry time, a session refresh message is
sent.
Setting the field to On Demand disables the session timer.
· Media Connection Preservation: Default = Disabled.
When enabled, allows established calls to continue despite brief network failures. Call handling features are no longer
available when a call is in a preserved state. Preservation on public SIP trunks is not supported until tested with a
specific service provider.
· In Service: Default = On.
When this field is not selected, the SIP trunk is unregistered and not available to incoming and outgoing calls.
· URI Type: Default = SIP. Release 6.2+
When SIP or SIPS is selected in the drop-down box, the SIP URI format is used (for example, name@example.com).
When Tel is selected in the drop-down box, the Tel URI format is used (for example, +1-425-555-4567). This affects
the From field of outgoing calls. The To field for outgoing calls will always use the format specified by the short codes
used for outgoing call routing. Recommendation: When SIP Secured URI is required, the URI Type should be set to
SIPS. SIPS can be used only when Layer 4 Protocol is set to TLS.
· Check OOS: Default = On.
If enabled, the system will regularly check if the trunk is in service using the methods listed below. 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 usable.
· For UDP and TCP trunks, OPTIONS message are regularly sent. If no reply to an OPTIONS message 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.
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.
This 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. If exported or imported as part of a trunk template 256 , this setting is not
supported by IP Office Basic Edition - Quick Mode mode systems.
· Name Priority: Default = System Default.
For SIP trunks, the caller name displayed on an extension can either be that supplied by the trunk or one obtained by
checking for a number match in the extension user's personal directory 387 and the system directory 450 . This setting
determines which method is used by the line. Select one of the following options:
· System Default
Use the system's Default Name Priority setting (System | Telephony | Telephony
219 ).
· Favour Trunk
Display the name provided by the trunk. For example, the trunk may be configured to provide the calling number
or the name of the caller. The system should display the caller information as it is provided by the trunk. If the
trunk does not provide a name, the system uses the Favour Directory method.
· Favour Directory
Search for a number match in the extension user's personal directory and then in the system directory. The first
match is used and overrides the name provided by the SIP line. If no match is found, the name provided by the
line, if any, is used.
· Caller ID from From Header: Default = Off.
Incoming calls can include caller ID information in both the From field and in the PAI fields. When this option is
selected, the caller ID information in the From field is used rather than that in the PAI fields.
Release 9.0
IP Office Manager
Page 317
15-601011 Issue 9.01 (Monday, September 09, 2013)
· Send From In Clear: Default = Off.
When selected, the user ID of the caller is included in the From field. This applies even if the caller has selected to be
or is configured to be anonymous, though their anonymous state is honored in other fields used to display the caller
identity.
· User-Agent and Server Headers: Default = Blank (Use system type and software level).
The value set in this field is used as the User-Agent and Server value included in SIP request headers made by this
line. If the field is blank, the type of IP Office system and its software level used. Setting a unique value can be useful
in call diagnostics when the system has multiple SIP trunks.
Release 9.0
IP Office Manager
Page 318
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: Line
SIP Prefix Operation
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
OPTIONS Operation
For Release 8.1 FP1, the sending of OPTIONS messages on a SIP line is controlled by a number of fields as follows:
· If either REFER Support or the UPDATE Supported values are set to Auto, then OPTIONS messages are sent.
· If neither REFER Support or the UPDATE Supported values are set to Auto, then:
· If the LAN interface's Binding Refresh Time is set, addition OPTIONS messages are not sent.
· If the LAN interface's Binding Refresh Time is 0, the sending of OPTIONS messages depends on the line's
Check OOS setting. If Check OOS is enabled, OPTIONS are not sent if line registrations occur more
frequently, otherwise OPTIONS are sent.
Release 9.0
IP Office Manager
Page 319
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.4.11.3 Transport
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
· ITSP Proxy Address and Calls Route via Registrar are mergeable.
Configuration Settings
· 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: Default = UDP.
· Send Port: When Network Configuration is set to TLS, the default setting is 5061. When Network Configuration is
set to TCP, the default setting is 5060.
· Listen Port: When Network Configuration is set to TLS, the default setting is 5061. When Network Configuration
is set to TCP, the default setting is 5060.
TLS connections support the following ciphers:
· TLS_RSA_WITH_AES_128_CBC_SHA
· TLS_RSA_WITH_AES_256_CBC_SHA
· TLS_DHE_RSA_WITH_AES_128_CBC_SHA
· TLS_DHE_RSA_WITH_AES_256_CBC_SHA
· Use Network Topology Info: Default = LAN1
This field associates the SIP line with the Network Topology settings (System | LAN1 | Network Topology 209 )
settings of the LAN interface. It also applies the LAN interfaces DiffServ Settings (System | LAN1 | VoIP 206 ) to
the outgoing traffic on the SIP line. If None is selected, STUN lookup is not applied and routing is determined by
the system's routing tables.
· 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. If exported or imported as part of a trunk template 256 ,
this setting not supported by IP Office Basic Edition - Quick Mode mode systems.
· 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.
Release 9.0
IP Office Manager
Page 320
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: Line
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.
Release 9.0
IP Office Manager
Page 321
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.4.11.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).
· 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. For outgoing calls using this SIP
URI, all valid short code CLI manipulations are used (transforming calling party number to ISDN will be ignored).
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 records on a SIP line.
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
Configuration Settings
· 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 Credentials User Name:
Use the User Name from the SIP Credentials
327
record being used for the call.
· Use Internal Data
Use the SIP Name value from the User | SIP 386 tab of the user making the call. The system can also use SIP URI
information configured for a hunt group (Hunt Group | SIP 409 ) or for the voicemail (System | Voicemail 214 ).
· Use Credentials Authentication Name
Use the Authentication Name from the SIP Credentials
· Use Credentials Contact
Use the Contact information from the SIP Credentials
327
327
record being used for the call.
record being used for the call.
· 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 Credentials User Name:
Use the User Name from the SIP Credentials
327
record being used for the call.
· Use Internal Data
Use the SIP Name value from the User | SIP 386 tab of the user making the call. The system can also use SIP URI
information configured for a hunt group (Hunt Group | SIP 409 ) or for the voicemail (System | Voicemail 214 ).
· Use Credentials Authentication Name
Use the Authentication Name from the SIP Credentials
· Use Credentials Contact
Use the Contact information from the SIP Credentials
327
327
record being used for the call.
record being used for the call.
· 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 Credentials User Name:
Use the User Name from the SIP Credentials
327
record being used for the call.
· Use Internal Data
Use the SIP Name value from the User | SIP 386 tab of the user making the call. The system can also use SIP URI
information configured for a hunt group (Hunt Group | SIP 409 ) or for the voicemail (System | Voicemail 214 ).
· Use Credentials Authentication Name
Use the Authentication Name from the SIP Credentials
· Use Credentials Contact
Use the Contact information from the SIP Credentials
Release 9.0
IP Office Manager
327
327
record being used for the call.
record being used for the call.
Page 322
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: Line
· PAI: Default = None.
You can enable P-Asserted-Identity (PAI) headers to assert the identity of users in outgoing SIP requests or response
messages. Use this setting to select the source of the user identity information or enter a value manually. The
selectable options are:
· None
When selected, the P-Preferred-Identity header is used instead of the P-Asserted-Identity, in order to ensure
compatibility with legacy networks.
· Use Credentials User Name:
Use the User Name from the SIP Credentials
327
record being used for the call.
· Use Internal Data
Use the SIP Name value from the User | SIP 386 tab of the user making the call. The system can also use SIP URI
information configured for a hunt group (Hunt Group | SIP 409 ) or for the voicemail (System | Voicemail 214 ).
· Use Credentials Authentication Name
Use the Authentication Name from the SIP Credentials
· Use Credentials Contact
Use the Contact information from the SIP Credentials
327
327
record being used for the call.
record being used for the call.
· Registration: Default = Primary
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.
· For Basic Edition and Standard Edition deployments, the same ID can be used for multiple lines.
· In a Server Edition network, the Outgoing Group ID used on a system must also be unique within the network, ie.
the same ID cannot be used in the configuration of any lines on another server system in the network.
Reserved Group ID
numbers
Description
90000 - 99999
Reserved for system use (not enforced).
99999 and 99998
In a Server Edition network, reserved for the H.323 lines to the Primary Server and
Secondary Server respectively.
999901 to 99930
In a Server Edition network, reserved for the H.323 lines from the Primary Server to each
expansion system in the network.
0
In a Server Edition network, the ID 0 cannot be used.
98888
For IP Office deployed in an Enterprise Branch environment, reserved for the SM line.
· 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.
For Outbound Contact Express deployments, the maximum value is 250.
Release 9.0
IP Office Manager
Page 323
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.4.11.5 VoIP
This form is used to configure the VoIP settings applied to calls on the SIP trunk.
Usability
· These settings are mergeable.
Configuration Settings
· Codec Selection: Default = System Default
This field defines the codec or codecs offered during call setup.
· The available codecs in default preference order are: G.711 A-Law, G.711 U-Law, G.729 and G.723.1.
Note that the default order for G.711 codecs will vary to match the system's default companding setting.
G.723.1 is not supported on Linux based systems.
· The G.722 64K codec is also supported on IP500/IP500 V2 systems with IP500 VCM, IP500 VCM V2 or IP500
Combo cards. For Server Edition it is supported on Primary Server, Secondary Serverand Expansion System
(L) systems and on Expansion System (V2) systems fitted with IP500 VCM, IP500 VCM V2 or IP500 Combo. It
is not supported on any systems that include any IP400 VCM cards.
· The codecs available to be used are set through the System Codec list (System | System Codec
drop-down selector options are:
251 ).
The
· System Default
This is the default setting. When selected, the codec list below show matches the codecs set in the system
wide Default Selection list (System | Codecs 251 ).
· Custom
This option allows specific configuration of the codec preferences to be different from the system Default
Selection list. When Custom is selected, the list can be used to select which codecs are in the Unused list
and in the Selected list and to change the order of the selected codecs.
· Fax Transport Support: Default = Off.
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, IP500 VCM V2 or IP500 Combo base card. For systems in a network, fax relay 528 is supported
for fax calls between the systems.
· None
Select this option if fax is not supported by the line provider.
· G.711
G.711 is used for the sending and receiving of faxes.
· T38
T38 is used for the sending and receiving of faxes.
· T38 Fallback
When you enable this option, T38 is used for sending and receiving faxes on a SIP line. If the called destination
does not support T38, the system will send a re-invite to change the transport method to G.711. This option is not
supported by Linux based systems.
· Location: Default = Cloud.
Specify a location to associate the extension with a physical location. Associating an extension with a location
· Allows emergency services to identify the source of an emergency call.
· Allows you to configure call access control settings for the location.
The drop down list contains all locations that have been defined in the Location
506
page.
· Call Initiation Timeout: Default = 4 seconds. Range = 1 to 99 seconds.
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 494 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 G.711 between systems. On trunk's between networked
systems, the same setting should be set at both ends.
Release 9.0
IP Office Manager
Page 324
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: Line
· Allow Direct Media Path: Default = Off.
This setting is only supported on Server Edition systems. This option is only available when Re-Invite Supported is
enabled.
The settings controls whether IP calls must be routed via the system or can be routed alternately if possible within the
network structure. If enabled, IP 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 and be using the same protocol (H.323 or
SIP). Enabling this option may cause some vendors problems with changing the media path mid call.
· 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.
· Codec Lockdown: Default = Off.
Supports RFC 3264 Section 10.2 when RE-Invite Supported is enabled. In response to a SIP offer with a list of
codecs supported, some SIP user agents supply a SDP answer that also lists multiple codecs. This means that the user
agent may switch to any of those codecs during the session without further negotiation. The system does not support
multiple concurrent codecs for a session, so loss of speech path will occur if the codec is changed during the session. If
codec lockdown is enabled, when the system receives an SDP answer with more than one codec from the list of offered
codecs, it sends an extra re-INVITE using just a single codec from the list and resubmits a new SDP offer with just the
single chosen codec.
· PRACK/100rel Supported: Default = Off.
When selected, supports Provisional Reliable Acknowledgement (PRACK) on SIP trunks. Enable this parameter when
you want to ensure that provisional responses, such as announcement messages, have been delivered. Provisional
responses provide information on the progress of the request that is in process. For example, while a cell phone call is
being connected, there may be a delay while the cell phone is located; an announcement such as “please wait while we
attempt to reach the subscriber” provides provisional information to the caller while the request is in process. PRACK,
which is defined in RFC 3262, provides a mechanism to ensure the delivery of these provisional responses.
· Force direct media with phones: Default = Off. (Server Edition only)
This setting is only supported on Server Edition systems. The setting is only useable when the trunk's Re-invite
Supported and Allow Direct Media Path settings are enabled and its DTMF Support option is set to RFC2833/
RFC4733. It also requires the H.323 IP extension involved in the call to also have Allow Direct Media Path enabled.
This feature is only supported with Avaya H.323 IP telephones. For calls where the Avaya H.323 IP extension using the
trunk is doing so as a direct media call, this feature allows digits presses on the extension to be detected and the call
changed to an indirect media call so that RFC2833 DTMF can be sent. The call remains as an indirect media call for 15
seconds after the last digit before reverting back to being a direct media call.
· G.711 Fax ECAN: Default = Off.
If Fax Transport Support is set to 'G.711' and also 'T.38 Fallback' to G.711 on IP500V2, when IP Office detects a fax
call, the IP Office negotiates to G.711 (if not already in G.711) and reconfigures the connection with echo cancellation
(ECAN) based on the 'G.711 Fax ECAN field. This can be used to avoid an ECAN mismatch with the SIP trunk service
provider. Also for fax calls, the connections NLP is disabled, a fixed jitter buffer is set and silence suppression is
disabled.
Release 9.0
IP Office Manager
Page 325
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.4.11.6 T38 Fax
The settings on this tab are only accessible if Re-invite Supported and Fax Transport Support are selected on the
VoIP 341 tab.
Fax relay 528 is only supported on IP500/IP500 V2 systems with IP500 VCM, IP500 VCM V2 and or IP500 Combo cards.
Fax relay is not supported on Server Edition.
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
Configuration Settings
· 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.
Release 9.0
IP Office Manager
Page 326
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: Line
10.4.11.7 SIP Credentials
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.
Usability
· Mergeable:
These settings are mergeable. Changes to these settings do not require a reboot of the system.
Configuration Settings
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 322 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 if 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.
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.
If selected, the fields above above are used for registration when making calls. If exported or imported as part of
a trunk template 256 , this setting is not supported by IP Office Basic Edition - Quick Mode mode systems.
Release 9.0
IP Office Manager
Page 327
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.4.12 SIP DECT Line
A SIP DECT line can be manually added. SIP DECT lines are used to manage D100 Base Station operation.
10.4.12.1 SIP DECT Base
Currently, IP Office supports four D100 Base Stations.
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
Configuration Settings
· Line Number: Default = Blank.
A unique line number associated with the SIP DECT Base Station.
Associated Extensions are other extensions that can log into the base station.
· Base Name: Default = Blank. Maximum 16 charaters
A name assigned to the base station. Each base station provisioned on the IP Office must have a unique name. The
field cannot be blank. The format is an alphanumeric string with no special characters.
· Base MAC Address: Default = Blank.
The MAC Address of the base station. If only one base station is provisioned, the field can remain at the default value.
If multiple base stations are provisioned, the MAC address for each base station must be entered.
· Configure Base IP: Default = Off.
Set to On to configure IP address attributes for the base station. When enabled, the Configure Base IP settings are
displayed.
· DHCP Client: Default = On.
When enabled, specifies that the base station operates as a DHCP client. When enabled, not other IP address
attributes can be configured.
· IP Address: Default = Blank.
The IP address of the base station. The IP address must be on the same subnet as one of the LAN interfaces.
· IP Mask: Default = Blank.
IP address mask.
· IP Gateway: Default = Blank.
The default gateway address.
· Provisioning Server: Default = IP Office interface address.
The server address from where the Base Station configuration files can be retrieved.
Release 9.0
IP Office Manager
Page 328
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: Line
10.4.12.2 VoIP
This form is used to configure the VoIP setting applied to calls on the SIP DECT line.
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
Configuration Settings
· IP Address: Default = Blank.
The IP address of the SIP DECT extension.
· Codec Selection: Default = Custom
This field defines the codec or codecs offered during call setup. The codecs available to be used are set through the
System Codec list (System | System Codec 251 ).
The Custom option allows specific configuration of the codec preferences to be different from the system Default
Selection list. When Custom is selected, the list can be used to select which codecs are in the Unused list and in the
Selected list and to change the order of the selected codecs.
The D100 Base Station supports only G711 codecs.
· TDM | IP Gain: Default = Default (0dB). Range = -31dB to +31dB.
Allows adjustment of the gain on audio from the system TDM interface to the IP connection. This field is not shown on
Linux based platforms.
· IP | TDM Gain: Default = Default (0dB). Range = -31dB to +31dB.
Allows adjustment of the gain on audio from the IP connection to the system TDM interface. This field is not shown on
Linux based platforms.
· DTMF Support: Default =RFC2833
The D100 Base Station supports only RFC2833.
· 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 G.711 between systems. On trunk's between networked
systems, the same setting should be set at both ends.
· Local Hold Music: Default = Off
· Allow Direct Media Path: Default = On
This settings controls whether IP calls must be routed via the system or can be routed alternately if possible within the
network structure.
· If enabled, IP 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 and be using the same protocol (H.323 or SIP). Enabling
this option may cause some vendors problems with changing the media path mid call.
· If disabled or not supported at on one end of the call, the call is routed via the system. 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.
Release 9.0
IP Office Manager
Page 329
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.4.13 SM Line
This type of line is used to create a SIP connection between an IP Office and an Avaya Aura® Session Manager. The
other end of the SIP connection must be configured on the Session Manager as a SIP Entity Link.
An SM Line can only be added to IP Office system Standard Mode or Server Edition configurations. It is typically used in
IP Office Standard mode in Enterprise Branch deployments connected to the Avaya Aura® network. For more details
about IP Office Enterprise Branch deployments refer to Deploying IP Office in an Avaya Aura® Branch Environment (18–
603853).
An SM Line can also be used in IP Office Server Edition to connect to an Avaya Aura® Session Manager. Through the SM
Line, IP Office Server Edition supports interoperability with Avaya Aura® Session Manager. It also supports
interoperability, via the Avaya Aura® Session Manager, with Avaya Aura® Communication Manager systems and with CS
1000 systems. Note that IP Office Server Edition is not used as an enterprise branch product and does not support some
of the IP Office enterprise branch functionality, such as management by Avaya Aura® System Manager, WebLM licensing,
Centralized Users or voicemail over the SM Line.
If the Avaya Aura® network has multiple Avaya Aura® Session Managers to provide redundancy, two SM lines can be
added, one configured for each Avaya Aura® Session Manager.
10.4.13.1 Session Manager
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
Configuration Settings
· Line Number: Default = Automatically assigned
This value is automatically assigned by the Enterprise Branch and should be unique for each line added to the
configuration.
· Session Manager line prioritization Up to two Session Manager lines can be configured. The two Session
Manager lines are prioritized based on the line number. The lower line number is considered the primary Session
Manager line. For example, if the first Session Manager line is configured as line number 17 and the second
Session Manager line is configured as line 18, then line number 17 is considered the primary Session Manager line.
If you want to designate the second Session Manager line (line 18 in this example) as the primary Session
Manager line, you must change one or both of the line numbers so that the second Session Manager line is
configured with a lower number than the current primary line.
· Session Manager line redundancy – Based on the priority of the Session Manager lines designated by the line
number, the active line to which theIP Office> sends all calls will always be the highest priority Session Manager
line in service. That is, if the primary Session Manager line is in service, it will be the active line for sending calls.
If the connection to the primary Session Manager line is lost, causing the IP Office to switch to the secondary
Session Manager line, then when the primary line comes back up later, the IP Office reverts back to the primary
Session Manager line.
· In Service: Default = Enabled
This option can be used to administratively disable the SM Line. It does not reflect the dynamic state of the line. If an
SM Line is administratively disabled it is not equivalent to being in the dynamic out of service state.
· SM Domain Name
This should match a SIP domain defined in the Session Manager system's SIP Domains table. Unless there are reasons
to do otherwise, all the Enterprise Branch systems in the Avaya Aura® network can share the same domain.
· SM Address
Enter the IP address of the Session Manager the line should use in the Avaya Aura network. The same Session
Manager should be used for the matching Entity Link record in the Avaya Aura® configuration.
· Outgoing Group ID: Default = 98888
This value is not changeable. However note the value as it is used in Enterprise Branch short codes used to route calls
to the Session Manager.
· Prefix: Default = Blank
This prefix will be added to any source number received with incoming calls.
· Max Calls: Default = 10
Sets the number of simultaneous calls allowed between the Enterprise Branch and Session Manager using this
connection. Each call will use one of the available licenses that are shared by all SIP trunks configured in the system.
· Network Type: Default = Private.
This option is available if Restrict Network Interconnect 219 (System | Telephony | Telephony 219 ) 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.
Release 9.0
IP Office Manager
Page 330
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: Line
· Due to the nature of this feature, its use is not recommended on systems also using any of the following other
system features: multi-site networks, VPNremote, application telecommuter mode.
· URI Type: Default = SIP.
When SIP or SIPS is selected in the drop-down box, the SIP URI format is used (for example, name@example.com).
This affects the From field of outgoing calls. The To field for outgoing calls will always use the format specified by the
short codes used for outgoing call routing. Recommendation: When SIP Secured URI is required, the URI Type should
be set to SIPS. SIPS can be used only when Layer 4 Protocol is set to TLS.
· Media Connection Preservation: Default = Enabled.
When enabled, attempts to maintain established calls despite brief network failures. Call handling features are no
longer available when a call is in a preserved state. When enabled, Media Connection Preservation applies to Avaya
H.323 phones that support connection preservation.
· Network Configuration: Default = TLS.
· Send Port: When Network Configuration is set to TLS, the default setting is 5061. When Network Configuration is
set to TCP, the default setting is 5060.
· Listen Port: When Network Configuration is set to TLS, the default setting is 5061. When Network Configuration
is set to TCP, the default setting is 5060.
TLS connections support the following ciphers:
· TLS_RSA_WITH_AES_128_CBC_SHA
· TLS_RSA_WITH_AES_256_CBC_SHA
· TLS_DHE_RSA_WITH_AES_128_CBC_SHA
· TLS_DHE_RSA_WITH_AES_256_CBC_SHA
· Session Timer: Default = 1200. Range = 90 to 64800
This field specifies the session expiry time. At the half way point of the expiry time, a session refresh message is
sent.
Setting the field to On Demand disables the session timer.
Communication Manager supports SIP session refresh via UPDATE in Communicaton Manger release 6.2 SP1 and later.
If using an earlier release of Communication Manager, then the Session Timer parameter must be set to On
Demand.
Release 9.0
IP Office Manager
Page 331
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.4.13.2 VoIP
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
Configuration Settings
· Codec Selection: Default = System Default
This field defines the codec or codecs offered during call setup.
· The available codecs in default preference order are: G.711 A-Law, G.711 U-Law, G.729 and G.723.1.
Note that the default order for G.711 codecs will vary to match the system's default companding setting.
G.723.1 is not supported on Linux based systems.
· The G.722 64K codec is also supported on IP500/IP500 V2 systems with IP500 VCM, IP500 VCM V2 or IP500
Combo cards. For Server Edition it is supported on Primary Server, Secondary Serverand Expansion System
(L) systems and on Expansion System (V2) systems fitted with IP500 VCM, IP500 VCM V2 or IP500 Combo. It
is not supported on any systems that include any IP400 VCM cards.
· The codecs available to be used are set through the System Codec list (System | System Codec
drop-down selector options are:
251 ).
The
· System Default
This is the default setting. When selected, the codec list below show matches the codecs set in the system
wide Default Selection list (System | Codecs 251 ).
· Custom
This option allows specific configuration of the codec preferences to be different from the system Default
Selection list. When Custom is selected, the list can be used to select which codecs are in the Unused list
and in the Selected list and to change the order of the selected codecs.
· Fax Transport Support: Default = Off.
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, IP500 VCM V2 or IP500 Combo base card. For systems in a network, fax relay 528 is supported
for fax calls between the systems.
· None
Select this option if fax is not supported by the line provider.
· G.711
G.711 is used for the sending and receiving of faxes.
· T38
T38 is used for the sending and receiving of faxes.
· T38 Fallback
When you enable this option, T38 is used for sending and receiving faxes on a SIP line. If the called destination
does not support T38, the system will send a re-invite to change the transport method to G.711. This option is not
supported by Linux based systems.
· Location: Default = Cloud.
· Call Initiation Timeout: Default = 4 seconds. Range = 1 to 99 seconds.
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 494 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 G.711 between systems. On trunk's between networked
systems, the same setting should be set at both ends.
· Allow Direct Media Path: Default = On
This settings controls whether IP calls must be routed via the system or can be routed alternately if possible within the
network structure.
· If enabled, IP 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 and be using the same protocol (H.323 or SIP). Enabling
this option may cause some vendors problems with changing the media path mid call.
· If disabled or not supported at on one end of the call, the call is routed via the system. RTP relay support allows
calls between devices using the same audio codec to not require a voice compression channel.
Release 9.0
IP Office Manager
Page 332
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: Line
· 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.
· Codec Lockdown: Default = Off.
Supports RFC 3264 Section 10.2 when RE-Invite Supported is enabled. In response to a SIP offer with a list of
codecs supported, some SIP user agents supply a SDP answer that also lists multiple codecs. This means that the user
agent may switch to any of those codecs during the session without further negotiation. The system does not support
multiple concurrent codecs for a session, so loss of speech path will occur if the codec is changed during the session. If
codec lockdown is enabled, when the system receives an SDP answer with more than one codec from the list of offered
codecs, it sends an extra re-INVITE using just a single codec from the list and resubmits a new SDP offer with just the
single chosen codec.
· Force direct media with phones: Default = Off.
Description required.
· G.711 Fax ECAN: Default = Off.
Description required.
Release 9.0
IP Office Manager
Page 333
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.4.13.3 T38 Fax
The settings on this tab are only accessible if Re-invite Supported and Fax Transport Support are selected on the
VoIP 341 tab.
Fax relay 528 is only supported on IP500/IP500 V2 systems with IP500 VCM, IP500 VCM V2 and or IP500 Combo cards.
Fax relay is not supported on Server Edition.
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
Configuration Settings
· 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.
Release 9.0
IP Office Manager
Page 334
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: Line
10.5 Control Unit
The Control Unit form gives details of the system and some devices connected to or within the system.
This includes some modules within the control nit as well as external expansion modules.
For Server Edition systems, for the Primary Server, Secondary Server and Expansion System (L) it shows
details for the physical server platform and details for the IP Office Media service being hosted on that
server. For the Expansion System (V2) it shows details of the IP500 V2 control unit and the cards installed
into the control unit.
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. This action can only be used with external
expansion modules attached to a system. The action should used with caution as deleting a module will also
delete any extensions or lines associated with the module being deleted. If the module is physically present,
default records are automatically recreated following a reboot.
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
Configuration Settings
· 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 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 LAN1.
· 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.
· Operating Mode
This field is available when a DS16B or DS30B digital expansion module is selected as the control unit. Select the
operating mode based on the type of telephones deployed.
· DS - 1400, 9500, 5400, 2400, T3, 4400 Series Phones
· BST - T7000, M7000 Series Phones
Release 9.0
IP Office Manager
Page 335
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.6 Extension
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.
Non-IP 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 records are automatically created for each physical extension port within the system. These
ports cannot be added or deleted manually.For Server Edition, non-IP extensions are only supported on Expansion
System (V2) units.
·
Standard Telephone
A standard extension.
·
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 and VoIP applications.
·
H.323 or SIP Extension
This icon indicates an IP extension. IP extensions are either added manually or by the automatic detection of the
phone being connected. IP extensions can also be added manually to support 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 record is created while the user is logged into
the application. That record is not editable. The softphone extension record is automatically deleted within a few minutes
of the user closing the softphone application.
Release 9.0
IP Office Manager
Page 336
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: Extension
10.6.1 Extn
This tab contains settings applicable to most types of extension.
For Server Edition, this type of configuration record can be saved as a template and new records created from a
template. See Templates 78 .
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
Configuration Settings
· 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 multi-site network). This does not occur it that user is set to Force Login (User |
Telephone 361 ).
· 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.
· Extensions associated with IP phones should not be given extension numbers greater than 7 digits.
· Users for CBC and CCC should only use up to 4 digit extension numbers.
· Phone Password: Default = Blank. Range = Up to 31 digits.
H.323 Extensions only. Does not apply to T3 series phones and DECT phones.
The code that must 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 entry must be at least 4 digits for DS port users. Login codes of up to 15 digits are supported
with Extn Login 869 buttons 869 . Login codes of up to 31 digits are supported with Extn Login 751 short codes 751 .
· Caller Display Type: Default = On.
Controls the presentation of caller display information for analog extensions, see Caller Display 532 . 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 998 . 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, 9500 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.
Release 9.0
IP Office Manager
Page 337
15-601011 Issue 9.01 (Monday, September 09, 2013)
· Digital extension ports report the type of digital phone connected or Unknown digital handset if no phone is
detected.
· H.323 extensions report the type of IP phone registered or Unknown H.323 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.
· Location: Default = System (None).
Specify a location to associate the extension with a physical location. Associating an extension with a location
· Allows emergency services to identify the source of an emergency call.
· Allows you to configure call access control settings for the location.
The drop down list contains all locations that have been defined in the Location
506
page.
· 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/IP500 V2
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).
When selected, disables the fixed SPEAKER button if present on the phone using this extension port. Only supported
on Avaya DS, TCM and H.323 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.
This setting is used with SIP extension devices.
Release 9.0
IP Office Manager
Page 338
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: Extension
10.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.
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
Configuration Settings
· Equipment Classification: Default = Standard Telephone
Only available for analog extension ports. Note that 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 361 (User | Telephony | Call Settings 361
) 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 743 features.
· When using a UPAM connected to an analog extension port, the extension's Equipment Classification
(Extension | Analog) 339 should be set to IVR Port and not Paging Speaker.
339
· 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.
· FAX Machine
If fax Relay 528 is being used, this setting should be selected on any analog extension connected to an analog fax
machine. This setting can also be used with SIP trunks.
· MOH Source
If selected, the port can be used as a music on hold source in the Tones and Music 223 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 545 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,
51V Stepped
Korea, Mexico, New Zealand, Peru, Russia, Saudi Arabia, South Africa,
Spain, United States, Venezuela.
Bahrain, Belgium, Denmark, Egypt, Finland, France, Germany, Greece, On = 101V on Phone V2
Hong Kong, Hungary, Iceland, Italy, India, Kuwait, Morocco,
modules and IP500 Phone
Netherlands, Norway, Oman, Pakistan, Poland, Portugal, Qatar,
cards, otherwise 81V.
Singapore, Sweden, Switzerland, Taiwan, Turkey, United Arab
Emirates, United Kingdom.
· IP500 V2: If the option Restrict Analog Extension Ringer Voltage is selected (System | Telephony | Telephony
219 ), 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.
Release 9.0
IP Office Manager
Page 339
15-601011 Issue 9.01 (Monday, September 09, 2013)
· 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
998 .
· 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.
Release 9.0
IP Office Manager
Page 340
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: Extension
10.6.3 VoIP
This tab is only available for H.323 and SIP extensions. The settings available will vary depending on the extension type:
· H.323 IP Extension
· SIP Extension
341
343
10.6.3.1 H323 Extension
These settings are shown for a H.323 IP extension.
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
Configuration Settings
· IP Address: Default = 0.0.0.0
The IP address of the phone. The default setting accepts connection from any address. For phones using DHCP, the
field is not updated to show the IP address being used by the phone.
· For T3 IP phones installed using DHCP, the address obtained and being used by the phone is displayed. If that
address is from the same range as the DHCP pool being supported by the IP Office system, Manager will indicate
an error.
· The IP Address field can be used to restrict the the source IP address that can used by a Remote H.323
Extension 590 . However, it should not used in the case where there is more than one remote extension behind the
domestic router.
· MAC Address: Default = 0000000000000 (Grayed out)
This field is grayed out and not used.
· Codec Selection: Default = System Default
This field defines the codec or codecs offered during call setup.
· The available codecs in default preference order are: G.711 A-Law, G.711 U-Law, G.729 and G.723.1.
Note that the default order for G.711 codecs will vary to match the system's default companding setting.
G.723.1 is not supported on Linux based systems.
· The G.722 64K codec is also supported on IP500/IP500 V2 systems with IP500 VCM, IP500 VCM V2 or IP500
Combo cards. For Server Edition it is supported on Primary Server, Secondary Serverand Expansion System
(L) systems and on Expansion System (V2) systems fitted with IP500 VCM, IP500 VCM V2 or IP500 Combo. It
is not supported on any systems that include any IP400 VCM cards.
· The codecs available to be used are set through the System Codec list (System | System Codec
drop-down selector options are:
251 ).
The
· System Default
This is the default setting. When selected, the codec list below show matches the codecs set in the system
wide Default Selection list (System | Codecs 251 ).
· Custom
This option allows specific configuration of the codec preferences to be different from the system Default
Selection list. When Custom is selected, the list can be used to select which codecs are in the Unused list
and in the Selected list and to change the order of the selected codecs.
· TDM | IP Gain: Default = Default (0dB). Range = -31dB to +31dB.
Allows adjustment of the gain on audio from the system TDM interface to the IP connection. This field is not shown on
Linux based platforms.
· IP | TDM Gain: Default = Default (0dB). Range = -31dB to +31dB.
Allows adjustment of the gain on audio from the IP connection to the system TDM interface. This field is not shown on
Linux based platforms.
· Supplementary Services: Default = H450.
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 G.711 between systems. On trunk's between networked
systems, the same setting should be set at both ends.
Release 9.0
IP Office Manager
Page 341
15-601011 Issue 9.01 (Monday, September 09, 2013)
· 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
bit-rate 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.
· Local Tones: Default = Off
When selected, the H.323 phones generate their own tones. This option is not supported by Avaya IP phones
softphone application.
· Allow Direct Media Path: Default = On
This settings controls whether IP calls must be routed via the system or can be routed alternately if possible within the
network structure.
· If enabled, IP 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 and be using the same protocol (H.323 or SIP). Enabling
this option may cause some vendors problems with changing the media path mid call.
· If disabled or not supported at on one end of the call, the call is routed via the system. 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. The phone must have firmware T246 or
higher.
· Reserve License: Default = None.
Each Avaya IP phones requires an Avaya IP Endpoint license. Each non-Avaya IP phones requires an 3rd Party IP
Endpoint license.
Normally these licenses are issued in the order that devices register. This option allows this extension to be prelicensed before the device has registered. This helps prevent a previously licensed phone becoming unlicensed
following a system restart if unlicensed devices are also present.
The drop down options are:
· Reserve Avaya IP Endpoint License
· Reserve 3rd Party IP Endpoint License
· Both
· None
Note that when WebLM licensing is enabled, this field is automatically set to Reserve Avaya IP Endpoint License.
The Both and None options are not available.
Release 9.0
IP Office Manager
Page 342
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: Extension
10.6.3.2 SIP Extension
There settings are shown for SIP IP extensions.
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
Configuration Settings
· IP Address: Default = 0.0.0.0
The IP address of the phone. The default setting accepts connection from any address. If an address is entered,
registration is only accepted from a device with that address.
· Codec Selection: Default = System Default
This field defines the codec or codecs offered during call setup.
· The available codecs in default preference order are: G.711 A-Law, G.711 U-Law, G.729 and G.723.1.
Note that the default order for G.711 codecs will vary to match the system's default companding setting.
G.723.1 is not supported on Linux based systems.
· The G.722 64K codec is also supported on IP500/IP500 V2 systems with IP500 VCM, IP500 VCM V2 or IP500
Combo cards. For Server Edition it is supported on Primary Server, Secondary Serverand Expansion System
(L) systems and on Expansion System (V2) systems fitted with IP500 VCM, IP500 VCM V2 or IP500 Combo. It
is not supported on any systems that include any IP400 VCM cards.
· The codecs available to be used are set through the System Codec list (System | System Codec
drop-down selector options are:
251 ).
The
· System Default
This is the default setting. When selected, the codec list below show matches the codecs set in the system
wide Default Selection list (System | Codecs 251 ).
· Custom
This option allows specific configuration of the codec preferences to be different from the system Default
Selection list. When Custom is selected, the list can be used to select which codecs are in the Unused list
and in the Selected list and to change the order of the selected codecs.
· Fax Transport Support: Default = Off.
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, IP500 VCM V2 or IP500 Combo base card. For systems in a network, fax relay 528 is supported
for fax calls between the systems.
· None
Select this option if fax is not supported by the line provider.
· G.711
G.711 is used for the sending and receiving of faxes.
· T38
T38 is used for the sending and receiving of faxes.
· T38 Fallback
When you enable this option, T38 is used for sending and receiving faxes on a SIP line. If the called destination
does not support T38, the system will send a re-invite to change the transport method to G.711. This option is not
supported by Linux based systems.
· TDM | IP Gain: Default = Default (0dB). Range = -31dB to +31dB.
Allows adjustment of the gain on audio from the system TDM interface to the IP connection. This field is not shown on
Linux based platforms.
· IP | TDM Gain: Default = Default (0dB). Range = -31dB to +31dB.
Allows adjustment of the gain on audio from the IP connection to the system TDM interface. This field is not shown on
Linux based platforms.
· 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 G.711 between systems. On trunk's between networked
systems, the same setting should be set at both ends.
· Local Hold Music: Default = Off
Release 9.0
IP Office Manager
Page 343
15-601011 Issue 9.01 (Monday, September 09, 2013)
· Allow Direct Media Path: Default = On
This settings controls whether IP calls must be routed via the system or can be routed alternately if possible within the
network structure.
· If enabled, IP 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 and be using the same protocol (H.323 or SIP). Enabling
this option may cause some vendors problems with changing the media path mid call.
· If disabled or not supported at on one end of the call, the call is routed via the system. 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.
· Codec Lockdown: Default = Off.
Supports RFC 3264 Section 10.2 when RE-Invite Supported is enabled. In response to a SIP offer with a list of
codecs supported, some SIP user agents supply a SDP answer that also lists multiple codecs. This means that the user
agent may switch to any of those codecs during the session without further negotiation. The system does not support
multiple concurrent codecs for a session, so loss of speech path will occur if the codec is changed during the session. If
codec lockdown is enabled, when the system receives an SDP answer with more than one codec from the list of offered
codecs, it sends an extra re-INVITE using just a single codec from the list and resubmits a new SDP offer with just the
single chosen codec.
· Reserve License: Default = None.
Each Avaya IP phones requires an Avaya IP Endpoint license. Each non-Avaya IP phones requires an 3rd Party IP
Endpoint license.
Normally these licenses are issued in the order that devices register. This option allows this extension to be prelicensed before the device has registered. This helps prevent a previously licensed phone becoming unlicensed
following a system restart if unlicensed devices are also present.
The drop down options are:
· Reserve Avaya IP Endpoint License
· Reserve 3rd Party IP Endpoint License
· Both
· None
Note the following:
· When WebLM licensing is enabled, this field is automatically set to Reserve Avaya IP Endpoint License. The
Both and None options are not available.
· When the Profile of the corresponding user is set to Centralized User, this field is automatically set to
Centralized Endpoint License and cannot be changed.
Release 9.0
IP Office Manager
Page 344
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: Extension
10.6.4 T38 Fax
The settings on this tab are only accessible if Re-invite Supported and Fax Transport Support are selected on the
VoIP 341 tab.
Fax relay 528 is only supported on IP500/IP500 V2 systems with IP500 VCM, IP500 VCM V2 and or IP500 Combo cards.
Fax relay is not supported on Server Edition.
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
Configuration Settings
· 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.
Release 9.0
IP Office Manager
Page 345
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.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.
308
line has been added to the
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
Configuration Settings
· DECT Line ID
Use the drop-down list to select the IP DECT line
308
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 License: Default = None.
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.
The drop down options are:
· Reserve Avaya IP Endpoint License
· None
Note that when WebLM licensing is enabled, this field is automatically set to Reserve Avaya IP Endpoint License
and cannot be changed.
The additional fields below depend on whether the IP DECT line has Enable Provisioning selected.
· Enable Provisioning Not Selected
· Handset Type: Default = Unknown
Correct selection of the handset type allows application of appropriate settings for the handset display and
buttons. Selectable handset types are 3720, 3725, 3740, 3749 or Unknown.
· Enable Provisioning Selected
· IPEI: Default = 0
This field, if set to a value other than 0, sets the IPEI number of the handset that is able to subscribe to the
DECT R4 system using this extension number. The IPEI for each DECT handset is unique.
· Use Handset Configuration: Default = Off.
If Use Handset Configuration. is selected, the handset user is able to set the phone language and date/
time format. If not selected, those settings will be driven by the system or user locale settings in the system
configuration.
Release 9.0
IP Office Manager
Page 346
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: Extension
10.6.6 SIP DECT Base
This tab is displayed for SIP DECT extensions.
Usability
· These settings are not mergeable. Changes to these settings will require a reboot of the system.
Configuration Settings
· DECT Line ID
Use the drop-down list to select the SIP DECT Line from the system to the base station.
Release 9.0
IP Office Manager
Page 347
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.7 User
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 361 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.
Server Edition User Management
In a Server Edition network, individual users are still added to the configuration of a particular server. Typically they are
added to the configuration of the server that hosts the user's physical extension or supports their main place of work.
That server is treated as the host system for the user. However, once a user is added to the configuration of a particular
system, their settings can also be accessed and edited under the Users grouping at the top of the navigation pane of
Manager.
Release 9.0
IP Office Manager
Page 348
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: User
Creating a User Right 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.
Release 9.0
IP Office Manager
Page 349
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.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.
For Server Edition, this type of configuration record can be saved as a template and new records created from a
template. See Templates 78 .
Usability
· Mergeable:
These settings are mergeable. Changes to these settings do not require a reboot of the system.
Configuration Settings
A
symbol indicates that the setting can also be set and locked within a set of user rights 482 with which the user is
associated using the Working Hour User Rights 350 and Out of Hours User Rights 350 settings. The user rights
applied can be controlled by a time profile 452 selected as the user's Working Hours Time Profile 350 setting. The effect
of the user rights can be displayed using the User Rights View 350 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. This field is case sensitive and must be unique.
· Names should not start with a space. Do not use punctuation characters such as #, ?, /, ^, > and ,.
· 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.
· Do not provision a user with the Name "admin". The user name "admin" is a reserved value on the one-X Portal
Instant Message (IM) and Presence server. An IP Office "admin" user will not have IM and presence services.
· For Outbound Contact Express deployments, when an agent logs in to an extension, the user name associated with
the extension is changed to the agent ID.
· Password: Default = Blank. Range = Up to 31 alphanumeric characters.
This password is used by user applications such as 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 354 ) or their phone
log in code (see User | Telephony | Supervisor Settings | Login Code 363 ).
Password complexity rules can be set through the General security settings 180 . If complexity is not met, an error is
displayed. The configuration can still be saved, except if system locale is set to France2.
· Account Status: Default = Enabled.
Use this setting to Enable or Disable a user account.
You can also require a password reset by selecting Force New Password. A user can only set a new password through
the one-X Portal user interface. This option should not be used if one-X Portal is not available.
The Account Status can also be Locked - Password Error or Locked - Temporary. The user account enters these
states automatically based on the password settings configured in the Security Settings General 180 tab. If a user
exceeds the Password Reject Limit, then the Password Reject Action is implemented.
If the Password Reject Action is Log and Disable Account, then the account status is changed to Locked Password Error.
If the Password Reject Action is Log and Temporary Disable, then the account status is changed to Locked Temporary.
· 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.
· Names should not start with a space. Do not use punctuation characters such as #, ?, /, ^, > and ,.
· Extension: Range = 2 to 15 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.
Release 9.0
IP Office Manager
Page 350
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: User
· Centralized users’ extension numbers can be up to 13 digits in length. Although IP Office supports extension
numbers up to 15 digits, the 13-digit length is determined by the maximum extension number length allowed for
provisioning Centralized users in Communication Manager.
· Email Address: Default = Blank
Use this field to enter the user's email address.
· Locale: Default = Blank (Use system locale 201 )
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 998 . 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.
· Priority: Default = 5. Range = 1 (Lowest) to 5 (Highest)
This setting is used by ARS 492 .
· System Phone Rights: Default = None.
This option replaces the System Phone 361 option used on pre-Release 6.0 systems. Users set as a system phone
user are able to access additional functions 547 .
· 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.
A user's profile controls whether they can be configured for a number of features.
Centralized Users are provisioned for enterprise branch deployments. Centralized Users are registered with
Session Manager and are able to utilize telephony features provided by Communication Manager. The Centralized
User profile is applicable to both SIP and analogue extensions. For more information on enterprise branch
deployments, see Deploying IP Office in an Avaya Aura Branch Environment. The following requirements must be met
when provisioning a centralized user:
· An SM line must be configured on the system.
· The user must be provisioned with an existing extension.
· The extension Base Extension value must match the centralized extension value.
· Centralized users must be configured with a password for SIP registration on Session Manager. The password is set
in User | Telephony | Supervisor Settings | Login Code 363 field.
The table below lists the different user profiles and the features accessible by each profile. Setting a user to a
particular profile enables those features by default, however they can be manually disabled if necessary. The number
of users that can be configured for each profile, other than Basic User, is controlled by the user licenses present in
the configuration.
System Type
Standard Mode
Server Edition
User Profile
Basic
User
Office
Worker
Telework
er
Mobile
Worker
Power
User
Basic
User
Office
Worker
Power
User
one-X Portal Services
Yes*
Yes
Yes
–
Yes
–
Yes
Yes
" Telecommuter
options
Yes*
–
Yes
–
Yes
–
–
Yes
Yes*
Yes
Yes
–
Yes
–
Yes
Yes
Yes*
–
–
Yes
Yes
Yes
Yes
Yes
TTS for Email Reading
–
–
–
Yes
Yes
–
–
Yes
IP Office SoftPhone
–
–
Yes
–
Yes
–
–
Yes
–
–
Yes
–
Yes
–
–
Yes
–
Yes
–
–
Yes
–
Yes
Yes
UMS Web Services
Mobility Features
Remote Worker
[2]
[3]
Flare Communicator
for IP Office [4]
1. A Preferred Edition system license is a pre-requisite for any user profile licenses.
Release 9.0
IP Office Manager
Page 351
15-601011 Issue 9.01 (Monday, September 09, 2013)
· For system's upgrade to Release 8.0, user profiles licenses are valid without the need for a
Preferred Edition license. This applies to systems upgraded within the 90-day free upgrade period
for new systems or upgraded with an System Upgrade License.
· In a multi-site network, the Preferred Edition license of the central system is automatically shared
with other systems in the network, enabling user profile licenses on those other systems. However,
each system supporting a Voicemail Pro server still requires its own Preferred Edition license for
Voicemail Pro operation.
2. The mobility features are enabled for all users by the Essential Edition system license.
3. Release 8.0+: The system supports users using remote H.323 extensions 590 . On non-Server Edition
systems, up to 4 Basic users are supported as remote extensions without needing to be licensed, ie. not
configured and licensed for a user profile. Additional remote users are supported if licensed and
configured for either a Teleworker or Power User user profile. On Server Edition systems, remote
workers are supported for users licensed and configured for the Power User user profile.
4. Supported for advanced Flare Communicator for IP Office usage if one-X Portal for IP Office and Voicemail
Pro applications are also installed. If otherwise, only basic Flare Communicator for IP Office usage is
supported. Basic Flare Communicator for IP Office usage can also be enabled for any user profile using a
Avaya Softphone license.
· Receptionist : Default = Off.
This settings allows the user to use the SoftConsole application. This requires the configuration to contain
Receptionist licenses. Up to 4 users can be licensed, 10 for Server Edition systems.
· For Server Edition, the licenses for SoftConsole are only supported in the configuration of the Primary Server
and with users hosted by that server. The use of SoftConsole is not supported for user's who then hot-desk to
other systems in the multi-site network.
· A license is only required when a configured user runs SoftConsole.
· Enable Softphone : Default = Off.
If selected, the user is able to use the IP Office Softphone application.
· Enable one-X Portal Services: Default = Off.
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.
· Enable one-X TeleCommuter:
If selected, the user is able to use the telecommuter mode features of the one-X Portal for IP Office application.
· Enable Remote Worker: Default = Off.
Indicates whether the user is allowed to use an H.323 remote extension 590 . Supported for up to 4 Basic users plus
any users licensed and configured as Teleworker and or Power User user profiles.
· If the user's Extension Number matches the Base Extension setting of an IP extension, the Allow
Remote Extn setting of that extension is automatically changed to match the user's Enable Remote
Worker setting and vice versa.
· Enable Flare: Release 8.1 FP1
This option allows the user to use Flare Communicator for IP Office as their current telephone device. It can be enabled
for users whose Profile is set to Officeworker or Power User. To enable Flare for Basic User, Mobile Worker or
Teleworker, you need the Avaya Softphone license.
· Send Mobility Email: Default = Off
When on, users that are assigned a Profile of Mobile Worker or Power User automatically receive a welcome email
with the following information:
· A brief introduction of one-X Mobile Preferred for IP Office.
· Instructions and links for installing and configuring the one-X Mobile Preferred client.
For more information on installing the one-X Mobile Preferred client, see Avaya one-X Mobile for IP Office
Administration Guide.
· 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.
For users logging on as agents in an Outbound Contact Express deployment, Ex Directory must be Off.
· 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:
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.
Release 9.0
IP Office Manager
Page 352
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: User
· Working Hours Time Profile: Default = <None> (Continuous).
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).
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).
This field allows selection of alternate user rights that are used outside the times defined by the user's Working Hours
Time Profile.
Release 9.0
IP Office Manager
Page 353
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.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.
Usability
· Mergeable:
These settings are mergeable. Changes to these settings do not require a reboot of the system.
Configuration Settings
A
symbol indicates that the setting can also be set and locked within a set of user rights 482 with which the user is
associated using the Working Hour User Rights 350 and Out of Hours User Rights 350 settings. The user rights
applied can be controlled by a time profile 452 selected as the user's Working Hours Time Profile 350 setting. The effect
of the user rights can be displayed using the User Rights View 350 control.
· Voicemail Code: Default = Blank. Range = 0 (no code) to 15 digits.
A code 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.
· The mailbox access code can be set through IP Office Manager or through the mailbox telephone user interface
(TUI). The minimum password length is:
· Voicemail Pro (Manager) - 0
· Voicemail Pro (Intuity TUI) - 2
· Embedded Voicemail (Manager) - 0
· Embedded Voicemail (Intuity TUI) - 0
· 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.
· Manager does not enforce any password requirements for the code if one is set through Manager.
· Embedded Voicemail
For Embedded Voicemail running in IP Office mailbox mode, the voicemail code is used if set.
· 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 359 list.
· 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.
· 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 359 list.
· Call Flow Password Request
Voicemail Pro call flows containing an action where the action's PIN code set to $ will prompt the user for their
voicemail code.
· 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.
· 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.
Release 9.0
IP Office Manager
Page 354
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: User
· Voicemail Help Default = Off
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 351 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. This option is not currently supported with Linux based Voicemail Pro.
· UMS Web Services: Default = Off.
For Server Edition systems this option can be enabled for users whose Profile 351 is set to Office Worker or Power
User. For standalone systems the option can be enabled for users whose Profile 351 is set to Teleworker, Office
Worker or Power User. When selected, the user can use any of the Voicemail Pro UMS services to access their
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 Release 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 supportedand uses the
system's SMTP 244 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. Many email systems impose limits
on emails and email attachment sizes. For example the default limit on an Exchange server is 5MB.
· 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 by Voicemail Pro 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, there is no mailbox synchronization between the
email and voicemail mailboxes. Users can also select this mode by dialing *01 from their extension.
· Note that until email forwarding is completed, the message is present in the voicemail server mailbox and so
may trigger features such as message waiting indication.
· UMS Exchange 2007
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.
Release 9.0
IP Office Manager
Page 355
15-601011 Issue 9.01 (Monday, September 09, 2013)
· 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.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 491 .
· The Park & Page feature is supported when the system voicemail type is configured as Embedded Voicemail
or Voicemail Pro. Park & Page is also supported on systems where Avaya Aura Messaging, Modular
Messaging over SIP, or CallPilot (for IP Office Aura Edition with CS 1000 deployments) is configured as the
central voice mail system and the local Embedded Voicemail or Voicemail Pro provides auto attendant
operation. The Park & Page feature allows a call to be parked while a page is made to a hunt group or
extension. This feature can be configured for Breakout DTMF 0, Breakout DTMF 2, or Breakout DTMF 3.
· 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 in IP Office mode).
· For voicemail systems set to Intuity emulation mode, the mailbox owner can also access this option when
collecting their messages by dialing *0.
· If the mailbox has been reached through a Voicemail Pro 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.
· When Park & Page is selected for a DTFM breakout, the following drop-down boxes appear:
· Paging Number – displays a list of hunt groups and users (extensions). Select a hunt group or
extension to configure this option.
· Retries – the range is 0 to 5. The default setting is 0.
· Retry Timeout – provided in the format M:SS (minute:seconds). The range can be set in 15-second
increments. The minimum setting is 15 seconds and the maximum setting is 5 minutes. The default
setting is 15 seconds
· 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 in IP Office 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 in IP Office mode).
Release 9.0
IP Office Manager
Page 356
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: User
10.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 552 in the Telephone Features section for full details of Do Not Disturb operation.
Usability
· Mergeable:
These settings are mergeable. Changes to these settings do not require a reboot of the system.
Configuration Settings
A
symbol indicates that the setting can also be set and locked within a set of user rights 482 with which the user is
associated using the Working Hour User Rights 350 and Out of Hours User Rights 350 settings. The user rights
applied can be controlled by a time profile 452 selected as the user's Working Hours Time Profile 350 setting. The effect
of the user rights can be displayed using the User Rights View 350 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 1000
when off hook. 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.
Release 9.0
IP Office Manager
Page 357
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.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 703 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.
Usability
· Mergeable:
These settings are mergeable. Changes to these settings do not require a reboot of the system.
Configuration Settings
A
symbol indicates that the setting can also be set and locked within a set of user rights 482 with which the user is
associated using the Working Hour User Rights 350 and Out of Hours User Rights 350 settings. The user rights
applied can be controlled by a time profile 452 selected as the user's Working Hours Time Profile 350 setting. The effect
of the user rights can be displayed using the User Rights View 350 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.
· *DCP
Short codes of this form are often inserted by the system. They are used by some phone types to contain settings
relating to functions such as ring volume and auto answer. Deleting such short codes will cause related phone settings
to return to their defaults.
· *DCP/Dial/8xxxxxxx, 0, 1, 1, 0/0
For system's with TCM phone ports, when a phone is first connected to the port, the button programming of the
associated user is overwritten with the default button programming appropriate for the phone model. Adding the
above short code prevents that behavior if not required, for example if a pre-built configuration including user
button programming is added to the system before the connection of phones.
Release 9.0
IP Office Manager
Page 358
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: User
10.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.
Usability
· Mergeable:
These settings are mergeable. Changes to these settings do not require a reboot of the system.
User Source Numbers
The following types of records can be added to a user's source numbers:
· BST_MESSAGE_FOR_YOU
If set, then the BST phone user sees the top line Message for you or Messages for you, indicating that voicemail
messages are present.
· BST_NO_MESSAGE_FOR_YOU
If set, the user does not see a message indication when the NoUser setting BST_MESSAGE_FOR_YOU is set. The
user's phone presents the idle date/time in the normal fashion.
· V<Caller's ICLID>
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 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 403 tab.
· P<Telephone Number>
This record 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.
· 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
571
operation for the user.
NoUser User Source Numbers
The following source numbers can also be used on the Source Numbers tab of the NoUser 549 user. These affect all
users on the system. Note that changes to these source numbers require a reboot of the system to become effective.
· ALLOW_5410_UPGRADES
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 IP Office Installation manual for full details.
· BST_MESSAGE_FOR_YOU
If set, all BST phones display the top line Message for you or Messages for you, indicating that voicemail messages
are present.
· DECT_REVERSE_RING
By default, when this parameter is not set, calls on DECT phones associated with a CTI application will ring as a Priority
call. When this parameter is set, DECT phones ring as a normal, external or internal, call.
· DISTINCT_HOLD_RINGBACK
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.
Release 9.0
IP Office Manager
Page 359
15-601011 Issue 9.01 (Monday, September 09, 2013)
· FORCE_HANDSFREE_TRANSFER
If set, when using the handsfree announced transfer 569 process, both the transfer enquiry and transfer completion
calls are auto-answered. Without this setting only the transfer enquiry call is auto-answered.
· 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
and 9600 Series phones.
532 .
Not supported for 1600
· NO_DIALLED_REF_EXTERNAL
On outgoing external calls made using short codes to dial the full number, only the short code dialed is displayed on
the dialing user's phone and any directory matching is based on that number dialled. On systems with this source
number added to the configuration, after dialing a short code the full number dialled by that short code is shown and
directory matching is based on that full number.
· ProgressEndsOverlapSend
See Line | VoIP 302 .
· SIP_OPTIONS_PERIOD=X (X = time in minutes)
The system sends SIP options messages periodically to determine if the SIP connection is active. See Options
Operations 319 for information on when SIP options messages are sent.
The rate at which the messages are sent is determined by the combination of the Binding Refresh Time (in seconds)
set on the Network Topology 209 tab and the SIP_OPTIONS_PERIOD parameter (in minutes). The frequency of
sent messages is determined as follows:
· If no SIP_OPTIONS_PERIOD parameter is defined and the Binding Refresh Time is 0, then the default value of
300 seconds is used.
· To establish a period less than 300 seconds, do not define a SIP_OPTIONS_PERIOD parameter and set the
Binding Refresh Time to a value less than 300 seconds. The OPTIONS message period will be equal to the
Binding Refresh Time.
· To establish a period greater than 300 seconds, a SIP_OPTIONS_PERIOD parameter must be defined. The
Binding Refresh Time must be set to a value greater than 300 seconds. The OPTIONS message period will be the
smaller of the Binding Refresh Time and the SIP_OPTIONS_PERIOD.
· VM_TRUNCATE_TIME=X (Range X = 0 to 7 seconds)
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 server how much to remove
from the end of the recording in order to remove the busy tone segment. This amount varies by system locale 998 , 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
The number of milliseconds to wait before cutting through the audio to Voicemail. Some delay is required to allow for
codec negotiation.
Release 9.0
IP Office Manager
Page 360
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: User
10.7.6 Telephony
This form allows you to set telephony related features for the user. These override any matching setting in the System |
Telephony 219 tab. The settings are grouped into a number of sub-tabs.
10.7.6.1 Call Settings
For details of the ringing tones, see Ring Tones
Telephony 219 tab.
543 .
DefaultRing uses the system default setting set through the System |
Usability
· Mergeable:
These settings are mergeable. Changes to these settings do not require a reboot of the system.
Configuration Settings
A
symbol indicates that the setting can also be set and locked within a set of user rights 482 with which the user is
associated using the Working Hour User Rights 350 and Out of Hours User Rights 350 settings. The user rights
applied can be controlled by a time profile 452 selected as the user's Working Hours Time Profile 350 setting. The effect
of the user rights can be displayed using the User Rights View 350 control.
· Outside Call Sequence: Default = Default Ring (Use system setting 219 )
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 219 )
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 219 )
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 219 ). 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 during which the user is treated as still being busy. During this
time:
· Other phones or applications monitoring the user's status will indicate the user as still being busy (on a call).
· Hunt group calls will not be presented to the user.
· If the user is using a single line set, direct calls also receive busy treatment. If the user is using a mutli-line set
(multiple call appearances), direct calls to them will ring as normal.
· 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
should be used.
363
(User | Telephony | Supervisor Settings
363 )
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.
· 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.
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.
Release 9.0
IP Office Manager
Page 361
15-601011 Issue 9.01 (Monday, September 09, 2013)
· 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 391 . Call
waiting should not be used for fax and modem devices.
· Answer Call Waiting on Hold: 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.
· Busy on Held: Default = On
If on, when the user has a call on hold, new calls receive busy treatment. They will follow the user's 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 the feature off 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.
·
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) 339 to Quiet Handset is recommended.
339
(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.
Release 9.0
IP Office Manager
Page 362
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: User
10.7.6.2 Supervisor Settings
These settings relate to user features normally only adjusted by the user's supervisor.
Usability
· Mergeable:
These settings are mergeable. Changes to these settings do not require a reboot of the system.
Configuration Settings
A
symbol indicates that the setting can also be set and locked within a set of user rights 482 with which the user is
associated using the Working Hour User Rights 350 and Out of Hours User Rights 350 settings. The user rights
applied can be controlled by a time profile 452 selected as the user's Working Hours Time Profile 350 setting. The effect
of the user rights can be displayed using the User Rights View 350 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 entry must be at least 4 digits for DS port users. Login codes of up to 15 digits are supported
with Extn Login 869 buttons 869 . Login codes of up to 31 digits are supported with Extn Login 751 short codes 751 .
Centralized users use the Login Code for SIP registration on Session Manager.
· 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.
· 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. Hot desking is not supported for centralized users.
· Users can only log out if they have a Login Code set.
· Supports the short code feature Change Login Code
·
732 .
Users can log out without having a Login Code set if they are currently logged in at an extension whose Base
Extension Number 337 (Extension | Extn) 337 no longer matches their own Extension 350 (User | User) 350 .
· If the user has a login code set, it is used by the Outgoing Call Bar Off
767
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 906 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
723 .
· Coverage Group: Default = <None>.
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 525 .
· Status on No Answer: Default = Logged On.
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 391 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.
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.
Release 9.0
IP Office Manager
Page 363
15-601011 Issue 9.01 (Monday, September 09, 2013)
· 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. .Release 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 479 .
· Incoming Call Bar: Default = Off
When enabled, this setting stops a user from receiving any external calls. On the calling phone, the call is rejected.
· 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 outgoing call
bar: Outgoing Call Bar On 767 , Outgoing Call Bar Off 767 and Change Login Code 732 .
· Inhibit Off-Switch Forward/Transfers: Default = Off.
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 565 .
· Can Intrude: Default = Off
Check this option if the user can join or interrupt other user's calls using call intrusion
conferencing.
533
methods other than
· Cannot be Intruded: Default = On
If checked, this user's calls cannot be interrupted or acquired by other internal users using call intrusion 533 . For users
with Cannot Be Intruded off, private call 536 can be used to indicate whether a call can be intrude or not.
· Can Trace Calls: Default = Off.
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.
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 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.
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 816 button.
· After Call Work Time (secs): Default = System Default. Range = 0 (No ACW) to 999 seconds.
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 250 is used. A value of 0 disables
the user from using ACW.
· Deny Auto Intercom Calls: Default = Off. Release 8.1 FP1.
When enabled, any automatic intercom calls 550 to the user's extension are automatically turned into normal calls.
Release 9.0
IP Office Manager
Page 364
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: User
10.7.6.3 Multi-line Options
Multi-line options are applied to a user's phone when the user is using an Avaya phones which supports appearance
buttons (call appearance, line appearance, bridged and call coverage). See Appearance Button Operation 938 .
Usability
· Mergeable:
These settings are mergeable. Changes to these settings do not require a reboot of the system.
Configuration Settings
A
symbol indicates that the setting can also be set and locked within a set of user rights 482 with which the user is
associated using the Working Hour User Rights 350 and Out of Hours User Rights 350 settings. The user rights
applied can be controlled by a time profile 452 selected as the user's Working Hours Time Profile 350 setting. The effect
of the user rights can be displayed using the User Rights View 350 control.
· 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 applicable for the user.
· Ring Delay: Default = Blank (Use system setting). Range = 0 (use system setting 219 ) to 98 seconds.
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.
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.
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.
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.
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.
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.
· Answer Pre-Select: Default = Off.
Normally when a user has multiple alerting calls, only the details and functions for the call on currently selected button
are shown. Pressing any of the alerting buttons will answer the call on that button, going off-hook will answer the
currently 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 off-hook. 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.
Release 9.0
IP Office Manager
Page 365
15-601011 Issue 9.01 (Monday, September 09, 2013)
· Reserve Last CA: Default = Off.
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.
· 1400, 1600, 9500 and 9600 Series telephone users can put a call on hold pending transfer if they already have
held calls even if they have no free call appearance button available. See Context Sensitive Transfer 566 .
· Abbreviated Ring:
This option has been replaced by the Attention Ring setting above.
Release 9.0
IP Office Manager
Page 366
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: User
10.7.6.4 Call Log
The system can store a centralized call log 522 for users. Each users' centralized call log can contain up to 30 call records
for user calls. When this limit is reached, each new call records replaces the oldest previous record.
On Avaya phones with a fixed Call Log or History button (1400, 1600, 9500 and 9600 Series), that button can be used
to display the user's centralized call log. The centralized call log is also used for M-Series and T-Series phone. 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 used if the user logs into one-X Portal for IP Office.
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 network.
Usability
· Mergeable:
These settings are mergeable. Changes to these settings do not require a reboot of the system.
Configuration Settings
A
symbol indicates that the setting can also be set and locked within a set of user rights 482 with which the user is
associated using the Working Hour User Rights 350 and Out of Hours User Rights 350 settings. The user rights
applied can be controlled by a time profile 452 selected as the user's Working Hours Time Profile 350 setting. The effect
of the user rights can be displayed using the User Rights View 350 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 228 (System | Telephony | Call Log 228 ). 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 records after (hours:minutes): Default = 00:00 (Never).
If a time period is set, records 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 219
(System | Telephony | Call Log) 219 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.
Release 9.0
IP Office Manager
Page 367
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.7.6.5 TUI
· Features Menu Controls
· User Setting: Default = Same as System
When set to Custom, the Features Menu list is enabled.
· Features Menu: Default = On
When set to off, TUI feature menus are not available.
When set to on, you can select to turn individual feature menus off or on. The following feature menus are listed:
· Basic Call Functions (Transfer to Mobile, Pickup, Park)
· Advanced Call Functions (Do Not Disturb, DNS Exceptions, Account Code)
· Forwarding
· Hot Desk Functions
· Passcode Change
· Phone Lock
· Self Administration
· Voicemail Controls
For information on telephony features, see the IP Office Product Description.
Release 9.0
IP Office Manager
Page 368
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: User
10.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 363 (User |
Telephony | Supervisor Settings 363 ) option should be selected. To bar all users from forwarding calls to external
numbers the Inhibit Off-Switch Forward/Transfers 219 (System | Telephony | Telephony 219 ) 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.
Usability
· Mergeable:
These settings are mergeable. Changes to these settings do not require a reboot of the system.
Configuration Settings
A
symbol indicates that the setting can also be set and locked within a set of user rights 482 with which the user is
associated using the Working Hour User Rights 350 and Out of Hours User Rights 350 settings. The user rights
applied can be controlled by a time profile 452 selected as the user's Working Hours Time Profile 350 setting. The effect
of the user rights can be displayed using the User Rights View 350 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 1000 when off hook. For
further details see Follow Me 554 .
· 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 1000 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.
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, 9500 and 9600 Series phone users can select this setting through
the phone menu. Note that if the user disables forward unconditional 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 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.
Release 9.0
IP Office Manager
Page 369
15-601011 Issue 9.01 (Monday, September 09, 2013)
· Forward Internal Calls: Default = On.
This option, when checked, sets that internal calls should be also be forwarded immediately when forward
unconditional is active.
· 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 361 (User | Telephony | Call Settings 361 ). 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.
When checked, this option sets that internal calls should be also be forwarded when forward on no answer or
forward on busy is active.
Release 9.0
IP Office Manager
Page 370
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: User
10.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.
Usability
· Mergeable:
These settings are mergeable. Changes to these settings do not require a reboot of the system.
Configuration Settings
· Dial In On: Default = Off
When enabled, dial in access into the system is available via this user.
· Dial In Time Profile: Default = <None>
Select the Time Profile 452 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 453 to restrict access to the system via this User account. If blank, there are no Dial In
restrictions.
Release 9.0
IP Office Manager
Page 371
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.7.9 Voice Recording
This tab is used to activate the automatic recording of user's external calls. The recording of internal calls 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.
· Note the following:
· 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.
Usability
· Mergeable:
These settings are mergeable. Changes to these settings do not require a reboot of the system.
Configuration Settings
· 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 Time Profile: Default = <None> (Any time)
Used to select a time profile 452 during which automatic call recording of outgoing calls is applied. If no profile is
selected, automatic recording of outgoing calls is active at all times.
· 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 452 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:
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.
· Voice Recording Library Authenticated:
This option is similar to Voice Recording Library above but instructs the voicemail server to create an
authenticated recording. If the file contents are changed, the file is invalidated though it can still be played.
· Auto Record Calls: Default = External.
This setting allows selection of whether External or External & Internal calls are subject to automatic call
recording.
Release 9.0
IP Office Manager
Page 372
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: User
· 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.
· Voice Recording Library:
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.
· Voice Recording Library Authenticated:
This option is similar to Voice Recording Library above but instructs the voicemail server to create an
authenticated recording. If the file contents are changed, the file is invalidated though it can still be played.
Release 9.0
IP Office Manager
Page 373
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.7.10 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 793 .
· 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.
Usability
· Mergeable:
These settings are mergeable. Changes to these settings do not require a reboot of the system.
Configuration Settings
A
symbol indicates that the setting can also be set and locked within a set of user rights 482 with which the user is
associated using the Working Hour User Rights 350 and Out of Hours User Rights 350 settings. The user rights
applied can be controlled by a time profile 452 selected as the user's Working Hours Time Profile 350 setting. The effect
of the user rights can be displayed using the User Rights View 350 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
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 805
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.
Release 9.0
IP Office Manager
Page 374
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: User
10.7.11 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.
10.7.11.1 T3 Telephony
These settings are applied to the user when they are using a T3 phone.
Usability
· Mergeable:
These settings are mergeable. Changes to these settings do not require a reboot of the system.
Configuration Settings
· 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.
This setting is used to control whether the user sees ISDN AOC information when using a T3 phone.
· Allow Self Administer: Default = Off.
If selected, this option allows the user to self-administer button programming.
10.7.11.2 Huntgroup
Avaya T3, 1400, 1600, 9500 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.
Usability
· Mergeable:
These settings are mergeable. Changes to these settings do not require a reboot of the system.
Configuration Settings
· 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: 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).
· 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.
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.
If selected, the user can change the fallback group used when the hunt group is in Out of Service mode.
Release 9.0
IP Office Manager
Page 375
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.7.11.3 1400/1600
This menu applies to 1400, 1600, 9500 and 9600 Series phones.
Configuration Settings
· Include Forwarding in Menu: Default = On. Release 5.0+.
This setting controls whether the user is able to view and use options to control their forwarding within the phone's
menus.
10.7.11.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.
Usability
· Mergeable:
These settings are mergeable. Changes to these settings do not require a reboot of the system.
Configuration Settings
· Menu No.
The menu position which the function is being set.
· Label
This is a text label for display on the phone. If no label is entered, the default label for the selected action is used.
Labels can also be changed through the menu on some phones, refer to the appropriate telephone user guide.
· Action 805
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.
Release 9.0
IP Office Manager
Page 376
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: User
10.7.12 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
No
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.
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.
· Logging out or setting do not disturb at the secondary only affects the secondary.
· Do Not Disturb Exceptions List
For both types of twinning, when DND is selected, calls from numbers entered in the user's Do Not Disturb
Exception List 357 are presented to both the primary and secondary phones.
Release 9.0
IP Office Manager
Page 377
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.7.12.1 Internal Twinning
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 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.
The following applies to internal twinned extensions:
· If using a T3, 1400, 1600, 9500 or 9600 Series phone as the secondary extension:
· The secondary extension's directory/contacts functions access the primary user's Centralized Personal
Directory 521 records in addition to the Centralized System Directory 517 .
· 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.
522 .
522 .
Note: The list mode
· It is also shown on 3700 Series phones on a DECT R4 system installed using system provisioning .
· 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.
Release 9.0
IP Office Manager
Page 378
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: User
Usability
· Mergeable:
These settings are mergeable. Changes to these settings do not require a reboot of the system.
Configuration Settings
· Internal Twinning:
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 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.
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.
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.
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.
Release 9.0
IP Office Manager
Page 379
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.7.12.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.
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
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 if the user's Forwarded Calls Eligible for Mobile Twinning setting is enabled.
· Hunt group calls except 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.
Usability
· Mergeable:
These settings are mergeable. Changes to these settings do not require a reboot of the system.
Configuration Settings
A
symbol indicates that the setting can also be set and locked within a set of user rights 482 with which the user is
associated using the Working Hour User Rights 350 and Out of Hours User Rights 350 settings. The user rights
applied can be controlled by a time profile 452 selected as the user's Working Hours Time Profile 350 setting. The effect
of the user rights can be displayed using the User Rights View 350 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 Release 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.
Release 9.0
IP Office Manager
Page 380
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: User
· For Release 6.0, this option can be enabled for users whose Profile 351 is set to Teleworker or Power User.
For systems upgraded to Release 6.0 with existing UMS Web Service licenses, those licenses can be used
with users whose Profile is set to Basic User.
· mobility features are enabled for all users by the Essential Edition system license.
· Mobile Twinning:
If selected, the user is enable for mobile twinning. The user can control this option through a Twinning
programmable button on their a phone.
924
· 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 Mobile Call Control 512 , 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.
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.
· 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.
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. (IP500/IP500 V2 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.
Release 9.0
IP Office Manager
Page 381
15-601011 Issue 9.01 (Monday, September 09, 2013)
· Mobile Call Control: Default = Off. (IP500/IP500 V2 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 512 .
· Mobile Callback : Default = Off. (IP500/IP500 V2 digital trunks only).
Mobile callback 515 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.
Release 9.0
IP Office Manager
Page 382
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: User
10.7.13 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.
Release 9.0
IP Office Manager
Page 383
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.7.14 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 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 214 .
· 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 1055 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 770 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#.
Usability
· Mergeable:
These settings are mergeable. Changes to these settings do not require a reboot of the system.
Configuration Settings
· 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.
· 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 1055 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.
545 ,
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.
Release 9.0
IP Office Manager
Page 384
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: User
· 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.
Release 9.0
IP Office Manager
Page 385
15-601011 Issue 9.01 (Monday, September 09, 2013)
10.7.15 SIP
This tab is available when a SIP trunk with a SIP URI 322 record has been added to the configuration. It is also available
when an H.323 trunk 299 set to IP Office SCN or IP Office SCN - Fallback has been added to the 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 multi-site
network, that includes calls which break out using a SIP trunk on another system within the network.
Usability
· Mergeable:
These settings are mergeable. Changes to these settings do not require a reboot of the system.
Configuration Settings
· SIP Name: Default = Blank on Voicemail tab/Extension number on other tabs.
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 = Blank on Voicemail tab/Name on other tabs.
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 = Blank on Voicemail tab/Extension number on other tabs.
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 = On on Voicemail tab/Off on other tabs.
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.
Release 9.0
IP Office Manager
Page 386
15-601011 Issue 9.01 (Monday, September 09, 2013)
Configuration Mode Field Descriptions: User
10.7.16 Personal Directory
Each user is able to have up to 100 personal directory records, up to the overall system limit as follows:
IP Office
Total User Directory Records
Server Edition
10800
IP500/IP500 V2
10800
These records are used as follows:
· When using ETR, M-Series, T-Series, T3, 1400, 1600, 9500 or 9600 Series phones, the user is able to view and call
their personal directory numbers.
· When using a 1400, 1600, 9500 or 9600 Series phone, the user is also able to edit and add personal directory
records.
· If the user hot desks to a T3, 1400, 1600, 9500 or 9600 Series phone on another system in a multi-site network, they
can still access their personal directory.
Users are able to view and edit their personal directory through their phone.
Directory records are used for two types of function:
· Directory Dialing
Directory numbers are displayed by user applications such as SoftConsole. Directory numbers are viewable
through the Dir 865 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 records 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 records from the system configuration. This includes HTTP and LDAP imported records.
· Groups
Groups on the system. If the system is in a multi-site network, it will also include groups on other
systems in the network. For pre-Release 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 multi-site network it will also include users on other systems in
the network.
· Personal
Available on T3, T3 IP, 1400, 1600, 9500 and 9600 Series phones. These are the user's personal
directory records stored within the system configuration.
· Speed Dialing
On M-Series and T-Series phones, a Speed Dial 916 button or dialing Feature 0 can be used to access
personal directory records with an index number.
· Personal: Dial Feature 0 followed by * and the 2-digit index number in the range 01 to 99.
· System: Dial Feature 0 followed by 3-digit index number in the range 001 to 999.
·
The Speed Dial 916 short code feature can also be used to access a directory speed dial using its index
number from any type of phone.
· Caller Name Matching
Directory records 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 user's personal directory overrides any
match in the system directory. Note that some user applications also have their own user directory.
· 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.
On SIP tr