https://osmocom.org/https://osmocom.org/favicon.ico?16647414092018-08-28T18:05:27ZOpen Source Mobile CommunicationsOsmoMGW - Feature #3507: allow shorter Connection Identifier 'I:'https://osmocom.org/issues/3507?journal_id=110422018-08-28T18:05:27Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-3 priority-2 priority-default closed" href="/issues/3429">Feature #3429</a>: idea: auto-cleanup endpoints after long period of inactivity?</i> added</li></ul> OsmoMGW - Feature #3507: allow shorter Connection Identifier 'I:'https://osmocom.org/issues/3507?journal_id=110492018-08-28T18:40:01Zneelsnhofmeyr@sysmocom.de
<ul></ul><p>RFC3435<br /><pre>
2.1.3.2 Names of Connections
Connection identifiers are created by the gateway when it is
requested to create a connection. They identify the connection
within the context of an endpoint. Connection identifiers are
treated in MGCP as hexadecimal strings. The gateway MUST make sure
that a proper waiting period, at least 3 minutes, elapses between the
end of a connection that used this identifier and its use in a new
connection for the same endpoint (gateways MAY decide to use
identifiers that are unique within the context of the gateway). The
maximum length of a connection identifier is 32 characters.
</pre></p>
<p>The <strong>maximum</strong> length is 32 characters, and the identifier's scope is indeed merely limited by that one specific endpoint (one call between currently no more than two subscribers).<br />I think we're still on the safe side if we reduce osmo-mgw to a length of 8 hex characters.</p> OsmoMGW - Feature #3507: allow shorter Connection Identifier 'I:'https://osmocom.org/issues/3507?journal_id=110502018-08-28T18:41:43Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/11050/diff?detail_id=17905">diff</a>)</li></ul> OsmoMGW - Feature #3507: allow shorter Connection Identifier 'I:'https://osmocom.org/issues/3507?journal_id=110512018-08-28T21:46:12Zlaforge
<ul></ul><p>On Tue, Aug 28, 2018 at 05:45:42PM +0000, neels [REDMINE] wrote:</p>
<blockquote>
<p>So I would vote for us simply reducing the length to 4.</p>
</blockquote>
<p>Fine with me. But please take the extra effort of putting together a proper bug<br />report for the MSC vendor referencing the exact RFC paragraph/quote that states<br />their implementation is broken.</p> OsmoMGW - Feature #3507: allow shorter Connection Identifier 'I:'https://osmocom.org/issues/3507?journal_id=110562018-08-29T00:11:45Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li></ul> OsmoMGW - Feature #3507: allow shorter Connection Identifier 'I:'https://osmocom.org/issues/3507?journal_id=110602018-08-29T00:39:46Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>% Done</strong> changed from <i>0</i> to <i>90</i></li></ul><p><a class="external" href="https://gerrit.osmocom.org/#/c/osmo-mgw/+/10676">https://gerrit.osmocom.org/#/c/osmo-mgw/+/10676</a></p> OsmoMGW - Feature #3507: allow shorter Connection Identifier 'I:'https://osmocom.org/issues/3507?journal_id=112952018-09-12T13:36:25Zneelsnhofmeyr@sysmocom.de
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Resolved</i></li><li><strong>% Done</strong> changed from <i>90</i> to <i>100</i></li></ul>