Project

General

Profile

Bug #2762

OsmoBSC: Assignment of "Signalling" channel fails

Added by laforge 7 months ago. Updated about 1 month ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
A interface
Target version:
-
Start date:
12/15/2017
Due date:
% Done:

100%

Estimated time:
Spec Reference:

Description

When sending a BSSMAP Assignment Command with channel type == signalling, OsmoBSC fails the assignment, despite plenty of channels being available.

See attached PCAP.

I'm creating TC_assignment_sign for this in the TTCN-3 testsuite.

bssmap-ass-signalling.pcapng bssmap-ass-signalling.pcapng 652 Bytes laforge, 12/15/2017 01:02 PM

History

#1 Updated by laforge 7 months ago

  • Description updated (diff)

#2 Updated by laforge 6 months ago

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

I have a fix in Change-Id I85ffcbd32ccd2617c897edb3b904f56bacd0684f of the laforge/fsm branch.

#3 Updated by laforge 6 months ago

  • Priority changed from Normal to High

#4 Updated by laforge 5 months ago

  • Status changed from In Progress to Stalled

waiting for dexter to complete the work on the FSM branch

#5 Updated by laforge 4 months ago

  • Assignee changed from laforge to dexter

this is unfortunately not fixed in the fsm branch but is now failing in a different way. We're sending a MODE MODIFY REQ to the MS, despite already being in signaling mode.

#6 Updated by dexter 3 months ago

  • % Done changed from 70 to 100

#7 Updated by dexter 3 months ago

  • % Done changed from 100 to 60

#8 Updated by dexter about 2 months ago

See update in #2936

#9 Updated by dexter about 2 months ago

  • Status changed from Stalled to In Progress

#10 Updated by dexter about 1 month ago

  • Status changed from In Progress to Resolved
  • % Done changed from 60 to 100

See #2936, TC_assignment_sign now passes.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)