Excellent, thanks

Yes. as BatBoy says you are lucky enough to be on a Huawei cabinet and your modem/router has G.Inp compatable software.

My understanding is that G.Inp is supposed to be applied to all VDSL2 lines, accepting the current issues with ECI cabinets, however there is a school of thought that G.Inp will only be applied to lines that due to their performance require G.Inp action (called re-transmission by BT )

I am of the belief that it is applied by default but certainly can not explain why some new users do not currently seem to have G.Inp applied and indeed some existing users are having G.Inp disabled ?

A DLM reset will removed G.Inp

Is that where OR reset, or can such a reset be caused by a user?

Where OR reset

In reply to a post by tiffy2:

Yes. as BatBoy says you are lucky enough to be on a Huawei cabinet and your modem/router has G.Inp compatable software.

My understanding is that G.Inp is supposed to be applied to all VDSL2 lines, accepting the current issues with ECI cabinets, however there is a school of thought that G.Inp will only be applied to lines that due to their performance require G.Inp action (called re-transmission by BT )

I am of the belief that it is applied by default but certainly can not explain why some new users do not currently seem to have G.Inp applied and indeed some existing users are having G.Inp disabled ?

Can you give examples of users disabled and/or never enabled on MWDS?

Can you give examples of users disabled and/or never enabled on MWDS?


Yes, me, MDWS ID tiffy, never enabled as stated earlier in this thread.
Other user I know of, kitz ID "j0hn", MDWS ID "minted", he has been waiting since February for G.Inp application.
There are certainly others who are on Huawei cabinets with compatable hardware & software awaiting G.Inp application.

MDWS users who have been de-G.Inp'ed other than by ECI cabinet issue:
Certainly more than the 10 currently showing on MDWS, all currently active users listing, circumstances not known, DSLAM reset etc., the site moderator, Tony Bailey could supply these details.

Regardless of reason for G.Inp de-activation why would DLM not re-apply G.Inp again ?

I can only speak for my line but I was enabled in March and it took several week for G.INP to be enabled. I then had a reset and it took a couple of days to be re-enabled again after the reset.

Just looking at the two MWDS lines you mention I notice that there are a lot of errors on your line but your upstream SNRM is 16db which I find very strange. Also minted has a lot of upstream errors. I also have some upstream errors but upstream G.INP has not been implemented on my line just downstream.

Maybe the upstream anomalies on these two lines are something DLM can't cope with and hasn't enabled G.INP downstream.

Might be worth starting a thread on Kitz and get someone expert to look over your MWDS graphs.