WebEx
This Zimlet integrates WebEx with the Zimbra Collaboration Suite.
The Zimlet allows you to list your upcoming WebEx meetings, as well as host and join a WebEx meeting with 1 click. Drag-and-Drop contacts and appointments to create new WebEx meetings.
- Right-click on the Zimlet panel icon to manage your WebEx accounts and meetings
- Create a WebEx meeting when creating an appointment
- Easily start a Quick meeting
- Drag-and-Drop contacts and email messages to create a new WebEx meeting with those contacts
- Drag-and-Drop an appointment to create a new WebEx meeting with the attendees at the same time as the appointment
Checkout YouTube Video here:
http://www.youtube.com/watch?v=6m_vne1cgvk
Revision Notes:
- 3.3 allows users to just 'insert' webex meeting info & allows them to make sure everything look right.
- 2.8 fixes http://bugzilla.zimbra.com/show_bug.cgi?id=55352
- 2.4 fixes some bugs and has localization.
| Downloads: | 10,141 |
|---|---|
| Latest Version: | 3.3 |
| Categories: | Business, Calendar, Contacts, CRM, Mail, Organization, Telecom, Travel, Web |
| Compatibility: | ZCS 6.0.6, ZCS 6.0.7 |
| License: | AL |
| Created: | April 18, 2007 |
| Updated: | February 21, 2012 |
Reviews
i find it very convenient to have WebEx available right in my Zimbra interface. I also really like when I schedule a meeting in Zimbra, I can click and save as a webex meeting w/o having to switch to the WebEx site.
my speaker and microphone does not work in a meeting when I create it using this zimlet in 6.0.9 NE
This zimlet does not work with Zimbra 7.1.3. The teleconference passcode will be reported by WebEx as invalid and there is no option to use the microphone and speaker. So essentially you can not schedule any meetings that require any kind of audio, which makes this zimlet a bit useless.
I contacted support and was told that this zimlet is not supported by them, that I need to contact the author.
This is not working for me either. I get the error: Test failed. This WebEx account is not valid.
The username and password are in fact correct. After I dismiss this error, I get a second error:
Error parsing WebEx XML response or malformed XML.
Details:
HTTP ERROR 500
Problem accessing /service/proxy. Reason:
Connection timed out: connect
Caused by:java.net.ConnectException: Connection timed out: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:529)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:564)
at com.zimbra.common.net.CustomSSLSocket.connect(CustomSSLSocket.java:292)
at com.zimbra.common.net.ProtocolSocketFactoryWrapper.createSocket(ProtocolSocketFactoryWrapper.java:46)
at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707)
at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1361)
at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:387)
at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
at com.zimbra.common.httpclient.HttpClientUtil.executeMethod(HttpClientUtil.java:53)
at com.zimbra.common.httpclient.HttpClientUtil.executeMethod(HttpClientUtil.java:39)
at com.zimbra.cs.zimlet.ProxyServlet.doProxy(ProxyServlet.java:243)
at com.zimbra.cs.zimlet.ProxyServlet.doPost(ProxyServlet.java:157)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:725)
at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:206)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:814)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390)
at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:218)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:422)
at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.handler.rewrite.RewriteHandler.handle(RewriteHandler.java:230)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:585)
at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:988)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:756)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:415)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:429)
at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:451)
Powered by Jetty://
That suggests that this may not be a genuine wrong-credentials message, but just the default message when the credentials fail to validate for any reason, including failure to connect at all in order to validate.
Add a Review
Please log in to post review/comments.
Older Versions
Version 2.8
| Compatibility: | ZCS 6.0, ZCS 6.0.6, ZCS 6.0.7 |
|---|---|
| Created: | March 29, 2011 |
| More details… |
