« Back to Cisco JTAPI Questions

CUCM 7.0 - CTI verification fails

Combination View Flat View Tree View
Threads [ Previous | Next ]
CUCM 7.0 - CTI verification fails
Answer
10/29/08 1:33 AM
This is an upgraded CUCM - from 6.0 to 7.0

Trying to verify the CTI connection by checking the Provider and I see this Exception:

using Cisco JTAPI version=6.0(0.9901)-139
com.cisco.jtapi.PlatformExceptionImpl: Unable to create provider -- directory login timeout

I looked online and one of the document which talks about the exceptions, doesn't mention the "directory login timeout".

Any suggestions ?

Arvind
Flag

Re: CUCM 7.0 - CTI verification fails
Answer
10/29/08 8:36 PM as a reply to Arvind Sharma.
Are you sure you're using the jtapi.jar for CallManager 7? The version nuber reported sounds very much like CCM6 - you absolutely need to use the new jtapi.jar for every major release (minor releases might be okay without adapting the jtapi.jar though it is not recommended either).
Flag

Re: CUCM 7.0 - CTI verification fails
Answer
10/29/08 10:27 PM as a reply to Arvind Sharma.
well... I thought the same thing first... but then I have another machine CUCM 7.0 - there the same test works, using the JTAPI-6.0.jar

Any clues to what does that error means ? Is it something in the CTI manager setup or JTAPI related ?

Arvind
Flag

Re: CUCM 7.0 - CTI verification fails
Answer
10/29/08 10:54 PM as a reply to Arvind Sharma.
Hi Arvind,
Actually the reply I posted on your other thread was meant for this one. Sorry for that. The exception that you have mentioned can be thrown when:
1. The user with which we are doing provider open is not associated with user group "Standard CTI Enabled" or
2. If #1 is not the case, then it could be a timeout during the user authentication from directory side. To ensure there is no issue with user credentials can you please try updating the user id/password and try a re-login? Also just check if user credential policy doesnt force you to change your password on next login.

Once, we are sure the config is correct, we can look into the logs to see what is causing this issue.

Thanks,
Abhishek
Flag

Re: CUCM 7.0 - CTI verification fails
Answer
10/30/08 9:07 PM as a reply to Arvind Sharma.
The user is associated with "Standard CTI Enabled".

I also changed the password and still gets the same Exception.


One thing I did notice that all this time my CTI manager was pointing to "Publisher". I switched that to "Subscriber" - and now I can verify the CTI !


Not sure if I can keep this setup as a solution since few of our lab setup don't have Subscriber.


Is that something you would expect CTI to behave if there is no Subscriber ?


Thanks!

Arvind
Flag

Re: CUCM 7.0 - CTI verification fails
Answer
10/30/08 9:58 PM as a reply to Arvind Sharma.
JTAPI is supposed to automatically fail over if you add both publisher and subscriber to the connection string.. so it is definitely not supposed to happen. Have you tried rebooting the pub just for good measure?

Also, even if it works, I'd still suggest you use the CCM 7 JTAPI when working with CCM7.
Flag

Re: CUCM 7.0 - CTI verification fails
Answer
10/31/08 12:45 AM as a reply to Arvind Sharma.
If the problem is not resolved by rebooting then I would be interested in knowing if both Publisher and Subscriber are running the same version. Its recommended that all Publishers and Subscriber should be running the same version. If they are running the same version, then we would need JTAPI/CTI/CallManager logs to investigate and see whats going wrong.

Regarding using of older JTAPI version with newer CUCM - JTAPI supports BWC so that shouldnt be an issue but still are there any specific reasons to not use 7.x JTAPI to connect to your 7.x CUCM?

Regards,
Abhishek Malhotra

P.S. Even though you can use old JTAPI client to connect to new CUCM(Supports BWC) but you cannot use newer JTAPI client to connect to older CUCM(No Support FWC)
Flag

Re: CUCM 7.0 - CTI verification fails
Answer
10/31/08 5:02 PM as a reply to Arvind Sharma.
There are some good reasons to use the most up-to-date version matching your CCM though: bug fixes. For instance.. the 6.1.1 TSP contains some nasty bugs that will make your life miserable - they've only been fixed in the 6.1.2 TSP..
Flag

Re: CUCM 7.0 - CTI verification fails
Answer
10/31/08 8:55 PM as a reply to Arvind Sharma.
The Sub and Pub both were rebooted and both are on exactly same version.

Even then I see the same results.

As I mentioned in the earlier posting - if I point to the CTI manager on the sub I do get successful verification. That is really wierd.

We have tried the same trick with some of our customers and that seems to work there as well.

I will move to the latest JTAPI jar in the upcoming new release for sure.

Thanks!
Arvind
Flag

Re: CUCM 7.0 - CTI verification fails
Answer
11/1/08 4:32 AM as a reply to Arvind Sharma.
Hi Arvind,

For this issue also, can you please provide us JTAPI and CTI/CCM Traces. If you are facing issues in collecting JTAPI logs then just share the CTI and CCM traces for this (detailed level traces - both SDL and SDI)

Regards,
Abhishek Malhotra
Flag

Re: CUCM 7.0 - CTI verification fails
Answer
11/5/08 5:07 AM as a reply to Arvind Sharma.
Since moving to Sub (CTI Manager pointing to Sub), this is working fine.

Arvind

Edited by: Arvind Sharma on Nov 4, 2008 6:08 PM
Flag