Bug #2649
closed
MGCP connection idetnifiers are hex strings, not integers
Added by laforge over 6 years ago.
Updated about 6 years ago.
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.
- Status changed from New to In Progress
- Status changed from In Progress to New
- Assignee changed from laforge to dexter
- % Done changed from 0 to 20
- Status changed from New to In Progress
- % Done changed from 20 to 100
The problem is now fixed, we are using 32 digit uppercase hex strings now.
- Status changed from In Progress to Resolved
- Status changed from Resolved to Closed
Also available in: Atom
PDF
