Project

General

Profile

Bug #2943

Errors in MGCP do not propagate back to MNCC gsm_subscriber_conn state machine

Added by daniel 9 months ago. Updated 5 months ago.

Status:
New
Priority:
Normal
Assignee:
Category:
MGCP towards MGW
Target version:
-
Start date:
02/13/2018
Due date:
% Done:

0%

Resolution:

Description

TC_mo_crcx_ran_reject shows that if the CRCX during call setup fails the call control state machine just stalls. The MGCP code handles that case and clears all connections on the endpoint.
The call control side is never notified of the failure and so the connection just hangs half open at that stage.
See handle_error() and the caller mgw_crcx_ran_resp_cb() in libmsc/msc_mgcp.c

In case of an error the MGCP code should make sure the call is released to the phone side and also notify the (external) mncc.

TC_mo_crcx_ran_reject.pcapng TC_mo_crcx_ran_reject.pcapng 3.75 KB pcap of the test daniel, 02/13/2018 07:52 PM

History

#1 Updated by laforge 9 months ago

  • Assignee set to sysmocom

#2 Updated by laforge 5 months ago

  • Category set to MGCP towards MGW
  • Assignee changed from sysmocom to daniel

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)