Hi, been a customer for sometime and have noticed a massive dedegration in call quality and usability this year. WorldXchange helpdesk point the finger at congestion and we’ve downgraded our codec, but trying to make or receive any call during the evenings (like when we’re actually at home) is a true waste of breath.

Any suggestions?

I know a guy in Telecom who wants our business and despite the separation actually should be able to pull strings with Chorus if required.

Happy to remain a loyal customer, but ONLY if I can have a usable product.

aadawson: [snip]I know a guy in Telecom who wants our business and despite the separation actually should be able to pull strings with Chorus if required.

[snip]

This is a serious allegation and would be a very serious breach of Telecom policy (at least) if it occurred. This doesn't happen, it's not allowed to happen, and Telecom staff are frequently reminded that despite enduring friendships with people from Chorus since before the separation, THIS SHOULD NEVER HAPPEN.

Cameronn: I can confirm these issues are 110% related to local congestion at your exchange/cabinet.

I'll have a word to our Service Delivery Manager at Chorus however the Service Specifications around UBA/BUBA are fairly low ;

__________________Throughput 99.9% probability of providing to any provisioned End User a minimum uplink and downlink average throughput of 32kbps during any 15 minute period on demand

Mean one-way packet delay - <1 sec

One-way packet delay variation - Unspecified

On-way packet loss ration - Unspecified__________________Unfortunately this means we don't have much leverage when applying pressure to fix it.

Maybe not, but are you already on the highest per user dimensioning level for BUBA handovers? The 32kbit value is (I believe) no longer relevant. (Note I'm not Chorus so I don't know for sure any mroe than you do - but could be worth checking)

aadawson: [snip]I know a guy in Telecom who wants our business and despite the separation actually should be able to pull strings with Chorus if required.

[snip]

This is a serious allegation and would be a very serious breach of Telecom policy (at least) if it occurred. This doesn't happen, it's not allowed to happen, and Telecom staff are frequently reminded that despite enduring friendships with people from Chorus since before the separation, THIS SHOULD NEVER HAPPEN.

RegardsNeil G

Thanks Neil , you bet me to this , this would treated very seriously by any provider working in the wholesale area and would put the persons job in jeopardy.

Thanks Cameron, any assistance would be apprecaited. The Chorus BCC tool just shows we're on an exchange, so I assume that just entiltes us to slow ADSL. Couldnt figure out how to drill down lower and search to the cabinet

aadawson: Thanks Cameron, any assistance would be apprecaited. The Chorus BCC tool just shows we're on an exchange, so I assume that just entiltes us to slow ADSL. Couldnt figure out how to drill down lower and search to the cabinet

If it doesn't drill down then you are direct on the exchange, not on a cabinet

aadawson: Thanks Cameron, any assistance would be apprecaited. The Chorus BCC tool just shows we're on an exchange, so I assume that just entiltes us to slow ADSL. Couldnt figure out how to drill down lower and search to the cabinet

Unless it says ADSL2+ then you probably just have BUBA . The dimensioning is such that once you get too many subscribers the performance goes downhill; it was certainly never designed with VoIP in mind. You're best to move to a traditional analog phone service, or see if anyone has LLU available in your area.

If internet performance is that bad perhaps you should look at a fixed wireless service froma local provider in the area. Should rpovide more consistent speeds during peak and you can run VFX over that.

Maybe not, but are you already on the highest per user dimensioning level for BUBA handovers? The 32kbit value is (I believe) no longer relevant. (Note I'm not Chorus so I don't know for sure any mroe than you do - but could be worth checking)

Cheers - N

These details are in the current as of Sept 2012, latest manual for BUBA. Doesn't seem to go into detail about the dimensioning, however I'd guess that the packet loss/latency details are exactly the same - which is where the problem ultimately lies with call quality.

Will be interesting to see what I get back from Chorus regarding the node.

Actually, I think we were talking at cross purposes... I was referring to the BUBA _HANDOVER_ dimensioning earlier, while the issue here seems is more related to the fact this is a rural area and possible actual backhaul congestion. (Not being Chorus I have no idea if that's the case though)