Ringback tone for incoming calls

[GoogleCodeExporter]

NOTE: This form is only for reporting bugs. For questions, comments, or
advice please visit:  http://groups.google.com/group/sipdroid-users

*************************************************
* Read the FAQ                                  *
*    Check if the bug has already been reported *
*        No doubles please                      *
*************************************************

Did you carefully read above and decide this means of communication is the
right for your notice? Don't just list an incompatible SIP server or
device, please. Try to look behind the scenes if you like to
contribute here. Thanks!

--
What steps will reproduce the problem?

1. Register phone to VoIP service through pbxes.org
2. Place call from PSTN to VoIP number

What is the expected output? What do you see instead?

One expects the incoming caller to hear the standard ringback tone, but
they hear a different one.  The call itself works fine once it is answered.

What version of the product are you using? On what operating system?

1.0.5 on Android 1.5

Please provide any additional information below.

If I register to the same pbxes account using a softphone on my laptop
instead of sipdroid, the normal ringback tone is heard by incoming callers.

I am located in Canada; perhaps the ringback tone that's being played when
I register with sipdroid is standard in other places, but it isn't standard
here; in fact, it is similar to a busy signal and is certain to confuse
callers.

Thanks to the develops for a great piece of software!

Original issue reported on code.google.com by brent....@gmail.com on 1 Sep 2009 at 6:36

[GoogleCodeExporter]

FWIW, I get this too, using a Moto Droid with Android 2.01. Using Pbxes with a 
Vonage softphone account. Do not know enough about SIP yet to know who is 
generating 
the strange ringback, but it almost sounds like a UK ringback. 

Original comment by david%re...@gtempaccount.com on 23 Dec 2009 at 7:15

[GoogleCodeExporter]

So I found ringback.ogg in the source tree, i.e. it is definitely sipdroid 
generating the ringback tone. Would be great to have the option to choose a 
ringback 
the way we can a ring tone. 

Original comment by david%re...@gtempaccount.com on 23 Dec 2009 at 9:34

[GoogleCodeExporter]

I am in canada also same problem .In coming callers here a slow beep...beep 
instead 
of ring....ring.Freephoneline.ca as VOIP and PBXes.

Original comment by ern...@gmail.com on 5 Jan 2010 at 9:56

[GoogleCodeExporter]

Found this at PBXes .Maybe some VOIP's only use 180?

In general, ringing is controlled via two Informational Responses in SIP: the 
180 
Ringing and the 183 Session Progress.

The main difference between them, is the 180 Ringing message instructs the UA 
to 
create the dial-tone locally, whereas the 183 Session Progress contains an SDP, 
which allows for regional ring-back and carrier announcements as well.

Original comment by ern...@gmail.com on 5 Jan 2010 at 10:14

[GoogleCodeExporter]

Yes, I believe you are correct. So this is not so much of a defect as a feature 
request, i.e. please allow the user to choose whatever sound file they want for 
ringbacks. 

Original comment by rev91770...@gmail.com on 5 Jan 2010 at 10:23

[GoogleCodeExporter]

The problem is that the Sipdroid UA is sending what's called early media by 
including
SDP with the 180 Ringing provisional response (see
http://www.faqs.org/rfcs/rfc3960.html for more info on early media).  This is a 
patch
that adds a config option to shut off early media entirely.

Original comment by erick%ju...@gtempaccount.com on 13 Apr 2010 at 7:31

Attachments:

• early_media.patch

[GoogleCodeExporter]

I've already seen and tested your patch. Unfortunately it made calls did not 
work 
when I chose to disable early media with it. There was no audio at all in the 
call.

Also I believe that a mobile client requires to start media early to adjust 
jitter 
buffers, load all required codecs and stuff, to avoid any latency at the 
beginning of 
calls, after accepting them. Therefore I would prefer not including this patch.

It would be better to make the ringback tone selectable. But this requires the 
code 
to be able to accept all kinds of audio files which are not supported yet in 
the 
code.

Original comment by pmerl...@googlemail.com on 13 Apr 2010 at 2:56

[GoogleCodeExporter]

Issue 483 has been merged into this issue.

Original comment by pmerl...@googlemail.com on 4 Jun 2010 at 3:35

[GoogleCodeExporter]

Issue 383 has been merged into this issue.

Original comment by pmerl...@googlemail.com on 4 Jun 2010 at 3:38

[GoogleCodeExporter]

Issue 466 has been merged into this issue.

Original comment by pmerl...@googlemail.com on 4 Jun 2010 at 3:38

[GoogleCodeExporter]

Issue 533 has been merged into this issue.

Original comment by pmerl...@googlemail.com on 2 Jul 2010 at 11:34

[GoogleCodeExporter]

Issue 383 has been marked as a duplicate of this and although the bug might be 
caused by the same thing the description is not correct.

It's not just a ringback issue as sipdroid is accepting the call so other 
phones in the ring group are no longer ringing.

Original comment by hadley.r...@gmail.com on 30 Aug 2010 at 3:41

[GoogleCodeExporter]

Issue 643 has been merged into this issue.

Original comment by pmerl...@googlemail.com on 17 Sep 2010 at 8:11

[GoogleCodeExporter]

Issue 483 has been merged into this issue.

Original comment by pmerl...@googlemail.com on 13 Feb 2011 at 8:01

[GoogleCodeExporter]

Issue 497 has been merged into this issue.

Original comment by pmerl...@googlemail.com on 13 Feb 2011 at 8:03

[GoogleCodeExporter]

Issue 819 has been merged into this issue.

Original comment by pmerl...@googlemail.com on 13 Feb 2011 at 8:06

[GoogleCodeExporter]

I had been commenting on Issue 819 which has been merged here. While the 
specific situation noted here is clearly presenting itself in a number of 
scenarions (noted by other issues merged in) I think there are actually a 
couple of separate issues of different severity within this one and just want 
to raise the point:

1) SipDroid auto-answers the incoming call (if I understand correctly, this is 
to get early media data to speed up the actual connection). It then passes back 
 the sound of a ringing phone to the caller until the callee actually picks up 
the line. This may have some benefits, but causes a number of problems:
  a) The ringtone inconsistency problem that is the source of this issue (Issue 122)
  b) This screws up multi-line switching systems like Google Voice, as the sipdroid line is connected and all the others stop ringing. As such, it makes such systems quite useless (Issue 383)

I can understand that there may be some benefit to autoanswering the line to 
get connection data, but it does seem like there are a number of use cases in 
which this is a problem. Is there any way to make this an option that can be 
disabled?

2) In some ways, far more serious is that WHEN sipdroid auto-answers the 
incoming line, it then for unclear reasons passes the incoming audio to the 
external speaker, ignoring volume settings (at least ignoring the ringer volume 
setting, may follow the media volume or something)? This is essentially the 
problem in issues 466, 533, 643, 497, and 819. 

This is clearly a bug, and a fairly significant one. I can not imagine an 
actual use case for this, and unfortunately it makes Sipdroid completely 
unusable in many, if not most environments (even if I'm not in a meeting or 
somewhere quiet, I still don't want my phone projecting the incoming callers 
voice around the room). There may be something about the underlying 
architecture that causes these two issue to be linked, but it seems as though 
they are actually fairly separate (though one could assume that if sipdroid 
didn't auto-answer, this wouldn't be a problem).

3) Finally, issue 483 seems to indicate a problem not only with the above, but 
also of turning the mic on and generating feedback. I don't know if that is 
actually the same problem or an entirely different one. 

The problem with all of these (well, #1 and #2 at least) put together is that 
while sipdroid is a spectacular program, between screwing up (in my case) 
google voice, and also projecting sound even in silent mode, it makes sipdroid 
unusable in most situations. As an added bonus, the instant answer seems (for 
unclear reasons) to trigger google voice into call presentation mode regardless 
of what the setting is, so even if a call comes in and the other person would 
have listened to the fake dialtone and not said anything, GV's polite call 
presentation lady's voice is consistently heard loud and clear on my end 
whenever I get a call.

It seems like this problem has been persisting for quite some time, and while I 
by no means am in a position to complain about free software, I would be 
curious as to what is making it so difficult to stamp out given that it seems 
like even an option to not auto-answer would fix it and how much it seems to 
undermine the utility of the program.

Thanks!

Original comment by abkris...@gmail.com on 17 Feb 2011 at 8:53

[GoogleCodeExporter]

coming from issue number 819:

notice the problem via pbxes/gtalk trunk incoming calls. i could hear a brief 
"... press 2" voice before the ring tone starts (or goes to vibrate/silent per 
setting). the voice seems to be coming from google voice call screening, even 
though it is already turned of. this happens even when ring was set to silent. 
does not happen with csipsimple. 

also, with this setup, incoming calls ring only for 10 seconds or so, the 
caller side will keep ringing then eventually goes into VM. sipdroid side just 
drops the connection as if the caller had hangup. same problem with csipsimple 
so it might be pbxes/gtalk trunk related. 

Original comment by bomb...@gmail.com on 14 Mar 2011 at 7:32

[GoogleCodeExporter]

The biggest problem of the early media is the "no incoming audio" problem when 
multiple Sipdroid instances are running behind the same router. When an 
incoming call rings multiple Sipdroid's behind the same router, all Sipdroid's 
are trying to connect to the server's media port from the same IP, and only one 
Sipdroid will get the incoming audio, and the one that does get the incoming 
audio may not be the one that actually answers the call. Out of a number of 
providers I tested, only PBXes.org and another provider would adjust the media 
to the correct phone after the call has being answered. All others failed with 
no incoming audio.

Original comment by jac...@gmail.com on 7 Apr 2011 at 7:15

[GoogleCodeExporter]

I noticed that Sipdroid uses a fixed local RTP port, which makes all instances 
of Sipdroid behind the same router undiscernable of their RTP adddress/port's 
from the view of the outside provider. How about using a random local RTP port 
in a port range? That may help solve the problem I mentioned above (Apr 7). 

Original comment by jac...@gmail.com on 21 Jun 2011 at 6:39

[GoogleCodeExporter]

It is a real issue here. All calls are actually auto answered, yet ringtone 
keeps going on. This issue will be raised to critical. Imagine someone calls 
you to do a prank. Keep saying dirty things before you get to answer the call. 
The audio is being routed to speaker loudly. 

Original comment by steve...@gmail.com on 16 Feb 2012 at 11:05

[GoogleCodeExporter]

I am annoyed by people not recognising that my phone is ringing... when they 
call me all they hear are some uniform blips and don't know what it is and 
often hang up and ring again... it's the kind of noise you'd expect to hear if 
you were on hold... It would be a fix for me if there was a way to change the 
audio file? - again, it only happens on sipdroid, when using other sip devices, 
they hear a normal ring.

Original comment by andah...@gmail.com on 17 Mar 2012 at 9:53

[GoogleCodeExporter]

Please fix Issue 122.  It is impossible to use this app in UK/Ireland if the 
ringing tone is not corrected.  Callers here hear a tone which is the 
equivalent of an engaged/busy tone, not a ringing (ring-ring) tone.  

Original comment by verbumtr...@gmail.com on 7 May 2013 at 6:31

[GoogleCodeExporter]

I agree with comment #23.

I stopped using sipdroid long ago because of this, and was only reminded of it 
because I just received an email alert of a new post (#23).

Original comment by andah...@gmail.com on 7 May 2013 at 6:35

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Several issues have been merged into this one (such as 497, 466). They 
expressed a different problem than the one described in the title of 122.

In my case, I am experiencing the problem described in #497 and #466: Before 
answering an incoming call, the voice of the caller is already been played 
through the rear speaker (hands-free style).

This is very privacy unfriendly, for the caller (who doesn't know that is 
already been heared) and for the person who receive the call (as all the 
surrounding people is able to hear the caller, even before answering the call).

Please, check it out!

Original comment by naje...@gmail.com on 4 Apr 2014 at 12:00

[GoogleCodeExporter]

My sipdroid is connected to PBXes. When it receives a call directly to the 
extension from Blink (mac) or a FritzBox, I hear a ringtone for about one 
second, then a change in sound quality, and finally an extremely loud screaming 
sound. This problem does not occur when the call comes from LinPhone. It also 
does not occur when the call goes to a ring group on PBXes. Apparently either 
PBXes or sipdroid is wise enough not to auto-answer a call to a ring group. 
Apparently sipdroid can live without auto-answering. It would be great if I 
could disable it altogether, so I can call the sipdroid extension internally 
without alarming the neighbours.

Original comment by m...@potse.nl on 9 Jan 2015 at 10:23

[GoogleCodeExporter]

PS to my previous comment (#27): this was with sipdroid 3.6 on a Galaxy S4 
Active with Android 4.4.2 

Original comment by m...@potse.nl on 9 Jan 2015 at 10:33