[cisco-voip] how to make ExtensionMobility use HTTPS

[cips]

I already figured this out, using HTTPS or port 8443 gives me the XML output
of the service so this part seems to work.

But I still have to "accept" the certificate warning.

I expect the phones need some kind of certificate to support this? I'm I
correct?

 

Any thoughts?

 

From: Jason Burns [mailto:burns.jason at gmail.com] 
Sent: dinsdag 18 januari 2011 22:14
To: Ryan Ratliff
Cc: cips; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] how to make ExtensionMobility use HTTPS

 

One small but crucial piece is the port. https defaults to tcp port 443.

CUCM Secure Services listen on 8443

https://<serverIP>:8443/<whatever your EM URL is>

Can you give that a try and see if it makes a difference?

-Jason

On Tue, Jan 18, 2011 at 12:32 PM, Ryan Ratliff <rratliff at cisco.com> wrote:

You shouldn't have to add a second service.  The phone service should have
two URLs you can provide, one for secure, one for non-secure. 

 

For testing purposes point a web browser to the https URL and see if it
gives you some xml text as a result.  Your browser may complain about the
formatting but you can view the source to see what comes back.

 

-Ryan

 

On Jan 18, 2011, at 10:37 AM, cips wrote:

 

Hi All,

 

Running CM 8, trying to figure out how I can allow my users to logon via
ExtensionMobility using HTTPS instead of HTTP.

Now the service is working pointing to
http://172.21.1.181:8080/emapp/EMAppServlet?device=#DEVICENAME#
<http://172.21.1.181:8080/emapp/EMAppServlet?device=#DEVICENAME%23>  but it
is not secure, using HTTP.

 

If I add another phone service pointing to
https://172.21.1.181/emapp/EMAppServlet?device=#DEVICENAME#
<https://172.21.1.181/emapp/EMAppServlet?device=#DEVICENAME%23>  this does
not work. I can see the service in the menu of my IP com (testing phone) but
when I hit the button nothing happens.

 

I assume I've missed something. I guess I need to install certificates and
the phones must be equipped with these certificates to get this to work?
Right?

 

Any thoughts or comments are welcome.

 

Regards.

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

 


_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20110119/68cba813/attachment.html>