Professional Documents
Culture Documents
Connector
Programming Guide
Table of contents
1 Introduction ....................................................................................... 4
1.1 Contact ............................................................................................... 4
1.2 Overview ............................................................................................. 4
1.3 Pre-requisites and Restrictions .................................................................. 4
2 Port Declaration in Genesys .................................................................... 4
3 Method Specifications ........................................................................... 4
4 Other Methods..................................................................................... 7
5 Examples ........................................................................................... 7
5.1 Example Directory .................................................................................. 7
5.2 Example Scenario: Receiving Calls .............................................................. 7
6 Log Files .......................................................................................... 12
Legal notice
Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo, are trademarks of Alcatel-Lucent. All
other trademarks are the property of their respective owners.
This document is for informational purpose only. Alcatel-Lucent assumes no responsibility for the
accuracy of the information presented, which is subject to change without notice.
HISTORICAL
1 Introduction
1.1 Contact
1.2 Overview
The OmniGenesys CCIvr Connector interfaces between a CCIvr and one Genesys T-Servers.
• OmniGenesys CCIvr Connector, release 9.0 or above (see the OmniGenesys CCIvr
Connector Installation guide)
• Switch-specific type: 8
• Register: true
3 Method Specifications
The COM methods which interface between the CCIvr and the OmniGenesys Tserver in the COM Call
building blocks are specified as follows:
RegMe
GetReg
AttachMultipleKeyValuePair
Goal: Attach user data to the T-Server that is related the call
Input Parameters:
• KeyValue: type string
DeleteAllUserData
DeleteUserData
GetAllKeyValuePairs
Input Parameter:
• Separator: type string
Output Parameter:
• Pairs: type string
Notes: the return value is a composed by all pairs “key / value” like key1;value1;key2;value2;
GetSimpleValueFromKey
Goal: Return the value associated to the specified key, from the user data
Input Parameter:
• Key: type string
Output Parameter:
• Value: type string
SendUserDataAndEvent
Output Parameter:
• Value: type string
SendUserDataAndWait
Goal: Send user Data by key/value pair and wait for the response.
Input Parameter:
• TheDn: type string
Output Parameter:
• Value: type string
WaitForNewEventUserEvent
4 Other Methods
Some functions are not implemented or make the same function like an other one.
For ascendant compatible version, these functions doesn't disappeared but now there are not
implemented or make the same work than an other one...
5 Examples
5.1 Example Directory
Application examples are provided to facilitate application operation.
They are available in the installation directory: \Samples
• [C:2] – BB Calculation
• [F:2] – BB StopPhoneCall
[B;2] Call COM Buildigng Block – Call the Method RegMe() to Register
The method relating to Register is RegMe. You must enter a parameter, in this example the
monitored used device.
In this example, we’re using the number of the caller device.
The dispatch pointer is the current pointer towards the COM object, obtained from the Register BB.
In this example, the attached data is: key1;value1;key2. To attach this data, create a variable
(type string) in which the Calculation BB result is stored. A temporary variable value (type string) is
used and contains the following string : key1;value1;key2;
Calculation Building Block: Get Current Time and Concatenate with the Last Building Block Result
Value
Final step: again, the dispatch pointer is the current pointer towards the COM object, obtained
from Register BB.
Attach the ReceiveCallSample script to several ports in the Configuration Panel (Launched from the
CCIvr Login Panel).
6 Log Files
Calling the IVR port in the log file (by default, log files are in the installation directory) of the CCIvr
Connector application provides a log as follows:
[2006-03-13 16:00:12,875] [8652] DEBUG - 31616::Context_Register:: New context activation .....
[2006-03-13 16:00:12,875] [8652] DEBUG - 31616:: EventNewClient, Nbev=4
[2006-03-13 16:00:12,875] [8652] DEBUG - 31616::CDn_SetComplexAction:: Set complex action:
AttachSimpleKeyValuePair, data= key1;value1;key2;16:00:12
[2006-03-13 16:00:12,875] [8652] DEBUG - 31616:: EventNewCmpxAction, Nbev=5
[2006-03-13 16:00:12,875] [8652] DEBUG - 31616::SetCmpxAction::new action AttachSimpleKeyValuePair
[2006-03-13 16:00:12,890] [8572] DEBUG - 31616 :: 31616::CmpxAction:: NewAction is:
itlibAttachSimpleKeyValuePair
[2006-03-13 16:00:12,890] [8572] DEBUG - 31616:: CDn_LookForOneSig:: Event significatif : EventEstablished
[2006-03-13 16:00:12,890] [8572] DEBUG - 31616:: =======>Go for Action : itlibAttachSimpleKeyValuePair
End of Document
www.alcatel-lucent.com/enterprise/services
Mail: professional.services@alcatel-lucent.com