osmo-bsc/af603c74b931d53ae078f106e39...

38 lines
1.2 KiB
Plaintext

{
"comments": [
{
"key": {
"uuid": "9aa7fdbe_35793894",
"filename": "README",
"patchSetId": 2
},
"lineNbr": 18,
"author": {
"id": 1000004
},
"writtenOn": "2017-09-05T10:41:50Z",
"side": 1,
"message": "as you mention OsmoMSC above, one could mention OsmoBTS here",
"revId": "af603c74b931d53ae078f106e39db5a98ef03a69",
"serverId": "035e6965-6537-41bd-912c-053f3cf69326",
"unresolved": false
},
{
"key": {
"uuid": "9aa7fdbe_556ebcca",
"filename": "README",
"patchSetId": 2
},
"lineNbr": 25,
"author": {
"id": 1000004
},
"writtenOn": "2017-09-05T10:41:50Z",
"side": 1,
"message": "It\u0027s not about RTP streams. It\u0027s about aggregating many (e.g. hundreds of) A interfaces from many (Osmo-)BSC into one A link to the MSC, so the MSC doesn\u0027t need to be configured with lots of A links/interfaces. This includes signaling and media handling, but it\u0027s not specifically related to RTP.",
"revId": "af603c74b931d53ae078f106e39db5a98ef03a69",
"serverId": "035e6965-6537-41bd-912c-053f3cf69326",
"unresolved": false
}
]
}