rtp
10 posts.
Managing the firewall on a cloud dialer
A VICIdial cloud server's firewall needs ongoing attention - carrier IP changes, agent network shifts, and OS upgrades can all silently break SIP or RTP.
Read postOpening the RTP port range on a cloud firewall
Cloud firewalls block inbound UDP by default, and a closed RTP port range is the most common reason VICIdial calls connect but carry no audio.
Read postChoosing a cloud region for your dialer
The cloud region where you deploy your VICIdial box affects call quality, data residency, and cost - here is how to pick the right one for your operation.
Read postCloud security groups for a VICIdial server
Cloud security groups default to blocking everything - this guide lists every port VICIdial and Asterisk need open and explains why each one matters.
Read postKeeping carrier latency low from the cloud
Cloud region placement has a direct effect on RTP path length and call quality - here is how to reduce carrier latency for your VICIdial box.
Read postInstalling VICIdial on a VPS
A VPS is a fine home for VICIdial if you get three things right: a real public IP, an open RTP range, and NAT handled. Here's how each one bites.
Read postWhen an agent can't hear the customer but the customer hears them
One-way audio means RTP is flowing in only one direction, almost always blocked by NAT, a firewall, or routing on the agent's leg.
Read postDiagnosing choppy or robotic audio on agent calls
Choppy, robotic, or garbled call audio almost always comes from the RTP path: jitter, packet loss, a codec mismatch, or a CPU-starved dialer.
Read postWhen recordings exist but have no sound: what to check
A recording file that exists but plays silent points at the RTP and mux path: codec, recording format, and the recording delay rather than missing files.
Read postOne-way audio on carrier calls: causes and fixes
One-way audio means signaling connected but RTP media is blocked one direction - almost always a NAT, public-IP, or RTP-port problem. Here is how to find it.
Read post