Hi Harald
Thank you for a letter.
as for
intra-
BSC handover, there could be 2 ways:
- process them as inter-
BSC. I'm pretty sure that in 2003
ip.access followed this way, as both
nanoBTS involved were connected to a single
BSC, and it was a gateway that processed handover
- use
osmo-
bsc_
mgcp as it was originally desired
It doesn't make much difference: minor changes in transcoder control, as MGCP logic was just reduced.
Meantime if the second way is chosen, I'll face the old problem again: I could not get how the endpoint from
BTS is delivered to
osmo-
bsc_
mgcp, and why it is lost in the particular deployment
I'll appreciate your vision of codec management: reasons for keeping it at BSC side (and some key/example how to configure them), or permission to reduce this logic.
If there is a demand to interact with a particular inflexible MSC, I would offer to filter out unsupported codecs in assignment procedure, keeping a single control point/decision maker
Best Regards,
Dmitri