ClearIP integrates with SIP devices using standard SIP (Session Initiation Protocol) signaling. The SIP device can be any device that can be configured with a SIP trunk such as a Session Border Controller (SBC), a softswitch, a SIP enabled PBX (Private Branch eXchange), a SIP to TDM (Time Division Multiplexing) gateway, or a proxy. The SIP device must be able to connect to ClearIP using SIP over TCP or TLS and not UDP.
To connect to ClearIP, you would create a SIP trunk on your SIP device pointing to ClearIP and put the ClearIP SIP trunk at the top of your routing table. Your network will send SIP INVITEs to ClearIP as if it were a normal SIP trunk.
ClearIP can process both outbound calls (provider-to-PSTN) and inbound calls (PSTN-to-provider). You can view the Organization section to learn how ClearIP settings must be configured to distinguish outbound and inbound call directions.
For outbound calls, ClearIP can perform any of these services:
- STIR/SHAKEN Authentication
- Robocall Mitigation
- Blacklisting
- Toll Fraud Prevention
- Static Routing and Least Cost Routing
For inbound calls, ClearIP can perform any of these services:
- STIR/SHAKEN Verification
- Robocall Prevention
- Blacklisting
- CNAM Lookups
- DID Routing
Switch and SBC Integration Guides
| Platform | ClearIP Services Enabled | Notes |
|---|---|---|
| AudioCodes | STIR/SHAKEN | |
| Cisco CUBE | Inbound Robocall and TDoS Prevention | |
| Metaswitch CFS and Perimeta | Outbound Robocall Mitigation, Toll Fraud Prevention, Routing. Does not support STIR/SHAKEN Authentication | Compatible with Metaswitch 8.3.11 SU 39 and higher |
| Metaswitch CFS and Perimeta | Inbound Robocall Blocking. Does not support CNAM integration | Requires MetaView 9.3.20 SU 29 or higher |
| Netsapiens | Enables all services for outbound and inbound calls | Core Module must be v41.2.2 or higher |
| Oracle SBC | Toll Fraud, Routing, Robocall Mitigation | |
| Oracle SBC | STIR/SHAKEN | Must be implemented after first Oracle SBC guide above |
| TelcoBridges ProSBC | Outbound Robocall Mitigation, STIR/SHAKEN Authentication, Toll Fraud Prevention | Requires ProSBC 3.0.90 or higher |
| TelcoBridges ProSBC | Inbound Robocall Prevention, CNAM, STIR/SHAKEN Verification | Requires ProSBC 3.0.90 or higher |
If your switch or SBC is not listed here, then please contact TransNexus for direct assistance at https://tickets.transnexus.com/
ClearIP Proxy Options
Most switch and SBC platforms can be configured to support the required integration with ClearIP. Some switch and SBC platforms may have limited capabilities and not be able to support the required integration on their own. For these platforms, you have the option to install a ClearIP proxy.
TLS Proxy
For users that do not have a SIP device that supports TCP or TLS available, ClearIP offers a TLS Proxy free of charge to assist with the integration.
In-line Proxy
If your SIP device does not support any of the following: 1) blocking calls on SIP 603, 2) routing calls on SIP 302 Contact header, or 3) copying Identity header or P-Asserted-Identity header from SIP 302 message and inserting the headers into a redirected SIP Invite, then ClearIP offers an In-line Proxy free of charge to assist with the integration.