Hi List
I just tested a server with two NICs, say
NIC#1: IP A, eth0
NIC#2: IP B, eth1
IP A and IP B are public IP on different IP subnets
I sniffered and found, like asterisk, callweaver always uses the IP A as
source IP in all UDP packets.
That causes problem with SIP clients that register themselves to IP B.
I think there're several scenarios:
1. clients initiate transactions like INVITE. callweaver needs to keep track
of what interface and IP received SIP method.
2. callweaver initiates transactions. callweaver needs to remember what
interface got REGISTER from a specific client.
3. manual config for a specific client, especially those won't register.
4. need more consideration about multiple registration.
anybody interested in making multihomed servers working?
I'm trying to make it work, but help needed.
Franz Wu
_______________________________________________
Callweaver-dev mailing list
[email protected]
http://lists.callweaver.org/mailman/listinfo/callweaver-dev
