<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix"><br>
<br>
You mean this list?<br>
<a class="moz-txt-link-freetext" href="https://whirlpool.net.au/wiki/fttn_registered_modem_router">https://whirlpool.net.au/wiki/fttn_registered_modem_router</a><br>
<br>
Matt.<br>
<br>
On 19/07/2016 6:00 PM, McDonald Richards wrote:<br>
</div>
<blockquote
cite="mid:CACrsH-7vmcQZHGtdBxko7uu61PKa2f0nUNE73qAd_p707Q_yRQ@mail.gmail.com"
type="cite">
<div dir="ltr">Why the secrecy regarding CPE
compliance/non-compliance? This is hardly a competitive
advantage... There would be a list on Whirlpool or similar
within months if they asked users "what's your NBN CPE?"
<div><br>
</div>
<div>Macca</div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mon, Jul 18, 2016 at 10:56 PM, Terry
Sweetser <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:terry+AusNOG@skymesh.net.au" target="_blank">terry+AusNOG@skymesh.net.au</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> Hi Noggers,<br>
<br>
This thread has presented some "not quite right
information".<br>
<br>
An NBN RSP is required to register each and every device
with NBN(tm) they plan to use with FTT[BN].<br>
<br>
That list becomes the "Approved List" of devices for your
RSP -- NBN(tm) will actually accept faults only if the
device is on that list.<br>
<br>
The list is "Commercial-In-Confidence" between your RSP
and NBN(tm).<br>
<br>
Several well know manufacturers have failed to meet the
full list of specifications from NBN(tm) and can not be
registered.<br>
(Do your own homework, I can't disclose who they are ...)<br>
<br>
For those of you who have access to the NBN Portal --
check the Trouble Tickets tab, start a Service Request and
select "VDSL2 equipment registration" for all of the
options.<br>
<br>
Of note is:<br>
<blockquote type="cite">
<dl>
<dd>Requirements for VDSL2 equipment registration
Service Requests</dd>
</dl>
<dl>
<dt><br>
</dt>
<dd> Before submitting this request, please ensure the
following requirements are met: <br>
<br>
<ul>
<li>The VDSL Customer Equipment and firmware in
this Service Request:
<ul>
<li>Supports all applicable mandatory ITU-T
requirements for vectored VDSL2 and NBN Co
NEBS Product Technical Specification</li>
<li>Has been tested successfully against every
relevant feature of the NBN Co NEBS Product
Technical Specification</li>
</ul>
</li>
<li>Upon request, you can provide evidence the
above requirements are met</li>
</ul>
</dd>
</dl>
</blockquote>
<br>
Sure, you can try to fudge the whole process, but you'll
get an instant "fail" of the Service Restoration process
when the NSOC see that your modem is not on the list
and/or compliant.<br>
<br>
<br>
<pre cols="72"><a moz-do-not-send="true" href="http://about.me/terry.sweetser" target="_blank">http://about.me/terry.sweetser</a>
</pre>
<br>
</div>
<br>
_______________________________________________<br>
AusNOG mailing list<br>
<a moz-do-not-send="true"
href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a><br>
<a moz-do-not-send="true"
href="http://lists.ausnog.net/mailman/listinfo/ausnog"
rel="noreferrer" target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br>
<br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
AusNOG mailing list
<a class="moz-txt-link-abbreviated" href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a>
<a class="moz-txt-link-freetext" href="http://lists.ausnog.net/mailman/listinfo/ausnog">http://lists.ausnog.net/mailman/listinfo/ausnog</a>
</pre>
</blockquote>
<p><br>
</p>
</body>
</html>