Re: UE Initiated Dedicated Bearer

Hi Aleksander, the business of secondary bearers is a bit murky, and so far it is limited to VoLTE in practical usage, for which use the modems create it automatically on top of the IMS bearer when an ATD; command is entered (or equivalent on MBIM/QMI). BR, Giacinto On Mon, Apr 26, 2021 at

Re: UE Initiated Dedicated Bearer

Hey, > I then came across this MR > https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/477?commit_id=bb6ed93dda185e679b76f77ffc67aa3a4a9eaf83 > which appears to be related to creating multiple bearers and configuring > said profiles through MM. I didn't see anything

Re: problems with QMI dual stack connections from MM - works with qmicli

Bjørn Mork writes: > Sorry, i do not think these issues are related to ModemManager at all. This is a test from freshly booted modem, MM not running: root@finn:~# qmicli -p -d /dev/cdc-wdm0 --device-open-sync

Re: UE Initiated Dedicated Bearer

Hello Giacinto, On Mon, Apr 26, 2021 at 11:51 AM Giacinto Cifelli wrote: > Hello Jack, > > what is your modem? Does it support secondary PDNs? > We are using the EM7411. Yes it does, we have also tested and verified that with a Network Initiated dedicated bearer the same QOS we have requested

Re: UE Initiated Dedicated Bearer

Hello Jack, what is your modem? Does it support secondary PDNs? And - mainly - does your subscription support the QOS that you have requested? Maybe you can switch to a more talkative error report, like AT+CMEE=2 Regards, Giacinto On Mon, Apr 26, 2021 at 5:43 PM Jack Broderick wrote: > >

UE Initiated Dedicated Bearer

Hello, I am currently attempting to setup multiple PDN connections to support QOS by creating a dedicated bearer, configuring the QOS profile and Traffic Flow Template, then sending a request to the MME for this second context. I have been following the 3GPP AT command guide to no avail: 1.

Re: problems with QMI dual stack connections from MM - works with qmicli

Aleksander Morgado writes: >> Some observations: >> >> - dual-stack fails if default bearer is connected as ipv4 only > > Oh, but this is expected, isn't it? or is it not expected? I have > always assumed that to be the case. Yes, I guess it is expected. It was mostly the APN change that

Re: problems with QMI dual stack connections from MM - works with qmicli

Hey, > >> > Well, the direct reason is clear from the log: We skip the > >> > CONNECT_STEP_IP_FAMILY_IPV4 step for bearer2+. So we can connect > >> > multiple IPv6 bearers after the first one. Just not any IPv4 or > >> > dual-stack. > >> > >> OK, an extra debug line proves that this is because

Re: problems with QMI dual stack connections from MM - works with qmicli

Aleksander Morgado writes: > Hey, > >> > Well, the direct reason is clear from the log: We skip the >> > CONNECT_STEP_IP_FAMILY_IPV4 step for bearer2+. So we can connect >> > multiple IPv6 bearers after the first one. Just not any IPv4 or >> > dual-stack. >> >> OK, an extra debug line proves

Re: problems with QMI dual stack connections from MM - works with qmicli

Hey, > > Well, the direct reason is clear from the log: We skip the > > CONNECT_STEP_IP_FAMILY_IPV4 step for bearer2+. So we can connect > > multiple IPv6 bearers after the first one. Just not any IPv4 or > > dual-stack. > > OK, an extra debug line proves that this is because of the only