Genesys CTI User Forum
Genesys CTI User Forum => Genesys CTI Technical Discussion => Topic started by: Todd on October 05, 2007, 07:32:24 PM
-
Does anyone know if it is possible to reset the CED within URS? My issue is I have a multiple menu's that I collect digits with and in a couple of those menus we allow them to "stay on the line...". Well, if a menu was before this, the CED is carrying over to this menu's strategy. Basically, URS thinks the user entered the CED in the second menu, when it was actually the first menu's option. Is there a way to wipe out the CED value?
-
I'll not use CED[] directly, instead attach it to a variable and then blank it (digits = CED[]; digists = "")
-
Thanks for the quick response. I'm not sure how that will help though. I'm still calling the CED function in another strategy further down the call path. If the CED value isn't cleared out, then the variable will have the same value that the CED function would. Make sense? I thought maybe within IRD I could use the SendEvent to clear out the CED value, but I can't seem to get that to work. Is this just not possible with the way Genesys and Avaya work? Should I not have a call path that uses CED more than once?
-
?? CED[] never manteins the value if you jump to another strategy...It's unique on the strategy running
Strategy 1:
Prompt for input > Collected on CED by URS > Save this on a variable x1 > Prompt for another input > Saved on CED [] > Save this on a variable x2
Strategy 2:
Prompt for input > Collected on CED by URS but at this time CED was NULL > Save on a variable x3 .....
And if you attached x1 and x2 you can mantain the data
Now variables are unique per call, so the only case i'd clean them is i want to reuse the variable but why?
Hope this helps
-
That's not what I'm seeing. The CED[] comes from the AttributeCollectedDigits on TServer. This value stays until it is overwritten. Is there a setting in TServer or URS to clear this out that maybe I dont have set? I did notice that I can have this value written to UserData (using preserve-collected-digits = first-event in TServer options), but it appears that even this value is read only and not allowing me to overwrite it.
It might help to know that I'm using announcements from Avaya vectors. I have one VDN with an announcement and a Genesys strategy loaded on that VDN to capture the collected digits. I receive say digit 1 on this strategy and send the call to the next VDN where the caller enters no digits and it times out. When I do a CED on the strategy loaded on the second VDN...the AttributeCollectedDigits is still "1".
-
Todd,
what about wiping them out on the vector?
-
That's an interesting idea. How would one go about doing that in a Vector...as you can tell I'm not a switch guy! :) I know enough about coding vectors to be dangerous!!