Skip to contentSkip to navigationSkip to topbar
Page toolsOn this pageProducts used
Looking for more inspiration?Visit the

22222: Emergency Status cannot be updated


WARNING: 22222

warning-22222 page anchor
PHONE NUMBERS
WARNING

This warning appears when you send an update request for an IncomingPhoneNumber that includes EmergencyStatus. Twilio does not enable or disable emergency calling by updating EmergencyStatus. Instead, associate or remove an emergency address with EmergencyAddressSid, then check emergencyAddressStatus to confirm whether the address is registered, unregistered, or still pending.

Possible causes

possible-causes page anchor
  • Your POST request to update an IncomingPhoneNumber included the EmergencyStatus parameter.
  • Your application tried to activate or deactivate emergency calling by setting EmergencyStatus to Active or Inactive. Twilio ignores those changes for emergency calling configuration.
  • You intended to register or remove an emergency address, but updated EmergencyStatus instead of EmergencyAddressSid.
  • Remove EmergencyStatus from the IncomingPhoneNumber update request.
  • To register emergency calling for a number, create and validate an emergency address if needed, then update the phone number with EmergencyAddressSid.
  • To remove an emergency address from a number, update EmergencyAddressSid to null. For curl, leave the value blank.
  • After you change the emergency address association, fetch the phone number and verify emergencyAddressStatus. A registered address is used when handling emergency calls from that number.
  • If you are replacing an emergency address, first disassociate the current address, confirm the number is unregistered, then associate the new address and confirm it becomes registered.

Additional resources

additional-resources page anchor