Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

JTAPI weirdness

Here's the scenario: All my phones are registered on my subscriber CCM, except the IP Communicator on my notebook. I'm currently connected to work via VPN and for some weird reason I have no connectivity at all to my subscriber. Suddenly, my JTAPI app only gets half the events it should so I start investigating. Via JTrace, I find out the following: regardless of me putting both call managers or only the publisher in the jtapi connection string, all phones that are subscribed with the subscriber only report out of service. On top of that, if I make a call to such a device from my IPC, it succeeds, but some events don't make it back. Now here's where it gets really weird: If I only register a call observer for the addresses on my IPC, then I get all the events for my lines. If I also register a call observer for a line that only reports out of service, I get less events.

Here's a JTrace trace: 3410 is a DN on my IP Communicator. 3407 is a DN on a phone registered with the subscriber (subscriber is not reachable via IP over VPN). If I make JTrace just watch 3410 and I make a call from 3410 to 3407, I get the following events:

NEW META EVENT_________META_CALL_STARTING

Received (P1-sdkuser) 32/1 CallActiveEv [#12] for callID=101 Cause: CAUSE_NEW_CALL

Received (P1-sdkuser) 32/1 ConnCreatedEv 3410 [#13] for 3410 16777287/1 Cause: CAUSE_NORMAL

Received (P1-sdkuser) 32/1 ConnConnectedEv 3410 [#14] for 3410 16777287/1 Cause: CAUSE_NORMAL

Received (P1-sdkuser) 32/1 CallCtlConnInitiatedEv 3410 [#15] for 3410 16777287/1 Cause: CAUSE_NORMAL CallControlCause: CAUSE_NORMAL

Received (P1-sdkuser) 32/1 TermConnCreatedEv SEP54554344520A [#16] for SEP54554344520A Cause: Other: 0

Received (P1-sdkuser) 32/1 TermConnActiveEv SEP54554344520A [#17] for SEP54554344520A Cause: CAUSE_NORMAL

Received (P1-sdkuser) 32/1 CallCtlTermConnTalkingEv SEP54554344520A [#18] for SEP54554344520A Cause: CAUSE_NORMAL CallControlCause: CAUSE_NORMAL

NEW META EVENT_________META_CALL_PROGRESS

Received (P1-sdkuser) 32/1 CallCtlConnDialingEv 3410 [#19] for 3410 16777287/1 Cause: CAUSE_NORMAL CallControlCause: CAUSE_NORMAL

NEW META EVENT_________META_CALL_PROGRESS

Received (P1-sdkuser) 32/1 CallCtlConnEstablishedEv 3410 [#20] for 3410 16777287/1 Cause: CAUSE_NORMAL CallControlCause: CAUSE_NORMAL

Received (P1-sdkuser) 32/1 ConnCreatedEv 3407 [#21] for 3407 0/0 Cause: CAUSE_NORMAL

NEW META EVENT_________META_CALL_PROGRESS

Received (P1-sdkuser) 32/1 ConnInProgressEv 3407 [#22] for 3407 0/0 Cause: CAUSE_NORMAL

Received (P1-sdkuser) 32/1 CallCtlConnOfferedEv 3407 [#23] for 3407 0/0 Cause: CAUSE_NORMAL CallControlCause: CAUSE_NORMAL

NEW META EVENT_________META_CALL_PROGRESS

Received (P1-sdkuser) 32/1 ConnAlertingEv 3407 [#24] for 3407 0/0 Cause: CAUSE_NORMAL

Received (P1-sdkuser) 32/1 CallCtlConnAlertingEv 3407 [#25] for 3407 0/0 Cause: CAUSE_NORMAL CallControlCause: CAUSE_NORMAL

If however, I make JTrace listen to both 3410 and 3407, here's what I get in the window of 3410:

1 REPLY

Re: JTAPI weirdness

NEW META EVENT_________META_CALL_STARTING

Received (P1-sdkuser) 33/1 CallActiveEv [#9] for callID=101 Cause: CAUSE_NEW_CALL

Received (P1-sdkuser) 33/1 ConnCreatedEv 3410 [#10] for 3410 16777289/1 Cause: CAUSE_NORMAL

Received (P1-sdkuser) 33/1 ConnConnectedEv 3410 [#11] for 3410 16777289/1 Cause: CAUSE_NORMAL

Received (P1-sdkuser) 33/1 CallCtlConnInitiatedEv 3410 [#12] for 3410 16777289/1 Cause: CAUSE_NORMAL CallControlCause: CAUSE_NORMAL

Received (P1-sdkuser) 33/1 TermConnCreatedEv SEP54554344520A [#13] for SEP54554344520A Cause: Other: 0

Received (P1-sdkuser) 33/1 TermConnActiveEv SEP54554344520A [#14] for SEP54554344520A Cause: CAUSE_NORMAL

Received (P1-sdkuser) 33/1 CallCtlTermConnTalkingEv SEP54554344520A [#15] for SEP54554344520A Cause: CAUSE_NORMAL CallControlCause: CAUSE_NORMAL

NEW META EVENT_________META_CALL_PROGRESS

Received (P1-sdkuser) 33/1 CallCtlConnDialingEv 3410 [#16] for 3410 16777289/1 Cause: CAUSE_NORMAL CallControlCause: CAUSE_NORMAL

NEW META EVENT_________META_CALL_PROGRESS

Received (P1-sdkuser) 33/1 CallCtlConnEstablishedEv 3410 [#17] for 3410 16777289/1 Cause: CAUSE_NORMAL CallControlCause: CAUSE_NORMAL

As you can see, we have some crucial events missing (they are crucial to my application at least). The 3407 window stays empty (discarding the out of service events for terminal and address). Does anybody have any idea why things act the way they do? Why would monitoring an additional terminal actually result in less information getting back to jtapi?

82
Views
0
Helpful
1
Replies