ClearIP facilitates compliance with the FCC 603+ regulation by providing callers with a means of requesting redress for calls blocked based on an analytics program. After validation, such redress requests will be available to operators for review in ClearIP under Analytics/Redress Requests.
Date Selection
As with other ClearIP analytics functions, the top-left of the Redress Requests screen provides options for date/time range selection. (See date/time range selection for more information.) The default initial view shows data for a rolling hour. The redress request timestamp is used for the data selection filter. NOTE: The redress request timestamp is the time the request was submitted.
Reviewing Redress Requests
Redress Requests are required to include a valid SIP Message ID. You can compare the information in the Redress Request to the information in the associated SIP Messages by clicking on the “View” link on the far right side of the table.
Marking Redress Requests
Individual Redress Requests can be marked as “Redressed” or “Rejected” by selecting the individual row in the table, and clicking on the “Update” button. A popup will display with two fields that the user can modify:
- Status - The status can be set to “Pending”, “Rejected”, or “Redressed.”
- Comment - The comment can be used to save any other extra information associated with marking the Redress Request.
Notifications
Redress Request Notifications allow ClearIP Operators to configure how they are notified of new redress requests. Notifications can be configured on the Configuration/Redress Request Notifications page. Only one notification per operator may be configured.
Notifications will be sent if one or more redress requests are received for the given operator since that last notification message was triggered. The first notification sent after a notification policy is created or enabled may be triggered by a redress request that occurred in the past. Subsequent notifications will only be sent if a new redress request is received after the previous messages was triggered. A subsequent email will not be sent until the policy’s frequency (hourly, daily or weekly) has elapsed. NOTE: There may be a delay between the time an email is triggered and when it is received.
The frequency is the minimum time between notification emails. The actual time between notifications could be longer. Notification emails are not sent until a redress request is received.
SIP 603+ Response
603+ (603 Network Blocked) responses are used to provide callers a means of seeking redress for calls blocked based on any analytics program.
A 603+ response, as defined by ATIS-1000099, will return “Network Blocked” in the status line, rather than the SIP 603 default Reason Phrase “Decline”. In addition, the SIP message Reason header will be populated with a redress URL and an associated ID. The web form hosted at the provided URL will enable callers to submit a redress request to the operator via ClearIP. The caller must include the provided ID in the redress request. If the redress request maps to a valid ClearIP SIP message, then the redress request will appear in ClearIP on the Analytics/Redress Requests page.
Example SIP 603 Network Blocked (603+) message from ClearIP:
SIP/2.0 603 Network Blocked
Via: SIP/2.0/TCP sip.clearip.com:5060
From: <sip:+14045266060@transnexus.com:5060>
To: <sip:+18554742536@sip.clearip.com:5060>
Reason: SIP;cause=603;text="v=analytics1;url=https://redress.example.com/;id=01234567-89ab-cdef0-1234-56789abcdef0";location=RLN
Call-ID: 123456
CSeq: 1 INVITE
Content-Length: 0
Redressable Call Blocking
ClearIP will send a 603+ response when a call is blocked for the following reasons:
NOTE: The call’s SBC must have 603 Plus enabled in order for a 603+ response to be sent. Otherwise, a standard 603 Decline response will be sent.
Submitting Redress Requests
Redress requests are only allowed for calls that receive 603+ (Network Blocked) response from ClearIP. In order to submit a redress request, the user must navigate to the URL provided in the SIP 603+ responses’s Reason header (see the SIP 603+ Response section on this page for an example). Upon navigating to the provided URL, the user will be presented with a form which must be completed in its entirety. All fields are required. The ID entered on the form must match the id provided in the Reason header of the SIP response. After the form is submitted, if the submission passes basic validation, a “success” message will be returned.
Next, ClearIP will verify that the provided ID matches a ClearIP SIP message that returned 603 Network Blocked. If a matching SIP message is not found, the request is silently discarded. After all of these validation checks are complete, the redress request will be made available to the operator associated with the call. If a redress request notification is configured for the operator, then a notification email will be sent according to the notification’s configuration.
NOTE: Only one redress request per SIP message may be submitted. Subsequent redress requests for the same SIP message will be silently discarded.