#351: aliased interface (Invalid)

Back to ticket list | See last change
Mar 17 2008 * 04:38
Reported by: Release: 1.2
Priority: Normal Milestone:
Component: SIP Assigned to:

When callweaver works on aliased interface with bindaddr=0.0.0.0 and SIP packet arrives on aliased eth0:0 adressed for example as 172.16.16.1 chan_sip always replies from primary interface eth0 addressed for example as 10.1.1.1.

Changelog:

Modified by Jun 05 2008 * 20:20

This is a know problem with chan_sip

Do you know if this is fixed in Asterisk, and if so, when it was fixed?

Modified by Jun 05 2010 * 15:47
  • Status: changed from Open to Invalid

This seems entirely correct to me. UDP is not session based. If you do not bind the alias address specifically but use a general 0.0.0.0 then outgoing packets will also source from 0.0.0.0 and this will be replaced with the primary address of the interface as packets go out. Maybe you should bind a socket on the alias address? Maybe you should use “iproute … src …” for some paths?