The SBC (Session Border Controller) is any network device that sends SIP INVITE messages to ClearIP. ClearIP uses the general term SBC to represent any SIP device, such as a softswitch, Private Branch eXchange (PBX) or SIP proxy. ClearIP only accepts SIP INVITEs from IP addresses that are configured as an SBC. Users may have multiple SBCs associated with their account. All other network traffic is refused by ClearIP with a SIP 403 Forbidden response.
Prerequisites
If the network of your SBC is configured with an access control list (e.g., firewall), please add the following subnets:
- 52.223.0.89/32
- 99.83.142.252/32
- 15.197.186.107/32
- 35.71.188.213/32
If the network of your SBC is not configured with an access control list, this step is unnecessary.
Setup
Click the Organization dropdown menu and select the SBCs option to display the SBC page. Click the Add button to fill out the form for adding SBCs.
The Name and IP Address fields are the only fields that are required to be filled for all new SBC entries. All other fields are set to an initial default value. Except for the IP address and Partition fields, all other field values can be updated at any time if needed. See below for more information on the various fields in the SBCs form.
NOTE: It can take up to 60 seconds for changes to the SBCs page to take effect.
Name
The human readable display name. it is reccommended that the SBC display name be a meaningful name that is easy to remember.
IP Address
This is the public IP address of the SIP device used to send SIP signaling to ClearIP.
Partition
The subdomain of sip.clearip.com. Leave this field blank to apply to any subdomain or sip.clearip.com.
The Partition feature can be used to create multiple SBCs within ClearIP without requiring multiple public IP addresses reserved for each SBC. Instead of sending all calls to sip.clearip.com, calls can be sent to different destinations of the form .sip.clearip.com where the can be any text. SBCs in ClearIP can be identified by a unique public IP address and partition pairing.
Here is an example of 2 SBCs that have been created. The SBCs have the same IP address with different partition values.
| Operator | Name | IP Address | Partition | Status | Comment |
|---|---|---|---|---|---|
| ABC Telco Inbound | Partition of SBC for INBOUND Calls | 1.1.1.1 | inbound | Active | |
| ABC Telco Outbound | Partition of SBC for OUTBOUND Calls | 1.1.1.1 | outbound | Active |
ClearIP checks for the partition in the SIP INVITE request URI.
INVITE sip:+18554742536@outbound.sip.clearip.com:5060 SIP/2.0
Via: SIP/2.0/TCP sip.clearip.com:5060
From: <sip:+14045266060@transnexus.com:5060>
To: <sip:+18554742536@outbound.sip.clearip.com:5060>
Call-ID: 123456
CSeq: 1 INVITE
Content-Length: 0
ClearIP checks for both the partition and SBC IP address to match an SBC to a call.
Status
If set to Inactive, ClearIP will return a 403 Forbidden immediately. If set to Block, ClearIP will return a 603 Decline immediately. The default value is Active.
No Fraud Detected Response Code
This is the response code to send when no fraud is detected. The default value is 503.
Most SBCs should use the SIP 503 code when no fraud is detected to allow route advance with some exceptions.
When ClearIP returns a SIP 503 response to certain SBCs, these SBCs tend to send multiple SIP INVITEs to ClearIP for each call attempt. When performing a DNS lookup and finding a list of multiple IP addresses, the SBCs send a SIP INVITE to each IP address in the list instead of choosing a single IP address to send the call to. This has the effect of inflating the call volume seen by ClearIP which can impact billing. When ClearIP returns the SIP 404 response, the SBC sends only a single SIP INVITE per call attempt which is the desired behavior.
SBCs that require a SIP 404 for No Fraud Detected Response Code:
- Metaswitch Perimeta SBC
- Oracle SBC where routing is performed by the SBC and not the switch
- Ribbon SWe SBC
- Sonus 5400 SBC
Additional configuration may be needed to enable route advance on a SIP 404 response if it is not the default behavior.
Routing
This field controls whether ClearIP uses the policies defined in the Routing menu for static or least cost routing. If set to No, ClearIP ignores any policies defined in the Routing menu. If set to Yes, ClearIP can return a SIP 302 response containing routes defined in the Routing menu. Default is set to No.
Include User Parameters in Routing Response
This field determines whether request URI user parameters will be included in the routing response. The default value is No.
If ClearIP is configured to return a SIP 302 for routing and the SIP INVITE contains a user parameter in the request URI that is required to be present in the redirect SIP INVITE, this field must be set to Yes.
Example SIP INVITE with cic User Parameter in Request URI:
INVITE sip:+185547425;cic=1234@sip.clearip.com:5060 SIP/2.0
Via: SIP/2.0/TCP sip.clearip.com:5060
From: <sip:+14045266060@transnexus.com:5060>
To: <sip:+18554742536@sip.clearip.com:5060>
Call-ID: 123456
CSeq: 1 INVITE
Content-Length: 0
Example SIP 302 Returning cic User Parameter in Contact Header when Field is Set to Yes:
SIP/2.0 302 Moved Temporarily
Via: SIP/2.0/TCP sip.clearip.com:5060
From: <sip:+14045266060@transnexus.com:5060>
To: <sip:+18554742536@sip.clearip.com:5060>
Contact: <sip:+18554742536;cic=0222@1.1.1.1>;q=0.99
Reason: SIP;cause=302;text="no-fraud-detected"
Call-ID: 123456
CSeq: 1 INVITE
Content-Length: 0
This ensures the cic parameter is included in the redirected SIP INVITE from the SBC to the external carrier.
By default, ClearIP only returns the called number in the Contact header without additional request URI user parameters in the SIP 302 response.
Return LRN In SIP Response
This field determines whether NPDI and RN parameters will be returned in the SIP response. The default value is No.
Example SIP 302 Response with LRN Returned in the Contact Header:
SIP/2.0 302 Moved Temporarily
Via: SIP/2.0/TCP sip.clearip.com:5060
From: <sip:+14045266060@transnexus.com:5060>
To: <sip:+18554742536@sip.clearip.com:5060>
Contact: <sip:+14047884802;npdi;rn=+14045679081@1.2.3.4:5060>;q=0.99
Reason: SIP;cause=302;text="no-fraud-detected"
Call-ID: 123456
CSeq: 1 INVITE
Content-Length: 0
In this example, a call is made to called number 14047884802. ClearIP performed an LRN lookup to determine the number has been ported to LRN 14045679081.
ClearIP always does an LRN lookup for each call and uses the LRN for static and least cost routing decisions. This field does not impact ClearIP routing or whether ClearIP performs an LRN lookup.
Return IDs in SIP Response
This field determines whether ClearIP IDs will be returned in the SIP response. The default value is No.
The IDs refer to the ClearIP ID values for the SIP Message, SBC, Service Provider, Group, and User for the call. These IDs can be used to reference the SIP Message, SBC, Service Provider, Group, and User using the ClearIP API.
Example SIP 302 Response with IDs Returned in X-Clearip-Id Header:
SIP/2.0 302 Moved Temporarily
Via: SIP/2.0/TCP sip.clearip.com:5060
From: <sip:+14045266060@transnexus.com:5060>
To: <sip:+18554742536@sip.clearip.com:5060>
X-Clearip-Id: 99999999-9999-4999-9999-999999999999;sbc=99999999-9999-4999-9999-999999999999;serviceProvider=99999999-9999-4999-9999-999999999999;group=99999999-9999-4999-9999-999999999999;user=99999999-9999-4999-9999-999999999999
Contact: <sip:+18554742536@sip.clearip.com:5060>;q=0.99
Reason: SIP;cause=302;text="no-fraud-detected"
Call-ID: 123456
CSeq: 1 INVITE
Content-Length: 0
From the example, the following IDs can be used with the ClearIP API:
SIP Message ID: 99999999-9999-4999-9999-999999999999
SBC ID: 99999999-9999-4999-9999-999999999999
Service Provider ID: 99999999-9999-4999-9999-999999999999
Group ID: 99999999-9999-4999-9999-999999999999
User ID: 99999999-9999-4999-9999-999999999999
Return Rates in SIP Response
This field determines whether billing and LCR rates will be returned in the SIP response. The default value is No.
ClearIP can return the LCR rate associated with each LCR destination within the SIP 302 response as parameters in the Contact header. If billing rates are configured, ClearIP returns the billing rate in the X-Billing-Rate header.
SIP/2.0 302 Moved Temporarily
Via: SIP/2.0/TCP sip.clearip.com:5060
From: <sip:+14045266060@transnexus.com:5060>
To: <sip:+18554742536@sip.clearip.com:5060>
X-Billing-Rate: 0.003
Contact: <sip:+18554742536@1.1.1.1>;q=0.99;rate=0.00032, <sip:+18554742536@2.2.2.2>;q=0.98;rate=0.0004
Reason: SIP;cause=302;text="no-fraud-detected"
Call-ID: 123456
CSeq: 1 INVITE
Content-Length: 0
In the example, ClearIP returns a list of 2 LCR routes. As the first route, ClearIP selects the carrier with IP address 1.1.1.1 using the uploaded LCR rate of $0.00032 per minute. For the second route, ClearIP selects the carrier with IP address 2.2.2.2 using LCR rate of $0.0004 per minute.
If a static route defined within the Inbound or Outbound Routes is applied to the call, ClearIP does not perform a LCR lookup and does not return an LCR rate in the SIP 302 response.
Return Reputation Score In SIP Response
This field determines whether the calling number reputation score will be returned in the SIP response. The default value is No.
ClearIP can return the calling number reputation in a X-Reputation-Score header in the SIP 302 response.
SIP/2.0 302 Moved Temporarily
Via: SIP/2.0/TCP sip.clearip.com:5060
From: <sip:+14045266060@transnexus.com:5060>
To: <sip:+18554742536@sip.clearip.com:5060>
X-Reputation-Score: 100
Contact: <sip:+18554742536@sip.clearip.com:5060>;q=0.99
Reason: SIP;cause=302;text="no-fraud-detected"
Call-ID: 123456
CSeq: 1 INVITE
Content-Length: 0
Return Verification Status In SIP Response
This field determines whether the verification status will be returned in the SIP response. The default value is No.
ClearIP can return the STI Verification Status in the SIP 302 response in the X-Verification-Status header.
SIP/2.0 302 Moved Temporarily
Via: SIP/2.0/TCP sip.clearip.com:5060
From: <sip:+14045266060@transnexus.com:5060>
To: <sip:+18554742536@sip.clearip.com:5060>
X-Verification-Status: successful
Contact: <sip:+18554742536@sip.clearip.com:5060>;q=0.99
Reason: SIP;cause=302;text="no-fraud-detected"
Call-ID: 123456
CSeq: 1 INVITE
Content-Length: 0
Possible values:
- successful
- invalid-token-signature
- certificate-chain-error
- certificate-error
- certificate-repository-error
- called-number-mismatch
- calling-number-mismatch
- invalid-token-typ
- invalid-token-ppt
- invalid-token-alg
- invalid-token-x5u
- invalid-token-dest
- invalid-token-orig
- invalid-token-iat
- invalid-token-origid
- invalid-token-attestation-indicator
- malformed-certificate-repository
- malformed-token
- invalid-parameter-ppt
- invalid-parameter-alg
- invalid-parameter-info
- malformed-identity-header
- no-identity-header
- no-verification-requested
Return Authentication Status In SIP Response
This field determines whether the authentication status will be returned in the SIP response. The default value is No.
ClearIP can return the STI Authentication Status in the SIP 302 response in the X-Authentication-Status header.
SIP/2.0 302 Moved Temporarily
Via: SIP/2.0/TCP sip.clearip.com:5060
From: <sip:+14045266060@transnexus.com:5060>
To: <sip:+18554742536@sip.clearip.com:5060>
Identity: eyJhbGciOiJFUzI1NiIsInBwdCI6InNoYWtlbiIsInR5cCI6InBhc3Nwb3J0IiwieDV1IjoiaHR0cHM6Ly9jZXJ0aWZpY2F0ZXMuY2xlYXJpcC5jb20vOTk5OTk5OTktOTk5OS00OTk5LTk5OTktOTk5OTk5OTk5OTk5LzAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwLnBlbSJ9.eyJhdHRlc3QiOiJBIiwiZGVzdCI6eyJ0biI6WyIxODU1NDc0MjUzNiJdfSwiaWF0IjoxNTc3ODM2ODAwLCJvcmlnIjp7InRuIjoiMTQwNDUyNjYwNjAifSwib3JpZ2lkIjoiOTk5OTk5OTktOTk5OS00OTk5LTk5OTktOTk5OTk5OTk5OTk5In0.abcdefghijklmnopqrstuvwzyzABCDEFGHIJKLMNOPQRSTUVWZYZ0123456789012345678901234567890123;info=<https://certificates.clearip.com/99999999-9999-4999-9999-999999999999/00000000000000000000000000000000.pem>;alg=ES256;ppt=shaken
X-Authentication-Status: successful
Contact: <sip:+18554742536@sip.clearip.com:5060>;q=0.99
Reason: SIP;cause=302;text="no-fraud-detected"
Call-ID: 123456
CSeq: 1 INVITE
Content-Length: 0
Possible values:
- successful
- blocked
- no-authority
- invalid-calling-number
- invalid-called-number
- ignored
- no-authentication-requested
CNAM Maximum Length
This field represents the maximum length of the caller display name to return. Longer values will be truncated to this length. The default value is 15.
CNAM Header
This is the header used to return the CNAM token. The default value is P-Asserted-Identity.
- P-Asserted-Identity:
SIP/2.0 302 Moved Temporarily
Via: SIP/2.0/TCP sip.clearip.com:5060
From: <sip:+14045266060@transnexus.com:5060>
To: <sip:+18554742536@sip.clearip.com:5060>
P-Asserted-Identity: "TransNexus" <sip:+14045266060@transnexus.com:5060>
Contact: <sip:+18554742536@sip.clearip.com:5060>;q=0.99
Reason: SIP;cause=302;text="no-fraud-detected"
Call-ID: 123456
CSeq: 1 INVITE
Content-Length: 0
- X-Asserted-Identity:
X-Asserted-Identity: "TRANSNEXUS" <sip:+14045266060@transnexus.com:5060>
- P-Asserted-Identity Embedded in Contact URI:
Contact: <sip:+18554742536@1.2.3.4:5060?P-Asserted-Identity=%22TRANSNEXUS%22%20%3Csip%3A14045266060%40transnexus.com%3A5060%3E>;q=0.99
The P-Asserted-Identity Embedded in Contact URI value is used to return CNAM for the Metaswitch Perimeta SBC, BroadWorks, and Oracle SBC.
- X-Asserted-Identity Embedded in Contact URI:
Contact: <sip:+18554742536@1.2.3.4:5060?X-Asserted-Identity=%22TRANSNEXUS%22%20%3Csip%3A14045266060%40transnexus.com%3A5060%3E>;q=0.99
- P-Asserted-Identity Embedded in Contact:
Contact: <sip:+18554742536@1.2.3.4:5060>;q=0.99?P-Asserted-Identity=%22TRANSNEXUS%22%20%3Csip%3A14045266060%40transnexus.com%3A5060%3E
The P-Asserted-Identity Embedded in Contact value can be used to return CNAM for the Sansay VSXi SBC.
- X-Asserted-Identity Embedded in Contact:
Contact: <sip:+18554742536@1.2.3.4:5060>;q=0.99?X-Asserted-Identity=%22TRANSNEXUS%22%20%3Csip%3A14045266060%40transnexus.com%3A5060%3E
Identity Header
This is the header used to return the Identity token. The default value is Identity.
- Identity:
SIP/2.0 302 Moved Temporarily
Via: SIP/2.0/TCP sip.clearip.com:5060
From: <sip:+14045266060@transnexus.com:5060>
To: <sip:+18554742536@sip.clearip.com:5060>
Identity: eyJhbGciOiJFUzI1NiIsInBwdCI6InNoYWtlbiIsInR5cCI6InBhc3Nwb3J0IiwieDV1IjoiaHR0cHM6Ly9jZXJ0aWZpY2F0ZXMuY2xlYXJpcC5jb20vOTk5OTk5OTktOTk5OS00OTk5LTk5OTktOTk5OTk5OTk5OTk5LzAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwLnBlbSJ9.eyJhdHRlc3QiOiJBIiwiZGVzdCI6eyJ0biI6WyIxODU1NDc0MjUzNiJdfSwiaWF0IjoxNTc3ODM2ODAwLCJvcmlnIjp7InRuIjoiMTQwNDUyNjYwNjAifSwib3JpZ2lkIjoiOTk5OTk5OTktOTk5OS00OTk5LTk5OTktOTk5OTk5OTk5OTk5In0.abcdefghijklmnopqrstuvwzyzABCDEFGHIJKLMNOPQRSTUVWZYZ0123456789012345678901234567890123;info=<https://certificates.clearip.com/99999999-9999-4999-9999-999999999999/00000000000000000000000000000000.pem>;alg=ES256;ppt=shaken
Contact: <sip:+18554742536@1.2.3.4:5060>;q=0.99
Reason: SIP;cause=302;text="no-fraud-detected"
Call-ID: 123456
CSeq: 1 INVITE
Content-Length: 0
The default Identity value can be used for ClearIP to return a standard Identity header. This value should be used for most platforms including netsapiens unless specified below.
- X-Identity:
X-Identity: eyJhbGciOiJFUzI1NiIsInBwdCI6InNoYWtlbiIsInR5cCI6InBhc3Nwb3J0IiwieDV1IjoiaHR0cHM6Ly9jZXJ0aWZpY2F0ZXMuY2xlYXJpcC5jb20vOTk5OTk5OTktOTk5OS00OTk5LTk5OTktOTk5OTk5OTk5OTk5LzAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwLnBlbSJ9.eyJhdHRlc3QiOiJBIiwiZGVzdCI6eyJ0biI6WyIxODU1NDc0MjUzNiJdfSwiaWF0IjoxNTc3ODM2ODAwLCJvcmlnIjp7InRuIjoiMTQwNDUyNjYwNjAifSwib3JpZ2lkIjoiOTk5OTk5OTktOTk5OS00OTk5LTk5OTktOTk5OTk5OTk5OTk5In0.abcdefghijklmnopqrstuvwzyzABCDEFGHIJKLMNOPQRSTUVWZYZ0123456789012345678901234567890123;info=<https://certificates.clearip.com/99999999-9999-4999-9999-999999999999/00000000000000000000000000000000.pem>;alg=ES256;ppt=shaken
The X-Identity value can be used to return the Identity header for the ClearIP In-line proxy.
- Identity Embedded in Contact URI:
Contact: <sip:+18554742536@1.2.3.4:5060?Identity=eyJhbGciOiJFUzI1NiIsInBwdCI6InNoYWtlbiIsInR5cCI6InBhc3Nwb3J0IiwieDV1IjoiaHR0cHM6Ly9jZXJ0aWZpY2F0ZXMuY2xlYXJpcC5jb20vOTk5OTk5OTktOTk5OS00OTk5LTk5OTktOTk5OTk5OTk5OTk5LzAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwLnBlbSJ9.eyJhdHRlc3QiOiJBIiwiZGVzdCI6eyJ0biI6WyIxODU1NDc0MjUzNiJdfSwiaWF0IjoxNTc3ODM2ODAwLCJvcmlnIjp7InRuIjoiMTQwNDUyNjYwNjAifSwib3JpZ2lkIjoiOTk5OTk5OTktOTk5OS00OTk5LTk5OTktOTk5OTk5OTk5OTk5In0.abcdefghijklmnopqrstuvwzyzABCDEFGHIJKLMNOPQRSTUVWZYZ0123456789012345678901234567890123%3Binfo%3D%3Chttps%3A%2F%2Fcertificates.clearip.com%2F99999999-9999-4999-9999-999999999999%2F00000000000000000000000000000000.pem%3E%3Balg%3DES256%3Bppt%3Dshaken>;q=0.99
The Identity Embedded in Contact URI value can be used to return the Identity header for the Metaswitch Perimeta SBC, BroadWorks, and Oracle SBC if using the embedded header mechanism.
- X-Identity Embedded in Contact URI:
Contact: <sip:+18554742536@1.2.3.4:5060?X-Identity=eyJhbGciOiJFUzI1NiIsInBwdCI6InNoYWtlbiIsInR5cCI6InBhc3Nwb3J0IiwieDV1IjoiaHR0cHM6Ly9jZXJ0aWZpY2F0ZXMuY2xlYXJpcC5jb20vOTk5OTk5OTktOTk5OS00OTk5LTk5OTktOTk5OTk5OTk5OTk5LzAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwLnBlbSJ9.eyJhdHRlc3QiOiJBIiwiZGVzdCI6eyJ0biI6WyIxODU1NDc0MjUzNiJdfSwiaWF0IjoxNTc3ODM2ODAwLCJvcmlnIjp7InRuIjoiMTQwNDUyNjYwNjAifSwib3JpZ2lkIjoiOTk5OTk5OTktOTk5OS00OTk5LTk5OTktOTk5OTk5OTk5OTk5In0.abcdefghijklmnopqrstuvwzyzABCDEFGHIJKLMNOPQRSTUVWZYZ0123456789012345678901234567890123%3Binfo%3D%3Chttps%3A%2F%2Fcertificates.clearip.com%2F99999999-9999-4999-9999-999999999999%2F00000000000000000000000000000000.pem%3E%3Balg%3DES256%3Bppt%3Dshaken>;q=0.99
- Identity Embedded in Contact:
Contact: <sip:+18554742536@1.2.3.4:5060>;q=0.99?Identity=eyJhbGciOiJFUzI1NiIsInBwdCI6InNoYWtlbiIsInR5cCI6InBhc3Nwb3J0IiwieDV1IjoiaHR0cHM6Ly9jZXJ0aWZpY2F0ZXMuY2xlYXJpcC5jb20vOTk5OTk5OTktOTk5OS00OTk5LTk5OTktOTk5OTk5OTk5OTk5LzAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwLnBlbSJ9.eyJhdHRlc3QiOiJBIiwiZGVzdCI6eyJ0biI6WyIxODU1NDc0MjUzNiJdfSwiaWF0IjoxNTc3ODM2ODAwLCJvcmlnIjp7InRuIjoiMTQwNDUyNjYwNjAifSwib3JpZ2lkIjoiOTk5OTk5OTktOTk5OS00OTk5LTk5OTktOTk5OTk5OTk5OTk5In0.abcdefghijklmnopqrstuvwzyzABCDEFGHIJKLMNOPQRSTUVWZYZ0123456789012345678901234567890123%3Binfo%3D%3Chttps%3A%2F%2Fcertificates.clearip.com%2F99999999-9999-4999-9999-999999999999%2F00000000000000000000000000000000.pem%3E%3Balg%3DES256%3Bppt%3Dshaken
- X-Identity Embedded in Contact:
Contact: <sip:+18554742536@1.2.3.4:5060>;q=0.99?X-Identity=eyJhbGciOiJFUzI1NiIsInBwdCI6InNoYWtlbiIsInR5cCI6InBhc3Nwb3J0IiwieDV1IjoiaHR0cHM6Ly9jZXJ0aWZpY2F0ZXMuY2xlYXJpcC5jb20vOTk5OTk5OTktOTk5OS00OTk5LTk5OTktOTk5OTk5OTk5OTk5LzAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwLnBlbSJ9.eyJhdHRlc3QiOiJBIiwiZGVzdCI6eyJ0biI6WyIxODU1NDc0MjUzNiJdfSwiaWF0IjoxNTc3ODM2ODAwLCJvcmlnIjp7InRuIjoiMTQwNDUyNjYwNjAifSwib3JpZ2lkIjoiOTk5OTk5OTktOTk5OS00OTk5LTk5OTktOTk5OTk5OTk5OTk5In0.abcdefghijklmnopqrstuvwzyzABCDEFGHIJKLMNOPQRSTUVWZYZ0123456789012345678901234567890123%3Binfo%3D%3Chttps%3A%2F%2Fcertificates.clearip.com%2F99999999-9999-4999-9999-999999999999%2F00000000000000000000000000000000.pem%3E%3Balg%3DES256%3Bppt%3Dshaken
Local Routing Algorithm
This is the algorithm used to determine if a call is local. The default value is Intra Rate Center.
Diversion Destination
This is the destination diverted calls will be sent to. The default value is captcha.clearip.com:5060;transport=tcp.
A diversion destination can be configured by adding an IP address, FQDN, or trunk group using the same formats as used for ClearIP static and least cost routing.
Example SIP 302 Redirecting Call to ClearIP CAPTCHA:
SIP/2.0 302 Moved Temporarily
Via: SIP/2.0/TCP sip.clearip.com:5060
From: <sip:+14045266060@transnexus.com:5060>
To: <sip:+18554742536@sip.clearip.com:5060>
Contact: <sip:+18324108099@captcha.clearip.com:5060;transport=tcp;id=99999999-9999-4999-9999-999999999999>;q=0.99
Reason: SIP;cause=302;text="diverted"
Call-ID: 123456
CSeq: 1 INVITE
Content-Length: 0
Static Destination
This is the static destination all calls will be sent to.
If a static destination is configured, ClearIP returns the destination within the SIP 302 Contact header. If static or least cost routing are configured, ClearIP returns the static or least cost routes if available instead of the static route.
This can be used to configure ClearIP to return the internal IP address of the switch in the SIP 302 response sent to the SBC to implement a hairpin call flow. For the hairpin scenario, the SBC must be configured to recurse on a SIP 302 to redirect the SIP INVITE to the switch’s internal signaling IP address.
Example SIP 302 with Static Destination Set to Internal IP Address 192.168.5.5:
SIP/2.0 302 Moved Temporarily
Via: SIP/2.0/TCP sip.clearip.com:5060
From: <sip:+14045266060@transnexus.com:5060>
To: <sip:+18554742536@sip.clearip.com:5060>
Contact: <sip:+18554742536@192.168.5.5>;q=0.99
Reason: SIP;cause=302;text="no-fraud-detected"
Call-ID: 123456
CSeq: 1 INVITE
Content-Length: 0
Minimum Calling Number Length
This is the minimum length a calling number must be to be processed by ClearIP. If the calling number is shorter than this length, ClearIP will return a 484 Address Incomplete response immediately. Set this to 0 to have no minimum length. The default value is 0.
This can be used to prevent local calls and calls to extension numbers from being processed. If all calls should be processed by ClearIP, set minimum length to zero.
Minimum Called Number Length
This is the minimum length a called number must be to be processed by ClearIP. If the called number is shorter than this length, ClearIP will return a 484 Address Incomplete response immediately. Set this to 0 to have no minimum length. The default value is 0.
This can be used to prevent local calls and calls to extension numbers from being processed. If all calls should be processed by ClearIP, set minimum length to zero.