Attention is currently required from: osmith, neels, fixeria. pespin has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-gsm-manuals/+/29353 )
Change subject: osmux: Use local/remote CID terminology ......................................................................
Patch Set 2:
(4 comments)
File common/chapters/osmux/mgcp_extension_osmux.adoc:
https://gerrit.osmocom.org/c/osmo-gsm-manuals/+/29353/comment/5baaa7bf_a020b... PS1, Line 46: original _remote CID_ sent during `CRCX`. The same way, all `MDCX` response shall
"MGW's remote CID" to clarify beyond doubt ... […]
Ack
https://gerrit.osmocom.org/c/osmo-gsm-manuals/+/29353/comment/fd069275_5f81c... PS1, Line 75: MGW's <<remote CID>>
if this was recvCID before, it should now either be MGW's local CID or peer's remote CID according t […]
Ack
https://gerrit.osmocom.org/c/osmo-gsm-manuals/+/29353/comment/7c64c9fe_65c62... PS1, Line 75: .Example: response to `CRCX` containing the MGW's <<remote CID>>
are you sure a space in a reference link works? […]
This was using wrong formatting to start with. I'll fix.
File common/chapters/osmux/osmux.adoc:
https://gerrit.osmocom.org/c/osmo-gsm-manuals/+/29353/comment/61e7f3ef_9dddb... PS1, Line 55: send Osmux frames the
still unresolved
I think it is resolved but you looked at the old version?
-
pespin