Integration capability
Integrations created, modified and maintained internally
Guardivia does not wait for an external product vendor to add an interface. The QoS Engineering Team owns every integration in this catalogue, and the tier of each one is stated plainly.
How does Guardivia handle integrations?
Guardivia classifies every integration as native (inside the product), prebuilt connector (adapted to your formats), standards-based (validated per vendor in the laboratory) or custom (developed by the in-house QoS Engineering Team against documented interfaces). Categories span SS7/MAP, SIGTRAN, SMPP/SMPPS, SIP/IMS, Diameter, HTTP/REST, webhooks, HLR/HSS/UDM, STP, SMSC, DRA, OCS/PCRF interfaces, OSS/BSS, billing, CDR, NOC/ENM, SNMP, SIEM, monitoring, sender-ID registries, MNP databases, partner APIs and legacy operator interfaces.
Native integration
Implemented within the Guardivia product and maintained as part of it.
Prebuilt connector
An existing Guardivia connector adapted to your formats during deployment.
Standards-based integration
Interoperates with any system implementing the referenced standard; validated per vendor in the laboratory.
Custom integration available
Developed and maintained by the in-house QoS Engineering Team against documented interfaces.
Catalogue
Integration categories
| Category | Tier | Notes |
|---|---|---|
| SS7 and MAP | Native integration | Operator SMSC, Core Network Suite, SMS Firewall (Hawk) |
| SIGTRAN, SCTP and M3UA | Native integration | All signaling products |
| SMPP and SMPPS | Native integration | SMSC, Enterprise Gateway, Firewall (Dolphin and Shark) |
| SIP and IMS | Native integration | Operator SMSC, IP-SM-GW |
| Diameter | Native integration | Diameter and DRA platform, HSS, IP-SM-GW charging |
| HTTP and REST APIs | Native integration | Provisioning, submission, reporting across all products |
| Webhooks | Native integration | Alerts, DLR callbacks, test results |
| HLR, HSS and UDM | Standards-based integration | MAP, Diameter S6a/S6d, HTTP/2 Nudm; Guardivia's own HLR/HSS/UDM is native |
| STP | Standards-based integration | M3UA associations to any STP; Guardivia STP is native |
| SMSC (third party) | Standards-based integration | SMPP or MAP toward existing SMSCs |
| DRA (third party) | Standards-based integration | Diameter peering |
| OCS and PCRF interfaces | Standards-based integration | Gy, Gx, Gz, Ro, Rf, S9; the OCS/PCRF itself is third party |
| OSS and BSS | Prebuilt connector | Provisioning, CDR export and reconciliation in agreed formats |
| Billing systems | Prebuilt connector | CDR mediation feeds |
| CDR platforms | Prebuilt connector | Voice and SMS CDR ingestion and export |
| NOC and ENM platforms | Standards-based integration | SNMP, syslog, webhooks |
| SNMP and MIB integration | Native integration | Traps and MIBs shipped with products |
| SIEM platforms | Standards-based integration | Security event export |
| Monitoring and alerting systems | Standards-based integration | Email, SMS, webhook, SNMP |
| Sender-ID registries | Custom integration available | Where the registry exposes a documented interface |
| MNP databases | Standards-based integration | Standard query interfaces; custom where required |
| Partner and aggregator APIs | Custom integration available | Route testing, reconciliation and onboarding |
| Customer-specific northbound interfaces | Custom integration available | Developed and maintained by the QoS Engineering Team |
| Legacy and proprietary operator interfaces | Custom integration available | Where technically documented |
In-house engineering advantage
Why integrations move faster at Guardivia
Guardivia develops and controls its telecom platforms internally, from protocol processing and security intelligence to dashboards, integrations and operational tools. This direct ownership enables faster customisation, accountable delivery, stable releases and SLA-backed support without dependency on outsourced proprietary product vendors.
Can Guardivia build a custom operator integration?
Yes. Because all products are developed in house, the QoS Engineering Team creates, modifies and maintains integrations against documented interfaces without waiting for an external product vendor.
Does every integration already exist?
No. The catalogue distinguishes native integrations, prebuilt connectors, standards-based integrations validated per vendor, and custom integrations available through in-house engineering.
Can Guardivia integrate with an existing SMSC?
Yes. The SMS Firewall and Enterprise SMPP Gateway connect to third-party SMSCs over SMPP or MAP; the Operator SMSC can coexist with or replace them.
See it running on your traffic profile.
Talk to the engineers who build the platform. Demos use your protocols, your integration points and your policy questions.