The Cisco Unified Application Environment 'Etch Bridge' listens on port 9000.

So if you are building an application using the 'cuae' tool, then you will want to change the default port of 4001 in your 'Main_Listener' class to 9000. It'd be nice perhaps if the generated code put in 9000 instead of 4001...

A little background... it's a matter of who does what. It's the Etch compiler that generates the file which has the 4001 port number, and so the cuae tool would have to come back in and replace that 4001 with 9000.

Seth

Did you call registerApplication first, before making any method calls? I think you are connected but you haven't registered yourself, but I can't be for sure from just that trace.

What would also be helpful to look at is the Application Server logs. You can go to /cuaeadmin > Serviceability > Server Logs > AppServer > find the most recent one (it's usually at the bottom at the moment).

You can see mention of registerApplication in slides 25/26/27 from this presentation at the 2.5 CUAE Developer Conference.
http://developer.cisco.com/c/document_library/get_file?folderId=63902&name=DLFE-8202.pdf.

This PDF comes from the Download link on this site...

What version is this server? Mceadmin should indicate the version at
the bottom.

I'm thinking you might be using 2.4.3, which doesn't have the Etch
Bridge component at all, making this impossible.

You could also do a quick sanity check to see if the Etch bridge is
alive (assuming you have version > 2.4.3) by going to the command line
and typing:


At this point, I'm checking the basice, because there seem to be some
fundamental issues with connecting..

Seth
-----Original Message-----
From: cuae-developers-bounces@developer.cisco.com
mailto:cuae-developers-bounces@developer.cisco.com On Behalf Of Vadim
Bruk
Sent: Tuesday, June 17, 2008 6:50 PM
To: cuae-developers@developer.cisco.com
Subject: Re: [Cuae-developers] default server port for Etch based apps

The exception doesn't give me a chance to register my app because it's
thrown when creating a new server instance.
Here is the most recent AppServer log:
2008:06:17::15:16:45(62): Warning: CI This server is not configured
with a hot-standby
2008:06:17::15:16:50(28): Info: HP Connected to H.323 service
successfully
2008:06:17::15:16:51(53): Info: JTP Setting log level for JTAPI service
v3.3 to level: 3
2008:06:17::15:16:51(56): Info: JTP Setting log level for JTAPI service
v4.0 to level: 3
2008:06:17::15:16:51(56): Info: JTP Setting log level for JTAPI service
v4.1 to level: 3
2008:06:17::15:16:51(57): Info: JTP Setting log level for JTAPI service
v4.2 to level: 3
2008:06:17::15:16:51(59): Info: JTP Setting log level for JTAPI service
v5.0 to level: 3
2008:06:17::15:16:51(60): Info: JTP Setting log level for JTAPI service
v5.1 to level: 3
2008:06:17::15:16:51(62): Info: JTP Setting log level for JTAPI service
v6.0 to level: 3
2008:06:17::15:16:51(64): Info: JTP Setting log level for JTAPI service
v6.1 to level: 3
2008:06:17::15:16:51(68): Verbose: Config Device Pool Data id = '1',
version= '6.0', name= 'CCM6', ip= '10.2.0.16', ctiAddr= '10.2.0.16'
2008:06:17::15:16:51(98): Info: JTP Connected to JTAPI service v4.0
successfully
2008:06:17::15:16:52(00): Info: JTP No CTI devices configured for v4.0.
2008:06:17::15:16:52(01): Info: JTP Connected to JTAPI service v3.3
successfully
2008:06:17::15:16:52(01): Info: JTP No CTI devices configured for v3.3.
2008:06:17::15:16:52(01): Info: JTP Connected to JTAPI service v4.1
successfully
2008:06:17::15:16:52(01): Info: JTP No CTI devices configured for v4.1.
2008:06:17::15:16:52(01): Info: JTP Connected to JTAPI service v4.2
successfully
2008:06:17::15:16:52(03): Info: JTP No CTI devices configured for v4.2.
2008:06:17::15:16:52(03): Info: JTP Connected to JTAPI service v5.0
successfully
2008:06:17::15:16:52(03): Info: JTP No CTI devices configured for v5.0.
2008:06:17::15:16:52(04): Info: JTP Connected to JTAPI service v5.1
successfully
2008:06:17::15:16:52(04): Info: JTP No CTI devices configured for v5.1.
2008:06:17::15:16:52(04): Info: JTP Connected to JTAPI service v6.0
successfully
2008:06:17::15:16:52(04): Info: JTP No CTI devices configured for v6.0.
2008:06:17::15:16:52(07): Info: JTP Setting log level for JTAPI service
v3.3 to level: 3
2008:06:17::15:16:52(09): Info: JTP Setting log level for JTAPI service
v4.0 to level: 3
2008:06:17::15:16:52(10): Info: JTP Setting log level for JTAPI service
v4.1 to level: 3
2008:06:17::15:16:52(14): Info: JTP Setting log level for JTAPI service
v4.2 to level: 3
2008:06:17::15:16:52(14): Info: JTP Setting log level for JTAPI service
v5.0 to level: 3
2008:06:17::15:16:52(15): Info: JTP Setting log level for JTAPI service
v5.1 to level: 3
2008:06:17::15:16:52(17): Info: JTP Setting log level for JTAPI service
v6.0 to level: 3
2008:06:17::15:16:52(18): Info: JTP Connected to JTAPI service v6.1
successfully
2008:06:17::15:16:52(18): Info: JTP No CTI devices configured for v6.1.
2008:06:17::15:16:52(20): Info: JTP Setting log level for JTAPI service
v6.1 to level: 3
2008:06:17::15:17:11(23): Info: SIP Connected to Sip service
successfully
2008:06:17::15:17:11(31): Warning: SIP No SIP devices configured. SIP
services are unavailable.
2008:06:17::15:17:14(85): Info: MEP Clearing MRG cache
2008:06:17::15:17:16(78): Info: CDL Adding '10.2.0.16 v6' to DeviceListX
cache list
2008:06:17::15:17:17(87): Info: CDL Device list cache refresh starting.
2008:06:17::15:17:22(15): Info: PP Connected to Presence service
successfully
2008:06:17::15:17:22(50): Info: PP Presence service started,
re-subscribe for notifications.
2008:06:17::15:17:25(65): Warning: CDL No subscribers configured for
cluster 'CCM6'; retrieving data from publisher.
2008:06:17::15:17:28(56): Info: CDL Device list cache refresh complete.

BTW, I had to use /mceadmin context on the server side becuase,
/cuaeadmin doesn't exist.
_______________________________________________
Cuae-developers mailing list
Cuae-developers@developer.cisco.com

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

I was able to do the telnet (the server port is open and the connection got accepted).
Also, here is a line on the bottom of the admin screen:
Firmware v2-3-0 / Software v2.5.0.7057 DEV

Here is the main method:
public static void main( String[] args ) throws Exception
{
// TODO Change to correct URI

RemotejtapitestServer server = null;
String uri = "tcp://10.11.3.23:9000";
System.out.println("Connecting to: " + uri);
server = jtapitestHelper.newServer( uri, null,
new MainjtapitestClient() );

// Connect to the service
server._startAndWaitUp( 4000 );
// TODO Insert Your Code Here
// Disconnect from the service
server._stopAndWaitDown( 4000 );
}

Here is the output which it produces:
Connecting to: tcp://10.11.3.23:9000
Exception in thread "main" java.lang.RuntimeException: unexpected exception sending message
at etch.bindings.java.transport.AbstractDeliveryService.begincall(AbstractDeliveryService.java:108)
at etch.bindings.java.support.RemoteBase._begincall(RemoteBase.java:69)
at cisco.uc.cuae.legacy.RemoteJTapiServer$_Async._begin_jTapiNonTriggeringSubscribe(RemoteJTapiServer.java:1559)
at cisco.uc.cuae.legacy.RemoteJTapiServer.jTapiNonTriggeringSubscribe(RemoteJTapiServer.java:244)
at jtapitest.RemotejtapitestServer.jTapiNonTriggeringSubscribe(RemotejtapitestServer.java:347)
at jtapitest.ImpljtapitestClient.<init>(ImpljtapitestClient.java:23)
at jtapitest.MainjtapitestClient.newjtapitestClient(MainjtapitestClient.java:52)
at jtapitest.jtapitestHelper.newServer(jtapitestHelper.java:48)
at jtapitest.MainjtapitestClient.main(MainjtapitestClient.java:29)
Caused by: java.io.IOException: closed
at etch.util.core.io.TcpConnection.checkOutputStream(TcpConnection.java:606)
at etch.util.core.io.TcpConnection.send(TcpConnection.java:563)
at etch.util.core.io.TcpConnection.data(TcpConnection.java:529)
at etch.util.core.io.Packetizer.packet(Packetizer.java:267)
at etch.bindings.java.transport.Messagizer.messagex(Messagizer.java:132)
at etch.bindings.java.transport.MailboxManager.message(MailboxManager.java:126)
at etch.bindings.java.transport.AbstractDeliveryService.begincall(AbstractDeliveryService.java:104)
... 8 more

Hi Vadim,

Something else is going on here, too.

Because you can see that ' jTapiNonTriggeringSubscribe' is being issued.
So you must be calling this. Where are you calling this? From which
method I mean?

seth

-----Original Message-----
From: cuae-developers-bounces@developer.cisco.com
mailto:cuae-developers-bounces@developer.cisco.com On Behalf Of Scott
Comer (sccomer)
Sent: Wednesday, June 18, 2008 1:30 PM
To: cuae-developers@developer.cisco.com
Subject: Re: [Cuae-developers] default server port for Etch based apps

Vadim,

please delete the server._stopAndWaitDown. apps should not do that. it
closes the connection.

scott out

Vadim Bruk wrote:
exception sending message
etch.bindings.java.transport.AbstractDeliveryService.begincall(AbstractD
eliveryService.java:108)
etch.bindings.java.support.RemoteBase._begincall(RemoteBase.java:69)
cisco.uc.cuae.legacy.RemoteJTapiServer$_Async._begin_jTapiNonTriggeringS
ubscribe(RemoteJTapiServer.java:1559)
cisco.uc.cuae.legacy.RemoteJTapiServer.jTapiNonTriggeringSubscribe(Remot
eJTapiServer.java:244)
jtapitest.RemotejtapitestServer.jTapiNonTriggeringSubscribe(Remotejtapit
estServer.java:347)
jtapitest.ImpljtapitestClient.<init>(ImpljtapitestClient.java:23)
jtapitest.MainjtapitestClient.newjtapitestClient(MainjtapitestClient.jav
a:52)
jtapitest.MainjtapitestClient.main(MainjtapitestClient.java:29)
etch.util.core.io.TcpConnection.checkOutputStream(TcpConnection.java:606
)
etch.bindings.java.transport.Messagizer.messagex(Messagizer.java:132)
etch.bindings.java.transport.MailboxManager.message(MailboxManager.java:
126)
etch.bindings.java.transport.AbstractDeliveryService.begincall(AbstractD
eliveryService.java:104)

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

I've fixed that. It's connecting right now.

Thank you,
Vadim.