Project

General

Profile

Actions

Bug #4784

open

wrong cause code (resources unavailable) in MO-to-MT call without response

Added by laforge over 3 years ago. Updated over 3 years ago.

Status:
New
Priority:
Normal
Assignee:
Category:
Call Control
Target version:
-
Start date:
10/08/2020
Due date:
% Done:

0%

Resolution:
Spec Reference:

Description

if a MO-to-MT call is performed using osmo-msc with internal MNCC handler, and the call proceeds up to the "ALERTING" being sent by the MT-leg (but the call is never accepted by the MT side), the CC RELEASE is sent using cause value "resources unavailable, unspecified" (GSM48_CC_CAUSE_RESOURCE_UNAVAIL). This is quite misleading to users, and one is trying to find what kind of resources miight be exhausted. But there is no exhaustion, "B" just never responded the call from "A".


Files

Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)