There's a mix-up with SDP building packets on red5phone. I was trying to run up
the sip/rdp connection through an openvpn tun interface. It registers just
fine, but is unable to be validated, because packets are returning to the
viaAddress on the initial header. The red5 machine has eth0 and tun0
interfaces. If i register to my asterisk via "the internet"(e.g eth0) it is ok,
because the handshake goes with the address of the eth0. If i decide to connect
via the openvpn tunnel i can see the packets through it, but the header on the
debug console states "sip:user@eth0.ip:port". I took a peek at the src and the
initial SDP and the RegisterClass are taking a property viaAddress from a
regular getHost routine. This is appropriate in most of the cases, but not mine
in particular.
I ended up setting the hostname environment variable to "10.10.5.10", which is
my tun0 ip, so that it would function correctly again.
There's an issue posted here with a similiar problem which builds up the
viaHeader with 127.0.0.1. You can again fix it with a simple `hostname your.ip`
before running red.
My suggestion is that a new configuration variable is introduced for just those
cases and control is more straight-forward.
Thank you.
Original issue reported on code.google.com by ser...@gmail.com on 17 Nov 2010 at 11:57
Original issue reported on code.google.com by
ser...@gmail.comon 17 Nov 2010 at 11:57