match MGCP "I:" Connection ID also when leading zeros are omitted
RFC3435 126.96.36.199 "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.