Create a Post
cancel
Showing results for 
Search instead for 
Did you mean: 
knassif
Explorer

sip trunk

we are having an issue where i'm using a auto nat of an object that NATS to the internet on a public IP address for a sip trunk cube router that connects to a provider, the provider is still seeing the RFC1918 IP address of the cube router and not the public NAT that it autonats to, what could be the issue here and what can be done to fix it. we dont have application layer blade , only firewall blade.

0 Kudos
4 Replies
CaseyB
Collaborator

Depending on what version and HF you are running, that is a known issue with SIP and auto NAT. The fix would be to use a manual NAT rule.

0 Kudos
knassif
Explorer

we are using R81.10 take 66 are we affected?

0 Kudos
CaseyB
Collaborator

R81.10 Fixes 

It doesn't look like it from the notes, but it wouldn't hurt to try the manual NAT rule. I've seen VoIP NAT issues appear multiple times in the fixes over the last couple years. We are not experiencing this issue on R81.10 Take 110 using manual NAT for SIP.

0 Kudos
knassif
Explorer

just tried manual NAT's still did not work

0 Kudos

Leaderboard

Epsum factorial non deposit quid pro quo hic escorol.

Upcoming Events

    CheckMates Events