Project

General

Profile

Feature #3509

match MGCP "I:" Connection ID also when leading zeros are omitted

Added by neels about 1 year ago. Updated about 1 year ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
-
Target version:
-
Start date:
08/29/2018
Due date:
% Done:

100%


Description

RFC3435 2.1.3.2 "Names of Connections" defines the "I:" Connection Identifier as hex stream.
Hence it is valid for a client to omit leading zeros from Connection Identifier returned by a CRCX response.

OsmoMGW currently generates fixed-length Connection Identifiers and quite possibly includes leading zeros.

When testing this against a particular SCCPlite MSC, I see that in a DLCX to cleanup after a CRCX that returned an ID with leading zeros, this MSC in fact omits the leading zeros, leading to a mismatch and DLCX failure.

osmo-mgw should match despite a differing number of leading zeros in the conn ID:

  • ignore leading zeros in the DLCX "I:" parameter, and
  • ignore leading zeros in the locally generated connection identifier.

Related issues

Related to OsmoMGW - Feature #3429: idea: auto-cleanup endpoints after long period of inactivity?Resolved07/28/2018

Related to OsmoMGW - Feature #3508: compare Connection Identifier 'I:' case insensitivelyResolved08/28/2018

History

#1 Updated by neels about 1 year ago

  • Related to Feature #3429: idea: auto-cleanup endpoints after long period of inactivity? added

#2 Updated by neels about 1 year ago

  • Status changed from New to In Progress

#3 Updated by neels about 1 year ago

  • Related to Feature #3508: compare Connection Identifier 'I:' case insensitively added

#4 Updated by neels about 1 year ago

  • % Done changed from 0 to 90

#5 Updated by neels about 1 year ago

  • Status changed from In Progress to Resolved
  • % Done changed from 90 to 100

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)