Routing calls

[CDBlue]

Hi,

I have a situation where I need to route calls coming into a CDN to another number. However, here's the twist, I only want to route every other call to this new number, and the other half I want to route as normal. Does anyone have any ideas that might help?

Thanks in advance,
CDB

 

[ErwinStevanus]

Under what condition do you route the calls? Do you route the call based on caller id?

If yes then you can use clid/wild clid variable to filter the calls for routing.

1. Create a global variable of CLID type or WILDCLID type (example clid_list_gv)
2. Modify your script as follow:

IF (CLID = clid_list_gv) THEN
ROUTE CALL number1_gv
ELSE
ROUTE CALL number2_gv
END IF

 

[bluerigsby]

You might try this option....

/*Set up a new primary script variable using INTEGAR with a value of 0 (i.e. cv_check)
Have the CDN deliver all calls to this Primary script . When the 1st call enters
this script,it checks the variable & if value = 0 the normal
The script you use is executed which is now a secondary script as you've remove it from the master*/

IF cv_check = 0 THEN
ASSIGN 1 TO cv_check
EXECUTE SCRIPT normal_script
END IF

/* If cv_check is 1 which it will be for the next call, either ROUTE the call to your
alternate number or execute another script depending on where this call is going*/

IF cv_check = 1 THEN
ASSIGN 0 TO cv_check
ROUTE CALL to xxxxx
END IF

/* The next call gets the cv_check 0 treatment again*/

No promises, I have not tried it live but I think this works.

 

[iptuser]

A slightly different way may be to assign a variable as above and increment for every call by one.
First call has a variable of one then route/ execute .....
Increment variable by 1
Second call is assigned the incremented variable then .......

At the start of the script there is also a check variable , is the variable greater then 1 then reset variable back to 0

Hopefully every call will either be 1 or 2 and they will change between the calls allowing the alternative routing


makes sense ?


Wayne

 

[sandyml]

Keep in mind that a call variable's default can be set for a call as it progresses through Symposium, the next call coming in still sees the original default. The value changes for that particular call, but it is not changing the default value that is actually set for that call variable..

 

[ErwinStevanus]

I agree with sandyml about the call variable.

How about using a simple text file to keep the call check (toggle 0 and 1)? Can we using HDX to manipulate data from a text file? Has anybody done this before?

Here is the logic:
1. Get call status from the text file
2. if status = 0 then
set status = 1
route call to CDN A
else
set status = 0
route call to CDN B
end if

 

[CDBlue]

Thanks for the tips guys. I've tried using a call variable already and it didn't work, since the call variable goes back to the default (as specified in the call variable section in symposium) once a call is finished. A global variable would have worked fine, but unfortunately you cannot change the value of a global variable from a script.

What we ended up doing was splitting the calls at our toll-free level. 1/2 the calls go to one CDN, and the other half are being routed to the other CDN right from our toll-free. We'll see how it works since this goes live only on Monday for a test.

 

[sandyml]

This actually is a feature that will be available in Release 5.0 -- the wild variable feature.