Map the existing service paths
Identify voice call routes, SMS delivery paths and USSD applications. Establish which network nodes and external partners participate in each service.
Operators, MVNOs & network integrators
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.
Relevant building blocks
These products provide a starting point for design. The final mix follows your operating model and the functions already available in your network.
Transit supplies gateway MSC voice functions and media-gateway control. Signal provides SS7 routing where the network design requires it.
Message supplies SMSC store-and-forward functions and application messaging integration. Dialog connects USSD sessions to HTTP application processing.
Use Identity when subscriber profiles, authentication or related network queries are within the scope you need to operate.
Integration boundaries
Identify ownership, interfaces and responsibilities before implementation begins.
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.
USSD application servers, business applications and external media gateways retain their own responsibilities. Select interfaces based on the products and service paths in scope.
Voice and messaging connectivity agreements, numbering and applicable charging relationships are defined with the responsible operators and partners.
Pilot & acceptance
Choose representative scenarios and measurable acceptance criteria for your environment. Targets and test scope are agreed for the project.
Where Transit is selected, test agreed call-routing, subscriber-query and media-gateway-control scenarios with the connected networks.
Where selected, test SMS submission and delivery paths, store-and-forward behavior and USSD interaction with the application backend.
Check the applicable charging exchanges, service records, routing changes and recovery procedures against the acceptance plan.
Planning questions
Bring the voice or messaging service paths you want to change, partner interfaces, application requirements, traffic profile and transition constraints.
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.
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.
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.
Fonetika Reach connects business applications and messaging partners with SMS delivery.
Get started
Bring the voice or messaging service paths you want to change, partner interfaces, application requirements, traffic profile and transition constraints.