<div dir="ltr"><div><div><div><div><div>Hi list,<br><br><br></div>Peter, thank you for your reply.<br><br></div>I still have questions about media control:<br><br></div>1) when parsing MGCP CRCX, sdp is not expected. May I change it?<br>
<br></div>2) I still can't run media in BSC mode. Seems I'm missing something.<br></div><div>osmo-bsc and osmo-bsc_mgcp are running<br></div><div>BSSAP works perfectly<br></div><div>But it seems two interfaces are working completely independent:<br>
</div><div>-- MGCP between MSC and BSC<br></div><div>-- interface between BSC and BTS (ip.access):<br></div><div>at MGCP, connection is acknowledged, endpoint is allocated (at BSC ip=192.168.1.11)<br></div><div>at ip.access interface between BSC and BTS, BTS replies to ip.accessCRCX with proper acknowledgement with proper ip:port at BTS (192.168.1.9) , then BSC issues ip.accessMDCX with endpoint ip zero:<br>
7e:73:01:09:f8:00:2d:<b>f0:00:00:00:00</b>:f1:0f:be:f4:00:f2:03<br></div><div>My attempts to modify connection at MGCP interface has no impact on ip.access interface<br><br></div><div>The key question, I'm not getting how osmo-bsc and osmo0bsc_mgcp are interacting.<br>
<br></div><div>Thank you,<br></div><div>Dmitri<br></div><div><br></div><div>PS my configs are<br>mgcp<br> local ip 192.168.1.11<br> bts ip 192.168.1.9<br> bind ip 192.168.1.11<br> bind port 2427<br> rtp base 6000<br>
sdp audio payload number 3<br> sdp audio payload name GSM/8000<br> number endpoints 31<br></div><div>and<br><br>e1_input<br> e1_line 0 driver ipa<br>network<br> network country code 250<br> mobile network code 07<br> short name OsmoBSC<br>
long name OsmoBSC<br> auth policy closed<br> location updating reject cause 13<br>! encryption a5 1<br> neci 1<br> paging any use tch 0<br> rrlp mode none<br> mm info 1<br> handover 0<br> handover window rxlev averaging 10<br>
handover window rxqual averaging 1<br> handover window rxlev neighbor averaging 10<br> handover power budget interval 6<br> handover power budget hysteresis 3<br> handover maximum distance 9999<br> timer t3101 10<br> timer t3103 0<br>
timer t3105 0<br> timer t3107 0<br> timer t3109 0<br> timer t3111 0<br> timer t3113 60<br> timer t3115 0<br> timer t3117 0<br> timer t3119 0<br> timer t3122 0<br> timer t3141 0<br> dtx-used 0<br> subscriber-keep-in-ram 0<br>
bts 0<br> type nanobts<br> band PCS1900<br> cell_identity 2611<br> location_area_code 51601<br> training_sequence_code 7<br> base_station_id_code 63<br> ms max power 15<br> cell reselection hysteresis 4<br> rxlev access min 0<br>
channel allocator ascending<br> rach tx integer 9<br> rach max transmission 7<br> ip.access unit_id 1801 0<br> oml ip.access stream_id 255 line 0<br> neighbor-list mode manual-si5<br> gprs mode none<br> trx 0<br>
rf_locked 0<br> arfcn 810<br> nominal power 0<br> max_power_red 20<br> rsl e1 tei 0<br> timeslot 0<br> phys_chan_config CCCH+SDCCH4<br> hopping enabled 0<br> timeslot 1<br> phys_chan_config TCH/F<br>
hopping enabled 0<br> timeslot 2<br> phys_chan_config TCH/F<br> hopping enabled 0<br> timeslot 3<br> phys_chan_config TCH/F<br> hopping enabled 0<br> timeslot 4<br> phys_chan_config TCH/F<br>
hopping enabled 0<br> timeslot 5<br> phys_chan_config TCH/F<br> hopping enabled 0<br> timeslot 6<br> phys_chan_config TCH/F<br> hopping enabled 0<br> timeslot 7<br> phys_chan_config TCH/F<br>
hopping enabled 0<br>msc<br>! ip.access rtp-base 6000<br> timeout-ping 20<br> timeout-pong 5<br> dest 192.168.50.10 5000 0<br><br></div><div>in fact, BSSAP goes from a card over VPN, while MGCP comes from self-written TRAU running locally, the same host as BSC<br>
<br><br></div></div>