Ok, I've got a zip file attached. Just tested it. It works on my system.
Which is the only thing I've been claiming all this time.
Some questions have been asked:
Q - Why use the bridging?
A - Why not? That's how I figured out how to do this - I make no claims that it's the easiest or best way.
Q - Why not use method X,Y,Z?
A - No reason at all. Go for it.
Now - READ THIS PART:
This is not the complete zimlet, the file was to large, so I removed the jar files JainSipApi1.1.jar and nist-sip-1.2.jar. Grab these from your existing copy and recreate the zip file.
What I changed:
Modified the jsp to handle the "180 Ringing" response, which I think may be causing some of the problems seen here. That's the only logic change I made.
I added the ability to turn debugging on and off in the config_template.xml. Legal values are "true" and "false". Other values will default to "false". No value will default to a stack trace I've also added a limit to the number of times it will try to bind, so it won't spin if the configured IP is wrong for the local host.
How to do this:
Recreate the zip (with the two jar files.)
zmzimletctl deploy com_zimbra_asterisk.zip
zmzimletctl getConfigTemplate com_zimbra_asterisk.zip > conf.xml
edit conf.xml to set IP addresses for the local server, the sip server, and turn debug on or off.
zmzimletctl configure conf.xml
Log in, set your accounts, and place a call.
Alternatively, just hit this URL (munged so it doesn't show up as a link):
http:/ /localhost/service/zimlet/com_zimbra_asterisk/asterisk.jsp?to=111&from=15555551212&uname=222&pas s=333&debug=true
Assuming localhost is where your server is.
If debugging is turned on, output will go to /opt/zimbra/tomcat/logs/catalina.out,
and will dump all the SIP traffic.
Then, when you're frustrated, you'll at least have some data to post. And, I'll do my best to keep up with this, and work through problems.
Lastly - Moebis - attacking someone who provides free software for your enjoyment is not the correct usage of the term "open source".