Cisco Cisco E-Mail Manager Unity Integration Option テクニカルリファレンス
ICM Software Configuration
29
29
29
off hardphone support add ―/h n‖ to your agent devices Parameter string
field.
See the Aastra ARI Release Notes for more details on agent device
See the Aastra ARI Release Notes for more details on agent device
configuration.
4.2.2. Translation Route Target DNIS
Every Translation Route Target DNIS that is configured for this peripheral
must be configured in the peripheral monitor table. Set Type to ―VDN‖,
the Config. Param. to ―SCI_REQ‖ and enter the DNIS value in the
Extension field.
4.2.3. Virtual VRU Scripts
For Virtual VRU Script support you need to configure your Virtual VRU
Scripts in the Peripheral Monitor table. All Virtual VRU Scripts
configured on the switch must have an entry of type VDN and the
Extension set to the ACD Pilot Directory number. The Virtual VRU Script
name in the Config. Param. field must match the exact name configured in
the Network VRU Script List.
Additionally there must be one entry of type VDN and Config. Param
Additionally there must be one entry of type VDN and Config. Param
―SCI_RESULT‖ in order to give the control back to ICM after a Virtual
VRU Script is finished.
4.3. Skill Group Configuration
Configure ICM Skillgroups as described in IPCC Installation and
Configuration Guide for Cisco IPCC Enterprise Edition
Configuration Guide for Cisco IPCC Enterprise Edition
.
4.4. Agent Configuration
Configure your agents using the Agent Configuration tools. If hardphone
support is enabled the AgentID (Peripheral number) must match the Agent
Identification configured on the Pointspan PBX. If an unconfigured agent
logs in to a monitored device, the router dynamically creates this agent in
ICM configuration database.
The ICM Software and PointSpan PBX agent mapping is as follows:
The ICM Software and PointSpan PBX agent mapping is as follows:
ICM Software
PointSpan PBX
Agent
Agent
Agent Peripheral Number
Agent Identification