A Switch is an aggregate of telephony resources within a Switching Office.
Most enterprise-level configurations have a one-to-one match between switches and switching offices. However, there may be instances when it is desirable to partition an office into more than one switch, perhaps due to CTI–link capacity limitations, or to create a more efficient and secure numbering plan. In that case, you must define these switches within a switching office.
Filter Name | Type | Description |
---|---|---|
tenant_dbid | int |
|
tserver_dbid | int |
|
DBID
—
tenantDBID
—
Tenant
to which this switch is allocated. Mandatory. Once specified,
cannot be changed.
physSwitchDBID
—
Physical Switch
within which this
switch is defined. Mandatory. Once specified, cannot be changed.
type
—
type
of the physical switch specified in physSwitchDBID
).
See CfgSwitchType
.
name
—
TServerDBID
—
Application
through which the telephony objects
of this switch are controlled. Parameter
tenantDBIDs
of the T-Server must be specified
and match the setting of tenantDBID
of this switch.
One T-Server cannot be associated with more than one switch unless
the switch is of type CFGMultimediaSwitch
. The property
is applicable for 5.1 applications only, for compatibility. Starting
from release 6.0 the association between T-Server and switch have
to be configured using CfgApplication (T-Server) object. See flexibleProperties
in CfgApplication.
linkType
—
CfgLinkType
switchAccessCodes
—
CfgSwitchAccessCode
). When used as an entry
in CfgDeltaSwitch
, it is a pointer to a list of switch access
codes added to the existing list.
DNRange
—
1100-1179, 1190-1195, 1199
).
state
—
CfgObjectState
userProperties
—
The current version of Configuration Server does not
verify correspondence between the switch numbering plan defined
by DNRange
and the actual DN numbers defined within
this switch by number
in CfgDN
. Such
verification may be implemented in one of the
next versions. In versions 5.1.1XX and earlier, it is users' responsibility
to make sure the range covers all actual DNs of the switch in question.
Deletion of Switch X will cause the following events set out in the order of arrival:
switchAccessCodes
of all switches
that were interfaced with Switch X
switchDBID
field
set to Switch X
accessNumbers
of all DNs which
were connected with Switch X
flexibleProperties
of all T-Servers
which were connected with Switch X
CfgDN
for
details)
CfgAgentLogin
for details)
Note: This XML was created using the Configuration Server 7.5 schema.
<CfgSwitch> <DBID value="101" /> <tenantDBID value="1" /> <physSwitchDBID value="101" /> <type value="12" /> <name value="Switch" /> <TServerDBID value="0" /> <linkType value="0" /> <state value="1" /> </CfgSwitch>