about new params --int-ip and --ext-ip

[GoogleCodeExporter]

I tried to configure siprtmp with
--int-ip as 127.0.0.1 and --ext-ip as a public ip 12.34.56.78
all SIP messages are going and received well, but no sound.
is it a NAT issue ? if yes, how should I set it ?

Thanks

Franck

Original issue reported on code.google.com by pratn...@gmail.com on 14 Apr 2011 at 5:37

[GoogleCodeExporter]

You should not use --int-ip to 127.0.0.1 if you intend to test between 
different computers. Using --int-ip to this will bind all your sockets to 
localhost hence it cannot easily receive packets with another host. SIP works 
because of the "rport" extension implemented in p2p-sip code. But media path 
won't.

If you leave out --int-ip parameter (i.e., don't supply it), then it will bind 
to "ALL" local IP addresses of your computer, and will work in most cases.

The only time you should supply --int-ip is if your computer has multiple 
non-local IP interfaces and you want to use one such interface only, instead of 
binding to all. Typically, this is needed if you have multiple virtual 
interfaces (e.g., due to virtualization/vmware/etc), then you can use --int-ip 
to specify the actual IP address to bind to.

The --ext-ip is needed typically when you are running siprtmp.py on Amazon EC2, 
whether the external IP address is different than the local interface address 
(10.x.x.x) and there is a full cone mapping between external and internal IP 
addresses. If you leave out --ext-ip, then it will use any locally available 
interface address, which works in most cases.

Additionally, the --host option is useful for specifying the listening IP 
address of the RTMP connection. If you leave it out, then it will use "ALL" IP 
addresses to bind to. One reason to specify --host is if you only want to 
accept RTMP connection from local machine, e.g., when running siprtmp.py as a 
local adaptor.

If you can let me know the network configuration/set up you want to try out, I 
can recommend the proper values of these options.

Original comment by kundan10 on 15 Apr 2011 at 5:57

[GoogleCodeExporter]

Hi Kundan,

I'd just like to avoid public rtp media access by unauthorized clients.
I have a public IP and want to use 127.0.0.1. but if it's not a security issue 
of course I can use public IP in --int-ip which I use already like this.
Thank you

Original comment by pratn...@gmail.com on 17 Apr 2011 at 4:46

[GoogleCodeExporter]

Marking as invalid, as this is just about some clarification on --int-ip and 
--ext-ip.

Original comment by kundan10 on 20 Sep 2011 at 5:47

• Changed state: Invalid