NetBorder Call Analyzer Release Update
This page is used to update the documentation as provided with the latest NetBorder Call Analyzer release.
Latest NetBorder Call Analyzer release is 1.0.10
Updates to NetBorder Call Analyzer 1.0.X documentation
- Release Notes:
- Important: AMD processors are not supported due to Intel-specific optimizations. Symptoms of an installation on an AMD processor: installation goes thru with error but the NetBorder Session Controller windows service is not installed.
Licensing in version 1.0.X is done based on the number of concurrent calls handled by the Session Controller service (port 5062), which stays in the call path even when the call analysis (cdp) segment of the call is over, for example when the agent and customer are talking together. Therefore the provided 1-channel evaluation license will only allow for one agent to participate in a campaign at a time.
Licensing in 1.0.8 will be based on the number of concurrent calls in active call analysis (predictive call attempts).
- The "Making a call using the B2BUA scenario" section on p.39 will not work as described using the default configuration of Call Analyzer 1.0.X. The outcome of trying it using the default configuration will be the following error shown in the Windows Event Viewer: Need to set sip.request.relay.server.address and sip.request.relay.server.port scenario parameters when using 'redirect' NetBorder scenario. You can skip the test in "Making a call using the B2BUA scenario" section and jump directly to "Making a call with CPA" on p.42.
In the "Values for ‘CPD-Result’ Header" on p.50, it should be added to the "Reject" outcome description that is it also returned in the case of the customer hanging-up the phone before the CPA analysis is over. The SIP "603 Decline" response code will be used for that condition .
"Configuring NetBorder to use a relay server" on p.59 documents that the B2BUA scenario will be used if no CPA is requested in the incoming call. That is not true in NetBorder Call Analyzer 1.0.X: the "redirect" scenario will be used in that case so that the caller will be redirected to the relay server so that Call Analyzer won't be tied into the call. See below for a guide on what needs to be configured base on the architecture used.
NetBorder Call Analyzer 1.0.X quick configuration guide
NetBorder Call Analyzer is based on a flexible scripting framework that can adapt to multiple deployment scenarios. The most important aspects of the deployment is whether the Call Analyzer can be used as an outbound proxy by the SIP user agent(s) placing the predictive calls (see network diagrams on p.58 and 59 of the CPA User's Guide), whether non-CPA calls will need to be routed through the Call Analyzer and what treatment should be done to those non-CPA calls if it's the case.
| Used as Outbound Proxy | May be destination of non-CPA calls | Treatment of Non-CPA calls | Initial Request Handler to use (paraxip.netborder.initialRequestHandler in $NETBORDER/config/sip-hub.properties) | Changes to be made in Initial Request Handler configuration ($NETBORDER/python-scripts/user/) | |
| 1 | Yes | Yes | B2BUA (Redirect not supported) | CpaFollowingRequestParam | Change SipCallEngineSMCall_redirect to SipCallEngineSMCall_b2bua in InitialRequestHandlerBase.py |
| 2 | Yes | No | N/A | CpaAlwaysActive | None |
| 3 | No | Yes | Redirect | CpaFollowingRequestParam |
sip.request.relay.server.address and port must be set in InitialRequestHandlerBase.py and InitialRequestHandlerCpaFollowingRequestParam.py |
| 4 | No | Yes | B2BUA |
CpaFollowingRequestParam |
Change SipCallEngineSMCall_redirect to SipCallEngineSMCall_b2bua in InitialRequestHandlerBase.py |
| 5 | No | No | N/A | CpaAlwaysActive | sip.request.relay.server.address and port must be set in CpaAlwaysActive.py |
NOTES
- The default configuration for NetBorder Call Analyzer 1.0.X is configuration 3.
- A restart of the Paraxip NetBorder Session Controller Windows service is needed to activate changes.
- Configuration 2 (used as Outbound proxy, for CPA calls only) is recommended if the SIP trunk configuration of the software used to place predictive calls permits it (ex Asterisk). Use configuration 3 for deployments with Genesys SIP Server.
