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.
...and this is the main problem. callweaver doesn't store this in the
peer struct. it's probably not too much work, so go ahead :)
3. manual config for a specific client, especially those won't
register.
4. need more consideration about multiple registration.
multiple registrations, if you mean peer [a] can register from host
1,2,3 and receive calls on all, is not possible with the current sip
stack. I would guess parts need a total rewrite, and I don't want
that job. there is work being done to write a new channel driver with
libsofia, which will hopefully be better than today's swedish crap.
roy
---
Roy Sigurd Karlsbakk
[EMAIL PROTECTED]
Tlf: 98013356
---
"Why is it drug addicts and computer afficionados are both called
users?" -- Clifford Stol
_______________________________________________
Callweaver-dev mailing list
[email protected]
http://lists.callweaver.org/mailman/listinfo/callweaver-dev
