Problem implementing call back script

Question

I'm having problems getting my message call back script to work.  The idea is that someone makes a call and if no agents are available after a few minutes they'll get a prompt asking them to leave their phone number for an agent to call them back.  The bulk of the script is taken from Cisco's script repository.  Everything works except for when the call terminates and is supposed to place a call to the BaseLineMessageCallback.aef script which will seek out the next available agent and then play a message stating the caller's phone number and a brief message.  Seems like no matter what I try when it goes to redirect the call to the BaseLineMessageCallback script the status is BUSY.  Here are the steps that I've done so far
1.) Created trigger for BaseLineMessageCallBack with the phone number of 6580
2.) Created a 2nd Call Control Group with the ID of 5, CTI route points are 7300 and 7301
3.) Created separate Dialog Group with the ID of 1
4.) The AdvMessageQueueing script is using the same CSS and Partition as BaseLineMessageCallBack, phone number is 6507
5.) Set Media Termination Point to True for Call Control Group 5.
6.) AdvMessageQueueing and BaseLineMessageCallBack are using different call control group and dialog group
I'm able to call both the 6580 and 6507 numbers without a problem from my phone.  The problem is just the redirecting from 6507 to 6580.
Any ideas?

Answer 1

There's a lot more that we'll need to know, to properly figure this out for you.  I would suggest this: start out small, and validate that you can even make a call with the Place Call step to a trigger, since that seems to be the area you've highlighted as a problem.
You can do this very easily by creating a brand new script with a single variable and two steps.  It's really just that simple.  No extra trigger, no application, just the one script, with its one variable, and two steps.  You can think of it like a disposible napkin that you'll use one time and then throw away.
Script1
Variables
Contact c = null
Steps
StartPlace Call (dest = "6507"; timeout = 30; CCG ID = 5; dialog group = 1; contact = c)  Successful    /* Place a comment step here, so when the called script answers, we should see this highlight in red. */  ...End
Start a reactive debug in the script editor: CTRL+Shift+R
For the Script, select: AdvMessageQueueing.aef (I think I read your post correctly and 6507 is the AdvMessageQueueing.aef script, right?  If not, let me know because that's important for this test)
For the Timeout, select: 60
Click OK
Now, make sure your Script1 window is the active window and press F10 three times (1 time to start active debugging; 1 time execute the Start step; 1 time to execute the Place Call step - Note 1: the Place Call Step will remain highlighted in red for now - Note 2: If you press F10 too quickly, the editor may not recognize your key press, so be sure to pause between key presses at this juncture).
What you should see happen is, a new window should open, and it should be the AdvMessageQueueing.aef script, but in reactive debug mode.  Since this is a phone call test, you will need to make sure the AdvMessageQueueing.aef script window is active and press F10 until the red highlighted step is whatever step immediately after the Accept step.  This answers the call and back in Script1 you should see the comment step highlighted now.
If you don't see that, then you know there is a problem with a CTI Port in CCG 5 calling a CTI Port in whatever CCG 6507 is associated with.  I know you said the Partitions and CSSes are the same, but I would ask that you just double check that the CSS on CCG5 contains the Partitions for both the 6507 Trigger and the CCG 6507 is associated with.
Let me know if you get past that part, or if we need to address any problems you encounter.
Good luck.
Anthony Holloway
Please use the star ratings to help drive great content to the top of searches.