Page Comparison

...

1. the backend service which runs as a self contained java serviceis a part of Noojee Admin
2. the front end AJAX library which needs to be integrated into your web application.

...

1. Asterisk configuration
2. Toolbar configuration
3. Plugin configurationAnswer bar - deploy & configure in java container (tomcat, glass fish ...)
4. Web page integration - addition of javascript to web pages

Packaging

Noojee Answer bar is packaged as a WAR file and will require a Java Servlet container to be deployed in.

A number of Java Servlet containers are available, and Noojee recommends Tomcat 6.

Tomcat 6 is free and available for download from the Apache Foundation.

Deployment

There are a number of files that will need to be made available on the web server - they are included in the WAR file and will be deployed automatically when the WAR file is deployed to the Java Servlet container (e.g. Tomcat).

Deployment of the Answer Bar will be specific to your java container, please refer to the containers documentation for deploying WAR files.

Tomcat 6 deployment

...

...

Noojee

...

cd /var/log/tomcat6
sudo mkdir noojee-answerbar
sudo chown tomcat6:tomcat6 noojee-answerbar
sudo service tomcat6 restart

You can now deploy the Noojee Answer WAR file to tomcat. Refer to the Apache Web site deployment guide for details.

Tomcat6 tip

Altering the Context tag in context.xml (/etc/tomcat6/context.xml for ubuntu 10.04) will allow reloading of the answerbar webapp without restarting tomcat

<Context reloadable="true">

Then to effect a restart of the webapp after changing config files, simply

touch web.xml

Noojee PBX deployment

If you are running Noojee PBX then the Answer Bar will already be deployed on your system and providing you have the appropriate license installed you can confirm it is running by viewing the following URL.

...

http://<pabx>/servicemanager/ToolbarPage

Where <pabx> is the IP address or host name of your Noojee PBX.

Dial Plan

The following dialplan will need to be added to your Asterisk server so that the Answer bar can connect calls when the answer button is clicked. If you are running Noojee PBX this context is shipped by default.

[answerbar]
exten => bounce,1,nocdr();noop;forkcdr(R)
exten => bounce,n,goto(answerbar,${answerbardest},1)
exten => _X.,1,dial(SIP/${EXTEN})

exten => h,1,resetcdr(w)

For your convenience we ship a copy of the above dial plan in answerbar.conf which is contained in the Noojee Answer WAR file. 

...

...

.

...

Noojee Answer is able to display the Direct In Dial (DID) number that a call comes in on. In order for this to work a channel variable 'DIDNum' must be set on each call. The DIDNum channel variable must contain the Direct In Dial number. On most Asterisk distributions this is set by default, so no action is required.

If this is not being set, dialplan similar to the following line may be required

exten => _X.,1,dial(SIP/${EXTEN})

Apache Forward

It is NOT advised to forward answer bar requests and under normal circumstances it is not required.

...

ProxyPassReverseCookiePath /noojee-answerbar /answerbar-deported

for deployment on Noojee PBX add the following lines to /etc/apache2/sites-enabled/njadmin

ProxyPassReverse /noojee-answerbar http://pbx.yourdomain.com:8080/noojee-answerbar
ProxyPass /noojee-answerbar http://pbx.yourdomain.com:8080/noojee-answerbar

...