You can set up Groups of DNs for use in network-level routing algorithms and in some types of statistics. Consult solution-specific documentation to see if you need to set up DN Groups.
When you are specifying a DN Group, remember that the DNs comprising this group must have the same telephony event model.
Filter Name | Type | Description |
---|---|---|
tenant_dbid | int |
|
dn_group_type | int |
CfgDNGroupType ). If
specified, Configuration Server will return information only about
the DN groups of this type.
|
dn_dbid | int |
|
state | int |
CfgObjectState ). If specified, Configuration Server
will return information only about DN groups that are currently
in this state.
|
name | string |
|
dbid | int |
|
groupInfo
—
CfgGroup
containing
general information about this group. Mandatory.
type
—
CfgDNGroupType
.
DNs
—
CfgDNInfo
).
The name of a DN group must be unique within the tenant, but can coincide with the names of access groups, place groups and agent groups of the same tenant.
The name of a DN group cannot be changed until there is at
least one DN listed in this group. See DNs property
Deletion of DN Group X will cause the following events set out in the order of arrival:
groupDBID
of all DNs that used
DN Group X for number translation
Note: This XML was created using the Configuration Server 7.5 schema.
<CfgDNGroup> <CfgGroup> <DBID value="124" /> <tenantDBID value="101" /> <name value="SomeDNs" /> <capacityTableDBID value="0" /> <quotaTableDBID value="0" /> <state value="1" /> <capacityRuleDBID value="0" /> <siteDBID value="0" /> <contractDBID value="0" /> </CfgGroup> <type value="3" /> <DNs> <CfgGroupDN> <DNDBID value="250" /> <trunks value="0" /> </CfgGroupDN> <CfgGroupDN> <DNDBID value="270" /> <trunks value="0" /> </CfgGroupDN> </DNs> </CfgDNGroup>