search

dizag / red5phone

Automatically exported from code.google.com/p/red5phone
1 stars 0 forks source link

Sound interrupts for some seconds when another client logs in #143

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Hi!
I have a problem with red5phone from sip_47 archive.

It's working perfectly, sound is good, but I have one problem:

1. Let's say i call through red5phone to answering machine. I hear sound, it's 
good.
2. When I'm listening to the sound another red5phone is connecting to red5. 
Exactly at this time my sound interrupts for some seconds and I see [SipUser] 
provider.halt message.

Please help!

Original issue reported on code.google.com by ukeb...@gmail.com on 21 Mar 2011 at 9:12

GoogleCodeExporter commented 8 years ago 
I was wrong a bit in describing the situation.

Here is the scenario to reproduce the bug:

1. Open red5phone in 1st browser window and place a call to somewhere (for 
testing answering machine is better).
2. While listening the voice  open another window with red5phone and register 
to the same server.
3. [b]Reload second window[/b] (or just close it) and the sound coming from the 
first red5phone window interrupts for some seconds. After that it continuous 
normally.

Here is red5 output after reloading second window:

Red5SIP Client leaving app 16
Red5SIP Client closing client 0AEC124B-F9C9-74CC-D6D8-D95A2856EA0B
Release ports: sip port 5090 audio port 3020
Release port number:5090
Release port number:3020
[SIPUser] close1
[SIPUser] hangup
[SIPUser] closeStreams
RTMPUser stopStream
[ERROR] [NioProcessor-1] org.red5.server.webapp.sip.RTMPUser - RTMPUser 
stopStream exception java.lang.NullPointerException
[SIPUser] unregister
RegisterAgent: Unregistering contact <sip:red5@192.168.1.240:5090>
SipUserAgent - hangup -> Init...
SipUserAgent - closeMediaApplication -> Init...
RegisterAgent: onTransFailureResponse start:
RegisterAgent: onTransFailureResponse 401 or 407:
RegisterAgent: Registration success:
[SIPUser] SIP Registration success 200 OK
[SIPUser] provider.halt

Original comment by ukeb...@gmail.com on 21 Mar 2011 at 5:01

GoogleCodeExporter commented 8 years ago 
Seems i have fixed this bug.
I have commented strings
// new Thread().sleep(3000);
and 
// sip_provider.halt();
in SIPUser class, function close()

I still don't know what exactly interrupts the sound, but with this fix it's 
working smoothly.

If anybody can explain what that strings do i'll be very grateful.

Original comment by ukeb...@gmail.com on 23 Mar 2011 at 3:29

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
I have replied in 144 issue:
http://code.google.com/p/red5phone/issues/detail?id=144&sort=-id

Original comment by ukeb...@gmail.com on 4 Apr 2011 at 7:49

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
...we are experiencing exactly the same issue using the sip_r54 release.
What is the reason to sleep all the threads for 3 seconds??

I think this is a major issue to be fixed as soon as possibile.
Could anybody explain what is the purpose of the following code lines in the 
Red5 SIP Stack?

new Thread().sleep(3000);
and 
sip_provider.halt();

Thank you in advance for any clarification and support...

Original comment by gosma...@gmail.com on 4 Nov 2011 at 8:08

GoogleCodeExporter commented 8 years ago 
Some updates from my experience...

1. The real problem is at
org/zoolu/sip/provider/SipProvider.java

Sound interrupts when it tries to halt tcp_server.
If we are using udp transport, we can comment starting and stopping tcp 
transport.

2. The second problem is too big delay in new Thread().sleep(3000);
200 would be more than enough, and with this value there's no sound 
interrupting.

Original comment by ukeb...@gmail.com on 5 Nov 2011 at 6:17