Page 15 of 20 FirstFirst ... 51314151617 ... LastLast
Results 141 to 150 of 198

Thread: Asterisk PBX Integration Zimlet (new)

  1. #141
    Join Date
    Jan 2010
    Posts
    3
    Rep Power
    5

    Unhappy Error when try to dial

    Hi all,

    I've try to call extention 701 via Zimbra but got this error. Anybody can help me to resolve this? Thanks

    Code:
    2010-01-15 17:58:07,603 INFO  [Asterisk-Java ManagerConnection-8-Reader-0] [] ManagerConnectionImpl - Connected via Asterisk Call Manager/1.0
    2010-01-15 17:58:07,612 INFO  [btpool0-0://10.0.0.127/service/zimlet/ch_bnc_asterisk/asterisk.jsp?callee=701] [] ManagerConnectionImpl - Successfully logged in
    2010-01-15 17:58:07,616 INFO  [btpool0-0://10.0.0.127/service/zimlet/ch_bnc_asterisk/asterisk.jsp?callee=701] [] ManagerConnectionImpl - Determined Asterisk version: Asterisk 1.4
    2010-01-15 17:58:15,629 ERROR [btpool0-0://10.0.0.127/service/zimlet/ch_bnc_asterisk/asterisk.jsp?callee=701] [] zimlet - Timeout on originating action
    2010-01-15 17:58:15,629 DEBUG [btpool0-0://10.0.0.127/service/zimlet/ch_bnc_asterisk/asterisk.jsp?callee=701] [] zimlet - handleRequest ok
    2010-01-15 17:58:15,630 DEBUG [btpool0-0://10.0.0.127/service/zimlet/ch_bnc_asterisk/asterisk.jsp?callee=701] [] zimlet - {"errorMessage":"Timeout on originating action","extenStateWarning":false,"error":true,"originateSuccess":false,"callee":"701 Mohd Fahmi"}
    2010-01-15 17:58:15,631 DEBUG [btpool0-0://10.0.0.127/service/zimlet/ch_bnc_asterisk/asterisk.jsp?callee=701] [] zimlet - AMI logoff
    2010-01-15 17:58:17,637 WARN  [btpool0-0://10.0.0.127/service/zimlet/ch_bnc_asterisk/asterisk.jsp?callee=701] [] ManagerConnectionImpl - Unable to send LogOff action
    org.asteriskjava.manager.TimeoutException: Timeout waiting for response to Logoff
            at org.asteriskjava.manager.internal.ManagerConnectionImpl.sendAction(ManagerConnectionImpl.java:825)
            at org.asteriskjava.manager.internal.ManagerConnectionImpl.sendAction(ManagerConnectionImpl.java:781)
            at org.asteriskjava.manager.internal.ManagerConnectionImpl.logoff(ManagerConnectionImpl.java:746)
            at org.asteriskjava.manager.DefaultManagerConnection.logoff(DefaultManagerConnection.java:305)
            at org.apache.jsp.ch_005fbnc_005fasterisk.asterisk_jsp.amiCleanUp(org.apache.jsp.ch_005fbnc_005fasterisk.asterisk_jsp:220)
            at org.apache.jsp.ch_005fbnc_005fasterisk.asterisk_jsp._jspService(org.apache.jsp.ch_005fbnc_005fasterisk.asterisk_jsp:833)
            at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:109)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
            at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:389)
            at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:486)
            at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:380)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
            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:216)
            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:418)
            at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:327)
            at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:126)
            at com.zimbra.cs.zimlet.ZimletResources.service(ZimletResources.java:95)
            at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
            at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166)
            at com.zimbra.cs.zimlet.ZimletFilter.doFilter(ZimletFilter.java:230)
            at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
            at org.mortbay.servlet.UserAgentFilter.doFilter(UserAgentFilter.java:81)
            at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter.java:132)
            at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
            at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388)
            at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
            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:418)
            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.handler.DebugHandler.handle(DebugHandler.java:77)
            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:543)
            at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:924)
            at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:547)
            at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
            at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:405)
            at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
            at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:451)
    2010-01-15 17:58:17,638 INFO  [btpool0-0://10.0.0.127/service/zimlet/ch_bnc_asterisk/asterisk.jsp?callee=701] [] ManagerConnectionImpl - Closing socket.
    2010-01-15 17:58:17,640 INFO  [Asterisk-Java ManagerConnection-8-Reader-0] [] ManagerReaderImpl - Terminating reader thread: Socket closed

  2. #142
    Join Date
    Jan 2010
    Posts
    1
    Rep Power
    5

    Default wat is wrong?

    Hi all
    my error is
    Code:
    2010-01-15 16:11:00,142 INFO  [btpool0-38://zimbra.moll-group.eu/service/zimlet/ch_bnc_asterisk/asterisk.jsp?callee=0620227820] [] zimlet - ch_bnc_asterisk userAstDialContext overwrites global astDialContext value: from_zimbra
    2010-01-15 16:11:00,142 WARN  [btpool0-38://zimbra.moll-group.eu/service/zimlet/ch_bnc_asterisk/asterisk.jsp?callee=0620227820] [] zimlet - Parse error while getting 'astManagerPort'. Using default 5038
    2010-01-15 16:11:00,142 ERROR [btpool0-38://zimbra.moll-group.eu/service/zimlet/ch_bnc_asterisk/asterisk.jsp?callee=0620227820] [] zimlet - Zimlet parameter 'astActionTimeout' is null. Check zimlet config!
    2010-01-15 16:11:00,142 ERROR [btpool0-38://zimbra.moll-group.eu/service/zimlet/ch_bnc_asterisk/asterisk.jsp?callee=0620227820] [] log - /service/zimlet/ch_bnc_asterisk/asterisk.jsp
    java.lang.NullPointerException
    and my config is
    Code:
    <zimletConfig name="ch_bnc_asterisk" version="0.65">
       <host name="zimbra.moll-group.eu">
            <property name="astManagerIp">127.0.0.1</property>
            <property name="astManagerPort">5038</property>
            <property name="astManagerUser">zimbra</property>
            <property name="astManagerSecret">123abc</property>
            <property name="astActionTimeout">8000</property>
            <property name="astNoExtenCheck">true</property>
            <property name="astDialContext">from_zimbra</property>
            <property name="astDialChannelType">Local</property>
            <property name="srcPhonePrefix">062022782</property>
            <property name="calleePrefix"></property>
            <property name="numberCleanRegExp">\s|\.|-|\,|(\(0\)|\(|\))</property>
            <property name="iddPrefix">00</property>
            <property name="astSMSVariable">SMS_MESSAGE</property>
            <property name="astSMSSendContext">sms-send</property>
            <property name="astSMSCenterChannel">CAPI/g1/0622100000</property>
       </host>
       <global>
            <property name="enableSMS">false</property>
            <property name="maxSMSLength">160</property>
            <property name="phonebookBaseUrl">http://www.gelbeseiten.de</property>
            <property name="phonebookUrlCommonParams">ext=1</property>
            <property name="phonebookUrlNumberParam">phone</property>
       </global>
    </zimletConfig
    thanks for you ideas

  3. #143
    Join Date
    May 2009
    Posts
    134
    Rep Power
    6

    Default

    I'm pretty ignorant about how all this works but my first thought is to wonder if you have not set the proper manager.conf permissions. Ours are:

    write = call,command,originate
    www.spiritualoutreach.com
    Making Christianity intelligible to secular society

  4. #144
    Join Date
    Jan 2010
    Posts
    3
    Rep Power
    5

    Lightbulb

    Quote Originally Posted by gracedman View Post
    I'm pretty ignorant about how all this works but my first thought is to wonder if you have not set the proper manager.conf permissions. Ours are:

    write = call,command,originate
    I have use this configuration in manager.conf and manage to call successfully.

    Code:
    read = all
    write = all
    for zimlet config, I was used this one:

    Code:
    <host name="mailcnc.freehostia.com">
        <property name="astManagerIp">10.0.0.128</property>
        <property name="astManagerPort">5038</property>
        <property name="astManagerUser">zimbra</property>
        <property name="astManagerSecret">test1234</property>
        <property name="astActionTimeout">8000</property>
        <property name="astNoExtenCheck">true</property>
        <property name="astDialContext">from-internal</property>
        <property name="astDialChannelType">SIP</property>
        <property name="srcPhonePrefix">7</property>
        <property name="calleePrefix"></property>
        <property name="numberCleanRegExp">\s|\.|-|\,|(\(0\)|\(|\))</property>
        <property name="iddPrefix">00</property>
        <property name="astSMSVariable">SMS_MESSAGE</property>
        <property name="astSMSSendContext">sms-send</property>
        <property name="astSMSCenterChannel">CAPI/g1/0622100000</property>
      </host>
    
      <global>	
        <property name="enableSMS">false</property>
        <property name="maxSMSLength">160</property>
         <property name="phonebookBaseUrl">http://tel.local.ch/q/</property>
         <property name="phonebookUrlCommonParams">ext=1</property>
         <property name="phonebookUrlNumberParam">phone</property>
      </global>
    FYI, I was able to integrate Zimbra with PBX in a Flash (PiaF) as well


    Bert82, I think you need to configure zimlet manually by run this "zmzimletctl configure /tmp/ch_bnc_asterisk_config.xml" and restart the mailbox "zmmailboxdctl restart"

    Hope this will help!

  5. #145
    Join Date
    Mar 2010
    Posts
    2
    Rep Power
    5

    Default Problem configuring zimlet

    Hi guys, this is my first post on the forum and my first install of the Asterisk zimlet. Iíve almost got this zimlet running Ė but not quite!

    I have a zimbra server (Version zcs-5.0.22) running on CentOS 5 that I am trying to install the zimlet on. The zimlet is v0.65. I get through the command-line install with no problems but am getting an error when I go to apply the configuration xml file right at the end. My config file is attached as config.txt

    I am suíd to zimbra. When I enter the command to apply the config file I get this:

    [zimbra@zimbra ~]$ zmzimletctl configure /tmp/zimlet.cfg
    [] INFO: Configure zimlet on zimbra.shb.local
    [] ERROR: Error
    com.zimbra.common.soap.SoapFaultException: system failure: cannot configure
    ExceptionId:btpool0-12:1268191950194:06a790d6b806dc4c
    Code:service.FAILURE
    at com.zimbra.common.soap.Soap12Protocol.soapFault(So ap12Protocol.java:86)
    at com.zimbra.common.soap.SoapTransport.extractBodyEl ement(SoapTransport.java:264)
    at com.zimbra.common.soap.SoapTransport.parseSoapResp onse(SoapTransport.java:225)
    at com.zimbra.common.soap.SoapHttpTransport.invoke(So apHttpTransport.java:291)
    at com.zimbra.common.soap.SoapHttpTransport.invoke(So apHttpTransport.java:226)
    at com.zimbra.common.soap.SoapTransport.invoke(SoapTr ansport.java:316)
    at com.zimbra.common.soap.SoapTransport.invoke(SoapTr ansport.java:280)
    at com.zimbra.cs.zimlet.ZimletUtil$ZimletSoapUtil.soa pConfigureZimlet(ZimletUtil.java:1339)
    at com.zimbra.cs.zimlet.ZimletUtil$ZimletSoapUtil.con figureZimletOnServer(ZimletUtil.java:1323)
    at com.zimbra.cs.zimlet.ZimletUtil$ZimletSoapUtil.con figureZimlet(ZimletUtil.java:1206)
    at com.zimbra.cs.zimlet.ZimletUtil.dispatch(ZimletUti l.java:1595)
    at com.zimbra.cs.zimlet.ZimletUtil.main(ZimletUtil.ja va:1639)
    [zimbra@zimbra ~]$

    Have you any idea what I could have done wrong? Any help would be much appreciated.

    Neil
    Attached Files Attached Files

  6. #146
    Join Date
    Mar 2010
    Posts
    2
    Rep Power
    5

    Default Next time I'll RTFF! (zimlet config problem)

    Quote Originally Posted by nellyb View Post
    Hi guys, this is my first post on the forum and my first install of the Asterisk zimlet. Iíve almost got this zimlet running Ė but not quite!

    I have a zimbra server (Version zcs-5.0.22) running on CentOS 5 that I am trying to install the zimlet on. The zimlet is v0.65. I get through the command-line install with no problems but am getting an error when I go to apply the configuration xml file right at the end. My config file is attached as config.txt

    I am suíd to zimbra. When I enter the command to apply the config file I get this:

    [zimbra@zimbra ~]$ zmzimletctl configure /tmp/zimlet.cfg
    [] INFO: Configure zimlet on zimbra.shb.local
    [] ERROR: Error
    com.zimbra.common.soap.SoapFaultException: system failure: cannot configure
    ExceptionId:btpool0-12:1268191950194:06a790d6b806dc4c
    Code:service.FAILURE
    at com.zimbra.common.soap.Soap12Protocol.soapFault(So ap12Protocol.java:86)
    at com.zimbra.common.soap.SoapTransport.extractBodyEl ement(SoapTransport.java:264)
    at com.zimbra.common.soap.SoapTransport.parseSoapResp onse(SoapTransport.java:225)
    at com.zimbra.common.soap.SoapHttpTransport.invoke(So apHttpTransport.java:291)
    at com.zimbra.common.soap.SoapHttpTransport.invoke(So apHttpTransport.java:226)
    at com.zimbra.common.soap.SoapTransport.invoke(SoapTr ansport.java:316)
    at com.zimbra.common.soap.SoapTransport.invoke(SoapTr ansport.java:280)
    at com.zimbra.cs.zimlet.ZimletUtil$ZimletSoapUtil.soa pConfigureZimlet(ZimletUtil.java:1339)
    at com.zimbra.cs.zimlet.ZimletUtil$ZimletSoapUtil.con figureZimletOnServer(ZimletUtil.java:1323)
    at com.zimbra.cs.zimlet.ZimletUtil$ZimletSoapUtil.con figureZimlet(ZimletUtil.java:1206)
    at com.zimbra.cs.zimlet.ZimletUtil.dispatch(ZimletUti l.java:1595)
    at com.zimbra.cs.zimlet.ZimletUtil.main(ZimletUtil.ja va:1639)
    [zimbra@zimbra ~]$

    Have you any idea what I could have done wrong? Any help would be much appreciated.

    Neil
    Thanks to mike.little - I ran the install through the admin GUI then ran config via zmzimletctl configure. The zimlet is now installed!

  7. #147
    Join Date
    May 2009
    Posts
    134
    Rep Power
    6

    Default Accounting for local country codes

    Hello, all. I just noticed some unpleasant behavior in the way we have configured our Asterisk zimlet. This particular PBX is in the US so we automatically add 011 when a number starts with +, i.e., international calling. Because our company is international, we enter our US numbers in our address list as +1 (xxx) xxx-xxxx. As a result, dialing these numbers from the zimlet prepends 011 and the call is routed as an international call.

    We could simply eliminate the +1 in our address lists but we really do like to consider ourselves a company without borders and not assume that all numbers are US unless otherwise stated! Would it be possible to extend the Zimlet configuration to enter the user's local country code and have this exempted from the international prepending logic? Thanks - John
    www.spiritualoutreach.com
    Making Christianity intelligible to secular society

  8. #148
    Join Date
    Mar 2007
    Posts
    14
    Rep Power
    8

    Default

    Quote Originally Posted by gracedman View Post
    Hello, all. I just noticed some unpleasant behavior in the way we have configured our Asterisk zimlet. This particular PBX is in the US so we automatically add 011 when a number starts with +, i.e., international calling. Because our company is international, we enter our US numbers in our address list as +1 (xxx) xxx-xxxx. As a result, dialing these numbers from the zimlet prepends 011 and the call is routed as an international call.

    We could simply eliminate the +1 in our address lists but we really do like to consider ourselves a company without borders and not assume that all numbers are US unless otherwise stated! Would it be possible to extend the Zimlet configuration to enter the user's local country code and have this exempted from the international prepending logic? Thanks - John
    It is best to take care of this in Asterisk, on the outbound trunk you should format the number correctly for the carrier you are using.

    Thanks for this great Zimlet, we have been using it for sometime with great success.

    We recently expanding our offices and added a second server to our Zimbra installation and also added a second Asterisk. Like a lot of people I started experiencing problems with the Host and Global configuration of the Zimlet.

    After spending a little time investigating I came to the conclusion that the design was not quite right IMHO. It is my experience that you usually define all configuration variables in the Global scope, and then over ride any that you need to in the Host scope.

    As an example the IP of our Asterisk needed to be set on a per host basis as well as the IDD Prefix. The way the code was written you had to define ALL parameters in the Host scope as well as Global scope. If you didn't the Zimlet threw Null Pointer exceptions, as well as this you had to maintain the same data in muliple places.

    So I have changed the code and contribute it here for your consumption. It may not be elegant, as this is my first venture into JSP, but here it is.

    The change is a re-write of the getZConfigAttribute method in asterisk.jsp.
    Code:
    private String getZConfigAttribute(Map zConfig, String attributeName) {
      String localAttribute  = (String) ((Map) zConfig.get("local")).get(attributeName);
      try {
        zimletLog.debug("Local Attribute '" + attributeName + "' value '" + localAttribute + "' length '" + localAttribute.length() + "'" );
        return localAttribute;
      } catch ( NullPointerException npeL ) {
        String globalAttribute = (String) ((Map) zConfig.get("global")).get(attributeName);
        try {
          zimletLog.debug("Global Attribute '" + attributeName + "' value '" + globalAttribute + "' length '" + globalAttribute.length() + "'" );
          return globalAttribute;
        } catch ( NullPointerException npeG ) {
          zimletLog.debug("Attribute '" + attributeName + "' not found in config.");
          return null;
        }
      }
    }
    Last edited by Stuart; 04-21-2010 at 03:57 AM.

  9. #149
    Join Date
    Apr 2010
    Posts
    2
    Rep Power
    5

    Default

    Hi Christof

    > In the meantime you can try version 0.62 Download Asterisk PBX
    > Integration Zimlet from SourceForge.net with zimbra 6.

    I have Zimbra 6.0.6 (Release 6.0.6_GA_2324.RHEL5_20100406131453. )
    and Asterisk Asterisk 1.6.0.26 and I'm experiencing the "Code:account.NO_SUCH_ZIMLET" problem both with the 0.62, 0.65, 0.65mod Asterisk Zimlet versions. Is there any new release which can fix this problem, or should I try earlier Zimbra versions?

    Cheers,
    IstvŠn

  10. #150
    Join Date
    Nov 2009
    Location
    Nantes, France
    Posts
    29
    Rep Power
    6

    Default

    @iviczi : the zimlet works with zimbra 6 and Asterisk 1.6.

    Where do you have this error "Code:account.NO_SUCH_ZIMLET" ?

    Did you create the two links before installing the zimlet ?

    Can you post your zimlet configuration file ?



    general: there are three or more threads concerning the same zimlet. Maybe we can write a summary concerning the installation process ?
    Last edited by typiquement; 05-06-2010 at 07:53 AM.

Similar Threads

  1. Replies: 21
    Last Post: 02-04-2010, 10:06 AM
  2. Outlook 2007 Beta error
    By bersrker in forum Zimbra Connector for Outlook
    Replies: 13
    Last Post: 07-17-2008, 08:38 AM
  3. Replies: 5
    Last Post: 01-11-2008, 05:34 AM
  4. weird Asterisk zimlet behaviour
    By bbarnett in forum Zimlets
    Replies: 4
    Last Post: 10-17-2007, 09:36 AM
  5. Post instsallation problems
    By Assaf in forum Installation
    Replies: 14
    Last Post: 01-29-2007, 11:38 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •