[Snap] Snap VoIP horribly broken

Forums › 2degrees (including Slingshot, Orcon, Flip, Stuff Fibre, MyRepublic, 2talk and Vocus) › [Snap] Snap VoIP horribly broken

1 | 2

chevrolux

4962 posts

Uber Geek
Inactive user

#830069 3-Jun-2013 15:57

Could it just be that silly internal port forwarding rule the Fritz has in it's default config?

You can telnet in to it and edit the ar7.cfg file and remove this rule.

CcMaN

87 posts

Master Geek

#830206 3-Jun-2013 19:57

chevrolux: Could it just be that silly internal port forwarding rule the Fritz has in it's default config?

You can telnet in to it and edit the ar7.cfg file and remove this rule.

So I have the ar7.cfg file, although I'm a bit confused. Is it safe just to comment out this entire section:

voip_forwardrules = "udp 0.0.0.0:5060 0.0.0.0:5060",
"tcp 0.0.0.0:5060 0.0.0.0:5060",
"udp 0.0.0.0:7078+32 0.0.0.0:7078";

chevrolux

4962 posts

Uber Geek
Inactive user

#830212 3-Jun-2013 20:20

I just removed them completely but yea, commenting them out will do the same job. They appear in a few places though so just search through from the top.

Not sure what that 7078 range is for though.

sbiddle

30853 posts

Uber Geek

Retired Mod

Trusted

Biddle Corp

Lifetime subscriber

#830216 3-Jun-2013 20:30

One would assume that as that section details the ports and 5060 is used for SIP that 7078 -> 7100 would be used for RTP.

sidefx

3711 posts

Uber Geek

Trusted

#830243 3-Jun-2013 21:22

In the export file from saving the fritzbox settings you get:

rtpport_start = 7078;
sip_srcport = 5060;

and:

voip_forwardrules = "udp 0.0.0.0:5060 0.0.0.0:5060",
"tcp 0.0.0.0:5060 0.0.0.0:5060",
"udp 0.0.0.0:7078+32 0.0.0.0:7078";

and under firewall:

rules = "udp 5060", "tcp 5060", "udp 7078-7110", "TCP 443";

I wonder if you could just edit it in that file, then restore to fritzbox?

"I was born not knowing and have had only a little time to change that here and there." | Octopus Energy | Sharesies
- Richard Feynman

CcMaN

87 posts

Master Geek

#830258 3-Jun-2013 21:51

chevrolux: I just removed them completely but yea, commenting them out will do the same job. They appear in a few places though so just search through from the top.

Not sure what that 7078 range is for though.

Cool, I've managed to block it. No disruption to my VoIP so far. Let's see if this holds up. :)

chevrolux

4962 posts

Uber Geek
Inactive user

#830390 4-Jun-2013 11:35

Would be interesting to see if it fixes the issue. Makes me wonder if Snap should just do it for every Frtiz they ship. For a 5 minute fix they could save themselves a hell of a lot of pain in the future if the Fritz's get compromised.

Equinox IT

Cloud spending continues to surge globally, but most organisations haven’t made the changes necessary to maximise the value and cost-efficiency benefits of their cloud investments. Download the whitepaper From Overspend to Advantage now.

CcMaN

87 posts

Master Geek

#831216 5-Jun-2013 19:33

Unfortunately, this did not fix my issue. The Fritzbox re-opened the port and reinstated it's default config for the voip_forwardrules.

sbiddle

30853 posts

Uber Geek

Retired Mod

Trusted

Biddle Corp

Lifetime subscriber

#831222 5-Jun-2013 19:52

I would imagine you'd break the SIP stack if you tried to block these ports.

maverick

3594 posts

Uber Geek

Trusted

WorldxChange

#831410 6-Jun-2013 05:39

Did you ask SNAP if they have the call records for those calls ?

Yes I am a employee of WxC (My Profile) ... but I do have my own opinions as well

https://www.facebook.com/wxccommunications

chevrolux

4962 posts

Uber Geek
Inactive user

#831448 6-Jun-2013 09:08

That's quite strange that the Fritz put those rules back in... I just checked on a Fritz I have removed the VoIP rules on (to get other VoIP devices working behind it).
It is a 7390 with 'FRITZ!OS 5.22'. Firmware version is 84.05.22.

The ar7 file is exactly how I left it 6 months ago.

This is not on Snap VDSL either.

1 | 2