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/.
Harald Welte laforge at gnumonks.orgHi! With the help of graphviz, I have written a small perl-based tool that allows you to generate ladder diagrams. It can be found at git://git.osmocom.org/gen_ladder.git For your reference, I'm attaching a sample input and output file. The bent/curved arrows are a result of graphviz trying to indicate that the message is between e.g. MS and MSC and 'bypasses' BTS and BSC. I'm still waiting for somebody with more graphviz skills to make this an option. Hope this is useful for some of you... -- - Harald Welte <laforge at gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) -------------- next part -------------- [entities] # define the entities in the system (in order) ms bts bsc # msc means MSC + VLR msc hlr [messages] # define the protocol messages in-order ms bts "L1 RACH burst" bts bsc "RSL CHAN RQD" bsc bts "RSL CHAN ACT REQ" bts bsc "RSL CHAN ACT ACK" bsc bts "RSL IMM ASS CMD" bts ms "IMMEDIATE ASSIGN" ms bsc "MM LOC UPD REQ" bsc msc "COMPL L3 INFO (LOC UPD REQ)" msc ms "MM IDENTITY REQUEST" ms msc "MM IDENTITY RESPONSE" msc hlr "MAP SEND AUTH INFO req" hlr msc "MAP SEND AUTH INFO resp" msc ms "MM AUTH REQ" ms msc "MM AUTH RESP" msc hlr "MAP UPD LOC AREA req" hlr msc "MAP INSERT SUBSCR DATA req" msc hlr "MAP INSERT SUBSCR DATA resp" hlr msc "MAP UPD LOC AREA resp" ms msc "Dedicated Channel" both dashed -------------- next part -------------- A non-text attachment was scrubbed... Name: location_update.ps Type: application/postscript Size: 40697 bytes Desc: not available URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20100709/8499bec1/attachment.ps>