- Products
- Learn
- Local User Groups
- Partners
- More
What’s New in Identity and Trust?
AI Security Masters
Security in the Pace of AI:
From Threat to Force Multiplier
CPX is Back!
Join us in Las Vegas, Vienna, and/or Bangkok!
Check Point Named a Leader
The Forrester Wave:
Enterprise Firewall Solutions, Q4 2026
What’s New in Agentic Network Orchestration
CheckMates Go:
Fun Ding
Hello guys,
First of all, I'm new with VoIP configuration and now encountering VoIP traffic issue while the call flow traverses the Check Point Gateway
I will briefly explain an issue.
1. When Phone device ( 192.168.10.204 ) that behind firewall calls to Phone device that's the opposite side of firewall ( 10.105.62.102 ). RTP message is working fine, both sides can hear each other
2. But If Phone devices from the opposite side call back to 172.19.0.204 ( translation to 192.168.10.204 ),
RTP message is not working properly, only one side can hear voice but another cannot.
In this point, Phone A could hear, but Phone B could not.
Please see diagram below to refer
Does anyone here ever encounter issue like this before?
Really appreciate every comments
Regards,
Sarm
Can you show us your NAT-rule for the connection. You have to translate both directions. Maybee this is a NAT problem. Did you see the NAT working for both directions?
We had an identic issue and used at first https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solut... to check the right rule set.
Based on how your VOIP Architecture is build you have to choose the right ruleset.
Then most stuff worked but for example more then one call at the same time (to/from external) wasn't possible. We haven't found any Log/Drop.
However our final solution was to disable all SIP IPS Rules for the VOIP Area.
KR
David
I describe exactly this issue in my article:
VoIP Issue and SMB Appliance (600/1000/1200/1400)

Hi,
We've had similiar problem but with H323 and no NAT in our case - "Hide internal networks behind gateway's IP" is checked and we have no NAT rules for VOIP traffic. Source and destination wasn't nated but payload was still nated. SK98354 in our case helped.
Depending on the version You are using look at this SK143713
Regards
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 10 | |
| 9 | |
| 7 | |
| 6 | |
| 6 | |
| 6 | |
| 4 | |
| 4 | |
| 3 | |
| 3 |
Tue 17 Nov 2026 @ 08:30 AM (EST)
Bogota Breakfast & Hack: IA bajo control y ataques en vivo con Workspace SecurityTue 17 Nov 2026 @ 05:00 PM (CET)
AI Security Masters: Security in the Pace of AI: From Threat to Force MultiplierTue 17 Nov 2026 @ 11:00 AM (EST)
Under the Hood: Check Point SASE | Troubleshooting Like a ProTue 24 Nov 2026 @ 01:30 PM (GMT)
La nueva realidad de los ataques DDoS: autonomía, escala y el futuro de la defensaTue 17 Nov 2026 @ 05:00 PM (CET)
AI Security Masters: Security in the Pace of AI: From Threat to Force MultiplierTue 17 Nov 2026 @ 11:00 AM (EST)
Under the Hood: Check Point SASE | Troubleshooting Like a ProTue 24 Nov 2026 @ 01:30 PM (GMT)
La nueva realidad de los ataques DDoS: autonomía, escala y el futuro de la defensaWed 02 Dec 2026 @ 03:30 PM (GMT)
The New DDoS Reality: Autonomy, Scale, and the Future of DefenseTue 17 Nov 2026 @ 08:30 AM (EST)
Bogota Breakfast & Hack: IA bajo control y ataques en vivo con Workspace SecurityAbout CheckMates
Learn Check Point
Advanced Learning
WE SECURE YOUR AI TRANSFORMATION