Persisting variable between scripts/calls

[jorendhaen]

We are trying to design a system for a customer where the routing is based on a variable.
This variable needs to persist between calls and scripts, this way, one script can set the variable, after which the other script can read the variable.

The system is hosted by 3CX.

We would preferably not send it to another server, as contacting a server every time a call comes is is not ideal.
Where and how can we save this variable?
(we are using the Call Flow Designer)

Thanks!

 

[Evolute IT]

Attach Call Data/Get Call Data

Use names starting with "public_". Those are stored on the call object that goes through the system. It's literally designed for what you want.

 

[jorendhaen]

Attach Call Data/Get Call Data

Use names starting with "public_". Those are stored on the call object that goes through the system. It's literally designed for what you want.

I'm not sure this does what we would like to achieve.
This adds some info to the call, but after the call has ended, this stops to exist.

What we really are trying to achieve is to have a dial code set a certain state.
After setting that state, all incoming calls need to be routed based on the state.
This is why I need a variable that keeps existing after a call has ended and a script has ended.
Is this possible?

Sorry if I wasn't clear enough before.

 

[edossantos_sipcaller]

In that case you can use a 3CX global property. Use the Get Global Property and Set Global Property components:
https://www.3cx.com/docs/manual/cfd-components/#h.2xhp8q9xqoin

From one CFD app you can toggle the value. From a second app you can just read it and route calls accordingly.

 

[jorendhaen]

In that case you can use a 3CX global property. Use the Get Global Property and Set Global Property components:
https://www.3cx.com/docs/manual/cfd-components/#h.2xhp8q9xqoin

From one CFD app you can toggle the value. From a second app you can just read it and route calls accordingly.

That's it!
Thank you!