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/.
Neels Hofmeyr nhofmeyr at sysmocom.deWith the lack of comments, I am implementing and using this, explicitly naming the entities that are sending and receiving GSUP messages in GSUP IEs. Still would like to get input on naming: For SMS, we have the SMSC and ESME entities. Are there similar terms for USSD? Which is the entity managing USSD dialogs? which is the entity sending the USSD messages? Is it EUSE <-> MSC? Thinking, in fact if our osmo-msc wasn't siamese twins with the SMSC we would have ESME <-> SMSC <-> MSC. And might make sense to explicitly state which MSC subsystem is being addressed, so rather: EMSE <-> SMSC <-> MSC-SMS (currently only EMSE <-> SMSC, the final SMSC <-> MSC-SMS step is implemented inside current osmo-msc) EUSE <-> MSC-USSD Does that sound about right? Thanks! ~N -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20190321/e4e4eef8/attachment.bin>