Jump to content

Calling Plus (VoLTE "Lite")


Recommended Posts

Is anyone testing Calling Plus in the wild? The two devices currently compatible are the LG Stylo 3 and Samsung J7 Perx. The service supposedly went live on 5/31/17.

 

"Calling Plus" bullet points, gathered from Reddit:

  • Voice is transmitted over LTE
  • Voice is not prioritized at the network level like in a traditional VoLTE implementation (Saturated LTE will cause call quality degradation)
  • Simultaneous voice and data
  • VoLTE/VoWi-Fi smooth handoffs both ways
  • No 1x fallback
I'm really interested in hearing early impressions of this quiet rollout.
  • Like 6
Link to comment
Share on other sites

I have a J7 that I just flashed the build on. The initial setup was straight forward, similar to enabling WIFI Calling, the user is prompted with a toggle to enable calls over LTE. I haven't tested any calls yet, but will do so tomorrow.

 

The one challenge I have is that my apartment building elevator is an RF blackhole, so I'll hand off from WIFI to 1x to 3G before reconnecting with LTE.

  • Like 5
Link to comment
Share on other sites

No QoS like the other 3? That won't be good. Their network is already saturated enough as is in some areas.

  • Like 9
Link to comment
Share on other sites

No QoS like the other 3? That won't be good. Their network is already saturated enough as is in some areas.

 

Yeah this is concerning; is this confirmed and is there a reason to this? I'm mostly concerned because I've noticed when band 41 gets (really) congested, ping times and uplink suffer, so I imagine this would have negative consequences if VoLTE isn't prioritized. 

  • Like 3
Link to comment
Share on other sites

No QoS - yet. This is just an early implementation for testing voice over LTE with a very small sample size. It's only on these two devices, I'd imagine by the time it hits the iPhone it will be full blown VoLTE with QoS. (Who knows, that could be a year off, or more.) 

  • Like 2
Link to comment
Share on other sites

I have a J7 that I just flashed the build on. The initial setup was straight forward, similar to enabling WIFI Calling, the user is prompted with a toggle to enable calls over LTE. I haven't tested any calls yet, but will do so tomorrow.

 

The one challenge I have is that my apartment building elevator is an RF blackhole, so I'll hand off from WIFI to 1x to 3G before reconnecting with LTE.

A few screenshots of the menu would be appreciated.
  • Like 3
Link to comment
Share on other sites

No QoS like the other 3? That won't be good. Their network is already saturated enough as is in some areas.

 

This isn't true VoLTE in the complete sense, just a way to route audio calls over LTE rather than 1x/PSTN.

 

That's why there is a giant BETA disclaimer on it.

  • Like 2
Link to comment
Share on other sites

It looks like an over the top solution like using messenger or FaceTime to make data calls to me.

 

Sent from my LG-LS993 using Tapatalk

 

No, not really. Think of it as an extension of the WiFi Calling already built into the device.

  • Like 1
Link to comment
Share on other sites

No, not really. Think of it as an extension of the WiFi Calling already built into the device.

If there's no network prioritization for a data call on LTE how is it different besides using the stock dialer?

 

Sent from my LG-LS993 using Tapatalk

  • Like 1
Link to comment
Share on other sites

Since I am not familiar with the new wifi calling setup (the one released in 2016), and Sprint's Calling Plus implementation is, from what I've heard, essentially wifi calling over LTE, is there a reason why a call could not be handed to eHRPD/EVDO as a data session? Probably a dumb question but just wanted to see if someone with more knowledge could chime in...

  • Like 1
Link to comment
Share on other sites

If there's no network prioritization for a data call on LTE how is it different besides using the stock dialer?

 

Sent from my LG-LS993 using Tapatalk

 

Because this is a beta service. 

  • Like 1
Link to comment
Share on other sites

I took some screenshots of the device enabled with Calling Plus.

 

 

 

 

 

 

 

 

 

 

 

How's the user experience in fringe lte / 1x spots?

  • Like 2
Link to comment
Share on other sites

How's the user experience in fringe lte / 1x spots?

 

I'll do some testing today and see how it works. I'm pretty sure the call will drop if the signal is that weak.

  • Like 2
Link to comment
Share on other sites

...Sprint's Calling Plus implementation is, from what I've heard, essentially wifi calling over LTE, is there a reason why a call could not be handed to eHRPD/EVDO as a data session?

 

EV-DO is a legacy system on a different pool of IP addresses.  A drop from LTE to EV-DO is not a handoff.  It requires a new data session with a new IP address.  A call in progress would not survive.

 

AJ

  • Like 6
Link to comment
Share on other sites

EV-DO is a legacy system on a different pool of IP addresses. A drop from LTE to EV-DO is not a handoff. It requires a new data session with a new IP address. A call in progress would not survive.

 

AJ

How about eHRPD?

  • Like 1
Link to comment
Share on other sites

eHRPD is pretty much EV-DO, the call would still drop going from LTE to eHRPD.

Why? eHRPD is EV-DO routed through the LTE core network. If the VoLTE call is essentially a data session (which is my current understanding) and the network has the ability to instruct your device to smoothly handoff from LTE to eHRPD (through an RRC release), why would the call drop? Data is data, right?

 

This is the only reason I can come up with as to why Sprint didn't do a full VoLTE implementation with QoS and all. A more over-the-top solution has the potential to run on networks other than LTE (it already runs on wifi) and with Sprint's ability to push devices both from LTE to 3G (with an RRC release) and from 3G to LTE (using the OtherRATNeighborList message), it seems like they might be trying to do something slightly unconventional to allow a CDMA fallback...

  • Like 7
Link to comment
Share on other sites

Why? eHRPD is EV-DO routed through the LTE core network. If the VoLTE call is essentially a data session (which is my current understanding) and the network has the ability to instruct your device to smoothly handoff from LTE to eHRPD (through an RRC release), why would the call drop? Data is data, right?

 

This is the only reason I can come up with as to why Sprint didn't do a full VoLTE implementation with QoS and all. A more over-the-top solution has the potential to run on networks other than LTE (it already runs on wifi) and with Sprint's ability to push devices both from LTE to 3G (with an RRC release) and from 3G to LTE (using the OtherRATNeighborList message), it seems like they might be trying to do something slightly unconventional to allow a CDMA fallback...

 

It's hard to find non-LTE areas where I live, will do some additional testing tomorrow on my commute home. LTE site density in NYC is not conducive for that type of testing :)

  • Like 2
Link to comment
Share on other sites

 

 

Why? eHRPD is EV-DO routed through the LTE core network. If the VoLTE call is essentially a data session (which is my current understanding) and the network has the ability to instruct your device to smoothly handoff from LTE to eHRPD (through an RRC release), why would the call drop? Data is data, right?

I read (a little) about rrc release from eNB to UE in context of a data session.

 

Is the eNB equipment fast enough to issue an RRC release with carrier balancing to not cause the call to fail? I know loading a web page or video can lag a little and it's not a big deal, but if that occurs on a voice call would it drop, or suffer decrease quality?

 

 

Sent from my SM-G930P using Tapatalk

  • Like 1
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • Was able to install the March 1 Android security patch. Seems slightly more accurate with 5g ca band id, but can not swear by it. Updated google play system update through the software information screen to March 1. *#73# still works. Froze updates waiting on SCP update beta to fix n41 showing as n38.
    • Just installed it. Thanks for the info.  71 mb mar 1st date.
    • There's a permit for a new 47 story building at 205 Montague St in Downtown Brooklyn. The problem is that  T-Mobile eNB 48352 is on the building next door and this new building will block two out of 3 sectors of the site. For reference, the new building will be roughly as tall as 16 Court St which is right across the street. This site is the primary site covering Cadman Plaza so I wonder what the plan is. Will they just try to change sector placement, move to a different building, or will this just speed up the conversion of the Sprint site at 25 Monroe Place?
    • At least not recently.  I think I might have seen this a year ago.  Not Sure.
    • Did they previously hop between n38 and n41 in prior version of SCP, or have you always seen n41 displayed properly?
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...