IPKall - Calls IN to Obi can hear me but I can't hear them
777funk:
I just setup an Obi100 with callwithus as my outgoing SIP and IPKall (free) as my incoming. If I call OUT from my Obi line, all is well.
However, if I call from a land line IN to my Obi line (the free IPKall Washington State phone number) they can hear me but I cannot hear the person on the other end.
IT seems to be a problem with the Obi configuration because on my softphone configured to the same SIP account (callwithus for outgoing linked to IPKall for incoming) everything works great.
Any tips on how to fix?
I've tried port forwarding on my Router and I've also tried STUN but I'm not sure I was doing it right. I clicked the Enable Stun box then entered the stun address in the box.
hwittenb:
As you know, the CallWithUs FAQ has the following entry about forwarding a DID to your CallWithUs account:
Q. I have my own VoIP DID, can I redirect it to you server via SIP?
A. Yes. If you want to redirect the DID to ring your SIP client registered with our server, set the DID calls forward with your DID provider to username@did.callwithus.com, where username is your 9 digits username. Your SIP client must have STUN enabled or be on a public IP address, we do not handle media and NAT for DIDs from a third party. If you want to redirect the DID to ring your PSTN number using our service or to have additional features provided by our service like caller ID with name, multiple DID destinations or handle NAT issues by our server, we need to know the DID number to enter it to our system as a DID with $0.5 monthly price and $2 setup fee. Set the DID call forwarding with your provider to didnumber@did.callwithus.com that case.
An audio problem where you have one way audio like you describe is usually due to not properly transmitting your external ip address or external port number inside the sip signalling packets, i.e. a NAT problem.
It sounds like you have STUN enabled correctly on the Sip SPX that you have registered to your account at CallWithUs. You can use any STUN server, however callwithus provides this service at stun.callwithus.com. Since this didn't solve the problem I would also try enabling ICE along with STUN. ICE (Interactive Connectivity Establishment) is an additional protocol to alleviate NAT problems and is enabled, like STUN, on the ITSP Profile-->General Tab at X_ICEEnable [check]
When I test my OBi with an IPKall number with my callwithus account it works fine, with or without the addtional STUN and ICE settings but I have a different local network router than you do.
777funk:
Here's what I've got. I tried varying a few things.
Is there anything obviously wrong here:
777funk:
The weird thing here is that my wife's windows softphone (PhonerLite) works great (two way). Obi isn't so fortunate for some reason. I may have to try another ATA if I can't find the problem here. Seems like otherwise the Obi is pretty straight forward. Just this one problem.
carl:
Just put your Obi into DMZ on your router. They will tell you all kinds of stories how dangerous that supposedly is, I do it for nearly 2 years with 2 accounts and no problems ( of course, you use super strong passwords for everything and no automatic balance refill anyway). i had no other choice because my gateway will block VOIP traffic no matter what unless I engage DMZ.
Navigation
[0] Message Index
[#] Next page