Hi Matt,

Thanks for the information. Yes, the issue is definitely with the response. The response should be in SOAP format and not a 0. I'm uncertain why this is happening in your environment so I will need more information.

Have you had any successful responses back to ACE or do they all fail with this error? Have you made any changes to Trainer code or are you using original released version? Can you tell me more about your ACE environment setup? Which service provider are your tel uri endpoints configured for?


Thanks,
Dipesh

Hi Matt,

Based on the error message, it sounds like the response back to server is not formatted correctly. In order to troubleshoot further, can you please provide full HTTP request and response (request coming from ACE to your client as POST and the response your client sends to ACE.)?

You can capture this information by using Wireshark, tcpmon (https://code.google.com/p/tcpmon/), or modifying code to log http req/res details.


Thanks,
Dipesh

Hi Greg,

I would first suggest that you download ACE documentation library so you have all the information available. You can visit http://www.avaya.com/support, Select "Download and Documents" link from top menu, Under product search, search for "Agile Communication Environment". In result window, click on View Documentation. Here you will see full listing of documentation for ACE. Alternatively, I have included document set library link for you:

http://support.avaya.com/css/P8/documents/100169279

In this document library, please review Avaya_ACE_Overview.pdf for architectural overview and also NN10850-007_Avaya_ACE_Web_Services.pdf for ACE API Reference.

Since ACE is exposed in form of SOAP/REST web service, this allows you to choose any environment/language of your preference that can connect to the service. We also have additional information on DevConnect portal that I would recommend reviewing. For example, we have ACE Web Services Trainer application which allows you to emulate and exercise just about all the capabilities provided by ACE Web Service. Please visit following link where you will find information about Trainer in addition to other helpful resources:

https://devconnect.avaya.com/public/dyn/d_dyn.jsp?fn=652

If you have further questions, please let us know.

Thank you,
Dipesh

Hello,

In regards to question #1, could you please clarify in detail what you are trying to accomplish? Are you trying to play voicemail on active call, programatically leave message onto specific voicemail box, or something else?

Thank you!

Brent,

If you subscribe for call notifications on a device (e.g. setting call monitor on device using Call Notification web services startCallNotification API), this will also provide Call ID which you may use to invoke Third Party Call Extension services. With the Call ID you can invoke singleStepTransfer or consult API calls as I mentioned previously.

Brent,

Another note that Third Party Call Extensions does require that the call is built using Third Party Call Control V2 using makeCall. In other words, ACE must be aware of the call for Call Extensions to function.

Similarly if you are working with Third Party Call Control v3, there is transferCallParticipant API that will help achieve transfer. With TPCCv3, the makeCallSession must be used to build the call in order for transfer to work.

As you can see with both of the transfer capabilities of ACE, it requires the call to be outbound.

Brent - I apologize, I overlooked some options that are available to you under Call Extensions web service. Under Call Extensions, you may use singleStepTransfer or redirectCall API's for blind transfer. The singleStepTransfer will act as true blind transfer whereas with redirectCall behaves similarly but only transfer at ringing event.

For warm transfer you may use both consultationCall with consultationComplete API's. These API's put together will provide the warm transfer capability. The consultationCall will place existing call on hold and place call to consulting endpoint. To finish, consultationComplete will transfer the held party to the consulted party.

For more information on these API's, please see Avaya ACE WEB Services documentation - Chapter 8: Third Party Call Extensions.

Please let me know if you have further questions.

Hi Brent,

There is not specific API for transfer but you can use playVoiceXmlMessage API under Audio Call Web Services. This will require for you to create a VoiceXML script in which you can place <transfer> element tag. Here you can define transfer type (bridge, blind, refer) and transfer to VDN. When you invoke playVoiceXmlMessage you will need to provide audioURL path which is location of the VXML script.

Thanks,
Dipesh

I checked ACE appcore log file for your Call ID 3a383a7c-557a-4113-b6d6-c679a0dde1c2. Even though you are receiving call id, ACE is not building the call due to invalid state of your endpoint. I saw following error statement in the log:

2012-06-29 04:02:06,251 DEBUG-[LRMI Connection-pool-1-thread-4][] (ThirdPartyCallContactStateChangeListener.java:141) process-[callId=3a383a7c-557a-4113-b6d6-c679a0dde1c2->(Active)] contact not in INVALID state - returning

To eliminate any softphone related issues, could you try testing using Avaya One-X softphone? I've tried using your credential and endpoints and it is working for me. Thanks!

Hi Parthiban,

How did you login to the two endpoints (sip:20071@avaya.com and sip:20073@avaya.com)? Are you using Avaya One-X SIP Emulator, Avaya Communicator, or IP Phone? Are you able to make calls directly between the two endpoints once logged in?

I just tested your endpoints in the Remote Lab and they are working for me.

It is available in the archives here: http://archive.apache.org/dist/maven/binaries/

With the latest version of maven, have you tried cleaning out the .m2 repository to see if that resolves the issues? Perhaps a library is corrupt. Also, were there new dependencies you added under pom.xml located under war?

If issue still persist please let us know.

Please see attached document for troubleshooting Scopia Conference URL access issues.

In CE 2.0, why am I unable to access Scopia conferences with the URL returned from Collaboration Environment’s createConf()?

In your service, locate and edit the pom.xml inside of the war directory structure:

|-myservice
|---pom.xml
|---myservice-ear
|-----pom.xml
|---myservice-svar
|-----pom.xml
|---myservice-war
|-----pom.xml <- This pom file

Update Collaboration API artifact dependency with new CE version. For example, if you are updating from CE 2.0 SP1 to CE 2.0 SP2 then update the version tag from 2.0.1.0.201011 to 2.0.2.0.202003. The artifactId remains the same as we are dealing with 2.0 version.

<dependency>
<groupId>com.avaya.collaboration.api</groupId>
<artifactId>avaya-aura-collaboration-api-2.0</artifactId>
<version>2.0.2.0.202003</version>
<scope>provided</scope>
</dependency>

After updating pom.xml, save the file and rebuilt the project using Maven.

In CE 2.0, how do I update and recompile my service for a new service pack release?