Project

General

Profile

Actions

Bug #2882

closed

OsmoMSC doesn't release call if BSS-side CRCX fails

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

Status:
Resolved
Priority:
Normal
Assignee:
Category:
MGCP towards MGW
Target version:
-
Start date:
01/26/2018
Due date:
% Done:

100%

Resolution:
Spec Reference:

Description

If the CRCX on the RAN side fails, we are issuing a DLCX on that endpoint and I get some related log messages, but the call remains in its state. The call should of course be terminated as without the MGW endpoint in operation we will never have a user plane working.

<0007> fsm.c:243 MGW(MGW_8)[0x9de2210]{ST_CRCX_RAN}: Allocated
<0007> msc_mgcp.c:913 MGW(MGW_8)[0x9de2210]{ST_CRCX_RAN}: Received Event 0
<0007> msc_mgcp.c:236 MGW(MGW_8)[0x9de2210]{ST_CRCX_RAN}: CRCX/RAN: creating connection for the RAN side on MGW endpoint:0x1...
<0020> mgcp_client.c:641 Queued 65 bytes for MGCP GW
<0007> msc_mgcp.c:261 MGW(MGW_8)[0x9de2210]{ST_CRCX_RAN}: state_chg to ST_CRCX_CN
<0007> msc_mgcp.c:918 (subscriber:IMSI:262420000000028) call assignment initiated
<0020> mgcp_client.c:470 Tx MGCP msg to MGCP GW: 'CRCX 5 1@mgw MGCP 1.0'
<0020> mgcp_client.c:472 Sending msg to MGCP GW size: 65
<0007> msc_mgcp.c:280 MGW(MGW_8)[0x9de2210]{ST_CRCX_CN}: CRCX/RAN: response yields error: 542 FORCED_FAIL
<0007> msc_mgcp.c:281 MGW(MGW_8)[0x9de2210]{ST_CRCX_CN}: operation failed on MGW -- graceful shutdown...
<0007> msc_mgcp.c:157 MGW(MGW_8)[0x9de2210]{ST_CRCX_CN}: state_chg to ST_CALL
<0007> msc_mgcp.c:161 MGW(MGW_8)[0x9de2210]{ST_CALL}: Received Event 4
<0007> msc_mgcp.c:690 MGW(MGW_8)[0x9de2210]{ST_CALL}: DLCX: removing connection for the RAN and CN side on MGW endpoint:0x1...
<0020> mgcp_client.c:641 Queued 29 bytes for MGCP GW
<0007> msc_mgcp.c:718 MGW(MGW_8)[0x9de2210]{ST_CALL}: state_chg to ST_HALT
<0020> mgcp_client.c:470 Tx MGCP msg to MGCP GW: 'DLCX 6 1@mgw MGCP 1.0'
<0020> mgcp_client.c:472 Sending msg to MGCP GW size: 29
<0007> msc_mgcp.c:730 MGW(MGW_8)[0x9de2210]{ST_HALT}: DLCX: response yields error: 250 OK
<0007> msc_mgcp.c:731 MGW(MGW_8)[0x9de2210]{ST_HALT}: operation failed on MGW -- graceful shutdown...
<0007> msc_mgcp.c:157 MGW(MGW_8)[0x9de2210]{ST_HALT}: transition to state ST_CALL not permitted!
<0007> msc_mgcp.c:161 MGW(MGW_8)[0x9de2210]{ST_HALT}: Received Event 4
<0007> msc_mgcp.c:759 MGW(MGW_8)[0x9de2210]{ST_HALT}: state_chg to ST_HALT
<0012> input/ipa.c:67 connection closed with server

As an oddity, the client code seems to have the opinion that 250 is an error response to DLCX.

MSC_Tests.TC_mo_crcx_ran_reject


Files

20180126-osmomsc-mocall-ran-crcx-reject.pcap 20180126-osmomsc-mocall-ran-crcx-reject.pcap 3.21 KB pcap file showing the problem laforge, 01/26/2018 09:51 PM
20180127-osmomsc-mtcall-ran-crcx-reject.pcap 20180127-osmomsc-mtcall-ran-crcx-reject.pcap 3.87 KB pcap file showing the problem in MT laforge, 01/27/2018 08:29 AM
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)