Jump to content

Calling Plus (VoLTE "Lite")


Recommended Posts

My call quality has been hit and miss especially on fragile B41.  Anything around RSRP -110 or worse, people on the other-side cannot hear me.  Sprint will really need to work on handing this off to B25/B26.  Is this even possible for it to switch bands when signal is weak on B41?
Sure it is. The eNB completely controls it. With proper VoLTE I imagine it will take being on a call into consideration for band selection.

Sent from my Pixel 2 XL using Tapatalk

Link to comment
Share on other sites

31 minutes ago, ingenium said:

Sure it is. The eNB completely controls it. With proper VoLTE I imagine it will take being on a call into consideration for band selection.

Sent from my Pixel 2 XL using Tapatalk
 

I hope so.  I am on B41 75% of the time, with config 2 in place the upload stuffers and calls over LTE also suffers.  Calls over B25 works so much better at the moment in my area.

Link to comment
Share on other sites

2 hours ago, bucdenny said:

My call quality has been hit and miss especially on fragile B41.  Anything around RSRP -110 or worse, people on the other-side cannot hear me.  Sprint will really need to work on handing this off to B25/B26.  Is this even possible for it to switch bands when signal is weak on B41?

This is the downside of a VOIP based setup like Calling Plus. In a full VoLTE setup voice packets are prioritized and the eNB will do whatever is needed to maintain voice quality / continuity. 

  • Like 1
Link to comment
Share on other sites

1 hour ago, lilotimz said:

This is the downside of a VOIP based setup like Calling Plus. In a full VoLTE setup voice packets are prioritized and the eNB will do whatever is needed to maintain voice quality / continuity. 

Poor handset RF performance also could be in play.  A -110 dBm RSRP on band 41 downlink should be fine for Calling Plus.  But if the handset is weak on band 41 uplink, it could be running out of uplink power at that signal level.

AJ

Link to comment
Share on other sites

6 minutes ago, WiWavelength said:

Poor handset RF performance also could be in play.  A -110 dBm RSRP on band 41 downlink should be fine for Calling Plus.  But if the handset is weak on band 41 uplink, it could be running out of uplink power at that signal level.

AJ

Would config 2 make it worse on the uplink side? Or in this case it wouldn't matter as the RF performance on the uplink is terrible.  Im on a S8+ HPUE device. 

Link to comment
Share on other sites

21 minutes ago, WiWavelength said:

Poor handset RF performance also could be in play.  A -110 dBm RSRP on band 41 downlink should be fine for Calling Plus.  But if the handset is weak on band 41 uplink, it could be running out of uplink power at that signal level.

AJ

Config 2 doesn’t help things either. Since the change to Config 2, even with a -80 dBm signal, I have trouble pulling more than 5 mbps upload. At -110 dBm, I’m lucky to pull half a megabit. 

Link to comment
Share on other sites

1 hour ago, RAvirani said:

Config 2 doesn’t help things either. Since the change to Config 2, even with a -80 dBm signal, I have trouble pulling more than 5 mbps upload. At -110 dBm, I’m lucky to pull half a megabit. 

Yes, but 0.5 Mbps uplink at -110 dBm RSRP on the downlink is at least an order of magnitude greater than what is needed to support Calling Plus.  Unless network congestion is a factor, uplink data speeds alone are not the bottleneck.  Rather, if those uplink data speeds are low because of retransmissions due to poor handset uplink RF output, then the uplink may have difficulty keeping up with near real time Calling Plus transmissions, even at 0.5 Mbps.

AJ

Link to comment
Share on other sites

1 hour ago, bucdenny said:

Im on a S8+ HPUE device. 

From what I recall of real world usage reports from last summer, many have concluded that the Samsung Galaxy S8 is a disappointing HPUE performer.

AJ

Link to comment
Share on other sites

20 minutes ago, Galaxyguy said:

From my personal experience, it seems my S8+ will start out on any band, but if it happens to go to B26, it likes to stay there for the remainder of the call, even when getting close to a tower. 

I am in B25/B41 only market.  I am on B41 75% of the time.  The problem is once its on B41 for any voice calls it does not switch to B25 when I am on RSRP -110 or worse.  I do not drop calls, but calls goes to crap.  Clients on the other end cannot hear me.  I have to remember each time to turn off VoLTE on my S8+ if I am at my office (fragile B41) or when I am driving because my phone seems to hang on B41 even at RSRP -120 or worse.

Link to comment
Share on other sites

2 hours ago, WiWavelength said:

Yes, but 0.5 Mbps uplink at -110 dBm RSRP on the downlink is at least an order of magnitude greater than what is needed to support Calling Plus.  Unless network congestion is a factor, uplink data speeds alone are not the bottleneck.  Rather, if those uplink data speeds are low because of retransmissions due to poor handset uplink RF output, then the uplink may have difficulty keeping up with near real time Calling Plus transmissions, even at 0.5 Mbps.

AJ

VOIP uses 8kbps to 90kbps up while you are talking and that same speed down while the other person is talking.  The actual bandwidth is based on the algorithm used with higher numbers of bits required for HD voice and lower for regular voice and more bits are used for a larger range of sounds.  The algorithms for streaming audio which VOIP uses automatically adjust the amount of data used based on the range of sounds they are trying to send at that time.  VoLTE is normally in the 16kbps to 32kbps range.

0.5mbps is the same as 500kb/s just to give you some idea of how much bandwidth you really have available.  At the highest possible quality and bit rate of 64kbps to 90kbps (which are almost never used on VoLTE connections) , near CD quality music could be broadcast over your VOIP call.  Those speeds are still less than 20% of your 0.5mbps speed or less than 5% if you are using closer to the minimum amount of standard voice bandwidth.

 

  • Thanks 1
Link to comment
Share on other sites

4 hours ago, WiWavelength said:

Yes, but 0.5 Mbps uplink at -110 dBm RSRP on the downlink is at least an order of magnitude greater than what is needed to support Calling Plus.  Unless network congestion is a factor, uplink data speeds alone are not the bottleneck.  Rather, if those uplink data speeds are low because of retransmissions due to poor handset uplink RF output, then the uplink may have difficulty keeping up with near real time Calling Plus transmissions, even at 0.5 Mbps.

AJ

How would Sprint make it work for these poor RF uplink issues?

Link to comment
Share on other sites

23 minutes ago, bucdenny said:

How would Sprint make it work for these poor RF uplink issues?

Introduce true VoLTE that will prioritize those data packets, and hopefully be more proactive at moving to the more favorable LTE band. Calling Plus seems to be more of a stopgap to buy time while VoLTE on the network is still perfected. 

  • Like 1
Link to comment
Share on other sites

Just now, Dkoellerwx said:

Introduce true VoLTE that will prioritize those data packets, and hopefully be more proactive at moving to the more favorable LTE band. Calling Plus seems to be more of a stopgap to buy time while VoLTE on the network is still perfected. 

And what is preventing Sprint getting true VoLTE out for testing?

Link to comment
Share on other sites

4 hours ago, radem said:

VOIP uses 8kbps to 90kbps up...

Thanks for that elaboration.  But did you mean to quote RAvirani instead of me?  Because I already covered everything you wrote in the simple statement "0.5 Mbps uplink...is at least an order of magnitude greater than what is needed to support Calling Plus."

AJ

Link to comment
Share on other sites

7 hours ago, WiWavelength said:

Yes, but 0.5 Mbps uplink at -110 dBm RSRP on the downlink is at least an order of magnitude greater than what is needed to support Calling Plus.  Unless network congestion is a factor, uplink data speeds alone are not the bottleneck.  Rather, if those uplink data speeds are low because of retransmissions due to poor handset uplink RF output, then the uplink may have difficulty keeping up with near real time Calling Plus transmissions, even at 0.5 Mbps.

AJ

Ah got it. Thanks for the clarification. 

Link to comment
Share on other sites

On 11/14/2017 at 6:40 PM, radem said:

VOIP uses 8kbps to 90kbps up while you are talking and that same speed down while the other person is talking.  The actual bandwidth is based on the algorithm used with higher numbers of bits required for HD voice and lower for regular voice and more bits are used for a larger range of sounds.  The algorithms for streaming audio which VOIP uses automatically adjust the amount of data used based on the range of sounds they are trying to send at that time.  VoLTE is normally in the 16kbps to 32kbps range.

0.5mbps is the same as 500kb/s just to give you some idea of how much bandwidth you really have available.  At the highest possible quality and bit rate of 64kbps to 90kbps (which are almost never used on VoLTE connections) , near CD quality music could be broadcast over your VOIP call.  Those speeds are still less than 20% of your 0.5mbps speed or less than 5% if you are using closer to the minimum amount of standard voice bandwidth.

 

end of the day on B41 my voice quality sux when near RSRP -110 and when on B25 I am able to have a normal call even at RSRP -115 quality. 

Link to comment
Share on other sites

2 hours ago, bucdenny said:

end of the day on B41 my voice quality sux when near RSRP -110 and when on B25 I am able to have a normal call even at RSRP -115 quality. 

Yeah, the -110dBm is your received strength.  The received strength at the site of your phone call may be far worse.  And synchronous quality is vital in a phone conversation.  It's not unusual for a device to have good Rx performance, but not necessarily Tx, especially at weaker signal strengths.  Your device may be a poor transmitter on B41.  Or there may be a lot of B41 noise.

Because of this, B41 may not be a good solution for VoIP.  But may be better for VoLTE, as the network QoS could control priority of your call and shunt you to a better band if required.  VoIP treats the call as data packets, the same as everything else.  And when minimum synchronistic standards are required, this could be a problem in many individual circumstances regarding signal quality/strength and hardware.

Robert

  • 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

    • Since this is kind of the general chat thread, I have to share this humorous story (at least it is to me): Since around February/March of this year, my S22U has been an absolute pain to charge. USB-C cables would immediately fall out and it progressively got worse and worse until it often took me a number of minutes to get the angle of the cable juuuussst right to get charging to occur at all (not exaggerating). The connection was so weak that even walking heavily could cause the cable to disconnect. I tried cleaning out the port with a stable, a paperclip, etc. Some dust/lint/dirt came out but the connection didn't improve one bit. Needless to say, this was a MONSTER headache and had me hating this phone. I just didn't have the finances right now for a replacement.  Which brings us to the night before last. I am angry as hell because I had spent five minutes trying to get this phone to charge and failed. I am looking in the port and I notice it doesn't look right. The walls look rough and, using a staple, the back and walls feel REALLY rough and very hard. I get some lint/dust out with the staple and it improves charging in the sense I can get it to charge but it doesn't remove any of the hard stuff. It's late and it's charging, so that's enough for now. I decide it's time to see if that hard stuff is part of the connector or not. More aggressive methods are needed! I work in a biochem lab and we have a lot of different sizes of disposable needles available. So, yesterday morning, while in the lab I grab a few different sizes of needles between 26AWG and 31 AWG. When I got home, I got to work and start probing the connector with the 26 AWG and 31 AWG needle. The stuff feels extremely hard, almost like it was part of the connector, but a bit does break off. Under examination of the bit, it's almost sandy with dust/lint embedded in it. It's not part of the connector but instead some sort of rock-hard crap! That's when I remember that I had done some rock hounding at the end of last year and in January. This involved lots of digging in very sandy/dusty soils; soils which bare more than a passing resemblance to the crap in the connector. We have our answer, this debris is basically compacted/cemented rock dust. Over time, moisture in the area combined with the compression from inserting the USB-C connector had turned it into cement. I start going nuts chiseling away at it with the 26 AWG needle. After about 5-10 minutes of constant chiseling and scraping with the 26AWG and 31AWG needles, I see the first signs of metal at the back of the connector. So it is metal around the outsides! Another 5 minutes of work and I have scraped away pretty much all of the crap in the connector. A few finishing passes with the 31AWG needle, a blast of compressed air, and it is time to see if this helped any. I plug my regular USB-C cable and holy crap it clicks into place; it hasn't done that since February! I pick up the phone and the cable has actually latched! The connector works pretty much like it did over a year ago, it's almost like having a brand new phone!
    • That's odd, they are usually almost lock step with TMO. I forgot to mention this also includes the September Security Update.
    • 417.55 MB September security update just downloaded here for S24+ unlocked   Edit:  after Sept security update install, checked and found a 13MB GP System update as well.  Still showing August 1st there however. 
    • T-Mobile is selling the rest of the 3.45GHz spectrum to Columbia Capital.  
    • Still nothing for my AT&T and Visible phones.
  • Recently Browsing

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