Universal Call ID
Issue 1.0 May 2003
243
When the communication server is before INTUITY Conversant:
1. The communication server receives an incoming call over an ISDN trunk.
2. The communication server does one of two things:
●
If the incoming call has a UCID (such as UCID “x”), then the communication server
passes it along.
●
If the incoming call does not have an associated UCID, the communication server
creates a new one (such as UCID “y”).
3. The communication server passes the UCID to INTUITY Conversant through an ASAI
connection (via the activation of split/skill or VDN “event notification” by the INTUITY
Conversant).
4. UCID information is sent to the CMS if trunk, VDN(s), and/or split/skill(s) involved in the
call are measured.
INTUITY Conversant transfers a call
The following call scenario involves a Conversant behind the communication server
configuration when Conversant initiates a call transfer after the call is answered by a port
on the INTUITY Conversant that serves as an ACD agent.
1. Call is directed to INTUITY Conversant VRU port (typically by call vectoring) with UCID
information (UCID “x” or UCID “y”).
2. INTUITY Conversant determines the call’s destination and transfers the call (via an
ASAI “third-party transfer” operation).
Switch
Switch
