This documentation relates to iSymphony 3.5. You can view older documentation on the Older Documentation page

Skip to end of metadata
Go to start of metadata

On this page:

Core Servers are utilized to identify a physical organization and have separate configuration from other Core Server instances. Core Servers are analogous to Locations in iSymphony 2.x.x but can support multiple PBX Connections. On first installation there will be one Core Server called default. Most users will never utilize more than the one default Core Server however users who wish to host multiple customers or utilize multi-tenancy on a single iSymphony server instance will want to create multiple Core Server instances.

When there are multiple Core Servers configured users must login in a specific way in order to specify which Core Server they wish to login to. See Connecting To The Client Interface for more information on the login procedure when multiple Core Servers defined.

Managing

Selecting a Core Server

Administrators can use the Current Server list in the top right hand corner of the Administration Interface to select the Core Server that you want to manage.

You can only view a Core Server configuration if you are a Super Administrator or you have been granted access by a Super Administrator. See Administrators for more information.

Core Server List

To access the Core Server list navigate to Current Server->Show All. From this list Administrators can add and remove Core Servers.

Only Super Administrators can create and remove Core Servers. See Administrators for more information.

Core Server Settings

You can access the Core Server properties page by selecting Settings in the administration menu.

Core Server Properties

Core Settings

 

Server Name:

The display name for the Core Server.

Unique Key:

The unique ID of the Core Server. This ID cannot be changed once the Core Server has been created. Specifies the folder name used for storing the Core Server configuration files within /opt/isymphony/server/conf/servers.

PBX Settings

 

Tenant Identifier:Specifies the tenant id the core server is associated with. Set to a blank value if not utilizing a multi-tenant phone system.
Originating Context:

 The dial plan context to use when originating calls in the panel.

Some Common Contexts:

  • default: Most custom hand built dial plans use this.
  • from-internal: Used by FreePBX based phone systems.
  • from-inside: Used by Thirdlane based phone systems.
  • from-inside-<tenant name>: Used by Thirdlane Multi-Tenant based phone systems.
Redirecting Context:
 The dial plan context to use when transferring calls in the panel. This is normally the same value as Originating Context.

Music on Hold Class:

The music on hold class to use when placing calls on hold in the panel.

Originate Timeout:

The amount of time in milliseconds that originations will attempt to ring the originating extension before giving up.

ConfBridge:If checked, app_confbridge will be used for dynamically created conference rooms. If unchecked, app_meetme will be used.

Recording Agents

This section lists the Recording Agents that are currently registered with the server. You can also edit the Recording Agent settings from this section. See Recording Agents for more information.

Only Super Administrators can manage Recording Agent Settings. See Administrators for more information.

Voicemail Agents

This section lists the Voicemail Agents that are currently registered with the server and allows administrators to specify which Voicemail Agents provide voicemail data to the current selected Core Server by checking them off in the list. You can also edit the Voicemail Agent settings from this section. See Voicemail Agents for more information.

Only Super Administrators can manage Voicemail Agent Settings. See Administrators for more information.