« Back to Cisco JTAPI Questions

Unreliable jtapi responses to commands

Combination View Flat View Tree View
Threads [ Previous | Next ]
Hi,
We've used JTAPI and experimented with a variety of callmanager versions and provider initiation models. Ultimately, we still find that the messages which come back are inconsistent--sometimes we get them, sometimes we do not.

Our approach has been to infer a line state based upon these messages (e.g. tell phone to go off hook, wait until jtapi message, via monitor, shows phone is off hook, etc). With the unreliable responses, that has been difficult.

1) Has anyone had similar experiences? If so, have you found alternatives?
2) Has anyone tried using AXL-Perfmon for line status to get it in response to JTAPI commands?

Thanks

Hi Robert,

Can you please tell us what are the messages that are coming inconsitently? I dont think JTAPI has any such known issue.

For Eg) If you have added a callObserver on a phone and if that phone goes offHook then you will see CallActiveEv and CallCtlConnInitiatedEv, I do think we get these events consistently today.

If you could explain exactly whats the issue and which event is missing then we can take a closer look in your issue. Also, please let us know the Call Manager and JTAPI version that are using.

For, your AXL query - I think you can write to AXL API forum or may be our developer support can point you to the same.

Thanks,
Abhishek M.
Cisco JTAPI Development Team.

AXL does not provide real-time line-state info, so that probably won't add anything.

As Abishek mentions, missing events are not a known issue and would be very surprising. Events which come in differing sequence are possible, and can be a bit of a challenge to handle. Some specific information may be helpful.