(In reply to comment #0)
> Forwarded from downstream Debian bug report:
> 
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718886
> 
> "I have a MultiSIM setup where my phone number is routed to multiple MEs,
> with all of them ringing at once. If any of the SIM cards is active in a
> modem run with libqmi, the call is rejected immediately and sent to
> voicebox.
> 
> This means my phone no longer rings while I'm online."

That is weird, very weird. libqmi doesn't even support the Voice service yet, so we do not explicitly process any incoming calls anywhere.

Is this when using ModemManager with QMI support? Or plain qmicli-based setup? If the former, can you manually run ModemManager to gather debug logs? See:
http://www.freedesktop.org/wiki/Software/ModemManager/Debugging/

Hi,

this is plain libqmi, with a Sierra Wireless modem:

[ 4467.638086] usb 3-1.5: New USB device found, idVendor=1199, idProduct=68a2
[ 4467.638093] usb 3-1.5: New USB device strings: Mfr=3, Product=2, SerialNumber=0
[ 4467.638097] usb 3-1.5: Product: MC7710
[ 4467.638101] usb 3-1.5: Manufacturer: Sierra Wireless, Incorporated

(In reply to comment #2)
> Hi,
> 
> this is plain libqmi, with a Sierra Wireless modem:
> 
> [ 4467.638086] usb 3-1.5: New USB device found, idVendor=1199, idProduct=68a2
> [ 4467.638093] usb 3-1.5: New USB device strings: Mfr=3, Product=2,
> SerialNumber=0
> [ 4467.638097] usb 3-1.5: Product: MC7710
> [ 4467.638101] usb 3-1.5: Manufacturer: Sierra Wireless, Incorporated

So which is the application using libqmi? Your own qmicli commands? Or...

I run qmicli from /etc/network/interfaces:

iface wwan0 inet dhcp
        pre-up qmicli -d /dev/cdc-wdm0 --dms-uim-verify-pin=PIN,xxxx
        pre-up qmi-network /dev/cdc-wdm0 start

(In reply to comment #4)
> I run qmicli from /etc/network/interfaces:
> 
> iface wwan0 inet dhcp
>         pre-up qmicli -d /dev/cdc-wdm0 --dms-uim-verify-pin=PIN,xxxx
>         pre-up qmi-network /dev/cdc-wdm0 start

Oh, ok... hard to gather unsolicited indications reported by the modem when no application is actually listening to them (qmi-network just calls qmicli internally, so no app is actually really reading from the port while connected).

Anyway; this behaviour is really handled by the modem firmware; the modem detects that there is an active connection ongoing and decides to tell the network that it cannot handle the call. What to do with that? hard to tell... There may be some configuration that I don't know about in the QMI services to handle this situation... no idea.

Are you sure you have the latest firmware version? Which revision do you have?

For workarounds, maybe your provider let you control if the extra SIM should ring? I have an option to let it ring the primary SIM first instead of simultaniously at both.

I'm going to close this as wontfix; I don't really think we can do anything with this at libqmi level...