The MNCC Unix Domain Socket encoding uses an int here, which is
a bit odd, given that it's an ASCII / IA5 char value on the actual
GSM L3. Let's convert from/to something useful.
Change-Id: Id17ac502ca33f4962214a3d5938d0dc29ca6ec1b
We start the call from the MNCC side, match on the paging and then
pick it up from there.
It currently fails as the MNCC_Emulation cannot yet handle "ConnHdlr
originated" MNCC calls yet.
Change-Id: I28c465187fd8b1dcfd687180b373a47bb9ac6734
MNCC has this weird encoding that the speech version array must
be terminated with one element '-1' at the end. Let's make sure
our default complies to this rule.
Change-Id: I2e06ed1b558c58a62a00ea8d3573bb31c0c3e750
Related: OS#2853
it seems the decoder is using '0' in positions where we have
not defined any enum value for '0'. Work around that.
Change-Id: I6bf0540f7ddd4dbe3b6c6ac06421a933126a7e17
This adds templates for sending and receiving MNCC messages from
the external MNCC handler point of view, i.e. as required for MSC
testing. The inverse templates will be needed if we want to implement
emulation of the MSC side of MNCC.
Change-Id: I77665aaf589bdaa9dc0aa6a5daa431fafdc2b383
Harald Welte