Fritz 7490 and Slingshot Fibre II

Forums › 2degrees (including Slingshot, Orcon, Flip, Stuff Fibre, MyRepublic, 2talk and Vocus) › Fritz 7490 and Slingshot Fibre II

vcnz

5 posts

Wannabe Geek

#226275 29-Dec-2017 17:42

Hi,

I have followed this previous thread (https://www.geekzone.co.nz/forums.asp?forumid=81&topicid=213882) to configure my own Fritz!box 7490 with Slingshot UFB. Everything is working fine for about a month until telephone service suddenly stopped about two days ago, my internet access is not affected. Now I am seeing these in the Event Log:

Registration of Internet telephone number 649[my_number] failed. Remote site reports reason for error 404
The telephone number 649[my_number] has not been available for more than one hour.
Registration of Internet telephone number 649[my_number] failed. Remote site reports reason for error 404 [2 messages since 29.12.17 16:33:00]
The telephone number 649[my_number] has not been available for more than one hour.

I tried some network debug and seems I can't access the SIP gateway for some reason. Should I be at least able to ping it?

$ host 119.224.142.182
182.142.224.119.in-addr.arpa domain name pointer default-rdns.vocus.co.nz.

$ tcptraceroute 119.224.142.182
traceroute to 119.224.142.182 (119.224.142.182), 30 hops max, 60 byte packets
1 192.168.178.1 (192.168.178.1) 0.657 ms 0.611 ms 0.770 ms
2 * * *
3 10.10.82.254 (10.10.82.254) 4.731 ms 4.487 ms 6.950 ms
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *

$ ping -c 3 119.224.142.182
PING 119.224.142.182 (119.224.142.182) 56(84) bytes of data.

--- 119.224.142.182 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2092ms

From the Fritz, this is my internet setting:
Internet connection established successfully. IP address: 101.98.23.##, DNS server: 202.180.64.10 and 202.180.64.11, gateway: 101.98.0.91, broadband PoP: cpcak4-bng1

Any help is greatly appreciated.

Regards,

Vincent

vcnz

5 posts

Wannabe Geek

#1926860 30-Dec-2017 09:51

Some more SIP specific tests...

$ nc -vz www.slingshot.co.nz 80
Connection to www.slingshot.co.nz 80 port [tcp/http] succeeded!

$ nc -vz 119.224.142.182 5060
(timed out)

$ traceroute www.slingshot.co.nz -T -p 80
traceroute to www.slingshot.co.nz (60.234.0.65), 30 hops max, 60 byte packets
1 192.168.178.1 (192.168.178.1) 0.683 ms 0.655 ms 0.813 ms
2 v1.cpcak4-bng1.tranzpeer.net (101.98.0.91) 2355.688 ms 2355.501 ms 2449.343 ms
3 default-rdns.vocus.co.nz (101.98.0.149) 7.894 ms 7.664 ms 7.428 ms
4 10.101.5.126 (10.101.5.126) 7.180 ms 6.942 ms 6.701 ms
5 default-rdns.vocus.co.nz (60.234.0.65) 6.452 ms 6.200 ms 5.976 ms

$ sudo traceroute 119.224.142.182 -T -p 5060
traceroute to 119.224.142.182 (119.224.142.182), 30 hops max, 60 byte packets
1 192.168.178.1 (192.168.178.1) 0.659 ms 0.638 ms 0.797 ms
2 v1.cpcak4-bng1.tranzpeer.net (101.98.0.91) 868.633 ms 868.538 ms 962.210 ms
3 10.10.82.254 (10.10.82.254) 4.782 ms 4.552 ms 4.318 ms
4 * * *
5 * * *
6 * * *

Pluralsight

Learn cloud, mobile, security, data and web technologies with Pluralsight (affiliate link).

squirt00

5 posts

Wannabe Geek

#1958432 15-Feb-2018 09:20

Hi Vincent

Did you ever manage to get your phone working again? I had UFB installed yesterday and managed to get internet access working using a Fritz 7490, but not the phone. Slingshot support told me there was no way it would ever work with my router and I would have to get one of the routers they supply. Is that what you've had to do?

Dave

vcnz

5 posts

Wannabe Geek

#1958788 15-Feb-2018 20:45

Hi,

I can confirmed that the instruction in the original thread is absolutely correct:

https://www.geekzone.co.nz/forums.asp?forumid=81&topicid=213882

The problem is 100% at Slingshot end, HOWEVER they will deny it with the usual "we don't support this model" reply. Even thought that is the exact model they provided for their most expensive plan... the reason they gave me was those has "special firmware"...

My problem was finally "resolved" when I gave in and got a Slingshot modem from them (luckily my contract was up, so i only need to pay S&H when I renew).

When it finally arrived, I still got only internet and no phone (exactly as when I was using Fritz). But now they have no excuse to not REALLY look into my problem. So after a few emails, they finally done some configuration on my homeline settings and I got internet and phone back. At that point I promptly unplug the Slingshot modem, plug in my Fritz 7490.... and MAGIC! everything is working again.

So after two weeks and $15 everything is back to normal. I have no issue ever since, and this time (*) I am keeping my Slingshot modem for any future problem.

Dave, I suggest you bribe / beg anyone to get your hand on a "NetComm NF4V" even temporarily, so Slingshot will look at your support case more seriously.

Regards,

Vincent

* As I mentioned in my original post, I was using the 7490 without any issue for a month initially. So I actually voluntarily returned my old Slingshot modem to them for reuse / recycle...

vcnz

5 posts

Wannabe Geek

#1958795 15-Feb-2018 20:57

FYI, these are my current settings:

Proof of success:

squirt00

5 posts

Wannabe Geek

#1958800 15-Feb-2018 21:24

Thanks Vincent, I suspected that they were having me on and it would be possible to get the Fritz working. I figured they just didn't want to go to the trouble of telling me what I needed to do. It will be very irritating if my setup is already perfect and the issue is just with their end. Had a similar problem with a neighbour's router. Unlimited Internet eventually found that they hadn't configured everything correctly and the router was set up OK all along.

I'll see if I can borrow an NF4V and if I can't I'll get one from Slingshot and, as you say, they'll be forced to diagnose any issues from there.

Thanks for your prompt and thorough reply, you have been very helpful.

Regards

Dave

squirt00

5 posts

Wannabe Geek

#1958807 15-Feb-2018 21:48

Thanks for the settings, Vincent, I had a few of them wrong.

Presumably the password is the same one that I use for Internet?

I'm getting a 404 response code to the SIP registration. According to Wikipedia:

404 Not Found

The server has definitive information that the user does not exist at the domain specified in the Request-URI. This status is also returned if the domain in the Request-URI does not match any of the domains handled by the recipient of the request.

So at least there does appear to be communication with the SIP registrar. That wasn't happening before I made the corrections.

Regards

Dave