COuld this include sending calls to an IVR using the Converse-on/converse-off step?
We are finding that there is a significant lag time between the hand off from the PBX to the IVR and I am trying to figure out how to reduce that time...
no, ivr has no relation to multimedia calls. as for time lag, first read this faq for an explanation of this lag, then show me the vector that does converse-on.
Hi Ariadne,
About the significant lag time betwen the hand off from the PBX to the IVR, check that you send the same number of parameters in the converse-on command than you receive in the IVR reception command.
If you send one parameter, let the second parameter empty (not 0).
Hope this help.
We need to send both the ANI (so that we can keep track of time of day based on time zone) and the VDN so that the IVR knows where to send it within the system... Here is a copy of the vector that I am using currently.
Number: 399 Name: IVR PRODUCTION
Multimedia? n Attendant Vectoring? n Meet-me Conf? n Lock? n
Basic? y EAS? y G3V4 Enhanced? y ANI/II-Digits? y ASAI Routing? y
Prompting? y LAI? n G3V4 Adv Route? y CINFO? y BSR? y Holidays? y
Variables? y
01 wait-time 2 secs hearing ringback
02
03 converse-on skill 400 pri m passing ani and vdn
04 collect 5 digits after announcement none for none
05 route-to digits with coverage y
06 route-to number 20826 with cov y if unconditionally
07 stop
Can you verify that the variable you use in the IVR are the same length than the one you send by PBX ?
For exemple :
If you send ANI 16 digits and VDN 5 digits,
check the variables you use in the IVR are the same length.
Usually these variables should be string type.
A last thing : Never use the default variable, always create yours.
first check if the ivr script consider # symbol as an end-of-digits sign. can't remember exactly what's this property name in prompt & collect block, but it's there. if it is turned off, ivr would wait for a specified timeout to expire, and that may cause the lengthy delay.
second, this scheme will always have unavoidable delay in call setup. that's because definity sends these parameters in form of dtmf codes to the ivr, and this process is slow, especially if you have to pass long digit strings. both these parameters are available via cti interface, consider using it.
I am setting up my attd group to also take calls in another location. The problem is I can put in a route-to step to a in-house extension with no problem, but when I try to route-to a regular telephone number, it does not route. this is how I have my vector set up.
01 wait-time 1 secs jearomg romgbacl
02 queue-to attd-group
03 route-to number 919085319375 with cov n if unconditionally
04 goto vector 3 if queue-fail
05 stop
TKS
Meshoo
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.