Fwd: Cinterion plugin patch

[matthew stanger]

Sorry I sent that last email a little prematurely, was still targeting my
email client and ctrl-entered for another window. You can disregard that
second comment, I see what you did for IP config. Last little things:

    /* Get a tet port to setup the connection on */
>
>
>
net*

There is also some spam warning messages in the logs every 30 secs. I
believe it's related to the new connection status monitory you recently
added. I'm guessing because we have the custom code for cgdcont/cid in the
Cinterion bearer and it's not getting populated for the mm-base-bearer? Not
an issue but just thought I'd mention it.

<debug> [1480215431.485739] [mm-iface-modem.c:1204]
update_signal_quality(): Modem /org/freedesktop/ModemManager1/Modem/0:
signal quality updated (40)
<warn>  [1480215435.426725] [mm-base-bearer.c:165]
load_connection_status_ready(): checking if connected failed: Couldn't load
connection status: cid not defined
<warn>  [1480215440.428026] [mm-base-bearer.c:165]
load_connection_status_ready(): checking if connected failed: Couldn't load
connection status: cid not defined
<warn>  [1480215445.427338] [mm-base-bearer.c:165]
load_connection_status_ready(): checking if connected failed: Couldn't load
connection status: cid not defined
<warn>  [1480215450.427193] [mm-base-bearer.c:165]
load_connection_status_ready(): checking if connected failed: Couldn't load
connection status: cid not defined
<warn>  [1480215455.427746] [mm-base-bearer.c:165]
load_connection_status_ready(): checking if connected failed: Couldn't load
connection status: cid not defined
<warn>  [1480215460.426707] [mm-base-bearer.c:165]
load_connection_status_ready(): checking if connected failed: Couldn't load
connection status: cid not defined
<debug> [1480215461.423502] [mm-port-serial.c:1288] mm_port_serial_open():
(ttyACM1) device open count is 2 (open)



The code works on my PLS8-X after testing.

Cheers,


On Sat, Nov 26, 2016 at 7:47 PM, matthew stanger <stangerm2 at gmail.com>
wrote:

> Code looks awesome (*¬*), so much to learn for me. A few comments which
> are all trivial and really don't need to be included but in attempt to be
> as detailed as you
>>
>>
>>  * The PDP context mapping is as suggested by Cinterion, although it
>> looks like
>>  * this isn't strictly enforced by the modem; i.e. SWWAN could work fine
>> with
>>  * any PDP context vs SWWAN interface mapping.
>
>
> It's really stupid but the reason for this mapping is for the PLS-X only,
> specifically when using Verizon Wireless as a carrier. As I interpret it
> this would also mean Verizon wouldn't be able to support dual SIM
> connections either. When I get to the dual SIM patch I'll be sure to keep
> it in mind but for now it's just an FYI.
>
>   /* Map PDP context from the current Bearer. USB0 -> 3rd context, USB1 ->
> 1st context.
>      * In Verizon Wireless networks PDP contexts with APN class 1, 2 and 4
> are dedicated to specific profile settings
>      * for LTE (see AT^SGAPN), meaning that <cid> 1, 2 and 4 are not
> allowed to be used for DUN, WWAN (RmNet)
>      * or IP service connections. */
>
>     switch (ctx->step) {
>>
>>     case CONNECT_3GPP_CONTEXT_STEP_FIRST: {
>>
>>         MMBearerIpFamily ip_family;
>>
>>
>
> Just curious why we moved this back to the 1st step? I thought you didn't
> want to create MBearerIpConfig before knowing if the modem is connected?
>
>
> On Fri, Nov 25, 2016 at 5:46 PM, Andrew Bird <ajb at spheresystems.co.uk>
> wrote:
>
>> On Fri, 25 Nov 2016 21:16:55 +0100
>> Reinhard Speyerer <rspmn at arcor.de> wrote:
>>
>> > On Fri, Nov 25, 2016 at 10:13:08AM +0100, Aleksander Morgado wrote:
>> > > Hey Reinhard & Matthew,
>> > >
>> > > On Thu, Nov 24, 2016 at 10:34 PM, Reinhard Speyerer <rspmn at arcor.de>
>> wrote:
>> > > [...]
>> > > > PLS8-E REVISION 02.011:
>> > > > +CUSD: 1,"Hauptmen~:\0A1 Guthabenkonto\0A2 Guthaben
>> Verf~gbarkeit\0A3 Gutschein einl|sen\0A4 Pack Manager\0A7 Tarifinfo\0A8
>> Hilfe",15
>> > >
>> > > Any idea if this has any impact on how ModemManager handles USSD in
>> > > this device? Or is this only an issue to the consumer of the USSD
>> > > responses?
>> >
>> > Hi Aleksander,
>> >
>> > I think ModemManager should replace the \xx escapes for devices which
>> > apply them like PLS8 with firmware 02.x and 03.x with the corresponding
>> > character before passing the +CUSD: string to the consumer of the USSD
>> > response.
>> >
>> > Regards,
>> > Reinhard
>>
>> Sorry to butt in, but if you do that won't any USSD messages that have
>> backslashes embedded be mistaken for the badly encoded ones and fixed up
>> erroneously.
>>
>> --
>> Andrew Bird <ajb at spheresystems.co.uk>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/modemmanager-devel/attachments/20161126/844d76c5/attachment.html>