> For the complete documentation index, see [llms.txt](https://help.sipgate.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sipgate.de/cloud-telefonanlage/en/getting-started/konfigurationsanleitungen/snom-telefon-reagiert-sehr-langsam-nach-autoprovisonierung.md).

# SNOM phone responds very slowly after auto-provisioning

Solution for slow Snom phones after auto-provisioning – adjust synchronization intervals or set fixed times.

When Snom phones are autoprovisioned and contact synchronization is also enabled, the phone may sometimes respond to commands only intermittently or with a significant delay. This is usually due to a large number of contacts being synchronized regularly.

In this case, the **intervals** at which contacts are resynchronized should be increased:

Log in to the Snom web interface ➔ Identity ➔ Features ➔ Phone Download Interval

Here, you can set the synchronization interval, up to a maximum of 1209600 seconds (= 14 days).

{% hint style="info" %}
Important: If you set the interval to 0, the phone syncs only on restart and not at any other time.
{% endhint %}

Alternatively, synchronization can be scheduled for a **specific time** of day. In the following example, synchronization takes place every day at 23:00:

{% code title="snom-provisioning-config.xml" %}

```xml
<prov_polling_enabled perm="RW">on</prov_polling_enabled>
<prov_polling_mode perm="RW">abs</prov_polling_mode>
<prov_polling_time perm="RW">23:00</prov_polling_time>
```

{% endcode %}

For more information, see the [Snom Help Center](https://service.snom.com/display/wiki/tbook_download_interval) .


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.sipgate.de/cloud-telefonanlage/en/getting-started/konfigurationsanleitungen/snom-telefon-reagiert-sehr-langsam-nach-autoprovisonierung.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
