Place Call from HTTP Triggered Application

[Ian Meyers]

I'm attempting to convert my callback script into a http triggered one where I pass the callback number through a parameter in the http trigger instead of having a caller enter the callback number when prompted.  I am able to get the callback number successfully from this URL http://<IP Address>:9080/Callback?number=<number for Callback> where <number for Callback> is any number on net into a variable within my script.  The problem I'm having now is when it gets to the Place Call step it fails because one of the parameters is a "Call Contact" variable and I don't see how I should populate it and the step fails. Any ideas?

[Anthony Holloway]

Since you said you were converting your callback script, I would assume you have a place call step already defined, no?

A place call step requires the following:

The number to call - sounds like you got this one covered

The call control group id to generate the call from a cti port - can you just copy the number from your existing script step?

The media or dialog group id to assign the call media capabilities - can you just copy the number from your existing script step?

I also forgot to mention you need to create a variable of type Contact and use that on the place call step as well.  Is that the piece you're needing?

[Ian Meyers]

I have all of that defined the same. Are you saying it's ok that the Call
Contact's value is null?

[Anthony Holloway]

No, you'll need to create a variable of type Contact, and assign this variable to the Place Call step.  Have you done that?  Can you screenshot the properties of the step?

[Ian Meyers]

I resolved the issue.  Turns out it was ok that the value of Call Contact was "null".  The Place call step failed in test because of the different call control group value in the different environment.  I updated that value in the place call step and everything worked fine. The Call Contact variable updated once the place call step was successful in the new http triggered application the same as it did in the call triggered application.  Thanks for responding!