Cisco Unified Application Environment Developer Forums

« Back to Developers

[Cuae-developers] FW: registering application

Combination View Flat View Tree View
Threads [ Previous | Next ]
[Cuae-developers] FW: registering application
Answer
6/20/08 12:07 AM
Hi Vadim:

Can you set your app server log levels to Verbose (Serviceability >
Trace Configuration > Application Server, Application Manager), rerun
the application and send us back the logs ? It appears an Etch Bridge
issue, but we need to see the logs to confirm.

Thanks,

-Zafar

-----Original Message-----
From: cuae-developers-bounces@developer.cisco.com
mailto:cuae-developers-bounces@developer.cisco.com On Behalf Of
Ramgopal Chockalingam -X (rchockal - Infosys at Cisco)
Sent: Wednesday, June 18, 2008 5:57 PM
To: cuae-developers@developer.cisco.com
Subject: Re: [Cuae-developers] registering application

Hi Vadim,

Hope you are trying to register your application after the server
startAndWaitUp. Do you mind sharing your Main function code over here ?

A working sample would be something like this:

public static void main( String[] args ) throws Exception
{
// TODO Change to correct URI
String uri = "tcp://10.89.31.153:9000";

RemoteInAndOut_JavaServer server =
InAndOut_JavaHelper.newServer( uri, null,
new MainInAndOut_JavaClient() );

// Connect to the service
server._startAndWaitUp( 4000 );

// TODO Insert Your Code Here
String key = server.registerApplication("InAndOut_Java",
"Default", "Administrator", "metreos");
System.out.println("Application Successfully registered
with key:"+key);
System.out.println("Press Any key to exit from the
application");
System.in.read();
// Disconnect from the service
server._stopAndWaitDown( 4000 );
}

regards,
Ram

Cisco Developer Services
http://developer.cisco.com/

-----Original Message-----
From: cuae-developers-bounces@developer.cisco.com
mailto:cuae-developers-bounces@developer.cisco.com On Behalf Of Vadim
Bruk
Sent: Wednesday, June 18, 2008 5:44 PM
To: cuae-developers@developer.cisco.com
Subject: [Cuae-developers] registering application

Hi,

After successful connecting I call registerApplication method and it
blocks there.
I do the method call with valid credentials and partition parameter
"Default". I've traced the method call down - it blocks somewhere after
calling of _end_registerApplication method of RemoteEtchBridgeServer
class.
What could be the problem?

Thank you,
Vadim.
_______________________________________________
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
Flag

Re: [Cuae-developers] FW: registering application
Answer
6/20/08 12:43 AM as a reply to ZAFAR SHAKEEL.
I couldn't attach The AppServer log file. So here it is:
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.
2008:06:17::17:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:17::17:17:23(31): Warning: CDL No subscribers configured for cluster 'CCM6'; retrieving data from publisher.
2008:06:17::17:17:25(68): Info: CDL Device list cache refresh complete.
2008:06:17::19:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:17::19:17:23(18): Warning: CDL No subscribers configured for cluster 'CCM6'; retrieving data from publisher.
2008:06:17::19:17:25(68): Info: CDL Device list cache refresh complete.
2008:06:17::21:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:17::21:17:23(12): Warning: CDL No subscribers configured for cluster 'CCM6'; retrieving data from publisher.
2008:06:17::21:17:25(59): Info: CDL Device list cache refresh complete.
2008:06:17::23:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:17::23:17:23(10): Warning: CDL No subscribers configured for cluster 'CCM6'; retrieving data from publisher.
2008:06:17::23:17:25(59): Info: CDL Device list cache refresh complete.
2008:06:18::01:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:18::01:17:23(12): Warning: CDL No subscribers configured for cluster 'CCM6'; retrieving data from publisher.
2008:06:18::01:17:25(62): Info: CDL Device list cache refresh complete.
2008:06:18::03:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:18::03:17:23(09): Warning: CDL No subscribers configured for cluster 'CCM6'; retrieving data from publisher.
2008:06:18::03:17:25(59): Info: CDL Device list cache refresh complete.
2008:06:18::05:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:18::05:17:23(35): Warning: CDL No subscribers configured for cluster 'CCM6'; retrieving data from publisher.
2008:06:18::05:17:25(85): Info: CDL Device list cache refresh complete.
2008:06:18::07:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:18::07:17:23(12): Warning: CDL No subscribers configured for cluster 'CCM6'; retrieving data from publisher.
2008:06:18::07:17:25(59): Info: CDL Device list cache refresh complete.
2008:06:18::09:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:18::09:17:23(14): Warning: CDL No subscribers configured for cluster 'CCM6'; retrieving data from publisher.
2008:06:18::09:17:25(60): Info: CDL Device list cache refresh complete.
2008:06:18::11:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:18::11:17:23(42): Warning: CDL No subscribers configured for cluster 'CCM6'; retrieving data from publisher.
2008:06:18::11:17:25(90): Info: CDL Device list cache refresh complete.
2008:06:18::13:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:18::13:17:23(56): Warning: CDL No subscribers configured for cluster 'CCM6'; retrieving data from publisher.
2008:06:18::13:17:25(90): Info: CDL Device list cache refresh complete.
2008:06:18::15:12:09(73): Info: AM [Application Diagnostics]
  • No applications installed *
2008:06:18::15:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:18::15:17:23(10): Warning: CDL No subscribers configured for cluster 'CCM6'; retrieving data from publisher.
2008:06:18::15:17:25(60): Info: CDL Device list cache refresh complete.
2008:06:18::17:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:18::17:17:23(12): Warning: CDL No subscribers configured for cluster 'CCM6'; retrieving data from publisher.
2008:06:18::17:17:25(64): Info: CDL Device list cache refresh complete.
2008:06:18::19:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:18::19:17:23(40): Warning: CDL No subscribers configured for cluster 'CCM6'; retrieving data from publisher.
2008:06:18::19:17:25(89): Info: CDL Device list cache refresh complete.
2008:06:18::21:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:18::21:17:23(50): Warning: CDL No subscribers configured for cluster 'CCM6'; retrieving data from publisher.
2008:06:18::21:17:26(00): Info: CDL Device list cache refresh complete.
2008:06:18::23:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:18::23:17:23(20): Warning: CDL No subscribers configured for cluster 'CCM6'; retrieving data from publisher.
2008:06:18::23:17:25(71): Info: CDL Device list cache refresh complete.
2008:06:19::01:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:19::01:17:23(10): Warning: CDL No subscribers configured for cluster 'CCM6'; retrieving data from publisher.
2008:06:19::01:17:25(59): Info: CDL Device list cache refresh complete.
2008:06:19::03:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:19::03:17:23(76): Warning: CDL No subscribers configured for cluster 'CCM6'; retrieving data from publisher.
2008:06:19::03:17:26(26): Info: CDL Device list cache refresh complete.
2008:06:19::05:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:19::05:17:23(10): Warning: CDL No subscribers configured for cluster 'CCM6'; retrieving data from publisher.
2008:06:19::05:17:25(59): Info: CDL Device list cache refresh complete.
2008:06:19::07:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:19::07:17:23(18): Warning: CDL No subscribers configured for cluster 'CCM6'; retrieving data from publisher.
2008:06:19::07:17:25(68): Info: CDL Device list cache refresh complete.
2008:06:19::09:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:19::09:17:23(10): Warning: CDL No subscribers configured for cluster 'CCM6'; retrieving data from publisher.
2008:06:19::09:17:25(59): Info: CDL Device list cache refresh complete.
2008:06:19::11:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:19::11:17:23(39): Warning: CDL No subscribers configured for cluster 'CCM6'; retrieving data from publisher.
2008:06:19::11:17:25(89): Info: CDL Device list cache refresh complete.

Also, there is couple things:
1. I don't have servicability menu in my mceadmin. Instead I had to use path: Main Control Panel > Core Components > Application Server
2. In what dir under Cisco Systems is Application Manager's log files?
Flag

Re: [Cuae-developers] FW: registering application
Answer
6/20/08 1:49 AM as a reply to ZAFAR SHAKEEL.
Vadim:

The logs show the registration request never made it the app server.
Most probably due to network issues. Debug time ...

1. try telnet the sever machine at port 9000 and see if its open

2. move the executable to the cuae server machine, so basically make it
local (this will cross check our network issue theory)

Let us know what you find out.

The admin console could be accessed two ways http://cuae-server/mceadmin
(old gui) and http://cuae-server/cuaeadmin (new improved gui and
recommended one!).

-Zafar

-----Original Message-----
From: cuae-developers-bounces@developer.cisco.com
mailto:cuae-developers-bounces@developer.cisco.com On Behalf Of Vadim
Bruk
Sent: Thursday, June 19, 2008 2:44 PM
To: cuae-developers@developer.cisco.com
Subject: Re: [Cuae-developers] FW: registering application

I couldn't attach The AppServer log file. So here it is:
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.
2008:06:17::17:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:17::17:17:23(31): Warning: CDL No subscribers configured for
cluster 'CCM6'; retrieving data from publisher.
2008:06:17::17:17:25(68): Info: CDL Device list cache refresh complete.
2008:06:17::19:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:17::19:17:23(18): Warning: CDL No subscribers configured for
cluster 'CCM6'; retrieving data from publisher.
2008:06:17::19:17:25(68): Info: CDL Device list cache refresh complete.
2008:06:17::21:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:17::21:17:23(12): Warning: CDL No subscribers configured for
cluster 'CCM6'; retrieving data from publisher.
2008:06:17::21:17:25(59): Info: CDL Device list cache refresh complete.
2008:06:17::23:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:17::23:17:23(10): Warning: CDL No subscribers configured for
cluster 'CCM6'; retrieving data from publisher.
2008:06:17::23:17:25(59): Info: CDL Device list cache refresh complete.
2008:06:18::01:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:18::01:17:23(12): Warning: CDL No subscribers configured for
cluster 'CCM6'; retrieving data from publisher.
2008:06:18::01:17:25(62): Info: CDL Device list cache refresh complete.
2008:06:18::03:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:18::03:17:23(09): Warning: CDL No subscribers configured for
cluster 'CCM6'; retrieving data from publisher.
2008:06:18::03:17:25(59): Info: CDL Device list cache refresh complete.
2008:06:18::05:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:18::05:17:23(35): Warning: CDL No subscribers configured for
cluster 'CCM6'; retrieving data from publisher.
2008:06:18::05:17:25(85): Info: CDL Device list cache refresh complete.
2008:06:18::07:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:18::07:17:23(12): Warning: CDL No subscribers configured for
cluster 'CCM6'; retrieving data from publisher.
2008:06:18::07:17:25(59): Info: CDL Device list cache refresh complete.
2008:06:18::09:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:18::09:17:23(14): Warning: CDL No subscribers configured for
cluster 'CCM6'; retrieving data from publisher.
2008:06:18::09:17:25(60): Info: CDL Device list cache refresh complete.
2008:06:18::11:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:18::11:17:23(42): Warning: CDL No subscribers configured for
cluster 'CCM6'; retrieving data from publisher.
2008:06:18::11:17:25(90): Info: CDL Device list cache refresh complete.
2008:06:18::13:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:18::13:17:23(56): Warning: CDL No subscribers configured for
cluster 'CCM6'; retrieving data from publisher.
2008:06:18::13:17:25(90): Info: CDL Device list cache refresh complete.
2008:06:18::15:12:09(73): Info: AM [Application Diagnostics]
  • No applications installed *
2008:06:18::15:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:18::15:17:23(10): Warning: CDL No subscribers configured for
cluster 'CCM6'; retrieving data from publisher.
2008:06:18::15:17:25(60): Info: CDL Device list cache refresh complete.
2008:06:18::17:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:18::17:17:23(12): Warning: CDL No subscribers configured for
cluster 'CCM6'; retrieving data from publisher.
2008:06:18::17:17:25(64): Info: CDL Device list cache refresh complete.
2008:06:18::19:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:18::19:17:23(40): Warning: CDL No subscribers configured for
cluster 'CCM6'; retrieving data from publisher.
2008:06:18::19:17:25(89): Info: CDL Device list cache refresh complete.
2008:06:18::21:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:18::21:17:23(50): Warning: CDL No subscribers configured for
cluster 'CCM6'; retrieving data from publisher.
2008:06:18::21:17:26(00): Info: CDL Device list cache refresh complete.
2008:06:18::23:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:18::23:17:23(20): Warning: CDL No subscribers configured for
cluster 'CCM6'; retrieving data from publisher.
2008:06:18::23:17:25(71): Info: CDL Device list cache refresh complete.
2008:06:19::01:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:19::01:17:23(10): Warning: CDL No subscribers configured for
cluster 'CCM6'; retrieving data from publisher.
2008:06:19::01:17:25(59): Info: CDL Device list cache refresh complete.
2008:06:19::03:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:19::03:17:23(76): Warning: CDL No subscribers configured for
cluster 'CCM6'; retrieving data from publisher.
2008:06:19::03:17:26(26): Info: CDL Device list cache refresh complete.
2008:06:19::05:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:19::05:17:23(10): Warning: CDL No subscribers configured for
cluster 'CCM6'; retrieving data from publisher.
2008:06:19::05:17:25(59): Info: CDL Device list cache refresh complete.
2008:06:19::07:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:19::07:17:23(18): Warning: CDL No subscribers configured for
cluster 'CCM6'; retrieving data from publisher.
2008:06:19::07:17:25(68): Info: CDL Device list cache refresh complete.
2008:06:19::09:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:19::09:17:23(10): Warning: CDL No subscribers configured for
cluster 'CCM6'; retrieving data from publisher.
2008:06:19::09:17:25(59): Info: CDL Device list cache refresh complete.
2008:06:19::11:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:19::11:17:23(39): Warning: CDL No subscribers configured for
cluster 'CCM6'; retrieving data from publisher.
2008:06:19::11:17:25(89): Info: CDL Device list cache refresh complete.

Also, there is couple things:
1. I don't have servicability menu in my mceadmin. Instead I had to use
path: Main Control Panel > Core Components > Application Server
2. In what dir under Cisco Systems is Application Manager's log files?
_______________________________________________
Cuae-developers mailing list
Cuae-developers@developer.cisco.com

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

Re: [Cuae-developers] FW: registering application
Answer
6/20/08 1:56 AM as a reply to ZAFAR SHAKEEL.
I think he tried that yesterday--pretty sure 9000 is open because he can
get past startAndWaitUp().

Vadim, a question--

In your Impl class, in the constructor--are you calling any methods at
all on the passed in 'server' object? This can cause a deadlock. Be
sure there are no methods called there. I think we went over this
yesterday but I want to be sure you aren't calling any methods there...

In fact, you don't want to invoke any methods on server until after you
call registerApplication(). Is that the case?

Seth

-----Original Message-----
From: cuae-developers-bounces@developer.cisco.com
mailto:cuae-developers-bounces@developer.cisco.com On Behalf Of Zafar
Shakeel (zshakeel)
Sent: Thursday, June 19, 2008 3:50 PM
To: cuae-developers@developer.cisco.com
Subject: Re: [Cuae-developers] FW: registering application

Vadim:

The logs show the registration request never made it the app server.
Most probably due to network issues. Debug time ...

1. try telnet the sever machine at port 9000 and see if its open

2. move the executable to the cuae server machine, so basically make it
local (this will cross check our network issue theory)

Let us know what you find out.

The admin console could be accessed two ways http://cuae-server/mceadmin
(old gui) and http://cuae-server/cuaeadmin (new improved gui and
recommended one!).

-Zafar

-----Original Message-----
From: cuae-developers-bounces@developer.cisco.com
mailto:cuae-developers-bounces@developer.cisco.com On Behalf Of Vadim
Bruk
Sent: Thursday, June 19, 2008 2:44 PM
To: cuae-developers@developer.cisco.com
Subject: Re: [Cuae-developers] FW: registering application

I couldn't attach The AppServer log file. So here it is:
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.
2008:06:17::17:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:17::17:17:23(31): Warning: CDL No subscribers configured for
cluster 'CCM6'; retrieving data from publisher.
2008:06:17::17:17:25(68): Info: CDL Device list cache refresh complete.
2008:06:17::19:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:17::19:17:23(18): Warning: CDL No subscribers configured for
cluster 'CCM6'; retrieving data from publisher.
2008:06:17::19:17:25(68): Info: CDL Device list cache refresh complete.
2008:06:17::21:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:17::21:17:23(12): Warning: CDL No subscribers configured for
cluster 'CCM6'; retrieving data from publisher.
2008:06:17::21:17:25(59): Info: CDL Device list cache refresh complete.
2008:06:17::23:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:17::23:17:23(10): Warning: CDL No subscribers configured for
cluster 'CCM6'; retrieving data from publisher.
2008:06:17::23:17:25(59): Info: CDL Device list cache refresh complete.
2008:06:18::01:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:18::01:17:23(12): Warning: CDL No subscribers configured for
cluster 'CCM6'; retrieving data from publisher.
2008:06:18::01:17:25(62): Info: CDL Device list cache refresh complete.
2008:06:18::03:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:18::03:17:23(09): Warning: CDL No subscribers configured for
cluster 'CCM6'; retrieving data from publisher.
2008:06:18::03:17:25(59): Info: CDL Device list cache refresh complete.
2008:06:18::05:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:18::05:17:23(35): Warning: CDL No subscribers configured for
cluster 'CCM6'; retrieving data from publisher.
2008:06:18::05:17:25(85): Info: CDL Device list cache refresh complete.
2008:06:18::07:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:18::07:17:23(12): Warning: CDL No subscribers configured for
cluster 'CCM6'; retrieving data from publisher.
2008:06:18::07:17:25(59): Info: CDL Device list cache refresh complete.
2008:06:18::09:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:18::09:17:23(14): Warning: CDL No subscribers configured for
cluster 'CCM6'; retrieving data from publisher.
2008:06:18::09:17:25(60): Info: CDL Device list cache refresh complete.
2008:06:18::11:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:18::11:17:23(42): Warning: CDL No subscribers configured for
cluster 'CCM6'; retrieving data from publisher.
2008:06:18::11:17:25(90): Info: CDL Device list cache refresh complete.
2008:06:18::13:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:18::13:17:23(56): Warning: CDL No subscribers configured for
cluster 'CCM6'; retrieving data from publisher.
2008:06:18::13:17:25(90): Info: CDL Device list cache refresh complete.
2008:06:18::15:12:09(73): Info: AM [Application Diagnostics]
  • No applications installed *
2008:06:18::15:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:18::15:17:23(10): Warning: CDL No subscribers configured for
cluster 'CCM6'; retrieving data from publisher.
2008:06:18::15:17:25(60): Info: CDL Device list cache refresh complete.
2008:06:18::17:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:18::17:17:23(12): Warning: CDL No subscribers configured for
cluster 'CCM6'; retrieving data from publisher.
2008:06:18::17:17:25(64): Info: CDL Device list cache refresh complete.
2008:06:18::19:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:18::19:17:23(40): Warning: CDL No subscribers configured for
cluster 'CCM6'; retrieving data from publisher.
2008:06:18::19:17:25(89): Info: CDL Device list cache refresh complete.
2008:06:18::21:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:18::21:17:23(50): Warning: CDL No subscribers configured for
cluster 'CCM6'; retrieving data from publisher.
2008:06:18::21:17:26(00): Info: CDL Device list cache refresh complete.
2008:06:18::23:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:18::23:17:23(20): Warning: CDL No subscribers configured for
cluster 'CCM6'; retrieving data from publisher.
2008:06:18::23:17:25(71): Info: CDL Device list cache refresh complete.
2008:06:19::01:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:19::01:17:23(10): Warning: CDL No subscribers configured for
cluster 'CCM6'; retrieving data from publisher.
2008:06:19::01:17:25(59): Info: CDL Device list cache refresh complete.
2008:06:19::03:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:19::03:17:23(76): Warning: CDL No subscribers configured for
cluster 'CCM6'; retrieving data from publisher.
2008:06:19::03:17:26(26): Info: CDL Device list cache refresh complete.
2008:06:19::05:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:19::05:17:23(10): Warning: CDL No subscribers configured for
cluster 'CCM6'; retrieving data from publisher.
2008:06:19::05:17:25(59): Info: CDL Device list cache refresh complete.
2008:06:19::07:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:19::07:17:23(18): Warning: CDL No subscribers configured for
cluster 'CCM6'; retrieving data from publisher.
2008:06:19::07:17:25(68): Info: CDL Device list cache refresh complete.
2008:06:19::09:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:19::09:17:23(10): Warning: CDL No subscribers configured for
cluster 'CCM6'; retrieving data from publisher.
2008:06:19::09:17:25(59): Info: CDL Device list cache refresh complete.
2008:06:19::11:17:16(79): Info: CDL Device list cache refresh starting.
2008:06:19::11:17:23(39): Warning: CDL No subscribers configured for
cluster 'CCM6'; retrieving data from publisher.
2008:06:19::11:17:25(89): Info: CDL Device list cache refresh complete.

Also, there is couple things:
1. I don't have servicability menu in my mceadmin. Instead I had to use
path: Main Control Panel > Core Components > Application Server
2. In what dir under Cisco Systems is Application Manager's log files?
_______________________________________________
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
Flag

Re: [Cuae-developers] FW: registering application
Answer
6/20/08 2:07 AM as a reply to ZAFAR SHAKEEL.
Seth,

I've rolled back to the original code - whatever has been generated by etch compiler. Only changed to the correct uri and added registerApplication call.
I've also traced with wireshark what's sent over the network - I can see a packet going (in clearemoticon) with my credentials to the AppServer. After that it hangs on reading.
Flag

Re: [Cuae-developers] FW: registering application
Answer
6/20/08 2:48 AM as a reply to ZAFAR SHAKEEL.
Vadim,

Can you please zip and send across your "\Program Files\Cisco
Systems\Unified Application Environment\AppServer" & "\Program
Files\Cisco Systems\Unified Application Environment\Logs\AppServer".
Hope you have set all the server logs to "verbose".

Along with the above, kindly send the wireshark capture at the server
side when your application is trying to register.

regards,
Ram

Cisco Developer Services
http://developer.cisco.com/

-----Original Message-----
From: cuae-developers-bounces@developer.cisco.com
mailto:cuae-developers-bounces@developer.cisco.com On Behalf Of Vadim
Bruk
Sent: Thursday, June 19, 2008 4:07 PM
To: cuae-developers@developer.cisco.com
Subject: Re: [Cuae-developers] FW: registering application

Seth,

I've rolled back to the original code - whatever has been generated by
etch compiler. Only changed to the correct uri and added
registerApplication call.
I've also traced with wireshark what's sent over the network - I can see
a packet going (in clearemoticon) with my credentials to the AppServer. After
that it hangs on reading.
_______________________________________________
Cuae-developers mailing list
Cuae-developers@developer.cisco.com

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

Re: [Cuae-developers] FW: registering application
Answer
6/20/08 3:47 AM as a reply to ZAFAR SHAKEEL.
Vadim,

Might be silly to ask, did you used cuae package and deployed the
generated mca file in the app server and then executing your client java
application ?

regards,
Ram

Cisco Developer Services
http://developer.cisco.com/

-----Original Message-----
From: Ramgopal Chockalingam -X (rchockal - Infosys at Cisco)
Sent: Thursday, June 19, 2008 4:49 PM
To: 'cuae-developers@developer.cisco.com'
Subject: RE: [Cuae-developers] FW: registering application

Vadim,

Can you please zip and send across your "\Program Files\Cisco
Systems\Unified Application Environment\AppServer" & "\Program
Files\Cisco Systems\Unified Application Environment\Logs\AppServer".
Hope you have set all the server logs to "verbose".

Along with the above, kindly send the wireshark capture at the server
side when your application is trying to register.

regards,
Ram

Cisco Developer Services
http://developer.cisco.com/

-----Original Message-----
From: cuae-developers-bounces@developer.cisco.com
mailto:cuae-developers-bounces@developer.cisco.com On Behalf Of Vadim
Bruk
Sent: Thursday, June 19, 2008 4:07 PM
To: cuae-developers@developer.cisco.com
Subject: Re: [Cuae-developers] FW: registering application

Seth,

I've rolled back to the original code - whatever has been generated by
etch compiler. Only changed to the correct uri and added
registerApplication call.
I've also traced with wireshark what's sent over the network - I can see
a packet going (in clearemoticon) with my credentials to the AppServer. After
that it hangs on reading.
_______________________________________________
Cuae-developers mailing list
Cuae-developers@developer.cisco.com

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

Re: [Cuae-developers] FW: registering application
Answer
6/20/08 4:14 AM as a reply to ZAFAR SHAKEEL.
Ram,

I definitely missed this step emoticon. It's working now.
Thank you for your help.

Vadim.
Flag

Re: [Cuae-developers] FW: registering application
Answer
6/20/08 4:27 AM as a reply to ZAFAR SHAKEEL.
Good to know it worked... we will handle this gracefully at the client
side emoticon

regards,
Ram

Cisco Developer Services
http://developer.cisco.com/

-----Original Message-----
From: cuae-developers-bounces@developer.cisco.com
mailto:cuae-developers-bounces@developer.cisco.com On Behalf Of Vadim
Bruk
Sent: Thursday, June 19, 2008 6:14 PM
To: cuae-developers@developer.cisco.com
Subject: Re: [Cuae-developers] FW: registering application

Ram,

I definitely missed this step emoticon. It's working now.
Thank you for your help.

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

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

Re: [Cuae-developers] FW: registering application
Answer
6/20/08 4:36 AM as a reply to ZAFAR SHAKEEL.
Ram,

One more question. I'm pretty new to CUAE development (as you may have noticed). What would be the proper steps in the code in order to start monitoring a phone through jtapi provider. In other words, I'd like to receive JTAPICallInitiated event, then what absolutely necessary that I'll have to have in my code from CUAE perspective?

Thank you,
Vadim.
Flag

Re: [Cuae-developers] FW: registering application
Answer
6/20/08 4:47 AM as a reply to ZAFAR SHAKEEL.
Vadim,

I would assume you haven't worked on previous CUAE designer development
as well...

As of now we have all the actions available as part of CUAE's JTAPI
provider over here
http://cuaesdk.sourceforge.net/api-2-4-3/Metreos.Providers.JTapi.html
and good news is; we are working on providing more samples as part of
wiki in developer.cisco.com CUAE tech center. However that's on the way.

To answer your question:

Basically, it depends on what one wanted to do; after
JTAPICallInitiated event is received via CUAE in your application; it's
up to the app developers need. I hope the above API guide would provide
you some pointers.

In general, you would answer or put on hold or redirect or
reject etc...

regards,
Ram

Cisco Developer Services
http://developer.cisco.com/

-----Original Message-----
From: cuae-developers-bounces@developer.cisco.com
mailto:cuae-developers-bounces@developer.cisco.com On Behalf Of Vadim
Bruk
Sent: Thursday, June 19, 2008 6:36 PM
To: cuae-developers@developer.cisco.com
Subject: Re: [Cuae-developers] FW: registering application

Ram,

One more question. I'm pretty new to CUAE development (as you may have
noticed). What would be the proper steps in the code in order to start
monitoring a phone through jtapi provider. In other words, I'd like to
receive JTAPICallInitiated event, then what absolutely necessary that
I'll have to have in my code from CUAE perspective?

Thank you,
Vadim.
_______________________________________________
Cuae-developers mailing list
Cuae-developers@developer.cisco.com

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

Re: [Cuae-developers] FW: registering application
Answer
6/20/08 4:54 AM as a reply to ZAFAR SHAKEEL.
You would need to create an Application user in CUCM with CTI Enabled
group.

Add your device as this user's controlled device.

Create Monitored CTI Device Pool as shown below. Add your device to
monitored device pool. And it would come up as running enabled if things
are set correctly as shown in second picture.

Once this is done, you would write your application to trigger off
JTAPICallInitiated. You would have to add cisco.uc.cuae.legacy.JTapi to
your mixin file.

This will enable you to include jtapiCallInitiated(...) event handler in
your Impl file. Which will service the incoming event.

  • Zafar


-----Original Message-----
From: cuae-developers-bounces@developer.cisco.com
mailto:cuae-developers-bounces@developer.cisco.com On Behalf Of Vadim
Bruk
Sent: Thursday, June 19, 2008 6:36 PM
To: cuae-developers@developer.cisco.com
Subject: Re: [Cuae-developers] FW: registering application

Ram,

One more question. I'm pretty new to CUAE development (as you may have
noticed). What would be the proper steps in the code in order to start
monitoring a phone through jtapi provider. In other words, I'd like to
receive JTAPICallInitiated event, then what absolutely necessary that
I'll have to have in my code from CUAE perspective?

Thank you,

Vadim.

_______________________________________________

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"
Attachment not added (content type not allowed): "image001.png"
Attachment not added (content type not allowed): "image002.png"
Flag

Re: [Cuae-developers] FW: registering application
Answer
6/20/08 5:01 AM as a reply to ZAFAR SHAKEEL.
Ram,

I mean do I have to subscribe for events to receive them? How do I specify terminals that I'm interested in?
I assume that I'll have to override jTapiCallInitiated method. What else should I do so the method gets called?

Thank you,
Vadim.
Flag

Re: [Cuae-developers] FW: registering application
Answer
6/20/08 6:31 PM as a reply to ZAFAR SHAKEEL.
Hi Vadim,

You have to ways--either by dynamically registered the device (as
described by this API reference page)
http://cuaesdk.sourceforge.net/api-2-4-3/Metreos.Providers.JTapi.JTapiNo
nTriggeringSubscribe.html

Or by going to mceadmin and statically defining which devices should be
registered.

Seth

-----Original Message-----
From: cuae-developers-bounces@developer.cisco.com
mailto:cuae-developers-bounces@developer.cisco.com On Behalf Of Vadim
Bruk
Sent: Thursday, June 19, 2008 7:02 PM
To: cuae-developers@developer.cisco.com
Subject: Re: [Cuae-developers] FW: registering application

Ram,

I mean do I have to subscribe for events to receive them? How do I
specify terminals that I'm interested in?
I assume that I'll have to override jTapiCallInitiated method. What else
should I do so the method gets called?

Thank you,
Vadim.
_______________________________________________
Cuae-developers mailing list
Cuae-developers@developer.cisco.com

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

Re: [Cuae-developers] FW: registering application
Answer
6/20/08 6:31 PM as a reply to ZAFAR SHAKEEL.
Hey Vadim,

Regarding clear text passwords--TLS will be supported by Etch soon, and
will also be the default way (maybe only way ) one connects to the CUAE
Etch bridge.

Seth
Flag

Re: [Cuae-developers] FW: registering application
Answer
6/23/08 8:01 PM as a reply to ZAFAR SHAKEEL.
Hi Zafaar,

I did exactly all this - and stll have a problem with jtapiNonTriggeringSubscribe method call. Here is what's in the AppServer log file:

2008:06:20::12:03:25(32): Warning: CI This server is not configured with a hot-standby
2008:06:20::12:03:29(35): Info: HP Connected to H.323 service successfully
2008:06:20::12:03:30(54): Info: JTP Setting log level for JTAPI service v3.3 to level: 3
2008:06:20::12:03:30(57): Info: JTP Setting log level for JTAPI service v4.0 to level: 3
2008:06:20::12:03:30(59): Info: JTP Setting log level for JTAPI service v4.1 to level: 3
2008:06:20::12:03:30(60): Info: JTP Setting log level for JTAPI service v4.2 to level: 3
2008:06:20::12:03:30(62): Info: JTP Setting log level for JTAPI service v5.0 to level: 3
2008:06:20::12:03:30(64): Info: JTP Setting log level for JTAPI service v5.1 to level: 3
2008:06:20::12:03:30(65): Info: JTP Setting log level for JTAPI service v6.0 to level: 3
2008:06:20::12:03:30(67): Info: JTP Setting log level for JTAPI service v6.1 to level: 3
2008:06:20::12:03:30(71): Verbose: Config Device Pool Data id = '1', version= '6.0', name= 'CCM6', ip= '10.2.0.16', ctiAddr= '10.2.0.16'
2008:06:20::12:03:30(85): Warning: JTP Failed to send register for device SEP0009B7DA0BCB
2008:06:20::12:03:31(10): Info: JTP Connected to JTAPI service v4.0 successfully
2008:06:20::12:03:31(12): Info: JTP No CTI devices configured for v4.0.
2008:06:20::12:03:31(14): Info: JTP Connected to JTAPI service v3.3 successfully
2008:06:20::12:03:31(14): Info: JTP No CTI devices configured for v3.3.
2008:06:20::12:03:31(14): Info: JTP Connected to JTAPI service v4.1 successfully
2008:06:20::12:03:31(14): Info: JTP No CTI devices configured for v4.1.
2008:06:20::12:03:31(15): Info: JTP Connected to JTAPI service v4.2 successfully
2008:06:20::12:03:31(15): Info: JTP No CTI devices configured for v4.2.
2008:06:20::12:03:31(17): Info: JTP Connected to JTAPI service v5.0 successfully
2008:06:20::12:03:31(17): Info: JTP No CTI devices configured for v5.0.
2008:06:20::12:03:31(18): Info: JTP Connected to JTAPI service v5.1 successfully
2008:06:20::12:03:31(18): Info: JTP No CTI devices configured for v5.1.
2008:06:20::12:03:31(18): Info: JTP Connected to JTAPI service v6.0 successfully
2008:06:20::12:03:31(18): Info: JTP Registering device 'SEP0009B7DA0BCB' with the JTAPI service v6.0
2008:06:20::12:03:31(21): Info: JTP Setting log level for JTAPI service v3.3 to level: 3
2008:06:20::12:03:31(23): Info: JTP Setting log level for JTAPI service v4.0 to level: 3
2008:06:20::12:03:31(25): Info: JTP Setting log level for JTAPI service v4.1 to level: 3
2008:06:20::12:03:31(26): Info: JTP Setting log level for JTAPI service v4.2 to level: 3
2008:06:20::12:03:31(29): Info: JTP Setting log level for JTAPI service v5.0 to level: 3
2008:06:20::12:03:31(31): Info: JTP Connected to JTAPI service v6.1 successfully
2008:06:20::12:03:31(31): Info: JTP No CTI devices configured for v6.1.
2008:06:20::12:03:31(31): Info: JTP Setting log level for JTAPI service v5.1 to level: 3
2008:06:20::12:03:31(32): Info: JTP Setting log level for JTAPI service v6.0 to level: 3
2008:06:20::12:03:31(34): Info: JTP Setting log level for JTAPI service v6.1 to level: 3
2008:06:20::12:03:36(57): Info: JTP Device 'SEP0009B7DA0BCB' registered successfully.
2008:06:20::12:03:48(89): Info: SIP Connected to Sip service successfully
2008:06:20::12:03:49(10): Warning: SIP No SIP devices configured. SIP services are unavailable.
2008:06:20::12:03:52(42): Info: MEP Clearing MRG cache
2008:06:20::12:03:54(68): Info: CDL Adding '10.2.0.16 v6' to DeviceListX cache list
2008:06:20::12:03:55(75): Info: CDL Device list cache refresh starting.
2008:06:20::12:03:59(59): Info: PP Connected to Presence service successfully
2008:06:20::12:04:00(03): Info: PP Presence service started, re-subscribe for notifications.
2008:06:20::12:04:01(64): Verbose: AM Application: jtapitest has correct directory structure
2008:06:20::12:04:06(04): Info: ARE Script 'script1' compiled successfully
2008:06:20::12:04:06(07): Verbose: ARE Registering script:
InternalMessage:
Type: CommandMessage
Message ID: RegisterScript
Routing GUID: unspecified
Source: Repository
SourceType: Core
SourceQueue: unspecified
Destination: Router
Fields:
ScriptName: script1
ApplicationQueueWriter: Metreos.Messaging.MessageQueueWriter
ApplicationName: jtapitest
Enabled: False
EventName: Metreos.Providers.JTapi.JTapiCallInitiated
PartitionName: Default
2008:06:20::12:04:06(31): Verbose: jtapitest New thread pool 'ARE Thread Pool' starting:
Initial thread count: 5
Max thread count: 10
New thread trigger: 400 ms
Dynamic thread decay time: 300000 ms
Request queue limit: -1 entries
2008:06:20::12:04:06(31): Verbose: jtapitest [111, ARE Thread Pool (static)] Worker thread started
2008:06:20::12:04:06(31): Verbose: jtapitest [112, ARE Thread Pool (static)] Worker thread started
2008:06:20::12:04:06(32): Verbose: jtapitest [113, ARE Thread Pool (static)] Worker thread started
2008:06:20::12:04:06(32): Verbose: jtapitest [114, ARE Thread Pool (static)] Worker thread started
2008:06:20::12:04:06(32): Verbose: jtapitest [115, ARE Thread Pool (static)] Worker thread started
2008:06:20::12:04:06(32): Info: jtapitest No constructor found
2008:06:20::12:04:06(34): Info: AM Application jtapitest loaded successfully.
2008:06:20::12:04:06(37): Info: DS Debug server started
2008:06:20::12:04:08(46): Info: CDL Device list cache refresh complete.
2008:06:20::14:03:54(70): Info: CDL Device list cache refresh starting.
2008:06:20::14:04:03(65): Info: CDL Device list cache refresh complete.
2008:06:20::15:06:04(15): Info: JTP Added JTapi call 1000001<->8S6qwlVG4F6XhYZH
2008:06:20::15:06:04(15): Info: JTP Sending third-party CallInitiated for: 1000001
2008:06:20::15:06:04(20): Warning: EPM Unable to trigger Etch application - jtapitest is not registered.
2008:06:20::15:06:04(21): Info: JTP Metreos.Providers.JTapi.JTapiCallInitiated event was not handled
2008:06:20::15:06:04(65): Info: JTP Sending third-party Hangup for '1000001' (cause=NORMAL)
2008:06:20::15:06:04(65): Warning: EPM Unable to trigger Etch application - jtapitest is not registered.
2008:06:20::15:06:04(67): Info: JTP Metreos.Providers.JTapi.JTapiHangup event was not handled
2008:06:20::15:06:05(00): Info: JTP Added JTapi call 1000002<->CzkTdnBjZfbRq2Bl
2008:06:20::15:06:05(00): Info: JTP Sending third-party CallInitiated for: 1000002
2008:06:20::15:06:05(01): Warning: EPM Unable to trigger Etch application - jtapitest is not registered.
2008:06:20::15:06:05(03): Info: JTP Metreos.Providers.JTapi.JTapiCallInitiated event was not handled
2008:06:20::15:06:05(39): Info: JTP Sending third-party Hangup for '1000002' (cause=NORMAL)
2008:06:20::15:06:05(39): Warning: EPM Unable to trigger Etch application - jtapitest is not registered.
2008:06:20::15:06:05(39): Info: JTP Metreos.Providers.JTapi.JTapiHangup event was not handled
2008:06:20::15:32:28(10): Info: JTP Added JTapi call 1000003<->QvzxmDSNgCsTyhsW
2008:06:20::15:32:28(10): Info: JTP Sending third-party CallInitiated for: 1000003
2008:06:20::15:32:28(10): Warning: EPM Unable to trigger Etch application - jtapitest is not registered.
2008:06:20::15:32:28(10): Info: JTP Metreos.Providers.JTapi.JTapiCallInitiated event was not handled
2008:06:20::15:32:28(81): Info: JTP Sending third-party GotDigits for '1000003': 1
2008:06:20::15:32:28(81): Warning: EPM Unable to trigger Etch application - jtapitest is not registered.
2008:06:20::15:32:28(81): Info: JTP Metreos.Providers.JTapi.JTapiGotDigits event was not handled
2008:06:20::15:32:29(35): Info: JTP Sending third-party GotDigits for '1000003': 0
2008:06:20::15:32:29(37): Warning: EPM Unable to trigger Etch application - jtapitest is not registered.
2008:06:20::15:32:29(37): Info: JTP Metreos.Providers.JTapi.JTapiGotDigits event was not handled
2008:06:20::15:32:29(68): Info: JTP Sending third-party GotDigits for '1000003': 2
2008:06:20::15:32:29(68): Warning: EPM Unable to trigger Etch application - jtapitest is not registered.
2008:06:20::15:32:29(68): Info: JTP Metreos.Providers.JTapi.JTapiGotDigits event was not handled
2008:06:20::15:32:30(01): Info: JTP Sending third-party GotDigits for '1000003': 7
2008:06:20::15:32:30(03): Warning: EPM Unable to trigger Etch application - jtapitest is not registered.
2008:06:20::15:32:30(03): Info: JTP Metreos.Providers.JTapi.JTapiGotDigits event was not handled
2008:06:20::15:32:30(06): Info: JTP Sending third-party Hangup for '1000003' (cause=DEST_NOT_OBTAINABLE)
2008:06:20::15:32:30(06): Warning: EPM Unable to trigger Etch application - jtapitest is not registered.
2008:06:20::15:32:30(06): Info: JTP Metreos.Providers.JTapi.JTapiHangup event was not handled
2008:06:20::15:32:35(26): Info: JTP Added JTapi call 1000004<->38jgcdZxqnF5WqXg
2008:06:20::15:32:35(26): Info: JTP Sending third-party CallInitiated for: 1000004
2008:06:20::15:32:35(26): Warning: EPM Unable to trigger Etch application - jtapitest is not registered.
2008:06:20::15:32:35(26): Info: JTP Metreos.Providers.JTapi.JTapiCallInitiated event was not handled
2008:06:20::15:32:35(73): Info: JTP Sending third-party GotDigits for '1000004': 1
2008:06:20::15:32:35(75): Warning: EPM Unable to trigger Etch application - jtapitest is not registered.
2008:06:20::15:32:35(75): Info: JTP Metreos.Providers.JTapi.JTapiGotDigits event was not handled
2008:06:20::15:32:35(84): Info: JTP Sending third-party GotDigits for '1000004': 0
2008:06:20::15:32:35(84): Warning: EPM Unable to trigger Etch application - jtapitest is not registered.
2008:06:20::15:32:35(84): Info: JTP Metreos.Providers.JTapi.JTapiGotDigits event was not handled
2008:06:20::15:32:35(93): Info: JTP Sending third-party GotDigits for '1000004': 3
2008:06:20::15:32:35(93): Warning: EPM Unable to trigger Etch application - jtapitest is not registered.
2008:06:20::15:32:35(95): Info: JTP Metreos.Providers.JTapi.JTapiGotDigits event was not handled
2008:06:20::15:32:36(04): Info: JTP Sending third-party GotDigits for '1000004': 7
2008:06:20::15:32:36(04): Warning: EPM Unable to trigger Etch application - jtapitest is not registered.
2008:06:20::15:32:36(04): Info: JTP Metreos.Providers.JTapi.JTapiGotDigits event was not handled
2008:06:20::15:32:36(06): Info: JTP Sending third-party Hangup for '1000004' (cause=DEST_NOT_OBTAINABLE)
2008:06:20::15:32:36(06): Warning: EPM Unable to trigger Etch application - jtapitest is not registered.
2008:06:20::15:32:36(06): Info: JTP Metreos.Providers.JTapi.JTapiHangup event was not handled
2008:06:20::15:32:40(03): Info: JTP Added JTapi call 1000005<->nRyHcKRvbCDbwsd2
2008:06:20::15:32:40(03): Info: JTP Sending third-party CallInitiated for: 1000005
2008:06:20::15:32:40(03): Warning: EPM Unable to trigger Etch application - jtapitest is not registered.
2008:06:20::15:32:40(03): Info: JTP Metreos.Providers.JTapi.JTapiCallInitiated event was not handled
2008:06:20::15:32:40(51): Info: JTP Sending third-party GotDigits for '1000005': 1
2008:06:20::15:32:40(51): Warning: EPM Unable to trigger Etch application - jtapitest is not registered.
2008:06:20::15:32:40(51): Info: JTP Metreos.Providers.JTapi.JTapiGotDigits event was not handled
2008:06:20::15:32:40(60): Info: JTP Sending third-party GotDigits for '1000005': 0
2008:06:20::15:32:40(60): Warning: EPM Unable to trigger Etch application - jtapitest is not registered.
2008:06:20::15:32:40(62): Info: JTP Metreos.Providers.JTapi.JTapiGotDigits event was not handled
2008:06:20::15:32:40(71): Info: JTP Sending third-party GotDigits for '1000005': 3
2008:06:20::15:32:40(71): Warning: EPM Unable to trigger Etch application - jtapitest is not registered.
2008:06:20::15:32:40(71): Info: JTP Metreos.Providers.JTapi.JTapiGotDigits event was not handled
2008:06:20::15:32:40(81): Info: JTP Sending third-party GotDigits for '1000005': 3
2008:06:20::15:32:40(81): Warning: EPM Unable to trigger Etch application - jtapitest is not registered.
2008:06:20::15:32:40(81): Info: JTP Metreos.Providers.JTapi.JTapiGotDigits event was not handled
2008:06:20::15:32:40(82): Info: JTP Sending third-party Hangup for '1000005' (cause=DEST_NOT_OBTAINABLE)
2008:06:20::15:32:40(82): Warning: EPM Unable to trigger Etch application - jtapitest is not registered.
2008:06:20::15:32:40(82): Info: JTP Metreos.Providers.JTapi.JTapiHangup event was not handled
2008:06:20::15:32:45(82): Info: JTP Added JTapi call 1000006<->TVqldfjfjfn7YCcG
2008:06:20::15:32:45(82): Info: JTP Sending third-party CallInitiated for: 1000006
2008:06:20::15:32:45(82): Warning: EPM Unable to trigger Etch application - jtapitest is not registered.
2008:06:20::15:32:45(82): Info: JTP Metreos.Providers.JTapi.JTapiCallInitiated event was not handled
2008:06:20::15:32:46(32): Info: JTP Sending third-party GotDigits for '1000006': 1
2008:06:20::15:32:46(32): Warning: EPM Unable to trigger Etch application - jtapitest is not registered.
2008:06:20::15:32:46(32): Info: JTP Metreos.Providers.JTapi.JTapiGotDigits event was not handled
2008:06:20::15:32:46(40): Info: JTP Sending third-party GotDigits for '1000006': 0
2008:06:20::15:32:46(40): Warning: EPM Unable to trigger Etch application - jtapitest is not registered.
2008:06:20::15:32:46(40): Info: JTP Metreos.Providers.JTapi.JTapiGotDigits event was not handled
2008:06:20::15:32:46(50): Info: JTP Sending third-party GotDigits for '1000006': 3
2008:06:20::15:32:46(50): Warning: EPM Unable to trigger Etch application - jtapitest is not registered.
2008:06:20::15:32:46(50): Info: JTP Metreos.Providers.JTapi.JTapiGotDigits event was not handled
2008:06:20::15:32:46(60): Info: JTP Sending third-party GotDigits for '1000006': 2
2008:06:20::15:32:46(60): Warning: EPM Unable to trigger Etch application - jtapitest is not registered.
2008:06:20::15:32:46(60): Info: JTP Metreos.Providers.JTapi.JTapiGotDigits event was not handled
2008:06:20::15:32:46(70): Info: JTP Sending third-party CallInitiated for: 1000006
2008:06:20::15:32:46(70): Error: LM License check FAIL: licensed: 6, running: 6. Running script instances has exceeded license. License overage period exceeded. Licensing limits are being strictly enforced.
2008:06:20::15:32:46(70): Info: JTP Metreos.Providers.JTapi.JTapiCallEstablished event was not handled
2008:06:20::15:32:46(76): Info: JTP Sending CallActive for call: 1000006
2008:06:20::15:32:46(76): Warning: EPM Unable to trigger Etch application - jtapitest is not registered.
2008:06:20::15:32:46(76): Info: JTP Metreos.Providers.JTapi.JTapiCallActive event was not handled
2008:06:20::15:32:49(12): Info: JTP Sending third-party Hangup for '1000006' (cause=NORMAL)
2008:06:20::15:32:49(15): Warning: EPM Unable to trigger Etch application - jtapitest is not registered.
2008:06:20::15:32:49(15): Info: JTP Metreos.Providers.JTapi.JTapiHangup event was not handled
2008:06:20::15:34:36(64): Info: JTP Added JTapi call 1000007<->P9fVklwVnQGTBqLJ
2008:06:20::15:34:36(65): Info: JTP Sending third-party CallInitiated for: 1000007
2008:06:20::15:34:36(65): Error: LM License check FAIL: licensed: 6, running: 6. Running script instances has exceeded license. License overage period exceeded. Licensing limits are being strictly enforced.
2008:06:20::15:34:36(65): Info: JTP Metreos.Providers.JTapi.JTapiCallInitiated event was not handled
2008:06:20::15:34:37(14): Info: JTP Sending third-party GotDigits for '1000007': 1
2008:06:20::15:34:37(14): Warning: EPM Etch application jtapiTest is not enabled, ignore event cisco.uc.cuae.legacy.JTapi.JTapiGotDigits.
2008:06:20::15:34:37(14): Info: JTP Metreos.Providers.JTapi.JTapiGotDigits event was not handled
2008:06:20::15:34:37(21): Info: JTP Sending third-party GotDigits for '1000007': 0
2008:06:20::15:34:37(23): Warning: EPM Etch application jtapiTest is not enabled, ignore event cisco.uc.cuae.legacy.JTapi.JTapiGotDigits.
2008:06:20::15:34:37(23): Info: JTP Metreos.Providers.JTapi.JTapiGotDigits event was not handled
2008:06:20::15:34:37(32): Info: JTP Sending third-party GotDigits for '1000007': 3
2008:06:20::15:34:37(32): Warning: EPM Etch application jtapiTest is not enabled, ignore event cisco.uc.cuae.legacy.JTapi.JTapiGotDigits.
2008:06:20::15:34:37(32): Info: JTP Metreos.Providers.JTapi.JTapiGotDigits event was not handled
2008:06:20::15:34:37(42): Info: JTP Sending third-party GotDigits for '1000007': 2
2008:06:20::15:34:37(42): Warning: EPM Etch application jtapiTest is not enabled, ignore event cisco.uc.cuae.legacy.JTapi.JTapiGotDigits.
2008:06:20::15:34:37(43): Info: JTP Metreos.Providers.JTapi.JTapiGotDigits event was not handled
2008:06:20::15:34:37(43): Info: JTP Sending third-party CallInitiated for: 1000007
2008:06:20::15:34:37(45): Error: LM License check FAIL: licensed: 6, running: 6. Running script instances has exceeded license. License overage period exceeded. Licensing limits are being strictly enforced.
2008:06:20::15:34:37(45): Info: JTP Metreos.Providers.JTapi.JTapiCallEstablished event was not handled
2008:06:20::15:34:37(50): Info: JTP Sending CallActive for call: 1000007
2008:06:20::15:34:37(50): Warning: EPM Etch application jtapiTest is not enabled, ignore event cisco.uc.cuae.legacy.JTapi.JTapiCallActive.
2008:06:20::15:34:37(51): Info: JTP Metreos.Providers.JTapi.JTapiCallActive event was not handled
2008:06:20::15:34:51(60): Info: JTP Sending third-party Hangup for '1000007' (cause=NORMAL)
2008:06:20::15:34:51(60): Warning: EPM Etch application jtapiTest is not enabled, ignore event cisco.uc.cuae.legacy.JTapi.JTapiHangup6.
2008:06:20::15:34:51(60): Info: JTP Metreos.Providers.JTapi.JTapiHangup event was not handled
Flag