IPKall - Calls IN to Obi can hear me but I can't hear them
777funk:
I just ran into another problem. I call forked to my cell (android) and it's ringing now which is great!
But I can't transmit voice either direction. Any ideas what this could be?
...by the way Carl, I tried the DMZ mode and no change. Actually I bypassed the router completely without any change. Seems to be a setting or issue with the obi.
hwittenb:
It sounds like you are doing the right things. I would run a detailed syslog on an incoming test call to see the packet detail of the sip signalling on the call to see if that gives any clue on what is going wrong. You are having problems starting up the voice rtp packet stream.
To run a detailed syslog you download and install a syslog program on a local pc. On the OBi's System Management --> Device Admin Tab you put the local network address for your pc running the syslog program in the Server box. The Syslog level should be the highest ... 7. On the Voice Services --> SPx Service Tab you set X_SipDebugOption to "Log All Messages"
The following OBi thread has a simple Windows pc Syslog program that you could download:
http://www.obitalk.com/forum/index.php?topic=707.0
As the thread indicates you can startup the program with the following Syslogd.bat. The program stores a log file on the pc's hard drive.
Syslogd.bat
syslogd -nl -s=all
777funk:
I have a log from the folks at IPKall, however I'm not sure how much of it should be posted publicly since it has some sensitive data (IP addresses, and SIP numbers). There'd probably need to be a lot of blanking out.
azrobert:
You can try pointing IPKall directly to your OBi bypassing CallWithUs.
Use "anything@xx.xx.xx.xx:5060" as the destination in IPKall where xx.xx.xx.xx is your public IP address.
I got my IPKall number to work without Stun or ICE. I had to port forward the RPT ports to the OBi.
hwittenb:
You could also take callwithus up on their 50c/month offer
"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."
and see if they solved your problem.
Navigation
[0] Message Index
[#] Next page
[*] Previous page