Cisco Cisco Computer Telephony Integration OS 8.5 Guide De Référence
3-12
CTI Driver for Siebel 7 Reference Guide for Cisco ICM/IPCC Enterprise & Hosted Editions
Cisco CTI OS Release 7.2(1)
Chapter 3 Customization
Siebel Commands
Siebel Commands
Siebel commands can be customized to translate to Driver commands through the DEF file. Commands
are mapped using Device command entries. These provide a mechanism for mapping commands, tool
tips, hotkeys, and passing command parameters. It is possible to use the CmdData entries to pop up
dialog boxes to query for arguments before sending the command to the driver.
are mapped using Device command entries. These provide a mechanism for mapping commands, tool
tips, hotkeys, and passing command parameters. It is possible to use the CmdData entries to pop up
dialog boxes to query for arguments before sending the command to the driver.
displays a portion of a sample DEF file. The Siebel CTI toolbar button for Login needs to
be invoked as a sub-command of the SignOnGroupInMenu command (refer to the Siebel documentation
for more details). The entry also defines several parameters to pass with the login command.
for more details). The entry also defines several parameters to pass with the login command.
Note
The example only demonstrates the Login command.
Example 3-6
Sample DEF File
[Command:SignOnGroupInMenu]
SubCommand_1 = "LoginToPBX"
Profile = ""
MenuPosition = "20"
Comments = ""
Title = "Log In"
ConnectedPartyDeviceIDType1 ...
ConnectedPartyDeviceIDType6
ConnectedPartyDeviceIDType6
Indicates the type of the device
identifier supplied in the following
ConnectedPartyDeviceID floating
field. There may be more than one
ConnectedPartyDeviceIDType field in
the message (see NumParties, above).
identifier supplied in the following
ConnectedPartyDeviceID floating
field. There may be more than one
ConnectedPartyDeviceIDType field in
the message (see NumParties, above).
ConnectedPartyDeviceID1 ...
ConnectedPartyDeviceID6
ConnectedPartyDeviceID6
The device identifier of one of the call
parties. There may be more than one
ConnectedPartyDeviceID field in the
message (see NumParties, above).
parties. There may be more than one
ConnectedPartyDeviceID field in the
message (see NumParties, above).
Table 3-6
Line Types
Parameter Name
Arguments Passed
DID
Direct inward call
Help
Assistance call
InboundACD
Inbound ACD call
Inside
Inside call
Message
Voice message call
OutboundACD
Outbound ACD call
Supervisor
Supervisor call
Unknown
Any purpose call
Table 3-5
Additional Parameters for the Event Conferenced Device Event (continued)
Parameter Name
Arguments Passed