b Number Table Audits: The Context
The role of core telecom network is to connect and carry traffic correctly and efficiently to expected destinations. Switches (MSC/MSS/GMSC) are key components of a telecoms network and primarily control this traffic flow.
The group of tables involved in lookups to enable service connectivity is loosely referred to as ‘B-number Tables’. Each switch has a set of B-number Tables that define allowed destinations (B Numbers), generation of charging data (xDRs) for such destinations and routing definitions for each B Number; this data needs to be validated against a ‘correct’ definition to assure integrity.
Incorrect definitions in B-number Tables deployed across a network will cause service issues and loss of profit. But given the often complex nature of the network, and the manual nature of many operating and management processes, mistakes do happen.
why B Number Table Audits
Identification of Revenue Leakages
Identification of CDR Suppression instances for chargeable events
Revenue leakage on account of connectivity failure due to B numbers not being configured / no route being defined for any B nos.
No balance depletion check on IN for prepaid calls
Revenue leakage on account of incorrect access barring
Revenue leakage on account of connectivity failure due to B numbers not being configured / no route being defined for any B nos.
Incurrence of higher carriage charges due to Incorrect Call Routing configurations
Incorrect classification of B Nos. e.g. local nos. classified as international
Incorrect routing definition; local traffic being carried as international
Incorrect routing priority configuration; routing done on network with higher carriage cost payout
Incorrect Routing Definition of International Destinations with own POI
solution Functionality Overview
Application Functionality Flow for Continual Assurance
