Bug 1374780

Summary: Nokia 0421:0638 sometimes doesn't connect
Product: Red Hat Enterprise Linux 7 Reporter: Lubomir Rintel <lrintel>
Component: ModemManagerAssignee: Lubomir Rintel <lrintel>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.4CC: aloughla, atragler, dcbw, lrintel, mleitner, rkhan, sukulkar, thaller
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-06-25 18:03:13 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Log from the failure
none
Successful connection none

Description Lubomir Rintel 2016-09-09 15:20:33 UTC
Created attachment 1199504 [details]
Log from the failure

"nmcli c up gsm" fails in ~1/30 cases when run in a loop.

Comment 1 Lubomir Rintel 2016-09-09 15:21:10 UTC
Created attachment 1199505 [details]
Successful connection

Comment 2 Dan Williams 2016-09-09 15:49:32 UTC
So the real cause of the failure is reported by %IER and it's 34; looking that up in the 3GPP TS 24.008 Annex G.4 shows:

Cause value = 34 Service option temporarily out of order 
This cause is sent when the MSC cannot service the request because of temporary outage of one or more functions required for supporting the service.

This would indicate a problem in the Yota NITB, if the modem is to be believed.

Comment 3 Dan Williams 2016-09-09 16:26:54 UTC
By "yota nitb" I actually mean the "YateBTS network-in-a-box"

Comment 5 sushil kulkarni 2019-06-25 18:03:13 UTC
There is no plan to address this.. Will re-open if a requirement for this modem comes up.

-Sushil