Overview

In a B2B telecom deployment, an ONT (Optical Network Terminal) delivering VoIP service relies on a tightly coupled chain of SIP registration, FXS port provisioning, codec negotiation, NAT traversal, and QoS policy. When incoming calls bypass the ringing phone and land directly in voicemail, the fault almost always sits in one of those layers. This FAQ provides definitive, engineer-grade answers covering pre-sales ONT VoIP capability questions and post-sales troubleshooting of SIP, FXS, and network-side issues.

Frequently Asked Questions

Q1: Why are incoming calls to my ONT VoIP phone going straight to voicemail?

The most common cause is a failed or expired SIP registration, which forces the carrier's softswitch to route inbound calls to the voicemail fallback instead of the endpoint. Verify the SIP REGISTER status on the ONT's VoIP status page, confirm the registrar address, port, and credentials, and check that the registration refresh timer has not lapsed due to a WAN IP change or NAT timeout. If registration shows active, inspect the FXS port profile and dial plan for a no-answer or immediate-forward rule.

Q2: What SIP registration parameters must be correct for inbound calls to reach an ONT FXS port?

Inbound calls require a valid, active SIP REGISTER binding for the exact AOR (Address of Record) the carrier routes to, typically the assigned DID. Confirm the registrar/proxy FQDN or IP, the SIP domain, the authentication username versus the registered AOR (they often differ), the registration expiry interval, and the outbound proxy setting if the carrier mandates one. A mismatch between the registered contact URI and the DID the carrier maps to voicemail is the single most frequent misconfiguration.

Q3: How do I verify FXS port and dial-plan configuration on the ONT for incoming call delivery?

Check the FXS port administrative state, the assigned telephone number, and the call-routing profile bound to that port in the ONT CLI or web GUI. Common faults include a port left in 'shutdown' or 'unregistered' state, a DID mapped to the wrong FXS port, or a dial plan that applies an unconditional 'CallForwardAll' to the voicemail pilot number. Use the ONT's VoIP call-detail and debug logs to confirm whether an INVITE was received and which internal endpoint it was forked to.

Q4: How do NAT, firewall, and QoS settings on the ONT affect VoIP call delivery?

Inbound SIP delivery fails when the ONT's NAT or firewall drops unsolicited INVITEs or does not rewrite SIP/SDP headers consistently. Ensure SIP ALG behavior is either correctly configured or disabled in favor of a compliant SBC, confirm the required UDP/TCP ports (typically 5060/5061 plus the RTP range) are permitted inbound, and verify the voice VLAN is prioritized with DSCP EF (46) marking. Asymmetric routing or an unbound WAN interface for the VoIP service will also cause one-way or missed inbound calls.

Q5: What ONT VoIP specifications should I confirm before purchase for reliable inbound call handling?

Pre-sales, confirm the ONT supports SIP (RFC 3261) with configurable registration timers, at least 2 FXS ports with independent profiles, G.711/G.729/G.722 codecs, T.38 fax relay, and an integrated or configurable SBC/NAT-traversal function. Also verify the ONT's VoIP call capacity (concurrent SIP sessions), its supported registrar failover behavior, and whether the carrier's softswitch requires a specific SIP profile or provisioning model (TR-069/OMCI).

Q6: How do I capture and interpret SIP traces on the ONT to diagnose voicemail routing?

Enable SIP packet capture or debug logging on the ONT and filter for REGISTER, INVITE, and 3xx/4xx responses to the carrier proxy. A 403 or 401 on REGISTER indicates credential or IP-binding rejection, while a 404 or 480 on INVITE indicates the carrier cannot locate the AOR, which is the direct signature of voicemail fallback. Preserve the Call-ID and Contact headers to compare the ONT's registered contact against the DID mapping in the carrier portal.

Q7: What firmware, provisioning, and power considerations affect ONT VoIP registration stability?

Registration stability depends on firmware maturity, correct TR-069 or OMCI provisioning of VoIP parameters, and clean redundant power. After any firmware upgrade, re-verify that VoIP profiles persisted and that the SIP registration timer was not reset to a default that exceeds the carrier's NAT binding lifetime. On ONTs with dual power inputs, confirm both feeds are healthy, since a power event that reboots the VoIP subsystem will drop registrations until the next refresh cycle.

Q8: How do I escalate an ONT VoIP voicemail issue to the carrier or vendor with actionable evidence?

Escalate with a structured evidence package: the ONT model and firmware version, the SIP registration status and expiry timer, timestamped SIP traces showing the INVITE and its response, the FXS port and dial-plan configuration export, and the WAN IP/NAT binding status at the failure time. Include the carrier's DID-to-AOR mapping confirmation so the vendor can rule out endpoint configuration versus softswitch routing as the root cause.