lneblett

IOP does not respect contact & connect headers in device's INVITE.

remote phone is connected via site-to-site IPSec VPN. The SIP settings are set to:

SIP replace 10.10.10.108/71.78.XX.XX

IP route is set to 10.10.10.0/255.255.224.0/10.10.10.108 0.0.0.0/0.0.0.0/71.78.XX.XX

The remote phone is 10.10.30.101 and the contact & connect headers tell the IOP to use the private IP of the phone, but the IOP responds back and tells the remote phone to use the public IP of 71.78.XX.XX and not the private IP of 10.10.10.108. The subnet mask used in the replace should encompass the 10.10.30.X range, but it seems to not.

I have two VPNs set, with 3 different subnets seen at the IOP:

10.10.10.0 local

10.10.20.0 remote

10.10.30.0 remote

Running a 63.0.4 release.

Do I need to have a separate entry for each VPN'ed LAN to use the local IP of the IOP?