A warning regarding vicidial and call compliance "teleb
Posted: Fri Jul 23, 2010 10:05 am
If you use "teleblock" from call compliance, your calls are auto-filtered at the ITSP level from local,state and federal DNC lists. Your ITSP will most likely return a 403 SIP Forbidden. It turns out that Vicidial has been interpreting this in vicidial_carrier_log as a dialstatus "congestion". We've verified that these leads have made their way into our recall logic as NA. We've paid 0.005 per lookup and simultaneously inadvertently have been recalling each lead up to 8 times. Resulting in several thousand dollars in overstated costs over the course of several months.
Here is the forbidden response we get from our ITSP when calls are teleblocked (Number is on DNC).
<--- SIP read from 69.94.226.XXX:5060 --->
SIP/2.0 403 Forbidden^M
Via: SIP/2.0/UDP 74.XXX.XX.XXX:5060;branch=z9hG4bK296266ea;rport=5060^M
From: "V0723094521000279289" <sip:XXX8@74.XXX.XX.XXX>;tag=as3b4e699c^M
To: <sip:1XXX@69.94.226.174;cpd=on>;tag=60340382-tdb1120402328^M
Call-ID: 50ca0b525659324840f23381381e5a80@74.XXX.XX.XXX^M
CSeq: 102 INVITE^M
Server: Sansay VSX 2.1^M
Content-Length: 0^M
Here is the entry from carrier_log.
select call_date,server_ip,lead_id,hangup_cause,dialstatus from vicidial_carrier_log where lead_id=280794;
+---------------------+---------------+---------+--------------+------------+
| call_date | server_ip | lead_id | hangup_cause | dialstatus |
+---------------------+---------------+---------+--------------+------------+
| 2010-07-13 15:21:31 | 192.168.1.236 | 280794 | 21 | CONGESTION |
| 2010-07-23 09:53:56 | 192.168.1.236 | 280794 | 21 | CONGESTION |
+---------------------+---------------+---------+--------------+------------+
Here is the entry from our vicidial_log showing that the 403 is ending up as a NA.
mysql> select call_date,status from vicidial_log where lead_id=280794;
+---------------------+--------+
| call_date | status |
+---------------------+--------+
| 2010-07-13 15:22:11 | NA |
| 2010-07-23 09:54:16 | NA |
+---------------------+--------+
Just a warning: If you use teleblock, ensure that you create a script to pull the congestions and update from NA to DNC or a Teleblock/DNC disposition.
Here is the forbidden response we get from our ITSP when calls are teleblocked (Number is on DNC).
<--- SIP read from 69.94.226.XXX:5060 --->
SIP/2.0 403 Forbidden^M
Via: SIP/2.0/UDP 74.XXX.XX.XXX:5060;branch=z9hG4bK296266ea;rport=5060^M
From: "V0723094521000279289" <sip:XXX8@74.XXX.XX.XXX>;tag=as3b4e699c^M
To: <sip:1XXX@69.94.226.174;cpd=on>;tag=60340382-tdb1120402328^M
Call-ID: 50ca0b525659324840f23381381e5a80@74.XXX.XX.XXX^M
CSeq: 102 INVITE^M
Server: Sansay VSX 2.1^M
Content-Length: 0^M
Here is the entry from carrier_log.
select call_date,server_ip,lead_id,hangup_cause,dialstatus from vicidial_carrier_log where lead_id=280794;
+---------------------+---------------+---------+--------------+------------+
| call_date | server_ip | lead_id | hangup_cause | dialstatus |
+---------------------+---------------+---------+--------------+------------+
| 2010-07-13 15:21:31 | 192.168.1.236 | 280794 | 21 | CONGESTION |
| 2010-07-23 09:53:56 | 192.168.1.236 | 280794 | 21 | CONGESTION |
+---------------------+---------------+---------+--------------+------------+
Here is the entry from our vicidial_log showing that the 403 is ending up as a NA.
mysql> select call_date,status from vicidial_log where lead_id=280794;
+---------------------+--------+
| call_date | status |
+---------------------+--------+
| 2010-07-13 15:22:11 | NA |
| 2010-07-23 09:54:16 | NA |
+---------------------+--------+
Just a warning: If you use teleblock, ensure that you create a script to pull the congestions and update from NA to DNC or a Teleblock/DNC disposition.