Skip to main content

Avaya SBC Phones Acquiring Service

Jeremy Boilard

Problem Statement

Remote Avaya phones remain on “Acquiring service” after an internet or power interruption. The Avaya SBC may boot with an incorrect date/time because of an intermittent hardware clock/RTC issue. When the SBC starts with a historical date, network time synchronization may not automatically correct the clock, SBC services may not recover cleanly, and remote registrations may fail. In the observed case, User Agent (UA) profiles were also corrupt after recovery and had to be removed and re-added.

Impact

Remote users cannot register or log in to Avaya phones. Local phones may remain operational, but remote agents may be unavailable until SBC services, time synchronization, and UA profiles are restored.

Alarm

No alarm was associated with this issue.

Troubleshooting Steps

  1. Confirm the scope of impact: determine whether only remote phones are stuck on “Acquiring service” and whether local phones are still registered.
  2. Ask whether there was a recent internet outage, power event, reboot, or manual restart before the issue began.
  3. Access the Avaya SBC by SSH if available. Avoid an uncontrolled hard power cycle while SSH access is active unless required, because access may be lost during recovery.
  4. Check the current SBC date/time and NTP status with: `timedatectl`.
  5. If the date/time is incorrect, manually correct it and re-enable NTP: `timedatectl set-ntp false`, then `timedatectl set-time "YYYY-MM-DD HH:MM:SS"`, then `timedatectl set-ntp true`.
  6. Reboot the SBC if required using: `reboot`. Allow extra time for the reboot because the process can be slow.
  7. After reboot, verify that the corrected date/time held and that the web administration interface and SBC services are available.
  8. If services do not recover cleanly, attempt a controlled SBC service restart from SSH: `/etc/init.d/ipcs-init stop`, wait approximately 15 seconds, then run `/etc/init.d/ipcs-init start`.
  9. If the web administration interface or core services still do not recover, follow the approved internal procedure to restore the SBC backup image/configuration or escalate to engineering for deeper boot/service troubleshooting.
  10. Once the SBC is accessible, review remote phone registration status and inspect User Agent (UA) profiles associated with remote phone registrations.
  11. If remote registrations still fail after SBC recovery and time correction, remove and re-add any corrupt UA profiles, then retest registration.
  12. Validate with a known-good Avaya remote phone, such as a J159 or J179, before asking users to retry production phones.
  13. Have affected users register the phone to the appropriate base extension and then log in with their assigned user extension. Do not share or document passwords in the ticket or article.
  14. Confirm that the remote phones show registered in the SBC/system status after user login.
  15. If the issue recurs after power or internet interruptions, investigate the SBC RTC/hardware clock. A failing RTC can cause the SBC to boot with an incorrect date/time and require manual recovery.

Resolution

The SBC date/time was corrected manually, NTP was re-enabled, and SBC services were restored. Remote registration continued to fail until corrupt UA profiles were removed and re-added. Lab testing with Avaya phones succeeded, and affected users were then able to register and log in. A later status check confirmed the remote phones were registered and operating properly. The underlying recurring cause was identified as an intermittent SBC RTC/hardware clock issue. Because the RTC/CMOS battery on the affected appliance model is not serviceable, permanent remediation requires SBC appliance replacement; otherwise the issue may recur after reboot, power loss, or internet disruption.