I assume you are using Beta2...

Try this:

tls://10.1.1.220:9000?TlsConnection.authReqd=false&filter=KeepAlive

________________________________

From: cuae-developers-bounces@developer.cisco.com on behalf of Shahed Moolji
Sent: Wed 8/13/2008 6:32 AM
To: cuae-developers@developer.cisco.com
Subject: [Cuae-developers] TimeOut Exception on registerApplication


Hi,

I am trying to deploy a simple MakeCall application using etch / java.

I am using the wiki example as a template, and have been able to
package and install the app.

However, when I execute the application I get an exception on
registerApplication.

I am using TCP as the transport, and as you can see from the output
below, I am able to upload my app and
use the Web Interface with TCP.

I have tried the following uri's for registering but neither seem to work

tcp://10.1.1.220:9001

tcp://10.1.1.220:9001?&TcpTransport.reconnectDelay=4000

The app is enabled and running on the server and all services are running.

I cant see any errors on in the AppServer or Mgmt logs.

Any ideas ?

Thanks
Shahed.


C:\WORK\src\ETCH01\MakeCall>cuae package
Created package file "C:\WORK\src\ETCH01\MakeCall\bin\MakeCall.mca"

C:\WORK\src\ETCH01\MakeCall>cuae update
The project property file MakeCall.properties is missing.
Enter the hostname or IP address of the management service (for
example: localhost, 1.1.1.1): 10.1.1.220
Protocol? [tcp or tls] tcp
Generated mgmt-service uri: tcp://10.1.1.220:9001
Enter management service login username: administrator
Enter management service login password:
Application : C:\WORK\src\ETCH01\MakeCall\bin\MakeCall.mca
Uploading : ================================> 100%
Application has been updated successfully

C:\WORK\src\ETCH01\MakeCall>cd dist

C:\WORK\src\ETCH01\MakeCall\dist>java -cp "c:\Program
Files\Etch\etch-0.96.0\lib\etch-java-runtime.jar";MakeCall.jar
com.voicetest.cuae.makecall.MainMakeCallClient
Exception in thread "main" etch.util.TimeoutException: timeout waiting
for cisco.uc.cuae.EtchBridge._result_registerApplication(-794886677)
at etch.bindings.java.transport.DefaultDeliveryService.endcall(DefaultDeliveryService.java:190)
at etch.bindings.java.support.RemoteBase._endcall(RemoteBase.java:101)
at cisco.uc.cuae.RemoteEtchBridgeServer$_Async._end_registerApplication(RemoteEtchBridgeServer.java:229)
at cisco.uc.cuae.RemoteEtchBridgeServer.registerApplication(RemoteEtchBridgeServer.java:69)
at com.voicerite.cuae.makecall.RemoteMakeCallServer.registerApplication(RemoteMakeCallServer.java:71)
at com.voicerite.cuae.makecall.MainMakeCallClient.main(MainMakeCallClient.java:34)
_______________________________________________
Cuae-developers mailing list
Cuae-developers@developer.cisco.com

_______________________________________________
Cuae-developers mailing list
Cuae-developers@developer.cisco.com

Attachment not added (content type not allowed): "att1.html"

Open C:\Program Files\Cisco Systems\Unified Application Environment\AppServer\AppServerService.exe.config

Step1:
Change
<add key="EtchBridgeCertificate" value="Etch"/>

to
<add key="EtchBridgeCertificate" value=""/>

then save the file

Step2:
Restart Application Server from management console

Step3:
Change your application's connection uri to
tcp://10.1.1.220:9000?filter=KeepAlive

________________________________

From: shahed100@gmail.com on behalf of Shahed Moolji
Sent: Wed 8/13/2008 7:05 AM
To: J.D. Liau (jliau)
Cc: cuae-developers@developer.cisco.com
Subject: Re: [Cuae-developers] TimeOut Exception on registerApplication


Thanks J.D.

That worked fine
The App works with no errors and I even get the TTS to play !!

Yes I am using Beta 2.

So now my next question is, :- I have the mgmt service running tcp,
but the etch bridge seems to be running tls ?

Can I also change this to use tcp ?

Not that I have anything against TLS :-) I just want to get a better
understanding of the setup and component interaction...

Thanks
Shahed


2008/8/13 J.D. Liau (jliau) <jliau@cisco.com>:

_______________________________________________
Cuae-developers mailing list
Cuae-developers@developer.cisco.com

Attachment not added (content type not allowed): "att1.html"

Sorry I sent the wrong link. Here is the link to the page on Etch
Bridge TLS from the Beta-2 Release Notes.

http://developer.cisco.com/web/cuae/wikidocs?src=/wiki/display/CUAE/2.5%
25281%2529+Beta+2+Notes+-+Etch+Bridge+TLS

To Disable TLS on Etch Bridge

If you do not want to use TLS for encryption or authentication, follow
these procedures:

1. Open C:\Program Files\Cisco Systems\Unified Application
Environment\AppServer\AppServerService.exe.config.
2. Set the EtchBridgeCertificate value to "".
3. Restart the Cisco Unified Application Server.

Jan

-----Original Message-----
From: cuae-developers-bounces@developer.cisco.com
mailto:cuae-developers-bounces@developer.cisco.com On Behalf Of Jan
Capps (jacapps)
Sent: Wednesday, August 13, 2008 9:28 AM
To: Shahed Moolji; J.D. Liau (jliau)
Cc: cuae-developers@developer.cisco.com
Subject: Re: [Cuae-developers] TimeOut Exception on registerApplication

Shahed,

The instructions for turning TLS for the Etch Bridge are located here.
I have pulled out the relevant part. Look at step 5 and on.
http://cuae/confluence/display/CUAE/CUAE+2.5(1)+Beta-2

Jan

Etch Bridge:

1. Etch Bridge adds TLS support, which means Etch application and
plugin must connect to Etch Bridge using TLS. By default, encryption is
ON but authentication is OFF.
2. Etch Bridge adds KeepAlive support. By default, the KeepAlive
messages are 15 seconds apart and if 4 KeepAlive messages fail then
force a reconnect.
3. Etch Bridge add MaxPacketSize support and set it to 100KB (-8
bytes header) by default.
4. CUAE platform installer will generate the certificates
(Personal:Etch, Trusted Root:Rootet) during installation for production.
For development, please follow the instruction in this page to create
both certificates and import the root certificate into trusted store
manually.


5. To turn off TLS support. Open AppServer.config (console mode) or
AppServerService.config (service mode) and set "EtchBridgeCertificate"
value to "" then restart AppServer.
6. To turn off KeepAlive support. Open AppServer.config (console
mode) or AppServerService.config (service mode) and set
"EtchBridgeKeepAliveDelay" value to "0" then restart AppServer.
7. To use default packet size. Open AppServer.config (console mode)
or AppServerService.config (service mode) and set
"EtchBridgeMaxPacketSize" value to "" then restart AppServer.
8. Locale support.

-----Original Message-----
From: cuae-developers-bounces@developer.cisco.com
mailto:cuae-developers-bounces@developer.cisco.com On Behalf Of Shahed
Moolji
Sent: Wednesday, August 13, 2008 9:05 AM
To: J.D. Liau (jliau)
Cc: cuae-developers@developer.cisco.com
Subject: Re: [Cuae-developers] TimeOut Exception on registerApplication

Thanks J.D.

That worked fine
The App works with no errors and I even get the TTS to play !!

Yes I am using Beta 2.

So now my next question is, :- I have the mgmt service running tcp, but
the etch bridge seems to be running tls ?

Can I also change this to use tcp ?

Not that I have anything against TLS :-) I just want to get a better
understanding of the setup and component interaction...

Thanks
Shahed


2008/8/13 J.D. Liau (jliau) <jliau@cisco.com>:
running.

etch.bindings.java.transport.DefaultDeliveryService.endcall(DefaultDeliv
eryService.java:190)
cisco.uc.cuae.RemoteEtchBridgeServer$_Async._end_registerApplication(Rem
oteEtchBridgeServer.java:229)
cisco.uc.cuae.RemoteEtchBridgeServer.registerApplication(RemoteEtchBridg
eServer.java:69)
com.voicerite.cuae.makecall.RemoteMakeCallServer.registerApplication(Rem
oteMakeCallServer.java:71)
_______________________________________________
Cuae-developers mailing list
Cuae-developers@developer.cisco.com

_______________________________________________
Cuae-developers mailing list
Cuae-developers@developer.cisco.com

_______________________________________________
Cuae-developers mailing list
Cuae-developers@developer.cisco.com