VoIP / Kamailio Developer / Postgres /GUI

System Use

Used for internal routing based on LCR & Capacity of carriers

Technology to be used

• Kamailio

• Postgress

• RTP Engine

• Redis (If needed)

• GUI – Up to developer

GUI / Back-end Features Required

Carriers Trunks (Calls Out)

Add Carrier

LCR – Upload Rates for LCR per carrier (Code, Destination, Rate/Price)

Ports & CPS Management per carrier trunk

Carrier IP Management (Option to add more then 1 IP) Round Robin option

Tick box for calls only to fail over in event of CPS/Ports being exceeded. No fail over for any other SIP codes.

ANI Manipulation. Example: If ANI starts with 61XXXXXXXX replace with 0XXXXXXXX Ability to add multiple Rules.

Routing Plans

Create Routing Plans by choosing what carrier you want in each routing plan

Customer Trunks (Calls in)

Create Customer

Assign Routing Plan

CPS/Port Limits

Add/Edit customer IP(s) and Tech Prefix

Disable or enable Media (RTP Engine)

ANI Manipulation Option, MIN/Max Length & only Allow ANI to pass starting with XX Ability to add multiple Rules.

CDR Search

Search CDR’s

GUI to have a CDR Retention Setting e.g., 30 Days (changeable) auto delete after XX days

Automatic Backup of CDR’s to FTP (SFTP settings changeable in GUI)

Optimisation / Logic / Geo Redundancy

This system is a basic routing system with no billing etc required. Port & CPS limits are extremely important and Kamailio must be optimized accordingly. The database will be hosted off-site (AWS) for redundancy. Kamailio's will be installed in a separate datacentre so Kamailio must not be Database Heavy, Local Redis per Kamailio may be required. Kamailio/DB must be optimized for heavy CPS/Concurrent calls. As we will be using Multiple Kamailios it would be nice to build the ability for Kamailios to share CPS/Port limits across all Kamailio nodes.

VoIP PostgreSQL Asterisk PBX SIP

ID projekta: #33870374

Več o projektu