kevindiffily / google-voice-sipsorcery-dialplans

Automatically exported from code.google.com/p/google-voice-sipsorcery-dialplans
0 stars 0 forks source link

Audio issues #63

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
i am currently using an ipad runing fring to connect to sip gate to sip sorcery 
to google voice. everything is connecting fine. i have the simple dial plan 
running because i dont have a giz 5 account. but when i call in either 
direction there is about a 2 second lag in the voice. i am an extreme noobie to 
this because i just set it up about an hour ago. if anyone has any help or 
needs more info please comment so we can help each other out

Original issue reported on code.google.com by freetest...@gmail.com on 15 Jun 2010 at 4:57

GoogleCodeExporter commented 9 years ago
Fring is bridging media, that's why you're experiencing delays. If you take a 
look at the diagram here:

http://www.fring.com/fring_is/how_fring_works/

you'll see that your Fring client connects to Fring server which in turn 
connects to SIP providers (Sipsorcery, etc). As always, it's a package deal. 
Fring uses proprietary protocol between the client (your iPad) and their 
server; this protocol is compressing data and often works on a very slow 
connections (where everything else fails). On the other hand, compression means 
"worse quality" and bridging (retransmission of voice data with protocol 
conversion on the way) means extra delays.

Which is why I prefer to use a "native" SIP client if bandwidth is not a factor.

Original comment by mte...@gmail.com on 15 Jun 2010 at 2:54

GoogleCodeExporter commented 9 years ago
i also tried using Weephone and Whisle and the delay is still there. and what 
exactly do you mean by "native" SIP client? 

Original comment by freetest...@gmail.com on 15 Jun 2010 at 5:21

GoogleCodeExporter commented 9 years ago
A 'native' SIP client is the one that works with SIP protocol directly. As far 
as I can judge, Weephone is the "native".

If it's not bridging, it must be your network connection. Have you checked ping 
to sipgate.com? If not, you should!

http://itunes.apple.com/us/app/nettools/id297964828?mt=8

Or, if you have a regular PC on the same connection, check ping time from 
there. I guess it's so big that you didn't notice much difference between Fring 
and Weephone...

Original comment by mte...@gmail.com on 15 Jun 2010 at 5:47

GoogleCodeExporter commented 9 years ago
well i tried my home wifi network and the ATT 3G network and noticed no 
difference whatsoever. is there any possibility that there is something I set 
up wrong inside of one of the sip services that could cause this delay in time?

Original comment by freetest...@gmail.com on 15 Jun 2010 at 8:42

GoogleCodeExporter commented 9 years ago
I really doubt that. Sipsorcery does not interfere in RTP path and therefore, 
can't cause the lag. So, it must be either Google Voice or Sipgate but I 
haven't heard of them causing any substantial delays.

Do you have a PC connected to your home WiFi? If yes, try to call using one of 
a proven softphones e.g. X-Lite.

Original comment by mte...@gmail.com on 16 Jun 2010 at 3:45

GoogleCodeExporter commented 9 years ago
i have tried that and the same.i think im going try and set up new accounts. i 
will post the report back tomorrow.

Original comment by freetest...@gmail.com on 16 Jun 2010 at 3:57

GoogleCodeExporter commented 9 years ago
Oh, it's an overkill. I'd check call legs one-by-one. First, try initiating a 
call from GV website and use some regular telephone (e.g. your cell) for 
callback. If there's no delay, everything is okay with GV.

Second, try checking your Sipgate connection. Register Weephone to Sipgate 
directly and try calling some free destination (use free minutes you got with 
Sipgate account, or 1-800-444-4444 or any other toll-free number). Most 
certainly that you'll face with delays at this point.

If so, you may want to replace Sipgate with some other DID (say, from IPKall) 
and check if this helps.

Original comment by mte...@gmail.com on 16 Jun 2010 at 9:35

GoogleCodeExporter commented 9 years ago
Sorry for the delay in responding, really busy day. I didnt have much time to 
play with it but here are some results. When calling from GV website it calls 
the SIP number and i pick it up. Then it calls a regular phone (my house 
phone). The delay is still there. Then i attempted setting Weephone to to 
Sipgate directly and i had problems. What I did was set the username and 
password and put the server to sipgate.com and restart the app. All it does is 
respond with "logged in: no". So im guessing that there is some other way to 
log in? And also do you have any ideas on having the iPad ring when the app is 
not open?

Original comment by freetest...@gmail.com on 17 Jun 2010 at 5:22

GoogleCodeExporter commented 9 years ago
I don't have the iPAD and can't help you with the Weephone. If I was you, I'd 
probably experiment with desktop/laptop connected to the same home WiFi network.

Sipgate should have instructions on how to configure softphone to connect to 
their server. All you need is just follow their instructions ;-)

Original comment by mte...@gmail.com on 17 Jun 2010 at 6:29

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
I just registered sipgate to a softphone on my laptop and the delay was still 
there. so i guess that sip gate is the problem. Do you know of any other free 
services like sipgate that hand out free numbers?

Original comment by freetest...@gmail.com on 17 Jun 2010 at 5:05

GoogleCodeExporter commented 9 years ago
You can try http://phone.ipkall.com/ or 
http://www.ipcomms.net/product-freedid.html (I deliberately posted full URL 
because it's hard to find Free DID on IPCOMMS website ;-)

Good thing about IPKall is that getting their DID is fast and easy. Bad thing: 
their DID are often returning the number of local termination instead of real 
caller ID. So, IPKall is good for outbound calls but for the inbound I'd 
recommend IPCOMMS.

IPCOMMS DID is harder to get and configure but they are good for both in and 
out calls.

Original comment by mte...@gmail.com on 17 Jun 2010 at 6:35

GoogleCodeExporter commented 9 years ago

Original comment by easter...@gmail.com on 24 Jun 2010 at 1:09

GoogleCodeExporter commented 9 years ago
Closing due to inactivity. No issue with scripts found, only audio issues due 
to network connectivity.

Original comment by easter...@gmail.com on 8 Feb 2011 at 2:20