Hi Vadim:

There are two issues. First part of your issue "when I was creating the
pool I had to enter user/password", try creating an Application user
with CTI control of all devices enabled in CCM. Use this guy's
credentials to create the pool.

We will look at the hanging issue.

-Zafar

-----Original Message-----
From: cuae-developers-bounces@developer.cisco.com
mailto:cuae-developers-bounces@developer.cisco.com On Behalf Of Vadim
Bruk
Sent: Friday, June 20, 2008 1:15 PM
To: cuae-developers@developer.cisco.com
Subject: [Cuae-developers] device monitoring

Hi,

I'd like start receiving jtapi events for a particular terminal. I'm
calling jTapiNonTriggeringSubscribe method with the following
parameters: sessionId as a string returned from registerApplication
call; deviceName is a device name that I took in CCM (in my case it's
SEP0009B7DA0BC; pool is the name of the configured in mceadmin
monitored cti device pool (question - when I was creating the pool I had
to enter user/password - are these the same as those in
registerApplication?), deviceType is JTapi.DeviceType.CTIMONITORED, and
options are null. My simple test blocks forever in the subcribe request.

In the log files I can see that AppServer complains about device type.
Specificaly:
2008:06:20::11:01:36(71): Info: JTP Registering new device
'SEP0009B7DA0BCB' type: True under CCM6 with JTAPI service v6.0
2008:06:20::11:01:36(71): Error: JTP Call encountered an error
(InvalidDeviceType): <no description>
So what device type should I use? Also, is it an expected behaviour when
the call blocks (even if the arguments are incorrect)?
_______________________________________________
Cuae-developers mailing list
Cuae-developers@developer.cisco.com

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

I can suggest a workaround for the timeout issue:

If you open up CUAE_DEV_TOOLS_DIR\Framework\1.0\idl\cisco\uc\cuae\legacy\JTapi.etch, and add to it near the top of the file this:


It should go above the 'service' keyword, specifically, your file should look like this:


This will cause your client to wait up to 5 seconds for a response--if it doesn't receive one, then it will move on.

In the meantime, probably for Beta-2, we will look at getting these @Timeout attributes in the Etch files automatically. But be aware that if you upgrade to beta 1 next week, you 'll need to add back the @Timeout to this service.

By the way, we need to fix the root issue here--the server should be responding.

I'm still looking at the reasons you might be getting that error...

Seth

Hi Seth,

I've restarted the AppServer. Now I don't see any AppServer log updates when run my app. Also in mceadmin I can see on the service control page line: "The application server service is enabled but communication with it has failed." Also the AppServer's status is Running.
And the subscription method call still blocks.
Just in case here is 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.


Vadim.