Poly OBi Voice Adapter Setup Guide

← Hardware & Devices

Poly OBi (formerly Obihai) voice adapters connect ordinary analogue phones and fax machines to SIPSTACK Nova PBX. SIPSTACK can generate the adapter’s configuration: you register the adapter in Switchboard, point it at your organization’s provisioning URL, and each phone port registers as an extension.

Every OBi model is marked Beta in the Switchboard model picker (listed under Poly OBi) and on this page.

Supported Models

Model	Phone ports	Status
OBi200	1	Beta
OBi202	2	Beta (discontinued by vendor)
OBi300	1	Beta
OBi302	2	Beta
OBi504vs	4	Beta
OBi508vs	8	Beta

OBi IP desk phones (OBi1022, OBi1032, OBi1062) are not in the Nova PBX catalog and are not auto-configured.

Before You Start: Your Provisioning URL and PIN

Every Nova PBX organization has one provisioning URL and one provisioning PIN that all of its devices share:

https://<slug>:<PIN>@cfg.sipstack.com/<slug>/

<slug> is your tenant slug (also the username).
<PIN> is your provisioning PIN — 8 digits for organizations set up since September 2026.

Both live in Switchboard → Nova PBX → System → PBX Settings → Provisioning Access. The URL is shown with the PIN masked; the Regenerate PIN button reveals a new PIN, once. The PIN is shown once when generated. Lost it? Rotate it in Provisioning Access — devices keep working on the old PIN for 24 hours.

There is no per-device password and nothing to copy from an individual device’s page: the same URL provisions every device in your organization.

Step 1: Register the Adapter in Switchboard

Log in to Switchboard.
Go to Nova PBX → Devices → Devices and click Register device. If the page asks you to generate your provisioning PIN first, do that in PBX Settings → Provisioning Access — devices cannot be registered until the PIN has been generated.
Enter the adapter’s MAC address from the label on its underside.
Pick Poly OBi and the model (it shows a Beta badge), then click Register device.
Assign one extension per phone port: line 1 rings and dials from PHONE 1, line 2 from PHONE 2, and so on.
Click Apply Changes. Applying publishes the adapter’s configuration to the provisioning server — until you apply, the server has nothing to hand the adapter.

Step 2: Set the ConfigURL

OBi adapters fetch their configuration from the URL in their ConfigURL field. The organization URL above ends at your folder; the adapter also needs the file name, so add $MAC.xml to the end. The adapter replaces $MAC with its own MAC address.

https://<slug>:<PIN>@cfg.sipstack.com/<slug>/$MAC.xml

Find the adapter’s IP address: pick up a phone on PHONE 1, dial ***1 and listen.
Open http://{adapter-ip} in a browser and sign in as admin.
Go to System Management → Auto Provisioning → ITSP Provisioning.
Set ConfigURL to the value above, with your slug and PIN filled in, and click Submit.
Reboot the adapter. It downloads its configuration and each assigned port registers.

Your DHCP server can also hand out the provisioning URL (option 160, or option 66 on some devices), but that value has no file name on the end, so setting the ConfigURL by hand as above is more reliable for OBi adapters.

SIPSTACK never writes the ConfigURL back into the configuration it sends, so the URL you entered (with your PIN) stays on the adapter.

What SIPSTACK Configures

One SIP account per assigned line, each with the extension’s credentials and the Nova SIP server. Each phone port is tied to its own account: calls to that extension ring that port, and calls from that port go out on it.
Dial plan. A digit map that lets every Nova star code through, including paging (*80 + page group), intercom (*81 + extension), park retrieve (*85), directed pickup (*87 + extension), voicemail (*97, *98), 3- and 4-digit extensions, North American numbers, 011 international, and 911, 988 and 112. Each of 911, 988 and 112 is sent the moment you finish dialling it.
Star codes go to Nova. The adapter’s own star-code features are turned off, so codes like *72 and *78 reach Nova instead of being handled inside the adapter.
Message waiting. Each account subscribes for voicemail notifications.
Fax (T.38). T.38 fax relay is turned on in the adapter’s codec profile. T.38 is available on the OBi202, OBi302 and later models. Plug the fax machine into a phone port that has its own extension.
NTP server, when one is set.
Web passwords, when your organization has them set.
Resync. The adapter checks for new configuration every hour. SIPSTACK also sends OBi adapters a “reprovision” signal when you click Reprovision on the device page. Support for this brand is in Beta, so the signal is not yet confirmed on every model: if the device has not picked up your change after a minute, reboot it.

What SIPSTACK Does Not Configure

The ConfigURL (see above).
Keys. An adapter has none; any key you add in Switchboard is skipped with a warning.
Time zone, daylight-saving rule and codecs. The adapter keeps its own values.
OBiTALK service. SIPSTACK does not use or change the OBiTALK account on the adapter.
Firmware. SIPSTACK does not update OBi firmware unless you pin a firmware version for the model in Switchboard, and only where its firmware catalog lists one.

Factory Reset

From a phone on PHONE 1, dial ***8, then press 1 to confirm. You can also hold the adapter’s RESET button for about 10 seconds. After a reset, enter the ConfigURL again.

Troubleshooting

Symptom	Likely cause	Fix
Phone port has no dial tone from Nova	The adapter has no configuration yet: MAC not registered, no extension on that line, or changes not applied	Check the MAC in Nova PBX → Devices, assign an extension to the port’s line, click Apply Changes, then reboot the adapter
Provisioning fails with `404`	The ConfigURL has no file name, or the MAC registered in Switchboard is wrong	End the ConfigURL with `$MAC.xml`; compare the MAC with the adapter’s label
Provisioning fails with `401`	Wrong slug or PIN in the ConfigURL	Compare with PBX Settings → Provisioning Access; after a rotation the previous PIN stops working 24 hours later
Provisioning fails for every device at once	100 failed attempts within an hour paused provisioning for your organization	Correct the PIN, wait for the hour to pass, then reboot one device before the rest
Faxes fail	The fax machine shares a port with a phone, or the model has no T.38 support	Give the fax machine its own port and extension; use an OBi202, OBi302 or later model
Registration fails, then the adapter can’t reach SIPSTACK at all for a while	The adapter is registering to the wrong SIP server or domain, often a value left over from a previous provider. Repeated failed registrations from your network can trigger a temporary IP block	The SIP server must be your organization’s SIP server exactly as shown on the extension’s SIP Auth tab. Factory reset the adapter so the provisioned value is used, wait for the block to clear, then try again. Contact support if it continues

For additional support, contact SIPSTACK at https://www.sipstack.com/contact.