Asterisk PBX Integration Zimlet

Interested in talking about Mash-up's? This is the place.
watanesachin
Posts: 18
Joined: Sat Sep 13, 2014 1:24 am

Asterisk PBX Integration Zimlet

Postby watanesachin » Mon Aug 23, 2010 1:21 pm

[quote user="typiquement"]in your manager.conf, try this :
bindaddr = 10.48.3.174
[zimbra]

secret = sachin12345

permit = 10.48.0.0/255.255.0.0

read = system,call,log,verbose,command,agent,user

write = system,call,log,verbose,command,agent,user
with a sip phone, you can establish a communication between 1000 and 1001 ?



if it doesn't work, try to replace by in your config.xml for the zimlet. And change 03185858 by . But maybe you need this line.[/QUOTE]

i done this but not working
zmzimletctl configure /tmp/ch_bnc_asterisk_config.xml
zmmailboxdctl restart
after changes i used this command am i going wright
pls reply am doing this work from last 1 months but no success


watanesachin
Posts: 18
Joined: Sat Sep 13, 2014 1:24 am

Asterisk PBX Integration Zimlet

Postby watanesachin » Mon Aug 23, 2010 1:38 pm

pls view this pics

untitled123.jpg

watanesachin
Posts: 18
Joined: Sat Sep 13, 2014 1:24 am

Asterisk PBX Integration Zimlet

Postby watanesachin » Mon Aug 23, 2010 2:22 pm

[quote user="watanesachin"]pls view this pics[/QUOTE]
hi pls seee

untitled444.jpg

gracedman
Advanced member
Advanced member
Posts: 125
Joined: Sat Sep 13, 2014 12:24 am

Asterisk PBX Integration Zimlet

Postby gracedman » Mon Apr 25, 2011 10:15 pm

Hello, all. We have just upgraded to Zimbra 7.1 (Release 7.1.0_GA_3140.RHEL5_64_20110329135300 CentOS5_64 NETWORK edition) and it looks like the zimlet is broken. We get the empty Asterisk PBX Integration Error dialog and the following in mailbox.log:
2011-04-25 23:11:07,724 WARN [btpool0-10://zimbra.pacifera.com/service/zimlet/ch_bnc_asterisk/asterisk.jsp?callee=2xxyyy7183] [] log - /service/zimlet/ch_bnc_asterisk/asterisk.jsp

org.apache.jasper.JasperException: PWC6033: Unable to compile class for JSP
PWC6197: An error occurred at line: 37 in the jsp file: /ch_bnc_asterisk/asterisk.jsp

PWC6199: Generated servlet error:

The method searchGal(String, ArrayList, ZMailbox.GalEntryType) in the type ZMailbox is not applicable for the arguments (String, String, ZMailbox.GalEntryType)


at org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:123)

at org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:296)

at org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:376)

at org.apache.jasper.compiler.Compiler.compile(Compiler.java:437)

at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:608)

at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:360)

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: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.servlet.Dispatcher.forward(Dispatcher.java:330)

at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:126)

at com.zimbra.cs.zimlet.ZimletResources.service(ZimletResources.java:96)

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:240)

at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)

at com.zimbra.cs.servlet.SetHeaderFilter.doFilter(SetHeaderFilter.java:79)

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 com.zimbra.cs.servlet.ThrottlingFilter.doFilter(ThrottlingFilter.java:71)

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: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.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:929)

at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)

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:410)

at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:451)
Any ideas what we can do to fix this? I tried redeploying the zimlet just in case but that did not help.
Either we need a real quick fix or we'll need to back out the upgrade. Thanks - John
uxbod
Ambassador
Ambassador
Posts: 7811
Joined: Fri Sep 12, 2014 10:21 pm

Asterisk PBX Integration Zimlet

Postby uxbod » Tue Apr 26, 2011 4:17 am

For the time being I believe we can just remove the following code from asterisk.jsp
} else if(this.searchGal) {

ZSearchGalResult zgalres = this.zmailbox.searchGal(phoneNbr,"",GalEntryType.all);

ZContact zcontact = null;

if (zgalres.getContacts().size()>=1) {

zcontact = zgalres.getContacts().get(0);

}

if(zcontact != null) {

String fname = this.getZContactAttr(zcontact,"firstName");

String lname = this.getZContactAttr(zcontact,"lastName");

String company = this.getZContactAttr(zcontact,"company");

zimletLog.debug("Gal fname: " + fname + " lname: " + lname + " company: " + company);

if(zgalres.getContacts().size() > 1 && company.length() > 0 ) {

searchRes = company;

}

else {

searchRes = fname + " " + lname;

}

}

}
as we do not enable SearchGal by default for the Zimlet. I believe the problem has been caused by Bug 56016 – Need to be able to search gal by name, department, and email address so in theory problem requires another parameter adding to the zmailbox.searchGal() function.
gracedman
Advanced member
Advanced member
Posts: 125
Joined: Sat Sep 13, 2014 12:24 am

Asterisk PBX Integration Zimlet

Postby gracedman » Tue Apr 26, 2011 9:32 am

That appears to have fixed the problem after fully redeploying, i.e,. rereading the configuration and flushing the cache by doing zmmailboxdctl stop and zmmailboxdctl start. Thanks - John
gracedman
Advanced member
Advanced member
Posts: 125
Joined: Sat Sep 13, 2014 12:24 am

Asterisk PBX Integration Zimlet

Postby gracedman » Tue Apr 26, 2011 9:43 am

Stuart is exactly right about handling the problem of prepending the international dialing code to local calls in Asterisk rather than the zimlet. Here is a more in-depth explanation from our internal ticket for addressing this issue for those who may need more information:


We have a problem with the Zimbra Asterisk Integration zimlet where it will prepend the international dialing prefix (e.g., 011 in the US, 00 in the UK) before any numbers preceded by a +. Thus, international friendly phone entries (e.g., +1 (234) 567-8901) will be misdialed when called from their own country (e.g., calling the example given from the US dials 01112345678901).

I originally thought this is something which should be fixed in the Asterisk zimlet but then realized this was not only very difficult but illogical. The issue is really not a user issue but a PBX issue. For example, we could rewrite the zimlet to allow a user to set their current country but, it doesn't matter if the caller is calling from the US or the UK or China. The issue is from where the PBX is dialing.
I then thought of editing the zimlet to configure the country code for the PBX but that still seemed the wrong place and what about when we start routing between PBXs in different countries. Thus, it seems we should fix this at the PBX level.
We have a section in each client's dial plan which sets the appropriate caller id number and handles routing for national and international calls when allowed. I think this is the place to do the rewriting of the international dialing prefix. For example, in our company dial plan, we would do this in the c100 context just before the entry for identifying and routing international calls. We would add the following:
exten => _0111NXXNXXXXXX,1,ExecIf($[${CALLERID(num)} - 1000000
exten => _0111NXXNXXXXXX,n,ExecIf($[${CALLERID(ani)} - 1000000
exten => _0111NXXNXXXXXX,n,Goto(outbound-US,${EXTEN:3},1)
I've reviewed the list of all country codes and it appears that they are intelligently enough structured that directly matching a country code will not accidentally match another country code with a longer sequence of digits, e.g., we can safely say 0044 means we have a UK international dialing prefix in front of a UK number because there is no three digit international country code starting with 44. Likewise, there are not two or three digit country codes starting with 1.


Hope this helps someone else! Thanks Stuart.
chlauber
Advanced member
Advanced member
Posts: 71
Joined: Fri Sep 12, 2014 11:41 pm

Asterisk PBX Integration Zimlet

Postby chlauber » Wed Apr 27, 2011 8:24 am

hi gracedman,

jep it seems that search gal has changed in api. i am going to fix this in a new version of the zimlet. as soon as i can download the source code for 7.1 i am able to have a look at the changes there...
sky_09
Posts: 2
Joined: Sat Sep 13, 2014 1:55 am

Asterisk PBX Integration Zimlet

Postby sky_09 » Sat Apr 30, 2011 10:31 am

Need HELP...
i have installed zcs 6, zimlet for asterisk and asterisk server,,

anything goes right,, but when client A call to client B it can't happen, in GUI no error,, but

when i see in /opt/zimbra/log/mailbox.log i get error like
PWC6032: Unable to load tag handler class "com.zimbra.cs.taglib.ZimletConfig" for tag "z:zimletconfig"
i hope u will response my question, i'm sorry for my english...
fuadprasetyo77
Posts: 6
Joined: Sat Sep 13, 2014 1:59 am

Asterisk PBX Integration Zimlet

Postby fuadprasetyo77 » Thu May 12, 2011 6:12 pm

i`ve installed the asterisk zimlet for 0.65,

and it was success.

i want to trunk into trixbox (asterisk server)

but i`ve new problem, that i can`t resolve with my self..... i really got stack
here my ch_bnc_asterisk_config.xml :






10.14.200.248

5038

zimbra

switching



8000



true



from-internal



SIP



1







s|.|-|,|((0)|(|))

Variable name used in SMS() application for SMS message body

-->

SMS_MESSAGE



sms-send



CAPI/g1/0622100000









true

160



http://tel.local.ch/q/>



ext=1



phone






and here the manager.conf in the trixbox :
;

; Asterisk Call Management support

;

[general]

enabled = yes

port = 5038

bindaddr = 0.0.0.0
[admin]

secret = amp111

deny=0.0.0.0/0.0.0.0

permit=127.0.0.1/255.255.255.0

read = system,call,log,verbose,command,agent,user,originate

write = system,call,log,verbose,command,agent,user,originate
[zimbra]

secret = switching

permit = 10.14.200.200/255.255.255.0

read = system,call,log,verbose,command,agent,user,originate

write = system,call,log,verbose,command,agent,user,originate
bindaddr = 10.14.200.200
#include manager_additional.conf

#include manager_custom.conf
and, when i make a call "4545" from asterisk zimlet,, there was an error said

" Authentication error on login to asterisk server for user zimbra"
and i look the log in the /tmp/zimbra/log/mailbox.log

here the contain of mailbox.log

info: null callee: 4545 smsTo: null smsMsg:

null

2011-05-13 06:15:11,035 INFO [btpool0-0] [] zimlet - ch_bnc_asterisk callee:4545

2011-05-13 06:15:11,035 DEBUG [btpool0-0] [] zimlet - Checking Extension state

2011-05-13 06:15:11,035 DEBUG [btpool0-0] [] zimlet - Checking Extension state skipped due to global config property 'astNoExtenCheck'

2011-05-13 06:15:11,035 DEBUG [btpool0-0] [] zimlet - Creating orignate action for dialing

2011-05-13 06:15:11,035 INFO [btpool0-0] [] zimlet - Do AMI login.

2011-05-13 06:15:11,036 INFO [btpool0-0] [] ManagerConnectionImpl - Connecting to 10.14.200.248:5038

2011-05-13 06:15:11,073 INFO [Asterisk-Java ManagerConnection-9-Reader-0] [] ManagerConnectionImpl - Connected via Asterisk Call Manager/1.1

2011-05-13 06:15:12,114 INFO [btpool0-0] [] ManagerConnectionImpl - Closing socket.

2011-05-13 06:15:12,115 INFO [Asterisk-Java ManagerConnection-9-Reader-0] [] ManagerReaderImpl - Terminating reader thread: No more lines available: null

2011-05-13 06:15:12,115 ERROR [btpool0-0] [] zimlet - Authentication error on login to asterisk server for user zimbra

2011-05-13 06:15:12,115 DEBUG [btpool0-0] [] zimlet - handleRequest ok

2011-05-13 06:15:12,116 DEBUG [btpool0-0] [] zimlet - {"callee":"4545","errorMessage":"Authentication error on login to asterisk server for user zimbra","extenStateWa$

2011-05-13 06:15:12,116 WARN [btpool0-0] [] zimlet - AMI not logged in, so no logoff from asterisk manager.
-------------------------------------------------------------------------------------------------------------------

please help Mr. Chlauber..

Thank you very much

:)

Return to “Zimlets”

Who is online

Users browsing this forum: No registered users and 3 guests