i've noticed the proxy-proto feature breaks kamailio as a registrar. when tcp_accept_haproxy=yes and a REGISTER is received from the loadbalancer, IP and Port variables are changed to the UAC's IP and Port. the location data that is saved is then inaccurate. when user location lookup is called, it returns the IP:port of the UAC. this will not work since the phone expects the INVITE to come from the load-balancer's IP:Port (not kamailio's).
the saved location data for the user should still be the load-balancer IP:port. I think the appropriate approach for proxy-proto is to not modify any existing IP and Port variables, but add new ones like @joelsdc suggested ($Ci, $Cp)
id be willing to write a patch for this but want to make sure others agree.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.