Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Terrydaktal]

I think for IPoE FTTC users connected to an MSE bRAS firstly through a QinQ GEA cablelink from the L2S to the EES and then a link to the MSE from the EES, the pseudowire goes from the MSE bRAS to the ISP edge? But for FTTC IPoE users connected to an EEA (before MSE upgrade?), the EEA pseudowires it to the core bRAS and then it's pseudowired to the ISP edge through the MSIL?

For non FTTC/P people, their broadband travels to the MSAN with the voice. I've seen diagrams that show the CMSAN applying CVLANs for broadband and SVLANs for voice (POTS to h.248) and the tier 1 FMSAN applying SVLANs for broadband. This presumably allows the correct H-VPLS pseudowires to be selected to the core bRAS or the correct egress ports to the correct MSE bRAS ethernet link if the EEA is an MSE bRAS instead (and if you're using IPoE then it can insert them for option 82 verification at the LNS). As for PPPoE users, I think you can still have L2TP tunnels set up over MPLS to the LNS. I don't think much changes there.

What it seems to me is that the FTTC/P and non-FTTC broadband is aggregated and ingresses into the EEA (MSE) node at the metro exchange as IP over ethernet over C/DWDM. So the EES must provide WDM capability like the FMSAN. For IPoE and PPPoE, the stacks egressing the EEA will be respectively IP over ethernet over AToM over MPLS over ethernet over DWDM, and IP over PPP over L2TP over UDP over IP over MPLS over ethernet over DWDM. And of course, h.248 over UDP over IP over MPLS over ethernet over DWDM

I've heard about the IEA but not really sure what that does I think just an aggregation switch between EEA and core bRAS. AP seems to be the link between bRAS and BEA and EP appears to be the link between AGC/BEA to the EEA and MSIL is the link between the EEA and CP/ISP edge router. I'm not if this is a dedicated EEA for MSIL hand-off or whether this EEA also handles the tasks of the EEA I mentioned earlier.

I see AMSAN a lot and I think that's just a term for the FMSAN between the CMSAN and the tier 1 node.

As for the voice, the MSAN line card performs POTS BORSCHT functions and converts POTS loop start signalling to H. 248 addressed to the AGC (presumably this is the MGC also called a softswitch / call server / call agent) at the metro node. I'm not sure whether the MSAN can perform an intra MSAN call to a customer connected to the same MSAN like an SSP can or whether it needs to contact the AGC and the AGC instructs it that the subscriber is on the same MSAN or whether calls always propagate to the call server (MGC) at the CP/ISP (which the AGC contacts using SIP) or whether theres a caching system going on.

As for connection with PSTN, one of the MGCs is going to have to connect to a signalling gateway and the signalling gateway to an STP and the STP to an SSP which has bearer channel links to the the MG (BT MSAN or ISP MG?).

Very important reference diagrams:
https://kitz.co.uk/adsl/images/btw_network.png
https://slideplayer.com/slide/7977235/
https://slideplayer.com/slide/7846865/
http://www.nyquistcapital.com/2007/02/27/bt21cn-supplier-analysis/
https://slideplayer.com/slide/7667001/
https://ibb.co/3Spgy7d
https://ibb.co/wsw7FV1
https://ibb.co/tBQqqN3
bt sin 472 & 511

[flilot]

The contents of my head are now all over the adjacent wall after exploding reading all those acronyms! 

[Alex Atkin UK]

Don't worry, I didn't understand any of it either.

Isn't it all moot anyway as they are transitioning everyone over to plain VoIP rather than routing the traffic over a dedicated VoIP VLAN?

[j0hn]

ISP's can use 802.1p to prioritize VOIP traffic.

With SOGFast it's mentioned in the STIN that VOIP traffic should be marked with 802.1p priority 4.

FTTP VOIP can be done with similar priority classes.

99% of the OP's post is WAY over my head.

Is there a question?
Or is this just a random post?

[niemand]

I understood most of this acronym soup, despite inaccuracies, though what the actual point of it was given the minor issues that most of 21CN is still broadband only, voice provided via Openreach WLR/FVA, and there are no operators using native Ethernet over BT Wholesale's WBC/WMBC services, all PPP, is a mystery to me.