This sequence works perfectly in 5G NSA but not in SA.
In SA, we are not able to connect to our internet apn.
We notice that in this case the modem always use the context 1 in AT+CGDCOUNT whatever the apn provided in mbimcli command.
In our case, by default, the context 1 was set to an ims. When we call the “sudo mbimcli -d /dev/cdc-wdm1 -v -p --connect=apn=internet,ip-type=ipv4,session-id=0”, the PDU session establishment request us done with ims instead of internet.
It is very strange, could you please provide us some support ?
i have removed ims from CGDCOUNT by an another one. In this case the other one is used. It is not ims or ip related.
The key point is that the apn used as a parameter in connect request in mbim and qmi is not considered. The one considered is always the one in Context 1.
The goal is to check you are e able to connect to the apn you set with the mbim command as explained in your reference manual.
To be sure to be connected on the apn you set on mbim command, you set either the APN in context 1 to NULL, or a default apn different the one you want to connect.
You call the command and you check if you are connected an if your IP address is the one corresponding to your APN.
In my case, using the mbim command, i connect to the apn in context 1 (if null, the default attahc one) so the and not the one on the command. The IP address is not the good one.
the purpose is to check that with your sdk is working or you have the same behavior as me.
I don’t have 5G SA network here, so not able to test for you on 5G SA connection.
Since you say only 5G SA has problem, you might need to contact distributor on this for the testing
Or you can just directly use same APN in data connection and AT+CGDCONT.
(normally i will use this method)