Enables dynamical routing of calls or messages in the fixed or mobile network based on flexible criteria, such as the number being dialed, the origin or destination of the call, network conditions, and the type of service requested. Provides greater flexibility and efficiency in how calls or messaging sessions are handled by the network, allowing for more advanced features in managing routing.
Number Portability is a critical feature in mobile networks, allowing subscribers to retain their phone numbers when switching from one service provider to another. This functionality is important for both consumers and the telecommunications industry for a variety of reasons:
Number portability is vital in mobile networks because it supports consumer convenience, fosters market competition, and encourages innovation. It allows users to change telecom providers without the hassle of changing their phone numbers, which in turn improves customer satisfaction and retention. For businesses, it ensures professional continuity, and for regulators, it provides a fair and competitive marketplace.
Flexible Number Routing (FNR) is a concept in telecommunications networks that refers to a method of dynamically routing calls or data based on flexible criteria, such as the number being dialed, the origin or destination of the call, network conditions, and the type of service requested. FNR provides greater flexibility and efficiency in how calls or data sessions are handled by the network, allowing for more advanced features in managing routing.
Common use cases:
We achieve a highly scalable and highly available architecture by using a cluster of 3 database nodes with replication, automated failover mechanisms, and stateless frontend containers managed by a load balancer and horizontal scaling. This setup ensures that the system can handle increasing traffic demands, recover from failures quickly, and maintain service continuity without downtime. The stateless nature of the frontend containers and redundancy in the database cluster guarantees that even if components fail, the overall system remains operational and efficient.
Software packaging | Docker images, RPM or DEB packages |
Database | Document-based NoSQL data store |
SCTP | RFC 4960; with multi-homing support |
M3UA | RFC 4666; IPSP, ASP and SGP modes |
SCCP | ITU-T Q.711 through Q.714 connectionless Class 0 & 1 |
TCAP | ITU-T Q.700 through Q.707, Q.781, Q.782, Q.791 |
INAP | ETSI ETS 300 374-1 & ITU-T Q.1218 CS-1R |
MAP | GSM MAP v1, v2, v3, v4 |
SIP | 3GPP TS.24.229 IMS SIP extensions TISPAN ES 283 003 IMS extensions IETF RFC 3261 session initiation protocol IETF RFC 3262 reliability of provisional responses IETF RFC 3263 locating SIP servers IETF RFC 2327 session description protocol IETF RFC 3264 an offer/answer model with SDP |