> ## Documentation Index
> Fetch the complete documentation index at: https://docs.famulor.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Zadarma
> Find your API keys, import a number, or connect Zadarma manually with direct SIP or a PBX extension
Use [carrier import](/telephony/carrier-import#zadarma-import) for automatic routing of a direct Zadarma number. Use the manual instructions below to keep an existing PBX call flow or manage SIP routing yourself.
## Get your API key and secret
1. Sign in to [your Zadarma account](https://my.zadarma.com/).
2. Open **Settings → Integrations and API → Keys and API**. In the German portal this is **Einstellungen → Integrationen und API → Schlüssel und API**.
3. Copy **Key** and **Secret** separately into Famulor's Zadarma connection form. If no keys exist yet, create them using the action shown by Zadarma. Existing keys do not need to be changed.
4. These are API credentials. The SIP login and SIP password used by the manual setup are different credentials.
## Automatic import
Activate a virtual number and disable its test mode. In Zadarma, assign it to a direct SIP login that is not linked to the PBX. If you want to keep PBX routing, use the manual PBX path instead. Zadarma can require a first top-up and a connected number before allowing an additional SIP login; keep a free login slot available.
Open **Settings → Phone numbers → Add a number → Import from your carrier → Zadarma** in Famulor. Enter a connection name, API key, secret and SIP region, then load the numbers. Select one active number and import it. Each connection creates a dedicated SIP login and replaces that number's SIP destination. Use a separate connection for each additional number, then assign an assistant.
For removal, restoration, troubleshooting and API/MCP/CLI commands, see [carrier import](/telephony/carrier-import#zadarma-import).
## Manual setup in Famulor
Open **Settings → Phone numbers → Add a number → Add SIP integration**, select your SIP region and copy the platform SIP host. Use these settings:
| Setting | Direct SIP | PBX extension |
| - | - | - |
| Trunk type and number | **Phone number (DID)**, exact public number with `+` and country code | Same; do not put the PBX extension in the DID field |
| Inbound authentication | **Provider source IPs**, direct list below | **Provider source IPs**, PBX list below |
| Outbound termination address | `sip.zadarma.com` | `pbx.zadarma.com` |
| Outbound username/password | From Zadarma **Settings → SIP settings** | From **My PBX → Extensions**, full login such as `123456-100` and its password |
| Transport / media encryption | **TCP** / **Disabled** | **TCP** / **Disabled** |
| Caller identity / number format | **Phone number**, international with `+` | Same |
Keep inbound username/password empty for these SIP-URI forwarding paths. Use credentials for **outbound** authentication. Select your public number as **CallerID** on the corresponding SIP login or PBX extension in Zadarma. Leave secure trunking off for this TCP profile. The platform does not register as a SIP phone; an “offline” extension alone does not prove forwarding has failed.
These earlier portal screenshots show where the settings are located. Labels may differ by language. If SIP settings says the login is linked to the virtual PBX, follow the PBX path instead. Use the full PBX login, not only its short extension number.
## Forward incoming calls from Zadarma
Build the destination from your exact public DID and the SIP host copied from Famulor:
```text theme={null}
+49301234567@YOUR_PLATFORM_SIP_HOST:5060;transport=tcp
```
Replace both example parts; use the hostname, never a resolved IP.
**Direct SIP:** in Zadarma, open **Settings → Virtual phone numbers**, click the number's gear, open **External server**, enable **External server (SIP URI)**, enter the destination and save.
**PBX:** open **My PBX → Extensions**, expand the intended extension, and open **Call forwarding and voicemail**. Choose **Always active** (or your intended availability condition), then **External server (SIP URI)**, enter the destination and save. Under **My PBX → Incoming calls and voice menu**, ensure the public number's scenario actually reaches that extension.
Earlier portal screenshots: Services → Connect number → Active numbers, then the gear and External server. Account details are obscured. Use your own number and the current settings above; displayed prices are illustrative.
## Inbound signaling addresses
Use only the list for the selected path. These are source addresses for calls **from Zadarma to Famulor**, not an outbound allowlist. The direct and PBX lists were checked against Zadarma's documentation and account portal on **7 October 2026**; verify the current list before changing a trunk.
**Direct number → external SIP URI:**
```text theme={null}
185.45.152.216/32
185.45.155.33/32
```
**PBX extension → external SIP URI:**
```text theme={null}
185.45.152.164/32
185.45.152.177/32
185.45.152.200/32
185.45.155.14/32
185.45.155.16/32
195.122.19.20/32
195.122.19.29/32
15.235.128.70/32
31.31.222.201/32
185.45.154.15/32
```
In the PBX forwarding form, **Show IP** displays the signaling hosts. Do not substitute the broader firewall/media networks shown underneath, and always keep the exact DID on the Famulor trunk.
## Check both directions
Assign an assistant, call the number from an external phone, and check **History**, the assistant response and two-way audio. Then place one outbound test to a number you control: verify audio and the caller ID displayed by the receiving phone. Outbound needs Zadarma credit and any applicable destination permissions. Test transfers separately; a successful inbound call does not confirm transfer support.
Sources: [Zadarma direct/PBX routing and gateway lists](https://zadarma.com/en/support/instructions/twilio/), [PBX voice-agent settings](https://zadarma.com/en/support/instructions/elevenlabs/), [Zadarma API](https://zadarma.com/en/support/api/).
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.