Feature #2281
closedallow multiple MGCP-GW per MSC
0%
Description
In the 3G implementation so far, the OsmoMSC has one MGCP-GW configured; there cannot be more (yet). In the AoIP 2G picture so far, the idea is to have one MGCP-GW per OsmoBSC. It is probably faster and simpler to go for the topology of one MGCP-GW per MSC rather than BSC. But is that sufficient?
If one per MSC, tell the BSC where its MGCP-GW is (vty config?)
If one per BSC, implement a way how the MSC keeps several MGCP-GW peers and knows which BSC needs which MGCP-GW. Also needed for Iu connections.
Related issues
Updated by neels almost 7 years ago
- Related to Feature #2289: implement AoverIP (OsmoMSC side) added
Updated by dexter almost 7 years ago
I do not see any problem here so far. There might be some pitfalls with several MGCPGW instances on the same machine (VTY-Ports etc...).
Each BSC will have one MGCPGW. However, the MSC will not be aware of that. It will send the IP/Port of its own MGCPGW via the assignment command to the BSC. The BSC will then negotiate that IP/Port to its private MGCPGW. The IP/Port which is returned then is handed back to the MSC via the assignment complete message. The MSC will have to connect that IP/Port combination then with its own MGCPGW. In parallel, the BSC will connect the BTS via IPACC to the other side of its private MGCPGW.
From the topological perspective, the private MGCPGW of the BSC is invisible to the MSC. The only difference will be that the MSC side of the network will transmit its RTP streams with the MGCPGW of the BSC instead with the BTS directly.
Updated by laforge over 6 years ago
- Status changed from New to Rejected
I agre with dexter here, not sure why the MSC would care at all if there are MGW's at the BSC or not. This is unrelated to the fact of the MSC having (and controlling) a MGW itself.
