Introduction

Purpose and scope

The documents describes reworking of existing functionality related to specific handling of BE Nodes on pre-AAA stage.

Ticket NumberTT#381297
Target Build
MR49-0
Affected ComponentsPortaAdmin, DB, PortaSIP
Document Start Date2015-06-08

Collaborators

Business Department

  • N/A

Development Department

Testing and Support Departments

Definitions, acronyms and abbreviation

Call Handling Rules: Set of automatically generated and manually defined rules which instructs PortaSIP regarding the way how a call should be handled on pre-AAA stage. I.e. rules define exact information which should be placed in BE request and authentication mechanism which should be used.

BE: Billing Engine.

References

  1. Current implementation issue: TT#424563
  2. TT#144339 - start usage of DB for passing Call Handling Rules from PortaAdmin to PortaSIP.
  3. Very first implementation (for informational purpose)

Overview

Because of specific role of  BE Nodes their requires particular handling from PortaSIP side. To be more precise PortaSIP should utilize so-called IP authentication for NAS with source IP matched to BE Node NAS IP address. Such logic is perfectly fit into Call Handling Rules logic so it was nature to perform it by Call Handling modules in PortaSIP.  For the time being we have passed knowledge about configured BE Nodes into PortaSIP by fetching data from specially created DB VIEW. The main issue with such solution is that possibility ot intersection with manually generated data (see TT#424563). Also since BE Node not only entities which requires special handling there is exist alternative mechanism - auto-generated Call Handling Rules. As result we have two different solution for similar tasks which makes whole design inconsistent and less reliable. So there is an intention to avoid usage of DB VIEW and utilize auto-generated rules for BE Nodes as well.

Specifications

Create "Business requirements" Create "Software requirements" Create "Design requirements"

Testing plan

Prepared by QA. The main goal  is to check Business and Software Requirements. This chapter should be prepared as separate document.

Feature integration guide

It is auxiliary maintenance description which carries information about how to deploy and configure developed solution, its limitation and usage particularities. This chapter should be prepared as separate document.