Difference between revisions of "NetBorder"
(→Configuration) |
(→Test your settings) |
||
Line 71: | Line 71: | ||
=== Test your settings === |
=== Test your settings === |
||
− | Make a call with the carrier settings. |
+ | Make a call with the carrier settings. For instance, with the example carrier shown above, change your "Dial Prefix" in your campaign to "7". |
− | Enter into the Vicidial user interface, and test the call. |
+ | Enter into the Vicidial user interface, and test the call. |
− | You can also connect to the system with a standard |
+ | You can also connect to the system with a standard agent phone. For instance, with the example carrier shown above, dial 71 + phone number from an agent phone. |
− | *Be aware of the pause while the Answering Machine Detection is working. |
+ | *Be aware of the pause after answering while the Answering Machine Detection is working. |
Revision as of 20:22, 25 September 2012
Here you will find installation instructions for the installation and configuration of Sangoma's Netborder Call Analyzer. This system was set up and tested on a system containing FreePBX and CentOS. As of now it is not supported by other Linux operating systems. FreePBX was not used during the testing of this software. Calls were made directly from vicidial through Netborder and out to the carrier.
For more detailed instructions please refer to the User guide located here:
http://www.sangoma.com/products/call_center_software/netborder_call_analyzer/download.html
Installation
Download NetBorderCallAnalyzerSetup2.<version>.<arch>.rpm to this directory. Linux_2.0.3 happens to be the version that was used in our installation.
cd /usr/src rpm -i NetBorderCallAnalyzerSetup2.xLinux_2.0.3.rpm
--This will install the Netborder software to /opt/Sangoma_NetBorderCallAnalyzer. --
Start Netborder
service netborder-call-analyzer start
In the event the service doesn't start view the messages log file for information
/var/log/messages
Start the Service automatically on startup/reboot
chkconfig netborder-call-analyzer on
Configuration
Since Netborder is a proxy service, the port for the proxy server must match the port for the final call server. However "outbondproxyport=" value is ignored in asterisk 1.4.39 (bug). If Netborder is running on port 5062, then the "carrier" must also be listening on port 5062. if the carrier is on 5060, then the port for netborder must be changed to match, as follows:
/opt/Sangoma_NetBorderCallAnalyzer/config
Add your Vicidial Server IP to these two files
nano +9 call-analyzer-engine.properties nano +9 call-analyzer-service.properties
Add your outbound Carrier IP here:
nano +39 CallAnalyzerAsOutboundProxy.call-properties
Should look like this entry here:
# Optional: set outbound proxy host:post to use to reach the callee # Applies to call with CPA active (cpd=on) or not common.b2bua.outbound.proxy.host=my.carrier.net common.b2bua.outbound.proxy.port=5060
Edit your Vicidial Carrier. We used a Paraxip entry, as follows:
[carriername] disallow=all allow=ulaw type=peer host=carriername/IP port=5062 insecure=port,invite outboundproxy=vicidialhostIP outboundproxyport=5062 nat=yes DIAL7TRUNK = SIP/carriername Dialplan Entry: exten => _71NXXNXXXXXX,1,AGI exten => _71NXXNXXXXXX,2,Dial(${DIAL7TRUNK}/${EXTEN:1},,tTor) exten => _71NXXNXXXXXX,3,Hangup
Test your settings
Make a call with the carrier settings. For instance, with the example carrier shown above, change your "Dial Prefix" in your campaign to "7".
Enter into the Vicidial user interface, and test the call.
You can also connect to the system with a standard agent phone. For instance, with the example carrier shown above, dial 71 + phone number from an agent phone.
- Be aware of the pause after answering while the Answering Machine Detection is working.