Vox Fatpipe Lite + Bolt-on technical question

Julian2

Well-Known Member
Joined
Aug 2, 2014
Messages
117
Reaction score
2
I'm looking at ISPs for basic web browsing and a lot of streaming live TV. I've pretty much settled on a shortlist of Crystalweb & Vox.

For Vox the generous on/off timings for the unlimited bolt-on (henceforth "UBO") is a big attraction but I want to make sure that I understand how I would make best use of the UBO.

As I understand it new connections after 18:00 (plus or minus a few minutes for clock issues) will be counted as UBO data but there is a slight "gotcha" in that any connection established prior to 18:00 will have been set up to deduct data from the basic Fat Pipe Lite (henceforth "FPL") 25GB allowance and so any data consumed down that connection, even data consumed after the 18:00 UBO activation time, will still be deducted from the FPL allowance. The particular scenario that might catch me out here is, if I started streaming a 1 hour TV program at 17:55, then almost all of that data would end up being deducted from my FPL allowance even though most of the stream data was delivered to me after 18:00.

First question. Is the above correct?

If yes then is it sufficient to simply stop (as in completely cancel and break connection with the server) any active stream at say 18:05-ish and immediately restart it in order to ensure that the connection is correctly booked against the UBO data allowance rather than the FPL allowance or is it necessary to disconnect from Vox entirely and re-login? If so then I'm guessing that a VPN might also pose a challenge since stopping a channel inside a VPN would still leave the connection to the VPN endpoint intact hence the VPN session would also need to be terminated in order to ensure that a brand new connection was seen by Vox when the streaming was restarted at 18:06-ish.

Finally, and assuming all my assumptions are still on track here and the above is acceptable, does Vox have a good enough dashboard such that I can run an experiment to make sure that I am avoiding post-18:00 streaming data getting billed against my FPL allowance? My experiment would be to look at my FPL data usage at say 17:55 and make a note of it, start a stream immediately (i.e. prior to 18:00), drop the stream at 18:05-ish, and then restart the stream for at least an hour plus whatever other streaming I want to do that evening. I would then check my FPL data usage first thing the following morning and it should show almost exactly the same data remaining as my 17:55 figure did minus about 10 minutes worth of streaming data consumed between 17:55 and 18:05. Are the tools there and the data usage updated sufficiently promptly for me to be able to run this experiment and get a reliable result?

- Julian
 
I doubt that is how they calculate it.

My wife have been streaming netflix for the last 2 hrs (watching a movie since 4pm)

It is now 18:10, and my vox shows that i have already used just over 2 gig after hours.

The stream was never paused or stopped.
 
I doubt that is how they calculate it.

My wife have been streaming netflix for the last 2 hrs (watching a movie since 4pm)

It is now 18:10, and my vox shows that i have already used just over 2 gig after hours.

The stream was never paused or stopped.

Thanks Polemus. Your info would certainly seem to indicate that my understanding is wrong. Looking back over the thread for the old "@lantic R59 uncapped 'bolt-on' feedback" thread (http://mybroadband.co.za/vb/showthread.php/434391-lantic-R59-uncapped-bolt-on-feedback), which I assume is the pre-cursor for the Fatpipe Lite bolt-on, I think I might have been reading about how it was behaving at a point when it had some issues with the 6:00pm cutover so I might have been thinking that an error condition was normal behaviour.

I'm still a bit confused by your data though; maybe I've misunderstood what you typed. If your wife started watching at 4:00 pm and finished at 18:10 and the usage measurements were entirely accurate (i.e. every second's worth of data downloaded for the stream prior to 18:00 is booked against the basic in-hours 25 GB per month cap and every second's worth of data from 18:00 onwards is booked against the unlimited after-hours cap then, unless your wife has discovered some whole new level of high resolution, I'm finding it hard to see how 2 gig of data could have been streamed between 18:00 and 18:10. With perfect second-by-second accounting of data usage, and assuming the whole movie involved downloading 2 GB of data over the 130 minutes of viewing, I would have expected about 1.85 GB to have been booked against the in-hours 25 GB allowance and 0.15 GB to have fallen into the after-hours bolt-on unlimited allowance.

Have I misunderstood what you wrote (in which case - sorry!)? If not them I'm still unclear but now for different reasons.

Maybe it works exactly the other way round to how I originally though. Maybe the data used by a connection is only totalled up and booked against an allowance at the point the connection is broken down. That would explain how I've read your data, i.e. because your wife (presumably) hit the stop button at 18:10 that was the point when the data use for the entire 130 minutes worth of streaming was seen by the system and booked against the currently active package which at that point would have been the after-hours unlimited bolt-on.

If my revised interpretation is correct then that's pretty great because I no longer need to worry about the scenario identical to your wife's example accidentally consuming my in-hours allowance, in fact that scenario would end up preserving daytime allowance rather than burning it up. The price that is paid would be that a stream started in the very early hours of the morning that was left running past the bolt-on cut-off point of 06:00 am would end up booking all the data for the stream against the daytime allowance. Since I'm allergic to early mornings the chances of me being up before 06:00 am are virtually zero and if I was I certainly wouldn't be watching TV so maybe the way this actually works is 100% benign for me.

- Julian
 

Hi Julian

My name is Chris, and I was one of the people who engineered this "UBO" on the network.

I'll lay this out as blunt and clear as I can to avoid any confusion.

The Fatpipe Lite + Bolt On utilizes two separate "counting" mechanisms in our subscriber management platform. These "counting" mechanisms have settings as to when they are "active"; which means, when usage is counted towards one and not the other.

Here are the EXACT configuration from the back end of our system:

Validity schedule:
Peak time: 0600-1759/Mon-Fri
Off peak time:0000-0559/Mon-Fri; 1800-2359/Mon-Fri; 0000-2359/Sat-Sun

We don't require you to disconnect or reconnect in order for these two slots to be used correctly. We handle it internally. Obviously time of day is required to be as sync as possible so there's an obvious variance of a few minutes before/after depending on how the NTP servers response on your machine and on our network.

Whether you are mid stream or not, the system calculates usage based on time stamps as the traffic passes the equipment. This usage is then collected on a separate set of systems in order to parse (process) the usage data records (UDRs) for presentment on our dashboards and are also used in billing routines.

The parsing of these files is delayed up to 15 minutes normally, which can mislead you in the dashboard view if you are unaware of this.

Lastly, traffic is traffic, we don't care if it's inside a VPN tunnel or not; we still know it exists and we count it based on time of day.

The current time on the relevant servers at the time of submitting this post was: Thu Oct 1 10:59:14 SAST 2015

I hope that this clears up any questions, if not, let me know.

Regards,
Chris
_____________________________

Chris Van Wie
Solution Architect
Vox Telecom Limited
 
Thank you Chris. All is clear now. What a fantastic reply. I especially like the finishing touch where you demonstrated the current time synchronisation by posting the changeover clock setting so that I could compare it with the time on your post. Clever.

It looks like it all works as I had hoped with no concerns about needing to log in and out to ensure changeovers. For someone doing lots of streaming the unlimited bolt-on really does become quite compelling value vs other ISP offerings, more so as one's line speed increases since the cost of the data doesn't change (although I am aware of the 10Mbps cap on the UBO so the comparisons with other ISPs stop being like-for-like beyond that). The UBO cut-in and cut-off timings also seem perfectly chosen for streaming; after-midnight products are really only good for downloading and pretty worthless for streaming, at least for my usage.

Thanks again for the clear and comprehensive reply.

- Julian
 
Thank you Chris. All is clear now. What a fantastic reply. I especially like the finishing touch where you demonstrated the current time synchronisation by posting the changeover clock setting so that I could compare it with the time on your post. Clever.

It looks like it all works as I had hoped with no concerns about needing to log in and out to ensure changeovers. For someone doing lots of streaming the unlimited bolt-on really does become quite compelling value vs other ISP offerings, more so as one's line speed increases since the cost of the data doesn't change (although I am aware of the 10Mbps cap on the UBO so the comparisons with other ISPs stop being like-for-like beyond that). The UBO cut-in and cut-off timings also seem perfectly chosen for streaming; after-midnight products are really only good for downloading and pretty worthless for streaming, at least for my usage.

Thanks again for the clear and comprehensive reply.

- Julian

My pleasure and I'm glad you caught the time reference. =)
 
Top
Sign up to the MyBroadband newsletter
X