NAT / Router Registration issues.

Have a question or problem with your Fongo application? This forum is the place to get help from both staff and fellow community members.
Fongo recommends Fongo Home Phone for a fully supported Home Phone system for only $4.95/mo
Gren
Just Passing Thru
Posts: 4
Joined: 06/26/2012
SIP Device Name: SPA112
Firmware Version: 1.1.0(011)
ISP Name: Freephoneline.ca
Computer OS: Windows 7
Router: DIR-615

NAT / Router Registration issues.

Post by Gren »

Ok, I have a problem.

Since sometime this morning, i've been getting registration failed. At some point in the last few days someone called and I couldn't hear them (more than once), and as of today, i'm getting nothing. It was absolutely working fine before, but ongoing network shenanigans caused mostly by rogers need to enforce their will have certainly occurred in too many places to nail down the culprit at this point.


8 hours of frustration later i'm sure a million settings changed, so I reset VOIP settings

after updating the firmware, and then just applied the settings provided by FPL, no luck.

SO, here's a quick map of how the interwebz finds it's way into my Cisco SPA112

Internet > SMC Cable / Router > Rogers Home Alarm Netgear > D-link DIR-615
> SPA112 (and everything else).

Before we moved (and the router change), I know it worked fine after just completing the 'quick setup' on the SPA112 and adding it's IP to the DMZ of my old router.

I'm forced to accept the following issues.

a) Rogers requires I use the SMC for my high speed package. It's routing sucks, I had nothing but NAT issues on Xbox using it, so i unlocked it and disabled all of it's routing/DHCP/wifi so it's only acting as a cable modem. This worked great until b.
B) Rogers Home Alaram requires a rogers configured router that I have no access to (and unlocking it would prevent my alarm from working. Effectively, I can not access the configuration on this thing in any way. It's providing a 172.1.etc.etc address... (but I can't see what address it gets from the internet anymore.) the only thing I can do is run something on the alarm control panel of the alarm that claims to set "My personal router as part of it's DMZ"
c) The Dir615 is a huge step up for wireless from my other router, and I don't have any money right now to buy something else. it also has to be girlfriend friendly since it's hers. I'm really not considering any non-standard firmwares at this point.
d) I hate rogers, but they give me good deals. Not good enough to pay for their home phone.
e) I already paid for freephonline SIP file and bought the ATA locally.
f) I'm color blind, and for some reason people choose to develop LEDs that thing red, orange, green, or yellow are easy to differentiate. This makes it hard to correctly answer any question that doesn't ask if i see on, off, blue, or 'other' colors.

Now, I have an existing primus VOIP account (which i'm trying to replace with FPL) The

linksys SPA2100 (I think?) seems to be working fine, came pre-configured, but no admin access to re-configure. I don't really wanna pay for this any more though.
I've set the SPA112 to get it's IP from dHCP (which is reserved to 192.168.1.112 by the DIR615.)
if I plug the SPA112 directly into the Netgear, I can make outgoing calls. Incoming calls don't seem to get through (straight to VM). Unfortunately I can't configure the netgear for port forwarding, and I can't see what DNS the netgear is actually providing)

I logged into the fPL desktop app and it seems to be working ok. I also closed it from the menu, (not force closed or anything, just in case). No help.

I manually set DNS settings, to no avail, using 4.4.2.2 and 8.8.8.8, but I can't see the actual DNS from Rogers DHCP due to it going to the netgears. This (DNS) is still the one I think may be the biggest issue.

I switched back to automatic for now, but those settings are still in there.

What I know about my DNS setup
Rogers DNS/IP: Unknown/Unknown
Netgear DNS/IP: Unknown/172.16.12.1
DIR615 DNS+Gateway/WAN/LAN IP: 172.16.12.1/ 172.16.12.100/ 192.168.1.1 Note: Advanced DNS Disabled (don't know where to enable, or what it does anyway), Seconday DNS 0.0.0.0

I set the DIR615 as below.
I turned the ALG checkbox for SIP off on the DIR615
Forwarding Rules:
SIP 5066 to 1982.168.1.112 (UDP) and blank TCP (Always/allow all)
RTP 16584-16682 to 192.168.1.112 (UDP) and blank TCP (Always/allow all)

on the SPA112 I used these settings:
* SIP menu
RTP Port Min / Max: 16584 / 16682
RTP Packet Size: 0.020
SIP TCP Port Min: 5066, SIP TCP PORT MAx: <blank> (*** I don't see a UDP field in this area)
*Line 1 Menu
NAT Mapping Enable: yes
NAT Keep Alive Enable: yes
NAT Keep Alive MSG: $NOTIFY
NAT Keep Alive Dest: $PROXY

SIP Transport: UDP
SIP Port: 5066
EXT SIP Port: <Blank>
(some of the settings below are default, i'm providing extras anyway)
Proxy: voip.freephoneline.ca
Outbound Proxy: voip.freephoneline.ca
Use Outbound Proxy: Yes
Register: Yes
Register Expires: 180
Use DNS SRV: no
Proxy Fallback Intvl 180
Use OB Proxy in Dialog: Yes
Make call without reg: no
ans call without reg: no
DNS SRV Auto Prefix: no
Proxy Redundancy Method: Normal
Mailbox Subscribe expires: 2147483647

Subscriber information 1647#######
Password: that's what she said
Use Auth ID: no
Auth ID: <blank>
Resident Online Number: <blank>

preferred codec G711u
Second Preferred Codec G279a
Use Pref Codec Only: no
Dial Plan: (911|[2-9]xxxxxxxxx|1xxxxxxxxxx|011xxxxxxxxxxxx.|98*|[6-7]x*xxxxxxxxxxx.)

I also changed the voltage and the other setting as instructed, but can't find them right now, (and it used to work before I changed them as well, so I don't know how much they matter)


there are 2 options to ignore registration when dialing/receiving, so i get a dialtone when enabled, but calls out give a straight to busy signal. This wasn't a surprise since I was just trying to confirm this was a registration problem, but I figured i'd mention it in case it tells you anything.

If I plug the SPA112 into the Netgear (Rogers) directly, I can make outgoing calls ok. No incoming calls. No llight on line 1.


Here's the questionable info
I know I used the FPL in the SPA112 before, and had it working, i just don't remember when/why it stopped.
Primus works OK (and doesn't seem to require any forwarding).
SPA112 doesn't work any better when primus is not connected (But, I used port 5066 and changed the RTP port ranges instead just to be safe.) the originals weren't working any better this morning.

Wow, that's a lot of info. If you need more, let me know, I have to go and therapeutically kick myself in the face for a while. Thanks for any help!
User avatar
TheHardy
***Übergod***
Posts: 1632
Joined: 08/13/2011
SIP Device Name: FPL PC softphone (buggy)
Firmware Version: 3.0.3.0
ISP Name: Telus Optik
Computer OS: Win7
Router: Actiontec V1000H
Smartphone Model: none
Location: Surrey, BC

Not a complete solution

Post by TheHardy »

Well, just a way to get info actually.

websites such as www.WIMI.com will help you get your IP address.

Clicking on your network settings from Windows (I am assuming windows????) will allow you to see the network configuration that our computers sees, so you can figure out some of the local IP addresses ....

other than that, the fact that you have so much rogers crap at is non-configurable is part of the issue. I do not know enough to help anymore, but there will be some other people weighing in I am sure!
Hardy - Surrey, BC ~~ increasingly disgruntled FPL user ... comon, fix your stuff!
driver/webmaster - INCARTA Professional Delivery & Moving -- http://www.incarta.ca 604-594-7126
dibsmft
*Go-To Guy*
Posts: 651
Joined: 05/11/2011
SIP Device Name: Yealink T22 (SPA3102 GS286)
Firmware Version: 7.60.0.110
ISP Name: Bell-Aliant DSL
Computer OS: Linux Mint
Router: Speedstream 6520
Smartphone Model: Google Nexus 5
Android Version: 3.2.1
Location: St. John's NL

Re: NAT / Router Registration issues.

Post by dibsmft »

Yes, that is a lot of info and sadly it does not help me see the light at all. In your case you probably need to run STUN and Nat Mapping for the ATA to get the external address.
tbrummell
Tried and True
Posts: 330
Joined: 09/21/2010
SIP Device Name: PIAF/Mitel/PolyCom/Cisco
Firmware Version: Asterisk 1.8
ISP Name: Rogers
Computer OS: CentOS/Windows2008/Win7/Android
Router: pfSense/Neoware thin client
Location: Ottawa

Re: NAT / Router Registration issues.

Post by tbrummell »

You are double NAT'd, good luck with that. SIP has a hard enough time behind 1 NAT, but when double NAT'd things get exponentially worse.

Ohhh, and you should be using port 5060 for SIP.
User avatar
TheHardy
***Übergod***
Posts: 1632
Joined: 08/13/2011
SIP Device Name: FPL PC softphone (buggy)
Firmware Version: 3.0.3.0
ISP Name: Telus Optik
Computer OS: Win7
Router: Actiontec V1000H
Smartphone Model: none
Location: Surrey, BC

Re: NAT / Router Registration issues.

Post by TheHardy »

tbrummell wrote:You are double NAT'd, good luck with that. SIP has a hard enough time behind 1 NAT, but when double NAT'd things get exponentially worse.

Ohhh, and you should be using port 5060 for SIP.
I think that due to the 2 VOIP providers, everything was moved to 5066 from the example... that should be okay on that front, no? If all the settings are correct.

As I don't have an ATA, I can't speak well to this.

I did notice that there are both 172. & 192. range private addresses being assigned, so it sounds like at least TWO things are playing at DHCP, even though the OP says one has been disabled. Unless this was a typo, I know that having two things want to be in charge is going to be an issue, unless there are two separate networks bridged (correctly) that I am not aware of ...
Hardy - Surrey, BC ~~ increasingly disgruntled FPL user ... comon, fix your stuff!
driver/webmaster - INCARTA Professional Delivery & Moving -- http://www.incarta.ca 604-594-7126
cu2o2o2
Lightly Seasoned
Posts: 227
Joined: 04/06/2010
SIP Device Name: Double-NAT PAP2T-NA
Firmware Version: 5.1.6 (LS)
ISP Name: Rogers Express with SB5101
Computer OS: Win7 32-bit for DV softphone
Router: WNR3500L behind DIR-615C1
Location: Brampton, ON

Re: NAT / Router Registration issues.

Post by cu2o2o2 »

Gren wrote:Ok, I have a problem.

Since sometime this morning, i've been getting registration failed. At some point in the last few days someone called and I couldn't hear them (more than once), and as of today, i'm getting nothing. It was absolutely working fine before, but ongoing network shenanigans caused mostly by rogers need to enforce their will have certainly occurred in too many places to nail down the culprit at this point.


8 hours of frustration later i'm sure a million settings changed, so I reset VOIP settings

after updating the firmware, and then just applied the settings provided by FPL, no luck.

SO, here's a quick map of how the interwebz finds it's way into my Cisco SPA112

Internet > SMC Cable / Router > Rogers Home Alarm Netgear > D-link DIR-615
> SPA112 (and everything else).

Before we moved (and the router change), I know it worked fine after just completing the 'quick setup' on the SPA112 and adding it's IP to the DMZ of my old router.

I'm forced to accept the following issues.

a) Rogers requires I use the SMC for my high speed package. It's routing sucks, I had nothing but NAT issues on Xbox using it, so i unlocked it and disabled all of it's routing/DHCP/wifi so it's only acting as a cable modem. This worked great until b.
B) Rogers Home Alaram requires a rogers configured router that I have no access to (and unlocking it would prevent my alarm from working. Effectively, I can not access the configuration on this thing in any way. It's providing a 172.1.etc.etc address... (but I can't see what address it gets from the internet anymore.) the only thing I can do is run something on the alarm control panel of the alarm that claims to set "My personal router as part of it's DMZ"
c) The Dir615 is a huge step up for wireless from my other router, and I don't have any money right now to buy something else. it also has to be girlfriend friendly since it's hers. I'm really not considering any non-standard firmwares at this point.
d) I hate rogers, but they give me good deals. Not good enough to pay for their home phone.
e) I already paid for freephonline SIP file and bought the ATA locally.
f) I'm color blind, and for some reason people choose to develop LEDs that thing red, orange, green, or yellow are easy to differentiate. This makes it hard to correctly answer any question that doesn't ask if i see on, off, blue, or 'other' colors.

Now, I have an existing primus VOIP account (which i'm trying to replace with FPL) The

linksys SPA2100 (I think?) seems to be working fine, came pre-configured, but no admin access to re-configure. I don't really wanna pay for this any more though.
I've set the SPA112 to get it's IP from dHCP (which is reserved to 192.168.1.112 by the DIR615.)
if I plug the SPA112 directly into the Netgear, I can make outgoing calls. Incoming calls don't seem to get through (straight to VM). Unfortunately I can't configure the netgear for port forwarding, and I can't see what DNS the netgear is actually providing)

I logged into the fPL desktop app and it seems to be working ok. I also closed it from the menu, (not force closed or anything, just in case). No help.

I manually set DNS settings, to no avail, using 4.4.2.2 and 8.8.8.8, but I can't see the actual DNS from Rogers DHCP due to it going to the netgears. This (DNS) is still the one I think may be the biggest issue.

I switched back to automatic for now, but those settings are still in there.

What I know about my DNS setup
Rogers DNS/IP: Unknown/Unknown
Netgear DNS/IP: Unknown/172.16.12.1
DIR615 DNS+Gateway/WAN/LAN IP: 172.16.12.1/ 172.16.12.100/ 192.168.1.1 Note: Advanced DNS Disabled (don't know where to enable, or what it does anyway), Seconday DNS 0.0.0.0

I set the DIR615 as below.
I turned the ALG checkbox for SIP off on the DIR615
Forwarding Rules:
SIP 5066 to 1982.168.1.112 (UDP) and blank TCP (Always/allow all)
RTP 16584-16682 to 192.168.1.112 (UDP) and blank TCP (Always/allow all)

on the SPA112 I used these settings:
* SIP menu
RTP Port Min / Max: 16584 / 16682
RTP Packet Size: 0.020
SIP TCP Port Min: 5066, SIP TCP PORT MAx: <blank> (*** I don't see a UDP field in this area)
*Line 1 Menu
NAT Mapping Enable: yes
NAT Keep Alive Enable: yes
NAT Keep Alive MSG: $NOTIFY
NAT Keep Alive Dest: $PROXY

SIP Transport: UDP
SIP Port: 5066
EXT SIP Port: <Blank>
(some of the settings below are default, i'm providing extras anyway)
Proxy: voip.freephoneline.ca
Outbound Proxy: voip.freephoneline.ca
Use Outbound Proxy: Yes
Register: Yes
Register Expires: 180
Use DNS SRV: no
Proxy Fallback Intvl 180
Use OB Proxy in Dialog: Yes
Make call without reg: no
ans call without reg: no
DNS SRV Auto Prefix: no
Proxy Redundancy Method: Normal
Mailbox Subscribe expires: 2147483647

Subscriber information 1647#######
Password: that's what she said
Use Auth ID: no
Auth ID: <blank>
Resident Online Number: <blank>

preferred codec G711u
Second Preferred Codec G279a
Use Pref Codec Only: no
Dial Plan: (911|[2-9]xxxxxxxxx|1xxxxxxxxxx|011xxxxxxxxxxxx.|98*|[6-7]x*xxxxxxxxxxx.)

I also changed the voltage and the other setting as instructed, but can't find them right now, (and it used to work before I changed them as well, so I don't know how much they matter)


there are 2 options to ignore registration when dialing/receiving, so i get a dialtone when enabled, but calls out give a straight to busy signal. This wasn't a surprise since I was just trying to confirm this was a registration problem, but I figured i'd mention it in case it tells you anything.

If I plug the SPA112 into the Netgear (Rogers) directly, I can make outgoing calls ok. No incoming calls. No llight on line 1.


Here's the questionable info
I know I used the FPL in the SPA112 before, and had it working, i just don't remember when/why it stopped.
Primus works OK (and doesn't seem to require any forwarding).
SPA112 doesn't work any better when primus is not connected (But, I used port 5066 and changed the RTP port ranges instead just to be safe.) the originals weren't working any better this morning.

Wow, that's a lot of info. If you need more, let me know, I have to go and therapeutically kick myself in the face for a while. Thanks for any help!
Since you do not want to spend any money at the moment, you can take a shot at this...

Change your current configuration:

Internet > SMC Cable / Router > Rogers Home Alarm Netgear > D-link DIR-615
> SPA112 (and everything else).

To:

Internet > SMC Cable / Router > D-link DIR-615> SPA112 and Rogers Home Alarm Netgear (and everything else).


Maintain the SIP and RTP port assignments and port forwarding that you posted.

Make sure that your alarm system works behind the DIR-615. We can deal with the phone problem later (if there is any).

Good luck! :)
.

You agree to read my posts at your own risk.
dibsmft
*Go-To Guy*
Posts: 651
Joined: 05/11/2011
SIP Device Name: Yealink T22 (SPA3102 GS286)
Firmware Version: 7.60.0.110
ISP Name: Bell-Aliant DSL
Computer OS: Linux Mint
Router: Speedstream 6520
Smartphone Model: Google Nexus 5
Android Version: 3.2.1
Location: St. John's NL

Re: NAT / Router Registration issues.

Post by dibsmft »

tbrummell wrote:You are double NAT'd, good luck with that. SIP has a hard enough time behind 1 NAT, but when double NAT'd things get exponentially worse.

Ohhh, and you should be using port 5060 for SIP.
This is the internal SIP port so it is OK as is. The external port is still 5060 and the packets should still be routed correctly. I would sooner not be double NATted but have often run things that way.
dibsmft
*Go-To Guy*
Posts: 651
Joined: 05/11/2011
SIP Device Name: Yealink T22 (SPA3102 GS286)
Firmware Version: 7.60.0.110
ISP Name: Bell-Aliant DSL
Computer OS: Linux Mint
Router: Speedstream 6520
Smartphone Model: Google Nexus 5
Android Version: 3.2.1
Location: St. John's NL

Re: NAT / Router Registration issues.

Post by dibsmft »

TheHardy wrote:
tbrummell wrote:You are double NAT'd, good luck with that. SIP has a hard enough time behind 1 NAT, but when double NAT'd things get exponentially worse.

Ohhh, and you should be using port 5060 for SIP.
I think that due to the 2 VOIP providers, everything was moved to 5066 from the example... that should be okay on that front, no? If all the settings are correct.

As I don't have an ATA, I can't speak well to this.

I did notice that there are both 172. & 192. range private addresses being assigned, so it sounds like at least TWO things are playing at DHCP, even though the OP says one has been disabled. Unless this was a typo, I know that having two things want to be in charge is going to be an issue, unless there are two separate networks bridged (correctly) that I am not aware of ...
A good point. Looks like a typo but if that is how it is forwarded then there may be no RTP ports available.
User avatar
bridonca
Technical Support
Posts: 1225
Joined: 11/16/2009
SIP Device Name: Netgear WGR615V
Firmware Version: latest
ISP Name: Eastlink
Computer OS: XP

Re: NAT / Router Registration issues.

Post by bridonca »

I am getting confused, so break this up. plug the ATA directly to the modem, and have nothing else connected to the modem. If it works fine, you have a router issue. Because of your complicated setup, you need a good router with stable logical firmware. the 615 is not it. You may be able to flash it to DDWRT depending on the version. (another red flag on a crappy router when it has different versions with different chipsets and memory, but same model)

Lovely choice on the ATA. Hard to find a more NAT unfriendly ATA, but you have it!
Gren
Just Passing Thru
Posts: 4
Joined: 06/26/2012
SIP Device Name: SPA112
Firmware Version: 1.1.0(011)
ISP Name: Freephoneline.ca
Computer OS: Windows 7
Router: DIR-615

Re: NAT / Router Registration issues.

Post by Gren »

TheHardy wrote:
tbrummell wrote:You are double NAT'd, good luck with that. SIP has a hard enough time behind 1 NAT, but when double NAT'd things get exponentially worse.

Ohhh, and you should be using port 5060 for SIP.
I think that due to the 2 VOIP providers, everything was moved to 5066 from the example... that should be okay on that front, no? If all the settings are correct.

As I don't have an ATA, I can't speak well to this.

I did notice that there are both 172. & 192. range private addresses being assigned, so it sounds like at least TWO things are playing at DHCP, even though the OP says one has been disabled. Unless this was a typo, I know that having two things want to be in charge is going to be an issue, unless there are two separate networks bridged (correctly) that I am not aware of ...
Rogers-IP: I'm really trying to get the DNS servers rogers assigns, not the IP address (preferably somewhere I can obtain them if they were to change, or some reliable ones since I can no longer just read the settings off the rogers router.)

Double-NAT (Yeah, Sigh...)
port 5066 - yeah, assuming it was a default, I switched to 5066 in case of some conflict with the primus settings.
FYI - Cable modem (SMC) assigns nothing, routing/wifi/dhcp disabled.
Rogers netgear router (unconfigurable, with my router in the DMZ) assigns 172.x.x.x
My router (dlink) assigns the 192.x.x.x addresses

So, effectively, the double-NAT is just a give up scenario in spite of the DMZ? (which is what I was hoping not to hear?

would it make any difference if i faked out my router to provide addresses in the same subnet as the netgear, since it should really only be supplying 1 or 2 addresses (router and alarm) ever anyway?
User avatar
TheHardy
***Übergod***
Posts: 1632
Joined: 08/13/2011
SIP Device Name: FPL PC softphone (buggy)
Firmware Version: 3.0.3.0
ISP Name: Telus Optik
Computer OS: Win7
Router: Actiontec V1000H
Smartphone Model: none
Location: Surrey, BC

Re: NAT / Router Registration issues.

Post by TheHardy »

bridonca wrote:I am getting confused, so break this up. plug the ATA directly to the modem, and have nothing else connected to the modem. If it works fine, you have a router issue. Because of your complicated setup, you need a good router with stable logical firmware. the 615 is not it. You may be able to flash it to DDWRT depending on the version. (another red flag on a crappy router when it has different versions with different chipsets and memory, but same model)

Lovely choice on the ATA. Hard to find a more NAT unfriendly ATA, but you have it!
Don't mind Bridonca too much, he is the resident curmudgeon (love ya), but he has valid points. The hardware you have is known not to play nicely with what you are trying to do, that is the subtle point.


Isolating one issue at a time (at the expense of the other things temporarily not working) may be the way to troubleshoot the devices that you DO have and are choosing to use.
Hardy - Surrey, BC ~~ increasingly disgruntled FPL user ... comon, fix your stuff!
driver/webmaster - INCARTA Professional Delivery & Moving -- http://www.incarta.ca 604-594-7126
User avatar
bridonca
Technical Support
Posts: 1225
Joined: 11/16/2009
SIP Device Name: Netgear WGR615V
Firmware Version: latest
ISP Name: Eastlink
Computer OS: XP

Re: NAT / Router Registration issues.

Post by bridonca »

Your situation is not impossible, just incredibly difficult. So you gotta listen to me here. Check to see if the ATA works fine when connected directly to the Rogers modem. If it does, you got a router issue, which either needs better firmware, or a better router.

Even with a double NAT, if have manually set a clear path for the SIP and RTP ports, and then use STUN to confirm the route, you should be good to go. But you need router firmware that can keep track of that, and the default Dlink firmware is confirmed to be very poor at that. So fix that. If you have the option to flash to DD WRT on your version of DIR 615, please exercise it, or get a router that can. You only need to stump $25. http://www.futureshop.ca/en-CA/product/ ... 75bb6een02

Oh yeah, I am using a DIR-615, with DD-WRT, and after a lot of pain, I got it working perfectly. So I might have a few clues.

I have hateful things to say about your ATA, but when configured properly, it works great. Getting there is more painful than it should be, but at least you know you got a good config if it works.
User avatar
TheHardy
***Übergod***
Posts: 1632
Joined: 08/13/2011
SIP Device Name: FPL PC softphone (buggy)
Firmware Version: 3.0.3.0
ISP Name: Telus Optik
Computer OS: Win7
Router: Actiontec V1000H
Smartphone Model: none
Location: Surrey, BC

Re: NAT / Router Registration issues.

Post by TheHardy »

bridonca wrote:Your situation is not impossible, just incredibly difficult. So you gotta listen to me here. Check to see if the ATA works fine when connected directly to the Rogers modem. If it does, you got a router issue, which either needs better firmware, or a better router.
Truer words not seen in the screen in a long time ...

Gren: I would take the advice seriously, he knows whereof he speaks and has helped quite a few folks with wonky set ups/configs.... 8-)
Hardy - Surrey, BC ~~ increasingly disgruntled FPL user ... comon, fix your stuff!
driver/webmaster - INCARTA Professional Delivery & Moving -- http://www.incarta.ca 604-594-7126
Gren
Just Passing Thru
Posts: 4
Joined: 06/26/2012
SIP Device Name: SPA112
Firmware Version: 1.1.0(011)
ISP Name: Freephoneline.ca
Computer OS: Windows 7
Router: DIR-615

Re: NAT / Router Registration issues.

Post by Gren »

Thanks for the advice, here's how far I've got since I found some time to focus on it.

Router-Free was unnecessary, I cut out the home alarm system (temporarily), reset the ATA defaults, (and faked router-free by putting the ATA through DMZ.)
then I had to change the DMZ back to the alarm system, (still hoping that falls under nobody noticing, though I did have at least one Rogers person tell me it would be ok as long as I ran the tests... now, I know how much the opinion of one customer support rep means, but at least it gives me deniability...)

So, here's what I have actually working right now.
Cable Modem > D-link (over-exuberant forwarding detailed below) > ATA
Cable Modem > D-Link - Netgear/Alarm Router
ATA was reset to defaults again, changed the provided SIP settings (from the fpl site), as well as the 2 NAT settings (mapping enable/keep alive)
Primus ATA is still connected/functional

I read on some random forum that someone was told by fpl to forward these port ranges, so after it worked using DMZ, I tried this and put the DMZ back onto the home alarm, and it's working so far.
10000-20000 (TCP & UDP)
5060-6061(TCP & UDP)
This seems ridiculously excessive, no? Could you suggest what's actually required, or confirm this is the case? (hopefully you can help me avoid the next step of randomly testing smaller ranges, which is what I will do when I can free up another hour or so)

Once I get the forwarding cleaned up, i'd like to try swapping the dlink/netgear order back to what Rogers 'supports' (the double-NAT-mare). Is (apparently) setting DMZ on the Netgear(Alarm)Router going to be adequate for the 'manual' port settings you mentioned?

Unfortunately, new router/new firmware is still a very very last resort, (due mostly to a picky fembot who is resistant to change.) I'll have to spend 3 hours discussing feelings in addition to whatever time I spend on the upgrades ;)
User avatar
TheHardy
***Übergod***
Posts: 1632
Joined: 08/13/2011
SIP Device Name: FPL PC softphone (buggy)
Firmware Version: 3.0.3.0
ISP Name: Telus Optik
Computer OS: Win7
Router: Actiontec V1000H
Smartphone Model: none
Location: Surrey, BC

Re: NAT / Router Registration issues.

Post by TheHardy »

I am not the router guru, but congrats on getting it going and the processes you went thru!

I can see that the non-monetary price of the upgrade would be the limiting factor, to be sure! ;)

As long as the rest of our regulars find this post and are not on vacation, I am positive that you can get definitive answers on narrowing down that DMZ range considerably ... you might accidentally go too far and have to stuff a little back in, but it will save you having to experiment in the blind, wearing an adult diaper, ski-gloves and bunny slippers!! :roll:

As for the other thing, I sure won't tell rogers if you won't! :)
Hardy - Surrey, BC ~~ increasingly disgruntled FPL user ... comon, fix your stuff!
driver/webmaster - INCARTA Professional Delivery & Moving -- http://www.incarta.ca 604-594-7126