Project

General

Profile

Bug #3187

rx cipher mode reject from BSS broken

Added by neels 3 months ago. Updated 29 days ago.

Status:
New
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
04/19/2018
Due date:
% Done:

0%

Estimated time:
Resolution:

Description

bssmap_rx_ciph_rej() looks for a cause IE using the BSS_MAP_MSG_CIPHER_MODE_REJECT message discriminator. This is clearly wrong and invariably leads to

<000a> a_iface_bssap.c:629 Rx MSC DT1 BSSMAP CIPHER MODE REJECT
<000a> a_iface_bssap.c:453 BSC sends cipher mode reject (conn_id=65)
<000a> a_iface_bssap.c:457 Cause code is missing -- discarding message!

We need a test verifying that the MSC properly receives a Cipher Mode Reject.
Since in ttcn3, we don't verify log output, this might actually be good to incorporate in the msc_vlr tests instead?
Is there a message response we could trigger on in ttcn3?


Related issues

Related to Cellular Network Infrastructure - Bug #3043: A5/3 encryption failsNew2018-03-08

History

#1 Updated by neels 3 months ago

  • Related to Bug #3043: A5/3 encryption fails added

#2 Updated by laforge 29 days ago

  • Assignee set to neels

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)