[cisco-voip] Using Updater for the jtapi.jar in CCM 4.2

[Paul Yago]

Thanks Wes, that's what I need to know for now.

Since 5.0 is working - doesn't require SSL - then we can just bundle
jtapi.jar.2.2.3.1 in our application (assume there's no legal issue) and
use it whenever we detect a 4.2 CCM.

-Paul

-----Original Message-----
From: Wes Sisk [mailto:wsisk at cisco.com] 
Sent: Monday, November 06, 2006 10:14 AM
To: Paul Yago
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Using Updater for the jtapi.jar in CCM 4.2

Paul,

Developer Support needs to know that interface is broken,

but generally this is a known issue with 4.2(3) as the Cisco Unity 
Express product suffers the same failure:
CSCsg11684 CUE: Verify Web & JTAPI username reports invalid CM version

/Wes

Paul Yago wrote:
> Hello,
>
> In CCM 4.1.x and CCM 5.0.x it is possible to download the jtapi.jar
> using the Updater package provided by Cisco. However in 4.2.x (4.2.3
in
> particular), I'm unable to connect without SSL (http only, as opposed
to
> https). In 5.0 this is not a problem. 
>
> I saw nothing in the Updater package documentation regarding this. I
> could allow my application machine to accept all self-signed
> certificates; however I'd prefer not to leave this kind of security
> hole. 
>
> Is there a more elegant solution that someone's discovered?
>
> Thanks,
> Paul
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>