Overview

Replacing a carrier-provided Optical Network Terminal (ONT) with a third-party OEM Optical Network Unit (ONU) is technically feasible for data services, but preserving legacy telephone (VoIP/POTS) service presents unique B2B integration challenges. This technical FAQ addresses pre-sales optical compatibility queries and post-sales configuration hurdles specific to enterprise deployments.

Frequently Asked Questions

Q1: Can I replace a carrier-provided ONT with an OEM ONU without losing telephone service?

Yes, but retaining telephone service requires the OEM ONU to support the carrier's specific VoIP signaling protocol (SIP or IMS-SIP) and the carrier must allow third-party ONU registration on their OLT. Carriers typically authenticate ONUs via a unique serial number or registration ID (e.g., MAC address or ONT ID) that must be pre-provisioned in the carrier's Element Management System (EMS) . Without updating the carrier's provisioning database, the OLT will not recognize the new ONU, and all services—including voice—will fail.

Q2: What optical module specifications are required for third-party ONU compatibility with carrier OLTs?

The OEM ONU must operate on the same PON technology (GPON, XGS-PON, or EPON) and wavelength plan as the carrier's OLT. For GPON, this typically means 1310nm upstream and 1490nm downstream; XGS-PON uses 1270nm upstream and 1577nm downstream . Additionally, the ONU's optical transceiver must meet the carrier's optical power budget (Class B+, C+, etc.) and the OLT must support the ONU's vendor ID or accept spoofed serial numbers if configuring a non-carrier device.

Q3: How do I configure VoIP/SIP parameters on an OEM ONU via CLI for telephone service?

VoIP configuration on an OEM ONU requires entering the carrier-provided SIP server address, user credentials (phone number and password), and proxy port into the ONU's voice service profile via CLI. On devices like Raisecom ONUs, the command structure is epon-onu [slot/olt/onu] voice followed by sip-agent voip-protocol {sip | ims-sip} to set the protocol type, then sip-user aor [number] username [user] password [pass] to register the line . Without these exact parameters obtained from the carrier, the ONU's POTS port will remain non-functional even if data connectivity succeeds.

Q4: What is the maximum throughput of a carrier-grade OEM ONU for enterprise voice and data traffic?

Enterprise-class OEM ONUs typically provide line-rate throughput up to 2.5 Gbps downstream and 1.25 Gbps upstream for GPON, or 10 Gbps symmetrical for XGS-PON. The backplane capacity is generally non-blocking for these rates, ensuring voice packets are not throttled by data traffic. For B2B deployments with high call volumes, selecting an ONU with hardware-based QoS and dedicated voice VLAN support is critical to maintain MOS (Mean Opinion Score) quality above 4.0.

Q5: How does ONU serial number spoofing work, and is it a viable method for replacing carrier ONT?

ONU serial number spoofing involves cloning the original carrier ONT's serial number onto the third-party ONU so the OLT recognizes it as the authorized device. While technically possible on some ONU models with writable serial number fields, it violates carrier terms of service and may trigger security alarms in the OLT . Some carriers actively detect duplicate serial numbers and will deny service to both devices, causing a complete outage. This approach is not recommended for production B2B environments.

Q6: What is the difference between carrier-provided ONT and OEM ONU in terms of telephone service support?

Carrier-provided ONTs are pre-configured and remotely managed by the carrier via OMCI/TR-069, with voice parameters automatically provisioned. OEM ONUs lack this automatic provisioning and require manual CLI configuration of all VoIP parameters . Additionally, carrier ONTs often integrate a POTS splitter or dedicated RJ-11 port with hardware echo cancellation and FAX support tuned to the carrier's softswitch, whereas generic OEM ONUs may require additional ATA devices or firmware updates to achieve equivalent voice quality.

Q7: How can I troubleshoot redundant power failover issues on an OEM ONU in a B2B deployment?

Redundant power failover troubleshooting begins with verifying the ONU's power status LEDs and checking that both AC/DC inputs are receiving voltage within the specified range. If the ONU fails to switch to the backup supply, check the power module seating and the alarm contacts on the rear panel. For managed ONUs, CLI commands such as show power or show system status can reveal which power source is active and whether the failover circuit has triggered an alarm. Persistent failover failure often indicates a faulty power module or a backplane power distribution issue.