APPENDIX D. The Number_Portability table description

Link copied to clipboard






The unique ID of the ported number record in the database



The ported number. When a call is being established, PortaBilling will compare the originally dialed number (CLD/DNIS) from the call request with values in this field. If matched with a database entry, then the call will be authorized, rated and routed depending on the prefix specified in the origin field of this entry



A target prefix used instead of the originally dialed number to authorize, rate and route the call. It can match a special recipient operator code maintained in tariffs (a symbolic name, e.g., Netcom) or a real destination from the recipient operator range. This prefix must exist in a routing tariff associated with this operator (vendor)



The unique ID of the virtual billing environment where the ported number belongs to. When a certain ported number must be checked only in a certain virtual billing environment it must have the i_env specified. The mapping table can contain globally applicable (used in all virtual billing environments) list of ported numbers – such entries will have the i_env field set to NULL. Note that in case of ambiguous match, the one with specified virtual billing environment is used



By default the same target prefixes are used for routing and calculating your expenses for termination of calls to vendors and for billing customers. This might not be always convenient for customer tariff management because the rules for routing and billing vendors might be different from those used for billing customers. This field allows to specify prefixes for matching rates in customer tariffs. In this case prefixes from this field will be used for billing customers instead of the ones specified in the origin field.



Ported number priority (experimental.)

On this page