78200X · Question #84
A remote worker with an Avaya SIP Client visits their office headquarters where the IP Office and one-X® Portal are located. Which two technologies enable the worker to re-register locally? (Choose…
The correct answer is B. Split DNS C. Network Access. See the full explanation below for the reasoning.
Question
A remote worker with an Avaya SIP Client visits their office headquarters where the IP Office and one-X® Portal are located. Which two technologies enable the worker to re-register locally? (Choose two.)
Options
- APort forwarding
- BSplit DNS
- CNetwork Access
- DXMPP
- EBorder controller
How the community answered
(40 responses)- A10% (4)
- B85% (34)
- D3% (1)
- E3% (1)
Community Discussion
6
Wesley A.Feb 21, 2026Split DNS and Network Access are your two answers here. Split DNS lets the SIP client resolve the IP Office server to its internal address when the worker is on the corporate LAN instead of the public address they use remotely, and Network Access detection is what tells the Avaya client it has gone from outside to inside so it can automatically switch registration without the user doing anything manually.
Ingrid P.Feb 25, 2026Split DNS and Network Access are the right picks here. Split DNS lets the SIP client resolve the IP Office address to a local IP when on-site instead of the external one, and Network Access handles the local re-registration detection so the endpoint switches cleanly from remote to on-net behavior without manual intervention.
Nina C.Mar 4, 2026Split DNS and Network Access let the client detect and re-register locally when on-site.
Ingrid P.Mar 6, 2026Split DNS handling is solid, but the re-registration timing depends heavily on your NRPT (Name Resolution Policy Table) flush interval, which can delay local detection by minutes if not tuned.
Tomasz V.Feb 27, 2026I am going with B and E on this one, because Split DNS handles the client resolving the internal FQDN when it detects it is on the corporate LAN, and the Session Border Controller is what the SIP REGISTER traverses when the worker is remote, so without the SBC already anchoring that registration path you cannot cleanly hand off or re-register to the local IP Office proxy when the client transitions inside. The SBC is not just a firewall pinhole, it is a back-to-back user agent that owns the registration state, which is exactly why it belongs in this answer.
Nina C.Mar 2, 2026Tomasz, your SBC reasoning makes sense in a general remote-worker scenario, but for this specific question the third piece is C, not E, because the SBC handles external traversal while C addresses what actually enables the client to re-home to the internal IP Office proxy once it detects it is on the LAN, which is the hand-off mechanism the question is really testing.