Bug #2877: OsmoMSC fails on bearer capability without octet 3a - OsmoMSC - Open Source Mobile Communications

Bug #2877

Added by laforge over 1 year ago. Updated 3 months ago.

Status:

New

Priority:

Normal

Assignee:

Category:

Target version:

Start date:

01/26/2018

Due date:

% Done:

Resolution:

Description

TS 24.008 Annex D.1.1 indicates by example that bearer capabilities can very well only consist of octets 1-3, without any octets 3a.

OsmoMSC fails in such situations as it relies on the codec information in octet 3a.

osmith, please write a related TTCN3 test. If the bug still exists, please discuss with neels how to proceed.

Also available in: Atom PDF