Actions
Feature #3509
closedmatch MGCP "I:" Connection ID also when leading zeros are omitted
Start date:
08/29/2018
Due date:
% Done:
100%
Spec Reference:
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
Updated by neels over 5 years ago
- Related to Feature #3429: idea: auto-cleanup endpoints after long period of inactivity? added
Updated by neels over 5 years ago
- Related to Feature #3508: compare Connection Identifier 'I:' case insensitively added
Updated by neels over 5 years ago
- % Done changed from 0 to 90
Updated by neels over 5 years ago
- Status changed from In Progress to Resolved
- % Done changed from 90 to 100
Actions