Cisco Cisco E-Mail Manager Unity Integration Option Riferimenti tecnici
![Cisco](https://files.manualsbrain.com/attachments/7380d0050044647c30f5c24bbbf5d0c0b6d9bb84/common/fit/150/50/faa183d287233c52228cfea3dbc2a127fe780f60564fcb0955d9c3d1cd23/brand_logo.png)
Default Peripheral Route
17
17
2.4. Peripheral Target
Peripheral Targets are the means through which the Unified ICM
maps/directs calls to Services, Skill Groups or Agents. A Peripheral Target
is specified by a Network Trunk Group and a DNIS pair. Each Peripheral
Target is again associated with a single Route.
maps/directs calls to Services, Skill Groups or Agents. A Peripheral Target
is specified by a Network Trunk Group and a DNIS pair. Each Peripheral
Target is again associated with a single Route.
A Route is associated with a Target Type (Service, Skill Group, Agent or
Translation Route). For accounting purposes, each Route is associated with a
Service. It is this mapping that will allow the Peripheral Gateway to define
the CallType (Service) when a new call arrives on the NEC.
Translation Route). For accounting purposes, each Route is associated with a
Service. It is this mapping that will allow the Peripheral Gateway to define
the CallType (Service) when a new call arrives on the NEC.
The DNIS configured in the Unified ICM Peripheral Target must correspond
to the ACD Pilot number defined on the NEC.
to the ACD Pilot number defined on the NEC.
2.5. Trunk Groups and Trunks
To enable reporting on trunk groups, they must be configured in Unified
ICM.
ICM.
Note: Unified ICM Trunk Groups correspond to NEC Routes.
Trunks need not be entered in the Unified ICM trunk configuration. As long
as the trunk groups are configured, the trunks will be automatically
configured by Unified ICM as events are reported for those trunks.
as the trunk groups are configured, the trunks will be automatically
configured by Unified ICM as events are reported for those trunks.
Note: All outbound trunks and their trunk groups must be configured in the
Peripheral Monitor Table – see the chapter on Unified ICM Configuration.
Peripheral Monitor Table – see the chapter on Unified ICM Configuration.
2.6. Default Peripheral Route
If the PG is informed of a call for which there is no Unified ICM Peripheral
Configuration (PeripheralTarget/Route and/or Service not configured), the
call is not tracked. This is likely to occur when the Unified ICM
configuration does not match the configuration defined on the NEC. An
example of this would be when a customer is not routing all call types
handled by the switch, but the CTI Link provides events on all Call Types.
Configuration (PeripheralTarget/Route and/or Service not configured), the
call is not tracked. This is likely to occur when the Unified ICM
configuration does not match the configuration defined on the NEC. An
example of this would be when a customer is not routing all call types
handled by the switch, but the CTI Link provides events on all Call Types.
To allow some type of monitoring of calls which have no definitive
Route/Service mapping, the Unified ICM provides the Peripheral Default
Route.
Route/Service mapping, the Unified ICM provides the Peripheral Default
Route.
The Peripheral Default Route provides a place holder to gather statistics on
calls monitored by the OAI/Infolink Link and which do not map to the
Unified ICM configuration. The Unified ICM will gather Route/Service
statistics associated with these unknown calls along with their Termination
Call details.
calls monitored by the OAI/Infolink Link and which do not map to the
Unified ICM configuration. The Unified ICM will gather Route/Service
statistics associated with these unknown calls along with their Termination
Call details.
From the Termination Call details of the call associated with the Peripheral
Default Route, the customer can track down the unknown call types. The
Termination Call detail will provide the DNIS/Pilot number associated with
the call. The customer can then update the Unified ICM configuration to
include the non-configured call types.
Default Route, the customer can track down the unknown call types. The
Termination Call detail will provide the DNIS/Pilot number associated with
the call. The customer can then update the Unified ICM configuration to
include the non-configured call types.