GSUP: E-interface messages for inter-MSC HO

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.

Oliver Smith osmith at sysmocom.de
Wed Feb 6 15:22:50 UTC 2019


On 2/6/19 12:52 AM, Neels Hofmeyr wrote:
> Now you know all the facts that I know, I'm currently not certain what would be
> the best to do. Can you figure it out?

After looking into the Wireshark dissector code, I came to the
conclusion that the ISDN-AddressString is exactly what you are seeing in
the dump. Furthermore, it is the same as the MSISDN.

Then I've looked up the existing MSISDN IE in the GSUP spec [1]:

> ISDN-AddressString / MSISDN / Called Party BCD Number
> 
> The MSISDN is encoded as an ISDN-AddressString in 3GPP TS 09.02 and Called Party
> BCD Number in 3GPP TS 04.08. It will be stored by the SGSN or VLR and then passed as is
> to the GGSN during the activation of the primary PDP Context.

(It also has a graph that looks like what you see in Wireshark.)

So my conclusion is, that we can just drop the handover_number IE and
use the existing msisdn_enc IE instead.

Regards,
Oliver

[1]:
https://git.osmocom.org/osmo-gsm-manuals/tree/common/chapters/gsup.adoc?id=68bbdc5f02d891133123573c422202f61923ebdf#n1062

-- 
- Oliver Smith <osmith at sysmocom.de>            https://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Director: Harald Welte



More information about the OpenBSC mailing list