Project

General

Profile

Actions

Bug #2649

closed

MGCP connection idetnifiers are hex strings, not integers

Added by laforge over 6 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Urgent
Assignee:
Category:
-
Target version:
-
Start date:
11/17/2017
Due date:
% Done:

100%

Spec Reference:

Description

The MGCP spec in RFC3435 is quite clear: Connection Identifiers are
hexadecimal strings of up to 32 characters. We should not print
and parse them as integers on either client or server.

Actions #1

Updated by laforge over 6 years ago

  • Status changed from New to In Progress
Actions #2

Updated by laforge over 6 years ago

  • Status changed from In Progress to New
  • Assignee changed from laforge to dexter
  • % Done changed from 0 to 20

See https://gerrit.osmocom.org/4906 as a starting point

Actions #3

Updated by dexter over 6 years ago

  • Status changed from New to In Progress
Actions #4

Updated by dexter over 6 years ago

  • % Done changed from 20 to 100

The problem is now fixed, we are using 32 digit uppercase hex strings now.

Actions #5

Updated by dexter over 6 years ago

  • Status changed from In Progress to Resolved
Actions #6

Updated by laforge about 6 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)