Project

General

Profile

Actions

Bug #2923

closed

osmo-msc considers 250 respose to DLCX as an error

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

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
02/10/2018
Due date:
% Done:

100%

Resolution:
Spec Reference:

Description

Sat Feb 10 10:36:53 2018 DMGCP <0007> msc_mgcp.c:729 MGW(MGW_8)[0x6120000117a0]{ST_HALT}: DLCX: response yields error: 250 OK
Sat Feb 10 10:36:53 2018 DMGCP <0007> msc_mgcp.c:730 MGW(MGW_8)[0x6120000117a0]{ST_HALT}: operation failed on MGW -- graceful shutdown...
Sat Feb 10 10:36:53 2018 DMGCP <0007> msc_mgcp.c:157 MGW(MGW_8)[0x6120000117a0]{ST_HALT}: transition to state ST_CALL not permitted!
Sat Feb 10 10:36:53 2018 DMGCP <0007> msc_mgcp.c:161 MGW(MGW_8)[0x6120000117a0]{ST_HALT}: Received Event 4

However, RFC3435 is quite explicit:

   250 The connection was deleted.  This return code can only be used
       for a successful response to a DeleteConnection command.

Actions #1

Updated by laforge about 6 years ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 90
Actions #2

Updated by laforge about 6 years ago

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

merged

Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)