STUN issues

(1/2) > >>

xibai:
Hi, I am using callwithus. I have the same problem as descried by slicemaster in his/her 1/8/2012 post (http://www.obitalk.com/forum/index.php?topic=2242.msg14242#msg14242) and 1/10/2012 post (http://www.obitalk.com/forum/index.php?topic=2254.msg14359#msg14359): SIP account is registered and I can call regular telephone numbers through OBI110 and Obi100 but there is no audio at all or one way audio when calling other callwithus' internal numbers. The registration status on callwithus' website shows it is behind "NAT." I have other VOIP adapters which works well with callwithus showing "no NAT."

Just wonder how slicemaster solved the problem.

RonR:
Have you tried connecting the OBi directly to the modem to see if the router appears to be a contributor to the problem?

xibai:
It is connected directly to the router. I used to have a ASUS Router n13u and I have recently changed to a new router LINKSYS E3000. Still have the problem.

RonR:
I was suggesting temporarily bypassing any router and connecting the OBi directly to your modem to see if the problem goes away.  If it doesn't, you've eliminated the router as a possible source of the the problem.  If the problem goes away, it's likely a router/NAT issue.

After making the direct connection, power-cycle both the modem and the OBi.

xibai:
Thanks, I will try.

FYI: as slicemaster said in his posts, I also tried following setting:

note: the only setting I took off of default pertaining to stun is the:
STUNEnable
STUNServer
X_STUNServerPort

As suggested by Stewart, I also tried setting X_SymmetricRTPEnable.

Still no working. Now I will try to connect it without the router.

Navigation

[0] Message Index

[#] Next page