[arm-allstar] Bind chan_echolink.so to specific IP address

[David McGough]

Patrick,

There are 2 config parameters in the echolink.conf file's node stanza
which allow the user to control the ip address and base UDP port which the
echolink instance uses.  These parameters are, for example:

[el0]
ipaddr = 192.168.234.12
port = 5198


....Note that the "port" parameter defines the echolink audio UDP port. 
The control port is always the next higher UDP port--typically 5199.

However, there is a problem in the current code.  Outbound echolink TCP
connections to the directory server don't bind to the ip address specified 
by this parameter; they bind to the default address of the network 
interface.  So, it's likely the wrong IP address will get reported to the 
echolink directory server, rendering echolink non-functional.

I'll fix this issue in the latest alpha code release and send you a 
message about it.


73, David K4FXC



On Mon, 18 Jul 2022, "Patrick Perdue via ARM-allstar" wrote:

> Is there a way to bind chan_echolink to a specific IP address the way 
> you can with iax? I am running two echolink conference servers on two of 
> the five available public IP addresses on one Raspberry Pi, neither of 
> which have IAX bound to them, and I want to also run HamVoIP's echolink 
> driver at the same time, obviously not on the same IP address as either 
> of the two conference servers. However, there doesn't seem to be a 
> bindaddr for echolink, and I don't know how to insure that iax and 
> echolink are on the same IP address with five available.
> 
> End goal:
> 
> IP address 1: IAX and chan_echolink.so
> 
> IP address 2: echolink conference 1
> 
> IP address 3: echolink conference 2
> 
> Thanks and 73
> 
> N2DYI
> 
> _______________________________________________
> 
> ARM-allstar mailing list
> ARM-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> 
> Visit the BBB and RPi2/3/4 web page - http://hamvoip.org
>