Hi, Having this feature would be great, because I'm facing exactly this issue using SIM cards from the Vodafone GDSP platform in conjunction with Telit LE910-V2 modem. Using this kind of SIM always result in "registration denied". With the information provided by Telit this behavior is clear now. It is essential to have a default PDP context #1 with valid credentials to allow registration.
I think a read only "InitialEpsBearer" is not sufficient. At least the credentials user and password must be configurable, to allow successful registration at the network. Implementation for MBIM devices is great. FYI, this is the information we got, which solve the registration problem: " When you want to do whatever data session on a cellular device (regardless from access technology) you need to "PDP attach" to the network; "PDP attach" provide an IP adress to the device 1.a 2G and 3G network are still based on a combination of CS + PS core network (Circuit Switched + Packet Switched) so in order to "attach" you need first to "register" to CS and PS. When you're CS registered you'll see +CREG: 0,1; when registered to PS (GPRS) you'll see +CGREG: 0,1. 1.b Now you're ready to open a "PDP context", an IP tunnel connected to Internet. To do this you need an APN and, as in your case, the credentials. AT#PDPAUTH= x,1,”…” , AT+CGDCONT=x," and ATD*99***x# are linked by "x" that's the context number: PDPAUTH allow you to set the credentials, CGDCONT the APN, ATD*99.. trigger the PDP attach with the previous parameters and starts PPP automatically. Contexts are just different IP tunnels connected to internet that can allow different data session in parallel. 1.c In 2G or 3G basically does not matter what context is used. 2.a In 4G all is routed via IP so when a cellular device connect to the network it performs directly a "PDP attach"; more specifically open a default EPS bearer on the first context. In 4G the context has a different roles: all route IP data but depending on operator they could be reserved or they can set to have different functions. For example, in case of Verizon and AT&T network is well know that context 1 has to be "left free" for registration/PDP attach only, so no other data sessions (e.g. PPP) have to be performed on context 1. This is why we generally suggest to move pure data sessions (PPP, Socekt Dial, etc..) on context different from the 1, for example the 3rd context. So generally speaking in 4G context 1 is reserved for registration (that's EPS default bearer), the others can be used for generic data transfer. 2.b So since "PDP attach" (registration) in 4G is performed directly on context 1 we need to set credentials. 3 In 2G, 3G PDP attach need always an APN 4 In 4G the 1 context (where default EPS bearer is created) generally does not require an APN, APN is required on other context to set up data sessions instead . In any case the rules are made by network operator In the end what you need is just to add the authentication on context 1 (using #PDPAUTH): this will allow to register properly in 4G. To avoid issues between contexts the PPP (ATD*99...) is better is done on context different form the 1st, so it's fine as you're doing it now." Regards, Carsten -----Ursprüngliche Nachricht----- Von: ModemManager-devel [mailto:modemmanager-devel-boun...@lists.freedesktop.org] Im Auftrag von Aleksander Morgado Gesendet: Freitag, 23. November 2018 18:02 An: ModemManager (development) Betreff: [review] LTE attach config and status Hey hey, See the following MR: https://gitlab.freedesktop.org/mobile-broadband/ModemManager/merge_requests/52 The changes will update the 3GPP interface with: * A new read-only property "InitialEpsBearer", which points to a Bearer object that will be automatically created and exposed in DBus when registered in LTE. This bearer object will define the settings/status of the initial LTE default bearer in effect at any given time during runtime. * A new read-only property "InitialEpsBearerProperties", a dictionary which contains the user-defined settings for the initial LTE default bearer. These settings MAY NOT be the ones effectively used at the end (e.g. if the network decides to use others, or if none provided by the user). * A new method "SetInitialEpsBearerProperties", which allows users to update the InitialEpsBearerProperties settings. The changes also include a new "bearer type" enumeration. The normal user-created bearers will be "default" bearers, while the initial automatically created bearer will be a "default initial" bearer. We also define an enum for "dedicated" bearers but we don't have APIs to support those yet . The logic is first implemented for MBIM devices, following the commands defined by Microsoft in the Basic Connect Extensions service: https://docs.microsoft.com/en-us/windows-hardware/drivers/network/mb-lte-attach-operations The ModemManager integration only changes the "home" network settings, we leave the "partner" and "non-partner" specific settings defined in the MBIM operations unchanged. NOTE! The commits are implemented right now on top of the mmcli key/value output changes, I pushed a MR which also contains those commits, just to avoid unnecessary rebase work. Comments welcome! -- Aleksander https://aleksander.es _______________________________________________ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel _______________________________________________ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
