Professional VoIP Setup with OpenSIPS + PostgreSQL + CGRateS
Budget: $250 – $750 USD
Description:
We're looking for a skilled VoIP engineer to perform a complete and well-documented installation of a production-ready VoIP environment using:
OpenSIPS (LTS version) as a SIP Proxy (Class 4).
CGRateS for real-time billing per SIP extension (tech prefix).
PostgreSQL as the main database.
The system will use OpenSIPS as a SIP proxy only (no media, no registration). The Asterisk server is already installed and will be used only as a SIP trunk to handle registration/auth and media.
Technical Requirements:
OpenSIPS (LTS) Installation
SIP Proxy role only – no media handling or registration.
Routing based on tech prefix.
Full support for NAT traversal.
Forwarding SIP traffic to Asterisk (trunk via IP/port).
PostgreSQL integration.
CGRateS Integration
Real-time billing based on the originating extension (tech prefix).
Custom billing cadence support (e.g., 0/30/6 or similar).
Store CDRs in PostgreSQL.
Integration with OpenSIPS via JSON API or similar robust method.
Administrative REST API
Create/manage clients (based on SIP extension/tech prefix).
Assign pricing, cadence, and destination routing.
Live call monitoring and historical usage.
System health checks (OpenSIPS and CGRateS).
Complete Documentation
Every step of the setup must be clearly documented.
Optionally, provide bash/automation scripts.
Must allow 100% reproducibility of the setup.
Docker Usage:
Optional, based on your expertise. If it simplifies deployment, you're free to use it.
Operational Flow:
Client registers on OpenSIPS domain.
OpenSIPS relays REGISTER to Asterisk.
Asterisk replies with 200 OK.
OpenSIPS routes SIP traffic and manages billing via CGRateS.
Requirements:
Proven experience with OpenSIPS + CGRateS.
Strong SIP/NAT/billing knowledge.
PostgreSQL + API expertise.
Important:
Shorter delivery time will be a strong advantage. The fastest professional with proven skills will win the job.
We're looking for a skilled VoIP engineer to perform a complete and well-documented installation of a production-ready VoIP environment using:
OpenSIPS (LTS version) as a SIP Proxy (Class 4).
CGRateS for real-time billing per SIP extension (tech prefix).
PostgreSQL as the main database.
The system will use OpenSIPS as a SIP proxy only (no media, no registration). The Asterisk server is already installed and will be used only as a SIP trunk to handle registration/auth and media.
Technical Requirements:
OpenSIPS (LTS) Installation
SIP Proxy role only – no media handling or registration.
Routing based on tech prefix.
Full support for NAT traversal.
Forwarding SIP traffic to Asterisk (trunk via IP/port).
PostgreSQL integration.
CGRateS Integration
Real-time billing based on the originating extension (tech prefix).
Custom billing cadence support (e.g., 0/30/6 or similar).
Store CDRs in PostgreSQL.
Integration with OpenSIPS via JSON API or similar robust method.
Administrative REST API
Create/manage clients (based on SIP extension/tech prefix).
Assign pricing, cadence, and destination routing.
Live call monitoring and historical usage.
System health checks (OpenSIPS and CGRateS).
Complete Documentation
Every step of the setup must be clearly documented.
Optionally, provide bash/automation scripts.
Must allow 100% reproducibility of the setup.
Docker Usage:
Optional, based on your expertise. If it simplifies deployment, you're free to use it.
Operational Flow:
Client registers on OpenSIPS domain.
OpenSIPS relays REGISTER to Asterisk.
Asterisk replies with 200 OK.
OpenSIPS routes SIP traffic and manages billing via CGRateS.
Requirements:
Proven experience with OpenSIPS + CGRateS.
Strong SIP/NAT/billing knowledge.
PostgreSQL + API expertise.
Important:
Shorter delivery time will be a strong advantage. The fastest professional with proven skills will win the job.