---
title: numbers.sip_provisioning_failed
description: 'The SIP registrar could not be reached, so no credential was created.'
summary: >-
  Returned when creating, rotating or revoking a SIP credential could not be
  completed against the registrar. Nothing is persisted — retry the request.
date: 2026-08-05T00:00:00.000Z
type: error
---


## Summary

`numbers.sip_provisioning_failed` means the SIP registrar could not be reached, or rejected the request, while creating, rotating or revoking a credential.

## Cause

SIP credentials are provisioned on the registrar synchronously, because the registrar — not Sautikit — generates the username and password. A successful response therefore proves the credential exists and is usable.

The same property means there is nothing useful to return when the registrar is unavailable: a password Sautikit invented locally would not register. So the request fails instead.

## What happened to your data

Nothing was created or changed:

- **On create**, no credential exists. It does not appear in the list, and it does not consume a slot against the number's limit.
- **On revoke**, the credential is left `active`. Sautikit will not report a device as disconnected when it may still be working.

## Resolution

Retry. This is a transient condition — the registrar is momentarily unreachable, not misconfigured.

If it persists, contact support. A configuration problem (as opposed to a transient one) surfaces as [`numbers.sip_config_unavailable`](/developers/errors/numbers.sip_config_unavailable) instead.

## Example response

```json
{
  "error": {
    "code": "numbers.sip_provisioning_failed",
    "message": "could not reach the SIP registrar to provision this credential — nothing was created; please retry",
    "request_id": "req_01900000abc"
  }
}
```

## Next steps

- [Numbers concepts — SIP credentials](/developers/concepts/numbers)
- [`numbers.sip_config_unavailable`](/developers/errors/numbers.sip_config_unavailable) — the registrar is not configured at all