firewalls and OBI, Callcentric, GV and dd-wrt w/SPI
Stewart:
Quote from: winterescape on November 25, 2011, 01:38:01 pm
Any idea when this firmware update to address this issue will be available?
IMHO, there is not yet enough evidence to show that you are being bitten by the same bug as RonR. In particular, when the remote party hangs up first, if a short (less than one minute) call disconnects correctly, but a long call (e.g. 15 minutes) does not, I would first suspect a timeout in the router.
The definitive test is to capture traffic at the OBi and confirm that it indeed receiving the BYE from Callcentric, but it is not responding properly.
winterescape:
Hmmm well O.K. I had interpreted Ron’s response as “Known issue” and had been looking for the update. I think I am back to where I started then assuming it is the router and not wanting to disable my firewall.
So how best to configure my router to keep Obi happy and keep my network computers properly protected?
DMZ or set up port forwarding for specific ports?
Thanks…
Stewart:
For SP1 or SP2 (whichever you are using with Callcentric), change X_UserAgentPort from 5060 to 5070 or from 5061 to 5071. Then, in DD-WRT, forward UDP port 5070 or 5071 to the private IP address of the OBi (which should be constant, either by assigning it statically in the OBi, or by using a DHCP Static Lease in DD-WRT). Reboot everything and test.
Felix:
Quote from: winterescape on November 26, 2011, 06:26:27 am
I think I am back to where I started then assuming it is the router and not wanting to disable my firewall.
So how best to configure my router to keep Obi happy and keep my network computers properly protected?
Note that Callcentric doesn't recommend that you disable your firewall. They only recommend that you disable SPI on your firewall... big difference! ;) Some people argue that SPI doesn't belong in the firewall in the first place; the bottom line - if you disable SPI, all your firewall protection will remain in place.
obi-support2:
On the contrary, I believe that OBiHAI support team has replied to RonR's
"suspected bug report" promptly via email and has suggested that the problem is likely to
be caused by STUN being enabled on his unit.
However we did not get any further confirmation from RonR
whether turning off STUN fixes the issue. We do not believe there is a bug in
RonR's case which we are not able to reproduce.
RonR might have a very unique setup that may not apply to other users.
Navigation
[0] Message Index
[#] Next page
[*] Previous page