) script. I
>>> changed to the Call Subflow and the issues went away for me.
>>>
>>>
>>>
>>> From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of
>>> Anthony Holloway
>>> Sent: Tuesday, July 18, 2017 5:13 PM
>&g
;> *From:* cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] *On
>> Behalf Of *Anthony Holloway
>> *Sent:* Tuesday, July 18, 2017 5:13 PM
>> *To:* Cisco VoIP Group <cisco-voip@puck.nether.net>
>> *Subject:* [cisco-voip] UCCX Custom Call Variables - Script to Scr
Agents transferring back in is no issue. We do this for post call surveys
and can write CCV for those. It's specifically for script to script
transfers where I cannot do what I need to do. I like your thought on
Context Service, and possibly tracking a customer journey that way. Seems
well
ay, July 18, 2017 5:13 PM
> *To:* Cisco VoIP Group <cisco-voip@puck.nether.net>
> *Subject:* [cisco-voip] UCCX Custom Call Variables - Script to Script
> Transfers
>
>
>
> I'm working on a menu selection tracking solution, which survives across
> transfers between dep
Admittedly, I have not tried exactly that, but what I do know is, the first
and second legs (seq num 0 and num 1) are written to CCD at the same time
(at the end of 0 and at the beginning of 1), and therefore, I would not be
able to record the menu presses in either if I did your suggestion. My
Ryan,
I like the suggestion, and infact was along the lines of something I
thought about: resetting by making the call go through a non-UCCX
controlled device between transfers, but I don't quite like the complexity
it introduces, but more so, I don't like using CDR for reporting. Thanks
for the
I'm handling this more-or-less using Bill's suggestion to set the session and
recall it later. Transferring between scripts is done by releasing the contact
back to the UCM and ponging back in off of a RP or similar that holds another
trigger. Or it's done by the agents when they get a call
changed to the
Call Subflow and the issues went away for me.
From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of
Anthony Holloway
Sent: Tuesday, July 18, 2017 5:13 PM
To: Cisco VoIP Group <cisco-voip@puck.nether.net>
Subject: [cisco-voip] UCCX Custom Call Variables -
What if you write the menu options to a placeholder variable, passing the
placeholder variable in session info and only set the CCV when the contact
terminates?
Sent from a mobile device with very tiny touchscreen input keys. Please excude
my typtos.
> On Jul 18, 2017, at 4:13 PM, Anthony
So, rather than transfer between applications; could you transfer into a CTIRp
then CFWD to the recipient application trigger (assuming retain original
calling party info is enabled)? Then use CAR to report/track hits to the CTIRp?
Sent from my iPhone
On Jul 18, 2017, at 6:15 PM, Anthony
Yes, but I'll hear what you have to say nonetheless.
On Tue, Jul 18, 2017 at 4:23 PM Ryan Huff wrote:
> I assume you are looking for a solution solely within the confines of
> ccx/cuic, without invoking the assistant of CUCM?
>
> Sent from my iPhone
>
> On Jul 18, 2017, at
I assume you are looking for a solution solely within the confines of ccx/cuic,
without invoking the assistant of CUCM?
Sent from my iPhone
On Jul 18, 2017, at 5:13 PM, Anthony Holloway
> wrote:
I'm working on a menu
I'm working on a menu selection tracking solution, which survives across
transfers between department IVRs. It's not going well. In fact, I'm 99%
positive it's not possible, and I might have to look outside of UCCX to
solve this. I.e., DB or WS integration
Scenario: Caller dials Main Line
13 matches
Mail list logo