Project

General

Profile

Bug #1933

voice call drops after B subscriber accepts the call

Added by wirelesss almost 3 years ago. Updated almost 3 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
01/30/2017
Due date:
% Done:

0%

Spec Reference:

Description

During the test of nanoBTS (model 165G) and NITB configured with dynamic channels: 3 TCH/H and 3 PDCH, it was found that the initiated voice call drops immediately after B subscriber accepts the call.
  • Selected default voice codec is: tch-h hr.

In the eth_tarce.pcap following is shown:

Frame # 41: MODE MODIFY REQuest (0x29)
Channel Mode IE:
Speech coding algorithm: GSM speech coding algorithm version 1: GSM FR or GSM HR (1) # 42: MODE MODIFY Negative ACKnowledge (0x2b)
Cause IE:
Class: Protocol error (6)
... # 45: GSM A-bis OML, Baseband Transceiver(00,00,ff) Failure Event Report
FOM Message Type: Failure Event Report
FOM Attribute ID: Event Type
FOM Attribute Length: 1
Event Type: Processor Failure (0x02) # 48 Event Type: Processor Failure (0x02)
GSM A-bis OML, Baseband Transceiver(00,00,ff) Failure Event Report

the NITB log file shows :

...
Mon Jan 30 16:13:42 2017 DRLL <0000> chan_alloc.c:352 (bts=0,trx=0,ts=2,pchan=TCH/H) Allocating lchan=0 as TCH_H
Mon Jan 30 16:13:42 2017 DRSL <0004> abis_rsl.c:1819 (bts=0,trx=0,ts=2,ss=0) Activating ARFCN(870) SS(0) lctype TCH_H r=CALL ra=0x41 ta=0
Mon Jan 30 16:13:42 2017 DRSL <0004> abis_rsl.c:580 (bts=0,trx=0,ts=2,pchan=TCH/H) Tx RSL Channel Activate with act_type=INITIAL
Mon Jan 30 16:13:42 2017 DRSL <0004> abis_rsl.c:1189 (bts=0,trx=0,ts=2,ss=0) state NONE -> ACTIVATION REQUESTED
Mon Jan 30 16:13:42 2017 DRSL <0004> abis_rsl.c:1546 (bts=0,trx=0,ts=2,ss=0) CHANNEL ACTIVATE ACK
Mon Jan 30 16:13:42 2017 DRSL <0004> abis_rsl.c:1189 (bts=0,trx=0,ts=2,ss=0) state ACTIVATION REQUESTED -> ACTIVE
Mon Jan 30 16:13:42 2017 DRLL <0000> abis_rsl.c:2009 (bts=0,trx=0,ts=2,ss=0) SAPI=0 ESTABLISH INDICATION
Mon Jan 30 16:13:42 2017 DRLL <0000> gsm_04_08.c:3723 Dispatching 04.08 message, pdisc=5
Mon Jan 30 16:13:42 2017 DRLL <0000> abis_rsl.c:2009 (bts=0,trx=0,ts=2,ss=0) SAPI=0 DATA INDICATION
Mon Jan 30 16:13:43 2017 DRLL <0000> abis_rsl.c:2009 (bts=0,trx=0,ts=2,ss=0) SAPI=0 DATA INDICATION
Mon Jan 30 16:13:43 2017 DRLL <0000> gsm_04_08.c:3723 Dispatching 04.08 message, pdisc=3
Mon Jan 30 16:13:43 2017 DMSC <000a> bsc_api.c:402 Sending ChanModify for speech: SPEECH_V1 on channel TCH_H
Mon Jan 30 16:13:43 2017 DRLL <0000> abis_rsl.c:2009 (bts=0,trx=0,ts=2,ss=0) SAPI=0 DATA INDICATION
Mon Jan 30 16:13:43 2017 DRSL <0004> abis_rsl.c:2226 (bts=0,trx=0,ts=2,ss=0) IPAC_BIND speech_mode=0x13 RTP_PAYLOAD=96
Mon Jan 30 16:13:43 2017 DRSL <0004> abis_rsl.c:1570 (bts=0,trx=0,ts=2,ss=0) CHANNEL MODE MODIFY NACK
Mon Jan 30 16:13:43 2017 DRSL <0004> abis_rsl.c:2413 (bts=0,trx=0,ts=2,ss=0) IPAC_CRCX_NACK

Failure Event Report Type=processing failure Severity=warning level failure Probable cause= 03 00 01 Additional Text=l3_0858_parser.c:852Unrecognised Cause value.

Failure Event Report Type=processing failure Severity=failure ceased Probable cause= 03 00 01 
Failure Event Report Type=processing failure Severity=warning level failure Probable cause= 03 00 01 Additional Text=l3_0858_parser.c:575## T  M/O Pass  Failure Reason

Failure Event Report Type=processing failure Severity=failure ceased Probable cause= 03 00 01 
Failure Event Report Type=processing failure Severity=warning level failure Probable cause= 03 00 01 Additional Text=l3_0858_parser.c:617 0  6 Man FALSE 0858_IE_VALUE_RFU

Failure Event Report Type=processing failure Severity=failure ceased Probable cause= 03 00 01 
Failure Event Report Type=processing failure Severity=warning level failure Probable cause= 03 00 01 Additional Text=l3_0858_parser.c:617 1  7 Opt Not parsed

Failure Event Report Type=processing failure Severity=failure ceased Probable cause= 03 00 01 
Failure Event Report Type=processing failure Severity=warning level failure Probable cause= 03 00 01 Additional Text=l3_0858_parser.c:617 2 53 Opt Not parsed

Failure Event Report Type=processing failure Severity=failure ceased Probable cause= 03 00 01 
Failure Event Report Type=processing failure Severity=warning level failure Probable cause= 03 00 01 Additional Text=l3_0858_parser.c:617 3 54 Opt Not parsed

Failure Event Report Type=processing failure Severity=failure ceased Probable cause= 03 00 01 
Failure Event Report Type=processing failure Severity=warning level failure Probable cause= 03 00 01 Additional Text=l3_main.c:399L3 msg parse failure. New msg (0x306) destroyed.

Failure Event Report Type=processing failure Severity=failure ceased Probable cause= 03 00 01 
Mon Jan 30 16:13:44 2017 DRLL <0000> chan_alloc.c:352 (bts=0,trx=0,ts=2,pchan=TCH/H) Allocating lchan=1 as TCH_H
Mon Jan 30 16:13:44 2017 DRSL <0004> abis_rsl.c:1819 (bts=0,trx=0,ts=2,ss=1) Activating ARFCN(870) SS(1) lctype TCH_H r=PAGING ra=0x2a ta=0
Mon Jan 30 16:13:44 2017 DRSL <0004> abis_rsl.c:580 (bts=0,trx=0,ts=2,pchan=TCH/H) Tx RSL Channel Activate with act_type=INITIAL
Mon Jan 30 16:13:44 2017 DRSL <0004> abis_rsl.c:1189 (bts=0,trx=0,ts=2,ss=1) state NONE -> ACTIVATION REQUESTED
Mon Jan 30 16:13:44 2017 DRSL <0004> abis_rsl.c:1546 (bts=0,trx=0,ts=2,ss=1) CHANNEL ACTIVATE ACK
Mon Jan 30 16:13:44 2017 DRSL <0004> abis_rsl.c:1189 (bts=0,trx=0,ts=2,ss=1) state ACTIVATION REQUESTED -> ACTIVE
Mon Jan 30 16:13:45 2017 DRLL <0000> abis_rsl.c:2009 (bts=0,trx=0,ts=2,ss=1) SAPI=0 ESTABLISH INDICATION
Mon Jan 30 16:13:45 2017 DRLL <0000> gsm_04_08.c:3723 Dispatching 04.08 message, pdisc=6
Mon Jan 30 16:13:45 2017 DRLL <0000> abis_rsl.c:2009 (bts=0,trx=0,ts=2,ss=1) SAPI=0 DATA INDICATION
Mon Jan 30 16:13:45 2017 DRLL <0000> abis_rsl.c:2009 (bts=0,trx=0,ts=2,ss=1) SAPI=0 DATA INDICATION
Mon Jan 30 16:13:45 2017 DRLL <0000> gsm_04_08.c:3723 Dispatching 04.08 message, pdisc=3
Mon Jan 30 16:13:45 2017 DMSC <000a> bsc_api.c:402 Sending ChanModify for speech: SPEECH_V1 on channel TCH_H
Mon Jan 30 16:13:45 2017 DRLL <0000> abis_rsl.c:2009 (bts=0,trx=0,ts=2,ss=1) SAPI=0 DATA INDICATION
Mon Jan 30 16:13:45 2017 DRSL <0004> abis_rsl.c:2226 (bts=0,trx=0,ts=2,ss=1) IPAC_BIND speech_mode=0x13 RTP_PAYLOAD=96
Mon Jan 30 16:13:45 2017 DRSL <0004> abis_rsl.c:1570 (bts=0,trx=0,ts=2,ss=1) CHANNEL MODE MODIFY NACK
Mon Jan 30 16:13:45 2017 DRSL <0004> abis_rsl.c:2413 (bts=0,trx=0,ts=2,ss=1) IPAC_CRCX_NACK

Package: libosmocore
Version: 0.9.0-5

hashes:
libosmo-abis: 254745880bb2ff7f17fe158fb7bfb5e1dc530906
libosmo-netif: 8d3384290ba7c79b290b492dd1279041fb578a9c
libosmo-sccp: 0c72c1c0d313321f65fd272840ed8e8ae69a04cd
libosmocore: 48f55833476439fc45fa4eaa4327beccdc92d44b
libsmpp34: 63d562c099f11c4d11a952a03bc54659f8b82319
openbsc: 3f940fc9eea40873185a240e68992e70a3e8abb4

tun0_trace.pcap tun0_trace.pcap 24 Bytes tun0 log wirelesss, 01/30/2017 04:39 PM
lo_trace.pcap lo_trace.pcap 109 KB lo interface log wirelesss, 01/30/2017 04:39 PM
eth_trace.pcap eth_trace.pcap 81.6 KB eth interface log wirelesss, 01/30/2017 04:39 PM
nitb_nano_3_TCH_H_3PDCH.log nitb_nano_3_TCH_H_3PDCH.log 238 KB nitb log file with 3 TCH/H and 3 PDCH wirelesss, 01/30/2017 04:44 PM
openbsc_nano.cfg openbsc_nano.cfg 4.7 KB nitb config file wirelesss, 01/30/2017 04:58 PM

History

#1 Updated by neels almost 3 years ago

  • Status changed from New to Feedback
  • Assignee set to wirelesss

The log goes thru various TCH/H lchans like this:

Mon Jan 30 15:27:57 2017 DRSL <0004> abis_rsl.c:1819 (bts=0,trx=0,ts=2,ss=0) Activating ARFCN(870) SS(0) lctype TCH_H r=CALL ra=0x4a ta=0
Mon Jan 30 15:27:57 2017 DRSL <0004> abis_rsl.c:580 (bts=0,trx=0,ts=2,pchan=TCH/H) Tx RSL Channel Activate with act_type=INITIAL
Mon Jan 30 15:27:57 2017 DRSL <0004> abis_rsl.c:1189 (bts=0,trx=0,ts=2,ss=0) state NONE -> ACTIVATION REQUESTED
Mon Jan 30 15:27:57 2017 DRSL <0004> abis_rsl.c:1546 (bts=0,trx=0,ts=2,ss=0) CHANNEL ACTIVATE ACK
Mon Jan 30 15:27:57 2017 DRSL <0004> abis_rsl.c:1189 (bts=0,trx=0,ts=2,ss=0) state ACTIVATION REQUESTED -> ACTIVE
Mon Jan 30 15:27:58 2017 DRLL <0000> abis_rsl.c:2009 (bts=0,trx=0,ts=2,ss=0) SAPI=0 ESTABLISH INDICATION
Mon Jan 30 15:27:58 2017 DRLL <0000> gsm_04_08.c:3723 Dispatching 04.08 message, pdisc=5
Mon Jan 30 15:27:58 2017 DRLL <0000> abis_rsl.c:2009 (bts=0,trx=0,ts=2,ss=0) SAPI=0 DATA INDICATION
Mon Jan 30 15:27:58 2017 DRLL <0000> abis_rsl.c:2009 (bts=0,trx=0,ts=2,ss=0) SAPI=0 DATA INDICATION
Mon Jan 30 15:27:58 2017 DRLL <0000> gsm_04_08.c:3723 Dispatching 04.08 message, pdisc=3
Mon Jan 30 15:27:58 2017 DMSC <000a> bsc_api.c:402 Sending ChanModify for speech: SPEECH_V1 on channel TCH_H
Mon Jan 30 15:27:58 2017 DRLL <0000> abis_rsl.c:2009 (bts=0,trx=0,ts=2,ss=0) SAPI=0 DATA INDICATION
Mon Jan 30 15:27:58 2017 DRSL <0004> abis_rsl.c:2226 (bts=0,trx=0,ts=2,ss=0) IPAC_BIND speech_mode=0x13 RTP_PAYLOAD=96
Mon Jan 30 15:27:58 2017 DRSL <0004> abis_rsl.c:1570 (bts=0,trx=0,ts=2,ss=0) CHANNEL MODE MODIFY NACK
Mon Jan 30 15:27:58 2017 DRSL <0004> abis_rsl.c:2413 (bts=0,trx=0,ts=2,ss=0) IPAC_CRCX_NACK

Failure Event Report Type=processing failure Severity=warning level failure Probable cause= 03 00 01 Additional Text=l3_0858_parser.c:852Unrecognised Cause value.

Failure Event Report Type=processing failure Severity=failure ceased Probable cause= 03 00 01 
Failure Event Report Type=processing failure Severity=warning level failure Probable cause= 03 00 01 Additional Text=l3_0858_parser.c:575## T  M/O Pass  Failure Reason

Failure Event Report Type=processing failure Severity=failure ceased Probable cause= 03 00 01 
Failure Event Report Type=processing failure Severity=warning level failure Probable cause= 03 00 01 Additional Text=l3_0858_parser.c:617 0  6 Man FALSE 0858_IE_VALUE_RFU

Failure Event Report Type=processing failure Severity=failure ceased Probable cause= 03 00 01 
Failure Event Report Type=processing failure Severity=warning level failure Probable cause= 03 00 01 Additional Text=l3_0858_parser.c:617 1  7 Opt Not parsed

Failure Event Report Type=processing failure Severity=failure ceased Probable cause= 03 00 01 
Failure Event Report Type=processing failure Severity=warning level failure Probable cause= 03 00 01 Additional Text=l3_0858_parser.c:617 2 53 Opt Not parsed

Failure Event Report Type=processing failure Severity=failure ceased Probable cause= 03 00 01 
Failure Event Report Type=processing failure Severity=warning level failure Probable cause= 03 00 01 Additional Text=l3_0858_parser.c:617 3 54 Opt Not parsed

Failure Event Report Type=processing failure Severity=failure ceased Probable cause= 03 00 01 
Failure Event Report Type=processing failure Severity=warning level failure Probable cause= 03 00 01 Additional Text=l3_main.c:399L3 msg parse failure. New msg (0x306) destroyed.

Failure Event Report Type=processing failure Severity=failure ceased Probable cause= 03 00 01

It seems the speech_mode would be the problem:

Mon Jan 30 15:27:58 2017 DRSL <0004> abis_rsl.c:2226 (bts=0,trx=0,ts=2,ss=0) IPAC_BIND speech_mode=0x13 RTP_PAYLOAD=96
Mon Jan 30 15:27:58 2017 DRSL <0004> abis_rsl.c:1570 (bts=0,trx=0,ts=2,ss=0) CHANNEL MODE MODIFY NACK

In the attached openbsc_nano.cfg, I can't find any speech codec config,
so from the default values in openbsc/src/libmsc/mncc_builtin.c it should be equivalent to this config,
which also matches the speech_mode=0x13:

mncc-int
 default-codec tch-f fr
 default-codec tch-h hr

Does it make sense to try other codecs with the nanoBTS?
According to openbsc/src/libbsc/abis_rsl.c ipa_smod_s_for_lchan() it would be possible to set AMR for TCH/H.

Ivaylo, has AMR on TCH/H been tested? If not, can you test it please?

#2 Updated by neels almost 3 years ago

The reply from Harald on openbsc@ is:

Why is there again an attempt to use HR (v1) with the nanoBTS?  It is a
codec that this BTS hardware is known to never have supported.

If this ticket had been updated right away I would not have spent time investigating.
Another call to please track the status in the tickets.

#3 Updated by wirelesss almost 3 years ago

  • Status changed from Feedback to In Progress

#4 Updated by wirelesss almost 3 years ago

  • Status changed from In Progress to Resolved

Ticket is set to Resolved as HR (v1) codec is not supported by nanoBTS.

#5 Updated by neels almost 3 years ago

  • Status changed from Resolved to Rejected

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)