Introduction

Purpose and scope

Ticket NumberTT#422784
Target Build
MR50-0
Affected ComponentsPortaConfigurator, PortaSIP Media ServerCluster
Document Start Date2015-06-10

Collaborators

Business Department

  • N/A

Development Department

Testing and Support Departments

  • TBD

Definitions, acronyms and abbreviation

PortaSIP Media Server Cluster (PSMSC): Clustered solution which capable to handle media and IVR application  and built on top of PotaSIP.

Processing Node:  Essential processing part of PortaSIP Media Server Cluster responsible for SIP calls handling and represented on PortaConfigurator as separate configuration instance.

Registrar Node: Essential processing part of PortaSIP Media Server Cluster responsible for SIP registration handling and represented on PortaConfigurator as separate configuration instance.

Dispatching Node: So-called "cluster fronted" - a Node which handles all incoming and outgoing traffic as servers as cluster entry-point. It includes routing and traffic limiting facilities plus there is a monitoring service for processing nodes.

References

  1. man hier(7)

Overview

Current ProcessingNode and Registrar layout assumes placing all instance related configuration, run and logs files into dedicated sub-folder in /porta_var directory. Such solution somewhat simplifies finding corresponding files during debugging and manipulation with files. However current solution contradicts to /porta_var main purpose - it should keep persistent data which are valuable for Customer and supposed to survive an update like DB, audio recordings, logs. As result instance directories requires special handling during update. Also it contradicts to standard file system hierarchy which clearly specify location of configuration, statistics and run-time files (see man 7 hier). So it was decide to minimize presence of PorcessingNode to the minimally required by "/porta_var" directory specification and reallocate files into standard location.

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.