Frequently asked questions

An Operator SMSC (Short Message Service Centre) is the network element that receives, stores, routes and delivers SMS on behalf of a mobile operator. It terminates SS7/MAP signaling with the MSC and HLR, connects to applications over SMPP or HTTP, and manages retries when subscribers are unreachable.

An Operator SMSC switches messages natively in the operator core using SS7/MAP, SIGTRAN and IMS, including HLR interrogation and store-and-forward. An SMPP gateway, such as the Guardivia Enterprise SMPP SMSC Gateway, manages application and aggregator accounts and routes their traffic toward upstream SMSCs; it does not itself terminate operator signaling.

Yes. The SS7/SIGTRAN stack, the SMPP and HTTP gateway and the SIP/IMS interface are all active in a single instance, so MAP subscribers, applications and IMS subscribers are served together.

Yes. Integration uses standard MAP operations over SIGTRAN. Where an operator's HLR or STP has implementation-specific behaviour, the QoS Engineering Team adapts the interface during laboratory validation.

Software-only on Linux, on bare metal or virtual machines, in your data centre or colocation facility, with cloud or hybrid options where validated. Nodes can be paired for high availability and replicated geographically where supported.

Releases are controlled and regression-tested by the QoS Engineering Team, then applied under change management. Support is delivered under agreed SLAs with direct access to the engineers who develop the platform.

No. The suite is a portfolio of signaling, subscriber-management, service-control, interworking, Diameter and roaming modules. The Guardivia Operator SMSC is one component that integrates with it.

Yes. Every module is deployable independently and exposes standard interfaces, so an HLR/HSS/UDM can serve a third-party MSC, MME or IMS core.

No. The IP-SM-GW interworks IMS SIP MESSAGE traffic (VoLTE/VoNR SMS) with MAP and SMPP domains. OTT application messages are outside its scope.

Any OCS, PCRF or charging system that implements the standard 3GPP Diameter interfaces (Gy, Gx, Gz, Ro, Rf, S9). Interoperability is validated per vendor during laboratory testing.

Yes. Because the suite is developed in house, the QoS Engineering Team creates and maintains custom integrations for documented legacy or proprietary interfaces without external vendor dependency.

Guardivia supplies HSS/UDM and SMSC components and provides consultancy and integration across S1AP, NAS, GTP, NGAP, PFCP and the HTTP/2 service-based architecture. RAN and packet-core functions are integrated, not supplied.

Yes. Hawk inspects SS7/SIGTRAN SMS signaling and passes content to the inspection layer; Dolphin and Shark inspect SMPP/ESME traffic directly. Both domains share one policy environment.

Yes. The firewall sits in front of any SMSC over MAP or SMPP. It is also pre-integrated with the Guardivia Operator SMSC.

The platform starts in monitoring and learning mode, builds baselines, then proposes classifications, rules and thresholds. An AI operational coworker issues daily recommendations early on, typically moving to weekly as traffic stabilises. An authorised engineer reviews and confirms every enforcement change.

According to policy they are dropped or quarantined with full reason codes, dimensions and CDRs for analyst review, reporting and forensic evidence.

This product's SS7 scope is SMS signaling. Broader SS7 category screening is addressed through the Core Network Suite STP platform or a separately scoped engagement.

It separates A2P from P2P, enforces sender-ID, aggregator and commercial-agreement registries, redirects unauthorised A2P to billable routes, generates CDRs and reconciles traffic against invoices.

No. The Enterprise SMPP SMSC Gateway manages application customers and routes their traffic to upstream SMSCs; the Operator SMSC is the network-side message centre with SS7/MAP and IMS signaling.

Operators filter messages by user, message-ID range, date range, country, operator, error or status, select a target SMSC and submit; the gateway reprocesses the selection.

Yes. A performance alert can be configured with a delivery-percentage threshold, minimum submissions and window; when breached it notifies by email, SMS or URL and can hold traffic until reviewed.

It counts OTP-like messages per source within a window and compares the share sent to distinct destinations against a threshold; sources below the threshold are blocked for a configurable period.

Yes. Admin (reseller) accounts manage their own users, routing and reports within a multi-tenant environment.

Yes. Because the gateway is developed in house, routing criteria, report layouts and alert channels can be extended by the QoS Engineering Team.

A verification method in which a service places a call to the user's number and terminates it before answer; the application reads the incoming caller ID as the verification code. It displaces billable SMS OTPs and appears in the network as bursts of unanswered short calls.

Voice CDRs at minimum. SIP or signaling events improve timeliness and enrichment where they can be provided.

By clustering near-zero-duration calls from rotating or sequential international caller IDs to many distinct subscribers, outside baseline behaviour, and scoring the cluster as a campaign.

Yes. When deployed with the Guardivia SMS Firewall, voice events are correlated with SMS OTP observations to identify FlashCall authentication patterns.

Guardivia's voice-security component or an integrated third-party voice firewall or SBC, through the enforcement interface, where technically supported.

Yes. The testing application reports the received sender ID and content, and the validation engine compares them with the submitted values, along with encoding, parts, URLs and message-centre information where exposed.

No. It is a strong indicator. The verdict correlates it with route, GT, CDR, SMSC, operator and device evidence before labelling the route.

The originating Global Title, the exact SMSC path and the interconnect identity. Those require network-side CDRs, traces or signaling records, which the platform can import for correlation.

Confirmed findings can support firewall blacklist and sender-ID policy updates, but human confirmation is available before a test result changes production rules.

No. It is a telecom route-testing platform using trap mobile numbers, real SIM cards and dedicated devices on live operator networks.

Yes. Partner and distributed-device testing is supported, with device registration, secure authentication and remote configuration.