SIP3.IO TAPIR Capacity Planning

SIP3.IO is a short word for Technical Transactions Analysis implementation.
TAPIR is an unique name of telecom protocols family product.
This document describes capacity planning aspects of SIP3.IO TAPIR functionality support.

For the correct sizing of the SIP3.IO TAPIR nodes a telecom and/or IP-telephony network and it’s traffic inspection need to be done. Some of important parameters are:

  • Number of days for call history storage required
  • Number of days for user registration history storage required
  • Number of legs for each of the call scenario
  • Number of traffic data source need to be analysed (including SPAN probes, CDR, etc)
  • Operations per call (technical transactions) for each of scenario
  • Identify if technical traffic copy recording already activated/used
  • Storage capacity limitations if a site already have HW to re-use
The listed parameters identification helps to clarify data volumes and plan on site or cloud resources required for the network.

The following capacity reference is useful for planning.

  • Calls history store for 20 days (SIP INVITE and associated exchange)
  • Customer User-Agents registration history sore for 20 days (SIP REGISTER)
Number of legs of capture is an important parameter.
The reference is designed as

  • 4-leg traffic: Internet -(1)- Access -(2)- SSW -(3)- SBC-I -(4)- SBC-Core

In each network a call could be assisted with a various number of infrastructure nodes intercommunication.
The reference use is:

  • 44 operations per call (SIP PDU or arrows on datagram)
  • 12 operations per leg
Protocol Data Unit (PDU) sizes may vary on a specific network according to numbering plan and other technical information.
The reference is:

  • SIP Header average size of 600 bytes
  • SIP Message body of INVITE (SDP+ISUP) average size of 900 bytes
Those conditions work as

  • 28KB per call (as of 4 legs and 44 operations) in RAW PCAP format
  • 393MB of DB use for SIP INVITE per day
  • 81MB of DB use for SIP REGISTER per day
Having storage compression enabled reference implementation goes:

  • Storage capacity required 3Tb (RAID10 on 8 disk drives)
Disk subsytem works with following IOPS

  • 250-350 average write intensity operations per seconds (IPS)
  • 2000-3000 peak write intensity operations per seconds (IPS)

© 2018, SIP3.IO, Inc.