Noojee Answer bar is a javascript toolbar which provides realtime information about incoming calls in a browser and allows a browser page or Web 2.0 application to be Screen Popped.
Noojee Answer bar has two main components
There are 4 parts to the deployment of the Answer bar:
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.
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.
The following provides deployment details for Tomcat 6 operating under Linux. Noojee recommends Ubuntu 10.04.
Before you deploy Noojee Answer to your Tomcat 6 server you first need to create the Noojee Answer log directory as follows:
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.
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 |
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.
The default start page is:
http://<pabx>/servicemanager/ToolbarPage |
Where <pabx> is the IP address or host name of your Noojee PBX.
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.
You can use the provided configuration file by including it from /etc/asterisk/extensions.conf with
#include 'answerbar.conf' |
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}) |
It is NOT advised to forward answer bar requests and under normal circumstances it is not required.
If your circumstances are not normal the following provides some guides on how to do this using Apache.
This may interfere with cookies which are used to track answer-bar sessions.
This command for the apache VirtualHost can be used to remap the cookie path to the correct path. In the example below "answerbar-deported" would be the path used to refer to the answer bar externally
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 |
Where pbx.yourdomain.com is the ip address or FQDN of your Asterisk PBX.