Collected Digits

[skarkera]

We have a Definity Prologix in our enterprise. We are implementing Siebel Enterprise applications with Dialogic CT-Connect 4.0 server and Dialogic Call Information Manager 2.0 for CTI functionality.

All configuration seems to be okay and we are getting ANI and DNIS information from the switch and we are able to screen pops.

We have a vector that plays a message and collects 6 digits that I want to pass to Siebel for doing a query. Please let me know if we can have variables in the vectors that can be referred to pass the collected digits.

Thanks in advance,
Sunil

 

[dimas]

Hi
There are vector commands for example:
01 collect 6 digits after announcement YYYY (your message)
02 route-to digits with coverage y

or
01 collect 6 digits after announcemen YYYY
02 goto step 05 if digits = (< or > or <= ...) 12345
03
04
05 route-to number ZZZZZZ

Is it an answer for your question?

 

[skarkera]

Thanks. I have a very similar vector. My vector collects the digits and passes it to another VDN that I monitor from my Dialogic CTI server using an ASAI link to the MAP-D board installed on my Lucent Definity Prologix switch. I do not know how to aquire that collected digits.

Thanks,
Sunil

 

[europe]

Sunil,

Have you tried putting ADJUNCT-ROUTE in the vector, that way the DEFINITY is suposed to hand over the call control towards the specified CTI extension, all info including the collected digits should be passed over.


Kind regards,

Europe

 

[europe]

Sunil,

This is what I found in the manual about the adjunct route:


The adjunct routing command provides a means for an adjunct ASAI processor to specify
the destination of a call. The switch provides information in an ASAI route request
message that the ASAI adjunct can use to first access a database and then determine a
route for the call. In a typical application, the ASAI adjunct might use the dialed number,
the Calling Party Number (CPN/BN), or the digits collected via Call Prompting to access
caller information and thereby determine the call route.
An adjunct specified in an adjunct routing command can route a call to an internal
number, an external number, a split, a VDN, an announcement extension, or a particular
agent. An adjunct can also provide priority ringing and priority queuing.


an example of a simple vector that uses adjunct routing:
1. adjunct routing link 1111
2. wait-time 60 seconds hearing ringback
3. route-to number 0 with cov n if unconditionally
4. disconnect after announcement 2000

In this vector, 1111 is the extension number of an ASAI link. Each ASAI link has a unique
extension number, even in a configuration where there might be multiple ASAI links to
the same adjunct.
When a call encounters an adjunct routing command, and if the call is not queued to a
split, the switch sends an ASAI message requesting a call route over the specified adjunct
link. The following list identifies the contents of the message, along with a comment or a
brief explanation for each item:

Calling number information.
Calling party number or billing number
(CPN/BN) provided by ISDN-PRI or R2MFC signaling facilities. If the call originates from a local switch extension, this extension is the calling number.

Originating line information (II-digits).
Two-digit code provided by ISDN-PRI facilities indicating the type of originating line being used.

Called number.
Originally called extension (if a call is forwarded to a VDN), or the first VDN through which the call was routed (if the call was not forwarded to the VDN).

Routing VDN.
Last VDN that routed the call to the vector that contains the adjunct routing command.

Call identifier.
ASAI identifier that permits the ASAI adjunct to track multiple calls via either Event Notification or Third Party Call Control. (See the DEFINITY Enterprise Communications Server Release 8 CallVisor ASAI Technical Reference for more information on ASAI.)

Look-Ahead Interflow information (if any).
Includes the original VDN display information, the priority level of the call at the originating switch, and the time that the call entered vector processing. (See Chapter 11.)

Digits collected via Call Prompting or Caller Information Forwarding (CINFO)
(if any; maximum of 16 digits). Digits are collected by the most recent collect digits command. (See Chapter 10 and Chapter 7.)

User-to-User Information (if any).
User-provided data associated with the call. If provided by ASAI, this data was provided in a 3rd-Party-Make-Call, Auto-Dial, or Route-Select message. If provided over ISDN, the data was in the SETUP message that delivered the call to this switch.

If the call is queued, the adjunct routing step is ignored, and vector processing continues at
the next vector step. :-Q

all this comes out the Call Vectoring/Expert Agent Selection (EAS) Guide manual try to get your hands on that !!

kind regards,

Europe

 

[roche]

Sunil,
We used to use CT-Connect in our call center. I agree with europe that the adjunct route is the option you need to use. You should have an ASAI extension assigned in the switch that points to the link(of the CT-Connect server) that is configured on the MAPD board. This will be the extension you need to use with the adjunct route command. Here is an example of what your vector will looke like.

1.wait 0 secs hearing ringback
2.collect 6 digits after announcement xxxx
3.adjunct rounte link xxxx
4.stop

Hope this helps

Roche