Project

General

Profile

Actions

Bug #3651

closed

SS request results in lingering lchan

Added by keith over 5 years ago. Updated over 5 years ago.

Status:
Resolved
Priority:
High
Assignee:
Target version:
-
Start date:
10/12/2018
Due date:
% Done:

100%

Spec Reference:

Description

SS codes such as *#21# are not handled correctly

Output on the HLR:

Fri Oct 12 14:55:26 2018 DSS <0004> hlr_ussd.c:467 262420312915730/0x20000003: Process SS (BEGIN)
Fri Oct 12 14:55:26 2018 DSS <0004> hlr_ussd.c:401 262420312915730/0x20000003: SS CompType=Invoke, OpCode=IngerrogateSS

followed by:

Fri Oct 12 14:55:56 2018 DSS <0004> hlr_ussd.c:195 262420312915730/0x20000003: SS Session Timeout, destroying

But osmo-bsc still has:

OsmoBSC# show lchan s        
BTS 0, TRX 0, Timeslot 0 CCCH+SDCCH4, Lchan 0, Type SDCCH, State ESTABLISHED - L1 MS Power: 5 dBm RXL-FULL-dl:  -47 dBm RXL-FULL-ul:  -56 dBm
OsmoBSC#

and this persists, with some phones, forever.


Files

local.pcap local.pcap 10.1 KB A / GSUP keith, 10/12/2018 02:18 PM
SS-abis.pcap SS-abis.pcap 34.8 KB Abis for *#21# keith, 10/12/2018 02:18 PM
USSD-good-abis.pcap USSD-good-abis.pcap 4.14 KB Abis for *#100# keith, 10/12/2018 02:18 PM
abis.pcap abis.pcap 124 KB keith, 10/13/2018 10:11 AM
local.pcap local.pcap 109 KB Capture of A/GSUP for above description. keith, 10/13/2018 10:20 AM
abis.pcap abis.pcap 28.2 KB Nokia calling KRZR keith, 10/13/2018 10:43 AM
local.pcap local.pcap 178 KB A / GSUP for the latest test keith, 10/13/2018 10:51 AM

Related issues

Related to OsmoMSC - Feature #3655: Introduce self-destruction timer for SS/USSD connectionsResolvedfixeria10/16/2018

Actions
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)