Absolutely, pretty much everything works except for one type of call.
Either way, it is somewhat irrelevant. In this scenario I did the two
capture simultaneously at eth1 (WAN) in the Endian and on the IP-PBX. I
compared the two captures side by side and here is the difference . . .
This is the
This cuts off, but I just ssh'd into my Endian and did lsmod | grep sip and
here's my results:
nf_nat_sip 3710 0
nf_conntrack_sip 10485 1 nf_nat_sip
nf_nat 10267 9
Thank a lot Matt for the info. At least this gives me something else to
look into before I yank the Endian. I will begin some research now and see
if this is where the problem lies.
As far as this mailing list and the forums you are correct it it garbage.
I don't really understand why though.
I completely agree. I love the product, just wish the community edition
had more attention. In the past few years the support in the community has
just gone way down hill. It used to be quite active.
On Thu, May 30, 2013 at 11:54 AM, Scott Howell scott.howel...@gmail.comwrote:
Thank a lot
You are most welcome.
On Thu, May 30, 2013 at 1:56 PM, Scott Howell scott.howel...@gmail.comwrote:
BTW, thanks for the info. I researched this a bit and think it may be my
culprit. I am going to manually unload the nf_conntrack_sip and nf_nat_sip
modules tonight and reboot to see if this
