FTTN Order

[hhwong]

Dane,
Any hint of Fusion to FTTN migration for current Fusion customer? Darn seeing the positive outcome really killing us

We can do this now, the "migration" is really just a new Fusion FTTN connection, then port your number and disconnect the old Fusion. It's not yet on the website, but you can order by phone, daytime. The staff have access to our beta test www site and can place orders for sites which are qualified.

Jumped on that right away. Ordered!

[bobfff]

Not happy, probably have to drop Sonic.

Just called Sales. I have Fusion and saw the last post about being able to order FTTN. After checking, the agent told me I would not be able to order the FTTN service (even though AT&T says it can deliver up to 75 mbps to my address) because "our president has made a decision about which locations we'll provide FTTN to.") In other words, it's technically possible to provide Sonic service piggybacking on AT&T to my home but for other reasons (preserving Fusion market share?) Sonic won't do so.

I am disappointed and much as I don't like the idea of switching to cable or AT&T, I do not see the value in continuing a relatively low speed connection with Sonic for substantially improved service, even with corporate entities I dislike.

Just a heads up to others who may have anticipated better speeds and Sonic's other advantages.

Bob

[klui]

Here's what happened during my migration yesterday.

The AT&T tech came within the specified window. He was a very friendly and easy-going guy. I had a lot of fun picking his brain.

Trying to write significant events during the migration:

• If you're between 1500-3000 feet from the VRAD you get a single pair; if you're over 3000 feet, you get bonding; I can't recall what happens if you're less than 1500 feet--I think you get bonding for even faster speeds.
• He connected my internal wiring to the telco portion of the NID, bypassing the owner's module to give me as much headroom as possible.
• My existing DSL+POTS were kept active due to the "Enterprise" nature of the installation -- "we're told people don't want to have any potential downtime." Because I only punched down two pairs of conductors, I didn't want to worry about the DSL and just kept POTS connected, asking the "DSL" pair switched to FTTN. An added benefit of using VoIP is I no longer require my adjunct ADSL splitter, which I would have had to upgrade if I kept POTS.
• My FTTN was supposed to be connected to the port serving my ADSL1. Due to keeping ADSL1 active, the tech connected the FTTN to another pair on the pole.
• His JDSU tester showed I am between 2400-2900 feet from the VRAD, closer than to my ADSL1's RT. My maximum download rate was a little over 40000 kbps, with a profile limit of 25000 kbps. The profile was using a little over 60% of the line's capacity.
• I was given a Pace 5031NV. I thought I would get an NVG589/599 so all the plans of using IP Passthrough went out the window. I guess that's about right since the 5x9 support bonding and I only have one pair. I normally run with NoScript and I had a tough time getting the Pace configured properly. There is probably JS that informed when a reboot was necessary after certain changes. My old Netopia 3546 didn't have this quirk.
• Using DMZ+.
• The Pace took a long time to connect at first, and we thought it was DOA. I thought I saw two reboot cycles.
• Connected the Sonic ATA to the modem and not my firewall. The ATA is supposed to have a web interface but ports 80 and 443 were closed. The IVR works. Temporary number works.
• The tech did something and found there were bridge taps. He dispatched a ticket to have them removed. His concern was not with the margin but potential for my line to be disconnected in the future. Another tech came by an hour after the first and discovered 3 taps totaling 1200 feet. After their removal, my maximum download rate reached a little over 55000 kbps. The profile limit remained the same giving me over 50% margin. I didn't pay attention to how the upload stats changed.
• Speedtest results from Sonic and speedtest.net were essentially the same before and after the bridge taps were removed: ping: 27ms; download 23 Mbps; upload: 1.9 Mbps.
• UV Realtime isn't fully compatible with the modem but it estimates I'm 1500 feet from the VRAD (I'll trust JDSU in this case). It recommended I be placed on the 32200/5040 profile. EDIT: there is actually no discrepancy. I had forgotten that when the tech told me the distance it was before the bridge taps were removed. Taking the average distance of 2700 feet and subtracting the 3 taps that totaled 1200 feet removed gives 1500 feet. It's interesting how internet maps calculation is much lower.
• The Pace's web interface has inconsistent response times. Sometimes the links are served right away, other times, it takes a while for the same links to come up. Software 9.8.1.489233-att.
• DSLreports states AT&T's new gateways have a limited number of NAT sessions, regardless if a user is using DMZ+ or IP Passthrough--a moot point if the hardware supported true bridge mode. The 5031NV has 1024 sessions while the NVG599 has 2048. I've read that NVG599s with older firmware allowed 8096 sessions. My firewall allows over 8000 sessions. I'm unsure if the limit is actually there or maybe something is compensating the limit shown on my gw. I sometimes see free sessions at even 0/1024 and I can still go to another website. There is another metric labeled "x/512 used in inbound sessions." I sometimes see x > 512.
• These gateways are neutered and dumbed down. I guess most people don't care. I would have preferred an ssh interface and SNMP capability. Even my 3546 has SNMP, although its MIB don't expose DSL line statistics. I monitor my devices and SNMP can come in handy. Remote syslog is available.
• It was relatively painless to modify the Cayman check_dsl_stats script to scrape the stats. Refer to https://www.dslreports.com/forum/r10456365- and https://www.dslreports.com/forum/r29352774-

Comparison of some stats on DSLreports: https://www.dslreports.com/forum/r29751 ... ings-stats

My current stats:

Code: Select all

                 Down          Up
User Rate:       25311 kbs     2036 kbs
Max User Rate:   54892 kbs     2036 kbs
Noise Margin:    21.6 dB       0.0 dB
Attenuation:     18.3 dB       0.0 dB
Output Power:    14.1 dBm      -5.5 dBm
Protocol:        G.993.2_8d
Channel:         Interleaved
DSLAM Vendor:    Country {65461} Vendor {CXSY} Specific {852 }

.
.
.

Code: Select all

Rate Cap         54634 kbs
Atten @ 300kHZ   9.2 dB

Over a period of 15 hours, I've experienced 0 errors, retrains, loss of framing/signal/power/margin. There were 63 corrected blocks.

The Protocol above indicate I'm on the 8d profile. https://www.dslreports.com/faq/uverse?text=1 Search for "What are connection profiles"

[toast0]

The VoIP gateway isn't working yet (its webpage says it's not registered), support said to call back tomorrow if it's still not working.

The gateway is now working! It's still on the temporary number (as expected), and its built in webserver and telnet server are disabled.

[ronandpablo]

Good news! However I called Sales and here's (my) story:

Seems that FFTN is not "officially" available to my location because seems the distance is a bit too much and the performance in speed is pretty much the same (~6mbps).

I'd _love_ to go FFTN for the main reason that I've been with too many instability problems with the current DSL (Support is aware and they are working hard on fixing it but it seems to be pointing the problem is with ATT, since we already ran a day test with the modem connected to the MPoE).

My say is: if the stability is going to improve because it will be done through new wiring (outside of the house and all the feet/miles of wiring) then I'd love to change to FFTN, I'm not *too* concerned about the speed since seems I'll be getting the same one.

Sales suggested that perhaps give it a try to the adjustments that Sonic support did today and if that doesn't fix it then may just manually order the FFTN change.

Suggestions? Would FFTN provide better stability? Problem we have is too many disconnects.

Trying as hard as possible to stay with Sonic with a more stable connection before going with the devil

[andsonic]

Report of my transition to FTTN:

I've been a Sonic legacy DSL user for years. The availability tool kept saying I was to far and behind a remote terminal. My legacy DSL speed was 1.5 mbs per second.

After a major saga with AT&T phone repair techs (bad damage on their side, I posted a pic earlier in the thread), FTTN is finally live. 19 mbs per second and I'm quite happy. We're just over 4000 ft from the node.

[Guest]

Not happy, probably have to drop Sonic.

Just called Sales. I have Fusion and saw the last post about being able to order FTTN. After checking, the agent told me I would not be able to order the FTTN service (even though AT&T says it can deliver up to 75 mbps to my address) because "our president has made a decision about which locations we'll provide FTTN to.") In other words, it's technically possible to provide Sonic service piggybacking on AT&T to my home but for other reasons (preserving Fusion market share?) Sonic won't do so.

I am disappointed and much as I don't like the idea of switching to cable or AT&T, I do not see the value in continuing a relatively low speed connection with Sonic for substantially improved service, even with corporate entities I dislike.

Just a heads up to others who may have anticipated better speeds and Sonic's other advantages.

Bob

From what I've read Sonic was letting people with old ASL (not Fusion) get first dibs on FTTN. They are planning to expand FTTN to Fusion customers in the next month or so. So.... patience?

[Guest]

We're also wrapping up ADSL2+ to VDSL2 migration process, so once that's available there will be an upgrade option for everyone. VDSL2 and optional X2 for those close, X2 for those at moderate lengths, and FTTN for those further out but served by an AT&T VRAD cabinet.

I've lost track at this point. Will the AT&T VRADs be using VDSL2? Or does it vary from box to box because of a mix of equipment?

[andsonic]

We're also wrapping up ADSL2+ to VDSL2 migration process, so once that's available there will be an upgrade option for everyone. VDSL2 and optional X2 for those close, X2 for those at moderate lengths, and FTTN for those further out but served by an AT&T VRAD cabinet.

I've lost track at this point. Will the AT&T VRADs be using VDSL2? Or does it vary from box to box because of a mix of equipment?

I'm on FTTN as of last week. My router claims its ADSL2+

[Guest]

I'm on FTTN as of last week. My router claims its ADSL2+

So what's your speed, and distance to the FTTN box (for context)?