When I got in today, it was evident that my coworker installed a ton of Zimlets overnight. I read in the wiki how to configure the asterisk Zimlet, and I seem to be having issues. It thinks the zimlet is not found...when it clearly was.
OK...nevermind. Evidently, if you're not in /opt/zimbra/zimlets-extra, you can't run the zmzimletctl command. Sounds like it'd be a simple fix in zmzimletctl. Ooh, a bash script! Here's a patch you can apply to make zmzimletctl less annoying:
EDIT: Dangit, if you wish to use filenames (like the cfg.tmp file in the example on Asterisk VOIP Zimlet - ZimbraWiki) you need to reference its full path. So...this script could use a little more intelligence in that regard. If this is a path Zimbra would like to pursue, I'd be happy to make it a little smarter.
EDIT #2: OK...I made a cfg.tmp file to reflect the real IP addresses of the SIP host and the local machine, but even though I can now make calls...the command mentioned to view the config doesn't ever reflect my changes. I still get the IP addresses that were set before my changes. (I'm using zmzimletctl getConfigTemplate com_zimbra_asterisk.zip)
The error I was getting, for those who might search for it:
--- zmzimletctl 2007-05-11 20:39:55.000000000 -0400
+++ zmzimletctl_with_cd 2007-06-05 10:27:17.000000000 -0400
@@ -24,4 +24,9 @@
# ***** END LICENSE BLOCK *****
exec `dirname $0`/zmjava com.zimbra.cs.zimlet.ZimletUtil "$@"
[zimbra@zimbra2 log]$ zmzimletctl getConfigTemplate com_zimbra_asterisk.zip
Error: Zimlet not found: com_zimbra_asterisk.zip