Dashboard Join Discord Back to overview

Setup docs

Configure your Action URL.

Every hardware phone fires a single HTTP request to its "Action URL" when it rings. Point that request at Phonetix and each ring becomes a direct message.

Before you start: run /new in Discord first. It registers you on the FREE tier and creates your first line automatically, giving you a working URL for each system below — copy those instead of typing anything by hand. Got more than one phone? Run /line add name:<name> for each additional line — every line gets its own token and its own set of URLs.

General setup.

The same three steps apply to every brand. Brand-specific menu paths are below.

  1. Get your token. Run /new in Discord — it creates your account and your first line, and hands you one URL per supported system. Each phone line has its own token; add more with /line add name:<name>.
  2. Find the Action URL field. On a hardware phone's web admin interface, locate the setting for outbound event notifications — usually filed under Maintenance, Features, or Advanced. On Asterisk, this is a dialplan line instead — see below.
  3. Paste and save. Assign your Phonetix URL to the ring / incoming-call event and save. Apply or reboot if your firmware requires it.

By brand.

Menu labels vary by model and firmware version. If a name below doesn't match exactly, search your phone's admin guide for "Action URL" or "Event URL."

Grandstream

Caller ID source: $remote

Web UI → Maintenance → Action URL → assign the URL to the Ring event.

https://phonetix.cc/<line-token>/grandstream?caller=$remote

Yealink

Caller ID source: $remote

Web UI → Features → Action URL → assign to Incoming Call.

https://phonetix.cc/<line-token>/yealink?caller=$remote

Fanvil

Caller ID source: $remote_number

Web UI → Features → Action URL → assign to the Incoming Call field.

https://phonetix.cc/<line-token>/fanvil?caller=$remote_number

Snom

Caller ID source: $remote

Web UI → Advanced → Action URL Settings → action_incoming_call.

https://phonetix.cc/<line-token>/snom?caller=$remote

Poly / Polycom

Caller ID source: CallingPartyDirNum (in the POST body — not a URL macro)

Poly phones work differently from every other brand here: instead of a GET request with a caller-ID macro in the URL, Poly sends an HTTP POST with an XML body on Telephony Event Notification. No macro or query string needed — just paste the bare URL below into that setting (usually under Settings → provisioning parameters, e.g. apps.telNotification.URL / apps.telNotification.callStateChange.enabled=1 depending on firmware).

https://phonetix.cc/<line-token>/poly

Asterisk

Caller ID source: ${CALLERID(num)}

Add a line to your dialplan (extensions.conf) that fires before the Dial() step:

exten => 100,1,TrySystem(curl -s "https://phonetix.cc/<line-token>/asterisk?caller=${CALLERID(num)}")
same => n,Dial(PJSIP/100)

Multiple phones?

Every phone line gets its own token and its own URLs, so alerts always tell you which line rang.

  1. /line add name:<name> — creates a new line (e.g. "Front Desk") and returns its Action URLs.
  2. /line list — shows every line on your account.
  3. /line remove name:<name> — deletes a line. Its token stops working immediately.

Want PRO?

PRO (5,000 calls/day) is $5/month and funds ongoing development.

  1. Head to the dashboard. Log in with Discord and hit "Upgrade to PRO" under Your Plan.
  2. Subscribe via Stripe. $5/month, cancel anytime from the same dashboard.

Not receiving a DM?

Two things stop delivery, and both are on the Discord side, not the phone side:

  1. No shared server. The bot can only DM a Discord account that shares at least one server with it.
  2. DMs closed. Check Discord's Privacy Settings and confirm direct messages from server members are allowed.