1. Brekeke Product Name and Version: Brekeke SIP Server 2.4.9.0/286.3
2. Java version:
3. OS type and the version: Windows Server 2003
4. UA (phone), gateway or other hardware/software involved:
5. Your problem:
Hello.
I have a scenario where the UA is behind NAT. The UA is assigned a 100.100.x.x address on the LAN and there is a VPN tunnel from the router to the HQ where the Brekeke PBX/SIP is located. Traffic going from the UA is NAT'd through the VPN tunnel so at the Brekeke end the traffic appears to be on the LAN, which is 10.x.x.x.
The first problem I had was with SIP. Because the SIP header contained the 100.100.x.x (pre-NAT) address the UA was being registered on the SIP server using this address. The actual IP address is of course the post-NAT 10.x.x.x address so SIP packets from Brekeke were being sent to 100.100.x.x and getting no where.
I fixed this by setting the following in the Advanced configuration:
register.contact.remote=true
Now SIP is going to the post-NAT 10.x.x.x address.
But RTP is still going to the pre-NAT 100.100.x.x address.
How can I fix this?
I have tried things like RTP relay "on" and I have also tried setting "net.rtp.follow.remoteaddr=true" in Advance configuration too but a packet capture always shows RTP going to the wrong IP address.
I can provide a screenshot of a packet capture if required.
Any help would be appreciated.
2. Java version:
3. OS type and the version: Windows Server 2003
4. UA (phone), gateway or other hardware/software involved:
5. Your problem:
Hello.
I have a scenario where the UA is behind NAT. The UA is assigned a 100.100.x.x address on the LAN and there is a VPN tunnel from the router to the HQ where the Brekeke PBX/SIP is located. Traffic going from the UA is NAT'd through the VPN tunnel so at the Brekeke end the traffic appears to be on the LAN, which is 10.x.x.x.
The first problem I had was with SIP. Because the SIP header contained the 100.100.x.x (pre-NAT) address the UA was being registered on the SIP server using this address. The actual IP address is of course the post-NAT 10.x.x.x address so SIP packets from Brekeke were being sent to 100.100.x.x and getting no where.
I fixed this by setting the following in the Advanced configuration:
register.contact.remote=true
Now SIP is going to the post-NAT 10.x.x.x address.
But RTP is still going to the pre-NAT 100.100.x.x address.
How can I fix this?
I have tried things like RTP relay "on" and I have also tried setting "net.rtp.follow.remoteaddr=true" in Advance configuration too but a packet capture always shows RTP going to the wrong IP address.
I can provide a screenshot of a packet capture if required.
Any help would be appreciated.