__color__,ticket,summary,component,version,milestone,type,owner,status,created,_changetime,_description,_reporter
3,56,osmo-bts: hand-over support is incomplete,osmo-bts,,,defect,laforge,new,2012-05-25T21:20:37+0200,2012-05-25T21:36:12+0200,"osmo-bts currently doesn't have hand-over support in L3, though it should be really simple to add.",laforge
3,58,osmo-bts: A5/3 and A5/2 are not tested yet,osmo-bts,,,defect,laforge,new,2012-05-25T21:22:14+0200,2012-05-25T21:22:14+0200,"So far, only A5/1 encryption has been tested.",laforge
4,57,"sysmobts L1 is not properly closed, DSP firmware reload is required",osmo-bts,,,defect,laforge,new,2012-05-25T21:21:32+0200,2012-05-25T21:21:32+0200,We should investigate what is not properly closed and try to make it work again without requiring DSP firmware reload before osmo-bts restart,laforge
4,62,osmo-bts: Avoid having to specify rtp local bind IP in config file,osmo-bts,,,defect,laforge,new,2012-05-25T21:33:53+0200,2012-05-25T21:33:53+0200,It's a bit cumbersome to have to specify the local IP address to which sockets shall bind.  This will especially cause problems if a BTS were to use dynamically allocated/changing IP addresses.,laforge
4,59,osmo-bts: use one manager thread per lchan,osmo-bts,,,enhancement,laforge,new,2012-05-25T21:28:02+0200,2012-05-25T21:28:02+0200,"Using one manager thread for each lchan will allow us to have blocking semantics in a series of events like L1 SAPI activation/deactivation sequences.

The threads would be sleeping almost all the time and only become active upon OML timeslot reconfiguration or RSL channel activation/deactivation.",laforge
4,60,osmo-bts: Start to use libosmo-abis/libosmo-netif,osmo-bts,,,enhancement,laforge,new,2012-05-25T21:29:06+0200,2012-05-25T21:29:06+0200,"There still is some ""private""/custom code regardin Abis/IP in osmo-bts that needs to be replaced with the generic implementation available in our librarires",laforge
4,61,osmo-bts: split TRAU/RTP frame handling into separate process,osmo-bts,,,enhancement,laforge,new,2012-05-25T21:32:44+0200,2012-05-25T21:32:44+0200,"it would be great to only deal with signalling inside the osmo-bts process, pushing all RTP/TCH handling into a separate process similar to a media gateway.

The main process then just sends control commands to the RTP/TCH process, particularly once the BSC instructs us to change/bind/connect the RTP socket related settings.

Our sysmobts L1 can already put the TCH related messages into a separate queue, keeping control with the main queue.",laforge