The problem of using callweaver with multiple public IP addresses (with NAT) was presented to me. Research using google and the callweaver.org search feature resulted in others having a similar issue, but no fix was available.
I have managed to modify the callweaver source to use the value stored in the 'fromdomain' variable pulled from the sip.conf file for the given channel. sip.conf looks like this: [7755336030] type=peer host=206.174.160.XXX context=inbound insecure=port,invite fromdomain=173.12.200.XX dtmfmode=rfc2833 canreinvite=no ;Let's try setting up the outgoing VoIP [65.115.130.XX] type=peer host=65.115.130.XX fromdomain=65.121.29.XX dtmfmode=rfc2833 canreinvite=no NAT is turned on globally. The 65.115.130.XX is strictly an outbound calling channel. The 7755336030 channel is a strictly inbound calling channel. All inbound SIP communication goes to and from 206.174.160.XXX and 173.12.200.XX. This is basically done by modifying the SIP header information when it's generated by substituting the default externip variable's info with the fromdomain variable's info, if present. Outbound calling does similar but with different IPs, of course. I'd like to submit this modification to the callweaver group for perusal and hopefully inserting into future releases, but am unsure how to. Can anyone help me out with this? Thanx!! G _______________________________________________ Callweaver-dev mailing list [email protected] http://lists.callweaver.org/mailman/listinfo/callweaver-dev
