Description
Hi, thanks for your app!
Polish operator - Orange - works well! VoWIFI and VoLTE - great!
Polish operator - Plus - works well! VoWIFI and VoLTE - great!
Polish operator - T-Mobile - VoWIFI, VoLTE not working at all, i see thet phone asks for edge servers via WiFi but dont attepming to connect.
Polish operator - Play - works well! VoLTE - but no VoWIFi.
I see that there is trying to connect to edge operator server and after some handshake connection dropped logs below.
Maybe some is verified ? Maybe usser agent? I see this can be modified - how to check other User Agent? For example from working samsung?
TCPDUMP for Play:
16:41:47.879021 IP 192.168.253.195.47741 > 89.108.200.112.500: isakmp: parent_sa ikev2_init
16:41:47.919832 IP 89.108.200.112.500 > 192.168.253.195.47741: isakmp: parent_sa ikev2_init[R]
16:41:47.942979 IP 192.168.253.195.43066 > 89.108.200.112.500: isakmp: parent_sa ikev2_init
16:41:47.983686 IP 89.108.200.112.500 > 192.168.253.195.43066: isakmp: parent_sa ikev2_init[R]
16:41:48.016234 IP 192.168.253.195.53081 > 89.108.200.112.4500: NONESP-encap: isakmp: child_sa ikev2_auth
16:41:48.163529 IP 89.108.200.112.4500 > 192.168.253.195.53081: NONESP-encap: isakmp: child_sa ikev2_auth[R]
16:41:48.315983 IP 192.168.253.195.53081 > 89.108.200.112.4500: NONESP-encap: isakmp: child_sa ikev2_auth
16:41:48.406161 IP 89.108.200.112.4500 > 192.168.253.195.53081: NONESP-encap: isakmp: child_sa ikev2_auth[R]
16:41:48.417290 IP 192.168.253.195.53081 > 89.108.200.112.4500: NONESP-encap: isakmp: child_sa ikev2_auth
16:41:48.481634 IP 89.108.200.112.4500 > 192.168.253.195.53081: UDP-encap: ESP(spi=0x59cfb5b6,seq=0x1), length 168
16:41:48.481688 IP 89.108.200.112.4500 > 192.168.253.195.53081: NONESP-encap: isakmp: child_sa ikev2_auth[R]
16:41:49.730284 IP 192.168.253.195.53081 > 89.108.200.112.4500: UDP-encap: ESP(spi=0x051b016c,seq=0x1), length 1304
16:41:49.730285 IP 192.168.253.195.53081 > 89.108.200.112.4500: UDP-encap: ESP(spi=0x051b016c,seq=0x2), length 1128
16:41:49.795468 IP 89.108.200.112.4500 > 192.168.253.195.53081: UDP-encap: ESP(spi=0x59cfb5b6,seq=0x2), length 168
16:41:50.104259 IP 89.108.200.112.4500 > 192.168.253.195.53081: UDP-encap: ESP(spi=0x59cfb5b6,seq=0x3), length 1464
16:41:50.169513 IP 192.168.253.195.53081 > 89.108.200.112.4500: UDP-encap: ESP(spi=0x051b016c,seq=0x3), length 168
16:41:50.193627 IP 89.108.200.112.4500 > 192.168.253.195.53081: UDP-encap: ESP(spi=0x59cfb5b6,seq=0x4), length 936
16:41:50.219036 IP 89.108.200.112.4500 > 192.168.253.195.53081: UDP-encap: ESP(spi=0x59cfb5b6,seq=0x5), length 792
16:41:50.223319 IP 192.168.253.195.53081 > 89.108.200.112.4500: UDP-encap: ESP(spi=0x051b016c,seq=0x4), length 168
16:41:50.246168 IP 192.168.253.195.53081 > 89.108.200.112.4500: UDP-encap: ESP(spi=0x051b016c,seq=0x5), length 168
16:41:50.246168 IP 192.168.253.195.53081 > 89.108.200.112.4500: UDP-encap: ESP(spi=0x051b016c,seq=0x6), length 168
16:41:50.249155 IP 192.168.253.195.53081 > 89.108.200.112.4500: UDP-encap: ESP(spi=0x051b016c,seq=0x7), length 168
16:41:50.265083 IP 192.168.253.195.53081 > 89.108.200.112.4500: UDP-encap: ESP(spi=0x051b016c,seq=0x8), length 168
16:41:50.267608 IP 192.168.253.195.53081 > 89.108.200.112.4500: UDP-encap: ESP(spi=0x051b016c,seq=0x9), length 168
16:41:50.282822 IP 192.168.253.195.53081 > 89.108.200.112.4500: UDP-encap: ESP(spi=0x051b016c,seq=0xa), length 120
16:41:50.295657 IP 89.108.200.112.4500 > 192.168.253.195.53081: UDP-encap: ESP(spi=0x59cfb5b6,seq=0x6), length 168
16:41:50.295713 IP 89.108.200.112.4500 > 192.168.253.195.53081: UDP-encap: ESP(spi=0x59cfb5b6,seq=0x7), length 168
16:41:50.317985 IP 89.108.200.112.4500 > 192.168.253.195.53081: UDP-encap: ESP(spi=0x59cfb5b6,seq=0x8), length 168
16:41:50.318042 IP 89.108.200.112.4500 > 192.168.253.195.53081: UDP-encap: ESP(spi=0x59cfb5b6,seq=0x9), length 168
16:41:50.359287 IP 192.168.253.195.53081 > 89.108.200.112.4500: NONESP-encap: isakmp: child_sa inf2
16:41:50.399064 IP 89.108.200.112.4500 > 192.168.253.195.53081: NONESP-encap: isakmp: child_sa inf2[R]
Activity
JaCzekanski commentedon Feb 9, 2023
Can confirm the same behavior on Pixel 6 with Play SIM card - VoLTE works (it actually did without this hack), VoWIFI does not.
bige93 commentedon Feb 9, 2023
Same here with Pixel 6 running on T-Mobile Poland network.
Since Android 13 VoLTE works on Pixel 6 out of the box, but not WiFi Calling.
I followed your instructions and run the script, then switched WiFi Calling on in the app.
WiFi Calling setting appeared right away, however I couldn't force it to work even after few reboots.
On top of that, whenever WiFi Calling is enabled in the device settings, phone can't register for VoLTE and calls are being placed over 3G.
Carrier supports WiFi Calling and I have it enabled on my line (I was using it with iPhone 7 previously).
Thanks!
adryb commentedon Feb 9, 2023
I had a chance to check the same - with root and Magisk module - the same with Play - VoLTE works, VoWIFI trying to connect as with your application.
@kyujin-cho can you help me with troubleshoot? I can do this on rooted firmware with root access.
kyujin-cho commentedon Feb 9, 2023
Hi! Thanks for the report. Method to retrieve IMS User-Agent value varies by manufacturer. For example, in Pixel, you need to dial ##0702## from default dialer and look up for IMS_USER_AGENT.
adryb commentedon Feb 9, 2023
On my pixel - stock rom - this code not works -> ##0702## its going as ussd.
JaCzekanski commentedon Feb 10, 2023
@adryb I think it's supposed to be
*#*#0702#*#*adryb commentedon Feb 10, 2023
Ok on google its:
#MANUFACTURE#_#MODEL#Android #AV##BUILD#
danparidae commentedon Feb 10, 2023
For me on Pixel 6 and Play sim it's
#MANUFACTURE#_#MODEL#_Android #AV#_#BUILD#adryb commentedon Feb 18, 2023
I made a lot of tests, on rooted phone too. Tried to capture traffic on phone side - in ipsec tunnel there is sedond tunnel that communicates with operator devces, i see only that fter some handshake(?) operator closes connection.
Its not related to patch.
kszaq commentedon Feb 18, 2023
@adryb Can you post a result of
adb shell dumpsys carrier_configwith Play SIM?adryb commentedon Feb 18, 2023
Sure. Attached.
cc_pixel.log
kszaq commentedon Feb 18, 2023
Thanks. The only difference I can see between Orange PL (working) and Play (not working) is that for Play, "ims" APN is defined in carrier settings. Can you try to add APN "ims" with any name and only APN type set to "ims", other options at default?
adryb commentedon Feb 18, 2023
Yep! That worked!!!!! IM ABLE TO CALL VIA VOWIFI!!!!
Which line this shows you?
kszaq commentedon Feb 18, 2023
It's not a line from
carrier_config. I looked at carrier settings in/system/product/etcCarrierSettings/. You can decode them usingprotoc --decode_raw. For Play,imsAPN is defined for only some bearers, I assume LTE and UMTS and because of this it's not used for IWLAN. If you redefineimswith no bearer, it is used for all network types and makes IMS register over WLAN.24 remaining items
mr-tical commentedon Apr 11, 2023
Do you guys have possibility to check this on Plus?
Edit: hmmm, strange, did nothing and VoWiFi started to work too.
mr-tical commentedon Apr 14, 2023
Patch is working on Android 14 beta 1
VoWiFi and VoLTE
PL Plus
artproject-2004 commentedon Sep 7, 2023
Hi, I can't configure out Pixel IMS service on Pixel 7 (Virgin mobile PL - now a part of PLAY carrier). I tried with/without ims APN but still without success. IMS status unregistered.
fillwithjoy1 commentedon Jan 17, 2024
funny thing is that wifi calling on the iphone is a different platform to support than to wifi calling on android
fillwithjoy1 commentedon Jan 17, 2024
also is this issue relevant now?
fillwithjoy1 commentedon Feb 16, 2024
@kyujin-cho requesting to close the issue
szmarczak commentedon Jul 5, 2024
I'm using nju mobile and WiFi calling doesn't work even after adding the ims apn (nothing phone 2).
Edit: I tried a carrier certified device (Samsung a53) and it still does not work. So my case is not relevant here and I need to contact my carrier's support.
fillwithjoy1 commentedon Jul 8, 2024
Well, how interesting that it's the carrier's issue...
samuelgarabini commentedon Nov 10, 2024
@kszaq Can you help me with my problem? #323
kszaq commentedon Nov 11, 2024
First make sure that it is working with your SIM on another phone. Sometimes operators need VoWiFi to be activated by accepting terms & conditions.
samuelgarabini commentedon Nov 11, 2024
Yes, it it is working. When I try in a different phone, both VoWifi and VoLTE works, but mine only VoLTE. I tried everything today. I appreacite if you could help me
kszaq commentedon Nov 11, 2024
The only thing I can recommend is that you delete "IMS" APN and re-add it, making sure that "bearer" is "not specified" only. If this doesn't work, it is possible that your network operator does not allow your phone to use VoWiFi.
samuelgarabini commentedon Nov 11, 2024
What do I need to mark besides "not specified"? Everything?