Operators, MVNOs & network integrators

Connect established services to the next network change.

Plan voice interconnection, SMS and interactive USSD services together with the signaling and subscriber systems they depend on. Choose the functions you need for a service introduction or a subsystem replacement.

Voice & Messaging Modernization — integration viewNetwork view
Mobile & voice networks
Messaging applications
FonetikaCore Suite
Subscriber services
Interconnection partners
Voice, SMS and USSD are separate service paths. The selected gateway, signaling and subscriber products connect to external applications and networks; this view does not imply an included IMS platform.

Relevant building blocks

Select the functions you need.

These products provide a starting point for design. The final mix follows your operating model and the functions already available in your network.

Voice routing and signaling

Transit supplies gateway MSC voice functions and media-gateway control. Signal provides SS7 routing where the network design requires it.

SMS and interactive applications

Message supplies SMSC store-and-forward functions and application messaging integration. Dialog connects USSD sessions to HTTP application processing.

Subscriber data

Use Identity when subscriber profiles, authentication or related network queries are within the scope you need to operate.

Integration boundaries

Plan the systems around the software.

Identify ownership, interfaces and responsibilities before implementation begins.

IMS and IP voice services

IMS, VoLTE and VoWiFi integration can be discussed as a separate engineering scope. Transit is a gateway MSC; it is not presented as a complete IMS service platform.

Applications and media

USSD application servers, business applications and external media gateways retain their own responsibilities. Select interfaces based on the products and service paths in scope.

Commercial interconnection

Voice and messaging connectivity agreements, numbering and applicable charging relationships are defined with the responsible operators and partners.

Pilot & acceptance

Agree what the evaluation should demonstrate.

Choose representative scenarios and measurable acceptance criteria for your environment. Targets and test scope are agreed for the project.

Voice scenarios

Where Transit is selected, test agreed call-routing, subscriber-query and media-gateway-control scenarios with the connected networks.

Message and session flows

Where selected, test SMS submission and delivery paths, store-and-forward behavior and USSD interaction with the application backend.

Records and operations

Check the applicable charging exchanges, service records, routing changes and recovery procedures against the acceptance plan.

Planning questions

Get the scope right from the start.

Bring the voice or messaging service paths you want to change, partner interfaces, application requirements, traffic profile and transition constraints.

Is this the same service as Fonetika Reach?

This solution uses software for organizations running their own voice and messaging infrastructure. Reach provides commercial SMS and messaging services for businesses and messaging partners.

Can we start with an SMSC or USSD gateway only?

Yes. Message and Dialog are separate products. Their integration with subscriber systems, signaling, charging and applications is scoped around the service you intend to operate.

Does the solution include IMS?

IMS, VoLTE and VoWiFi requirements are addressed as a separate integration scope. The product mix on this page covers gateway voice, SMS, USSD, signaling and subscriber data; IMS functions and responsibilities must be defined for the project.

Looking for messaging as a service?

Fonetika Reach connects business applications and messaging partners with SMS delivery.

Explore Fonetika Reach

Get started

Let’s define your solution.

Bring the voice or messaging service paths you want to change, partner interfaces, application requirements, traffic profile and transition constraints.