https://osmocom.org/https://osmocom.org/favicon.ico?16647414092018-05-29T16:34:43ZOpen Source Mobile CommunicationsOsmoSGSN - Bug #3302: implement a FSM for GMM Attach Requesthttps://osmocom.org/issues/3302?journal_id=95792018-05-29T16:34:43Zlynxis
<ul><li><strong>Subject</strong> changed from <i>implement GMM Attach Request</i> to <i>implement a FSM for GMM Attach Request</i></li><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li><li><strong>Assignee</strong> set to <i>lynxis</i></li><li><strong>Priority</strong> changed from <i>Normal</i> to <i>High</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>50</i></li></ul><p>The old code does layer violations and use a un-maintainable recursive function.<br />Replacing the code with a FSM.</p> OsmoSGSN - Bug #3302: implement a FSM for GMM Attach Requesthttps://osmocom.org/issues/3302?journal_id=95832018-05-29T16:37:28Zlynxis
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-5 priority-2 priority-default closed" href="/issues/2954">Bug #2954</a>: No GMM ATTACH REJECT on GSUP SendAuthInfo Error</i> added</li></ul> OsmoSGSN - Bug #3302: implement a FSM for GMM Attach Requesthttps://osmocom.org/issues/3302?journal_id=95862018-05-29T16:40:35Zlynxis
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-7 priority-2 priority-default" href="/issues/2958">Bug #2958</a>: OsmoSGSN doesn't authenticate on second/further ATTACH REQUEST</i> added</li></ul> OsmoSGSN - Bug #3302: implement a FSM for GMM Attach Requesthttps://osmocom.org/issues/3302?journal_id=95902018-05-29T16:43:06Zlynxis
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-5 priority-2 priority-default closed" href="/issues/2952">Bug #2952</a>: No timeout waiting for SendAuthInfo Response on GSUP</i> added</li></ul> OsmoSGSN - Bug #3302: implement a FSM for GMM Attach Requesthttps://osmocom.org/issues/3302?journal_id=96882018-05-31T13:08:38Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-1 priority-2 priority-default" href="/issues/1818">Bug #1818</a>: IuPS: CN should Iu Release in certain situations</i> added</li></ul> OsmoSGSN - Bug #3302: implement a FSM for GMM Attach Requesthttps://osmocom.org/issues/3302?journal_id=96892018-05-31T13:11:14Zneelsnhofmeyr@sysmocom.de
<ul></ul><p>Added relation to <a class="issue tracker-1 status-1 priority-2 priority-default" title="Bug: IuPS: CN should Iu Release in certain situations (New)" href="https://osmocom.org/issues/1818">#1818</a>: this is only very remotely related to <a class="issue tracker-1 status-1 priority-2 priority-default" title="Bug: IuPS: CN should Iu Release in certain situations (New)" href="https://osmocom.org/issues/1818">#1818</a> -- it's about the other half of attaching, namely detaching. It's sort of in the same ballpark of things to be fixed, so just maybe you can take this aspect into consideration as well. If it's too far away, then forget about the relation.</p> OsmoSGSN - Bug #3302: implement a FSM for GMM Attach Requesthttps://osmocom.org/issues/3302?journal_id=106692018-08-08T11:10:56Zlaforge
<ul><li><strong>Priority</strong> changed from <i>High</i> to <i>Immediate</i></li></ul> OsmoSGSN - Bug #3302: implement a FSM for GMM Attach Requesthttps://osmocom.org/issues/3302?journal_id=113622018-09-15T16:50:27Zlynxis
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Feedback</i></li></ul> OsmoSGSN - Bug #3302: implement a FSM for GMM Attach Requesthttps://osmocom.org/issues/3302?journal_id=113662018-09-15T20:12:28Zlynxis
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Closed</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul>