Author Message
CraigJohnson5
Joined: Oct 24, 2013
Messages: 413
Offline
I am able to make calls with both TPCC v2 and TPCC v3 with your extensions over the VPN tunnel. I used 20072 and 20073. What application are you using to make your calls with ACE?
CraigJohnson5
Joined: Oct 24, 2013
Messages: 413
Offline
Nevermind the application question, I see you are using the ACE Exhibitor.
BalaSriram
Joined: Dec 23, 2013
Messages: 0
Offline
craig, I am sitting in India and can coordinate for this testing. Let me know what time suits you or if you can give me the procedure, i can follow and share details that you might need.
DipeshGandhi2 [Avatar]

Joined: Nov 14, 2011
Messages: 35
Offline
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!

Dipesh Gandhi
Software Engineer, Avaya DevConnect

BalaSriram
Joined: Dec 23, 2013
Messages: 0
Offline
Dipesh

You are correct. the problem was with the OneX communicator. We used a older version of OneX communicator where this issue was happening. We upgraded to the 6.x version of Communicator and the events were populated properly and we were able to test the basic functionality. Thanks a lot for your help.

Go to:   
Mobile view