Imcoming calls through Fritz fon app

General
1

Hi everybody,

is anybody using iode on his phone and a Fritzbox as router?

I’d like to use my phone to receive incoming calls, at least when I’m at home and in my wifi. Unfortunately nothing’s happening on my phone when somebody calls.

This has always worked on a non-iode Android phone of mine.

I have already checked the permissions, turned off multiple battery optimization options, the permissions and also on the Fritzbox if the phone is configured to receive incoming calls. Can’t find any mistake there either.

iode blocker stream view doesn’t show any blocked connections.

In addition I’ve consulted this AVM FAQ entry: FRITZ!App Fon klingelt nicht bei Anrufen | FRITZ!App Fon | AVM Deutschland

Is anybody here using my constallation successfully receiving calls on his phone?

Best regards,
Jens

2

The AVM app is crap. It doesn’t work here, neither on iodé, /e/OS nor VollaOS. I sent a feedback (from the app), but to no avail.

3

I also have a Fritzbox for the telephone at home.
For calls I use the app Linphone. You can use this app as a normal IP phone client via SIP. You just need to enter your password and the IP of your fritzbox and choose UDP for the transport. In the advanced settings you can then activate the background mode to receive incoming calls.
I use the Fritz fon app only to access the telephone book.

4

Thanks!

I had read that the router can act as a sip server as well. I’ve given this a try yesterday already. It’s working as long as my phone is in the router’s wifi. But in my cases that’s not really my home network. There’s just the Fritzbox and my regular firewall.
When you’re not in the Fritzbox’s wifi, it appears it refuses connections from other subnets.

I’ll see if it’s possible to achieve this through some kind of NAT.

5

I can confirm that incoming calls with local WiFi connection is not working as of now with app versions 2.12.2 and 2.12.1.

Afair it worked in the past, didn’t try that since longer time.

Outbound calls are working.

Activated debug log, incoming call is received, but not processed proper by app:

  7204 13185 D GmsGcmMcsInput: Incoming message: DataMessageStanza{id=*, from=*, to=*, category=de.avm.android.fritzapp, app_data=[AppData{key=google.c.sender.id, value_=*}, AppData{key=ciphertext, value_=*}, AppData{key=tag, value_=*}, AppData{key=protected, value_=*}, AppData{key=iv, value_=*}, AppData{key=aad, value_=*}], persistent_id=*, last_stream_id_received=3, ttl=20, sent=*}
08-09 08:12:15.052  4632 13571 I audio_hw_proxy_9810: primary_in-proxy_start_capture_stream: started PCM Device
08-09 08:12:15.052  4632 13571 I audio_hw_primary: primary_in-in_read: transited to Capturing
08-09 08:12:15.052  4632 13571 D audio_hw_primary: in_read: reconfig_delay_ms 15
08-09 08:12:15.063  7204 13185 D GmsGcmMcsSvc: Adding app de.avm.android.fritzapp to the temp allowlist 
08-09 08:12:15.069  7204 13185 D GmsGcmMcsSvc: Deliver message to all receivers in package de.avm.android.fritzapp
08-09 08:12:15.075  7204  7204 D GmsGcmRegister: onBind: Intent { act=com.google.android.c2dm.intent.REGISTER pkg=com.google.android.gms }
08-09 08:12:15.076  7204  7204 D GmsGcmRegister: handleMessage: package=de.avm.android.fritzapp what=2 id=8
08-09 08:12:15.076  7204  7204 D GmsGcmRegister: Ack * for de.avm.android.fritzapp
08-09 08:12:15.087  7204  8945 D GmsGcmMcsSvc: Ack initiated, reason: Intent { act=org.microg.gms.gcm.mcs.ACK cmp=com.google.android.gms/org.microg.gms.gcm.McsService (has extras) }
08-09 08:12:15.091  7204  7204 D GmsGcmRegister: onBind: Intent { act=com.google.android.c2dm.intent.REGISTER pkg=com.google.android.gms }
08-09 08:12:15.092  7204 13186 D GmsGcmMcsOutput: Outgoing message: IqStanza{type=SET, id=, extension=Extension{id=13, data_=[size=0]}, last_stream_id_received=5, status=0}
08-09 08:12:15.095  7204  7204 D GmsGcmRegister: handleMessage: package=de.avm.android.fritzapp what=3 id=9

App is registered to microg.gms - any idea which settings may block this further?

required condition application option is active: “Auf Anrufe reagieren”

6

Thanks for confirming I’m not the only one.

Looks like getting this to work shouldn’t be too hard for AVM. I guess they are just not interested. :roll_eyes: