Hello all,
We trying to bring up set of BTS with virtual Um with different configurations:
1 BTS -> 1 TRX -> 1 MS works fine as expected
1 BTS -> 1 TRX -> 2 MS works fine as well
But I see some unpredictable behaviour when I have
1 BTS -> 2 TRX(872,873) -> 1 MS
MS can attach on one ARFCN (872) but when it tries to attach on 873
looks like PRACH does not reach BTS and I do not see Channel Request
on BSC side.
So, the question is it workable configuration:
Several TRX to 1 MS with different power level to allow MS to choose a
best cell to attach?
I have just one idea: to have several virtphy instances for MS
connected to different UDP ports.
Thank you
Vania
Hi All,
I was again looking at advancing with LCLS support.
I've made a couple of proposals, which at least get it to the stage
where the global call reference it consistent from the A leg to B leg of
a call, with both the internal mncc and external, and therefore
osmo-bsc can make use of either the lcls-mode (mgw|bts)-loop.
The implementation in the osmo-sip-connector doing nothing more than
passing the GCR from leg to leg, but it's more complicated than this.
We need to allow the PBX to have the audio streams until the PBX itself
decides to remove itself from the stream. (as it is you won't even hear
ringback)
I know all this is spec-ed somewhere in LCLS, I'm just not sure
where/how this SIP re-INVITE processing should be implemented, in the
sip conn, or the MSC - which I guess, takes us back again to neels' long
standing proposals for parsing SDP inside the MSC. Maybe it' s time to
get that merged.
Anyway.. I have some time scheduled to try to move this forward towards
a definitive solution, just writing here in case anyone else can help.
Thanks.
k/
