Open GoogleCodeExporter opened 8 years ago
I have the same problem. Did you solve this issue?
Original comment by rafaelf...@gmail.com
on 25 Jun 2009 at 2:57
Seems like I'm hitting also the same problem. Are you running on Linux/Ubuntu?
For me, everything works fine when Red5 is on Windows. But when I move it to
Ubuntu,
REGISTER works but when I make a call I get the following,
====
SIPUser register
RegisterAgent: Registering contact <sip:3000@127.0.0.1:5070> (it expires in
3600
secs)
RegisterAgent: Attempt to set renew time above original renew. Attempted=3600
origrenew=600
Response=SIP/2.0 200 OK
Via: SIP/2.0/UDP
127.0.0.1:5070;branch=z9hG4bK34861;received=192.168.0.184;rport=5070
From: "Richard Test" <sip:3000@192.168.0.184>;tag=z9hG4bK85257171
To: "Richard Test" <sip:3000@192.168.0.184>;tag=as6bdc5114
Call-ID: 239382910682@127.0.0.1
CSeq: 1 REGISTER
User-Agent: Asterisk PBX
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Supported: replaces
Expires: 3600
Contact: <sip:3000@127.0.0.1:5070>;expires=3600
Date: Fri, 26 Jun 2009 14:44:25 GMT
Content-Length: 0
RegisterAgent: Registration success:
SIP Registration success 200 OK
SIPUser Calling 600
RTMPUser startStream
[DEBUG] [NioProcessor-1] org.red5.server.net.rtmp.BaseRTMPClientHandler -
connect
server: localhost port 1935 application sip connectCallback
org.red5.server.webapp.sip.RTMPUser@1497b1
[DEBUG] [NioProcessor-1] org.red5.server.net.rtmp.BaseRTMPClientHandler -
connect
server: localhost port 1935 connectionParams {objectEncoding=0, app=sip,
flashVer=WIN 9,0,115,0, fpad=false, tcUrl=rtmp://localhost:1935/sip,
audioCodecs=1639, videoFunction=1, pageUrl=null, path=sip, capabilities=15,
swfUrl=null, videoCodecs=252} connectCallback
org.red5.server.webapp.sip.RTMPUser@1497b1 conectCallArguments null
===
600 is my echo test application....I just hear ringing but on my Asterisk
console, I
can't see the call coming in.
It seems that Red5 hangs when the RTMPClient tries to connect back (loopback)
into
the sip application.
After a while, Red5 disconnects the RTMPConnection...
====
[WARN] [Red5_Scheduler_Worker-11] org.red5.server.net.rtmp.RTMPConnection -
Closing
RTMPMinaConnection from 192.168.0.199 : 63374 to 192.168.0.184 (in: 3590 out
3370 ),
with id 15164472, due to too much inactivity (60999ms), last ping sent 1000ms
ago
[INFO] [Red5_Scheduler_Worker-11]
org.red5.server.adapter.MultiThreadedApplicationAdapter - W3C
x-category:session x-
event:disconnect c-ip:192.168.0.199 c-client-id:0
SIPUser close1
SIPUser hangup
SIPUser closeStreams
RTMPUser stopStream
[DEBUG] [Red5_Scheduler_Worker-11]
org.red5.server.net.rtmp.BaseRTMPClientHandler -
disconnect
SIPUser unregister
RegisterAgent: Unregistering contact <sip:3000@127.0.0.1:5070>
[DEBUG] [NioProcessor-2] org.red5.server.net.rtmp.BaseRTMPClientHandler -
connectionClosed
RegisterAgent: Registration success:
SIP Registration success 200 OK
SipUserAgent - hangup -> Init...
SipUserAgent - closeMediaApplication -> Init...
SIPUser provider.halt
=====
And Red5 server hangs/dies...can't connect any client to it anymore.
Anybody care to share there experiences/findings?
Original comment by ritza...@gmail.com
on 26 Jun 2009 at 3:06
I'm running on Open SUSE Linux, but on Windows it works fine.
Original comment by rafaelf...@gmail.com
on 26 Jun 2009 at 8:20
I rebuilt Red5 and Red5Phone on Linux SUSE and Ubuntu, but I'm still facing this
problem.
Original comment by rafaelf...@gmail.com
on 3 Jul 2009 at 6:30
I think the problem is here starting in line 142 of RTMPUser
try {
connect( host, port, app, this );
//while ( !startPublish ) {
// Thread.yield();
//}
}
catch ( Exception e ) {
logger.error( "RTMPUser startStream exception " + e );
}
There is no need to wait anymore after a connect.
Original comment by olajide....@gmail.com
on 11 Jul 2009 at 10:05
Original issue reported on code.google.com by
liweisp...@gmail.com
on 2 May 2009 at 4:37Attachments: