OD version 7

I need to use the AT&T transfer connect feature to pass a call and data to a third party. I already have the AT&T Transfer Connect feature on the AT&T network according to the AT&T reference manual TR 50075.

My issue is setting up OD to place the data in the D-Channel so AT&T can forward the data to the third party.

I have experience using transfer connect to transfer the caller only but this is the first request to use the data forwarding feature.

What do I need to do to get the data in the D-Channel?

Thanks in advance.

I need to override the requestBegin method in a Data object and detect if a call is still valid. How is this done?

Correction... I got it working.

I followed the directions and my projects are not detecting the new version.

I stopped Eclipse.
extracted the jar files to: ~/com.avaya.cc.core_6.0.0.1102/lib/

Restarted Eclipse.

Enabled VXML logging.

When running my app, I still see this as the version:
<meta name="runtime-version" content="06.00.11.03"/>

Will you email me the patch?
scott.thurmond@primerica.com

Ross, it appears I am dealing with the same issue. My version info:

Version: 6.0 (6.0.0.1102) Build id: 201206201400

Would the described patch apply to this version?

Hi, Ross. Will you also send the example to me? scott.thurmond@primerica.com

Thanks.

Is there a way to check to see if a phrase exists in the phraseset before I attempt to use it in a dynamic prompt?


For example, I have this line of code in a dynamic prompt:
add(1, new com.avaya.sce.runtime.PromptElement(com.avaya.sce.runtime.PromptElement.PHRASESET,"LifeOpsVoice:1168_outstanding_owner_requirements",false));

I would like to check to see if
1168_outstanding_owner_requirements exists in phraseset
LifeOpsVoice before I use it and get a runtime error.

Thanks in advance.

This topic is pretty old but I am having the same issue with Orchestration Designer 6. For a number of reasons, I am running a base version of Eclipse (Helios) with the Orchestration Designer 6 P2 plugin.

I am attempting to process data from a web service from a Servlet.

The web service executes fine and I get a response.

On occasion the web service returns an error and I have code to detect the error. My question is from a servlet, how do I branch on a caught Exxeption?

When I catch an Exception or I determine that an error has been generated inside the servletImplementation method how do I branch the caller off to an alternate path.

The examples I have found in devconnect only show samples where an e.printStackTrace() is printed. I actually want to handle the exception. Any help would be appreciated.

Update - I WAS able to get the response unpacked using the 1.4 connector. I would like to understand the what the issue is with the Axis2 connector. When your expert returns next week will you have them look at this?

Thank you!

I am getting the same error using the 1.4 connector.

Ok. I'll try the 1.4 connection and post my findings. Thanks.

No, just Axis2. Which should I be using? I suspected I needed to use the latest connector?

The type is a String.
The value is ""