more verbose MNCC logging

It is pretty unclear what codec items MNCC sends and receives exactly
when:
* Bearer Capabilities speech versions,
* 'payload message type' and
* the new SDP information

Include these items in MNCC rx and tx logging.

In msc_log_to_ladder.py, in sequence charts generated from an actual
osmo-msc log, also show all MNCC codec items.

Change-Id: I19ccffa2f9b627ad51fffd344ee6e75908d30295

1 files changed, 1 insertions, 0 deletions

diff --git a/include/osmocom/msc/codec_mapping.h b/include/osmocom/msc/codec_mapping.h
index 1232d2d8a..6d55f2dc4 100644
--- a/include/osmocom/msc/codec_mapping.h
+++ b/include/osmocom/msc/codec_mapping.h
@@ -45,6 +45,7 @@ const struct codec_mapping *codec_mapping_by_gsm0808_speech_codec(const struct g
 const struct codec_mapping *codec_mapping_by_perm_speech(enum gsm0808_permitted_speech perm_speech);
 const struct codec_mapping *codec_mapping_by_subtype_name(const char *subtype_name);
 const struct codec_mapping *codec_mapping_by_mgcp_codec(enum mgcp_codecs mgcp);
+const struct codec_mapping *codec_mapping_by_mncc_pmt(uint32_t pmt);
 
 int bearer_cap_add_speech_ver(struct gsm_mncc_bearer_cap *bearer_cap, enum gsm48_bcap_speech_ver speech_ver);
 int sdp_audio_codec_add_to_bearer_cap(struct gsm_mncc_bearer_cap *bearer_cap, const struct sdp_audio_codec *codec);