Aeonix

Administration Manual

Version 5.1

Document Edition 7.3

The information contained in this document is proprietary and is subject to all relevant
copyright, patent and other laws protecting intellectual property, as well as any specific
agreement protecting TADIRAN TELECOM (TTL) L.P.'s (herein referred to as the
"Manufacturer") rights in the aforesaid information. Neither this document nor the information
contained herein may be published, reproduced or disclosed to third parties, in whole or in part,
without the express, prior, written permission of the Manufacturer. In addition, any use of this
document or the information contained herein for any purposes other than those for which it
was disclosed is strictly forbidden.

The Manufacturer reserves the right, without prior notice or liability, to make changes in
equipment design or specifications.

Information supplied by the Manufacturer is believed to be accurate and reliable. However, no

responsibility is assumed by the Manufacturer for the use thereof nor for the rights of third
parties which may be affected in any way by the use thereof.

Any representation(s) in this document concerning performance of the Manufacturer's

product(s) are for informational purposes only and are not warranties of future performance,
either express or implied. The Manufacturer's standard limited warranty, stated in its sales
contract or order confirmation form, is the only warranty offered by the Manufacturer in
relation thereto.

This document may contain flaws, omissions or typesetting errors; no warranty is granted nor
liability assumed in relation thereto unless specifically undertaken in the Manufacturer's sales
contract or order confirmation. Information contained herein is periodically updated and
changes will be incorporated into subsequent editions. If you have encountered an error, please
notify the Manufacturer. All specifications are subject to change without prior notice.

© Copyright by TADIRAN TELECOM (TTL) L.P., 2012-2020.

All rights reserved worldwide.

All trademarks contained herein are the property of their respective holders.
 Disclaimer
The illustrations and other views, telephone displays or screen captures appearing in this
manual are examples used to explain more clearly, how the features and controls are used.
Therefore, what appears on the display or screen capture in the illustrations may differ from
what appears on the actual equipment, and some of the illustrations may represent something
impossible in actual operation. The functions that can be used and the information that can be
displayed will differ depending on the telephony state and external equipment being connected.
The names of companies, products, people, characters, and/or data mentioned herein are
fictitious and are in no way intended to represent any real individual, company, product, or
event, unless otherwise noted.
 Record of Changes
Edition
Issue Date Brief Description
No.

7.3 Sept-26-2019 Aeonix Version 5.1: Multi-Tenant.

7.2 Sept-12-2019 Aeonix Version 4.2: Re-merged A4C callouts from Version 3.2
SP1 (skipped Version 4.1).
7.1 July-7-2019 Aeonix Version 4.2: NIC Bond Support; Alarm for Port
Disconnect; Default Password Indication; Keep Alive
Unregistered Trunks; DTMF Functions for Touch; Aeonix
Codecs; Services Directory for Touch; Network Sniffer and
Memory Dump Logs.
7.0 Dec-10-2018 Aeonix Version 4.1: RoD Using SeaMail; Programmed Phone
Button Sync; improved ELIN and LLDP descriptions; Admin
Password Policy Alarms.
6.9 Aug-1-2018 Aeonix Version 4.0: Small edits and corrections.
6.8 June-19-2018 Aeonix Version 4.0: BLF on Trunk; Call Duration; Camp on
Busy; ELIN by LLDP; Dial Lock; Provisioning Profiles.
6.7 Mar-15-2018 Aeonix Version 3.2 SP1: Persistent Media option for SIP trunks.
Recommend to physically remove a server from network that has
been deleted from a cluster. Recall on hold timeout supported
through Aeonix on MGCP, not SIP. Single Sign On (SSO).
6.6 Dec-28-2017 Aeonix Version 3.2: T27G, T41S, T46S, T48S Phones; Aeonix
SIP Phones Firmware Update; TGW24-3G Gateway; TGW Plug
and Play Deployment; Aeonix Contact Center - Record on
Demand; Aeonix Call Accounting - Version 11; Aeonix License
Management Improvements; Aeonix Upgrade Procedure
Improvements; Aeonix Server Cluster Management
Improvements; Aeonix Logs Management Improvements;
Aeonix Alarms Reporting Improvements; Aeonix LDAP
Integration.
6.5 Aug-10-2017 Aeonix Version 3.1: 20 servers per cluster removed Limit of 25
members in a ULA Group (not 50). E911 alarms. Alarm: Non-
Tadiran MAC detected.
 Record of Changes
Edition
Issue Date Brief Description
No.
6.4 Apr-13-2017 Aeonix Version 3.1: IPv6, E911.
6.3 Jan-19-2017 Aeonix Version 3.0: Aeonix Touch (user email for, mobile next
version, and more info pop-up), Aeonix Contact Center HA
modes
6.2 Dec-28-2016 Aeonix Version 3.0: Survivability mode warning, Aeonix Touch
desktop softphone and mobile authorization, user licensing,
additional provisioning parameters for LDAP directory, non-
ACC calls not rejected on DND, layer 3 QoS notes, Room
Recording, Auto Camp-on DSS button, Maintenance Tool
upgrade and rollback for Aeonix Contact Center and SeaMail,
Show ELIN on emergency calls note removed, Trunk group
prefix removed, Maximum simultaneous firmware upgrades,
Aeonix Configuration Wizard State and Province, provisioning
profile location for Aeonix Touch devices, Aeonix Touch MSI
download, enduser Aeonix Contact Center client download,
enduser FLIPS download, enduser TAPI and DialIt download,
enduser Aeonix Touch download
6.1 Aug-22-2016 Aeonix Version 3.0: Staging license key, Allow paging note,
user profile for outgoing external calls for ACC and virtual
endpoints, Ignore incoming routing rules for ULA members,
Trusted IP addresses for Action URI, Wave Gateway cluster
survivability mode, Trunk group prefix, Headset only mode for
FlexSet phone users via the Wave Gateway, Provisioning profile
parameter applicability, Tadiran SIP phones speed dial presence
 Record of Changes
Edition
Issue Date Brief Description
No.
6.0 July-07-2016 Aeonix Version 3.0: Default internal aliases, Aeonix Contact
Center server alarm, multi-language announcers, user email, user
login name, display in directory, restrict direct call pickup, Allow
Paging, Ring Control, Use by App, Force Logout, Enabling ACD
and Hunt Working Modes removed, Late media support,
Misdialed calls destination, Trunk group members sort, Disable
call waiting tone on MGCP & FlexSet, During transfer force call
waiting on destination side, Layer 3 QoS Handling, show ELIN
on emergency calls, Trunk Group transferred calls, Interdigit
timeout other provisioning parameter, User profile photo, Aeonix
directory, Aeonix Touch, Aeonix Maintenance Tool feature
overview, Multi-function speed dialing button programming,
Multi-device call pickup, Aeonix Installation Wizard, MGCP
terminal removed, Silent monitor on multi-device, Aeonix
Contact Center service, Page Queue timeout, Default language
removed from System Parameters, Online CDR Server
Configuration alarm, Tadiran SIP phones Plug and Play, export
users, set default user, T19P E2 phones, Forwarding DSS button,
Camp-on DSS button, TGW gateways, T29G phones, Back
button, Pickup blinking Speed Dial, Ignore incoming routing
rules of ULA members, Wave Gateway survivability, Support
RFC 2833 for ACD & Hunt group announcers, Direct Call
Transfer Setup for Aeonix Touch Users, Send IM to SIP phones
5.5 May-23-2016 Aeonix Version 2.5: Aeonix Installation Wizard (SE), minor
changes
5.4 Mar-20-2016 Aeonix Version 2.5: Display/First/Last name behavior, ESF
protocol other provisioning parameter, Wave Gateway updates,
check out note, non-Tadiran users, minor changes
5.3 Feb-03-2016 Aeonix Version 2.5: T49, Trunk registration statuses changes
5.2 Jan-28-2016 Aeonix Version 2.5: Enable fax, ANI restriction change
 Record of Changes
Edition
Issue Date Brief Description
No.
5.1 Jan-18-2016 Aeonix Version 2.5: Show ELIN on emergency calls, Trunk
Group transferred calls, TLS/SRTP Handling for SIP Trunks,
Maximum 8 servers per cluster, EXP20 for T27P phones,
provisioned dial now rules, logout disabled after emergency call,
TLS provisioning with port 5061, DNS SRV Query Handling for
SIP Trunks
5.0 Aug-24-2015 Aeonix Version 2.5: Page Queue DSS button, Not provisionable
programmable button, DTMF support for alarm console,
External phone, Call Recording - Aeonix Contact Center agent
range, changes to Trunk registration status icons, simplified
entity creation (and cloning), 911 emergency callback, Importing
/ Exporting Trunk Group Call Routing Rules, Adding Variables
for User Manipulation Rule Actions, T21P E2, T23G and T27P,
LDAP Connection Base DN field size, Unblock SIP phones,
CDR receipt acknowledgment, Hospitality permissions, ESF
protocol, standalone SeaMail removed, TLS/SRTP Handling for
SIP Trunks, EXP20 for T27P phones
4.6 May-26-2015 Aeonix Version 2.4: Everyone can initiate incoming external call
to start Zone Page, copy ADC profile, cannot delete default ADC
profile, can copy default ADC profile, UCx not part of Wave
Gateway systems, Aeonix Maintenance Tool download, Offset
time from GMT other provisioning parameter
4.5 April-02-2015 Aeonix Version 2.4: Aeonix Logger updates (sticky recording
mode, no conference entity, wildcards, ROD not persistent, non-
sticky mode (note), recording centers displayed,
AeonixLoggerTKGrp trunk group associated with all recording
servers, 1000 BRE rules, ACC agent recorded on logout), 3 new
cluster alarms, cluster enhancements
4.4 Mar-08-2015 Remove G.723, Room Status 1-16, ULA for SIP phones, Tadiran
SIP phones, record on demand feature code (default 1443),
voicemail keep alive timeout, Aeonix Logger alarms, hyphen
wildcard removed, new Tadiran logo
 Record of Changes
Edition
Issue Date Brief Description
No.
4.3 Dec-14-2014 Invite timeout, Trunk user name / password for all registration
options, LCD logo mode for T19P and T48G, Send Start Call
Detail Record, External members for conference calls and zone
pages, Dial Out 9 select or clear both for provisioned SIP phones,
Aeonix licensing application error messages, Enable fax
capabilities, provisioning profile parameters configured from
other pages, check boxes removed from User page, ACD & Hunt
tab, Add outside line access code prefix, conference call LED
behavior, BRE wildcards, Support base port for Coral Version
14.67.x and Base port removed from IPnet trunk configuration,
alarms sorted by time, phone search criteria, specific ACD/Hunt
main and back up servers, ANI and DNIS Chain Manipulation
for Trunk Groups, Restricted or Empty ANI Number Conditions
for Trunk Groups, ARS table for voicemail service, TAPI Service
Provider and DialIt Application Download
4.2 Oct-30-2014 Server Alarms what to do, Call Forward to external number
blocked, Request to Speak During Aeonix Conference Call, first
three ACD/Hunt overflow defaults Put in queue, Non-ACD calls
note, T19P
4.1 Aug-18-2014 Aeonix Logger (Call Recording), Auto-refresh notes, changes to
Wave Gateway List page, button programming icons, external
music source alarm, dispatch console status, voicemail status,
status icon tooltip notes, rule list search / filter, Micros (Fidelio /
Opera) and Silverbyte PMS integration, VLAN Network Phone
Provisioning Parameters, Longest time in IDLE for Hunt Group
removed, High availability retry count, Reject call for Hunt and
ACD services, Wave Gateway Alarms tab, T48G, ACD / Hunt
Intervals & Timeouts moved to separate Parameters tab, delete
current alarms
 Record of Changes
Edition
Issue Date Brief Description
No.
4.0 June-30-2014 Aeonix Version 2.4, Hyper-V, Auto Redial, Virtual Endpoint
Overflow tab, Music Service (MoH) from external sources, Flash
Mode (Continuous Conference, Swap, Consultation), SIP
admission control, Split Silent Monitoring, Zero Effort
Licensing, High Availability legend, Prevent Upgrade without
License Support, Dial Out 9, Group Listening (Combined
Audio), Site Name displayed at top of web pages, SIP Phone
Blocked from Registering Icon, Conference Call Announcers tab,
Call Forward No Answer Timeout limit, Toll Barriers assigned to
trunk groups, Schedules removed for trunk groups, changes to
Alarms Configuration, new alarms, SNMP support for NMS
applications, SIP phone password, Dial Out 9, LCD logo mode,
Wave Gateway Alarms tab, Time and Date CDR service, ACD
and Hunt service back up server in cluster config, Toll Barrier
Sub-profile for Trunk Groups
3.1 May-4-2014 Aeonix Version 2.3, Dispatch Console Automatically
Conferences Aliases, Dispatch Console Clone Profile, Dispatch
Console allow Automatic tab selection, Virtual endpoints /
handled by / backed up by, Tadiran SIP phones ESF server,
backup NTP server, HSB now High Availability, embedded
Aeonix Contact Center, secured SIP phones, FlexIP Softphone
client download, Aeonix Contact Center Visor and Agent clients
download, LSAS support, TLS/SRTP for SIP extensions
 Record of Changes
Edition
Issue Date Brief Description
No.
3.0 Feb-26-2014 Aeonix Version 2.3, Hospitality (Wakeup, Room Status),
Ringback and Waiting tone support (180 - Ringback tone added
and 180+SDP Call progress tone removed for trunks and
gateways), Multi-level Administration, changes to SIP Voicemail
page, Virtual Agents, changes to Trunk List page, changes to
Trunk licenses, changes to Alarms Configuration page, Aeonix
Contact Center clients downloads, MGCP gateways removed,
PMS Connection alarm, Notification Options page updated and
Wave Gateway alarms added, Provisioning FTP server alarm
notification removed, Aeonix Contact Center phone button
features, custom phone firmware, grace period/license/support
warning messages, Add license, Aeonix Contact Center Loggers
license removed, Secured Trunk Group profile, Required security
level for user, Toll barrier profile defaults, Virtual endpoints
servers, Call intrusion tab removed (My Account), ACD & Hunt
Group tab removed (My Account), Support RFC 2833, gif to png
2.3 Jan-14-2014 Aeonix Version 2.2.91, secured SIP phone registration, user
default password, contact center agents without call waiting, dial
plan caution, and trunk group call intrusion tab
2.2 Nov-06-2013 Aeonix Version 2.2, T40 Series (T41P, T42G, T46G), external
sources for announcers removed, ESF (SIP) features, Dispatch
user, CDR service, Virtual Endpoints, phone firmware not
upgradable
2.1 Oct-16-2013 2DT added, Licenses and Glossary updated
2.0 Sept-15-2013 Aeonix Aeonix 2, Update 1
1.4 Mar-20-2013 Auto Provisioning for T300 and P-Series
1.3 Dec-26-2012 Minor changes
1.2 Nov-05-2012 New Look & Feel
1.1 Oct-31-2012 For Beta sites
1.0 Apr-19-2012 Aeonix Version 1.0
 Table of Contents

1 Overview

Introduction to this Manual ........................................................................... 1-1

Intended Audience ................................................................................ 1-1
Document Structure .............................................................................. 1-2
Manual Conventions.............................................................................. 1-3

Introduction to Aeonix .................................................................................. 1-5

About Aeonix ......................................................................................... 1-6
Aeonix Building Blocks .......................................................................... 1-7
Supported Devices .............................................................................. 1-12
Supported Codecs............................................................................... 1-13

Support and Documentation....................................................................... 1-15

Support................................................................................................ 1-16
Upgrading the Aeonix Ecosystem ....................................................... 1-16
Related Documentation ....................................................................... 1-17

2 Aeonix Features

Setting up Aeonix Features .......................................................................... 2-1

Aeonix Contact Center .......................................................................... 2-5
Aeonix Directory .................................................................................... 2-5
Aeonix Logger (Call Recording) ............................................................ 2-6
Aeonix Record on Demand (RoD) with SeaMail) .................................. 2-7
Aeonix Maintenance Tool ...................................................................... 2-7
Aeonix Touch ........................................................................................ 2-8
ANI (Caller ID) Restriction ..................................................................... 2-8
Auto Answer .......................................................................................... 2-8
TOC

Auto Redial............................................................................................ 2-9

Automatic Call Distribution (ACD) and Hunt Groups ............................. 2-9

Aeonix Administration Manual Table of Contents i

 Automatic Database Backup ............................................................... 2-10
Automatic Route Selection (ARS) ....................................................... 2-10
Batch Import of Users.......................................................................... 2-11
Break-in ............................................................................................... 2-11
Break-out ............................................................................................. 2-11
Call Details Records (CDR)................................................................. 2-12
Call Time Limit..................................................................................... 2-12
Call Groups ......................................................................................... 2-12
Call Log ............................................................................................... 2-12
Call Pickup .......................................................................................... 2-12
Call Preemption ................................................................................... 2-13
Call Waiting (Multi-appearance) .......................................................... 2-14
Camp-on.............................................................................................. 2-14
Closed User Groups (CUG) ................................................................ 2-16
Computer Telephony Integration (CTI)................................................ 2-17
Conference Calling .............................................................................. 2-17
Deflect (Divert) Call ............................................................................. 2-18
Dial Lock.............................................................................................. 2-18
Direct Inward Dialing (DID).................................................................. 2-18
Dispatch Console ................................................................................ 2-19
Do Not Disturb (DND).......................................................................... 2-19
Emergency Conference Calling........................................................... 2-20
Enhanced Emergency 911 Call Support (ELIN / LLDP) ...................... 2-21
Enhanced SIP Functionality (ESF) ...................................................... 2-21
FlexiCall............................................................................................... 2-23
FlexIP Softphone ................................................................................. 2-23
Gateways ............................................................................................ 2-24
Group Listening ................................................................................... 2-24
Headset Only Mode............................................................................. 2-24
Hospitality ............................................................................................ 2-25
Hot Station........................................................................................... 2-25
Incoming Call Routing (Call Forwarding and Call Rejection)............... 2-25
Lightweight Directory Access Protocol (LDAP) ................................... 2-26
Login and Logout................................................................................. 2-26
Mobility ................................................................................................ 2-27
Multi-Level Administration ................................................................... 2-27
TOC

Multi-Tenant Mode .............................................................................. 2-28

Music on Hold (MOH) .......................................................................... 2-29

ii Table of Contents Aeonix Administration Manual

 Mute .................................................................................................... 2-29
Network Alarms ................................................................................... 2-30
Outgoing Call Routing (Dialed Number Manipulation) ........................ 2-31
Page Queue ........................................................................................ 2-31
Profile Programming............................................................................ 2-32
Programmable Phone Buttons ............................................................ 2-32
PnP / Provisioning for Tadiran SIP Phones and P-Series Phones...... 2-32
Recall on Transfer ............................................................................... 2-33
Redial .................................................................................................. 2-34
Redundancy ........................................................................................ 2-34
Registration Load Balancing ............................................................... 2-35
Remote Server Maintenance............................................................... 2-35
Reports ................................................................................................ 2-36
Room Recording ................................................................................. 2-36
Schedule Programming ....................................................................... 2-37
Sea Attendant...................................................................................... 2-37
Sea Navigator...................................................................................... 2-39
Silent Monitoring.................................................................................. 2-40
Single Sign On .................................................................................... 2-40
TAPI Service Provider and DialIt ........................................................ 2-41
Timeout Programming ......................................................................... 2-41
Toll Barrier ........................................................................................... 2-41
Transfer ............................................................................................... 2-42
Unified Messaging and Voicemail ....................................................... 2-42
User Line Appearance (ULA) .............................................................. 2-43
User Presentation................................................................................ 2-44
Virtual Endpoints ................................................................................. 2-45
Voice Page .......................................................................................... 2-45
Web Portal........................................................................................... 2-46
Zone Page ........................................................................................... 2-46

3 Getting Started

Aeonix Portal for Administrators................................................................... 3-1

Aeonix Web Page Structure .................................................................. 3-2
Administrator Levels .............................................................................. 3-4
TOC

Aeonix Administration Manual Table of Contents iii

 Basic Tasks .................................................................................................. 3-5
Configuring HTTPS for the Aeonix Web Portal ..................................... 3-6
Logging in to Aeonix .............................................................................. 3-8
Admin Password Policy ....................................................................... 3-10
Accessing Online Help ........................................................................ 3-14
Logging out from the Aeonix Web Portal............................................. 3-14

Initial Aeonix Configuration ........................................................................ 3-17

Aeonix Configuration Wizard ............................................................... 3-18

Licenses ..................................................................................................... 3-29

License Information Page.................................................................... 3-32
License Information ............................................................................. 3-35
Activating the First License ................................................................. 3-40
Activating License Updates Automatically or On-Demand .................. 3-43
Activating Another License Key Server ............................................... 3-46
Adding a License Manually ................................................................. 3-47
Aeonix Licensing and Aeonix Licensing Application Messages .......... 3-52

General Procedures ................................................................................... 3-63

Navigating ........................................................................................... 3-64
Entering Information ............................................................................ 3-64
Saving ................................................................................................. 3-64
Cloning Entities ................................................................................... 3-65
Deleting Entities .................................................................................. 3-66

Aeonix Setup Procedure ............................................................................ 3-67

4 Global Settings

Country-specific Dial Codes ......................................................................... 4-1

Country List Page .................................................................................. 4-2
Defining a Country................................................................................. 4-4

Locations ...................................................................................................... 4-9

Location List Page ............................................................................... 4-10
TOC

Defining a Location.............................................................................. 4-12

Defining Emergency Call Settings ....................................................... 4-16

iv Table of Contents Aeonix Administration Manual

 Assigning a Location to a User............................................................ 4-17

Dial Plans ................................................................................................... 4-19

Dial Plan List Page .............................................................................. 4-20
Defining a Dial Plan ............................................................................. 4-20

Closed User Groups (CUG) ....................................................................... 4-29

Closed User Group Tree Page ............................................................ 4-31
Defining a Closed User Group ............................................................ 4-32
Adding Members to a Closed User Group .......................................... 4-35
Deleting a Closed User Group ............................................................ 4-35

Schedules .................................................................................................. 4-37

Schedule List Page ............................................................................. 4-38
Defining a Schedule ............................................................................ 4-39

Automatic Route Selection (ARS) .............................................................. 4-43

ARS Table List Page ........................................................................... 4-44
Defining an ARS Table ........................................................................ 4-46
Testing an ARS Table ......................................................................... 4-49
Assigning Automatic Route Selection Tables to Users ....................... 4-50
ARS Table Example ............................................................................ 4-50

LDAP Connections ..................................................................................... 4-53

Lightweight Directory Access Protocol (LDAP) ................................... 4-53
LDAP Connection List ........................................................................ 4-54
Defining an LDAP Connection............................................................. 4-55
Testing LDAP Connections Parameters.............................................. 4-61
Synchronizing LDAP Connection Parameters..................................... 4-62
Default LDAP Directory ....................................................................... 4-64

Single Sign On ........................................................................................... 4-67

Single Sign On .................................................................................... 4-67
Deployment and Configuration ............................................................ 4-67
How to Join a Linux Server into an Active Directory Domain .............. 4-72
Configuring ACC for SSO Environment .............................................. 4-77
TOC

Aeonix Administration Manual Table of Contents v

 5 Profiles

Profiles ......................................................................................................... 5-1

Profile Definition Example ..................................................................... 5-2

Managing Sub-profiles ................................................................................. 5-3

Profile List Page for Sub-profiles ........................................................... 5-5
General Information Sub-profiles .......................................................... 5-8
Timeout Sub-profiles ........................................................................... 5-12
Feature Configuration Sub-profiles ..................................................... 5-15
Toll Barrier Sub-profiles....................................................................... 5-24
Schedule Sub-profiles ......................................................................... 5-28
Incoming Call Routing Sub-profiles ..................................................... 5-31
Outgoing Call Routing Sub-profiles ..................................................... 5-41
Administration Level Sub-profiles ........................................................ 5-49
Phone Profiles ..................................................................................... 5-54

Managing Profiles ...................................................................................... 5-83

User and Trunk Group Profile List Pages............................................ 5-84
Defining a User Profile ........................................................................ 5-86
Defining a Trunk Group Profile ............................................................ 5-88

Managing Provisioning Profiles .................................................................. 5-91

Provisioning Profile List Page.............................................................. 5-92
Defining a Provisioning Profile ............................................................ 5-94

6 Managing Users

Users ............................................................................................................ 6-1

User List Page ....................................................................................... 6-2

Defining a User ............................................................................................ 6-9

Defining User Identity Settings ............................................................ 6-14
Uploading a User Profile Photo ........................................................... 6-18
Assigning Aliases to Users .................................................................. 6-19
Managing Voicemail Boxes for Users ................................................. 6-24
TOC

Specifying External Phone Numbers................................................... 6-27

Overriding User Profiles ...................................................................... 6-29

vi Table of Contents Aeonix Administration Manual

 Configuring a User’s Phone Profiles ................................................... 6-49
Managing a User’s Phones ................................................................. 6-56
Configuring Mobility Rules for a User .................................................. 6-62
Managing a User’s ULA Settings ........................................................ 6-65
Setting the Meet-me Conference Access Code .................................. 6-72
Resetting a User’s Password .............................................................. 6-73
Viewing ACD and Hunt Group Membership ........................................ 6-74
Defining Permission Settings .............................................................. 6-74

Importing / Exporting Users........................................................................ 6-79

Importing Users into Aeonix ................................................................ 6-79
Exporting Users from Aeonix............................................................... 6-85

Importing LDAP Users................................................................................ 6-87

Associating Users with Groups .................................................................. 6-93

Group List and Pickup Group List Pages ............................................ 6-93
Defining a Group ................................................................................. 6-96

Aeonix Clients for Users............................................................................. 6-99

Downloading the Sea Navigator / Sea Attendant Client .................... 6-102
Downloading the Visor / Agent Client ................................................ 6-103
Downloading the FlexIP Softphone (FLIPS)...................................... 6-104
Downloading the TAPI Service Provider and DialIt ........................... 6-105
Downloading the Aeonix Maintenance Tool ...................................... 6-106
Downloading Aeonix Touch............................................................... 6-107

7 Managing Phones

Phones ......................................................................................................... 7-1

Phone List Page .................................................................................... 7-3

Configuring Phones in Aeonix ...................................................................... 7-9

Defining a Phone in Aeonix ................................................................. 7-10
Defining the Default User of a Phone .................................................. 7-24
TOC

Aeonix Administration Manual Table of Contents vii

 Phone Templates ...................................................................................... 7-25

8 Managing Trunks

Trunks .......................................................................................................... 8-1

Trunk List Page ..................................................................................... 8-2

Configuring Trunks in Aeonix ....................................................................... 8-9

Defining a Trunk in Aeonix .................................................................. 8-10
Trunk Parameters................................................................................ 8-13
Defining the Default Trunk Group of a Trunk ...................................... 8-25

Trunk Templates ........................................................................................ 8-27

9 Managing Trunk Groups

Trunk Groups ............................................................................................... 9-1

Trunk Group List Page .......................................................................... 9-2

Defining a Trunk Group ................................................................................ 9-5

Defining Trunk Group Settings .............................................................. 9-9
Assigning Aliases to Trunk Groups ..................................................... 9-10
Overriding Trunk Group Profiles.......................................................... 9-10
Defining Incoming and Outgoing Call Routing for Trunk Groups ........ 9-11
Defining the Trunk Members of a Trunk Group ................................... 9-23
Reserving a Trunk Group for Emergency Calls................................... 9-24
Adding a Trunk Group for Trunk Group Speed Dial ............................ 9-26
Authorizing Trunk Group Members to perform Silent Monitoring ........ 9-26

Importing / Exporting Trunk Group Rules................................................... 9-27

Importable Trunk Group Call Routing Rules ....................................... 9-27
Importing Trunk Group Call Routing Rules ......................................... 9-28
Exporting Trunk Group Call Routing Rules ......................................... 9-30
TOC

viii Table of Contents Aeonix Administration Manual

 10 Managing VOIP Gateways

Gateways ................................................................................................... 10-1

Tadiran TGW Gateway Series ............................................................ 10-1
Wave Gateway Series ......................................................................... 10-2
VOIP Gateway List Page..................................................................... 10-4

Configuring Wave Gateways...................................................................... 10-7

Defining a Wave Gateway ................................................................... 10-8
Defining Wave Gateway Setup/Synchronization/Alarm Parameters . 10-10

Configuring Wave Gateway Cards ........................................................... 10-17

Card List ............................................................................................ 10-18
Managing Wave Gateway Phones or Trunks .................................... 10-22
Configuring Card Parameters............................................................ 10-24
Adding a Card ................................................................................... 10-37
Deleting a Card ................................................................................. 10-38

Configuring Tadiran TGW Gateways........................................................ 10-41

Defining a Tadiran TGW Gateway .................................................... 10-42
Defining Tadiran TGW Gateways with Plug and Play Deployment ... 10-50
User Definitions CSV Import File....................................................... 10-58
Defining a Tadiran TGW PRI Gateway ............................................. 10-60

11 Managing Aliases

Aliases (“Phone Extensions”) ..................................................................... 11-1

Alias Lists Page ................................................................................... 11-2

Assigning Aliases ....................................................................................... 11-5

12 Configuring Services

Services ..................................................................................................... 12-1

Defining ACD Groups................................................................................. 12-5

TOC

ACD Group List Page.......................................................................... 12-6

Defining an ACD Group....................................................................... 12-8

Aeonix Administration Manual Table of Contents ix

 Setting Codecs for ACD & Hunt Announcers .................................... 12-16

Configuring the Aeonix Contact Center.................................................... 12-17

Aeonix Contact Center Service List Page ......................................... 12-18
Defining Aeonix Contact Center Aliases and Call Failover Options .. 12-20

Configuring Call Recording ...................................................................... 12-23

Call Recording List Page ................................................................... 12-24
Defining a Call Recording Rule ......................................................... 12-28
Defining a Recording Server ............................................................. 12-32
Record on Demand (RoD) Using SeaMail ........................................ 12-35

Configuring the Hospitality Service .......................................................... 12-39

Hospitality List Page .......................................................................... 12-40
Defining a Hospitality Service............................................................ 12-41

Defining Hunt Groups............................................................................... 12-45

Hunt Group List Page........................................................................ 12-46
Defining a Hunt Group....................................................................... 12-48

Defining Call Groups ................................................................................ 12-59

Call Group List Page ......................................................................... 12-60
Defining a Call Group ........................................................................ 12-61

Defining Conference Calls........................................................................ 12-63

Conference Call List Page................................................................. 12-64
Defining Conference Call Alias Numbers .......................................... 12-65

Defining Emergency Conference Calls .................................................... 12-71

Emergency Conference Call List Page ............................................. 12-72
Defining Emergency Conference Call Alias Numbers ....................... 12-73

Defining Meet-Me Conference Aliases..................................................... 12-79

Meet Me Conference Configuration List Page .................................. 12-80
Defining Default Values for Meet-me Conference Security Settings . 12-82
Defining Meet-me Conference Alias Numbers .................................. 12-86
TOC

Defining Mobility Aliases .......................................................................... 12-89

Mobility List Page .............................................................................. 12-90

x Table of Contents Aeonix Administration Manual

 Defining a Mobility Alias .................................................................... 12-91
Configuring Rules for a Mobility Alias................................................ 12-93

Configuring Call Detail Records (CDR) .................................................... 12-97

Computer Telephony Integration (CTI) ..................................................... 12-99

Directory ................................................................................................. 12-101

Defining Dispatch Consoles ................................................................... 12-103

Dispatch Console List Page ............................................................ 12-104
Defining a new Dispatch Console ................................................... 12-106
Defining a Dispatch Console Profile ................................................ 12-107

Configuring the E911 Database Connector............................................ 12-109

E911 Database Connector Page..................................................... 12-110

Configuring the Music Service.................................................................12-111

Music Service List Page .................................................................. 12-112
Configuring a Music Source and MOH Alias Numbers ................... 12-114

Configuring Page Queue Park/Pickup.................................................... 12-117

Defining Alias Numbers for Page Queue Park/Pickup .................... 12-118

Configuring PnP / Provisioning Service.................................................. 12-123

Viewing Updated Phone Firmware Files ......................................... 12-124
Configuring PnP Provisioning.......................................................... 12-126
Defining New Configuration Sets .................................................... 12-130

Importing Audio Files ............................................................................. 12-133

Configuring Voicemail ............................................................................ 12-137

SIP Voicemail List Page .................................................................. 12-138
Defining Voicemail Applications in Aeonix ...................................... 12-140
Accessing SeaMail .......................................................................... 12-148

Defining Virtual Endpoints ...................................................................... 12-149

TOC

Virtual Endpoint List Page ............................................................... 12-150

Defining Virtual Endpoint and Virtual Agent Alias Numbers ............ 12-152

Aeonix Administration Manual Table of Contents xi

 Defining Zone Page Calls ...................................................................... 12-159
Zone Page List Page ....................................................................... 12-160
Defining Zone Page Call Alias Numbers ......................................... 12-161

13 Managing Your Account

Your Own Account...................................................................................... 13-1

Configuring Your Account........................................................................... 13-3

Defining Your Presence Status ........................................................... 13-4
Modifying Your Identity Settings .......................................................... 13-5
Managing Your Phone Numbers ......................................................... 13-5
Managing Your Voicemail Settings ..................................................... 13-6
Overriding Your Profile Configuration.................................................. 13-6
Defining Your Phones ......................................................................... 13-7
Managing Your Phone Profiles............................................................ 13-7
Setting the Access Code for a Meet-me Conference Alias ................. 13-7
Managing Your Mobility Rules............................................................. 13-8
Managing Your ULA Settings .............................................................. 13-8
Installing the Sea Navigator on Your Workstation ............................... 13-9
Installing the Sea Attendant on Your Workstation ............................... 13-9
Installing the Aeonix Contact Center Client on Your Workstation ..... 13-10
Installing the FlexIP Softphone Client on Your Workstation .............. 13-10
Installing TAPI Service Provider and DialIt on Your Workstation ...... 13-10
Installing Aeonix Touch on Your Workstation.................................... 13-11

Managing Your Call Logs ......................................................................... 13-13

Viewing Your Call Logs ..................................................................... 13-13
Deleting Call Log Entries ................................................................... 13-14
Exporting Your Call Logs................................................................... 13-15

14 Maintaining Aeonix

Alarms ........................................................................................................ 14-1

Viewing Alarms.................................................................................... 14-2
Configuring Alarm Access Parameters ............................................. 14-18
TOC

Configuring Alarm Notification Options ............................................. 14-22

xii Table of Contents Aeonix Administration Manual

 System Information .................................................................................. 14-25
Displaying Aeonix Version Information.............................................. 14-26
System Parameters ........................................................................... 14-27

Clusters .................................................................................................... 14-33

Displaying Cluster Information .......................................................... 14-34
Restarting Servers After Network Connection Restored ................... 14-39
Configuring the Cluster for Registration Load Balancing .................. 14-41
Setting Server for ACD and Hunt Services ....................................... 14-43
Server Settings for the Aeonix Contact Center Service .................... 14-44
Enabling and Configuring High Availability........................................ 14-51

Data Backup and Restoring via Web ....................................................... 14-55

Creating a Backup ............................................................................. 14-56
Restoring the Database with a Backup ............................................. 14-57
Setting up a Schedule for Automatic Backup .................................... 14-58

Upgrading Aeonix via Web....................................................................... 14-63

Upgrade Preparation ......................................................................... 14-63
Aeonix Upgrade Procedure ............................................................... 14-64
Status Messages ............................................................................... 14-66
Logs................................................................................................... 14-67

Restarting Aeonix via Web ....................................................................... 14-69

Downloading Logs via Web...................................................................... 14-71

Server-based Maintenance Tools............................................................. 14-79

Accessing the Aeonix Server ............................................................ 14-79
Restarting Aeonix from the Server .................................................... 14-81
Checking the Aeonix Service Status ................................................. 14-82
Aeonix Server Database Export and Import Procedures .................. 14-83
Aeonix Debugging Commands.......................................................... 14-85
Log Files ............................................................................................ 14-90
Ethereal Network Analyzer ................................................................ 14-92
Aeonix Troubleshooting Examples .................................................... 14-94
TOC

Aeonix Administration Manual Table of Contents xiii

 Aeonix Error Messages ............................................................................ 14-99
Access and Password-related Error Messages .............................. 14-100
General Error Messages ................................................................. 14-101
Global Settings Error Messages...................................................... 14-103
Group-related Error Messages ........................................................ 14-104
Phone and Phone Profiles-related Error Messages ........................ 14-105
Routing and Digit Manipulation Error Messages ............................. 14-106
Schedules-related Error Messages ................................................. 14-107
Voicemail-related Error Messages .................................................. 14-108

15 Aeonix Multi-Tenant Mode

Overview .................................................................................................... 15-1

Tenant List .................................................................................................. 15-3

Dial Plan ..................................................................................................... 15-7

Tenants and Users ................................................................................... 15-11

Tenant User Profiles.......................................................................... 15-11
Outgoing Call Routing Profile ............................................................ 15-13
User List ............................................................................................ 15-16
New User........................................................................................... 15-16
Import / Export Users ........................................................................ 15-20
User Permnissions ............................................................................ 15-21

Service List............................................................................................... 15-23

Multi-Tenant Mode Services.............................................................. 15-23
ACD Pages........................................................................................ 15-25
Hunt Group Page .............................................................................. 15-29
Conference Call................................................................................. 15-31
Meet-Me Conference Page ............................................................... 15-33
Music Source..................................................................................... 15-34
Page Queue Park / Pickup Page....................................................... 15-35
PnP / Auto Provisioning Page ........................................................... 15-36
SIP Voicemail Page........................................................................... 15-37
TOC

Zone Page ......................................................................................... 15-38

xiv Table of Contents Aeonix Administration Manual

 Phones ..................................................................................................... 15-39
Feature Codes................................................................................... 15-39
Button Programming Through Aeonix Admin .................................... 15-40
Button Programming Through the Phones ........................................ 15-41
FlexiCall Dial without ‘9’ .................................................................... 15-41
ANI Display / Call Log ....................................................................... 15-41
SeaMail Operation............................................................................. 15-41
Unsupported Phones and Applications ............................................. 15-42

16 Glossary

Glossary of Terms ...................................................................................... 16-1

TOC

Aeonix Administration Manual Table of Contents xv

TOC

xvi Table of Contents Aeonix Administration Manual

 Chapter 1

Overview

1.1 Introduction to this Manual....................................................1-1

1.2 Introduction to Aeonix ...........................................................1-5

1.3 Support and Documentation ...............................................1-15

Aeonix Administration Manual

 1.1 Introduction to this Manual

This manual describes how the administrator configures Aeonix. The administrator
adds users and assigns them call extension numbers (aliases) and phones. Likewise,
the administrator adds and configures gateways and trunks to work with Aeonix. The
administrator is also responsible for configuring and maintaining Aeonix entities.
Finally, the administrator can define other Administration Levels with customized
Administration Tasks, authorizing other users, for example, to add new users to the
system.
Prior to using Aeonix, the application must be installed, and a soft key with the
appropriate license permissions must be uploaded and deployed on the designated
Aeonix License Key server. For details refer to the Installation procedure (see Related
Documentation, page 1-17).

 Intended Audience

The instructions in this manual are designed for administrators of Aeonix.

Administrators are personnel who have full authority to configure all aspects of the
system, including users, telephones, gateways, trunks, aliases, and Administration
Levels in the system.

Introduction to this Manual

1

Aeonix Administration Manual Overview 1-1

  Document Structure

The following table provides a short outline of each chapter.

Chapter Topic Description

Chapter 1 Overview This chapter describes this manual and includes:

(this chapter)  Outline of the Aeonix system
 Target audience definition
 List of related documentation
 Description of the conventions used in the
manual

Chapter 2 Aeonix This chapter introduces Aeonix features and

Features provides guidelines on how to set them up.

Chapter 3 Getting Started This chapter describes how to log in to the Aeonix
Portal and perform basic tasks. It also provides an
outline of Aeonix setup procedures and describes
how to access licensing information.

Chapter 4 Global Settings This chapter describes how to configure Aeonix

global settings: Closed User Groups, Dial Codes,
Dial Plans, Locations, Schedules, Automatic Route
Selection tables, and LDAP Connections.

Chapter 5 Profiles This chapter describes how to configure Aeonix

profiles, sub-profiles, and Auto Provisioning
profiles.

Chapter 6 Managing This chapter describes creating, maintaining,

Users importing, and grouping Aeonix users.

Chapter 7 Managing This chapter describes Aeonix phones and phone

Phones templates. It includes instructions on how to define
different phone types in the system.

Chapter 9 Managing Trunk This chapter describes Aeonix trunk groups, how
Groups they are configured, and how their configuration
Introduction to this Manual

differs from the configuration of Aeonix users.

Chapter 8 Managing This chapter describes Aeonix trunks and trunk

Trunks templates. It includes instructions on how to define
different trunk types in the system.

Chapter 10 Managing VOIP This chapter describes how to define

Gateways VOIP Gateway units in the Aeonix system.
1

Chapter 11 Managing This chapter describes alias types. It also includes

Aliases instructions on how to view and set aliases.

1-2 Overview Aeonix Administration Manual

 Chapter Topic Description

Chapter 12 Configuring This chapter describes Aeonix services and their

Services configuration.

Chapter 13 Managing Your This chapter describes how to manage your own
Account account by utilizing the User Menu options.

Chapter 14 Maintaining This chapter describes procedures used for

Aeonix periodical Aeonix maintenance and
troubleshooting.

Chapter 16 Glossary This chapter provides a description of Aeonix

terminology.

 Manual Conventions

It is important to understand the symbols and typographical conventions used in this

manual. These conventions and symbols indicate information that requires special
attention, as illustrated in the following examples:

Calls out special features or limitations of the Aeonix4Cloud (A4C) edition of

Aeonix.

There is a risk of causing the Aeonix service to malfunction.

Introduction to this Manual

Indicates important information demanding special attention.

NOTES:
A page that is intentionally left blank, and can be used for note-taking.
1

Aeonix Administration Manual Overview 1-3

 In addition, the following typographical conventions are used throughout this manual.

Table 1-1 Typographical

Conventions Convention Use
Italics  Titles of related documentation
 Menu option path denotations. A > sign denotes the path of the
option, such as Administration>Services>Services List.
 Directory path denotations

Bold type  Names of buttons, icons, and menus

 Names of fields, parameters, and options on the Web page
 Selectable drop-down list values
 Text usually displayed in italics when it appears in cautions and
notes
 Names of keys on a telephone, including keypad keys, fixed
function keys, and programmable buttons
 Emphasized text

ALL CAPS Keyboard names, combinations, and sequences, such as CTRL

and SHIFT+P
Blue font Clickable cross-reference links
Message Text prompts and commands in a Linux terminal window or on a
style DOS screen
Introduction to this Manual
1

1-4 Overview Aeonix Administration Manual

 1.2 Introduction to Aeonix

This section provides basic information about Aeonix and lists the devices that can be
connected to it:
 About Aeonix, page 1-6
 Aeonix Building Blocks, page 1-7
 Supported Devices, page 1-12
 Supported Codecs, page 1-13
Aeonix features and their configuration are described in Chapter 2, Aeonix Features.

Introduction to Aeonix
1

Aeonix Administration Manual Overview 1-5

  About Aeonix

Aeonix is a powerful, flexible, and adaptable Unified Communications and

Collaboration (UC&C) platform providing softswitch capabilities in conjunction with
Video conferencing and collaboration. Aeonix offers the benefits of converged IP
communications to all organizations, regardless of their size. With minimal
implementation costs and maximum scalability on an extendable platform, Aeonix
can be expanded or upgraded according to the enterprise’s changing needs.
Whether as an independent system or integrated with existing systems and endpoints,
Aeonix connects between endpoints, protocols, and media gateways. This provides
full feature functionality for heterogeneous media environments of voice, video,
messaging, fax, chat, text messages, URL, and HTML pages.
Aeonix’s user-centric approach simplifies communications with individual call
routing options and customizable individual user preferences. Aeonix also offers
user-friendly Web administration with a range of supervision features.
Aeonix has built-in distributed ACD capabilities and integrated IVR, and is integrated
with Tadiran Telecom’s Aeonix Contact Center applications for more sophisticated
call center functionalities. Distinct groups such as departments or companies can be
managed as completely separate entities through the same Aeonix application.
Existing Coral IPx/FlexiCom customers can take advantage of their investment and
enjoy the benefits of Aeonix. By converting every Coral IPx/FlexiCom to a Tadiran
Wave gateway, existing line cards and telephones (analog and digital sets) can become
part of the Aeonix system. Aeonix can also benefit existing Coral users with its ability
to serve as a survivable remote system when connected as a node on a Coral QNET
network.
An enhanced Aeonix version is available for ASPs and ITSPs, offering hosted and
co-hosted solutions. Customers can enjoy unique numbering plans, separated
administration and billing, and personal routing rules.
Introduction to Aeonix
1

1-6 Overview Aeonix Administration Manual

  Aeonix Building Blocks

Aeonix consists of the following building blocks:

 Entities, page 1-7
 Global Settings, page 1-7
 Profiles, page 1-8
 Administration Levels and Tasks, page 1-9
 Services, page 1-11

Entities
An Aeonix network consists of users, trunk groups, gateways, phones, and trunks.
Users represent individuals; trunk groups represent logical groups of trunks with a
common purpose.
Phones and trunks relate to actual hardware or software devices. Examples for
phones are a telephone or a softphone application on a user’s workstation; examples
for trunks are a SIP trunk, an analog trunk, or an E1/T1 channel to the PSTN. Phones
are associated with users, as a user needs to be logged in through a phone in order to
receive any service from the Aeonix system (such as placing and receiving calls). To
allow the logical configuration of a group of trunks, the system requires trunks to be
associated with trunk groups.
In addition, each user and each trunk group have one or more unique aliases assigned.
An alias is a specific number, range of numbers, or expression that is dialed to reach
the user or trunk group from within the Aeonix network. (External callers either dial
prefix digits or a central number followed by an extension number.) If a user’s cellular
phone or other external devices are defined in Aeonix, a call to the alias of this user
will also ring on these devices, if required.
Coral Wave Gateway and Tadiran TGW Gateway units are represented as gateways.
Gateways are used to connect legacy and non-IP equipment to Aeonix.
Introduction to Aeonix
Global Settings
Global settings are definitions and parameter values that are defined at the system
level, rather than for a specific entity.
The system provides predefined default instances for global settings. Default instances
cannot be removed, but their values can be modified. You can also create and apply
1

additional global setting instances. For example, you can use the predefined country

Aeonix Administration Manual Overview 1-7

 codes as the default codes and define dial codes for additional countries. Global
settings include:

Table 1-2 Global Settings

Description Global Settings Descriptions

Country and area international and national dial codes and patterns
codes

Locations setting that indicates the country and area in which a phone
or trunk is located and used, including emergency call
configuration

Dial plans internal plans that defines the alias patterns that can be
assigned, as well as the codes dialed to make use of
Aeonix features

CUGs (Closed groups or sub-groups of Aeonix users that function as

User Groups) separate virtual “sub-systems” on the same Aeonix system.
Calls from a peer CUG are handled as external calls. Each
CUG is assigned a dial plan.

Schedules time plans for holidays, work hours, or one-time or recurring

periods. Schedules can be applied to users and trunk
groups through Schedule profiles.

ARS (Automatic allows the system to route outgoing calls through the most
Route Selection) suitable transmission channel (trunk group), according to the
prefix of the calls

LDAP connections allows the system to be updated and kept synchronized with
the data residing on the organization’s LDAP server

The term 'CUG' is used throughout this manual. Currently, only the root CUG
(i.e. system-wide CUG) is supported in Aeonix.

Profiles
Introduction to Aeonix

Profiles are sets of parameters that can be associated with an entity. Dedicated profile
types for users and trunk groups exist, as well as template definitions for the different
phone and trunk types.
Profiles include a variety of general parameters, timeout settings, toll restrictions,
feature specifications, phone parameters, and trunk parameters. Profiles can also
1

define flexible routing and forwarding schemes for incoming and outgoing calls.

1-8 Overview Aeonix Administration Manual

 Users and trunk groups are assigned default or administrator-defined profiles, as
required. Profiles can be overridden both globally and for a specific user or trunk
group.

Each user profile is associated with an Administration Level that cannot be

overridden.

Auto Provisioning profiles contain pre-configured sets of features and parameters

which can be associated globally with Tadiran SIP phones, P-Series phones, and
Tadiran TGW gateways. Once configured, the Auto Provisioning service
automatically polls and updates these phones with the latest phone firmware and
configuration files.

Administration Levels and Tasks

Aeonix allows for complete multi-level administration. The administrator can define
administration level profiles that can be applied to allow subsets of users to access and
manage particular pages in the Aeonix Web Portal, referred to as Administration
Tasks. For example, the User List page is automatically displayed upon log in, but only
to users with Users task administration privileges. Unless modified, the default user
profile is automatically applied to new users, giving them personal account
management privileges that only allows them access to their personalized Web Portal
- refer to the Aeonix Configuration Guide for End Users (see Related Documentation,
page 1-17).

The administrator can define new administration level profiles with any
combination of administration tasks. Users assigned to a user profile
associated with an administration level profile that does not include any
administration tasks will not have access rights even to their own
personalized Web Portal.

The following table describes the five default administration level profiles and their Introduction to Aeonix
corresponding administration tasks.

Table 1-3 Default

Administration Level
Level Name Task Name Main Tasks Description
Profiles
Personal Administrator  End Users  Personal Account
Management
1

Aeonix Administration Manual Overview 1-9

 Level Name Task Name Main Tasks Description

Users Administrator  Users  Add/remove users

 Dial Plans and  Add/remove dial plans
Digit Mappings  Defining PnP / provisioning
 PnP / Provisioning profiles
Profiles

Telephony  Dial Plans and  Add/remove dial plans

Administrator Digit Mappings  Defining PnP / provisioning
 PnP / Provisioning profiles
Profiles  Trunk/Trunk Group/ARS
 Trunks and ARS configuration
 VOIP Gateways  VOIP Gateway configuration

Applications  SeaMail Services  Voicemail configuration

Administrator  ACD and CTI  ACD/CTI configuration
Services  Mobility configuration
 Mobility Services  Conference configuration
 Conference  Page Queue, CDR,
Services Dispatch Console
 Other Services configuration

Technician  End Users  Personal Account

Administrator  Users Management
 Dial Plans and  Add/remove users
Digit Mappings  Add/remove dial plans
 PnP / Provisioning  Defining PnP / provisioning
Profiles profiles
 Trunks and ARS  Trunk/Trunk Group/ARS
 SeaMail Services configuration
 ACD and CTI  Voicemail configuration
Services  ACD/CTI configuration
 Mobility Services  Mobility configuration
 Conference  Conference configuration
Services  Alarm access and
 Alarms notification configuration
 Multi-Tenants  Multi-Tenant management
 System and  System/Cluster
Clusters management
Introduction to Aeonix

 LDAP  LDAP configuration

 VOIP Gateways  VOIP Gateway configuration
 Licensing  Licensing management
 Other Services  Page Queue, CDR,
Dispatch Console
configuration
1

1-10 Overview Aeonix Administration Manual

 Services
Some Aeonix features rely on centralized applications called services (such as the
Auto Provisioning service). These services must be configured before the related
features can be used.

Introduction to Aeonix
1

Aeonix Administration Manual Overview 1-11

  Supported Devices

The following is a list of peripheral devices currently supported by Aeonix. You might
need some of the following equipment to work with Aeonix. To learn how to set them
up and connect them to Aeonix, refer to the relevant manuals as described in the
Related Documentation section of this manual.
 MGCP: FlexSet-IP 280S, T200M Series (T207M, T208M/BL) IP telephone
 Tadiran SIP Phones: T19P, T19P E2, T21P E2, T23G, T27P, T29G, T320,
T320P, T322, T328, T41P, T42G, T46G, T48G, T49G
 SIP: P-Series (P-335, P-450) IP telephone
 FlexIP Softphone (FLIPS)
 SeaBeam video softphone (Version 1.5.20.2 build 62959 and higher)
 Coral IPx Office with QSIG IP (Net-IP feature authorization)
 Coral IPx 500 with QSIG IP (Net-IP feature authorization) and
PUGWipx/PUGW-2Gipx card
 Coral IPx 800, 3000, 4000 with QSIG IP (Net-IP feature authorization) and
PUGW/PUGW-2G card
 Coral FlexiCom 400 (with HDC Controller), 5000, 6000 with QSIG IP (Net-IP
feature authorization) and PUGW/PUGW-2G card
 SIP-based AudioCodes FXO/FXS gateways
 Tadiran TGW gateways
 Sentinel Pro
 Wave Gateway, as well as any voice terminals or trunks supported by and
connected through the Wave Gateway. These include FlexSet, DST, and DKT
phones; Single Line Telephones (SLT); Loop Start, Ground Start, E1/T1, BRI,
and PRI trunks; and many more. (For a full list, refer to the Wave Gateway
documentation.)
 Other third-party phones (off the shelf) that have been approved for use with
Introduction to Aeonix

Aeonix. Contact the Aeonix manufacturer's representative for the approved list
of tested equipment and along with their test data.
1

1-12 Overview Aeonix Administration Manual

  Supported Codecs

Aeonix supports the following codecs:

 G.711 (µ-law and A-law algorithms)
 G.729

Aeonix EP-to-EP Codec Negotiation

When connecting two endpoints, Aeonix tries to assign the lowest resource codec that
is acceptable to both endpoints for the call.

Example
The initiator sends the list of codecs it has available locally, in this order:
g711
g729
g722
Aeonix will reorder the list and send to the destination:
g729
g711
g722
putting the lowest resource codecs earlier in the list. The endpoints will then negotiate
the codec based on the reordered priority of codecs.

Introduction to Aeonix
1

Aeonix Administration Manual Overview 1-13

NOTES:
 1.3 Support and Documentation

This section provides information about the following:

 Support, page 1-16
 Upgrading the Aeonix Ecosystem, page 1-16
 Related Documentation, page 1-17

Support and Documentation

1

Aeonix Administration Manual Overview 1-15

  Support

The manufacturer is committed to quality service and customer support. Therefore, if

any problem related to the Aeonix system occurs, contact one of the manufacturer’s
support centers listed at http://www.tadirantele.com/tadiran-telecom/support.aspx or your
Aeonix manufacturer’s representative.
In the email, include the following information:
 The caller’s phone number
 The called phone number
 The date and time of the event
 Other details related to the event
In addition, attach the system log files (see Log Files, page 14-90) and if relevant,
Ethereal network analyzer reports (see Ethereal Network Analyzer, page 14-92) to the
email.

 Upgrading the Aeonix Ecosystem

Upgrading Aeonix servers with the latest Aeonix ecosystem software versions,
including Aeonix, Aeonix Contact Center, and SeaMail is quick and easy. Just follow
the steps in the Aeonix Upgrade Version Wizard. A Rollback Wizard is also available.
Refer to the Aeonix Maintenance Tool Manual (see Related Documentation, page 1-17).

To obtain additional licenses, the Aeonix soft key must be updated. This is
described in detail in the Aeonix Installation Manual.
Support and Documentation
1

1-16 Overview Aeonix Administration Manual

  Related Documentation

Refer to the following documentation, as required, for information regarding the

Aeonix system and the devices that can be connected to the Aeonix network.

Table 1-4 Related

Documentation
Item Subject Manual

Aeonix Minimum Aeonix Installation -

requirements Hardware and Software
Guidelines

Installation procedure Aeonix Installation Manual

for Manufacturer-installed
Systems

Aeonix Installation Manual

for Customer-installed
Systems

Version upgrade Aeonix Maintenance Tool

Manual

Web Portal for End Aeonix Configuration Guide

users for End Users

FlexIP Softphone How to use and FlexIP SoftPhone User

(FLIPS) Installation Procedure Guide

SeaBeam Softphone General description SeaBeam User Guide for

and how to use Aeonix

Installation SeaBeam Softphone

procedure, and Installation Manual
troubleshooting

FlexSet-IP 280S General description FlexSet-IP 280S User Guide

terminals and how to use for Aeonix

Installation, FlexSet-IP 280S

Troubleshooting and
Support and Documentation
IP station Installation Manual
Hardware Reference for Aeonix 1

Aeonix Administration Manual Overview 1-17

 Item Subject Manual

T200M Series (MGCP) General description T207M/NP, T208M/BL,

terminals and how to use T207M and T208M
IP Telephone User Guide for
Aeonix

Quick User Guide T200M Quick Reference

Guide - How to Use Aeonix
Telephony Features

Installation, T207M/NP, T208M/BL,

Troubleshooting and T207M and T208M IP
Hardware Reference station Installation Manual
for Aeonix

P-Series (SIP) terminals General description Third-party SIP Telephone

and how to use User Guide for Aeonix

Polycom P-335 and P-450

User Guides

Quick guide Polycom P-335 and P-450

Quick Start Guides

Polycom P-335 and P-450

Quick User Guides

T20 Series (SIP) Aeonix features Third-Party SIP Telephone

terminals operation User Guide for Aeonix

T300 Series (SIP) Aeonix features Third-Party SIP Telephone

terminals operation User Guide for Aeonix

T40 Series (SIP) Aeonix features Third-Party SIP Telephone

terminals operation User Guide for Aeonix

SeaMail Administration and SeaMail Administration and

configuration Configuration Manual for
Aeonix
Support and Documentation

Voicemail description SeaMail User Guide for

and how to use Aeonix

Short User Guide SeaMail Voice Messaging -

Quick User Guide

Quick guide MAILBOX TYPE: Bureau

(CO Messaging Octel)

MAILBOX TYPE: Message

1

(Voice Messaging)

1-18 Overview Aeonix Administration Manual

 Item Subject Manual

Sentinel Pro General description, Sentinel Pro 6.5 Installation

installation, Procedure and Reference
troubleshooting and Manual for Aeonix
hardware reference

Coral IPx/FlexiCom Database Coral IPx/FlexiCom

systems configuration for Program Interface &
QSIG IP (Net-IP Database Reference Manual,
feature authorization) Version 15 or higher

UGW, PUGW or Coral IPx/FlexiCom Service

PUGW-2G card for and Peripheral Cards
QSIG IP (Net-IP) Installation Manual (Chapter
10)

Wave Gateway systems Database Coral Wave Gateway

configuration via PI Program Interface &
Database Reference Manual

Coral system Coral Wave Gateway

conversion to Conversion Procedure for
Wave Gateway Coral IPx/FlexiCom Systems

FlexSet 120S, 121S FlexSet 120S and 121S

User Guide for Aeonix

FlexSet 280S, 281S FlexSet 280S and 281S

User Guide for Aeonix

FlexSet FlexSet 280, 280D, 120,

120, 120D, 120L, 120D & 120L User Guide for
280, 280D, 280D-HS Aeonix

DKT and DST

SLT SLT User Guide for Aeonix

FlexSet installation FlexSet (120, 120D, 120L,

120S, 121S, 280, 280D,
Support and Documentation
280D-HS, 280S, 281S,
APDL, PEX, APA and CPA)
Digital Station Terminal
Equipment Installation
Manual
1

Aeonix Administration Manual Overview 1-19

 Item Subject Manual

Tadiran TGW Gateway TGW4/8, TGW4/8 Gateway Series

systems TGW8S-2G, User Configuration Manual
TGW8-2G

TGW16, TGW24-16, TGW16/24/96 Gateway

TGW24-24, Series User Configuration
TGW96-24, Manual
TGW96-96

TGW1E1-2G, TGWxE1-2G PRI (ISDN)

TGW2E1-2G, Trunk Gateway Series User
TGW4E1-2G Configuration Manual
Support and Documentation
1

1-20 Overview Aeonix Administration Manual

 Chapter 2

Aeonix Features

2.1 Setting up Aeonix Features ..................................................2-1

Aeonix Administration Manual

 2.1 Setting up Aeonix Features

This section briefly describes the main features of the Aeonix system and refers to the
relevant pages in the Aeonix Web Portal.

For a comprehensive description of Aeonix features, refer to the Aeonix

Product Description (see Related Documentation, page 1-17).

Aeonix users can activate features by:

 Configuring the keyset through the keyset's display using soft keys and arrow
keys
 Using a programmable keyset button that is programmed for the feature
(see Phone Profiles, page 5-54 and Programmable Button Dial Functions, page 5-60)
 Configuration via the Aeonix Web Portal for Users
 Entering the relevant codes. These dial codes are defined in the dial plan of the
users (see Dial Plans, page 4-19).
Access to some features can be restricted by the administrator.

For detailed instructions on activation and use of features, refer to the User
Guide of the relevant phone (see Related Documentation, page 1-17).

Setting up Aeonix Features

2

Aeonix Administration Manual Aeonix Features 2-1

 This section describes the following basic features:
 Aeonix Contact Center, page 2-5
 Aeonix Directory, page 2-5
 Aeonix Logger (Call Recording), page 2-6
 Aeonix Record on Demand (RoD) with SeaMail), page 2-7
 Aeonix Maintenance Tool, page 2-7
 Aeonix Touch, page 2-8
 ANI (Caller ID) Restriction, page 2-8
 Auto Answer, page 2-8
 Auto Redial, page 2-9
 Automatic Call Distribution (ACD) and Hunt Groups, page 2-9
 Automatic Database Backup, page 2-10
 Automatic Route Selection (ARS), page 2-10
 Batch Import of Users, page 2-11
 Break-in, page 2-11
 Call Details Records (CDR), page 2-12
 Call Time Limit, page 2-12
 Call Groups, page 2-12
 Call Log, page 2-12
 Call Pickup, page 2-12
 Call Preemption, page 2-13
 Call Waiting (Multi-appearance), page 2-14
 Camp-on, page 2-14
 Closed User Groups (CUG), page 2-16
 Computer Telephony Integration (CTI), page 2-17
Setting up Aeonix Features

 Conference Calling, page 2-17

 Deflect (Divert) Call, page 2-18
 Dial Lock, page 2-18
 Direct Inward Dialing (DID), page 2-18
 Dispatch Console, page 2-19
 Do Not Disturb (DND), page 2-19
2

 Emergency Conference Calling, page 2-20

2-2 Aeonix Features Aeonix Administration Manual

  Emergency Conference Calling, page 2-20
 Enhanced SIP Functionality (ESF), page 2-21
 FlexiCall, page 2-23
 FlexIP Softphone, page 2-23
 Gateways, page 2-24
 Group Listening, page 2-24
 Headset Only Mode, page 2-24
 Hospitality, page 2-25
 Hot Station, page 2-25
 Incoming Call Routing (Call Forwarding and Call Rejection), page 2-25
 Lightweight Directory Access Protocol (LDAP), page 2-26
 Login and Logout, page 2-26
 Mobility, page 2-27
 Multi-Level Administration, page 2-27
 Multi-Tenant Mode, page 2-28
 Multi-Tenant Mode, page 2-28
 Mute, page 2-29
 Network Alarms, page 2-30
 Outgoing Call Routing (Dialed Number Manipulation), page 2-31
 Page Queue, page 2-31
 Profile Programming, page 2-32
 Programmable Phone Buttons, page 2-32
 PnP / Provisioning for Tadiran SIP Phones and P-Series Phones, page 2-32
 Recall on Transfer, page 2-33
 Redial, page 2-34
 Redundancy, page 2-34 Setting up Aeonix Features

 Registration Load Balancing, page 2-35

 Remote Server Maintenance, page 2-35
 Reports, page 2-36
 Room Recording, page 2-36
 Schedule Programming, page 2-37
2

 Sea Attendant, page 2-37

Aeonix Administration Manual Aeonix Features 2-3

  Sea Navigator, page 2-39
 Silent Monitoring, page 2-40
 Single Sign On, page 2-40
 Timeout Programming, page 2-41
 Toll Barrier, page 2-41
 Transfer, page 2-42
 Unified Messaging and Voicemail, page 2-42
 User Line Appearance (ULA), page 2-43
 User Presentation, page 2-44
 Virtual Endpoints, page 2-45
 Voice Page, page 2-45
 Web Portal, page 2-46
 Zone Page, page 2-46
Setting up Aeonix Features
2

2-4 Aeonix Features Aeonix Administration Manual

  Aeonix Contact Center

Aeonix Contact Center is an intuitive, flexible and easy to use all in one contact center
management solution. This out-of-the-box call routing system provides sophisticated
call blending, call proxy and automated callback features. Multimedia queue
management enables intuitive, prompt and personalized attention.
Aeonix Contact Center’s detailed historical, real time and cradle to grave reporting
allow organizations to easily and quickly measure contact center resources and to
adjust to changing business demands. It integrates seamlessly with customer CRM
solutions and can easily blend inbound and outbound calls to manage sales campaigns
and customer order processing.
The Aeonix Contact Center is designed to function in a clustered environment. A
secondary server can be defined for high availability purposes.
Feature Configuration
 Licenses (License Information, page 3-35)
 Aeonix Contact Center service—set up Aeonix Contact Center aliases (IRN)
numbers and configure call failover options (Configuring the Aeonix Contact Center,
page 12-17)
 Set server for Aeonix Contact Center service in a clustered environment (Server
Settings for the Aeonix Contact Center Service, page 14-44).
 For users that are allowed to use the Aeonix Contact Center client—download
the client on each user’s workstation (Downloading the Visor / Agent Client, page 6-103),
or instruct the users to download the client by themselves (Aeonix Contact
Center Installation and Getting Started).

 Aeonix Directory

The Aeonix directory displays all the selected internal Aeonix aliases, including
Aeonix users, Aeonix Touch users, Hunt groups, ULA groups, Zone page, Conference
calls, and Meet-me conferences. Aeonix users can access, search for, and dial these
contacts directly from their supported phones.
Provisioned Tadiran SIP phones connect to the LDAP directory, while FlexSet, Setting up Aeonix Features
MGCP, and DKT phones obtain the directory directly from the Aeonix database.
Depending on phone type, the directory can be accessed using various methods,
including dialing the feature code (default: 1994), pressing the Directory soft key, or
pressing a pre-programmed button.
2

Aeonix Administration Manual Aeonix Features 2-5

 Contacts can be searched for according to Display name, First name, Last name, and
Login name, and then dialed using the usual methods.
Feature Configuration
 Define which contacts to display in the directory (Defining User Identity Settings,
page 6-14)
 Programmed phone button (Programmable Button Dial Functions, page 5-60) or
 Directory code (Table 4-10, Feature Codes for Dial Plans)
 Default LDAP directory connection credentials (Default LDAP Directory, page 4-64)

 Aeonix Logger (Call Recording)

The Tadiran branded Aeonix Logger is a call recording and screen logging system that
records communication between SIP trunks and phones, as well as between
MGCP/analog/digital trunks and phones. Voice recordings in conjunction with screen
capturing capabilities allow all user activity to be thoroughly monitored and powerful
search mechanisms allow all recordings to be easily retrieved and played back by the
system administrator locally or remotely via a user-friendly web-based management
interface.
Aeonix Logger supports active recording, where streams are sent to the recorder from
a central point regardless of network topology. This method of recording allows any
endpoint and logical entity in the system to be recorded using Basic Rule Engine
(BRE) recording rules, including analog phones, digital phones, digital trunks, VoIP
phones, SIP trunks, user entities, ULA and more.
Selective recording can also be performed on demand by Aeonix users on supported
phones and applications via CSTA. A CSTA link can be used to send CTI information
(caller ID, dial number, alias, and DNIS) from the Aeonix to the Aeonix Logger, which
then generates meta data for storage purposes.

Feature Configuration
Setting up Aeonix Features

 Call Recording service—set up selective recording rules and associate recording

servers with recording centers (Configuring Call Recording, page 12-23)
 Programmed phone button (Programmable Button Dial Functions, page 5-60) or
 Record on demand code (Table 4-10, Feature Codes for Dial Plans)
 Aeonix Web Portal for Users (refer to the Aeonix Configuration Guide for End
Users)
2

2-6 Aeonix Features Aeonix Administration Manual

  Aeonix Record on Demand (RoD) with SeaMail)

Aeonix can be configured to use the SeaMail product as a call recording center. In
some cases it may required to provide Record On Demand capability for Aeonix
without the need to deploy an additional server. This can be the case in an Aeonix
system deployed to a small- to mid-sized business. In this solution the recordings are
stored in the user's mailbox, and can be retrieved by either listening to them via the
phone or by sending them to the user's email address as an attachment.
Recording with SeaMail is initiated by the user on demand (RoD). The user initiates
the recording by activating the RoD feature during or before the call.
Limitations:
 Recording by Rules - Not Supported
 Total recording - Not Supported
 Keep Control - Not Supported
 Sticky Recording - Not Supported

Feature Configuration
 Call Recording service—in the absence of an Aeonix Logger configured as the
recording center, Aeonix will use the SeaMail as the recording center if it has
been activated and licensed (Configuring Call Recording, page 12-23)
 Programmed phone button (Programmable Button Dial Functions, page 5-60) or
 Record on demand code (Table 4-10, Feature Codes for Dial Plans)
 Aeonix Web Portal for Users (refer to the Aeonix Configuration Guide for End
Users)

 Aeonix Maintenance Tool

The Aeonix Maintenance Tool is designed for support personnel who monitor Aeonix:
 Identify and solve issues with Aeonix calls
 View and analyze call details to prevent problems Setting up Aeonix Features

 Automatically upgrade and rollback Aeonix ecosystem versions, including

Aeonix, Aeonix Contact Center, and SeaMail
Feature Configuration
 Download the Aeonix Maintenance Tool (Downloading the Aeonix Maintenance Tool,
page 6-106).
2

Aeonix Administration Manual Aeonix Features 2-7

  Aeonix Touch

Aeonix Touch is a comprehensive, feature rich unified communications client that can
be operated from a desktop computer, offering a full range of capabilities that combine
all the benefits of a standard phone with the convenience and flexibility of an
interactive software application.
Feature Configuration
 Licenses (Licenses, page 3-29)
 Download the Aeonix Touch client on each user’s workstation (Aeonix Clients for
Users, page 6-99), or instruct the users to download the client by themselves
(Aeonix Configuration for End Users).

 ANI (Caller ID) Restriction

The ANI number refers to the phone from which the call is made. ANI restriction
allows a user’s ANI to be hidden from the external call destination.
Feature Configuration
 For all calls—in the user’s Feature Configuration profile (Feature Configuration
Sub-profiles, page 5-15)
 For a specific call—Programmed phone button (Programmable Button Dial Functions,
page 5-60) or ANI Restriction code (Table 4-10, Feature Codes for Dial Plans)

 Auto Answer

Auto Answer sets the phone to automatically accept incoming calls, that is, activate
the speaker or the headset when an incoming call is received. This feature is mainly
used by call center agents in telemarketing and support centers.
This feature can be turned on and off directly from the phone or in the user’s Feature
Configuration profile.
Setting up Aeonix Features

Feature Configuration
 User’s Feature Configuration profile (Feature Configuration Sub-profiles, page 5-15) or
Auto Answer code (Table 4-10, Feature Codes for Dial Plans)
2

2-8 Aeonix Features Aeonix Administration Manual

  Auto Redial

Auto Redial allows users to automatically dial busy and non-answering destinations
according to the predefined number of ring attempts by pressing a dedicated soft key,
programmed button, or code.
This feature can be suspended by activating the Freeze Auto Redial feature.
Feature Configuration
 Auto Redial—set number of ring attempts and time intervals between attempts,
in the Feature Configuration profile (Feature Configuration Sub-profiles, page 5-15). This
parameter can be overridden for individual users.
 Programmed phone button (Programmable Button Dial Functions, page 5-60) or
 Auto Redial and Freeze Auto Redial codes (Table 4-10, Feature Codes for Dial
Plans)

 Automatic Call Distribution (ACD) and Hunt Groups

The Aeonix distributed ACD feature allows Aeonix users to function as call center
agents via ACD and Hunt groups. When used in conjunction with the Aeonix Contact
Center, the ACD feature allows for a complete call center solution.
An ACD/Hunt group is assigned an alias number and includes specified users and/or
user groups. A call to this number is directed to the first available user (agent)
according to the specified call distribution method. If all logged-in ACD/Hunt group
members are busy or on break, the incoming call is put on the group’s waiting queue.
According to the ACD/Hunt group definition, the caller either hears a recorded
message or music until an ACD group member becomes available, is automatically
transferred to a specified overflow destination such as voicemail, or is disconnected.
ACD/Hunt group members can make use of ACD related features, including:
 Answer, reject, and place ACD calls on hold, during which time the agent
becomes unavailable to answer other calls (including private calls)

Setting up Aeonix Features

 Log in and out of an individual ACD group (ACD members only)
 Take a break (release status) from all ACD groups to which they are currently
logged in, and resume active status in all those groups when the break is over
2

Aeonix Administration Manual Aeonix Features 2-9

 A user can be a member of several ACD/Hunt groups.
Feature Configuration
 Specify group members, call distribution method, announcements, and overflow
parameters (Defining ACD Groups, page 12-5 and Defining Hunt Groups, page 12-45).
 Set server for ACD service in a clustered environment (Setting Server for ACD and
Hunt Services, page 14-43).
 Specify the codecs used for announcers (Setting Codecs for ACD & Hunt Announcers,
page 12-16).

 Automatic Database Backup

The Aeonix database can be backed up at any time, or automatically at programmable

intervals. In a cluster of several Aeonix servers, a backup file destination can be
specified for each server. Backup files can be used to restore a corrupted database.
Feature Configuration
 See Setting up a Schedule for Automatic Backup, page 14-58.

 Automatic Route Selection (ARS)

The trunk groups (channels) through which Aeonix routes outgoing calls can be
flexibly defined to improve call quality and throughput while reducing costs. Taking
into account calling user location, destination number, and applicable call routing
rules, ARS tables route the calls through the optimal available trunk group. For further
details, see Automatic Route Selection (ARS), page 4-43.
Feature Configuration
 Define trunk groups (Chapter 9, Managing Trunk Groups).
 Define countries and areas (Defining a Country, page 4-4).
 Define the ARS table (Defining an ARS Table, page 4-46).
 Test the ARS table definition (Testing an ARS Table, page 4-49).
Setting up Aeonix Features
2

2-10 Aeonix Features Aeonix Administration Manual

  Batch Import of Users

Multiple users and their phones can be imported into the Aeonix system from a CSV
file. Prior to the import, the administrator specifies which fields are included in the file
and in what order.
Feature Configuration
 See Importing / Exporting Users, page 6-79.

 Break-in

An authorized Aeonix user can enter an established call in order to establish

communication with the conversing parties, effectively creating an ad-hoc conference
call. If the target user is already in a conference, the authorized Aeonix user that breaks
in will join the already existing conference. A break-in message is indicated on the
phone displays, and a break-in tone is heard by all parties to warn them of the break-in
when the break-in occurs, and every 30 seconds thereafter.
Feature Configuration
 Assign users that are authorized to perform Break-in (Defining Permission Settings,
page 6-74)
 Programmed phone button (Programmable Button Dial Functions, page 5-60) or
 Break-in code (Table 4-10, Feature Codes for Dial Plans)

 Break-out

An authorized Aeonix user can perform a Break-out on a target destination. Any call
that the destination is involved with is put on hold for the destination, and then a call
is created between the user and the target destination..
Feature Configuration

Setting up Aeonix Features

 Assign users that are authorized to perform Break-out (Defining Permission Settings,
page 6-74)
 Programmed phone button (Programmable Button Dial Functions, page 5-60) or
 Break-out code (Table 4-10, Feature Codes for Dial Plans)
2

Aeonix Administration Manual Aeonix Features 2-11

  Call Details Records (CDR)

The system supports on demand and online CDR applications that provide
information on each call in Aeonix.
Feature Configuration
 CDR service (Configuring Call Detail Records (CDR), page 12-97)

 Call Time Limit

The Aeonix administrator can set an outbound and transit call duration limit for
individual users., for cost protection.
Feature Configuration
 Call Time Limit (Feature Configuration Sub-profiles, page 5-15, Figure 5-6, Table 5-6)

 Call Groups

A call group includes several users and/or user groups under a dedicated alias number.
When this number is called, the phones of all members belonging to the call group ring
until one of them answers the call.
Feature Configuration
 See Feature Parameters, page 5-17.

 Call Log

This feature allows users to view and redial their most recent outgoing and incoming
calls to their telephone, including unanswered incoming calls. The call display
Setting up Aeonix Features

includes the caller number and the name associated with that number, as available.

 Call Pickup

A ringing phone can be picked up from any phone within your system or from a
pre-programmed Pickup Group, as follows:
2

2-12 Aeonix Features Aeonix Administration Manual

 Directed Call Pickup
An authorized user can pick up any ringing phone in the system by dialing the direct
call pickup number followed by the alias of the ringing phone.
In addition, users with multiple devices can divert a call from one device to another
device of theirs when the first device is ringing or in an active call by dialing the call
pickup number followed by the activation code from their second device.

Group Call Pickup

A call to a member of a pickup group (see Associating Users with Groups, page 6-93) can
be picked up by any member dialing the group call pickup code.
Feature Configuration
 Call pickup activation—Feature Configuration profile (Feature Configuration
Sub-profiles, page 5-15)
 Assign users that are authorized to perform call pickup (Defining Permission Settings,
page 6-74)
 Define the pickup group (Associating Users with Groups, page 6-93).
 Pickup codes (Table 4-10, Feature Codes for Dial Plans)

 Call Preemption

Call Preemption can be defined for user, conference call, and zone page aliases. It
ranks the priority of calls (medium, high, or urgent). When dialing a lower ranked alias
that is currently making a call or being called, Call Preemption causes the call attempt
to be dropped in favor of the higher priority incoming call.
Similarly, Call Preemption determines the action to be taken when the destination is
currently busy with a lower ranked call:
 Call Waiting – the called user is notified by a special call waiting indication
tone that there is an incoming call of higher priority (even though the called
user’s call waiting feature is not activated). This is the default action.
 Break In – the called user is notified by a special break-in indication tone and
the call turns into a three-way conference call between the existing parties and Setting up Aeonix Features
the incoming call of higher priority. In the event a conference call cannot be
established, the original call is dropped and the incoming call of higher priority
begins a private call with the called user.
 Hold – the party with which the called user is conversing is put on hold and
the incoming call of higher priority rings at the called user.
2

Aeonix Administration Manual Aeonix Features 2-13

 Call Preemption overrides any blocking features, including Forward on busy
and DND.

 Call Waiting (Multi-appearance)

When a caller calls to a phone on which call waiting is activated and the phone is
engaged, the caller does not receive a busy signal but is put into a wait queue instead.
While in the wait queue, the caller hears either a regular ringing tone or a call waiting
ringback tone. The called user is notified by a special call waiting indication tone.
On display-equipped phones, the number or name of the callers are indicated on the
phone display. A waiting party can also be indicated by a lit Line button on the user’s
phone. More than one Line button can be programmed for multiple waiting calls.
Call waiting can be activated for all calls (internal and external).
Feature Configuration
 Call waiting activation—Feature Configuration profile (Feature Configuration
Sub-profiles, page 5-15)
 Line buttons—button programming (Phone Profiles, page 5-54)

 Camp-on

Camp-on is used after trying to call a busy or non-answering destination. Camp-on

notifies the camping-on user by means of a distinctive dial tone when the camped-on
destination becomes available, and automatically calls it again as soon as the user
picks up the phone.
There are three Aeonix Camp-on options:
 camp-on idle starts ringing as soon as the non-answering party indicates it is
Setting up Aeonix Features

available by being first busy and then idle again. This option is for when it is
known that the other destination is out of the office and cannot get back to the
user right away.
 Camp-on busy informs the user that the called busy user or alias has become
idle. This option is for when it is known that the other destination is in the
office and can get back to the user shortly.
 Camp-on auto the system automatically makes the camp-on request based on
2

the destination and state (busy or idle) of the last outgoing internal call. In this

2-14 Aeonix Features Aeonix Administration Manual

 case, the last call data is kept for 5 minutes, after which pressing the Auto
Camp-on button will not make the camp-on request.
To camp on a called number, the user dials the Camp-on Idle or Camp-on Busy feature
code, or activates the corresponding programmed phone button. Camp-on is
automatically canceled as soon as the camped-on party answers the phone, or if it does
not become idle after a preset period.
Feature Configuration
 Programmed phone button (Programmable Button Dial Functions, page 5-60) or
 Camp-on Idle or Camp-on Busy code (Table 4-10, Feature Codes for Dial Plans)

Aeonix provides Camp On features for SLT / POTS telephones for low-cost
deployments.

Setting up Aeonix Features

2

Aeonix Administration Manual Aeonix Features 2-15

  Closed User Groups (CUG)

Currently only the root CUG (i.e. system-wide CUG) is supported in Aeonix.

The use of Closed User Groups (CUG) enables multiple organizations or departments
to co-exist as separate, fully independent units in the same Aeonix system. Each of the
CUGs is treated as a totally different exchange, even though they are managed in the
same Aeonix system.
With CUGs, the same system can be shared by multiple companies, or by different
departments within a company. This feature can be used to create hosted and co-hosted
systems for ASPs and ITSPs (Application Service Providers and Internet Service
Providers).
Dial patterns and feature codes can be separately defined for each CUG.
Administrators assigned to a CUG can view and manage the settings and entities of
this CUG and its subordinated CUGs; Root CUG administrators have access to all
settings and entities in the system (see also Administrator Levels, page 3-4).
Users of different CUGs can be assigned the same ID and alias number. A member of
another CUG can be called by dialing the relevant CUG code followed by the alias
number of this user, provided inter-group access is allowed.
When put on hold or transferred to another number, callers to a CUG are played a
music on hold.
Feature Configuration
 Define dial plans (Dial Plans, page 4-19)
 Define the Closed User Groups (Closed User Groups (CUG), page 4-29).
 Define global settings: When adding profiles, sub-profiles, schedules, and ARS
tables, assign them the relevant CUG. (Once saved, the CUG assignment
cannot be changed.)
 Define entities: When adding users, phones, trunk groups, trunks, gateways,
user groups, and pickup groups, assign them the relevant CUG. (Once saved,
Setting up Aeonix Features

the CUG assignment cannot be changed.)

 When importing users belonging to another CUG than Root, make sure the CUG
is specified (Importing / Exporting Users, page 6-79).

For more information on Closed User Group capabilities and limitations,

contact your Aeonix representative.
2

2-16 Aeonix Features Aeonix Administration Manual

  Computer Telephony Integration (CTI)

The system supports and enables interoperability of standard CSTA 3 based

applications that integrate telephone and computer operations, allowing, for example,
to view information about an incoming call on a workstation screen.

Only Tadiran SIP Phones and Aeonix Touch Softphones, connected to an

Aeonix system, can be controlled via Aeonix CTI application control.

Feature Configuration
 CTI service—set the CTI port (Computer Telephony Integration (CTI), page 12-99).

 Conference Calling

A call with more than two participants is called a conference call. Aeonix supports the
following conference types:

Up to 250 members combined can participate in all types of conference calls

on one server.

 Conference call — the initiator dials the conference call number and all the
members join the conference call. In addition, authorized users can also join an
existing conference call. Up to 125 members can participate in this type of
conference call.
 Meet-me conference — a dial-in teleconference. Each of the participants dials
the same previously agreed conference alias number to join the conference.
 N-way (add-on) conference — the conference initiator calls the other
participants and invites them to join. The maximum number of participants Setting up Aeonix Features
depends on the number of Aeonix servers and available resources.
Secure meet-me conferencing with password (access code) protection is also
available. Conference owners can set or remove access codes. Conference participants
2

Aeonix Administration Manual Aeonix Features 2-17

 can be released on a last-in-first-out basis. The Aeonix MCU service supports multiple
codec types—G.711 and G.729—in a single meet-me conference call.
Feature Configuration
 See Defining Conference Calls, page 12-63
 Meet-me conference — define alias numbers, conference owner, access code,
security parameters, announcements (Defining Meet-Me Conference Aliases,
page 12-79).
 Release last conference member — through programmed phone button
(Programmable Button Dial Functions, page 5-60)

 Deflect (Divert) Call

This feature allows users to divert an incoming call while actively engaged in another
call, or while an idle telephone is ringing, without answering it. The call the user is
engaged in is not interrupted, nor is the incoming caller aware of the diversion.
Feature Configuration
 Programmed phone button (Programmable Button Dial Functions, page 5-60)

 Dial Lock

Dial Lock allows a user to lock their phone so that no outbound calls can be made from
the phone. The user can answer an incoming (emergency) call by entering their PIN,
and the phone will remain in Dial Lock after the call is disconnected.
Feature Configuration
 Define profiles and sub-profiles, or modify default profile settings (Chapter 5,
Profiles).

 Direct Inward Dialing (DID)

Setting up Aeonix Features

This feature allows outside callers to dial a user number and be directly connected to
the user, without going through the system auto-attendant or operator.
2

2-18 Aeonix Features Aeonix Administration Manual

 To implement DID, the trunk group responsible for routing incoming external calls is
programmed with a digit manipulation rule.
Feature Configuration
 Trunk group — on the Incoming Routing tab, define a DNIS manipulation rule
that removes the prefix digits from the dialed number or numbers (Defining Digit
Manipulation Rules for Trunk Groups, page 9-14).

 Dispatch Console

The Dispatch Console application is used to monitor and coordinate responses to both
emergency and day-to-day operations across multiple locations. Dispatchers can
easily communicate with peers at the click of a button and all calls in the Dispatch
Console can be recorded and stored for future analysis and review.
The Dispatch Console also supports interoperable communications among users of all
devices, wherever they are located, and provides control of remote extensions through
an easy-to-use on-screen interface.
The Dispatch Console is composed of a left phone, a right phone, and a PC between
them. It can be run from a web browser via a PC or touch screen portable devices, such
as a tablets and smart phones. When a user connects to the Dispatch Console, the grid
and buttons are displayed as defined by the administrators of the Dispatch Console,
according to the profile associated with the Dispatch Console.
Feature Configuration
 Define dispatch consoles (Defining a new Dispatch Console, page 12-106)
 Define dispatch console profiles (Defining a Dispatch Console Profile, page 12-107)
 Dispatch user configuration—set up a user as a dispatch console user (Defining
User Identity Settings, page 6-14)
 Automatically conference aliases (System Information, page 14-25)

 Do Not Disturb (DND)

Setting up Aeonix Features
The DND feature blocks the telephone for all incoming calls. Callers to a phone with
DND status receive a busy tone or are forwarded to another predefined destination. If
a ULA owner has DND assigned, calls to this group are immediately disconnected.
Users can activate or cancel DND from their Aeonix Web Portal, or from their phones
by pressing a programmed button or dialing the DND feature code. Rules for
2

Aeonix Administration Manual Aeonix Features 2-19

 forwarding or rejecting incoming calls on DND are specified in the user’s Incoming
Call Routing profile (see Incoming Call Routing Sub-profiles, page 5-31).
Feature Configuration
 Programmed phone button (Programmable Button Dial Functions, page 5-60) or
 DND code (Table 4-10, Feature Codes for Dial Plans) or
 Aeonix Web Portal for Users (refer to the Aeonix Configuration Guide for End
Users)

 Emergency Conference Calling

Emergency Conference calls include several users and/or user groups under dedicated
alias numbers. These alias numbers function as virtual conference rooms. When an
initiator dials a conference call number, all the members join the conference call.
Authorized users can also join an existing conference call. The system can be
configured to notify participants of the incoming conference call. Up to 125 members
can participate in a conference call.
Emergency Conference Service implements a special Conference Call template,
which has the following specific aspects:
 Emergency Conference Call supports the Tadiran Panic Button SIP device.
 An Emergency Conference is initiated when a SIP endpoint dials the alias of
an Emergency Conference.
 The Emergency Conference displays the name of the endpoint caller. A name
can be associated with the Tadiran Panic Button device, so that conference
members receiving an invite to join can see who/what initiated the Emergency
Conference.
 The Emergency Conference call is created from a pool of aliases. If no alias is
available, the Emergency Conference call will be created without an alias, so
that emergency calls will always be supported.
Setting up Aeonix Features

 Unlike the normal Conference Call, there is no Announcers Tab for setting up
announcers. An emergency call should not be cluttered with announcer
prompts.
Feature Configuration
 See Defining Emergency Conference Calls, page 12-71
2

2-20 Aeonix Features Aeonix Administration Manual

  Enhanced Emergency 911 Call Support (ELIN / LLDP)

Where emergency centers are available, the system can be configured to support
emergency calls. Users in distress can call for help without having to tell the
emergency operator where they are; this information is automatically provided
through the phone from which they are calling. Call blocking definitions, such as toll
barrier rules and ANI restrictions, are not applied to emergency calls. Emergency calls
can be placed from any phone connected to Aeonix, regardless of the login status of
the phone. The only exceptions are immediate hot station phones, which call an
individually specified emergency number.
Aeonix 4.1 supports Link Layer Discovery Protocol (LLDP) for emergency
Emergency Line / Location Identification Number (ELIN) processing. The ELIN
number for a SIP end-point can be defined in Aeonix, in which case the ELIN will be
added by Aeonix during an emergency call. Alternatively, the ELIN can be defined in
the terminal switch to which the end-point is connected. In this default case, the ELIN
is loaded to the phone from the switch by the switch firmware, and from there is loaded
up into the Aeonix database. Aeonix Administrators must be aware that any ELIN
programming on the switch will take precedence over an Aeonix-defined ELIN .
Feature Configuration
 For users—set emergency call settings for their location (Defining Emergency Call
Settings, page 4-16).
 For a specific phone—set ELIN (Defining a Phone in Aeonix, page 7-10).
 Allocate trunk groups per location, or as described in Reserving a Trunk Group for
Emergency Calls, page 9-24.
 Enable emergency callback feature (System Parameters, page 14-27)

 Enhanced SIP Functionality (ESF)

ESF allows users of Tadiran SIP phones to configure programmable buttons such as
Break-in, Conference call, Deflect, Silent monitoring, and Aeonix Contact Center

Setting up Aeonix Features

functions. In order to activate ESF, the Provisioning service must be active (see
Configuring PnP / Provisioning Service, page 12-123) and the domain name (default
spc.aeonix.com) must be set in the DNS server (see ESF for Tadiran SIP Phones,
page 5-20).

In order to benefit from high availability (see Redundancy, page 2-34) a DNS server must be
2

present in the network and accessible to the Aeonix server.

Aeonix Administration Manual Aeonix Features 2-21

 In addition, it is possible to activate this functionality and telephony features directly
via the Aeonix CTI control mechanism (see Computer Telephony Integration (CTI),
page 2-17) without the need for any external application.
Feature Configuration
 User’s Feature Configuration profile—SIP Features Configuration (ESF for Tadiran
SIP Phones, page 5-20)
 Programmed phone button (Programmable Button Dial Functions, page 5-60)
Setting up Aeonix Features
2

2-22 Aeonix Features Aeonix Administration Manual

  FlexiCall

FlexiCall allows users to receive calls on any of their devices. An incoming call rings
on all or specific phones associated with the relevant user until the user answers the
call on one of the phones. If the answering phone is an external device, the call
automatically becomes a mobility call (see Mobility, page 2-27).
Feature Configuration
 User—define the user’s phone numbers by their external or alias numbers
(Assigning Aliases to Users, page 6-19 and Specifying External Phone Numbers, page 6-27).
 User’s Incoming Call Routing profile—specify which phone will ring on an
incoming call (Defining Basic Rules for Incoming Call Routing, page 5-33). Incoming call
routing can also be done by the user.

 FlexIP Softphone

The FlexIP softphone is a comprehensive software-based application, designed to

offer a full range of features and capabilities that combines all the benefits of a
standard phone with the convenience and flexibility of an interactive software
application. The FlexIP softphone can be used as an extension on the
LAN/WAN/Internet, home office phone or remote branch office application phone. It
is meant for traveling between zones, yet always an integral part of the corporate
network. Like any telephone, the FlexIP softphone can receive and make phone calls,
forward incoming calls, automatically answer or play a recorded message and more.
It has the look, feel and functionality of a standard phone with many additional
features that make it ideally suited as an “away from office” office phone.
Feature Configuration
 Licenses (License Information, page 3-35)
 For users that are allowed to use the FlexIP softphone—download the FlexIP
softphone client on each user’s workstation (Downloading the FlexIP Softphone (FLIPS),
page 6-104), or instruct the users to download the FlexIP softphone client by
themselves (FlexIP SoftPhone User Guide).

Setting up Aeonix Features

2

Aeonix Administration Manual Aeonix Features 2-23

  Gateways

Aeonix is a pure VoIP system and requires gateways to connect to legacy equipment
to the PSTN network and to interface digital and analog devices.
Tadiran TGW gateways provide residential telephony and fax services through
broadband networks via FXS and FXO ports, enabling vast deployment in delivering
Aeonix as enterprise-based voice applications.
The Wave Gateway allows Aeonix to integrate the existing hardware of a Coral
IPx/FlexiCom systems. All features of Aeonix are applied to the trunks and phones
(stations) of the Coral IPx/FlexiCom legacy equipment.
Feature Configuration
 Licenses (Licenses, page 3-29)
 TGW gateway configuration (Configuring Tadiran TGW Gateways, page 10-41)
 Wave gateway configuration (Configuring Wave Gateways, page 10-7)
 Define Wave Gateway phones (Chapter 7, Managing Phones).
 Define Wave Gateway trunks (Chapter 8, Managing Trunks).
 Set default user code (Table 4-10, Feature Codes for Dial Plans)

 Group Listening

The speaker key or another dedicated key can be programmed for combined audio to
activate the Group Listening feature. This feature allows simultaneous use of the
speaker and the handset. The conversation is carried on as usual through the handset,
while the conversation is also broadcast through the speaker.
Feature Configuration
 Speaker button with toggle option (Assign dial functions to programmable phone buttons:,
page 5-59) or
 Programmed phone button (Programmable Button Dial Functions, page 5-60)
Setting up Aeonix Features

 Headset Only Mode

Headset Only mode can be used by ACD agents, operators and any other T207M,
T208M/BL, FlexSet-IP 280S IP, as well as FlexSet phone users via the Wave Gateway,
to conduct conversations via a headset. Calls are conducted via the headset even if the
cradle switch is on-hook, enabling users to make full use of the hands-free operation.
A zip tone is heard via the headset indicating incoming calls.
2

2-24 Aeonix Features Aeonix Administration Manual

  Hospitality

Aeonix can be seamlessly integrated with Property Management Systems (PMS),

providing hotel/motel functionality such as messaging, guest directory and details, and
check-in and check-out services.

Currently, Aeonix integrates with Micros (Fidelio / Opera) and Silverbyte

PMS systems.

Aeonix built-in Hospitality features include:

 Wake up — service to guests requesting to be called at a designated time.
 Room Status — a set of 16 flexibly defined room statuses. Changes in room
status are reported to the PMS system for further handling.
Feature Configuration
 Feature setup Defining a Hospitality Service, page 12-41.

 Hot Station

A user’s phones can be configured to act as hot stations. An immediate hot station
automatically calls a specified destination when the user lifts the phone handset or
presses any key on the dial pad. A delayed hot station calls the specified destination
if after an internal dial tone was received, no key is dialed within a certain time period.
Outgoing call routing also includes the capability of defining a user’s phones as hot
stations. A hot station automatically calls a specified destination when the user
operates the phone.
Feature Configuration
 Feature setup and activation is part of the procedure described in Outgoing Call
Routing Sub-profiles, page 5-41.

Setting up Aeonix Features

 Incoming Call Routing (Call Forwarding and Call Rejection)

An Aeonix user’s incoming calls can be rejected or forwarded to another user, a

mailbox, or an external number, depending on configurable conditions. The
availability of the user (idle, busy, or no answer), the user presence, the date or time
2

Aeonix Administration Manual Aeonix Features 2-25

 the call was received, and the caller ID can all be used as conditions for call forwarding
or rejection. For call forward on no answer, a forward delay can be defined.
Feature Configuration
 For a specific user—define or modify incoming call routing rules (Overriding
Incoming Call Routing Rules, page 6-40). Mandatory and optional rules can only be
changed in the Incoming Call Routing sub-profile.
 For multiple users—define or modify the relevant Incoming Call Routing
sub-profile (Incoming Call Routing Sub-profiles, page 5-31).
See also Page Queue, page 2-31.

 Lightweight Directory Access Protocol (LDAP)

Aeonix can add, delete, and update users from an Active Directory or any LDAP based
directory. This capability allows for using a central LDAP based organizational
directory as the primary reference in the enterprise for user data. Any change in user
data in the directory can then be updated in the Aeonix configuration. Prior to the
update, the system provides the administrator the ability to preview and edit the
changes before saving them to the Aeonix database.
Feature Configuration
 Define LDAP connections (Defining an LDAP Connection, page 4-55).
 Verify LDAP parameters (Testing LDAP Connections Parameters, page 4-61).
 Import LDAP users (Importing LDAP Users, page 6-87).

 Login and Logout

Aeonix allows users to log out from their phones and log in to other phones connected
to the system, provided guest login is not restricted for these phones. This feature is
useful in call centers, where one telephone can be used consecutively by several agents
working in separate shifts. It also allows temporary assignment of a phone to a guest
or to IT personnel for maintenance purposes.
Setting up Aeonix Features

Once a user has logged in to a phone, the user’s profile settings are applied to this
phone. A user is automatically logged in to a phone if the user is defined as its default
user.
Feature Configuration
 Set the user alias and PIN code for authorized login / logout (Defining User Identity
Settings, page 6-14). The PIN code can also be specified by the user.
2

2-26 Aeonix Features Aeonix Administration Manual

  Mobility

Mobility provides an internal dial tone and Aeonix services to users of remote and
cellular phones. Once recognized by the system, external callers, as Aeonix users, can
place calls and benefit from Aeonix features. An authentication process, based on a
combination of the caller number, user name, and PIN password, prevents service
abuse by hackers or unauthorized callers.
Mobility significantly cuts costs by allowing traveling personnel and employees to
place calls through the Aeonix network, rather than through expensive cellular and
long-distance lines. The service can be implemented through:
 Call-through—the external user calls a dedicated number and receives a dial
tone after successfully completing the authentication process.
 Callback—the external user calls a dedicated number. Aeonix identifies the
user, disconnects the call, and calls the user back at a predefined callback
number. Upon answering the call, the user receives a dial tone.
During a mobility call, a DTMF-tone based interactive subscriber’s menu allows the
user to activate basic call features by pressing keys on the phone dial pad. Users can
transfer calls to their desk phones or mailboxes, divert calls to other users, monitor
calls, place new calls, and more.
Feature Configuration
 Mobility service—set up call-through and callback alias numbers. For each alias,
define call parameters and access rules. (See Defining Mobility Aliases, page 12-89.)
 User—set the user alias and PIN code (Defining User Identity Settings, page 6-14) and
configure mobility access rules (Configuring Mobility Rules for a User, page 6-62).
 User—set Callback and Call-through settings to determine whether the caller’s
external number (ANI) or alias number is displayed to the party receiving the call
(Feature Configuration Sub-profiles, page 5-15).

 Multi-Level Administration

Aeonix allows for complete multi-level administration by assigning administration Setting up Aeonix Features
level profiles and their associated administration tasks (see Administration Levels and
Tasks, page 1-9) to subsets of users. This determines which users in the system have the
authority to access and/or manage which particular pages in the Aeonix Web Portal.
In addition to the default levels (see Table 1-3 on page 1-9), the administrator is
authorized to define additional administration level profiles with customized
administration tasks. When defining administration level profiles, the administrator
2

Aeonix Administration Manual Aeonix Features 2-27

 can assign either Read/Write or Read Only privileges to the specified administration
tasks.
For example, when defining an administration level profile that grants Read/Write
privileges for the Users task, users whose user profile is associated with this
administration level will be authorized to add new users to the system. When added,
these new users are then also associated with a specific user profile that includes a
certain administration level and corresponding administration tasks, allowing them to
access and/or manage the particular Aeonix Web Portal pages associated with this
level.
Feature Configuration
 Define administration level profiles (Chapter 5, Administration Level
Sub-profiles).

 Multi-Tenant Mode

Aeonix Multi-Tenant Mode is exclusively run in the A4C environment.

Multi-Tenant Mode is invoked in an Aeonix A4C instance when it is created
as a Multi-Tenant Mode instance in the Aeonix4Cloud Portal.

Aeonix Multi-Tenant Mode supports multiple tenants running in a single instance of

Aeonix on a single virtual machine. Each tenant implements the telephony system of
a customer. The tenants are managed through the Aeonix4Cloud Portal. A dealer can
manage multiple tenants on a single virtual machine. Tadiran manages the entire
collection of tenants and dealers in the cloud / data center. When an Aeonix instance
runs in Multi-Tenant Mode, it presents additional features in the Admin GUI that are
not available in the normal mode.
Setting up Aeonix Features

Aeonix Multi-Tenant Mode supports basic Aeonix UC&C operation and

SeaMail voicemail operation. As multi-tenant is purposed to reduce cost for
smaller telephony installations, the current version does not support Aeonix
Contact Center or Aeonix Logger.
2

2-28 Aeonix Features Aeonix Administration Manual

 The goal of Aeonix Multi-Tenant Mode is to reduce the overall hosting costs in the
Aeonix4Cloud environment, and to pass those cost savings to dealers and their
tenants/customers..
Feature Configuration
 For tenant creation, refer to Aeonix A4C Portal Guide for Partners / Dealers.
 For operation of Aeonix Mult-Tenant Mode features, see Chapter 15, Aeonix
Multi-Tenant Mode.

 Music on Hold (MOH)

Callers placed on hold are played music or messages from:

 An audio file from the music source defined for the entire system (on the root
CUG level).
 A Music service that defines a music source from an audio file or IP
streaming. Once a Music source is defined, callers placed on hold by aliases
associated with the music source are played music or messages defined for the
specified source.

Callers placed on hold by aliases not associated with a specific Music

Service continue hearing music or messages from the default system-wide
music audio file as defined in the root CUG.

Feature Configuration
 Root CUG (Closed User Group)—specify the default music on hold source for
G729, PCM-A and PCM-U codecs when no specific MOH was defined for the
target alias (Defining a Closed User Group, page 4-32).
 Music service–specify the music source (file or IP stream) and the aliases that
use this MOH (Configuring a Music Source and MOH Alias Numbers, page 12-114)

 Mute Setting up Aeonix Features

Mute Microphone turns off the microphone before or during a conversation, so that
the other party cannot hear the user. Mute Ringing turns off the ringing of an
incoming call.
Both mute types are activated by pressing a dedicated soft key or programmed button
on an MGCP keyset (FlexSet-IP 280S, T207M, T208M/BL) or on a digital keyset
2

Aeonix Administration Manual Aeonix Features 2-29

 (FlexSet 120, 120D, 120L, 120S, 121S, 280, 280D, 280D-HS, 280S, 281S, DKT, and
DST; connected through a Coral Wave Gateway).
Feature Configuration
 Programmed phone button (Programmable Button Dial Functions, page 5-60)
 User’s Feature Configuration profile—only to mute the microphone on incoming
voice page calls (Feature Configuration Sub-profiles, page 5-15)

 Network Alarms

Aeonix creates and displays alarm messages when system resources or licenses are
becoming scarce or malfunctioning (see Alarms, page 14-1). Depending on system
configuration, these alarms are displayed in the Alarms report, sent to an external
SNMP / NMS server, or sent to specified email addresses.
Feature Configuration
 Set the alarm threshold and notification method for each alarm type (Configuring
Alarm Notification Options, page 14-22).
 Set parameters for accessing SNMP / NMS server or sending emails to SMTP
addresses (Configuring Alarm Access Parameters, page 14-18).
Setting up Aeonix Features
2

2-30 Aeonix Features Aeonix Administration Manual

  Outgoing Call Routing (Dialed Number Manipulation)

Outgoing Aeonix calls can be manipulated and rerouted by the system. Outgoing call
routing is flexible and based on configurable Automatic Route Selection tables. The
system supports a variety of operations for truncating, modifying, or replacing all or
specific outgoing call numbers, and redirects the calls accordingly. In addition, the
caller (user) ID information displayed to external destinations can be hidden or
redefined.
Feature Configuration
 For a specific user—define or modify outgoing call routing settings (Overriding
Outgoing Call Routing Parameters and Rules, page 6-43). Rules defined in an Outgoing
Call Routing sub-profile cannot be modified at the user level.
 For multiple users—define or modify the relevant Outgoing Call Routing
sub-profile (Outgoing Call Routing Sub-profiles, page 5-41).
See also Page Queue, page 2-31.

 Page Queue

A call can be put on hold by dialing a dedicated page queue alias number and then
retrieved by dialing this number from any other phone in the system. For example, an
office manager or hotel operator places a call received for a certain user in page queue
and then announces to this user which page queue alias to dial in order to retrieve the
call.

Page Queue is an Aeonix feature that incorporates the functionality of call

transfer. It is not necessary or recommended that the user press Transfer
before pressing Page Queue as a “destination”. Page Queue will
automatically transfer the call to the configured alias numbers as described
in Configuring Page Queue Park/Pickup, page 12-117.

Feature Configuration Setting up Aeonix Features

 Define Page Queue alias numbers (Configuring Page Queue Park/Pickup, page 12-117).
 Programmed phone button (Programmable Button Dial Functions, page 5-60)
2

Aeonix Administration Manual Aeonix Features 2-31

  Profile Programming

User settings are defined through user profiles. Parameters set up in profiles include
general and timeout settings; call feature configuration; incoming call forwarding or
rejection; manipulation rules for outgoing calls; toll barrier restrictions; and
programming of phone buttons.
Some profile parameters are configured by the administrator only, while others can be
overridden by the users depending on override permissions. Trunk groups are
programmed using trunk group profiles.
Feature Configuration
 Define profiles and sub-profiles, or modify default profile settings (Chapter 5,
Profiles).
 Assign sub-profiles to User or Trunk Group Profiles (Defining a User Profile, page 5-84
and Defining a Trunk Group Profile, page 5-86)
 Assign the profiles to users and trunk groups (Assigning a Profile to a User, page 6-30
and Defining Trunk Group Settings, page 9-9)
 Override sub-profile parameters for a specific user or trunk group (Overriding User
Profiles, page 6-29 and Overriding Trunk Group Profiles, page 9-10). Sub-profiles may be
override-protected.

 Programmable Phone Buttons

Users can configure programmable buttons on their phones to call any user or external
number, or to activate a specific feature. A button programmed to ring a specific
number will light up when that number is occupied or flash when there is an incoming
call from the programmed number.
Feature Configuration
 For a specific user—define or modify phone button programming (Configuring a
User’s Phone Profiles, page 6-49). Locked buttons can only be reprogrammed in the
relevant phone sub-profile.Aeonix 4.1 and later support Programmable Button
Sync between Aeonix and Tadiran SIP phone memory. See Configuring a User’s
Phone Profiles, page 6-49 for details.
Setting up Aeonix Features

 For multiple users—define or modify the relevant phone sub-profile (Phone Profiles,
page 5-54).
See also Page Queue, page 2-31.

 PnP / Provisioning for Tadiran SIP Phones and P-Series Phones

The Provisioning service allows Tadiran SIP phones and P-Series phones (see
2

Supported Devices, page 1-12) to be automatically updated in Aeonix with the latest

2-32 Aeonix Features Aeonix Administration Manual

 configuration and firmware files. Provisioning profiles contain parameters that are
used to automatically configure these phones. In addition to provisioning profiles,
configuration sets (see Defining New Configuration Sets, page 12-130) can be associated
on the provisioning profile level for both these phone types. All provisioning
parameters are stored in the Aeonix database and are protected with a full redundancy
mechanism.
Once defined, the system automatically updates the phones’ configuration according
to the phone’s parameters, provisioning profile, and configuration sets.
In parallel to the provisioning service, Plug and Play (PnP) modes can be used to
quickly and easily define on premise as well as remote (via VPN) Tadiran SIP phones
on site.
There are two PnP modes:
 Auto Phone mode – Used to generate new Tadiran SIP phone entities upon
phone requests for provisioning. In this case, no default user is assigned to the
phone. When Auto Phone mode is activated, a default user can be assigned
using feature code 159 (default).
 Auto Phone & User mode – Used to generate new Tadiran SIP phone, as
described above and, in addition, used to automatically generate users for these
phones

Alternatively, users can be imported for PnP purposes.

Feature Configuration
 Provisioning service—specify the polling interval to check for new phone
configurations including firmware updates (Configuring PnP / Provisioning Service,
page 12-123)
 Define provisioning profiles (Managing Provisioning Profiles, page 5-91)
 Define new configuration sets (Defining New Configuration Sets, page 12-130)
 Assign provisioning profiles to phones (Provisioning Parameters, page 7-16)
 Importing PnP users (Importing / Exporting Users, page 6-79)

Setting up Aeonix Features

 Set default user—from phones defined as Default User or with no user value
when in Auto Phone PnP mode (Table 4-10, Feature Codes for Dial Plans)

 Recall on Transfer

When a call is transferred to a destination that does not answer, the call is returned
(recalled) to the initiator of the transfer, according to the transferor’s Recall on
2

Transfer timer (see Recall on transfer timeout, page 5-14).

Aeonix Administration Manual Aeonix Features 2-33

 Recall on Transfer can be activated for all calls (internal and external).
Feature Configuration
 Recall on Transfer—enable or disable Recall on Transfer in the Feature
Configuration profile (Feature Configuration Sub-profiles, page 5-15). This parameter can
be overridden for individual users

 Redial

Redial allows users to dial the last dialed number by pressing a dedicated soft key,
programmed button, or code.
Feature Configuration
 Programmed phone button (Programmable Button Dial Functions, page 5-60) or
 Redial code (Table 4-10, Feature Codes for Dial Plans)

 Redundancy

An Aeonix network can be configured as a cluster of several distributed Aeonix

servers. Each server keeps its database updated through ongoing communication with
the other servers in the cluster. As a result, Aeonix networks are fully redundant and
fault-tolerant.
The current connection status of each server belonging to an Aeonix cluster is
displayed in the Web administration. To ensure smooth operation even in the case of
a server shutdown, up to nine backup servers can be specified on each endpoint.
Registration to alternative servers is also available for Wave Gateway, and SIP
gateways, which connect legacy phones and trunks to Aeonix.
In addition, users of Tadiran SIP phones, which support DNS-SRV as their Transport
protocol, benefit from High Availability redundancy. When High Availability is
enabled, ongoing calls and call features, including transfer, hold, and retrieval options,
Setting up Aeonix Features

continue unaffected.

In order to benefit from redundancy, a DNS server must be present in the network and
accessible to the Aeonix server.
2

2-34 Aeonix Features Aeonix Administration Manual

 Status Display
 Connection status of each server in the Aeonix network (Displaying Cluster
Information, page 14-34)
 High Availability activation and setup (Enabling and Configuring High Availability,
page 14-51)

 Registration Load Balancing

Endpoint registration can be effectively controlled on the cluster level. This improves
resource usage by optimizing phone allocation among the servers. A Load Balancing
Logic (LBL) algorithm takes into account server and endpoint locations, as well as the
maximum number of endpoints allowed per server. Endpoints can migrate to any
server as per their call agent list, thereby creating the best mix of endpoint allocation
among the servers of a cluster.
Feature Configuration
 Feature setup (Configuring the Cluster for Registration Load Balancing, page 14-41) and
activation (Displaying Cluster Information, page 14-34)

 Remote Server Maintenance

Aeonix servers can be configured and maintained from a remote workstation through
a secure programming interface designed for low bandwidth resources.
Server maintenance functions include server IP address configuration, version
upgrade, cluster setup, and more. Standard and proprietary Linux shell script
commands facilitate efficient debugging tasks, including event tracing, resource
monitoring, and identification of call failure causes. Detailed log files and third-party
network analysis tools are also available. For details, see Server-based Maintenance
Tools, page 14-79.

Setting up Aeonix Features

2

Aeonix Administration Manual Aeonix Features 2-35

  Reports

Aeonix includes reports displaying updated information. Most reports can be

configured to be sent to specific email addresses. Alarm report details can also be
viewed through an external SNMP application or NMS server.
Report Display
 Cluster status (Clusters, page 14-33)
 Licenses (Licenses, page 3-29)
 Server / License / Wave Gateway alarms (Viewing Alarms, page 14-2)
 Voicemail reports (refer to the SeaMail Administration Manual listed in Related
Documentation, page 1-17)

 Room Recording

Room recording allows a room to be continually recorded for monitoring purposes via
the microphone of the designated device.
CP860 IP conference phone is the Tadiran certified device for Room Recording. It
comes equipped with three built-in microphones for 360º voice pickup over a distance
of 10 feet.

Optional expansion microphones are available for even greater reception for
larger conference rooms.

Feature Configuration
 Call Recording Rule—set up the call recording rule associated with the room
recording device (Defining a Call Recording Rule, page 12-28)
 Room Recording—set Continuous connection in the Feature Configuration
profile (Feature Configuration Sub-profiles, page 5-15). This parameter can be
overridden for individual users.
Setting up Aeonix Features

 Call Waiting—clear in the Feature Configuration profile (Feature Configuration

Sub-profiles, page 5-15). This will prevent call waiting tone interruptions during
recording.
 When using two Aeonix Logger trunks (one active and the other
passive)—define the Keep-alive timeout to be smaller than the Room Recording
timeout (Keep-alive timeout, page 8-14)
 Define SIP Session parameters (Session-Expires Time, page 7-21 and Minimum
Session-Expires, page 7-22)
 For optimal performance, configure the device side (contact your Aeonix
representative for details)
2

2-36 Aeonix Features Aeonix Administration Manual

  Schedule Programming

Schedules are used to have a system activity, such as forwarding calls to a mailbox, be
performed only at a specific time or at regular intervals.
Schedules consist of one or more time frames. Each time frame specifies a once-only
time and date or a yearly, monthly, or weekly recurrence pattern. Complex scheduling
specifications can be defined as well, for example, every year on the last Thursday in
November between 11 AM and 1 PM.
Feature Configuration
 System-wide schedules (Schedules, page 4-37)
 Schedules to be assigned to a User or Trunk Group profile (Schedule Sub-profiles,
page 5-28)
 Schedules for a specific user or trunk group (Overriding Schedules, page 6-39)

 Sea Attendant

The Sea Attendant is a unified communications desktop productivity tool designed to

help attendants better manage and distribute incoming calls. The Sea Attendant
provides a highly intuitive visual interface that includes screen-based call status and
call handling prompts, real-time Busy Lamp Field status, and a telephony keypad for
fast, efficient attendant call handling of other system users.
The Sea Attendant runs on top of the Aeonix system and allows attendants to:
 See the presence status of all users
 See all incoming calls from one screen, allowing attendants to prioritize calls
 See call states, such as when a call has been held for too long and its state
time turns from green to red, providing attendants with additional information
to help them handle calls more efficiently
 Quickly access all Outlook contacts, system users, and private directories

Setting up Aeonix Features

 Answer or redirect incoming calls to voicemail, place calls on hold, retrieve,
transfer, mute and set up three-way conference calls
 Customize font, size, and color appearance of incoming, held, and active calls
The Sea Attendant integrates with Microsoft Outlook and supports a wide range of
Aeonix telephony features, as well as peer-to-peer real-time Instant Messaging (IM)
and video calls between logged-in Sea Attendant and Sea Navigator users. When
offline, sticky notes can be sent to and retrieved by users once they go online. Upon
2

login, the application is automatically upgraded if a new version is available.

Aeonix Administration Manual Aeonix Features 2-37

 A Tadiran license is required to use the Sea Attendant. For information about
Sea Attendant features and usage, refer to the Sea Attendant User Guide or the
Sea Attendant Online Help.

Sea Attendant can be used with the following phones: Tadiran SIP phones,
P-Series, FlexSet via Wave Gateway, FlexSet-IP 280S, FlexIP Softphone,
T200M series (T207M, T208M/BL).

No Support for: SLT via Wave Gateway, SLT via Tadiran-TGW gateway, or
any other third-party SIP phones.

The number of users that can have the Sea Attendant installed on their computer
depends on the system license settings and is displayed on the License Information
page (see Figure 3-15 on page 3-35).
Feature Configuration
 Licenses (License Information, page 3-35)
 For a specific user—specify whether the user is allowed to use the
Sea Attendant (Overriding Feature Parameters, page 6-36).
 For multiple users—allow or restrict the use of the Sea Attendant in the relevant
Feature Configuration sub-profile (Feature Configuration Sub-profiles, page 5-15).
See also Page Queue, page 2-31.
 For users that are allowed to use the Sea Attendant—download the Sea
Attendant on each user’s workstation (Downloading the Sea Navigator / Sea Attendant
Client, page 6-102), or instruct the users to download the Sea Attendant by
themselves (Aeonix Configuration Manual for End Users).
Setting up Aeonix Features
2

2-38 Aeonix Features Aeonix Administration Manual

  Sea Navigator

The Sea Navigator is an advanced desktop communications manager application that

runs on top of the Aeonix system. It allows users to place and receive calls, as well as
access their voicemail, email, and fax messages, from a single unified location.
Sea Navigator users can establish, handle, and answer calls and Instant Messaging
(IM) chats by clicking icons, pop-up menu options, or programmable virtual buttons.
Public and personal libraries allow users to view and communicate with other
Sea Navigator users, Microsoft Outlook and LDAP contacts, and any specified
external party. For Sea Navigator users, their current idle/busy status, online status,
and presence information is displayed as well.
In addition, the Sea Navigator supports TAPI and Terminal Services, upgrading
automatically to a new version, password-secured access, and many other features.
For information about the Navigator features and usage, refer to the Sea Navigator
Online Help.
The number of users that can have the Sea Navigator installed on their computer
depends on the system license settings and is displayed on the License Information
page (see Figure 3-15 on page 3-35).
Feature Configuration
 Licenses (License Information, page 3-35)
 For a specific user—specify whether the user is allowed to use the
Sea Navigator (Overriding Feature Parameters, page 6-36).
 For multiple users—allow or restrict the use of the Sea Navigator in the relevant
Feature Configuration sub-profile (Feature Configuration Sub-profiles, page 5-15).
See also Page Queue, page 2-31.
 For users that are allowed to use the Navigator—download the Navigator on
each user’s workstation (Downloading the Sea Navigator / Sea Attendant Client,
page 6-102), or instruct the users to download the Navigator by themselves
(Aeonix Configuration Manual for End Users).

Sea Navigator can be used with the following phones: Tadiran SIP phones, Setting up Aeonix Features
P-Series, FlexSet via Wave Gateway, FlexSet-IP 280S, FlexIP Softphone,
T200M series (T207M, T208M/BL).

No Support for: SLT via Wave Gateway, SLT via Tadiran-TGW gateway, or
any other third-party SIP phones.
2

Aeonix Administration Manual Aeonix Features 2-39

  Silent Monitoring

Silent monitoring refers to the practice of call center managers or senior agents
listening in on conversations between agents and customers, as well as for voice
recording purposes. It is generally used in training as well as day-to-day call center
interactions to ensure that customer service and productivity goals are being met. For
quality assurance purposes the agent is not aware if the call is being monitored or not.

Silent monitoring can be performed on both sides of the conversation or on

one of the conversing parties only (Split Silent Monitoring for listening
purposes).

Feature Configuration
 Assign users that are authorized to perform Silent Monitoring (Defining Permission
Settings, page 6-74)
 Authorize trunk group members to perform Silent Monitoring (Authorizing Trunk
Group Members to perform Silent Monitoring, page 9-26)
 Programmed phone button (Programmable Button Dial Functions, page 5-60) or
 Silent Monitoring codes (Table 4-10, Feature Codes for Dial Plans)

 Single Sign On

Single Sign On (SSO) is a standard for secure domain environments, in which

authentication is established when the user logs into to the secure domain through an
SSO-managed protocol. When the user is logged in at their workstation, they may
launch authorized applications which do not then present their own login sequences.
The SSO protocol uses LDAP User ID during authentication, and authorized
applications check against that LDAP User ID when launched.
Feature Configuration
 Set up Aeonix servers in a Kerberos-based SSO environment Single Sign On,
Setting up Aeonix Features

page 4-67.
 Turn Aeonix SSO integration on / off System Parameters, page 14-27.
2

2-40 Aeonix Features Aeonix Administration Manual

  TAPI Service Provider and DialIt

Aeonix supports TAPI (Telephony Application Programming Interface) click-to-call.

The TAPI Service Provider links the TAPI subsystem in Windows with Aeonix,
allowing system users to make calls directly from their Outlook contacts.
In addition, DialIt is included in the TAPI Service Provider package. It allows system
users to make calls from anywhere on their workstation.
Feature Configuration
 Download the TAPI Service Provider and DialIt application on each user’s
workstation (Downloading the TAPI Service Provider and DialIt, page 6-105), or instruct the
users to download by themselves (Aeonix Configuration Manual for End Users).

 Timeout Programming

A timeout defines the amount of time the system waits before it performs a certain
activity (for example, disconnects a call or rings again for a held call). Several timeout
values can be set.
Feature Configuration
 For a specific user or trunk group—define or modify timeout values (Overriding
Timeout Parameters, page 6-35). Some timeouts are preset and cannot be modified.
 For multiple users or trunk groups—define or modify the relevant Timeout
sub-profile (Timeout Sub-profiles, page 5-12).
See also Page Queue, page 2-31.

 Toll Barrier

Toll barrier rules can be set up to block outgoing calls depending on the destination.
Exceptions to these rules can be defined as well. The system performs an analysis on
the dialed digits in order to allow or restrict the call according to these rules.
This feature is mostly used for preventing employees from placing costly Setting up Aeonix Features
premium-rate service calls or international calls.
Feature Configuration
 For a specific user—set or modify toll barrier rules (Overriding Toll Barrier Rules,
page 6-37).
 For User or Trunk Group profile—define or modify the relevant Toll Barrier
sub-profile (Toll Barrier Sub-profiles, page 5-24).
See also Page Queue, page 2-31.
2

Aeonix Administration Manual Aeonix Features 2-41

  Transfer

An Aeonix user can transfer both internal and external calls to another destination
within the system or outside it. During the transfer, the other call participant or
participants are put on hold and hear music or an announcement defined for the system
(see Multi-Tenant Mode, page 2-28).
Call transfer can be screened or unscreened:
 Screened transfer—the user announces the call before transferring.
 Unscreened transfer—the user transfers the call without a prior announcement
or without notifying the recipient.
To transfer a call, the user presses a programmed button or soft key on the phone.
Feature Configuration
 Programmed phone button (Programmable Button Dial Functions, page 5-60)
 Flash mode (Feature Configuration Sub-profiles, page 5-15).

 Unified Messaging and Voicemail

Aeonix includes SeaMail as its fully integrated default voicemail and Unified
Messaging (UM) application.
The Aeonix system can also be set up to work with additional voicemail programs,
such as Microsoft Exchange connected through SIP Trunk presenting the UC, as it can
be connected to MS LYNC Mediator.
SeaMail users can receive voice and fax messages as email attachments, or have their
emails converted to voice files and listen to them from their voice mailbox.
SeaMail users can:
 Receive voice and fax messages as email attachments, or emails as
text-to-speech converted voice messages (depending on the system
Setting up Aeonix Features

configuration)
 Hear and manage voice messages
 Record and forward messages to mail boxes or groups
 Specify their own voicemail settings, including password, introductory
greeting, and wake-up calls
 Activate or disable call screening
SeaMail provides an automated attendant facility, enabling callers to a “main”
2

business number to access directory assistance or self-route calls to various

2-42 Aeonix Features Aeonix Administration Manual

 destinations, such as specific departments, alias numbers, or mailboxes. SeaMail’s
intuitive Web-based scripting tool facilitates multi-level message handling and
Interactive Voice Response (IVR) programming.
Feature Configuration
 Define the SeaMail as a SIP voicemail service (Defining Voicemail Applications in
Aeonix, page 12-140).
 Set SeaMail access numbers and server connection settings (Accessing SeaMail,
page 12-148).
 Assign voicemail boxes to users (Managing Voicemail Boxes for Users, page 6-24).
 Set mailbox and other voicemail parameters (refer to the SeaMail Administration
and Configuration Manual for Aeonix).

 User Line Appearance (ULA)

ULA provides workgroup shared line button functionality. A user can be defined as
the owner of a ULA group, in which an incoming call can ring, as well as flash a
programmed shared line button, at the devices of the group members. The members
can also place calls on behalf of their group owner.
ULA is ideal for management positions in which a manager (the group owner) is
assisted by one or more assistants (the regular group members). An incoming call to a
ULA group owner’s alias can be answered and handled by any of the assistants.
Each ULA group consists of its group owner and one or more regular members (up to
25 members per group). The manager (owner) and assistants (regular members) can:
 View and answer incoming calls to the ULA owner
 Have incoming calls to their ULA ringing at their phones immediately, after a
delay, or not at all
 Put a call on hold for consultation. Any member can retrieve a held call unless
the call is put on exclusive hold.
 Transfer the call

Setting up Aeonix Features

 Transfer calls to the manager’s voice mailbox
 Voice page the manager
 Place calls on behalf of the manager
 The assistants can call the manager with a double click (on a ULA button)
The manager (owner) can also deflect an incoming call before it gets answered.
Keyset buttons can be programmed as shared line buttons. As soon as a ULA group
2

member answers an incoming call, the devices of the other members stop ringing, but

Aeonix Administration Manual Aeonix Features 2-43

 the shared line button remains lit on the phones. The button flashes, blinks, or is
steadily lit to reflect the current status of the call.
For each user, the Web Portal displays (if available) the ULA group this user owns and
the owner of groups to which the user belongs as a regular member. The Portal also
shows to which groups the user is currently logged in.
Feature Configuration and Management
 ULA owner configuration—set up a user as the owner of a ULA group, and
specify the members and ring parameters of this group (Managing a User’s ULA
Settings, page 6-65).
 ULA call routing parameters—for each user owning a ULA group, specify
incoming routing parameters related to ULA. See Incoming Call Routing Sub-profiles,
page 5-31.
 Exclusive Hold—enable or disable Exclusive Hold in the Feature Configuration
profile (Feature Configuration Sub-profiles, page 5-15). This parameter can be
overridden for individual users.
 Phone programmable buttons—in the user’s phone profile, program phone
buttons with ULA features as required (Phone Profiles, page 5-54).

 User Presentation

The system identifies users by their unique User ID. The display of user information
on internal phones is specified through profiles. This parameter can be overridden for
all phones of an individual user or for specific phones belonging to this user.
When a user connecting from outside places an internal call (mobility call), the ANI
number or the internal display name of this user is displayed at the called destination,
as specified in the mobility settings of this user.
Feature Configuration
 User—set the display name (Defining User Identity Settings, page 6-14)
 Phone—override the display name for a specific phone (Configuring a User’s Phone
Profiles, page 6-49)
 Mobility—set Callback and Call-through settings to determine whether the
caller’s external number (ANI) or alias number is displayed to the party receiving
Setting up Aeonix Features

the call (Feature Configuration Sub-profiles, page 5-15).

2

2-44 Aeonix Features Aeonix Administration Manual

  Virtual Endpoints

The Virtual Endpoint service enables external customer applications (such as IVR
systems) to manage the control flow of incoming calls, allowing these applications to
perform operations on calls.
Feature Configuration
 Virtual Endpoints service—define virtual endpoint alias numbers (Defining Virtual
Endpoint and Virtual Agent Alias Numbers, page 12-152).

 Voice Page

This feature allows an Aeonix user to place a call and talk without having to wait for
the called person to manually answer the call. Similar to receiving an intercom call,
the called user hears the paging via the telephone speaker and can answer directly or
after picking up the handset. Each user also has the option of blocking this feature and
receiving voice page calls as regular calls.
Voice page calls are of higher priority than regular calls and announced by a special
ring tone. Call forwarding and rejection rules are not applied to these calls.

Voice page destinations must be MGCP keysets (FlexSet-IP 280S, T207M,

T208M/BL) or digital keysets (FlexSet 120, 120D, 120L, 120S, 121S, 280,
280D, 280D-HS, 280S, 281S, DKT, and DST; connected through a Wave
Gateway).
Voice page calls to any other device are handled as regular calls.

Feature Configuration
 User’s Feature Configuration profile (Feature Configuration Sub-profiles, page 5-15)

Setting up Aeonix Features

2

Aeonix Administration Manual Aeonix Features 2-45

  Web Portal

The Aeonix Web Portal is a centralized, Java-based web interface that can be accessed
from any workstation connected to the network. To enhance network security, the
Portal can be set up for access via HTTPS (secured HTTP).
The Web Portal’s well-arranged, intuitive structure provides administrators with a
convenient tool to manage Aeonix settings and entities. The Portal supports multiple
languages.
A restricted version of the Aeonix Web Portal is available for each user in the system.
Users access the portal to manage their own parameter settings and presence status.
For more information, refer to the Aeonix Configuration Guide for End Users (see
Related Documentation, page 1-17).

 Zone Page

Zone Page calls include several users and/or user groups under dedicated alias
numbers. When an initiator dials a Zone Page number, the system places calls to all
the members (Auto Answer mode). During the dialing period, which can take a few
seconds, the system plays the mandatory announcement to members that are already
connected to the zone page call. This message is then optionally followed by a user
defined First announcement. During the Zone Page, all the members’ phones will be
muted. Up to 125 members can participate in a Zone Page call.
Feature Configuration
 See Defining Zone Page Calls, page 12-159
Setting up Aeonix Features
2

2-46 Aeonix Features Aeonix Administration Manual

 Chapter 3

Getting Started

3.1 Aeonix Portal for Administrators ...........................................3-1

3.2 Basic Tasks...........................................................................3-5

3.3 Initial Aeonix Configuration .................................................3-17

3.4 Licenses..............................................................................3-29

3.5 General Procedures............................................................3-63

3.6 Aeonix Setup Procedure.....................................................3-67

Aeonix Administration Manual

 3.1 Aeonix Portal for Administrators

This section describes:

 Aeonix Web Page Structure, page 3-2
 Administrator Levels, page 3-4

Aeonix Portal for Administrators

3

Aeonix Administration Manual Getting Started 3-1

  Aeonix Web Page Structure

The layout of the Aeonix Web page and its functional areas have been designed to be
easy to understand and to use. The figure below shows an example page that
exemplifies the basic structure of the Aeonix Web Portal.

Figure 3-1 Aeonix Web

Page

The minimum recommended screen resolution is 1024 by 768 pixels.

Aeonix Portal for Administrators
3

3-2 Getting Started Aeonix Administration Manual

 The Aeonix Web Portal for Administrators consists of the following areas:

Area Function Description

1 Left navigation Contains category and menu items, providing the

pane user with quick and clear navigation

2 Category buttons Clicking Administration, Settings, System, or My

Account displays the relevant menus in the Menu
area.
My Account is not available for the default
administrator aeonixadmin.

3 Menu area Displays the menus, menu options, and

sub-options relevant to the selected category

4 Information area Displays detailed information related to the

functionality of the current page

5 User utility area  Displays the user name, customer (cluster)

name, and date
 Provides shortcuts to password modification,
help, logout, and version information

Aeonix Portal for Administrators

3

Aeonix Administration Manual Getting Started 3-3

  Administrator Levels

Currently only the root CUG (i.e. system-wide CUG) is supported in Aeonix.

An administrator’s display and monitoring capabilities are defined by the Closed User
Group (CUG) to which the administrator belongs (see Closed User Groups (CUG),
page 4-29). The default administrator aeonixadmin and Root CUG administrators can
view and manage all entities and settings in the system. (If not mentioned otherwise,
the screen shots in this manual reflect the aeonixadmin display level.)
CUG administrators can view and manage only entities and settings belonging to their
CUG and sub-CUGs related to this CUG. For example, if the following CUG structure
has been defined:
f

 Root administrators manage all CUGs (including Root)

 Company A administrators manage the CUGs Company A, Company A
Marketing, and Company A R&D.
 Company B administrators manage the CUGs Company B and Company B
Support.
 Company A Marketing, Company A R&D, and Company B Support
administrators manage their respective CUG only.
As with other entities, an administrator’s CUG assignment is performed when this
Aeonix Portal for Administrators

administrator’s user entity is added in the Aeonix Web Portal. This assignment is
mandatory and cannot be changed for entities that have already been defined.

For more information on Closed User Group capabilities and limitations,

contact your Aeonix representative.
3

3-4 Getting Started Aeonix Administration Manual

 3.2 Basic Tasks

This section describes the following basic tasks:

 Configuring HTTPS for the Aeonix Web Portal, page 3-6
 Logging in to Aeonix, page 3-8
 Admin Password Policy, page 3-10
 Accessing Online Help, page 3-14
 Logging out from the Aeonix Web Portal, page 3-14

Basic Tasks
3

Aeonix Administration Manual Getting Started 3-5

  Configuring HTTPS for the Aeonix Web Portal

Aeonix administrators can configure HTTPS secured layer mode access to the Aeonix
web portal by running the aeonix_https.sh script, as follows:
[root@bart ~]# aeonix_https.sh on

If you do not want to use the secured mode, run the script with the off
parameter instead or do not run the script at all.

To determine the current security mode (secured or unsecured), run the

aeonix_https.sh script without any parameter, as follows:
[root@bart ~]# aeonix_https.sh
The system responds by displaying a message that includes the security mode status
(‘not secured’ in the example below).
Aeonix Web Admin HTTPS tool <Aeonix Version>
Use optional argument 'on'/'off' to toggle HTTPS mode.
Aeonix Web Admin is running on HTTP (not secured)

In order for the script to take effect, the Aeonix service must be restarted. Depending
on the case, use one of the following scripts to ensure that the service is started:

If not already running, use: [root@bart ~]# service aeonix start

If already running, use: [root@bart ~]# service aeonix restart
Or:
[root@bart ~]# service aeonix stop
[root@bart ~]# service aeonix start

The aeonix_https.sh changes the settings for the single server (the one it
runs on). If you want to apply the same change for another server in a
cluster, just repeat the procedure on that specific server. This approach
allows you to have different configurations for different servers in a cluster.
Basic Tasks

After running the script and starting the aeonix service, the Aeonix web portal can be
accessed in the usual manner by typing http:// and the address string in the Internet
Explorer Address bar (see To log in to Aeonix:, page 3-8).
3

3-6 Getting Started Aeonix Administration Manual

 The first time you browse, you will get a security alert prompting you to accept the
certifying authority.

The Security Alert may vary according to browser and browser version.

Click View Certificate and follow the instructions to accept the certifying authority.
The next time you browse to the Aeonix web portal, the Security Alert does not appear.

If you use hostname instead of IP address to browse to the portal (e.g.

http://rssys:8080/aeonix), or if your server has multiple IP addresses and you
are not using the first address in the list, some browser versions may
continue to warn you with security alerts. You can ignore these alerts.

Basic Tasks
3

Aeonix Administration Manual Getting Started 3-7

  Logging in to Aeonix

Aeonix administrators log into the Aeonix system as described in the following
procedure. The Aeonix Web Portal runs on most internet browsers, such as Internet
Explorer, Google Chrome, and Firefox Mozilla.

Ensure that the Display all websites in Compatibility View is disabled

before using Internet Explorer to log in to Aeonix.

Before logging in, make sure the Aeonix service is running on one of the
Aeonix servers and the soft key containing the required licenses is uploaded
and deployed on the designated Aeonix License Key server. Refer to the
Aeonix Installation Manual for details (see Related Documentation, page 1-17).

To log in to Aeonix:
1 From the workstation, open your Internet browser.
2 Enter either of the following text strings in the Address bar:
 http://<aeonixserver IP>:8080/aeonix (replace <aeonixserver IP> with the
IP address of the Aeonix server)
 http://<hostname>:8080/aeonix (replace <hostname> with the host name of
the Aeonix server)

By default, after running the Aeonix kickstart, the Aeonix Admin static IP
address Login page address is http://10.0.0.50:8080/aeonix.

3 Click the Go button or press ENTER. The Aeonix Login page is displayed.
Basic Tasks
3

3-8 Getting Started Aeonix Administration Manual

Figure 3-2 Login Page

The Aeonix version and build number is displayed at the bottom right of the
login screen.

The Aeonix Web Portal is configured to be displayed in your default language,

as defined in your General Information profile (see Table 5-4 on page 5-10).
4 If necessary, select another language from the Language drop-down list.
5 Enter the user name and password.

The user name and password for accessing the Aeonix Web Portal for
Administrators are aeonixadmin and anx, respectively. Users defined as
administrators automatically access the Web Portal for Administrators after
logging in with their user name (ID) and password.

6 Enter the Security Code from the Captcha text that is displayed to the right.
The field is not case-sensitive. If you have trouble matching the text, click the
New Captcha Text icon (circular arrow) to be provided with a new text.
Basic Tasks

7 Click Login. The User List page is displayed.

If this is a new Aeonix installation, you are prompted to perform basic

configuration setup instead (see Aeonix Configuration Wizard, page 3-18).
3

Aeonix Administration Manual Getting Started 3-9

 If you do not use the Aeonix Web Portal for longer than a predefined timeout
period, you will be prompted to log in again.

 Admin Password Policy

The following improvements have been made for Aeonix Admin password security.

Password Strength
The user can change their password in the same way as before but password strength
is checked on the fly (character by character) as the user types it in and the strength
meter shows the strength. The system is using the same mechanism used for SIP phone
passwords.

Figure 3-3 Password

Strength

When the user types in the new password in the New password or Confirm password
fields the display shows the characters typed (not “*”).
The user can automatically generate a password with 100% strength from the system.
Basic Tasks

In both cases (of manual password change or system generated) the user needs to
confirm the password and press the Save button in order for the password to take
effect.
The system accepts password strength of 70% or higher.
3

3-10 Getting Started Aeonix Administration Manual

 In case the user tries to save a password with less than 70% strength the system
displays an error message "Weak Password - Try again" and the submitted password
will not be stored.
On upgrade from previous versions all administrator passwords are checked for
strength and if too weak (below 70%) the system generates an alarm "Weak Admin
Password detected <Login Name>".

Reuse of Password
Aeonix keeps the history of all passwords of all users. A history of maximum 1000
passwords are stored for each user. If the new password selected by an Administrator
is already in the history file, the password is not accepted and the system displays an
error message: “Password reuse is not allowed. Please try again”.

this prevents users from cycling between 2 or 3 identical passwords and

prevents multiple administrators from using the same password.

Default Password Usage

As part of the daily scan, Aeonix checks if users are using the default password for
users as defined in the system parameters page. If an administrator is using the default
an alarm is generated “Default password is in use by <login name>”.

Password Aging Policy

A password aging policy can be set in Aeonix.

Basic Tasks
3

Aeonix Administration Manual Getting Started 3-11

 Figure 3-4 Password
Aging Policy

The Aeonix Password Aging Period can be set in the range 0 to 365. If the value is
set to 0, the aging check mechanism is disabled.
Aeonix checks the Administrator passwords age per administrator and uses 2
thresholds
 75% of the aging period - generate an alarm.
 100% of the aging period - block the administrator.
A Password Aging Alarm generated when password age has reached 75% of the aging
period. See details in the alarm section
When password age reaches the full aging period, the Administrator access is blocked.
The aging period is valid for administrators that use weak passwords or default
password. The administrators are blocked.
When a user becomes a non-administrator the system sends an alarm "Administrator
access blocked due to password age reached the full aging period".
When a user in "blocked" status tried to login into the system, they get the Change
Password screen and must change the old password in order to login to the system.
The password is checked for strength and not-reused as described in Password Strength,
page 3-10, and Reuse of Password, page 3-11.
Basic Tasks
3

3-12 Getting Started Aeonix Administration Manual

 Verify Human Access
Captcha is now used to block machine hacking attempts. See Figure 3-2.
Aeonix Captcha Captcha 4 characters entry is now required as part of the login
sequence. It is a mix of characters and numbers.
User input is not case sensitive.

3-Strikes Out
To block hacking, the system counts the number of failed logins per user per 10 minute
period. If 3 successive failures of the login process are detected in the 10 minute
period, the user access to Aeonix Admin is blocked for a further 10 minutes and a
“Admin hacking attempt alarm” is generated.

Distributed Hacking Detection

The systems detects 3 failures to login by different users within a 10 minute period and
generates an “Admin hacking attempt alarm”. In this case no administrator is blocked.
To unblock a blocked administrator their password should be reset by another
administrator.

Aeonix Password Management Alarms

Five new alarms have been defined that can be issued by Aeonix with respect to
password management.

Alarm Condition Remediation

Weak Admin Aeonix checks all administration Login normally with the old password
Password Detected passwords strength once every 24 and change the password.
hours, and generates an alarm for
every Admin with a weak password
(lower than 70% strength).

Default Admin Aeonix checks all administration Login normally with the default
Basic Tasks

Password Detected passwords every 24 hours and password and change the password.
generates an alarm for every Admin
that is using the system default
password.
3

Aeonix Administration Manual Getting Started 3-13

 Alarm Condition Remediation

Password Aging Aeonix checks all adinistration Login normally with the old password
passwords every 24 hours and and change the password.
generates an alarm for every Admin
whose password has reached 75% of
the its age limit.

Administrator Access This alarm is generated if an Admin Call Tadiran Support.

Blocked password reaches its age limit,
resulting in the Admin’s access (login)
being bloacked.

Administrator Hacking 2 possible events can generate this None. Warning only.
Alert alarm:
1 3 failed login attempts by the same
Admin within a 10-minute window.
2 3 failed login attempts by multiple
Admins within a 10-minute window.

 Accessing Online Help

Aeonix features context-sensitive online help offering easy and fast access to topics
on which assistance is required.

To access online help:

1 At the bottom of the Aeonix page, click Help. The online help is displayed,
focusing on the currently displayed topic.

Click (Help icon) at the top of the page to access general online help.

2 Using the search and index tabs, browse to refine the search.

 Logging out from the Aeonix Web Portal

Basic Tasks

To log out from the Aeonix Web Portal:

At the top of the page, click (Logout icon). The Aeonix login page is
3

displayed.

3-14 Getting Started Aeonix Administration Manual

 If you do not use the Aeonix Web Portal for longer than a predefined timeout
period, you will be prompted to log in again.

Basic Tasks
3

Aeonix Administration Manual Getting Started 3-15

NOTES:
 3.3 Initial Aeonix Configuration

This section describes:

 Aeonix Configuration Wizard, page 3-18

Initial Aeonix Configuration

3

Aeonix Administration Manual Getting Started 3-17

  Aeonix Configuration Wizard

After running the Aeonix kickstart software package or launching the Aeonix
ecosystem in a cloud / virtual environment, you will be redirected to the Aeonix
Configuration wizard upon logging into the Aeonix Admin.

Activating the Aeonix Configuration Wizard in an A4C instance is not

allowed.

For cloud / virtual operation, Aeonix supports VMware using the Open
Virtualization Format (OVF) platform, Hyper-V (VHD), and Amazon AWS
(AMI). Aeonix does not support vMotion under VMware.

The wizard simplifies the initial setup of Aeonix and Aeonix Contact Center, allowing
you to define basic configuration settings.

Configuration definitions will only take effect after completing the wizard.

To perform initial system configuration:

1 From your workstation, log in to the Aeonix Admin (see Logging in to Aeonix,
page 3-8). The Aeonix Configuration Wizard - License Agreement page is
displayed.

The Aeonix Configuration wizard can be accessed for update purposes at

any time via the System, System Parameters menu of the Aeonix Admin.
Initial Aeonix Configuration
3

3-18 Getting Started Aeonix Administration Manual

Figure 3-5 Aeonix
Configuration Wizard -
License Agreement Page

If Temporary License is displayed, the system was installed without proper

licenses. Contact your Aeonix representative to obtain a permanent license
before the 30-day grace period expires. To learn more about the Aeonix
licensing mechanism, see Chapter 3, Licenses.

2 Read the Tadiran Telecom (TTL) end-user License Agreement, select the I
Accept check box if you agree, and then click Next. The Aeonix

Initial Aeonix Configuration

Configuration Wizard - Network page is displayed.
3

Aeonix Administration Manual Getting Started 3-19

 Figure 3-6 Aeonix
Configuration Wizard -
Network Page

In cluster environments, you are first prompted to select which server you
want to configure. If you select another server than the current one, you are
automatically redirected to that server’s IP address (no login required). The
Configuration Wizard must be run on all servers in the Aeonix cluster.

3 On the Aeonix Configuration Wizard - Network page, set the following

parameters:
Initial Aeonix Configuration

Table 3-1 Network

Parameters Field Description

Host name The hostname of Aeonix in the network.

NOTE: When updating an already licensed system,

editing this field will cause the system license to
become invalid.
3

IPv4 Configuration

3-20 Getting Started Aeonix Administration Manual

 Field Description

Static IP address The static local IP address of Aeonix in the network (in
(Default: 10.0.0.50) IPv4 format).

Subnet mask (Default: The subnet mask address of the gateway in the network
255.255.255.0) (in IPv4 format).

Default router address The default router address to which Aeonix is connected
in the network (in IPv4 format)

IPv6 Configuration

Static IP address The static local IP address of Aeonix in the network (in
IPv6 format).

Prefix Mask The prefix mask address of the gateway in the network
(in IPv6 format).

Default router address The default router address to which Aeonix is connected
in the network (in IPv6 format)

Primary DNS server The primary DNS server used by Aeonix in the network
(in IPv4 format)

Secondary DNS server The secondary DNS server used by Aeonixin the
network (in IPv4 format)

Bonding ethernet ports If the server has 2 NIC cards installed, Aeonix can
(Only displayed when configure them to be used in a Linux Network Bonding
2 NIC cards are configuration. Click the checkbox to enable Network
installed in server.) Bonding. ETH0 and ETH1 logical ports will be
configured to operate in Mode-1 Active-Backup. This
mode is used for failover. Only one logical port is active
at anytime. If unchecked, ETH0 NIC is used normally,
and the second NIC is ignored.

Any changes made to the Network Parameters page will cause Aeonix to Initial Aeonix Configuration
restart after completing the wizard.

4 Click Next. The Aeonix Configuration Wizard - Time and Date page is
displayed.
3

Aeonix Administration Manual Getting Started 3-21

 Figure 3-7 Aeonix
Configuration Wizard -
Time and Date Page

5 On the Aeonix Configuration Wizard - Time and Date page, set the following
parameters:

Table 3-2 Time and Date

Parameters Field Description
Initial Aeonix Configuration

Date & Time The current date and time associated with Aeonix

Time Zone The time zone associated with Aeonix

NTP server address 1 The name or IP address of the first NTP server address
according to which time is set for Aeonix.

NOTE: Aeonix servers connected in a cluster should have

the same NTP server assigned in each case, to
3

keep the servers in the cluster in time

synchronization.

3-22 Getting Started Aeonix Administration Manual

 Field Description

NTP server address 2 The name or IP address of the second (backup) NTP
(Default: server address according to which time is set for
il.pool.ntp.org) Aeonix.

NOTE: Aeonix servers connected in a cluster should have

the same NTP server assigned in each case, to
keep the servers in the cluster in time
synchronization.

Any changes made to the date and time parameters will cause Aeonix to
restart after completing the wizard.

6 Click Next. The Aeonix Configuration Wizard - Security page is displayed.

Figure 3-8 Aeonix

Configuration Wizard -
Security Page

Initial Aeonix Configuration

3

Aeonix Administration Manual Getting Started 3-23

 7 On the Aeonix Configuration Wizard - Security page, set the following
password parameters:

If you manually change a password, make sure that it contains at least one
digit, one special character, one upper case letter, one lowercase letter, and
is at least 7 characters long. Alternatively, you can automatically change a
password by clicking Generate password.

Table 3-3 Security

Parameters Field Description

‘aeonixadmin’ The default Aeonix administrator password for accessing

password the Aeonix Admin and web portal

User default password The default user password assigned to users by Aeonix

SIP default password The default authentication password used by Aeonix

(Default: during the phone registration process.
Aeonix123@)

8 Click Next. The Aeonix Configuration Wizard - Cluster Configuration page is

displayed.

When creating a cluster, the database will be taken from the server on which
the configuration wizard was activated.

In order for changes to take effect:

 All the servers in the cluster must be active

 All the servers in the cluster must be installed with the same Aeonix
software version
Initial Aeonix Configuration
3

3-24 Getting Started Aeonix Administration Manual

Figure 3-9 Aeonix
Configuration Wizard -
Cluster Configuration
Page

9 On the Aeonix Configuration Wizard - Cluster Configuration page, set the

following parameters for the standalone server and, in a cluster environment,
click Add to set for additional servers in the cluster:

Initial Aeonix Configuration

When adding, modifying, or removing servers in a cluster environment, it is
recommended that you run the wizard from the designated Aeonix License
server where the main database resides (usually the main office of your
organization).
3

Aeonix Administration Manual Getting Started 3-25

 Table 3-4 Cluster
Configuration Parameters Field Description

Server Name The name of the Aeonix server.

NOTE: In a single server environment, the name of the

server (anxStandalone) cannot be changed.

Address The IP address of the Aeonix server

Host Name The host name of the Aeonix server

Aeonix Contact Center The primary or secondary Aeonix server associated with
Aeonix Contact Center for High Availability purposes (for
details, see Server Settings for the Aeonix Contact Center
Service, page 14-44)

Country The country in which the Aeonix server is located.

NOTE: After the wizard is completed, Aeonix

automatically configures the preinstalled dial
plans (xml file) for the selected country.

State / Province The name of the state or province associated with the
area in which the Aeonix server is located, if relevant

Area The area in which the Aeonix server is located

Any changes made to the Cluster Configuration Parameters page will cause
Aeonix to restart after completing the wizard.

If you Delete a server from a cluster, it is recommended that the server be

disconnected from the network so that it does not interfere with the
remaining cluster or system operation.
Initial Aeonix Configuration

10 Click Next. The Aeonix Configuration Wizard - Summary page is displayed.

3

3-26 Getting Started Aeonix Administration Manual

Figure 3-10 Aeonix
Configuration Wizard -
Summary Page (example)

11 This page displays a summary of all the configured items. Review the Initial Aeonix Configuration

definitions, and if everything is correct, click Finish to begin the installation.

The Status page indicates the progress of the installation. Once complete, the
definitions take effect. In cluster environments, the installation process can
take up to several hours, depending on database size.
3

Aeonix Administration Manual Getting Started 3-27

 Figure 3-11 Aeonix
Configuration Wizard -
Status Page

12 If network, time/date, or cluster changes were made, the Aeonix system

restarts, after which the Aeonix Login page is automatically displayed. Upon
log in, the Aeonix Configuration Wizard - Status page is displayed again.
Initial Aeonix Configuration

You can click the Restart Wizard button to run the wizard again.
3

3-28 Getting Started Aeonix Administration Manual

 3.4 Licenses

Aeonix requires licenses before it can be fully configured and used.

For details about how to purchase licenses, refer to the Aeonix Installation
Manual (see Related Documentation, page 1-17).

These licenses are stored on a soft key, which must be uploaded and deployed on the
designated Aeonix License Key server. This soft key holds the maximum number of
licensed resources that can be implemented in the system. Each Aeonix system,
whether based on one server or configured as a cluster of servers, must have exactly
one soft key license. Consequently, in a cluster, only one server requires a soft key
license.
Aeonix Users and the devices they use while connected to Aeonix require licenses.
The licenses are stored in pools, so that as the Aeonix Administrator creates new users,
and the users log onto Aeonix with their devices, the licenses are consumed from the
pools. When a user logs a device off from Aeonix, that license is returned to the user
device license pool.
The Aeonix Administrator can create two different kinds of users. An Advanced User
can have up to six devices defined. A Gateway User can have a single
Gateway-connected device defined.
When a user is created by the Aeonix Administrator, a user license for that type of user
is consumed for the duration of the existence of that user in the system.
In the case of the Advanced User, the user can have one device defined that does not
consume an additional device license. The first Advanced User device can be one of:
 Tadiran SIP phone
 Tadiran MGCP phone
Licenses

 Non-Tadiran SIP phone

Additional devices defined for the Advanced User consume additional device
licenses as shown in the following figure.
3

Aeonix Administration Manual Getting Started 3-29

 Figure 3-12 Aeonix User
License Scheme
Licenses
3

3-30 Getting Started Aeonix Administration Manual

 Additional licenses can be added to the Advanced User for up to six defined devices
total, including the first device licensed under the Advanced User License. Each
additional license can support one of:
 Tadiran SIP phone
 Tadiran MGCP phone
 Non-Tadiran SIP phone
 Aeonix Touch for Windows
 Aeonix Touch for Android or iOS (mobile)
 Gateway-connected device such as an FXS analog phone or fax
Licenses can be activated using one of the following methods:
 Automatically–Aeonix checks for and installs available license updates.
 On-Demand–Administrators with licensing task privileges can activate
licenses without having to access the Tadiran Licensing server GUI.
 Manually–Administrators with licensing task privileges can activate licenses
by accessing the Tadiran Licensing server GUI.
This section describes the following:
 License Information Page, page 3-32
 License Information, page 3-35
 Activating the First License, page 3-40
 Activating License Updates Automatically or On-Demand, page 3-43
 Activating Another License Key Server, page 3-46
 Adding a License Manually, page 3-47
 Aeonix Licensing and Aeonix Licensing Application Messages, page 3-52

Licenses
3

Aeonix Administration Manual Getting Started 3-31

  License Information Page

The License Information page (Figure 3-13) displays the purchased licenses of the
Aeonix system and the Aeonix Contact Center (Figure 3-15) and the date on which
Technical support expires. It includes a list of all resource types that require a separate
license, the allowed number of resources, and the currently used resources.
The License Information page is displayed if there is a licensing related problem every
time the default administrator aeonixadmin logs in to the Aeonix Web Portal:

Table 3-5 License

warning messages Message Descriptions

The system requires a You log into a system for which there is no valid
valid license to operate. license key deployed on the designated Aeonix
License Key server. Please add your license key
(see Activating the First License, page 3-40) or contact
your manufacturer's representative to obtain a
license key.

The system could not You log into a system for which there is no longer a
detect a license key, and valid license key deployed on the designated
has entered Grace Period Aeonix License Key server. The system has entered
mode. Grace Period mode, a 30 day period during which
time you can rectify the problem.

The system detected a An administrator made a change to the server clock

clock change, and has time causing the system to enter Grace Period
entered Grace Period mode.
mode.

The system detected that There are more Aeonix servers in the cluster than
the number of servers the maximum allowed according to the number of
exceeded its limit, and has licensed servers (see Table 3-7 on page 3-36).
entered Grace Period
mode.

Your grace period is about This message is displayed every time you log in to
to expire in [x] days. remind you how many days are left before the
Grace Period ends. Please contact your
manufacturer's representative to rectify the problem.

Your grace period has The Grace Period has ended.

expired The Aeonix system will no longer function. Please
Licenses

contact your manufacturer's representative to rectify

the problem.
3

3-32 Getting Started Aeonix Administration Manual

 Message Descriptions

Your Aeonix support This message is displayed every time you log in to
contract will expire in [x] remind you how many days are left before the
day(s). Technical support expires. Please contact your
manufacturer's representative to renew your
Technical support license.

Your Aeonix support The Aeonix system is running without the Technical
contract has now expired. support license.
This message is displayed until the Technical
support license is renewed. Please contact your
manufacturer's representative to renew your
Technical support license.

NOTE: No upgrade of the system can take place

while the Technical support license is expired.

To open the License Information page:

1 At the bottom of the navigation pane, click System. The pane displays the
System menus.
2 Select the License menu, and then click License.

Licenses
3

Aeonix Administration Manual Getting Started 3-33

 Figure 3-13 License
Information Page -
Aeonix Tab

Download Usage Report

Click the Download Usage Report link in the first row of the Aeonix Resource table
to see the usage of licenses per user. You will be prompted to Open or Save (to your
local Windows computer) an Excel file that appears as shown in the following figure.

Figure 3-14 Aeonix

Advanced User License
Usage Report
Licenses
3

3-34 Getting Started Aeonix Administration Manual

Figure 3-15 License
Information Page -
Aeonix Contact Center
Tab

 License Information

The License Information page (Figure 3-13 above) provides the following
information:
 General license information (see Table 3-6 below)
 Resource-specific license information, including available number of resources
that the license allows and the currently used number or resources. For a
description of the resource types that require licenses, see Table 3-7 on
page 3-36.

Click Refresh License to update the License Information page with the
latest license details.

Licenses
3

Aeonix Administration Manual Getting Started 3-35

 Table 3-6 General License
Information Parameter Description

Key ID The key ID assigned to the license by the manufacturer.

‘Staging’ indicates that the system has been installed with

a 30 day trial license that includes the full set of features.
In addition to the Aeonix Admin, during this period access
will also be granted to the Aeonix Contact Center and
SeaMail interfaces. Contact your Aeonix representative to
obtain a permanent license before the 30-day grace period
expires.

NOTE: The number of days left in Trial License mode is

indicated at the top of the License Information page.
Grace period countdown is based on the time the
Aeonix system is up and running and not according
to actual calendar days when the grace period
began, affording administrations more flexibility when
staging Aeonix.

License key server The designated Aeonix server on which the soft key license
is uploaded and deployed

Technical support The date on which the Aeonix technical support expires
expiration

Last license The status of the last license activation

activation status

Table 3-7 Aeonix

Resource Types Resource Type Description
Requiring Separate
Licenses Advanced Aeonix The maximum number of users that can be concurrently
users logged into their Aeonix UC&C registered devices (see
related device licenses below - Aeonix Tadiran devices, Aeonix
Gateway devices, Aeonix Touch desktop softphones, Non-Tadiran
devices).

NOTE: User license resources are pooled - they are only

utilized when users log into their devices and are
freed up when users log out of their devices.

Aeonix Gateway The maximum number of users that can be concurrently

users logged into their Aeonix gateway registered devices (see
related devices below - Aeonix Gateway devices).
Licenses

NOTE: User license resources are pooled - they are only

utilized when users log into their devices and are
freed up when users log out of their devices.
3

3-36 Getting Started Aeonix Administration Manual

 Resource Type Description

Aeonix Tadiran Allows Advanced Aeonix users to log in to their Tadiran SIP
devices phones, MGCP phones (including FlexSet-IP 280S and
T200M Series phones), FlexIP softphones (FLIPS), and
Bria softphones.

NOTE: The Advanced Aeonix users license includes 1

Aeonix Tadiran devices license a user can use to log
into any of their Tadiran devices listed above.

Aeonix Gateway Allows Aeonix Gateway users and Advanced Aeonix users to log in
devices to their FlexSet, DST, DKT, and SLT phones connected to
Aeonix gateways, including Tadiran TGW gateways, Wave
Gateways, and Audiocodes gateways purchased from
Tadiran.

NOTE: The Aeonix Gateway users license includes 1 Aeonix

Gateway devices license a user can use to log into
any of their Aeonix gateway devices listed above.

Aeonix Touch Allows authorized Advanced Aeonix users to log in to their

desktop softphones Aeonix Touch softphone on their Windows PC.

NOTE: When Aeonix Touch is used to control a user's

Aeonix Tadiran device ('control' mode), no license is
required.

Non-Tadiran Allows Advanced Aeonix users to log in to their third-party

devices phones that have been approved for use with Aeonix, such
as P-Series phones.

NOTE: This is an add-on to the Aeonix Tadiran devices

license. In the event that a user's non-Tadiran device
malfunctions, the user will not require any additional
licensing to operate their Aeonix Tadiran device.

Attendant Console The number of concurrent users that can make use of the
users Aeonix Attendant application (that is, can have the Sea
Attendant option selected in their Feature Configuration
profile)

Aeonix Dispatch The maximum number of Aeonix dispatch consoles allowed

Consoles in the system
(concurrent)
Licenses

Aeonix Gateway The maximum number of phones behind Tadiran Gateways

users (including third party gateways such as AudioCodes
gateways purchased from Tadiran)
3

Aeonix Administration Manual Getting Started 3-37

 Resource Type Description

Aeonix IP Net The maximum number of concurrent IP-Net calls allowed

(concurrent calls) via IPNet trunks.

NOTE: Requires parallel NET_IP and NETWORKING

authorization in the Wave Gateway IPx/FlexiCom
system.

Aeonix non-Tadiran The maximum number of registered users allowed in the

users system that are connected via non-Tadiran licensed
phones or other third party phones

Aeonix servers In clustered systems, the maximum number of Aeonix

servers in the cluster

Aeonix SIP Trunks The maximum number of concurrent SIP trunk or gateway
/ Gateways calls that can be transmitted via trunks or gateways
(concurrent calls)

Aeonix Tadiran The maximum number of registered Tadiran users allowed

users in the system.

Aeonix Touch users The maximum number of users that are authorized to use
Aeonix Touch on their computer as a softphone in the
system.

NOTE: In addition to the Aeonix Touch users license, an

Aeonix Touch softphone requires an Aeonix Tadiran
users license.

FlexIP Softphones The maximum number of FlexIP (FLIPS) softphones

allowed in the system

G729 single media The maximum number of G.729 codec channels allowed in
channels the system

Hospitality Whether the Hospitality service is enabled or disabled:

0 = Disabled
1 = Enabled

NOTE: In addition to the license requirement, SeaMail must

be installed on the system for the Hospitality Service
to function.
Licenses

Mobility users The maximum number of users that can place and receive
mobility calls (that is, Callback and Call-through calls)

NOTE: Mobility user license are issued in packs of 5.

3

3-38 Getting Started Aeonix Administration Manual

 Resource Type Description

Navigator users The number of users that can make use of the
Sea Navigator application (that is, can have the Sea
Navigator option selected in their Feature Configuration
profile)

Table 3-8 Aeonix Contact

Center Resource Types Resource Type Description
Requiring Separate
Licenses Aeonix Contact The level of Aeonix Contact Center:
Center level  Full Aeonix Contact Center
 Aeonix Contact Center Lite demo

Automated The maximum number of automated campaign outbound

campaign ports calls that can take place simultaneously

Chat agents The maximum number of concurrent agents that can be

logged into chat enabled groups

Cradle to Grave Whether the Cradle to Grave application is enabled or

disabled:
0 = Disabled
1 = Enabled

Email agents The maximum number of concurrent agents that can be

logged into email enabled groups

IVR (concurrent The maximum number of calls that can be simultaneously

calls) connected to IVR ports

Outbound The maximum number of concurrent agents that can be

campaign voice logged into progressive dial list enabled groups
agents

Real-time monitors The maximum number of monitors that can be concurrently

connected to the Aeonix Contact Center

Visors The maximum number of visors that can be concurrently

connected to the Aeonix Contact Center

Voice agents The maximum number of concurrent agents that can be

logged into the Aeonix Contact Center
Licenses
3

Aeonix Administration Manual Getting Started 3-39

  Activating the First License

In a new system where no license exists you are prompted upon login to activate the
first license:

Figure 3-16 No License

Exists

To automatically activate the first license:

1 From the Install license on server drop-down list, select the Aeonix server on
which the soft key license is to be uploaded and deployed.

When selecting a server on which to install the soft key license, take into
consideration the architecture of your system. For example, if there are 4
servers geographically located at one site and 1 server located remotely, it
makes more sense to select one of the local servers over the remote server
to act as the designated License server.

2 In the Enter product key text box, enter the product key (a 32 alphanumeric
string).

If you do not have the product key, contact your Aeonix representative.
Licenses

3 Read and accept the Tadiran Telecom (TTL) end-user License Agreement.
4 Click Activate to save the product key in the Aeonix server and retrieve the
license from the Tadiran Licensing server.
3

3-40 Getting Started Aeonix Administration Manual

Figure 3-17 Retrieving
License from Tadiran
Licensing Server

5 Click Activate at the bottom of the page to store and activate the license on
the Aeonix server.

The Aeonix server on which the licenses are installed cannot be changed
unless it is down. See Activating Another License Key Server, page 3-46.

6 The Activating licensing, please wait message is displayed, followed by the

Aeonix has been activated message.

Figure 3-18 License

Activated

Licenses

7 Click OK. The Aeonix server is now activated with the license.
3

Aeonix Administration Manual Getting Started 3-41

 If there is no online access available to the Tadiran Licensing server, or if the
license update did not succeed for another reason, the following
corresponding messages are displayed instead:
 Activation was not successful. Please make sure you have online access
from the machine you are attempting to activate from. If you continue
having this problem, please contact your Tadiran support representative.
 Activation was not successful. The error returned is <error message
text>. Please contact your Tadiran support representative and provide
them with this information.
Licenses
3

3-42 Getting Started Aeonix Administration Manual

  Activating License Updates Automatically or On-Demand

Once the first license has been activated (see Activating the First License, page 3-40), you
can activate license updates automatically or on-demand from the Manage License
Page.

This procedure must be performed on the designated Aeonix License Key

server. All Aeonix servers in the cluster must be running during this process.

To activate license updates automatically:

1 At the bottom of the navigation pane, click System. The pane displays the
System menus.
2 Select the License menu, and then click Manage License.
3 Click Automatic Updates to display this area of the page.

Figure 3-19 Automatically

Activating License
Updates - Manage
License Page

4 Select Automatically update licensing if online access is available if you

want Aeonix to check for and automatically install license updates from the
Tadiran Licensing Web server daily (at midnight, according to the local time of
the Aeonix License Key server).
Licenses

If this check box is not selected but access to the server is available and an
update found, the administrator will be notified that the update is available
when logging into the system next time.
3

5 Click Save.

Aeonix Administration Manual Getting Started 3-43

 To activate license updates on-demand:
1 At the bottom of the navigation pane, click System. The pane displays the
System menus.
2 Select the License menu, and then click Manage License.

Figure 3-20 Activating

License Updates
on-demand - Manage
License Page

3 Click Update. If there are valid updated v2c files on the Tadiran Licensing
server, Aeonix retrieves these files.

Figure 3-21 Retrieving

Licenses from Tadiran
Licensing Server -
Manage License Page

4 Click Update at the bottom of the page to store and activate the licenses in the
proper order on the Aeonix server.
Licenses

The Aeonix server on which the licenses are installed cannot be changed
unless it is down. See Activating Another License Key Server, page 3-46.
3

3-44 Getting Started Aeonix Administration Manual

 5 The Updating licensing, please wait message is displayed, followed by the
The license has been updated message.

Figure 3-22 License

Updated Message

6 Click OK. The Aeonix server is now activated with the license updates.

If there are no license updates available, no online access is available to the

Tadiran Licensing Web server, or the license update did not succeed for
another reason, the following corresponding messages are displayed
instead:
 No license updates are available.

 License update was not successful. Please make sure you have online
access from the machine you are attempting to activate from. If you
continue having this problem, please contact your Tadiran support
representative.
 Activation was not successful. The error returned is <error message
text>. Please contact your Tadiran support representative and provide
them with this information.

Licenses
3

Aeonix Administration Manual Getting Started 3-45

  Activating Another License Key Server

In the event that the Aeonix server on which the license is installed is down, you are
prompted to activate another server in the Aeonix cluster instead.

To activate another license key server:

1 At the bottom of the navigation pane, click System. The pane displays the
System menus.
2 Select the License menu, and then click Manage License.

Figure 3-23 No License

Key Server Detected -
Manage License Page

3 Click Activate New Server, and then proceed to install the license on the new
Aeonix server (see Activating the First License, page 3-40).
Licenses
3

3-46 Getting Started Aeonix Administration Manual

  Adding a License Manually

Use this procedure to manually create the soft key license and activate your Aeonix
system or to manually add a license to a system that has already been activated.

This procedure must be performed on the designated Aeonix License Key

server. All Aeonix servers in the cluster must be running during this process.

To manually add a license:

1 At the bottom of the navigation pane, click System. The pane displays the
System menus.
2 Select the License menu, and then click Manage License.
3 Click Manual License Management to display the area of this page.

Figure 3-24 Manual

License Management
Page - First License

4 From the Download the signature file (.c2v) from drop-down list, select the
Aeonix server from where you want to retrieve the C2V signature file.
Licenses

5 Click Download File.

The C2V file is named fingerprint.c2v. The license key information, including
the unique ID number of the license key, is encrypted in this file and is used to
3

physically identify the Aeonix License Key server.

Aeonix Administration Manual Getting Started 3-47

 6 Access https://licensing.tadirantele.com:8443/ems/customerLogin.html from
any Internet browser. The Aeonix Product Key Login screen is displayed.

Figure 3-25 Aeonix

Product Key Login
Screen

7 Enter your product key (a 32 alphanumeric string) and click Login. The
Aeonix Product Key Registration screen is displayed.

If you do not have your product key, contact your Aeonix representative.

Figure 3-26 Aeonix

Product Key Registration
Screen

8 It is strongly recommended to register the product key by filling in the

mandatory fields and clicking Save. The Aeonix Product Key Main screen is
Licenses

displayed.
3

Alternatively, click Register Later.

3-48 Getting Started Aeonix Administration Manual

Figure 3-27 Aeonix
Product Key Main Screen

9 Click Offline Activation to generate the license file. The Generate License
screen is displayed.

Generating the license file might take up to one minute.

Figure 3-28 Aeonix

Generate License Screen

Licenses

10 Click to upload the fingerprint (signature) C2V file from the location
you stored it (see Step 5), and then click Generate. The V2C file is generated.
3

Aeonix Administration Manual Getting Started 3-49

 Figure 3-29 Generated
V2C File

11 Click Download V2C File to download the new V2C file to the server.
12 Copy the V2C file to the location you stored the original C2V file (see Step 5).
13 In the Aeonix Admin, open the Manage License page again (see Figure 3-24).
14 Click Choose File to open the V2C file.
15 If this is the first license, from the Into server drop-down list select the
Aeonix server you want to designate as the Aeonix server on which the soft
key license is uploaded and deployed.

When selecting a server on which to install the soft key license, take into
consideration the architecture of your system. For example, if there are 4
servers geographically located at one site and 1 server located remotely, it
makes more sense to select one of the local servers over the remote server
to act as the designated License server.

Before saving the license, you must read and accept the Tadiran Telecom
(TTL) EULA.
Licenses

16 Click Save. Aeonix will load this file, thereby creating the soft key license and
activating your Aeonix system. The status of the activation is indicated at the
top of the page.
3

The soft key license is now configured with the appropriate license settings.

3-50 Getting Started Aeonix Administration Manual

 Allow a few seconds for Aeonix to load the soft key license. Then, on the
License Information page, click Refresh License and verify that the correct
license items and quantities have been loaded to the system.

Licenses
3

Aeonix Administration Manual Getting Started 3-51

  Aeonix Licensing and Aeonix Licensing Application Messages

The following tables describe the licensing related messages that might be displayed
while working with the Manage License page.

Table 3-9 Aeonix

Licensing Messages Message Description

Activation was not There is no online access available to the Tadiran

successful. Please Licensing server. Reestablish online connectivity.
make sure you have
online access from
the machine you are
attempting to
activate from.

Activation was not The license update did not succeed because of a
successful. The problem in the Aeonix Product Key application.
error returned is See Table 3-7 on page 3-36 for a description of the
<error code>. specified message.

No license updates You tried to update a license when no updates are

are available. available.

The product key Contact Customer Support.

provided has already
been activated.

Not all licenses If the problem persists, contact Customer Support.

could be updated.
Please try again.

The licensing server If required, proceed to activate another server as

is down. the license key server (see Activating Another License
Key Server on page 3-46).

Table 3-10 Aeonix

Licensing Application Code Message Description
Messages
0 HASP_STATUS_OK Request successfully completed

1 HASP_MEM_RANGE Request exceeds the Sentinel

HASP protection key memory
range
Licenses

3 HASP_INSUF_MEM System out of memory

4 HASP_TMOF Too many open sessions

3

3-52 Getting Started Aeonix Administration Manual

 Code Message Description

5 HASP_ACCESS_DENIED Access to Feature denied

6 HASP_INCOMPAT_FEATURE Legacy decryption function

cannot work on the Feature

7 HASP_HASP_NOT_FOUND Sentinel HASP protection key

no longer available

8 HASP_TOO_SHORT Encrypted/decrypted data length

too short to execute function call

9 HASP_INV_HND Invalid handle passed to

function

10 HASP_INV_FILEID Specified File ID not recognized

by API

11 HASP_OLD_DRIVER Installed driver too old to

execute function

12 HASP_NO_TIME Real-time clock (rtc) not

available

13 HASP_SYS_ERROR Generic error from host system

call

14 HASP_NO_DRIVER Required driver not installed

15 HASP_INV_FORMAT Unrecognized file format for

update

16 HASP_REQ_NOT_SUPP Unable to execute function in

this context

17 HASP_INV_UPDATE_OBJ Binary data passed to function

does not contain an update

18 HASP_KEYID_NOT_FOUND Sentinel HASP license you

requested to update not found

19 HASP_INV_UPDATE_DATA Required XML tags not found.

Contents in binary data are
Licenses

missing or invalid.

20 HASP_INV_UPDATE_NOTSUPP Update request not supported

by Sentinel HASP
3

protection key

Aeonix Administration Manual Getting Started 3-53

 Code Message Description

21 HASP_INV_UPDATE_CNTR Update counter not set correctly

22 HASP_INV_VCODE Invalid Vendor Code passed

23 HASP_ENC_NOT_SUPP Sentinel HASP protection key

does not support
encryption type

24 HASP_INV_TIME Passed time value outside

supported value range

25 HASP_NO_BATTERY_POWER Real-time clock battery out of

power

26 HASP_NO_ACK_SPACE Acknowledge data requested by

the update
ack_data parameter is NULL

27 HASP_TS_DETECTED Program running remotely on a

terminal server

28 HASP_FEATURE_TYPE_NOT_IMPL Requested Feature type not

implemented

29 HASP_UNKNOWN_ALG Unknown algorithm used in V2C

file

30 HASP_INV_SIG Signature verification operation

failed

31 HASP_FEATURE_NOT_FOUND Requested Feature no longer

available

32 HASP_NO_LOG Access log not enabled

33 HASP_LOCAL_COMM_ERROR Communication error between

program and local
HASP License Manager

34 HASP_UNKNOWN_VCODE Vendor Code not recognized by

API
Licenses

35 HASP_INV_SPEC Invalid XML specification

36 HASP_INV_SCOPE Invalid XML scope

3

3-54 Getting Started Aeonix Administration Manual

 Code Message Description

37 HASP_TOO_MANY_KEYS Too many Sentinel HASP

protection keys currently
connected

38 HASP_TOO_MANY_USERS Too many users currently

connected

39 HASP_BROKEN_SESSION Session has been interrupted

40 HASP_REMOTE_COMM_ERROR Communication error between

local and remote HASP
License Managers

41 HASP_FEATURE_EXPIRED Feature expired

42 HASP_OLD_LM HASP License Manager version

too old

43 HASP_DEVICE_ERR Input/output error occurred in

secure storage area of
HASP SL key
OR
In the case of a HASP HL key,
USB communication error
occurred

44 HASP_UPDATE_BLOCKED Update installation not permitted

45 HASP_TIME_ERR System time has been tampered

with

46 HASP_SCHAN_ERR Communication error occurred

in secure channel

47 HASP_STORAGE_CORRUPT Corrupt data exists in secure

storage area of
Sentinel HASP protection key

48 HASP_NO_VLIB Unable to find Vendor library

49 HASP_INV_LIB Unable to load Vendor library

Licenses

50 HASP_SCOPE_RESULTS_EMPTY Unable to locate any Feature

matching scope
3

Aeonix Administration Manual Getting Started 3-55

 Code Message Description

52 HASP_HARDWARE_MODIFIED HASP SL key incompatible with

machine hardware.
HASP SL key locked to different
hardware.
OR
In the case of a V2C file, conflict
between HASP SL key data and
machine hardware data. HASP
SL key locked to different
hardware.

53 HASP_USER_DENIED Login denied because of user

restrictions

54 HASP_UPDATE_TOO_OLD Trying to install a V2C file with

an update counter that is out of
sequence with update counter in
the Sentinel HASP protection
key. Values of update counter in
file are lower than those in
Sentinel HASP protection key.

55 HASP_UPDATE_TOO_NEW Trying to install a V2C file with

an update counter that is out of
sequence with the update
counter in the Sentinel HASP
protection key. First value in file
is more than 1 greater than
value in Sentinel HASP
protection key

56 HASP_OLD_VLIB Vendor library too old

57 HASP_UPLOAD_ERROR Check in of a file (such as V2C,

H2R) using Admin Control
Center failed, possibly because
of illegal format

58 HASP_INV_RECIPIENT Invalid XML RECIPIENT

parameter

59 HASP_INV_ACTION Invalid XML action parameter

Licenses

60 HASP_TOO_MANY_PRODUCTS The scope specified in the

Transfer function does not
specify a unique Product
3

61 HASP_INV_PRODUCT Invalid Product information

3-56 Getting Started Aeonix Administration Manual

 Code Message Description

62 HASP_UNKNOWN_RECIPIENT Update can only be applied to

recipient machine specified in
the Detach function, not to this
machine

63 HASP_INVALID_DURATION Invalid detached license

duration period specified.
Duration must be less than or
equal to maximum allowed for
this license.

OR:

Duration extension is to a date

earlier than the expiration date
of the current detached license.

64 HASP_CLONE_DETECTED Cloned Sentinel SL storage was

detected. Feature is unavailable.

65 HASP_UPDATE_ALREADY_ADDED The specified V2C or or V2CP

update was already installed in
the License Manager service

66 HASP_HASP_INACTIVE Specified Key ID is in Inactive

state

67 HASP_NO_DETACHABLE_FEATURE No detachable Feature exists in

the specified key from which the
detached license is requested

68 HASP_TOO_MANY_HOSTS The specified scope does not

specify a unique host

69 HASP_REHOST_NOT_ALLOWED Rehost action is not allowed for

the specified Key ID

70 HASP_LICENSE_REHOSTED Original license has been

transferred to another machine.
Therefore, the license cannot be
returned to the source machine.
Licenses

71 HASP_REHOST_ALREADY_APPLIED Old rehost license cannot be

applied. A rehost-counter
mismatch occurred
3

72 HASP_CANNOT_READ_FILE A V2C or V2CP file was not

found, or access was denied

Aeonix Administration Manual Getting Started 3-57

 Code Message Description

73 HASP_EXTENSION_NOT_ALLOWED The license cannot be extended

because the number of
detached licenses is greater
than the number of concurrent
licenses allowed

74 HASP_DETACH_DISABLED The user attempted to detach a

Product from a network license
hosted on a virtual machine.
However, none of the Features
included in the Product are
enabled for virtual machines.

75 HASP_REHOST_DISABLED The user attempted to rehost a

protection key from a virtual
machine. However, none of the
Features contained in the
protection key are enabled for
virtual machines.

76 HASP_DETACHED_LICENSE_FOUND The user attempted to format an

SL-Admin Mode key or to
migrate an SL-Legacy key to an
SL-Admin Mode key. However,
a Product is currently detached
from the key.

77 HASP_RECIPIENT_OLD_LM For a rehost operation: The

fingerprint of the target machine
was collected using tools (RUS
utility or Licensing API) earlier
than Sentinel LDK v.7.0.

78 HASP_SECURE_STORE_ID_ A secure storage ID mismatch

MISMATCH occurred.

79 HASP_DUPLICATE_HOSTNAME The license fingerprint is bound

to a specific hostname;
however, two or more machines
with this hostname were found
in the network. As a result, the
license cannot be used.
Licenses
3

3-58 Getting Started Aeonix Administration Manual

 Code Message Description

80 HASP_MISSING_LM A protected application tried to

log in to a Feature that supports
concurrency on a Sentinel HL
(Driverless configuration) key.
The Sentinel LDK License
Manager service is not active on
the computer where the key is
located.

81 HASP_FEATURE_INSUFFICIENT_ A protected application tried to

EXECUTION_COUNT consume multiple executions
while logging in to a Feature.
However, the license does not
contain the number of
executions that were requested.

82 HASP_INCOMPATIBLE_PLATFORM The function is attempting to

perform an operation that is not
compatible with the target
platform.

83 HASP_HASP_DISABLED A Sentinel HL (Driverless

configuration) key was disabled
because a user attempted to
tamper with the key or with the
protected application.

84 HASP_SHARING_VIOLATION An HL key is being shared by

the use of a USB splitter device
(such as Smart X). When this
error occurs, a "sharing
violation" message is also
displayed on the relevant page
in Admin Control Center.

400 HASP_NO_API_DYLIB Unable to locate dynamic library

for API

401 HASP_INVALID_API_DYLIB Dynamic library for API is invalid

500 HASP_INVALID_OBJECT Object incorrectly initialized

501 HASP_INVALID_PARAMETER Scope string too long (max.

Licenses

length 32 KB)

502 HASP_ALREADY_LOGGED_IN Logging in twice to same object

3

Aeonix Administration Manual Getting Started 3-59

 Code Message Description

503 HASP_ALREADY_LOGGED_OUT Logging out twice from same

object

525 HASP_OPERATION_FAILED Incorrect use of system or

platform

698 HASP_NOT_IMPL Requested Feature type not

implemented

699 HASP_INT_ERR Internal error occurred in API

Licenses
3

3-60 Getting Started Aeonix Administration Manual

NOTES:
Licenses
3

3-62 Getting Started Aeonix Administration Manual

 3.5 General Procedures

General procedures are procedures that are performed in the same way throughout the
Web Portal. They include:
 Navigating, page 3-64
 Entering Information, page 3-64
 Saving, page 3-64
 Cloning Entities, page 3-65
 Deleting Entities, page 3-66

General Procedures
3

Aeonix Administration Manual Getting Started 3-63

  Navigating

Use the category and menu option buttons in the left navigation pane to display the
required Web page.
Each entity has its own main page from which it is configured. For example, each user
has their own User page. From this page, you can access all parameters that are
directly related to the relevant user.
Some configuration procedures require the opening of secondary pages from the
entity’s main page. For example, overriding a user’s general information parameter
values is performed from the General Information Profile page of this user.

 Entering Information

You can define a large number of parameters in the Aeonix Web Portal. To specify the
value of a parameter, either select it from a drop-down list, type it in the field, or start
typing and then select from a list of suggested entries.

 Saving

After making the required changes on the currently displayed page, click Save to
permanently store the changes in the Aeonix database, or Cancel to discard the
changes.
On secondary pages, an OK button is available instead of the Save button. Clicking
OK temporarily saves the changes and returns to the previous page. To make the
change permanent, click OK to navigate back to the entity’s main page, and then click
Save.

If you make changes to an entity and do not click Save on the entity’s main
page, the changes will not be saved.
General Procedures

If a mandatory field has not been filled in or an invalid value has been entered, a
corresponding message is displayed when you click Save. You can save the entity and
close its page only after entering a valid entry in the field.
3

3-64 Getting Started Aeonix Administration Manual

  Cloning Entities

On pages that include a list of entities, you can create a copy of an existing entity. For
example, you can clone users on the User List page.

To clone an entity:
1 On the relevant List page, click (the Clone icon) to the right of the
relevant entity, as in the following figure of the User List page.

Figure 3-30 Selecting an

entity to Clone

2 A new page is opened for creating a cloned entity.

Figure 3-31 New page of

cloned entity

General Procedures
An indexing suffix is automatically added to the entity’s ID. In the example
above, the original User ID is x2050; the cloned ID is x2050_1.
3

Aeonix Administration Manual Getting Started 3-65

  Deleting Entities

On pages that include a list of entities, you can delete one or multiple listed items. For
example, you can delete phones on the Phone List page.
Default entities pre-configured in the system, such as the Default Dial Plan, cannot be
deleted. Some entities that are used by other entities cannot be deleted either. For
example, it is not possible to delete a user profile if this profile is assigned to a user.

Once an entity has been deleted, it is completely removed from the database
and cannot be restored. It is therefore recommended to back up the
database before deleting crucial or multiple items (see Creating a Backup,
page 14-56).

To delete an entity:
1 On the relevant List page, select the check box left of the item or items to be
deleted, as in the following figure of the Phone List page.

Figure 3-32 Selecting

Entities for Deletion
General Procedures

2 Click Delete. A confirmation message is displayed.

3

3 Click Yes to delete the item or items.

3-66 Getting Started Aeonix Administration Manual

 3.6 Aeonix Setup Procedure

Before configuring the system, read Aeonix Building Blocks, page 1-7, which
provides an overview of the components that comprise an Aeonix network.

Once Aeonix is installed and running with the proper license settings, you can start
configuring the system. Configuring the network in the Aeonix Web Portal includes
the procedures below:
4 Defining global settings (optional)
Aeonix provides default values for most global setting parameters. You can
override these values, or add global setting instances and use them instead of
the default values.
Define global settings in the following order:
 Country-specific Dial Codes, page 4-1
 Locations, page 4-9
 Dial Plans, page 4-19
 Closed User Groups (CUG), page 4-29
 Schedules, page 4-37
Prior to defining Automatic Route Selection tables, define the relevant trunk
groups (see Step 8).
5 Defining profiles and phone templates (optional)
Just as with global settings, preconfigured default profiles and templates are
Aeonix Setup Procedure
included in the system and can be modified. You can also define additional
profiles and templates, and use them instead (see Chapter 5, Profiles).
6 Adding and configuring users (see Chapter 6, Managing Users)
7 Adding phones and associating them with their users (see Chapter 7, Managing
Phones). The phones can also be added and some of their parameters defined
while configuring their users (in Step 6).
3

Aeonix Administration Manual Getting Started 3-67

 Change the Aeonix default domain name, if necessary, before adding the
phones.
8 Adding and configuring trunk groups (see Chapter 9, Managing Trunk Groups)
9 Adding trunks and associating them with their trunk groups (see Chapter 8,
Managing Trunks)
10 Adding and configuring Wave Gateways if available (see Chapter 10,
Managing VOIP Gateways)
11 Defining Automatic Route Selection tables to dedicate trunk groups for
outgoing call routing (see Automatic Route Selection (ARS), page 4-43)
12 Configuring services required for certain features (see Chapter 12, Configuring
Services; the features are described in Chapter 2, Aeonix Features)

The domain name of the Aeonix system can be modified only as long as no
phones or trunks have been added (see System Parameters, page 14-27).
Aeonix Setup Procedure
3

3-68 Getting Started Aeonix Administration Manual

 Chapter 4

Global Settings

4.1 Country-specific Dial Codes .................................................4-1

4.2 Locations ..............................................................................4-9

4.3 Dial Plans............................................................................4-19

4.4 Closed User Groups (CUG)................................................4-29

4.5 Schedules ...........................................................................4-37

4.6 Automatic Route Selection (ARS).......................................4-43

4.7 LDAP Connections .............................................................4-53

4.8 Single Sign On....................................................................4-67

Aeonix Administration Manual

 4.1 Country-specific Dial Codes

Every country has its own set of access codes, including international, long distance
carrier, and area dial codes, as well as emergency numbers and other short numbers.
These settings are defined in international and country-wide numbering plans, and
used for making calls to external numbers (that is, to destinations outside the local
network).
To allow Aeonix users to call external numbers, the applicable country and area dial
codes must be configured in the Aeonix system. These dial codes are managed from
the Country List Page. Managing country and area dial codes are described in Defining a
Country, page 4-4.

To associate country and area dial codes with Aeonix users, phones, or
trunks, they must be assigned to locations. For details, see Locations, page 4-9.

Country-specific Dial Codes

4

Aeonix Administration Manual Global Settings 4-1

  Country List Page

The Country List page displays the countries defined in the system. To open this page:
1 On the navigation pane, click Settings. The pane displays the Settings menus.
2 Select the Locations menu, and then click Country List.

Figure 4-1 Country List

Page

The country list is sorted by the Name column. If the list includes more than
one page, use the page navigation bar at the bottom of the list to navigate
between the pages.

For each country, the list displays the following information.

Table 4-1 Country List

Parameters Field Description

Name The name of the country

Country Code The call prefix used for calling this country from abroad

Long Distance The call prefix used for making long distance calls
Country-specific Dial Codes

Emergency The number dialed in this country to contact local emergency

Number services
4

4-2 Global Settings Aeonix Administration Manual

 From this page, you can perform the following actions:

Table 4-2 Actions

Performed from the Action Button Description
Country List Page
Add country Click Add to add a new country definition
(see Defining a Country, page 4-4).

Update In the list, click the country name to update the

—
country details of this country.
Delete Select the check box next to the country or
country countries to be deleted and then click Delete
(see Deleting Entities, page 3-66).

NOTE: A country cannot be deleted if it includes one

or more areas.
Access Click Help to receive online help.
online help

Country-specific Dial Codes

4

Aeonix Administration Manual Global Settings 4-3

  Defining a Country

To define a country:
1 On the Country List page (see Figure 4-1), do one of the following:
 To add a country, click Add, or select Add Country from the Locations
menu in the navigation panel.
 To update a country, select it from the country list.
The Country page is displayed.

Figure 4-2 Country Page

for a New Country
(General Tab)
Country-specific Dial Codes

2 Set the country parameters as described in the following table.

Table 4-3 General

Country Parameters Field Descriptions

Name The name of the country.

NOTE: The name of an existing country entry cannot

be modified.
4

4-4 Global Settings Aeonix Administration Manual

 Field Descriptions

Country code The call prefix that callers dial when calling this
country from another country.
Example: Country code of the United States is 1.

NOTE: The code of an existing country entry cannot

be modified.

Description A short description (optional)

Long distance access code The prefix dialed before the area code when making
a long distance call.
Example: US long distance access code is 1.

NOTE: In cases long distance calls can be made

without this prefix, leave the Mandatory
check box clear.

Emergency number The number callers dial to contact local emergency

services for assistance. This number can be dialed
with or without the outside line access code.
Example: The US emergency number is 911.

3 International access codes are prefixes used to dial out of the country. Define
them as follows under the General tab:
 To add an access code, click Add right of the International Access Codes
box, enter the access code in the displayed Access Code field, and click
OK.
For example, the international access code used in the United States is 011.
 To update an access code, select it and click Update to display the Access
Code field. Enter the correct access code and click OK.
 To delete an access code, select it and click Delete.
4 Country-wide numbers are short numbers and prefixes used country-wide for

Country-specific Dial Codes

accessing services such as operator assistance and wake-up services. Define
them as follows under the General tab:
 To add a country-wide number, click Add right of the Country-wide
Numbers box, enter the number in the displayed Number field, and click
OK.
Country-wide number examples for the United States are 800 (toll-free
calls), 900 (country-wide dial-it services), and 710 (United States
4

Government).

Aeonix Administration Manual Global Settings 4-5

  To update a country-wide number, select it and click Update to display the
Number field. Enter the correct number and click OK.
 To delete a country-wide number, select it and click Delete.
5 Click the Areas tab to add or delete areas as described in the following
procedures:
 Defining an Area, page 4-6
 Deleting Entities, page 3-66
6 On the Country page, click Save. The country is included in the list on the
Country List page.

Defining an Area

To add an area to a country, or to update a previously added area:

1 Under the Area tab of the Country page, click Add to define a new area,
Delete to remove an area, or click an area to update it. The Area page is
displayed.

Figure 4-3 Area Page for

a New Country
Country-specific Dial Codes
4

4-6 Global Settings Aeonix Administration Manual

 2 Define the area parameters as described in the following table.

Table 4-4 Country

Parameters Field Descriptions

Display name The name of the area

Area code The call prefix that callers dial to access the area.
Example: New York City has multiple area codes, including
917, 212, 347, 646, and 718, according to the region and the
network type. For each area code, a separate area must be
defined.

NOTE: To access the area from within the same country, the
long distance access code must be dialed before the
area code if the Mandatory check box is selected. The
long distance access code is defined country-wide
(see Defining a Country, page 4-4).

State / province The name of the state or province associated with the area, if
relevant

Use long If this check box is selected, the long distance access code
distance and and the area code must be dialed even for local calls. If the
area code on check box is cleared, local numbers are dialed without long
local calls distance access and area codes.

3 Area-wide numbers are short numbers and prefixes used within the area for
accessing services. Define the phone number patterns of the area:
 To add a area-wide number, click Add right of the Area-wide Numbers
box, enter the pattern in the displayed Number field, and click OK.
For example, in many US and Canadian cities, 311 is dialed to access
non-emergency municipal services.
 To update an area-wide number, select it and click Update. Enter the
correct pattern in the Number field and click OK.
 To delete an area-wide number, select it and click Delete.
4 At the bottom of the page, click OK. The name and area code of the area are Country-specific Dial Codes
displayed on the Country page under the Area tab.
5 Click Save to save the new settings.
4

Aeonix Administration Manual Global Settings 4-7

NOTES:
 4.2 Locations

Once country and area codes have been configured (see Country-specific Dial Codes,
page 4-1), they are associated with locations. A location relates to a specific country
and area within this country, and additionally defines basic emergency call (E-911)
settings. Multiple locations can be defined for any country and area, even if no Aeonix
server is installed there.
Locations are managed from the Location List Page. Managing locations includes the
following procedures:
 Defining a Location, page 4-12
 Defining Emergency Call Settings, page 4-16

Assigning Locations
Locations are assigned to Aeonix devices and specify the country and area in which
these devices are located and used. Devices include:
 Phones (see Defining a Phone in Aeonix, page 7-10)
 Trunks (see Defining a Trunk in Aeonix, page 8-10)
 Wave Gateways (see Defining a Wave Gateway, page 10-8)
 SIP voicemail services (see Defining Voicemail Applications in Aeonix, page 12-140)
Locations are also assigned to users. Users do not have to dial the codes and prefixes
of their associated location even when calling from another country, provided they are
connected to Aeonix (see Assigning a Location to a User, page 4-17).

Locations
4

Aeonix Administration Manual Global Settings 4-9

  Location List Page

The Location List page displays the locations defined in the system. To open this page:
1 On the navigation pane, click Settings. The pane displays the Settings menus.
2 Select the Locations menu, and then click Location List.

Figure 4-4 Location List

Page

The location list is sorted by the Name column. If the list includes more than
one page, use the page navigation bar at the bottom of the list to navigate
between the pages.

For each location, the list displays the following information.

Table 4-5 Location List

Parameters Field Description

Name The name of the location

Description An optional description of the location

Country The country of the location

Area The area in the country associated with the location

Time Zone The time zone associated with the location

Locations
4

4-10 Global Settings Aeonix Administration Manual

 From this page, you can perform the following actions:

Table 4-6 Actions

Performed from the Action Button Description
Location List Page
Add location Click Add to add a new location (see Defining a
Location, page 4-12).

Update In the list, click the location name to update the

—
location details of this location.
Delete Select the check box next to the location or locations
location to be deleted and then click Delete (see Deleting
Entities, page 3-66).
Access Click Help to receive online help.
online help

Locations
4

Aeonix Administration Manual Global Settings 4-11

  Defining a Location

To add or update a location:

1 On the Location List page (see Location List Page, page 4-10), do one of the
following:
 To add a location, click Add, or select Add Location from the Locations
menu in the navigation pane.
 To update a location, select it from the location list.
The relevant Location page is displayed.

Figure 4-5 Location Page

for a New Location

2 Set the location parameters as described in the following table.

Table 4-7 Location

Parameters Field Description

Name The name for the location, for example, Main Office.

NOTE: The name of existing locations cannot be modified.

Description A short description (optional)

Locations

Country The country of the location. (To define a country in the

Aeonix, see Defining a Country, page 4-4.)
4

4-12 Global Settings Aeonix Administration Manual

 Field Description

State/province The relevant state or province in the country.

NOTE: This field is only displayed if the Country selected

above has a state/province defined.

Area The relevant area in the country.

NOTE: This field is only displayed if a value has been selected

in the Country field above.

Time zone The time zone of the location

Default Sub Chose a Default Sub Location from the list. Default Sub
Location Locations are defined in the Sub Locations tab.

Devices at this Device and user attributes will be included in the updates to
location will be the E911 service provider database.
included in the
E911

Emergency In the Emergency Location ID (ELIN) field, enter the number

Location ID that the PSAP associates with the location.
(ELIN)
NOTE: Specifying an ELIN in this field will override any ELIN
set by IT in the switch port that the phone is connected
to, or ELIN programmed directly on the phone.

NOTE: Mobile devices such a notebook running Aeonix Touch

for Windows, a cellphone running Aeonix Touch for
Android, or a SIP handset running on WIFI do not
support the LLDP protocol.

Local Emergency The number to be dialed for emergency. 911 for example.
Number

Misdialed calls The destination user or number where

destination undefined/invalid/unroutable numbers are routed

3 Define emergency call parameters and emergency trunk groups as described in

Defining Emergency Call Settings, page 4-16.
4 Click Save. The location is included in the list on the Location List page.
Locations

To add or update a sub location:

1 On the Sub Location tab, do the following:
 To add a location, click Add.
4

The Location > Add page is displayed.

Aeonix Administration Manual Global Settings 4-13

 Figure 4-6 Location >
Add Page

2 Set the Sub Location parameters as described in the following table.

Table 4-8 Sub Location

Parameters Field Description

Sub Location The name for the sub location, for example, Chemistry
Name Building.

Description A short description (optional)

Emergency In the Emergency Location ID (ELIN) field, enter the number

Location ID that the PSAP associates with the location.
(ELIN)

Street The street name (if relevant).

Number The street address (if relevant).

City The city.

State/province The relevant state or province in the country.

Zip / Postal Code The Postal Code for the location.

Locations

3 Click Ok. The General tab of the Location page is displayed. The new Sub
Location is now available in the Default Sub Location list. Click Save to
save the newly defined Sub Location.
4

4-14 Global Settings Aeonix Administration Manual

 Locations
4

Aeonix Administration Manual Global Settings 4-15

  Defining Emergency Call Settings

Aeonix provides basic support of Enhanced 911, a feature supplied by the 911
emergency-calling system in the USA and Canada. This feature allows 911 operators
in PSAP (Public Safety Answering Point) and local emergency centers to be notified
of the emergency location without the person calling for help having to provide it.
Emergency calls have to reach their destination as fast as possible. For this purpose,
dedicated trunks are required to route them directly to the closest emergency service
node. In Aeonix, the trunk groups containing these trunks can either be specified as in
the following procedure, or on the relevant Trunk Group pages as described in
Reserving a Trunk Group for Emergency Calls, page 9-24.
Emergency call settings are configured at the location level on the relevant Location
page (see ) and applied to all 911 calls placed from this location (except for immediate
hot station devices). Toll barrier and ANI restrictions do not apply to emergency calls.

The emergency location (ELIN) can also be specified at the phone level. The
ELIN defined for a phone overrides the ELIN of the location if an emergency
call is placed from this phone.

To configure a location for emergency call support:

 In the Default sub location field,
 In the Emergency location ID (ELIN) field, enter the number that the PSAP
associates with the location.
 In the Local emergency number field, enter the number to which an
emergency call is routed if no emergency trunk group is available. (In this
case, the call routing is determined by the relevant ARS table, as described in
Automatic Route Selection (ARS), page 4-43.)
 To reserve a trunk group for emergency calls, select it from the Trunk Groups
box and click (the right arrow). (You can use the Search box for this
purpose.) The selected trunk group is moved to the Reserved box and added to
the list of emergency trunk groups.
Repeat this step to add other trunk groups.
Locations

To make a reserved trunk group available for all calls, remove it from the
Reserved box by selecting it there and clicking (the left arrow). You can
reserve or free multiple trunk groups by holding down the CTRL or SHIFT
4

key while selecting them.

4-16 Global Settings Aeonix Administration Manual

 E911 functionality is only supported on PRI and CAMA trunks; select the
trunk groups accordingly.

 Assigning a Location to a User

Assigning a location at the user level allows users to make calls using the dial codes
appropriate to this location rather than the dial codes relevant to the location of the
phone.
A user associated with a location dials according to the rules of this location even
when calling from an office abroad, provided this office is connected to the
organization’s Aeonix network. For example, users associated with “New York” do
not have to dial the international and long distance carrier access codes when calling
a destination in New York, even if they are calling from an office located outside of
the USA.
Location assignments are configured in the General Information sub-profile.
Depending on profile override permissions, location assignments can be overridden
for specific users (or trunk groups). For a detailed description of profiles,
see Chapter 5, Profiles.

If override is allowed, users can also set their location themselves in the
Aeonix Web Portal for Users. Refer to the relevant User Guide listed in
Related Documentation, page 1-17.

Locations
4

Aeonix Administration Manual Global Settings 4-17

NOTES:
 4.3 Dial Plans

Dial plans define:

 The structure and length of the aliases that can be assigned to Aeonix users
and trunk groups
 The codes that are dialed to make use of Aeonix features (see Chapter 2,
Aeonix Features for a description of the features)
Aeonix comes with a predefined System Dial Plan, which by default is assigned to the
Root CUG.
Dial plans are managed from the Dial Plan List Page. Managing dial plans is described
in Defining a Dial Plan, page 4-20.

When connecting to Aeonix from external systems (via SIP trunks, for example) ensure
that the dial plans of the two systems are different. If there is overlap, you can add ANI
manipulation rules to the Trunk Group of the external system to ensure there is no clash
between the dial plans (see Configuring Incoming Call Routing, page 9-12).

Dial Plans
4

Aeonix Administration Manual Global Settings 4-19

  Dial Plan List Page

The Dial Plan List page displays the dial plans defined in the system. To open this
page:
1 On the navigation pane, click Settings. The pane displays the Settings menus.
2 Select the Dial Plans menu, and then click Dial Plan List.

Figure 4-7 Dial Plan List

Page

The dial plan list is sorted by the Name column. If the list includes more than
one page, use the page navigation bar at the bottom of the list to navigate
between the pages.

From this page, you can perform the following actions:

Table 4-9 Actions

Performed from the Dial Action Button / Icon Description
Plan List Page
Add dial plan Click Add to add a new dial plan (see Defining a Dial
Plan, page 4-20).

Update dial In the list, click the dial plan name to update the
—
plan details of this dial plan.
Delete dial Select the check box next to the dial plan or dial
plan plans and click Delete (see Deleting Entities, page 3-66).

Access Click Help to receive online help.

online help

Clone dial Click this icon to create a duplicate of a specific dial

plan plan.

 Defining a Dial Plan

Dial Plans

To add or update a dial plan:

1 On the Dial Plan List page (see Dial Plan List Page, page 4-20), do one of the
4

following:

4-20 Global Settings Aeonix Administration Manual

  To create a dial plan, click Add, or select Add Dial Plan from the Dial
Plans menu in the navigation panel.
 To update a dial plan, select it from the dial plan list.
 To create a new dial plan based on the settings of an existing one, click
(the Clone icon) to the right of the relevant dial plan.

When you clone a dial plan, all parameter values are copied to the new dial
plan except for the dial plan name.

The relevant Dial Plan page is displayed.

Figure 4-8 Dial Plan Page

for a New Dial Plan
(Aliases Tab)

2 If this is a new dial plan, enter a name in the Name field.

The name of an existing dial plan cannot be modified.

3 Click the Aliases tab to display a list of predefined alias numbering patterns.
Add, update, or delete patterns as required:
 To add a pattern, click Add, enter the number in the Pattern field that is
Dial Plans

displayed at the bottom of the list, and click OK. Use the X wildcard to
represent any digit.
For example, 2XXX includes all numbers from 2000 to 2999. 706X
4

includes all numbers from 7060 to 7069.

Aeonix Administration Manual Global Settings 4-21

  To update a pattern, select it and click Update. Modify the number in the
Pattern field and click OK.
 To delete a pattern, select it and click Delete. You can select more than one
pattern for deletion by using the CTRL and SHIFT keys.

Patterns must be composed of numbers only. Use the X wildcard to

represent any digit.

4 Click the Features tab.

Figure 4-9 Dial Plan

Page—Features Tab

5 In each field under the Features tab, enter the digit or digit sequence to be
dialed, as described in the following table. (If necessary, feature codes can be
defined as is or start with the # (pound) sign, except for the Activate and
Deactivate features.)
In each field, you can enter more than one digit combination. Separate them
Dial Plans

using commas.

For information on how to use these codes, refer to the User Guide of the
4

relevant telephone (see Related Documentation, page 1-17).

4-22 Global Settings Aeonix Administration Manual

Table 4-10 Feature Codes
for Dial Plans Field Default Description
Dial No

ACD group 1974 Allows a member of an ACD group to log in to the

login/logout group or to log out of the group (toggle function).

Activate code 11 Activates a feature. Dial the code defined for a

feature, a forward destination or ACD group
number if necessary, and the Activate feature
code.

Agent 1975 In ACD groups, allows an agent to put himself into

release/resume break status (unavailable for calls to this ACD
group) and into non-break status (available for
calls).

Allow identity 14440 If dialed before placing a call, this code displays
presentation the calling user’s number to the call destination
party.

Auto Redial 178 Automatically redials busy or non-answering

external destinations according to the pre-defined
number of ring attempts.

Auto answer 138 When receiving an incoming call, automatically

off-hooks and activates microphone and speaker.
This feature allows call center agents to answer
calls without picking up the handset.

Break-in 124 Allows authorized user to break-in to an

established call.

Break-out 1447 Allows authorized user to break-out a target from a

call (placing the call on hold for the target), and
entering into a call with the target.

Call pickup 77 Allows users to retrieve a ringing call at another

(directed) phone.
In addition, users with multiple devices can divert
a call from one device to another device of theirs
when the first device is ringing or in an active call.

Call pickup 76 Allows any group member to pick up a ringing call

(group) for this group.
Dial Plans

Camp-on busy 176 Monitors a busy call destination and calls it as

soon as it becomes idle.
4

Aeonix Administration Manual Global Settings 4-23

 Field Default Description
Dial No

Camp-on idle 177 Monitors a non-answering idle call destination and

calls it as soon as the destination phone becomes
busy and then idle again.

SLT Camp-on Initiates a Camp-On Busy to a destination from an

(one digit) SLT / Pots phone. Pressing HKFLS will return the
user to dial tone. The default is no value defined
(disabled).
Aeonix provides Camp-On Busy for SLT / POTS
telephones for low-cost deployments.

Deactivate 10 Disables a previously activated feature. Dial the

code feature’s code followed by the Deactivate feature
code.

Directory 1994 Provides access to the Aeonix directory from

FlexSet, MGCP, and DKT phones.

Do Not Disturb 145 Automatically provides a Do-Not-Disturb busy tone

(DND) to callers. On an MGCP keyset (FlexSet-IP 280S,
T207M, T208M, T207M/NP, T208M/BL) or on a
digital keyset (FlexSet 120, 120D, 120L, 120S,
121S, 280, 280D, 280D-HS, 280S, 281S, and
DKT; connected through a Wave Gateway); a
DND indicator is displayed on the display panel.

NOTE: For contact center agents, only non-ACC

calls will be rejected.

Forward all 141 Forwards incoming calls to a specified number.

Forward on 140 Forwards incoming calls to a specified number

busy when the line is busy.

Forward on 143 Forwards incoming calls to a specified number

logoff when the user is logged out from all internal
devices assigned to this user and has no external
phone number defined.

Forward on no 142 Forwards incoming calls to a specified number

answer when the user does not answer the phone.
Dial Plans

Freeze Auto 179 Suspends the Auto Redial feature.

Redial

Last redial * Redials the last number dialed, including feature

4

codes dialed for this number.

4-24 Global Settings Aeonix Administration Manual

 Field Default Description
Dial No

Login/Logout 123 Toggles the caller's login/logout status by logging

in a logged out user and logging out a logged in
user.
This feature is mostly used when logging in to a
phone as a guest. (Default users are automatically
logged in when the phone registers with the
system.)

NOTE: When making an emergency call with the

emergency callback feature enabled, the
user will not be able to perform manual
logout of the phone for the next hour.
For logging in to an ACD group, see
ACD group login/logout above in this table.

Outside line 9 Provides the access tone for making calls outside
access code of the organization.

Restrict identity 14441 If dialed before placing a call, this code hides the
presentation calling user’s number from the call destination
party.

Record on 1443 Allows a user to record a call while in idle, hold, or

demand held state (toggle function).

Room Status 172 Allows hospitality users to activate a room status

definition on their phone by dialing 172 followed by
two digits (01-16) to indicate which of the various
16 room status definitions to activate.

Set default 159 Allows a user to set the default user of their
user registered Tadian SIP phone (and existing MGCP
or digital phones) by dialing 159 on the user’s
phone followed by the alias of the user, thereby
associating the phone with the user.

NOTE: This feature can be activated when the

system is in Auto Phone PnP mode (see
Configuring PnP Provisioning, page 12-126) from
phones that have a value defined as Default
User and from phones that have no value. It
can also be used when Tadiran TGW
Dial Plans

gateways Auto Generation mode is

activated without users (see Defining a Tadiran
TGW Gateway, page 10-42).
4

Aeonix Administration Manual Global Settings 4-25

 Field Default Description
Dial No

Silent monitor 1981 Allows an authorized user to listen in on an

both sides established call for monitoring and voice recording
purposes.

NOTE: The authorized user continues monitoring

the line (even when there is no active call)
until the feature is deactivated and the
parties of the call are not aware that the call
is being monitored.

Silent monitor 1449 Allows an authorized user to listen in on agent

partner side conversations (to the user partner call side only) of
an established call for monitoring and voice
recording purposes.

NOTE: The authorized user continues monitoring

the line (even when there is no active call)
until the feature is deactivated and the party
is not aware that the call is being monitored.

Silent monitor 1448 Allows an authorized user to listen in on agent

user side conversations (to the Aeonix user call side only) of
an established call for monitoring and voice
recording purposes.

NOTE: The authorized user continues monitoring

the line (even when there is no active call)
until the feature is deactivated and the party
is not aware that the call is being monitored.

Turn off MWI 175 Turns off the message waiting indicator lamp on
the user’s phone, which is lit if the user has
unretrieved messages waiting in the voicemail box.

NOTE: For phones without MWI lamps, a special

ringing can be used—and turned off—to
notify of new messages. To learn more
about MWI, refer to the SeaMail
Administration Manual (see Related
Documentation, page 1-17).

Voice page 191 Allows a user to place a voice page call to another
user, provided the called user is configured to
Dial Plans

accept voice page calls and uses an MGCP

keyset (FlexSet-IP 280S, T207M, T208M,
T207M/NP, T208M/BL) or a digital keyset (FlexSet
120, 120D, 120L, 120S, 121S, 280, 280D,
280D-HS, 280S, 281S, DKT, and DST; connected
4

through a Wave Gateway).

4-26 Global Settings Aeonix Administration Manual

 Field Default Description
Dial No

Wakeup 173 Allows hospitality users to request to be called at a

designated time.

NOTE: Wakeup call attempts will be made even

when users are in DND mode.

6 Click Save to save the dial plan. The dial plan is included in the list on the
Dial Plan List page.

Dial Plans
4

Aeonix Administration Manual Global Settings 4-27

NOTES:
 4.4 Closed User Groups (CUG)

Currently only the root CUG (i.e. system-wide CUG) is supported in Aeonix.

Closed User Groups (CUG) are used to manage different companies within the same
VoIP system. Each CUG is treated as a unique exchange, even though the CUGs are
managed in the same Aeonix system. CUGs allow for building up hosted and
co-hosted systems, in which members of one CUG do not have access to the
information of other independent CUGs.
Each CUG can contain one or more subordinated CUGs (sub-CUGs). While
administrators of the CUG can access information related to this CUG and all its
sub-CUGs, sub-CUG administrators can only access the information in the
subordinated CUG to which they belong (see also Administrator Levels, page 3-4).
The assignment of settings to an entity might be restricted depending on the CUG
associated with these settings. For example, if the CUGs Company A and Company B
have been defined at the same hierarchy level, it is not possible to select and assign a
sub-profile belonging to Company A to a Company B user profile. However, a user
profile assigned to sub-CUG Company B Marketing can include a Company B
sub-profile.
You can define new Closed User Groups, edit the settings of an existing CUG and
delete obsolete CUGs. Aeonix comes with a default Closed User Group named Root.
This CUG contains all existing and future CUGs in the system and cannot be deleted.
Each Closed User Group must be assigned a dial plan, which specifies the applicable
dial patterns and feature codes. For the Root CUG (meaning system-wide), you can Closed User Groups (CUG)
also define the music or message that is played when a caller is put on hold or
transferred to another number. Confirmation and rejection tones can be used to notify
users of SIP phones as to whether or not they succeeded in activating a feature.
When a new entity (user, trunk group, phone, trunk, Wave Gateway, or user/pickup
group) is defined in Aeonix, it must be assigned a Closed User Group. An existing
entity cannot be moved to another CUG. This applies also to ARS tables, schedules,
4

profiles, and sub-profiles.

Aeonix Administration Manual Global Settings 4-29

 Closed User Groups are managed from the Closed User Group Tree Page. Managing
Closed User Groups includes the following procedures:
 Defining a Closed User Group, page 4-32
 Adding Members to a Closed User Group, page 4-35
Closed User Groups (CUG)
4

4-30 Global Settings Aeonix Administration Manual

  Closed User Group Tree Page

Currently only the root CUG (i.e. system-wide CUG) is supported in Aeonix.

CUGs are configured and managed on the Closed User Group Tree page.

To open this page:

1 On the navigation pane, click Settings. The pane displays the Settings menus.
2 Select the CUGs menu, and then click CUG Tree.

Figure 4-10 Closed User

Group Tree Page

The Closed User Group Tree page shows the CUGs defined in the system in a
hierarchical tree structure.
From this page, you can perform the following actions:

Table 4-11 Actions

Performed from the Action Button Description
Closed User Group Tree
Page Define new Click to add a new Closed User Group under Root
CUG or under another existing CUG (see Defining a Closed
User Group, page 4-32).
Edit CUG Click to make changes to the settings of a CUG.

Delete CUG Click to delete a CUG (see Deleting a Closed User Group,
page 4-35).

Access Click Help to receive online help.

Closed User Groups (CUG)

online help
4

Aeonix Administration Manual Global Settings 4-31

  Defining a Closed User Group

Currently only the root CUG (i.e. system-wide CUG) is supported in Aeonix.

To add or update a CUG:

1 On the Closed User Group Tree page (see Figure 4-10), do one of the
following:
 To add a Closed User Group in the CUG hierarchy tree, select Root or the
Closed User Group under which to place the new CUG, and then click Add
Sub-CUG.
 To update a Closed User Group, select it in the hierarchy tree and click
Edit CUG.
The relevant Closed User Group page is displayed.

Figure 4-11 Closed User

Group Configuration
Page for a New CUG

2 Set the CUG configuration parameters as described in the following table.

Closed User Groups (CUG)

Table 4-12 CUG Setting

Parameters Field Description

CUG name The name of the Closed User Group.

NOTE: The name of an existing CUG cannot be modified.

Description A text description of the CUG (optional)

4

4-32 Global Settings Aeonix Administration Manual

 Field Description

Access code A unique number for accessing the CUG from within the
telephone dialing system.

NOTE: The access code of an existing CUG cannot be

modified.

Dial plan The dial plan applied to the CUG (see Dial Plans, page 4-19)

3 The Music and Tone Files parameter box lists the audio files for messages
played to callers put on hold.

Table 4-13 Music on Hold

Audio Files Message Type Description

Music On Hold The file containing the music or message played to callers
while they are put on hold

Confirmation The file containing the tone or message played on a SIP

phone upon successful activation or deactivation of a feature

Rejection The file containing the tone or message played on a SIP

phone if the activation or deactivation of a feature failed

In the current version, music on hold parameters can be modified for the
Root CUG only.

Click Edit next to the message to be modified. The Music On Hold

Configuration dialog box is displayed.

Closed User Groups (CUG)

4

Aeonix Administration Manual Global Settings 4-33

 Figure 4-12 Music On
Hold Configuration
Dialog Box

You can define the audio source for each codec type (G711 A-law,
G711 µ-law, and G.729) as described in the following table.

Table 4-14 Audio Sources

for Announcements Option Description

None Select this option to specify that no announcement or music

is played for the selected codec type.

File Select this option to retrieve the announcement or music from

an audio file. This file must be located on the Aeonix server
under /home/aeonixadmin/aeonix/resources/audio.

NOTE: If Aeonix runs in a cluster environment, the file must be

Closed User Groups (CUG)

stored on each of the servers.

4 Scroll down to the bottom of the dialog box and click OK to close the dialog
box.
5 Click Save. The Closed User Group is saved and displayed at the relevant
place in the hierarchy tree.
4

4-34 Global Settings Aeonix Administration Manual

  Adding Members to a Closed User Group

Currently only the root CUG (i.e. system-wide CUG) is supported in Aeonix.

CUG members can be Aeonix users, trunk groups, phones, or trunks. It is not possible
to add members to a CUG through the Closed User Group Tree page. Entities are
associated with Closed User Groups only as part of the initial entity definition process.
An entity’s CUG membership cannot be modified.
Administrators assigned to the Root CUG have access to all entities and settings
defined in the system. In contrast, administrators and users assigned to a CUG can
display or monitor only entities and settings that belong to this CUG, or to sub-CUGs
related to this CUG.

 Deleting a Closed User Group

Currently only the root CUG (i.e. system-wide CUG) is supported in Aeonix.

When you delete a Closed User Group, all its sub-groups are also deleted.

To delete a CUG:
1 From the Closed User Group tree (see Figure 4-10), select the required CUG.
2 Click Remove CUG. The Delete CUG confirmation message is displayed.
3 Click Yes to delete the CUG and all its sub-groups from the system.

Closed User Groups (CUG)

4

Aeonix Administration Manual Global Settings 4-35

NOTES:
 4.5 Schedules

Schedules can be used to control when selected routing rules for forwarding or
rejecting incoming calls will be in effect. A schedule consists of time frames for
special situations, such as holidays or emergency situations, and for repeating
situations, such as working hours, night hours, or weekends.
Once a schedule has been defined, it can be used to apply an incoming call routing rule
only at the specified time frame or frames. For example, on holidays, incoming calls
can be automatically forwarded to the users’ mailboxes. Schedules can also be defined
or overridden for a specific user, as in the case in which night calls are forwarded to
the user’s cellular phone number.
Global schedules are managed from the Schedule List Page. Managing schedules is
described in Defining a Schedule, page 4-39.
To learn about incoming call routing and the use of schedules within incoming call
routing rules, see Incoming Call Routing Sub-profiles, page 5-31.

Schedule Levels
Schedules can be defined at the following three levels:
 Global—these are system-wide schedules that can be assigned to any schedule
profile, user, or trunk. Managing global schedules is described in this section.
 Schedule profile—a schedule profile can include global schedules, as well as
schedules created specifically for this profile (see Schedule Sub-profiles,
page 5-28).
 Individual user—an assigned schedule profile can be modified for a specific
user, or replaced by a global schedule (Overriding Schedules, page 6-39). Schedules
4

Aeonix Administration Manual Global Settings 4-37

  Schedule List Page

Global schedules are created and managed from the Schedule List page. To open this
page:
1 On the navigation pane, click Settings. The pane displays the Settings menus.
2 Select the Schedules menu, and then click Schedule List.

Figure 4-13 Schedule List

Page

The Schedule List page shows the schedules defined in the system. If a schedule
includes more than one time frame, they are displayed in a drop-down list.
From this page, you can perform the following actions:

Table 4-15 Actions

Performed from the Action Button Description
Schedule List Page
Add new Click Add to add a new global schedule
schedule (see Defining a Schedule, page 4-39).

Update n the list, click the schedule name to update the

—
schedule details of this schedule.
Delete Select the check box next to the schedule or
schedule schedules to be deleted and then click Delete
(see Deleting Entities, page 3-66).

NOTE: Deleting a schedule also deletes all time

frames that belong to this schedule.
Access Click Help to receive online help.
online help
Schedules
4

4-38 Global Settings Aeonix Administration Manual

  Defining a Schedule

To add or update a schedule:

1 On the Schedule List page (see Figure 4-13), do one of the following:
 To create a schedule, click Add, or select Add Schedule from the
Schedules menu in the navigation panel.
 To update a schedule, select it from the schedule list.
The relevant Schedule page is displayed.

Figure 4-14 Schedule

Page for a New Schedule

2 If this is a new schedule, enter a name in the Name field, for example,
Holidays or Work Hours.
3 Use the Time Frame List area to define or remove time frames as described in
the following procedures:
 Defining a Time Frame, page 4-39
 Deleting Entities, page 3-66
4 On the Schedule page, click Save. The schedule is saved and displayed on the
Schedule List page.

Defining a Time Frame

A schedule must have at least one time frame in order to be meaningful.

To add or update a time frame:

1 On the Schedule page (see Figure 4-14), click Add in the Time Frame List, or
Schedules

click the name of the time frame to be updated. The Time Frame page is
displayed.
4

Aeonix Administration Manual Global Settings 4-39

 Figure 4-15 Time Frame
Page

2 If this is a new time frame, enter a name in the Name field, such as
Independence Day or Regular Work Hours.

The name of an existing time frame cannot be modified.

3 Set the time zone for the time frame:

 To use the time zone defined in Aeonix, select Adjust time zone.
 To assign another time zone, clear Adjust time zone and select the relevant
time zone from the drop-down list.
4 For a time frame that occurs only once, clear the Recurrence check box, and
specify the date and hour in the Start time and the End time fields.

If you select All day event, the time frame covers the whole day.
Consequently, the drop-down lists for specifying the hours are not displayed.

5 For a recurring time frame, select Recurrence. The Recurrence parameters are
displayed on the page.
Schedules
4

4-40 Global Settings Aeonix Administration Manual

Figure 4-16 Time Frame
Page with Recurrence
Parameters

Set the relevant options as described in the following table.

Schedules
4

Aeonix Administration Manual Global Settings 4-41

 Table 4-16 Parameters for
Recurrent Time Frames Field Option Description

Recurrence Daily In Every...day(s), enter a daily interval for the time

pattern frame.
Example: If you enter 3, a routing rule that is based
on this time frame is activated every third day.

Weekly In Recur every...week(s), enter the weekly interval for

the time frame. Select one or more weekdays to include
these days in the time frame.
Example: If you enter 4 and select Saturday and
Sunday, a routing rule that is based on this time
frame is activated every forth week on Saturday and
Sunday.

Monthly Set the relevant option:

 Day of month(s)—the day of the month and the
monthly interval of the time frame.
Example, Day 3 of every 2 month(s) means that a
routing rule that is based on this time frame is
activated bi-monthly on the third of the month.
 Weekday of month(s)—the weekday and the monthly
interval of the time frame.
Example, The first Sunday of every 2 month(s)
means that a routing rule that is based on this time
frame is activated bi-monthly on the first Sunday of
the month.

Yearly Set the relevant option:

 Date—the time frame’s month and day in every year.

Example, Every January, 1 means that a routing

rule that is based on this time frame is activated
every New Year’s Day.
 Weekday and month—the weekday and month of the
time frame

Range of The start date and, optionally, the end date of the
recurrence period during which a routing rule based on this time
frame is activated. If no end date is required, select No
end date.
Schedules

6 Click OK. The name of the time frame, as well as its type, start time, and end
time, are displayed in the Time Frame List on the Schedule page.
7 Click Save.
4

4-42 Global Settings Aeonix Administration Manual

 4.6 Automatic Route Selection (ARS)

Automatic Route Selection (ARS) tables specify the trunk groups through which
external calls are routed. This feature provides the capability of routing outgoing calls
through the most cost-effective channels while maintaining acceptable call quality.

Before ARS tables can be created, the required trunk groups must be
defined (see Chapter 9, Managing Trunk Groups), as well as the applicable
country and area codes (see Country-specific Dial Codes, page 4-1).

Automatic Route Selection tables are managed from the ARS Table List Page. Managing
Automatic Route Selection includes the following procedures:
 Defining an ARS Table, page 4-46
 Testing an ARS Table, page 4-49
The system includes a predefined default ARS table, which can be modified, but not
deleted. Which ARS table is used for routing a call depends on the Outgoing Call
Routing sub-profile of the calling user (see Assigning Automatic Route Selection Tables to
Users, page 4-50).

How Automatic Route Selection Works

You can define ARS routing tables to specify how calls are routed depending on their
prefix number. A prefix number can be based on one of the following, which is
prioritized by the system from most to least specific:

Automatic Route Selection (ARS)

 Country code, area code, and the first digits of a phone number (given highest
priority)
 Country code and area code (given medium priority)
 Country code (given low priority)
 A default prefix definition can be defined for the routing of calls that do not
match any of the prefixes specified in the routing table (given lowest priority)
When performing Automatic Route Selection for an outgoing call, the system attempts
to make the best prefix match according to the above priority levels and routes the call
4

according to the corresponding trunk group. If the trunk group of a prefix number of

Aeonix Administration Manual Global Settings 4-43

 a higher priority is unable to process the call, the system checks the next priority level
until it reaches the lowest priority level (if necessary).
The system also takes into account the country code and the area code of the calling
user’s location (see Locations, page 4-9) and adds the codes to the dialed number if they
are missing.
An example of how a routing table affects the routing of calls is provided in ARS Table
Example, page 4-50. A further case that involves Automatic Route Selection can be
found in Example for Digit Manipulation Rules in a Trunk Group, page 9-21.

 ARS Table List Page

Routing tables are defined and managed from the ARS Table List page. To open this
page:
1 On the navigation pane, click Settings. The pane displays the Settings menus.
2 Select the ARS menu, and then click ARS Table List.

Figure 4-17 ARS Table

List Page

The ARS Table List page displays the names of all Automatic Route Selection tables
defined in the system.
Automatic Route Selection (ARS)
4

4-44 Global Settings Aeonix Administration Manual

 From this page, you can perform the following actions:

Table 4-17 Actions

Performed from the ARS Action Button / Icon Description
Table List Page
Add new Click Add to add a new routing table (see Defining an
ARS table ARS Table, page 4-46).

Update ARS In the list, click the routing table name to update the
—
table details of this table.
Delete ARS Select the check box next to the routing table or
table tables to be deleted and then click Delete
(see Deleting Entities, page 3-66).
Access Click Help to receive online help.
online help

Clone ARS Click this icon to create a duplicate of a specific

table routing table.

Automatic Route Selection (ARS)

4

Aeonix Administration Manual Global Settings 4-45

  Defining an ARS Table

To add a new or update an existing Automatic Route Selection table:

1 On the ARS Table List page (see Figure 4-17), do one of the following:
 To create a routing table, click Add, or select Add ARS Table from the
ARS menu in the navigation panel.
 To update an existing routing table, select it from the ARS table list.
 To create a new routing table based on the settings of an existing one, click
(the Clone icon) to the right of the relevant routing table.

When you clone a routing table, all parameter values are copied to the new
routing table except for the ARS table name and the Closed User Group.

The relevant ARS Table page is displayed.

Figure 4-18 ARS Table

Page for a New ARS
Table

The page displays a list of the defined prefixes, the prefix details (country
code, area code, and number), and the trunk groups (channels) through which
the relevant calls are routed.
2 If this is a new automatic routing table, enter the table name in the Name
Automatic Route Selection (ARS)

field.
3 In the Prefix List, specify outgoing call prefixes and their Automatic Route
Selection trunk groups. Use the following procedures as required:
 Defining a Prefix Routing Definition, page 4-47
 Deleting Entities, page 3-66
4 Verify that the Automatic Route Selection table definitions are correct
(see Testing an ARS Table, page 4-49). Make corrections as required.
5 Click Save. The routing table is saved and displayed on the ARS Table List
4

page.

4-46 Global Settings Aeonix Administration Manual

 Defining a Prefix Routing Definition

To add or update the Automatic Route Selection settings of a prefix:

1 In the prefix list on the ARS Table page (see Figure 4-18), perform the
required action:
 Click Add to add a new prefix routing definition.
 Click Add Default to define how a call is routed if it does not match any
prefix routing definition in the prefix list.
 Click a list to update its routing definitions.
The fields for defining the ARS settings of the prefix are displayed.

Figure 4-19 Defining ARS

Settings for a Prefix

2 Define the prefix number (only digits).

Automatic Route Selection (ARS)

The Default routing definition does not apply to a specific prefix; therefore, no
prefix can be defined for it.

 To apply the prefix routing definition to calls of a specific country, enter the
Country code (without the international access code).
 To apply the prefix routing definition to calls of a specific area, enter the
Country code and the Area code (without the long distance access code).
 To apply the prefix routing definition for numbers that begin with the same
digits, enter the Country code and the Area code, and enter the digits in
4

Aeonix Administration Manual Global Settings 4-47

 the Number field. This is typically used for companies, in which all
employee phone numbers begin with the same digit or digits.
Example: If Country code is set to 44 (UK), Area code to 161
(Manchester), and Number to 444, all calls to numbers in Manchester
beginning with 444 are routed according to the defined routing pattern.
3 The Available Trunk Groups box displays the trunk groups defined in the
system (see Chapter 9, Managing Trunk Groups). To route outgoing calls with
the specified prefix through a specific trunk group, select the trunk group and
click (the right arrow). The selected item is moved to the Selected Trunk
Groups box.
Repeat this step to add other trunk groups to the Selected Trunk Groups box.

To remove a trunk group from the Selected Trunk Groups box, select it and
click (the left arrow). You can add or remove multiple trunk groups by
holding down the CTRL or SHIFT key while selecting them.

4 Use (the Up and Down arrows) to define the routing order of the trunk
groups in the Selected Trunk Groups box. The system routes outgoing calls
with the specified prefix number through the first available trunk group listed
in the box.
5 Click OK. The prefix routing definition is displayed in the prefix list.
6 Click Save.
Automatic Route Selection (ARS)
4

4-48 Global Settings Aeonix Administration Manual

  Testing an ARS Table

For complex routing schemes, it is recommended to check whether the prefix routing
definitions are correct. The ARS testing feature allows you to view through which
trunk group a specific dial number is routed.

To verify an ARS table:

1 On the ARS Table page (see Figure 4-18), click the Test bar. The test fields
are displayed.

Figure 4-20 ARS Test

Parameters

2 In the Dial number field, enter a dial number as it would be dialed from the
selected origin location (see the following step).
3 Select the Origin location from which the call is placed. The system
automatically adds the country code and area code to the destination number as
required by the origin location.
4 Click the Test button. The trunk group or groups for routing the specified call
are displayed.
If more than one prefix definition applies to the specified call, the trunk groups
of the closest prefix match are displayed first. If no Automatic Route Selection
scheme is defined for the prefix of the specified call, the system displays none.
If the test yields unexpected results, check the following:
 The ARS table prefixes and their associated trunk group or groups (see Defining
an ARS Table, page 4-46).

Automatic Route Selection (ARS)

 The Origin location selected for the test—verify that the correct location was
selected and make sure the relevant country and area are associated with this
location (see Locations, page 4-9).
 The location’s country—make sure the country code and the relevant area code
are correctly defined (see Country-specific Dial Codes, page 4-1).
4

Aeonix Administration Manual Global Settings 4-49

 Even if the test is successful, the ARS routing definitions will not apply to
calls that are restricted by the toll barrier settings of the calling user. See Toll
Barrier Sub-profiles, page 5-24 for details.

 Assigning Automatic Route Selection Tables to Users

An Automatic Route Selection table can be associated with Outgoing Call Routing
sub-profiles (see Outgoing Call Routing Sub-profiles, page 5-41) and applied to the calls
placed by users that are assigned the relevant sub-profile. For a specific user, the
assigned routing table can be replaced by another, just like other outgoing call routing
parameters (see Overriding Outgoing Call Routing Parameters and Rules, page 6-43).
The use of profiles allows you to apply different routing tables to different users. For
example, to route calls from the CEO through a dedicated high-quality trunk group,
define the relevant routing table, include this table in an Outgoing Call Routing
sub-profile, and assign the sub-profile to the CEO user profile.

 ARS Table Example

This example assumes the relevant countries, area codes, locations, and
trunk groups have been previously defined (see Country-specific Dial Codes,
page 4-1, Locations, page 4-9, and Chapter 9, Managing Trunk Groups).

In this example, an organization has two offices in the United States (country code 1):
one in Brooklyn (area code 718) and one in Manhattan (area code 212). In addition,
the organization has an office in Switzerland (country code 41).
Automatic Route Selection (ARS)

For each of the office locations, a gateway is defined as a trunk group in Aeonix. These
trunk groups are referred to as GW_Brooklyn, GW_Manhattan, and GW_Swiss
respectively.
The following ARS table (prefix list) defines how the organization’s outgoing calls are
routed.
4

4-50 Global Settings Aeonix Administration Manual

Figure 4-21 ARS Table
Example

When an employee of this organization places a call to a destination outside of the

organization, the system automatically adds the country code and the area code in the
dialed number as required, uses the relevant ARS table to compile a list of all trunk
groups that fully or partially match the call prefix, and tries to route the call through
the trunk group that best matches the prefix (that is, the first match in the list). If the
call transmission fails, the system tries the next trunk group in the list.
In this example, if a user dials 1-212-5555555, the ARS table’s routing rules apply in
the following order:
 Use GW_Manhattan (the trunk group specified for the prefix 1-212)
 Use GW_Brooklyn or, if not available, GW_Manhattan (the trunk groups
specified for the US country code prefix 1)
 Use GW_Brooklyn (the default trunk group)
As a result of these rules, the system tries to route the call through GW_Manhattan. If

Automatic Route Selection (ARS)

the routing fails, GW_Brooklyn is used instead.
If the user dials 41-1-1234567, the system tries to route the call through
GW_Switzerland (the trunk group specified for the Swiss country code prefix 41). If
the routing does not succeed, the default trunk group GW_Brooklyn is used.
4

Aeonix Administration Manual Global Settings 4-51

NOTES:
 4.7 LDAP Connections

The LDAP (Lightweight Directory Access Protocol) synchronization capability of the

Aeonix system helps to keep user data updated by synchronizing it with the database
residing on the organization’s LDAP server. Just as other users defined in Aeonix,
imported LDAP users are displayed on the User List page (see Figure 4-1).

 Lightweight Directory Access Protocol (LDAP)

The Lightweight Directory Access Protocol, or LDAP, is a networking protocol for

querying and modifying directory services running over TCP/IP. The database of an
LDAP server usually consists of LDAP directories in the form of a tree of entries.
LDAP entries may represent people, organizational units, printers, documents, groups
of people, and so on. Each entry is identified by a unique DN (distinguished name).
The DN indicates the location of the entry within the directory tree and consists of a
set of named attributes with values.
Connections to LDAP servers and corresponding LDAP query search options can be
configured in Aeonix for the purpose of retrieving user information from the LDAP
Active Directory. User attributes between Aeonix and the LDAP server can be mapped
for all types of Aeonix alias entities, including Aeonix users, Hunt groups, ULA
groups, Zone page, Conference calls, and Meet-me conferences.
Provisioned Tadiran SIP phones have LDAP read-only access to the Aeonix database
as defined by the default LDAP directory, providing Aeonix users with access to the
built-in Aeonix directory.
LDAP connections are managed from the LDAP Connection List Page. Managing LDAP Connections

LDAP connections includes the following procedures:

 Defining an LDAP Connection, page 4-55
 Testing LDAP Connections Parameters, page 4-61
 Synchronizing LDAP Connection Parameters, page 4-62
 Default LDAP Directory, page 4-64
4

Aeonix Administration Manual Global Settings 4-53

  LDAP Connection List

The LDAP Connection List page displays the LDAP connections defined in the
system. To open this page:
1 On the navigation pane, click Settings. The pane displays the Settings menus.
2 Select the LDAP menu, and then click LDAP connection List.

Figure 4-22 LDAP

Connection List Page

The LDAP Connection List page shows the LDAP connections defined in the system.
For each LDAP connection, the list displays the following information.

Table 4-18 LDAP

Connection List Field Description
Parameters
Connection ID The name of the LDAP server

Description A short description of the LDAP server (optional)

Server Address The LDAP server address (IPv4 or IPv6) to which LDAP
requests are sent

Server Port The TCP/IP port on which the LDAP server is listening
(Default:
389)

CUG The Closed User Group associated with the LDAP connection
(see Closed User Groups (CUG), page 4-29).

TLS Transport Layer Security. A check icon is displayed if defined

as a secured LDAP connection (see Table 4-20).

NOTE: The default server port for secured LDAP connections

is 636.
LDAP Connections
4

4-54 Global Settings Aeonix Administration Manual

 From this page, you can perform the following actions:

Table 4-19 Actions

Performed from the Action Button / Icon Description
LDAP Connection List
Page Add LDAP Click Add to add a new LDAP connection
connection (see Defining an LDAP Connection, page 4-55).

View / Edit In the list, click the server ID to view or edit the
LDAP — details of this LDAP connection.
connection
Delete LDAP Select the check box next to the server ID or server
connection IDs and click Delete (see Deleting Entities, page 3-66).

NOTE: LDAP connections assigned to a CUG cannot

be deleted.
Access Click Help to receive online help.
online help

 Defining an LDAP Connection

To add or update an LDAP connection:

1 On the LDAP Connection List page (see Figure 4-22), do one of the following:
 To create an LDAP connection, click Add, or select Add LDAP
Connection from the LDAP menu in the navigation panel.
 To update an LDAP connection, select it from the LDAP connection list.
The relevant LDAP Connection page is displayed.

Figure 4-23 LDAP

Connection Page for a
New LDAP Connection -
Connection Tab

LDAP Connections

2 If this is a new LDAP connection, enter a name of the LDAP server in the
Server ID field
4

3 Enter an optional description of the LDAP connection in the Description field.

Aeonix Administration Manual Global Settings 4-55

 4 Set the Connection tab parameters as described in the following table.

Table 4-20 LDAP

Connection Parameters Field Description

Server address The LDAP server address (IPv4 or IPv6) to which LDAP
requests are sent.

User name A valid user name required for accessing the LDAP server.

Password The corresponding password required for accessing the

LDAP server.

Port The TCP/IP port on which the LDAP server is listening.

NOTE: The default server port for LDAP connections is 389.

TLS If this check box is selected, this is a secured Transport

Layer Security (TLS) LDAP connection (see Table 4-18).

NOTE: The default server port for secured LDAP connections

is 636.

Synchronization The parameters in this section control auto-synchronization of

Aeonix with the specified LDAP service.

At time of day What time the daily synchronization will be run automatically.

Servers Which Aeonix servers in the cluster will be updated.

5 Click the Attribute Mapping tab.

Figure 4-24 LDAP

Connection
Page—Attribute Mapping
Tab
LDAP Connections
4

4-56 Global Settings Aeonix Administration Manual

 6 Set the attribute mapping parameters as described in the following table.

Table 4-21 Attribute

Mapping for LDAP Field Description
Connection
User The LDAP entry may have special characters or syntax that is not
regular desired in the Aeonix version of the data. Click the check box to
expression enable regular expression filtering of the LDAP field as it is copied
(unique for into Aeonix. Enter the appropriate regular expression for the
each LDAP desired filter affect.
field)

Login The LDAP attribute name corresponding to the User ID field in

name Aeonix (mandatory).
(Default: Set the relevant mapping option:
cn)  cn—common name LDAP directory attribute
 objectGUID—the unique identifier for the LDAP directory object.
 Other—enter another LDAP attribute to map to the Aeonix user
ID.

Display The LDAP attribute name corresponding to the Display name field
name in Aeonix (optional).
Select the Display name check box and set the relevant option:
 displayName—display name LDAP directory attribute
 Other—enter another LDAP attribute to map to the Aeonix user
ID.

First name The LDAP attribute name corresponding to the First name field in
Aeonix (optional).
Select the First name check box and set the relevant option:
 givenName—given name LDAP directory attribute
 Other—enter another LDAP attribute to map to the Aeonix user
ID.

Last name The LDAP attribute name corresponding to the Last name field in
Aeonix (optional).
Select the Last name check box and set the relevant option:
 sn—surname LDAP directory attribute
 Other—enter another LDAP attribute to map to the Aeonix user
ID.

Description The LDAP attribute name corresponding to the Description field in

LDAP Connections

Aeonix (optional).
Select the Description check box and set the relevant option:
 Description—description LDAP directory attribute
 Other—enter another LDAP attribute to map to the Aeonix user
ID
4

Aeonix Administration Manual Global Settings 4-57

 Field Description

Email The Email attribute name corresponding to the Email field in Aeonix
(optional).
Select the Email check box and set the relevant option:
 email—email LDAP directory attribute
 Other—enter another LDAP attribute to map to the Aeonix user
ID

Internal The LDAP attribute name corresponding to the Internal Numbers

Aliases field in Aeonix (optional).
Select the Internal Aliases check box to set the telephoneNumber
LDAP directory attribute. To the right of the Internal Aliases box,
you can add/remove additional attributes, as follows:
 Add—click, add other attributes (except for N/A), and click OK.
 Select—click, add additional attributes (otherTelephone,
ipPhone, and otherIpPhone) from the drop-down list, and click
OK.
 Delete—select the attribute you want to delete from the list.

External The LDAP attribute name corresponding to the External Numbers

Numbers field in Aeonix (optional).
Select the External Aliases check box to set the mobile LDAP
directory attribute. To the right of the External Aliases box, you
can add/remove additional attributes, as follows:
 Add—click, add other attributes (except for N/A), and click OK.
 Select—click, add additional attributes (otherMobile and
homePhone) from the drop-down list, and click OK.
 Delete—select the attribute you want to delete from the list.

7 Click the Search Settings tab.

LDAP Connections
4

4-58 Global Settings Aeonix Administration Manual

Figure 4-25 LDAP
Connection
Page—Search Settings
Tab

8 Click on a search filter Name to open a search filter, or click Add to create a
new search filter. The Search Filter page is displayed as shown in the
following figure.

Figure 4-26 LDAP Search

Filter Page—Search Filter
Tab

LDAP Connections

9 Enter the base distinguished name in the Base DN field.

4

Aeonix Administration Manual Global Settings 4-59

 The base DN indicates the starting point for searches in this LDAP directory
server.

10 In the Filter box, enter search filters to specify which records are returned by
the LDAP Directory Server (optional).

Search filters are composed of attribute matching components. For example,

constructing a search filter to return all the entries in a directory that contain
an attribute called uid with one value equaling testuser would use the
following filter: (uid=testuser)

11 Click on the New User Settings tab to set parameters for how new Aeonix
users will be created for entries in the LDAP database that have not previously
been defined in Aeonix.

Figure 4-27 LDAP Search

Filter Page—New User
Settings Tab

The following fields can be defined in the New Users Settings tab.
LDAP Connections

Table 4-22 LDAP New

Users Settings Field Description
Parameters
Closed User The Closed User Group associated with the LDAP connection
Group (see Closed User Groups (CUG), page 4-29).
4

4-60 Global Settings Aeonix Administration Manual

 Field Description

User profile A User Profile defined in the Aeonix system (see Defining a
User Profile, page 5-86).

Create mailbox The corresponding password required for accessing the

LDAP server.

Voicemail service The TCP/IP port on which the LDAP server is listening.

NOTE: The default server port for LDAP connections is 389.

12 Click OK to go back to the LDAP Connection page.

13 Click Save to save the LDAP connection. The LDAP connection is included in
the list on the LDAP Connection list page.

 Testing LDAP Connections Parameters

To test definitions of an LDAP connection:

1 On the LDAP Connection List page, click the relevant Connection ID in the
list.
In the LDAP Connection page click Test Definitions.

Figure 4-28 LDAP

Connection Page

LDAP Connections
4

The test results are displayed as shown in the following figure.

Aeonix Administration Manual Global Settings 4-61

 Figure 4-29 LDAP
Connection Test Results
Dialog Box

If the connection to the LDAP server or LDAP attribute mapping failed, one
or more fields defined on the LDAP Connection Page may contain incorrect
values. Make the required corrections and click Test again.

2 Click Export to save the test results as a .CSV file on the local client machine,
or click Back to return to the LDAP Connection page.

 Synchronizing LDAP Connection Parameters

To synchronize definitions of an LDAP connection:

1 On the LDAP Connection List page (see Figure 4-22), click the relevant server
ID from the list. The LDAP Connection page is displayed as shown in the
following figure.
LDAP Connections
4

4-62 Global Settings Aeonix Administration Manual

Figure 4-30 LDAP
Connection page

2 Click Synchronize Now to synchronize the LDAP connection parameters. This

may take a few moments.

LDAP Connections
4

Aeonix Administration Manual Global Settings 4-63

  Default LDAP Directory

Aeonix is configured to connect to the Aeonix LDAP server for the purpose of
retrieving Aeonix directory entry information. The parameters on the Default LDAP
Directory page, as well as other LDAP connection parameters (see Other Provisioning
Parameters, page 7-19), are included as part of the provisioning process, allowing users
of supported provisioned Tadiran SIP phones to conveniently access, search for, and
make calls to contacts in the Aeonix directory.

To view or update the default LDAP directory connection credentials:

1 From the LDAP Connection List page (see Figure 4-22), click the Default
LDAP Directory from the list; the Default LDAP Directory page is displayed.

Figure 4-31 Default LDAP

Directory page

The default LDAP Directory page consists of the following connection parameters:

Table 4-23 Default LDAP

Directory Connection
Parameters
Field Description

Server address The LDAP server address to which LDAP requests are
(Default: 127.0.0.1) sent.

Port (Default: 389) The TCP/IP server port on which the Aeonix LDAP
server is listening.
LDAP Connections

TLS Select for secured Transport Layer Security (TLS)

LDAP connection.

NOTE: The default server port for secured LDAP

connections is 636.
4

4-64 Global Settings Aeonix Administration Manual

 Field Description

User name (Default: The user name required for accessing the Aeonix
cn=Directory Manager) LDAP server.

NOTE: The default value cannot be modified.

Password (default: anx) The corresponding password required for accessing

the Aeonix LDAP server.

NOTE: The default value cannot be modified.

2 Click Save to save any changes you made.

Click Test Definitions if you want to verify the LDAP connection (see Testing
LDAP Connections Parameters, page 4-61).

LDAP Connections
4

Aeonix Administration Manual Global Settings 4-65

LDAP Connections
4

4-66 Global Settings Aeonix Administration Manual

 4.8 Single Sign On

This section describes the Single Sign capability of Aeonix. This feature allows
Aeonix to be deployed in a Kerberos-based secure Active Directory domain.

 Single Sign On

Single Sign On (SSO) is a standard for secure domain environments, in which

authentication is established when the user logs into to the secure domain through an
SSO-managed protocol. When the user is logged in at their workstation, they may
launch authorized applications which do not then present their own login sequences.
The SSO protocol uses LDAP User ID during authentication, and authorized
applications check against that LDAP User ID when launched

 Deployment and Configuration

Assumptions
Your Aeonix Linux server host name: linuxserver
Your Aeonix domain account: linuxuser
Your domain name: example.com
Your realm: EXAMPLE.COM
Active Directory and KDC (Key Distribution Center) server: kdcserver.example.com

Pre-Installation Requirements
Single Sign On

A central part of Kerberos' trusted third party authentication scheme is the Key
Distribution Center (KDC), which is a centralized repository for users' password
information. Before deploying Kerberos, a server must be selected to take on the role
of KDC. Physical and network security will be critical for this server, since a
4

compromised KDC compromises the security of the entire realm.

Aeonix Administration Manual Global Settings 4-67

 Selecting a descriptive name for the Kerberos authentication realm is also important.
Conventionally, the realm names is the site's domain name fully capitalized. For
instance, the site example.com would conventionally use EXAMPLE.COM for its
realm name.

Installation
Join your Aeonix Linux machine into the domain active directory according to the the
instructions given in the section below: How to Join a Linux Server into an Active Directory
Domain on page 4-72.

Active Directory (KDC) Server

1 Aeonix Domain Account
At the active directory server, add a service account (E.g. linuxuser) for your Aeonix
Linux server, which is conceptually very similar to adding a regular domain user
account; except that its password is set to never expire.
2 Register Service Principal Name
Register a Service Principal Names (SPN) directory property for your Aeonix domain
account.
At the active directory server (KDC) server, execute:
C:\Program Files\Support Tools>
setspn -A HTTP/linuxserver.example.com linuxuser
setspn -A HTTP/linuxserver linuxuser
setspn -L linuxuser

3 Host Names
Each (Aeonix) server in a Kerberos authentication realm must be assigned a Fully
Qualified Domain Name (FQDN).
For example, a device with the hostname linuxserver in the parent domain
example.com has the fully qualified domain name linuxserver.example.com
The FQDN must be forward-resolvable and reverse-resolvable.
Single Sign On

Active Directory depends heavily on DNS, so it is likely that the Active

Directory Domain Controller is also running the Microsoft DNS server
package. If this is the case, verify that each server has a FQDN assigned to
it
4

4-68 Global Settings Aeonix Administration Manual

 If the server already has an FQDN assigned to it, test forward and reverse look-up with
the following commands:
$ nslookup linuxserver.example.com
$ nslookup <linuxserver ip address>
The output of the first command should contain the IP address of the server. The
output of the second command should contain the FQDN of the server.
If the server does not already have a FQDN assigned to it and DNS services are not
available, name resolution can be implemented by editing the local hosts file (typically
this is located in /etc/hosts) on each server and client, adding the following line:
127.0.0.1 linuxserver.example.com localhost linuxserver
Test the local DNS name resolution using the nslookup technique described at the
beginning of the section.
4 Check Connectivity
All servers and clients that participate in a Kerberos realm must be able to
communicate with each other.
To verify connectivity between hosts, ping each host's FQDN:
$ ping linuxserver.example.com
PING linuxserver.example.com (10.0.0.1) 56(84) bytes of data.
64 bytes from linuxserver.example.com (10.0.0.1): icmp_seq=1 ttl=128
time=0.176ms
$ ping linuxserver
PING linuxserver (10.0.0.1) 56(84) bytes of data.
64 bytes from linuxserver (10.0.0.1): icmp_seq=1 ttl=128 time=0.176ms
The output of the ping command shows successful resolution of the FQDN to an IP
Address, and a sample reply from the server. A reply from the server serves as
confirmation that the host and the server can communicate.
Connectivity failures while pinging the KDC's FQDN usually point to DNS server or
client configuration errors.

Configuration

Aeonix Linux Server

1 krb5.conf
Single Sign On

Edit the file /home/aeonixadmin/aeonix/webadmin/krb5.conf.

 Replace the EXAMPLE.COM with your domain name and realm.
 Replace the kdcserver.example.com with your active directory server.
4

Aeonix Administration Manual Global Settings 4-69

 [libdefaults]
default_realm = EXAMPLE.COM
default_tkt_enctypes = aes128-cts rc4-hmac des3-cbc-sha1 des-cbc-md5 des-cbc-crc
default_tgs_enctypes = aes128-cts rc4-hmac des3-cbc-sha1 des-cbc-md5 des-cbc-crc
permitted_enctypes = aes128-cts rc4-hmac des3-cbc-sha1 des-cbc-md5 des-cbc-crc

[realms]
EXAMPLE.COM = {
kdc = kdcserver.example.com
default_domain = EXAMPLE.COM
}

[domain_realm]
.EXAMPLE.COM = EXAMPLE.COM

2 login.conf
Edit the file /home/aeonixadmin/aeonix/webadmin/login.conf.
 Replace the linuxuser with your Aeonix domain account user name.

spnego-client {
com.sun.security.auth.module.Krb5LoginModule required;
};

spnego-server {
com.sun.security.auth.module.Krb5LoginModule required
storeKey=true
isInitiator=false
useKeyTab=true
keyTab="/home/aeonixadmin/aeonix/webadmin/anx.keytab"
principal=linuxuser;
};

3 Encrypt Aeonix Domain Account Password

Create key-tab file for your Aeonix domain account (E.g. linuxuser).
At Any PC with JAVA installed, that is logged on to the domain, execute:

C:\Program Files (x86)\Java\jre1.8.0_121\bin>

ktab.exe -a linuxuser linuxuserpassword -k anx.keytab
Single Sign On

ktab.exe -l -k anx.keytab
4

4-70 Global Settings Aeonix Administration Manual

 You should see the pattern: [email protected]
Copy the generated file anx.keytab into your Aeonix Linux server at:
/home/aeonixadmin/aeonix/webadmin

Domain Browsers
All domain clients must configure their browsers to Enable Integrate Windows
Authentication

Internet Explorer or Chrome

 At the Internet Options window, click the Advanced tab and scroll to Security
settings Turn on "Windows Integrated Authentication".
 Make sure that the domain (in our case linuxserver.example.com) is listed in
IE's local intranet site section.

Firefox
 At the desktop, log in to the windows active directory domain and activate
Firefox.
 At the address field, type about:config.
 In the Filter, type network.n
 Double click on network.negotiate-auth.trusted-uris. This preference lists the
sites that are permitted to engage in SPNEGO Authentication with the browser.
Enter a comma-delimited list of trusted domains or URLs.
 Click OK. The configuration appears as updated.
 Restart your Firefox browser to activate this configuration.

Time Synchronization
The Kerberos protocol requires the time of the client and server to match: if the system
clocks of the client does not match that of the server, authentication will fail. The
simplest way to synchronize the system clocks is to use a Network Time Protocol
(NTP) server.

Firewalls
Single Sign On

As with all network services, Kerberos service must be allowed to pass through any
firewalls between hosts.
4

Aeonix Administration Manual Global Settings 4-71

 Aeonix GUI
Enable the Single Sign On option at the "System'System Parameters" web page, as
described in System Parameters on page 14-27.

 How to Join a Linux Server into an Active Directory Domain

Install Prerequisites
[root@AeonixPM2 ~]# yum -y install nss-pam-ldapd sssd_client sssd-client
ypbind nscd krb5-workstation ipa-client mlocate samba

Procedure

Run the authconfig tool on the Linux machine

[root@AeonixPM2 ~]# authconfig-tui

1 Click Next.
Single Sign On
4

4-72 Global Settings Aeonix Administration Manual

 2 On: "IPAv2 Settings", press "Join Domain".

3 Click Yes in the Save Settings panel.

4 Enter an Administrator password and click Ok.

Single Sign On
4

Aeonix Administration Manual Global Settings 4-73

 5 Renter the Administrator password in the CLI:
[/usr/bin/net join -w tadirantele -S tbs-dc01 -U Administrator]
Enter Administrator’s password:
Click Next.

6 On the LDAP Settings panel, enter the name for the LDAP server (Domain
Controller), the Base DN (the domain name). Click Next.
Single Sign On
4

4-74 Global Settings Aeonix Administration Manual

 7 On the Winbind Settings panel click Join Domain.

8 On the Save Settings panel click Yes.

Single Sign On
4

Aeonix Administration Manual Global Settings 4-75

 9 In the Join Settings panel enter the Administrator password.

10 Reenter the Administrator password at the CLI.

[/usr/bin/net join -w tadirantele -S tbs-dc01 -U Administrator]
Enter Administrator’s password:
11 Click Ok.
Joined ‘AEONIXPM2’ to dns domain ‘tadirantele.com’
[/usr/bin/net join -w tadirantele -S tbs-dc01 -U Administrator]
Enter Administrator’s password:
Using short domain name -- TADIRANTELE
Joined ‘AEONIXPM2’ to dns domain ‘tadirantele.com’
Starting nscd: [ OK ]
Starting Winbind services: [ OK ]
Starting nslcd: [ OK ]
[root@AeonixPM2 ~]#
You should now be able to see the machine in Active Directory Users and
Computers:

Check if the server is joined into the AD domain.

1 net ads testjoin
[root@AeonixPM2 ~]# net ads testjoin
Join is OK
[root@AeonixPM2 ~]#
2 If the server was not joined, try to join it manually:
Single Sign On

net ads join -w TADIRANTELE -S tbs-dc01 -U Administrator

4

4-76 Global Settings Aeonix Administration Manual

  Configuring ACC for SSO Environment

In order for Aeonix Call Center to function in a Single Sign On (SSO) environment,
the Domain Controller for the SSO environment must be configured.

General
1 Create general user ACC-SSO-user with password (my is ASU@ANXtestAD).
Set 'password never expires'.
2 Run 'cmd' as administrator (otherwise you'll get error 0x2098/8344 ->
Insufficient access rights to perform the operation.).
3 Execute following command, where 'ACC-SSO/ACCSERVER' is principal
name of ACC service and 'ACC-SSO-user' is user used for ACC:
setspn -A ACC-SSO/ACCSERVER ACC-SSO-user

Generate keytab
1 Linux:
a run ktutil
[root@alishervm3 etc]# ktutil
b Execute following command in ktutil console:
ktutil: addent -password -p ACC-SSO/[email protected] -k 3 -e
arcfour-hmac
where: 'ACC-SSO/[email protected]' is service principal
name in domain ANXTESTAD.COM, '3' - is key version number, 'arcfour-hmac'
is encryption method
c Enter same password as you set for user 'ACC-SSO-user'
Password for ACC-SSO/[email protected]:
d Check that principal was applied
ktutil: l
slot KVNO Principal
---- ---- ----------------------------------------------------------
1 3 ACC-SSO/[email protected]
e Save keytab and exit:
Single Sign On

ktutil: wkt /etc/krb5.keytab.accserver

ktutil: q
4

Aeonix Administration Manual Global Settings 4-77

 f Verify keytab using klist:
[root@alishervm3 etc]# klist -ketK /etc/krb5.keytab.accserver
Keytab name: FILE:/etc/krb5.keytab.accserver
KVNO Timestamp Principal
---- ----------------- ---------------------------------------------
3 02/07/18 15:43:36 ACC-SSO/[email protected] (arcfour-hmac)
(0xb4f8fc659b3435eeb192f55f2d876e97)
2 Domain Controller
a Run 'cmd' as administator (otherwise you'll get error
b Execute following command:
ktpass -princ ACC-SSO/[email protected] -mapuser
[email protected] -crypto RC4-HMAC-NT -ptype
KRB5_NT_PRINCIPAL -pass ASU@ANXtestAD -out
c:\temp\spnego\acc-sso.accserver.keytab

Targeting domain controller: TTL-ADtest.ANXtestAD.com

Using legacy password setting method
Successfully mapped ACC-SSO/ACCSERVER to ACC-SSO-user.
Key created.
Output keytab to c:\temp\spnego\acc-sso.accserver.keytab:
Keytab version: 0x502
keysize 66 ACC-SSO/[email protected] ptype 1 (KRB5_NT_PRINCIPAL)
vno 3 etype 0x17 (RC4-HMAC) keylength 16
(0xb4f8fc659b3435eeb192f55f2d876e97)
3 No matter how you created keytab, copy the result file to ACC server with
name /etc/krb5.keytab

In case this file already exist, and principal names inside this file are needed,
then you may join current file and new file using ktutil

NOTE: In case this file already exist, and principal name inside this file are needed,
then you may join current file and new file using ktutil
ktutil: rkt <keytab1>
ktutil: rkt <keytab2>
ktutil: wkt <target_keytab>
Single Sign On
4

4-78 Global Settings Aeonix Administration Manual

 Single Sign On
4

Aeonix Administration Manual Global Settings 4-79

NOTES:
 Chapter 5

Profiles

5.1 Profiles..................................................................................5-1

5.2 Managing Sub-profiles..........................................................5-3

5.3 Managing Profiles ...............................................................5-83

5.4 Managing Provisioning Profiles ..........................................5-91

Aeonix Administration Manual

 5.1 Profiles

Profiles are sets of parameter values that can be associated with an Aeonix user or
trunk group.

Auto Provisioning profiles are sets of parameter values that can be

associated with Tadiran SIP phones, P-Series phones, and Tadiran TGW
gateways. To learn about defining this type of profile, see Managing
Provisioning Profiles, page 5-91.

When a user or a trunk group is added to the system, the entity is automatically
assigned the values of its profile. If profile values are changed, any entity that is
assigned this profile is modified accordingly.
A profile includes several sub-profiles, each of them specifying values for a set of
parameters. The same sub-profile can be assigned to several profiles. Whether a
sub-profile or its parameter values can be overridden at the user (or trunk group) level
depends on the specific profile configuration. For an example of an Aeonix profile
structure, see Profile Definition Example, page 5-2.

Profile modifications are not implemented for a specific entity if the relevant
sub-profile parameter values have been overridden. To learn about
overriding the profile of a user or a trunk group, see Overriding User Profiles,
page 6-29.

Aeonix provides at least one default profile for each profile and sub-profile type. All
values of a default profile can be modified. Additional profiles of any profile type can
be defined as well; however, default profiles cannot be deleted.
Profiles are managed from the Profiles tab area under the Settings menu of the Aeonix
Web Portal. Managing profiles includes the following procedures:
Profiles

 Managing Sub-profiles, page 5-3

 Managing Profiles, page 5-83
Managing Provisioning Profiles, page 5-91
5

Aeonix Administration Manual Profiles 5-1

  Profile Definition Example

The following table provides a model example of the user profiles and sub-profiles
defined in an Aeonix system, how they are related, and whether sub-profiles can be
overridden for specific users.

Table 5-1 Profile User profile Manager Sales R&D

Definition Example
Sub-profiles

General Info Default General Default General Default General

Override allowed Override allowed Override allowed

Timeout Manager Timeout Sales Timeout R_D Timeout

Override allowed Override allowed Override allowed

Toll barrier Manager Toll Barrier Sales Toll Barrier R_D Toll Barrier
Override allowed Override not allowed Override not allowed

Phone Default profiles Default profiles Default profiles

Override allowed Override allowed Override allowed

Schedule Default Schedule Default Schedule Default Schedule

Override allowed Override not allowed Override not allowed

Incoming Manager Incoming Sales Incoming R_D Incoming Call

Call Routing Call Routing Call Routing Routing
Override allowed Override allowed Override allowed

Outgoing Manager Outgoing Default Outgoing Default Outgoing

Call Routing Call Routing Call Routing Call Routing
Override allowed Override not allowed Override not allowed

Feature Manager Features Sales Features R_D Features

Config Override allowed Override allowed Override allowed

Overriding sub-profiles at the entity level is described in Overriding User Profiles,

page 6-29.
Profiles
5

5-2 Profiles Aeonix Administration Manual

 5.2 Managing Sub-profiles

A sub-profile specifies the values for a set of content-related parameters. The

sub-profile types available are: General Information; Timeouts; Toll Barrier;
Schedule; Incoming Call Routing; Outgoing Call Routing; Feature Configuration;
Administration Level and phone profiles for MGCP phones (FlexSet-IP 280S, T207M,
T208M, T207M/NP, T208M/BL), SIP phones (Tadiran SIP phones and P-Series
phones), and digital phones (FlexSet 120, 120D, 120L, 120S, 121S, 280, 280D,
280D-HS, 280S, 281S, DKT, CPA and DST connected through a Wave Gateway).
For each type, multiple sub-profiles can be created in addition to the predefined
default sub-profiles. Sub-profiles can be updated whenever required.

When defining a sub-profile, either leave the default values in the text fields
or change these values. If a sub-profile text field is empty, the sub-profile
cannot be saved.

A profile includes one sub-profile of each type. (Incoming Call Routing, Outgoing
Call Routing, Feature Configuration, and Administration Level sub-profiles, as well
as phone profiles, are not used in trunk group profiles.) By default, this is a predefined
sub-profile, but it can be replaced. Profiles are described in detail in Managing Profiles,
page 5-83.

Aeonix users and trunk groups have the sub-profiles of their profiles
indicated on their pages (under the Profile tab). To learn about managing
profiles at the entity level, see Overriding User Profiles, page 6-29.
Managing Sub-profiles
5

Aeonix Administration Manual Profiles 5-3

 Sub-profiles are managed from their List pages as described in Profile List Page for
Sub-profiles. The following sections describe how to configure sub-profiles:
 General Information Sub-profiles, page 5-8
 Timeout Sub-profiles, page 5-12
 Feature Configuration Sub-profiles, page 5-15
 Toll Barrier Sub-profiles, page 5-24
 Schedule Sub-profiles, page 5-28
 Incoming Call Routing Sub-profiles, page 5-31
 Outgoing Call Routing Sub-profiles, page 5-41
 Administration Level Sub-profiles, page 5-49
 Phone Profiles, page 5-54
Managing Sub-profiles
5

5-4 Profiles Aeonix Administration Manual

  Profile List Page for Sub-profiles

A Profile List page is available for each sub-profile type. It displays the available
sub-profiles of the relevant type.

To open a Profile List page of a specific sub-profile type:

1 On the navigation pane, click Settings. The pane displays the Settings menus.
2 Select the Profiles menu, and then click Sub-profiles. The available
sub-profile types are listed on the navigation pane.
3 Click the relevant sub-profile type. Its Profiles page is displayed, as the
General Information Profiles page in the figure below.

Figure 5-1 Profiles Page

for General Information
Sub-profiles

The sub-profile list is sorted by the Name column. If the list includes more
than one page, use the page navigation bar at the bottom of the list to
navigate between the pages.

Managing Sub-profiles
5

Aeonix Administration Manual Profiles 5-5

 For each sub-profile, the Profile List page displays some of the following information.

Table 5-2 Profile List

Parameters for Column Description
Sub-profiles
Name The name of the sub-profile

Description An optional description of the sub-profile

Type The profile type (user or trunk group)

CUG The Closed User Group associated with the sub-profile

(see Closed User Groups (CUG), page 4-29)

Language The language for users who are applied the sub-profile
(General Information (for details, see Table 5-4 on page 5-10)
sub-profiles only)

Location The location the sub-profile assigns to users, if any

(General Information (see Locations, page 4-9)
sub-profiles only)

Type The phone type to which the phone profile applies

(phone profiles only)

Local Display The text displayed on the panel of the phone if their
(phone profiles only) users are applied the phone profile

Routing Table Name The ARS table the sub-profile uses to route the calls
(Outgoing Call Routing (see Automatic Route Selection (ARS), page 4-43)
sub-profiles only)
Managing Sub-profiles
5

5-6 Profiles Aeonix Administration Manual

 From this page, you can perform the following actions:

Table 5-3 Actions

Performed from a Profile Action Button / Icon Description
List Page for Sub-profiles
Add Click Add to add a new sub-profile.
sub-profile For a description of the procedure, see the section
relating to the relevant sub-profile type:
 General Information Sub-profiles, page 5-8
 Timeout Sub-profiles, page 5-12
 Feature Configuration Sub-profiles, page 5-15
 Toll Barrier Sub-profiles, page 5-24
 Schedule Sub-profiles, page 5-28
 Incoming Call Routing Sub-profiles, page 5-31
 Outgoing Call Routing Sub-profiles, page 5-41
 Phone Profiles, page 5-54

Update In the list, click the sub-profile name to update the

—
sub-profile details of this sub-profile.
Delete Select the check box next to one or more
sub-profile sub-profiles to be deleted and then click Delete
(see Deleting Entities, page 3-66).

NOTE: Sub-profiles assigned to a profile, user, or

trunk group cannot be deleted.
Access Click Help to receive online help.
online help

Clone Click this icon to create a duplicate of a specific

sub-profile sub-profile.

Managing Sub-profiles
5

Aeonix Administration Manual Profiles 5-7

  General Information Sub-profiles

General Information sub-profiles are defined similarly for user profiles and for trunk
group profiles, although some parameters are not used in trunk groups.

Changing the “Required Security Level” is not allowed in an A4C instance.

To add or update a General Information sub-profile:

1 At the bottom of the navigation pane, click Settings. The pane displays the
Settings menus.
2 Select the Profiles menu, and then click Sub-profiles. The available
sub-profile types are listed on the navigation pane.
3 Click General Information. The existing General Information sub-profiles are
listed on the General Information Profile List page (Figure 5-1).
4 Do one of the following:
 To create a sub-profile, click Add and then select the required profile type
(user or trunk group).
 To update an existing sub-profile, select it from the list.
 To create a new sub-profile based on the settings of an existing one, click
(the Clone icon) to the right of the relevant sub-profile.

When you clone a sub-profile, all parameter values are copied to the new
sub-profile except for the sub-profile name and the Closed User Group.
Managing Sub-profiles
5

5-8 Profiles Aeonix Administration Manual

 The relevant General Information Profile page is displayed.

Figure 5-2 Profile Page

for a New General
Information Sub-profile

5 Set the sub-profile identity parameters:

a If this is a new sub-profile, enter a name in the Name box.
b In the Description box, enter a description of the sub-profile (optional).

The Name and the Closed User Group of an existing sub-profile cannot be
modified.

6 Set or view the sub-profile’s parameters as described in the following table.

Managing Sub-profiles

Location is the only relevant and displayed parameter for trunk groups.
5

Aeonix Administration Manual Profiles 5-9

 Table 5-4 General
Information Parameters Field Description

Language The language (English, Hebrew, Russian, Chinese) used

for:
 The text displayed on the user’s Tadiran SIP phone
LCD screen
 The language of the user’s Tadiran SIP phone web
portal
 The default language of the user’s Aeonix Web Portal
(see Login Page, page 3-9)
 The language of announcers played to the user
(currently, English and Chinese come pre-installed)

NOTE: Hebrew is not supported in the portals (English is

used instead when this language is selected).

Always use dial rules If selected, the system automatically applies the dial rules
of this location defined for the location selected below.

Location The location of the user (see Locations, page 4-9)

NOTE: Also applicable for trunk groups.

Date format The format in which dates are displayed for the user in
the Aeonix Web Portal.
The date format syntax uses M for month, d for day,
and y for year. The number of times the digits are
repeated determines the length of the entry. To illustrate,
the fifth day of 2013 will be displayed as follows in the
formats available by default:
 M/d/yy—1/5/13
 M/d/yyyy—1/5/2013
 MM/dd/yy—01/05/13
 MM/dd/yyyy—01/05/2013
 yy/MM/dd—13/01/05
 yyyy/MM/dd—2013/01/05
 dd/MMM/yy—05/Jan/13
 dd/MMM/yyyy—05/Jan/2013
 d/M/yy—5/1/13
 d/M/yyyy—5/1/2013
Managing Sub-profiles

The available date formats are defined in the System

Parameters table (see System Parameters, page 14-27).

Date separator The character used for separating the date units.
To illustrate, if - (dash) is selected, the example above will
be displayed as 05-Jan-13 for date format dd/MMM/yy.
The available separators are defined in the System
Parameters table (see System Parameters, page 14-27).
5

5-10 Profiles Aeonix Administration Manual

 Field Description

Time format The format in which the time is displayed for the user:
 A.M / P.M.—the time is displayed in 12-hours format
and followed by AM for hours before noon, or by PM for
hours after noon.
 24H—the time is displayed in 24-hours format.

Required security The signaling and media security level for the user:
level  Unencrypted—Aeonix uses TCP or UDP only for the
signaling session (not TLS) and uses RTP for the
media (not SRTP).
 Best Effort—Aeonix attempts to establish TLS
signaling and can revert to TCP or UDP if the endpoint
does not support it.

NOTE: Bria and SeaBeam softphones cannot work in Best

Effort mode if they are configured to TLS/SRTP.

User License The user license type for the user that, when used in
conjunction with the relevant device licenses (see
Table 3-7page 3-36), allows users to log into their devices.
 Advanced Aeonix user—allows a user to operate up
to six devices (default option).

NOTE: Authorization must also be set In order to use

Aeonix Touch softphone (see Enable Aeonix Touch).
 Aeonix gateway user—allows a user to operate one
device that is connected to an Aeonix gateway.

NOTE: Making changes to this setting will cause these

users to be logged out of all of their devices. In this
event, any ongoing calls will be disconnected.

7 Click Save. The sub-profile is included in the list on the General Information
Profile List page.

Managing Sub-profiles
5

Aeonix Administration Manual Profiles 5-11

  Timeout Sub-profiles

Timeout sub-profiles are defined similarly for user profiles and for trunk group
profiles.

To add or update a Timeout sub-profile:

1 At the bottom of the navigation pane, click Settings. The pane displays the
Settings menus.
2 Select the Profiles menu, and then click Sub-profiles. The available
sub-profile types are listed on the navigation pane.
3 Click Timeouts. The existing Timeout sub-profiles are listed on the Timeout
Profiles page.

Figure 5-3 Timeout

Profiles Page

4 Do one of the following:

 To create a sub-profile, click Add.
 To update an existing sub-profile, select it from the list.
 To create a new sub-profile based on the settings of an existing one, click
(the Clone icon) to the right of the relevant sub-profile.

When you clone a sub-profile, all parameter values are copied to the new
sub-profile except for the sub-profile name and the Closed User Group.
Managing Sub-profiles
5

5-12 Profiles Aeonix Administration Manual

 The relevant Timeout Profile page is displayed.

Figure 5-4 Timeout

Profile Page for a New
Sub-profile

5 Set the sub-profile identity parameters:

a If this is a new sub-profile, enter a name in the Name box.
b In the Description box, enter a description of the sub-profile (optional).

The Name of an existing sub-profile cannot be modified.

6 Set or view the sub-profile’s parameters as described in the following table.

Table 5-5 Timeout

Parameters Field Description

Dial tone timeout Number of seconds the dial tone is heard before the
system disconnects for internal calls

Interdigit timeout For internal calls, the number of seconds allowed

between pressing digit keys before the system tries to
establish the call

Managing Sub-profiles
Reorder timeout  During a call, the number of seconds a reorder tone
is heard before a call is disconnected.
 When activating or deactivating a feature from the
phone, the number of seconds a confirmation tone is
heard before the feature is activated or deactivated.

Busy timeout When a call is made to a busy destination, the number

of seconds a busy tone is heard before the call is
disconnected. This tone is only heard if the destination
5

has call waiting disabled.

Aeonix Administration Manual Profiles 5-13

 Field Description

Recall on hold timeout When a caller is put on hold, the number of seconds
(MGCP phones only) after which the phone rings again for this call. Not
supported as an Aeonix feature on SIP phones, but can
be set as a feature of the phone firmware and URL
interface -- however it is not supported in provisioning.

Recall on transfer When a call is transferred to a destination that does not

timeout answer, the number of seconds after which the call is
recalled back to the device of the user (if less than the
Ring timeout above)

Ringback timeout Number of seconds a ringing signal is heard for an

(read-only) outgoing call before the call is disconnected

7 Click Save. The sub-profile is included in the list on the Timeout Profile List
page.
Managing Sub-profiles
5

5-14 Profiles Aeonix Administration Manual

  Feature Configuration Sub-profiles

Feature Configuration sub-profiles are assigned to user profiles only and define the
way the following Aeonix features are applied to users:
 Call Waiting
 Call Time Limit for External Calls
 Auto Answer
 Voice Page
 Callback and Call-through (Mobility)
 ANI Restriction
 Exclusive Hold (for ULA)
 Call Pickup
 Client Applications (Aeonix Touch and Sea Navigator / Sea Attendant)
 Recall (on Transfer)
 ESF for Tadiran SIP Phones
 Auto Redial
 Flash Mode
 Instant Messages
 LDAP Single Sign-on Allowed Applications
 Permissions by User Level
For a description of these features, see Chapter 2, Aeonix Features.

To add or update a Feature Configuration sub-profile:

1 On the navigation pane, click Settings. The pane displays the Settings menus.
2 Select the Profiles menu, and then click Sub-profiles. The available
sub-profile types are listed on the navigation pane.
3 Click Feature Configuration. The existing Feature Configuration sub-profiles Managing Sub-profiles
are listed on the Feature Configuration Profiles page.

Figure 5-5 Feature

Configuration Profiles
Page
5

Aeonix Administration Manual Profiles 5-15

 4 Do one of the following:
 To create a sub-profile, click Add.
 To update an existing sub-profile, select it from the list.
 To create a new sub-profile based on the settings of an existing one, click
(the Clone icon) to the right of the relevant sub-profile.

When you clone a sub-profile, all parameter values are copied to the new
sub-profile except for the sub-profile name and the Closed User Group.

The relevant Feature Configuration Profile page is displayed.

Figure 5-6 Feature

Configuration Profile
Page for a New
Sub-profile

5 Set the sub-profile identity parameters:

a If this is a new sub-profile, enter a name in the Name box.
b In the Description box, enter a description of the sub-profile (optional).

The Name of an existing sub-profile cannot be modified.

Managing Sub-profiles

6 Click one or more features to display the parameters of these features. (Click
Toggle Panels to display hidden and hide displayed parameters).
7 Set or view the sub-profile parameters as described in the following table.
5

5-16 Profiles Aeonix Administration Manual

Table 5-6 Feature
Parameters Feature Field Description

Call Waiting Allow call Allows call waiting for both internal and external
waiting calls. When receiving a call during a phone
conversation, the user hears a call waiting tone
and can put the ongoing call on hold to answer
the call.
If not selected, call waiting is disabled for calls.
Calls are rejected if the user is on the phone,
and the caller hears a busy tone.

NOTE: This parameter must be disabled for

contact center agents.

NOTE: FlexSet-IP 280S Version 3.26 or higher,

when this feature is selected, receives a
call waiting tone ONLY via the handset.
The tone is not sounded via the
loudspeaker in handsfree mode, but the
user sees the calling party number on the
keyset display.

Disable call If selected, users of MGCP and Wave Gateway

waiting tone FlexSet phones will not hear a Call Waiting tone
on MGCP & during an ongoing call when there is another
FlexSet incoming call to this user.

Limit number If selected, Aeonix places a limit on the number

of waiting calls of waiting calls allowed for this device, as
specified by the number entered in the adjacent
text box. This check box is clear by default (an
unlimited number of waiting calls is allowed).

Internal call If selected, during transfer of calls (internal or

and/or external) to a busy phone, Aeonix ignores the
External call destination’s Enable Call Waiting setting.

NOTE: When the transferring party is using a SIP

phone, this feature is supported for single
step transfers.

Auto Allow auto Activates auto answer on the user’s phones. Managing Sub-profiles
Answer answer Auto answer picks up the phone in
speakerphone mode.

NOTE: Auto answer can only be used on

supported phones.
5

Aeonix Administration Manual Profiles 5-17

 Feature Field Description

After...seconds Defines the amount of time after which a ringing

phone enters auto answer mode.

NOTE: This field is only enabled if Allow auto

answer is selected.

Call Time Call time limit Activates the Call Time Limit feature. This limits
Limit for the number of minutes a user can run an
External external outbound or transit call.
Calls
After...minutes Enter the number of minutes after which the call
will be disconnected.

Play warning Enter the number of seconds before

tone...seconds disconnecting the call when a warning tone will
before be played.
disconnecting
the call

Voice Page Accept voice Allows the user’s phones to accept voice page
page calls. If this check box is cleared, an incoming
voice page call is considered as a regular call
and handled accordingly.

NOTE: Voice page calls can only be placed to

supported phones.
Calls to unsupported phone types are
automatically converted into regular calls.

Answer The amount of time during which a voice page

after...seconds call rings before it is established via the
speakerphone of the called phone.

NOTE: This field is only enabled if Accept voice

page is selected, and is relevant for voice
page calls to supported phones.

Mute Turns off the microphone of the voice page

microphone destination user, so that the paging caller can
hear the paged user only after this user picks up
Managing Sub-profiles

the phone or presses the Speaker button.

This check box is selected by default.

NOTE: This field is only enabled if Accept voice

page is selected, and is only available on
supported phones.
5

5-18 Profiles Aeonix Administration Manual

 Feature Field Description

Callback ANI Mobility allows external users to place calls just

and Call Presentation as if they were in the office. ANI presentation
Through determines whether the Internal number (the
(Mobility) alias) or the External number (the ANI) of the
calling user will be displayed to the receiver of
the call.
If the receiver of the call is an external
destination, the Internal number will include the
office number of the calling user.

ANI Restrict Select to restrict the receiver of the call from

Restriction identity viewing the caller’s ANI.
presentation

Exclusive Exclusive hold If selected, only the user who put a ULA call on
Hold hold can retrieve the held call.
If not selected, a held ULA call can be retrieved
by the ULA group owner or by any member of
the group.

Pickup Allow direct Select to allow users to pick up calls of other

pickup users in the system (see Defining Permission
Settings, page 6-74).

Pressing on a Specifies the action to perform when a blinking

blinking speed Speed dialing button is pressed:
dial performs  No action
 Direct pickup
 Group pickup

Client Sea Navigator Specifies whether a user can use the

Applications or Sea Navigator or Sea Attendant application.
Sea Attendant
allowed NOTE: If the number of users allowed to use the
application exceeds the available
licenses, the user entry is not saved and a
relevant note is displayed on the License
Information page (see Figure 3-15 on
page 3-35). Managing Sub-profiles

Enable Aeonix Specifies whether a user can use the Aeonix

Touch Touch desktop softphone application.

NOTE: No authorization is required to use Aeonix

Touch desktop softphone in Control
mode.
5

Aeonix Administration Manual Profiles 5-19

 Feature Field Description

Recall Internal call Allows transferred calls (internal or external

and/or numbers) that are not answered to be recalled
External call back to the user who initiated the transfer,
according to the user’s set Recall on Transfer
timer (see Recall on transfer timeout, page 5-14).
When a call is recalled, the call display of the
transferor specifies the reason for the recall (not
applicable for SLT and SIP phones).

NOTE: Calls are recalled even when users are in

DND mode.

ESF for Phone ESF Allows Enhanced SIP Functionality (ESF) on

Tadiran SIP password Tadiran SIP Phones with programmable buttons
Phones based on the phone’s default Admin password.
In order to change the phone’s administrator
password, enter the password in the adjacent
Phone ESF password text box.

ESF protocol In order to change to secured communications

between the ESF server and the Tadiran SIP
phones, select HTTPS for ESF protocol.

NOTE: Selecting HTTPS may adversely affect

phone LED indicators, causing delays in
some cases.

Auto Redial Maximum Defines the maximum number of redial attempts

redial attempts (15 by default).

NOTE: Auto Redial can only be used on

supported phones.

If busy, redial Defines the amount of time after which a redial

after...seconds attempt is made to the busy external destination
(60 seconds by default).

If no answer, Defines the amount of time after which a redial

redial attempt is made to the non-answering or call
after...seconds waiting external destination (180 seconds by
Managing Sub-profiles

default).

Flash Mode Continuous Specifies the default flash mode when defining a
conference or Flash Transfer programmable button (see Flash
Swap or mode, page 5-68).
Consultation
5

5-20 Profiles Aeonix Administration Manual

 Feature Field Description

Instant Send instant Allows users to receive instant messages to

Messages messages to their supporting Tadiran SIP phones.
Tadiran SIP
phones

LDAP Aeonix Use the checkboxes to enable user access for

Single Contact Aeonix components in Single Sign-On mode.
Sign-On Center Agent
Allowed
Applications Aeonix
Contact
Center
Supervisor

Aeonix
Administration

Seamail

Permission Enable Sets users of the profile to operate in

by User permission by Permission by User Level mode. In this mode,
Level user level Aeonix uses the assigned User Level (see
below) to decide which users have invasive
permission to Break-In, Break-Out, or Silent
Monitor against a target destination. The
following rules are followed in the permission
evaluation:
 The Permission List (see Defining Permission
Settings, page 6-74) has priority.
 If the action is permitted by the Permission
List evaluation, it is performed.
 If not, and the user has the Permission by
User Level feature enable, the value of the
permission levels of the initiator and the
target are compared.
 User Level 0 is assumed for users who do
not have the feature enabled.
 If the User Level of the initiator is higher than
that of the target, the action is performed. Managing Sub-profiles

User level Sets the User Level in the profile. User Level
can be 0 - 255. 0 is the default. Higher values
represent users with greater permission to
perform invasive operations.
5

Aeonix Administration Manual Profiles 5-21

 Feature Field Description

Permanent Permanent NOTE: CP860 IP conference phone is the

Connect for connect Tadiran certified device for Room
Room Recording. Contact your Aeonix
Recording representative for details.
Select to set the room recording device with a
permanent connection. This check box is clear
by default. Ensure that the device has been
defined with the required BRE recording rule
(see Defining a Call Recording Rule, page 12-28).

NOTE: In order to avoid call waiting tone

interruptions during recordings, it is
recommended to clear Allow call waiting
above.

NOTE: Ensure that the Session-Expires Time for the

room recording device is set to 90
seconds. The Session Timer parameter
should also be set on the device side (in
the Account, Advance tab).

NOTE: It is recommended to leave the Minimum

Session-Expires with the default value (90
seconds) to prevent the room recording
device from staying connected after an
Aeonix system restart. The Session
Expires parameter should also be set on
the device side (in the Account, Advance
tab).
Aeonix will place a call to the user’s default
alias, ignoring all blocking features including
incoming rules, DND, and Forward in order to
maintain a continuous connection with the
device for Room Recording purposes.

NOTE: In the event the call gets disconnected,

Aeonix will reestablish the call.
Managing Sub-profiles
5

5-22 Profiles Aeonix Administration Manual

 Feature Field Description

Renew after Ensure that the check box is selected;

otherwise, the recording file will have no size
limit.
In the adjacent box, it is recommended to leave
the default value (60 minutes) in order to keep
the size of recording files to a minimal.

NOTE: This field is only enabled if Allow auto

answer is selected.

NOTE: When using 2 Aeonix Logger trunks (one

active and the other passive), this timeout
must be smaller than the trunk Keep-alive
timeout value in order to allow the passive
Aeonix Logger to complete the recording
without losing any information.

8 Click Save. The sub-profile is included in the list on the Feature Configuration
Profile List page.

Managing Sub-profiles
5

Aeonix Administration Manual Profiles 5-23

  Toll Barrier Sub-profiles

Toll Barrier sub-profiles are defined similarly for user profiles and for trunk group
profiles. These parameters define call numbers and destinations that are blocked for
outgoing calls and call forwarding. Toll barrier restrictions also apply to calls
manipulated by Outgoing Call Routing rules (see Outgoing Call Routing Sub-profiles,
page 5-41).

Toll barrier restrictions are not applied to emergency (911) calls.

For an example of a Toll Barrier sub-profile, see Toll Barrier Sub-profile Example,
page 5-26.

To add or update a Toll Barrier sub-profile:

1 On the navigation pane, click Settings. The pane displays the Settings menus.
2 Select the Profiles menu, and then click Sub-profiles. The available
sub-profile types are listed on the navigation pane.
3 Click Toll Barrier. The existing Toll Barrier sub-profiles are listed on the Toll
Barrier Profiles page.

Figure 5-7 Toll Barrier

Profiles Page

4 Do one of the following:

 To create a sub-profile, click Add.
 To update an existing sub-profile, select it from the list.
Managing Sub-profiles

 To create a new sub-profile based on the settings of an existing one, click

(the Clone icon) to the right of the relevant sub-profile.

When you clone a sub-profile, all parameter values are copied to the new
sub-profile except for the sub-profile name and the Closed User Group.
5

The relevant Toll Barrier Profile page is displayed.

5-24 Profiles Aeonix Administration Manual

Figure 5-8 Toll Barrier
Profile Page for a New
Sub-profile

You can use the Search box to textually search for and display specific items
in the list.

5 Set the sub-profile identity parameters:

a If this is a new sub-profile, enter a name in the Name box.
b In the Description box, enter a description of the sub-profile (optional).

The Name of an existing sub-profile cannot be modified.

Managing Sub-profiles
6 From the Basic behavior drop-down list, select one of the following:
 Allow all calls to allow users to make outgoing calls to any destination
except for the destinations defined in the Do not allow calls to box below.
 Reject all calls to prevent users from making outgoing calls to any
destination except for the destinations defined in the Allow calls to box
below.
5

Aeonix Administration Manual Profiles 5-25

 If Basic behavior is set to Reject all calls, the Do not allow calls to box is
not displayed. In this case, skip the following step and continue with Step 8.

7 Use the Allow calls to box to define numbering patterns (partial or complete
phone numbers) of the destinations that users are allowed to call.
Add new, update, or remove patterns as required:
 To add a pattern, click Add, enter the number in the displayed Pattern box,
and click OK.
In the United States, for example, you can enter 1900XXXXXXX to
prevent users from making premium rate phone calls.
 To update a pattern, select it and click Update. Modify the number that is
displayed in the Pattern box and click OK.
 To delete a pattern, select it and click Delete. You can select more than one
pattern for deletion by using the CTRL and SHIFT keys.

Patterns must be composed of numbers only. Use the X wildcard to

represent any digit.

8 Use the Do not allow calls to box to define numbers and numbering patterns
of destinations that users are not allowed to call, regardless of the value in the
Basic behavior field and the entries in the Do not allow calls to box (if
available). Add new, update, or remove patterns as described in the previous
step.
9 To override the Direct incoming calls to external destinations parameter,
which blocks users from redirecting incoming calls to external destinations,
select Allow (the default option is Restrict.)
10 Click Save. The sub-profile is included in the list on the Toll Barrier Profile
List page.
Managing Sub-profiles

Toll Barrier Sub-profile Example

The following figure shows a (fictive) toll barrier definition that prevents users in the
United States from calling abroad except for calling a British business partner.
5

5-26 Profiles Aeonix Administration Manual

Figure 5-9 Toll Barrier
Sub-profile Example

Managing Sub-profiles
5

Aeonix Administration Manual Profiles 5-27

  Schedule Sub-profiles

This section describes how to set up a Schedule sub-profile. To learn about

how to include defined schedules and time frames in call forwarding rules,
see Incoming Call Routing Sub-profiles, page 5-31.

Just as global schedules (see Schedules, page 4-37), schedules defined in a Schedule
sub-profile are used for defining advanced call forwarding and rejection rules in
Incoming Call Routing sub-profiles.
However, in contrast to global schedules, the schedules and time frames of a Schedule
sub-profile can be a component of a user’s call forwarding rules only if this sub-profile
is included in the user profile associated with this user.

To add or update a Schedule sub-profile:

1 On the navigation pane, click Settings. The pane displays the Settings menus.
2 Select the Profiles menu, and then click Sub-profiles. The available
sub-profile types are listed on the navigation pane.
3 Click Schedule. The existing Schedule sub-profiles are listed on the Schedule
Profiles page.

Figure 5-10 Schedule

Profiles Page

4 Do one of the following:

 To create a sub-profile, click Add.
 To update an existing sub-profile, select it from the list.
Managing Sub-profiles

 To create a new sub-profile based on the settings of an existing one, click

(the Clone icon) to the right of the relevant sub-profile.

When you clone a sub-profile, all parameter values are copied to the new
sub-profile except for the sub-profile name and the Closed User Group.
5

The Schedule Profile page is displayed.

5-28 Profiles Aeonix Administration Manual

Figure 5-11 Schedule
Profile Page for a New
Schedule Sub-profile

5 Set the sub-profile identity parameters:

a If this is a new sub-profile, enter a name in the Name box.
b In the Description box, enter a description of the sub-profile (optional).

The Name of an existing sub-profile cannot be modified.

6 To add a new schedule to the sub-profile:

a In the Schedule List area, click Add. The Schedule page is displayed.
b Enter a name in the Name box.
c In the Time Frame List, configure the time frames (see Defining a Time
Frame, page 4-39).
d Click OK.
7 To update a schedule of the sub-profile:
a In the Schedule List, click the name of the schedule. The Schedule page is
displayed.
b In the Time Frame List, configure the time frames (see Defining a Time
Frame, page 4-39).
c Click OK. Managing Sub-profiles

8 To add a copy of a global schedule to the sub-profile:

a In the Schedule List, click Import. The Schedule page displays a list of the
available global schedules.
b Select the check boxes next to the relevant schedule or schedules and click
Select.
5

Aeonix Administration Manual Profiles 5-29

 9 To delete a schedule from the sub-profile:
a On the Schedule Profile page, select the check boxes left of the relevant
schedule or schedules in the Schedule List.
b Click Delete. A confirmation message is displayed.
c Click Yes to delete the schedule or schedules.
10 Click Save. The sub-profile is displayed on the Schedule Profile List page.
Managing Sub-profiles
5

5-30 Profiles Aeonix Administration Manual

  Incoming Call Routing Sub-profiles

Incoming Call Routing sub-profiles are assigned to user profiles only. They define to
which devices incoming calls are routed and allow the forwarding or rejection of calls
upon a combination of conditions. Possible conditions include the result of the call,
the availability of the called user, the number of the caller, as well as the date,
weekday, or time the call was placed.
The routing conditions and call forwarding destinations are defined using rules. These
rules can be of the following types:
 Mandatory—high priority rules. These rules are defined in the sub-profile and
cannot be overridden at the user level.
 Optional—sub-profile rules that can be overridden at the user level
 User’s rules—rules that are defined for a specific user. These rules are only
set at the user level and override the optional rules (see Overriding Incoming Call
Routing Rules, page 6-40).
You can define basic and advanced incoming call routing rules. Basic rules are applied
to all incoming calls regardless of the caller. Advanced rules forward or reject calls
according to caller, user presence, and timing conditions. The priorities of the rules can
be configured as well.

Calls are not forwarded if the specified forward destination or destinations

are restricted by the user’s toll barrier settings (see Toll Barrier Sub-profiles,
page 5-24).

To add or update an Incoming Call Routing sub-profile:

1 On the navigation pane, click Settings. The pane displays the Settings menus.
2 Select the Profiles menu, and then click Sub-profiles. The available
sub-profile types are listed on the navigation pane.
3 Click Incoming Call Routing. The existing Incoming Call Routing Managing Sub-profiles
sub-profiles are listed on the Incoming Call Routing Profiles page.

Figure 5-12 Incoming

Call Routing Profiles
Page
5

Aeonix Administration Manual Profiles 5-31

 4 Do one of the following:
 To create a sub-profile, click Add.
 To update an existing sub-profile, select it from the list.
 To clone a new sub-profile based on the settings of an existing one, click
(the Clone icon) to the right of the relevant sub-profile.

When you clone a sub-profile, all parameter values are copied to the new
sub-profile except for the sub-profile name and the Closed User Group.

The relevant Incoming Call Routing Profile page is displayed.

Figure 5-13 Incoming

Call Routing Profile Page
for a New Sub-profile

5 Set the sub-profile identity parameters:

a If this is a new sub-profile, enter a name in the Name box.
Managing Sub-profiles

b In the Description box, enter a description of the sub-profile (optional).

The Name of an existing sub-profile cannot be modified.

6 Define basic call routing rules as required (see Defining Basic Rules for Incoming
5

Call Routing, page 5-33).

5-32 Profiles Aeonix Administration Manual

 7 Optionally define advanced call routing rules (see Defining Advanced Rules for
Incoming Call Routing, page 5-35).
8 Click Save. The sub-profile is displayed on the Incoming Call Routing List
page.

Defining Basic Rules for Incoming Call Routing

An Incoming Call Routing sub-profile’s basic rules are applied to all incoming calls
for the users associated with this sub-profile. Only one basic rule can be defined for
each call forwarding condition.

To learn about advanced incoming call routing rules, see Defining Advanced
Rules for Incoming Call Routing, page 5-35.

The basic rules are defined on the Incoming Call Routing Profile page of the relevant
sub-profile (see Figure 5-13). The following basic rules are available:
 Forward on busy—forwards calls when the phone line is busy. This rule does
not apply if call waiting is activated (see Call Waiting (Multi-appearance),
page 2-14).
 Forward all—forwards all calls
 Forward on DND—forwards or rejects calls when the user’s presence status
is DND (see the User Guide of the relevant telephone)
 On logout—forwards calls, or routes calls to the members of the user’s ULA
group, if the user is logged out from all internal devices assigned to this user
and has no external phone number defined
 Ring on—specifies whether incoming calls ring on a user’s internal phone,
external phones, and/or devices of members belonging to the user’s owned
ULA group. An incoming call rings (or is indicated) on all selected devices
and stops ringing when the call is answered.
If an incoming call is not answered within a specified time period, it is Managing Sub-profiles
forwarded to another user or number (external number or Coral extension), or
rejected. This rule also applies to call waiting when callers put on hold are not
answered.

To set up a basic rule:

1 Select the Enable check box to activate the rule.
5

If this check box is not selected, the rule is temporarily disabled.

Aeonix Administration Manual Profiles 5-33

 2 To prevent the rule from being overridden at the user level, select Mandatory.
Mandatory rules are always applied first.
If this check box is not selected, the rule is optional.
3 Specify the rule parameters as follows:

Table 5-7 Rule

Parameters Rules Fields

Forward on busy Call forward destination: Next to the rule, select User and
Forward all enter the relevant user, or select Number and enter the
Forward on DND number of an external destination, a group, a service, or a
connected Coral extension.
For DND rules, you can also select Reject to reject incoming
calls and disconnect the callers.

NOTE: An external destination cannot be selected if the Direct

incoming calls to external destinations parameter
has been set to Restrict (see Toll Barrier Sub-profiles,
page 5-24Toll Barrier Sub-profiles).

On logout Select either of the following:

 Forward to—select User and enter the relevant user, or
select Number and enter the number of an external
destination, a group, a service, or a connected Coral
extension
 Ring on ULA—select to have incoming calls routed to the
members of the user’s ULA group. This option is only
relevant if the user is a ULA group owner.

Ring on Next to the rule, select whether incoming calls are to be

routed to the user’s internal devices, external phones, and/or
to the members of the user’s ULA group.
 If no answer after...seconds: Specify the number of
seconds after which calls are forwarded or rejected if they
are not answered.
 Forward or reject calls:
To forward calls, select Forward to and specify the call
forward destination: Either select the relevant User, or
select Number and enter the number of an external
destination, a group, a service, or a connected Coral
Managing Sub-profiles

extension.
To reject calls, select Reject the call.

4 Click Save.
5

5-34 Profiles Aeonix Administration Manual

 Defining Advanced Rules for Incoming Call Routing
Advanced incoming call routing rules are used to forward or reject calls based on
caller numbers, time of call, presence, and the telephone status of users associated with
the relevant Incoming Call Routing sub-profile. Multiple rules can be defined for the
same routing conditions and are applied according to their priority.

To learn about basic incoming call routing rules, see Defining Basic Rules for
Incoming Call Routing, page 5-33.

The rules of an Incoming Call Routing sub-profile are either mandatory or optional.
While mandatory rules cannot be overridden at the user level, optional rules can be
overridden (but not removed) for a specific user.

This procedure describes how to define advanced rules for an incoming call
routing sub-profile. The procedure is similar for setting up advanced
incoming call routing rules for a specific user, except that no mandatory or
optional rules can be defined at the user level. To learn more about how to
adjust incoming call routing parameters for a user, see Overriding Incoming Call
Routing Rules, page 6-40.

To define an advanced Incoming Call Routing rule:

1 Click Advanced at the bottom of the Incoming Call Routing Profile page of
the relevant sub-profile. The fields for viewing and defining advanced rules are
displayed.

Managing Sub-profiles
5

Aeonix Administration Manual Profiles 5-35

 Figure 5-14 Advanced
Incoming Call Routing
Rules (Sub-profile)

You can use the Search box to textually search for and display specific items
in the list.

2 Click Mandatory and Optional to view or hide the required types of rules.
Each box lists the rules in the order in which they are executed. Select a rule
to display its full syntax underneath the list box. (This option is available for
all types of incoming call routing rules.)
Managing Sub-profiles
5

5-36 Profiles Aeonix Administration Manual

Figure 5-15 Advanced
Incoming Call Routing
Rule Details (Sub-profile)

The icons and labels to the left and the right of the boxes are described in the
following table.

Table 5-8 Actions for

Defining Advanced Call Action Button / Icon Description
Routing Rule
(Sub-profile) Move rule up Click to move a selected rule up in its rule box. This
action increases the priority of the rule.
Move rule Click to move a selected rule down in its box. This
down action decreases the priority of the rule.
Add rule Add Click to add a new advanced call routing rule.
Update rule Update Click to update a selected rule.
Delete rule Click to delete a selected rule. You can delete
Delete multiple rules by holding down the CTRL or SHIFT
key while selecting them.
Move rule to Click to move a selected mandatory rule to the
Move Down
lower box Optional rule box and turn it into an optional rule.
Move rule to Click to move a selected optional rule to the
upper box Move Up Mandatory rule box and turn it into an mandatory
rule.
Managing Sub-profiles
3 To the right of the relevant rule box, click Add to define a new advanced rule,
or select an existing rule and click Update. The advanced rule fields are
displayed for the rule.
5

Aeonix Administration Manual Profiles 5-37

 Figure 5-16 Advanced
Rule Parameters for an
Incoming Call Routing
Rule

4 To limit the rule to calls from specific callers, select from. You can define the
callers in the following ways:
 from—applies the rule only to calls from the listed callers
 from everyone except—applies the rule to all incoming calls except for
calls placed by the callers listed in the adjacent box
Add a caller or callers to the list:
a Click Add.
b Select the caller or callers:

Option Description

Number Enter the number of an external destination, a group,

a service, or a connected Coral extension.
Managing Sub-profiles

User Select a user from the drop-down list.

Starts with Enter the digits with which the calling number starts.

Range Specify a range of numbers.

Restricted All incoming calls for which the ANI (calling number)
number information is not provided
5

c Click OK. The caller is added to the list.

5-38 Profiles Aeonix Administration Manual

 You can edit list entries or remove them using the Update and Delete
buttons.

5 To limit the rule to calls at specific dates, days, or time periods:

a Select the at a time belonging to any of the following schedules check
box. The available global schedules are listed.
b Click the node of a schedule to display its time frames.

Figure 5-17 Time Frames

c Select the relevant schedules to include all their time frames in the rule, or
select specific time frames.

Global schedules are defined and managed as described in Schedules,

page 4-37.
At the user level, the schedules defined in the user’s Schedule sub-profile
are listed in addition to the global schedules (see Overriding Schedules,
page 6-39).

6 To restrict the rule by user presence:

a Select the and the user’s presence is any of the following check box. The
presence options are displayed (Online, DND, At a meeting).
b Select the relevant presence option or options.

The user presence is defined individually by the users themselves from the
Aeonix Web Portal for Users. For details, refer to the User Guide of the
relevant telephone (see Related Documentation, page 1-17). Managing Sub-profiles

7 To restrict the rule by phone status:

a Select the and the user’s phone status is any of the following check box.
The phone status options are displayed (Busy, Idle, Offline).
b Select the relevant presence option or options.
5

Aeonix Administration Manual Profiles 5-39

 8 Select the routing action for the rule:

Option Description

Ring on Rings on devices. Specify the following:

 Whether the calls are to ring on the user’s internal devices,
external phones, and/or members of the ULA group owned
by the user.
 If no answer after...seconds: Specify the number of
seconds after which calls are forwarded or rejected if they
are not answered.

NOTE: The value entered cannot exceed 65000 seconds.

 Forward or reject calls
To forward calls, select Forward to and specify the call
forward destination: Either select the relevant User, or
select Number and enter the number of an external
destination, a group, a service, or a connected Coral
extension.
To reject calls, select Reject the call.

Forward to Forwards the calls.

To specify the forward destination, either select the relevant
User, or select Number and enter the number of an external
destination, a group, a service, or a connected Coral
extension.

Reject the call Rejects the calls and disconnects the callers

9 Click OK. The rule is displayed in the relevant list box.

10 Click Save.
Managing Sub-profiles
5

5-40 Profiles Aeonix Administration Manual

  Outgoing Call Routing Sub-profiles

Outgoing Call Routing sub-profiles are assigned to user profiles only. They define
how the system routes and handles calls placed by users that are assigned the relevant
profile.
An Outgoing Call Routing sub-profile defines which Automatic Route Selection table
is applied to outgoing external calls. It is also used for the following:
 Enabling and configuring the hot station feature. If this feature is enabled, the
user’s phone automatically dials a specified number when the user operates the
phone.
The operations that induce the phone to call depend on the hot station mode
and on the type of the phone. Hot station triggers are lifting the phone handset
or pressing a key. Refer to the User Guide of the relevant phone for details
(see Related Documentation, page 1-17).
 Outside line access code parameters. If enabled, the system automatically adds
the outside line access code when a call is placed to an external number. In
this case, you do not have to dial the outside line access code when placing
calls to external numbers.

These parameters cannot be overridden.

 Manipulating digits of outgoing calls, mainly for assigning speed dial functions
to dial pad keys. Unlike speed dial functions set in phone profiles (see Phone
Profiles, page 5-54), these functions apply to all phones of a user, regardless of
their type.

Outgoing call routing parameters (except the Outside line access code
parameters) and rules can be overridden for a specific user (see Overriding
Outgoing Call Routing Parameters and Rules, page 6-43).
Managing Sub-profiles

To add or update an Outgoing Call Routing sub-profile:

1 On the navigation pane, click Settings. The pane displays the Settings menus.
2 Select the Profiles menu, and then click Sub-profiles. The available
sub-profile types are listed on the navigation pane.
3 Click Outgoing Call Routing. The existing Outgoing Call Routing
5

sub-profiles are listed on the Outgoing Call Routing Profiles page.

Aeonix Administration Manual Profiles 5-41

 Figure 5-18 Outgoing
Call Routing Profiles
Page

4 Do one of the following:

 To create a sub-profile, click Add.
 To update an existing sub-profile, select it from the list.
 To create a new sub-profile based on the settings of an existing one, click
(the Clone icon) to the right of the relevant sub-profile.

When you clone a sub-profile, all parameter values are copied to the new
sub-profile except for the sub-profile name and the Closed User Group.

The relevant Outgoing Call Routing Profile page is displayed.

Figure 5-19 Outgoing

Call Routing Profile Page
for a New Sub-profile
Managing Sub-profiles
5

5-42 Profiles Aeonix Administration Manual

 You can use the Search box to textually search for and display specific items
in the list.

5 Set the sub-profile identity parameters:

a If this is a new sub-profile, enter a name in the Name box.
b In the Description box, enter a description of the sub-profile (optional).

The Name of an existing sub-profile cannot be modified.

6 Select the relevant ARS table name. (To learn more about routing tables and
how they are defined, see Automatic Route Selection (ARS), page 4-43).
7 To activate and configure the hot station feature:
a Select the Enable hot station check box. The hot station parameters are
displayed.
b Select the Hot station mode as follows:
Immediate—the phone calls the hot station destination immediately after
the phone handset has been lifted or any key or number (including 911 and
emergency numbers) has been pressed.
Delayed—the phone calls the hot station destination if after an internal dial
tone was received, and no key is dialed during the Interdigit Timeout
defined in the relevant Timeout sub-profile (see Table 5-5 on page 5-13).
c In the Call to fields, specify the destination user or number for hot station
calls.

Managing Sub-profiles
SIP phones call the hot station destination only after the user dials at least
two digits and presses the Send button.
The Delayed hot station mode can only be used with MGCP-based phones
(FlexSet-IP 280S, T207M, T208M, T207M/NP, T208M/BL) and
digital keysets (FlexSet 120, 120D, 120L, 120S, 121S, 280, 280D, 280D-HS,
280S, 281S, DKT and DST; connected through a Wave Gateway).

8 Configure the outside line access code parameters:

5

Aeonix Administration Manual Profiles 5-43

  Add outside line access code when application dials—If selected, the
outside access code is automatically added when the user places a call to an
external number, or when an application (such as Sea Navigator) places a
call to an external number.

 By default, this check box is cleared, requiring the user to dial the outside
line access code to place calls to external numbers.
 When you enable the feature by clicking the check box, a system
information message is displayed: “Verify that there is no conflict between
the system dial plan and ARS”.

9 Define rules for manipulating outgoing call numbers as required. The

following procedures are available for defining and removing rules:
 Defining Dialed Number Manipulation Rules, page 5-45
 Deleting Dialed Number Manipulation Rules, page 5-48
10 Use (the Up and Down arrows) to arrange the rules in the required

priority order. A higher rule overrides any conflicting lower rule.

Click a rule to display its full syntax underneath the list box.

11 Click Save. The sub-profile is saved and displayed on the Outgoing Call
Routing List page.
Managing Sub-profiles
5

5-44 Profiles Aeonix Administration Manual

 Defining Dialed Number Manipulation Rules
A dialed number manipulation rule consists of a condition and of one or more
manipulations performed on outgoing call numbers if the condition is met.

To add or update a dialed number manipulation rule:

1 On the Outgoing Call Routing Profile page (see Figure 5-18), click Add right
to the Dialed Number Manipulation Rules box, or select a rule from the box
and click Update to modify an existing rule.
The fields for defining the condition of the rule are displayed, as well as
previously defined actions.

Figure 5-20 Dialed

Number Manipulation
Rule: Defining the
Condition

2 Select the relevant call type (DNIS or ANI) from the drop-down list, then
define the condition of the rule using the If the dialed number fields:
 To apply the rule to all dialed numbers beginning with a specific prefix or
set of digits, select starts with and enter the prefix or the first digits of the
number (digits only). Managing Sub-profiles

 To apply the rule to a specific dialed number, select is and enter the number
(digits only).
 To apply the rule to all outgoing calls, select is any number.
 To apply the rule to a range of dialed numbers, select is between and
specify the range.
5

 To apply the rule to any call that has a number that is restricted or empty.

Aeonix Administration Manual Profiles 5-45

 The is restricted or empty option is not relevant for DNIS manipulation
rules.

3 To cancel outgoing routing rules that are to be executed after this rule, select
Stop processing other rules.
4 To define an action for the rule, click Add. The Action fields are displayed.

Figure 5-21 Dialed

Number Manipulation
Rule: Defining the
Actions

5 Specify the required action using either of the following options:

Managing Sub-profiles

 Add offset—adds the specified offset number to the dialed number

(mathematical operation). For example, if you select this option and enter 5,
the dialed number 012233445 is changed to 012233450.
 Add prefix—adds the specified prefix number to the beginning of the
dialed number. For example, if you select this option and enter 03, the
dialed number 445566778 is changed to 03445566778.
5

5-46 Profiles Aeonix Administration Manual

  Add suffix—appends the specified suffix number to the dialed number. For
example, if you select this option and enter 5, the dialed number 012233445
is changed to 0122334455.
 Remove first digits—removes the specified number of digits from the
beginning of the dialed number. For example, if you select this option and
enter 2, the dialed number 034455667 is truncated to 4455667.
 Remove last digits—removes the specified number of digits from the end
of the dialed number. For example, if you select this option and enter 3, the
dialed number 023344558 is truncated to 023344.
 Replace number—replaces the dialed number with the specified number.
6 You can also enter the relevant digit string variables in the adjacent field.

You can use any combination of digits (0-9), asterisks ('*'), and pound ('#')
signs, and any combination of the following variables, which can be used a
multiple of times.

Table 5-9 Manipulation

Rule Action Variables Variable Description

[ANI] [ANI] will be replaced with the ANI of the call

[DNIS] [DNIS] will be replaced with the DNIS of the call

[MODANI] [MODANI] will be replaced with the modified ANI as

calculated till this point

[MODDNIS] [MODDNIS] will be replaced with the modified DNIS

as calculated till this point

[N:<num digits>] A running counter (where <num digits> designates the

counter’s maximum length) can be used, for example,
to identify the call instead of the ANI. The counter does
not start from zero, the start number is random.
Managing Sub-profiles
Examples:
[N:7] can produce a counter result that can contain a
minimum of one digit and a maximum of 7 digits.
[N:0] can produce a counter with unlimited digits (use if
you do not want counters to be repeated)
[N:07] will always produce a counter with seven digits
5

7 Click one of the following under the Action fields:

Aeonix Administration Manual Profiles 5-47

 8 Click OK & Add under the Action fields. The action is listed in the box
above. (Clicking OK hides the Action fields.)
9 To define further actions for the rule, repeat Steps 5-8 above.
10 Use (the Up and Down arrows) to set the priority order of the actions. A

higher action is performed before a lower action.

You can modify or delete any of the defined actions by selecting it and
clicking Update or Delete respectively.

11 Click OK at the bottom of the page. The rule is listed in the Digit
Manipulation Rules box on the Outgoing Call Routing Profile page.
12 Click Save.

Deleting Dialed Number Manipulation Rules

To delete a rule:
1 On the Outgoing Call Routing Profile page (see Figure 5-18), select the
relevant rule from the Dialed Number Manipulation Rules box. You can
delete multiple rules by holding down the CTRL or SHIFT key while selecting
them.
2 Click Delete. The rule is removed from the box.
Managing Sub-profiles
5

5-48 Profiles Aeonix Administration Manual

  Administration Level Sub-profiles

Administration Level sub-profiles are assigned to user profiles only. These parameters
define administration task privileges granted to users whose user profile is associated
with the particular administration level profile, authorizing them to access and/or
manage the Aeonix Web Portal pages associated with this administration level profile.

To add or update an Administration Level sub-profile:

1 At the bottom of the navigation pane, click Settings. The pane displays the
Settings menus.
2 Select the Profiles menu, and then click Sub-profiles. The available
sub-profile types are listed on the navigation pane.
3 Click Administration Level. The existing Administration Level sub-profiles
are listed on the Administration Levels Profile List page.

Figure 5-22
Administration Levels
Profiles Page

For a listing of the administration tasks associated with each default

administration level profile, see Table 1-3 on page 1-9.

4 Do one of the following:

Managing Sub-profiles
 To create a sub-profile, click Add.
 To update an existing sub-profile, select it from the list.
 To create a new sub-profile based on the settings of an existing one, click
(the Clone icon) to the right of the relevant sub-profile.
5

Aeonix Administration Manual Profiles 5-49

 When you clone a sub-profile, all parameter values are copied to the new
sub-profile except for the sub-profile name and the Closed User Group.

The relevant Administration Level Profile page is displayed.

Figure 5-23 Profile Page

for a New Administration
Level Sub-profile

5 Set the sub-profile identity parameters:

a If this is a new sub-profile, enter a name in the Name box.
Managing Sub-profiles

b In the Description box, enter a description of the sub-profile (optional).

The Name and the Closed User Group of an existing sub-profile cannot be
modified.

6 Set or view the sub-profile’s task privileges as described in the following table.
5

5-50 Profiles Aeonix Administration Manual

 You can assign either Read/Write or Read Only privileges for each task. Use
the top check boxes to toggle between selecting or clearing all parameters.

Table 5-10 Administration

Level Task Parameters Field (Task) Description

End Users Allows users to access and/or manage their own

personalized Web Portal (refer to the Aeonix Configuration
Guide for End Users).

Users Allows users to access and/or manage the following

Aeonix Web Portal pages:
 Users–see Chapter 6, Managing Users
 Phones–see Chapter 7, Managing Phones
 Aliases–see Chapter 11, Managing Aliases
 Schedules–see Schedules, page 4-37
 User Profiles–see Chapter 5, Managing Profiles
 Sub-Profiles–see Managing Sub-profiles, page 5-3
 Download Clients–see Aeonix Clients for Users, page 6-99

NOTE: When the Read/Write check box is selected, click

the Tasks assignable to new users... link to define which
tasks users of this administration level can assign to
new users; otherwise, all the tasks will be assigned.

Dial Plans and Digit Allows users to access and/or manage the following
Mappings Aeonix Web Portal pages:
 Dial Plans–see Dial Plans, page 4-19

PnP / Provisioning Allows users to access and/or manage the following

Services Aeonix Web Portal pages:
 PnP / Provisioning Service–see Configuring PnP /
Provisioning Service, page 12-123
 Aliases–see Chapter 11, Managing Aliases
 Provisioning Profiles–see Managing Provisioning Profiles,
page 5-91

Managing Sub-profiles
5

Aeonix Administration Manual Profiles 5-51

 Field (Task) Description

Trunks and ARS Allows users to access and/or manage the following
Aeonix Web Portal pages:
 Trunk Groups–see Trunk Groups, page 9-1
 Trunks–see Chapter 8, Trunks
 Configuring Trunks–see Configuring Trunks in Aeonix,
page 8-9
 Trunk Templates–see Trunk Templates, page 8-27
 ARS–see Automatic Route Selection (ARS), page 4-43
 Schedules–see Schedules, page 4-37
 Trunk Group Profiles–Managing Profiles, page 5-83
 General Info., Timeouts, and Toll Barrier
Sub-Profiles–see Managing Sub-profiles, page 5-3

SeaMail Services Allows users to access and/or manage the following

Aeonix Web Portal pages:
 SeaMail–see Configuring Voicemail, page 12-137
 Aliases–see Chapter 11, Managing Aliases

ACD and CTI Allows users to access and/or manage the following
Services Aeonix Web Portal pages:
 ACD Groups–see Defining ACD Groups, page 12-5
 CTI–see Computer Telephony Integration (CTI), page 12-99
 Hunt Groups–see Defining Hunt Groups, page 12-45
 Aliases–see Chapter 11, Managing Aliases

Mobility Services Allows users to access and/or manage the following

Aeonix Web Portal pages:
 Mobility Aliases–see Defining Mobility Aliases, page 12-89
 Aliases–see Chapter 11, Managing Aliases

Conference Services Allows users to access and/or manage the following

Aeonix Web Portal pages:
 Call Groups–see Defining Call Groups, page 12-59
 Conferences–see Defining Conference Calls, page 12-63
 Meet-Me Conferences–see Defining Meet-Me Conference
Aliases, page 12-79
 Zone Pages–see Defining Zone Page Calls, page 12-159
Managing Sub-profiles

 Aliases–see Chapter 11, Managing Aliases

Alarms Allows users to access and/or manage the following

Aeonix Web Portal pages:
 Alarms–see Alarms, page 14-1

Multi-Tenants Allows users to access and/or manage the following

Aeonix Web Portal pages:
5

 CUG–see Closed User Groups (CUG), page 4-29

5-52 Profiles Aeonix Administration Manual

 Field (Task) Description

System and Clusters Allows users to access and/or manage the following
Aeonix Web Portal pages:
 Locations–see Locations, page 4-9
 Countries–see Country-specific Dial Codes, page 4-1
 Clusters–see Clusters, page 14-33
 Backup and Restore–see Data Backup and Restoring via
Web, page 14-55
 System–see System Information, page 14-25
 Restarting Aeonix–see Upgrading Aeonix via Web, page 14-63
 Licensing (view only)–see License Information Page,
page 3-32

LDAP Allows users to access and/or manage the following

Aeonix Web Portal pages:
 LDAP–see LDAP Connections, page 4-53

VOIP Gateways Allows users to access and/or manage the following

Aeonix Web Portal pages:
 Gateways–see Chapter 10, Managing VOIP Gateways

Other Services Allows users to access and/or manage the following

Aeonix Web Portal pages:
 CDR–see Configuring Call Detail Records (CDR), page 12-97
 Dispatch Consoles–see Defining Dispatch Consoles,
page 12-103
 Hospitality–see Configuring the Hospitality Service, page 12-39
 Page Queue Park/Pickup–see Configuring Page Queue
Park/Pickup, page 12-117
 Virtual Endpoints–see Defining Virtual Endpoints, page 12-149
 Aeonix Contact Center–see Configuring the Aeonix Contact
Center, page 12-17
 Music–see Configuring the Music Service, page 12-111
 Recording–see Configuring Call Recording, page 12-23
 Prompt and Message–see Importing Audio Files, page 12-133

Licensing Allows users to access and/or manage the following

Aeonix Web Portal pages:
Managing Sub-profiles
 Licenses–see Licenses, page 3-29

7 Click Save. The sub-profile is included in the list on the Administration Levels
Information Profile List page.
5

Aeonix Administration Manual Profiles 5-53

  Phone Profiles

Phone profiles are sub-profiles that define the properties (speed dial and other
functions of the phones’ programmable buttons) of the following MGCP, SIP, and
digital phones connected to Aeonix:
 MGCP IP phones: FlexSet-IP 280S, T207M, T208M, T207M/NP, T208M/BL
 Tadiran SIP phones: T19P, T19P E2, T21P E2, T23G, T27P, T29G, T322,
T328, T41P, T42G, T46G, T48G, T49G
 P-Series phones: P-335, P-450
 FlexSet 28x Series digital phones connected through a Wave Gateway:
FlexSet 280S, FlexSet 281S, FlexSet 280D, FlexSet 280D-HS, and FlexSet 280
 FlexSet 12x Series digital phones connected through a Wave Gateway:
FlexSet 120S, FlexSet 121S, FlexSet 120D, and FlexSet 120
 DKT and DST digital phones connected through a Wave Gateway:
DKT 2320, DKT 2300, DKT 2120, DKT 2100, DKT 1110, DKT 1100, and
DST
The values and functions defined for a phone profile are applied by default to the
relevant phones of users whose assigned profile includes this phone profile. At the
user level, additional phone profiles can be defined and associated to specified phones
(see Configuring a User’s Phone Profiles, page 6-49).
This section describes the following:
 Defining a Phone Profile, page 5-54
 Programmable Button Dial Functions, page 5-60
 Programming TEM Buttons of T207M, T208M, T207M/NP, T208M/BL Phones,
page 5-78

Defining a Phone Profile

This section describes how to define a phone profile for any of the phone types listed
Managing Sub-profiles

on page 5-54.

Programming TEM buttons on T207M, T208M, T207M/NP, T208M/BL

phones is described in Programming TEM Buttons of T207M, T208M, T207M/NP,
T208M/BL Phones, page 5-78.
5

5-54 Profiles Aeonix Administration Manual

 To add or update a phone profile:
1 On the navigation pane, click Settings. The pane displays the Settings menus.
2 Select the Profiles menu, and then click Sub-profiles. The available
sub-profile types are listed on the navigation pane.
3 Click Phone. The existing phone profiles are listed on the Phone Profiles page.

Figure 5-24 Phone

Profiles Page

4 Do one of the following:

 To add a new phone profile, click the Add button and select the relevant
phone icon as described in Table 5-11 on page 5-56.
 To update a default or another existing phone profile, click its name. Managing Sub-profiles
 To create a new phone profile based on the settings of an existing one, click
(the Clone icon) to the right of the relevant phone profile.

When you clone a phone profile, all parameter values are copied to the new
phone profile except for the profile name and the Closed User Group.
5

Aeonix Administration Manual Profiles 5-55

 The relevant phone’s Profile page is displayed, as in the following figure for a
new T46G Tadiran SIP phone profile.

Figure 5-25 Phone Profile

Page for a New T46G
Profile

A phone profile page displays an image of the following phones:

Table 5-11 Phone Profiles

Phone Profile Displayed Image Use for Phones

FlexSet-IP 280S FlexSet-IP 280S  FlexSet-IP 280S

T207M / T208M T208M series with  T207M

Managing Sub-profiles

optional TEM  T208M

(Telephone  T207M/NP
Expansion Module)  T208M/BL

DKT 1110 / DST DKT 1110  DKT 1110

 DKT 1100
 DST
5

5-56 Profiles Aeonix Administration Manual

 Phone Profile Displayed Image Use for Phones

DKT 21xx DKT 2120 with  DKT 2120

optional DPEM  DKT 2100
(Digital
Programmable
Expansion Module)

DKT 23xx DKT 2320 with  DKT 2320

optional DPEM  DKT 2300
(Digital
Programmable
Expansion Module)

FlexSet 120D FlexSet 120D  FlexSet 120

 FlexSet 120D
 FlexSet 120L

FlexSet 12xS FlexSet 120S or  FlexSet 120S

FlexSet 121S  FlexSet 121S
(look the same)

FlexSet 280D FlexSet 280D  FlexSet 280

 FlexSet 280D
 FlexSet 280D-HS

FlexSet 28xS FlexSet 280S or  FlexSet 280S

FlexSet 281S (look  FlexSet 281S
the same) with
optional FlexSet 40B
expansion module

P-335 P-335  P-335

P-450 P-450  P-450

T322 T322  T322

T328 T328 with optional  T328

expansion module Managing Sub-profiles

T19P T19P  T19P

T19P E2 T19P E2  T19P E2

T21P E2 T21P E2  T21P E2

T23G T23G  T23G

5

Aeonix Administration Manual Profiles 5-57

 Phone Profile Displayed Image Use for Phones

T27P T27P with EXP20  T27P

expansion module

T29G T29G  T29G

T41P / T42G T42G  T41P

 T42G

T46G T46G with EXP40  T46G

expansion module

T48G T48G with EXP40  T48G

expansion module

T49G T49G  T49G

5 Set the phone profile identity parameters:

a If this is a new phone profile, enter a name in the Name box.

The Name of an existing phone profile cannot be modified.

6 Click Properties to display the phone properties and set them as described in
the following table.

Table 5-12 Phone

Properties Field Option Description

Local display Text to be displayed on the panel of the phone.

If this field is empty, the Display name of the
user is used instead.

NOTE: This field is ignored for phones without a

display.
Managing Sub-profiles
5

5-58 Profiles Aeonix Administration Manual

 Field Option Description

Speakers On-Off NOTE: Not applicable for SIP phones.

mode
Speaker mode cannot be toggled during a call.
When the Speaker (SPKR) button is pressed on
the phone, the call is disconnected.
This mode is used mostly in the call center
environment, in which the agent uses headsets
and the phone handset is permanently on-hook.
The agent uses the Speaker button to answer
and hang up calls.

Toggle NOTE: Only applicable for Tadiran SIP phones

with programmable buttons.
Speaker mode can be toggled during a call.
When the Speaker (SPKR) button is pressed on
the phone, the call toggles between handset
and speakerphone mode.

Group When using the handset and the Speaker

Listening (SPKR) or Group Listening button is pressed on
the phone, the phone’s speaker can be toggled
for group listening.

7 Assign dial functions to programmable phone buttons:

a Click the relevant button on the image of the phone.
A red indication flashes next to the button. To the right of the phone, the
system shows the current setting and provides a drop-down list of the
options for configuring the button. The options are described in
Programmable Button Dial Functions, page 5-60.

Figure 5-26 Button

Programming for T46G
Phones

Managing Sub-profiles

b Specify the function for the button. For example, select Deflect from the
Feature type drop-down list and specify the destination user, number, or
5

speed dial number in the Direct incoming calls to fields.

Aeonix Administration Manual Profiles 5-59

 Figure 5-27 Programming
a Deflect Button for T46G
Phones

c Select Lock if you do not want the button function to be modifiable for
users of this profile.
d If you want to customize the name of the function as it is displayed on the
phone, enter the required text in the Label field.
e Click OK. The icon of the selected function is displayed to the left of the
button.

To learn about how to program T207M, T208M, T207M/NP, T208M/BL TEM

buttons, see Programming TEM Buttons of T207M, T208M, T207M/NP, T208M/BL
Phones, page 5-78.

8 Click Save. The phone profile is included in the list on the Phone Profile List
page.

Programmable Button Dial Functions

The programmable buttons of phones can be assigned the dial functions listed in
Table 5-13 and Table 5-14 (for a list by phone type, refer to the Aeonix Product
Description).
Managing Sub-profiles

Tadiran SIP phones with programmable buttons require the Provisioning

service to be active (see Chapter 12, Configuring PnP / Provisioning
Service) and must be ESF enabled (see ESF for Tadiran SIP Phones, page 5-20).
5

5-60 Profiles Aeonix Administration Manual

Table 5-13 Programmable
Phone Button Dial Dial Feature Icon Description
Functions
ACD Login / Press the button and select the number of your
Logout ACD group to log in to this ACD group. Repeat this
procedure to log in to further ACD groups.
Use the same procedure to log out of an ACD
group in which you are currently logged in (toggle
feature).

NOTE: A label can be defined on supported phones.

ACD Release / Press the button to indicate that you are

Resume unavailable to receive calls for all your ACD groups
to which you are logged in.
Press the button again to return to all your ACD
groups (toggle feature).

NOTE: A label can be defined on supported phones.

Aeonix Contact Center See Table 5-14, Programmable Phone Button Dial
Functions for Aeonix Contact Center.

NOTE: A label can be defined on supported phones.

Alarm agent Press the unlit button (which indicates that the
phone is currently set to RFC 2833 mode) - the
button flashes until the phone provisioning process
has been completed.

NOTE: If the phone is not in idle state, provisioning

will be delayed until the phone becomes idle
again.
Once activated, the button becomes lit, indicating
that the phone is now set to SIP INFO mode. Use
the same procedure to return to RFC 2833 mode
(toggle feature).

NOTE: A label can be defined on supported phones.

Auto Redial Press the Auto Redial button to add the last busy
or non-answering external destination number
dialed to the auto redial queue (up to 20 numbers Managing Sub-profiles
can be stored in the Redial list).
Press the Freeze Auto Redial button to suspend
the Auto Redial feature; Auto Redial and Freeze
Auto Redial buttons flash.
Pressing any of the flashing buttons unfreezes all
the numbers in the Redial list and the buttons stop
flashing.

NOTE: A label can be defined on supported phones.

5

Aeonix Administration Manual Profiles 5-61

 Dial Feature Icon Description

Break-in NOTE: You must be authorized to perform a

Break-in (see Defining Permission Settings,
page 6-74).
Press the button to break-in to an established
two-party call. If no user or alias number is
specified for the button, enter the required
destination alias after pressing the button
Alternatively, if the destination is defined as Speed
dialing and a separate Speed dialing button has
been defined, press the Break-in button, and while
it flashes, press the Speed Dial button to send it to
the specified destination. A prefix number can be
added before the number to be dialed.
In addition, when dialing a number that is busy or
on call waiting, a forced break-in is performed.

NOTE: A label can be defined on supported phones.

Break-out NOTE: You must be authorized to perform a

Break-out (see Defining Permission Settings,
page 6-74).
Press the button to break-out a target from an
established call. The target’s established call is put
on hold for the target, and the target is than
connected in a call with the user. If no user or alias
number is specified for the button, enter the
required destination alias after pressing the button
Alternatively, if the destination is defined as Speed
dialing and a separate Speed dialing button has
been defined, press the Break-out button, and
while it flashes, press the Speed Dial button to
send it to break-out specified destination. A prefix
number can be added before the number to be
dialed.
In addition, when dialing a number that is busy or
on call waiting, a forced break-out is performed.

NOTE: A label can be defined on supported phones.

Managing Sub-profiles
5

5-62 Profiles Aeonix Administration Manual

 Dial Feature Icon Description

Camp-on You can define Camp-on for the following

conditions:

Camp-on idle—Request to activate a call back

when the designated destination indicates that it is
available (for example, by being first busy and then
becoming idle again).

Camp-on busy—Request to activate a call back

when the designated busy destination becomes
available again.

Camp-on auto—The system automatically makes

the camp-on request based on the destination and
state (busy or idle) of the last outgoing internal call.

NOTE: In this case, the last call data is kept for 5

minutes, after which pressing the Auto
Camp-on button will not make the camp-on
request. Press the activated DSS button to
cancel the last camp-on request. The LED
will only be turned off once all the camp-on
requests are deactivated.

Specify one of the following destination types

(relevant for Camp-on idle and Camp-on busy):

User—Aeonix user
Alias—Aeonix user alias
Speed dialing—In this mode, the Camp-on button
works in conjunction with a Speed Dialing button.
Once pressed, the Camp-on button LED will blink
for 5 seconds. During this time, pressing any
Speed Dialing button will set the Camp-on target to
the value of the Speed Dialing target.

NOTE: A label can be defined on supported phones.

Aeonix provides SLT Camp-On for SLT / POTS Managing Sub-profiles
telephones for low-cost deployments. See Feature
Codes for Dial Plans, page 4-23.
5

Aeonix Administration Manual Profiles 5-63

 Dial Feature Icon Description

Conference call Conference call managers use this button to

activate the following features:

NOTE: Members that have these DSS keys

configured can see the button’s
corresponding LED status. Pressing the
button will affect the conference only if the
member is also a conference manager.
Add / remove—If a user or alias number is used,
pressing this button will add/remove the specified
target to the conference call; If the DSS is set to
be Conference Call, pressing this button will
add/remove all the available members of the
specified conference call to this conference call.
Alternatively, if a separate Speed dialing button
has been defined, press that button to add or
remove the specified member.

NOTE: A lit LED indicates that the member is a

passive participant in the conference without
speaking rights; a fast flashing LED
indicates that the member made a request to
speak; and a slow flashing LED indicates
that the member can speak.
Lock / unlock—press this button to prevent/allow
users from joining the conference call.

NOTE: A lit LED indicates that the conference is

locked to other users. However, managers
can still add members to the conference
using the Add / Remove DSS buttons, even
if the conference is locked.
Managing Sub-profiles
5

5-64 Profiles Aeonix Administration Manual

 Dial Feature Icon Description

Conference call Mute / unmute—If a user or alias number is used,

(continued) pressing this button during a conference call will
prevent/allow the specified conference call member
to speak. A lit LED indicates that the member is in
mute.

NOTE: If no user or alias number is specified, this

feature is used in conjunction with the Add /
Remove button defined for specified
members. When pressing Mute / Unmute,
the button’s LED flashes for four seconds.
During this time, pressing a member’s Add /
Remove button will cause the members to
be muted or unmuted. Press this button
twice to mute all the members. Alternatively,
if a separate Speed dialing button has been
defined, press that button to mute or unmute
the specified member.

NOTE: Muted participants can press 0 on

supporting phones to request to speak.
Terminate—press this button to end the
conference call.

NOTE: A label can be defined on supported phones.

Managing Sub-profiles
5

Aeonix Administration Manual Profiles 5-65

 Dial Feature Icon Description

Custom Press the button to activate the defined

provisioning provisioning feature (only applicable for Tadiran
feature SIP phones - refer to the corresponding phone
manufacturer’s Auto Provisioning documentation
for details.

NOTE: For P-Series phones, macros can be

defined. Adding $P1N10$ at the end of the
feature code will prompt the user with further
instructions on the phone display.
For Tadiran SIP phones via soft keys, the following
types are available:
 Call return - to place a call to the last incoming
call
 History - to access the phone call log
 Menu - to access the phone menu
 Status - to access the phone status menu

For T20 and T40 Series Tadiran SIP phones, the

following types are available:
 BLF - to monitor the specified line for busy / idle
status
 Call return - to place a call to last incoming call
 DTMF - to automatically send the specified key
sequence during an active call

NOTE: You can use any combination of digits (0-9),

asterisks ('*'), pound ('#') signs, and any
combination of the letters A-D.

NOTE: Aeonix Touch accepts the following DTMF

sequences to activate Mobility Features:
*1 get back line (dial tone)
*2 move from mobile to desktop
 Group listening—to simultaneously activate the
speakerphone and handset/headset mode
during an active call
 Hold—to place an active call on hold or resume
Managing Sub-profiles

a held call
 Line—to place a call
 Not provisionable—to reserve this programmable
button for direct configuration via the phone itself
(provisioning definitions will not affect this
button)
5

5-66 Profiles Aeonix Administration Manual

 Dial Feature Icon Description

Custom  Prefix—to add the specified prefix digit before

provisioning the number to be dialed
feature (continued)  Transfer (one-step)—to transfer the active call to
the specified destination without first notifying
the recipient of the transfer
 URL - to trigger the phone to send an http GET
request containing the specified URL

NOTE: A label can be defined on supported phones.

Deflect Press the button to transfer an incoming call to a

specified user, external number, Coral extension,
or call group.
Alternatively, if the destination is defined as Speed
dialing and a separate Speed dialing button has
been defined, press the Deflect button, and while it
flashes, press the Speed Dial button to send it to
the specified destination. A prefix number can be
added before the number to be dialed.

NOTE: A label can be defined on supported phones.

Directory Press the button when in idle, transfer, hold, or dial

tone state to access the Aeonix directory.

NOTE: A label can be defined on supported phones.

DND Automatically rejects incoming calls.

NOTE: For contact center agents, only non-ACC

calls will be rejected.

NOTE: A label can be defined on supported phones.

Emergency call Press this button to place an emergency call (for

example, 911 is dialed in the United States). The
relevant emergency center must be defined in the
system (see Defining Emergency Call Settings, page 4-16).
In addition, if the emergency callback feature is
enabled (see System Parameters, page 14-27), Callback
by emergency personnel will be rerouted to the Managing Sub-profiles
user that placed the emergency call (ignoring user
DND or FWD All rules) for the next hour. During
this time the user will not be able to perform
manual logout of the phone.

NOTE: A label can be defined on supported phones.

5

Aeonix Administration Manual Profiles 5-67

 Dial Feature Icon Description

Flash mode While engaged in a call, press the button, thereby

putting the second party on hold, and then perform
the following according to the defined feature
below:

NOTE: Separate buttons can be defined for

Consultation, Continuous conference, and
Swap.
 Consultation - Dial a third party to consult
privately with this person. Press the button again
to release the consulted party and return to the
second party.
 Continuous conference - Dial a third party.
When the third party answers, press the button
again to connect the held party with the third
party and yourself, effectively creating a 3-way
call. Press the button again to add the 4th party.
Dial the party. When the party answers, press
the button again to add the party to the 3-way
call, effectively turning it into a multi-party
ad-hoc conference call. Press the button as
required to continue adding parties to the
conference call.
 Swap - Dial a third party to converse privately
with this person. Press the button again to return
to the second party, putting the third party on
hold. Press the button as required to switch
back and forth between the two calls (toggle
feature).

NOTE: If the As Set in the user profile is selected,

the Flash mode used is derived from the
user’s Feature Configuration profile (see
Flash Mode, page 5-20).

NOTE: A label can be defined on supported phones.

Managing Sub-profiles
5

5-68 Profiles Aeonix Administration Manual

 Dial Feature Icon Description

Forward Configure forwarding of incoming calls to the

specified destination. You can define Forward for
the following conditions:

Forward all—Forward all calls to the designated

destination.

Forward on busy—Forward calls to the

designated destination when the phone line is
busy.

NOTE: Call Waiting must be deactivated.

Forward on no answer—Forward calls to the

designated destination when the user does not
answer the phone before the Ring Timeout is
reached (default: 30 seconds).

Forward on logoff—Forward calls to the

designated destination if the user is logged out
from all of his internal devices.

Forward on DND—Forward calls to the

designated destination when the user’s presence
status is DND.

Forward on no answer and busy—Forward calls

to the designated destination if the user does not
answer the phone or if the phone line is busy.

Specify one of the following destination types:

User—Aeonix user
Number—Any valid internal or external number
Speed dialing—In this mode, the Forward button
works in conjunction with a Speed Dialing button.
Once pressed, the Forward button LED will blink Managing Sub-profiles
for 5 seconds. During this time, pressing any
Speed Dialing button will set the Forward target to
the value of the Speed Dialing target.
In addition, you can optionally specify a prefix
number that will enable you, for example, to
reroute the forwarded call via a specific trunk.

NOTE: Once defined, you can double-click the

button at any time to cancel the setting.
5

NOTE: A label can be defined on supported phones.

Aeonix Administration Manual Profiles 5-69

 Dial Feature Icon Description

Group listening While engaged in a call, press this button to

simultaneously use the speaker and handset (not
applicable for FlexSet-IP phones). Press the button
again to turn off speakerphone mode (toggle
feature).

NOTE: For Tadiran SIP phones, see Custom

provisioning feature, page 5-66.

Group pickup Press this button to pick up a ringing call for your
pickup group.

NOTE: A label can be defined on supported phones.

Headset only Press the button to activate Headset Only mode.

NOTE: Local feature in SIP phones.

Hold During an ongoing call, press the button to

temporarily interrupt the call and put the other
party in waiting mode (on hold).

NOTE: For Tadiran SIP phones, see Custom

provisioning feature, page 5-66.

Line Used for making and receiving calls. When several

Line buttons are in use, the phone acts as a
multi-line device.

NOTE: For Tadiran SIP phones, see Custom

provisioning feature, page 5-66.

Message waiting Press the button to directly access your voicemail

box.

NOTE: A label can be defined on supported phones.

Mute Press the button before or during a conversation to

turn off the microphone, so that the other party
cannot hear you.
If call muting is activated, press the button again to
Managing Sub-profiles

disable it (toggle feature).

NOTE: Local feature in SIP phones.

Page Queue Press the button to park a call to the specified

Page Queue number. A lit LED indicates that the
call can be picked up by you or by other users with
the same Page Queue DSS defined.
5

NOTE: A label can be defined on supported phones.

5-70 Profiles Aeonix Administration Manual

 Dial Feature Icon Description

Record on demand NOTE: The Record on demand programmable

button is available on supported phones. For
other phones, you can activate/deactivate
during idle or hold states by using the
record on demand feature code (default
1443).
Press the button during any call state (ringing, ring
back, hold, held, idle) to record the call. If
activation is done during idle, the next incoming or
outgoing call is recorded.
Press the button on and off in any state (toggle
feature). Record on demand will stop recording if
you leave the call (put the call on hold, transfer the
call, etc.).

NOTE: A label can be defined on supported phones.

Redial Press the button to dial the last dialed number,

including feature codes dialed for this number.

NOTE: A label can be defined on supported phones.

Release last In a conference call, press the button to disconnect

conference the party that joined the conference last.
member
NOTE: Not applicable for SIP phones.

Restrict Press this button before placing a call to allow or

identification restrict your calling number (ANI) information to be
provided to the receiver of the call.

NOTE: Not applicable for SIP phones.

Room status Press the button and enter the relevant room
status code (01-16).

NOTE: Not applicable for SIP phones.

Managing Sub-profiles
5

Aeonix Administration Manual Profiles 5-71

 Dial Feature Icon Description

Shared line button NOTE: The number of shared line buttons that can
be used depends on the Max. number of
waiting calls threshold defined in the user’s
Feature Configuration sub-profile (see Table
5-6 on page 5-17).
Press this button to answer or place a call on
behalf of a ULA group. This button can always be
configured but works only for members of the
specified ULA group.
Users press a shared line button to answer an
incoming call to the specified ULA group, or to
place a call on behalf of the group. Pressing the
button twice allows ULA members to directly call
the group owner.
A shared line button flashes to indicate incoming
ULA calls, or calls put on hold. The button is lit
when the user answers or has placed a ULA call,
as well as when another ULA member puts a call
on exclusive hold.
ULA owner—specifies the ULA group for which
the button will be used. Enter the user of the
relevant ULA group owner.
Line no.—specifies the order at which shared line
buttons assigned to a ULA group are activated if
several ULA calls are received or placed at the
same time.

NOTE: A label can be defined on supported phones.

Managing Sub-profiles
5

5-72 Profiles Aeonix Administration Manual

 Dial Feature Icon Description

Silent monitor Authorized users (see Defining Permission Settings,

page 6-74) use this button to activate the following
features:

NOTE: When dialing a number that is busy or on call

waiting, pressing the button when no target
was specified will cause the call to be
monitored as well.
Silent monitor both sides—Press the button to
monitor an established two-party call or Meet-me
conference. If no user or alias number is specified
for the button, enter the required destination alias
after pressing the button. Alternatively, if the
destination is defined as Speed dialing and a
separate Speed dialing button has been defined,
press the Silent monitor button, and while it
flashes, press the Speed Dial button to send it to
the specified destination. A prefix number can be
added before the number to be dialed.
Silent monitor partner side—Press the button to
monitor the user partner side of an established
two-party call. If no user or alias number is
specified for the button, enter the required
destination alias after pressing the button.
Alternatively, if the destination is defined as Speed
dialing and a separate Speed dialing button has
been defined, press the Silent monitor button, and
while it flashes, press the Speed Dial button to
send it to the specified destination. A prefix
number can be added before the number to be
dialed.
Silent monitor user side—Press the button to
monitor the user side of an established two-party
call. If no user or alias number is specified for the
button, enter the required destination alias after
pressing the button. Alternatively, if the destination
is defined as Speed dialing and a separate Speed
dialing button has been defined, press the Silent
monitor button, and while it flashes, press the
Speed Dial button to send it to the specified Managing Sub-profiles
destination. A prefix number can be added before
the number to be dialed.

NOTE: If the user has more than one device, the

phone that is defined with Use by App (see
Figure 6-23) is the device that will be
actually monitored.

NOTE: A label can be defined on supported phones.

5

Aeonix Administration Manual Profiles 5-73

 Dial Feature Icon Description

Single step Press the button while engaged in a call to put the
transfer second party on hold and establish a call
connection between the second party and another
specified user, external number, Coral extension,
or call group.
Alternatively, if the destination is defined as Speed
dialing and a separate Speed dialing button has
been defined, press the Single step transfer button,
and while it flashes, press the Speed Dial button to
send it to the specified destination. A prefix
number can be added before the number to be
dialed.

NOTE: Not applicable for SIP phones.

Speaker Used for hands-free conversation.

NOTE: Local feature in SIP phones.

Managing Sub-profiles
5

5-74 Profiles Aeonix Administration Manual

 Dial Feature Icon Description

Speed dialing NOTE: Users cannot speed dial to numbers that are
blocked by their toll barrier settings (see Toll
Barrier Sub-profiles, page 5-24).
Used for calling a specified user, external number,
Coral extension, call group, or service by pressing
the button instead of dialing the number.
If the speed dialing destination is a user, the button
lights if any of this user’s alias numbers is busy.
If the speed dialing destination is a service (such
as Voice Page), the button lights if all alias
numbers assigned to this service are busy.
On supported Tadiran SIP phones, if the speed
dialing destination is a user, the button shows user
presence, as follows:
 Off–User B is logged out of Aeonix
 Green–User B is in idle state
 Red–User B is in busy state
 Flashing red–User A put user B on hold, in
which case user A can resume the held call by
pressing the flashing red LED
OR
User B has a ringing incoming call, in which
case authorized user A (see Pickup on page 5-19)
can pick up the call by pressing the flashing red
LED.

NOTE: For Tadiran SIP phone models with color

touch screens, presence is indicated on the
Speed dial button (Green for available and
Red for busy).
If the speed dialing destination is a service (such
as Meet-me Conference), the button lights if the
alias number assigned to this service is busy.

NOTE: A label can be defined on supported phones.

Voice page Press the button to voice-page another user in the

system. If no user or alias number is specified for
the button, enter the required destination alias after Managing Sub-profiles
pressing the button. Alternatively, if the destination
is defined as Speed dialing and a separate Speed
dialing button has been defined, press the Voice
page button, and while it flashes, press the Speed
Dial button to send it to the specified destination. A
prefix number can be added before the number to
be dialed.

NOTE: Not applicable for SIP phones.

5

Aeonix Administration Manual Profiles 5-75

 Dial Feature Icon Description

Wakeup Press the button and enter the time you want to be
awoken.

NOTE: Wakeup call attempts will be made even

when in DND mode.

NOTE: Not applicable for SIP phones.

Table 5-14 Programmable

Phone Button Dial Dial Feature Description
Functions for Aeonix
Contact Center Login & Logout Press the button to log in to all your primary Aeonix
Primary Groups Contact Center groups.
Use the same procedure to log out of all your primary
Aeonix Contact Center groups (toggle feature).

Group Login & Press the button to log in to the Aeonix Contact Center
Logout group specified.
Use the same procedure to log out of this specific Aeonix
Contact Center group, which you are currently logged into
(toggle feature).

Release & Resume Press the button to indicate that you are unavailable to
receive ACC calls for all your Aeonix Contact Center
groups to which you are logged in.
Press the button again to return to all your Aeonix Contact
Center groups (toggle feature).

Release & Resume Press the button and enter the specified release code to
with Code indicate that you are unavailable to receive ACC calls for
all your Aeonix Contact Center groups to which you are
logged in.
Press the button again and enter the release code to
return to all your Aeonix Contact Center groups (toggle
feature).
Managing Sub-profiles

Extend Wrap-up Press the button to ignore the Wrap-up timeout and
continue in the Wrap-up state.

End Wrap-up Press the button to exit the Wrap-up state.

Wrap-up with Code During a call or while in Wrap-up state press the button
and specified Wrap-up code to enter the Wrap-up
associated with the call.
5

If you enter more than one Wrap-up code during a call,

only the first one is used.

5-76 Profiles Aeonix Administration Manual

 Dial Feature Description

Group Queue Info Press the button to display the number of calls waiting in
queue for the Aeonix Contact Center group specified.
This information is displayed for approximately five
seconds.

Managing Sub-profiles
5

Aeonix Administration Manual Profiles 5-77

 Programming TEM Buttons of T207M, T208M, T207M/NP, T208M/BL
Phones
A Telephone Expansion Module (TEM) can be attached to T207M, T208M,
T207M/NP, T208M/BL phones, providing 22 additional bi-functional programmable
buttons.

To program TEM buttons in a T207M / T208M phone profile:

1 Access the phone profile’s page (see Defining a Phone Profile, Steps 1-4 on
page 5-55). The relevant T207M / T208M Profile page displays a T207M,
T208M, T207M/NP, T208M/BL phone with an attached TEM.

Figure 5-28 Phone Image

on T207M/208M Profile
Page
Managing Sub-profiles

2 If required, set the phone profile identity parameters and assign dial functions
to the four programmable buttons on the phone (see Defining a Phone Profile,
Steps 5-7 on page 5-58).
3 Program the TEM buttons. For each of these buttons, you can additionally
assign an alternate function using the Shift button of the phone.
5

5-78 Profiles Aeonix Administration Manual

 To assign a dial function to a TEM button:
a Click the TEM button on the image of the phone. (To assign an alternate
function, click the relevant Shift button at the bottom before clicking the
button.)
A red indication flashes next to the button (or in the row below the button
for an alternate function). To the right of the phone, the system shows the
current setting and provides a drop-down list of the options for configuring
the button. The options are described in Programmable Button Dial Functions,
page 5-60.

Figure 5-29 Image on

T207M/208M Profile Page

Managing Sub-profiles
5

Aeonix Administration Manual Profiles 5-79

 Figure 5-30 Programming
a TEM Button for Speed
Dial

b Specify the function for the button. For example, select Speed Dial from
the Feature type drop-down list and specify the destination user or number
in the Dial to fields.
c Select Lock as required. If this check box is selected, the button function
cannot be modified for the specified user.
d Click OK. The icon of the selected function is displayed next to the button.
(Shift function icons are displayed indented in the row under the button.)
The following figure shows an example for a TEM button definition with a
basic and an alternate function. In this example, the top left TEM button is
used for putting a caller on hold; however, if the relevant Shift button is
pressed before this button, the phone calls a specified user or number. The top
right TEM button is used for calling two different numbers; which number is
dialed depends on whether the Shift button was pressed.
Managing Sub-profiles
5

5-80 Profiles Aeonix Administration Manual

Figure 5-31 T207M,
T208M, T207M/NP,
T208M/BL Button
Programming Example

4 Click Save.

If the profile is applied to a phone that does not have a TEM, the functions
assigned to the TEM buttons are not relevant for this phone.

Managing Sub-profiles
5

Aeonix Administration Manual Profiles 5-81

Managing Sub-profiles
5

5-82 Profiles Aeonix Administration Manual

 5.3 Managing Profiles

A profile is a set of selected sub-profiles of several sub-profile types (see Managing

Sub-profiles, page 5-3). Defining a profile includes selecting sub-profiles for the profile,
as well as specifying whether they can be overridden for a particular entity.
Two profile types exist in the Aeonix system:
 User profiles are assigned to Aeonix users and define values of user
parameters. To learn more about users, see Chapter 6, Managing Users.
 Trunk group profiles are assigned to Aeonix trunk groups and define values
of trunk group parameters. To learn more about trunk groups, see Chapter 9,
Managing Trunk Groups.
User profiles and trunk group profiles are managed in the same way, except that some
sub-profiles— Incoming Call Routing, Outgoing Call Routing, Feature Configuration,
and Phone profiles—are only associated with user profiles. For trunk groups, routing
rules are defined individually for each trunk group, rather than through profiles
(see Defining Incoming and Outgoing Call Routing for Trunk Groups, page 9-11).
The profiles are managed from the User and Trunk Group Profile List Pages. Managing
profiles includes the following procedures:
 Defining a User Profile, page 5-86
 Defining a Trunk Group Profile, page 5-88

Managing Profiles
5

Aeonix Administration Manual Profiles 5-83

  User and Trunk Group Profile List Pages

The User Profile List page displays the user profiles defined in the system; the Trunk
Group List page displays the trunk group profiles.

To open these pages:

1 On the navigation pane, click Settings. The pane displays the Settings menus.
2 Select the Profiles menu, and then click User Profile List or Trunk Group
Profile List.

Figure 5-32 User Profile

List Page

Figure 5-33 Trunk Group

Profile List Page

The profile lists are sorted by the Name column. If the list includes more than
one page, use the page navigation bar at the bottom of the list to navigate
between the pages.

For each profile, the list displays the following information.

Table 5-15 Profile List

Parameters for User and Field Description
Trunk Group Profiles
Name The name of the profile

Description An optional description of the profile

Managing Profiles

CUG The Closed User Group associated with the profile (see Closed User
Groups (CUG), page 4-29)
5

5-84 Profiles Aeonix Administration Manual

 From this page, you can perform the following actions:

Table 5-16 Actions

Performed from a User or Action Button / Icon Description
Trunk Group Profile List
Page Add profile Click Add to add a new profile.
For a description of the procedure, see the section
relating to the relevant profile type:
 Defining a User Profile, page 5-86
 Defining a Trunk Group Profile, page 5-88

Update In the list, click the profile name to update the details
—
profile of this profile.
Delete profile Select the check box next to the profile or profiles to
be deleted and then click Delete (see Deleting Entities,
page 3-66).

NOTE: Profiles assigned to users or to trunk groups

cannot be deleted.
Access Click Help to receive online help.
online help

Clone profile Click this icon to create a duplicate of a specific

profile.

Managing Profiles
5

Aeonix Administration Manual Profiles 5-85

  Defining a User Profile

To add or update a user profile:

1 On the User Profile List page (see Figure 5-32), do one of the following:
 To create a new user profile, click Add.
 To update an existing user profile, select it from the list.
 To create a new user profile based on the settings of an existing one, click
(the Clone icon) to the right of the relevant profile.

When you clone a user profile, all parameter values are copied to the new
profile except for the profile name and the Closed User Group.

The relevant User Profile page is displayed.

Figure 5-34 User Profile

Page for a New Profile
Managing Profiles

2 If this is a new profile, enter its name in the Name box.

5

5-86 Profiles Aeonix Administration Manual

 The Name cannot be modified for an existing profile.

3 In the Description box, enter a description of the profile (optional).

4 For any of the listed sub-profile types (except for phone profiles), do the
following as required:
 Select the relevant sub-profile from the drop-down list. (Initially, the default
sub-profile is assigned.)
 Select the Allow Override check box to allow overriding of sub-profile
values for a user, or clear this check box to make the override impossible.

The Administration Level sub-profile cannot be overridden.

Before sub-profiles (except for the default sub-profiles) can be selected, they
must be defined in the system as described in Managing Sub-profiles, page 5-3.

5 Select the Phone Profiles check box to allow overriding of phone profiles for
a user, or clear this check box to make the override impossible.
6 To replace a phone profile:
a In the Phone Profiles box, select the assigned phone profile for the relevant
phone type. (If this is a new user profile, this is the relevant default phone
profile.)
b Click Replace and select the required phone profile from the drop-down list
that is displayed under the box.
c Click OK.

Before phone profiles (except for the default phone profiles) can be selected,
they must be defined in the system as described in Phone Profiles, page 5-54.

7 Click Save. The profile is displayed in the list on the User Profile List page.
Managing Profiles
5

Aeonix Administration Manual Profiles 5-87

  Defining a Trunk Group Profile

To add or update a trunk group profile:

1 On the Trunk Group Profile List page (see Figure 5-33), do one of the
following:
 To create a new trunk group profile, click Add.
 To update an existing trunk group profile, select it from the list.
 To create a new trunk group profile based on the settings of an existing one,
click (the Clone icon) to the right of the relevant profile.

When you clone a trunk group profile, all parameter values are copied to the
new profile except for the profile name and the Closed User Group.

The relevant Trunk Group Profile page is displayed.

Figure 5-35 Trunk Group

Profile Page for a New
Profile

2 If this is a new profile, enter its name in the Name box.

The Name cannot be modified for an existing profile.

3 In the Description box, enter a description of the profile (optional).

Managing Profiles

4 For any of the listed sub-profile types, do the following:

 Select the relevant sub-profile from the list. (Initially, the default sub-profile
is assigned.)
 Select the Allow Override check box to allow overriding of sub-profile
values, or clear this check box to make the override impossible.
5

5-88 Profiles Aeonix Administration Manual

 Before sub-profiles (except for the default sub-profiles) can be selected, they
must be defined in the system as described in Managing Sub-profiles, page 5-3.

5 Click Save. The profile is included in the list on the Profile List page.

Managing Profiles
5

Aeonix Administration Manual Profiles 5-89

NOTES:
 5.4 Managing Provisioning Profiles

Provisioning profiles contain parameters used to automatically configure Tadiran SIP

phones, P-Series phones, and Tadiran TGW gateways. Defining a new Provisioning
profile includes specifying SIP server and time parameters, as well as specifying
whether the profile is associated with a customized set of configurations (optional).

Changing the “Default Provisioning Profile” is not allowed in an A4C

instance.

To take advantage of this on boot up, the DHCP server must have option 66
set to the hostname or IP address of the Aeonix server (it is recommended to
use the hostname for redundancy purposes).

Provisioning profiles are managed from the Provisioning Profile List Page. Managing
Auto Provisioning profiles includes the following procedures:
 Provisioning Profile List Page, page 5-92
 Defining a Provisioning Profile, page 5-94

Managing Provisioning Profiles

5

Aeonix Administration Manual Profiles 5-91

  Provisioning Profile List Page

The Provisioning Profile List page displays the provisioning profiles defined in the
system.

To open this page:

1 On the navigation pane, click Settings. The pane displays the Settings menus.
2 Select the Profiles menu, and then click Provisioning Profile List.

Figure 5-36 Provisioning

Profile List Page

The provisioning profile list is sorted by the Name column. If the list includes
more than one page, use the page navigation bar at the bottom of the list to
navigate between the pages.

For each provisioning profile, the list displays the following information.

Table 5-17 Provisioning

Profile List Parameters Field Description

Name The name of the provisioning profile

SIP Server The IP address (IPv4 or IPv6) or host name of the Aeonix
Address server on which the provisioning service is hosted and to
which phones send all requests

P-Series The P-Series configuration set associated with this

Configuration Set provisioning profile
Managing Provisioning Profiles

Tadiran SIP The Tadiran SIP phones configuration set associated with
Phones this provisioning profile
Configuration Set
5

5-92 Profiles Aeonix Administration Manual

 Provisioning Profile List Page Actions
From the Provisioning Profile List page, you can perform the following actions:

Table 5-18 Actions

Performed from the Action Button / Icon Description
Provisioning Profile List
Page Add Click Add to add a new provisioning profile
provisioning (see Defining a Provisioning Profile, page 5-94).
profile
Update In the list, click the provisioning profile name to
provisioning — update the details of this profile.
profile
Delete Select the check box next to the provisioning profile
provisioning or profiles to be deleted and then click Delete
profile (see Deleting Entities, page 3-66).
Access Click to receive online help.
online help

Managing Provisioning Profiles

5

Aeonix Administration Manual Profiles 5-93

  Defining a Provisioning Profile

To add or update a provisioning profile:

1 On the Provisioning Profile List page (see Figure 5-36), do one of the
following:
 To create a new provisioning profile, click Add.
 To update an existing provisioning profile, select it from the list.
The relevant Provisioning Profile page is displayed.

Figure 5-37 Provisioning

Profile Page for a New
Profile
Managing Provisioning Profiles

On this page, you can perform the following actions:

2 If this is a new provisioning profile, enter its name in the Name box.

The Name cannot be modified for an existing profile.

3 In the Description box, enter a description of the profile (optional).

5

4 Set or view the Topology parameters as described in the following table.

5-94 Profiles Aeonix Administration Manual

Table 5-19 Topology
Parameters Option Field Description

Device Local The device is connected on the same

placement network as the server.
relative to
Aeonix Remote via SBC The device is connected via a B2BUA
proxy such as an SBC.

NOTE: When this option is selected, the

radio buttons for SIP server /
Registrar options Aeonix and
SBC / Other are removed. When
you choose the Remote via SBC
option, you must define both an
Aeonix server and an SBC /
other server.

Remote via The device is connected via Outbound

outbound proxy Proxy.

5 Set or view the profile’s Primary and Secondary servers parameters as

described in the following table.

Table 5-20 Primary and

Secondary Servers Option Field Description
Parameters
SIP server / Aeonix (default) The IP address (IPv4 or IPv6), host
Registrar name, or DNS name of the Aeonix
server on which the phones register. To
assign a specific server, select Aeonix
and then select the required server from
the drop-down list that appears.
Enter the SIP port of the Aeonix server
on which the phones are registered on
(by default 5060, or, when transport
protocol TLS is used, secured port
5061).

Managing Provisioning Profiles

NOTE: It is recommended to use the DNS
name option for redundancy
purposes.

SBC / Other The IP address (IPv4 or IPv6), host

name, or DNS name of the SBC or other
server on which the phones register. The
Port field must be filled in, with a
validated range 1 - 6500.
5

Aeonix Administration Manual Profiles 5-95

 Option Field Description

ESF Server The IP address (IPv4 Registrar: Default, cannot be changed.

or IPv6), host name, Port: Displays 8080 / 8443. The value is
or DNS name of the set per endpoint in the User Feature
ESF server on which page.
the phones register.

Directory ESF Server Registrar: Default, cannot be changed.

Server Port: 389. Default, cannot be changed.

Other Server: The IP address (IPv4 or IPv6),

host name, or DNS name of the server
on which the phones register.
Port: Enter any port 1 - 65636

NTP Server The IP address (IPv4 There is no validation.

or IPv6), host name,
or DNS name of the
server on which the
phones register.

6 Set or view the profile’s time parameters as described in the following table.
7 Set or view the profile’s Network VLAN parameters for Tadiran SIP phones,
as described in the following table.

The Network VLAN parameters are only applicable for Tadiran SIP phones.

Table 5-21 Network VLAN

Parameters Option Field Description

WAN Port Active Select Yes to enable VLAN setting for

the WAN port
Managing Provisioning Profiles

VID (1-4094) Enter the WAN port VLAN ID

Priority Select the WAN port VLAN ID priority (1

to 7)

DHCP VLAN Active Select Yes to enable the WAN port VLAN
setting from DHCP server

Option (0-255) Enter the DHCP option for DHCP

request.
5

NOTE: The default is 132.

5-96 Profiles Aeonix Administration Manual

 Option Field Description

PC Port Active Select Yes to enable the PC port VLAN

setting from DHCP server

VID (1-4094) Enter the PC port VLAN ID

Priority Select the PC port VLAN priority (1 to 7)

8 View the Tadiran SIP phones profile’s default firmware versions:

Table 5-22 Tadiran SIP

Phones Firmware Field Description
Parameters
Maximum Enter the quantity for batch processing of phone firmware
simultaneous upgrades. The default is 20. If the limit is reached, any
firmware upgrades additional phones requiring firmware upgrade will be
serviced in a subsequent batch.

Managing Provisioning Profiles

5

Aeonix Administration Manual Profiles 5-97

 Field Description

T19P Default: Use the default firware version which is delivered

and installed with the Aeonix upgrade version.
T19P E2 Custom: You can load customized firmware versions for
testing purposes using an SSH program such as WinSCP
T21P E2 and store them in the Aeonix directory under
/home/aeonixadmin/aeonix/webadmin/webapps/aeonix/Pro
T23G visioning. Click Custom and enter the file name of the
relevant custom firmware version
T27P Firmware name: The name of the firmware file used for
this phone type.
T29G NOTE: T19P supports up to firmware 31.7x.19.x.
T19P E2 supports firmware 31.8x.19.x and higher.
T320

T322

T328

T40G

T41P

T41S

T42G

T42S

T46G

T46S

T48G
Managing Provisioning Profiles

T48S

T49G

T58V
5

5-98 Profiles Aeonix Administration Manual

 When the Aeonix software version is upgraded, all custom firmware versions are
reverted to their default settings.

9 View the Tadiran TGW profile’s default firmware versions:

Table 5-23 Tadiran TGW

Firmware Parameters Field Description

Maximum Enter the quantity for batch processing of phone firmware

simultaneous upgrades. The default is 20. If the limit is reached, any
firmware upgrades additional phones requiring firmware upgrade will be
serviced in a subsequent batch.

TGW 8-2G Default: Use the default firware version which is delivered
and installed with the Aeonix upgrade version.
TGW 16-3G Custom: You can load customized firmware versions for
testing purposes using an SSH program such as WinSCP
TGW 24-3G and store them in the Aeonix directory under
/home/aeonixadmin/aeonix/webadmin/webapps/aeonix/Pro
TGW 96-2G visioning. Click Custom and enter the file name of the
relevant custom firmware version
TGW x E1-2G Firmware name: The name of the firmware file used for
this TGW type.

10 View and set the profile’s Tadiran TGW Time-Division Multiplexing (TDM)
parameters:

Table 5-24 Tadiran TGW

Time-Division Field Description

Managing Provisioning Profiles

Multiplexing Parameters
Interface Choose the TGW interface: E1 orT1.

PCM Encoding Choose the PCM encoding: A-Law or u-Law.

Signaling Standard Choose the signaling standard: CCITT, NI2, DMS100, or

DMS250:

Timeslot search Choose the timeslot search mode: FORWARD,

mode BACKWARD, or CIRCULAR.
5

Aeonix Administration Manual Profiles 5-99

 11 Set or view the profile’s Advanced parameters as described in the following
table.

Table 5-25 Advanced

Parameters Field Description

Location Associates Aeonix Touch devices sharing the selected

location with this provisioning profile.
Aeonix Touch devices use the SIP server or SBC to
connect to Aeonix.

NOTE: Aeonix Touch devices that are not associated

with any provisioning profile will be associated
with the Default Provisioning Profile.

Dial now rules The dial plan from which to apply the phone’s dial now
rules to the provisioning profile (see Dial Plans, page 4-19).

NOTE: Select Auto-Detect if you want to apply the dial

plan of the CUG with which the user is
associated.

LCD logo mode The logo setting for the phones, as follows:
 System logo intermittently displays the Aeonix logo
on the phones’ screen during idle.
 Custom logo if you want to use a different logo,
such as a company logo.
 Disabled displays no logo on the phones (default
option).

NOTE: Only applicable for supported Tadiran SIP

phones.

High availability retry The number of times the phone attempts a request
count before switching to another Aeonix server in the cluster.

NOTE: Only applicable for Tadiran SIP phones.

Trusted IP addresses For security purposes, select Aeonix servers to allow

for Action URI Tadiran SIP phones to only connect with Aeonix
Managing Provisioning Profiles

servers. Alternatively, to also allow connection to the

Sea Navigator, select Any.

NOTE: Only applicable for Tadiran SIP phones.

P-Series configuration The customized P-Series configuration set associated

set with this provisioning profile

Tadiran SIP phones The customized Tadiran SIP phones configuration set
configuration set associated with this provisioning profile
5

TGW configuration set The customized TGW configuration set associated with
this provisioning profile

5-100 Profiles Aeonix Administration Manual

 To learn how to define additional configuration sets, see Defining New
Configuration Sets, page 12-130.

12 Click Save. The profile is displayed in the list on the Provisioning Profile List
page.

Provisioning definitions will take effect after the phone's next configuration
check.

Managing Provisioning Profiles

5

Aeonix Administration Manual Profiles 5-101

Managing Provisioning Profiles
5

5-102 Profiles Aeonix Administration Manual

 Chapter 6

Managing Users

6.1 Users ....................................................................................6-1

6.2 Defining a User .....................................................................6-9

6.3 Importing / Exporting Users ................................................6-79

6.4 Importing LDAP Users ........................................................6-87

6.5 Associating Users with Groups...........................................6-93

6.6 Aeonix Clients for Users .....................................................6-99

Aeonix Administration Manual

 6.1 Users

A user is a person using a telephone or another device in the Aeonix system to make
and receive calls. A user usually has one or more unique alias numbers defined (see
Chapter 11, Managing Aliases) and is assigned to one or more phones (see Chapter 7,
Managing Phones).

Aeonix trunk groups are very similar to users but refer to gateways and IP
trunks connected to Aeonix. See Chapter 9, Managing Trunk Groups for
details.

The users available in the system are listed on the User List Page. Managing users
includes the following procedures:
 Defining a User, page 6-9
 Importing / Exporting Users, page 6-79
 Importing LDAP Users, page 6-87
 Associating Users with Groups, page 6-93

Users
6

Aeonix Administration Manual Managing Users 6-1

  User List Page

The User List page is automatically displayed to administrators:

 After logging in to the Aeonix Web Portal (see Logging in to Aeonix, page 3-8)
 After clicking Administration on the navigation pane

Figure 6-1 User List Page

The User List page displays the existing users in the system. It also contains an area
(click Search to display this area) in which search criteria can be defined to find and
display specific users.
The users listed with a green circle icon are currently logged into the system. Click
Refresh to manually update the list.

The status icons on this page automatically refresh every minute.

The user list is sorted by the Login Name column. If the list includes more than one
page, use the page navigation bar at the bottom of the list to navigate between the
pages according to the following table:

These navigation options are available on any list page that comprises more
than one page.

Table 6-1 Page

Navigation Options Button When To Use

To navigate to the next page

To navigate five pages forward

Users

To fast forward
6

6-2 Managing Users Aeonix Administration Manual

 Button When To Use

1... To navigate to a specific page within a range of up

to 10 pages. The currently displayed page is
indicated by a line below the number.

To navigate to the previous page

To fast rewind

To navigate to the first page

The list displays up to 10 rows by default. To change the number of rows

displayed, enter the number in the Rows per page field and click Set.

For each user, the list displays the following information.

Users
6

Aeonix Administration Manual Managing Users 6-3

 Table 6-2 User List
Parameters Field Description

Status icon A circle icon to the left of each user indicates the following:
(circle)  Green - the user is logged into Aeonix
 Red - the user is logged out

NOTE: View the specific icon’s tooltip for more information.

Login Name Unique identifier of the user. Typically, the worker ID or other
unique number or name is used.

Description A short description of the user (optional).

Display Name The name of the user as viewed by other users.

Also displayed as the contact’s name in the Aeonix Dispatch
Console Phonebook.

Alias Number or numbers associated with this user. An alias

number is dialed or entered to contact the user, regardless of
the user’s current location (see Chapter 11, Managing
Aliases).

Closed User The Closed User Group to which the user is assigned.
Group Closed User Groups are used for creating sub-groups of
users.

Sea Navigator / Is displayed for users that are allowed to use the
Sea Attendant Sea Navigator or Sea Attendant application on their desktop,
User icon that is, have the Sea Navigator or Sea Attendant check box
selected in their Feature Configuration profile.
Icons are displayed as follows:
 (Active Sea Navigator)—indicates that the Sea
Navigator is installed and running on the user’s desktop
 (Active Sea Attendant)—indicates that the Sea
Attendant is installed and running on the user’s desktop
To learn about how to install the Sea Navigator or Sea
Attendant, see Aeonix Clients for Users, page 6-99. Using the client
is described in the corresponding Online Help.
Users
6

6-4 Managing Users Aeonix Administration Manual

 User List Page Actions
From this page, you can perform the following actions:

Table 6-3 Actions

Performed from the User Action Button / Icon Description
List Page
Add user Click Add to add a new user (see Defining a User,
page 6-9).

Update user In the list, click the Login name to update the details
—
of this user.
Delete user Select the check box next to the user or users to be
deleted and then click Delete (see Deleting Entities,
page 3-66).
Refresh Click Refresh to update the list to the current status.
display

Access Click Help to access online help.

online help

Clone user Click this icon to create a duplicate of a specific

user.

Reset user’s Click to reset the password of this user to the default
password value (see Resetting a User’s Password, page 6-73).

NOTE: For administrators, the default password is

anx; for regular users, the default password is
automatically generated by the system, as
displayed on the System Parameters page
(see Figure 14-6, System Parameters Page).
Search for Click to display the Search area, define search
users values, and then click Apply to search for existing
users (see Searching for Users, page 6-6).
Click Reset to remove entered values from the
search configuration fields. This allows you to define
and start a new search.

Users
6

Aeonix Administration Manual Managing Users 6-5

 Searching for Users
In the Search area at the top of the user list, you can search for specific users using the
following search criteria:

Search Criteria Search Results

Login name Users that contain the specified search value in their
Login name field

Description Users that contain the specified text in their Description field

Display name Users that contain the specified search value in their Display
name field

Alias Users whose alias number contain the specified number

Closed User Users that belong to the specified Closed User Group
Group

User ID Users that contain the specified search value in their User ID
field

ULA owner Users that are ULA group owners

(when selected)

Navigator or Users that are allowed to use the Sea Attendant or

Attendant client Sea Navigator on their workstation
user
(when selected)

LDAP user from Users that were uploaded to Aeonix from the last LDAP
last import import.
(when selected)

Administrator Users that are administrators.

(when selected)

Click the Search bar to display the search fields and fill in one or more fields as
required. When you start filling in the Login name, Description, Display name,
Alias, or User ID, all existing entities containing the entered value are displayed
below the field. Select the required value (if available) or type it in.
Users
6

6-6 Managing Users Aeonix Administration Manual

Figure 6-2 User Search

Click Search to filter the display by the entered criteria. The User List will include all
users that have values corresponding to the search values or containing them in the
relevant fields. Example: If you enter jo in the User ID field and click Apply, users
with the user ID johns, major, 2jo3, and so on are displayed (provided these users are
defined in the system).

Users
6

Aeonix Administration Manual Managing Users 6-7

NOTES:
 6.2 Defining a User

The following procedure describes how to define a user in the Aeonix system.

Prior to addin g users, make sure Aeonix global settings and user profiles
are properly defined. See Chapter 4, Global Settings and Chapter 5, Profiles
for details.

To define a user:
1 In the navigation pane, click Administration. The pane displays the
Administration menus.
2 In the navigation pane, select the Users menu, and then do one of the
following:
 Option a
 Option b
 Option c
a To define a new user, click Add User. When you add a new user, an
indexing suffix is automatically attributed to the user in the following
format: User_x, where x is a running number. For example, when adding
the first user to the system, the Login name will be User_1. The next Login
name will be User_2, and so forth.
In addition to the Login name, the following parameter field values are
automatically filled in by the system when adding a new user:

Table 6-4 Predefined User

Fields Field Value
Defining a User

User ID Same as Login name field

Display name Same as original Display name field

Closed User Group Root

6

Aeonix Administration Manual Managing Users 6-9

 Field Value

Profile Default User Profile

b To update an existing user, click User List. On the User List page, click the
Login name of the relevant user.
c To create a new user based on the settings of an existing one: From the
User List page (see Figure 6-1), click (the Clone icon) to the right of
the relevant user; a new page is opened for creating a cloned entity. An
indexing suffix is automatically added to the user. For example, if the
original Login name is Mike, the cloned user’s Login name will be Mike_1.
In addition to the Login name, the following fields and tabs are
automatically cloned by the system when cloning a user: Display name,
Closed User Group, Profile, First name, Last name, User ID,
Description, PIN, Dispatch user, Profiles tab, and Permissions tab.

The remaining fields and tabs are not cloned. For example, the Aeonix
Contact Center agent number field is a unique number used to identify the
agent and cannot be cloned.

The User page is displayed.

Defining a User
6

6-10 Managing Users Aeonix Administration Manual

Figure 6-3 User Page

3 Fill in the fields to define the general and identity settings of the user
(see Defining User Identity Settings, page 6-14).
4 Optionally set a photo for the user (see Uploading a User Profile Photo,
page 6-18).
5 Specify the user’s internal alias numbers (see Assigning Aliases to Users,
page 6-19).
6 Create a mailbox for the user (see Managing Voicemail Boxes for Users,
page 6-24).
Defining a User

7 Specify external numbers, such as cellular phone or home phone numbers and
outside line access code prefix setting (see Specifying External Phone Numbers,
page 6-27).
8 Customize the profile values as required (see Overriding User Profiles, page 6-29).
6

This includes, among many others, call routing and forwarding definitions.

Aeonix Administration Manual Managing Users 6-11

 9 Optionally configure the default phone profile or add phone profiles for
specific phones defined in the system. This includes configuring phone buttons
and more (see Configuring a User’s Phone Profiles, page 6-49).
10 Define one or more phones for the user (see Managing a User’s Phones,
page 6-56).
11 Optionally set up mobility rules for remote access to internal system services
(see Configuring Mobility Rules for a User, page 6-62).
12 Optionally define the user as the owner of a ULA group (see Managing a User’s
ULA Settings, page 6-65).
13 Optionally set the access code to a meet-me conference alias if the user has
been defined as the owner of this number (see Setting the Meet-me Conference
Access Code, page 6-72).
14 If necessary, reset the user password for accessing the Aeonix Web Portal
(see Resetting a User’s Password, page 6-73).
15 Optionally define permission settings for the user (see Defining Permission
Settings, page 6-74).
16 Click Save. The user is added to the user list.

Alternatively, if you want to save and clone the current user, click
at the bottom of the page; a new page is opened for
creating a cloned entity, where an indexing suffix is automatically added to
the user’s Login name. For example, if the original Login name is Mike, the
cloned user will be Mike_1 (as described above).

Verifying Proper Setup

After configuring a user and the user’s phone to work with Aeonix, check the
following basic points:
 Aeonix Web Portal
 On the User List page (see Figure 6-1), a green circle icon to the left of the
user indicates that this user is logged into the system. For a description of
Defining a User

how to quickly locate the user entry in the list, see Searching for Users,
page 6-6.
 On the user’s Phones tab (see Figure 6-22), a green circle icon to the left of
the user’s phone indicates that it is working (registered in Aeonix).
The user’s phone
6

 The phone can be used to make and receive calls.

6-12 Managing Users Aeonix Administration Manual

  Voicemail messages can be heard, sent, and managed from the phone.
 The phone display shows the current time and date, the user’s alias or
display name, and defined soft key options.

Defining a User
6

Aeonix Administration Manual Managing Users 6-13

  Defining User Identity Settings

General user settings are defined in the upper part of the User page; user identity
parameters are defined under the Identity & Aliases tab. The following table
describes these parameters.
Defining a User
6

6-14 Managing Users Aeonix Administration Manual

Table 6-5 General and
Identity Parameters for Field Description
Users
Login name Unique identifier of the user. Typically, the worker ID, name
of the worker, or some other unique number.
It is used by the Aeonix user to log in to the Aeonix Web
Portal, as well as for logging in to other Aeonix applications,
such as Aeonix Touch.

NOTE: When this field is defined for a new user, its value is
retained as the User ID (see below) of the user.

Display name Name of the user as it is shown on the display panel of the
phone or phones associated with the user. This name is
also displayed at the other phone when calling another user
and as the contact’s name in the Aeonix Dispatch Console
Phonebook.
When this field is defined for a new user, there is an option
to use this name as the first and last name of the user. In
this case, use a space to separate the display name into two
names. The system will automatically fill in the First name
and Last name fields below with these names once you
click Save, provided that you leave these fields blank.

NOTE: If you do not use a space as a separator, the name will

be filled in the First name field only.
Conversely, you can leave the Display name field blank and
enter the names in the First name and Last name fields;
the system will automatically copy these names as the
user’s display name.

NOTE: For phones that can be assigned a phone profile, a

value in the field Local display overrides the Display
name of the phone (see Configuring a User’s Phone
Profiles, page 6-49).

Closed User The Closed User Group to which the individual belongs
Group (see Closed User Groups (CUG), page 4-29).
(Default: Root)
NOTE: This field cannot be modified after the user is added to
the system.

Profile The profile assigned to the user. Assigning another profile

(Default: Default resets the Profile values of the user to the default values of
User Profile) the new profile. For more information, see Chapter 5,
Defining a User

Profiles and Overriding User Profiles, page 6-29.

First name First name of the user (optional).

NOTE: If you want this name to be automatically copied to the

display name, leave the Display name field blank.
6

Aeonix Administration Manual Managing Users 6-15

 Field Description

Last name Last name of the user (optional).

NOTE: If you want this name to be automatically copied to the

display name, leave the Display name field blank.

Email The email address of the user. This is required for Aeonix
Touch clients to sign into the Aeonix Touch server and for
Aeonix Touch presence purposes.

Description Short description of the user (optional).

Display in Clear if you do not want the system to include the user in
directory (Default: the Aeonix directory.
selected)

The profile photo assigned to the user (see Uploading a User

Profile Photo, page 6-18).

PIN A numeric password consisting of 6-12 digits. Together with

the user’s alias, the PIN is required for user authentication
by phone, such as for callback and call-through.
In the Retype PIN box, enter the PIN again for verification.

User ID Unique ID for the user derived from the login name when
(read-only) defining a new user (see above).
It is used by Aeonix to identify the user when it
communicates with other applications.

NOTE: Once the user ID is set, it cannot be modified.

Dispatch user Select to define the user as a Dispatch user, and then select
the permission level for the user:
 User: The user can use the Aeonix Dispatch Console
 Admin: The user can configure the Aeonix Dispatch
Console grid and buttons
 Super Admin: The user can, in addition to configure the
Aeonix Dispatch Console, set up the first install instance
of the Aeonix Dispatch Console

NOTE: For more information, see Defining Dispatch Consoles,

page 12-103.
Defining a User
6

6-16 Managing Users Aeonix Administration Manual

 Field Description

Allow automatic NOTE: This option is only applicable to Dispatch users and is
tab selection only displayed if the Dispatch user option above is
selected.
Select if you want the grid on the Dispatch Console to
automatically display the tab on which the incoming call to
this user is defined in the Dispatch Console;

NOTE: If the caller is programmed on more than one tab, the

console will activate the first tab that contains that
caller.
If this check box is cleared, the tab will flash, instead of
being displayed, to indicate that there is an incoming call on
that tab.

Aeonix Contact Unique number used to identify the user as an Aeonix

Center agent Contact Center agent (corresponds to the agent number in
number (for the Aeonix Contact Center).
PC-less agent
only)

Defining a User
6

Aeonix Administration Manual Managing Users 6-17

  Uploading a User Profile Photo

You can upload a photo, which will be included as part of the user’s profile entry in
the phonebook.

To avoid aspect ratio distortion, ensure the photo is square (height and width
are equal). You can use any graphic editor program to resize your photo.

To add or change an Aeonix user profile photo:

1 On the User page, click the Identity & Aliases tab (see Figure 6-5).
2 Click or on the existing photo; the Change Photo dialog box is
displayed.

Figure 6-4 Change Photo

dialog box

3 Select Upload photo, click Choose File, and then use the displayed dialog
box to locate the required photo (in JPG, PNG, or GIF format).

Alternatively, select Delete photo if you want to remove the photo from the
Defining a User

user’s profile.

4 Click OK. The photo is uploaded to Aeonix.

5 Click Save.
6

6-18 Managing Users Aeonix Administration Manual

  Assigning Aliases to Users

An alias is a number (“extension”) assigned to a user or other entity. This number is

the internal call number of the user. Which of the user’s devices will ring is specified
in the user’s incoming call routing rules (see Incoming Call Routing Sub-profiles,
page 5-31).
This section describes the following procedures:
 Defining an Alias for a User, page 6-19
 Deleting a User’s Alias, page 6-22
 Setting the Default Alias for a User, page 6-22

An already used alias cannot be assigned to a new user. View the already
assigned aliases on the Alias Lists page as described in Chapter 11,
Managing Aliases. In addition, the alias number must follow the patterns
defined in the applicable dial plan (see Dial Plans, page 4-19).

Defining an Alias for a User

You can add one or more aliases for the same user; however, a specific alias can be
assigned only to one entity. This entity is a user, a trunk group, or a service.

Make sure that the alias number to be assigned is not already in use and
complies with the patterns of the applicable dial plan.

To assign a new alias to a user or modify an existing alias:

1 On the User page (see Figure 6-3), click the Identity & Aliases tab.

Defining a User
6

Aeonix Administration Manual Managing Users 6-19

 Figure 6-5 Identity &
Aliases Tab—Aliases

2 To the right of the Aliases box, click Add, or select an existing alias in the
box and click Update. The Alias Configuration page is displayed on the User
page.

Figure 6-6 Alias

Configuration Page for
Users
Defining a User
6

6-20 Managing Users Aeonix Administration Manual

 3 Select the alias type (usually Complete for a user) and define the alias as
follows:

Type Description

Complete Use to define a specific alias number.

 Enter the number in the Alias text box.

NOTE: You can click Suggest available aliases to view a list of

available aliases and alias ranges.

NOTE: The alias number must consist of at least three digits.

 Enable inter-group access - currently not in use
Use Call preemption to define the call priority and behavior used
when this alias is dialed. Prioritized calls cause calls with a lower
priority to be dropped when the call is of higher precedence than
routine calls.
 From the Priority drop-down list, select the priority of the call.
 From the Action drop-down list, select the action to be taken when
the alias is busy or non-answering (only available when Medium,
High, or Urgent is selected from the Priority drop-down list).

NOTE: For more information, see Call Preemption, page 2-13.

Range Use to define a range of numbers used to reach the user.

 Enter the lowest number of the range in the Start of range box.
 Enter the highest number of the range in the End of range box.

Prefix Use to define prefix digits and route all aliases beginning with this
prefix to the user.
 Select Prefix and enter the prefix in the text box.
 Select Limit length and enter a number to restrict the amount of
digits, including the prefix, that can be dialed to reach the user
associated with this alias.

NOTE: When a call is placed to a prefix alias number, the system

automatically removes the prefix digit or digits.

The type of an existing alias cannot be modified.

Defining a User

4 Click OK.
5 Click Save.
6

Aeonix Administration Manual Managing Users 6-21

 Aeonix searches for an alias number in the following order:
 It tries to find a number matching a complete alias.
 If no match is found, the system checks if the number falls into a defined alias
range.
 If still no match is found, the system checks whether the number has a prefix
that matches one of the defined alias prefixes.

Deleting a User’s Alias

To delete an alias:
1 On the User page, click the Identity & Aliases tab (see Figure 6-5).
2 In the Aliases box, select the alias number and click Delete. The alias is
removed from the box.
3 Click Save to delete the alias.

If you delete an alias number that has a voicemail box assigned, the mailbox
is also deleted.

Setting the Default Alias for a User

When assigning an internal alias to a user, it is automatically set as the default alias so
that it can be used for identifying the user when dialing out, for example, to the
voicemail system. Likewise, when creating a new voicemail box for a user (see
Creating a Mailbox for a New User, page 6-25), the default alias is automatically associated
with the mailbox. When more than one alias is assigned to a user, do the following to
assign a different alias as the default alias.

To set another default alias for a user:

1 On the User page, click the Identity & Aliases tab (see Figure 6-5).
2 In the Aliases box, select the alias number and click Set Default. The alias is
Defining a User

marked as the new default alias (see alias 2002 in the example below).
6

6-22 Managing Users Aeonix Administration Manual

Figure 6-7 New Default
Alias

3 Click Save to save this as the default alias.

If an alias range is selected as the default, the first alias in the range is
assigned as the default alias.

Defining a User
6

Aeonix Administration Manual Managing Users 6-23

  Managing Voicemail Boxes for Users

You can create a voicemail box for the first complete alias number of a new user. This
voicemail box is automatically removed from the system if the alias number is deleted.
You can also delete only the voicemail box.
This section describes the following procedures:
 Creating a Mailbox for a New User, page 6-25
 Deleting a Mailbox, page 6-26

For instructions on how to create voicemail boxes for existing users, to

modify voicemail boxes, or to create voicemail boxes for additional alias
numbers, refer to the SeaMail Administration and Configuration Manual
for Aeonix (see Related Documentation, page 1-17).
Defining a User
6

6-24 Managing Users Aeonix Administration Manual

 Creating a Mailbox for a New User

To create a voicemail box for a new user:

1 On the User page of a new user (see Figure 6-3), click the Identity & Aliases
tab.

Figure 6-8 Identity &

Aliases Tab—Create
Voice mail Box

2 Select the required service from the Voicemail service drop-down list.
3 Select the adjacent Create mailbox check box.

 A voice mail box can only be created if the user has at least one complete
alias number assigned.
 The default alias is automatically associated with the mailbox (see Setting
the Default Alias for a User, page 6-22).
Defining a User

 Ensure that a corresponding mailbox is defined at the user’s selected

voice mail service. The default mailbox password is 0000.

4 Click Save.
6

Aeonix Administration Manual Managing Users 6-25

 Deleting a Mailbox

To delete a user’s voice mail box:

1 On the User page, click the Identity & Aliases tab.
2 Select Delete voice mail box under the Aliases box.
3 Click Save. The voice mail box is deleted from the system.
Defining a User
6

6-26 Managing Users Aeonix Administration Manual

  Specifying External Phone Numbers

External phone numbers belong to phones that are not located in the organization, such
as a user’s cellular phone or home phone.
Specifying the external phone numbers is necessary for making use of the Multiple
Devices per User (FlexiCall) feature. This feature allows a user to have an incoming
call ring simultaneously on the user’s internal and external devices until the call is
answered.
This section describes the following procedures:
 Specifying an External Phone Number for a User, page 6-28
 Deleting a User’s External Number, page 6-29

Defining a User
6

Aeonix Administration Manual Managing Users 6-27

 Specifying an External Phone Number for a User
You can specify one or multiple external phone numbers for the same user.

To define or modify an external number:

1 On the User page (see Figure 6-3), click the Identity & Aliases tab.

Figure 6-9 Identity &

Aliases Tab—External
Numbers

2 To the right of the External Numbers box, click Add, or select a number in
the box and click Update.
3 In the External number box, enter the external number as dialed from the
user’s default location.
To enter a full number with prefixes and suffixes, add + (the Plus sign) at the
beginning of the number.
4 Click OK. The number is added to the External Numbers box.
5 Clear the Add outside line access code prefix check box if you do not want
Defining a User

the system to add the outside line access code when placing calls to external
numbers (selected by default).
6 Click Save.
6

6-28 Managing Users Aeonix Administration Manual

 Deleting a User’s External Number

To delete an external number:

1 On the User page, click the Identity & Aliases tab.
2 In the External Numbers box, select the external number and click Delete.
The number is removed from the box.
3 Click Save.

 Overriding User Profiles

A user profile consists of several assigned sub-profiles, one for each sub-profile type.
A sub-profile includes a set of content-related parameters. Whether a sub-profile can
be overridden for a specific user, depends on the definition of the profile assigned to
this user. Profiles and sub-profiles are described in detail in Chapter 5, Profiles.
By default, a new user is assigned the Default User Profile and the sub-profiles related
to this profile. The user’s profile assignment and sub-profile values can be modified
as described in the following sections:
 Assigning a Profile to a User, page 6-30
 Replacing a User’s Sub-profiles, page 6-30
 Overriding Sub-profile Parameter Values, page 6-33

Modifications in a user’s profile setup are indicated as follows on the user’s

Profiles tab:
 Replaced sub-profiles are displayed in red.

 Sub-profiles with overridden parameter values are marked as

overridden.

Defining a User
6

Aeonix Administration Manual Managing Users 6-29

 Assigning a Profile to a User
Each user is assigned one of the user profiles defined in the system. On the User page,
you can replace the assigned profile by selecting another profile from the Profile
drop-down list (see Defining User Identity Settings, page 6-14). The sub-profiles assigned
to the user are replaced with the sub-profiles of the new profile.

Replacing a User’s Sub-profiles

By default, a user’s sub-profiles, which are displayed under the Profiles tab
(see Figure 6-10), are taken from the profile assigned to the user. For example, if a user
is assigned the Default User Profile, its sub-profiles are automatically applied to this
user and profile updates reflected in the user’s settings.
Replacing a sub-profile means breaking, for this user, the link between this sub-profile
and the profile. This means that the sub-profile remains linked to the user even if
another sub-profile is assigned to the user’s profile. However, modifications of the
sub-profile are still reflected in the relevant user parameters.
You can change the General Information, Timeout, Feature Configuration, Toll
Barrier, Schedule, Incoming Call Routing, and Outgoing Call Routing sub-profile
assignment of a specific user as described in Replacing a Sub-profile, page 6-31 (for
phone profiles see Configuring a User’s Phone Profiles, page 6-49).

You cannot change the Administration Level of a specific user. However, you
can set full administrator rights for the user (see Viewing Administration Level
Parameters, page 6-44).

If necessary, a sub-profile replacement can be cancelled and the link between the
user’s profile and the sub-profile recreated (see Canceling a Sub-profile Replacement,
page 6-32).
Example: Mr. Smith, a software programmer, is assigned the R&D profile, which
includes the R_D Timeout sub-profile. When he has to join a two-week conference
abroad, the Aeonix administrator replaces his R_D Timeout sub-profile with the Sales
Timeout sub-profile. After Mr. Smith comes back, the administrator cancels the
Defining a User

change. (This example is based on the profile structure defined in Profile Definition
Example, page 5-2.)
6

6-30 Managing Users Aeonix Administration Manual

 In addition to overriding sub-profile assignments, individual sub-profile
parameters can be overridden as well (see Overriding Sub-profile Parameter
Values, page 6-33).
A sub-profile cannot be replaced if its Allow Override option is disabled in the
assigned profile (see Managing Profiles, page 5-83).

Replacing a Sub-profile
The following procedure describes how to modify a user’s sub-profile assignment. To
learn about how to override specific sub-profile parameters, see Overriding Sub-profile
Parameter Values, page 6-33.

A sub-profile cannot be replaced if override permissions are denied.

Sub-profile override permissions are set in the profile assigned to the user
(see Managing Profiles, page 5-83).

To replace a user’s sub-profile (except for Administration Level profiles):

To learn how to replace a user’s phone profiles, see Configuring a User’s Phone
Profiles, page 6-49.

1 On the User page (see Figure 6-3), click the Profiles tab.

Figure 6-10 Profiles Tab

Defining a User
6

Aeonix Administration Manual Managing Users 6-31

 2 Click the sub-profile to be replaced. The parameters of the sub-profile are
displayed for the user, as in Figure 6-11 for the General Information
sub-profile.
3 Select the Change sub-profile check box. The sub-profile fields are enabled.

If the Change sub-profile check box is disabled, the profile assigned to the
user does not allow modifications of this sub-profile.

4 From the drop-down list, select the required sub-profile.

5 Click OK. The Profiles tab displays the sub-profile replacement in red.
6 Click Save to apply the changes.

Canceling a Sub-profile Replacement

This procedure restores the link between the sub-profile and the profile associated
with the user. As prior to the replacement, the profile assigned to the user determines
which sub-profile is used.

To cancel a sub-profile replacement:

1 On the Profiles tab (see Figure 6-10), select the relevant sub-profile. (Replaced
sub-profiles are displayed in red.) The sub-profile parameters are displayed.
2 Clear the Change sub profile check box. The drop-down list is disabled and
displays the name of the sub-profile assigned to the user’s profile.
3 Click OK. The Profiles tab displays the sub-profile without red color-coding.
4 Click Save.
Defining a User
6

6-32 Managing Users Aeonix Administration Manual

 Overriding Sub-profile Parameter Values
A user’s default parameter values are defined by the sub-profiles of the profile
assigned to this user. Depending on the profile definition, you can override these
values.
Modifying the source sub-profile does not affect an overridden sub-profile parameter.
However, if the user is assigned another profile (see Assigning a Profile to a User,
page 6-30) the value is reset in accordance with the newly assigned profile. Overridden
parameter values are also reset if the sub-profile is replaced by another sub-profile.
Example: For Mr. Smith, the General Information parameters, including Time
Format, are defined by the Default General sub-profile. In the Default General
sub-profile, the value of Time Format is set to AM-PM. If, for Mr. Smith, this value
is overridden and changed to 24H, the change remains even if the parameter value is
modified in the Default General sub-profile source. If, however, Mr. Smith’s
sub-profile is replaced, the parameter is changed accordingly for Mr. Smith.
The following sections describe how to override sub-profile parameters:

You cannot override Administration Level parameters for a user. However,

you can set full administrator rights for the user (see Viewing Administration Level
Parameters, page 6-44).

 Overriding General Information Parameters, page 6-34

 Overriding Timeout Parameters, page 6-35
 Overriding Feature Parameters, page 6-36
 Overriding Toll Barrier Rules, page 6-37
 Overriding Schedules, page 6-39
 Overriding Incoming Call Routing Rules, page 6-40
 Overriding Outgoing Call Routing Parameters and Rules, page 6-43
The following sections describe how to cancel the parameter overrides:
 Canceling Overrides of General Information Parameters, page 6-46
 Canceling Overrides of Timeout Parameters, page 6-46
Defining a User

 Canceling Overrides of Feature Parameters, page 6-46

 Canceling Overrides of Toll Barrier Rules, page 6-47
 Reversing Schedule Overrides, page 6-47
Canceling Overrides of Incoming Call Routing Rules, page 6-47
6

Aeonix Administration Manual Managing Users 6-33

 Overriding and override canceling of phone profile parameters are described in
Configuring a User’s Phone Profiles, page 6-49.

Overriding General Information Parameters

To override a user’s General Information sub-profile parameters:

1 On the User page, click the Profiles tab (see Figure 6-10).
2 Click the General Information sub-profile. The user’s parameter values are
displayed.

Figure 6-11 User’s

General Information
Parameters
Defining a User

You can override the parameters of a sub-profile only if their Override check
boxes are enabled. Whether a sub-profile can be overridden is defined in the
profile assigned to the user (see Managing Profiles, page 5-83).

3 Select the Override check box next to the relevant parameters. The
parameters’ link to the source sub-profile is broken, and the parameters can be
6

modified as required.

6-34 Managing Users Aeonix Administration Manual

 For a description of the parameters, see Table 5-4.

4 Click OK. On the Profiles tab, an overridden comment is displayed after the
name of the sub-profile.
5 Click Save.

Overriding Timeout Parameters

To override a user’s Timeout sub-profile parameters:

1 On the User page, click the Profiles tab (Figure 6-10).
2 Click the Timeouts sub-profile. The parameters are displayed for the user.

Figure 6-12 User’s

Timeout Parameters

You can override the parameters of a sub-profile only if their Override check
Defining a User

boxes are enabled. Whether a sub-profile can be overridden is defined in the

profile assigned to the user (see Managing Profiles, page 5-83).

3 Select the Override check box next to the relevant parameters. The
parameters’ link to the source sub-profile is broken, and the parameters can be
modified as required.
6

Aeonix Administration Manual Managing Users 6-35

 For a description of the parameters, see Table 5-5.

4 Click OK. On the Profiles tab, an overridden comment is displayed after the
name of the sub-profile.
5 Click Save.

Overriding Feature Parameters

To override a user’s Feature Configuration sub-profile parameters:

1 On the User page, click the Profiles tab (see Figure 6-10).
2 Click the Feature Configuration sub-profile. The features are displayed.
3 Click one or more features to display the parameters of these features for the
user. (Click Toggle Panels to display hidden and hide displayed parameters).

Figure 6-13 User’s

Feature Parameters
Defining a User

You can override the parameters of a sub-profile only if their Override check
boxes are enabled. Whether a sub-profile can be overridden is defined in the
profile assigned to the user (see Managing Profiles, page 5-83).

4 Select the Override check box next to the relevant parameters. The
6

parameters’ link to the source sub-profile is broken, and the parameters can be
modified as required.

6-36 Managing Users Aeonix Administration Manual

 For a description of the parameters, see Table 5-6.

5 Click OK. On the Profiles tab, an overridden comment is displayed after the
name of the sub-profile.
6 Click Save.

Overriding Toll Barrier Rules

To override a user’s toll barrier rules:

1 On the User page, click the Profiles tab (see Figure 6-10).
2 Click the Toll Barrier sub-profile. The user’s toll barrier details are displayed.

Figure 6-14 A User’s Toll

Profile Details

Click the Base Toll Barrier toggle bar to display or hide the details of the toll
barrier sub-profile assigned to the user.

3 By default, the Change Method is set to None (view-only display). To make

changes:
 Select Extend to add new toll barrier patterns or to override existing
patterns.
 Select Override to define toll barrier rules from the beginning for this user.
Defining a User

The Basic behavior drop-down list below can only be modified if the
Change Method is set to Override.
6

Aeonix Administration Manual Managing Users 6-37

 4 From the Basic behavior drop-down list, select one of the following:
 Allow all calls to allow users to make outgoing calls to any destination
except for the destinations defined in the Do not allow calls to box below.
 Reject all calls to prevent users from making outgoing calls to any
destination except for destinations defined in the Allow calls to box below.

If Basic behavior is set to Reject all calls, the Do not allow calls to box is
not displayed. In this case, skip the following step and continue with Step 6.

5 Use the Do not allow calls to box to define numbering patterns (partial or
complete phone numbers) of destinations that users are not allowed to call.
Add new, update, or remove patterns as required:
 To add a pattern, click Add, enter the number in the displayed Pattern box,
and click OK. Use the X wildcard to represent any digit.
 To update a pattern, select it and click Update. Modify the number that is
displayed in the Pattern box and click OK.
 To delete a pattern, select it and click Delete. You can select more than one
pattern for deletion by using the CTRL and SHIFT keys.

Patterns must be composed of numbers only. Use the X wildcard to

represent any digit, as in Toll Barrier Sub-profile Example, page 5-26.

6 Use the Allow calls to box to define numbers and numbering patterns of
destinations that users are allowed to call, regardless of the value in the Basic
behavior field and the entries in the Do not allow calls to box (if available).
Add new, update, or remove patterns as described in the previous step.
7 To override the Direct incoming calls to external destinations parameter,
which determines whether or not to block user-defined incoming call
redirections to external destinations, select the relevant check box (Allow or
Restrict.)
Defining a User

8 Click OK. On the Profiles tab, an overridden comment is displayed after the
name of the sub-profile.
9 Click Save.
6

6-38 Managing Users Aeonix Administration Manual

 Overriding Schedules
The following procedure describes how to customize schedules for a specific user.
Each user has the following schedules assigned:
 The schedules defined in the Schedule sub-profile assigned to this user (unless
they have been manually deleted)
 Any imported global schedules
 Any schedules defined for this user

For a detailed description of schedules, see Schedules, page 4-37.

To define a user’s schedules and time frames:

1 On the User page, click the Profiles tab (see Figure 6-10).
2 Click the Schedule sub-profile. The Schedule List is displayed for the user.

Figure 6-15 A User’s

Schedule List

3 To define a new schedule for the user:

a In the Schedule List, click Add. The Schedule page is displayed.

Figure 6-16 Schedule in a

Defining a User

User’s Schedule Profile

6

Aeonix Administration Manual Managing Users 6-39

 b Enter a name in the Name box.
c In the Time Frame List, configure the time frames (see Defining a Time
Frame, page 4-39).
d Click OK.
4 To update a schedule of the sub-profile:
a In the Schedule List, click the name of the schedule. The Schedule page is
displayed.
b In the Time Frame List, configure the time frames (see Defining a Time
Frame, page 4-39).
c Click OK.
5 To add a copy of a global schedule to the sub-profile:
a In the Schedule List, click Import. The Schedule page displays a list of the
available global schedules.
b Select the check boxes next to the relevant schedule or schedules and click
Select.
6 To delete a schedule from the sub-profile:
a On the Schedule Profile page, select the check boxes left of the relevant
schedule or schedules in the Schedule List.
b Click Delete. A confirmation message is displayed.
c Click Yes to delete the schedule or schedules.
7 Click OK. On the Profiles tab, an overridden comment is displayed after the
name of the sub-profile.
8 Click Save.

Overriding Incoming Call Routing Rules

The following procedure describes how to modify incoming call routing rules for a
specific user. You can override any rule, except the following:
 Basic rules marked as mandatory in the sub-profile assigned to the user
(Mandatory check box selected)
Defining a User

 Basic rules that are disabled in the sub-profile assigned to the user (Enable
check box not selected)
 Advanced mandatory rules defined for the sub-profile
For more information, see Incoming Call Routing Sub-profiles, page 5-31.
6

6-40 Managing Users Aeonix Administration Manual

 To override a user’s Incoming Call Routing sub-profile rules:
1 On the User page, click the Profiles tab (see Figure 6-10).
2 Click the Incoming Call Routing sub-profile. The basic incoming call routing
rules are displayed for the user.

Figure 6-17 A User’s

Basic Incoming Call
Routing Rules

You can override the basic incoming call routing rules only if the Override
check box of the relevant sub-profile is enabled. Sub-profile override
permissions are defined in the profile assigned to the user (see Managing
Profiles, page 5-83).

3 Select the Override check box next to the relevant rules. The rules’ link to the
source sub-profile is broken, and the rules can be modified as required.

For a description of the rules, see Defining Basic Rules for Incoming Call Routing,
page 5-33.
Defining a User

4 Click Advanced. The fields for viewing and setting advanced rules are shown.
6

Aeonix Administration Manual Managing Users 6-41

 Figure 6-18 A User’s
Advanced Incoming Call
Routing Rules

You can use the Search box to textually search for and display specific items
in the list.

5 Click Mandatory, User’s Rules, and Optional to view or hide the required
types of rules. (The User’s Rules are displayed by default.) Each box lists the
rules in the order in which they are executed.
6 Using the buttons to the left and the right of the User’s Rules box, manage the
user’s incoming routing rules as required:
 Click a rule to display its full syntax underneath the box. (This option is
available for all types of incoming call routing rules.)
 Use (the Up and Down arrows) to set the priority order of the user
rules. (All user rules have a lower priority than the sub-profile’s mandatory
rules, but a higher priority than its optional rules.)
 Use the Add or Update button to add new or update existing user rules.
(For detailed instructions, see Defining Advanced Rules for Incoming Call
Routing, page 5-35.)
 Click Delete to delete a selected user rule.
Defining a User

7 Click OK. On the Profiles tab, an overridden comment is displayed after the
name of the sub-profile.
8 Click Save.
6

6-42 Managing Users Aeonix Administration Manual

 Overriding Outgoing Call Routing Parameters and Rules
The following procedure describes how to override outgoing call routing parameters
for a user and define user-specific digit manipulation rules for outgoing calls.
The Outgoing Call Routing sub-profile assigned to a user can include routing rules,
which define actions and manipulations to be performed on outgoing calls. You cannot
modify or delete these rules for a specific user; however, you can override them by
defining routing rules for the user.

To override a user’s Outgoing Call Routing sub-profile parameters:

1 On the User page, click the Profiles tab (see Figure 6-10).
2 Click the Outgoing Call Routing sub-profile. The outgoing call routing
parameters and rules are displayed for the user.

Figure 6-19 A User’s

Outgoing Call Routing
Parameters and Rules

You can use the Search box to textually search for and display specific items
in the list.
Defining a User
6

Aeonix Administration Manual Managing Users 6-43

 You can override the parameters (except the Outside line access code
parameters) and rules only if the Override check box of the relevant
sub-profile is enabled. Sub-profile override permissions are defined in the
profile assigned to the user (see Managing Profiles, page 5-83).

3 Select the Override check box next to the relevant parameters. The
parameters’ link to the source sub-profile is broken, and they can be modified
as required.

For a description of the parameters, see Outgoing Call Routing Sub-profiles,

page 5-41.

4 In the Dialed Number Manipulation Rules box at the bottom of the page,
add, update, or delete user-specific rules as required. These procedures are
performed as described in Defining Dialed Number Manipulation Rules, page 5-45
and Deleting Dialed Number Manipulation Rules, page 5-48, but from the User page
instead of the Outgoing Call Routing Profile page.

Administrator-defined dialed number manipulation rules (that is, rules

defined in the sub-profile) cannot be modified or deleted. However, they are
always of lower priority than the defined user-specific rules and can therefore
be overridden.

5 Use (the Up and Down arrows) to set the priority order of the rules.
6 Click OK. On the Profiles tab, an overridden comment is displayed after the
name of the sub-profile.
7 Click Save.

Viewing Administration Level Parameters

The following procedure describes how to view administration level task parameters
for a user.
Defining a User

The Administration Level sub-profile assigned to a user include administration tasks,

which allow the user to access and/or manage particular Aeonix Web Portal pages
associated with this level. You cannot modify or delete these tasks for a specific user;
however, you can assign full administrator rights to the user via this page.
6

6-44 Managing Users Aeonix Administration Manual

 To view a user’s Administration Level parameters:
1 On the User page, click the Profiles tab (see Figure 6-10).
2 Click the Administration Level sub-profile. The administration level task
parameters are displayed for the user.

Figure 6-20 A User’s

Administration Level
Task Parameters

For a description of the administration task parameters, see Table 5-10.

To assign full administrator rights to a user:

1 On the User page, click the Profiles tab (see Figure 6-10).
2 Click the Administration Level sub-profile. The administration level task
parameters are displayed for the user.
3 At the top of the page, select the Yes check box.
4 Click OK. On the Profiles tab, Administrator is displayed after the name of
Defining a User

the sub-profile.
5 Click Save.
6

Aeonix Administration Manual Managing Users 6-45

 Canceling Overrides of General Information Parameters

To reset overridden parameter values to the values of the sub-profile:

1 On the User page, click the Profiles tab (see Figure 6-10).
2 Click the General Information sub-profile. The parameters are displayed for
the user.
3 Clear the Override check box next to the relevant parameters. The parameter
fields are disabled and display the values of the sub-profile.
4 Click OK to return to the Profiles tab. If all parameter overrides have been
canceled, the overridden comment after the sub-profile name is removed.
5 Click Save.

Canceling Overrides of Timeout Parameters

To reset overridden parameter values to the values of the sub-profile:

1 On the User page, click the Profiles tab (see Figure 6-10).
2 Click the Timeouts sub-profile. The parameters are displayed for the user.
3 Clear the Override check box next to the relevant parameters. The parameter
fields are disabled and display the values of the sub-profile.
4 Click OK to return to the Profiles tab. If all parameter overrides have been
canceled, the overridden comment after the sub-profile name is removed.
5 Click Save.

Canceling Overrides of Feature Parameters

To reset overridden parameter values to the values of the sub-profile:

1 On the User page, click the Profiles tab (see Figure 6-10).
2 Click the Feature Configuration sub-profile, and then click the relevant
features. The parameters of these features are displayed for the user.
3 Clear the Override check box next to the relevant parameters. The parameter
fields are disabled and display the values of the sub-profile.
Defining a User

4 Click OK to return to the Profiles tab. If all parameter overrides have been
canceled, the overridden comment after the sub-profile name is removed.
5 Click Save.
6

6-46 Managing Users Aeonix Administration Manual

 Canceling Overrides of Toll Barrier Rules

To reset a user’s toll barrier rules to the sub-profile’s settings:

1 On the User page, click the Profiles tab (see Figure 6-10).
2 Click the Toll Barrier sub-profile. The toll barrier details are displayed for the
user (see Figure 6-14).

Click the Base Toll Barrier toggle bar to display or hide the details of the toll
barrier sub-profile assigned to the user.

3 From the Change Method drop-down list, select None. The Basic behavior
field and the pattern boxes are disabled and display the settings of the
sub-profile.

If None is already selected, clear the Override check box next to the Direct
calls to external destinations parameter instead.

4 Click OK to return to the Profiles tab. If all parameter overrides have been
canceled, the overridden comment next to the sub-profile name is removed.
5 Click Save.

Reversing Schedule Overrides

Unlike most sub-profile parameters, a user’s schedules do not have Override check
boxes that can be cleared to cancel overrides. To reverse schedule changes for a user,
use the procedure described in Overriding Schedules, page 6-39.

Canceling Overrides of Incoming Call Routing Rules

Only overrides of basic incoming call routing rules can be cancelled. Advanced
user-specific rules are adjusted as described in Overriding Incoming Call Routing Rules,
page 6-40.

To cancel overrides of basic incoming call routing rules:

Defining a User

1 On the User page, click the Profiles tab (see Figure 6-10).
2 Click the Incoming Call Routing sub-profile. The parameters are displayed for
the user (see Figure 6-17).
3 Clear the Override check box next to the relevant rules. The parameter fields
6

are disabled and display the values of the sub-profile.

Aeonix Administration Manual Managing Users 6-47

 4 Click OK to return to the Profiles tab. If all parameter overrides have been
canceled, the overridden comment next to the sub-profile name is removed.
5 Click Save.

Canceling Overrides of Outgoing Call Routing Parameters and Rules

Only overrides of outgoing call routing parameters (ARS table and Hot Station) can
be canceled. User-specific outgoing call routing rules are adjusted as described in
Overriding Outgoing Call Routing Parameters and Rules, page 6-43.

To cancel overrides of outgoing call routing parameters:

1 On the User page, click the Profiles tab (see Figure 6-10).
2 Click the Outgoing Call Routing sub-profile. The parameters are displayed for
the user (see Figure 6-19).
3 Clear the Override check box next to the relevant parameters. The parameter
fields are disabled and display the values of the sub-profile.
4 Click OK to return to the Profiles tab. If all parameter overrides have been
canceled, the overridden comment next to the sub-profile name is removed.
5 Click Save.
Defining a User
6

6-48 Managing Users Aeonix Administration Manual

  Configuring a User’s Phone Profiles

Phone profiles define the settings and dial functions of phones. The profile assigned
to a user includes a phone profile that is applied by default to Aeonix phones
associated with this user.

To view a list of applicable phones or to learn about how to configure a

default phone profile, see Phone Profiles, page 5-54.

Default phone profiles cannot be associated with a specific phone. However, you can
define additional phone profiles for specific phones, which apply when the user uses
these phones. (These phones must be defined in the system, as described in Configuring
Phones in Aeonix, page 7-9.)

The user of the phone can change the button definitions from the Aeonix
Web Portal for Users. For more information, refer to the Configuration Guide
for End Users (see Related Documentation, page 1-17).

Managing phone profiles includes:

 Defining a User’s Phone Profiles, page 6-50
 Deleting a Phone Profile of a User, page 6-55

Defining a User
6

Aeonix Administration Manual Managing Users 6-49

 Defining a User’s Phone Profiles
By default, a user’s default phone profiles are sub-profiles linked to and determined
by the user profile assigned to this user. You can break this link and select another
phone profile or override parameter values. In addition, you can add new, clone, and
update phone profiles for specific phones.
Overridden parameters are not affected by modifications of the phone profile.
However, if the user is assigned another user profile (see Assigning a Profile to a User,
page 6-30), the parameter values of the default phone profile are reset in accordance
with the newly assigned profile. Overridden parameter values of the default phone
profile are also reset if a previous override is canceled and the link between the phone
profile and the user profile is recreated.

The following procedure describes how to define phone profiles for the
phones of a specific user. To learn about defining phone profiles that can be
applied to multiple users, see Defining a Phone Profile, page 5-54.

To add or update a phone profile for a user:

1 On the User page, click the Profiles tab (see Figure 6-10).
2 Do one of the following:
 To view/update the phone profile for the currently active phone, click the
phone above the Phone Profiles box.
 To add a new phone profile for a specific phone, click Add to the right of
the Phone Profiles box and select the relevant phone icon.
 To create a new phone profile based on the settings of an existing one,
select a phone profile in the Phone Profiles box and click Clone.
 To update an existing phone profile, select it in the Phone Profiles box.
The relevant phone’s Profile page is displayed, as in the following figure for a
new FlexSet-IP 280S phone profile.
Defining a User
6

6-50 Managing Users Aeonix Administration Manual

Figure 6-21 New Phone
Profile for a Specific
FlexSet-IP 280S Phone

3 To break the link to the profile assigned to the user, select the check box next
to the Override profile drop-down list. The drop-down list is enabled.

Clearing the Override profile check box re-links the phone profile to the
user’s profile.

4 To base the phone settings on a different phone profile than the phone profile
of the assigned user profile, select the relevant phone profile from the
Override profile drop-down list. (This option is only available if the Override
profile check box is selected and if profiles have been defined for this phone -
see Defining a Phone Profile, page 5-54.)
Defining a User

5 If this is a new phone profile, select from the Phone ID drop-down list the
phone to which the phone profile settings are applied when operated by the
user.
6

Aeonix Administration Manual Managing Users 6-51

 The phone ID assignment of an existing phone profile cannot be modified.
For the default phone profile, the Phone ID field is not available since the
profile is not related to a particular phone.

6 Click Properties to display the phone properties. (These properties are

described in detail in Figure 5-7 on page 5-59.) You can override or set them
as follows:
a In the Local display field, enter the text to be displayed on the phone’s
display panel. (If this field is left empty, the user’s Display name is
displayed on the phone.)
b To override the Speakers mode parameter, select the check box next to the
relevant field. The parameter’s link to the phone profile is broken, and the
parameter can be modified as required.

Clearing the check boxes re-links the parameters to the phone profile of the
assigned user profile.

7 Assign dial functions to programmable phone buttons:

a Click the relevant button on the image of the phone.
A red indication flashes next to the button. To the right of the phone, the
system shows the current setting and provides a drop-down list of the
options for configuring the button. The options are described in
Programmable Button Dial Functions, page 5-60.
b Specify the function for the button. For example, select Speed Dial from
the Feature type drop-down list and specify the destination user or number
in the Dial to fields.
c Click OK. The selected function’s icon is displayed to the left of the button.

You cannot assign or modify dial functions to a button that has been locked
Defining a User

in the source sub-profile (see Phone Profiles, page 5-54).

For instructions on how to program T207M, T208M/BL phones’ TEM buttons,
see Programming TEM Buttons of T207M, T208M, T207M/NP, T208M/BL Phones,
page 5-78.

8 When you have finished configuring the buttons, click OK. The main User
6

page is displayed.

6-52 Managing Users Aeonix Administration Manual

 You can click Restore Defaults to revert the buttons to the user assigned
phone sub-profile buttons scheme.

9 Click Save to apply the new settings.

Programmable Button Sync with Tadiran SIP Phones

Aeonix 4.1 and later supports synchronization of phone button programming between
the Aeonix database and the phone’s memory, according to the following
programming methods:
 Programming buttons via the phone physical interface (syncs immediately ~10
seconds)
 Programming buttons via the phone’s URL interface (syncs immediately ~10
seconds)
 Programming buttons via the Aeonix User Configuration Portal (syncs
immediately ~10 seconds)
 Programming buttons via the Aeonix Administration Phone Profile page (syncs
in the next provisioning cycle, default is once per day)

Programming
The following procedures are used to program buttons in Aeonix 4.1

Deleting Buttons
 Deleting a programmed button via the phone physical interface, or the phone
URL interface -- the button will be restored almost immediately from the
Aeonix database. To clear a user-programmed button, set it to empty via the
Aeonix User Configuration Portal.
 If the button is set in the Aeonix Administration Phone Profile page, it will
always be restored when the phone is provisioned.
 For a fully clear (empty) button, the button must be clear in both the Aeonix
User Configuration Portal and the Aeonix Administration Phone Profile page.
Defining a User

Conversion of Phone Functions to Aeonix Format

If the function being programmed from the phone physical interface or the phone URL
interface is an Aeonix-supported function, the format of the programmed function will
6

be converted to the Aeonix format. The following table shows examples of the
conversion for different function types.

Aeonix Administration Manual Managing Users 6-53

 Table 7 Phone Function
Format Convertion to Programmed on Phone Conversion to Aeonix Format
Aeonix Format
linekey.21.type = 13 (speed dial) linekey.21.type = 17 (URL)
linekey.21.line = 1 linekey.21.line = 1

linekey.21.value = 1234567890 linekey.21.value

=http://tadspc.tadirantele.com:8080/aeonix/spc?
ep_id=sip %3AJoT48G%40aeonix.com&

event=button_pressed&button_id=4322

linekey.21.label = OneTwo linekey.21.label = OneTwo

linekey.21.extension = %NULL% linekey.21.extension = %NULL%
linekey.21.xml_phonebook = 0 linekey.21.xml_phonebook = 0
linekey.21.pickup_value = %NULL% linekey.21.pickup_value = %NULL%

If the function being programmed on a button is a phone-defined function, but not an

Aeonix-defined function, the function will be stored in the Aeonix database as text
with no conversion.

Button Lock
If the user programs a button via the phone physical interface or the phone URL
interface, and the button is protected by Lock in the Aeonix User Configuration Portal
or the Aeonix Administration Phone Profile, the phone will display an error message:
“Program failed, button is locked”.

Required Phone Firmware Version

Tadiran SIP phones must be upgraded to the firmware versions included in Aeonix 4.1
to take advantage of Programmed Button Sync.

Required Aeonix Version

Programmed Button Sync is supported in Aeonix Version 4.1 and later.
Defining a User
6

6-54 Managing Users Aeonix Administration Manual

 Deleting a Phone Profile of a User

The default phone profiles cannot be deleted.

To delete a phone profile of a user:

1 On the User page, click the Profiles tab (see Figure 6-10).
2 In the Phone Profiles box, select the phone profile or profiles and click
Delete. You can delete multiple phone profiles by holding down the CTRL or
SHIFT key while selecting them.
3 Click Save. The phone profiles are deleted.

Defining a User
6

Aeonix Administration Manual Managing Users 6-55

  Managing a User’s Phones

The user cannot make or receive calls without at least one phone. This phone (or an
external number) must be defined in the system and associated with the user.
The following procedure describes how to define a user’s phone in Aeonix and
configure basic phone parameters. Advanced settings of this phone are defined
through the Phone page (see Configuring Phones in Aeonix, page 7-9).
In addition, the phone itself must be configured to work with the system. Only then
will the user be able to place and receive calls. For instructions on how to configure
the phone, refer to the relevant phone documentation (see Related Documentation,
page 1-17).
Managing a user’s phone includes:
 Adding a User’s Phone, page 6-57
 Viewing and Editing User’s Phones, page 6-59
Defining a User
6

6-56 Managing Users Aeonix Administration Manual

 Adding a User’s Phone

To define a phone for a user:

1 On the User page, click the Phones tab.

Figure 6-22 Phones Tab

This tab contains the following:

 The My Phones table, which lists previously defined phones for this user
(see Viewing and Editing User’s Phones, page 6-59)
 The New Phone Configuration section for adding a new phone
2 From the Phone type drop-down list in the New Phone Configuration section,
select the phone type according to the following table.

Table 6-1 Phone Type

Options Phone Type When To Select

Tadiran MGCP For a FlexSet-IP 280S, T207M, T208M/BL phone

FlexIP Softphone For a FlexIP Softphone (FLIPS)

SIP terminal For a SIP phone, including a Tadiran SIP phone

and P-Series phone
Defining a User

Wave Gateway station For an analog phone or a digital keyset connected

through a Wave Gateway.
(SLT, FlexSet 120, 120D, 120L, 120S, 121S, 280,
280D, 280D-HS, 280S, 281S, DKT, CPA and DST).
6

Aeonix Administration Manual Managing Users 6-57

 3 From the Device model drop-down list (only displayed if the phone type is
SIP Terminal), select the relevant phone model (Tadiran SIP phone or P-Series
phone).

Select Auto-Detect if you want the system to automatically detect the phone
model.

4 Enter the MAC address of the phone in the field that is displayed below.

These phones are assigned Tadiran MAC address by the manufacturer.

They are in the format 00-0A-6B-XX-YY-ZZ.

5 In the Phone ID fields, enter the MAC address (MGCP phones), SIP User
Name (SIP phones), or shelf/slot/card assignment (Wave Gateway phones) of
the phone, as well as the name of the domain (server) to which the phone is
connected.

For Tadiran MGCP phones (see Phone Profiles, page 5-54),

FlexIP SoftPhone (FLIPS), and SIP phones, the domain name is always the
Aeonix domain (usually aeonix.com).

6 From the Location drop-down list in the New Phone Configuration section,
select the location where the phone is used. (To learn about defining locations
in the Aeonix system, see Locations, page 4-9.)
7 Click Save at the bottom of the User page.
You can repeat the above procedure to define multiple phones for the user. The defined
phones are displayed in the user’s My Phones table and added to the Phone List Page
(see page 7-3).
Defining a User
6

6-58 Managing Users Aeonix Administration Manual

 Viewing and Editing User’s Phones
You can view or edit the following phones from a User page:
 Phones assigned to the user as their default user
 Phones to which the user is currently logged in, even if this user is not the
default user of these phones

To view or edit the phones of a user:

1 On the User List page (see Figure 6-1), click the Login Name of the user. The
relevant User page is displayed (see Figure 6-3).
2 Click the Phones tab. The My Phones tables lists the phones of the user.

Figure 6-23 Phones Tab

with User’s Phones

The following information is displayed for the phones:

Table 6-2 Phone Details

Phone Attributes When To Select

Status icon (circle)  Green - the phone is registered in the system,

and the user is logged in to the phone
 Red - the phone is not registered
 Green/Red -
The phone is registered in the system, but the
user is not logged in through this phone.
OR
Changes made in Aeonix are currently not
synchronized with the phone. Once provisioning
is executed and, as a result, synchronization
between Aeonix and the phone is restored, the
icon will revert to green.
The lack of synchronization can result from a
mismatch of provisioning parameters or firmware
Defining a User

between Aeonix and the phone.

NOTE: View the specific icon’s tooltip for more

information.

ID Unique identifier for the specific phone device. Click

this field to open the relevant Aeonix Phone page.
6

Aeonix Administration Manual Managing Users 6-59

 Phone Attributes When To Select

Model The model number of the phone (see Supported

Devices, page 1-12)

Default User A check mark indicates that the user is the default
user of this phone. If the user is currently logged in
through the phone but is not its default user, this
field is left blank.

Allow Auto Answer Select to permit the phone to receive Voice and
Zone Pages, and to allow Auto Answer.

NOTE: For users with multi-devices, it is

recommended to select this option for the
main device only.

Dial Lock Allows the user to lock the phone with the Dial Lock
feature. Dial Lock feature for Tadiran phones is
described in Aeonix Configuration Guide for End
Users.

Ring Control (Default:  Always - the phone will ring on all incoming calls
Always)  Internal call - the phone will only ring on
incoming internal calls
 External call - the phone will only ring on
incoming external calls
 Never - the phone will not ring on any incoming
call

Ctrl via CTI Allows the phone to be used in conjunction with

Aeonix Touch, Sea Navigator, Sea Attendant,
Aeonix Contact Center, and ACD Agent via the
Aeonix CTI interface. This also determines on which
of the user’s phones silent monitoring is performed
on.

NOTE: If the designated phone is deleted from the

system, this option is reset to cleared.

NOTE: Only Tadiran SIP Phones and the Aeonix

Touch softphone can be controlled via CTI.

Registered on The Aeonix server (call agent) on which the phone

Defining a User

is registered.

IP Address The IP address assigned to the phone (if any). This

address is displayed if the phone is registered.
Click this field to open the Web page of the phone.
6

6-60 Managing Users Aeonix Administration Manual

 Phone Attributes When To Select

Force Logout Select to log out the phone when guest login is
being used.

Defining a User
6

Aeonix Administration Manual Managing Users 6-61

  Configuring Mobility Rules for a User

Mobility rules allow outside users calling a mobility alias number to obtain internal
dial tone and internal system services. For a general description of the mobility
feature, see Mobility, page 2-27.
If mobility service aliases have been configured in the system, mobility rules can be
defined (see Defining Mobility Aliases, page 12-89). These rules are either defined while
configuring a mobility alias, or for a specific user as described in Defining a Mobility Rule
for a User, page 6-63.
You can define one or more mobility rules. To avoid ambiguity, the system makes sure
a new rule does not conflict with an existing rule before saving it. For details,
see Non-conflicting Rules, page 12-93.
Defining a User
6

6-62 Managing Users Aeonix Administration Manual

 Defining a Mobility Rule for a User

To add or update a mobility rule:

1 On the User page (see Figure 6-3), click the Mobility tab. The Mobility tab
displays the previously defined rules (if any).

Figure 6-24 Mobility Tab

2 Click Add, or click the Service Number of the rule to be updated. The Add
Rule or Update Rule page is displayed.

Figure 6-25 New Mobility

Rule

3 Select Rule enabled to have the rule activated once it has been saved. If this
check box is not selected, the other rule parameters cannot be modified.
4 From the Service number drop-down list, select an available mobility service
alias. (Mobility service numbers are defined as described in Defining Mobility
Defining a User

Aliases, page 12-89.)

The service number is an internal alias and not intended for outside callers.
To obtain the number that the user must dial to access the mobility service
from outside, contact your IT manager.
6

Aeonix Administration Manual Managing Users 6-63

 5 Specify the Authentication Method. You can select either method, both
methods, or – for callback mobility only – no method.
 To base the authentication on the user’s external number, select ANI and
enter the full ANI number (including prefixes and suffixes) of the user.
 To base the authentication on the user passcode, select PIN.
6 Specify the service access method: Under Service Type, select Callback and
enter a full callback number (including prefixes and suffixes), or select
Call-through.
7 Click OK. The rule is included in the mobility rule list.
8 Click Save.
Defining a User
6

6-64 Managing Users Aeonix Administration Manual

  Managing a User’s ULA Settings

A ULA (User Line Appearance) group is a group of users with a manager/assistants

hierarchy, in which incoming calls to the group owner can ring at and be handled by
any of the group members.

Tips:
To learn more about the ULA feature, see User Line Appearance (ULA), page 2-43.

You can set up a ULA group for any user (see Configuring a User’s ULA Group,
page 6-67). The user for which you define the group will be the owner of this group. A
user can also be member of one or more ULA groups owned by other users. To view
the configuration of these groups, see Viewing the Configuration of a ULA Group Owned by
Another User, page 6-70.
The ULA groups a user belongs to are displayed on the user’s ULA tab. The ULA tab
is divided into two main parts:
 My Owned Group—lists the members of the ULA group in which the user is
the group owner
 Membership in Groups—lists all ULA groups to which the user belongs as a
regular member (not owner)

Figure 6-26 ULA Tab with

Defined ULA Groups

For each of the listed groups, you can define whether the user is logged in, and whether
incoming calls will ring on the user’s phone (see .Specifying the ULA Login Status and
Ring Policy of ULA Group Members, page 6-70).
A ULA group consists of the group owner and at least one additional member. To
delete a ULA group, remove the owner or all its members from the group, as described
Defining a User

in Deleting a ULA Group, page 6-71.

6

Aeonix Administration Manual Managing Users 6-65

 Users can manage the ULA group they own from the Aeonix Web Portal for
Users, but cannot edit a ULA group they do not own, even if they are group
members. For more information, refer to the Configuration Guide for End
Users (see Related Documentation, page 1-17).

Additional Procedures for Programming ULA Groups

Managing ULA groups also requires programming at the following levels:
 Incoming call routing—routing incoming calls to the ULA group (see Incoming
Call Routing Sub-profiles, page 5-31)
 Phone profile—programming buttons with ULA functions (see Configuring a
User’s Phone Profiles, page 6-49)
 Feature configuration—enabling or disabling Exclusive Hold (see Feature
Configuration Sub-profiles, page 5-15)
Defining a User
6

6-66 Managing Users Aeonix Administration Manual

 Configuring a User’s ULA Group
ULA groups are configured from the User page of their group owners. A user can be
the owner of only one ULA group.

To configure a ULA group:

1 On the User page of the user who is the owner of the group, click the ULA
tab. The tab displays the My Owned Group and Membership in Groups
bars.
2 Click My Owned Group. The members of the user’s ULA group, if any have
been previously defined, are displayed.

Figure 6-27 ULA Tab with

No Owned Group Defined

3 Click Configure. (Alternatively, if the ULA group has already been defined,
you can click the first Member ID entry in the My Owned Group list.) The
ULA Group page is displayed.

Figure 6-28 ULA Group

Page

Defining a User

The Unassigned box includes the users that are not assigned to the ULA
group.
6

Aeonix Administration Manual Managing Users 6-67

 The Assigned box displays the current group members, as well as (in square
brackets) their ring policy. The group owner (current user) automatically
appears as the first entry in the box.

A ULA group must contain the group owner and at least one regular group
member.

4 To add a user to the ULA group, select the relevant user entry in the
Unassigned box and click (the right arrow). (You can use the Search box
for this purpose.) The selected user is moved to the Assigned box.
Repeat this step to add other users to the group. You can add multiple users by
holding down the CTRL or SHIFT key while selecting them.
5 To specify a user’s ring policy for incoming calls to the ULA group owner,
select the user entry and click the relevant option to the right of the Assigned
box.

Table 6-3 ULA Ring

Policy Options Phone Type When To Select

Ring An incoming call to the ULA owner immediately

rings at the phone or phones associated with the
user.
At the same time, a button programmed as a
shared line button in the user’s phone profile
(see Configuring a User’s Phone Profiles, page 6-49) blinks
to indicate an incoming ULA call until the call is
answered.

NOTE: Calls do not ring if the user is in DND (Do Not

Disturb) state or has Call Forward All
assigned.

No ring Incoming calls to the ULA owner do not ring at the

user’s phone or phones, but shared line buttons
blink to indicate the calls.

Ring delayed An incoming call to the ULA owner rings at the

user’s phone or phones if the call has not been
Defining a User

answered before the Delayed Ring Timer

(see Step 7 below) has expired. Shared line
buttons, however, immediately blink to indicate
incoming calls.

NOTE: Calls do not ring if the user is in DND (Do Not

Disturb) state or has Call Forward All
6

assigned.

6-68 Managing Users Aeonix Administration Manual

 6 To remove a user from the ULA group, select the relevant entry in the
Assigned box and click (the right arrow). The selected user is moved to
the Unassigned box, and the entry’s ring policy assignment is deleted.
Alternatively, you can remove members from the ULA tab by selecting the
check box to the left of the relevant My Owned Group user entry or entries
and clicking Delete.
7 In the Delayed ring timer box, enter the number of seconds after which an
incoming call rings at the phone of ULA members with Ring Delayed policy if
the call has not been answered before.

To allow delayed ringing, the delayed ring timer must be smaller than the
system-wide predefined ring timeout and, if specified in the incoming call
routing’s Ring on rule, the No Answer timeout (see Incoming Call Routing
Sub-profiles, page 5-31).

8 Select the Ignore incoming routing rules of ULA members (excluding the
ULA owner) check box if you want ULA group members to receive FlexiCall
ULA members. Calls received directly to this device are not affected by this
parameter.

Not applicable for ULA group owners.

9 Click OK to return to the ULA tab (see Figure 6-26 on page 6-65). The
members of the user’s ULA group are listed in the My Owned Group box.
The first entry in the list is the ULA group owner (that is, the current user).
10 At the bottom of the User page, click Save.

Defining a User
6

Aeonix Administration Manual Managing Users 6-69

 Viewing the Configuration of a ULA Group Owned by Another User
You can view the settings of the ULA groups to which a user belongs but does not
own. The configuration of these groups, however, can only be done from the User
page of the ULA group owner.

To view the configuration of a ULA group to which the user belongs:

1 On the User page, click the ULA tab (see Figure 6-26 on page 6-65).
2 If required, click Membership in Groups to display the ULA groups to which
the user belongs but does not own.
3 Click the Group Owner of the relevant ULA group entry. The group
configuration details are displayed as in Figure 6-28 on page 6-67; however,
they cannot be changed.

Specifying the ULA Login Status and Ring Policy of ULA Group Members
On a user’s ULA tab (see Figure 6-26 on page 6-65), you can specify the ULA login
status and ring policy for the following group members:
 The user as ULA group owner—represented in the My Owned Group list by
the first entry
 Other members belonging to the user’s ULA group—represented in the My
Owned Group list by the subsequent entries
 The user as a member of a ULA group belonging to another user—represented
in the Membership in Groups list by the entry with the relevant Group Owner

To set the ULA login status and ring policy:

1 On the User page, click the ULA tab (see Figure 6-26 on page 6-65). If
required, click My Owned Group or Membership in Groups to display the
relevant ULA lists.
2 To log a user in to a ULA group, select the Logged in to ULA check box of
the relevant list entry. A user (owner or regular member) logged in to a ULA
group receives calls placed to this ULA group and can place calls on behalf of
Defining a User

this group’s owner.

To log a user out from a ULA group, clear the Logged in to ULA check box
of the relevant list entry.
3 To change a user’s ring policy, select the required Ring Policy option of the
6

relevant list entry. (For an explanation of the options, see Table 6-3 on
page 6-68.)

6-70 Managing Users Aeonix Administration Manual

 Deleting a ULA Group

To delete a ULA group:

1 On the User page of the ULA group owner, click the ULA tab (see Figure
6-26 on page 6-65). If required, click My Owned Group to list the ULA
group members.
2 Select the check box to the left of the first My Owned Group entry and click
Delete. A confirmation message is displayed.
3 Click Yes. The ULA group is deleted, and all entries are removed from the My
Owned Group list.

Defining a User
6

Aeonix Administration Manual Managing Users 6-71

  Setting the Meet-me Conference Access Code

If the user has been specified as the owner of a meet-me conference alias, the
conference access code can be modified from the relevant User page.
To learn more about meet-me conferences and how to define their owners, see Defining
Meet-Me Conference Aliases, page 12-79.

To define or remove the access code of a meet-me conference alias:

1 On the User List page (see Figure 6-1), click the Login Name of the user. The
relevant User page is displayed (see Figure 6-3).
2 Click the Conferences tab.

Figure 6-29 Conferences

Tab

The My Conferences table lists the alias numbers and access codes of the
meet-me conference for which the user has been specified as their owner.
3 In the Access Code field of the relevant conference alias, enter or remove the
code as required. (The access code cannot be modified if a call is currently
using the conference alias.)
4 At the bottom of the User page, click Save.
Defining a User
6

6-72 Managing Users Aeonix Administration Manual

  Resetting a User’s Password

You can reset any user’s password to the system's default value.

For administrators, the default password is anx; for regular users, the
default user password is automatically generated by the system, as
displayed on the System Parameters page (see Figure 14-6).

To reset a user password:

1 On the User List page (see Figure 6-1) locate the entry relating to the user. You
can use the Search function for this purpose (see Searching for Users, page 6-6).
2 Click (the Reset password icon). A confirmation box prompts you to
reset the password of this user.
3 Click Yes to reset the password.

Users can modify their own passwords as described in Admin Password Policy,
page 3-10.

Defining a User
6

Aeonix Administration Manual Managing Users 6-73

  Viewing ACD and Hunt Group Membership

You can view the ACD and/or Hunt groups to which the user belongs, if any, from the
ACD & Hunt tab.
To learn more about the ACD feature and how to define ACD groups, see Defining ACD
Groups, page 12-5; To learn more about the Hunt feature and how to define Hunt
groups, see Defining Hunt Groups, page 12-45.

To view user ACD and/or Hunt group membership information:

1 On the User List page (see Figure 6-1), click the Login Name of the user. The
relevant User page is displayed (see Figure 6-3).
2 Click the ACD & Hunt tab.

Figure 6-30 ACD & Hunt

Tab

 Defining Permission Settings

The Permissions tab allows you to define permissions for the following features:
 Silent Monitor—who the user is authorized to monitor (and the users that can
monitor the user).
 Break-in / Break-out—who the user is authorized to break-in to (and the
users that can break-in to the user). Who the user can perform Break-out on
(and the users who can perform Break-out on the user).
 Call Pickup—who the user is authorized to perform call pickup for (and the
users that can perform call pickup on the user).

To define call intrusion permission settings (Silent Monitoring and Break-in):

Defining a User

1 On the User List page (see Figure 6-1), click the Login Name of the user. The
relevant User page is displayed (see Figure 6-3).
2 Click the Permissions tab.
6

6-74 Managing Users Aeonix Administration Manual

Figure 6-31 Permissions
Tab

The Unassigned boxes include the users and groups that cannot perform the
corresponding call intrusion action.

Below the boxes, you can use the (right arrow) to display the next items
Defining a User

or the Search box to search for and display specific items in the list.

The Assigned boxes display the current users and groups on which the user
can perform the corresponding call intrusion action.
6

Aeonix Administration Manual Managing Users 6-75

 The adjacent boxes display the users and groups that can perform the
corresponding call intrusion actions on the user.

3 To add a user or group, select the relevant entry in the Unassigned box and
click (the right arrow). (You can use the Search box for this purpose.) The
selected user or group is moved to the Assigned box.
Repeat this step to add other users or groups. You can add multiple users or
groups by holding down the CTRL or SHIFT key while selecting them.
4 Select the Allow silent monitor on trunk to trunk calls check box to allow
the user to perform Silent Monitoring on trunk to trunk calls (transit calls).
5 At the bottom of the User page, click Save.

To define call pickup permission settings:

1 On the User List page (see Figure 6-1), click the Login Name of the user. The
relevant User page is displayed (see Figure 6-3).
2 Click the Permissions tab (see above), and scroll down to the Call Pickup area
at the bottom of the page.

This area is disabled for users whose Feature configuration profile setting
does not allow for directed call pickup (see Pickup, page 5-19).

3 Do one of the following:

 Select the Allow pickup calls for all users check box (default) to allow the
user to perform call pickup on all other users.
 Clear the Allow pickup calls for all users check box; the area is expanded.
4 Expand the Call Pickup area.
Defining a User
6

6-76 Managing Users Aeonix Administration Manual

Figure 6-32 Call Pickup
Area - Expanded

The Unassigned box includes the users and groups the user cannot perform
direct call pickup on.

Below the box, you can use the (right arrow) to display the next items or
the Search box to search for and display specific items in the list.

The Assigned box displays the current users and groups the user can perform
call pickup on.

The adjacent box displays the users and groups that can perform call pickup
on this user.

5 To add a user or group, select the relevant entry in the Unassigned box and
click (the right arrow). (You can use the Search box for this purpose.) The
selected user or group is moved to the Assigned box.
Repeat this step to add other users or groups. You can add multiple users or
groups by holding down the CTRL or SHIFT key while selecting them.
6 At the bottom of the User page, click Save. Defining a User
6

Aeonix Administration Manual Managing Users 6-77

NOTES:
 6.3 Importing / Exporting Users

The Aeonix Web Portal supports batch import and export of users from a CSV
(comma-separated) file.

 Importing Users into Aeonix

Prior to the import, specify the fields to be imported, the order in which they are
arranged in the file, and ensure that the CSV file is in UTF-8 encoding format.
If a user cannot be created, a record including the reason of the failure is written to an
error file. This error file is located under the same directory as the import file and has
the same name extended by ERR. For example, the error file of the import file
NewUsers.csv is called NewUsersERR.csv.
In addition, batch import of users from a CSV file for PnP purposes is supported. The
Phone provisioning MAC parameter can accept the value 'PNP' as the phone's MAC
address and the Phone provisioning model parameter as the PnP phone model,
allowing the imported user to be associated with the new phone when Auto Phone &
User PnP mode is used. (see Configuring PnP Provisioning, page 12-126).
In this mode, when a Tadiran SIP phone makes requests for plug and play, Aeonix
attempts to link the newly created phone to the user in the following manner:
 First priority is given to imported users having the same phone models. Aeonix
looks up the first available user that has the PnP flag with the user’s PnP
model being identical to the phone’s model, and links the phone to that user.
 Second priority is given to imported users with no associated phone models. Importing / Exporting Users
Aeonix looks up the first available user with the PnP flag with no phone model
definition and links the phone to that user.
Upon successful linkage, the phone ID gets the value of the alias, and Aeonix
associates the user as the phone’s Default User.
6

Aeonix Administration Manual Managing Users 6-79

 If there is no user that was imported from a CSV file, Aeonix creates a user.
In this case, the phone ID gets the value of the PnP alias (for example,
PnP2000 is the first possible value).

The following table describes the fields that can be imported if available in the CSV
file.

Table 6-4 Imported User

:

Parameters Field Description

Description A short description of the user

Display name The name of the user as viewed by other users. This field must
not exceed 15 characters.
If no display name is provided, the system uses the first name
and the last name of the user separated by a space, such as
John Smith.

External The external phone numbers of the user. Only complete

numbers numbers separated by spaces are imported.

First name The first name of the user

Internal The alias numbers assigned to the user. Only complete aliases
aliases separated by spaces are imported.

NOTE: A user is not created if the alias number of this user cannot
be imported, for example, because it already exists in the
Aeonix system or does not comply with the relevant dial
plan patterns.

Last name The last name of the user

Login name Unique identifier of the user. Typically, the worker ID, name of
the worker, or some other unique number used by the Aeonix
user to log in to the Aeonix Web Portal, as well as for logging in
to other Aeonix applications, such as the Aeonix Dispatch
Importing / Exporting Users

Console.

Location The Location of the user

NOTE: Should be equal to one of the locations already defined in

Aeonix. See Table 4-7 on page 4-12.)

Phone domain The domain (server) to which the phone is connected. This is the
phone ID part after the @ sign.
6

6-80 Managing Users Aeonix Administration Manual

 Field Description

Phone ELIN The user’s ELIN (Emergency Location Identification Number),

which is displayed to the receiver when the user makes an
emergency call.

Phone The Location of the phone

location
NOTE: Should be equal to one of the locations already defined in
Aeonix. See Table 4-7 on page 4-12.)

Phone name The MAC address, IP address, or shelf/slot/card assignment of

the phone. This is the phone ID part before the @ sign.

Phone The MAC address of the phone, according to which the Aeonix
provisioning server identifies the phone for provisioning purposes
MAC

Phone The model number of the Tadiran SIP phone: T19P, T21P,
provisioning T23P, T27P, T320, T322, T328, T41P, T42G, T46G, T48G,
model T49G

Phone The name of the provisioning profile associated with this phone
provisioning
profile

Phone type The type of the phone to be added (see Table 6-1 on
page 6-57).

NOTE: If the imported file contains a non-existent phone type, the

related user will not be imported.

PIN A numeric password consisting of 6-12 digits. Together with the

user’s alias, the PIN is required for user authentication by phone,
such as for callback and call-through.

Profile CUG NOTE: Currently not in use

Profile name The Profile assigned to the user. If no profile is specified for a
user, this user is assigned the default user profile.

NOTE: Should be equal to one of the user profiles already defined Importing / Exporting Users
in Aeonix. See Figure 5-34 on page 5-86.

NOTE: If the imported file contains a non-existent profile, the

related user will not be imported.

SIP voicemail The service where a voicemail box can be assigned to the user.

NOTE: If left blank, no mailbox can be created for the user.

6

User CUG NOTE: Currently not in use

Aeonix Administration Manual Managing Users 6-81

 Field Description

User ID Unique user identifier; mandatory for the import of the user

To import users from a CSV file:

1 On the navigation pane, click Administration. The pane displays the
Administration menus.
2 Select the Users menu, and then click Import / Export Users. The Import /
Export Users page is displayed.

Figure 6-33 IImport Area

of Import / Export Users
Page

The fields that can be imported are described in Table 6-4 on page 6-80.
Importing / Exporting Users

3 To import a field, select it in the Available Fields box and click (the right
arrow). The selected field is moved to the Import Fields box and added to the
list of fields to be included in the import procedure.
Repeat this step to add other fields.
6

6-82 Managing Users Aeonix Administration Manual

 To exclude a field from the import procedure, remove it from the Import
Fields box by selecting it there and clicking (the left arrow). You can
include or exclude multiple fields by holding down the CTRL or SHIFT key
while selecting them.

4 Use (the Up and Down arrows) next to the Import Fields box to specify
the order in which the fields appear in the CSV file.
5 Click Choose File and use the displayed dialog box to locate the required CSV
file on your workstation or network.
Ensure that these fields correspond to the actual fields in the CSV file. For
example, when selecting the fields as shown in Figure 6-33, the CSV file
should appear as follows:

Figure 6-34 CSV File

Format Example

For example, entry one in the CSV file above corresponds to the following fields:

Table 6-5 Entry example

for user with Wave Field Value
Gateway Station
User ID Amir Pa

Internal aliases 2006

Description Amir’s T-46G phone

Phone name phone2006

NOTE: In entry five, 0/7/0 refers to the location of the phone on

the Coral card (shelf/slot/ckt) in the Wave Gateway.
Importing / Exporting Users
Phone type SIP terminal

Phone domain aeonix.com

NOTE: In entry five, wg5.aeonix.com refers to the name of the

Wave Gateway to which Amir’s phone is connected.

Phone 00:15:65:4a:ac:3d is the phone’s MAC address for

provisioning MAC provisioning purposes
6

Aeonix Administration Manual Managing Users 6-83

 6 If the user you want to import user already exists in the system (as determined
by the User ID), select Update existing users if you want Aeonix to update
the user instead of creating a new user. All user fields can be updated except:
User ID, Phone type, and Internal aliases (in the case of Internal aliases,
Aeonix adds a new alias and the existing alias is not removed from the
system).

When importing users with multi-devices, this check box must be selected.

7 If a SIP Voicemail service has been defined in the system (see Defining
Voicemail Applications in Aeonix, page 12-140), select Create mailbox if you want
to create voicemail boxes for the imported users.

Before creating a mailbox, ensure that a corresponding voicemail is defined

and active at the user’s selected voice mail service. The default mailbox
password is 0000.

8 Click Import. A message is displayed indicating the number of the imported

users.
9 Click OK. The imported users are displayed on the User List page (see Figure
6-1).
Importing / Exporting Users
6

6-84 Managing Users Aeonix Administration Manual

  Exporting Users from Aeonix

You can export Aeonix users to a CSV (comma-separated) file.

To export Aeonix users:

1 From the Import / Export Users page (see Figure 6-33), expand the Export
area.

Figure 6-35 Export Area

of Import / Export Users
Page

2 Click Export; the .csv file is downloaded to your computer.

The exported file can be managed externally in any spreadsheet editor.

Importing / Exporting Users

6

Aeonix Administration Manual Managing Users 6-85

NOTES:
 6.4 Importing LDAP Users

The Aeonix Web Portal supports import of LDAP (Lightweight Directory Access
Protocol) users from an Active Directory or any LDAP based directory according to
predefined LDAP connections (see Defining an LDAP Connection, page 4-55). This
capability allows for using a central LDAP based organizational directory as the
primary reference in the enterprise for user data. Any change in user data in the
directory can then be updated into the Aeonix configuration.
Prior to the import, you can specify the action or actions to perform (import new users,
update existing users, and delete users) according to basic or advanced filtering
options. In addition, you can preview and edit the changes before saving them to the
Aeonix database.
If a user cannot be created, a record including the reason of the failure is written to an
error file. This error file is located under the same directory as the import file and has
the same name extended by ERR. For example, the error file of the import file
NewUsers.csv is called NewUsersERR.csv.

Aeonix does not perform any operations that affect the LDAP values of the
Active Directory.

To import LDAP users from an Active Directory:

1 On the navigation pane, click Administration. The pane displays the
Administration menus.
2 Select the Users menu, and then click Import LDAP Users. The Import
Importing LDAP Users
LDAP Users page is displayed.
6

Aeonix Administration Manual Managing Users 6-87

 Figure 6-36 Import LDAP
Users Page

3 From the LDAP connection drop-down list, select the LDAP connection from
which to import users.

The search settings (Base DN, Filter, and Scope) are displayed as defined
Importing LDAP Users

for the LDAP connection (see Figure 4-25). However, you can override these
settings for specific import instances in steps 4 through 6.

4 Edit the base distinguished name in the Base DN field as required (optional).
5 In the Filter box, edit the search filters to specify which records are returned
by the LDAP Directory Server as required (optional).
6 From the Scope drop-down list, change to one of the following as required
6

(optional):

6-88 Managing Users Aeonix Administration Manual

  Sub tree to search the entire sub tree starting at the base DN level.
 Single level to search immediately below the base DN level.
 Base to only search the named entry (typically used to read one entry).
7 Specify the required Import action by selecting from the following options:
 Add new users—to upload new users from the LDAP Directory.

Figure 6-37 Import All

New Users—Sub-options

In the sub-options that are displayed you can assign default values (optional).

If you do not fill in default values and these values are not imported from
LDAP Directory, Aeonix assigns the same default values as when a new
user is manually created by an administrator of the same level.

 Update existing users—to update existing users from the LDAP Directory.
 Delete users—to delete LDAP users from the Aeonix database.
8 Select the Use these settings in future import check box to save these
settings for subsequent import instances (optional).
9 Click Import. The LDAP User List page is displayed (see Figure 6-38).

If the connection to the LDAP server or LDAP attribute mapping failed, one
or more fields contain incorrect values. Make the required corrections and
click Import again.
Importing LDAP Users
6

Aeonix Administration Manual Managing Users 6-89

 Figure 6-38 LDAP User
List Page

The LDAP User list is sorted by the User ID column. If the list includes more
than one page, use the page navigation bar at the bottom of the list to
navigate between the pages.

10 The LDAP User List page displays the LDAP users that are ready to be
synchronized with the LDAP Directory in the New, Updated, and Deleted
tabs.
11 In each tab, select the users (or click Select all and Clear all for multiple
selections) to synchronize with the LDAP Directory.
Importing LDAP Users

The Updated tab displays the values of both the LDAP Directory (first row)
and the current Aeonix (second row) values. You can edit the values you
want to be saved in the Aeonix database.

12 Click Save Changes. The Save Changes dialog box is displayed.

6

6-90 Managing Users Aeonix Administration Manual

Figure 6-39 Save
Changes Dialog Box

13 Click Yes to synchronize the Aeonix user list with the Active Directory. The
imported users are displayed on the User List page (see Figure 6-1).

In the event of an error message, click Download File to view details in the
newly created LDAPErrorLogFile.cvs file.

Importing LDAP Users

6

Aeonix Administration Manual Managing Users 6-91

NOTES:
 6.5 Associating Users with Groups

Aeonix supports forming groups of specific users. Groups are used for reflecting
organization departments and hierarchies, as well as for applying group-related
services.
User groups and pickup groups are defined and managed in the same way from their
respective list pages (see Group List and Pickup Group List Pages, page 6-93). Managing
groups is described in Defining a Group, page 6-96.
You can add available users and groups as members of a user group, and build a
hierarchy of groups and sub-groups to reflect the organization structure. User groups
also allow you to conveniently include multiple users in another group, instead of
assigning each user separately.
In a pickup group, a call to a member of this group can be retrieved by any member
dialing the group alert call pickup code (see Group Call Pickup, page 2-13).

Other Group Types

Additional group types are described in the following sections:
 Defining ACD Groups, page 12-5
 Defining Call Groups, page 12-59

 Group List and Pickup Group List Pages

Associating Users with Groups

The Group List page displays the user groups defined in the system; the Pickup Group
List page displays the existing pickup groups.
To open these pages:
1 On the navigation pane, click Administration. The pane displays the
Administration menus.
2 Select the Users menu, and then click Group List or Pickup Group List.
6

Aeonix Administration Manual Managing Users 6-93

 Figure 6-40 Group List
Page

Figure 6-41 Pickup Group

List Page

The group lists are sorted by the ID column. If the list includes more than one
page, use the page navigation bar at the bottom of the list to navigate
between the pages.

For each group, the list displays the following information:

Figure 6-42 Group List

Parameters Field Description

Group ID Unique identifier for the group.

NOTE: Once the ID is set, it cannot be modified.

Description A short description of the group (optional)

Closed User The CUG to which the group belongs.

Group
NOTE:

Size The number of items (users or groups) that this group

contains
Associating Users with Groups

From this page, you can perform the following actions:

6

6-94 Managing Users Aeonix Administration Manual

Table 6-6 Actions
Performed from the Action Button Description
Group List Page
Add group Click Add to add a new group (see Defining a Group,
page 6-96).

Update In the list, click the ID of a group to update the

—
group details of this group.
Delete group Select the check box next to one or more groups to
be deleted and then click Delete (see Deleting Entities,
page 3-66).

NOTE: A group that belongs to another group or has a

service assigned cannot be deleted.
Access Click Help to access online help.
online help

Associating Users with Groups

6

Aeonix Administration Manual Managing Users 6-95

  Defining a Group

You can create a group and assign individual users or groups as its members.

To add or update a user group or a pickup group:

1 On the relevant Group List page (see Figure 6-40 or Figure 6-41), click Add
or select a group. The relevant Group page is displayed, as in the following
figure for a new user group.

Figure 6-43 Group Page

2 In the Group ID text box, enter a unique identifier for the group.

The ID of an existing group cannot be modified.

3 In the Description text box, enter a short description of the group (optional).
4 To view the members of a group, select the group from the list and click View
Associating Users with Groups

Group. A tree of the users and sub-groups belonging to the group is displayed
at the bottom of the page.

Below the box, you can use the (right arrow) to display the next items or
the Search box to search for and display specific items in the list.

5 To add a user or group to this group, select it and click (the right arrow).
(You can use the Search box for this purpose.) The selected item is moved to
6

the Assigned box and added to the list of items to be included in the group.

6-96 Managing Users Aeonix Administration Manual

 Repeat this step to add other users or groups.

To remove an item from the Assigned box, select it and click (the left
arrow). You can add multiple users and groups by holding down the CTRL or
SHIFT key while selecting them.

6 Click Save. The new group is added and is included in the list of the Group
List page.

Associating Users with Groups

6

Aeonix Administration Manual Managing Users 6-97

NOTES:
 6.6 Aeonix Clients for Users

Aeonix offers the following advanced desktop UC&C communications applications.

The clients must be locally installed on the user’s workstation, which meets the
hardware and software minimum requirements.

The following features are not supported in A4C:

Sea Attendant
Sea Navigator
FLIPS
TAPI Service Provider & Dialit
Aenix Maintenance Tool

For a detailed description of the installation procedure and minimum

requirements, refer to the client’s corresponding installation or Quick Start
document.

 Sea Attendant – an intelligent communications platform for attendant

positions that effectively streamlines interaction with other users in the system,
and is introduced in Sea Attendant, page 2-37. (For a detailed description of the
Sea Attendant features and usage, refer to the Sea Attendant Online Help.)

In the user’s Feature Configuration profile, under Client Applications, the

corresponding client option must be selected. The number of users that can Aeonix Clients for Users
be authorized to use the Sea Attendant Client depends on the User license
configuration (see Licenses, page 3-29).

 Sea Navigator – an advanced desktop communications manager application

for Aeonix users, and is introduced in Sea Navigator, page 2-39. (For a detailed
description of the Sea Navigator features and usage, refer to the Sea Navigator
Online Help.)
6

Aeonix Administration Manual Managing Users 6-99

 In the user’s Feature Configuration profile, under Client Applications, the
corresponding client option must be selected. The number of users that can
be authorized to use the Sea Navigator Client depends on the User license
configuration (see Licenses, page 3-29)

 Aeonix Contact Center – an advanced, powerful, yet easy-to-use application

with a rich set of telephony and ACD capabilities for Aeonix users, and is
introduced in Aeonix Contact Center, page 2-5. (For a detailed description of the
Visor and Agent features and usage, refer to the corresponding Online Help.)
 FlexIP Softphone (FLIPS) – a comprehensive software-based phone offering
a full range of features and capabilities as well as convenience and flexibility,
and is introduced in FlexIP Softphone, page 2-23. (For a detailed description of
the FLIPS installation and usage, refer to the FlexIP SoftPhone User Guide.)
 TAPI Service Provider and DialIt – a configuration package that allows
system users to make calls directly from their Outlook contacts, and, using
DialIt, make calls from anywhere on their workstation, and is introduced in
Single Sign On, page 2-40. (For a detailed description of the TAPI Service
Provider and DialIt installation and usage, refer to the TAPI Service Provider
Quick Start.)
 Aeonix Maintenance Tool – part of the Aeonix software installation package,
this application allows support personnel to quickly and easily monitor the
Aeonix system, as well as upgrade and rollback Aeonix ecosystem versions
(Aeonix, Aeonix Contact Center, and SeaMail) and is introduced in Aeonix
Record on Demand (RoD) with SeaMail), page 2-7. (For a detailed description of
the tool, refer to the Aeonix Maintenance Tool Reference Manual.)
 Aeonix Touch – a comprehensive, feature-rich unified communications
softphone client for Aeonix users, and is introduced in Aeonix Touch, page 2-8.
(For a detailed description of Aeonix Touch, refer to the Aeonix Touch
Reference Manual.)
Aeonix Clients for Users

Users can download and install the clients by themselves from the Aeonix
Web Portal for users. For details, refer to the Aeonix Configuration Guide
for End Users (see Related Documentation, page 1-17).
6

6-100 Managing Users Aeonix Administration Manual

 The client download procedures are described in the following sections:
 Downloading the Sea Navigator / Sea Attendant Client, page 6-102
 Downloading the Visor / Agent Client, page 6-103
 Downloading the FlexIP Softphone (FLIPS), page 6-104
 Downloading the TAPI Service Provider and DialIt, page 6-105
 Downloading the Aeonix Maintenance Tool, page 6-106
 Downloading Aeonix Touch, page 6-107

Aeonix Clients for Users

6

Aeonix Administration Manual Managing Users 6-101

  Downloading the Sea Navigator / Sea Attendant Client

To download the Sea Navigator / Sea Attendant client onto a user’s

workstation:

To download on your own workstation, navigate to Settings, Downloads.

1 On the user’s workstation, log in to the Aeonix Web Portal (see Logging in to
Aeonix, page 3-8).
2 On the navigation pane, click Settings. The pane displays the Settings menus.
3 Select the Downloads menu, and then click Navigator / Attendant Client.
The Navigator / Attendant Console Client Download page is displayed.

Figure 6-44 Navigator /

Attendant Console Client
Download Page

4 Click Download. A standard File Download dialog box is displayed,

prompting you to run or save the Client setup.exe file.
5 Download the file in either of the following ways:
 To run the file without saving it first, click Run.
 To save the file at a specified location before running it, click Save, save it
at the required location, and then double-click it.

To learn how to install, configure, upgrade, and uninstall the client, refer to
the Sea Navigator or Sea Attendant Quick Start. To learn how to use the Sea
Navigator and Sea Attendant, refer to the corresponding online help.
Aeonix Clients for Users


6

6-102 Managing Users Aeonix Administration Manual

  Downloading the Visor / Agent Client

To download the Aeonix Contact Center Visor / Agent client onto a user’s
workstation:
1 On the user’s workstation, log in to the Aeonix Web Portal (see Logging in to
Aeonix, page 3-8).
2 On the navigation pane, click Settings. The pane displays the Settings menus.
3 Select the Downloads menu, and then click Aeonix Contact Center. The
Aeonix Contact Center Download page is displayed.

Figure 6-45 Aeonix

Contact Center Download
Page

4 Click the appropriate Download button. The selected file is downloaded.

You can run the .msi installer for Aeonix Contact Center Agent for a first-time
installation on the client PC by launching it with a Double-Click. For an
upgrade installation over an existing installation, the .msi installer must be
copied to the PC hard disk. Then the following command must be from a
Windows Command Shell:
Aeonix Clients for Users
msiexec /i Aeonix_Contact_Center_Agent_3.2.111.msi
REINSTALLMODE=vomus REINSTALL=all

The .msi installer can also be used for group installations under policy by the
Aeonix Administrator / IT team.
6

Aeonix Administration Manual Managing Users 6-103

  Downloading the FlexIP Softphone (FLIPS)

To download the FlexIP Softphone (FLIPS) client onto a user’s workstation:

To download on your own workstation, navigate to Settings, Downloads.

1 On the user’s workstation, log in to the Aeonix Web Portal (see Logging in to
Aeonix, page 3-8).
2 On the navigation pane, click Settings. The pane displays the Settings menus.
3 Select the Downloads menu, and then click FlexIP Softphone Client. The
FlexIP Softphone Client Download page is displayed.

Figure 6-46 FlexIP

Softphone Client
Download Page

4 Click Download. The SoftphoneSetup.zip file is downloaded.

To learn how to install, configure, and use the FlexIP Softphone client, refer
to the FlexIP Softphone User Guide and online help.
Aeonix Clients for Users
6

6-104 Managing Users Aeonix Administration Manual

  Downloading the TAPI Service Provider and DialIt

To download the TAPI Service Provider and DialIt application onto a user’s
workstation:

To download on your own workstation, navigate to Settings, Downloads.

1 On the user’s workstation, log in to the Aeonix Web Portal (see Logging in to
Aeonix, page 3-8).
2 On the navigation pane, click Settings. The pane displays the Settings menus.
3 Select the Downloads menu, and then click TSP and DialIt Application. The
TAPI Service Provider (TSP) Download page is displayed.

Figure 6-47 TAPI Service

Provider (TSP) Download
Page

4 Click Download. The Tapi_DialIt.zip file is downloaded.

To learn how to install, configure, and use the TAPI Service Provider and
DialIt application, refer to the TAPI Service Provider Quick Start.

Aeonix Clients for Users

6

Aeonix Administration Manual Managing Users 6-105

  Downloading the Aeonix Maintenance Tool

To download the Aeonix Maintenance Tool onto your workstation:

To download on your own workstation, navigate to Settings, Downloads.

1 On your workstation, log in to the Aeonix Admin (see Logging in to Aeonix,

page 3-8).
2 On the navigation pane, click Settings. The pane displays the Settings menus.
3 Select the Downloads menu, and then click Aeonix Maintenance Tool. The
Aeonix Maintenance Tool Download page is displayed.

Figure 6-48 Aeonix

Maintenance Tool
Download Page

4 Click Download. The Aeonix Maintenance Tool zip file is downloaded.

To learn how to run and use the Aeonix Maintenance Tool, refer to the
Aeonix Maintenance Tool Reference Manual.
Aeonix Clients for Users
6

6-106 Managing Users Aeonix Administration Manual

  Downloading Aeonix Touch

To download the Aeonix Touch client to a user’s workstation:

To download on your own workstation, navigate to Settings, Downloads.

1 On the user’s workstation, log in to the Aeonix Web Portal (see Logging in to
Aeonix, page 3-8).
2 On the navigation pane, click Settings. The pane displays the Settings menus.
3 Select the Downloads menu, and then click Aeonix Touch. The Aeonix Touch
Download page is displayed.

Figure 6-49 Aeonix Touch

Download Page

4 Click Download. The Aeonix Touch zip file is downloaded.

Aeonix Administrators can download an MSI package to use for distributing

the Aeonix Touch installation through the group policy.

To learn how to use Aeonix Touch, refer to the Aeonix Touch Reference
Manual.

Aeonix Clients for Users

6

Aeonix Administration Manual Managing Users 6-107

Aeonix Clients for Users
6

6-108 Managing Users Aeonix Administration Manual

 Chapter 7

Managing Phones

7.1 Phones..................................................................................7-1

7.2 Configuring Phones in Aeonix ..............................................7-9

7.3 Phone Templates ................................................................7-25

Aeonix Administration Manual

 7.1 Phones

This section describes how to define a phone device in Aeonix, including in the
Wave Gateway and TGW units. To learn about how to program phone buttons,
see Phone Profiles, page 5-54.
Phones are physical devices on which users place and receive calls. A phone can be a
telephone, a handset, or a workstation with virtual telephone software running. It is
necessary to define telephones in Aeonix before any calls can be routed to them.
It is important to remember that for the purposes of a VoIP system, the physical
location of the phone is not relevant. That is, if an IP phone is moved from one office
to another, the system recognizes the phone and not the extension number of the local
outlet as with a traditional phone. This means that when a user moves to another office,
the user simply has to take the telephone to the new office, and the call is automatically
routed to this phone.
Furthermore, if Support guest login is set, a user can log into any phone and the relevant
definitions for this user profile will apply to the phone. A user can even have more than
one set of definitions for the phone, for example, to set different speed dial buttons for
home and office. Logging in to and making use of a phone is described in the User
Guide of the relevant phone (see Related Documentation, page 1-17).
With SIP-based virtual software telephone applications (softphones), the actual
workstation running the SIP softphone is not the phone device– the softphone
application is. Therefore, the phone is set at any workstation where the user installs
and logs onto the SIP softphone. Moving the physical workstation has no effect on this
definition.
Users can have multiple concurrently active telephony devices. When setting a user
feature or changing user presence the change affects all the user's devices.
 Presence – For example, when the user is in a call, all of the user’s devices
will reject new calls (unless Call Waiting is enabled by the user).
Phones

 Incoming Calls – All of the user’s phones will simultaneously ring (default
ring policy).
7

Aeonix Administration Manual Managing Phones 7-1

 Concurrent multiple calls of the same user can be handled as long as Call
Waiting is activated in the user profile.

 MWI – the message waiting indicator lamp (if exists) on all of the user’s
phones will light if a message is left for the user.
 DND – When Do Not Disturb is set on any of the user’s phones, all of them
will ignore regular incoming calls, as well as voice page and zone page calls.
 FWD – All of the user’s phones will forward calls in the same manner
(according to the user’s incoming call routing rules).

This section describes the following:

 The phones available in the system are listed on the Phone List Page, page 7-3
 Configuring Phones in Aeonix, page 7-9
 Defining default settings for new phones in Phone Templates, page 7-25
Phones
7

7-2 Managing Phones Aeonix Administration Manual

  Phone List Page

To open the Phone List page:

1 On the navigation pane, click Administration. The pane displays the
Administration menus.
2 Select the Phones menu, and then click Phone List.

Figure 7-1 Phone List

Page

The Phone List page displays the phones configured in the system. It also contains an
area in which search criteria can be defined to find and display specific phones.
The phones listed with a green circle icon are currently registered in Aeonix. Click
Refresh to manually update the list.
Phones
7

Aeonix Administration Manual Managing Phones 7-3

 The status icons on this page automatically refresh every minute.
For Wave Gateway phones (stations), a card’s phone list includes only the
phones belonging to this card (see Chapter 10, Managing VOIP Gateways).
The list displays up to 10 rows by default. To change the number of rows
displayed, enter the number in the Rows per page field and click Set.
The phone list is sorted by the ID column. If the list includes more than one
page, use the page navigation bar (see Table 6-1) at the bottom of the list to
navigate between the pages.

For each phone, the list displays the following information.

Table 7-1 Phone List

Parameters Field Description

Status icon A circle icon to the left of each phone indicates the following:
(circle)  Green - that the phone is registered in the system
 Red - that the phone is not registered
 Green/Red -
Changes made in Aeonix are currently not synchronized with
the phone. Once provisioning is executed and, as a result,
synchronization between Aeonix and the phone is restored, the
icon will revert to green.

NOTE: The lack of synchronization can result from a mismatch of

provisioning parameters or firmware between Aeonix and
the phone.
 Red ‘do not enter’ - the system has blocked the SIP phone
from registering. The system blocks the registration for 10
minutes after 3 failed attempts to verify the password.

NOTE: View the icon’s tooltip for more information (for example,
the tooltip for the red ‘do not enter’ icon indicates the time
remaining before the specified server stops blocking the
registration.

ID Unique identifier for the specific phone device.

NOTE: Once the ID is set, it cannot be modified.

Description Optional text description of the phone. This can include the name
of the user, the serial number, or another identifying label on the
physical phone.
Phones

NOTE: For a phone defined through a user’s Phone tab (under

New Phone Configuration), the default description is
phone of <User ID>.
7

7-4 Managing Phones Aeonix Administration Manual

 Field Description

Default User The default user defined for this phone (if any). The default user
is automatically logged into the system if the phone is registered.
Click the user entity to view or modify its details (see Defining a
User, page 6-9).

Model The model of the phone (see Table 7-4 on page 7-10 for a list of
possible phone types)

Registered on The Aeonix server on which the phone device is registered. This
information is of importance in clusters of multiple servers.

IP Address The IP address (IPv4 or IVp6) assigned to the phone (if any).
This address is defined on the phone and retrieved from the
Aeonix system when the phone is registered.

Phone List Page Actions

From the Phone List page, you can perform the following actions:

Table 7-2 Actions

Performed from the Action Button / Icon Description
Phone List Page
Add phone Click Add to add a new phone (see Defining a Phone in
Aeonix, page 7-10).

Update In the list, click the phone ID to update the details of

—
phone this phone.
Delete Select the check box next to the phone or phones to
phone be deleted and then click Delete (see Deleting Entities,
page 3-66).
Unblock Select the check box next to the SIP phone or
phone phones with the Not Registered (Blocked) Red ‘do
not enter’ status icon, and then click Unblock.

NOTE: To avoid being re-blocked, it is recommended

to correct the security parameters of the
phone before clicking this button.
Refresh Click Refresh to update the list to the current status.
display

Click Back to return to the previous page.

Phones

Go back

NOTE: Only displayed when accessing the list from

another page.
Click Help to access online help.
7

Access
online help

Aeonix Administration Manual Managing Phones 7-5

 Action Button / Icon Description
Clone phone Click this icon to create a duplicate of a specific
details phone.

Search for Click to display the Search area, define search

phones values, and then click Apply to search for existing
phones (see Searching for Phones, page 7-7).
Click Reset to remove entered values from the
search configuration fields. This allows you to define
and start a new search.
Phones
7

7-6 Managing Phones Aeonix Administration Manual

 Searching for Phones
In the search area at the top of the phone list, you can search for specific phones
according to the specified search criteria described in Table 7-3 on page 7-7.
Click the Search button to display the search fields and fill in one or more fields as
required. When you start filling in the ID, Description, or Default user, all existing
entities containing the entered value are displayed below the field. Select the required
value (if available) or type it in.
Click Search to filter the display by the entered criteria. The list will include all
phones that have values corresponding to the search values or containing them in the
relevant fields.

Table 7-3 Phone Search

Criteria Search Criteria Search Results

ID Phones that contain the specified search value in their ID

field

Status Phones that have one of the following statuses:

 All - All phones
 Registered - Phones that are registered in the system
 Not Registered - Phones that are not registered in the
system
 Not Provisioned - Phones that are either pending
provisioning or that there firmware version is not
synchronized with the system

Description Phones that contain the specified text in their Description

field

Default user Phones that contain the specified search value in their
Default user field

Type Phones that match the specified phone type in their Type
field. Select All to search for all phone types.

IP address Phones that include the specified search value in their IP

address field

Registered on Phones that include the specified search value in their

Registered on field
Phones
7

Aeonix Administration Manual Managing Phones 7-7

NOTES:
 7.2 Configuring Phones in Aeonix

This section describes the activities involved in managing phones in the Aeonix Web
Portal:
 Defining a Phone in Aeonix, page 7-10
 Defining the Default User of a Phone, page 7-24
To manage trunks and gateways, use the procedure described in Chapter 8, Managing
Trunks.

Configuring Phones in Aeonix

7

Aeonix Administration Manual Managing Phones 7-9

  Defining a Phone in Aeonix

Each phone must be defined in the Web Portal to operate in the Aeonix system.

The only phone type that is supported in A4C is “SIP Terminal”. All other
phone types are not supported.

A user’s phones can also be directly defined through the user’s page, as
described in Managing a User’s Phones, page 6-56.

Max. 3,200 registered endpoints (phones+trunks) per server (Dell R610).

Max. 8 servers per cluster.
Max. 25,000 registered endpoints per cluster.

To add or update a phone:

1 In the navigation pane, select the Phones menu, and then do one of the
following:
 To define a new phone, click Add Phone, and then select the phone type as
described in the following table.

Table 7-4 Phone Types

Phone Type When To Select

Tadiran MGCP For a FlexSet-IP 280S, T207M, T208M, T207M/NP,

T208M/BL phone
Configuring Phones in Aeonix

FlexIP softphone For a FlexIP Softphone (FLIPS)

SIP terminal  For a Tadiran SIP phone (see Supported Devices,

page 1-12)
 For a P-Series phone (P-335, P-450)
 For a third-party SIP phone, a SIP softphone
(including SeaBeam), or an analog phone
connected through a SIP-based Coral Teleport
FXS gateway
7

7-10 Managing Phones Aeonix Administration Manual

 Phone Type When To Select

Wave Gateway station For an analog phone or a digital keyset connected

through a Wave Gateway.
(SLT, FlexSet 120, 120D, 120L, 120S, 121S, 280,
280D 280D-HS, 280S, 281S, DKT, CPA and DST).
To learn about the Wave Gateway, see Chapter 10,
Managing VOIP Gateways.

 To update an existing phone, click Phone List and select the relevant ID in
the list.
 To create a copy of an existing phone, click Phone List. On the Phone List
page (see Figure 7-1), click (the Clone icon) to the right of the
relevant phone.

When you clone a phone, all parameter values are copied to the new phone
except for the Phone ID and the Closed User Group.

The Phone page displays the phone parameters as in the following figure for a
new Tadiran SIP phone.

Figure 7-2 Phone Page

for a New Tadiran SIP
Phone - General Tab

Configuring Phones in Aeonix

2 If this is a new phone, define the Phone ID fields as described in Table 7-5:
 In the first field (before the @ sign), enter the phone name.
7

Aeonix Administration Manual Managing Phones 7-11

  In the second field (after the @ sign), enter the name of the domain to
which the phone is connected. The default domain name of Aeonix is
aeonix.com, but it can be changed as long as no phones and trunks have
been defined (see System Parameters, page 14-27).

Table 7-5 Phone ID

Definition Phone Type Device Name When To Select

Tadiran MGCP MAC address of aeonix.com

terminals / the phone. (or Aeonix domain)
softphones
Example:
00:0a:6b:00:
00:1e

SIP terminals / SIP user name aeonix.com

P-Series of the phone. (or Aeonix domain)
phones /
Tadiran SIP
phones

Wave Gateway Wave Gateway <CWG>.<domain>

terminals shelf/slot/card (replace <CWG> with the name of the
assignment of Coral Wave Gateway unit and <domain>
the device with the Aeonix domain).
connected
Example: CWG1.aeonix.com
through the
Wave Gateway.
Example:
0/1/0

3 On the General tab, define the parameters described in Table 7-6 for any
phone type.

Table 7-6 General Phone

Parameters Phone Type When To Select

Closed User Group The Closed User Group to which the phone belongs
Configuring Phones in Aeonix

(Default: Root) (see Closed User Groups (CUG), page 4-29).

NOTE: This field cannot be modified after the phone

is added to the system.

Description Optional description of the phone

Keep-alive timeout Number of seconds between keep-alive messages

(Default: 60 seconds) before the phone is assumed to be malfunctioning

NOTE: This field is not used for Wave Gateway

7

phones.

7-12 Managing Phones Aeonix Administration Manual

 Phone Type When To Select

Location The location where the phone is used (see Locations,

page 4-9).

Sub Location The sub location of the device. See Defining a

Location, page 4-12.

Floor The floor on which the device is located.

Room The room in which the device is located.

Emergency location ID For emergency (“911”) calls, a number indicating

(ELIN) the exact location to the local emergency call center
(PSAP). If this field is filled in, it overrides the
corresponding field value defined for the location
associated with the phone. To learn more about
emergency call configuration, see Defining Emergency
Call Settings, page 4-16.
Depending on the PSAP configuration, the phone
ELIN can be associated with a callback number.

NOTE: Leave this field empty if the phone serves

more than one user, for example, a device in
a call center in which the agent changes with
the work shift.

SIP password (Default: NOTE: This option is only applicable to SIP

Aeonix123@) terminals.
The authentication password used during the phone
registration process. The default password
(Aeonix123@) is automatically generated by the
system during the installation process. It is
recommended to change this initial password
manually or by clicking Generate password.
If you change the password manually, make sure
that it contains at least one digit, one special
character, one upper case letter, one lowercase

Configuring Phones in Aeonix

letter, and is at least 7 characters long.

NOTE: The strength of the password is progressively

displayed below this field and must reach
100% to be accepted.

Default user The user associated by default with the phone. (For
more information, see Defining the Default User of a
Phone, page 7-24).

NOTE: For provisioned SIP phones, the profile

settings of this user are automatically applied
7

to the phone when it is connected.

Aeonix Administration Manual Managing Phones 7-13

 Phone Type When To Select

Ring control (Default:  Always - the phone will ring on all incoming calls
Always)  Internal call - the phone will only ring on
incoming internal calls
 External call - the phone will only ring on
incoming external calls
 Never - the phone will not ring on any incoming
call

Enable fax The method for handling fax calls:

(Default: Strict detection)  Strict detection – Aeonix will allow fax
transmission to this device only if both sides of
the call are detected to be faxes
 Yes – Aeonix will allow fax transmission to this
device if either side of the call is detected to be
initiating a fax transmission
 No – the system will not allow fax transmission to
or from this device

Support guest login Whether users can log in to this phone even if they
(Default: Yes) are not its default user (see above).

NOTE: When guest users log in, their provisioning

profile is loaded to the host phone.

Allow paging Select to permit the phone to receive Voice and

Zone Pages, and to allow Auto Answer.

NOTE: For users with multi-devices, it is

recommended to select this option for the
main device only.

Force logout Select to log out the phone when guest login is
being used.
Configuring Phones in Aeonix

All other phone parameters are derived from the SIP Terminal template (see
Chapter 7, Phone Templates).

4 Click the Provisioning tab (applicable for Tadiran SIP phones and P-Series
phones), and then select the Device model of the phone, such as T328.

Select Auto-Detect if you want the system to automatically detect the phone
model.
7

7-14 Managing Phones Aeonix Administration Manual

Figure 7-3 Provisioning
Tab for Tadiran SIP
Phones and P-Series
Phones (example)

5 In the MAC address field, start filling in the MAC address to display a list of
all the existing MAC addresses containing the entered value, and then select
the required value.

Configuring Phones in Aeonix

Alternatively, for Tadiran SIP phones only, select the adjacent check box, and
then select the phone’s MAC address from the Select from Plug & Play
drop-down list.

6 Select the name of the Provisioning name associated with this phone.
7 View or define the parameters described in Table 7-7.
7

Aeonix Administration Manual Managing Phones 7-15

  The read-only parameters displayed in Table 7-7 are derived from the
selected provisioning profile and can only be edited via the profile itself.
 Making changes to provisioning parameters might cause the phone to
restart after any ongoing calls are disconnected.
 To learn how to define additional configuration sets, see Defining New
Configuration Sets, page 12-130.
 In order for the provisioning profile parameters to take effect, the
parameters of the phone must NOT be changed via the phone or the
phone’s web page.
 For P-Series phones, in the event that conflicting parameter values are
entered either via the phone or the phone's web page, the provisioning
profile parameters will be lost.
 For Tadiran SIP phones, in the event that conflicting parameter values are
entered either via the phone or the phone's web page, the system will use
the provisioning profile parameters.

Table 7-7 Provisioning

Parameters Field Description

SIP server address 1 The IP address (IPv4 or IPv6) or host name of the
first Aeonix server on which the provisioning service
is hosted and on which the phone registers

Port The SIP port of the first Aeonix server on which the
phones are registered on (by default 5060, or, when
transport protocol TLS is used, secured port 5061)

SIP server address 2 The IP address (IPv4 or IPv6) or host name of the
second Aeonix server on which the provisioning
service is hosted and on which the phone registers

Port The SIP port of the second Aeonix server on which

the phones are registered on (by default 5060, or,
Configuring Phones in Aeonix

when transport protocol TLS is used, secured port

5061)

Outbound proxy address The IP address (IPv4 or IPv6) or hostname of the

SIP server or Sentinel Pro to which the phone
sends all requests

Port The port of the outbound proxy server which

manages the phone’s SIP sessions (by default
5060, or, when transport protocol TLS is used,
secured port 5061)
7

7-16 Managing Phones Aeonix Administration Manual

 Field Description

NTP server address 1 The name or IP address (IPv4 or IPv6) of the first
NTP server address according to which time is set
for the phone

NTP server address 2 The name or IP address (IPv4 or IPv6) of the

second NTP server address according to which time
is set for the phone.

NOTE: Only applicable for Tadiran SIP phones.

Dial now rules The dial plan from which to apply the phone’s dial
now rules to the provisioning profile (see Dial Plans,
page 4-19).

NOTE: Auto-Detect indicates that the dial plan of the

CUG with which the user is associated is
used.

LCD logo mode The logo setting for the phone.

NOTE: Only applicable for supported Tadiran SIP

phones.

High availability retry count The number of times the phone attempts to connect
to the server before the phone with fail over to the
next Aeonix server in the cluster.

NOTE: Only applicable for Tadiran SIP phones.

VLAN WAN port active Whether VLAN for the Internet port via the users’
phone interface is set.

VLAN WAN VID The VLAN WAN ID

VLAN WAN priority The VLAN WAN priority (1 to 7)

VLAN PC port active Whether the VLAN for the PC port via the users’
phone is set.

VLAN PC VID The VLAN PC ID Configuring Phones in Aeonix

VLAN PC priority The VLAN PC priority (1 to 7)

VLAN DHCP active Whether the VLAN DHCP discovery via the phone’s
web user interface is set

VLAN DHCP option The VLAN DHCP option (default: 132)

7

Phone firmware The Tadiran SIP phone firmware file

Aeonix Administration Manual Managing Phones 7-17

 Field Description

Maximum simultaneous For phone batches, the maximum number of

firmware upgrades firmware versions that can be simultaneously
loaded into the Aeonix Admin (default: 20).

NOTE: If the limit is reached, any additional phones

requiring firmware upgrade will be serviced in
a subsequent batch.

Provisioning configuration The customized Tadiran SIP phone or P-Series

set phone configuration set associated with this
provisioning profile

Number of line keys The maximum line accounts defined for this phone

NOTE: This field is only displayed for P-Series

phones.

Calls per line The number of active or held calls on the line until a
busy signal is returned to a caller.

NOTE: This field is only displayed for P-Series

phones.

Codecs The In use box displays the codecs currently used

by the phone. To associate an available codec,
select it from the Unused box, and click (the
right arrow). The selected item is moved to the In
use box.

8 Expand the Codecs area to view the codecs currently being used by the phone.

Figure 7-4 Phone Codecs

Configuring Phones in Aeonix

9 To associate an available codec, select it from the Unused box, and click
(the right arrow). The selected item is moved to the In use box.
10 The following table describes additional provisioning parameters that are
defined from other pages of the Aeonix Admin:
7

7-18 Managing Phones Aeonix Administration Manual

Table 7-8 Other
Provisioning Parameters Parameter Description

Automatic The Tadiran SIP and P-Series Firmware files that are
firmware upgrade currently used in Aeonix.

Button label The Local display text displayed on the user’s phone (see
Table 5-12).

ESF protocol The protocol by which the ESF server and phones
communicate with each other - "HTTPS" or "HTTP" (see
Table 5-6).

High Availability Subscriber registration, registration fail retry interval, and

retry counts when Enable High Availability is set (see
Figure 14-14).

Interdigit timeout For Tadiran SIP phones, the Interdigit timeout after which
dialed digits are sent when attempting to establish an
internal call (see Table 5-5).

NOTE: Digits can still be sent by pressing the pound (#) sign.

LDAP directory The following parameters and corresponding default values

are used when provisioning supported Tadiran SIP phones
with the LDAP directory:
 Enable LDAP – Enabled
 LDAP Name Filter –
(|(displayName=%)(sn=%)(givenname=%))
 LDAP Number Filter – (telephoneNumber=%)
 Server Address – [IP address / host name of
Aeonix server]
 Port – 389
 Base – dc=directory,dc=com
 LDAP Name Attributes – displayName
 LDAP Number Attributes – telephoneNumber
 LDAP Display Name – %displayName
 Directory – LDAP
 LDAP Lookup For Incoming Call – Disabled

Configuring Phones in Aeonix

 LDAP Lookup For Callout – Disabled

Offset time from The Time zone according to the Location of the phone (see
GMT Table 4-7 and Table 7-6).

Phone emergency The Local emergency number to which emergency calls

number are routed according to the Location of the phone (see
Figure 4-5 and Table 7-6).

Phone web The Phone password used for allowing enhanced SIP
Features functionally and for accessing the phone’s web
7

interface
password portal (see Table 5-6).

Aeonix Administration Manual Managing Phones 7-19

 Parameter Description

Provisioning The interval check period used for new phone configurations
polling interval and firmware updates (see Figure 12-67).

SIP account The Device Name of the SIP phone (see Table 7-5).
authorization
name

SIP account The SIP password used during the phone registration
authorization process (see Table 7-6).
password

SRTP The transportation type and the voice encryption settings

based on the Required security level - "Unencrypted" or
"Best Effort" encrypted (see Table 5-4).

Time DST The system’s Daylight Savings Time based on the phone
location time zone.

Time format The Time format (12 or 24 hours) in which the time is
displayed for the user (see Table 5-4).

User display name The Display name of the logged in user as shown on the
user’s phone (see Table 6-5).

User DSS keys The Programmable buttons assigned to the logged in user
(see Table 5-13).

Voicemail number The Voice mail service Alias associated with the user’s
voicemail (see Figure 6-8).

11 For a SIP phone, click the Advanced tab.

Configuring Phones in Aeonix
7

7-20 Managing Phones Aeonix Administration Manual

Figure 7-5 Advanced Tab
for SIP Phones

12 Define the SIP session handling parameters described in Table 7-9.

Table 7-9 SIP Session

Handling Parameters for Field Description
SIP Phones
Requires session Select Yes if Aeonix initiates calls with session timer refresh,
timer which is used to determine whether the SIP session is still
active.

NOTE: If you are configuring a Yealink CP860 or CP920

conference phone (non-Tadiran firmware), set this field
to No. In the Yealink phone configuration, under the
Account tab, configure only one SIP server (i.e. leave
the fields under SIP Server 2 empty).

Session-Expires The Aeonix proposal time for the Session-Expires Time (in

Configuring Phones in Aeonix

Time seconds). For Permanent Connect for Room Recording, set to 90
seconds and set on the device side (in the Account,
Advance tab).

NOTE: This field is only relevant if the field Require session

timer is set to Yes.
7

Aeonix Administration Manual Managing Phones 7-21

 Field Description

Minimum The minimum Session Expires Time value (between 90

Session-Expires and 10000) agreed upon by both call parties.

NOTE: For Permanent Connect for Room Recording, it is

recommended to leave the default value (90 seconds)
to prevent the room recording device from staying
connected after an Aeonix system restart. The
Session Expires parameter should also be set on the
device side (in the Account, Advance tab).

Requires PRACK Currently not in use

Authenticate Currently not in use

inbound messages

Send 181 - when Determines whether or not SIP message 181 is sent when a
call is forwarded call is forwarded. Select Yes to send SIP message 181.
Select No not to send SIP message 181.

Supported transfer Select Refer if the REFER command can be used for call
method transfer. Select Re-Invite if the RE-INVITE command can be
used for call transfer.

NOTE: This field is device dependent. Most SIP service

providers only support RE-INVITE.

NOTE: If you are configuring a Yealink CP860 or CP920

conference phone (non-Tadiran firmware), set this field
to Re-Invite. In the Yealink phone configuration, under
the Account tab, configure only one SIP server (i.e.
leave the fields under SIP Server 2 empty).

Ringback tone Whether the ringback tone is provided by the local phone or
by Aeonix. Select from the following:
 Provided by local phone (180) - local ringback (default
option)
 Provided by Aeonix (183+SDP) - Aeonix ringback
Configuring Phones in Aeonix

Waiting tone Whether the waiting tone is provided by the local phone or
by Aeonix. Select from the following:
 Provided by local phone (182) - local ringback
 Provided by Aeonix (183+SDP) - Aeonix ringback
(default option)
7

7-22 Managing Phones Aeonix Administration Manual

 Field Description

Call progress tone Whether the call progress tone is provided by the local
phone or by the destination phone, or the call is considered
as being answered (for billing purposes). Select from the
following:
 Provided by remote side (183+SDP) - by remote side
(default option)
 Provided by local phone (180) - by local phone
 Answer the call (200+SDP) - call is answered

Send Invite to Determines when to send the INVITE WITH REPLACES

transfer target response. Select Before consultation answer to send the
INVITE response before the 3rd party answers a two-step
transfer on alert. Select After consultation answer to send
the INVITE response after the 3rd party answers a two-step
transfer on alert. This field is device dependent.

Alarm agent Reflects the current agent mode of the phone (Yes indicates
that the DTMF transport method is set to SIP INFO and No
indicates that it is set to RFC 2833). You can change this
setting, thereby changing the setting in the phone’s
corresponding “DTMF Type” entry (for phones that support
provisioning) accordingly. This synchronization allows you to
change the agent mode for phones that are either not ESF
enabled or do not have an Alarm agent button defined.

NOTE: Upon Aeonix system restart, the currently set phone

mode will be retained.

13 Click Save to add the phone to the system.

Configuring Phones in Aeonix

7

Aeonix Administration Manual Managing Phones 7-23

  Defining the Default User of a Phone

A phone is usually assigned a default user. This can be done when adding the phone
to the system or while updating an already existing phone.

If a phone is added from a User page, the user is automatically defined as

the default user of this phone. In this case, there is no need to manually
assign the default user.

When a phone is connected, it automatically uses the default user’s relevant phone
profile settings (if existing), which include features such as speed dial buttons. For
details about setting a profile, see Configuring a User’s Phone Profiles, page 6-49.

To define the default user of a phone:

1 On the relevant Phone page (see Figure 7-2), enter any character of the
relevant user’s first name, last name, or login name in the Default user field
and select the user from the list displayed below the field.
2 If necessary, enter or update the other parameters. (For details, see Defining a
Phone in Aeonix, page 7-10.)
3 Click Save. The phone is assigned a default user.
Configuring Phones in Aeonix
7

7-24 Managing Phones Aeonix Administration Manual

 7.3 Phone Templates
(Applied to New Phones)

A phone template defines the initial default values for a phone of a specific type. When
a phone is added to the system, it is automatically assigned the appropriate default
values. Unlike profiles (see Chapter 5, Profiles), phone template values are only
applied to new phones. Changes in a template are not reflected in phones that have
already been defined in Aeonix.
For each phone type, the system includes a template. You cannot add or remove
templates, but you can modify the template values.

To edit the template of a phone type:

1 On the navigation pane, click Administration. The pane displays the
Administration menus.
2 Select the Phones menu, and then click Phone Template. The available phone
types are listed on the navigation pane (see Table 7-4).
3 Select the relevant phone type. The Phone Template page displays the fields of
the phone type, as in the following figure for Tadiran MGCP phones
(FlexSet-IP 280S, T207M, T208M, T207M/NP, T208M/BL).

Figure 7-6 Phone

Template Page for MGCP
Phones (FlexSet-IP 280S,

Phone Templates (Applied to New Phones)

T207M, T208M, T207M/NP,
T208M/BL)

Aeonix Administration Manual Managing Phones 7-25

 4 Fill in the fields as described in Table 7-6. (The fields Closed User Group and
Default user are not available for phone templates.)
5 Click Save to save the template.
Phone Templates (Applied to New Phones)
7

7-26 Managing Phones Aeonix Administration Manual

 Chapter 8

Managing Trunks

8.1 Trunks ...................................................................................8-1

8.2 Configuring Trunks in Aeonix................................................8-9

8.3 Trunk Templates .................................................................8-27

Aeonix Administration Manual

 8.1 Trunks

Trunks are the channels through which Aeonix trunk groups route calls. A trunk can
be a SIP trunk, SIP gateway trunk, or Coral IPnet trunk. It is necessary to define trunks
in Aeonix before any calls can be routed through them.
Trunks must be assigned to trunk groups to operate in the system. A trunk group can
be a SIP gateway trunk or Wave Gateway telephony system. To learn more about trunk
groups, see Chapter 9, Managing Trunk Groups.
The trunks available in the system are listed on the Trunk List Page.

Changing any aspect or parameter of trunks which are present in the Trunk
List page is not allowed in A4C.

Configuring the trunks is described in Configuring Trunks in Aeonix, page 8-9; defining
default settings for new trunks is described in Trunk Templates, page 8-27.

Table 8-1 Trunk Types

Trunk Type When To Select

Coral (IPnet) For a Coral IPx/FlexiCom PBX

SIP Trunk and Gateway For a SIP trunk (such as Aeonix Contact Center)
and SIP gateway (such as: Tadiran TGW,
AudioCodes M/MP) or for a SIP-based
Coral Teleport FXO gateway trunk

Wave Gateway trunk For an E&M (ear and mouth) trunk connected
(E&M) through a Wave Gateway

Wave Gateway trunk For an LS/GS (loop start/ground start) trunk

(LS/GS) connected through a Wave Gateway.

Wave Gateway trunk For an MFC (multi-frequency code signaling) trunk

Trunks

(MFC) connected through a Wave Gateway

Wave Gateway trunk (PRI For a PRI ISDN trunk connected through a
8

ISDN) Wave Gateway

Aeonix Administration Manual Managing Trunks 8-1

 Trunk Type When To Select

Wave Gateway trunk (PRI For a PRI QSIG trunk connected through a
QSIG) Wave Gateway

Coral (IPnet) For a Coral IPx/FlexiCom PBX

 Trunk List Page

To open the Trunk List page:

1 On the navigation pane, click Administration. The pane displays the
Administration menus.
2 Select the Trunks menu, and then click Trunk List.

Figure 8-1 Trunk List

Page
Trunks
8

8-2 Managing Trunks Aeonix Administration Manual

 The Trunk List page displays the trunks configured in the system. It also contains an
area in which search criteria can be defined to find and display specific trunks.
The top of the page provides the following general information about all trunks:

Table 8-2 General Trunks

Information Parameter Description

SIP trunk / gateway The maximum number of concurrent SIP trunk or gateway
licenses calls that can be transmitted via trunks or gateways

Used The total number of licenses used by all trunks

Reserved The total number of licenses that are reserved

Used on reserved The total number of licenses being used by all reserved
trunks trunks

The trunks listed with a green circle icon are currently registered in Aeonix. Click
Refresh to manually update the list.

The status icons on this page automatically refresh every minute.

For Wave Gateway trunks, a card’s trunk list includes only the trunks
belonging to this card (see Chapter 10, Managing VOIP Gateways).
The list displays up to 10 rows by default. To change the number of rows
displayed, enter the number in the Rows per page field and click Set.
The trunk list is sorted by the ID column. If the list includes more than one
page, use the page navigation bar (see Table 6-1) at the bottom of the list to
navigate between the pages.

For each trunk, the list displays the following information.

Trunks
8

Aeonix Administration Manual Managing Trunks 8-3

 Table 8-3 Trunk List
Parameters Field Description

Status icon A circle icon to the left of each Wave Gateway trunk indicates the
(circle) following:
 Green - the trunk is registered in the system and logged in to
a trunk group.
 Red - the trunk is not registered in the system or not logged in
to a trunk group.
 Blue - N/A
 Red/Green - N/A

A circle icon to the left of each SIP and IPnet Gateway indicates
the following:
 Green - the trunk is registered in the system and logged in to
a trunk group.
 Red - the trunk is not registered in the system.
 Blue - the trunk registration status is unknown.
 Red/Green - the trunk is registered in the system but not
logged in to a trunk group.

ID Unique identifier for the specific trunk.

NOTE: Once the ID is set, it cannot be modified.

Description Optional text description of the trunk. This can include the name
of the trunk, the serial number, or another identifying label.

Default Trunk The ID of the default trunk group defined for this trunk (if any).
Group The default trunk group is automatically logged into the system if
the trunk is registered.
Click the trunk group entity to view or modify its details
(see Defining a Trunk Group, page 9-5).

NOTE: The display name of the default trunk group is displayed in

addition to the trunk group ID, if it has been defined.

Type The type of the trunk (see Table 8-5 on page 8-10 for a list of
possible trunk types)

Registered on The Aeonix server on which the trunk device is registered. This
information is of importance in clusters of multiple servers.

IP Address The IP address and port assigned to the trunk. This address is
defined on the trunk and retrieved from the Aeonix system when
the trunk is registered.
Trunks

Reserved The total number of licenses that are reserved for the trunk.
Licenses
8

8-4 Managing Trunks Aeonix Administration Manual

 Field Description

Max The maximum number of concurrent calls that can be made via
Concurrent the trunk.
Calls

Used The total number of licenses used for the trunk.

Trunks
8

Aeonix Administration Manual Managing Trunks 8-5

 Trunk List Page Actions
From the Trunk List page, you can perform the following actions:

Table 8-4 Actions

Performed from the Action Button / Icon Description
Trunk List Page
Add trunk Click Add to add a new trunk (see Defining a Trunk in
Aeonix, page 8-10).

Update trunk In the list, click the trunk ID to update the details of
—
this trunk.
Delete trunk Select the check box next to the trunk or trunks to
be deleted and then click Delete (see Deleting Entities,
page 3-66).
Refresh Click Refresh to update the list to the current status.
display

Go back Click Back to return to the previous page.

NOTE: Only displayed when accessing the list from

another page.
Access Click Help to access online help.
online help

Clone trunk Click this icon to create a duplicate of a specific

trunk.

Search for Click to display the Search area, define search

trunks values, and then click Apply to search for existing
trunks (see Searching for Trunks, page 8-7).
Click Reset to remove entered values from the
search configuration fields. This allows you to define
and start a new search.
Trunks
8

8-6 Managing Trunks Aeonix Administration Manual

 Searching for Trunks
In the search area at the top of the trunk list, you can search for specific trunks
according to the fields mentioned in Table 8-3 on page 8-4.
Click the Search button to display the search fields and fill in one or more fields as
required. When you start filling in the ID, Description, or Default trunk group, all
existing entities containing the entered value are displayed below the field. Select the
required value (if available) or type it in.
Click Search to filter the display by the entered criteria. The list will include all trunks
that have values corresponding to the search values or containing them in the relevant
fields.

Trunks
8

Aeonix Administration Manual Managing Trunks 8-7

NOTES:
 8.2 Configuring Trunks in Aeonix

This section describes the activities involved in managing trunks in the system:
 Defining a Trunk in Aeonix, page 8-10
 Defining the Default Trunk Group of a Trunk, page 8-25
To manage phones, use the procedure described in Chapter 7, Managing Phones.

Configuring Trunks in Aeonix

8

Aeonix Administration Manual Managing Trunks 8-9

  Defining a Trunk in Aeonix

Each trunk must be defined in the Aeonix Web Portal to operate in the Aeonix system.

To add or update a trunk:

1 In the navigation pane, select the Trunks menu, and then do one of the
following:
 To define a new trunk, click Add Trunk, and then select the trunk type as
described in the following table.

Table 8-5 Trunk Types

Trunk Type When To Select

Coral (IPnet) For a Coral IPx/FlexiCom PBX

SIP Trunk / For a SIP Internet trunk or SIP gateway (such as: Tadiran
Gateway TGW, AudioCodes M/MP) or for a SIP-based
Coral Teleport FXO gateway trunk

Wave Gateway For an E&M (ear and mouth) trunk connected through a
trunk (E&M) Wave Gateway

Wave Gateway For an LS/GS (loop start/ground start) trunk connected

trunk (LS/GS) through a Wave Gateway.

Wave Gateway For an MFC (multi-frequency code signaling) trunk

trunk (MFC) connected through a Wave Gateway

Wave Gateway For a PRI ISDN trunk connected through a Wave Gateway
trunk (PRI ISDN)

Wave Gateway For a PRI QSIG trunk connected through a Wave Gateway
trunk (PRI QSIG)

NOTE: For a description of the Wave Gateway and its configuration see Chapter 10,
Managing VOIP Gateways.
Configuring Trunks in Aeonix

 To update an existing trunk, click Trunk List and select the relevant ID in
the list.
 To create a copy of an existing trunk, click Trunk List. On the Trunk List
page (see Figure 8-1), click (the Clone icon) to the right of the
relevant trunk.
8

8-10 Managing Trunks Aeonix Administration Manual

 When you clone a trunk, all parameter values are copied to the new trunk
except for the Trunk ID and the Closed User Group. In addition, the selection
of servers and entered UGW addresses are not copied to a new Coral IPnet
trunk.

The Trunk page displays the trunk parameters as in the following figure for a
new Coral IPnet trunk.

Figure 8-2 Trunk Page for

a New Coral IPnet Trunk

2 If this is a new trunk, define the Trunk ID fields as described in the following
table:
 In the first field (before the @ sign), enter the trunk name.
 In the second field (after the @ sign), enter the name of the domain to
which the trunk is connected. The default domain name of Aeonix is
aeonix.com, but it can be changed as long as no phones and trunks have
been defined (see System Parameters, page 14-27).

Configuring Trunks in Aeonix

Table 8-6 Trunk ID
Definition Trunk Type When To Select

SIP trunks and The SIP User Name aeonix.com (or Aeonix
gateways domain)

Coral units Any descriptive name aeonix.com (or Aeonix

domain)
8

Aeonix Administration Manual Managing Trunks 8-11

 Trunk Type When To Select

Wave Gateway The trunk name of the <CWG>.<domain>

trunks device connected through (replace <CWG> with the name
the Wave Gateway. of the Coral Wave Gateway
Example: 0/1/0 unit and <domain> with the
Aeonix domain).
Example: CWG1.aeonix.com

3 Fill in the fields as described in Trunk Parameters, page 8-13.

4 Click Save to add the trunk to the system.
Configuring Trunks in Aeonix
8

8-12 Managing Trunks Aeonix Administration Manual

  Trunk Parameters

The following tables list the various parameters that are defined for a trunk:

All other trunk parameters are derived from the SIP Trunk template (see
Chapter 8, Trunk Templates).

 Table 8-7 describes the parameters that are defined on the General tab for
trunks of any type.
 Table 8-8 describes the parameters on the Configuration tab of Coral IPnet
trunks.
 Table 8-9 describes configuration and SIP session related parameters for SIP
trunks and gateways. These parameters are available on the Configuration tab
of SIP trunks and gateways, and are applicable to all registration modes.
 Table 8-10 describes SIP registration parameters. These parameters are
available on the Configuration tab for SIP trunks and gateways that are
registered to external systems.
 Table 8-11 describes SIP registration parameters. These parameters are
available on the Configuration tab for SIP trunks and gateways that are
registered to Aeonix systems.
 Table 8-12 describes SIP registration parameters. These parameters are
available on the Configuration tab for SIP trunks and gateways that are not
registered to any server.
 Table 8-13 describes the in-line call destination parameters on the
Configuration tab of Wave Gateway trunks.
 Table 8-14 describes SIP protocol settings. These parameters are available on
the Protocol Settings tab of SIP trunks and gateways.
 Table 8-15 describes Provisioning settings. These parameters are available on

Configuring Trunks in Aeonix

the Provisioning tab for SIP trunks that are linked to Tadiran TGW gateways.
8

Aeonix Administration Manual Managing Trunks 8-13

 Table 8-7 General Trunk
Parameters Field Description

Closed User Group The Closed User Group to which the trunk belongs
(Default: Root) (see Closed User Groups (CUG), page 4-29).

NOTE: This field cannot be modified after the trunk is

added to the system.

Description Optional description of the trunk

Keep-alive timeout Number of seconds between keep-alive registration

(Default: 60 seconds) messages before the trunk is assumed to be
malfunctioning. This value is pushed to the SIP trunk
provider and sets the interval at which the provider will
send keep-alive registration messages to Aeonix.

NOTE: For Permanent Connect for Room Recording using two

Aeonix Logger trunks (one active and the other
passive), the Renew after timeout must be smaller
than the value entered here in order to allow the
passive Aeonix Logger to complete the recording
without losing any information.

NOTE: This field is not used for Wave Gateway trunks.

Enable heartbeat by Heartbeat by OPTIONS is an Aeonix feature that actively

OPTIONS (Default: 8 pings the trunk provider using the SIP OPTIONS Request
seconds) protocol. Use the radio buttons to enable or disable the
feature. If enabled specify the SIP OPTIONS Request
interval in the field.

Location The location where the trunk is used (see Locations,

page 4-9)

Default Trunk Group The trunk group associated by default with the trunk. The
location and profile settings of this trunk group are
automatically applied to the trunk when it is connected.
(For more information, see Defining the Default Trunk Group of a
Trunk, page 8-25.)
Configuring Trunks in Aeonix
8

8-14 Managing Trunks Aeonix Administration Manual

Table 8-8 Configuration
Parameters for Coral Field Description
IPnet Trunks
Servers Select the Aeonix server or servers to which the device is
connected.

NOTE: This field is only available in systems with multiple

Aeonix servers.

PCM encoding Select the required encoding method used for digitalizing
analog signals.
Make sure the same option is selected on the side of the
Coral device. For details, refer to the Coral documentation
(see Related Documentation, page 1-17).

NOTE: This field must also be set for Wave Gateway trunks.

MWI mode Select the voicemail Message Waiting Indicator mode

defined for the Coral system.

UGW Addresses To define the Coral device through which Aeonix should
route outgoing calls, click Add and enter the IP address or
Host name of the device, as well as its Port. The device is
added to the box.
If the network contains several Coral systems, you can add
more than one device for redundancy. To update or delete
a previously entered Coral definition, select it in the list box
and click Update or Delete as required.

NOTE: The Port of a UGW address is set to 2427 by default.

Change this value if necessary.

Configuring Trunks in Aeonix

8

Aeonix Administration Manual Managing Trunks 8-15

 Table 8-9 Configuration
and SIP Session Field Description
Handling Parameters for
SIP Trunks and Gateways Maximum The maximum number of concurrent calls that can be made
concurrent calls via this trunk / gateway (unlimited by default).

Reserved licenses The number of licenses that can be reserved for this trunk or
gateway.

Outbound Proxy Select the Outbound proxy check box if an outbound proxy
is required by the ITSP side, and specify the following fields:
 Host—the IP address or name of the outbound proxy
(IPv4 or IPv6)
 Port—the SIP port of the outbound proxy (for secured
communications, use port 5061)
 Protocol—the protocol used to communicate with the
outbound proxy (for secured communications, use TLS)

Alternatively, if you are using DNS SRV queries, select

the DNS SRV option, and then, in the text box that is
displayed below, enter the DNS SRV name as supplied to
you by your IT administrator.

SBC SIP Address Allows SIP trunks that cross a NAT server or firewall to
register and make calls with a SIP service provider when
using an SBC in Aeonix.
Select the SBC SIP Address check box if an SBC is used
on the Aeonix side, and specify the following fields:
 Host—the IP address of the SBC (IPv4 or IPv6)
 Port—the SIP port of the SBC (for secured
communications, use port 5061)
 Protocol—the protocol used to communicate with the
SBC (for secured communications, use TLS)

NAT External When the SIP service provider can cross the NAT server
Address in without need for an SBC, the external address of the NAT
‘contact’ and ‘via’ will be used in the ‘contacts’ and via’ parameters of INVITE
and REGISTER messages:
 Host—the IP address of the NAT (IPv4 or IPv6)
Configuring Trunks in Aeonix

Require session Select Yes if the proxy server of the SIP device requires
timer periodical refreshing of SIP sessions to determine whether
they are still active.
8

8-16 Managing Trunks Aeonix Administration Manual

 Field Description

Session-Expires NOTE: This field is only relevant when the registration mode is
Time Aeonix registers on SIP trunk. In these cases, this
parameter is sent to the remote trunk side.
The length of the time period before which a SIP session
must be refreshed. This is the value the device proposes for
a SIP session.
The receiving party can accept the proposed value only if it
is equal or higher than the receiving party’s Minimum timer
(see below).
Enter a number between 90 and 10000. The value of this
field must not be lower than the Minimum timer.

NOTE: This field is only enabled if the field Require session

timer is set to Yes.

Minimum NOTE: This field is only relevant when the registration mode is
Session-Expires SIP trunk registers on Aeonix. In these cases, if the
remote trunk side tries to register with a value that is
lower than the minimum allowed for this parameter, the
registration will be rejected.
The required minimum amount of time which must separate
one session refresh from the next.
The value of this field depends on the system configuration
and load, and must not be higher than the Session expires
field above.
Enter a number between 90 and 10000. The value of this
field must not be higher than the Session expires value.

NOTE: This field is only enabled if the field Require session

timer is set to Yes.

Requires PRACK Currently not in use

Authenticate Currently not in use

inbound messages

Configuring Trunks in Aeonix

Send 181 - when Determines whether or not SIP message 181 is sent when a
call is forwarded call is forwarded. Select Yes to send SIP message 181.
Select No not to send SIP message 181.

Allow incoming Select Yes for applications (such as Aeonix Contact Center)
call deflection that connect to Aeonix as though they were trunks but that
require full phone functionality (such as deflecting incoming
calls) while connected to the system.
8

Aeonix Administration Manual Managing Trunks 8-17

 Field Description

Supported transfer Select REFER if the REFER command can be used for call
method transfer. Select re-INVITE if the RE-INVITE command can
be used for call transfer.

NOTE: This field is device dependent. Most SIP service

providers only support RE-INVITE

Send invite to Determines when to send the INVITE WITH REPLACES

transfer target response. Select Before consultation answer to send the
INVITE response before the 3rd party answers a two-step
transfer on alert. Select After consultation answer to send
the INVITE response after the 3rd party answers a two-step
transfer on alert. This field is device dependent.

Late media Determines whether Aeonix starts call negotiation via the
support trunk, without supplying a list of suggested media codecs,
and getting from the remote side a reply with its supported
media.(selected by default).

Persistent media Sets the RE-INVITE negotiating algorithm such that: The IP
address and Port of the RE-INVITE command is kept on the
ITSP side. If the Trunk is known to not change the CAP on
RE-INVITE, the system will take for granted that the same IP
and Port will be used, in order to save the time of
interrogating and waiting for a response from the Trunk.

The default setting of Persistemt media for different Trunk

configuration operations is as follows:

 Add Trunk - Persistent media is “off”

 Copy Trunk - Copy this parameter as is
 Aeonix Logger Trunks - Persistent media is “on” by
default
 TGW Trunks - Persistent media is “on” by default
Configuring Trunks in Aeonix
8

8-18 Managing Trunks Aeonix Administration Manual

 Field Description

Codecs The Codecs selection list is used in conjunction with the

Provider keeps IP address and port on Re-Invite
response checkbox to accelerate the media negotiation
process during call setup for call transfer and conference
calls. Aeonix can take a specification of codecs for a trunk, if
it is known that all endpoints on that trunk use the same
codecs. This is used to improve performance of transfer and
conference calls, removing a potentially serious audio delay
during connection. It removes the requirement for Aeonix to
query the target endpoint for its codec type(s). Instead,
Aeonix can immediately send the (assigned) codec type
back to the inviting caller. To setup the Codecs list, the
administrator should know the order used by the SIP trunk
provider, and set them up in the same order.

NOTE: This feature should be used with caution. The order of

codecs in the In Use list must match the order in the
provider’s SIP trunk specification. If no codecs are
moved to the In Use list, the default behavior is for
Aeonix to query an endpoint for its codec type(s) and
return the result to the conference invite or transfer
caller.
The In Use box displays the codecs currently used by the
trunk or gateway. To associate an available codec, select
the codec from the Unused box, and click (the right
arrow). The selected item is moved to the In Use box.

Support RFC 2833 Specifies whether or not the SIP trunk supports RFC 2833.

NOTE: This field is only available when codecs are displayed

in the In Use box.

Table 8-10 Registration

Parameters for SIP Field Description
Trunks and Gateways
Registered to External Registration Click Aeonix registers on SIP trunk if the Aeonix SIP trunk /
Systems (tab) gateway registers by sending a SIP REGISTER message to

Configuring Trunks in Aeonix

an external system server.

NOTE: This field is only enabled in systems with multiple Aeonix

servers.

Servers Select the Aeonix server or servers to which the device is

connected.

NOTE: This field is only enabled in systems with multiple Aeonix

servers if the field Aeonix registers on SIP trunk is
selected.
8

Aeonix Administration Manual Managing Trunks 8-19

 Field Description

Add contact Setting that indicates whether to add the contact user as a
user as prefix prefix to the dial number of an outgoing call. Select Yes or No
as required.

Account name The name of the Aeonix system as defined in the IP trunk /
gateway. It is the user part of the contact URI (Uniform
Resource Identifier) and identifies the system at the SIP trunk
/ gateway service provider.

NOTE: In the contact URI, the user part is the number or string
that stands before the @ sign.

Add account Setting that indicates whether to add the account name (see
name as prefix above) as a prefix to the dial number of an outgoing call.
Select Yes or No as required.

Trunk user The user name required for accessing the trunk / gateway.
name

Trunk password The password required for accessing the trunk / gateway.

Registration If the registration process fails, the time period after which
backoff timer Aeonix retries to register to the registrar.
Configuring Trunks in Aeonix
8

8-20 Managing Trunks Aeonix Administration Manual

 Field Description

Proxy SIP To define the SIP server details in IPv4 or IPv6 (IP address or
Address hostname, protocol, and port):

NOTE: The same settings can be defined in the Registrar

Addressarea below when registration requests are sent to
a separate server.
1 Click Add.
2 In the text box that is displayed, enter the address of the
SIP server.
3 From the Protocol drop-down list, select the transport layer
used for connecting to this trunk. For secured
communications, select TLS and port 5061. In this case, if
the user that calls the trunk or receives a call from this trunk
is defined with Best Effort security level, Aeonix will
establish an encrypted SRTP session.

NOTE: Aeonix does not check the certificate of SIP phones or

trunks.

NOTE: In case of a call between a phone or SIP trunk that

supports encryption and a phone or SIP trunk that does
not, the established call will not be encrypted.
4 Click OK. The address is added to the box.

If several addresses are available, you can add more than one
address for redundancy. The system uses the first available
address, according to the order in which the addresses are
listed.
To update or delete a previously entered address, select it in
the list box and click Update or Delete as required.

Registrar To define the Registrar server details in IPv4 or IPv6 (IP

Address address or hostname, protocol, and port), follow the steps
described for the Proxy SIP Address area above.
If several registrar servers are available, you can add more
than one address for redundancy. The system uses the first
available address, according to the order in which the proxy

Configuring Trunks in Aeonix

addresses are listed.
To update or delete a previously entered address, select it in
the list box and click Update or Delete as required.

Table 8-11 Registration

Parameters for SIP Field Description
Trunks and Gateways
Registered to Aeonix Registration Click SIP trunk registers on Aeonix if the SIP trunk /
Systems (tab) gateway registers by sending a SIP REGISTER message to
8

the Aeonix server.

Aeonix Administration Manual Managing Trunks 8-21

 Field Description

Servers These fields are disabled in this registration mode.

Add contact Setting that indicates whether to add the contact user as a
user as prefix prefix to the dial number of an outgoing call. Select Yes or No
as required.

Trunk user The user name required for accessing the trunk.
name

Trunk password The password required for accessing the trunk.

Table 8-12 Registration

Parameters for SIP Field Description
Trunks and Gateways not
Registered on any Server Registration Click None if the trunk does not register with any server.
(tab)

Servers Select the Aeonix server or servers to which the device is

connected.

NOTE: This field is only enabled in systems with multiple Aeonix

servers.

Add contact Setting that indicates whether to add the contact user as a
user as prefix prefix to the dial number of an outgoing call. Select Yes or No
as required.

Trunk user The user name required for accessing the trunk.
name

Trunk password The password required for accessing the trunk.

Invite timeout If several proxy SIP addresses are defined for the SIP server
(Default: 6 (see below), the number of seconds the system waits until it
seconds) assumes the proxy is malfunctioning and attempts to send
requests to the next address in the list.
Configuring Trunks in Aeonix
8

8-22 Managing Trunks Aeonix Administration Manual

 Field Description

Proxy SIP To define the SIP server details (IP address or hostname,
Address protocol, and port):
1 Click Add.
2 In the text box that is displayed, enter the address of the
SIP server.
3 From the Protocol drop-down list, select the transport layer
used for connecting to this trunk. For secured
communications, select TLS. In this case, if the user that
calls the trunk or receives a call from this trunk is defined
with Best Effort security level, Aeonix will establish an
encrypted SRTP session.

NOTE: Aeonix does not check the certificate of SIP phones or

trunks.

NOTE: In case of a call between a phone or SIP trunk that

supports encryption and a phone or SIP trunk that does
not, the established call will not be encrypted.
4 Enter the SIP server Port that sends all the phone requests
(5060 for UDP and TCP; 5061 for TLS).
Enter the address and click OK. The address is added to the
list box.
If several addresses are available, you can add more than one
address for redundancy. The system uses the first available
address, according to the order in which the addresses are
listed.
To update or delete a previously entered address, select it in
the list box and click Update or Delete as required.

Table 8-13 Configuration

Parameters for Wave Field Description
Gateway Trunks
Direct in-line Setting that indicates whether the trunk routes incoming calls
calls directly to a specified destination.

Direct in-line The user or external number to which incoming calls are Configuring Trunks in Aeonix
destination directed.
To direct the call to an internal user, select User from the
drop-down list and choose the user.
To direct the call to an external number, select Number from
the drop-down list and enter the number.

NOTE: For Wave Gateway trunks, this field is only enabled if the
field Direct in-line calls above is set to Yes.
8

Aeonix Administration Manual Managing Trunks 8-23

 Field Description

Reserved Whether licenses can be reserved for this Wave Gateway

licenses trunk (default 0). Select 1 to allow reserving licenses.

Table 8-14 Protocol

Setting Parameters Field Description
for SIP Trunks and
Gateways Ringback Whether the ringback tone is provided locally by the remote side or
tone by Aeonix. Select from the following:
 Provided locally by remote side (180)—default option
 Provided by Aeonix (183+SDP)

Waiting Whether the waiting tone is provided locally or by the remote side
tone or by Aeonix. Select from the following:
indication  Ringback (180)
 Local waiting tone (182)
 Provided by Aeonix (183+SDP)—default option

Call The method by which progress tones from remote trunks and
progress gateways are handled when a call from a SIP is outgoing to another
tone trunk and the trunk requests to open the media before answering.
Select from the following:
 Provide ringback locally by remote side (180)—no SDP
 Provided by destination transparently (183+SDP)—default
option
 Answer the call (200+SDP)

Music on Enables Music on Hold to be heard by another party when trunk or

hold SDP gateway calls are put on hold. Select Send only to send MOH via
SENDONLY or select Send receive to send MOH via SENDRECV
according to the requirements of the SIP service provider.

Routing Determines how incoming calls are routed.

incoming Select one of the following:
calls  INVITE—to route incoming calls according to the INVITE line
according
 To—to route incoming calls according to the To header
Configuring Trunks in Aeonix

to

From Determines the format of the From header for outgoing calls
header according to the requirements of the SIP service provider.
field

Table 8-15 Provisioning

Setting Parameters for Field Description
SIP Trunks Linked to
Tadiran TGW Gateways
8

Device From the drop-down list, select the Tadiran TGW gateway model to
model which this SIP trunk is connected.

8-24 Managing Trunks Aeonix Administration Manual

 Field Description

MAC From the drop-down list, select the MAC address of the Tadiran
address TGW gateway to which this SIP trunk is connected.

Physical From the drop-down list, select the physical line on the TGW
line gateway to which the trunk is connected.

 Defining the Default Trunk Group of a Trunk

A trunk is usually assigned a default trunk group. This can be done when adding the
trunk to the system or while updating an already existing trunk.

If trunks are defined as members of a trunk group, this trunk group is

automatically defined as their default trunk group. In this case, there is no
need to manually assign the default trunk group. (For details, see Defining the
Trunk Members of a Trunk Group, page 9-23).

To define the default trunk group of a trunk:

1 On the relevant Trunk page (see Figure 8-2), enter the first character of the
relevant trunk group ID in the Default trunk group field and select the trunk
group from the list displayed below the field.
2 If necessary, enter or update the other parameters. (For details, see Trunk
Parameters, page 8-13.)
3 Click Save. The trunk is assigned a default trunk group.

Configuring Trunks in Aeonix

8

Aeonix Administration Manual Managing Trunks 8-25

NOTES:
 8.3 Trunk Templates

A trunk template defines the initial default values for a trunk of a specific type. When
a trunk is added to the system, it is automatically assigned the appropriate default
values.
For each trunk type, the system includes a template. You cannot add or remove
templates, but you can modify the template values.

To edit the template of a trunk type:

1 On the navigation pane, click Administration. The pane displays the
Administration menus.
2 Select the Trunks menu, and then click Trunk Template. The available trunk
types are listed on the navigation pane (see Table 8-5).
3 Select the relevant trunk type. The Trunk Template page displays the fields of
the selected trunk type, as in the following figure for SIP IP trunks.

Figure 8-3 Phone

Template Page for SIP
Trunk / Gateway

4 Fill in the fields as described in Trunk Parameters, page 8-13. (The fields Closed
User Group and Default trunk group are not available for trunk templates.)
Trunk Templates

5 Click Save to save the template.

8

Aeonix Administration Manual Managing Trunks 8-27

NOTES:
 Chapter 9

Managing Trunk Groups

9.1 Trunk Groups ........................................................................9-1

9.2 Defining a Trunk Group.........................................................9-5

9.2 Importing / Exporting Trunk Group Rules ...........................9-27

Aeonix Administration Manual

 9.1 Trunk Groups

An Aeonix trunk group is a logical grouping of trunks connected to the Aeonix system
that serve a common purpose. A trunk group usually has one or more unique alias
numbers defined (see Chapter 11, Managing Aliases) and is assigned to one or more
trunks (see Chapter 8, Managing Trunks). Typical examples of trunk groups include a
group of trunks connecting Aeonix to the PSTN, or trunks connecting a Coral IPx to
Aeonix.

Aeonix trunk groups are defined in a very similar way as Aeonix users
(see Chapter 6, Managing Users).

The trunk groups available in the system are listed on the Trunk Group List Page. For
trunk group configuration details, see Defining a Trunk Group, page 9-5.

Trunk Groups
9

Aeonix Administration Manual Managing Trunk Groups 9-1

  Trunk Group List Page

To open the Trunk Group List page:

1 On the navigation pane, click Administration. The pane displays the
Administration menus.
2 Select the Trunk Groups menu, and then click Trunk Group List.

Figure 9-1 Trunk Group

List Page

The Trunk Group List page displays the existing trunk groups in the system.
The trunk groups listed with a green circle icon are currently registered in the system
through associated trunks. Click Refresh to manually update the list.

The status icons on this page automatically refresh every minute.

The trunk group list is sorted by the Trunk Group ID column. If the list
includes more than one page, use the page navigation bar (see Table 6-1) at
the bottom of the list to navigate between the pages.

The list displays up to 10 rows by default. To change the number of rows

displayed, enter the number in the Rows per page field and click Set.
Trunk Groups
9

9-2 Managing Trunk Groups Aeonix Administration Manual

 For each trunk group, the list displays the following information:

Table 9-1 Trunk Group

List Parameters Field Description

Status icon A circle icon to the left of each trunk group indicates the
(circle) following:
 Green - at least one trunk related to the trunk group is
registered in Aeonix.
 Red - the related trunks are not registered.

NOTE: View the specific icon’s tooltip for more information.

Trunk Group Unique identifier of the trunk group. Typically, a name indicating
ID the purpose of the gateway or IP trunk is used.

Description A short description of the trunk group (optional)

Display Name The name of the trunk group as viewed by Aeonix users

Alias Number or numbers associated with this trunk group. An alias

number is dialed or entered to access the trunk group, regardless
of its current location (see Chapter 11, Managing Aliases).

From this page, you can perform the following actions:

Table 9-2 Actions

Performed from the Action Button / Icon Description
Trunk Group List Page
Add trunk Click Add to add a new trunk group (see Defining a
group Trunk Group, page 9-5).

Update trunk In the list, click the trunk group ID to update the
—
group details of this trunk group.
Delete trunk Select the check box next to the trunk group or
group groups to be deleted and then click Delete
(see Deleting Entities, page 3-66).

NOTE: The AeonixLoggerTKGrp trunk group cannot

be deleted.
Refresh Click Refresh to update the list to the current status.
display
Trunk Groups

Access Click Help to receive online help.

online help

Clone trunk Click this icon to create a duplicate of a specific

group trunk group.
9

Aeonix Administration Manual Managing Trunk Groups 9-3

NOTES:
 9.2 Defining a Trunk Group

A new trunk group that is connected to the network must be assigned an endpoint
(IP trunk or gateway) and an alias (extension number or numbers). The following
procedure describes how to create a new trunk group with new equipment and an alias.

Prior to adding trunk groups, make sure Aeonix global settings and trunk
group profiles are properly defined. See Chapter 4, Global Settings and
Defining a Trunk Group Profile, page 5-88 for details.

To add a new trunk group to the system:

1 On the navigation pane, click Administration. The pane displays the
Administration menus.
2 In the navigation pane, select the Trunk Groups menu, and then do one of the
following:
 Option a
 Option b
 Option c
a To define a new trunk group, click Add Trunk Group. When you add a
new trunk group, an indexing suffix is automatically attributed to the
entity’s ID in the following format: Trunk_Group_x, where x is a running
number. For example, when adding the first trunk group to the system, the
Trunk Group ID will be Trunk_Group_1. The next Trunk Group ID will be
Trunk_Group_2, and so forth. You can manually edit the Trunk Group ID Defining a Trunk Group
as required.
In addition to the Trunk Group ID, the following parameter field values are
automatically filled in by the system when adding a new trunk group:
9

Aeonix Administration Manual Managing Trunk Groups 9-5

 Table 9-3 Predefined
Trunk Group Fields Field Value

Display name Same as Trunk Group ID field

Closed User Group Root

Profile Default Secured Trunk Group Profile

ARS Table Name (on the Incoming Default outgoing routing table
Routing tab)

b To update an existing trunk group, click the relevant ID in the list.

c To create a new trunk group based on the settings of an existing one: From
the Trunk Group List page (see Figure 9-1), click (the Clone icon) to
the right of the relevant trunk group; a new page is opened for creating a
cloned entity. An indexing suffix is automatically added to the entity’s ID.
For example, if the original Trunk Group ID is Loopback, the cloned ID
will be Loopback_1.
In addition to the Trunk Group ID, the following fields and tabs are
automatically cloned by the system when cloning a trunk group: Display
name, Closed User Group, Profile, Description, Profiles tab, Incoming
Routing tab, Outgoing Routing tab, Emergency tab, and Permissions tab.

The remaining fields and tabs are not cloned. For example, the Members
tab fields are not cloned.

The Trunk Group page is displayed.

Defining a Trunk Group
9

9-6 Managing Trunk Groups Aeonix Administration Manual

Figure 9-2 New Trunk
Group Page

3 Fill in the fields to define the general and identity settings of the trunk group
(see Defining Trunk Group Settings, page 9-9).
4 Add an alias (see Assigning Aliases to Trunk Groups, page 9-10).
5 Optionally override the trunk group profile values (see Overriding Trunk Group
Profiles, page 9-10).
6 Set up rules for incoming and outgoing call routing (see Defining Incoming and Defining a Trunk Group
Outgoing Call Routing for Trunk Groups, page 9-11).
7 Add a trunk or trunks to the trunk group (see Defining the Trunk Members of a
Trunk Group, page 9-23).
8 Optionally reserve the trunk group for emergency purposes (see Reserving a
Trunk Group for Emergency Calls, page 9-24).
9
9

Optionally authorize trunk group members to perform Silent Monitoring

(see Authorizing Trunk Group Members to perform Silent Monitoring, page 9-26).

Aeonix Administration Manual Managing Trunk Groups 9-7

 10 Click Save. The trunk group is added to the trunk group list.

Alternatively, if you want to save and clone the current trunk group, click
at the bottom of the page; a new page is opened for
creating a cloned entity, where an indexing suffix is automatically added to
the entity’s ID. For example, if the original Trunk Group ID is Loopback, the
cloned ID will be Loopback_1 (as described above).
Defining a Trunk Group
9

9-8 Managing Trunk Groups Aeonix Administration Manual

  Defining Trunk Group Settings

General trunk group settings are defined in the upper part of the Trunk Group page;
trunk group identity parameters are defined under the Identity & Aliases tab. The
following table describes these parameters.

Table 9-4 General Trunk

Group Settings Field Description

Trunk Group ID Unique ID for the trunk group. Typically, this is a

descriptive name.

NOTE: This field must only be defined for new trunk groups.

Display name Name of the trunk group as it is displayed on a phone or

another endpoint when communicating with this endpoint

Closed User Group The Closed User Group the trunk group belongs to
(Default: Root) (see Closed User Groups (CUG), page 4-29).

NOTE: This field cannot be modified after the trunk group is

added to the system.

Profile The profile assigned to the trunk group. Assigning another

(Default: Default profile resets the profile values of the trunk group to the
Secured Trunk default values of the new profile. For more information,
Group Profile) see Overriding Trunk Group Profiles, page 9-10.

NOTE: The default secured trunk group profile includes the

default secured toll barrier sub-profile, which blocks
outbound calls and restricts incoming calls to
external destinations.

Description Short description of the trunk group (optional)

Defining a Trunk Group

9

Aeonix Administration Manual Managing Trunk Groups 9-9

  Assigning Aliases to Trunk Groups

Each trunk group defined must have at least one alias number assigned to operate in
the system.
Aliases are assigned to trunk groups exactly as they are assigned to users (see Assigning
Aliases to Users, page 6-19).

An already used alias cannot be assigned to a new trunk group. View the
already assigned aliases on the Alias Lists page as described in Aliases
(“Phone Extensions”), page 11-1. In addition, make sure the new alias number
complies with the patterns of the applicable dial plan (see Dial Plans,
page 4-19).

Limitation: There is no support for presence indication for aliases that are
specified via a Prefix or a Range.

 Overriding Trunk Group Profiles

A trunk group profile consists of several assigned sub-profiles, one for each
sub-profile type. A sub-profile includes a set of content-related parameters. Whether
sub-profiles can be overridden for a specific trunk group, depends on the definition of
the profile assigned to this trunk group. Profiles and sub-profiles are described in
detail in Chapter 5, Profiles.
By default, a new trunk group is assigned the Default Secured Trunk Group profile and
the sub-profiles related to this profile. The profile assignment and sub-profile values
of a trunk group can be modified similarly as for a user (see Overriding User Profiles,
page 6-29). The only differences are:
 In the General Information sub-profile, some parameters are not relevant for
Defining a Trunk Group

trunk groups.
 Phone, Schedule, Incoming Call Routing, Outgoing Call Routing, or Feature
Configuration sub-profiles are not assigned to trunk groups. Incoming and
outgoing routing rules are defined separately for each trunk group as described
in Defining Incoming and Outgoing Call Routing for Trunk Groups, page 9-11.
 No phone profiles are assigned to trunk groups.
9

9-10 Managing Trunk Groups Aeonix Administration Manual

  Defining Incoming and Outgoing Call Routing for Trunk Groups

To specify how a trunk group routes incoming and outgoing calls, you can define rules
for manipulating digits of calls that are transmitted or received through the trunk
group. A digit manipulation rule consists of one or more manipulations performed on
calling or called numbers.
Digit manipulation rules can be created for the following call numbers:
 DNIS—the number dialed by the caller placing a call through the trunk group
 ANI—the phone number of the caller
 Manipulated DNIS—the number dialed by the caller placing a call through
the trunk group based on the result of the previous DNIS manipulation
 Manipulated ANI—the phone number of the caller based on the result of the
previous ANI manipulation
Which calls are routed through the trunk group depends on the Automatic Routing
Selection (ARS) settings. To enable trunk-to-trunk routing, you can assign an ARS
table to the trunk group, which defines how incoming trunk calls are routed. ARS
tables and their configuration are described in Automatic Route Selection (ARS),
page 4-43.)

Aeonix automatically removes the External access code defined in the dial
plan (usually 9) that users dial to place external calls. Therefore, no rule
must be defined for this action. To learn about dial plans, see Dial Plans,
page 4-19.

Use the following procedures for defining routing parameters and call digit
manipulation rules:
 Configuring Incoming Call Routing, page 9-12
 Configuring Outgoing Call Routing, page 9-13
 Defining Digit Manipulation Rules for Trunk Groups, page 9-14
Defining a Trunk Group
 Deleting Digit Manipulation Rules for Trunk Groups, page 9-20
For a detailed example of defining digit manipulation rules for a trunk group,
see Example for Digit Manipulation Rules in a Trunk Group, page 9-21.
9

Aeonix Administration Manual Managing Trunk Groups 9-11

 Configuring Incoming Call Routing
A trunk group’s incoming call routing settings define how the trunk group handles
external calls to Aeonix users if the calls are routed through this trunk group.

To configure the incoming call routing settings of a trunk group:

1 On the Trunk Group page (see Figure 9-2), click the Incoming Routing tab.

Figure 9-3 Incoming

Routing Tab
(Trunk Group)

2 Under ARS Table Name, select an ARS table. This table defines how
incoming trunk calls are routed and is required for trunk-to-trunk grouping
scenarios.
Defining a Trunk Group

3 Under Manipulation Rules, define digit manipulation rules to manipulate the

ANI or DNIS number of external callers (see Defining Digit Manipulation Rules for
Trunk Groups, page 9-14).
4 Click Save.
9

9-12 Managing Trunk Groups Aeonix Administration Manual

 Configuring Outgoing Call Routing
A trunk group’s outgoing call routing settings define how the trunk group handles
external calls placed by Aeonix users if the calls are routed through this trunk group.

To configure the outgoing call routing settings of a trunk group:

1 On the Trunk Group page (see Figure 9-2), click the Outgoing Routing tab.

Figure 9-4 Outgoing

Routing Tab
(Trunk Group)

2 Under Dialed Number Conversion, select or clear check boxes as follows:

Defining a Trunk Group
Table 9-5 Dialed Number Convert full numbers Select this check box to automatically convert international
Conversion to local numbers and cross-area dial numbers to local numbers by removing
(Default: selected) country codes, area codes, and other prefixes.
9

Aeonix Administration Manual Managing Trunk Groups 9-13

 Use dialed number If this check box is selected, the dialed number is left
when caller and unchanged if the caller uses the same area code as the
trunk share area trunk that transmits the call.
code In areas with inconsistent dial patterns, this feature might
(Default: selected) be required to prevent converting of local calls into
long-distance calls.

On transferred calls, Select the relevant outgoing trunk group transferred

use (including forwarded, deflected and FlexiCall) call handling
(Default: Originator option:
ANI)  Originator ANI – The ANI from the original incoming
call will be displayed to the receiver of the transfer.
 Last destination – The user that transferred the call to
the outgoing trunk will be displayed to the receiver of
the transfer.

3 Under Manipulation Rules, define digit manipulation rules to manipulate the

ANI (alias) or DNIS number of Aeonix users placing external calls
(see Defining Digit Manipulation Rules for Trunk Groups, page 9-14).
4 Click Save.

Defining Digit Manipulation Rules for Trunk Groups

To add or update a digit manipulation rule:

1 On the Trunk Group page (see Figure 9-2), click the relevant tab:
 To define a digit manipulation rule for incoming external calls, click the
Incoming Routing tab (see Figure 9-3).
 To define a digit manipulation rule for external calls placed by Aeonix
users, click the Outgoing Routing tab (see Figure 9-4).
2 Click ANI Manipulation Rules for External Calls or DNIS Manipulation
Rules for External Calls to display the relevant Manipulation Rules box.

Figure 9-5 ANI

Manipulation Rules box
Defining a Trunk Group

with Rules
9

9-14 Managing Trunk Groups Aeonix Administration Manual

 You can use the Search box to textually search for and display specific items
in the list.

3 To the right of the box, click Add to define a new rule, or select a rule from
the box and click Update to modify an existing rule.
The fields for defining the condition of the rule are displayed, as well as
previously defined actions, as in the following figure for incoming external
calls.

Figure 9-6 Manipulation

Rule: Defining the
Condition

4 Select the relevant ANI or DNIS call type from the drop-down list:
 original ANI - The ANI manipulation will be based on the original ANI.
 original DNIS - The DNIS manipulation will be based on the original
DNIS.
 manipulated ANI - The ANI manipulation will be based on the result of Defining a Trunk Group
the previous ANI manipulation.

If the first original ANI manipulation on 9265xxx is to remove the first three
digits (result 5xxx), and the second manipulated ANI manipulation (on the
result) is to replace the first digit with the digit ‘2’, the final result will be 2xxx.
9

Aeonix Administration Manual Managing Trunk Groups 9-15

  manipulated DNIS - The DNIS manipulation will be based on the result of
the previous DNIS manipulation.

The manipulated ANI option is not available for DNIS incoming

manipulation rules. Likewise, the manipulated DNIS option is not available
for ANI outgoing manipulation rules.

5 From the adjacent drop-down list, define the condition of the rule:
 To apply the rule to all numbers beginning with a specific prefix or set of
digits, select starts with and enter the prefix or the first digits of the
number (digits only).
 To apply the rule to a specific number, select is and enter the number (digits
only).
 To apply the rule to all calls, select is any number.
 To apply the rule to a range of numbers, select is between and specify the
range.
 To apply the rule to any call that has a number that is restricted or empty.

The is restricted or empty option is not relevant for DNIS manipulation

rules.

6 To cancel incoming routing rules that are to be executed after this rule, select
Stop processing other rules.
7 To define an action for the rule, click Add. The Action fields are displayed.
Defining a Trunk Group
9

9-16 Managing Trunk Groups Aeonix Administration Manual

Figure 9-7 Manipulation
Rule: Defining the
Actions

8 Specify the required action using one of the following options:

 Add offset—adds the specified offset number to the number (mathematical
operation). For example, if you select this option and enter 5, the number
012233445 is changed to 012233450.
 Add prefix—adds the specified prefix number to the beginning of the
number. For example, if you select this option and enter 03, the number
445566778 is changed to 03445566778.
 Add suffix—appends the specified suffix number to the number. For
example, if you select this option and enter 5, the number 012233445 is
changed to 0122334455. Defining a Trunk Group

 Remove first digits—removes the specified number of digits from the

beginning of the number. For example, if you select this option and enter 2,
the number 034455667 is truncated to 4455667.
 Remove last digits—removes the number of digits from the end of the
number. For example, if you select this option and enter 3, the number
023344558 is truncated to 023344.
9

Aeonix Administration Manual Managing Trunk Groups 9-17

  Replace the number with—replaces the number with the specified
number.
9 You can also enter the relevant digit string variables in the adjacent field.

You can use any combination of digits (0-9), asterisks ('*'), and pound ('#')
signs, and any combination of the following variables, which can be used a
multiple of times.

Table 9-6 Manipulation

Rule Action Variables Variable Description

[ANI] [ANI] will be replaced with the ANI of the call

[DNIS] [DNIS] will be replaced with the DNIS of the call

[MODANI] [MODANI] will be replaced with the modified ANI as

calculated till this point

[MODDNIS] [MODDNIS] will be replaced with the modified DNIS

as calculated till this point

[N:<num digits>] A running counter (where <num digits> designates the

counter’s maximum length) can be used, for example,
to identify the call instead of the ANI. The counter does
not start from zero, the start number is random.
Examples:
[N:7] can produce a counter result that can contain a
minimum of one digit and a maximum of 7 digits.
[N:0] can produce a counter with unlimited digits (use if
you do not want counters to be repeated)
[N:07] will always produce a counter with seven digits

10 Click one of the following under the Action fields:

 OK to add this action to the Action box above.
Defining a Trunk Group

 OK & Add to add this action and proceed to add more actions to the
Action box above.
11 Use (the Up and Down arrows) to set the priority order of the actions.

A higher action overrides any conflicting lower action.

9

9-18 Managing Trunk Groups Aeonix Administration Manual

 You can modify or delete any of the defined actions by selecting it and
clicking Update or Delete respectively.

12 Click OK at the bottom of the page. The rule is listed in the relevant
Manipulation Rules box under the Incoming Routing or the Outgoing
Routing tab of the trunk group.
13 Use (the Up and Down arrows) to set the priority order of the rules.

A higher rule overrides any conflicting lower rule.

Click a rule to display its syntax under the box.

14 Click Save.

Defining a Trunk Group

9

Aeonix Administration Manual Managing Trunk Groups 9-19

 Deleting Digit Manipulation Rules for Trunk Groups

To delete a digit manipulation rule:

1 On the Trunk Group page (see Figure 9-2), click the relevant tab:
 To delete a manipulation rule for incoming external calls, click the
Incoming Routing tab (see Figure 9-3).
 To delete a manipulation rule for outgoing external calls, click the
Outgoing Routing tab (see Figure 9-4).
2 Click ANI Manipulation Rules for External Calls or DNIS Manipulation
Rules for External Calls to display the relevant Manipulation Rules box.
3 Select the rule or rules to be deleted. You can delete multiple rules by holding
down the CTRL or SHIFT key while selecting them.
4 Click Delete. The rule or rules are removed from the box.
5 Click Save. The rules are deleted.
Defining a Trunk Group
9

9-20 Managing Trunk Groups Aeonix Administration Manual

 Example for Digit Manipulation Rules in a Trunk Group
An organization has two offices, one in New York and another in Florida. They have
two Aeonix systems, one in each office, that share licensing and databases.
To reach the Florida office, employees in New York dial 9 (the external access code)
plus a long-distance call number:
1-941-XXX-XXXX
1-407-XXX-XXXX
(1 is the long distance access code; 941 and 407 are Florida area codes; and
XXX-XXXX stands for any seven-digit local phone number.)
A trunk group has been created for the local trunks that are terminated in the Florida
office. To make use of this trunk group, the following settings must be defined in the
Aeonix Web Portal:
 The trunk group, as described in this chapter. This example details the digit
manipulation rules that must be set for the trunk group.
 An ARS table that defines that outside calls beginning with 1-941 or 1-407 are
routed through this trunk group. This table is assigned to each employee in the
New York office. (To learn more about ARS tables, see Automatic Route
Selection (ARS), page 4-43.)

The following local dial rules must be taken into account when defining digit
manipulation rules for the trunk group:
 All calls in or to the 407 area include the long distance and area codes
(1-407-XXX-XXXX).
 All long distance calls to the 941 area include the long distance and area codes
(1-941-XXX-XXXX).
 Local calls in the 941 area use only the last seven digits (XXX-XXXX) for the
exchanges 227, 234, 238, 295, 406, 531, 803, 806, 879, and 932. All other
exchanges in the 941 area require local calls to include the long distance and
Defining a Trunk Group
area codes, just like long distance calls.
9

Aeonix Administration Manual Managing Trunk Groups 9-21

 To define the rules for the Florida trunk group, click its Outgoing Routing tab. In the
ANI Manipulation Rules for External Calls box, set the following rules:
If the ANI starts with 1941227, then remove the first 4 digits.
If the ANI starts with 1941234, then remove the first 4 digits.
If the ANI starts with 1941238, then remove the first 4 digits.
If the ANI starts with 1941295, then remove the first 4 digits.
If the ANI starts with 1941406, then remove the first 4 digits.
If the ANI starts with 1941531, then remove the first 4 digits.
If the ANI starts with 1941803, then remove the first 4 digits.
If the ANI starts with 1941806, then remove the first 4 digits.
If the ANI starts with 1941879, then remove the first 4 digits.
If the ANI starts with 1941932, then remove the first 4 digits.
Other calls to the 941 and 407 areas do not require manipulation rules, since the full
number including the long distance code, the area code, and the local number must be
dialed.

For detailed instructions on how to define a manipulation rule, see Defining

Digit Manipulation Rules for Trunk Groups, page 9-14.
Defining a Trunk Group
9

9-22 Managing Trunk Groups Aeonix Administration Manual

  Defining the Trunk Members of a Trunk Group

A trunk group cannot operate in the network without trunks. These devices must be
defined in Aeonix and associated with the trunk group. Only then the trunk group will
be able to function in the network.

The following procedure describes how to assign one or more trunks to a

trunk group. These trunks are defined and managed through the Trunk page
(see Defining a Trunk in Aeonix, page 8-10).

To include or exclude trunks as members of a trunk group:

1 On the relevant Trunk Group page (see Figure 9-2), click the Members tab.

Figure 9-8 Members Tab

2 The Trunk List box displays the ID values of the trunks belonging to the
Closed User Group of the trunk group. Defining a Trunk Group

To include a trunk in the trunk group, select it in the Trunk List box and click
(the right arrow). (You can use the Search box for this purpose.) The
selected item is moved to the Members box and added to the list of items to
be included in the trunk group.
Repeat this step to add other trunks.
9

Aeonix Administration Manual Managing Trunk Groups 9-23

 To change the order of which trunks are used when outgoing calls are routed
through this trunk group, click Ascending or Descending as required.

To remove an included item from the trunk group, select it in the Members
box and click (the left arrow). You can include or exclude multiple trunks
by holding down the CTRL or SHIFT key while selecting them.

3 Click Save.

 Reserving a Trunk Group for Emergency Calls

A trunk group can be dedicated to be used for emergency calls only. Calls on an
emergency trunk group bypass the ARS mechanism and are directly routed to the
closest emergency center.
The same emergency trunk group can be associated with one or multiple locations
defined in Aeonix and handle emergency calls placed from these locations. The
association can be specified either as described in the following procedure, or on the
relevant Location pages as described in Defining Emergency Call Settings, page 4-16.

E911 functionality is only supported on PRI and CAMA trunks.

To configure a trunk group for emergency calls:

1 On the relevant Trunk Group page (see Figure 9-2), click the Emergency tab.
Defining a Trunk Group
9

9-24 Managing Trunk Groups Aeonix Administration Manual

Figure 9-9 Emergency
Tab

2 To reserve the trunk group for emergency calls from a specific location, select
it in the Available Locations box and click (the right arrow). The selected
location is moved to the Selected Locations box and added to the list of
locations associated with the emergency trunk group.
Repeat this step to add other locations.

To disconnect an associated location from the trunk group, remove it from

the Selected Locations box by selecting it there and clicking (the left
arrow). You can associate or disconnect multiple locations by holding down
the CTRL or SHIFT key while selecting them.

3 Click Save.

Defining a Trunk Group

9

Aeonix Administration Manual Managing Trunk Groups 9-25

  Adding a Trunk Group for Trunk Group Speed Dial

A Trunk Group can be dedicated to be used by users to direct outbound calls over a
specific Trunk.
Trunk Group Speed Dial allows the user to specify that a call about to be dialed is be
routed through a specific Trunk. The user first presses the Trunk Group Speed Dial
button, followed by a speed dial button or dial pad number.
A Trunk Group for Trunk Group Speed Dial must be specified as follows:
 The Trunk Group contains only one member, as defined below.
 The member Trunk can only be an analog trunk: Coral Wave Gateway (IPx)
4/8T or TGW FXO Gateway.
When one or more Trunk Groups for Speed Dial have been defined as described
above, they can be assigned by a user or system administrator as a Speed Dial Button
to be pressed before entering an outbound call via Speed Dial or Dial Pad. Refer to the
Section “Programmable Button Dial Functions” in Chapter 4 “Configuring Your
Telephone” in Aeonix Configuration Guide for End Users.
The Trunk Group Speed Dial button supports Busy, Idle, Alert (incoming), and Hold
presence indications.

 Authorizing Trunk Group Members to perform Silent Monitoring

Authorized trunk group members can monitor Aeonix users and meet-me conference
aliases.

To authorize trunk group members to perform silent monitoring:

1 On the relevant Trunk Group page (see Figure 9-2), click the Permissions tab.

Figure 9-10 Permissions

Tab
Defining a Trunk Group

2 Select the Allow silent monitoring check box to allow trunk group members
to perform Silent Monitoring on Aeonix users and meet-me conference aliases.
3 Click Save.
9

9-26 Managing Trunk Groups Aeonix Administration Manual

 9.3 Importing / Exporting Trunk Group Rules

The Aeonix Web Portal supports the batch import and export of incoming and
outgoing trunk group rules in Aeonix from CSV (comma-separated) files. These files
can be managed externally in a spreadsheet editor.

 Importable Trunk Group Call Routing Rules

The following table describes the Trunk Group parameters (not case sensitive) that can
be imported if available in the CSV file.

Figure 9-11 Imported

Trunk Group Parameters
Parameter Description

Trunk Group ID Unique identifier of the trunk group

Routing  Incoming Routing – defines how the trunk group

handles external calls to Aeonix users when calls are
routed through this trunk group
 Outgoing Routing – defines how the trunk group
handles external calls placed by Aeonix users when
calls are routed through this trunk group

Manipulation Rule  DNIS – the number dialed by the caller placing a call

Importing / Exporting Trunk Group Rules

through the trunk group
 ANI – the phone number of the caller

Manipulation Source  Original DNIS – DNIS manipulation is based on the

original DNIS
 Manipulated DNIS – DNIS manipulation is based on
the result of the previous DNIS manipulation
 Original ANI – ANI manipulation is based on the
original ANI
 Manipulated ANI – ANI manipulation is based on the
result of the previous ANI manipulation
9

Aeonix Administration Manual Managing Trunk Groups 9-27

 Parameter Description

Manipulation Action  Starts with – rule is applied to all numbers beginning

with the specified prefix or set of digits
 is – the rule is applied to the specified number
 is any number – the rule is applied to all calls
 is between – the rule is applied to the specified range
of numbers
 is restricted or empty – the rule is applied to any call
that has a number that is restricted or empty

Manipulation Value  The value that is relevant to the specified manipulation

action (relevant for manipulation actions Starts with,
is, and is between)

Manipulated Value  The value that is relevant to the specified manipulation

action (relevant for manipulation action is between)

Stop Process Rule  TRUE – routing rules that are executed after the
specified rule are canceled
 FALSE – routing rules that are executed after the
specified rule are not canceled

Change Action  Add offset – adds the specified offset number to the
number
 Add prefix – adds the specified prefix number to the
beginning of the number
 Add suffix – appends the specified suffix number to
the number
 Remove first digits – removes the specified number
of digits from the beginning of the number
 Remove last digits – removes the number of digits
from the end of the number
 Replace the number with – replaces the number with
the specified number (unless the number is restricted
Importing / Exporting Trunk Group Rules

or empty)

Change Action Value The value that is relevant to the specified change action

 Importing Trunk Group Call Routing Rules

Prior to performing the import, ensure that the trunk groups that you want to import
rules for already exist in the system. In addition, ensure that the parameters being
imported and the order they are arranged correspond to the parameters described in
Figure 9-11. For example, the CSV file should be constructed as follows:
9

9-28 Managing Trunk Groups Aeonix Administration Manual

Figure 9-12 CSV File
Format Example

Trunk groups that already exist in Aeonix but are not included in the CSV will
not be affected.

To import Trunk Group Call Routing parameters from a CSV file:

1 On the navigation pane, click Administration. The pane displays the
Administration menus.
2 Select the Trunk Groups menu, and then click Import / Export Trunk
Groups. The Import / Export Trunk Groups page is displayed.

Figure 9-13 Import /

Export Trunk Groups
Page

Importing / Exporting Trunk Group Rules

3 Select Overwrite all existing rules with imported rules if you want to
replace all the existing rules with the rules you are about to import.
9

Aeonix Administration Manual Managing Trunk Groups 9-29

 4 Click the Choose File button and use the displayed dialog box to locate the
required CSV file on your workstation or network; the name of the selected
CSV file is displayed adjacent to the button.
5 Click Import. The trunk group rules are imported into Aeonix.

You will be informed in the event of any errors in the import; however, errors
do not stop the import process.

 Exporting Trunk Group Call Routing Rules

You can export trunk group call routing rules to a CSV (comma-separated) file.

To export trunk group call routing rules:

1 On the Import / Export Trunk Groups page (see Figure 9-13), start filling in
the name of the trunk group you want to export in the Trunk Group ID text
box; all existing trunk groups containing the entered value are displayed below
the text box.

Alternatively, to export the rules of all trunk groups, select the All groups
check box.

2 Select the required trunk group, and click Export; the .csv file is downloaded
to your computer.
Importing / Exporting Trunk Group Rules
9

9-30 Managing Trunk Groups Aeonix Administration Manual

 Chapter 10

Managing VOIP Gateways

10.1 Gateways............................................................................10-1

10.2 Configuring Wave Gateways ..............................................10-7

10.3 Configuring Wave Gateway Cards....................................10-17

10.4 Configuring Tadiran TGW Gateways ................................10-41

Aeonix Administration Manual

 10.1 Gateways

Aeonix is a pure VoIP system and requires gateways to connect to legacy equipment
to the PSTN network and to interface digital and analog devices. Depending on its
type, a gateway allows the system to integrate legacy phones, legacy trunks, or both.
This chapter describes how to configure Wave gateways through the Aeonix Web
Portal.

Wave Gateway is not supported in A4C.

To learn how to configure the gateway phones and trunks in Aeonix, see:
 Chapter 7, Managing Phones
 Chapter 8, Managing Trunks
To learn how to configure Tadiran TGW gateways, see Configuring Tadiran TGW
Gateways, page 10-41.

 Tadiran TGW Gateway Series

Tadiran TGW gateways provide residential telephony and fax services through
broadband networks via FXS and FXO ports, enabling vast deployment in delivering
Aeonix as enterprise-based voice applications. Tadiran TGW gateways can be auto
provisioned. In addition, batch configuration allows Aeonix administrators to
automatically define Tadiran TGW gateways and their related physical and logical
entities, including users, trunk groups, phones, and trunks in one quick and easy
operation.
Gateways

For a detailed listing of all Tadiran TGW models, refer to the Aeonix Product
Description (see Related Documentation, page 1-17).
10

Aeonix Administration Manual Managing VOIP Gateways 10-1

  Wave Gateway Series

The Wave Gateway series includes the Coral IPx Office, 500, 800, 3000, 4000; Coral
FlexiCom 400 (with HDC controller), 5000, 6000; and Coral III-4GC models.
The Wave Gateway allows Aeonix to integrate the existing hardware of a Coral
IPx/FlexiCom systems. All features of Aeonix are applied to the trunks and phones
(stations) of the Coral IPx/FlexiCom legacy equipment. Aeonix supports multiple
Wave Gateway units.
The Coral IPx and FlexiCom systems that can be upgraded to Wave Gateway systems
are displayed in Figure 10-1.
The Wave Gateway can be installed along with Aeonix as a completely new system,
or it can be upgraded from an existing Coral IPx/FlexiCom system. To learn more
about the Wave Gateway, refer to the relevant documentation (see Related
Documentation, page 1-17).
The Wave Gateways configured via the Web Portal are listed on the VOIP Gateway List
Page. For configuration details, see Configuring Wave Gateways, page 10-7.
Gateways
10

10-2 Managing VOIP Gateways Aeonix Administration Manual

Figure 10-1 Wave Legacy Equipment
Gateway Configuration

Analog Station Digital Station Digital Station Public Switched

500/2500 type FlexSet 120 series FlexSet 280 series Magneto Station Telephone Network

PSTN

Central Office / local exchange trunks

ISDN (PRI/BRI), T1, E1, SS7
loop-start, ground-start,
50Hz, 12kHz, & 16kHz meter,
DID/DDI, ALS-70, FTZ, RTT

Coral Wave Gateway Options

OK
OK

AL T
AL T

1 2 3 1 2 3

4 5 6 4 5 6

7 8 9
7 8
8 99 8 9

0
0

IPx Office IPx 500 IPx 800 IPx 3000/4000 FlexiCom 5000/6000 FlexiCom 400

Voice over
Internet Protocol
(VoIP)

Aeonix

1
2 A BC

3D EF

4 GH I

5 JK L

6 MNO

7
P QRS

8 TU V

9
W XY Z

* 0
#
-
+

FlexSet-IP 280S T200M Series Tadiran SIP P-Series Bria, SeaBeam

Phones and
FlexIP SoftPhone

IP phones
Gateways

The Coral IPx 4000 system cannot be converted to a Wave Gateway unless
it is converted to IPx 3000 first. The Coral FlexiCom 6000 system cannot be
converted to a Wave Gateway unless it is converted to FlexiCom 5000 first.
10

Aeonix Administration Manual Managing VOIP Gateways 10-3

  VOIP Gateway List Page

The VOIP Gateway List page lists the configured Tadiran TGW Gateways and Wave
Gateways and their corresponding statuses.
To open the VOIP Gateway List page:
1 On the navigation pane, click Administration. The pane displays the
Administration menus.
2 Select the VOIP Gateways menu, and then click VOIP Gateway List {1}.

Figure 10-2 VOIP

Gateway List Page

The gateways listed with a green circle icon are currently registered with Aeonix.
Click Refresh to manually update the list.

The status icons on this page automatically refresh every minute.

The VOIP Gateway List page displays the gateway units in the system, sorted by their
ID.
If the list includes more than one page, use the page navigation bar at the bottom of
the list to navigate between the pages.
Gateways
10

10-4 Managing VOIP Gateways Aeonix Administration Manual

 For each gateway, the list displays the following information.

Table 10-1 VOIP Gateway

List Fields Field Description

Status icon A circle icon to the left of each TGW Gateway indicates the
(circle) following:
 Green - at least one of the TGW Gateway phones is currently
registered on an Aeonix server; provisioning may be required
(see tooltip)
 Red - none of the TGW Gateway phones is currently
registered on any Aeonix server; provisioning may be required
or provisioning has failed (see tooltip)
 Green/Red - at least one of the TGW Gateway phones is
currently registered on an Aeonix server, but provisioning has
failed and is pending (see tooltip). Once provisioning is
executed and, as a result, synchronization is restored, the icon
will revert to green.

A circle icon to the left of each Wave Gateway indicates:

 Green - the Wave Gateway is currently registered on at least
one Aeonix server.
 Red - the Wave Gateway is currently not registered on any
Aeonix server.

NOTE: View the icon’s tooltip for more information.

ID Unique identifier of the gateway. Typically, a name indicating the

purpose or number of the gateway is used.

NOTE: Click the relevant ID to view or modify gateway details.

Description A short description of the gateway (optional)

Location The location where the gateway is used (see Locations, page 4-9)

Type The type of the gateway (TGW or Wave Gateway)

Registered on All Aeonix servers on which the gateway is registered. This field
is blank if none of the gateway’s devices (phone or trunk) is
registered.

NOTE: This information is of importance in Aeonix clusters.

IP Address The IP address assigned to the gateway. This field is blank if

none of the gateway’s devices (phone or trunk) is registered. For
Gateways

TGW gateways, click the relevant IP Address to access the TGW

box Admin.

NOTE: It is not recommended to make changes to parameters in

the TGW box that are provisioned by Aeonix, as they will
10

get overwritten in the next provisioning session.

Aeonix Administration Manual Managing VOIP Gateways 10-5

 Field Description

Configure {2} In the list, click to configure this Wave Gateway (see Defining
Wave Gateway Setup/Synchronization/Alarm Parameters, page 10-10).

From this page, you can perform the following actions:

Table 10-2 Actions

Performed from the VOIP Action Button / Icon Description
Gateway List Page
Add gateway Click Add to add a new gateway (see Defining a
Wave Gateway, page 10-8).

Update In the list, click the ID to update the details of this

—
gateway gateway.
Delete Select the check box next to the gateway or
gateway gateways to be deleted and then click Delete
(see Deleting Entities, page 3-66).
Refresh Click Refresh to update the list to the current status.
display

Access Click Help to receive online help.

online help

Configure In the list, click to configure this Wave gateway

gateway — (see Defining Wave Gateway Setup/Synchronization/Alarm
Parameters, page 10-10).
Clone Click this icon to create a duplicate of a specific
gateway gateway.
Gateways
10

10-6 Managing VOIP Gateways Aeonix Administration Manual

 10.2 Configuring Wave Gateways

This section describes the activities involved in managing Wave Gateways in the
Aeonix Web Portal.

Wave Gateway is not supported in A4C.

 Defining a Wave Gateway, page 10-8

 Defining Wave Gateway Setup/Synchronization/Alarm Parameters, page 10-10
To set up Wave Gateway cards and access its phones (stations) and trunks,
see Configuring Wave Gateway Cards, page 10-17.

Configuring Wave Gateways

10

Aeonix Administration Manual Managing VOIP Gateways 10-7

  Defining a Wave Gateway

This procedure includes adding a Wave Gateway and specifying its basic (Aeonix
related) parameters.

To add or update a Wave Gateway configuration:

1 In the navigation pane, select the VOIP Gateways menu, and then do one of
the following:
 To define a new Wave Gateway, click Add VOIP Gateway.
 To update an existing Wave Gateway, click VOIP Gateway List and select
the relevant ID in the list.
 To create a copy of an existing Wave Gateway, click VOIP Gateway List.
On the VOIP Gateway List page (see Figure 10-2), click (the Clone
icon) to the right of the relevant gateway.

When you clone a Wave Gateway, all parameter values are copied to the
new gateway except for the gateway ID and the Closed User Group. The IP
address of the gateway is not copied to a new gateway.

The Wave Gateway page is displayed (to define a TGW Gateway, see Defining
a Tadiran TGW Gateway, page 10-42).

Figure 10-3 VOIP

Gateway Page for a new
Wave Gateway

2 Set the basic parameters as described in the following table.

Configuring Wave Gateways

Table 10-3 Basic Wave

Gateway Parameters Field Description

ID Unique ID for the gateway. (The ID can only include

letters, digits, dashes (-), and underscores (_); spaces are
not allowed.)

NOTE: This field must only be defined for new gateways.

10

10-8 Managing VOIP Gateways Aeonix Administration Manual

 Field Description

Closed User Group The Closed User Group the gateway belongs to
(Default: Root) (see Closed User Groups (CUG), page 4-29).

NOTE: This field cannot be modified after the gateway is

added to the system.

Description Short description of the gateway (optional)

IP address The IP address assigned to the gateway (IPv4 or IVp6):

 For IPx Office Wave Gateways—the CUGW address
 For IPx 500, 800, 3000 Wave Gateways—the MAP
address
 For FlexiCom 5000 Wave Gateways—the MAP address
This field is required for Aeonix to connect to the gateway.
If no IP address has been defined for a Wave Gateway, its
default IP address is 192.168.10.11.

NOTE: Do NOT use this field to change the IP address of

the gateway. To change this IP address, see Table
10-4 on page 10-10.

Port The port through which the gateway communicates with

(Preset to 11004) Aeonix (read-only)

Keep-alive timeout Number of seconds between keep-alive messages before

(Default: 60 sec.) a phone or trunk connected to the gateway is assumed to
be malfunctioning.

3 Click Save. The Wave Gateway is included in the VOIP Gateway list.

Configuring Wave Gateways

10

Aeonix Administration Manual Managing VOIP Gateways 10-9

  Defining Wave Gateway Setup/Synchronization/Alarm Parameters

Use this section to define location, setup, digital clock synchronization, and alarm
parameters for the Wave Gateway.

To define Wave Gateway setup and digital clock synchronization settings:

1 From the table on the Wave Gateway List page (see Figure 10-2), click
Configure for the relevant Wave Gateway. Aeonix connects to the
Wave Gateway database and displays Wave Gateway specific parameters. This
may take a few minutes.

Figure 10-4 Wave

Gateway Page—Location
and Setup Parameters

2 Set the Location and Setup parameters as described in the Table 10-4.
Record the IP addresses of the Coral IPx/FlexiCom MAP/PUGW/PUGW-2G x
interface elements in Table 10-5 and save for future use.

Table 10-4 Wave Gateway

Configuring Wave Gateways

Location and Setup Field Description

Parameters
Version The software version of the Wave Gateway.

NOTE: Wave Gateway cluster survivability support requires Wave

Gateway Version 3.12.16 or higher.
10

10-10 Managing VOIP Gateways Aeonix Administration Manual

 Field Description

Country The country in which the Wave Gateway is located.

The Wave Gateway supports a selection of country specific tone
plans and other parameters as follows.
Wave Gateway enables interoperability with various PSTN
interfaces including PRI (Primary Rate Interface) and BRI (Basic
Rate Interface) supporting different protocol flavors such as
EuroISDN, AT&T, QSIG, and Q931 over Q921.
Furthermore, the Wave Gateway supports E1 and T1 interface
using the CAS (Channel Associated Signaling) supporting
different protocol flavors such as E&M, MFC, R2, and MFC/R2.
Using the T1 interface, Wave Gateway supports the Robbed Bit
method. These interfaces can be provided with the required
impedance per country standard: 120 or 100 ohms.

Location The location where the Wave Gateway is used.

(Default:
Default NOTE: Only locations associated with the selected country are
Location) included in the drop-down list.

IP address The IP address assigned to the Wave Gateway.

Subnet mask The subnet mask address of the Wave Gateway

Default router The IP address of the nearest router to the Aeonix server
address

Servers A list of available Aeonix servers. Select the servers you want to
use with this Wave Gateway.

Table 10-5 IP Addresses

of IPx/FlexiCom Signaling Wave Gateway MAP/CUGW Recorded Value
Interface Elements
IP address

Subnet mask

Default router address Configuring Wave Gateways

3 For multi-cluster sites, remote telephony survivability can be configured. In the

event that connections to all the servers in the primary cluster go down, the
Wave Gateway will register phones to the secondary cluster, thereby retaining
local telephony functionality.
10

Aeonix Administration Manual Managing VOIP Gateways 10-11

 If secondary cluster servers are associated with this Wave Gateway, you will
be prompted to either attribute Primary cluster survivability mode to this
Wave Gateway or disassociate the other cluster servers from this Wave
Gateway.

4 Cluster survivability mode can be enabled to allow for local telephony

continuity at remote sites where connection to the cluster is lost.
This is done by setting a separate backup Aeonix cluster at the remote site
(referred to as the Secondary cluster). Under normal circumstances, Wave
Gateway phones at the remote location are connected to the main Primary
cluster. However, when the connection of the remote location to the primary
cluster is down, the Wave Gateway automatically switches to the secondary
cluster, allowing telephony functionality to continue as before. When the
connection of the remote location to the primary cluster is restored, the Wave
Gateway automatically switches back to the primary cluster.
Note: Active calls are not disconnected during a primary cluster failure.
Aeonix registers the phone to the new cluster once the call is terminated.
The Wave Gateway passively monitors the connection status of the Aeonix
servers in the Primary cluster. Once the connection of at least one server in the
primary cluster is restored, the Wave Gateway will reconnect the phones to the
primary cluster after the time set in the Reconnect to primary timeout
parameter has expired.

Set the survivability parameters as described in the Table 10-6.

Table 10-6 Wave Gateway

Survivability Parameters Field Description

Survivability Select this check box to display the Cluster mode drop-down list.
Configuring Wave Gateways
10

10-12 Managing VOIP Gateways Aeonix Administration Manual

 Field Description

Cluster mode From the drop-down list, select the role of this cluster survivability
mode (Primary or Secondary). Primary designates that this is
the cluster the Wave Gateway normally connects to, while
Secondary designates the cluster to be used in the event that all
the servers in the Primary cluster are down.

Reconnect to If Primary is selected, you can define the number of seconds

primary Aeonix waits before reconnecting to the primary cluster once it
timeout has detected that at least one server is stable again.
(default: 180
seconds) NOTE: It is recommended to enable cluster High Availability (see
Enabling and Configuring High Availability, page 14-51) in order to
optimize connection times when connecting to another
server or cluster.

Servers The list of available Aeonix servers in the primary cluster. Select
the servers you want to use with this Wave Gateway.

Other cluster The list of the Aeonix servers in the secondary cluster. Click the
servers link to quickly access the relevant Aeonix server.

5 Click the Synchronization tab. This tab is used to define the clock reference
source with which the Wave Gateway switching is synchronized.

Figure 10-5
Synchronization Tab

Configuring Wave Gateways

6 Set digital clock synchronization parameters as follows:
a To use a digital trunk card as the primary (PRM) clock—under Primary,
select the relevant card from the Shelf, Slot drop-down list. The Sync
status of the card is displayed to the left.
10

Aeonix Administration Manual Managing VOIP Gateways 10-13

 A green circle icon indicates that the clock is active; a red icon, that the clock
is not active. View the specific icon’s tooltip for more information.

b To use a digital trunk card as the secondary (SEC) clock—under

Secondary, select the relevant card from the Shelf, Slot drop-down list.
The sync status of the card is displayed to the left.

The Peer drop-down list is available when the 2DT card is selected from the
Shelf, Slot drop-down list. Select the peer from the corresponding
drop-down list as required. Select Both for synchronization redundancy.

Current Clock shows the current clock reference source with which the
Wave Gateway is synchronized. If no source is available, the gateway uses its
internal Self (master) clock.
7 Click the Card List tab and configure the Wave Gateway cards and devices.
(For detailed instructions, see Configuring Wave Gateway Cards, page 10-17).
8 Click the Alarms tab. This tab is used to configure the Wave Gateway to send
alarms to Aeonix, which in turn sends the alarms to the NMS system.

Figure 10-6 Alarms Tab

Configuring Wave Gateways

9 Set the Alarm parameters as described in the Table 10-7.

10

10-14 Managing VOIP Gateways Aeonix Administration Manual

Table 10-7 Wave Gateway
Alarm Parameters Parameter Description

Report Notifies Aeonix of Wave Gateway alarms (default: selected).

alarms
NOTE: For Wave Gateway versions lower than 3.12.11, the default
is cleared.

NOTE: By default, the Wave Gateway updates Aeonix with its

status every 15 minutes.

Report Now Click this button to automatically update Aeonix with the latest
Wave Gateway status.

System type IPx 500 / IPx 4GC / FlexiCom 4GC / IPx SVC / HDC / MEX /
Office

Monitored by The server that is connected to the WG and gets the WG alarms

Fault alarm The port through which the gateway sends alarms to Aeonix
port (read-only)
(preset to
11015)

Refresh The frequency (in minutes) that Aeonix is updated with the latest
alarm Wave Gateway status
frequency
(preset to 15)

Last The last time the Wave Gateway initialized

Initialization
Time

Last The reason for the last initialization:

Initialization  LOCK_DEV - Lock device failure
Cause  GC_FAULT - Problem with the GC
 POWER_UP - Irrelevant for ATS systems

NOTE: All other causes are internal errors.

Configuring Wave Gateways

10 Click Save. The Wave Gateway is included in the gateway list.
10

Aeonix Administration Manual Managing VOIP Gateways 10-15

NOTES:
 10.3 Configuring Wave Gateway Cards

For the Wave Gateway1 and its connected phones and trunks to operate in Aeonix, the
Wave Gateway peripheral cards must be properly configured. The Wave Gateway
phones and trunks must be defined as well.

Wave Gateway is not supported in A4C.

Once a Wave Gateway has been defined and successfully connected to Aeonix, its
inserted peripheral cards are displayed and can be managed in the Aeonix Portal
through the Wave Gateway Card List tab. Managing Wave Gateway peripheral cards
includes the following:
 Card List, page 10-18
 Managing Wave Gateway Phones or Trunks, page 10-22
 Configuring Card Parameters, page 10-24
 Adding a Card, page 10-37
 Deleting a Card, page 10-38

Wave Gateway devices can be defined in Aeonix through their Phone and
Trunk pages. For instructions, see Chapter 7, Managing Phones and
Chapter 8, Managing Trunks.

Configuring Wave Gateway Cards

10

1. The Coral Gateway series includes the Coral IPx Office, 500, 800, 3000; FlexiCom 400
(with HDC controller), 5000

Aeonix Administration Manual Managing VOIP Gateways 10-17

  Card List

Wave Gateway peripheral cards are accessed and configured from the Card List tab.

To display this tab:

1 On the VOIP Gateway List page (see Figure 10-2), click the ID of the relevant
Wave Gateway. The Wave Gateway page is displayed.
2 Click Configure. The Wave Gateway configuration parameters are displayed.
3 Click the Card List tab.

Figure 10-7 Card List Tab

The Card List tab displays the peripheral cards of the Wave Gateway unit, including
trunk, station, media resources, and PCM resources peripheral card types. If further
cards are inserted into the Wave Gateway, click Refresh to update the list with the new
cards.
Configuring Wave Gateway Cards

The peripheral cards are sorted by Shelf/Slot. Active cards are displayed first. For each
card, the list displays the following information and links.
10

10-18 Managing VOIP Gateways Aeonix Administration Manual

Table 10-8 Card List
Parameters Field Description

Status icon Is displayed to the left of each card.

(circle) A circle icon to the left of each card indicates the following:
 Green - the card is in ACTIVE status.
 Red - the card is in any other status (specified in the Status
column).

NOTE: View the specific icon’s tooltip for more information.

Shelf / Slot The shelf and slot physical location of the peripheral card in the
Wave Gateway unit. For trunk or station type peripheral cards,
click to set up and manage phones or trunks of this card from the
Trunk List page.

NOTE: When adding a new trunk, select the check box to add all
the available endpoints that are on the specified card.

P_Type Present card type—the name of the peripheral card currently

inserted in the specified slot.

Table: If this value is different from the I_Type value, the inserted
card will not function.

I_Type Install type—the peripheral card name for which the slot has
been initially configured.

NOTE: The card list does not include empty shelf/slots for which no
IType is specified.

Status The current status of the peripheral card. Possible values are:
 ACTIVE
 ACTIVE/P—partially active
8DRCF/8DRCM/8DRCM-2 card: not enough resources to
support sub-circuits
iDSP card: not all tone generators are being used
 REPLACED—P_Type and I_Type do not show the same card
names

Configuring Wave Gateway Cards

 WAIT_DB
All cards: the card has not received its database or has not
reported initialization
UGW card: wrong MAC address, no network connection to
Media and/or Signaling, MRC or network configuration problem
 NO_RESOURCES—insufficient Wave Gateway memory to
initialize card
 Fault—HDLC problem

Version / The software version and subversion loaded on the card

Subversion
10

Aeonix Administration Manual Managing VOIP Gateways 10-19

 Field Description

Card Click Configure to set up a digital trunk card, media card, or

Configuration resource card. For other cards, this column is left blank.
Configuring Wave Gateway Cards
10

10-20 Managing VOIP Gateways Aeonix Administration Manual

 Card List Tab Actions
From the Card List tab, you can perform the following actions:

Table 10-9 Actions

Performed from the Card Action Button / Icon Description
List Tab
Define Shelf/Slot Click to display and manage the phones or trunks
phones or column entry connected through this card (see Managing Wave
trunks of Gateway Phones or Trunks, page 10-22).
card
Configure Configure Click to set card parameters.
card (in Card  PUGW/PUGW-2G: Media (see Media Channel
Configuration Configuration for PUGW/PUGW-2G Cards, page 10-25)
column)  ISDN (PRI, BRI): D-channel or B-channel
signaling (see D-Channel Configuration for ISDN Cards,
page 10-29)
 Other digital cards: signaling (see Signaling Channel
Configuration for Non-ISDN Digital Cards, page 10-36)
Add card Define the card configuration of a slot before
inserting a card into this slot (see Adding a Card,
page 10-37).
Delete card Delete the card configuration of a slot after removing
the card from this slot (see Deleting a Card, page 10-38).

Configuring Wave Gateway Cards

10

Aeonix Administration Manual Managing VOIP Gateways 10-21

  Managing Wave Gateway Phones or Trunks

Wave Gateway phones (stations) and trunks are physically connected to a

Wave Gateway unit through ports of dedicated cards. The Wave Gateway uses
station-type cards for Wave Gateway phones and trunk-type cards for Wave Gateway
trunks. For a list of card types, refer to the Wave Gateway Program Interface
Reference Manual (see Related Documentation, page 1-17).
To function, Wave Gateway phones and trunks must also be defined in Aeonix, just as
any Aeonix device. Defining Wave Gateway phones or trunks can be performed as
described in Configuring Phones in Aeonix, page 7-9 or Configuring Trunks in Aeonix,
page 8-9, or from their Wave Gateway card page as described in the following
procedure. Defining Wave Gateway phones or trunks can be performed as follows:
 Using the procedure for defining phones or trunks in Aeonix (see Configuring
Phones in Aeonix, page 7-9 or Configuring Trunks in Aeonix, page 8-9)
 From their Wave Gateway card page (see below)

Defining Wave Gateway Phones and Trunks at Card Level

To define Wave Gateway phones (stations) or trunks for their card:

1 On the Card List tab (see Figure 10-7), click the Shelf/Slot entry of the
relevant station or trunk card.
Depending on the selected card type, the Phone List page or Trunk List page is
displayed, listing the phones or trunks that have already been defined for this
card.

Phones and trunks that have not been defined in Aeonix are not included in
the list, even if they are connected to the Wave Gateway unit.
Configuring Wave Gateway Cards

Figure 10-8 Phones for a

Station-type Card
10

10-22 Managing VOIP Gateways Aeonix Administration Manual

Figure 10-9 Trunk List for
a Trunk-type Card

The information provided in the Phone List and Trunk List is the same as in
Phone List Page, page 7-3 and Trunk List Page, page 8-2, except that only devices
belonging to the relevant card are listed.
2 Do any of the following:
 To update the list display, click Refresh.
 To add a phone or trunk definition, click Add. See Defining a Phone in
Aeonix, page 7-10 or Defining a Trunk in Aeonix, page 8-10.
 To update a phone or trunk definition, click the relevant ID in the list.
 To search for a phone or trunk related to the card, use the Search utility.
See Searching for Phones, page 7-7 or Searching for Trunks, page 8-7.
 To view or edit the default entity of a phone or trunk, click the relevant
Default User or Default Trunk Group in the list.
 To delete one or more phone or trunk definitions, select the check box left
of the relevant items and click Delete.
3 Click Back to return to the Card List tab on the Gateway page.
4 Click Save.

Configuring Wave Gateway Cards

10

Aeonix Administration Manual Managing VOIP Gateways 10-23

  Configuring Card Parameters

To configure a card:
1 On the Card List tab (see Figure 10-7), click Configure to the right of the
relevant card (in the Card Configuration column). The card parameters are
displayed.
2 View or set card parameters:
 CUGW, PUGW and PUGW-2G cards—see Media Channel Configuration for
PUGW/PUGW-2G Cards, page 10-25
 ISDN PRI and BRI cards (2DT, PRI-23, PRI-30, 4TBR, and 8TBR)—
see D-Channel Configuration for ISDN Cards, page 10-29
 Non-ISDN digital cards (30T, T1, and UDT)— see Signaling Channel
Configuration for Non-ISDN Digital Cards, page 10-36
3 Click OK to return to the Card List tab on the Gateway page.
4 Click Save.
Configuring Wave Gateway Cards
10

10-24 Managing VOIP Gateways Aeonix Administration Manual

 Media Channel Configuration for PUGW/PUGW-2G Cards

Updating any parameters causes a card to be restarted and terminates all calls related
to this card:

Figure 10-10 GW Card

Configuration

Media channel parameters for PUGW/PUGW-2G cards include:

 General and signaling parameters (see PUGW/PUGW-2G Cards: General and
Signaling Parameters, page 10-26)
 Media parameters (see PUGW/PUGW-2G Cards: Media Parameters, page 10-27)
 Security type parameters (see PUGW/PUGW-2G Cards: Security Type Parameters,
page 10-28)
 Capacity parameters (see PUGW/PUGW-2G Cards: Capacity Parameters,
page 10-28)

Configuring Wave Gateway Cards

10

Aeonix Administration Manual Managing VOIP Gateways 10-25

 PUGW/PUGW-2G Cards: General and Signaling Parameters
Field Description

Type The type of the PUGW/PUGW-2G card

(Read-only)

Location The shelf and slot where the card is located

(Read-only)

Local IP The static local IP address for the PUGW/PUGW-2G card

address signaling. This field must be updated upon PUGW/PUGW-2G
card initialization. The local address is used for IP devices
located within the system network, i.e. between the
Wave Gateway and the Router.
Enter a valid IP Socket (IP Address and IP Port number).
 When no Router/NAT server is used, the Global and Local
sockets are identical.
 The signaling IP port must be 2427.
 If no IP port number is entered, the system automatically
assigns the default CA_SIG_PORT value defined in the
Wave Gateway Program Interface. For details, refer to the
Wave Gateway Program Interface Reference Manual
(see Related Documentation, page 1-17).
 If this field is left blank while the Global IP Address below is
defined, the Global IP Address will be deleted by the system.

Global IP The static global IP socket (IP address and IP port) for the
address PUGW/PUGW-2G card signaling. This address is used for
remote IP endpoints or nodes.

NOTE: When no router or NAT server is used, the Local and the
Global IP addresses are identical (see Local IP address
above).

Subnet mask The subnet mask address of the card

Default router The default router address of the card

Configuring Wave Gateway Cards

address

Diff Serv Always set to No.

802.1 Q/p Always set to No.

10

10-26 Managing VOIP Gateways Aeonix Administration Manual

 PUGW/PUGW-2G Cards: Media Parameters
Parameter Description

MAC This field is relevant for the MG modules only. Therefore, any
value can be entered in this field or the field may be left blank.
The entered value is saved regardless of the true MAC
address.
In order to view the true MAC address for any MRC, browse to
its PUGW/PUGW-2G address via any Internet Browser. The
MRC MAC address can also be found on the inside of the
Wave Gateway (Coral IPx Office) motherboard.

Local IP The static local IP socket (IP Address and IP Port) for the
address media module.
The local IP address is the address of the PUGW/PUGW-2G
card when accessed from the LAN.
PUGW port: 16400
UGW port: 30000

Global IP The static, global IP Socket (IP Address and IP Port) for the
address media module.
The global IP address is the address of the PUGW/PUGW-2G
card when accessed from the other side of the NAT (the
outside world).
PUGW port: 16400
UGW port: 30000

Subnet mask The subnet mask address of the media module

Default router The default router address of the media module

address

Echo The echo cancellation period required for this UGW or UGWipx
cancellation card.
period
NOTE: An echo cancellation period of longer than 32 msec
reduces the MG endpoint capacity. The MG will provide

Configuring Wave Gateway Cards

20 instead of 24, 40 instead of 48, or 60 instead of 72
channels.

MG The compression capabilities (codecs) available with this media

compression module.
capability
NOTE: This field is only displayed if a physical PUGW/PUGW-2G
(Read-only)
card is installed.

Diff Serv Always set to No.

10

802.1 Q/p Always set to No.

(Read-only)

Aeonix Administration Manual Managing VOIP Gateways 10-27

 PUGW/PUGW-2G Cards: Security Type Parameters
Field Description

DES Always set to No

(Read-only)

Triple DES Always set to No

(Read-only)

PUGW/PUGW-2G Cards: Capacity Parameters

Field Description

Physical Capacity
(only displayed if the physical PUGW/PUGW-2G card is installed)

Media channels The maximum number of media channels that can be

(Read-only) supported by the PUGW/PUGW-2G card, based on the card
hardware and regardless of assigned resources.

Resource types The type of system resources supported by the MRC located
(Read-only) on this card (if available)

NOTE: This field is only relevant for MRC cards.

Max G.711 The maximum number of media channels that are available
media channels when using G.711 protocol, when this card is used only for
(Read-only) media channels.
When other media protocols are used, or if MRC resources are
used, this number of media channels cannot be achieved.

NOTE: This field is only relevant for MRC cards.

Required Capacity

Media channels The maximum number of media channels that the media
Configuring Wave Gateway Cards

module can support based on its type (24, 30, 48, 60, or 72).
Media channels are needed when one of the calling parties is
not an IP host, for Wave Gateway phones to any phone that is
not a Wave Gateway phone and to any Aeonix application.
 The actual number of channels that the media module can
support (see Media channels under Physical Capacity above)
 The corresponding value defined in Sizes (refer to the
Wave Gateway Program Interface Reference Manual)
Only when none of the media gateway compression definitions
match the compressions defined for the IP phones, then the
call cannot be completed.
10

10-28 Managing VOIP Gateways Aeonix Administration Manual

 D-Channel Configuration for ISDN Cards

Figure 10-11 ISDN Card

Configuration (8TBR
Card)

Signaling parameters for ISDN cards include:

 General parameters (see ISDN Cards: General Parameters, page 10-30)
 BRI cards only parameters (see ISDN Cards: BRI Parameters, page 10-33)
 Parameters for channels using the QSIG protocol (see ISDN Cards: QSIG
Parameters, page 10-35)

Configuring Wave Gateway Cards

10

Aeonix Administration Manual Managing VOIP Gateways 10-29

 ISDN Cards: General Parameters
Field Description

Peer The D-signaling channel to be configured.

NOTE: This field can only be selected for BRI and 2DT cards.
For PRI cards, the D-channel is always 0.

Peer type The trunk protocol of the peer to be configured:

 PRI23 (North American market)
 PRI30 (Other)

NOTE: This field is only displayed for 2DT cards.

Description Optional description of the card (up to 16 characters)

Protocol ID The used standard public or private network protocol:

 AT&T, ETSI (for TBR card version 8.60)
 ETSI (European)
 Australia (not applicable for 2DT cards)
 QSIG (Internal Network Trunks: ECMA 143/ETSI
300172/ISO DIS11572 Standard). This option is used for
private networks. See also ISDN Cards: QSIG Parameters,
page 10-35.
For PRI cards: Do not set this field to QSIG if the card
accommodates trunks with Overlap dialing method.
For BRI cards: The Protocol ID of Channel 0 is also used for
the other signaling channels of the card. This field can be
defined individually for each channel only if Channel 0t is set to
QSIG.

Protocol side Defines the DSL side at the particular exchange (channel) as
the User or Master side.
A Digital Subscriber Line (DSL) must always have one
exchange side defined as User (slave) while the other side is
defined as Network (master). The Network side resumes call
control in restart (protocol failure) situations. In glare situations,
Configuring Wave Gateway Cards

Network side calls take priority over User side calls.

Set this field as follows:
 User—if the other side of the DSL is the PSTN (i.e. any
public network)
 Network—if the other side is an ISDN application, such as
video conferencing, or any vendor’s equipment that cannot
function as the Network side
 Symmetric—if the other side (not applicable for 2DT cards)

NOTE: This field is only displayed if all of the following apply:

The card is a PRI card.
10

Protocol ID is not set to QSIG.

10-30 Managing VOIP Gateways Aeonix Administration Manual

 Field Description

B Channel The procedure in case the network fails to accept a requested

negotiation channel:
 Exclusive—failure to accept the requested channel by the
network causes the call to be disconnected by Aeonix.
 Preferred—failure to accept the requested channel causes
the network to suggest an alternative channel. As a result,
Aeonix switches the call over to the suggested channel.
The procedure is transparent to the user.

NOTE: This field relates only to outgoing calls. Incoming calls

are automatically Exclusive.

Extension NOTE: This field is only displayed if all of the following apply:
The card is a BRI card.
Protocol ID is not set to QSIG.
Protocol side is set to Network.
Defines the Network extension as a port or trunk:
 Yes—connects the BRI line to an external application or
terminal equipment such as video, router, ISDN telephone,
and so on
 No—connects the BRI line to another PBX, thus defining the
BRI line as a trunk

Local ringback NOTE: This field is only displayed if all of the following apply:
The card is a PRI card.
Protocol ID is not set to QSIG.
Protocol side is set to Network.
The source of the ringback tone sent to the caller making a call
over a PRI trunk:
 Yes—the local Aeonix system sends the ringback tone to the
calling party.
 No—the remote PBX sends the ringback tone.
Set this field to Yes when the remote PBX does not support
the requested ringback tone.

Configuring Wave Gateway Cards

End of dial digit NOTE: For most European systems, this field is not relevant and
must be left blank.
The character added to the end of the destination number
(called party number) sent over the trunk to signal the end of
dialing.

‘Sending Defines whether or not a “sending complete” information

Complete’ for element should be added to the Called Party number,
outgoing calls indicating that the entire number was transmitted.
10

Aeonix Administration Manual Managing VOIP Gateways 10-31

 Field Description

‘Sending NOTE: This field is only displayed if Protocol ID is not set to

Complete’ for QSIG.
incoming calls
Specify as follows:
 Set to Yes if all incoming network calls are known to be
enblock calls.
 Set to No if overlap as well as enblock network calls are
expected.

Connect when NOTE: This field is only displayed if Protocol ID is not set to
destination is QSIG.
not ISDN This field applies only to overlap calls and is only relevant
for the Italian market.
This field is used in situations when an overlap call is sent to a
system (e.g., Interactive Voice Response - IVR) that sends
back the ISDN progress message Dest_is_not_ISDN.
 Yes—allows Aeonix to switch to a connect state and start
sending DTMF tones to the terminating device or terminating
non-ISDN switch after receiving the Dest_is_not_ISDN
message.
After incoming digits have been received, the system sends
DTMF tones before connecting when a PRI progress
message Dest_is_not_ISDN is received from the far side
(CO or PBX).
 No—the system cannot read the Dest_is_not_ISDN
message and therefore can send and receive DTMF tones
only after a preconfigured timeout period.

Change to NOTE: This field is only displayed if Protocol ID is not set to

DTMF when QSIG. This field applies only to overlap calls and is only
call proceeding relevant for the Italian market.
This field is used in situations when an overlap call is sent on a
PRI trunk to an application (e.g., Interactive Voice Response -
IVR) that sends back an ISDN Call Proceeding message (88H)
before a Connect message is received.
Configuring Wave Gateway Cards

 Yes—allows Aeonix to start sending DTMF tones to the

terminating device after receiving the ISDN Call Proceeding
message and before a Connect message is sent (effectively
not charging for the call).
After incoming digits have been received, the system sends
DTMF before connect when a PRI Progress message
call_proceeding is received from the far side (CO or
PBX).
 No—the system cannot read the Dest_is_not_ISDN
message and therefore can send and receive DTMF tones
only after receiving the Connect message.
10

10-32 Managing VOIP Gateways Aeonix Administration Manual

 ISDN Cards: BRI Parameters
Field Description

Synchronize NOTE: This field is only displayed for BRI cards.

channel Set to Yes only if Permanent active channel below is set to
Yes.
This field is relevant when the BRI card is selected as the PRM
or SEC clock reference source (see Defining Wave Gateway
Setup/Synchronization/Alarm Parameters, page 10-10). In such a case,
one of the 4 or 8 channels (4TBR or 8TBR) is automatically
selected by the system as the synchronization source.
This field determines whether or not the current channel may
be one of the synchronization sources.

Permanent NOTE: This field is only displayed for BRI cards.

active channel
This field is determined according to an agreement or a
request of the CO at the far side.
 Yes—the line is permanently active even if there is no
conversation taking place.
 No—the line is silent and inactive when no conversation is
taking place. Data does not flow through the line, and it can
not operate as a synchronization clock source.

Power supply NOTE: This field is only displayed for BRI cards and does only
apply to 4/8TBR-P cards.
Defines whether the 4/8TBR-P card, when installed, supplies
power (-48V: US systems or -42V: European Systems) for the
BRI lines to the ISDN terminal equipment.

TEI assignment NOTE: This field is only displayed for BRI cards.
The Terminal Endpoint Identifier (TEI) for layer 2 of the
protocol communications.
Select Fixed if a pre-assigned value defined as 0 is used.
Generally, select this option if Aeonix is connected to a PBX or
to a public network (the CO).

Configuring Wave Gateway Cards

Select Auto if the value is defined automatically by the
Network or User side (see Protocol side above). Use this option
in the following cases:
 The protocol side of the line is defined as network and the
line is connected to an ISDN application, such as video
conference or router.
 The BRI line is used as a multipoint BRI support.
10

Aeonix Administration Manual Managing VOIP Gateways 10-33

 Field Description

External line is NOTE: This field is only displayed for BRI cards.
physically
Select Yes to identify the BRI port as active and connected to
connected
a physical line. This option is recommended unless there are
particular problems with the specific channel.
Select No if the port is not connected to a line and a reset
option is required for the BRI line. When this option is selected,
the BRI line is disabled and the channel LED is lit.
Configuring Wave Gateway Cards
10

10-34 Managing VOIP Gateways Aeonix Administration Manual

 ISDN Cards: QSIG Parameters
The parameters in the following table are only displayed for the channel if its
Protocol ID (on page 10-30) is set to QSIG. The following requirements must be met
when defining these parameters:
 PRI/BRI card version 6.0 or higher is required between all nodes.
 The parameters must be defined identically in all the network nodes.
 Network PBXs with Coral software versions lower than 10 (and PRI/BRI card
versions lower than 6.0) do not support CISC (Call Independent Signaling
Connection). Therefore, network camp-on, follow-me and divert features
cannot work between the nodes or via a node with a PRI/BRI card version
lower than 6.0.

Field Description

Support CISC CISC (call independent signaling connection) calls are

D-channel signaling without B-channel (voice). They allow
using QSIG network features between nodes, such as camp-on
and follow-me.
Set this fields as follows:
 Yes—CISC calls are supported. Once a connection is made
between the two parties (nodes), signaling continues
between both sides as required by the application.
 No—CISC calls are not supported. Select this option if any
one of the network nodes does not support CISC.

Protocol profile Defines the Protocol Profile field in QSIG Facilities for Aeonix
features used in this network node. The Protocol Profile is
defined as 11H for ECMA or as 1FX for ISO.

NOTE: To communicate, all the network node PBXs must have

the same protocol profile defined.

Configuring Wave Gateway Cards

10

Aeonix Administration Manual Managing VOIP Gateways 10-35

 Signaling Channel Configuration for Non-ISDN Digital Cards
For non-ISDN digital cards, the trunk signaling method can be selected for each time
slot (trunk). The following methods are available:

Method Description Relevant for

E&M Ear and Mouth tie trunk All non-ISDN digital cards

DDI Direct Dialing Inward trunk All non-ISDN digital cards

(same as DID) except for 30T/ T1

DDO Direct Dialing Outward trunk All non-ISDN digital cards

(same as DOD) except for 30T/ T1

LS Loop Start trunk 30T/ T1

Configuring Wave Gateway Cards
10

10-36 Managing VOIP Gateways Aeonix Administration Manual

  Adding a Card

This procedure allows you to define a card configuration for a specific shelf/slot, and
insert the card at a later stage into the Wave Gateway unit, such as
Coral IPx Office, 500, 800, 3000 and FlexiCom 5000.

To add a Wave Gateway card configuration:

1 On the Card List tab (see Figure 10-7), click Add. The Add Card box is
displayed showing all available shelf/slots, including those for which no
I_Type has been configured.

Figure 10-12 Add Card

box

2 In the I_Type column, select the card type for the relevant Shelf/Slot entry.
3 Click OK.
4 Click Save at the bottom of the Card List tab. The VOIP Gateway List page is
displayed.

Configuring Wave Gateway Cards

5 Click the relevant Wave Gateway to return to the Wave Gateway page and
configure the new card as required (see Managing Wave Gateway Phones or
Trunks, page 10-22 and Configuring Card Parameters, page 10-24). 10

Aeonix Administration Manual Managing VOIP Gateways 10-37

  Deleting a Card

The following procedure removes a card, as well as all its phones or trunks, from the
Wave Gateway database. However, the phone or trunk definitions are not deleted from
the Aeonix database and displayed on the general Phone List or Trunk List page.
Deleting a card configuration removes a slot assignment and thereby frees
Wave Gateway database resources.

A card configuration can only be removed if no card is inserted in the

relevant slot. Therefore, prior to deleting the configuration, remove the
relevant card from the Wave Gateway unit.
Applicable Wave Gateway unit, such as Coral IPx Office, 500, 800, 3000 and
FlexiCom 5000.

To delete a Wave Gateway card configuration:

1 On the Card List tab (see Figure 10-7), select the check boxes next to the card
or cards to be deleted.
2 Click Delete. A confirmation box prompts you to delete this card.
3 Click Yes. The card is deleted from the Wave Gateway database and removed
from the card list.
4 Click Save.
Configuring Wave Gateway Cards
10

10-38 Managing VOIP Gateways Aeonix Administration Manual

NOTES:
Configuring Wave Gateway Cards
10

10-40 Managing VOIP Gateways Aeonix Administration Manual

 10.4 Configuring Tadiran TGW Gateways

This section describes how to configure Tadiran TGW Gateways in the Aeonix Web
Portal.
 Defining a Tadiran TGW Gateway, page 10-42

Configuring Tadiran TGW Gateways

10

Aeonix Administration Manual Managing VOIP Gateways 10-41

  Defining a Tadiran TGW Gateway

This procedure describes how to add a Tadiran TGW Gateway, including specifying
its basic (Aeonix related) parameters, provisioning settings, and batch configuration
settings.
When a Tadiran TGW gateway is physically connected to the Aeonix network, it is
automatically identified by the system according to its MAC address, as follows:
 The gateway is plugged in and connected to the network
 The gateway accesses the DHCP server to get its IP address and the
provisioning server address
 The gateway initiates a provisioning request to the Aeonix server URL and
specifies its MAC address in this request
 If the gateway is unlisted with Aeonix, the MAC is added to the MAC list of
gateways that are pending batch or manual configuration
At this point, the gateway and its related entities can be configured by manually
entering the gateway’s MAC address, or by selecting the gateway’s MAC address
from the Select from Plug & Play option (see Table 10-10).

For Auto Generation options, see Table 10-13, Table 10-14, Table 10-15,
and Table 10-16.

To add or update a Tadiran TGW Gateway configuration:

1 In the navigation pane, select the VOIP Gateways menu, and then do one of
the following:
 To define a new Tadiran TGW Gateway, click Add VOIP Gateway, and
then from the Device model drop-down list, select the relevant TGW
Configuring Tadiran TGW Gateways

gateway model.
 To update an existing Tadiran TGW Gateway, click VOIP Gateway List
and select the relevant ID in the list.
 To create a copy of an existing Tadiran TGW Gateway, click VOIP
Gateway List. On the VOIP Gateway List page (see Figure 10-2), click
(the Clone icon) to the right of the relevant gateway.
10

10-42 Managing VOIP Gateways Aeonix Administration Manual

 When you clone a Tadiran TGW Gateway, all parameter values are copied to
the new gateway except for the gateway ID and the Closed User Group. The
IP address of the gateway is not copied to a new gateway.

The VOIP Gateway page is displayed.

Figure 10-13 Tadiran

TGW Gateway Page for a
new VOIP Gateway

2 Set the basic parameters as described in the following table.

Configuring Tadiran TGW Gateways

Table 10-10 Basic Tadiran
TGW Gateway Field Description
Parameters
ID Unique ID for the gateway. (The ID can only include
letters, digits, dashes (-), and underscores (_); spaces are
not allowed.)

NOTE: This field must only be defined for new gateways.

Closed User Group The Closed User Group the gateway belongs to
(Default: Root) (see Closed User Groups (CUG), page 4-29).
10

NOTE: This field cannot be modified after the gateway is

added to the system.

Aeonix Administration Manual Managing VOIP Gateways 10-43

 Field Description

Description Short description of the gateway (optional)

Registered entries For existing Tadiran TGW gateways, links to the

associated entities of the gateway are displayed and the
number of registered entities is indicated.

NOTE: Click the relevant entity to access the corresponding

page in the Aeonix Admin.

Device model The selected Tadiran TGW gateway model

IP address For existing Tadiran TGW gateways, the IP address

assigned to the gateway is displayed. This address is
defined on the gateway and retrieved from the Aeonix
system when the gateway is registered. Click the IP
address to access the TGW box Admin.

NOTE: It is not recommended to make changes to

parameters in the TGW box that are provisioned by
Aeonix, as these parameters will get overwritten in
the next provisioning session.

MAC address Start filling in the MAC address of the gateway to display a
list of all the existing MAC addresses containing the
entered value, and then select the required value.
Alternatively, select the adjacent check box, and then
select the gateway’s MAC address from the Select from
Plug & Play drop-down list. See the following section
Defining Tadiran TGW Gateways with Plug and Play Deployment
beginning on page 10-50 for the procedure to deploy a Tadiran
TGW via the Plug and Play feature.

NOTE: In the event a faulty TGW gateway is replaced,

Aeonix automatically updates related entities,
including users, trunk groups, phones, and trunks
with the new MAC address.
Configuring Tadiran TGW Gateways

3 For auto provisioning, set the parameters as described in the following table.
10

10-44 Managing VOIP Gateways Aeonix Administration Manual

Table 10-11 Auto
Provisioning Parameters Field Description

Auto provisioning Select to activate auto provisioning. For a list of the

parameters that are provisioned, see Table 10-12.

NOTE: Auto provisioning is activated during the following

hour after clicking Save even if no parameters
were changed.

Provisioning profile Select the required provisioning profile from the

drop-down list.

NOTE: The details of the provisioning parameters are

displayed below the selected profile.

The following requirements must be met when using Auto Provisioning:

 The DHCP server must have option 66 set to the hostname or IP address
of the Aeonix server. It is recommended to use the hostname for
redundancy purposes.
 The server URL must be defined in secured layer mode (https) access to
Aeonix in the following format: https://<aeonixserver
address>:8443/aeonix/Provisioning (replace <aeonixserveraddress>
with the IP address of the Aeonix server or with the Aeonix servers DNS
name in a cluster environment). It is recommended to use the DNS name
for redundancy purposes.

4 If auto provisioning is used, the gateway is automatically configured according

to parameters defined from the Provisioning Profiles page and from other
pages of the Aeonix Admin, as follows:

Table 10-12 Provisioning

Parameters Parameter Description

Configuring Tadiran TGW Gateways

Outbound The IP address or hostname of the SIP server or SBC to which
proxy address phones connected to the gateway send all requests, as defined
from the Provisioning Profile page (see Table 5-25).

IP address or The IP address, host name, or DNS name of the Aeonix server
host name on which the phones connected to the gateway register, as
defined from the Provisioning Profile page (see Table 5-20).

SIP account The Device Name of the SIP phone used during the registration
authorization process of phones connected to the gateway, as defined from
10

name the Phone page.

Aeonix Administration Manual Managing VOIP Gateways 10-45

 Parameter Description

SIP account The SIP password used during the registration process of
authorization phones connected to the gateway when the Auto-Detect option is
password used, as defined from the Phone page (see Table 7-6).

Dial Plan The dial plan from which to apply Dial now rules to phones
connected to the gateway, as defined from the Provisioning
Profile page (see Table 5-25).

Country code The Country/ Region tone selection setting, as defined in the
Tadiran TGW box.

Offset time The Time zone according to the Location of the phone (see
from GMT Table 4-7).

NTP server The name or IP address of the first NTP server address
address 1 according to which time is set for phones connected to the
gateway, as defined from the Provisioning Profile page (see
Table 5-17).

5 All other parameters must be manually configured via the Tadiran TGW box
itself, which can be accessed directly by clicking the gateway’s ID via the
VOIP Gateway List page of the Aeonix Admin.

It is not recommended to make changes to parameters in the TGW box that

are provisioned by Aeonix, as these parameters will get overwritten in the
next provisioning session.

6 For Auto Generation of users and trunk groups batch configuration, set the
parameters as described in the following table.
Configuring Tadiran TGW Gateways

Table 10-13 Auto

Generation Users / Trunk Field Description
Groups Parameters
User login name The user login prefix assigned to newly created users.
prefix For example, if the prefix is a1 and the first available
alias is 4000, then the newly created user’s login name
would be a14000.

User alias starts at The starting alias according to which newly created
(Default: 4000) users are assigned available aliases during the batch
configuration process.
10

Voicemail service Select the required voicemail service from the

drop-down list.

10-46 Managing VOIP Gateways Aeonix Administration Manual

 Field Description

Create mailbox Provided that the selected voicemail service is active,

select this check box to create a mailbox for the newly
created users.

NOTE: The default mailbox password is 0000.

User profile The profile assigned to the user.

(Default: Default
User Profile)

Trunk group ID The trunk group ID prefix assigned to newly created

prefix trunk groups.

Trunk group alias The starting alias according to which newly created
starts at (Default: trunk groups are assigned available aliases during the
7000) batch configuration process.

Trunk group profile The profile assigned to the trunk group.

(Default: Default
Secured Trunk
Group Profile)

In addition, when the Users Auto Generation option is used, Aeonix attempts
to link the newly created TGW gateway phones to the user in the following
manner:
 First priority is given to imported users having the same TGW models.
Aeonix looks up the first available user that has the PnP flag with the user’s
PnP model being identical to the TGW model, and links the TGW to that
user.
 Second priority is given to imported users with no associated TGW models.
Aeonix looks up the first available user with the PnP flag with no TGW

Configuring Tadiran TGW Gateways

model definition and links the TGW to that user.

If no user was found, Aeonix creates a new user with parameters as

specified above (see Table 10-13, Auto Generation Users / Trunk Groups
Parameters).

7 For Auto Generation phones and trunks, set the parameter as described in the
following table.
10

Aeonix Administration Manual Managing VOIP Gateways 10-47

 Table 10-14 Auto
Generation Phones / Field Description
Trunks Parameter
Location (Default: The location where the phones and trunks are used.
Default location)

In this case, no default user is assigned to the phone. When Auto Generation
mode is activated without users, a default user can be assigned using
feature code 159 (see Set Default User in Table 4-10).

8 Click Save to save configuration changes, and, if specified, to perform auto

provisioning within the following hour and batch configuration on all related
TGW gateway entities. The TGW gateway is included in the VOIP Gateway
List page.
When Phone / Trunks Auto Generation is used, Aeonix creates phone and
trunk entities with the following parameters, which are linked by MAC address
to the created TGW gateway:

Table 10-15 Auto

Generation Tadiran SIP Parameter Description
phone parameters
Phone ID The SIP user name of the phone, in the following
format:

Box ID-N (where N is the physical line connection

starting from 1). For example, if the TGW box is
MyTGW, and the phone’s physical connection 22, the
phone ID would be MyTGW-22.

SIP password The authentication password used during the phone

registration process.
Configuring Tadiran TGW Gateways

NOTE: This is an auto generated, strong password.

MAC address The MAC address of the TGW gateway.

Physical line The physical line on the TGW gateway to which the
phone is connected.

Phone location The location of the phone

Default user The default user defined for this phone, in case Users
Auto Generation is used
10

10-48 Managing VOIP Gateways Aeonix Administration Manual

 All other phone parameters are derived from the SIP Terminal template (see
Chapter 7, Phone Templates).

Table 10-16 Auto

Generation SIP Trunk Parameter Description
parameters
Trunk ID The ID of the SIP trunk, in the following format:

Box ID-N (where N is the physical connection starting

from 1). For example, if the TGW box is MyTGW, and
the trunk’s physical connection 2, the trunk ID would be
MyTGW_2.

Registration mode SIP Trunk registers on Aeonix

Physical line The physical line on the TGW gateway to which the
trunk is connected.

Trunk location The location of the trunk

Default Trunk The default trunk group defined for this trunk, in case
Group Trunk Groups Auto Generation is used.

NOTE: Aeonix automatically adds the generated SIP

trunks as members of this Trunk group.

All other trunk parameters are derived from the SIP Trunk template (see
Chapter 8, Trunk Templates).

Configuring Tadiran TGW Gateways

10

Aeonix Administration Manual Managing VOIP Gateways 10-49

  Defining Tadiran TGW Gateways with Plug and Play Deployment

This procedure describes how to add Tadiran TGW Gateways and Phones using the
TGW Plug and Play Deployment feature.

For full TGP Plug and Play support, DHCP and DNS services are
required in the installation.

DHCP
DHCP is required to:
 Assign the Gateway its IP address (mandatory)
 Provide the device the address of the DND (recommended)
 Provide the device the address or name of the Aeonix server for provisioning
by using Option 66 (recommended)

TGW Provisioning Environment

TGW Plug and Play automation comprises three key functions:
 Batch operation to define all SIP Phones/SIP Trunks and Users/Trunk Groups
required for operation of a TGW -- in one action (to minimize manual admin
definition in Aeonix)
 Provisioning for TGW per type (to automate GW configuration)
Both the above functions require creation of a GW new entity in the system.
 Upgrade of TGW versions from Aeonix
Configuring Tadiran TGW Gateways

MAC Addresses for TGW Plug and Play

The automation creates a series of available MAC addresses known to Aeonix. The
network resources requirements for the TGW MAC address to appear in the Aeonix
New VOIP Gateway are described below.
10

10-50 Managing VOIP Gateways Aeonix Administration Manual

 TGW Device Configuration
The TGW must have the following settings configured via the device’s web portal
GUI:
 https://172.28.101.250:8443/aeonix/Provisioning/
 https://URL-NAME:8443/aeonix/Provisioning/
The DNS server must be set for URL-NAME, which is the Aeonix IP for
provisioning
 Select Option 66 if the DHCP server is set by IT to reply to the Aeonix IP for
provisioning
The following figure shown the TGW Auto Provisioning settings in the device’s web
portal GUI.

Figure 10-14 TGW Device

Setting for Auto
Provisioning

Time Window for MAC Address Availability in Aeonix

Configuring Tadiran TGW Gateways

When a TGW device is physically installed on the network, its (unassigned) MAC
address appears in the Select from Plug and Play List drop-down list on the Add
VOIP Gateway page for a limited amount of time as determined by the parameters
described below:

Start Time
 Precondition - TGW box provisioning is set correctly
 Immediate after the TGW device is restarted
10

 After 1 hour if you don't restart the TGW device

Aeonix Administration Manual Managing VOIP Gateways 10-51

 Timeout After Disconnect
 After 24 hours if you disconnect the box without configuring it

Alarm for Non-Configured TGW

 If you connect a TGW device for a period of more than 72 hours without
configuring/provisioning, a "Non-Configured TGW is Connected" alarm is
issued by Aeonix.

TGW Aeonix Configuration

To create a new TGW device instance choose VOIP Gateways > Add VOIP Gateway.
The New VOIP Gateway page is displayed as shown in the following figure.

Figure 10-15 New VOIP

Gateway Page
Configuring Tadiran TGW Gateways

The MAC addresses appear in the Select from Plug & Play list drop down list for a
certain period of time, as defined in Time Window for MAC Address Availability in Aeonix,
page 10-51. If the time period expires (72 hours), a "Non-configured TGW is
10

connected" alarm is generated by Aeonix. Choose a MAC address from the list, or
enter a MAC address manually.

10-52 Managing VOIP Gateways Aeonix Administration Manual

Figure 10-16 New VOIP
Gateway page - MAC
selected

Fill out the fields for the TGW. See the subsections in Defining a Tadiran TGW Gateway,
page 10-42 for detailed description of each of the fields and options.

Auto Generation Parameters

By checking the Users / Trunk Groups and/or the Phones / Trunks check-boxes, you
can have Aeonix generate new entities assigned to the new TGW entity. The new
entities will have the string from the User login name prefix field as a prefix string

Configuring Tadiran TGW Gateways

in their IDs, as shown in Figure 10-19 and Figure 10-20. Use the remaining Auto
Generation fields to define the attributes the new entities will have, as well as the range
and number of entities to be created and assigned to the TGW entity.

For Auto Generation options, see Table 10-13, Table 10-14, Table 10-15,
and Table 10-16.
By default, Auto Generation of users is based on the Default User Profile in
which users will consume Advanced User Licenses. To have the users
consume GW User Licenses instead, use a profile that is set for GW User
10

License.

Aeonix Administration Manual Managing VOIP Gateways 10-53

 Auto Provisioning Parameters
Set the Auto Provisioning parameters and select the Provisioning Profile. To create a
new provisioning profile, see Managing Provisioning Profiles on page 5-91.

For Auto Provisioning options, see Table 10-11 and Table 10-11.

When you have completed the definitions of the TGW, click Save. The VOIP Gateway
List page is displayed with the new TGW entity as shown in the following figure.

Figure 10-17 VOIP

Gateway List page - new
TGW entity displayed
Configuring Tadiran TGW Gateways

To verify and/or edit the details of the new entity, click on the ID of the new TGW
entity to display the VOIP Gateway page for that entity, as shown in the following
figure.
10

10-54 Managing VOIP Gateways Aeonix Administration Manual

Figure 10-18 VOIP
Gateway page - TGW
defined

To see the new user and phone entities that were created by the Auto Generation
process, click on the Phone List link. The Phone List page for the TGW is displayed
as shown in the following figure.

Configuring Tadiran TGW Gateways

10

Aeonix Administration Manual Managing VOIP Gateways 10-55

 Figure 10-19 VOIP
Gateway - Phone List

To see the new trunk entities that were created by the Auto Generation process, click
on the Trunk List link in the VOIP Gateway page. The Trunk List page for the TGW
is displayed as shown in the following figure.
Configuring Tadiran TGW Gateways
10

10-56 Managing VOIP Gateways Aeonix Administration Manual

Figure 10-20 VOIP
Gateway - Trunk List

Configuring Tadiran TGW Gateways

10

Aeonix Administration Manual Managing VOIP Gateways 10-57

  User Definitions CSV Import File

If you don’t want to use the Auto Generated user IDs described above, you can import
a CSV users definition file during the Plug and Play installation process.
See Importing / Exporting Users on page 6-79 for details on importing a users definition
file.
The TGW definition process uses the range of user IDs to create user entities and
assign them to the new TGW entity.
The CSV file must have the following format with the following fields defined in it
(the column headers are not included in the file):

Table 10-17 Users User Internal Phone Phone Phone Provisioning

Definition CSV File ID Alias Provisioning Provisioning Profile
Format MAC Model

3901 3901 PNP TGW96 Default provisioning

profile

3902 3902 PNP TGW96 Default provisioning

profile

3904 3904 PNP TGW96 Default provisioning

profile

3930 3930 PNP TGW96 Default provisioning

profile

3956 3956 PNP TGW96 Default provisioning

profile

3996 3996 PNP TGW96 Default provisioning

profile
Configuring Tadiran TGW Gateways

All fields are string fields that must have the exact string value in them.

To use a CSV file during TGW Plug and Play deployment:

1 Import the CSV file as described in Importing / Exporting Users on page 6-79.
2 In the Add VOIP Gateway page define the ID for the TGW.
3 Select the TGW Mac Address from the Select from Plug & Play list.
4 Check the Auto Provisioning check-box.
5 Check the Users / Trunk Groups check-box.
10

6 Check the Phones / Trunks check-box.

10-58 Managing VOIP Gateways Aeonix Administration Manual

 7 Set the User alias starts at field to the value of the first user ID defined in the
CSV file.
8 Click Save.
9 Reboot the TGW device.
 Auto Provisioning will update the TGW device firmware in necessary, and set
default parameters.
 The TGW will be assigned the users from the CSV file according to the User
alias starts at field.
 The phones will be registered in Aeonix.
10 Check that all 96 phones are operating correctly in the Phone List (green icon).
11 Check that all 96 users are registered correctly in the User List (green icon).

Configuring Tadiran TGW Gateways

10

Aeonix Administration Manual Managing VOIP Gateways 10-59

  Defining a Tadiran TGW PRI Gateway

Defining a PRI gateway is similar to defining other TGW gateways. Fill in the
parameter fields and choose the MAC Address from the Select from Plug & Play list.
Fill in the Auto Generation and Auto Provisioning fields as required.

Figure 10-21 New VOIP

Gateway Page - PRI TGW
Configuring Provisioning
Fields

Click Save to create the new PRI TGW entity. In the VOIP Gateways List page, click
Configuring Tadiran TGW Gateways

on the ID of the new PRI TGW entity. Verify and/or edit the fields in the PRI TGW
entity as required.
10

10-60 Managing VOIP Gateways Aeonix Administration Manual

Figure 10-22 VOIP
Gateway Page - TGW PRI
Defined

Configuring Tadiran TGW Gateways

10

Aeonix Administration Manual Managing VOIP Gateways 10-61

NOTES:
 Chapter 11

Managing Aliases

11.1 Aliases (“Phone Extensions”) .............................................11-1

11.2 Assigning Aliases................................................................11-5

Aeonix Administration Manual

 11.1 Aliases (“Phone Extensions”)

Aliases resemble internal phone extensions; however, they are associated with a
specific Aeonix user or trunk group rather than with a particular device or wall outlet.
Aliases are also assigned to certain services, such as call groups, ACD groups,
conference call servers, mobility services, and voicemail servers.

Aliases function for trunk groups just as for users.

When an internal call is received at any of the user’s aliases, the user’s phone or
phones will ring. You cannot assign the same alias to more than one user. However,
you can define many aliases per user.
The following alias types exist in Aeonix:
 Complete number—the exact number or extension assigned to a user.
 Range—a range of numbers assigned to a user. Any dialed number that falls
into this range is routed to its associated user.
 Prefix—a prefix assigned to a user. Any time a number starting with the prefix
is dialed, the user identified with that prefix receives the call.
When a number is dialed, the Aeonix system first searches for a matching complete
alias number. If no complete number is available, the system checks whether the dialed
number falls into one of the assigned alias ranges. If not, the system checks whether
the dialed number can be associated with a defined prefix.
When a call is placed to a prefix alias number, the system automatically removes the
Aliases (“Phone Extensions”)
prefix digit or digits.
11

Aeonix Administration Manual Managing Aliases 11-1

  Alias Lists Page

To open the Alias Lists page:

1 On the navigation pane, click Administration. The pane displays the
Administration menus.
2 Select the Aliases menu, and then click Aliases.

Figure 11-1 Alias Lists

Page—Complete Tab

The Alias Lists page displays the alias numbers assigned to users. It is divided into
Aliases (“Phone Extensions”)

tabs as follows:
 Click the Complete tab (see Figure 11-1 above) to view a list of assigned
complete alias numbers.
11

11-2 Managing Aliases Aeonix Administration Manual

 This tab displays up to 10 rows by default. To change the number of rows
displayed, enter the number in the Rows per page field and click Set.

 Click the Range tab (see Figure 11-2) to display a list of assigned alias
number ranges.
 Click the Prefix tab (see Figure 11-3) to view a list of assigned prefix aliases.

Figure 11-2 Alias Lists

Page—Range Tab

Figure 11-3 Alias Lists

Page—Prefix Tab

Each alias list is sorted by its first column. If the list includes more than one
page, use the page navigation bar (see Table 6-1) at the bottom of the list to
navigate between the pages.

The list displays the following information for an alias:

Aliases (“Phone Extensions”)

11

Aeonix Administration Manual Managing Aliases 11-3

 Table 11-1 Alias List
Parameters Field Is Displayed Description
under Tab

Alias Complete Complete alias number

Start of range Range Lower limit of alias range

End of range Range Upper limit of alias range

Prefix Prefix Prefix assigned to a user

Length Prefix Amount of digits, including the prefix number

digits that can be dialed to reach the user,
trunk group, or service associated with this
alias

User Complete, User, trunk group, or service with which the

Range, Prefix alias number is associated.
Click the entity to view or modify its details
(see Defining a User, page 6-9 and Defining a Trunk
Group, page 9-5).

CUG Complete, Closed User Group to which the entity

Range, Prefix belongs (see Closed User Groups (CUG), page 4-29)
Aliases (“Phone Extensions”)
11

11-4 Managing Aliases Aeonix Administration Manual

 11.2 Assigning Aliases

Aliases are assigned, updated, or deleted in the following places:

 For users, through the Identity & Aliases tab on the User page (see Assigning
Aliases to Users, page 6-19)
 For trunk groups, through the Alias tab on the Trunk Group page (see Assigning
Aliases to Trunk Groups, page 9-10)
 For ACD groups, on the ACD Group page (see Defining ACD Groups, page 12-5)
 For call groups, on the Call Group page (see Defining Call Groups, page 12-59)
 For meet-me conferences, on the Meet-Me Conference Configuration page
(see Defining Meet-Me Conference Aliases, page 12-79)
 For mobility services, on the Mobility Alias page (see Defining Mobility Aliases,
page 12-89)
 For park/pickup numbers, on the Page Queue Park/Pickup page (see Defining
Alias Numbers for Page Queue Park/Pickup, page 12-118)
 For voicemail servers, on the SIP Voicemail page (see Configuring Voicemail,
page 12-137)

Assigning Aliases
11

Aeonix Administration Manual Managing Aliases 11-5

NOTES:
 Chapter 12

Configuring Services

12.1 Services ..............................................................................12-1

12.2 Defining ACD Groups .........................................................12-5
12.2 Configuring the Aeonix Contact Center ............................12-17
12.4 Configuring Call Recording...............................................12-23
12.5 Configuring the Hospitality Service...................................12-39
12.6 Defining Hunt Groups .......................................................12-45
12.7 Defining Call Groups.........................................................12-59
12.8 Defining Conference Calls ................................................12-63
12.9 Defining Emergency Conference Calls.............................12-71
12.10 Defining Meet-Me Conference Aliases.............................12-79
12.11 Defining Mobility Aliases..................................................12-89
12.12 Configuring Call Detail Records (CDR) ............................12-97
12.13 Computer Telephony Integration (CTI) .............................12-99
12.14 Directory .........................................................................12-101
12.15 Defining Dispatch Consoles ...........................................12-103
12.16 Configuring the E911 Database Connector....................12-109
12.17 Configuring the Music Service........................................ 12-111
12.18 Configuring Page Queue Park/Pickup............................12-117

Aeonix Administration Manual

 12.19 Configuring PnP / Provisioning Service..........................12-123
12.19 Importing Audio Files......................................................12-133
12.21 Configuring Voicemail.....................................................12-137
12.22 Defining Virtual Endpoints ..............................................12-149
12.23 Defining Zone Page Calls...............................................12-159
12

12-0 Configuring Services Aeonix Administration Manual

 12.1 Services

Aeonix services are centralized applications that provide the basis for Aeonix features
and capabilities. For a description of the telephony features that Aeonix supports,
see Chapter 2, Aeonix Features.
Some services relate to specialized groups to which members are assigned. Other
services are used for specifying connection parameters and access numbers to servers
supporting a certain feature.

Services
12

Aeonix Administration Manual Configuring Services 12-1

 Configure Aeonix services as described in the following sections:
 Defining ACD Groups, page 12-5
 Configuring the Aeonix Contact Center, page 12-17
 Configuring Call Recording, page 12-23
 Configuring the Hospitality Service, page 12-39
 Defining Hunt Groups, page 12-45
 Defining Call Groups, page 12-59
 Defining Conference Calls, page 12-63
 Defining Meet-Me Conference Aliases, page 12-79
 Defining Mobility Aliases, page 12-89
 Configuring Call Detail Records (CDR), page 12-97
 Computer Telephony Integration (CTI), page 12-99
 Directory, page 12-101
 Defining Dispatch Consoles, page 12-103
 Configuring the E911 Database Connector, page 12-109
 Defining Emergency Conference Calls, page 12-71
 Configuring the Music Service, page 12-111
 Configuring Page Queue Park/Pickup, page 12-117
 Configuring PnP / Provisioning Service, page 12-123
 Importing Audio Files, page 12-133
 Configuring Voicemail, page 12-137
 Defining Virtual Endpoints, page 12-149
 Defining Zone Page Calls, page 12-159
Services are configured from the Service List page.

To open this page:

1 On the navigation pane, click Administration. The pane displays the
Administration menus.
2 Select the Services menu, and then click Service List.
Services

The Service List page displays the configurable services (see Figure 12-1),
as well as a short description of each service.
12

Click Help to obtain more information about services.

12-2 Configuring Services Aeonix Administration Manual

Figure 12-1 Service List
Page

Services
12

Aeonix Administration Manual Configuring Services 12-3

Services
12

12-4 Configuring Services Aeonix Administration Manual

 12.2 Defining ACD Groups

Automatic Call Distribution (ACD) groups are managed from the ACD Group List Page.

Tips:
To learn more about the ACD feature, see Automatic Call Distribution (ACD) and
Hunt Groups, page 2-9.

Managing ACD groups includes the following procedures:

 Defining an ACD Group, page 12-8.
 Setting Codecs for ACD & Hunt Announcers, page 12-16

For a description of Automatic Call Distribution and related features,

see Automatic Call Distribution (ACD) and Hunt Groups, page 2-9.

Defining ACD Groups

12

Aeonix Administration Manual Configuring Services 12-5

  ACD Group List Page

The ACD Group List page displays the ACD groups defined in the system sorted by
alias number. To open this page, click ACD in the table on the Service List page
(see Figure 12-1).

Figure 12-2 ACD Group

List Page

The ACD group list is sorted by the Alias column. If the list includes more
than one page, use the page navigation bar (see Table 6-1) at the bottom of
the list to navigate between the pages.

For each ACD group, the list displays the following information.

Table 12-1 ACD Group

List Parameters Field Description

Alias The alias number assigned to the ACD group

Description An optional description of the ACD group

Call Distribution The call distribution method (Terminal, Circular, or Longest

Method Time in Idle)
Defining ACD Groups
12

12-6 Configuring Services Aeonix Administration Manual

 From this page, you can perform the following actions:

Table 12-2 Actions

Performed from the ACD Action Button / Icon Description
Group List Page
Add ACD group Click Add to add a new ACD group
(see Defining an ACD Group, page 12-8).

Update ACD group In the list, click the ACD group alias to update
—
the details of this ACD group.
Delete ACD group Select the check box next to the ACD group or
groups to be deleted and then click Delete
(see Deleting Entities, page 3-66).
Access online help Click Help to receive online help.

Define announcer ACD & Hunt On the Services menu in the navigation pane,
codecs Codecs (menu click this link to define codecs for ACD
option) announcers (see Setting Codecs for ACD & Hunt
Announcers, page 12-16).

Defining ACD Groups

12

Aeonix Administration Manual Configuring Services 12-7

  Defining an ACD Group

To create or update an ACD group:

1 On the ACD Group List page (see Figure 12-2), click Add to create a new
ACD group, or select an existing ACD group from the list to update it. The
ACD Group page is displayed.

Figure 12-3 ACD Group

Page for a New ACD
Group

2 Enter a free alias number in the Alias text box. This number is the internal call
number of the ACD group.

The alias number must consist of at least three digits and cannot be modified
for an existing ACD group. You can click the Suggest Available Aliases
Defining ACD Groups

button to view a list of available aliases and alias ranges.

3 In the Description text box, enter a short description of the ACD group
(optional).

4 From the Group tab, the Unassigned box below the tab displays the ID values
of all users and groups belonging to the selected Closed User Group
12

(see Closed User Groups (CUG), page 4-29).

12-8 Configuring Services Aeonix Administration Manual

 ACD features are only available on supported phones.

To view the members of a group, select the group from the list and click View
Group. A tree of the users and sub-groups belonging to the group is
displayed at the bottom of the page.

5 To add a user or group to the ACD group, select it in the Unassigned box and
click (the right arrow). The selected item is moved to the Assigned box and
added to the list of items to be included in the ACD group.
Repeat this step to add other users or groups.

Below the box, you can use the (right arrow) to display the next items or
the Search box to search for and display specific items in the list.

To delete an item from the ACD group, remove it from the Assigned box by

selecting it there and clicking (the left double-arrow). You can add or
remove multiple users and groups by holding down the CTRL or SHIFT key
while selecting them.

6 To sort a user or group, select it from the Assigned box and use (the Up
and Down arrows) to move the item to the required position.
Repeat this step to sort other users or groups.
7 Select one of the following Call Distribution Method options:
 Terminal—the system selects the first user that becomes available
according to the order in the Assigned box. This is the default selection.
 Circular—the system selects the next agent after the last one to have Defining ACD Groups
answered.
 Longest time in idle—the system selects the agent that has been idle the
longest in the campaign.

Non-ACD calls are not part of the idle time calculation.

12

Aeonix Administration Manual Configuring Services 12-9

 8 Click the Announcers tab. This tab contains the music file configuration
parameters for defining the music and messages to be played to callers.

Figure 12-4 Announcers

Tab for ACD Groups

The following Music File Configuration announcers are available:

Table 12-3 ACD Music

File Configuration Field Description
Parameters
Mandatory The audio file containing an announcement played to
announcement file callers on each call to the ACD group. When selected,
all incoming callers to an ACD group hear this
introductory announcement in its entirety usually
explaining about the company, product, or campaign.

First The audio file containing an announcement played to

announcement file callers when their call is put on a waiting queue. If
selected, callers hear this announcement once usually
informing them that their call has been placed in queue.
This announcement is cut short once an agent becomes
available to attend to the caller.

Periodic The audio file containing an announcement played

announcement file periodically to callers while they are waiting on the line.
If selected, these announcers are played intermittently
between background music according to the set interval
(see Hunt Interval and Timeout Parameters, page 12-57) until the
ACD call is answered.
Defining ACD Groups

Music The source of the music played to callers between the

announcements while the callers are waiting on the line

9 Clear the check box next to the relevant announcement file to prevent it from
being played to callers.
10 For each music file configuration field, click Edit. The corresponding dialog
12

box is displayed for specifying the location of the music or announcement file.

12-10 Configuring Services Aeonix Administration Manual

Figure 12-5 Dialog Box
for First Announcement
File (Example)

11 For the required codec, select the name of the audio file to be played.

Tips:
To learn how to add additional audio files, see Importing Audio Files, page 12-133.

When you select an audio file, Aeonix will first attempt to play the
corresponding file in the language specified in the user profile (see General
Information Parameters, page 5-10). If such a language does not exist, the default
file will be played instead.

Ensure that:
 The default audio files are located on the Aeonix server in:
/home/aeonixadmin/aeonix/resources/audio
 In the audio folder there are sub-directories per language named
according to ISO-639 conventions (for example, zh for Chinese)
Defining ACD Groups
 The file names in the language sub-directories are identical to the file
names in the parent directory
 There is a file for each codec type (G.711Alaw, G.711µlaw, and G.729)
 In cluster environments, the files are stored on all of the Aeonix servers

12 Click OK. The dialog box is closed.

12

13 Click the Overflow tab. The tab displays the possible overflow situations.

Aeonix Administration Manual Configuring Services 12-11

 Figure 12-6 Overflow Tab
for ACD Groups

The table below describes the displayed overflow options.

Table 12-4 ACD Overflow

Options Option Description

No agent is logged in No user (call center agent) is logged in.

All agents are released Agents are logged in but all of them are temporarily
released, therefore none is available for calls.

No agent answers No user answers the call.

Maximum queue The maximum number of callers allowed in the

capacity has been waiting list has been exceeded. This option defines
reached what happens with the additional callers.

Waiting in queue time The caller has not been answered for longer than
expiration the Waiting in queue timeout threshold.

14 For each overflow option, you can define what happens if the overflow
threshold has been exceeded. Click Edit to the right of the appropriate option.
Defining ACD Groups

The Overflow dialog box is displayed.

For the first three overflow options, the default is Put in queue; for the last
two overflow options, the default is Disconnect.
12

12-12 Configuring Services Aeonix Administration Manual

Figure 12-7 Overflow
Dialog Box

15 Select one of the following options:

 Disconnect—the call is disconnected, and the caller receives a busy tone.
This is the default selection.
 Reject —the call is rejected with busy reason, and no announcer is played.

This option is only available for the Maximum queue capacity has been
reached overflow option.

 Put in queue—the caller remains in the waiting list even after the threshold
has been reached.
 Redirect to—the caller is forwarded to a specified user or external number.
Select the user or enter the external number as required.
16 Click OK. The dialog box is closed.
17 Click the Parameters tab. The tab displays the interval and timeout
parameters and is used for defining thresholds.

Defining ACD Groups

12

Aeonix Administration Manual Configuring Services 12-13

 Figure 12-8 Parameters
Tab for ACD Group

The Server configuration options are displayed in cluster environments only.

18 If Default Server is selected, the service uses the server as defined in the
cluster configuration (see Setting Server for ACD and Hunt Services, page 14-43);
otherwise, to assign a specific server in an Aeonix cluster instead, select the
server on which the ACD service runs from the Handled by drop-down list
and then, from the adjacent drop-down list, select the back up server.
19 Define the interval and timeout fields according to the following table.

Table 12-5 ACD Interval

and Timeout Parameters Field Default Description

Maximum queue 20 The maximum number of callers that can

capacity be put on hold in the waiting queue

Periodic 60 The number of seconds after which the

announcement periodic announcement is repeated for a
interval caller put on hold
Defining ACD Groups

Waiting in queue 200 The number of seconds during which a

time caller stays in the waiting queue
12

12-14 Configuring Services Aeonix Administration Manual

 Field Default Description

Wrap-up time 20 The number of seconds the user (call

center agent) is granted after finishing a
call before receiving another call

Ring agent time 20 The maximum number of seconds an

ACD call can ring at an agent’s
extension, after which the agent is put
on Auto Release and the call is diverted
to the next available agent

20 Click Save. The ACD group is included in the list of the ACD Group List
page.

Defining ACD Groups

12

Aeonix Administration Manual Configuring Services 12-15

  Setting Codecs for ACD & Hunt Announcers

Aeonix supports G.711 a-law, G.711 µ-law, and G.729 codec type files for all ACD and
Hunt announcers.

To set codecs for ACD and Hunt announcers:

1 While on the ACD Group List page (see Figure 12-2) or the Hunt Group List
page (see Figure 12-28), click ACD & Hunt Codecs from the Services menu
on the navigation pane. The Codecs page is displayed.

Figure 12-9 Codecs Page

for ACD and Hunt
Announcers

2 The Supported box displays the codecs defined in the system. To disassociate
a codec from ACD and Hunt announcers, select the codec and click (the
left arrow). The selected item is moved to the Not Supported box.
Repeat this step to add other codecs to the Not Supported box.

You can add or remove multiple codecs by holding down the CTRL or SHIFT
key while selecting them.
Defining ACD Groups

3 Use (the Up and Down arrows) to define the order of the codecs in the
Supported box. The system negotiates the best codec match for incoming
ACD and Hunt calls according to the order of the codecs listed in the box.
4 For ACD and Hunt calls announcers for phones that are not set to SIP INFO
mode, select the Support RFC 2833 check box.
5 Click Save.
12

12-16 Configuring Services Aeonix Administration Manual

 12.3 Configuring the Aeonix Contact Center

The Aeonix Contact Center service enables the management of Aeonix Contact
Center aliases (IRN) numbers, which determine the routing of incoming Aeonix
Contact Center calls.
In addition, the Aeonix Contact Center service can be used to configure Call failover
options for each alias, which determines how Aeonix Contact Center calls are handled
in the event that the Aeonix Contact Center is down or experiencing an overload.

Refer to the Aeonix Contact Center Administration Guide for information

about defining the required parameters on the Aeonix Contact Center side.

The Aeonix Contact Center is managed from the Aeonix Contact Center Service List Page.
Managing Aeonix Contact Center aliases is described in Defining Aeonix Contact Center
Aliases and Call Failover Options, page 12-20.

Configuring the Aeonix Contact Center

12

Aeonix Administration Manual Configuring Services 12-17

  Aeonix Contact Center Service List Page

The Aeonix Contact Center Service List page displays the Aeonix Contact Center IRN
alias numbers) defined in the system. To open this page, click Aeonix Contact Center
in the table on the Service List page (see Figure 12-1).

Figure 12-10 Aeonix

Contact Center Service
List Page

The list is sorted by the Alias / IRN column. If the list includes more than one
page, use the page navigation bar (see Table 6-1) at the bottom of the list to
navigate between the pages.

The list displays the following information.

Table 12-6 Aeonix

Contact Center Service Field Description
List Parameters
Alias / IRN The Aeonix Contact Center alias (IRN) number

Description An optional description of the Aeonix Contact Center alias

Call Failover Details of the call Aeonix Contact Center alias failover policy
Configuring the Aeonix Contact Center
12

12-18 Configuring Services Aeonix Administration Manual

 From this page, you can perform the following actions:

Table 12-7 Actions

Performed from the Action Button Description
Aeonix Contact Center
Service List Page Add Aeonix Click Add to add a new Aeonix Contact Center
Contact Center alias (see Defining Aeonix Contact Center Aliases and
alias Call Failover Options, page 12-20).
Update Aeonix In the list, click the alias to update the details of
Contact Center — this configuration.
alias
Delete Aeonix Select the check box next to the alias or
Contact Center aliases to be deleted and then click Delete
alias (see Deleting Entities, page 3-66).
Access online help Click Help to receive online help.

Search for an Click to display the Search area, define search

Aeonix Contact values, and then click Apply to search for a
Center alias specific alias.
Click Reset to remove entered values from the
search configuration fields and display the full
list.

Configuring the Aeonix Contact Center

12

Aeonix Administration Manual Configuring Services 12-19

  Defining Aeonix Contact Center Aliases and Call Failover Options

To add or update an Aeonix Contact Center alias:

1 On the Aeonix Contact Center Service List page (see Figure 12-10), do one of
the following:
 To define a new Aeonix Contact Center alias, click Add.
 To update an existing Aeonix Contact Center alias, select it from the list.
The Aeonix Contact Center Alias (IRN) Configuration page is displayed.

Figure 12-11
Des

Configuration Page for a

New Aeonix Contact
Center Alias
Configuring the Aeonix Contact Center

2 In the Description text box, enter a short description of the Aeonix Contact
Center alias (optional).
3 To associate a user profile (including location and routing rules settings) with
outgoing external calls, enter the required profile in the For outgoing external
calls, use profile of text box.
12

12-20 Configuring Services Aeonix Administration Manual

 4 Select the alias type (usually Complete) and define the alias as follows:

Type Description

Complete Use to define a specific alias number.

 Enter the number in the Alias text box.

NOTE: You can click Suggest Available Aliases to view a list of

available aliases and alias ranges.

NOTE: The alias number must consist of at least three digits.

Range Use to define a range of numbers used to reach the Aeonix Contact
Center.
 Enter the lowest number of the range in the Start of range box.
 Enter the highest number of the range in the End of range box.

The type of an existing alias cannot be modified.

Aeonix searches for an alias number in the following order:

 It tries to find a number matching a complete alias.
 If no match is found, the system checks if the number falls into a defined alias
range.
 If still no match is found, the system checks whether the number has a prefix
that matches one of the defined alias prefixes.
5 Specify the Call failover threshold for incoming calls that are not handled
within a predefined time (default: 20 seconds), and then select one of the
following overflow options:
 Disconnect with busy reason—the call is disconnected, and the caller

Configuring the Aeonix Contact Center

receives a busy reason for the disconnection. This is the default selection.
 Disconnect—the call is disconnected.
 Redirect to—the call is forwarded to a specified user, or internal / external
number. Select the user or enter the number as required.
6 To play an audio file before the selected overflow action, select the check box
below the options, and then click Edit to specify the file name for the required
codec. A dialog box is displayed for specifying the location of the audio file.
12

Aeonix Administration Manual Configuring Services 12-21

 Figure 12-12 Play Audio
Des

File Dialog Box

7 Define the audio sources for the required codec types (see Table 4-14 on
page 4-34), and, if you selected File, select the required audio file from the
adjacent drop-down list.

Tips:
To learn how to add additional audio files, see Importing Audio Files, page 12-133.

8 Click OK. The dialog box is closed.

Configuring the Aeonix Contact Center

9 Click Save. The Aeonix Contact Center alias is included in the Aeonix Contact
Center Service List page.
12

12-22 Configuring Services Aeonix Administration Manual

 12.4 Configuring Call Recording

The Call Recording service is used to configure selective recording rules and for
associating recording servers with recording centers.

Tips:
To learn more about call recording, see Aeonix Logger (Call Recording), page 2-6.

Call Recording settings are managed from the Call Recording List Page. Managing the
Call Recording service includes the following procedures:
 Defining a Call Recording Rule, page 12-28
 Defining a Recording Server, page 12-32

Configuring Call Recording

12

Aeonix Administration Manual Configuring Services 12-23

  Call Recording List Page

The Call Recording page displays the recording rules and centers defined in the
system. To open this page, click Call Recording in the table on the Service List page
(see Figure 12-1).

Figure 12-13 Call

Recording List Page

The Selective Recording tab of the Call Recording page contains an area (click Search
to display this area) in which search criteria can be defined to find and display specific
rules.
This tab can be sorted by any column. Select the required column from the Sort by
drop-down list. Once selected, you can toggle the sort order of the column items by
Configuring Call Recording

clicking the Reverse button.

The Call Recording list is sorted by the Name column. If the list includes
more than one page, use the page navigation bar (see Table 6-1) at the
bottom of the list to navigate between the pages.
12

12-24 Configuring Services Aeonix Administration Manual

 For each call recording rule, the list displays the following information.

Table 12-8 Call Recording

Parameters Field Description

Name The name of the recording rule

Entity Type The entity type of the recording target: User, Phone, Trunk
Group, Trunk, ULA, ACC Agent, and All (for when no specific
entity was defined for the rule)

Entity ID The entity ID of the inbound / outbound call to be recorded

Caller ID The caller ID or caller ID range of the inbound / outbound call

to be recorded

DNIS The DNIS or DNIS range of the inbound / outbound call to be

recorded

On Days The day of the week to perform the recording

From Time The time of the day to start the recording

To Time The time of the day to end the recording

Time Zone The time zone of the recording

NOTE: By default, the time zone of the Aeonix server.

Sticky A check mark indicates that the recording mode is ‘sticky’.

Active A check mark indicates that the rule is activated.

NOTE: You can select or clear the relevant check box as

required.

From this page, you can perform the following actions:

Configuring Call Recording

12

Aeonix Administration Manual Configuring Services 12-25

 Table 12-9 Actions
Performed from the Action Button / Icon Description
Recording Rules Page
Add recording rule Click Add to add and set up a new recording
rule (see Defining a Call Recording Rule, page 12-28).

Update recording In the list, click the name of the recording rule
rule — to update the details of this recording rule
configuration.
Delete recording Select the check box next to the recording rule
rule or rules to be deleted and then click Delete
(see Deleting Entities, page 3-66).
Access online help Click Help to receive online help.

Clone recording Click this icon to duplicate the details of a

rule specific recording rule configuration to a new
recording rule.
Search for Click to display the Search area, define search
recording rules values, and then click Apply to search for
existing rules (see Searching for Call Recording
Rules, page 12-27).
Click Reset to remove entered values from the
search configuration fields. This allows you to
define and start a new search.
Configuring Call Recording
12

12-26 Configuring Services Aeonix Administration Manual

 Searching for Call Recording Rules
In the Search area at the top of the selective recording list, you can search for specific
call recording rules using the following search criteria:

Search Criteria Search Results

Name Rules that contain the specified text in their Name field

Entity ID Rules that contain the specified text in their Entity ID field

Caller ID Rules that contain the specified text in their Caller ID field

DNIS Rules that contain the specified text in their DNIS field

Entity Type Rules that contain the specified Entity Type

NOTE: All searches for rules for which no specific entity was
defined.

Click the Search bar to display the search fields and fill in one or more fields as
required. When you start filling in the Name, Entity ID, Caller ID, or DNIS all
existing entities containing the entered value are displayed below the field. Select the
required value (if available) or type it in. Or select the required Entity Type.

Figure 12-14 Call

Recording Rules Search

Click Apply to filter the display by the entered criteria. The Call Recording Rules List
will include all the rules that have values corresponding to the search values or
containing them in the relevant fields. Example: If you enter 00 in the DNIS field and Configuring Call Recording
click Apply, rules for recording outbound international calls are displayed.
12

Aeonix Administration Manual Configuring Services 12-27

  Defining a Call Recording Rule

You can define up to 1000 call recording rules in the system.

To add or update a call recording rule:

1 On the Selective Recording List tab (see Figure 12-13), do one of the
following:
 To define a call recording rule, click Add.
 To update an existing call recording rule, select it from the list.
 To define a new call recording rule based on the settings of an existing one,
click (the Clone icon) to the right of the relevant rule.

When you clone a call recording rule, all parameter values are copied to the
new rule except for the rule name.

The New Recording Rule page is displayed.

Figure 12-15 New

Recording Rule
(Selective Recording Tab)
Configuring Call Recording

2 Enter the name of the call recording rule in the Name box.
3 In the Description text box, enter a short description of the call recording rule
12

(optional).

12-28 Configuring Services Aeonix Administration Manual

 4 To limit the rule to calls to/from specific entities, select the Record calls on...
check box. The entities that can be applied to this rule are displayed in the
adjacent drop-down list.

If you do not select on, all the entities are automatically selected, indicating
that call inbound / outbound calls will be recorded.

5 Select the required entity.

Figure 12-16 Entity Types

6 You can define entities in the following ways:

If you do not define details of a specific entity, all the entities of this type are
automatically selected.

Entity Options Description

User / ULA /  Number: Enter the internal alias number of the user, ULA
Aeonix Contact or Aeonix Contact Center agent or Conference Call. See
Center agent / also Table 12-10, Wildcards.
Conference Call
NOTE: When you start filling in the number, all existing aliases
containing the entered value are displayed below the
Number field.

Configuring Call Recording

NOTE: The call will be recorded even when the Aeonix
Contact Center agent is logged out of the Aeonix
Contact Center group.
 Range:
Start of range: Enter the lowest number in the range
End of range: Enter the highest number in the range. For
example, if you want to define aliases 2000 to 2010, enter
2000 in the Start of range box and 2010 in the End of
range box.
12

Phone In the adjacent box, enter the phone ID.

Aeonix Administration Manual Configuring Services 12-29

 Entity Options Description

Trunk group In the adjacent box, enter the trunk group ID.

Trunk In the adjacent box, enter the SIP trunk ID.

7 To set the rule to continuously record calls until they are terminated (even if
the call is transferred), select continuously (sticky recording mode).

If this check box is not selected, the recording rule is re-evaluated after each
call event (transfer, hold, etc.) and if the recording entity is still part of the
call, the recording continues.

8 To include a time frame for the rule, select at a time frame as the following.

Figure 12-17 Time Frame

Options

9 Select the relevant options in the following table.

Entity Options Description

Every day Clear this check box, and then select one or more weekdays
(default: selected) to include these days in the time frame.

NOTE: If you do not clear this check box, all the days of the
week are automatically selected.

All day (default: Clear this check box, and then specify the hour in the Start
selected) time and the End time drop-down lists.

NOTE: If you do not clear this check box, all the hours of the
day are automatically selected.
Configuring Call Recording

Time zone Select this check box, and then specify the relevant time
(default: cleared) zone from the drop-down list.

NOTE: If you do not select this check box, the time zone
defined in Aeonix is automatically selected.

10 To include a caller ID for the rule, select and the caller ID is the following.
12

12-30 Configuring Services Aeonix Administration Manual

Figure 12-18 Caller ID
Options

11 Select the relevant options in the following table.

Caller ID Options Description

 Number: Enter the caller ID (ANI number) of the inbound /

outbound call to be recorded. See also Table 12-10,
Wildcards.
 Range:
Start of range: Enter the lowest number in the range
End of range: Enter the highest number in the range

12 To include a DNIS number for the rule, select and DNIS is the following.

Figure 12-19 DNIS

Options

13 Select the relevant options in the following table.

DNIS Options Description

 Number: Enter the DNIS number of the inbound /

outbound call to be recorded. See also Table 12-10,
Wildcards.
 Range:
Start of range: Enter the lowest number in the range
End of range: Enter the highest number in the range

Configuring Call Recording

14 When entering caller ID, DNIS, ACC Agent, user, or ULA numbers, the
following wildcards can be used:

Table 12-10 Wildcards

Sign Mnemonic Example

x or X Matches any single 73xx matches

digit from 0-9 numbers 7300 to 7399
12

Aeonix Administration Manual Configuring Services 12-31

 Sign Mnemonic Example

! (exclamation Matches zero or more 74! matches any

mark) characters pattern that starts with
74, including 74

15 By default, the rule is set to be active. If you want to temporarily disable the
rule, clear the Activate the rule check box.
16 Click OK at the bottom of the page. The rule is added to the Selective
Recording list.
17 Click Save.

To delete a call recording rule:

1 On the Selective Recording List tab (see Figure 12-13), select the relevant rule
or rules from the list.
2 Click Delete. A confirmation message is displayed.
3 Click Yes. The rule is removed from the list.
4 Click Save.

 Defining a Recording Server

To associate a recording server with a recording center:

1 Click the Recording Centers tab.

Figure 12-20 Recording

Centers Tab
Configuring Call Recording

The recording centers tab list is sorted by the Recording Center column. If
12

the list includes more than one page, use the page navigation bar (see Table
6-1) at the bottom of the list to navigate between the pages.

12-32 Configuring Services Aeonix Administration Manual

 For each recording center, the list displays the following information.

Table 12-11 Recording

Centers List Parameters Field Description

Status icon A circle icon to the left of each recording center indicates the
(circle) following:
 Green - a recording server is defined for the recording
center
 Red - no recording server is defined for the recording
center

NOTE: View the specific icon’s tooltip for more information.

Recording Center The name of the recording center

NOTE: Only centers with physical Aeonix servers are

displayed.

Aeonix Server The name of the Aeonix server

Call Recording Centers are derived from Aeonix locations that have an
Aeonix server and as such cannot be added, removed, or modified.

2 Click the relevant Recording Center from the list.

Figure 12-21 Associating

Recording Servers with
Recording Centers

Configuring Call Recording

12

3 Click Add or Update to add a new or update an existing recording server.

Aeonix Administration Manual Configuring Services 12-33

 The Aeonix Logger trunk must be defined to register on Aeonix and have the
same user name and password as the corresponding SIP register username
and password as in the Aeonix Logger. Refer to the Aeonix Logger
Installation and Configuration Guide for information about defining the
corresponding parameters on the Aeonix Logger side via the CSTA&SIP
Server Config page.

Figure 12-22 Recording

Server Parameters

4 In the Name text box, enter the name of the recording server.
5 In the Address text box, enter the IP address, host name, or DNS name of the
SIP server on which the call recordings register.

It is recommended to use the DNS name option for redundancy purposes.

6 Click OK.

Repeat steps 3 to 6 as required to add other recording servers.

7 Click OK at the bottom of the page.

8 Click Save at the bottom of the Call Recording page.
Configuring Call Recording

When adding a recording server for the first time, the system automatically
generates the AeonixLoggerTKGrp trunk group with which all recording
servers are associated. This trunk group cannot be deleted.
12

12-34 Configuring Services Aeonix Administration Manual

  Record on Demand (RoD) Using SeaMail

Aeonix can be configured to use the SeaMail product as a call recording center. In
some cases it may required to provide Record On Demand capability for Aeonix
without the need to deploy an additional server. This can be the case in an Aeonix
system deployed to a small- to mid-sized business. In this solution the recordings are
stored in the user's mailbox, and can be retrieved by either listening to them via the
phone or by sending them to the user's email address as an attachment.
Recording with SeaMail is initiated by the user on demand (RoD). The user initiates
the recording by activating the RoD feature during or before the call.

Limitations:
 Recording by Rules - Not Supported
 Total recording - Not Supported
 Keep Control - Not Supported
 Sticky Recording - Not Supported

Recorder Configuration
When RoD is activated the Aeonix selects the recoding target based on the following
logic.
If an Aeonix Logger Server is Configured (at least 1 server is defined):
Use the Aeonix logger for recording.
Else if no Aeonix Logger Server is configured:
If the user that pressed RoD has SeaMail voicemail configured:
Use the VM configured for the user for recording.
Else no SeaMail voicemail is configured for the user that pressed RoD
Do not record.
Configuring Call Recording

Aeonix Logger and SeaMail recording cannot be mixed on the same system.
12

Aeonix Administration Manual Configuring Services 12-35

 Record on Demand Process with SeaMail
 Activation and indications on the phones are the same as when using Aeonix
Logger as the recording center.
 RoD is supported by all Aeonix phones.
 The RoD feature can be activated using either a programmed DSS key or
dialing the feature code + activation code
 Only desk phones (with DSS keys) can activate ROD during the call.
 Default feature code for "Record on Demand" is 1443 (same as coral).
 Activation requires the Activation code . Ex. 144311
 Deactivation requires deactivation code. Ex. 144310
 RoD can be activated from Idle, Idle + Holding, or during the call.
 RoD is a toggle feature and can be turned on and off during the call
 Phones can activate recording only for themselves (1st party)

Persistency
 ROD feature is activated for one call only. If activated before the call it would
record the next call. If activated during the call it would record the current call.
 Persistent Recording (of all calls) requires activation of a recording rule and
cannot be activated via the phone.

Permission
 RoD can be activated by any phone (no control by the phone profile)

Stickiness
 Recording is not sticky and terminates in case of transfer
 Recording resumes (new record) after hold/resume
Configuring Call Recording

Desktop Application
 RoD can be activated from desktop Applications like ACC Agent, A-Touch or
ADC.
 ROD can be activated by either party of the call or both parties, however the
Aeonix initiates only one recording session with the Seamail for the call. The
Seamail needs to attach the recording to the mailbox of the party that is
indicated as 'internal' by the Aeonix. If both parties are 'internal' the SeaMail
12

needs to replicate the recording and store in both parties mailboxes.

12-36 Configuring Services Aeonix Administration Manual

 Notifications and Indications
 Indications on phones and displays are the same as when using Aeonix Logger
as the recording center.
 Aeonix can inject a periodic beep tone during the call. The beep tone is
recorded by the seamail as part of the call.
 If MBX is defined as UM, The Seamail will send an email to the user mailbox
with the following information.
 Subject - Call Recording from xxxx to yyyy at hh:mm:ss
 Where
 xxxx is the caller id
 yyyy - is the called id
 hh:mm:ss - is the start time of the recording
 If no MBX is associated with the call the recording is not stored.
 The MWI indication on phones is the same as for any new voicemail message.
 In case a Recording license is used the message is not sent to the mailbox /
email and can be seen on the GUI by the administrator.

Aeonix GUI
In the Aeonix Selective Recording page a warning can be displayed:
"Selective recording requires that at least one Aeonix logger server would be
registered with the Aeonix in order to function"

Configuring Call Recording

12

Aeonix Administration Manual Configuring Services 12-37

NOTES:
 12.5 Configuring the Hospitality Service

Hospitality services are managed from the Hospitality List Page.

Tips:
To learn more about Hospitality features, see Hospitality, page 2-25.

Managing Hospitality services includes the following procedure:

 Defining a Hospitality Service, page 12-41.

In addition to the license requirement, SeaMail must be installed on the

system for the Hospitality Service to function.

Configuring the Hospitality Service

12

Aeonix Administration Manual Configuring Services 12-39

  Hospitality List Page

The Hospitality List page displays the Hospitality services defined in the system
sorted by facility name. To open this page, click Hospitality in the table on the Service
List page (see Figure 12-1).

Figure 12-23 Hospitality

List Page

The Hospitality list is sorted by the Facility name column. If the list includes
more than one page, use the page navigation bar (see Table 6-1) at the
bottom of the list to navigate between the pages.

For each Hospitality service, the list displays the following information.

Table 12-12 Hospitality

List Parameters Field Description

Facility Name The name of the facility

Description An optional description of the facility

Closed User The Closed User Group associated with the facility (see
Group Closed User Groups (CUG), page 4-29).

From this page, you can perform the following actions:

Configuring the Hospitality Service

Table 12-13 Actions

Performed from the Action Button Description
Hospitality List Page
Add Hospitality Click Add to add a new Hospitality service
service (see Defining a Hospitality Service, page 12-41).

Update Hospitality In the list, click the Hospitality service to update

—
service its the details.
Delete Hospitality Select the check box next to the Hospitality
service service or services to be deleted and then click
Delete (see Deleting Entities, page 3-66).
12

12-40 Configuring Services Aeonix Administration Manual

 Action Button Description
Access online help Click Help to receive online help.

 Defining a Hospitality Service

To create or update a Hospitality service:

1 On the Hospitality List page (see Figure 12-23), click Add to create a new
Hospitality service, or select an existing Hospitality service from the list to
update it. The Hospitality page is displayed.

Figure 12-24 Hospitality

for a New Hospitality
Service

Configuring the Hospitality Service

2 Enter the name of the facility in the Facility name text box.
3 In the Description text box, enter a short description of the facility (optional).
4 From the Configuration tab, set the Wakeup Definition parameters as
described in the following table:
12

Aeonix Administration Manual Configuring Services 12-41

 Table 12-14 Wakeup
Definitions Parameters Variable Description

Number of snoozes Defines the maximum number of Wakeup call attempts to

perform when the destination “snoozes” or does not
answer.

Snooze every Defines the time interval between “snooze” or

disconnection and the next Wakeup call attempt.

Ring duration Defines the duration of each Wakeup call attempt.

Automatically When a Wakeup call attempt is made to a destination that

disconnect the call does not hang up, the number of seconds after which the
after system force releases (disconnects) the destination. At the
end of this period, another Wakeup call is attempted.

5 Select Require confirmation on wakeup to force a disconnection (for

example, when the guest dials ‘5’).
6 Click the Announcers tab. These audio files contain the announcements that
can be played to callers during their Wakeup call.

Figure 12-25 Announcers

Tab for Wakeup Calls
Configuring the Hospitality Service

7 For the required codec, select the name of the audio file to be played.

Tips:
12

To learn how to add additional audio files, see Importing Audio Files, page 12-133.

12-42 Configuring Services Aeonix Administration Manual

 When you select an audio file, Aeonix will first attempt to play the
corresponding file in the language specified in the user profile (see General
Information Parameters, page 5-10). If such a language does not exist, the default
file will be played instead.

Ensure that:
 The default audio files are located on the Aeonix server in:
/home/aeonixadmin/aeonix/resources/audio
 In the audio folder there are sub-directories per language named
according to ISO-639 conventions (for example, zh for Chinese)
 The file names in the language sub-directories are identical to the file
names in the parent directory
 There is a file for each codec type (G.711Alaw, G.711µlaw, and G.729)
 In cluster environments, the files are stored on all of the Aeonix servers

8 Click the Room Status tab.

Figure 12-26 Room

Status Tab

9 Enter the name of the room status in the corresponding field. Configuring the Hospitality Service

10 Click the Permissions tab.

12

Aeonix Administration Manual Configuring Services 12-43

 Figure 12-27 Permissions
Tab for Hospitality
Service

11 Define up to four guest call levels for this facility by associating the required
toll barrier with the corresponding hospitality permission number.

Upon check out, Aeonix sets the permission level to 1 by default.

To learn more about defining this type of sub-profile, see Toll Barrier Sub-profiles,
page 5-24.

For example, you can associate toll barriers that restrict guests to only dial internal,
local, regional, or national calls. Default Toll Barrier is the default setting.
12 Click Save. The Hospitality service is included in the list of the Hospitality
List page.
Configuring the Hospitality Service
12

12-44 Configuring Services Aeonix Administration Manual

 12.6 Defining Hunt Groups

Hunt groups are managed from the Hunt Group List Page.

Tips:
To learn more about Hunt groups, see Automatic Call Distribution (ACD) and Hunt
Groups, page 2-9.

Managing Hunt groups includes the following procedures:

 Defining a Hunt Group, page 12-48.
 Setting Codecs for ACD & Hunt Announcers, page 12-16

For a description of Hunt group and related features, see Automatic Call
Distribution (ACD) and Hunt Groups, page 2-9.

Defining Hunt Groups

12

Aeonix Administration Manual Configuring Services 12-45

  Hunt Group List Page

The Hunt Group List page displays the Hunt groups defined in the system sorted by
alias number. To open this page, click Hunt in the table on the Service List page
(see Figure 12-1).

Figure 12-28 Hunt Group

List Page

The Hunt group list is sorted by the Alias column. If the list includes more
than one page, use the page navigation bar (see Table 6-1) at the bottom of
the list to navigate between the pages.

For each Hunt group, the list displays the following information.

Table 12-15 Hunt Group

List Parameters Field Description

Alias The alias number assigned to the Hunt group

Description An optional description of the Hunt group

Call Distribution The call distribution method (Terminal or Circular)

Method

Presentation The in-band DTMF presentation format (None, [DNIS]*[ANI]*,

Format [ANI]*[DNIS]*, or Other)
Defining Hunt Groups
12

12-46 Configuring Services Aeonix Administration Manual

 From this page, you can perform the following actions:

Table 12-16 Actions

Performed from the ACD Action Button / Icon Description
Group List Page
Add Hunt group Click Add to add a new Hunt group
(see Defining a Hunt Group, page 12-48).

Update Hunt group In the list, click the Hunt group alias to update
—
the details of this Hunt group.
Delete Hunt group Select the check box next to the Hunt group or
groups to be deleted and then click Delete
(see Deleting Entities, page 3-66).
Access online help Click Help to receive online help.

Define announcer ACD & Hunt On the Services menu in the navigation pane,
codecs Codecs (menu click this link to define codecs for Hunt
option) announcers (see Setting Codecs for ACD & Hunt
Announcers, page 12-16).

Defining Hunt Groups

12

Aeonix Administration Manual Configuring Services 12-47

  Defining a Hunt Group

To create or update a Hunt group:

1 On the Hunt Group List page (see Figure 12-28), click Add to create a new
Hunt group, or select an existing Hunt group from the list to update it. The
Hunt Group page is displayed.

Figure 12-29 Hunt Group

Page for a New Hunt
Group

2 Enter an available alias number in the Alias text box. This number is the
internal call number of the Hunt group.

The alias number must consist of at least three digits and cannot be modified
Defining Hunt Groups

for an existing Hunt group. You can click the Suggest Available Aliases
button to view a list of available aliases and alias ranges.

3 In the Description text box, enter a short description of the Hunt group
(optional).

4 From the General tab, select one of the following Presentation format of
playing DTMF to agent options:
12

12-48 Configuring Services Aeonix Administration Manual

  None—the system does not send the DTMF presentation. This is the default
selection.
 [DNIS]*[ANI]*—The system uses the DNIS of the incoming call as the
DTMF presentation, followed by an asterisk ('*'), followed by the ANI of
the incoming call, followed by a final asterisk ('*').
Example:
If the DNIS of the incoming call is 1111 and the ANI is 2222, the
presentation string will be 1111*2222*
 [ANI]*[DNIS]*—The system uses the ANI of the incoming call as the
DTMF presentation, followed by an asterisk ('*'), followed by the DNIS of
the incoming call, followed by a final asterisk ('*')
Example:
If the DNIS of the incoming call is 1111 and the ANI is 2222 than the
presentation string will be 2222*1111*
 Other—enter the relevant digit string in the Format field that is displayed.

You can use any combination of digits (0-9), asterisks ('*'), and pound ('#')
signs, and any combination of the following variables, which can be used a
multiple of times.

Table 12-17 DTMF

Playback Variables Variable Description

[ANI] [ANI] will be replaced with the ANI of the incoming call

[DNIS] [DNIS] will be replaced with the DNIS of the incoming

call

[N:<num digits>] A running counter (where <num digits> designates the

counter’s maximum length) can be used to identify the
call instead of the ANI. The counter does not start from
zero, the start number is random. Defining Hunt Groups

Examples:
[N:7] can produce a counter result that can contain a
minimum of one digit and a maximum of 7 digits.
[N:0] can produce a counter with unlimited digits (use if
you do not want counters to be repeated)
[N:07] will always produce a counter with seven digits
12

Aeonix Administration Manual Configuring Services 12-49

 Variable Description

[P:<wait time ms>] When dialing the number, a pause can be used to insert a
delay during the digit string transmission.

NOTE: The maximum pause time is 10000ms. Use

additional pause variables if more time is required.
Example: [P:200] will produce a pause of 200ms.

5 In the DTMF digit duration text box, enter the Digit On period (50-500ms),
as generated by the gateway. (The default value is 70.)
6 Select one of the following Replace incoming call ANI options:
 Never—the system does not change the ANI of the incoming call. This is
the default selection.
 Always—the system always changes the ANI of the incoming call
according to the digits specified in the Format field that is displayed,
which determines the ANI replacement format.
 If empty—if the incoming call has no ANI, the system uses the digits
specified in the Format field that is displayed, which determines the ANI
replacement format.

You can use any combination of digits (0-9), asterisks ('*'), and pound ('#')
signs, and any combination of the following variables, which can be used a
multiple of times).

Table 12-18 ANI

Replacement Variables Variable Description

[ANI] [ANI] will be replaced with the ANI of the incoming call

[DNIS] [DNIS] will be replaced with the DNIS of the incoming

call
Defining Hunt Groups
12

12-50 Configuring Services Aeonix Administration Manual

 Variable Description

[N:<num digits>] A running counter (where <num digits> designates the

counter’s maximum length) can be used to identify the
call.
Examples:
[N:7] can produce a counter result that can contain a
minimum of one digit and a maximum of 7 digits.
[N:0] can produce a counter with unlimited digits (use if
you do not want counters to be repeated)
[N:07] will always produce a counter with seven digits

7 From the Group tab, the Unassigned box below the tab displays the ID values
of all users and groups belonging to the selected Closed User Group
(see Closed User Groups (CUG), page 4-29).

Below the box, you can use the (right arrow) to display the next items or
the Search box to search for and display specific items in the list.

Figure 12-30 Group Tab

for Hunt Group

Defining Hunt Groups

12

Aeonix Administration Manual Configuring Services 12-51

 Hunt features are only available on supported phones.

To view the members of a group, select the group from the list and click View
Group. A tree of the users and sub-groups belonging to the group is
displayed at the bottom of the page.

8 To add a user or group to the Hunt group, select it in the Unassigned box and
click (the right arrow). (You can use the Search box for this purpose.) The
selected item is moved to the Assigned box and added to the list of items to be
included in the Hunt group.
Repeat this step to add other users or groups.

To delete an item from the Hunt group, remove it from the Assigned box by

selecting it there and clicking (the left double-arrow). You can add or
remove multiple users and groups by holding down the CTRL or SHIFT key
while selecting them.

9 To sort a user or group, select it from the Assigned box and use (the Up
and Down arrows) to move the item to the required position.
Repeat this step to sort other users or groups.
10 Select one of the following Call Distribution Method options:
 Terminal—the system selects the first user that becomes available
according to the order in the Assigned box. This is the default selection.
 Circular—the system selects the next agent after the last one to have
answered.
11 Click the Announcers tab. This tab contains the music file configuration
parameters for defining the music and messages to be played to callers.
Defining Hunt Groups
12

12-52 Configuring Services Aeonix Administration Manual

Figure 12-31 Announcers
Tab for Hunt Groups

The following Music File Configuration announcers are available:

Table 12-19 Hunt Music

File Configuration Field Description
Parameters
Enable audio When selected, allows you to activate announcers and
playback music.

NOTE: If not selected, the caller will hear a ring back tone
until an agent becomes available.

Mandatory The audio file containing an announcement played to

announcement file callers on each call to the Hunt group. When selected,
all incoming callers to a Hunt group hear this
introductory announcement in its entirety usually
explaining about the company, product, or campaign.

First The audio file containing an announcement played to

announcement file callers when their call is put on a waiting queue. If
selected, callers hear this announcement once usually
informing them that their call has been placed in queue.
This announcement is cut short once an agent becomes
available to attend to the caller.
Defining Hunt Groups
Periodic The audio file containing an announcement played
announcement file periodically to callers while they are waiting on the line.
If selected, these announcers are played intermittently
between background music according to the set interval
(see Periodic announcement file, page 12-53) until the Hunt
call is answered.

Music The source of the music played to callers between the

12

announcements while the callers are waiting on the line.

Aeonix Administration Manual Configuring Services 12-53

 12 Select the Enable audio playback check box. The music file configuration
check boxes are enabled. Do one of the following:
 Clear the check box next to the relevant announcement file (except Music)
to prevent it from being played to callers.
 Click Edit next to the relevant announcement file. A dialog box is
displayed for specifying the location of the music or announcement file.

Figure 12-32 Dialog Box

for First Announcement
File

Aeonix supports G.711 a-law, G.711 µ-law, and G.729 codec type files for all
Hunt announcers. To learn how to set codecs for Hunt announcers, see
Figure Setting Codecs for ACD & Hunt Announcers, page 12-16.

13 For the required codec, select the name of the audio file to be played.

Tips:
To learn how to add additional audio files, see Importing Audio Files, page 12-133.

When you select an audio file, Aeonix will first attempt to play the
Defining Hunt Groups

corresponding file in the language specified in the user profile (see General
Information Parameters, page 5-10). If such a language does not exist, the default
file will be played instead.

Ensure that:
12

 The default audio files are located on the Aeonix server in:
/home/aeonixadmin/aeonix/resources/audio

12-54 Configuring Services Aeonix Administration Manual

  In the audio folder there are sub-directories per language named
according to ISO-639 conventions (for example, zh for Chinese)
 The file names in the language sub-directories are identical to the file
names in the parent directory
 There is a file for each codec type (G.711Alaw, G.711µlaw, and G.729)
 In cluster environments, the files are stored on all of the Aeonix servers.

14 Click OK. The dialog box is closed.

15 Click the Overflow tab. The tab displays the possible overflow situations.

Figure 12-33 Overflow

Tab for Hunt Groups

The table below describes the displayed overflow options.

Table 12-20 Hunt

Overflow Options Field Description

No agent is logged No user (call center agent) is logged in.

in

No agent answers No user answers the call.

Maximum queue The maximum number of callers allowed in the waiting

capacity has been list has been exceeded. This option defines what
reached happens with the additional callers.

Waiting in queue The caller has not been answered for longer than the
time expiration Waiting in queue timeout threshold.

16 For each overflow option, you can define what happens if the overflow Defining Hunt Groups
threshold has been exceeded. Click Edit to the right of the appropriate option.
The Overflow dialog box is displayed.

For the first three overflow options, the default is Put in queue; for the last
two overflow options, the default is Disconnect.
12

Aeonix Administration Manual Configuring Services 12-55

 Figure 12-34 Overflow
Dialog Box

17 Select one of the following options:

 Disconnect—the call is disconnected, and the caller receives a busy tone.
This is the default selection.
 Reject —the call is rejected with busy reason, and no announcer is played.

This option is only available for the Maximum queue capacity has been
reached overflow option.

 Put in queue—the caller remains in the waiting list even after the threshold
has been reached.
 Redirect to—the caller is forwarded to a specified user or external number.
Select the user or enter the external number as required.
18 Click the Parameters tab. The tab displays the interval and timeout
parameters and is used for defining thresholds.
Defining Hunt Groups
12

12-56 Configuring Services Aeonix Administration Manual

Figure 12-35 Parameters
Tab for Hunt Group

The Server configuration options are displayed in cluster environments only.

19 If Default Server is selected, the service uses the server as defined in the
cluster configuration (see Setting Server for ACD and Hunt Services, page 14-43);
otherwise, to assign a specific server in an Aeonix cluster instead, select the
server on which the Hunt service runs from the Handled by drop-down list
and then, from the adjacent drop-down list, select the back up server.
20 Define the interval and timeout fields according to the following table.

Table 12-21 Hunt Interval

and Timeout Parameters Field Default Description

Maximum 20 The maximum number of callers that can

queue be put on hold in the waiting queue
capacity

Periodic 60 The number of seconds after which the

announcem periodic announcement is repeated for a
ent interval caller put on hold
Defining Hunt Groups

Waiting in 200 The number of seconds during which a

queue time caller stays in the waiting queue
12

Aeonix Administration Manual Configuring Services 12-57

 Field Default Description

Wrap-up 20 The number of seconds the user (call

time center agent) is granted after finishing a call
before receiving another call

Ring agent 20 The maximum number of seconds a Hunt

time call can ring at an agent’s extension, after
which the agent is put on Auto Release and
the call is diverted to the next available
agent

21 Click Save. The Hunt group is included in the list of the Hunt Group List
page.
Defining Hunt Groups
12

12-58 Configuring Services Aeonix Administration Manual

 12.7 Defining Call Groups

A call group includes several users and/or user groups under a dedicated alias number.
When this number is called, the phones of all members belonging to the call group ring
until one of them answers the call.
Call groups are managed from the Call Group List Page. Managing call groups is
described in Defining a Call Group, page 12-61.

Defining Call Groups

12

Aeonix Administration Manual Configuring Services 12-59

  Call Group List Page

The Call Group List page displays the call groups defined in the system sorted by alias
number. To open this page, click Call Group in the table on the Service List page
(see Figure 12-1).

Figure 12-36 Call Group

List Page

The call group list is sorted by the Alias column. If the list includes more than
one page, use the page navigation bar (see Table 6-1) at the bottom of the
list to navigate between the pages.

For each call group, the list displays the following information.

Table 12-22 Call Group

List Parameters Field Description

Alias The alias number assigned to the call group

From this page, you can perform the following actions:

Table 12-23 Actions

Performed from the Call Action Button Description
Group List Page
Add call group Click Add to add a new call group (see Defining
a Call Group, page 12-61).

Update call group In the list, click the call group alias to update
—
the details of this call group.
Delete call group Select the check box next to the call group or
groups to be deleted and then click Delete
Defining Call Groups

(see Deleting Entities, page 3-66).

Access online help Click Help to receive online help.
12

12-60 Configuring Services Aeonix Administration Manual

  Defining a Call Group

To create or update a call group:

1 On the Call Group List page (see Figure 12-36), click Add to create a new call
group, or select a call group from the list to update it. The Call Group page is
displayed.

Figure 12-37 Call Group

Page for a New Call
Group

2 Enter a free alias number in the Alias text box. This number is the internal call
number of the call group.

The alias number must consist of at least three digits and cannot be modified
for an existing call group. You can click the Suggest Available Aliases
button to view a list of available aliases and alias ranges.

3 The Unassigned box below the Alias field displays the ID values of all users
and groups belonging to the selected Closed User Group (see Closed User
Defining Call Groups

Groups (CUG), page 4-29).

To view the members of a group, select the group from the list and click View
Group. A tree of the users and sub-groups belonging to the group is
displayed at the bottom of the page.
12

Aeonix Administration Manual Configuring Services 12-61

 To add a user or group to the call group, select it in the Unassigned box and
click (the right arrow). (You can use the Search box for this purpose.) The
selected item is moved to the Assigned box and added to the list of items to be
included in the call group.
Repeat this step to add other users or groups.

To delete an item from the call group, remove it from the Assigned box by

selecting it there and clicking (the left arrow). You can add or remove
multiple users and groups by holding down the CTRL or SHIFT key while
selecting them.

4 Click Save. The call group is included in the list of the Call Group List page.
Defining Call Groups
12

12-62 Configuring Services Aeonix Administration Manual

 12.8 Defining Conference Calls

Conference calls include several users and/or user groups under dedicated alias
numbers. These alias numbers function as virtual conference rooms. When an initiator
dials a conference call number, all the members join the conference call. Authorized
users can also join an existing conference call. The system can be configured to notify
participants of the incoming conference call. Up to 125 members can participate in a
conference call.

Tips:
To learn more about conference calls, see Conference Calling, page 2-17.

Conference calls are managed from the Conference Call List Page.
Managing conference calls is described in Defining Conference Call Alias Numbers,
page 12-65.

Defining Conference Calls

12

Aeonix Administration Manual Configuring Services 12-63

  Conference Call List Page

The Conference Call List page displays the conference call alias numbers defined in
the system. To open this page, click Conference Call in the table on the Service List
page (see Figure 12-1).

Figure 12-38 Conference

Call List Page

The conference call list is sorted by the Alias column. If the list includes more
than one page, use the page navigation bar (see Table 6-1) at the bottom of
the list to navigate between the pages.

For each conference call configuration, the list displays the following information.

Table 12-24 Conference

Call List Parameters Field Description

Alias The alias number assigned to the conference call

Description An optional description of the conference call

From this page, you can perform the following actions:

Table 12-25 Actions

Performed from the Action Button Description
Conference Call List
Page Add conference Click Add to add a new conference call alias
call alias (see Defining Conference Call Alias Numbers,
page 12-65).
Defining Conference Calls

Update conference In the list, click the alias to update the details of
—
call alias this conference call configuration.
Delete conference Select the check box next to the alias or
call alias aliases to be deleted and then click Delete
(see Deleting Entities, page 3-66).
Access online help Click Help to receive online help.
12

12-64 Configuring Services Aeonix Administration Manual

  Defining Conference Call Alias Numbers

To add or update a conference call alias:

1 On the Conference Call List page (see Figure 12-38), do one of the following:
 To define a new conference call alias, click Add.
 To update an existing conference call alias, select it from the list.
The Conference Call Configuration page is displayed.

Figure 12-39 Conference

Call Page for a New
Conference Call

2 Enter the conference call number in the Alias text box. This number is
internally dialed to initiate or join the conference call.

The alias number must consist of at least three digits and cannot be modified
for an existing conference call. You can click the Suggest Available Aliases
button to view a list of available aliases and alias ranges. Defining Conference Calls

3 In the Description text box, enter a short description of the conference call
(optional).
4 Specify the Call Preemption priority and behavior to be used on conference
call members when this conference call alias is dialed. For example, from the
Priority drop-down list, select High and then, from the Action drop-down list,
12

select Call Waiting. For more information, see Call Preemption, page 2-13.

Aeonix Administration Manual Configuring Services 12-65

 The Action drop-down list is only available when Medium, High, or Urgent is
selected from the Priority drop-down list.

5 Specify the required General conference call parameters by selecting from the
following options:
 Participants will automatically join the conference––to activate the
speaker or headset of all members when an incoming conference call is
received.

Auto Answer can only be used on supporting phones.

 Participants joining the conference will be muted––to turn off the

microphone of all members when the conference call starts. During the
conference itself, conference managers can mute/unmute specific members
(see Programmable Button Dial Functions, page 5-60).

Muted participants can press 0 on supporting phones to request to speak.

 Terminate the conference when the initiator disconnects––to disconnect

all members when the initiator disconnects.
6 Select one of the following to define who can initiate conference calls:
 Managers only—only managers can initiate conference calls.
 Managers and members—managers and members can initiate conference
calls. This is the default selection.
 Everyone—any user can initiate conference calls.
7 Select one of the following to define who can add participants to conference
calls:
Defining Conference Calls

 Managers only—only managers can add participants to conference calls.

 Managers and members—managers and members can add participants to
conference calls. This is the default selection.
 Everyone—any system user can add participants to conference calls.
8 Click the Group tab to define the managers and members of the conference
call.
12

12-66 Configuring Services Aeonix Administration Manual

Figure 12-40 Group Tab
for Conference Calls

9 The Unassigned box displays the ID values of all system users and groups that
are not assigned to the conference as members (upper list) or managers (lower
list).

Below the boxes, you can use the (right arrow) to display the next items
or the Search box to search for and display specific items in the list.

To view the members of a group, select the group from the list and click View
Group. A tree of the users and sub-groups belonging to the group is
displayed at the bottom of the page. Defining Conference Calls

To add a user or group to the conference call as a member or manager, select it

in the relevant Unassigned box and click (the right arrow). (You can use
the Search box for this purpose.) The selected item is moved to the Assigned
box and added to the list of items to be included in the conference call.
Repeat this step to add other users or groups as members or managers of the
12

conference call.

Aeonix Administration Manual Configuring Services 12-67

 To delete a member or manager, remove it from the relevant Assigned box

by selecting it there and clicking (the left arrow). You can add or remove
multiple users and groups by holding down the CTRL or SHIFT key while
selecting them.

10 Use the External Members box (middle list) to define external users as a
conference members.

Because it cannot be known in advance if the initiator of the Conference Call

will have “dial out without ‘9’ access code” configured or not, you must
specify External Member numbers with the ‘9’ prefix explicitly included in the
External Members box.

Add new, update, or remove external users as required:

 To add an external user, click Add, enter the phone number in the adjacent
box, and click OK.
 To update an external user, select the user and click Update. Modify the
number that is displayed in the adjacent box, and click OK.
 To delete an external user, select the user and click Delete. You can select
more than one user for deletion by using the CTRL and SHIFT keys.
11 Click the Announcers tab.

Figure 12-41 Announcers

Tab for Conference Calls
Defining Conference Calls

The following Audio File Configuration announcers are available:

12

12-68 Configuring Services Aeonix Administration Manual

Table 12-26 Conference
Call Audio File Field Description
Configuration Parameters
Conference entry The audio file containing the start notification tone or
tone file announcement to be played to the connecting
participants while the Conference Call is being initiated.

NOTE: This check box is selected by default.

First The audio file containing the subsequent optional

announcement file announcement to be played to the conference
participants after the conference entry tone. If selected,
participants hear this announcement once.

12 For each audio file configuration field, click Edit. The corresponding dialog
box is displayed for specifying the location of the announcement file.

Figure 12-42 Dialog Box

for Conference Entry
Tone Announcement File
(Example)

Defining Conference Calls

13 Define the audio sources for the required codec types (see Table 4-14 on
page 4-34), and, if you selected File, select the required audio file from the
adjacent drop-down list.
12

Aeonix Administration Manual Configuring Services 12-69

 Tips:
To learn how to add additional audio files, see Importing Audio Files, page 12-133.

14 Click OK. The dialog box is closed.

15 Click Save. The conference call is included in the list of the Conference Call
List page.
Defining Conference Calls
12

12-70 Configuring Services Aeonix Administration Manual

 12.9 Defining Emergency Conference Calls

Emergency Conference calls include several users and/or user groups under dedicated
alias numbers. These alias numbers function as virtual conference rooms. When an
initiator dials a conference call number, all the members join the conference call.
Authorized users can also join an existing conference call. The system can be
configured to notify participants of the incoming conference call. Up to 125 members
can participate in a conference call.
Emergency Conference Service implements a special Conference Call template,
which has the following specific aspects:
 Emergency Conference Call supports the Tadiran Panic Button SIP device.
 An Emergency Conference is initiated when a SIP endpoint dials the alias of
an Emergency Conference.
 The Emergency Conference displays the name of the endpoint caller. A name
can be associated with the Tadiran Panic Button device, so that conference
members receiving an invite to join can see who/what initiated the Emergency
Conference.
 The Emergency Conference call is created from a pool of aliases. If no alias is
available, the Emergency Conference call will be created without an alias, so
that emergency calls will always be supported.
 Unlike the normal Conference Call, there is no Announcers Tab for setting up
announcers. An emergency call should not be cluttered with announcer

Defining Emergency Conference Calls

prompts.

Tips:
To learn more about Emergency Conference Calls, see Emergency Conference
Calling, page 2-20.

Emergency Conference calls are managed from the Emergency Conference Call List
Page.
Managing conference calls is described in Defining Emergency Conference Call Alias
12

Numbers, page 12-73.

Aeonix Administration Manual Configuring Services 12-71

  Emergency Conference Call List Page

The Emergency Conference Call List page displays the conference call alias numbers
defined in the system. To open this page, click Emergency Conference Call in the
table on the Service List page (see Figure 12-1).

Figure 12-43 Emergency

Conference Call List
Page

The Emergency Conference Call list is sorted by the Alias column. If the list
includes more than one page, use the page navigation bar (see Table 6-1) at
the bottom of the list to navigate between the pages.

For each conference call configuration, the list displays the following information.

Table 12-27 Emergency

Conference Call List Field Description
Parameters
Alias The alias number assigned to the conference call

Description An optional description of the conference call

From this page, you can perform the following actions:

Table 12-28 Actions

Defining Emergency Conference Calls

Performed from the Action Button Description

Emergency Conference
Call List Page Add conference Click Add to add a new conference call alias
call alias (see Defining Emergency Conference Call Alias
Numbers, page 12-73).
Update conference In the list, click the alias to update the details of
—
call alias this conference call configuration.
Delete conference Select the check box next to the alias or
call alias aliases to be deleted and then click Delete
(see Deleting Entities, page 3-66).
Access online help Click Help to receive online help.
12

12-72 Configuring Services Aeonix Administration Manual

  Defining Emergency Conference Call Alias Numbers

To add or update a conference call alias:

1 On the Emergency Conference Call List page (see Figure 12-43), do one of the
following:
 To define a new conference call alias, click Add.
 To update an existing conference call alias, select it from the list.
The Conference Call Configuration page is displayed.

Figure 12-44 New

Emergency Conference
Call Page

2 Enter the conference call number in the Alias text box. This number is

Defining Emergency Conference Calls

internally dialed to initiate or join the conference call.

The alias number must consist of at least three digits and cannot be modified
for an existing conference call. You can click the Suggest Available Aliases
button to view a list of available aliases and alias ranges.

3 In the Description text box, enter a short description of the conference call
(optional).
12

Aeonix Administration Manual Configuring Services 12-73

 4 Specify the Call Preemption priority and behavior to be used on conference
call members when this conference call alias is dialed. For example, from the
Priority drop-down list, select High and then, from the Action drop-down list,
select Call Waiting. For more information, see Call Preemption, page 2-13.

The Action drop-down list is only available when Medium, High, or Urgent is
selected from the Priority drop-down list.

5 Specify the required General conference call parameters by selecting from the
following options:
 Participants will automatically join the conference––to activate the
speaker or headset of all members when an incoming conference call is
received.

Auto Answer can only be used on supporting phones.

 Participants joining the conference will be muted––to turn off the

microphone of all members when the conference call starts. During the
conference itself, conference managers can mute/unmute specific members
(see Programmable Button Dial Functions, page 5-60).

Muted participants can press 0 on supporting phones to request to speak.

 Terminate the conference when the initiator disconnects––to disconnect

all members when the initiator disconnects.
6 Select one of the following to define who can initiate conference calls:
Defining Emergency Conference Calls

 Managers only—only managers can initiate conference calls.

 Managers and members—managers and members can initiate conference
calls. This is the default selection.
 Everyone—any user can initiate conference calls.
7 Select one of the following to define who can add participants to conference
calls:
 Managers only—only managers can add participants to conference calls.
 Managers and members—managers and members can add participants to
12

conference calls. This is the default selection.

12-74 Configuring Services Aeonix Administration Manual

  Everyone—any system user can add participants to conference calls.
8 Click the Group tab to define the managers and members of the conference
call.

Figure 12-45 Group Tab

for Emergency
Conference Calls

9 The Unassigned box displays the ID values of all system users and groups that
are not assigned to the conference as members (upper list) or managers (lower
list).

Below the boxes, you can use the (right arrow) to display the next items
or the Search box to search for and display specific items in the list.

To view the members of a group, select the group from the list and click View Defining Emergency Conference Calls
Group. A tree of the users and sub-groups belonging to the group is
displayed at the bottom of the page.

To add a user or group to the conference call as a member or manager, select it

in the relevant Unassigned box and click (the right arrow). (You can use
the Search box for this purpose.) The selected item is moved to the Assigned
box and added to the list of items to be included in the conference call.
12

Aeonix Administration Manual Configuring Services 12-75

 Repeat this step to add other users or groups as members or managers of the
conference call.

To delete a member or manager, remove it from the relevant Assigned box

by selecting it there and clicking (the left arrow). You can add or remove
multiple users and groups by holding down the CTRL or SHIFT key while
selecting them.

10 Use the External Members box (middle list) to define external users as a
conference members.

Because it cannot be known in advance if the initiator of the Conference Call

will have “dial out without ‘9’ access code” configured or not, you must
specify External Member numbers with the ‘9’ prefix explicitly included in the
External Members box.

Add new, update, or remove external users as required:

 To add an external user, click Add, enter the phone number in the adjacent
box, and click OK.
 To update an external user, select the user and click Update. Modify the
number that is displayed in the adjacent box, and click OK.
 To delete an external user, select the user and click Delete. You can select
more than one user for deletion by using the CTRL and SHIFT keys.
11 Click OK. The dialog box is closed.
12 Click Save. The conference call is included in the list of the Conference Call
List page.
Defining Emergency Conference Calls

13 If support for PSAP emergency call back is required, in Aeonix System

Parameters set the checkbox for Enable Emergency Callback Feature as
shown in the following figure.
12

12-76 Configuring Services Aeonix Administration Manual

Figure 12-46 Enable
Emergency Callback

Defining Emergency Conference Calls

12

Aeonix Administration Manual Configuring Services 12-77

NOTES:
 12.10 Defining Meet-Me Conference Aliases

Aeonix supports meet-me and 3-way conference calling. The access to a call
conference can be password-controlled. For information about conference calls and
directions for use, see Conference Calling, page 2-17.
Meet-me conference calling requires dedicated alias numbers for conference calls.
These alias numbers function as virtual conference rooms.

Tips:
To learn more about conference calls, see Conference Calling, page 2-17.

Alias numbers, as well as meet-me conference security parameters and settings, are
managed from the Meet Me Conference Configuration List Page.
Configuring a meet-me conference alias includes the following procedures:
 Defining Default Values for Meet-me Conference Security Settings, page 12-82
 Defining Meet-me Conference Alias Numbers, page 12-86

Defining Meet-Me Conference Aliases

12

Aeonix Administration Manual Configuring Services 12-79

  Meet Me Conference Configuration List Page

The Meet Me Configuration List page displays meet-me conference alias numbers
defined in the system. To open this page, click Meet-Me Conference in the table on
the Service List page (see Figure 12-1).

Figure 12-47 Meet Me

Configuration List Page

The meet-me configuration list is sorted by the Alias column. If the list
includes more than one page, use the page navigation bar (see Table 6-1) at
the bottom of the list to navigate between the pages.

For each meet-me configuration, the list displays the following information.

Table 12-29 Meet Me

Configuration List Field Description
Parameters
Alias An alias number dedicated for meet-me conference calls

Secured Setting that indicates whether the meet-me conferences

made through this alias number are password-protected
Defining Meet-Me Conference Aliases
12

12-80 Configuring Services Aeonix Administration Manual

 From this page, you can perform the following actions:

Table 12-30 Actions

Performed from the Meet Action Button / Icon Description
Me Configuration List
Page Add meet-me Click Add to add a new meet-me conference
conference alias alias (see Defining Meet-me Conference Alias
Numbers, page 12-86).
Update meet-me In the list, click the alias to update the details
—
conference alias of this meet-me configuration.
Delete meet-me Select the check box next to the alias or
conference alias aliases to be deleted and then click Delete
(see Deleting Entities, page 3-66).
Access online help Click Help to receive online help.

Clone meet-me Click this icon to copy the details of a specific

conference alias meet-me configuration to a new meet-me
conference alias.
Manage meet-me View Default On the Services menu in the navigation pane,
default values (menu option) click this link to view or monitor the meet-me
configuration default values.

Defining Meet-Me Conference Aliases

12

Aeonix Administration Manual Configuring Services 12-81

  Defining Default Values for Meet-me Conference Security Settings

The Default meet-me configuration includes the default values for meet-me security
parameters. Except for announcements, these values can be overridden for the specific
meet-me alias numbers (see Defining Meet-me Conference Alias Numbers, page 12-86).

To define default security parameters for meet-me conferences:

1 Select the Services menu, and then click Service List.
2 On the Service List page (see Figure 12-1), click Meet-Me Conference. The
Meet Me Configuration List page is displayed.
3 In the navigation pane, select View Default from the Services menu. The
Default Meet-Me Configuration page is displayed.

Figure 12-48 Default

Meet-Me Configuration
Page
Defining Meet-Me Conference Aliases

4 Set default values for the fields described in the following table.

Table 12-31 Meet-me

Enter

Parameters Field Description

Maximum number of The maximum number of failed access attempts

attempts before the user is disconnected
12

12-82 Configuring Services Aeonix Administration Manual

 Field Description

Access code The digit the user enters after entering the access
termination digits code. You can define more than one digit (no need
to separate them with commas).
NOTE: If the user does not enter a termination digit
after the access code, the system waits until
the Access code timeout (see below) before it
checks the code.

Access code timeout The time within which the user must enter an access
code

Enter password Voice announcement prompting the user to enter the

access code

Wrong password Announcement informing the user that the entered

access code is wrong. The user is prompted to
re-enter the access code.

Maximum number of Announcement informing that the number of times

attempts exceeded the user failed to access the conference has
exceeded the threshold defined in the Maximum
attempts field above. The user is disconnected after
this announcement.

Transferring to Announcement received after successful access.

conference After this announcement, the user is connected to the
conference.

Conference not Announcement informing the user that connecting to

available the conference failed although the correct access
code was entered

5 If necessary, define default announcement files for the meet-me

Defining Meet-Me Conference Aliases

announcements by clicking Edit next to the relevant announcement. The
Announcer Details dialog box is displayed.

12

Aeonix Administration Manual Configuring Services 12-83

 Figure 12-49 Announcer
Details Dialog Box

6 Define the audio sources for the required codec types (see Table 4-14 on
page 4-34).

Tips:
To learn how to add additional audio files, see Importing Audio Files, page 12-133.

When you select an audio file, Aeonix will first attempt to play the
corresponding file in the language specified in the user profile (see General
Information Parameters, page 5-10). If such a language does not exist, the default
file will be played instead.
Defining Meet-Me Conference Aliases

Ensure that:
 The default audio files are located on the Aeonix server in:
/home/aeonixadmin/aeonix/resources/audio
 In the audio folder there are sub-directories per language named
according to ISO-639 conventions (for example, zh for Chinese)
 The file names in the language sub-directories are identical to the file
names in the parent directory
 There is a file for each codec type (G.711Alaw, G.711µlaw, and G.729)
12

 In cluster environments, the files are stored on all of the Aeonix servers

12-84 Configuring Services Aeonix Administration Manual

 7 Click OK.
8 On the Default Meet Me Configuration page, click Save to save the settings
and return to the Meet-Me List page.

Defining Meet-Me Conference Aliases

12

Aeonix Administration Manual Configuring Services 12-85

  Defining Meet-me Conference Alias Numbers

To add or update a meet-me conference alias:

1 On the Meet Me Configuration List page (see Figure 12-47), do one of the
following:
 To define a new meet-me conference alias, click Add.
 To update an existing meet-me conference alias, select it from the list.
 To define a new meet-me conference alias based on the settings of an
existing one, click (the Clone icon) to the right of the relevant alias.

When you clone a meet-me configuration alias, all parameter values are
copied to the new alias except for the meet-me conference number.

The Meet Me Conference Configuration page is displayed.

Figure 12-50 Meet Me

Conference Configuration
Page for a New Alias
Defining Meet-Me Conference Aliases

2 Enter the meet-me conference number in the Alias field. This number is
internally dialed to reach the meet-me conference.
12

12-86 Configuring Services Aeonix Administration Manual

 Make sure that the alias includes at least three digits, is not already in use,
and complies with the alias patterns of the applicable dial plan (see Dial Plans,
page 4-19). You can click the Suggest Available Aliases button to view a list
of available aliases and alias ranges.

3 Select the Server on which the meet-me conference application runs.

4 In the Access code field, enter the code (password) that must be dialed to join
a meet-me conference call.

If the Access code field is left blank, the placed meet me conference calls
are not password-secured, and the meet-me configuration parameters are
not relevant (except for the Transferring to conference and Conference
not available announcements).

5 In the Owner field, enter any character of the relevant user’s first name, last
name, or login name and select the user from the list displayed below the field.
A conference owner can modify the access code (see above) and control other
participants in a conference call. The same user can be owner of several
meet-me conference aliases.
6 To define or modify a meet-me configuration parameter, select the Override
check box next to the relevant field and enter the required value. (The
parameters are described in Table 12-31 on page 12-82.)

If a field’s Override check box is selected, changes in the Default meet-me

configuration are not reflected in this field.

7 If needed, specify the source for any of the announcements (see Step 5 in

Defining Meet-Me Conference Aliases

Defining Default Values for Meet-me Conference Security Settings, page 12-82).
8 Click Save. The meet-me conference alias is displayed in the list on the Meet
Me Configuration List page.
12

Aeonix Administration Manual Configuring Services 12-87

NOTES:
 12.11 Defining Mobility Aliases

Mobility allows authorized users to receive an internal dial tone and access Aeonix
services from their cellular or other external handset. After successful user
authorization, the system either provides the dial tone directly (call-through), or
disconnects the call and calls the user back (callback).

Tips:
To learn more about the mobility feature, see Mobility, page 2-27.

A mobility alias number is the internal number associated with a mobility service.
The system matches this alias with an IT-defined mobility access number, which users
call from outside to access mobility services. Mobility aliases, as well as general
mobility call parameters and rules, are managed from the Mobility List Page.
Configuring a mobility alias is described in Defining a Mobility Alias, page 12-91.

Defining Mobility Aliases

12

Aeonix Administration Manual Configuring Services 12-89

  Mobility List Page

The Mobility List page displays mobility alias numbers defined in the system. To open
this page, click Mobility in the table on the Service List page (see Figure 12-1).

Figure 12-51 Mobility List

Page

The mobility list is sorted by the Alias column. If the list includes more than
one page, use the page navigation bar (see Table 6-1) at the bottom of the
list to navigate between the pages.

For each mobility alias, the list displays the alias number and an optional description
of the alias.
From this page, you can perform the following actions:

Table 12-32 Actions

Performed from the Action Button / Icon Description
Mobility List Page
Add mobility alias Click Add to add and set up a new mobility
alias (see Defining a Mobility Alias, page 12-91).

Update mobility In the list, click the alias to update the details of
—
alias this mobility alias configuration.
Delete mobility Select the check box next to the alias or
alias aliases to be deleted and then click Delete
(see Deleting Entities, page 3-66).
Access online help Click Help to receive online help.

Clone mobility Click this icon to duplicate the details of a

Defining Mobility Aliases

alias specific mobility configuration to a new mobility

alias.
12

12-90 Configuring Services Aeonix Administration Manual

  Defining a Mobility Alias

To add or update a mobility alias number:

1 On the Mobility List page (see Figure 12-51), do one of the following:
 To define a new mobility alias, click Add.
 To update an existing mobility alias, select it from the list.
 To define a new mobility alias based on the settings of an existing one,
click (the Clone icon) to the right of the relevant alias.

When you clone a mobility alias, all parameter values are copied to the new
alias except for the alias number.

The Mobility Alias page is displayed.

Figure 12-52 Mobility

Alias Page for a New
Alias (General Tab)

2 At the top of the page and on the General tab, set the parameters as described
in the following table.

Defining Mobility Aliases

12

Aeonix Administration Manual Configuring Services 12-91

 Table 12-33 Mobility
Service General Field Description
Parameters
Alias An internal alias number for the mobility service.
This number cannot be used from outside to access the
mobility service. To access the mobility service from
outside, the matching IT-defined mobility access number
must be dialed.

NOTE: Make sure that the number includes at least three

digits, is not already in use, and complies with the
alias patterns of the applicable dial plan (see Dial
Plans, page 4-19) You can click the Suggest
Available Aliases button to view a list of available
aliases and alias ranges.

Description An optional description of the mobility alias

Maximum call Once the mobility user has received an internal dial tone,
attempts the number of calls or call attempts the user can make
before the mobility session is disconnected

Maximum In callback scenarios, the number of times the system

callback attempts attempts to call back the user. If the callback fails, the
system plays an “exceeded number of call attempts”
announcement and disconnects the call.

Callback delay In callback scenarios, the interval in seconds between

time callback attempts

Answer delay For an authorized outside user using the internal dial
time tone to place a call, the maximum number of seconds
the system waits for the called party to answer

Delay before In callback scenarios, the number of seconds the system

making callback waits before it tries to call back the user

3 Click the Rules tab to view or set up mobility rules (see Configuring Rules for a
Mobility Alias, page 12-93).
4 At the bottom of the Mobility Alias page, click Save. The mobility alias is
Defining Mobility Aliases

displayed in the list on the Mobility List page.

12

12-92 Configuring Services Aeonix Administration Manual

  Configuring Rules for a Mobility Alias

Mobility rules specify how a calling user is authorized and granted mobility services.
These rules are defined per mobility alias as described in this section, or per user as
described in Configuring Mobility Rules for a User, page 6-62.
This section includes the following:
 Non-conflicting Rules, page 12-93
 Defining a Rule for a Mobility Alias, page 12-94

Non-conflicting Rules
For each new mobility rule that is created, the system verifies that the rule does not
conflict with already existing rules before saving it. When defining a rule, make sure
it is constructed according to the following guidelines:

Table 12-34 Mobility Rule Mobility User Authentication Service Limitation

Guidelines Alias Method Type
(Service #)

Same alias — Only ANI — Only one rule can

be defined for the
same ANI.

Same alias Same user — Callback No other identical

rule can be defined
for call-through.

— — At least one Call-through At least one

method authentication
method must be
selected for
call-through.

Defining Mobility Aliases

12

Aeonix Administration Manual Configuring Services 12-93

 Defining a Rule for a Mobility Alias

When defining a rule, make sure it does not conflict with already existing
rules. For details, see Non-conflicting Rules, page 12-93.

To add or update a mobility rule for a mobility alias:

1 On the relevant Mobility Alias page (see Figure 12-52), click the Rules tab.
The already defined mobility rules are displayed, if existing.

Figure 12-53 Mobility

Alias—Rules Tab with
Existing Rules

2 Do one of the following:

 To define a new mobility rule, click Add.
 To update a rule, click the user corresponding to the relevant rule.
The Add Rule or Update Rule page is displayed.

Figure 12-54 Add Rule

Page for a Mobility Alias
Defining Mobility Aliases
12

12-94 Configuring Services Aeonix Administration Manual

 3 Select Rule enabled to have the rule activated once it has been saved. If this
check box is not selected, the other rule parameters cannot be modified.
4 In the User text box, enter the internal User ID of the relevant user.
5 Specify the Authentication method. You can select either method, both
methods, or – for callback mobility only – no method.
 To base the authentication on the user’s external number, select ANI and
enter the full ANI number (including prefixes and suffixes) of the user.
 To base the authentication on the user passcode, select PIN.
6 Specify the service access method: Under Service type, select Callback and
enter a full callback number (including prefixes and suffixes), or select
Call-through.
7 Click OK to return to the Mobility Alias page.
8 Click Save.

Defining Mobility Aliases

12

Aeonix Administration Manual Configuring Services 12-95

NOTES:
 12.12 Configuring Call Detail Records (CDR)

Aeonix provides online CDR output for any type of call in the system. CDR reports
include call details such as start time and date, call duration, IP address, etc.
When defining online mode, you must set the IP address of the Windows host server
and port on which the CDR application resides.

To assign CDR configuration settings:

1 In the table on the Service List page (see Figure 12-1), click the CDR service.
The CDR page is displayed.

Figure 12-55 CDR Page

2 In the Description text box, enter a short description of the CDR configuration Configuring Call Detail Records (CDR)
(optional).
3 From the Mode drop-down list, select the required CDR mode (default: None,
where CDR records are not sent to any application).

Offline and Online & Offline modes are not in use - they are reserved for
12

backward compatibility purposes only.

Aeonix Administration Manual Configuring Services 12-97

 When Online mode is selected, define the following parameters:
4 From the Time and Date drop-down list, select the required time and date to
appear on CDR reports.
5 Select Send start call detail record if you want to include Start Call details in
online CDR reports. This information indicates the destination of outgoing
calls, allowing for quick response, for example, to emergency (911) calls. It
can also be used for detecting fraudulent calls and, in conjunction with an
appropriate third party application, blocking such calls.
6 Select Remote server acknowledges CDRs if you want the system to wait for
an ACK from the Call Accounting server after CDR reports are sent. The
Remote server must be configured accordingly to send the ACK byte for every
CDR that is received.
7 In the IP address / Host name field, enter the IP address or host name of the
Call Accounting server on which the online CDR application resides.
8 In the Send to Port field, enter the port number of the Call Accounting server
on which the online CDR application resides.
9 Click Save.
Configuring Call Detail Records (CDR)
12

12-98 Configuring Services Aeonix Administration Manual

 12.13 Computer Telephony Integration (CTI)

Computer Telephony Integration integrates and coordinates data with voice systems
to enhance telephone service. For example, CTI allows Caller ID information to be
displayed on a PC, or coordinates phone and data transfer between two parties.
Each Aeonix server has a default port assigned for Computer Telephony Integration
(CTI). You can change the port, if necessary.

Only Tadiran SIP Phones and Aeonix Touch Softphones, connected to an

Aeonix system, can be controlled via Aeonix CTI application control.

To assign an Aeonix port number for CTI purposes:

1 In the table on the Service List page (see Figure 12-1), click the CTI service.
The CTI page is displayed.

Figure 12-56 CTI Page

Computer Telephony Integration (CTI)

2 In the Port field, enter the port number as required. (The default value is
2555.)
3 Click OK. 12

Aeonix Administration Manual Configuring Services 12-99

Computer Telephony Integration (CTI)
12

12-100 Configuring Services Aeonix Administration Manual

 12.14 Directory

Aeonix provides a special Directory Group management feature for Aeonix Touch
users.
This advanced feature is still being developed for a future release of Aeonix. It is not
currently operable except at select Beta Sites.

Directory
12

Aeonix Administration Manual Configuring Services 12-101

Directory
12

12-102 Configuring Services Aeonix Administration Manual

 12.15 Defining Dispatch Consoles

Dispatch Console profiles contain the settings used to automatically configure

Dispatch Console grids and buttons. Dispatch administrators (see Defining User Identity
Settings, page 6-14) define these settings via the dispatch console itself.

Tips:
To learn more about the Dispatch Console, see Dispatch Console, page 2-19.

To learn how to configure and use the Dispatch Console, refer to the
Dispatch Console Online Help.

Dispatch Consoles are managed from the Dispatch Console List Page (page 12-104).
Managing Dispatch Consoles includes the following procedures:
 Defining a new Dispatch Console, page 12-106
 Defining a Dispatch Console Profile, page 12-107

Defining Dispatch Consoles

12

Aeonix Administration Manual Configuring Services 12-103

  Dispatch Console List Page

The Dispatch Console List page displays the dispatch consoles defined in the system.
To open this page, click Dispatch Console in the table on the Services List page
(see Figure 12-1).

Figure 12-57 Dispatch

Console List Page

The dispatch console list is sorted by the Name column. If the list includes
more than one page, use the page navigation bar at the bottom of the list to
navigate between the pages.

For each dispatch console, the list displays the following information.

Table 12-35 Dispatch

Console List Parameters Field Description

Status icon (circle) A circle icon to the left of each dispatch console indicates
the following:
 Green - the dispatch console is logged into Aeonix
 Red - the dispatch console is logged out of Aeonix

NOTE: View the specific icon’s tooltip for more information.

Name The name of the dispatch console

Description An optional description of the dispatch console

Profile Name The name of the profile associated with this dispatch
console
Defining Dispatch Consoles

Left Alias The alias number assigned to the left phone of the
dispatch console

Right Alias The alias number assigned to the right phone of the
dispatch console
12

12-104 Configuring Services Aeonix Administration Manual

 From the Dispatch Console List page, you can perform the following actions:

Table 12-36 Actions

Performed from the Action Button / Icon Description
Dispatch Console List
Page Add dispatch Click Add to add a new dispatch console
console (see Defining a new Dispatch Console, page 12-106).

Update In the list, click the dispatch console name to

dispatch — update the details of this dispatch console.
console
Delete dispatch Select the check box next to the dispatch console
console to be deleted and then click Delete (see Deleting
Entities, page 3-66).
Refresh Click Refresh to update the list to the current
status.

Access online Click Help to receive online help.

help

Clone dispatch Click this icon to duplicate the details of a specific

console dispatch console to a new dispatch console.

Manage Dispatch On the Services menu in the navigation pane,

dispatch Console click this link to manage dispatch console profiles.
console profiles Profiles (menu
option)

Defining Dispatch Consoles

12

Aeonix Administration Manual Configuring Services 12-105

  Defining a new Dispatch Console

To add or update a dispatch console:

1 On the Dispatch Console List page (see Figure 12-57), do one of the
following:
 To create a new dispatch console, click Add.
 To update an existing dispatch console, select it from the list.
 To define a new dispatch console based on the settings of an existing one,
click (the Clone icon) to the right of the relevant dispatch console.

When you clone a dispatch console, all parameter values are copied to the
new dispatch console except for the name.

The relevant Dispatch Console page is displayed.

Figure 12-58 Dispatch

Console Page for a New
Dispatch Console

2 Enter the name of the dispatch console in the Name box.

3 In the Description text box, enter a short description of the dispatch console
(optional).
4 From the Dispatch Console Profile drop-down list, select the profile you want
Defining Dispatch Consoles

to associate with this dispatch console (see Defining a Dispatch Console Profile,
page 12-107).
5 In the Left alias text box, enter the first digit of the relevant alias and select
the alias from the list displayed below the field.
6 In the Right alias text box, enter the first digit of the relevant alias and select
the alias from the list displayed below the field.
7 Click Save. The profile is displayed in the list on the Dispatch Console List
12

page.

12-106 Configuring Services Aeonix Administration Manual

  Defining a Dispatch Console Profile

To add, clone or delete a dispatch console profile:

1 While on the Dispatch Console List page (see Figure 12-57), click Dispatch
Console Profiles from the Services menu on the navigation pane. The
Dispatch Console Profiles page is displayed.

Figure 12-59 Dispatch

Console Profiles Page

Add new, remove, or copy dispatch console profiles as required:

 To add a profile, click Add, enter the name in the displayed Profile Name
box, and click OK.
 To delete a dispatch console, select it and click Delete. You can select more
than one dispatch console for deletion by using the CTRL and SHIFT keys.
Defining Dispatch Consoles

You cannot delete the default Aeonix Dispatch Console profile.

 To copy a profile, select it and click Clone. The new name in the displayed
in the Profile name box. An indexing suffix is automatically added to the
cloned dispatch console profile name. For example, if the original name is
12

QA Team, the cloned name will be QA Team_1. All the other attributes of

Aeonix Administration Manual Configuring Services 12-107

 the dispatch console associated with the original profile, such as button grid
setup, are copied as is to the new profile.
2 Click OK.
3 Click Save. The dispatch console profiled is included in the list on the
Dispatch Console Profiles page.
Defining Dispatch Consoles
12

12-108 Configuring Services Aeonix Administration Manual

 12.16 Configuring the E911 Database
Connector

The E911 databse update service sends Aeonix device and user update information to
an E911 service provider, which allows them to update their NEMA database.

Configuring the E911 Database Connector

12

Aeonix Administration Manual Configuring Services 12-109

  E911 Database Connector Page

The E911 Dabase Connector page allows you to define a prefix string that will identify
email sent from Aeonix to the E911 service provider containing database updates (as
a .CSV file attachment). To open this page, click E911 Database Connector in the
table on the Service List page (see Figure 12-1).

Figure 12-60 E911

Database Connector
Page

Enter the file prefix string in the File Prefix for E911 Email Update field. Click Save
to save the information into the Aeonix system.
The Send Now button can be used to force an immediate send of the Aeonix device
parameters to the E911 service provider for testing.
Configuring the E911 Database Connector
12

12-110 Configuring Services Aeonix Administration Manual

 12.17 Configuring the Music Service

The Music service enables parties put on hold to hear music or messages played from
audio files or IP streaming music sources. Up to 10 music services with IP stream
source and an unlimited number of music services with file source can be defined. A
list of aliases and alias ranges can be assigned to each music source.
Callers placed on hold by aliases associated with the music source are played music
or messages as defined for the specified source. Callers placed on hold by aliases not
associated with a specific Music source continue hearing music or messages from the
default system-wide music audio file as defined in the root CUG (see Defining a Closed
User Group, page 4-32).
The Music service is managed from the Music Service List Page. Managing the Music
service is described in Configuring a Music Source and MOH Alias Numbers, page 12-114.

Configuring the Music Service

12

Aeonix Administration Manual Configuring Services 12-111

  Music Service List Page

The Music Service List page displays the music sources defined in the system. To open
this page, click Music in the table on the Service List page (see Figure 12-1).

Figure 12-61 Music

Service List Page

The Music Service list is sorted by the Name column. If the list includes more
than one page, use the page navigation bar (see Table 6-1) at the bottom of
the list to navigate between the pages.

For each music service configuration, the list displays the following information.

Table 12-37 Music

Service List Parameters Field Description

Name The name of the music service

Type The music source type (audio file or IP stream)

Description An optional description of the music service

Information The IP address or URL of the incoming IP port of the RTP

stream for IP stream configured music sources, and the
codec type for IP stream audio sources
Configuring the Music Service
12

12-112 Configuring Services Aeonix Administration Manual

 From this page, you can perform the following actions:

Table 12-38 Actions

Performed from the Action Button Description
Music Service List Page
Add music service Click Add to add a new music source
(see Configuring a Music Source and MOH Alias
Numbers, page 12-114).
Update music In the list, click the music source to update the
—
service details of this music source configuration.
Delete music Select the check box next to the music source
service or sources to be deleted and then click Delete
(see Deleting Entities, page 3-66).
Access online help Click Help to receive online help.

Configuring the Music Service

12

Aeonix Administration Manual Configuring Services 12-113

  Configuring a Music Source and MOH Alias Numbers

To add or update a music source and associated alias numbers:

1 On the Music Service List page (see Figure 12-61), do one of the following:
 To define a new music source, click Add.
 To update an existing music source, select it from the list.
The Music Source Configuration page is displayed.

Figure 12-62
Configuration Page for a
New Music Source

2 In the Name text box, enter the name of the music source.
Configuring the Music Service

3 In the Description text box, enter a short description of the music source
(optional).
4 Define whether the music source is from an audio file or IP stream:
a File - click Edit. The Audio Files dialog box is displayed.
12

12-114 Configuring Services Aeonix Administration Manual

Figure 12-63 Audio Files
Des

Dialog Box

Define the audio sources for the required codec types (see Table 4-14 on
page 4-34), and, if you selected File, select the required audio file from the
adjacent drop-down list, and then click OK. The dialog box is closed.

Tips:
To learn how to add additional audio files, see Importing Audio Files, page 12-133.

Or
b IP stream - select the incoming IP port and the codec of the RTP stream.
The music input sampling rate must be 8kHz mono (64kbit/sec).

Configuring the Music Service

If Aeonix runs in a cluster environment, the audio stream must be sent to the
same IP port on each of the servers as configured below.
12

Aeonix Administration Manual Configuring Services 12-115

 Figure 12-64 IP Stream
Music Source
Configuration

5 To the right of the Assign MOH to Alias box, click Add, enter an alias or
range of aliases or click Update to modify an existing entry.
6 Click OK. The dialog box is closed.
7 Click Save. The music service is included in the list of the Music Service List
page.

Deleting a MOH Alias

To delete a MOH alias:

Configuring the Music Service

1 In the Assign MOH to alias box, select the alias number and click Delete.
The alias is removed from the box.
2 Click Save to delete the alias.
12

12-116 Configuring Services Aeonix Administration Manual

 12.18 Configuring Page Queue Park/Pickup

Aeonix supports various types of call parking and call pickup. One of them, Page
Queue Park/Pickup, involves parking calls to predefined alias numbers.

Tips:
To learn more about the page queue feature, see Page Queue, page 2-31.

Defining Alias Numbers for Page Queue Park/Pickup, page 12-118 describes how to
dedicate alias numbers for the queue call park/pickup service.

Page Queue is an Aeonix feature that incorporates the functionality of call

transfer. It is not necessary or recommended that the user press Transfer
before pressing Page Queue as a “destination”. Page Queue will
automatically transfer the call to the configured alias numbers as described
in this chapter.

Configuring Page Queue Park/Pickup

12

Aeonix Administration Manual Configuring Services 12-117

  Defining Alias Numbers for Page Queue Park/Pickup

To define an alias (internal access number) for page queue park/pickup:

1 On the Service List page (see Figure 12-1), click Page Queue Park/Pickup.
The Page Queue Park/Pickup page is displayed showing the already assigned
alias numbers, if available.

Figure 12-65 Page Queue

Park/Pickup Page

2 In the Display name field, enter the text to be displayed to the parking user,
the parked user, and the user retrieving the parked call.
3 Click Add to add a new alias, or select an alias from the list to update it. The
Alias page is displayed.

Figure 12-66 Defining a

Page Queue Park/Pickup
Alias
Configuring Page Queue Park/Pickup

Make sure that the alias number to be assigned is not already in use and that
it does not comply with the alias patterns of the applicable dial plan (see Dial
Plans, page 4-19).
12

12-118 Configuring Services Aeonix Administration Manual

 4 When the Complete alias type is used (default), specify the Call Preemption
priority and behavior to be used when this Page Queue Park/Pickup alias is
dialed. For example, from the Priority drop-down list, select High and then,
from the Action drop-down list, select Call Waiting. For more information, see
Call Preemption, page 2-13.

The Action drop-down list is only available when Medium, High, or Urgent is
selected from the Priority drop-down list.

5 Select the required alias type and define the alias as follows:

Type Description

Complete Use to define a specific alias number.

 Enter the number in the Alias text box.

NOTE: The alias number must consist of at least three digits.

Range Use to define a range of numbers used to park calls and pick up
parked calls.
 Enter the lowest number of the range in the Start of range box.
 Enter the highest number of the range in the End of range box.
Note: For performance it is recommended to not specify a Queue
greater than 100 numbers.

Prefix Use to define prefix digits and dedicate all aliases beginning with this
prefix for page queue park/pickup.
 Select Prefix and enter the prefix in the text box.
 Select Limit length and enter a number to restrict the amount of
digits, including the prefix, that can be dialed to park or pick up a
call. For example: if you specify a 3-digit Prefix, and a Limit
length of 4, the Queue will be 10 deep -- the 3-digit Prefix with
one more digit allowed to range from 0 to 9. If in the same case
you specify a Limit length of 5, the Queue will be 100 deep, with

Configuring Page Queue Park/Pickup

the last two digits ranging from 00 to 99.
Note: For performance it is recommended to not specify a Queue
greater than 100 numbers.

The type of an existing alias cannot be changed.

6 Click OK. The alias number is displayed in the alias list on the Page Queue
Park/Pickup page.
12

7 To add or update additional aliases, repeat Steps 3-6.

Aeonix Administration Manual Configuring Services 12-119

 8 In the Recall on page queue timeout text box, enter the number of seconds
after which a call that is put on hold in a page queue is recalled back to the
user that put the call on hold (Default: 120 seconds).
9 Click Save.
Configuring Page Queue Park/Pickup
12

12-120 Configuring Services Aeonix Administration Manual

NOTES:
Configuring Page Queue Park/Pickup
12

12-122 Configuring Services Aeonix Administration Manual

 12.19 Configuring PnP / Provisioning Service

The Provisioning service is responsible for keeping Tadiran SIP phones, as well as
P-Series phones, up-to-date in Aeonix. The system automatically updates phone
configurations that comprise SIP Terminal provisioning profile parameters (see
Managing Provisioning Profiles, page 5-91) and Configuration Sets (see Defining New
Configuration Sets, page 12-130), which are files that contain additional pre-configured
sets of features and parameters.
In addition, Plug and Play (PnP) modes can be used to quickly and easily define on
premise and remote (via VPN) Tadiran SIP phones on site. PnP can be used in parallel
to regular telephony operations.
A Tadiran SIP phone that is physically connected to the Aeonix network is
automatically identified by the system according to its MAC address, as follows:
 The phone is plugged in and connected to the network
 The phone accesses the DHCP server to get option 66
 The phone initiates a provisioning request to the Aeonix server URL
 The phone enters into the MAC list
At this point, the phone can be configured manually according to the MAC list (see
Select from Plug & Play drop-down, as shown in Figure 7-3), or automatically using
one of the PnP modes (see Configuring PnP Provisioning, page 12-126).
The following requirements must be met when configuring PnP and the Provisioning

Configuring PnP / Provisioning Service

service:
 A DHCP server with option 66 set to the hostname or IP address of the
Aeonix server. It is recommended to use the hostname for redundancy
purposes.
 For Tadiran SIP phones, the server URL must be defined in secured layer
mode access to Aeonix in the following format:
https://<aeonixserveraddress>:8443/aeonix/Provisioning (replace
<aeonixserveraddress> with the IP address of the Aeonix server or with the
Aeonix servers DNS name in a cluster environment). It is recommended to use
12

the DNS name for redundancy purposes.

Aeonix Administration Manual Configuring Services 12-123

 It is recommended to always use secured layer mode when Tadiran SIP
phones are connected to Aeonix. However, if P-Series phones are also used
in your system and you cannot use secured mode for the Tadiran SIP
phones, you must disable the "forceSecuredProvisioning" flag via SSH:
aeonix_params.sh -set redsea.conf.forceSecuredProvisioning 0

 For P-Series phones, the server URL must be defined in non-secured mode in
the following format: http://<aeonixserver IP>:8080/aeonix/Provisioning
(replace <aeonixserver IP> with the IP address of the Aeonix server or the
Aeonix servers DNS name in a cluster environment). It is recommended to use
the DNS name for redundancy purposes.
Configuring the server includes the following procedures:
 Viewing Updated Phone Firmware Files, page 12-124
 Defining New Configuration Sets, page 12-130
Configuring PnP includes the following procedures:
 Configuring PnP Provisioning, page 12-126

 Viewing Updated Phone Firmware Files

Aeonix functions as the provisioning server, which includes built-in firmware files.
When polled, provisioned phones that have firmware files that are different from these
files will automatically receive these updated files from Aeonix.

To view updated phone firmware files:

1 In the table on the Service List page (see Figure 12-1), click the PnP /
Configuring PnP / Provisioning Service

Provisioning service. The PnP / Auto Provisioning Service page is displayed.

12

12-124 Configuring Services Aeonix Administration Manual

Figure 12-67 Firmware
Tab for PnP / Auto
Provisioning Service
Page

Configuring PnP / Provisioning Service

The Firmware tab displays the Tadiran SIP phones and P-Series phones
firmware files that are currently used in Aeonix.
2 Use the drop-down lists to specify the interval for which the phone checks for
new configurations. (The default is 1 day and the minimum is 1 hour.)
3 At the bottom of the page, click Save.
12

Provisioning definitions will take effect after the phone's next configuration
check.

Aeonix Administration Manual Configuring Services 12-125

  Configuring PnP Provisioning

The Plug and Play tab is used for PnP provisioning of Tadiran SIP phones.
There are two PnP modes:
 Auto Phone mode – Used to generate new Tadiran SIP phone entities upon
phone requests for provisioning (see Table 12-41). In this case, no default user
is assigned to the phone. When Auto Phone mode is activated, a default user
can be assigned using feature code 159 (see Figure 4-9)
 Auto Phone & User mode – Used to generate new Tadiran SIP phone entities,
and, in addition, used to automatically generate users for these phones (see
Table 12-40)
Aeonix attempts to establish a provisioning session with all the phones in the MAC
list that are pending PnP provisioning and are not yet associated with any phone
definition.

Each entry in the MAC list must be refreshed by a request for provisioning
from the phone at least once a day; otherwise, the phone is automatically
removed from the list (see Table 14-2 - Stale MAC removed from MAC list
alarm).

To PnP provision Tadiran SIP phones:

1 From the PnP / Auto Provisioning Service page (see Figure 12-67), click the
Plug and Play tab.

Figure 12-68 Plug and

Play Tab for PnP / Auto
Provisioning Service
Page
Configuring PnP / Provisioning Service
12

12-126 Configuring Services Aeonix Administration Manual

 The following PnP configuration parameters are available:

Table 12-39 PnP

Configuration Parameters Field Description

Mode (Default: The PnP mode. Select one of the following:

Off)  Auto Phone to generate new Tadiran S|P phone
entities upon phone requests for provisioning.
 Auto Phone & User to generate new Tadiran S|P
phone entities upon phone requests for provisioning
and associate the phones with imported Aeonix
users, or newly created users.
 Off to deactivate PnP mode.

NOTE: The phone ID generated is based on the phone’s

MAC address and is preceded by the PNP prefix
(for example, PNP000A6B010203).

Plug & Play The time (30 minutes, 1 hour, or 4 hours) after which
timeout (Default: 1 PnP mode is deactivated. PnP mode can be extended
hour) during this period by clicking Save again.

NOTE: After the timeout has been reached, a pop-up

message is displayed notifying the administrator
who activated PnP mode, that it has expired.

Table 12-40 Auto

Generated Users Field Description
Configuration Parameters
Closed User The Closed User Group to which the user is assigned.
Group (Default:
Root)

Profile (Default: The profile assigned to the user.

Default User
Profile)

Configuring PnP / Provisioning Service

User alias starts at The starting alias according to which newly created
(Default: 2000) users are assigned available aliases during the PnP
process.

User login name When in Auto Phone & User PnP mode, the user login
prefix (Default: prefix assigned to newly created users. For example, if
PNP) the first available alias is 2000, then the newly created
user’s login name would be PNP2000.

Voicemail service Select the required voicemail service from the

drop-down list.
12

Aeonix Administration Manual Configuring Services 12-127

 Field Description

Create mailbox Provided that the selected voicemail service is active,

select this check box to create a mailbox for the newly
created users.

NOTE: The default mailbox password is 0000.

Table 12-41 Auto

Generated Phones Field Description
Configuration Parameters
Location (Default: The location where the phone is used.
Default location)
NOTE: Only servers of the selected location will answer
plug and play requests.

Provisioning profile The name of the provisioning profile associated with this
(Default: None) phone, which is used to define various phone
parameters such as SIP server, Time server, etc.

2 Click Save to activate the selected PnP mode.

A PnP icon is displayed at the top of each Aeonix Admin page to remind you
that you are in PnP mode. View the icon’s tooltip for the time remaining in
PnP mode.

Figure 12-69 PnP Icon

(example)
Configuring PnP / Provisioning Service
12

12-128 Configuring Services Aeonix Administration Manual

 After the Plug & Play timeout is reached, a pop-up screen is displayed
notifying the administrator who activated PnP mode that it has ended. PnP
mode can be extended by the timeout value by clicking Save again.

Configuring PnP / Provisioning Service

12

Aeonix Administration Manual Configuring Services 12-129

  Defining New Configuration Sets

Aeonix comes with predefined profile configuration sets, which by default are
assigned for provisioning purposes for Tadiran SIP phones, P-Series phones, and
Tadiran TGW gateways. These configuration sets can then be associated with profiles
(see Defining a Provisioning Profile, page 5-94).
However, you can create additional Configuration Sets based on this default set by
using an SSH program, such as WinSCP (http://winscp.net/eng/download.php).

To create a new configuration set:

1 Open a WinSCP session (or any other SSH program).

Figure 12-70 Logging

into Aeonix via SSH
Program
Configuring PnP / Provisioning Service

2 Enter the following information:

 Host name: [the host name of your Aeonix system]
 User name: aeonixadmin
12

 Password: Aeonix

12-130 Configuring Services Aeonix Administration Manual

 3 Click Login; you are now logged into the Aeonix system.
4 For P-Series phones, go to the
/home/aeonixadmin/aeonix/resources/provisioning/PSeries/Templates
directory (right pane), and copy the Default folder to your computer (left
pane).

or

For Tadiran SIP phones, go to the

/home/aeonixadmin/aeonix/resources/provisioning/T3XX/Templates
directory (right pane), and copy the Default folder to your computer (left
pane).

For Tadiran TGW gateways, go to the

/home/aeonixadmin/aeonix/resources/provisioning/TGW/Templates
directory (right pane), and copy the Default folder to your computer (left
pane).

5 Rename the folder as required.

6 Modify the configuration files as required according to the corresponding
phone manufacturer’s Auto Provisioning documentation.

Do not rename the configuration files.

7 Move the files back to the Aeonix server (right pane).

Configuring PnP / Provisioning Service

The files must be copied to all the servers in the cluster.

8 Save the configuration file. The Configuration Set is now available when
defining provisioning profiles (see Advanced Parameters, page 5-100).
12

Aeonix Administration Manual Configuring Services 12-131

NOTES:
 12.20 Importing Audio Files

The Prompt and Message service enables administrators to import Wav and MP3 input
audio files. These files are then converted to G.711Alaw, G.711µlaw, and G.729 format
and replicated to all the servers of the Aeonix cluster. These files are used for playing:
 Aeonix–Music on Hold (MOH), as well as announcers for ACD / Hunt group,
Wake-up call, Conference call, virtual endpoint, Zone Page announcers, etc.
 Aeonix Contact Center–Music on Hold (MOH), queue music, and IVR
announcers
 SeaMail–recorded message prompts

To import audio files:

For best results, ensure that the quality of the input files are of high quality.

1 In the table on the Service List page (see Figure 12-1), click the Prompt and
Message service. The Prompt and Message page is displayed.

Figure 12-71 Prompt and

Message Page

Importing Audio Files

12

Aeonix Administration Manual Configuring Services 12-133

 2 Click the Choose File button and use the displayed dialog box to locate the
required input audio file (up to 20MB) on your workstation or network; the
name of the selected audio file is displayed adjacent to the button.

If the imported recorded file exceeds 5 minutes, it will be truncated to the first
5 minutes. Multiple files can be uploaded in zip files of up to 40MB.

3 Select the required system module (Aeonix, Aeonix Contact Center, or SIP
voicemail).
4 In the corresponding Audio language drop-down list, select the language of
the audio file or files (if a zip file) being imported.

For Aeonix and SeaMail, ensure that you define a default audio file. That
way, if the file to be played does not exist in the user’s designated language,
the default language file will be played instead.

For customized Aeonix Contact Center audio files, click the Custom folder
check box, and select the required folder location from the drop-down list.

5 Click Import. The audio file or files are imported.

Repeat Step 2 o Step 5 to import additional audio files for the same or a
different system module.

Aeonix automatically converts the files to the supported formats and then
distributes them to each server in the Aeonix cluster into the specified
language sub-folders, as follows:
Importing Audio Files

The original input files are retained under

/home/aeonixadmin/aeonix/resources/audio/unconverted/

 Aeonix audio files:

/home/aeonixadmin/aeonix/resources/audio
 Aeonix Contact Center audio files:
12

/home/aeonixadmin/aeonix/resources/audio/ACC-IVR

12-134 Configuring Services Aeonix Administration Manual

  SeaMail audio files:
/usr/T3/vox.alaw/
/usr/T3/vox.ulaw/
/usr/T3/vox.g729/

The folders where the audio files are located are kept in sync on all the
servers in the cluster. When adding a new server to the cluster, the files are
replicated to the new server within an hour after the server is up and running.

Importing Audio Files

12

Aeonix Administration Manual Configuring Services 12-135

NOTES:
 12.21 Configuring Voicemail

Aeonix voicemail applications provide users with advanced voicemail and unified
messaging capabilities.

Tips:
To learn more about the voicemail feature, see Unified Messaging and Voicemail,
page 2-42.

Aeonix includes by default the SeaMail voicemail application, but can be configured
to support multiple SIP voicemail applications. Before voicemail can be used, the
relevant application must be defined as an Aeonix service through the SIP Voicemail List
Page. Integrating a voicemail application into Aeonix is described in Defining Voicemail
Applications in Aeonix, page 12-140.

SeaMail
Once the application has been defined as a SIP voicemail in Aeonix, the system
provides direct access to all voicemail properties and settings (see Accessing SeaMail,
page 12-148). Users can be assigned a voicemail box for their alias number
(see Managing Voicemail Boxes for Users, page 6-24).

Configuring Voicemail
12

Aeonix Administration Manual Configuring Services 12-137

  SIP Voicemail List Page

The SIP Voicemail List page displays the voicemail applications defined in the system.
To open this page, click SIP Voicemail in the table on the Service List page
(see Figure 12-1).

Figure 12-72 SIP

Voicemail List Page

For each voicemail application, the list displays the following information.

Table 12-42 SIP Voicemail

List Parameters Field Description

Status icon A circle icon to the left of each voicemail application indicates
(circle) the following:
 Green - for voicemail applications that are configured to
register on Aeonix, indicates that the voicemail is currently
registering on Aeonix
 Red - for voicemail applications that are configured to
register on Aeonix, indicates that the voicemail is currently
not registering on Aeonix
 Blue - the voicemail has been configured to not register on
Aeonix

NOTE: View the specific icon’s tooltip for more information.

ID Unique identifier of the voicemail application

Display Name The name of the voicemail application displayed to users

Voicemail True indicates that, upon registering, the voicemail

Registers on application sends a message to the Aeonix server.
Aeonix False indicates that the application will be manually
authenticated without registering on Aeonix (static
Configuring Voicemail

registration).

Device Address The URI (Uniform Resource Identifier) address and port at
which the voicemail application can be accessed

Aliases The alias number or numbers associated with the voicemail

application.
12

NOTE: If the application is assigned more than one alias, they

are displayed in a drop-down list.

12-138 Configuring Services Aeonix Administration Manual

 From this page, you can perform the following actions:

Table 12-43 Actions

Performed from the SIP Action Button Description
Voicemail List Page
Add voicemail Click Add to add a new voicemail application
application (see Defining Voicemail Applications in Aeonix,
page 12-140).
Update voicemail In the list, click the voicemail application ID to
—
application update the details of this application.
Delete voicemail Select the check box next to the voicemail
application application or applications to be deleted and
then click Delete (see Deleting Entities, page 3-66).
Access online help Click Help to receive online help.

Configuring Voicemail
12

Aeonix Administration Manual Configuring Services 12-139

  Defining Voicemail Applications in Aeonix

Aeonix can have one or more voicemail applications installed. This section describes
how to define voicemail application parameters and alias numbers that allow users to
access their mailboxes.
You can update the properties and alias numbers of an already defined voicemail
application as well.

To add or update a voicemail application:

1 On the SIP Voicemail List page (see Figure 12-72), click Add to define a new
voicemail application, or click an existing application to update it. The SIP
Voicemail page is displayed.

Figure 12-73 SIP

Voicemail Page for a New
Voicemail Application
Configuring Voicemail

For previously defined applications, the SIP Voicemail also contains a

Configure button for accessing voicemail parameters (see Accessing SeaMail,
page 12-148).
12

2 Set the SIP voicemail general identity parameters as described in the following
table and in Table 8-9.

12-140 Configuring Services Aeonix Administration Manual

Table 12-44 Voicemail
Identity Parameters Field Descriptions

ID Unique identifier of the voicemail application.

NOTE: This field is mandatory. Once saved, it cannot be

modified.

Display name The name of the voicemail application as viewed by users

Location The location where the voicemail application is used

(see Locations, page 4-9)

3 Set and manage the voicemail aliases as described in the following procedures:
 Defining Alias Numbers for a Voicemail Application, page 12-146
4 Deleting Voicemail Alias Numbers, page 12-147Click the Registration tab.

Figure 12-74 Voicemail

Registration tab

5 Set the voicemail registration parameters.

Table 12-45 Voicemail

Registration Parameters Field Descriptions

Voicemail Set to Yes if upon registering you want the voicemail

registers on application to send a message to the Aeonix server.
Aeonix Set to No if you want the application to be manually
authenticated without registering it in the Aeonix system (static
registration).

NOTE: It is recommended to select Yes; otherwise, there will be Configuring Voicemail

no true indication that the voicemail server is operating
(blue status icon), nor will it be possible to forward
incoming calls to another voicemail service in the event
that this voicemail service stops registering in Aeonix.

Keep-alive Number of seconds between keep-alive messages before the

timeout voicemail application is assumed to be malfunctioning.
(Default: 10
12

seconds) NOTE: Only displayed if the Voicemail registers on Aeonix field

is set to Yes.

Aeonix Administration Manual Configuring Services 12-141

 Field Descriptions

Voicemail SIP The URI (Uniform Resource Identifier) address at which the
address Aeonix can reach the voicemail application. Specify the
following fields:
 The IP address (IPv4 or IPv6) of the application
 Port—the SIP port of the application (by default 5060, or,
when transport protocol TLS is used, secured port 5061)
 Protocol—the protocol used to communicate with the
application

Servers Select the server or servers on which the application is running.

NOTE: This field is only available in systems with multiple Aeonix

servers if the field Voicemail registers on Aeonix is set
to No.

6 Click the Configuration tab.

Figure 12-75 Voicemail

Configuration tab
Configuring Voicemail
12

12-142 Configuring Services Aeonix Administration Manual

 7 Set the voicemail configuration parameters.

Table 12-46 Voicemail

Configuration Parameters Field Descriptions

Requires Select Yes if Aeonix initiates calls with session timer refresh,
session timer which is used to determine whether the SIP session is still
active.

NOTE: It is recommended to select Yes if the voicemail

application does not register with Aeonix.

Session-Expires The Aeonix proposal time for the Session Expires Time (in
Time seconds).

NOTE: This field is only relevant if the field Require session

timer is set to Yes.

Minimum The minimum Session Expires Time value (between 90 and

Session-Expires 10000) agreed upon by both call parties.

Requires Whether Provisional Response Acknowledgement (PRACK)

PRACK messages are used to ensure proper call progress (currently
set to No).

NOTE: This field cannot be modified.

Authenticate Whether a valid user name and password must be supplied for
inbound incoming calls (currently set to No).
messages
NOTE: This field cannot be modified.

Diversion The diversion header specifies the user for which voicemail
header format messages are diverted to the mailbox. This field specifies the
diversion header prefix the voicemail uses (currently set to Sip
URI).

NOTE: This field cannot be modified.

Send 181 - Determines whether or not SIP message 181 is sent when a
when call is call is forwarded (currently set to Yes).
forwarded
NOTE: This field cannot be modified.
Configuring Voicemail
Supported Whether the Refer or Re-invite command is used for call
transfer method transfer (currently set to re-INVITE).

NOTE: This field cannot be modified.

Call progress NOTE: The method by which progress tones from remote trunks
tone are handled when a call from a SIP is outgoing to
another trunk and the trunk requests to open the media
12

before answering (currently set to 183+SDP-device /

ITSP dependent). This field cannot be modified.

Aeonix Administration Manual Configuring Services 12-143

 Field Descriptions

Send Invite to Determines when to send the INVITE WITH REPLACES

transfer target: response. Currently set to After consultation answer, which
sends the INVITE response after the 3rd party answers a
two-step transfer on alert.

NOTE: This field cannot be modified.

Forward to This field is relevant for incoming calls that are redirected once
mailbox of or several times because the called user or extension does not
(Default: Last answer. In this scenario, the non-answering parties can be
redirection) internal Aeonix destinations or external PBX (Coral)
destinations with Aeonix mailboxes.
 Select Last redirection to route the call to the mailbox
assigned to the last number to which the call was redirected.
 Select Original destination to route the call to the mailbox
assigned to the called destination.
For calls to an external PBX extension that are redirected to
an Aeonix user, specify the original destination as follows:
Prefer external PBX destination—route the call to the
mailbox of the external extension. If this mailbox is not
available, try the Aeonix user mailbox instead.
Prefer internal destination—route the call to the mailbox of
the Aeonix user. If this mailbox is not available, try the
external PBX mailbox instead.

8 Click the Routing tab.

Figure 12-76 Voicemail

Routing tab
Configuring Voicemail

9 Set the voicemail routing parameters.

12

12-144 Configuring Services Aeonix Administration Manual

Table 12-47 Voicemail
Routing Parameters Field Descriptions

Forward on Select the check box, and enter the name of the user, number,
logoff or other voicemail application you want to forward incoming
calls to in the event that this voicemail service is not registering
on Aeonix.

NOTE: Only relevant if the voicemail server is set to register on

Aeonix (see Table 12-45).

Forward on Select the check box, and enter the name of the user, number,
busy or voicemail application you want to forward incoming calls to in
the event that this voicemail service is not available to receive
calls

ARS Table Specify which ARS table the SIP voicemail service will use to
Name dial outbound calls.

NOTE: To learn more about routing tables and how they are
defined, see Chapter 4, Automatic Route Selection
(ARS).

10 Click Save.

Configuring Voicemail
12

Aeonix Administration Manual Configuring Services 12-145

 Defining Alias Numbers for a Voicemail Application
A voicemail alias number is the internal call number of the voicemail application.

Make sure that the alias number to be assigned is not already in use and
complies with the alias patterns of the applicable dial plan (see Dial Plans,
page 4-19).

To assign or update an alias:

1 On the SIP Voicemail List page, Identity & Aliases tab (see Figure 12-73),
click Add to the right of the Aliases box, or select an alias in the box and
click Update. The Alias page is displayed.

Figure 12-77 Defining a

SIP Voicemail Alias

2 When the Complete alias type is used (default), specify the Call Preemption
priority and behavior to be used when this voicemail alias is dialed. For
example, from the Priority drop-down list, select High and then, from the
Action drop-down list, select Call Waiting. For more information, see Call
Preemption, page 2-13.
Configuring Voicemail

The Action drop-down list is only available when Medium, High, or Urgent is
selected from the Priority drop-down list.
12

12-146 Configuring Services Aeonix Administration Manual

 3 Select the alias type and define the alias as follows:

Type Description

Complete Use to define a specific alias number.

 Enter the number in the Alias text box.

NOTE: You can click the Suggest Available Aliases button to view a
list of available aliases and alias ranges.

NOTE: The alias number must consist of at least three digits.

Range Use to define a range of numbers used to access voicemail.

 Enter the lowest number of the range in the Start of range box.
 Enter the highest number of the range in the End of range box.

Prefix Use to define prefix digits and route all aliases beginning with this
prefix to the voicemail application.
 Select Prefix and enter the prefix in the text box.
 Select Limit length and enter a number to restrict the amount of
digits, including the prefix, that can be dialed to reach voicemail.

The type of an existing alias cannot be changed.

4 Click OK. The new alias number is displayed in the Aliases box on the SIP
Voicemail page.
5 Click Save.

Deleting Voicemail Alias Numbers

To delete alias numbers:

1 On the SIP Voicemail List page (see Figure 12-72), select the relevant alias in
the Aliases box and click Delete. A confirmation message is displayed.
Configuring Voicemail

You can select more than one alias number by using the CTRL and SHIFT
keys.

2 Click Yes. The alias or aliases are removed from the Aliases box on the SIP
Voicemail page.
3
12

Click Save.

Aeonix Administration Manual Configuring Services 12-147

  Accessing SeaMail

This procedure describes how to access the SeaMail Web Portal. The
SeaMail properties and settings are described in detail in the
SeaMail Administration and Configuration Manual for Aeonix.

To access the SeaMail Web Portal:

1 On the SIP Voicemail List page (see Figure 12-72), click the SeaMail
application name. The SIP Voicemail page, Configuration tab is displayed.
2 At the bottom of the page, click Configure to open the SeaMail Web Portal;
the SeaMail parameters are displayed and can be defined or edited as required.

Figure 12-78 SeaMail

Configuring Voicemail
12

12-148 Configuring Services Aeonix Administration Manual

 12.22 Defining Virtual Endpoints

The Virtual Endpoint service enables external customer applications to manage the
control flow of incoming calls. An incoming call to one of the service's assigned
aliases will be answered by the Virtual Endpoint service. From that moment on the
customer's external application can, via CTI, receive the call associated events (e.g.,
when the user presses digits, the call is disconnected, etc.) and perform operations on
the call (e.g., play sound files to the user, transfer the call to an agent, etc.). An
example of such an external application is a customer IVR system.
In addition, the Virtual Endpoint service can be configured with multiple sub-aliases
referred to as Virtual Agents, which can only be reached via the Virtual Endpoint
service (they cannot be called directly). When an incoming call arrives to a Virtual
Endpoint Service that has Virtual Agents, it transfers the call to the first available
agent. If all agents are busy, the incoming call will be parked.

Parked calls are transferred on a FIFO basis (i.e., the first incoming call will
be serviced first) to the first available agent.

Virtual Endpoint services are managed from the Virtual Endpoint List Page.
Managing Virtual Endpoint services are described in Defining Virtual Endpoint and Virtual
Agent Alias Numbers, page 12-152.

Defining Virtual Endpoints

12

Aeonix Administration Manual Configuring Services 12-149

  Virtual Endpoint List Page

The Virtual Endpoint List page displays the virtual endpoint alias numbers defined in
the system. To open this page, click Virtual Endpoint in the table on the Service List
page (see Figure 12-1).

Figure 12-79 Virtual

Endpoint List Page

The virtual endpoint list is sorted by the Alias column. If the list includes more
than one page, use the page navigation bar (see Table 6-1) at the bottom of
the list to navigate between the pages.

For each virtual endpoint configuration, the list displays the following information.

Table 12-48 Virtual

Endpoint List Parameters Field Description

Alias The alias number assigned to the virtual endpoint

Description An optional description of the virtual endpoint

Handled by The server or servers that handle incoming calls to the

Virtual Endpoint alias

Backed up by The backup server or servers that handle incoming calls to

the Virtual Endpoint alias
Defining Virtual Endpoints
12

12-150 Configuring Services Aeonix Administration Manual

 From this page, you can perform the following actions:

Table 12-49 Actions

Performed from the Action Button Description
Virtual Endpoint List
Page Add virtual Click Add to add a new virtual endpoint alias
endpoint alias (see Defining Virtual Endpoint and Virtual Agent Alias
Numbers, page 12-152).
Update virtual In the list, click the alias to update the details of
—
endpoint alias this virtual endpoint configuration.
Delete virtual Select the check box next to the alias or
endpoint alias aliases to be deleted and then click Delete
(see Deleting Entities, page 3-66).
Access online help Click Help to receive online help.

Defining Virtual Endpoints

12

Aeonix Administration Manual Configuring Services 12-151

  Defining Virtual Endpoint and Virtual Agent Alias Numbers

To add or update a virtual endpoint alias:

1 On the Virtual Endpoint List page (see Figure 12-79), do one of the following:
 To define a new virtual endpoint alias, click Add.
 To update an existing virtual endpoint alias, select it from the list.
The Virtual Endpoint Configuration page is displayed.

Figure 12-80
Configuration Page for a
New Virtual Endpoint
Defining Virtual Endpoints

You can use the Search box to textually search for and display specific items
in the list.
12

12-152 Configuring Services Aeonix Administration Manual

 2 Enter the virtual endpoint number in the Alias text box. This number is
internally dialed to activate the virtual endpoint.

The alias number must consist of at least three digits and cannot be modified
for an existing virtual endpoint. You can click the Suggest Available Aliases
button to view a list of available aliases and alias ranges.

3 In the Description text box, enter a short description of the virtual endpoint
(optional).
4 To associate a user profile (including location and routing rules settings) with
outgoing external calls, enter the required profile in the For outgoing external
calls, use profile of text box.
5 Select Auto answer to automatically activate auto answer on the virtual
endpoint.

If cleared, the Overflow tab is displayed (see Figure 12-82).

6 To associate a user profile (including location and routing rules settings) with
outgoing external calls, enter the required profile in the Virtual Endpoint page
of the Aeonix Admin.
7 By default, incoming calls to a Virtual Endpoint alias are handled by the server
that received the calls. In cluster environments, to assign a specific server or
all the servers in an Aeonix cluster instead, select the servers from the
Handled by and backed up by drop-down lists.

In the event that these servers are not available, an incoming call will be
handled by the server that received the call.

8 The following Audio File Configuration announcer is available:

Defining Virtual Endpoints
Table 12-50 Virtual
Endpoint Audio File Field Description
Configuration
First The audio file containing an optional announcement to
announcement file be played. If selected, the caller hears this
announcement once.

NOTE: If this check box is not selected, callers are

12

prevented from hearing the First announcement

file.

Aeonix Administration Manual Configuring Services 12-153

 9 For the audio file configuration field, click Edit. A dialog box is displayed for
specifying the location of the first announcement file.

Figure 12-81 Dialog Box

for First Announcement
File

10 Define the audio sources for the required codec types (see Table 4-14 on
page 4-34), and, if you selected File, select the required audio file from the
adjacent drop-down list.

Tips:
To learn how to add additional audio files, see Importing Audio Files, page 12-133.

11 Click OK. The dialog box is closed.

12 Click the Overflow tab (only displayed when the Auto answer check box is
Defining Virtual Endpoints

cleared). The tab displays the possible overflow situations.

12

12-154 Configuring Services Aeonix Administration Manual

Figure 12-82 Overflow
Tab for New Virtual
Endpoint

13 Specify the Call failover threshold for incoming calls that are not handled
within a predefined time (default: 20 seconds), and then select one of the
following overflow options:
 No action—the call continues ringing even after the threshold has been
reached.
 Disconnect with busy reason—the call is disconnected, and the caller
receives a busy reason for the disconnection. This is the default selection.
 Disconnect—the call is disconnected.
 Redirect to—the call is forwarded to a specified user or external number.
Select the user or enter the external number as required.
14 To play an audio file before the selected overflow action, select the check box
below the options, and then click Edit to specify the file name for the required
codec.
15 Click Save. The virtual endpoint is included in the list of the Virtual Endpoint
List page.

To add or update a virtual agent alias number: Defining Virtual Endpoints

1 To the right of the Virtual Agents List box, click Add, or select an existing
alias in the box and click Update. The Alias Configuration page is displayed
on the Virtual Endpoint List page.
12

Aeonix Administration Manual Configuring Services 12-155

 Figure 12-83 Alias
Configuration Page for
Virtual Agents

2 Select the alias type (usually Complete for a virtual agent) and define the alias
as follows:

Type Description

Complete Use to define a specific alias number.

 Enter the number in the Alias text box.

NOTE: You can click Suggest Available Aliases to view a list of

available aliases and alias ranges.

NOTE: The alias number must consist of at least three digits.

Range Use to define a range of numbers used to reach the virtual agent.
 Enter the lowest number of the range in the Start of range box.
 Enter the highest number of the range in the End of range box.

The type of an existing alias cannot be modified.

3 Select Virtual agent should auto answer (default) to automatically activate

auto answer on the virtual agent endpoints.
4 Click OK.
Defining Virtual Endpoints

5 Click Save.
Aeonix searches for an alias number in the following order:
 It tries to find a number matching a complete alias.
 If no match is found, the system checks if the number falls into a defined alias
range.
 If still no match is found, the system checks whether the number has a prefix
12

that matches one of the defined alias prefixes.

12-156 Configuring Services Aeonix Administration Manual

 Deleting a Virtual Agent Alias

To delete a virtual agent alias:

1 In the Virtual Agents List box, select the virtual agent alias number and click
Delete. The alias is removed from the box.
2 Click Save to delete the alias.

Defining Virtual Endpoints

12

Aeonix Administration Manual Configuring Services 12-157

NOTES:
 12.23 Defining Zone Page Calls

Zone Page calls include several users and/or user groups under dedicated alias
numbers. When an initiator dials a Zone Page number, the system places calls to all
the members in Auto Answer mode.
During the dialing period, which can take a few seconds, the system plays the
mandatory announcement to members that are already connected to the Zone Page
call. This message is then optionally followed by a user defined First announcement.
During the Zone Page, all the members’ phones will be muted. Up to 125 members
can participate in a Zone Page call.
Zone Page calls are managed from the Zone Page List Page. Managing Zone Page calls
is described in Defining Zone Page Call Alias Numbers, page 12-161.

Defining Zone Page Calls

12

Aeonix Administration Manual Configuring Services 12-159

  Zone Page List Page

The Zone Page List page displays the zone page alias numbers defined in the system.
To open this page, click Zone Page in the table on the Service List page (see Figure
12-1).

Figure 12-84 Zone Page

List Page

The zone page list is sorted by the Alias column. If the list includes more
than one page, use the page navigation bar (see Table 6-1) at the bottom of
the list to navigate between the pages.

For each zone page configuration, the list displays the following information.

Table 12-51 Zone Page

List Parameters Field Description

Alias The alias number assigned to the zone page

Description An optional description of the zone page

From this page, you can perform the following actions:

Table 12-52 Actions

Performed from the Zone Action Button Description
Page List Page
Add zone page Click Add to add a new zone page call alias
alias (see Defining Zone Page Call Alias Numbers,
page 12-161).
Defining Zone Page Calls

Update zone page In the list, click the alias to update the details of
—
alias this zone page configuration.
Delete zone page Select the check box next to the alias or
alias aliases to be deleted and then click Delete
(see Deleting Entities, page 3-66).
Access online help Click Help to receive online help.
12

12-160 Configuring Services Aeonix Administration Manual

  Defining Zone Page Call Alias Numbers

To add or update a zone page alias:

1 On the Zone Page List page (see Figure 12-84), do one of the following:
 To define a new zone page alias, click Add.
 To update an existing zone page alias, select it from the list.
The Zone Page Configuration page is displayed.

Figure 12-85
Configuration Page for a
New Zone Page

2 Enter the zone page number in the Alias text box. This number is internally
dialed to activate the zone page.

The alias number must consist of at least three digits and cannot be modified
for an existing zone page. You can click the Suggest Available Aliases
button to view a list of available aliases and alias ranges. Defining Zone Page Calls

3 In the Description text box, enter a short description of the zone page
(optional).
4 Specify the Call Preemption priority and behavior to be used on zone page
members when this zone page alias is dialed. For example, from the Priority
drop-down list, select High and then, from the Action drop-down list, select
12

Call Waiting. For more information, see Call Preemption, page 2-13.

Aeonix Administration Manual Configuring Services 12-161

 The Action drop-down list is only available when Medium, High, or Urgent is
selected from the Priority drop-down list.

5 Specify the settings for the following General zone page parameters:
 Terminate the zone page when the playback ends––to disconnect all
members when the predefined announcement ends.
 Terminate the zone page when the initiator disconnects––to disconnect
all members when the initiator disconnects.
 Zone page initiator will have audio priority––Aeonix usually grants
speaking privilege to the three members with the strongest signals. Enabling
this feature ensures that the initiator is included as one of the three sources,
even if their signal is not one of the three strongest in the call.
6 Select one of the following to define who can activate zone page calls:
 Managers only—only managers can activate zone page calls.
 Managers and members—managers and members can activate zone page
calls. This is the default selection.
 Everyone—any user can activate zone page calls.

To allow incoming external calls to start zone pages, set this parameter value
to Everyone.

7 Click the Group tab to define the managers and members of the zone page
call.
Defining Zone Page Calls
12

12-162 Configuring Services Aeonix Administration Manual

Figure 12-86 Group Tab
for Zone Page Calls

8 The Unassigned box displays the ID values of all users and groups that are not
assigned to the zone page as members (upper list) or managers (lower list).

Below the boxes, you can use the (right arrow) to display the next items Defining Zone Page Calls
or the Search box to search for and display specific items in the list.

To view the members of a group, select the group from the list and click View
Group. A tree of the users and sub-groups belonging to the group is
displayed at the bottom of the page.
12

Aeonix Administration Manual Configuring Services 12-163

 To add a user or group to the zone page as a member or manager, select it in
the relevant Unassigned box and click (the right arrow). The selected item
is moved to the Assigned box and added to the list of items to be included in
the zone page call.
Repeat this step to add other users or groups as members or managers of the
zone page call.

To delete a member or manager, remove it from the relevant Assigned box

by selecting it there and clicking (the left arrow). You can add or remove
multiple users and groups by holding down the CTRL or SHIFT key while
selecting them.

9 Use the External Members box (middle list) to define external users as a
conference members.

Because it cannot be known in advance if the initiator of the Zone Page Call
will have “dial out without ‘9’ access code” configured or not, you must
specify External Member numbers with the ‘9’ prefix explicitly included in the
External Members box.

Add new, update, or remove external users as required:

 To add an external user, click Add, enter the phone number in the adjacent
box, and click OK.
 To update an external user, select the user and click Update. Modify the
number that is displayed in the adjacent box, and click OK.
 To delete an external user, select the user and click Delete. You can select
more than one user for deletion by using the CTRL and SHIFT keys.
10 Click the Announcers tab.

Figure 12-87 Announcers

Defining Zone Page Calls

Tab for Zone Page Calls

12

The following Audio File Configuration announcers are available:

12-164 Configuring Services Aeonix Administration Manual

Table 12-53 Zone Page
Audio File Configuration Field Description
Parameters
Mandatory The audio file containing the announcement to be
announcement file played to the connected members while the Zone Page
call is dialed to the other members.

First The audio file containing the subsequent optional

announcement file announcement to be played to the Zone Page members
after the mandatory announcer. If selected, members
hear this announcement once.

NOTE: If this check box is not selected (default),

members are prevented from hearing the First
announcement file.

11 For each audio file configuration field, click Edit. The corresponding dialog
box is displayed for specifying the location of the announcement file.

Figure 12-88 Dialog Box

for Mandatory
Announcement File
(Example)

Defining Zone Page Calls

12 Define the audio sources for the required codec types (see Table 4-14 on
page 4-34), and, if you selected File, select the required audio file from the
adjacent drop-down list.
12

Aeonix Administration Manual Configuring Services 12-165

 Tips:
To learn how to add additional audio files, see Importing Audio Files, page 12-133.

13 Click OK. The dialog box is closed.

14 Click Save. The zone page is included in the list of the Zone Page List page.
Defining Zone Page Calls
12

12-166 Configuring Services Aeonix Administration Manual

 Chapter 13

Managing Your Account

13.1 Your Own Account ..............................................................13-1

13.2 Configuring Your Account ...................................................13-3

13.3 Managing Your Call Logs..................................................13-13

Aeonix Administration Manual

 13.1 Your Own Account

Just as regular users, administrators have their own ID number, identity parameters,
alias numbers, voicemail boxes, and routing definitions. These settings can be
configured from the My Account menu located at the bottom of the navigation pane.

My Account is not available for the predefined default administrator

aeonixadmin, because aeonixadmin is not a user.
For regular users, My Account is the only available category. It has the
same structure as My Account for administrators, but includes less
configurable parameters and options. For details, refer to the Aeonix
Configuration Guide for End Users (see Related Documentation, page 1-17).

Figure 13-1 My Account

for Administrators (My
Settings)

Your Own Account

13

Aeonix Administration Manual Managing Your Account 13-1

 For administrators, My Account provides an access point for convenient
configuration of their account settings. However, except for their presence status and
their mailbox configuration, administrators can configure all their parameters and
settings through their User page, as described in Defining a User, page 6-9.
Your Own Account
13

13-2 Managing Your Account Aeonix Administration Manual

 13.2 Configuring Your Account

This section describes or refers to the procedures for setting up your account through
the My Account menu:
 Defining Your Presence Status, page 13-4
 Modifying Your Identity Settings, page 13-5
 Managing Your Phone Numbers, page 13-5
 Managing Your Voicemail Settings, page 13-6
 Overriding Your Profile Configuration, page 13-6
 Defining Your Phones, page 13-7
 Managing Your Phone Profiles, page 13-7
 Setting the Access Code for a Meet-me Conference Alias, page 13-7
 Managing Your Mobility Rules, page 13-8
 Managing Your ULA Settings, page 13-8
 Installing the Sea Navigator on Your Workstation, page 13-9
 Installing the Sea Attendant on Your Workstation, page 13-9
 Installing the Aeonix Contact Center Client on Your Workstation, page 13-10
 Installing the FlexIP Softphone Client on Your Workstation, page 13-10
 Installing TAPI Service Provider and DialIt on Your Workstation, page 13-10
 Installing Aeonix Touch on Your Workstation, page 13-11

Configuring Your Account

13

Aeonix Administration Manual Managing Your Account 13-3

  Defining Your Presence Status

You can set your presence to reflect your current online status. Your presence status
can be used as a condition for forwarding or rejecting calls (see Defining Advanced Rules
for Incoming Call Routing, page 5-35).

To set your presence status:

1 On the navigation pane, select Presence Information from the My Account
menus. The Presence page is displayed.

Figure 13-2 Presence

Page

2 If the page indicates you are currently not logged in to any of your devices,
click Refresh.
If the offline indication remains, verify that you and your associated phone are
correctly defined and registered in the Aeonix system.
3 Select the relevant Status When Logged In option—Online, DND, or At a
meeting.

If you select DND, a Do-Not-Disturb busy tone is played to callers.

The DND status can also be accessed by dialing the DND code defined in
the dial plan (see Table 4-10 on page 4-23). This status is reflected both on
the Presence page and on the display panel of the caller’s phone.

4 Click Save.
Configuring Your Account
13

13-4 Managing Your Account Aeonix Administration Manual

  Modifying Your Identity Settings

On the navigation pane, select My Settings from the My Account menu. Your identity
settings are defined in the upper part of your User page and under the Identity &
Aliases tab.

Figure 13-3 Identity &

Aliases Tab (My Account
Menu)

You can modify your identity parameters as described in Table 6-5 on page 6-15,
except for your Login name, Profile, and User ID.

 Managing Your Phone Numbers Configuring Your Account

On the navigation pane, select My Settings from the My Account menus. Your
numbers are displayed under the Identity & Aliases tab in the Internal Aliases and
External Numbers boxes (see Figure 13-3).
Update or delete your numbers as required (see Assigning Aliases to Users, page 6-19 and
Specifying External Phone Numbers, page 6-27). If you delete an alias number that has a
13

voicemail box assigned, the mailbox is also deleted.

Aeonix Administration Manual Managing Your Account 13-5

  Managing Your Voicemail Settings

On the navigation pane, select My Settings from the My Account menus. If a

voicemail box has been defined for your alias number, it is displayed under the
Identity & Aliases tab below the Aliases box.
 To view or set up your voicemail box settings, click Configure my voice
mailbox. For a detailed description of the voicemail parameters, or to learn
how to configure your voicemail box, refer to the SeaMail User Guide
(see Related Documentation, page 1-17).
 To delete your voicemail box without removing the related alias number, select
Delete voicemail box and click Save.

You can also access the settings of your or another voicemail box as
described in Accessing SeaMail, page 12-148.

 Overriding Your Profile Configuration

On the navigation pane, select My Settings from the My Account menus, and then
click the Profiles tab.

Figure 13-4 Profiles Tab

Configuring Your Account

Adjust your profile configuration and values as described in Overriding User Profiles,
page 6-29.
To override incoming or outgoing call routing parameters, you can also use the My
Incoming Routing or My Outgoing Routing menu. The parameters and rules that
can be defined are described in Overriding Incoming Call Routing Rules, page 6-40 and
Overriding Outgoing Call Routing Parameters and Rules, page 6-43.
13

13-6 Managing Your Account Aeonix Administration Manual

  Defining Your Phones

On the navigation pane, select My Settings from the My Account menus, and then
click the Phones tab.

Figure 13-5 Phones Tab

The My Phones table displays your phones that have already been defined in the
system (see Viewing and Editing User’s Phones, page 6-59). Under New Phone
Configuration, you can add your phones to Aeonix and configure their basic
parameters (see Managing a User’s Phones, page 6-56). Advanced phone parameters are
set as described in Configuring Phones in Aeonix, page 7-9.

 Managing Your Phone Profiles

You can update a phone profile by selecting it from the navigation pane. (If necessary,
click the Phone Profiles node to display the available phone profiles.) For detailed
instructions, see Configuring a User’s Phone Profiles, page 6-49.

The currently active phone is highlighted in blue.

 Setting the Access Code for a Meet-me Conference Alias

If you are defined as the owner of a meet-me conference alias, you can specify the
Configuring Your Account
access code for joining conferences at this alias.
On the navigation pane, select My Settings from the My Account menus, and then
click the Conferences tab.
13

Aeonix Administration Manual Managing Your Account 13-7

 Figure 13-6 Conferences
Tab

Set or remove access codes as described in Setting the Meet-me Conference Access Code,
page 6-72.
To learn more about meet-me conferences and how to define their owners, see Defining
Meet-Me Conference Aliases, page 12-79.

 Managing Your Mobility Rules

On the navigation pane, select My Settings from the My Account menus, and then
click the Mobility tab (see Figure 13-7). This tab displays the mobility rules that have
been defined for you.

Figure 13-7 Mobility Tab

Add, change, or delete mobility rules as described in Configuring Mobility Rules for a User,
page 6-62.
Configuring Your Account

 Managing Your ULA Settings

On the navigation pane, select My Settings from the My Account menus, and then
click the ULA tab (see Figure 13-8). This tab displays the members of your ULA
group if available, and also lists the ULA groups to which you belong as a regular
13

member.

13-8 Managing Your Account Aeonix Administration Manual

Figure 13-8 ULA Tab

You can add members to your ULA group (up to 50 members per group), set your and
their ULA login status and ring policy, or remove members. You can also specify your
login status and ring policy in groups to which you are assigned as a regular member;
to manage these groups, however, you have to navigate to the User page of their
owners. For detailed instructions, see Managing a User’s ULA Settings, page 6-65.

 Installing the Sea Navigator on Your Workstation

The Sea Navigator is an advanced desktop communications application that runs on

top of Aeonix. For an introduction to the Sea Navigator, see Sea Navigator, page 2-39.
The Sea Navigator client download and installation procedure is described in Aeonix
Clients for Users, page 6-99.
You can download and install the Sea Navigator client on your workstation from the
Settings>Downloads menu (see Downloading the Sea Navigator / Sea Attendant Client,
page 6-102).

You must be authorized to use the application in your Feature Configuration

profile settings - see Table 5-6 on page 5-17.

Configuring Your Account

 Installing the Sea Attendant on Your Workstation

The Sea Attendant is an advanced desktop unified communications manager

application for operators that runs on top of Aeonix. For an introduction to the Sea
Attendant, see Sea Attendant, page 2-37. The Attendant client download and
installation procedure is described in Aeonix Clients for Users, page 6-99.
13

Aeonix Administration Manual Managing Your Account 13-9

 You can download and install the Sea Attendant client on your workstation from the
Settings>Downloads menu (see Downloading the Sea Navigator / Sea Attendant Client,
page 6-102).

You must be authorized to use the application in your Feature Configuration

profile settings - see Table 5-6 on page 5-17.

 Installing the Aeonix Contact Center Client on Your Workstation

The Aeonix Contact Center is an advanced telephony and ACD application. For an
introduction to the Aeonix Contact Center, see Aeonix Contact Center, page 2-5. The
Aeonix Contact Center client download and installation procedure is described in
Aeonix Clients for Users, page 6-99.
You can download and install the Aeonix Contact Center client on your workstation
from the Settings>Downloads menu (see Downloading the Visor / Agent Client,
page 6-103).

 Installing the FlexIP Softphone Client on Your Workstation

The FlexIP is a softphone-based phone offering a full range of capabilities. For an

introduction to the FlexIP softphone, see FlexIP Softphone, page 2-23. The FlexIP
softphone client download and installation procedure is described in Aeonix Clients for
Users, page 6-99.
You can download and install the FlexIP softphone client on your workstation from
the Settings>Downloads menu (see Downloading the FlexIP Softphone (FLIPS),
page 6-104).
Configuring Your Account

 Installing TAPI Service Provider and DialIt on Your Workstation

This is a configuration package that allows you to make calls from your Outlook
contacts and to make calls from anywhere on your workstation. For an introduction,
see Single Sign On, page 2-40. The download and installation procedure is described in
Aeonix Clients for Users, page 6-99.
13

13-10 Managing Your Account Aeonix Administration Manual

 You can download and install the package on your workstation from the
Settings>Downloads menu (see Downloading the TAPI Service Provider and DialIt,
page 6-105).

 Installing Aeonix Touch on Your Workstation

Aeonix Touch is feature-rich unified communications client. For an introduction to

Aeonix Touch, see Aeonix Touch, page 2-8. The Aeonix Touch client download and
installation procedure is described in Aeonix Clients for Users, page 6-99.
You can download and install the Aeonix Touch client on your workstation from the
Settings>Downloads menu (see Downloading Aeonix Touch, page 6-107).

Configuring Your Account

13

Aeonix Administration Manual Managing Your Account 13-11

NOTES:
 13.3 Managing Your Call Logs

You can access your Call Log directly through the My Account menus in order to
view a list of all incoming and dialed numbers. In addition, you can remove and export
call log entries from the Call Log list.
 Viewing Your Call Logs, page 13-13
 Deleting Call Log Entries, page 13-14
 Exporting Your Call Logs, page 13-15

 Viewing Your Call Logs

The Call Log page displays details of your latest call logs, including date and time of
the call, duration of the call, and the phone and contact name of the caller. It also
contains an area in which search criteria can be defined to find and display specific
call logs.

The Call Log list is limited to 100 entries. Oldest entries are bumped out of
the list as new entries are entered, if the list is full. Entries are maintained in
the list for 30 days, after which they are automatically deleted.

To view your call logs:

1 From the My Account menu, click Call Log. The Call Log page is displayed
(see Figure 13-9).
Click Refresh to update the list. Managing Your Call Logs

Figure 13-9 Call Log

Page
13

Aeonix Administration Manual Managing Your Account 13-13

 By default, the call log table is sorted by the Date/Time column. To sort
according to a different column, use the Sort by drop-down list. If the list
includes more than one page, use the page navigation bar at the bottom of
the list to navigate between the pages.

This table displays the following Call Log details:

Field Description

Call Type Icon - Answered Call

- Outgoing Call
- Missed Call

Date/Time The call date and time.

Duration The duration of the call in minutes and seconds.

Contact Name The name of the person you called (outgoing calls) or person
that called you (answered and missed calls).

Phone The phone number of the caller.

Save Icon - Saved Sea Navigator / Sea Attendant Call Logs

 Deleting Call Log Entries

You can delete one or multiple call log entries.

To delete call logs:

1 On the Call Log page (see Figure 13-9), select the check boxes left of the call
log entries you want to delete.
Managing Your Call Logs

2 Click Delete. A confirmation message is displayed.

13

13-14 Managing Your Account Aeonix Administration Manual

Figure 13-10 Confirm
Message

3 Click Yes to delete the entry or entries from the Call Log page.

 Exporting Your Call Logs

You can export your call logs to a CSV (comma-separated) file.

To export your call logs:

1 On the Call Log page (see Figure 13-9), click Export. A standard File
Download dialog box is displayed, prompting you to open or save the
CallLog.csv file.
2 Download the file in either of the following ways:
 To run the file without saving it first, click Open.
 To save the file at a specified location before running it, click Save.
Managing Your Call Logs
13

Aeonix Administration Manual Managing Your Account 13-15

NOTES:
 Chapter 14

Maintaining Aeonix

14.1 Alarms.................................................................................14-1

14.2 System Information...........................................................14-25

14.3 Clusters.............................................................................14-33

14.4 Data Backup and Restoring via Web................................14-55

14.5 Upgrading Aeonix via Web ...............................................14-63

14.6 Restarting Aeonix via Web................................................14-69

14.7 Downloading Logs via Web ..............................................14-71

14.8 Server-based Maintenance Tools .....................................14-79

14.9 Aeonix Error Messages ....................................................14-99

Aeonix Administration Manual

 14.1 Alarms

Aeonix can create alarm messages (traps) on system malfunction and shortage of
resources. The system sends these messages to external SNMP Network Management
System applications or NMS servers, or to specified email addresses using SMTP.
Alarm types are sent for server related reasons, such as when CPU, disk space, and
memory resources are becoming insufficient in an Aeonix server. Alarms are also
triggered on missing license permissions, or on license resources that are becoming
scarce. Finally, alarms are sent for Wave Gateway faults, such as when there is no
communication with a card.
For each alarm type, you can specify a threshold. If the resource usage exceeds this
threshold, the system sends an alarm.
This section describes the following alarm-related procedures:
 Viewing Alarms, page 14-2
 Configuring Alarm Access Parameters, page 14-18
 Configuring Alarm Notification Options, page 14-22

Alarms
14

Aeonix Administration Manual Maintaining Aeonix 14-1

  Viewing Alarms

To display the alarms:

1 At the bottom of the navigation pane, click System. The pane displays the
System menus.
2 Select the Alarms menu, and then click one of the following in the Alarms
menu:
 To view the current list of server, license, and Wave Gateway alarms, click
Current Alarms (see Figure 14-1).
 To view all the alarms, click All Alarms (see Figure 14-2).

The Alarm lists are sorted by the Time column with the most recent alarms
displayed first.

Figure 14-1 Current

Alarms Page
Alarms
14

14-2 Maintaining Aeonix Aeonix Administration Manual

Figure 14-2 All Alarms
Page

For server and license alarms, the following information is displayed:

Column Information

Severity icon Is displayed to the left of each alarm.

(circle)  A red circle icon indicates a critical alarm.
 A green circle icon indicates a non-critical alarm.

NOTE: View the specific icon’s tooltip for more information.

Server The Aeonix server for which the alarm has been created

Name The server resource that is missing / insufficient or the license

item that triggered the alarm.

Time The date and time the alarm was issued.

Alarms
14

Aeonix Administration Manual Maintaining Aeonix 14-3

 Column Information

Severity The severity of the alarm:

 None
 Cleared
 Indeterminate
 Critical
 Major
 Minor
 Warning

Category The category of the alarm:

 None
 Other
 Communication
 Quality of service
 Processing error
 Equipment
 Environmental
 Integrity violation
 Operational violation
 Physical violation
 Security service mechanism violation
 Time domain violation

Description The alarm content. View the description text’s tooltip for more
information.

For Wave Gateway alarms, the following information is displayed:

Column Information

Severity icon Is displayed to the left of each alarm.

(circle)  A red circle icon indicates a problem alarm.
 A green circle icon indicates an informational alarm.

NOTE: View the specific icon’s tooltip for more information.

Wave Gateway The Wave Gateway for which the alarm has been created

Name The item that triggered the alarm.

NOTE: Click the name to view more details of the fault and the
Alarms

recommended course of action.

Time The date and time the alarm was issued

14

14-4 Maintaining Aeonix Aeonix Administration Manual

 Column Information

Severity The severity of the alarm:

 None
 Cleared
 Indeterminate
 Critical
 Major
 Minor
 Warning

Category The category of the alarm:

 None
 Other
 Communication
 Quality of service
 Processing error
 Equipment
 Environmental
 Integrity violation
 Operational violation
 Physical violation
 Security service mechanism violation
 Time domain violation

Description The alarm content. View the description text’s tooltip for more
information.

Alarms List Page Actions

From the Alarms List pages, you can perform the following actions:

Table 14-1 Actions

Performed from the Action Button / Icon Description
Alarms List Pages
Delete Select the check box next to the current alarm or
current alarm alarms to be deleted and then click Delete
(see Deleting Entities, page 3-66).

NOTE: Only applicable for the Current Alarms list

page.
Refresh Click Refresh to update the list to the current status.
display
Alarms

Clear display Click Clear All to remove all the alarms from the list.
14

NOTE: Only applicable for the All Alarms list page.

Aeonix Administration Manual Maintaining Aeonix 14-5

 Action Button / Icon Description
Access Click Help to access online help.
online help

You can view all alarms in the system or only the current alarms. Displayed are:
 Server alarms—(see Table 14-2 below for a description of server alarms)
 License alarms—alarms on license resources that are almost used up or have
expired (see Table 3-7 on page 3-36 for a description of license alarms)
 Wave Gateway alarms—(see Table 14-4 below for a description of Wave
Gateway alarms)

Table 14-2 Server Alarms

Alarm Name Description What To Do

Aeonix Contact One or more Aeonix Contact Center servers Check that the ACC service/s at the
Center Server is down. Linux level are running. Run the
Connection accstat command for indications that
a restart is needed. Restart the ACC
service: Service > ACC > Restart. If
this doesn’t resolve the problem,
open a service ticket with Customer
Support.

Aeonix Support This notification is displayed one month Contact your authorized Tadiran
About to Expire before Technical support expires. representative to renew technical
support.

Aeonix Support This notification is displayed when Technical Contact your authorized Tadiran
Expired support expires. representative to renew technical
support.

Concurrent Calls The total number of concurrent calls on all Consider purchasing additional
Count trunks has exceeded its threshold value and licenses to increase your system
there are no more available SIP capacity.
trunk/gateway resources for calls to be
made.

Connection failure Aeonix failed to connect to email server Contact Customer Support.
to email server “xxx”
Alarms
14

14-6 Maintaining Aeonix Aeonix Administration Manual

 Alarm Name Description What To Do

Cluster Connection One or more servers in the cluster is down. 1 Verify there is communication
between all servers.
2 Check if the disconnected server is
up or has any type of malfunction.
3 Renew network/communication
between servers.
4 If it was a network problem, the
cluster will connect automatically
as connection is resorted.
5 Restart server if needed.
6 Contact Customer Support with the
relevant information

Cluster Fatal 100% of the redo-log has been reached. Cluster auto-recovery cannot be
Disconnection performed. Once the network has
been restored, manually restore the
cluster (see below).
1 The same as Cluster Connection,
above.
2 As soon as connection is restored
or down servers are up and
running, the System Administrator
needs to follow the pop-up panel
instructions for server/s restart.

Cluster Manual The network connection was restored after Log in to Aeonix and follow the
Restoration 100% of the redo-log has been exceeded. restart server instructions.

Cluster 30% - 50% of the redo-log was reached. No action required. Cluster
Recoverable auto-recovery will be performed.
Disconnection

CPU usage CPU usage of the server has exceeded its View Aeonix sysHealth files to
threshold value. determine if this is a steady state or
a momentary state.
 If it is a steady state, check that
your servers meet Tadiran server
specifications.
In virtual machine environment, it
is crucial to check that you have
enough CPU's per the spec
 If it is a momentary state, your
Alarms

server may not be configured well.

Download Aeonix logs and open a
ticket for Tadiran Customer
14

Support to discuss.

Aeonix Administration Manual Maintaining Aeonix 14-7

 Alarm Name Description What To Do

Default Admin Aeonix checks administrators’ passwords Change the administrator password
Password Detected every 24 hours, and generates an alarm per via the Aeonix login dialog box.
each administrator that is using the system
default password.

Default Password System detected that the system default Update the relevant SIP endpoints
Alert password is being used by SIP endpoints with secured passwords.

Disk Usage Server disk space usage has exceeded its  Check that your server spec meets
threshold value. Tadiran specifications.
 Login to your server file system to
check what is taking the disk
space.
 Do not delete anything unless you
are sure it will NOT cause
problems.
 Consult with Tadiran Customer
Support if there is any doubt

Duplicate ELIN The same ELIN appears several times  This is a configuration issue within
Aeonix.
 Check your configuration and
remove every duplicated ELIN in
Aeonix location programming.
 If it does not resolve the problem,
open a service ticket with
Customer Support.

E911illegal mail The E911 service destination address is  This is a configuration issue within
address ill-formed Aeonix.
 Check the email address you
configured in Aeonix. Try sending
email from a “regular” client using
the same credentials.
 If this does not resolve the
problem, open a service ticket with
Customer Support.

E911 missing file The E911 service “xxx” does not define the  This is a configuration issue within
name name of the report file Aeonix.
 The prefix file name is missing in
the Aeonix programming. The
Prefix file name is programmed in
Alarms

Aeonix Services List (E911

Database Connector).
 If this does not resolve the
14

problem, open a service ticket with

Customer Support.

14-8 Maintaining Aeonix Aeonix Administration Manual

 Alarm Name Description What To Do

Empty E911 report The E911 report created by the service is Open a service ticket with Customer
empty Support.

ESF Server The ESF server on which the Provisioning  The ESF (Provioning Server) is
service resides is not available defined in Settings > Profiles >
Provisioning Profile list. It is
either one of the servers SIP
Server1/2, or another when using
DNS. Either way, the ESF server
is always one of the Aeonix
servers in the cluster.
 Check the communication with the
ESF server. PING is a good start
but you might need to verify SIP
etc. are not blocked.
 Check that the specific Aeonix
server is up and running.
 Check your DNS server.
 Contact Tadiran Customer
Support.

External Music The music source is not transmitting audio Check your audio source to see it is
Source as set in the service configuration. still connected or contact customer
support.

Failed to send E911 service “xxx” failed to send report to  This is a configuration issue within
E911 report “yyy” Aeonix.
 Check the email address you
configured in Aeonix. Try to
sending email from “regular” client
using the same credentials.
 If this does not resolve the
problem, open a service ticket with
Customer Support.

Grace Period System is running without the necessary  Check the Aeonix license server to
licenses and will stop working once the see if it is down or disconnected.
grace period has ended.  Check if the Aeonix license file
was tampered with or is corrupted.
 Contact your authorized Tadiran
representative.

Incorrect SIP Model One or more Tadiran SIP phones and Update the relevant SIP endpoints
Alarms

P-Series phones cannot register because with the correct device model.
there is a mismatch between the model
numbers in the Aeonix database and the
actual model numbers.
14

Aeonix Administration Manual Maintaining Aeonix 14-9

 Alarm Name Description What To Do

Keep-Alive Status While monitoring replication transport The Cluster management module will
functionality the connection between the handle this situation to gain full
server and cluster nodes was problematic. cluster functionality. Check the
network connection between servers
as it might be unstable.
If this does not resolve the problem,
please open a service ticket with
Customer Support.

Location Without Location has no country definitions. Associate the location with a country.
Country Warning

Memory Usage Server memory usage has exceeded its  View Aeonix sysHealth files to
threshold value. determine if this is a steady state
or a momentary state.
 If this is a steady state, or you
have frequent alarms, check that
your servers meet Tadiran server
specs.
 If not resolved by the above, open
a service ticket with Tadiran
Customer Support and attach all
logs including sysHealth.

No E911 active There is no active E911 active service.  This is a configuration issue in
service Aeonix.
 Locations in Aeonix have the box
checked "Devices at this location
will be included in the E911" but
the service is not activated.
 Activate the service in Aeonix.

No ELIN No ELIN for device “xxx”.  This is a configuration issue in

Aeonix.
 Locations are defined in the US
without ELIN number defined in
Aeonix.
 Add ELIN locations assigned to the
devices in Aeonix.
Alarms
14

14-10 Maintaining Aeonix Aeonix Administration Manual

 Alarm Name Description What To Do

No email for E911 The E911 service “xxx” has no destination This is a configuration issue in
service email service. Aeonix.
Open up a SSH session in Aeonix
and use the following commend to
define the email address where E911
update file will be sent:
>aeonix_aparms.sh -set
911ETC_RECEIVERS
[[email protected]]
Add the email address required.

No email server Email server is not defined. Set the email server address in
Aeonix Admin > System > Alarms
> Alarms Configuration

No sub-location Location “xxx” does not have a default This is a configuration issue in
sub-location. Aeonix.
Add the sub-location in the location
programming in Aeonix.
If this does not resolve the problem,
open a service ticket with Customer
Support.

Online CDR Server The Online CDR server is down.  Check that the CDR server is up
Connection and running.
 Check that the network connection
to the CDR server is working.
 Check that the CDR server is not
stuck.
 Restarting the CDR server might
address the problem.
 If not, open a service ticket with
Tadiran Customer Support and
attach the required information and
logs.

Persistent Persistent data is out of sync. The synchronization process is

Threshold currently being executed.
Exceeded

PMS Connection The connection to the PMS server is down. Check whether the PMS server is
operational and network connection
exists or contact Customer Support.
Alarms

Recording License The number of concurrent calls allowed by Obtain additional recording licenses.
Exceeded the Aeonix Logger license were fully utilized.
14

Aeonix Administration Manual Maintaining Aeonix 14-11

 Alarm Name Description What To Do

Recording Aeonix internal resources were fully utilized. Make sure you are not reaching the
Resources limit of recording channels per Aeonix
Depletion server.
An additional Aeonix server
deployment might be required.
Contact Customer Support.

Recording Server Aeonix cannot connect to the recording Check whether the Logger server is
Failure server. operational and network connection
exists.
Restart Logger server.
Open ticket with Tadiran support
including Logger and Aeonix logs.

Server Overload An alarm is sent warning that the system is View Aeonix sysHealth and
Warning almost overloaded. anxOverload files to determine if this
is a steady state or a momentary
state.
If this is a steady state, or you have
frequent alarms, check that your
servers meet Tadiran server specs.
If not resolved by the above, open
service ticket with Tadiran Customer
Support and attach all logs including
sysHealth and anxOverload.

Server Overloaded System is overloaded according to the View Aeonix sysHealth and
Server_Config.xml. Registered endpoints will anxOverload files to determine if this
not be able to make and receive calls and is a steady state or a momentary
new endpoint registration requests will be state.
rejected by the system in an effort to correct If it is a steady state, or you have
the overload. frequent alarms, check that your
servers meet Tadiran server specs.
NOTE: Emergency calls are supported during
overloads. If not resolved by the above, open a
service ticket with Tadiran Customer
Support and attach all logs including
sysHealth and anxOverload.

SIP Password System detected password hacking attempts Contact the person responsible for
Hacking on SIP endpoints. security in your organization.

SIP Registration System detected and blocked registration Contact the person responsible for
Alarms

Potential Rogue attempts from potential rogue SIP endpoints security in your organization.
(i.e., more than one registration IP address
is being assigned for the same endpoint).
14

14-12 Maintaining Aeonix Aeonix Administration Manual

 Alarm Name Description What To Do

SIP Registration System detected “xxx” registration attempts Contact the person responsible for
Scan to non-existent SIP endpoint “yyy” within a security in your organization.
10 minute period.

Stale MAC System detected that the specified phones Most likely, the phone is physically
removed from MAC have not requested provisioning for over 24 disconnected from the system. No
list hours. action required.

Too many E911 More than one E911 service are active. Open a service ticket with Tadiran
services Customer Support.

Transient Threshold Transient data is out of sync. Aeonix service restart is required to
Exceeded regain full cluster functionality.

Unauthorized Aeonix detects that an unauthorized phone Program the phone or remove it from
Phone Detection with IP “xxx” and MAC “yyy” has been the system.
registered to the system.

Unknown email The E911 email server “xxx” is unknown. Check that the E911 email server
server address has been specified correctly.
If problem persists, open a service
ticket with Tadiran Customer Support.

Unused phones System detected that the specified phones Program the phone or remove it from
that have requested provisioning during the the system.
last 3 days have not yet been programmed
in the system.

Weak Admin Aeonix checks administrator password Change the administrator password
Password Detected strength every 24 hours and generates an via the Aeonix login dialog box which
alarm for each administrator password that provides an indicator of password
is weak (lower than 70% strength). strength.

Weak SIP System detected weak passwords for SIP Update the relevant SIP endpoints
Password endpoints after an Aeonix upgrade. with secured passwords.

Table 14-3 License

Alarms

Alarm Name Description What To Do

Advanced Aeonix "Description: Consider purchasing additional

Alarms

users The notification is generated whenever licenses. For that, contact your
number of defined users is greater than the authorized Tadiran representative
threshold set in the Aeonix. "
14

Aeonix Administration Manual Maintaining Aeonix 14-13

 Alarm Name Description What To Do

Aeonix Dispatch "Description: Consider purchasing additional

Consoles The notification is generated whenever licenses. For that, contact your
(concurrent) number of defined Aeonix Dispatch authorized Tadiran representative
Consoles is greater than the threshold set in
the Aeonix."

Aeonix Gateway "Description: Consider purchasing additional

devices The notification is generated whenever licenses. For that, contact your
number of defined Aeonix Gateway Devices authorized Tadiran representative
is greater than Aeonix is licensed for."

Aeonix Gateway "Description: Consider purchasing additional

users The notification is generated whenever licenses. For that, contact your
number of defined Aeonix Gateway Users is authorized Tadiran representative
greater than Aeonix is licensed for."

Aeonix IP Net "Description: Consider purchasing additional

(concurrent calls) The notification is generated whenever licenses. For that, contact your
number of simultaeous conversations using authorized Tadiran representative
SIP trunk are greater than the threshold set
in the Aeonix. "

Aeonix Tadiran "Description: Consider purchasing additional

devices The notification is generated whenever licenses. For that, contact your
number of defined Aeonix Tadiran Devices authorized Tadiran representative
is greater than Aeonix is licensed for."

Aeonix Touch "Description: Consider purchasing additional

desktop softphones The notification is generated whenever licenses. For that, contact your
number of defined Touch Softphones are authorized Tadiran representative
greater than the threshold set in Aeonix."

Aeonix servers "Description: Consider purchasing additional

The notification is generated whenever licenses. For that, contact your
number of defined Aeonix servers are authorized Tadiran representative
greater than the threshold set in the Aeonix.
"

Attendant Console "Description: Consider purchasing additional

users The notification is generated whenever licenses. For that, contact your
number of defined Aeonix Attendant Console authorized Tadiran representative
Users is greater than Aeonix is licensed for.
Alarms

"
14

14-14 Maintaining Aeonix Aeonix Administration Manual

 Alarm Name Description What To Do

FlexIP softphones "Description: Consider purchasing additional

The notification is generated whenever licenses. For that, contact your
number of defined FlexSet IP Softphones is authorized Tadiran representative
greater than Aeonix is licensed for. "

G729 single media "Description: Consider purchasing additional

channels The notification is generated whenever licenses. For that, contact your
number of simultaeous conversations using authorized Tadiran representative
G.729 codec are greater than the threshold
set in the Aeonix."

Mobility users "Description: Consider purchasing additional

The notification is generated whenever licenses. For that, contact your
number of defined Mobility rules is greater authorized Tadiran representative
than Aeonix is licensed for."

Non-Tadiran "Description: Consider purchasing additional

devices The notification is generated whenever licenses. For that, contact your
number of defined non-Tadiran devices are authorized Tadiran representative
greater than the threshold set in the Aeonix."

Table 14-4 Wave Gateway

Alarms

Alarm Name Description What To Do

Battery Type This notification is generated whenever the Replace the battery on the DBMS
battery on the RAM memory card of the card in the Wave Gateway.
Wave Gateway is low and needs to be
replaced.

Card This notification is generated whenever a Reset card and observe. If the
card in the Wave Gateway has a minor problem continues, replace the card.
failure and needs attention.

Card Port This notification is generated whenever a Reset card and observe. If the
port on a card in the Wave Gateway has a problem continues, replace the card.
minor failure and needs attention.

Digital Trunk This notification is generated whenever a Reset card and observe. If the
digital trunk card in the Wave Gateway has problem continues, replace the card.
Alarms

a major failure and needs immediate

attention.
14

Aeonix Administration Manual Maintaining Aeonix 14-15

 Alarm Name Description What To Do

Duplication This notification is generated whenever a Replace the defective card or power
duplication of common control in the Wave supply.
Gateway has a major failure and needs
immediate attention.

Duplication Slave This notification is generated whenever the Replace the defective card or power
slave side of duplicate common control in supply.
the Wave Gateway has a major failure and
needs immediate attention.

Expansion This notification is generated when an alarm Correct the programming in the Wave
Configuration is raised in Office Wave Gateway system if Gateway
there is expansion shelf with installed cards
installed but the expansion type is not
defined in sysgen-->0 in the Wave Gateway
Office.

HDLC This notification is generated whenever the Contact field support at Tadiran.
HDLC highway in the Wave Gateway has a
failure to communicate to peripheral cards
and needs attention.

IOM Type This notification is generated is a problem Reset card and observe. If the
with the IOM channel of the SDT/SFT cards problem continues, replace the card.
installed in the Wave Gateway

Memory This notification is generated whenever the Replace the DBM memory card.
RAM memory card of the Wave Gateway
has an error and needs to be replaced.

PCM Hardware This notification is generated is a PCM Contact field support at Tadiran.
problem (audio problem on the PCM HW)
existing in the Wave Gateway.

PCM Time Slot A time slot problem (audio problem on a Contact field support at Tadiran.
specific timeslot) is detected in the Wave
Gateway cabinet.

Power Supply A power supply in the Wave Gateway has a Replace the defective power supply.
major failure and needs immediate attention.

Protection Level A hardware problem in the memory card Replace the DBM memory card.
(MEX/DBX…) in the Wave gateway has
Alarms

been detected.

Real Time Clock A problem with the real time clock in the Reset card and observe. If the
14

Type MEX card in the Wave Gateway has been problem continues, replace the card.
detected.

14-16 Maintaining Aeonix Aeonix Administration Manual

 Alarm Name Description What To Do

Synchronization Generated whenever the synchronization of Reset card and observe. If the
digital trunk card in the Wave Gateway fails problem continues, replace the card.
and needs immediate attention.

Wait State This notification is generated because of a Replace the DBM memory card.
detected hardware problem in the memory
card (MEX/DBX…) in the Wave Gateway.

Wave Gateway This notification is generated in the Wave Reset card and observe. If the
Card is Out gateway when a card is installed (CLIS problem continues, replace the card.
-i_type) but is not active (CLIS -p_type) for
some reason.

Wave Gateway This notification is generated whenever the  Check the network.
Fault communications between the Wave  Check wave gateway for hardware
Gateway and Aeonix fails and needs failures.
immediate attention.  Check wave gateway site log for
errors.
 Contact Customer Support at
Tadiran.

Table 14-5 Admin

Password Alarms

Alarm Name Description What To Do

Weak Admin Aeonix checks all administration passwords Login normally with the old password
Password Detected strength once every 24 hours, and and change the password.
generates an alarm for every Admin with a
weak password (lower than 70% strength).

Default Admin Aeonix checks all administration passwords Login normally with the default
Password Detected every 24 hours and generates an alarm for password and change the password.
every Admin that is using the system default
password.

Password Aging Aeonix checks all adinistration passwords Login normally with the old password
every 24 hours and generates an alarm for and change the password.
Alarms

every Admin whose password has reached

75% of the its age limit.
14

Aeonix Administration Manual Maintaining Aeonix 14-17

 Alarm Name Description What To Do

Administrator This alarm is generated if an Admin Call Tadiran Support.

Access Blocked password reaches its age limit, resulting in
the Admin’s access (login) being bloacked.

Administrator 2 possible events can generate this alarm: None. Warning only.
Hacking Alert  3 failed login attempts by the same Admin
within a 10-minute window.
 3 failed login attempts by multiple Admins
within a 10-minute window.

 Configuring Alarm Access Parameters

Alarms can be retrieved from an SNMP server or received by email. Alarm access
parameters therefore include:
 SNMP—the user name and password required for connecting the SNMP server
to the Aeonix server
 NMS—the IP address or server name of the NMS server to which SNMP
alarm messages are sent
 SMTP—SMTP email server IP address or name and the email addresses to
which the alarms are to be sent

Changing the “SNMP Server” and the “NMS System” parameters is not
allowed in A4C.

To configure alarm access parameters:

1 At the bottom of the navigation pane, click System. The pane displays the
System menus.
2 Select the Alarms menu, and then click Alarms Configuration. The Alarms
Configuration page is displayed.
Alarms
14

14-18 Maintaining Aeonix Aeonix Administration Manual

Figure 14-3 Alarms
Configuration Page

3 If your organization uses an SNMP server, specify the relevant user name and
password:
a Enter the User name and Password the system must use for connecting to
the Aeonix SNMP server. (The default user name and password is
AeonixUser and AeonixPassword respectively.)
b In the Retype password box, enter the password again for verification.

The entered values must match with the user name and the password
defined in the SNMP server, otherwise the connection will fail.

4 If your organization uses an NMS server, specify the following:

Table 14-6 NMS Server

Parameters Field Description

IP address or host The IP address or host name of the NMS server to which
name SNMP alarm messages are sent.

Port The port of the NMS server to which SNMP Trap

(Default: 162) messages are sent.

User name The user name used to access the NMS server.

Authentication The authentication protocol used to verify that the

protocol messages are from a valid source.
Alarms

Password The password used to access the NMS server.

14

Retype password Enter the password again for verification purposes.

Aeonix Administration Manual Maintaining Aeonix 14-19

 Field Description

Privacy protocol The SNMP Privacy Protocol the Aeonix server uses for
communicating with the NMS server.

Privacy password The SNMP privacy password configured for use when
communicating with the NMS server.

Retype privacy Enter the SNMP privacy password again for verification
password purposes.

5 Click the Email tab.

Figure 14-4 Email tab for

Alarms Configuration
Alarms

You can use the Search box to textually search for and display specific items
in the list.
14

14-20 Maintaining Aeonix Aeonix Administration Manual

 6 To receive the alarms per email, specify the SMTP email server address:

Changing the “SMTP Email Servers” parameters is not allowed in A4C.

a In the IP address or host name box, enter the IP address or host name of
the SMTP email server.
b In the port box, enter the TCP port the email server uses for sending
emails. (If this field is left empty, the default port 25 is used.)
c In the Sender name box, enter a valid email address from which alarm
messages are to be sent.
7 In the Email List box, specify the email addresses to which alarm messages
are to be sent:

It is permitted to add email addresses to the Email list, but predefined email
addresses should not be modified or deleted in A4C.

 To add an email address, click Add, enter the email address in the Email
box, and click OK. The email address is added to the Email List box.
 To update an email address, select it in the list box and click Update. Make
changes as required and click OK.
 To delete an email address, select it and click Delete.
To make sure the email addresses have been correctly defined and are
working, click Test Email. The system sends a test email to each specified
address and notifies you of the outcome.
8 At the bottom of the Alarms Configuration page, click Save.

If you made changes to NMS System parameters (see Table 14-6 on

page 14-19), the NMS server will be updated with the changes about a
minute after clicking Save.
Alarms
14

Aeonix Administration Manual Maintaining Aeonix 14-21

  Configuring Alarm Notification Options

Alarm notification settings determine which alarm messages are sent, and how.

To configure alarm notification settings:

It is not permitted to change Notification Options in A4C.

1 At the bottom of the navigation pane, click System. The pane displays the
System menus.
2 Select the Alarms menu, and then click Notification Options. The
Notification Options page is displayed.

Figure 14-5 Notification

Options

3 The Notification Options table lists the available alarm types. Specify the
Alarms

following for each alarm type:

14

14-22 Maintaining Aeonix Aeonix Administration Manual

Table 14-7 Alarm
Notification Options Parameter Description

Send by Mail Select this check box to have the alarm messages sent to
the email addresses specified in Configuring Alarm Access
Parameters, page 14-18.

Send by SNMP Select this check box to have the alarm messages sent to
the SNMP application / NMS server.

Show in Report Select this check box to have these alarm messages
included in the Current Alarms and All Alarms report
pages if the specified Threshold is reached.
(For a description of the alarm reports, see Viewing Alarms,
page 14-2.)

Threshold Enter the percentage above which the alarm message is

considered critical and sent to the specified destination.
For example, if you enter 85 for disk space, an alarm will
be sent as soon as more than 85% of the available disk
space is in use.

4 Click Save.

Partner/Customer and Landlord Email Destinations

An alarm email destination is defined for each alarm in the Alarms Configuration file
which can be found at:
/home/aeonixadmin/aeonix/config/alarmsConfiguration.xml
For every alarm, there is a <destinationType> tag. The tag value can be either
"normal" or "landlord".
In case of "normal", email will be send to both "Partner/Customer " and "Data Center".
In case of "landlord", email will be send to "Data Center" only.

Alarms
14

Aeonix Administration Manual Maintaining Aeonix 14-23

Alarms
14

14-24 Maintaining Aeonix Aeonix Administration Manual

 14.2 System Information

The following sections describe how to access Aeonix system information in the Web
Portal:
 Displaying Aeonix Version Information, page 14-26
 Clusters, page 14-33 (relevant for clustered systems)
 System Parameters, page 14-27

To view information related to licenses, see Licenses, page 3-29.

System Information
14

Aeonix Administration Manual Maintaining Aeonix 14-25

  Displaying Aeonix Version Information

To view the current Aeonix version:

 At the top of the page, click (About Aeonix icon). The About Aeonix
dialog box displays the current Aeonix version.
System Information
14

14-26 Maintaining Aeonix Aeonix Administration Manual

  System Parameters

System parameters define the initial system configuration and interface settings. The
parameters described in this section can be displayed and programmed in the Aeonix
Web Portal.

Modifying System Parameters is not permitted in A4C.

Several system parameters relate to the SeaMail voicemail application. To

learn about SeaMail, refer to the SeaMail Administration Manual (see Related
Documentation, page 1-17).

To view and set values for system parameters:

1 At the bottom of the navigation pane, click System. The pane displays the
System menus.
2 Select the System Parameters menu, and then click System Parameters. The
System Parameters page is displayed.

System Information
14

Aeonix Administration Manual Maintaining Aeonix 14-27

 Figure 14-6 System
Parameters Page

3 Set parameter values, where required, as described in the following table:

Table 14-8 System

Parameter Description
System Information

Parameters

Customer (Cluster) The name assigned to the Aeonix cluster. This name
name appears between the user name and date at the top of
Aeonix Web pages.
14

14-28 Maintaining Aeonix Aeonix Administration Manual

 Parameter Description

System administrator The system administrator mailbox number. The system

mailbox number needs this number to access SeaMail.
The default value is 100.

NOTE: This number must match the corresponding

Admin mailbox number defined in the SeaMail
Web Portal.

SeaMail role assigned The SeaMail role assigned to regular users. In

to regular users SeaMail, roles specify the items and parameters a user
can access and modify.

NOTE: The specified role must be defined in the

SeaMail Web Portal.

SeaMail role assigned The SeaMail role assigned to system administrators.

to system administrators This role must be defined in the SeaMail Web Portal.

SeaMail role assigned The SeaMail role assigned to CUG administrators. This
to CUG administrators role must be defined in the SeaMail Web Portal.

CUG administrator The Closed User Group administrator mailbox number.

mailbox number This number is identical to the system administrator
mailbox number if CUG and system administrators use
the same mailbox.
The default value is 100 and must match the
corresponding Admin mailbox number in the SeaMail
Web Portal.

User default password The automatically generated default password

assigned to new regular users of this Aeonix system.

NOTE: When upgrading the Aeonix software version,

existing users who changed their passwords will
automatically be assigned this password.

Alarm agent DTMF The DTMF digits duration when in ‘Agent’ (SIP INFO)
duration mode (see Alarm agent, page 7-23).
The default value is 500 ms (milliseconds).

NOTE: The maximum setting is 2000 ms, and the

System Information

minimum setting is 55 ms.

14

Aeonix Administration Manual Maintaining Aeonix 14-29

 Parameter Description

Layer 3 QoS voice The DSCP value used to determine the priority
priority assigned to outbound voice traffic for Tadiran SIP
Phones.
The default value is 0.

NOTE: Values 0 and 46 are supported for MGCP

phones. When configuring another value, Aeonix
will substitute the set value with the best possible
match.

Layer 3 QoS signaling The QoS Layer 3 setting for Tadiran SIP Phones.
priority The default value is 0.

NOTE: Values 0, 24, 26, 28, 30, 32 are supported for

MGCP phones. When configuring another value,
Aeonix will substitute the set value with the best
possible match.

System domain name The system domain name. This name appears in
phone and trunk IDs after the @ sign (see Table 7-5
on page 7-12 and Table 8-6 on page 8-11).
The default system domain name is aeonix.com.

NOTE: The system domain name can only be

modified if no phones or trunks have been
defined in the system. Specify the domain
name prior to adding phones and trunks.

Additional date format The character currently used for separating the date
separators units in the Default General Information sub-profile

Current date format Available date format separators, in addition to the

separator currently used separator

Separator of date format The character used for separating between the date
options format options. The default character is a comma (,).

Available date format The date formats that can be selected in the General
options Information sub-profile. Use Java conventions when
entering date formats.
System Information

Dispatch Console If selected, pressing a programmed virtual dial number

automatically button in the Aeonix Dispatch Console will add the
conferences aliases alias to conference
14

14-30 Maintaining Aeonix Aeonix Administration Manual

 Parameter Description

Enable emergency If selected, when an emergency call is made Aeonix

callback feature retains the information of the user that made the call
and the ELIN that is used with this call. For the next
hour, when emergency personnel at the PSAP (Public
Safety Answering Point) make an ELIN call back in an
effort to reconnect with the person in distress, they will
be rerouted to the user who made the emergency call.

NOTE: User call Forward All and DND will be ignored

and the user will not be able to logout of the
phone during this time to allow for the callback to
reach the emergency call initiator.

LDAP synchronization If selected, Aeonix will use an LDAP database for

information about users rather than data entered
manually in the Aeonix web admin. Aeonix can be set
to periodically synchronize with an LDAP database,
and the administrator can use the Synchronize Now
button in the Aeonix web admin to force an
unconditional sync. The Aeonix LDAP facility is
described in LDAP Connections on page 4-53 and Importing
LDAP Users on page 6-87.

LDAP single sign-on If selected, the product ecosystem of Aeonix, Aeonix

Call Center, and SeaMail will operate in Single Sign
On (SSO) mode. SSO is a standard for secure domain
environments, in which authentication is established
when the user logs into to the secure domain through
an SSO-managed protocol. When the user is logged in
at their workstation, they may launch authorized
applications which do not then present their own login
sequences. The SSO protocol uses LDAP User ID
during authentication, and authorized applications
check against that LDAP User ID when launched. See
Single Sign On on page 4-67 for details on deploying
Aeonix in an SSO environment.

4 Click Save.
System Information
14

Aeonix Administration Manual Maintaining Aeonix 14-31

System Information
14

14-32 Maintaining Aeonix Aeonix Administration Manual

 14.3 Clusters

The following sections describe how to access Aeonix cluster related pages in the Web
Portal:
 Displaying Cluster Information, page 14-34
 Restarting Servers After Network Connection Restored, page 14-39
 Configuring the Cluster for Registration Load Balancing, page 14-41
 Setting Server for ACD and Hunt Services, page 14-43
 Server Settings for the Aeonix Contact Center Service, page 14-44
 Enabling and Configuring High Availability, page 14-51

These sections are only relevant for systems consisting of two or more
clustered Aeonix servers.
Clusters of Aeonix servers are created during system installation. For details,
refer to the Aeonix Installation Manual (see Related Documentation, page 1-17).

Clusters
14

Aeonix Administration Manual Maintaining Aeonix 14-33

  Displaying Cluster Information

The Cluster Status page displays information about your Aeonix network, including
connection status, number of registered endpoints, and voicemail server associated
with each server in the cluster.
In the event that cluster functionality is compromised, the system will prompt you as
to which server or servers need to be restarted in order to recover the cluster.

To view Aeonix cluster status information:

1 At the bottom of the navigation pane, click System. The pane displays the
System menus.
2 Select the Cluster menu, and then click Cluster Status. The Cluster Status
page is displayed listing all servers belonging to the cluster.

Figure 14-7 Cluster

Status Page
Clusters
14

14-34 Maintaining Aeonix Aeonix Administration Manual

 The statuses on this page automatically refresh every minute.

For each server, the page displays the following information.

Table 14-9 Cluster

Information Field Description

Cluster Status Displays the operational status of the servers in the cluster.

Status icon (circle) A circle icon to the left of each server indicates the
connection status of the server in relation to the server the
administrator is currently logged in to, as follows:
 Green - the server is running and connected to your
server
 Red - the server is disconnected from your server

NOTE: Once the network connection has been restored, the

server will be restarted in order to recover the cluster.
 Yellow - the server has been temporarily disconnected
from your server

NOTE: If the network connection has been restored while

this server is still marked as Yellow, the server will
automatically be reconnected to the cluster via the
Aeonix auto-recovery mechanism.

NOTE: View the specific icon’s tooltip for more information.

Server Name The name of the server in the Aeonix system

NOTE: The first row displays the server you are logged in to.

Address Depending on the cluster definition, either the server’s IP

address (IPv4 or IPv6) or its host name

EPs Displays the number of registered endpoints

(phones+trunks) in each clustered server

In Start Time The date and time of the last change in the server’s
receive status.

NOTE: For a stand-alone server, this field is empty.

Out Start Time The date and time of the last change in the server’s
transmission status.
Clusters

NOTE: For a stand-alone server, this field is empty.

14

Aeonix Administration Manual Maintaining Aeonix 14-35

 Field Description

Voicemail The name of the voicemail service instance. A server may

have multiple voicemail instances installed on it. The
voicemail instance may be running in registered or
unregistered mode. If the drop-down list has a red border,
this indicates that at least one of the voicemail services on
that server has a problem. Display the list to see which
voicemail services have problems, indicated by red text.

Call Recording The location name of the call recording instance running on
that server. Red text indicates that the call recording
service has a problem.

Contact Center Indicates that a Contact Center instance is running on the

server. A server can be running either a primary instance
(ACC-P) or a secondary instance (ACC-S) in a Contact
Center High Availability configuration. Red text indicates a
problem with the Contact Center instance.

License Indicates which server in the cluster acts as the Aeonix

License service. Red text indicates a problem with the
Aeonix License service.

Server Local Time Displays the Server Local Time. It is recommended that
servers in a cluster be set to synchronize their time with an
NPT Internet time server. By assigning the servers in a
cluster the same NPT Internet time server, they will be kept
in synchronization with each other.
See Table 3-2, Time and Date Parameters for a description of
setting the NPT Internet time server for an Aeonix server.

Total registered The total registered endpoints in the system (sum of the
endpoints EPs column).

Cluster Integrity Displays the status of the synchronization between the

servers in the cluster.
 The name of host server from which the integrity check
is being run is displayed. Which server is host effects the
view of the integrity situation.
 A server-to-server matrix table shows the
server-to-server statuses as known to the host server.

Server columns The columns in the Cluster Integrity table also show the
Clusters

servers in the cluster “to” which connectivity is known.

Server rows The rows in the Cluster Integrity table show the servers in
the cluster “from” which connectivity is known.
14

14-36 Maintaining Aeonix Aeonix Administration Manual

 Field Description

Server integrity The items in the table map all the possible server-to-server
table items connections in the cluster. In each server-to-server
relationship the status is represented as one of the
following color and text label combinations (as shown in the
legend below the table display).

Green Connected. The pair of servers are connected and running

in synch in the cluster.

Yellow Pend Connect. The pair of servers are disconnected from

each other, pending reconnection. The synchronization log
file is accruing and has not exceeded filesize limit.

Red Pend Connect. The pair of servers are disconnected from

each other, pending reconnection. The synchronization log
file has reached maximum filesize and is no longer being
written to.

Red Pend restart. The pair of servers are connected, but the
synchronization log file has reached maximum filesize and
is no longer being written to.

Red Pend restart at HH:MM. The pair of servers are connected

and running in synch. One of the servers has a request for
a restart pending.

Grey N/A. The identity diagonal through the matrix in which there
is no server-to-server relationship.

To investigate the reason of a server malfunction, you can use the tools
described in Server-based Maintenance Tools, page 14-79.

Cluster Information Page Actions

From this page, you can perform the following actions:

Table 14-10 Actions

Performed from the Action Button Description
Clusters

Cluster Information Page

Refresh Click Refresh to receive the most updated
display cluster information.
14

Aeonix Administration Manual Maintaining Aeonix 14-37

 Action Button Description
Activate Click to activate the defined endpoint
load registration load balance settings
balance (see Configuring the Cluster for Registration Load
Balancing, page 14-41).
Access Click Help to access online help.
online help
Clusters
14

14-38 Maintaining Aeonix Aeonix Administration Manual

  Restarting Servers After Network Connection Restored

In cluster environments a network failure may require a server or group of servers to

be restarted. The Cluster Status page displays the following pop-up screen when there
is a change in the status of the cluster, such that the auto-recovery mechanism cannot
be performed. In this case, you will be prompted to restart Aeonix servers according
to their connection status group.

Figure 14-8 Restart

Server/s Pop-up Screen

This pop-up will be displayed when logging in after the network connection
has been restored and auto-recovery cannot be performed. This pop-up will
reappear in the event not all the servers reconnected successfully to the
cluster and auto-recovery cannot be performed.

To recover a cluster:
Clusters

1 Select the connection status group for which you want to perform a restart:
 Red – To restart all the servers with connection status Red.
14

 Green – To restart all the servers with connection status Green.

Aeonix Administration Manual Maintaining Aeonix 14-39

  Both – To restart all the servers with connection status Red and Green.

Servers with Yellow connection status cannot be selected because they are
still disconnected from the server.

2 Click Restart; Aeonix restarts all the selected servers. This process may take a
few minutes.

If you click Cancel instead, the pop-up will be displayed the next time you log
in to Aeonix.
Clusters
14

14-40 Maintaining Aeonix Aeonix Administration Manual

  Configuring the Cluster for Registration Load Balancing

You can configure server location and capacity settings for endpoint registration load
balancing purposes. In addition, you can set the reconnection method to use in the
event one or more of the servers in a cluster requires a restart because it is not
synchronized with the other servers in the cluster or its functionality has been
compromised.

To configure Aeonix cluster server locations and capacities:

1 At the bottom of the navigation pane, click System. The pane displays the
System menus.
2 Select the Cluster menu, and then click Cluster Configuration. The Cluster
Configuration page is displayed listing all servers belonging to the cluster.

Figure 14-9 Cluster

Configuration Page

3 Specify the following parameters for each server in the cluster:

Table 14-11 Cluster

Server Parameters Field Description

Location Select the location of the server.

Clusters
14

Aeonix Administration Manual Maintaining Aeonix 14-41

 Field Description

Endpoint Capacity Enter the optimal number of endpoints that can register
to the server under normal conditions (when all the
other servers are connected and functioning properly).

Maximum Capacity Enter the maximum number of endpoints that can

register to the server. This must be larger than the
number entered for the EP Capacity parameter.
 Max. 3,000 registered endpoints per server

Click the icon to store the aeonixadmin user’s SSH password in the
Aeonix database, which is used when accessing this Aeonix server via an
SSH interface.

4 Select one of the following reconnection methods to use in the event one or
more of the servers in a cluster requires a restart because it is not synchronized
with the other servers in the cluster or because its functionality has been
compromised:
 Manually to be prompted (see Restarting Servers After Network Connection
Restored, page 14-39) as to when the restart will occur.
 Automatically to set a specific time of day for the restart from the Hour
and Minutes drop-down lists. (In this case, you will not be prompted for a
restart.)
 Schedule to set a specific day and time for the restart from the Day, Hour
and Minutes drop-down lists. (In this case, you will not be prompted for a
restart.)
5 Click Save.

 Changes are applied only after clicking the Start Load Balance on the
Cluster Status page.
 Prior to activating Load Balancing for systems that include Wave
Clusters

Gateway keysets, ensure that all the Aeonix servers are recognized in the
Wave Gateway (see Servers, page 10-11).
14

14-42 Maintaining Aeonix Aeonix Administration Manual

  Setting Server for ACD and Hunt Services

As a distributed solution, the Aeonix ACD and Hunt services are designed to function
in a clustered environment. This means that call center agents attending calls for the
same campaign can be logged in at any server within the cluster. The Aeonix ACD and
Hunt service itself, however, must be run from one specific server. Main and backup
servers for the ACD and Hunt services can be configured from the ACD & Hunt
Service Page.

To set the default server on which the ACD and Hunt services are run:
1 At the bottom of the navigation pane, click System. The pane displays the
System menus.
2 Select the Cluster menu, and then click ACD & Hunt Service. The ACD and
Hunt Service page is displayed.

Figure 14-10 ACD & Hunt

Service Page

3 From the Service runs by default at drop-down list, select the server on
which the ACD and Hunt services run by default. Then, from the adjacent
drop-down list, select the back up server.

In a single server environment, the name of the server is displayed and

cannot be changed (anxStandalone by default).

4 Click Save.
5 Click Restart. A confirmation box is displayed.
6 Click Yes. After Aeonix has been restarted, the system informs you whether
the operation was successful, or specifies that the server could not be restarted.
Clusters
14

Aeonix Administration Manual Maintaining Aeonix 14-43

  Server Settings for the Aeonix Contact Center Service

The Aeonix Contact Center is designed to function in a clustered environment in order

to support High Availability failover modes. During the Aeonix installation process on
a server, the Aeonix Centact Center module is always installed, and by default is
Inactive. With the appropriate purchased licenses, one or two Aeonix Contact Center
modules in a cluster can be activated to run. Running one Aeonix Contact Center
module constitutes the Standalone Mode. Running two Aeonix Contact Center
modules in a cluster constitutes a High Availability Cluster Mode implementation. In
either case, one Aeonix Contact Center service must be run as the Primary server.
In the case of a High Availability implementation with two Aeonix Contact Center
modules running in a cluster, the Primary Aeonix Contact Center synchronizes the
database from the Primary to the Secondary server, which passively monitors all
Aeonix Contact Center calls, as well as supervisor and agent clients. In the event that
the Primary server goes down, the Secondary server takes over as the Active server,
allowing waiting calls to be kept in queue without disruption.
With multiple servers in a cluster, the Aeonix Contact Center High Availability feature
has several possible modes, states, transitions, and outcomes. Administrators need to
be aware of these so that they can plan and execute the correct remediation, after the
fact of a High Availability transition, for any type of failure within the Aeonix Contact
Center High Availability cluster that may have caused the transition.
The following figure shows the basic Aeonix Contact Center operational “modes”
which are based on the network topology as the Aeonix Contact Center modules see it.
Clusters
14

14-44 Maintaining Aeonix Aeonix Administration Manual

Figure 14-11 Aeonix
Contact Center High
Availability Modes

In Standalone Mode, a single Aeonix Contact Center module is Active and provides
the service without High Availability failover protection. All other Aeonix servers in
Clusters

the cluster do not have their installed Aeonix Contact Center modules activated -- the
modules are Inactive.
14

Aeonix Administration Manual Maintaining Aeonix 14-45

 In High Availability Cluster Mode, two Aeonix servers have their Aeonix Contact
Center modules activated. For example, on the Primary Server, the Aeonix Contact
Center module is Active, and on the secondary Server, the Aeonix Contact Center
module is Passive (the reverse can also occur with Passive on the Primary server and
Active on the Secondary server). The Passive module tracks the activity of the Active
module, waiting to serve as the Primary module if a failover event occurs.
Island Mode is a unique failover state that can be entered if a particular kind of failure
occurs in the network topology. If the Active and Passive modules become unable to
communicate with each other on the network, an Unknown status is reflected in each
module with regard to the other module. In this case, both modules operate as Active
modules, and routing of Agent and Visor traffic to the Aeonix Contact Center modules
around the broken connection is handled by the Aeonix platforms on the servers in the
cluster.
The following table summarizes the modes, transition events, High Availability
recovery outcomes, and remediation tasks that can occur in an Aeonix Contact Center
High Availability server cluster.

Table 14-12 Aeonix

Contact Center HA
Modes

Mode Transition Event High Availability State Remediation Tasks

Standalone Start Prim. Active

Prim. Fails No service Restart Prim.

Cluster Start Prim. Active, Second. Passive

Mode Prim. Fails Second. becomes Active Restart Prim. / Switch
Second. Fails Prim. continues Active Restart Second.

Island Mode Start Prim. Active, Second. Passive

Network Connectivity Fails Prim Active, Second. Active System auto-restores

In the case of Cluster Mode in which the Active Aeonix Contact Center module fails,
the Passive module takes over and becomes the Active module. When the other
module is restarted, it joins the cluster now as Passive. In order to restore the original
configuration, the administrator must click the Switch to active button as shown in
Figure 14-11.
Clusters

In the case of Island Mode, where both Aeonix Contact Center modules become
Active because of a network connectivity failure, the original configuration is
14

automatically restored once the network connectivity failure is remediated. Any

14-46 Maintaining Aeonix Aeonix Administration Manual

 configuration changes made to the secondary server during Island mode will be lost
and overwritten with the database of the primary server.

To set the servers on which the Aeonix Contact Center service is run:
1 At the bottom of the navigation pane, click System. The pane displays the
System menus.
2 Select the Cluster menu, and then click Aeonix Contact Center Service. The
Aeonix Contact Center Service page is displayed.

Figure 14-12 Aeonix

Contact Center Service
Page

In standalone systems, the secondary server option is not displayed.

3 From the Primary drop-down list, select the Aeonix server on which the
Aeonix Contact Center service runs.
Clusters
14

Aeonix Administration Manual Maintaining Aeonix 14-47

 Define the primary server as the server where the main database resides (usually the
main office of your organization) since in the event of a cluster failure the database of
the secondary server is overwritten with the database of the primary server.
Similarly, if you later want to select a different Aeonix server as the primary server, back
up the database of the current primary server, and then restore the database to the new
primary server, since current Aeonix Contact Center data is not automatically copied
from one server to another.

4 From the Secondary drop-down list, select the secondary Aeonix server used
for high availability purposes.
5 Click Save and wait a few minutes for the configuration changes to take effect.

Figure 14-13 Aeonix

Contact Center Service
Configured (example)

6 Configuration Status: OK indicates that both servers have been configured

identically.

If the configuration does not succeed, the reason is displayed instead. See
Table 14-13 below for a list of possible errors. Click Reconfigure and wait
until the system configures the Aeonix Contact Center again. If the error
persists, contact customer support for assistance.

A circle icon to the left of each server indicates the Aeonix Contact Center
connection status to the Aeonix server:
 Green – Aeonix Contact Center is running and connected to the Aeonix
server
Clusters

 Red – Aeonix Contact Center is disconnected from the Aeonix server

14

14-48 Maintaining Aeonix Aeonix Administration Manual

 If the connection status is Red (Failure), click Restart to restart the Aeonix
Contact Center service. If the error persists, contact customer support for
assistance.

The connection status also indicates which server is the Active server and
which is the Passive server, which is the server that passively monitors all
Aeonix Contact Center calls.

To set the other server as the active server, click Switch to active.

In the event that either the primary or secondary Aeonix Contact Center server
malfunctions, changes to the Aeonix Contact Center configuration cannot be performed.
Instead, in order to retain high availability, the following must be performed via the Aeonix
Configuration Wizard:
 If the Secondary server malfunctions - assign a third server as the secondary server and
remove the malfunctioning server from the cluster
 If the Primary server malfunctions - replace the primary server with the secondary server,
assign a third server as the secondary server, and then remove the malfunctioning server
from the cluster

Clusters
14

Aeonix Administration Manual Maintaining Aeonix 14-49

 Table 14-13 Possible
Configuration Errors Configuration Status Messages

The primary Aeonix Contact Center service at <xxx> could not be stopped.

The secondary Aeonix Contact Center service at <xxx> could not be stopped.

The primary Aeonix Contact Center service at <xxx> could not be started.

The secondary Aeonix Contact Center service at <xxx> could not be started.

The Aeonix Contact Center backup file at <xxx> could not be created.

The Aeonix Contact Center tar.gz backup file at <xxx> could not be created.

The MYSQL service on the primary Aeonix Contact Center server <xxx> could
not be stopped.

The MYSQL service on the secondary Aeonix Contact Center server <xxx>
could not be stopped.

The MYSQL service is not running on the secondary Aeonix Contact Center
server <xxx>.

The MYSQL service is not running on the primary Aeonix Contact Center
server <xxx>.

No secondary Aeonix Contact Center server has been detected.

An SSH connection could not be established at <xxx>.

The copy file process to the secondary Aeonix Contact Center server <xxx>
did not succeed.

Replication failed The MYSQL configuration replication process did not

succeed.

The input parameter of the replication setup is invalid.

The primary and secondary Aeonix Contact Center servers are running
different Aeonix Contact Center versions.

Configuration failed, timeout exceeded.

Clusters
14

14-50 Maintaining Aeonix Aeonix Administration Manual

  Enabling and Configuring High Availability

You can enable the High Availability feature to work on servers both within and
among Aeonix cluster locations.

High Availability requires higher bandwidth capacities. Ensure that your Aeonix network
meets bandwidth requirements before enabling this feature. Refer to the Aeonix
Installation - Hardware and Software Guidelines for details (see Related Documentation,
page 1-17).

If some server suffers a failure and the High Availability feature is enabled, the
workload of the failed server is distributed among the other servers. This allows
ongoing Tadiran SIP phone calls and call options (such as transfer, hold, and retrieve)
to continue unaffected in the event of a failure on the server where the phone is
originally registered on.

In order for the High Availability parameters to take effect, these phone must
be configured via their phone web page. Refer to the User Guide of the
relevant phone for details (see Related Documentation, page 1-17).

In addition, you can configure server locations for High Availability purposes,
including which locations backup the other, the timeout duration for servers within the
same location, and the timeout duration between servers in different locations. The
timeout specifies how long the corresponding server waits before initiating the
failover process.

To enable High Availability between locations:

1 At the bottom of the navigation pane, click System. The pane displays the
System menus.
2 Select the Cluster menu, and then click High Availability. The High
Availability page is displayed listing all servers belonging to the cluster.
Clusters
14

Aeonix Administration Manual Maintaining Aeonix 14-51

 Figure 14-14 High
Availability Page

3 Select Enable High Availability to enable this feature to work on servers

within the same Aeonix cluster location.

Green indicates that High Availability is also enabled to work among the
other defined Aeonix cluster locations; Red indicates that it is not enabled
among these server locations; Grey indicates a cell in the table where a high
availability setting is not applicable.

4 At the bottom of the page, click Save.

To edit High Availability settings:

1 Click Edit next to the relevant location. A dialog box is displayed for
specifying High Availability settings for the selected location.

Figure 14-15 High

Availability Configuration
Page
Clusters

2 By default, the Timeout within the location is set to 7 seconds. To make

changes:
14

 Select Override default

14-52 Maintaining Aeonix Aeonix Administration Manual

  In the adjacent box, enter the new High Availability keep-alive timeout
value for servers within this location

The minimum value of this field is 1 second. However, it is not recommended

to set a value lower than the default value.

3 For each Aeonix cluster location, set or view the high availability parameters
in the following table:

Table 14-14 High

Availability Parameters Field Description

Enabled If selected, high availability is enabled with this location.

Timeout The timeout duration between locations (by default 10

seconds). To make changes, select Custom from the
drop-down list, and then enter the required timeout value in
the adjacent box.

4 At the bottom of the page, click Save.

5 Repeat the above procedure as required to configure High Availability settings
for the other server locations.

Clusters
14

Aeonix Administration Manual Maintaining Aeonix 14-53

Clusters
14

14-54 Maintaining Aeonix Aeonix Administration Manual

 14.4 Data Backup and Restoring via Web

The configuration of an Aeonix system, including the definition of users, trunk

groups, phones, and trunks, is stored in a dedicated, continuously updated database.
In clusters with multiple Aeonix servers, the servers are kept synchronized and each
contain a database of the whole system. Restored databases, as well as parameters set
for scheduled backup, are replicated to all servers as soon as they are running the
Aeonix service.
The Aeonix Web Portal enables administrators to back up or restore this database from
their workstations. The Portal provides a convenient interface for:
 Creating a Backup, page 14-56
 Restoring the Database with a Backup, page 14-57
 Setting up a Schedule for Automatic Backup, page 14-58

Database backup and restore utilities are also available on each Aeonix
server and described in Aeonix Server Database Export and Import Procedures,
page 14-83.
The backup and restore procedures must be performed while Aeonix is
running.

Data Backup and Restoring via Web

14

Aeonix Administration Manual Maintaining Aeonix 14-55

  Creating a Backup

A backup of the Aeonix database can be created at any time. Using HTTP, the system
downloads the data in zipped XML format and saves the file at a destination specified
by the administrator. The backup file name includes the name of the server and a
timestamp.

To create a backup of the Aeonix database:

1 At the bottom of the navigation pane, click System. The pane displays the
System menus.
2 Select the Backup/Restore menu, and then click Create backup. The Create
Backup page is displayed.
3 Click Create. The backup creation process can take up to several minutes,
depending on the system configuration.
4 At the end of a successful backup process, click Download File. (If the
process fails, a detailed error message is displayed.)
A standard File Download dialog box is displayed.
5 Click Open to view the contents of the backup file, or Save to store the file at
a specified destination.
Data Backup and Restoring via Web
14

14-56 Maintaining Aeonix Aeonix Administration Manual

  Restoring the Database with a Backup

Restoring the Aeonix database causes the Aeonix service to be restarted on all Aeonix
servers in the system. Restarting Aeonix disconnects all ongoing calls in the system
and discards any unsaved changes in entity definitions.

The database restoring procedure is used for repairing a corrupted Aeonix database, or
for importing a database from another Aeonix system. In clustered Aeonix systems
with multiple servers, the restored database contents are replicated to each server if or
as soon as it is up and running.
To ensure reliable system operation, the restore procedure validates the backup file
before importing it into the database. The validation makes sure the file format and
structure are correct, and verifies database integrity. It also looks for the database
version and automatically performs version upgrade if necessary.
Immediately before restoring the database, the system backs up the database and saves
it in the default backup directory. If the restore procedure fails, the backup is imported
back into the database.

The database restoring procedure requires all servers in a cluster to be

synchronized. If the contents in the databases of the servers differ, the
replication process will fail.
The restoring procedure will delete the current database after replacing it.
For traceability purposes, it is recommended to create a backup prior to
restoring (see Creating a Backup, page 14-56).

Data Backup and Restoring via Web

To restore the Aeonix database:
1 At the bottom of the navigation pane, click System. The pane displays the
System menus.
2 Select the Backup/Restore menu, and then click Restore. The Restore page is
displayed.
14

Aeonix Administration Manual Maintaining Aeonix 14-57

 Figure 14-16 Restore
Page

The page warns you of the impact database restoring might have on system
operation. It also lists the numbers of currently active calls, all of which will
be disconnected by the restoring procedure.
3 To restore the database with a manually created backup file, select Upload
backup file, and then click Choose File to specify the destination of the file.
Select the required XML file, or a ZIP file containing the required file. The
system supports the uploading of remote files via HTTP.
4 To restore the database with an automatically created backup file, select Use
scheduled backup file and click the relevant file in the table.
5 Click Restore. The restoring process can take up to several minutes,
depending on the system configuration. Once the database has been restored,
the Restore button changes to Restart.
6 Click Restart to restart the Aeonix service on all servers and re-log in to the
Aeonix Web Portal. The content of the selected backup file will be replicated
to all servers in the cluster.
Data Backup and Restoring via Web

If the system could not restore the database, an error message is displayed.
Depending on the reason of the failure, Aeonix may have to be restarted.

 Setting up a Schedule for Automatic Backup

Scheduled Backup programs the Aeonix system to automatically back up the database
14

on a regular basis. This section describes how to configure the automatic backup

14-58 Maintaining Aeonix Aeonix Administration Manual

 schedule, including backup timing and backup file destination. In clustered systems,
the destination can be defined individually for each Aeonix server.

By default, every night at 03:00 AM, each Aeonix server automatically backs
up its database in an XML file, compresses this file, and stores it under
/home/aeonixadmin/aeonix/local/backup. If more than 60 backup files are
stored in this folder, the system deletes the oldest files.

To configure the automatic backup schedule:

1 At the bottom of the navigation pane, click System. The pane displays the
System menus.
2 Select the Backup/Restore menu, and then click Set Backup Schedule. The
Scheduled Backup page is displayed.

Figure 14-17 Scheduled

Backup Page

For each server, the Scheduled Backup page lists the last backup and the
destination of the backup file, if created. Failed backup attempts are displayed
in red.

Data Backup and Restoring via Web

3 Set the backup schedule fields as described in the following table.

Table 14-15 Backup

Schedule Parameters Field Description

Backup time The hour at which the backup is performed

Back up The daily interval at which the backup is performed

every...day(s)
14

Starting from The date of the day from which the backup schedule is
applied

Aeonix Administration Manual Maintaining Aeonix 14-59

 4 If necessary, specify the destination at which the backup files are saved on the
servers, as described in Specifying the Scheduled Backup Destination, page 14-61.
The default backup destination can be specified for each Aeonix server in the
system.

You can back up the database at any moment and have the backup file
saved at the specified scheduled backup destinations. Click Backup Now to
instantly back up the database at the scheduled destinations.

5 Click Save to save the configuration.

Data Backup and Restoring via Web
14

14-60 Maintaining Aeonix Aeonix Administration Manual

 Specifying the Scheduled Backup Destination
By default, the system saves scheduled backup files in a preset local directory on each
connected Aeonix server. For any of these servers, you can replace this directory by
any accessible local or remote destination. You can also specify a common destination
by defining a backup destination for one server and copy it to the other servers.

To define the scheduled backup file destination for a server:

1 On the Scheduled Backup page (see Figure 14-17), click the relevant server in
the table. The scheduled backup fields are displayed for the selected server.

Figure 14-18 Scheduled

Backup Fields for Server

2 Select Perform Backup if necessary. If this check box is cleared, no backup

file will be created for this server.
3 To save the backup file on the server, select Save locally on disk and specify
the backup destination path in the Location field.
4 To save the backup file on a remote server using Secured File Transfer
Protocol, select Use SFTP and set the fields described in the following table.

Data Backup and Restoring via Web

Table 14-16 Remote
Backup Destination Field Description
Parameters for Aeonix
Server Host The IP address of the remote destination server

Port The port the remote server uses for SFTP transmission
(Default: 22)

Remote directory The path and directory where the file is to be saved on the
remote server

User name The user name SFTP requires for logging in to the remote
14

server

Aeonix Administration Manual Maintaining Aeonix 14-61

 Field Description

Password The password SFTP requires for logging in to the remote

server

Click Check Connection to verify that Aeonix can connect to the remote
server.

The connection can fail for various reasons, for example:

 The remote server is down and has to be restarted.

 Remote backup destination fields contain incorrect values and have to be

redefined. See the table above for a description of the fields.
Make the required corrections and click Check Connection again.

5 To use the specified destination for the scheduled backup files of all servers in
the cluster, click Apply to All Servers.
6 Click Save.
Data Backup and Restoring via Web
14

14-62 Maintaining Aeonix Aeonix Administration Manual

 14.5 Upgrading Aeonix via Web

This section describes how to download and upgrade the version of Aeonix, ACC, and
SeaMail using the Aeonix Upgrade feature in the Aeonix Web Portal.

Upgrading via web is not permitted in an A4C instance.

 Upgrade Preparation

Prior to upgrading to Aeonix:

1 Be sure you have dedicated, 64-bit platform Aeonix servers that comply with
the minimum requirements, as specified in Aeonix Installation Hardware and
Software Requirements Version 3.2

The Aeonix servers running on a 32-bit OS must be upgraded to 64-bit

before the Aeonix version upgrade can be performed. If you are upgrading
from Aeonix 2.5, or from 32-bit servers, contact your dealer or Tadiran
Support for additional details.

2 Backup the old Aeonix, ACC, and SeaMail, and their databases, for recovery
purposes. See the application note AN1801-001 Consistent Full Backup of
Aeonix Product Ecosystem for instructions and use-cases of full backups of the
Upgrading Aeonix via Web
entire suite of Aeonix modules.
3 Download the Aeonix update file from the Tadiran website Partner Page. The
Update feature can only operate with auhorized Tadiran update files. These
files are .zip archives that have the following naming convention:
Aeonix_Update_x.x.x.zip
where each “x” is a part of the version number. For example:
14

Aeonix_Update_3.0.678

Aeonix Administration Manual Maintaining Aeonix 14-63

 The .zip Update file contains updates for Aeonix, ACC, and SeaMail.
4 Familiarize yourself with the Aeonix Administration Manual.

 Aeonix Upgrade Procedure

To use the Upgrade feature:

1 From Aeonix Admin > System > Backup Restore > Create Backup, create,
download, and store a backup of the Aeonix database for recovery purposes.
To backup ACC and SeaMail refer to ACC Administration Guide and SeaMail
Administration Guide for their update features. Also refer to the application
note AN1801-001 Consistant Full Backup of Aeonix Product Ecosystem for
instructions and use-cases for full backups of the entire suite of Aeonix
modules.
2 Copy the Aeonix .zip upgrade file that you downloaded from the Tadiran
Partner Page (website) to your workstation or to the Aeonix Repository
directory on one of the Aeonix servers (home\aeonixadmin\upgrade).
3 Open Aeonix Admin > System > Maintenance > Upgrade as shown in the
following figure.
Upgrading Aeonix via Web
14

14-64 Maintaining Aeonix Aeonix Administration Manual

Figure 14-19 Upgrade
Page

4 Select the location of the Aeonix Upgrade package on either the local client
PC, or on the host Aeonix server in as noted in Step 2.
a Local PC - If the file resides on your local PC choose this option. Use the
file navigation field to navigate to and select the file on your PC. You can
upload the file to the host server, and then run the upgrade later, by clicking
on the Upload button. Or you can upload the file and start the upgrade
process by clicking on the Upload & Upgrade button, after selecting the
servers to be upgraded.
b Aeonix Repository - If the file already resides in the repository directory
on the host server, choose this option. The Upload and Upload & Upgrade

Upgrading Aeonix via Web

buttons are replaced by a single Upgrade button. The PC navigation field is
replaced by a file selection field. Select the file from the list of files in the
repository.
5 Select the servers to be upgraded. There are several considerations for how to
upgrade an Aeonix server cluster.
a Choose one server database to be used as the source for all upgraded
servers.
14

Aeonix Administration Manual Maintaining Aeonix 14-65

 b With a distribution of SIP phones registered as primary and secondary on
different servers (for failover), choose all the servers with primary phone
registrations and update them in the first pass.
c In the second pass upgrade all servers with secondary phone registrations.
Keep the same source database assignment from the first pass. (Best
Practice: Keep a clean configuration of primary phone registrations on
primary servers, and secondary phone registrations on secondary servers.)
d Alternatively, you can update the servers one at a time. This will preserve
asymmetrical phone registrations intact. Always keep the same source
database assignment.
6 Start the upgrade process.
a Local PC - If the Aeonix Update file resides on the local client PC, click
Upload & Upgrade.
b Aeonix Repository - If the file resides in the host server Aeonix Repository
directory, click the Upgrade button.

 Status Messages

As the Upload or the Upgrade progresses, Aeonix displays status message as shown
in the following figure.
Upgrading Aeonix via Web
14

14-66 Maintaining Aeonix Aeonix Administration Manual

Figure 14-20 Upgrade
Page - Status Messages

 Logs

The Upgrade process also records status in an Aeonix system log file. Use the Log
Download feature to download an Aeonix system log files archive. See Downloading
Logs via Web beginning on page 14-71. In the log file archive, the Upgrade log file can
be found at:
AnxLogs/home/aeonixadmin3.2/aeonix/logs/web/anxConfSys.log.[sessionID]

Upgrading Aeonix via Web

14

Aeonix Administration Manual Maintaining Aeonix 14-67

Upgrading Aeonix via Web
14

14-68 Maintaining Aeonix Aeonix Administration Manual

 14.6 Restarting Aeonix via Web

This section describes how to use the Aeonix Web Portal to restart the Aeonix service
on a stand-alone Aeonix server, or on one or more servers belonging to the same
Aeonix cluster. You can also directly restart Aeonix on a server without using the
Portal. For instructions, see Restarting Aeonix from the Server, page 14-81.

Restarting the Aeonix service disconnects all ongoing calls in the system and discards
any unsaved changes in entity definitions.

Aeonix can only be restarted on operating servers.

To restart one or more Aeonix servers via the Web Portal:

1 At the bottom of the navigation pane, click System. The pane displays the
system options.
2 Select the Restart category, and then click Restart in the Restart menu. The
Restart Server page is displayed.

Figure 14-21 Restart

Server Page

Restarting Aeonix via Web

3 Servers to Restart is only displayed for Aeonix clusters. If displayed, select

the server or servers which should be restarted.
14

4 Click Restart. A confirmation box is displayed.

Aeonix Administration Manual Maintaining Aeonix 14-69

 5 Click Yes. After Aeonix is restarted, the system informs you whether the
operation was successful, or specifies the server(s) that could not be restarted.
Restarting Aeonix via Web
14

14-70 Maintaining Aeonix Aeonix Administration Manual

 14.7 Downloading Logs via Web

This section describes how to use the Aeonix Web Portal to set System Logs
parameters and to download the System Log files..
The Aeonox Logs page is accessed from Aeonix Admin > System > Maintenance >
Aeonix Logs as shown in the following figure.

Figure 14-22 Aeonix

Logs > Configure Page

Downloading Logs via Web

Click on the Create Dump banner to expand or collapse the Packet Sniffer and
Memory Dump details.
14

Aeonix Administration Manual Maintaining Aeonix 14-71

 Table 14-17 Aeonix Logs
Configuration Fields Field Description

New log If a log collection .zip file exists on the Aeonix server due to a
collection previous Collect only run (see below), the Aeonix Logs
page is displayed with New log collection unchecked, and
the log collection file displayed as available for download to
the Local PC or an SFTP server. To proceed with a new log
collection, click the New log connection checkbox.
If there is no log collection .zip file on the Aeonix server when
you open the Aeonix Logs page, the page will be displayed
will all fields available for specifying the new log collection.

Create Dump Click on the Create Dump banner to expand or collapse the
Packet Sniffer and Memory Dump details.

Packet Capture Select the servers for which PCAP (Wireshark) network
(Sniffer) packet capture (sniffer) will be done.

Memory Dump Select the servers for which Java memory dump will be done.
(Java)

Start Start the network packet capture and memory dump

operation (one shot).

Stop Stop the network packet capture operation.

NOTE: This has no effect on the memory dump operation

which will continue to completion.

NOTE: The network packet capture files and the memory

dump files are stored in the log files area of each
respective server that the processes are run on. To get
these files, download the log files for the respective
servers as described in the following table entries.

Collect logs Choose the dates when the log collecting will be active.
created between Dates in the future will be interpreted as “up to the current
moment” of the collection run.
Downloading Logs via Web

Time zone Choose the time zone to apply to the dates for the log
collection. Times in the future will be interpreted as “up to the
current moment” of the collection run.
14

14-72 Maintaining Aeonix Aeonix Administration Manual

 Field Description

Of the following Choose the Aeonix components for which logs will be
components collected:
 Aeonix
 SIP
 Aeonix Contact Center
 Aeonix Contact Center core
 SeaMail
Select all - selects all the components.
Clear all - clears all the component selections.

From servers Choose the servers from which logs will be collected.
Select all - selects all the components.
Clear all - clears all the component selections.

Compress the Enter a suffix to be appended to the filename which has the
resulting files into form of:
one ZIP file with AnxLogs_YYY-MM-DD_HH-MM-SSsuffix.zip
name suffix where “suffix” is the string that you specify.

Transfer the log Specify the output target location:

collection file to  Local PC - after the collection of the log files, you will be
prompted with a dialog about where to save the .zip file on
the client PC.
 SFTP Server - after the collection of the log files, the .zip
file will be automatically uploaded to the specified SFTP
server:
- Host
- Port
- Username
- Password
- Check Connection (tests the specified SFTP connection)
 Collect only - the .zip file is placed on the Aeonix server
in the archive directory /aeonixadmin. The file is
overwritten on any subsequent Collect only run. The file
can be downloaded by revisiting the main Aeonix Logs
page.
Downloading Logs via Web
Date and time the Enter the date and time the problem occurred. The text will
problem occurred be included as a descriptor field at the top of the main
problem-info.txt file in the .zip archive.

Time zone Enter the time zone for the date and time the problem
occurred. The text will be included as a descriptor field at the
top of the main problem-info.txt file in the .zip archive.
14

Aeonix Administration Manual Maintaining Aeonix 14-73

 Field Description

Description Enter a small text that describes the problem being analyzed.
The text will be included as a descriptor field at the top of the
main problem-info.txt file in the .zip archive.

Start Start the collection of the log files.

When you click the Start button, the status of the log files collection process is
displayed as shown in the following figure.

Figure 14-23 Aeonix

Logs Status In Progress
Display
Downloading Logs via Web

When the collecting process has completed, the status is indicated as shown in the
following figure.
14

14-74 Maintaining Aeonix Aeonix Administration Manual

Figure 14-24 Aeonix
Logs Status Completed
Display

Click the Back button to go back to the Aeonix Log page and specify a download
target location.

Downloading Logs via Web

14

Aeonix Administration Manual Maintaining Aeonix 14-75

 If a log collection file is currently stored on the Aeonix server when you open the
Aeonix Logs page, the file is displayed for download as shown in the following figure.

Figure 14-25 Aeonix

Logs > Transfer Log
Collection File- Local PC

Choose Local PC or SFTP Server from the drop down list. If you choose an SFTP
server, the fields for specifying the SFTP server are displayed as shown in the
following figure.
Downloading Logs via Web
14

14-76 Maintaining Aeonix Aeonix Administration Manual

Figure 14-26 Aeonix
Logs > Transfer Log
Collection File - SFTP

Enter the fields as detailed in Table 14-17. Click the Start button to start the download,
or click the New log collection checkbox to define a new log collection run.

Downloading Logs via Web

14

Aeonix Administration Manual Maintaining Aeonix 14-77

NOTES:
 14.8 Server-based Maintenance Tools

This section describes maintenance tools and procedures that are not included in the
Aeonix Web Portal, but are available on Aeonix servers. System maintenance can be
performed locally via the Aeonix server or remotely by using any standard SSH
(Secure Shell) command line utility.
Aeonix is installed on a dedicated server and runs on CentOS Linux (UNIX).

To learn how to install and configure Aeonix on the server, refer to the
Aeonix Installation Manual (see Related Documentation, page 1-17).

Maintenance tasks are performed through the command line interface.

This section describes built-in and external maintenance options that can ensure the
proper operation of the Aeonix system:
 Accessing the Aeonix Server, page 14-79
 Restarting Aeonix from the Server, page 14-81
 Checking the Aeonix Service Status, page 14-82
 Aeonix Server Database Export and Import Procedures, page 14-83
 Aeonix Debugging Commands, page 14-85
 Log Files, page 14-90
 Ethereal Network Analyzer, page 14-92

Server-based Maintenance Tools

In addition, this section includes some example scenarios in which the described
maintenance options are used (see Aeonix Troubleshooting Examples, page 14-94).

 Accessing the Aeonix Server

This section describes the following procedure:

 Logging in to the Aeonix Server, page 14-80—required after reboot and when
14

accessing a remote server

Aeonix Administration Manual Maintaining Aeonix 14-79

 Logging in to the Aeonix Server

To log in to the Aeonix server:

1 At the end of the login as command line prompt, type a user name (the
default is root) and press ENTER. The system prompts you for the password.
2 Type the password (the default is 123456) and press ENTER. After successful
authentication, the system displays the last login details and logs you in.
Server-based Maintenance Tools
14

14-80 Maintaining Aeonix Aeonix Administration Manual

  Restarting Aeonix from the Server

The Aeonix service can be restarted, on any or all servers in a cluster, via the Aeonix
Web Portal (see Upgrading Aeonix via Web, page 14-63).
Aeonix can also be directly restarted on a server, as described in the following
procedure. (The service aeonix start command is also used to start Aeonix
for the first time.)

Restarting the Aeonix service disconnects all ongoing calls in the system and discards
any unsaved changes in entity definitions.

To restart Aeonix:
1 Log in to the Aeonix server if necessary (see Accessing the Aeonix Server,
page 14-79).
2 At the end of the command line prompt, type service aeonix stop and
press ENTER.
3 Type service aeonix start and press ENTER.
Upon successful startup, the terminal window displays the messages Starting
Aeonix service...OK
and (for conference call support) Starting aeonixMP service...OK.

Server-based Maintenance Tools

14

Aeonix Administration Manual Maintaining Aeonix 14-81

  Checking the Aeonix Service Status

This procedure allows you to view the status of the Aeonix service. It is not intended
for restarting the service.

Do not restart Aeonix from the Service Configuration dialog box, as this can cause
unwanted system resets. Instead, restart Aeonix as described in Upgrading Aeonix via Web,
page 14-63 or Restarting Aeonix from the Server, page 14-81.

To view the Aeonix service status:

1 Log in to the Aeonix server if necessary (see Accessing the Aeonix Server,
page 14-79).
2 At the end of the command line prompt, type startx and press ENTER. The
desktop screen of Aeonix.
3 Click the Start icon and then select System>Services. The Service
Configuration dialog box is displayed.

Figure 14-27 Service

Configuration Dialog Box
Server-based Maintenance Tools

4 In the list of services, scroll down to the aeonix service and select it. Do NOT
clear the check box to its left.
14

The status of each Aeonix module is displayed.

14-82 Maintaining Aeonix Aeonix Administration Manual

  Aeonix Server Database Export and Import Procedures

Aeonix database export (backup) and import (restore) can be performed via the
Aeonix Web Portal (see Data Backup and Restoring via Web, page 14-55), or on any
server belonging to an Aeonix cluster as described in the following procedures.
 Export Procedure, page 14-84
 Import Procedure, page 14-84

Export and import procedures must be performed while Aeonix is running.

Server-based Maintenance Tools

14

Aeonix Administration Manual Maintaining Aeonix 14-83

 Export Procedure
The export procedure generates an XML file containing all data related to users,
phones, aliases, and user restrictions.

To export the Aeonix database:

1 Log in to the Aeonix server if necessary (see Accessing the Aeonix Server,
page 14-79).
2 At the end of the command-line prompt, type
./aeonix_exportDB.sh <DataBase>
while replacing <DataBase> with the path and the file name of the XML
file to be generated.

If the exported XML file is used for backup purposes, store it at a secure
location.

3 Press ENTER. The XML file is created.

Import Procedure

The import procedure erases all previous Aeonix data on the server.

To import a previously exported Aeonix XML file to the Aeonix database:

1 Log in to the Aeonix server if necessary (see Accessing the Aeonix Server,
page 14-79).
2 At the end of the command-line prompt, type:
Server-based Maintenance Tools

./aeonix_importDB.sh <DataBase>
while replacing <DataBase> with the path and the file name of the XML
file to be imported.
3 Press ENTER.
4 Restart Aeonix (see Restarting Aeonix from the Server, page 14-81). The updated
data is available for display in the Aeonix Portal.
14

14-84 Maintaining Aeonix Aeonix Administration Manual

  Aeonix Debugging Commands

This section describes the available debugging commands:

 aeonix_tevent.sh [options], page 14-86
 aeonix_mapUser.sh [options], page 14-88
 aeonix_countCalls.sh, page 14-89
 General Linux Commands, page 14-89

Use the --help option to display a description about the current command.
Help information is also displayed whenever you type an incorrect
expression.

Server-based Maintenance Tools

14

Aeonix Administration Manual Maintaining Aeonix 14-85

 aeonix_tevent.sh [options]
Use the aeonix_tevent.sh command to trace Aeonix events. For each event, a
message describing the event is displayed in real time on the screen. The following
example traces a conversation between two phones.

Figure 14-28 Traced

Aeonix Events

You can add the following options to the command:

Table 14-18 aeonix_tevent

.sh [options] Option Description
Server-based Maintenance Tools

-B n Displays the last n messages before continuing to display current

messages.

-d Displays detailed messages

14

14-86 Maintaining Aeonix Aeonix Administration Manual

 Option Description

-e regex Displays messages related to the phone or phones specified in the

regular expression regex

NOTE: A regular expression is a wildcard pattern used by Unix for

representing a sequence of characters. For example, the option
-e 02:33 displays all events relating to endpoints with ID
values containing the sequence 02:33.

NOTE: You can specify multiple regex values. Separate them using the
characters \| (a backslash followed by the pipe symbol)
without spaces.

-l n Displays the last n messages and exits

-s Displays messages related to the service specified in the service

service parameter. Specify the services as in the following table

Table 14-19 Service

Options for Debugging Service Parameter Debugged Service

CG Call group

CTI Computer Telephony Integration (CTI)

ACD Automatic Call Distribution (ACD)

PB Playback (for Music on Hold)

MC Multipoint Controller service (for

conference calls)

GAP Group alerting call pickup

PQPP Page queue park/pickup

Server-based Maintenance Tools

DAP Direct alerting call pickup

DPP Direct park/pickup

CO Camp-on

You can define multiple services in the service parameter. Separate them
using | (the pipe symbol) without spaces.
14

Aeonix Administration Manual Maintaining Aeonix 14-87

 aeonix_mapUser.sh [options]
Use the aeonix_mapUser.sh command to display a list of phone IDs for each
specified user. By default, the following is displayed:
 All phones with which the user is associated as the default user
 All phones through which the user is logged into Aeonix
You can add the following options to the command:

Table 14-20 aeonix_mapU

ser.sh [options] Option Description

-u users The users to be monitored. This option must be defined for at least
one user.

NOTE: You can define multiple users in the users parameter.

Separate them using | (the pipe symbol) without spaces

-d Displays only the phones for which the specified user is defined as
the default user.

-l Displays only the phones through which the user has logged into the
Aeonix.

-s Displays messages related to the service specified in the service

service parameter. Specify the services (except for the MC conference
service) as described in Table 14-19 on page 14-87.

NOTE: You can specify more than one service by separating them
using | (the pipe symbol) without spaces.
Server-based Maintenance Tools
14

14-88 Maintaining Aeonix Aeonix Administration Manual

 aeonix_countCalls.sh
Use the aeonix_countCalls.sh command to count and display the number of
current calls in the system.

General Linux Commands

You can use the following Linux commands for Aeonix server maintenance:

Table 14-21 General

Linux Commands Option Description

top View online information about the available resources on the Aeonix
server.

df View information about available disk space on the server.

netstat View network information.

Server-based Maintenance Tools

14

Aeonix Administration Manual Maintaining Aeonix 14-89

  Log Files

This section relates to the log files that are created and stored on the Aeonix server:
 Aeonix Log Files, page 14-91
 Aeonix Conference Log Files, page 14-91
 Linux Log Files, page 14-91
The log files are in Log4J format. To view log details using the Chainsaw Open Source
application, type aeonix_chainsaw.sh in the command-prompt line of a terminal
window.

Figure 14-29 Chainsaw

Log4J Log Viewer
Server-based Maintenance Tools
14

14-90 Maintaining Aeonix Aeonix Administration Manual

 Aeonix Log Files
Aeonix log files are created and stored on the Aeonix server in the directory
/home/aeonixadmin/aeonix/logs. In case of system malfunction, forward the log files
to Aeonix Customer Support (see Support, page 1-16).
The following log files provide important information for troubleshooting the system:
 stdout.log—log file containing all server and database information (stored in
/home/aeonixadmin/aeonix/logs/server)
 catalina.out—log file containing output messages related to the Web (stored in
/home/aeonixadmin/aeonix/logs/web)

The /server and /web directories include archive sub-directories for each
weekday (/Sun, /Mon, /Tue, /Wed, /Thu, /Fri and /Sat). Every midnight, log
files from the previous day are moved to the appropriate sub-directory. A log
file is deleted after eight days.

Aeonix Conference Log Files

Log files related to conference calls are stored separately in the directory
/home/aeonixadmin/aeonixMP/log. These logs include signaling and functionality
data, but are not useful for pinpointing voice quality problems.

Linux Log Files

Linux log files are helpful in pinpointing failures that occurred in the past, such as
server reset. They are stored in the relevant folders in /var/log.
Linux log files are text files and can be displayed using any text editor, including vi.

Server-based Maintenance Tools

14

Aeonix Administration Manual Maintaining Aeonix 14-91

  Ethereal Network Analyzer

Network analyzers are used for understanding and solving network problems. One of
the commonly used network analysis tools is Ethereal.
The Ethereal network analyzer allows you to capture, in real time, information about
data transmission between endpoints on the network. Ethereal provides details about
each transmitted data package. It can also indicate if the communication between two
specific endpoints works only in one direction.
The Ethereal network analyzer is installed by default on each Aeonix server. Ethereal
includes a GUI for convenient capturing and browsing of network data. In addition,
Ethereal provides a terminal-based version called Tethereal, which allows users to
display the captured network data on a terminal window.

Figure 14-30 Ethereal

Report of Captured Data
Server-based Maintenance Tools
14

14-92 Maintaining Aeonix Aeonix Administration Manual

 Detailed information on Ethereal can be found at http://www.ethereal.com/docs/.

Server-based Maintenance Tools

14

Aeonix Administration Manual Maintaining Aeonix 14-93

  Aeonix Troubleshooting Examples

The following sections describe common troubleshooting scenarios:

 User Cannot Call a Specific Number, page 14-95
 No Phone Registered in Aeonix, page 14-95
 Bad Voice Quality in Conference Calls, page 14-96
Server-based Maintenance Tools
14

14-94 Maintaining Aeonix Aeonix Administration Manual

 User Cannot Call a Specific Number
Scenario: A user reports that he/she cannot reach a specific extension.

What to do:
1 Run the aeonix_mapUser.sh command (see aeonix_mapUser.sh [options],
page 14-88) to detect the ID of the phone through which the user is logged in to
the Aeonix system.
For example, if the user ID is johns, type in the command prompt line
aeonix_mapUser.sh -u johns
2 Run the aeonix_tevent.sh command (see aeonix_tevent.sh [options],
page 14-86) to trace the actions the user has performed from his phone.
For example, if the user’s phone ID includes the digits 0c:72, type
aeonix_tevent.sh -e 0c:72 -d -l 50
in the command prompt line to receive detailed information about the last 50
actions.
3 Based on the above information:
 Check whether the user dialed the correct number
 Check the reason for the call rejection.

No Phone Registered in Aeonix

Scenario: Aeonix users cannot make or receive calls because their phones are not
registered.

What to do:
 Use a network analyzer tool (such as the Ethereal Network Analyzer, page 14-92)
to ensure that the Aeonix server receives the register requests. (For optimal

Server-based Maintenance Tools

results, use a capture filter.)
 Verify that the Aeonix service is running (see Checking the Aeonix Service Status,
page 14-82).
 Run the aeonix_tevent.sh command for the phone IDs and check the
details to find the reason for the registration rejection.
14

Aeonix Administration Manual Maintaining Aeonix 14-95

 Bad Voice Quality in Conference Calls
Scenario: The voice quality of conference calls is impaired.

What to do:
 Run the top command (see General Linux Commands, page 14-89) and check the
CPU usage of the Aeonix server. You may be required to move the conference
media server module to a different server.
 Use a network analyzer tool (such as the Ethereal Network Analyzer, page 14-92)
to ensure the conference call RTP packets are appropriately sent and received.
Server-based Maintenance Tools
14

14-96 Maintaining Aeonix Aeonix Administration Manual

NOTES:
Server-based Maintenance Tools
14

14-98 Maintaining Aeonix Aeonix Administration Manual

 14.9 Aeonix Error Messages

This section describes Aeonix error messages. It also suggests how common failures
can be solved.
The following error message types can be displayed in the Aeonix Web Portal:
 Access and Password-related Error Messages, page 14-100
 General Error Messages, page 14-101
 Global Settings Error Messages, page 14-103
 Group-related Error Messages, page 14-104
 Phone and Phone Profiles-related Error Messages, page 14-105
 Phone and Phone Profiles-related Error Messages, page 14-105
 Routing and Digit Manipulation Error Messages, page 14-106
 Schedules-related Error Messages, page 14-107
 Voicemail-related Error Messages, page 14-108

Aeonix Error Messages

14

Aeonix Administration Manual Maintaining Aeonix 14-99

  Access and Password-related Error Messages

The following table lists error messages related to program access failures, as well as
password-resetting error messages (see Admin Password Policy, page 3-10).

Table 14-22 Web Portal—

Access Error Messages Error Message Description What To Do
<Resource type> exceeds The authorized number of Contact Customer Support to
its license limit. entities has been used up for upgrade the soft key license.
the specified resource type.

Check Server (appears at On the Aeonix server, the Check the Aeonix database
login) Aeonix database is not connectivity.
available or corrupted.

Only for first-time login after Load the license key into the
Aeonix installation: No soft server and restart the Aeonix
key license key is loaded in system.
the Aeonix server.

No servers exist. The Aeonix database is not Restart the database.

operating.

The license limit has been The licensed resources are Contact Customer Support to
exceeded. used up. upgrade the soft key license.

Wrong user name or When logging in to the Log in again using the correct
password system, you entered a wrong user name and password.
user name or a wrong
password.

Your session has expired, Too much time passed since Click Login and log in to the
please log in again. your last action using the Aeonix.
Aeonix Web Portal. Your
login is no longer valid.

Your session is invalid, The IP communication Click Login and log into the
please log in again. session was interrupted, for Aeonix.
example, due to a network
failure.

“New password” and When trying to change your Fill in the Change Password
“Confirm password” fields password, you entered fields again while taking care to
do not match. different values in the New enter the same value in the New
password and Confirm password and Confirm
password fields. password fields. (The system is
case-sensitive.)
Wrong password When trying to change your Fill in the Change Password
password, you entered a fields again while entering the
wrong password in the Old current password name correctly
Aeonix Error Messages

password field. in the Old password field.

14

14-100 Maintaining Aeonix Aeonix Administration Manual

  General Error Messages

The following table lists common error messages that are not limited to a specific
Aeonix element or entity.

Table 14-23 Web Portal—

General Error Messages Error Message Description What To Do
<Entity type>: <ID value> For a new entity, you typed Enter another value that is not
already exists. an ID value that is already in already in use.
use for an existing entity of
the same type. Examples of
entity types are users, trunk
groups, phones, and trunks.
This error message refers to
IDs or names that have to be
unique for each entity
belonging to a specific CUG.

<Field value> should have The value you typed in the Type a shorter text that does not
less than <number of> specified field has too many exceed the permitted length.
characters. characters or digits. For
example, the display name
you typed for a user is too
long.

<Field value> should have The value you typed in the Type a value that has at least
more than <number of> specified field has less than the required minimum number of
characters. the minimum of characters or characters or digits.
digits required. For example,
you defined a new alias
number with less than three
digits.

<Field> is not in the right The value you entered for Enter the value in the correct
format. the specified field has the format.
wrong format and can
therefore not be processed
by the system.
This error message can
include a description of the
required format. For
example, while defining a
new FlexSet-IP 280S phone,
you entered its MAC address
in the wrong format.
<Field> must be entered. The specified field is Specify a value for this field.
mandatory. For example, you
tried to save a new user
without specifying a Login
name for the new user. Aeonix Error Messages
<Field> must be selected. An option must be selected Select an option from the list.
from the specified drop-down
list. For example, you did not
select a dial plan for a new
CUG.

<Item> already exists. The value you typed for a Enter another value that is not
new item already exists for already in use for an existing
an existing item. For item of the same type.
example, you entered an
14

existing alias number for a

new user.

Aeonix Administration Manual Maintaining Aeonix 14-101

 Error Message Description What To Do
<Item> is in use. Assigned items, such as If you need to delete the item,
profiles, cannot be deleted. first remove each existing
For example, you cannot assignment to users or other
delete a toll barrier profile entities.
that has been assigned to
one or more users.
Cannot remove <entity You are trying to delete an Make sure the entity to be
type and name> because entity that is assigned to deleted is not assigned to any
it is used by <assigned another entity; for example, a entity.
entity type and name>. dial plan assigned to a CUG.

Internal error. Please try An internal server error has Close the Aeonix page of the
again. occurred on the Aeonix browser, open the Aeonix Web
server. Portal again and log in. If this
does not solve the problem,
contact your network system
administrator.

Invalid <field>. The value you entered for Enter a valid value.
the specified field is not
valid, although it may have
the required format.

Last <item>. You cannot scroll down Scroll up the list to locate the
further because you already required item. Use the Search
reached the last item in the facility to find a user in the user
list. list.

Only one <item> must be You selected multiple items Select only one item and click
selected. from a list and tried to Update. If necessary, edit other
update them simultaneously. items one by one.

The value is higher than The value you entered Enter a value that is lower than
the allowable maximum of exceeds the preset or equal to the maximum value.
<maximum value>. maximum. For example,
when defining a prefix alias,
you set the Limit length field
to a value higher than the
predefined maximum value
of 64.

The value is lower than The value you entered is Enter a value that is higher than
the allowable minimum of below the preset minimum. or equal to the minimum value.
<minimum value>.
Aeonix Error Messages
14

14-102 Maintaining Aeonix Aeonix Administration Manual

  Global Settings Error Messages

The following table describes the error messages that are displayed in connection with
global setting definitions.

Table 14-24 Web Portal—

Global Setting Error Error Message Description What To Do
Messages
Alias <alias number> is You tried to define an alias Type a number that follows the
not in the dial plan. number that does not match dial plan’s alias patterns. View
the alias patterns of the the alias patterns defined for the
appropriate dial plan. dial plan, if necessary.

Area <area name> cannot The area you are trying to If you need to delete the area,
be removed. It is used by delete is assigned to one or assign to the user’s phone a
<location>. more users. location that is not associated
with this area and/or select
another location from the
Always use dial rules of this
location drop-down list in the
user’s general settings.

At least one international No international access code Under the General tab of the
access code needs to be was defined for the country new country, define at least one
inserted. you try to create. international access code before
saving the country.

Cannot remove dial plan You tried to delete a dial If you need to delete the dial
<dial plan name> because plan that is assigned to a plan, assign another dial plan to
it is used by CUGs: <CUG Closed User Group. the CUG.
name or names>.

Country <country name> The country you are trying to If you need to delete the country,
cannot be removed. It is delete is assigned to one or assign to the user’s phone a
used by <location>. more users. location that is not associated
with this country and/or select
another location from the
Always use dial rules of this
location drop-down list in the
user’s general settings.

Country/area <country or You typed the name of a Select the country or area from
area name> does not non-existent country or area. the list, or type it in correctly.
exist.

Aeonix Error Messages

14

Aeonix Administration Manual Maintaining Aeonix 14-103

  Group-related Error Messages

The following table describes the error messages that can be displayed in context with
user groups, call groups, or ACD groups.

Table 14-25 Web Portal—

Group Error Messages Error Message Description What To Do
<Name of Group X> You are trying to include Check which group should be a
causes circular Group Y in Group X, but member of the other, and define
dependency for <Name of Group X is a member of the groups accordingly.
Group Y>. Group Y.

A file name is required. In the Audio Configuration Either select None, or select File
dialog box, you selected the and type the appropriate file
File option and clicked OK name.
without specifying the file.

No item was selected. On a group’s page, you First select a group and then
clicked View Group without click View Group.
first selecting an item in the
Unassigned box.

Only a group can be In the Unassigned box, you Select a group and click View
selected. selected a non-group item Group.
and clicked View Group.

Only one group can be You selected more than one Select one group and click View
selected. item in the Unassigned box Group.
before you clicked View
Group.
Aeonix Error Messages
14

14-104 Maintaining Aeonix Aeonix Administration Manual

  Phone and Phone Profiles-related Error Messages

The following table describes the error messages that relate to phones and phone
profiles.

Table 14-26 Web Portal—

Phone-related Error Error Message Description What To Do
Messages
Default profiles cannot be You are trying to delete a Adjust the profile as required, or
deleted. default phone profile. define a new phone profile and
associate it with the user’s
phone.

Aeonix Error Messages

14

Aeonix Administration Manual Maintaining Aeonix 14-105

  Routing and Digit Manipulation Error Messages

The following table describes the error messages that are displayed in connection with
routing definitions and digit manipulation rules.

Table 14-27 Web Portal—

Routing and Digit Error Message Description What To Do
Manipulation Error
Messages At least one call originator When defining an advanced Either clear the from check box
needs to be inserted. incoming call routing rule, the or enter at least one number in
from check box was the list box (see Defining Advanced
selected but no caller Rules for Incoming Call Routing,
number specified. page 5-35 for details).

At least one digit When defining a digit Define at least one action in the
manipulation action needs manipulation rule, the Actions box (see Defining Dialed
to be inserted. condition was specified, but Number Manipulation Rules,
the corresponding actions page 5-45).
were not.
Aeonix Error Messages
14

14-106 Maintaining Aeonix Aeonix Administration Manual

  Schedules-related Error Messages

The following table describes the error messages that are displayed in connection with
schedules and time frames.

Table 14-28 Web Portal—

Schedule Error Messages Error Message Description What To Do
The day of the month is When defining a yearly Select a possible value for the
incorrect. recurrence pattern for a time day of the month.
frame, the Every month
fields were incorrectly
defined, such as January
32.

The recurrence pattern is The recurrence pattern of the Correct the recurrence pattern
invalid. time frame you are defining definition of the time frame.
is invalid. For example, no
week day was selected for a
weekly recurrence pattern.

The start time must For a recurrence pattern of a In the recurrence’s Start time
precede the end time. time frame, either the start and End time fields, make sure
time was set to be later than the start time is earlier than the
the end time, or the start end time.
date was set to be later than Under Range of recurrence,
the end date. make sure the start date is
earlier than the end date (if
defined).

Aeonix Error Messages

14

Aeonix Administration Manual Maintaining Aeonix 14-107

  Voicemail-related Error Messages

The following table describes the error messages that are displayed when creating or
deleting a user’s voicemail box.

For a detailed description of the SeaMail Web Portal, refer to the SeaMail
Administration and Configuration Manual for Aeonix (see Related
Documentation, page 1-17).

Table 14-29 Web Portal—

Voicemail Error Error Message Description What To Do
Messages
A user must have at least You tried to save a user that To save the user without
one complete, numeric has the Create voicemail creating a voicemail box for the
alias to create a voicemail box check box selected, but time being, clear the Create
box. no complete alias number voicemail box check box prior
assigned. to saving.
The system needs the alias To save the user with an
number to create a mailbox assigned voicemail box, add a
with this number. complete alias number for this
user and click Save.

Could not create voicemail The system could not create Check the network status. If the
box <mailbox number>. a voicemail box for the alias problem persists, contact
number, usually due to a Customer Support.
network problem.

Could not delete voicemail The system could not delete Check the network status. If the
box <mailbox number>. a user’s existing mailbox, problem persists, contact
usually due to a network Customer Support.
problem.

Incorrect source: <mailbox When replacing a user’s In the SeaMail Web Portal, either
number> or destination: main alias number, the redefine the source mailbox or
<mailbox number>. mailbox number should be manually assign a non-occupied
changed accordingly by the mailbox number as required.
system. This error occurs if
the source mailbox number
was previously deleted in
SeaMail, or if the mailbox
number to be assigned is
already in use.
Unknown voicemail error Trying to create or delete a Check the network status. If the
user’s mailbox resulted in an problem persists, contact
error of an unknown type. Customer Support.
Aeonix Error Messages

Voicemail box <mailbox The system cannot In the SeaMail Web Portal, either
number> already exists. automatically create a delete the relevant mailbox or
voicemail box for the alias, create a mailbox with another
because a mailbox with this number for the user.
number has already been
manually created.
Voicemail role <role The role (permissions) In the SeaMail Web Portal,
name> does not exist. assigned to the user has redefine the relevant role. You
been deleted. can view the assigned role in the
user’s mailbox properties.
14

14-108 Maintaining Aeonix Aeonix Administration Manual

 Chapter 15

Aeonix Multi-Tenant Mode

15.1 Overview.............................................................................15-1

15.2 Tenant List...........................................................................15-3

15.3 Dial Plan .............................................................................15-7

15.4 Tenants and Users............................................................15-11

15.5 Service List .......................................................................15-23

15.6 Phones..............................................................................15-39

Aeonix Administration Manual

15

15-0 Aeonix Multi-Tenant Mode Aeonix Administration Manual

 15.1 Overview

Aeonix Multi-Tenant Mode is exclusively run in the A4C environment.

Multi-Tenant Mode is invoked in an Aeonix A4C instance when it is created
as a Multi-Tenant Mode instance in the Aeonix4Cloud Portal.

Aeonix Multi-Tenant Mode supports multiple tenants running in a single instance of

Aeonix on a single virtual machine. Each tenant implements the telephony system of
a customer. The tenants are managed through the Aeonix4Cloud Portal. A dealer can
manage multiple tenants on a single virtual machine. Tadiran manages the entire
collection of tenants and dealers in the cloud / data center. When an Aeonix instance
runs in Multi-Tenant Mode, it presents additional features in the Admin GUI that are
not available in the normal mode.

Aeonix Multi-Tenant Mode supports basic Aeonix UC&C operation and

SeaMail voicemail operation. As multi-tenant is purposed to reduce cost for
smaller telephony installations, the current version does not support Aeonix
Contact Center or Aeonix Logger.

The goal of Aeonix Multi-Tenant Mode is to reduce the overall hosting costs in the
Aeonix4Cloud environment, and to pass those cost savings to dealers and their
tenants/customers.
This chapter describes the following Multi-Tenant features:
 Tenant List, page 15-3
 Dial Plan, page 15-7
 Tenants and Users, page 15-11
Service List, page 15-23
Overview

 Phones, page 15-39

15

Aeonix Administration Manual Aeonix Multi-Tenant Mode 15-1

Overview
15

15-2 Aeonix Multi-Tenant Mode Aeonix Administration Manual

 15.2 Tenant List

The Tenant List page is the entry point to the Aeonix system in Aeonix Multi-Tenant
Mode. The Tenant List page is used to view the tenants that have been created by and
are managed by a single dealer, and for selecting a Tenant for parameter configuration.
. Selecting a Tenant sets the Aeonix system to that Tenant, so that only services and
user for that Tenant will be shown. Many parameter fields require that a Tenant be
selected before you can edit them.

The Tenant List is for Tenant selection only. You cannot create new tenants,
or delete tenants from the Tenant List page in an A4C Aeonix instance in
Multi-Tenant Mode. You can only create or delete tenants via the
Aeonix4Cloud Portal.

The Tenant List page is accessed from Settings > Tenants > Tenant List as shown in
the following figure.

Tenant List
15

Aeonix Administration Manual Aeonix Multi-Tenant Mode 15-3

 Figure 15-1 Tenants List
Page

The Tenant List page displays information in the following fields:

Column / Information
Button

Tenant Name The customer name as entered in the A4C Portal.

Tenant ID A unique identifier assigned by the A4C Portal. It serves as the

link between the Aeonix tenant and the A4C Portal customer.

Alias Prefix The 4-digit prefix that is assigned to all aliases associated with
the tenant. The Alias Prefix is in the range 8000-8999
representing a capacity of 1000 tenants in a single Aeonix
Multi-Tenant Mode instance. The Alias Prefix for a tenant is
determined automatically by the A4C Portal when the tenant is
Tenant List

created.

Licensed The total number of licenses that have been purchased and
made available for the tenant.
15

In Use The number of licenses in active use under the tenant.

15-4 Aeonix Multi-Tenant Mode Aeonix Administration Manual

 Column / Information
Button

DIDs The tenant DID numbers and ranges. This column is only
updated when the dealer has updated the DIDs via the A4C
Portal.

Search Displays search fields and activation buttons for the list. Search
fields:
 Tenant Name: A tenant name as defined in the first column
of the list. Substrings are accepted.
 Alies Prefix: An alias prefix as defined in the second column.
Search activation buttons:
 Apply: Apply the filter to the list, and only display matches.
 Show All: Return to displaying the full list.

Tenant List
15

Aeonix Administration Manual Aeonix Multi-Tenant Mode 15-5

Tenant List
15

15-6 Aeonix Multi-Tenant Mode Aeonix Administration Manual

 15.3 Dial Plan

Aeonix Multi-Tenant Mode assigns a default dial plan to Tenants. The System and
Default Tenant Dial Plans are accessed at System > Dial Plan List as shown in the
following figure.

Figure 15-2 Dial Plan List

Click on System Dial Plan in the Dial Plan List to display the System Dial Plan page
as shown in the following figure.
Dial Plan
15

Aeonix Administration Manual Aeonix Multi-Tenant Mode 15-7

 Figure 15-3 System Dial
Plan

The System Dial Plan in Aeonix Multi-Tenant Mode includes the following Patterns:
 8xxx2xx
 8xxx3xx
 8xxx4xx
 8xxx5xx
 89999xx
 68xxxxxx (aliases on a Trunk Group to Voice for “Direct Transfer to Voice
Mail”)

In Aeonix Multi-Tenant Mode, the extensions only include 3 digits. It is not

Dial Plan

possible to define numbers with more or less digits. In Aeonix Multi-Tenant

Mode the System Dial Plan is not modifiable. Dealers cannot change, add, or
remove entries, and cannot clone profiles.
15

15-8 Aeonix Multi-Tenant Mode Aeonix Administration Manual

 Aeonix Multi-Tenant Mode supports a deafult Dial Plan that is assigned to individual
Tenants.

The Dial Plans assigned to Tenants are not modifiable by the dealer /
administrator.

The Default Tenant Dial Plan can be opened in Settings > Dial Plan > Dial Plan
List as shown in the following figure.

Figure 15-4 Default

Tenant Dial Plan

The Default Tenant Dial Plan is assigned automatically to the Default Provisioning
Profile as shown in the following figure.
Dial Plan
15

Aeonix Administration Manual Aeonix Multi-Tenant Mode 15-9

 Figure 15-5 Default
Provisioning Profile

The assigned Default Tenant Dial Plan cannot be changed by the dealer.
Dial Plan
15

15-10 Aeonix Multi-Tenant Mode Aeonix Administration Manual

 15.4 Tenants and Users

 Tenant User Profiles

Aeonix Multi-Tenant Mode supports a maximum of 998 Tenants. The list of defined
Tenant User Profiles can be seen at Settings > Profiles > User Profile List as shown
in the following figure.

Figure 15-6 User Profile

List

Tenants and Users

15

Aeonix Administration Manual Aeonix Multi-Tenant Mode 15-11

 Select the Tenant from the list. The User Profile for the Tenant is displayed as shown
in the following figure.

Figure 15-7 User Profile

for Tenant

Each User Profile is associated with its corresponding User Outgoing Call Routing
definition. The association is read-only and cannot be changed by the dealer. The
dealer can modify Tenant User Profile details in the User Profile page, but cannot
select a different User Outgoing Call Routing.
Tenants and Users
15

15-12 Aeonix Multi-Tenant Mode Aeonix Administration Manual

  Outgoing Call Routing Profile

A Tenant is created with a default Outgoing Call Routing Profile as shown in the
following figure.

Figure 15-8 Outgoing

Call Routing Profiles List

Click on the Name of the Outgoing Call Profile for a given Tenant to see the Outgoing
Call Routing Profile as shown in the following figure.

Tenants and Users

15

Aeonix Administration Manual Aeonix Multi-Tenant Mode 15-13

 Figure 15-9 Outgoing
Call Routing Profile

The dealer can add Dialed Number Manipulations Rules as required for an
individual Tenant.
The Dialed Number Manipulation Rules of each tenant's outgoing Call Routing
Profile will automatically include the following lines. These lines cannot be modified.
 "If DNIS 'is between 76-77 then Add prefix 1 and Remove first 1 digits and
stop processing other rules.
 If DNIS 'is between' 200-599 then add prefix <Tenant's Prefix> and stop
processing other rules.
 If DNIS 'is between' 7000-7999 then add prefix 7<Tenant's Prefix> and stop
Tenants and Users

processing other rules.

 If DNIS is 999 add prefix 8999 and stop processing other rules.
 If DNIS is between <Tenant's Prefix>200-<Tenant's Prefix>998 add 1 first
digit and remove 1 first digit Stop processing other rules.
 If DNIS is 9<Emergency Number> add 1 first digit and remove 1 first digit
15

Stop processing other rules.

15-14 Aeonix Multi-Tenant Mode Aeonix Administration Manual

  If DNIS is <Emergency Number> add 1 first digit and remove 1 first digit
Stop processing other rules.
 If DNIS 'is between' 6000-6998' then Remove 1 first digit, add prefix
6<Tenant's Prefix> and stop processing other rules.
 If DNIS is 8999999 add 1 first digit and remove 1 first digit Stop processing
other rules.
 If DNIS start with '9' then add prefix '1' and remove '1' and stop processing
other rules.
Note: Numbers 6000-6998 is reserved to Direct Transfer to VM (68000XXX).
Note: Numbers 700-799 is reserved to PageQ (78000XXX).
For example, this is the set of rules for a Tenant with 8000:
If DNIS 'is between 76-77 then Add prefix 1 and Remove first 1 digits and stop
processing other rules.
 If DNIS 'is between' 200-599 then add prefix 8000 and stop processing other
rules.
 If DNIS 'is between' 7000-7999 then add prefix 78000 and stop processing
other rules.
 If DNIS is 999 add prefix 8999 and stop processing other rules.
 If DNIS is 911 add 1 first digit and remove 1 first digit Stop processing other
rules.
 If DNIS is 11 add replace number with 911 and Stop processing other rules.
 If DNIS 'is between' 8000200-8000998 add 1 first digit and remove 1 first
digit Stop processing other rules.
 If DNIS 'is between' 6000-6998' then Remove 1 first digit, add prefix 68000
and stop processing other rules.
 If DNIS is 8999999 add 1 first digit and remove 1 first digit Stop processing
other rules.
 If DNIS start with '9' then add prefix '1' and remove '1' and stop processing
other rules.
Tenants and Users
15

Aeonix Administration Manual Aeonix Multi-Tenant Mode 15-15

  User List

The User List displays all users (end points) in the dealer’s Aeonix Multi-Tenant Mode
instance. The assignment of each user to a Tenant is shown in the Tenant Name
column.

Figure 15-10 User List

Note that the alias of a user is composed of the Tenant-specific Alias prefix and the 3
digits of the user phone number.

 New User
Tenants and Users

To add a new User (end point) to a Tenant, choose User > Add User. The New User
page is displayed as shown in the following figure.
15

15-16 Aeonix Multi-Tenant Mode Aeonix Administration Manual

Figure 15-11 New User

The administrator specifies the Tenant Name for the new user, as well as any other
details for the user. When adding an Aeonix Internal Alias, the Tenant-specific prefix
is automatically included as shown in the following figure.

Tenants and Users

15

Aeonix Administration Manual Aeonix Multi-Tenant Mode 15-17

 Figure 15-12 New User
Add Alias

When adding a Range of Aliases, or a Prefix, by selecting the appropriate

radio-button, the Tenant alias-prefix is also displayed in the New User > Alias page as
shown in the following figure.
Tenants and Users
15

15-18 Aeonix Multi-Tenant Mode Aeonix Administration Manual

Figure 15-13 New User
Add Alias Range

In Aeonix Multi-Tenant Mode you cannot add an Alias to a user until you
have defined a Tenant for the user. The system will display an error message
in the New User page as shown in the following figure.

Figure 15-14 New User

Add Alias Error Message

Tenants and Users

15

Aeonix Administration Manual Aeonix Multi-Tenant Mode 15-19

  Import / Export Users

In Aeonix Multi-Tenant Mode the Import and Export processes include the Tenant
field, and the alias field has the Multi-Tenant Mode style structure of 8xxxyyy where
8xxx is the Tenant-specific Alias-prefix, and yyy is the 3-digit user phone number.

Figure 15-15 Import /

Export Users

Aeonix checks the validity of the User Tenant and Alias fields during Import: User
Tenant is a Tenant Name, and the Internal Alias must include a Tenant-specific Alias
prefix in the form 8xxx corresponding to the Tenant Name. If any records have
problematic fields, an error message is displayed on the Import / Export Users page
for that record, and the record is not added / updated to the database.
Tenants and Users
15

15-20 Aeonix Multi-Tenant Mode Aeonix Administration Manual

  User Permnissions

In Aeonix Multi-Tenant Mode the User Permissions page now only displays users
from the same Tenant as the user that is being defined, in the Unassigned list box.

Figure 15-16 User

Permissions

Tenants and Users

15

Aeonix Administration Manual Aeonix Multi-Tenant Mode 15-21

Tenants and Users
15

15-22 Aeonix Multi-Tenant Mode Aeonix Administration Manual

 15.5 Service List

 Multi-Tenant Mode Services

In Aeonix Multi-Tenant Mode, the Tenant field has been added to most service
entities, and the Search function has been added to allow viewing user instances for a
Tenant in service instances.

Aeonix Multi-Tenant Mode has a reduced set of Aeonix Services for smaller
tenant telephony systems. The following Aeonix Services are not available in
a tenant system:

ACC
Call Group
Call Recording
CTI
Dispatch Console
E911 database Connector
Emergency Conference
Hospitality
Virtual Endpoints
LDAP

In Multi-Tenant Mode the Services List appears as shown in the following figure.

Service List
15

Aeonix Administration Manual Aeonix Multi-Tenant Mode 15-23

 Figure 15-17 Service List

In Multi-Tenant Mode most Service pages display the additional Tenant field, which
allows the dealer to select which tenant services he wishes to review or edit. The
following sections describe specific changes to Service pages that support
Multi-Tenant Mode.
Service List
15

15-24 Aeonix Multi-Tenant Mode Aeonix Administration Manual

  ACD Pages

The ACD Group List page now displays the Tenant Name column as shown in the
figure below.

Figure 15-18 ACD Group

List Page

Service List
15

Aeonix Administration Manual Aeonix Multi-Tenant Mode 15-25

 Figure 15-19 ACD Group
List Page Search

Click on the Search button to display the Search fields as shown in the figure above.
You can search by Tenant Name, or by Alias, or by both combined. After specifying
the search criteria, click on the Apply button. The list of ACD Group aliases will be
filtered according to the search criteria and redisplayed. Click the Show All button to
clear the filter and display all ACD Group aliases.
Service List
15

15-26 Aeonix Multi-Tenant Mode Aeonix Administration Manual

 The ACD Group page now displays the Tenant Name to which the ACD Group is
assigned. The Tenant Name is assigned when you create a new ACD Group by
clicking Add in the ACD Group List page.

Figure 15-20 ACD Group

Page

Service List
15

Aeonix Administration Manual Aeonix Multi-Tenant Mode 15-27

 Figure 15-21 New ACD
Group Page

In Aeonix Multi-Tenant Mode, the New ADC Group page now requires you to
specify the Tenant Name.
Service List
15

15-28 Aeonix Multi-Tenant Mode Aeonix Administration Manual

  Hunt Group Page

The Hunt Group List page now displays the Tenant Name column and the Search
facility as shown in the figure below.

Figure 15-22 Hunt Group

List Page

Service List
15

Aeonix Administration Manual Aeonix Multi-Tenant Mode 15-29

 Figure 15-23 New Hunt
Group Page

In Aeonix Multi-Tenant Mode, the New Hunt Group page now requires you to
specify the Tenant Name.
The Suggest Available Aliases button and the Unassigned group members list box,
show only selections available for the Tenant that is defined in the Tenant Name field.
Service List
15

15-30 Aeonix Multi-Tenant Mode Aeonix Administration Manual

  Conference Call

The Conference Call List now includes the Tenant Name column, and the Search
facility with Tenant Name field.

Figure 15-24 Conference

Call List

Click the Add button to create a new Conference Call. The New Conference Call
page is displayed as shown in the following figure.

Service List
15

Aeonix Administration Manual Aeonix Multi-Tenant Mode 15-31

 Figure 15-25 Conference
call Page

The Suggest Available Aliases button, the Group Members, and Group Managers,
show only selections available for the Tenant that is defined in the Tenant Name field.
Service List
15

15-32 Aeonix Multi-Tenant Mode Aeonix Administration Manual

  Meet-Me Conference Page

In the New Meet-Me Conference Configuration page the Suggest Available Aliases
button and the Owner field show only selections available for the Tenant that is
defined in the Tenant Name field, as shown in the following figure.

Figure 15-26 New

Meet-Me Conference
Configuration Page

Service List
15

Aeonix Administration Manual Aeonix Multi-Tenant Mode 15-33

  Music Source

In the Music Source page the Tenant Name field is used to define the Tenant, and the
Assign MOH to Alias fields show the Tenant prefix that will be used in the
assignment, as shown in the following figure.

Figure 15-27 New

Meet-Me Conference
Configuration Page

If you choose Range instead of Alias in the drop down list, the Start of Range and End
of Range fields also show the Tenant prefix.
Service List
15

15-34 Aeonix Multi-Tenant Mode Aeonix Administration Manual

  Page Queue Park / Pickup Page

Adding a new Page Queue Park / Pickup alias requires you to specify a Tenant as
shown in the following figure.

Figure 15-28 Add Page

Queue Park / Pickup
Alias

Service List
15

Aeonix Administration Manual Aeonix Multi-Tenant Mode 15-35

  PnP / Auto Provisioning Page

PnP / Auto Provisioning requires you to specify a Tenant. The Tenant prefix is
displayed in the User Alias Starts At field as shown in the following figure.

Figure 15-29 PnP / Auto

Provisioning
Service List
15

15-36 Aeonix Multi-Tenant Mode Aeonix Administration Manual

  SIP Voicemail Page

In Aeonix Multi-Tenant Mode, the Voicemail Service has a default alias of 8999999
and cannot be changed.
The administrator cannot Add or Delete aliases. The buttons on the Aliases panel are
greyed-out as shown in the following figure.

Figure 15-30 SIP

Viocemail

Service List
15

Aeonix Administration Manual Aeonix Multi-Tenant Mode 15-37

  Zone Page

Adding a New Zone Page requires the administrator to define the Tenant in the
Tenant Name field. After the Tenant is defined, the Alias field displays the Tenant
prefix, and the Suggest Available Aliases function displays alias ranges for that
Tenant. Additionally, the Group Members Unassigned list and the Group Managers
Unassigned list display aliases from the defined Tenant.

Figure 15-31 New Zone

Page
Service List
15

15-38 Aeonix Multi-Tenant Mode Aeonix Administration Manual

 15.6 Phones

 Feature Codes

Aeonix completes the 3 digits of “destination” to a valid alias by adding the tenant
prefix of this user. The following figure shows the required System Dial Plan fields
for feature codes:

Figure 15-32 System Dial

Plan Feature Codes

Phones
15

Aeonix Administration Manual Aeonix Multi-Tenant Mode 15-39

  Button Programming Through Aeonix Admin

 The administrator can program a button via 'User' and 'Alias' modes.
 When the administrator selects 'User' mode, Aeonix admin only displays the
users of the phone's 'default user' tenant.
 When the administrator selects 'Number' mode, type a 3-digit number. There is
no need to complete it to a 7-digit number.
The following figure shows programming a phone button via the Aeonix Admin in
Aeonix Multi-Tenant Mode.

Figure 15-33 Button

Programming - Aeonix
Admin
Phones
15

15-40 Aeonix Multi-Tenant Mode Aeonix Administration Manual

  Button Programming Through the Phones

A user can program a button by 'User' and by 'Alias' mode.

When the user selects 'User' mode, Aeonix will only display the users of the phone's
'default user' Tenant.
When the user selects 'Number' mode, he will type a 3-digit number. There is no need
to complete it to a 7-digit number.

 FlexiCall Dial without ‘9’

If Aeonix does not find a match on any of the User Outgoing Call DNIS manipulation
Rule, then it assumes it is an external number. “Add Outside Number Access Code” is
set by default in Aeonix Multi-Tenant Mode.

 ANI Display / Call Log

Call Log and ANI of internal calls show the 3-digit number of the user.

 SeaMail Operation

SeaMail includes the mailboxes of all users in the Aeonix Multi-Tenant Mode system.
The user’s mailbox is user alias 8xxxyyy. The user can only change their mailbox
preferences and listen to their messages.

Listening to Mailbox Messages

When a caller belonging to a Tenant presses on the 'Mailbox' button, or dials Voice
Mail alias (8999999), they will get the option to listen to their voice mail messages or
change their personal options. SeaMail receives the alias of the user 8xxx-yyy that
allows them to open a mailbox 8xxxyyy of the corresponding department.
Phones
15

Aeonix Administration Manual Aeonix Multi-Tenant Mode 15-41

  Unsupported Phones and Applications

The following phones and applications are not supported in Aeonix 5.1 Multi-Tenant
Mode:
 MGCP Phones and GW
 Navigator
 Sea Attendant
 ADC client
 ACC agent
The following Aeonix features are not supported in Aeonix 5.1 Multi-Tenant Mode:
 ACC
 Call Group
 Call Recording
 CTI
 Dispatch Console
 E911 Database Connector
 Emergency Conference
 Hospitality
 Virtual Endpoints
 LDAP
 VOIP FXS Provisioning
 FXO
Phones
15

15-42 Aeonix Multi-Tenant Mode Aeonix Administration Manual

 Chapter 16

Glossary

16.1 Glossary of Terms...............................................................16-1

Aeonix Administration Manual

16

16-0 Glossary Aeonix Administration Manual

 16.1 Glossary of Terms

ACD (Automatic Call In Automatic Call Distribution, an alias number is assigned for multiple users and user
Distribution)
groups. A call to this number is routed to the first available user (and not to all users
as with call groups). If all answering positions are busy, ACD plays a recorded
message or music and puts the caller on hold until an answering position becomes
available.

Aeonix Contact Center An intuitive, flexible and easy to use all in one contact center management solution for
(ACC)
Aeonix systems.

Alias The number used to reach a specific Aeonix user from within the system. Unlike a
traditional extension number, an alias is associated with the user, rather than a
particular telephone or wall outlet. If a user's cellular phone or other external devices
are defined in Aeonix, a call to the alias of this user can also ring on these devices.
Aliases can also be assigned to trunk groups or to certain services, such as call groups,
ACD groups, conference call servers, mobility services, and voicemail servers.

Area code Code dialed to reach an area’s telephone exchange system.

ARS (Automatic Route A feature used for optimizing the routing of outgoing calls. Automatic Route Selection
Selection)
allows administrators to specify the channels (trunk groups) through which calls are
transmitted, depending on the prefix of the call destination.

Auto answer A feature that sets the phone to automatically accept incoming calls.

Call forwarding Redirects an incoming call to another alias or external number. Call forwarding and
call rejection are part of incoming call routing.

Call group In a call group, an alias number is assigned for multiple users and user groups. When
this number is called, the telephones of all users included in the call group ring until
Glossary of Terms

one of the users answers the call.

Call muting A feature that turns off the microphone before or during a conversation, so that the
other party cannot hear the user.

Dial The entering of the relevant digits for operating a feature or sending a call to a
16

destination by pressing the number on a telephone’s dial pad.

Aeonix Administration Manual Glossary 16-1

 External number The phone number of an external device, for example, a cellular phone or a phone at
the user’s home.

Feature A telephony capability Aeonix supports that can be activated by dialing a code.

Gateway A network device that translates call data between networks or protocols in real time.
For example, data can be translated between the public/private switched telephone
network (PSTN) and an IP network. For a VoIP gateway, the primary functions include
voice and fax compression/decompression, packetization, call routing, and control
signaling. Gateways include interfaces to external controllers (gatekeepers or
softswitches), billing systems, and network management systems.

Hot station A telephone that automatically dials to a specified number when the handset is lifted
or a key is pressed. The routing can take place immediately upon off-hook or after a
programmable delay to allow the user to start dialing.

Idle The state of a phone or trunk that is not ringing or busy, and is therefore available for
use.

Incoming call routing The way incoming calls are forwarded or rejected. Incoming calls can be rejected or
routed to different destinations depending on user availability, caller, and call time.

Internal call A call to / from a device within a local network.

Internal phone / alias A phone that is directly connected to Aeonix, or connected through a Wave Gateway
/ SIP gateway. Internal callers can reach the user of this phone by dialing the user’s
alias number without prefixes.
Typically, office phones are internal phones.

License key A software-based license key that holds the number of purchased Aeonix and SeaMail
(optional) licenses. The license key must be uploaded and deployed on the designated
Aeonix License Key server.

Lightweight Directory A networking protocol for querying and modifying directory services running over
Access Protocol (LDAP)
TCP/IP. This feature enables managers to quickly and conveniently import new users
or to update details of existing users.

Location Setting that indicates the country and area in which a phone or trunk is located and
Glossary of Terms

used. A phone’s location can be redefined for the phone user.

Long distance access code Code dialed to make long distance calls.

MAC (Media Access A unique hardware address burned on a specific phone, computer, gateway, or other
Control) Address
hardware device.
16

16-2 Glossary Aeonix Administration Manual

 MGCP Media Gateway Control Protocol (MGCP). A VoIP protocol that allows voice
gateways to control external call control elements in distributed gateway architectures.
MGCP aims to eliminate the need for complex, processor-intense IP telephony
devices, thus simplifying and lowering the cost of these terminals.
MGCP was originally intended for gateways but can be adopted for terminals; its call
processing function is shifted from the gateways (and terminals) to a central call server
(the Aeonix server).
The Aeonix system supports MGCP phones such as: FlexSet-IP 280S, T207M,
T208M, T207M/NP, T208M/BL.

Music on hold A service that plays music or a message to callers while they are on hold or transferred
to another number. Music on Hold indicates to callers that they are still connected and
makes the waiting time appear shorter, thereby causing them to stay longer on the line.

Off-hook The state of a phone when its cradle is lifted. Off-hook provides the dial tone, enabling
you to dial or activate a feature.

On-hook The state of a phone when its phone handset is in its cradle.

Outgoing call routing A set of parameters and rules that define the way outgoing calls are routed. Outgoing
call routing includes ARS and hot station definitions, caller ID display parameters, and
rules for manipulating call dial numbers.

Phone The actual hardware or software that “rings” when called. A phone can be:
 An MGCP keyset, such as: FlexSet-IP 280S, T207M, T208M, T207M/NP,
T208M/BL
 A digital keyset connected through a Wave Gateway, such as: FlexSet 120,
120D, 120L, 120S, 121S, 280, 280D, 280D-HS, 280S, 281S, DKT, and
DST
 A SIP phone, such as: Tadiran SIP phones and P-Series phones
 An analog phone SLT connected through a gateway, such as Wave Gateway
 A softphone application on the user’s workstation, such as: Bria, SeaBeam
and FlexIP SoftPhone (FLIPS). Glossary of Terms

If a default user has been defined, a newly connected phone can be used to
make calls to other users in the network. To receive calls, however, the phone
must first be associated with a specific user.

Phone profile Defines the basic behavior of a telephone for a user, as well as the functions of the
phone’s programmable buttons. Currently only in use for MGCP keysets (FlexSet-IP
16

280S, T207M, T208M, T207M/NP, T208M/BL) and digital keysets (FlexSet 120,

Aeonix Administration Manual Glossary 16-3

 120D, 120L, 120S, 121S, 280, 280D, 280D-HS, 280S, 281S, DKT, and DST;
connected through a Wave Gateway).

Pickup group A call to a member of a pickup group can be retrieved by any member dialing the
group alert call pickup code.

Profile A set of parameter values that can be associated with an Aeonix entity. There are
dedicated profile types for users and for trunk groups.

PSAP (Public Safety An emergency call center to which 911 calls are routed.
Answer Point)

Schedule A set of time frames for special weekdays, dates, or hours. Schedules are used for
timing of call routing activities.

Sea Attendant An advanced desktop unified communications manager application for operators that
runs on top of the Aeonix system.

Sea Navigator A multi-media communications desktop application that runs on top of Aeonix.

Service A centralized application required for using specific Aeonix features and capabilities.

SIP Session Internet Protocol (SIP). A signaling protocol for Internet conferencing,
telephony, presence, events notification and instant messaging. The Aeonix system
supports telephones, gateways, and applications that comply with SIP. The Aeonix
system supports SIP phones such as: Tadiran SIP phones and P-Series phones.

Soft key For a telephone with a display panel, a key at the bottom/top/side of the panel used to
directly activate the currently displayed feature.

Softphone An application that simulates a real phone and runs on a general purpose workstation,
rather than a dedicated telephony device. It is usually used with a headset connected
to the sound card of the computer. The Aeonix system supports softphone applications
such as: SeaBeam and FlexIP.

Station Coral legacy phones connected to Aeonix through a Wave Gateway are also referred
to as stations.

Subnet mask A mask used to tell how many places (bits) in an IP address identify the subnetwork,
Glossary of Terms

and how many places provide room for host addresses.

Template A set of parameter values that defines the initial default values for new phones,
gateways, and trunks.

Timeout A predetermined period of time allowed to complete a specific function.

16

16-4 Glossary Aeonix Administration Manual

 Time frame A specified one-time or recurrent period, day, or date, such as a holiday. A schedule
consists of time frames.

Toll barrier A restriction on making calls to certain numbers or destinations.

Transfer/Xfer While engaged in a call, a user can initiate this feature by pressing the XFER
(Transfer) key. XFER has a distinctive dial tone and allows transfer of the call or the
activation of a feature. XFER puts the second party on hold and provides a tone or
plays a message.

Trunk An external line from the phone company that terminates at the customer’s location.

Trunk group A gateway or telephony system connected to Aeonix that usually has a unique alias
number (or multiple numbers) defined and is assigned to one or more trunks.

UM (Unified Messaging) A feature enabling users to receive voice messages, faxes, and emails at one unified
access point.

UGW (Universal Gateway A Coral-internal gateway enabling the Coral system to operate with Aeonix and IP
card)
phones using the QSIG networking protocol.

ULA group A ULA group is a group of users in which an incoming call can ring, as well as flash
a programmed shared line button, at the devices of these users. ULA group members
can also place calls on behalf of their group.
Each ULA group consists of its group owner and one or more regular members (up to
50 members per group). The same user can be the owner of one ULA group only.

User An individual connected to the Aeonix system that usually has one or more unique
alias numbers defined and is associated with one or more phones.

User group A collection of users. User groups allow administrators to treat multiple users as one
unit.

Voicemail A centralized system (such as SeaMail) of managing telephone messages for a large
group of people. The system stores incoming messages in personalized mailboxes
associated with the user’s phone number.

Wave Gateway A Coral IPx or FlexiCom unit that has been modified to be controlled by Aeonix,
Glossary of Terms

enabling Aeonix to integrate legacy IPx or FlexiCom legacy hardware and equipment.
All Aeonix features are applied to the legacy trunks and phones connected to the Wave
Gateway.
16

Aeonix Administration Manual Glossary 16-5

Glossary of Terms
16

16-6 Glossary Aeonix Administration Manual

Israel +972-3-9262000

USA +1-678-506-7200

Russia +7-495-7750855

China +86-10-58696418

India +91-11-41523168 / 23353822

Visit us at: www.tadirantele.com