Why do you need it actually? Freeswitch will see proxy IP, yes, but the websocket connection will be bind to one of the ports of haproxy and it should work fine.
But FreeSwitch wants SIP headers "X-AUTH-IP" and "X-AUTH-PORT" in every SIP message not only connection establishing First of all Freeswitch doesn't require those headers. Well for that you should use STUN and set that in your clients application. Another way is to use Kamailio, yes, it can add those on the fly, but again - you must put it instead of the proxy server (which you may actually want to do as it is a SIP proxy by-desing and it works with websockets pretty fine).
Alexandru Covalschi VoIP Engineer and System Administrator tel: +373 673 98 493
3 янв. 2017 г., в 22:47, Sergey Safarov <s.safarov@gmail.com> написал(а):
Then you will try cofigure Kamailio between NGINX and FreeSwitch. In this case Kamailio can parce http headers and add requred SIP header. Are you can suggest other way to publish FreeSwitch socket on same port with http server?