macielbombonato / bigbluebutton

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

bbb-voip should close socket properly or re-use sockets #744

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
After 11 days, the demo server isn't able to connect to Asterisk.

The problem is that bbb-voip isn't able to bind to a local port. It's either 
because we are not closing it properly or the OS is holding it long. I suspect 
the first one.

We should enhance bbb-voip to create a pool of sockets. Once it uses a socket, 
it puts the socket into the pool and reuse it. If all the sockets in the pool 
is being used, then it should try to create a new socket and put it into the 
pool.

2010-11-17 13:08:00,310 [NioProcessor-1] DEBUG o.b.voiceconf.red5.Application - 
VoiceConferenceApplication roomJoin[7378]
2010-11-17 13:08:00,355 [NioProcessor-1] DEBUG o.b.voiceconf.red5.Service - 
Joining voice conference 78749
2010-11-17 13:08:00,355 [NioProcessor-1] DEBUG o.b.voiceconf.sip.CallAgent - 
call 78749
2010-11-17 13:08:00,356 [NioProcessor-1] ERROR o.b.voiceconf.sip.CallAgent - 
Failed to setup local audio socket.
2010-11-17 13:08:00,356 [NioProcessor-1] ERROR o.b.voiceconf.sip.CallAgent - 
Failed to setup local audio socket.
2010-11-17 13:08:00,356 [NioProcessor-1] ERROR o.b.voiceconf.sip.CallAgent - 
Failed to setup local audio socket.
2010-11-17 13:08:00,356 [NioProcessor-1] DEBUG o.b.voiceconf.sip.CallAgent - 
notifyListenersOnOutgoingCallFailed for 7378
2010-11-17 13:08:00,356 [NioProcessor-1] DEBUG 
o.b.voiceconf.red5.ClientConnection - onOutgoingCallFailed
2010-11-17 13:08:07,874 [NioProcessor-1] DEBUG o.b.voiceconf.red5.Application - 
VoiceConferenceApplication roomLeave[7377]
2010-11-17 13:08:07,874 [NioProcessor-1] DEBUG o.b.voiceconf.red5.Application - 
Red5SIP Client closing client 7377

Original issue reported on code.google.com by ritza...@gmail.com on 17 Nov 2010 at 2:31

GoogleCodeExporter commented 9 years ago
Restarting Red5 fixes the problem which means we are not releasing the sockets 
properly.

Original comment by ritza...@gmail.com on 17 Nov 2010 at 3:36

GoogleCodeExporter commented 9 years ago
Is this fixed in 0.8?  (If not, we can defer it, but not sure if we've changed 
this implementation).

Original comment by ffdixon@gmail.com on 28 Mar 2012 at 3:01

GoogleCodeExporter commented 9 years ago
we have a range of ports and search for available port.

Original comment by ritza...@gmail.com on 28 Mar 2012 at 3:30