so, since upgrading to iOS 9 GM, I have noticed that when in a low HSPA+ signal area with Wi-Fi calling enabled, but not active...once the phone signal reaches the threshold where Wi-Fi calling would normally enable itself, the call will go silent. It doesn't drop, both ends remain connected, but both ends are totally silent like someone has muted the phone. Disconnecting. The call results in AT&T Wi-Fi immediately popping up in the status bar, and placing the call over Wi-Fi works flawlessly. If I disable Wi-Fi calling, and place the call over the cellular network in the same low signal area, the call also works flawlessly.
It seems like Wi-Fi is trying to enable itself during the call, but it's not supposed to be, thus the phone doesn't know what to do. It seems like the simple remedy would be to allow Wi-Fi calling to work like it does with T-Mobile, and activate anytime you're on Wi-Fi instead of only when signal levels are low. Also, I'm not in a VoLTE area, so it can't switch between Wi-Fi and cellular network seamlessly. From what I understand, it's not supposed to even attempt the switch once you have already placed the call from the cellular network, only when initially placing the call on the Wi-Fi network, and moving out of wireless range.
Anyone else seeing the same issue since upgrading? Bug report has already been submitted, so hopefully 9.1 can have this resolved.
It seems like Wi-Fi is trying to enable itself during the call, but it's not supposed to be, thus the phone doesn't know what to do. It seems like the simple remedy would be to allow Wi-Fi calling to work like it does with T-Mobile, and activate anytime you're on Wi-Fi instead of only when signal levels are low. Also, I'm not in a VoLTE area, so it can't switch between Wi-Fi and cellular network seamlessly. From what I understand, it's not supposed to even attempt the switch once you have already placed the call from the cellular network, only when initially placing the call on the Wi-Fi network, and moving out of wireless range.
Anyone else seeing the same issue since upgrading? Bug report has already been submitted, so hopefully 9.1 can have this resolved.