With regards the 98 where you see 103 my guess would be your router is Gigabit so its squeezing that little bit more out of the fibre - Voyager may well have provided an older 100Mbit only router as they were only on a 100 plan.

My brother is with Orcon for 100 fibre in Christchurch and his router is a very old Dynalink NF4V, doesn't do AC, doesn't do 5Ghz at all and the ethernet is only 100Mbit.

As said - In both cases they are getting what they've paid for but providing old stock routers for these connections is a little lame but on the other hand if you want decent Wifi never use the ISP provided device - Just turns its wifi off. Even for the Internet connection itself you will often be better off with another device.

I got 98 on the provided device and 109 on my own router. Then I put in two Unifi AC Long Range access points mounted to the ceiling in two rooms at either end of the house and I get the full 109Mbit up and Down (Business 100/100 plan) anywhere in the house on devices with modern enough wifi like my ipad.

Now, (see my other thread on the non-help from Voyager).

Another thing.

Ever since the hooked him up, he has been able to make calls and receive local calls but not receive toll calls.

I ring him and get engaged.

First it was to be fixed X day.

X day came and went, nothing.

He rang back, oh yeah fixed that day.

Nope.

And on to today. Still not.

he has rung and been told A)they rang and it's fine B)Made some changes and it's fine and no it isn't, so now it's MY phone that is the issue.

Of course.

I can ring anyone ion the country just fine, except him, I STILL get engaged from their number, but no it's my problem, not Voyagers.

It's not so much there may be an issue....it's the slack response, the buck passing, the oh it's sorted (but isn't) they seem to do.

Again.

It's what put me off them in the first place.

Why should my brother be running around trying to prove it to them, getting various people to try to ring? I told him, dump them and get another provider.

pctek:

 

Now, (see my other thread on the non-help from Voyager).

 

Another thing.

 

Ever since the hooked him up, he has been able to make calls and receive local calls but not receive toll calls.

 

 

 

I ring him and get engaged.

 

 

 

First it was to be fixed X day.

 

X day came and went, nothing.

 

He rang back, oh yeah fixed that day.

 

 

 

Nope.

 

This might actually be a problem at your phone provider - Possibly you are with the supplier he ported his number from and so your provider still thinks its an internal route and sends the number off to oblivion.

I had a client who ported a number from Vodafone to a Voip provider - Everyone in the country could ring her just as long as they weren't on Vodafone. Vodafone eventually admitted they hadn't followed the correct procedure when they got the port notification and fixed it.

@pctek, have a look at this thread

https://www.geekzone.co.nz/forums.asp?forumid=43&topicid=238167

Same/similar issue with Voyager and national calls

sbiddle:

 

Basically there is nothing wrong. 

 

Latency would be explained by using an off-net speedtest server that doesn't peer locally - ie if they are in Napier for example and picking Napier as the server and Voyager don't peer in Napier with them (I'd be surprised if anybody peers in Napier) then traffic will go to Auckland and back which explains the latency.

 

....

Mr @sbiddle is 100% correct ... on all counts.

The service speed looks perfectly fine - it is a 100/20 service, achieving 98.95mbps and 20.65mbps, so well with spec. 
Voyager does not peer in Napier, so latency to other Napier test servers transit via Auckland - the fact it's transiting via AKL could reduce the service speed. I would suggest trying an AKL test server - Spark (AKL) is a fairly reasonable one.

Hell of a coincidence, he gets a new landline and I can't ring his number immediately.

There were issues, they kept telling him it's fixed, well seems most of it...others can ring now.

But.

I can ring all over the country. Let's be specific.  His number is 8421xxx

So I look up assorted shops and places in his suburb...including 8421zzz, I can ring them all.

I can ring all over Hawkes bay, I had done, as we are going to move their eventually, I checked out vets and such there. I can ring them all.

Except his number.

I even ask Spark (Why should I, I know it's not them), but OK, so as Spark says:

Hi (pctek)

Thank you for contacting Spark via email, sorry to know about this issue.

06-842-1xxx

If you are able to ring a different number from your phone but not the number above, then most likely either the user of the number above blocked your number from calling it or there is something wrong on their line blocking your call from reaching that number, either way, if you are able to make and receive other phone calls from your number then that only confirms that your line is working fine.

Thanks

pctek:

 

Hell of a coincidence, he gets a new landline and I can't ring his number immediately.

 

....

 

It's not a coincidence at all. He was on Spark, he ported to Voyager. Somewhere between yourself and Voyager there is a number routing issue.
Unfortunately it's quite common with number porting (regardless of who). It just means something, somewhere hasn't updated.

pctek:

 

I even ask Spark (Why should I, I know it's not them), but OK, so as Spark says:

 

Hi (pctek)

 

 

 

Thank you for contacting Spark via email, sorry to know about this issue.

 

06-842-1xxx

 

 

 

If you are able to ring a different number from your phone but not the number above, then most likely either the user of the number above blocked your number from calling it or there is something wrong on their line blocking your call from reaching that number, either way, if you are able to make and receive other phone calls from your number then that only confirms that your line is working fine.

 

Unfortunately thats a fairly standard response from Spark - it doesn't even look like they've investigated, just sent you back a canned response.

Maybe your brother is actually blocking your call? :P

Uhuh, now you say it's his fault - with Spark.

I saw his emails/txts, you guys said the issue was with MY line.

Crap.

He notified Spark about the move. He also signed up with you. Why didn't YOU ensure it was all sorted, more buck passing again.

Help him out, he does have some disabilities you know, YOU go hassle Spark if it is their issue, not me, not him.

Hi @pctek,

Please re-read my previous posts (on both threads), you will see I have covered most of this before.

We have provided instructions to your bother on how to get this resolved, (here: https://www.geekzone.co.nz/forums.asp?forumid=43&topicid=238167&page_no=1#2049905), but have yet to receive anything from him.

We are unable to take action from your posts or information because it's not your account - even if you are a relative.

Until you brother lodges a fault I am unable to assist any further - so I will cease responding to you on this topic (on both threads) as I feel it is not achieving anything except to increase a post count.

pctek:

 

Uhuh, now you say it's his fault - with Spark.

 

 

 

I saw his emails/txts, you guys said the issue was with MY line.

 

 

 

Crap.

 

 

 

He notified Spark about the move. He also signed up with you. Why didn't YOU ensure it was all sorted, more buck passing again.

 

 

 

Help him out, he does have some disabilities you know, YOU go hassle Spark if it is their issue, not me, not him.

 

As I mentioned earlier with one of my clients who ported from Vodafone to another supplier - Vodafone had dropped the ball and in your brothers case it may well be Spark who have dropped the ball now. My understanding is Voyager (In this case) make a request to have a phone number ported from its current provider to them, this process notifies the current provider - They at the agreed time Voyager provision the number in their system and the old provider De-Provisions it - Voyager don't have access into sparks System to do it and its supposed to be relatively automated but sometimes the old provider doesn't do their bit properly.

My client spend many hours talking to Vodafone who constantly said it wasn't their issue, she had to deal with the new provider. Eventually the new provider managed to talk some sense into someone at Vodafone who got them through to the right backend team who say the problem immediately and fixed it. 

The issue is with the likes of Spark and Vodafone they can be pretty unhelpful when not dealing with Their Client which makes it pretty tricky for Ex Clients or Competition.

I constantly ring providers on behalf of my clients and get the runaround - Even when I'm ringing to notify the provider of an issue at their end they often refuse to talk to me because I'm not the client.

mobiusnz:

 

pctek:

 

Uhuh, now you say it's his fault - with Spark.

 

 

 

I saw his emails/txts, you guys said the issue was with MY line.

 

 

 

Crap.

 

 

 

He notified Spark about the move. He also signed up with you. Why didn't YOU ensure it was all sorted, more buck passing again.

 

 

 

Help him out, he does have some disabilities you know, YOU go hassle Spark if it is their issue, not me, not him.

 

 

As I mentioned earlier with one of my clients who ported from Vodafone to another supplier - Vodafone had dropped the ball and in your brothers case it may well be Spark who have dropped the ball now. My understanding is Voyager (In this case) make a request to have a phone number ported from its current provider to them, this process notifies the current provider - They at the agreed time Voyager provision the number in their system and the old provider De-Provisions it - Voyager don't have access into sparks System to do it and its supposed to be relatively automated but sometimes the old provider doesn't do their bit properly.

My client spend many hours talking to Vodafone who constantly said it wasn't their issue, she had to deal with the new provider. Eventually the new provider managed to talk some sense into someone at Vodafone who got them through to the right backend team who say the problem immediately and fixed it. 

The issue is with the likes of Spark and Vodafone they can be pretty unhelpful when not dealing with Their Client which makes it pretty tricky for Ex Clients or Competition.

I constantly ring providers on behalf of my clients and get the runaround - Even when I'm ringing to notify the provider of an issue at their end they often refuse to talk to me because I'm not the client.

 

This is a little disingenuous... The reason you may perceive that "the likes of Spark and Vodafone [..] can be pretty unhelpful" in these cases probably has a lot to do with them taking privacy LAWS seriously. Sometimes the identity of the person calling NEEDS to match - either for strict legal reasons, or due to policy enacted to try and minimise accidental privacy related issues.

Although unfamiliar with the specifics of this case - portraying providers taking privacy and legal requirements seriously is NOT a negative.

Cheers - N