Skip to main content
If your organization runs its own PBX or a contact-center platform, you can connect it the same way you’d connect any SIP trunk — no number porting required. Start with SIP provider guides for the shared mechanism (the platform SIP FQDN, the exact DID, and inbound authentication); this page covers what’s specific to eight PBX and contact-center platforms, including a few things that look broken but are expected.
Wildix sends calls to the platform over a static SIP trunk that doesn’t register: the trunk points at the platform SIP FQDN and answers the platform’s authentication challenge with the inbound SIP username and password. With registration off, WMS → Trunks shows the trunk in grey, as not registered. That’s expected, not a fault.On the platform, create one SIP trunk per DID: trunk type Phone number (DID), the exact +E.164 number, and SIP username/password for inbound authentication. The form also asks for a Termination address — enter your Wildix PBX hostname. Choose the EU SIP region if your PBX runs in Europe, then assign an assistant.In Wildix:
  1. Open WMS → Trunks and click + below the SIP trunk table.
  2. Set Address or Host Name to the platform SIP FQDN, without a sip: prefix, and leave Enable registration off.
  3. Enter the platform trunk’s SIP username as Auth Login and its password as Password. Leave From user empty: Wildix forces that value into the From header, so the assistant would see it instead of the caller’s number.
  4. Under Advanced, set Transport to TCP. For encrypted calls, use TLS with SDES-SRTP instead, and enable Secure trunking on the platform trunk too.
  5. In Audio codecs, keep only alaw and ulaw — Wildix enables g729 by default, so remove it. Set DTMF mode to rfc2833.
  6. Enable Show original caller number so the assistant sees the real caller, not your Wildix number. Enable Support Refer and Hold so the assistant can cold-transfer calls back to Wildix users.
  7. Add a Wildix dialplan rule that calls the exact +E.164 DID through this trunk — for example after hours from a timetable, as overflow from a group, or as an IVR option.
Option labels depend on your WMS version. Wildix’s trunk settings guide describes every field.
Route the full DID through the trunk, in the same +E.164 format as on the platform trunk. Don’t use an internal short code such as 999 as the number Wildix dials: the platform only accepts the exact DID, so the call never reaches the assistant.
This setup covers calls from Wildix to the assistant. Assistant calls out through your Wildix numbers aren’t a confirmed setup yet — contact support before you plan outbound calls or campaigns over Wildix.
OpenScape Business sends calls to the platform as an additional Internet Telephony Service Provider (ITSP) without registration. The steps are the same on OpenScape Business X1, X3, X5, X8 and S, in V3 and V4.Without registration, OpenScape Business grays out Authorization name and Password, so it can’t answer the platform’s authentication challenge. The platform trunk therefore uses Provider source IPs with your PBX’s fixed public IP address. If your PBX has no fixed public IP, don’t use a trunk: forward the calls to a platform phone number instead (see Call forwarding setup).Before you start
  • The fixed public IPv4 address your PBX uses on the Internet.
  • WBM access with the Expert profile.
  • A free ITSP slot (up to 8 ITSPs can be active) and one free ITSP channel license per simultaneous call to the assistant.
  • On X5/X8: every call from a digital or ISDN phone, or an ISDN line, to the trunk uses one DSP channel. The mainboard has up to 8; an OCCB1 or OCCB3 board adds more. G.729 and encryption use extra DSP channels, so use G.711.
On the platform
  1. Open Settings → Numbers → Add a number → Add SIP integration. Choose the EU SIP region if your PBX runs in Europe, and copy the SIP host from the SIP URI, without the sip: prefix and without ;transport=tcp.
  2. Set Trunk type to Phone number (DID) when OpenScape Business dials a full number, and enter that exact number, for example +497121123456. The trunk must match the user-part of the INVITE exactly. The platform does not add a +. If a trace shows a national user such as 07121123456, store those digits instead. Use a number from your own number block.
  3. Set Inbound authentication to Provider source IPs and enter your PBX’s public IP as /32, for example 203.0.113.10/32. Never enter a wider range.
  4. Enter your PBX’s public host name or IP as Termination address. This is where the assistant sends a new call when it dials out or transfers. Use the PBX’s public gateway, not a website and not the PBX’s private LAN address. There is no registration and no username or password.
  5. Save and assign an assistant to the number.
In OpenScape BusinessField names below follow the English WBM; the German WBM uses translated labels.
  1. Go to Setup → Wizards → Central Telephony and click Edit next to Internet Telephony. Clear No call via Internet, then click Add to create a new ITSP.
  2. Leave Base Template empty, set Provider Name to Famulor (10 characters at most) and activate Enable Provider.
  3. Enter the platform SIP host as Domain Name and as Provider Proxy, port 5060. Leave Use Registrar, Use Outbound Proxy, Use Inbound Proxy and Use STUN off.
  4. Click OK & Next, then Add to create an account. Enter any name as Internet Telephony Station, for example the DID. Authorization name and Password stay grayed out; that’s expected without registration. Under call number assignment, choose Use public number (DID).
  5. Finish the wizard. The status shows the ITSP as set up but not registered (yellow). That’s expected, not a fault.
  6. In Expert Mode → Telephony → Voice Gateway → Internet Telephony Service Provider, open the new ITSP and set Transport protocol to TCP, Transport security to traditional (UDP or TCP) and Media security to RTP only.
  7. On the Edit STUN Configuration tab, set STUN Mode to Use static IP and enter your public IP and Public SIP Port. Your router must forward the PBX’s SIP and RTP ports, as for any other ITSP.
  8. In Expert Mode → Telephony → Voice Gateway → Codec Parameters, give G.711 A-law priority 1, set the frame size to 20 ms and enable DTMF tones according to RFC2833. On X5/X8, consider Use G.711 only to save DSP channels; that change restarts the system.
  9. So the assistant sees the real caller, not your PBX number, open Show Extended SIP Provider Data on the ITSP: set CLIP outgoing in From header – user part to Call number and enable Diversion: From contains original Calling Party Number. Mitel reserves these fields for authorized service personnel, so ask your Mitel partner to make this change.
  10. In Expert Mode → Telephony → LCR, create the route to the assistant:
    • Dial rule: a new rule with the dial rule format D followed by the DID digits with country code and without +, for example D497121123456, when the trunk is stored as +497121123456. The platform does not add a +. A national number such as 07121123456 doesn’t match that trunk. If OpenScape Business puts a national user in the INVITE, store that exact user on the trunk instead.
    • Route table: a free table (16 or higher) with the Famulor ITSP route and the new dial rule.
    • Dial plan: a free entry (36 or higher) whose Dialed digits match what your users or rules dial for the assistant, for example 0C07121-123456, pointing at the new route table. The more specific entry wins over the general 0CZ entry.
  11. Send calls to the assistant by dialing that number from OpenScape Business: for example as call forwarding of a group, as night service, or as an option in an auto attendant.
Without a fixed public IP, inbound authentication by source IP can’t work, and OpenScape Business sends no password without registration. Don’t open the trunk to wider IP ranges to make it work; forward the calls to a platform phone number instead.
For encrypted calls, activate Secure Trunk in the wizard, set Transport security to secure (tls), Media security to SDES only and the port to 5061, and enable Secure trunking on the platform trunk. Start with TCP and switch to TLS only once calls work. If the PBX rejects the TLS connection, import the CA certificate under Security → Signaling and Payload Encryption (SPE) → SPE CA Certificate(s).Calls from the assistant back into OpenScape Business are a new INVITE to the termination address on TCP port 5060. The PBX must accept TCP 5060, and UDP for the audio, from the outbound source addresses. Set Outbound region to Germany or Automatic. Audio ports change on every call.The number being called is in the request address, with a plus and country code. The sender is the number stored on the trunk. OpenScape Business should place that call out through your existing telephone provider, the same way a phone on the PBX calls out. If that provider rejects the short trunk number as the displayed caller, map it on the PBX to the public number of that extension before the call leaves. The PBX’s answer must advertise a public audio address. A private LAN address in that answer means the caller hears silence. Leave the existing provider connection, including a carrier on a different port, and Diversion: From contains original Calling Party Number as they are.

Validate the setup

Call the DID from an external phone and confirm a new inbound record in History, the assigned assistant, and two-way audio. For platforms with a distinct outbound leg (3CX, Asterisk, Genesys Cloud), place one outbound test call too — an inbound success doesn’t confirm outbound is configured correctly, and vice versa. See also SIP provider guides, BYO SIP trunk, and Other and custom SIP providers. Sources: 3CX SIP trunks, Asterisk documentation, Starface knowledge base, Wildix trunk settings, Mitel OpenScape Business V4 Administrator Documentation, Genesys BYOC Cloud, Five9 documentation, Aircall support. Accessed 22 August 2026; the Wildix guide on 15 October 2026; the Mitel guide on 27 October 2026. Outbound source addresses are maintained on the BYO SIP trunk page and were confirmed on 29 October 2026.