hluesea / sipdroid

Automatically exported from code.google.com/p/sipdroid
GNU General Public License v3.0
0 stars 0 forks source link

on outbound calls - no ringback & unless called party picks up quickly, the call fails #460

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Sipdroid/1.4.7 beta/ADR6300 (HTC Incredible)

When placing an outbound call, I do not hear ringback - just a horrible
noise - sounds like high-pitched electrical noise.  If the called party
picks up quickly, the call completes.  See
sipdroid_callcomplete_noringback.pcap

If the called party doesn't pick up after 1 or 2 rings, Sipdroid closes out
the call screen (but still reports an active call in the notification bar).
 The called party phone cannot answer the call when in this state because
Sipdroid does respond to 200 OK (or BYE).  I have to force close Sipdroid
to "end" the call from Sipdroid's perspective. See
sipdroid_callfailure_noringback.pcap

Original issue reported on code.google.com by ryan.rev...@gmail.com on 14 May 2010 at 2:50

Attachments:

GoogleCodeExporter commented 9 years ago
HTC Incredible
SipDroid 1.5.2 (beta)
3CX PABX Software, V8

I have this same exact issue, TCP or UDP, WiFi/NAT between phone and 3CX, and 
3G as well, using STUN. The high-pitched electrical noise (good description) is 
the indicator that the problem will happen. 

It doesn't happen when I call our IVR (which picks up immediately) or an 
outside number via our SIP to PSTN provider (I hear ringback from that). It 
only happens when I call another extension on our PBX, and if the other 
extension doesn't pick up within a second or two. I hear the squealing instead 
of the ringback.

I apologize not to have packet traces, I will try to get some. 

I should note that at least for me, the called party CAN answer after SipDroid 
abandons the call. The other phone acts like the call is connected, just no 
audio. As the original poster points out, SipDroid is not sending the BYE, it 
is just abandoning the call mid-way in a nonconformant way. And like the 
original poster, it leaves the "call in progress" notification in the bar. I 
found I could clear it up without killing SipDroid - just place another call 
and hang up after it completes.

Original comment by dc3de...@gmail.com on 30 Jun 2010 at 7:05