Name | Modified | Size | Downloads / Week |
---|---|---|---|
Parent folder | |||
ch_bnc_asterisk_0.62.zip | 2009-01-30 | 356.7 kB | |
Totals: 1 Item | 356.7 kB | 0 |
Installing ch_bnc_asterisk -------------------------- First: It does not work with the Zimbra Desktop version. It works with the Open Source Edition as well as with Network Edition. Currently verion 0.71 tested with ZCS 7.1.1 For ZCS 5.x use Version 0.65, for ZCS 6.x and 7.0 use Version 0.7b. For ZCS 6 and ZCS 7 we need to fix JSP/taglib support with symlinks. Add symlinks in /opt/zimbra/jetty/webapps/zimlet/WEB-INF # cd /opt/zimbra/jetty/webapps/zimlet/WEB-INF # ln -s /opt/zimbra/jetty/webapps/service/WEB-INF/zimbra.tld # ln -s /opt/zimbra/jetty/webapps/service/WEB-INF/lib If you are upgrading from older version, you might need to remove asterisk-java-1.0.0-m2.jar manually. Basically it's been installed like any other zimlet. See also administation guide chapter 14 http://www.zimbra.com/docs/ne/latest/administration_guide/wwhelp/wwhimpl/js/html/wwhelp.htm CLI example for a Linux server: 1) Copy ch_bnc_asterisk.zip to /opt/zimbra/zimlets scp ch_bnc_asterisk.zip zimbra@zdev:zimlets/ 2) Install as user "zimbra" zmzimletctl install zimlets/ch_bnc_asterisk.zip 3) Get configuration template and edit configuration to your needs. zmzimletctl getConfigTemplate zimlets/ch_bnc_asterisk.zip > /tmp/ch_bnc_asterisk_config.xml vi /tmp/ch_bnc_asterisk_config.xml 4) Configure zimlet zmzimletctl configure /tmp/ch_bnc_asterisk_config.xml (In cases you get SOAP Error during configuration try reinstalling zimlet using admin webgui or you might need renaming the Zimlet's zip to ch_bnc_asterisk.zip) 5) restart mailboxd This is the only part that is not usual for installing a zimlet. This is because a zmzimletctl install does not load the needed jar file included in the zimlet. zmmailboxdctl restart Zimlet Debugging ----------------- * Client: For the client part it may help to just open the Firefox Error Console (JavaScript errors). * Server: Set the log level for the zimelts to DEBUG. Configure this the following way: Add the following line to /opt/zimbra/conf/log4j.properties.in log4j.logger.zimbra.zimlet=DEBUG After editing log4j.properties.in you need to restart mailboxd: zmmailboxdctl restart Then watch logfile /opt/zimbra/log/mailbox.log. The Zimbra server does some caching. So after installing a new Zimlet or new Version its a good idea to restart mailboxd and to do a logoff/login.