This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Manuals for Osmocom GSM components".

The branch, master has been updated
       via  3bcb9f4c151205a743162eb740f77d9b6dfaa2b1 (commit)
       via  e62d414c0cd3ce8068e99e299b5c5065e59ae1f3 (commit)
      from  bbfb0c33ef7a4c75219c01c5101245698baeee12 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
http://cgit.osmocom.org/osmo-gsm-manuals/commit/?id=3bcb9f4c151205a743162eb740f77d9b6dfaa2b1

commit 3bcb9f4c151205a743162eb740f77d9b6dfaa2b1
Author: Harald Welte <[email protected]>
Date:   Tue Jul 11 17:42:04 2017 +0200

    Add Message Sequence Chart for MO call with ext. MNCC in OsmoMSC
    
    We simply talk to the MGW instead of the BTS, everything else should
    remain identical.
    
    Change-Id: I5c249cc2144276a25dba4d7bcb086a34b52d6334

http://cgit.osmocom.org/osmo-gsm-manuals/commit/?id=e62d414c0cd3ce8068e99e299b5c5065e59ae1f3

commit e62d414c0cd3ce8068e99e299b5c5065e59ae1f3
Author: Harald Welte <[email protected]>
Date:   Tue Jul 11 17:23:47 2017 +0200

    Add Message Sequence Chart for a MO calls with ext. MNCC handler
    
    Change-Id: Ida10fc7ccb345b8cd084c4ecc5f4f7d4ce6c98a0

-----------------------------------------------------------------------

Summary of changes:
 common/chapters/msc_mncc_mo_rtp.msc  |  90 ++++++++++++++++++++++++++++++
 common/chapters/nitb_mncc_mo_rtp.msc | 104 +++++++++++++++++++++++++++++++++++
 common/chapters/nitb_mncc_mo_tch.msc |  92 +++++++++++++++++++++++++++++++
 3 files changed, 286 insertions(+)
 create mode 100644 common/chapters/msc_mncc_mo_rtp.msc
 create mode 100644 common/chapters/nitb_mncc_mo_rtp.msc
 create mode 100644 common/chapters/nitb_mncc_mo_tch.msc


hooks/post-receive
-- 
Manuals for Osmocom GSM components

Reply via email to