cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1115
Views
0
Helpful
2
Replies

Pass UCCX Session Variables from script 1 to script 2

kmeehan36
Level 1
Level 1

My environment is a healthcare administrator approves or denies hospital or doctor precertification.

 

We are on uccx 10.6 and have started to carry session variables.

Member id

Date of birth

city

state

zip code

 

from script 1 to script 2,

 

it is not uncommon to have providers  call multiple times a day, so I map session variables to the session. I can get all data to cross scripts.

What I am seeing is old session data in new calls.

Script 1

I map get session to session,  use the set step to set the session, set set session info then redirect the caller to script 2.

 

Script 2

I map get session to session, then set step to set the session, and finally get session info.

 

Why would I get old session variable data from a new caller? I set Default Session Timeout to 5 minutes thinking this would resolve the issue. However there was no effect.

 

Any assistance is greatly appreciated, I am causing a great deal of disruption and can not roll back.

1 Accepted Solution

Accepted Solutions

Jonathan Schulenberg
Hall of Fame
Hall of Fame
Every JTAPI-triggered execution of the script automatically gets a unique Session referred to as the “— Triggering Contact —“ session. Are you using this or manually creating one manually and specifying your own Session Mapping ID? If the later, my guess is that your Mapping ID isn’t as unique as you think it is. Just use the Triggering Contact session. That should remain intact between scripts as long as you aren’t doing something unsupported in CUCM.

View solution in original post

2 Replies 2

Anthony Holloway
Cisco Employee
Cisco Employee
From a first read, it doesn't sound like you're doing it correctly. However, without seeing your script, it's hard to know for sure. What more can you share? Have you tried to proof your understanding of sessions in a separate call flow? One with the minimal amount of steps and functionality?

Jonathan Schulenberg
Hall of Fame
Hall of Fame
Every JTAPI-triggered execution of the script automatically gets a unique Session referred to as the “— Triggering Contact —“ session. Are you using this or manually creating one manually and specifying your own Session Mapping ID? If the later, my guess is that your Mapping ID isn’t as unique as you think it is. Just use the Triggering Contact session. That should remain intact between scripts as long as you aren’t doing something unsupported in CUCM.