Bell Fibe 25 with Cellpipe 7130 and Linksys SPA3102

[Liptonbrisk]

Has anyone using Bell's Cellpipe 7130 successfully used freephoneline?
Bell's Fibe modem is built into the Cellpipe router.
Bell Fibe customers have no choice but to use the Cellpipe 7130.

I also have a Linkys WRT610N. My setup is Cellpipe (wireless disabled)--->SPA3102--->WRT610N(wireless enabled)

I've port forwarded 5060-6061 and 10000-20000 to 177.168.2.2 (spa3102)

http://192.168.0.1 is the internet address for the spa3102 though.

However, using 192.168.0.1 as a port forward destination doesn't help either.

The problem is I can't hear anyone. They can hear me fine.
Also calling from my Telus cellphone to my freephoneline number produces a busy signal.

Does anyone know if the Cellpipe 7130 blocks UDP port forwarding?

I stuck 177.168.2.2 in the DMZ host IP address as well.
That didn't help.
Then I stuck 192.168.0.1 in the DMZ host IP as well.
That didn't help.

[Liptonbrisk]

A friend told me to do this:

Visit http://www.justbroadband.org/forum/r238 ... DP-traffic

So, try this: http://www.broadbandreports.com/forum/r ... -as-bridge"

This Cellpipe 7130 (it's a modem built into a router) issue is seriously annoying. Anyway, I'm going to give that a shot.

So, I'll go cellpipe 7130-->Linksys WRT610N (have this log into PPOE and do port forwarding)-->SPA3102

Maybe that will work. Now I have to rewire and reconfigure everything.

[FONGO_steve]

Thanks for keeping us updated on this - I'm sure that information will be very valuable for future users who may be in your shoes!

I have your email in our support box too, but I'll just continue my correspondence here and file that email. That way things don't overlap between forum/email chat!

Keep us posted how the setup change goes

[Madwand]

I have the cellpipe and a Linksys WRT54GLS and with those connected and then the VOIP adapter I have no problems whatsoever.

Just tell the Cellpipe not to connect for web browsing and let the router do the PPPOE Login.

You should be fine.

[Bloodsong]

I have the cellpipe and a Linksys WRT54GLS and with those connected and then the VOIP adapter I have no problems whatsoever.

Just tell the Cellpipe not to connect for web browsing and let the router do the PPPOE Login.

You should be fine.

I was about to ask if that would even be an option here Madwand, I'm glad someone else on Fibe is hanging around to field these questions. It's not available in my area yet, so I haven't even gotten to see someone's Bell Fiberoptic setup.

[FONGO_steve]

I haven't even gotten to see someone's Bell Fiberoptic setup.

Keep in mind it's not true FTTH, just fiber to the node, and copper to the home as usual

[Liptonbrisk]

Okay, I can now make calls fine now, and I can hear what the other person is saying. Blocking UDP forwarding and DMZ from working properly in the Cellpipe 7130 is pretty disgusting on Bell's part, in my opinion.

I reset factory defaults on the Cellpipe, and just entered my ppoe info in the Linksys SPA3102.

So I'm basically going Cellpipe-->SPA3102 (Linksys ATA)--->WRT610N (Linksys wireless router)

I put the SPA3102 first because I didn't want to bother with QOS. In theory, I should never
have to be concerned if I'm doing a lot of stuff while making phone calls.

The problem now is that I appear to be having issues getting name display to show up on my Panasonic KX-TGA552M phone properly now, however. I seem to only be getting phone numbers to show up.

[Liptonbrisk]

So I'm basically going Cellpipe-->SPA3102 (Linksys ATA)--->WRT610N (Linksys wireless router)

Nevermind. That was a horrible idea. I've lost half my bandwidth by putting the SPA3102 before the WRT610N. I'll have to reverse the order.

[Bloodsong]

Heh heh,
Well remember you still only have 25Mb bandwidth out of the house, so being slowed to 100 between the router and the ATA shouldn't be that big an issue, but do keep an eye on your download rates and let us know what you find.

It is nice when you know you can do (in house) gaming, file and media streaming behind the ATA without a front facing effect, but you're right there will be cases where that's just not feasible for everyone.

[Liptonbrisk]

Heh heh,
Well remember you still only have 25Mb bandwidth out of the house, so being slowed to 100 between the router and the ATA shouldn't be that big an issue, but do keep an eye on your download rates and let us know what you find.

When going from Cellpipe-->SPA3102-->WRT610N, I was getting max download of 7mb/s to my local computer.

When going from Cellpipe-->WRT610N-->SPA3102, I get a bit over 25 mb/s.

QOS settings in the SPA3102 don't seem to help.

What's really annoying though is that in order to access the SPA3102 from its web interface, I can see no other way other than to run RJ45 cable to a computer to access 192.168.0.1(the SPA3102N) from the SPA3102's ethernet port. Going from Cellpipe-->SPA3102-->WRT610N, I don't need to run RJ45 cable. If you or someone else has a solution (other than using a wireless bridge), I'm interested.

[Liptonbrisk]

The problem now is that I appear to be having issues getting name display to show up on my Panasonic KX-TGA552M phone properly now, however. I seem to only be getting phone numbers to show up.

Also, I find this a bit troubling. If anyone has any suggestions, I'd appreciate reading them.

[FONGO_steve]

The problem now is that I appear to be having issues getting name display to show up on my Panasonic KX-TGA552M phone properly now, however. I seem to only be getting phone numbers to show up.

Also, I find this a bit troubling. If anyone has any suggestions, I'd appreciate reading them.

I'll start with a simple suggestion: tried a different phone?
Our server sends out the name+number of those calling you, if available. So if it isn't being shown, then ATA or phone are likely the culprit.

[Liptonbrisk]

The problem now is that I appear to be having issues getting name display to show up on my Panasonic KX-TGA552M phone properly now, however. I seem to only be getting phone numbers to show up.

Also, I find this a bit troubling. If anyone has any suggestions, I'd appreciate reading them.

I'll start with a simple suggestion: tried a different phone?
Our server sends out the name+number of those calling you, if available. So if it isn't being shown, then ATA or phone are likely the culprit.

I'm pretty sure it's a setting in the SPA3102, since PSTN also seems to be causing this problem through the SPA3102. Without the SPA3102 name display works fine with regular Bell phoneline. So, if someone has a SPA3102 related suggestion, that would be great.

[Bloodsong]

What's really annoying though is that in order to access the SPA3102 from its web interface, I can see no other way other than to run RJ45 cable to a computer to access 192.168.0.1(the SPA3102N) from the SPA3102's ethernet port. Going from Cellpipe-->SPA3102-->WRT610N, I don't need to run RJ45 cable. If you or someone else has a solution (other than using a wireless bridge), I'm interested.

Well, a few possibilities, one you're now logging into your SPA from the front end (WAN port), you would have to enable remote web-access to connect directly as though from the WAN.

Don't worry, this is safe as long as you don't setup a port-forwarding rule from the WRT to the SPA's remote access port (usually 8080 or 8088 by default.)

Next, ignore the WAN/Internet port and connect through one of the switch ports to the WRT, you should then be able to keep the SPA on the same subnet as the rest of your computers and connect via it's LAN IP.

The only other option beyond that I could see is using some VPN magic, which would require that the SPA is capable of being a VPN client, and I know nothing about third party firmware capabilities for ATAs, nor do I trust them to do something like VPN connections reliably.

*thinks*
If you're connecting an IP Phone to the ATA it may be possible to bounce off of that somehow, such as using it as an SSH/Telnet proxy, but that too would require a little white-hat magic

[Liptonbrisk]

Well, a few possibilities, one you're now logging into your SPA from the front end (WAN port), you would have to enable remote web-access to connect directly as though from the WAN.

Remote Management Access?

Okay, I've enabled that.

Next, ignore the WAN/Internet port and connect through one of the switch ports to the WRT

How?

[Bloodsong]

Well, a few possibilities, one you're now logging into your SPA from the front end (WAN port), you would have to enable remote web-access to connect directly as though from the WAN.

Remote Management Access?

Okay, I've enabled that.

Next, ignore the WAN/Internet port and connect through one of the switch ports to the WRT

How?

Sorry I should have been more clear. "Next option"

If you've turned on remote management access then you should be able to connect by it's front facing IP, just make sure in the web browser to punch in the IP AND remote management port (ex. A.B.C.D:8080).

[Liptonbrisk]

If you've turned on remote management access then you should be able to connect by it's front facing IP, just make sure in the web browser to punch in the IP AND remote management port (ex. A.B.C.D:8080).

Ah, yeah, that doesn't appear to work, unfortunately (tried that already). But thanks for the info.

[Bloodsong]

Alright, if you plug into one of the switch ports instead of the WAN port your ATA should acquire a DHCP address. I don't know how configurable these are. (whether you'll be able to pick an IP or not)

Being through a switchport instead of the WAN port it should be able to access by IP the way you're used to.

[Liptonbrisk]

Alright, if you plug into one of the switch ports instead of the WAN port your ATA should acquire a DHCP address. I don't know how configurable these are. (whether you'll be able to pick an IP or not)

Being through a switchport instead of the WAN port it should be able to access by IP the way you're used to.

The SPA3102 always has been attached to Ethernet port 1 in my setup, and it's been assigned a static IP using the Linksys WRT610N as the gateway (I use static IPs).

Cellpipe ethernet 1-->Linksys WRT610N (does PPoE sign in) internet port
Linksys WRT610N ethernet 1-->SPA3102 internet port

I cannot use http://178.16x.x.x:8080.
And I can't use 192.168.0.1 (spa3102 default)

[Bloodsong]

The SPA should be assigned by to an IP on the same subnet range as your computer given by the router, not an external IP.

This subnet range should fall into the Private Class C range (192.168.x.y/24)

So when you do an ifconfig (linux) or ipconfig (windows) from a terminal/command prompt, you should see your computers IP as 192.168.x.y, what you need to see is that "192.168.x" is the same on both your computer and your SPA. This would place them in the same subnet.

The last thing you want is for internal network equipment to be on a public IP address.

[Liptonbrisk]

The SPA should be assigned by to an IP on the same subnet range as your computer given by the router

They are, and they are on the same subnet. It's a static IP (assigned by the router) based on mac address. The SPA3102 is assigned to DHCP. This is on the WAN side on the SPA3102. The LAN side of the SPA3102 (which I'm not using) is set to the default 192.168.0.1. I just the set the LAN side to same subnet--and still can't see 192.168.0.1 without using RJ45 cable from the SPA3102's ethernet port running to a computer.

The last thing you want is for internal network equipment to be on a public IP address.

Yes, I haven't been exactly truthful about what specific IPs I assign, but they're in these ranges:
172.16.0.0 through 172.31.255.255
192.168.0.0 through 192.168.255.255

[Bloodsong]

Hehe alright, scared me there, class B private's okay
But still tricky to understand what's happening.

Generally speaking (ignoring the WAN port) if two systems are switched on the same network and subnet, you should not be having that issue >.>

If you're connecting VIA the WAN port, then it should just be a matter of remote admin and connecting to the right port.
Unfortunately I don't have a SPA to test with, perhaps when this disk failure and response time investigation is through, Kris or Steve will be able to test some settings with us.

Or one of the other users who has a SPA?

[Liptonbrisk]

Generally speaking (ignoring the WAN port) if two systems are switched on the same network and subnet, you should not be having that issue

Yes, that's what I thought too. So I am confused. I do have Dlink DAP-1522 bridge setup on 172.x.x.5 (assigned by linksys router), which I'm not positive that I setup properly. I'm just using the DAP-1522 for my audio/video gear. My a/v gear connects to the internet fine. My A/V gear has been assigned IPs by the WRT610N.

And this spa3102 is setup on 172.x.x.9 on the wrt610n--but the SPA3102 is not hooked up to the bridge. The SPA3102 is hooked up to the WRT610N.

Is that the problem (having the SPA3102 as .9 and coming after the bridge at .5)? I wouldn't think that would be the problem.

[Bloodsong]

No the order in which the addressing is assigned should not matter.

Should be as simple as 172.x.x.9:8080 (8088?) in a web browser for front end access. *frowns and looks around*

[Liptonbrisk]

No the order in which the addressing is assigned should not matter.

Remote Wan management in the SPA3102 suddenly started working. Odd.
But that's good anyway.