Webrtc client IP addresses and reverse proxy

[Vieri]

Hi,

According to ASTERISK-30272: webrtc client IP addresses behind reverse proxy this feature request should be discussed here.

Briefly:

asterisk -rx “pjsip show endpoints” | grep Contact

shows 127.0.0.1 for webrtc clients connecting via reverse proxy.

Could Asterisk show X-Forwarded-For only for “trusted” proxies?

This matter has already been brought up here:

Websocket for WebRTC behind Reverse Proxy

Im trying to run the http server of Asterisk behind a reverse proxy (running on the same device as Asterisk itself). All is working ok, except i always get 127.0.0.1 as the host for the devices connected using websockets. This a common problem with reverse proxies, because after passing it, the new source ip is no longer the original one but the one of the reverse proxy, but normally this can be solved by using the header ’ X-Forwarded-For’ or ’ X-Real-IP’ in the http request and putting the ori…

I don’t have a patch proposal, but wouldn’t it be useful?

[jcolp]

I don’t think anyone can disagree with it being useful. Someone ultimately has to do the work, though.