Why is this place so dead?

[gripen]

TheRoDent, I say hold onto the domain name until you get to speak to someone who knows whats going on ie. a ProAsm and not a Ms.Potgieter. Then when you have a reasonable explanation, modify the content on the site (sentechsucks) or hand over the name if they really want it. Personally, my speed is sorted out.

 

[Scarface]

Hey, there is a problem in the fact that there is no consistency in the service. I am happy that I am getting better speeds than ever before and I don't see why I should keep shut. What it does indicate rather is that Sentech does not know what they are doing...

The Rodent, maybe a list of demands should be set up and we should all sign the petition. The first demand would be that customers who have logged one or more legit tickets should get at least 1 month credit...those with reception problems where the Zone Locator says "Good" but we all know better, another credit (or a decent antenna like the one from Andrews)

I would also like to see a job satisfaction score on call logged...ie. good bad very bad sentech sucks etc and we should have access to the stats ie. ave score, time to closure etc - I give my customers access to that.

Anyone with more demands (realistic ones)?

-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<-<

If you had a friend who talked to you, like you sometimes talk to yourself, would you continue to hang around with that person? - Rob Bremer

 

[regardtv]

Reading between the lines and making some informal queries it sounds like Sentech are possibly not implementing the bandwidth management as well as they should.

This is just my 5 cents worth but this is the way I think it should be implemented..

Take the available bandwidth - assign 3 primary priority queues:

* Prio 1 - 512K users
* Prio 2 - 256K users
* Prio 3 - 128K users

These queues do not restrict available bandwidth it simply manages priorities for bandwidth.

Then, as each radius session is initiated (user connects) assign them to an individual rate limited queue...

While the individual rate limiter may be resource intensive this can be cleanly spread across the network by doing this provisioning either per tower or per region....

-----

This setup should provide the following:

1) Bigger package users will gain the advantages they deserve within the Sentech environment

2) Rate limits will be accurately applied without weird contention pools comming into play.


-----

This may be part of what they are changing - I see that disconnect/reconnect is giving me back the same IP repeatedly .. Maybe the radius server is keeping my address available to me and with it an individual rate limited queue ...

----
I'm rambling ... tired ... thoughts anyone ?

(maybe this belongs on a new thread ...)

************************************************************
The views expressed on this site are my own and NOT those of my employer.

 

[Ditch]

<blockquote id="quote"><font size="1" face="Verdana, Arial, Helvetica" id="quote">quote:<hr height="1" noshade id="quote"><i>Originally posted by regardtv</i>
<br />But I'm not accepting anything - especially not until we have an official announcement from Sentech as to WHY they took so long to fix it and what the problems were ;-)
<hr height="1" noshade id="quote"></blockquote id="quote"></font id="quote">
Ditto.

The root of the problem seems to have been that they simply didn't have enough bandwidth ("Smith says that in order to rectify the problem, Sentech has added a significant amount of local and international bandwidth"). But this seems like such an incredibly basic thing for an ISP - "we have so many users, we need this much bandwidth" - that it's almost impossible that this was either a mistake or a "technical problem" - so the 'economic theory' is the only really viable one. They didn't buy enough BW, and then just tried to explain it away with a call center "lies policy". It does also seem that their BW management systems may not be 'up to scratch' and are being looked at, but this issue is really totally insignificant next to just plain not buying enough BW. So attempting to focus on this latter issue in the media with vague references ("Smith says the problem was in managing collective Internet bandwidth") is a smokescreen to distract attention from the major (and basically inexcusable) issue.