Axivox/Compatible phones
Phones

The phone configures itself, you don't configure it

You declare the device's MAC address and attach it to an extension. The first time it starts up, it fetches its configuration and sets itself up: its number, its keys, its directory. That's true for Snom and Yealink. Any other SIP-standard phone is registered with credentials.

Provisioning

Unbox it, plug it in, that's it

A new phone knows nothing about you. Zero-touch provisioning handles that moment: the device announces itself, we recognise it by its MAC address, and it receives the configuration of the extension you attached it to.

  • Nothing to type on the device's keypad
  • A replaced phone is picked up the same way
  • Keys and directory arrive with the rest
Le même poste sur un téléphone de bureau, dans un navigateur et sur un ordinateur, avec un seul numéro et un audio chiffré.Your extension 204encrypted audio204Desk phoneSnom, Yealink204Browsernothing to installSoftphoneWindows and macOSOne number, one accountand the same directory everywhereopus · G722
How it works

Four steps, and none of them on the phone's keypad

You declare the MAC address

It's printed underneath the device and on its box. It's the only thing we need to recognise it.

You attach it to an extension

The extension already carries its internal number, voicemail, keys and permissions. The phone inherits all of it.

You plug it in

The first time it starts up, it fetches its configuration and sets itself up. Nobody types a server address on site.

You change whatever you want, afterwards

A key to revisit, an extension to reassign: the change goes out to the device with nobody having to travel.

A phone's record: its model, its MAC address, the extension it's attached to.
A phone's record: its model, its MAC address, the extension it's attached to.
The connection

Encrypted on both sides, and no TFTP

An extension's configuration contains its SIP credentials: it has no business travelling in the clear over a network. Many installations still use TFTP, a protocol with no encryption and no authentication. We don't use it.

  • The device and the server each present a certificate
  • The configuration never travels in the clear
  • A device we don't recognise gets nothing
And other devices

The SIP standard, whatever the brand

We follow the standard, with no proprietary extension: whatever speaks SIP registers with us.

The two provisioned brands

Snom and Yealink configure themselves.

  • Registered by MAC address, nothing to do on site
  • Configuration received on first start-up
  • Keys and directory pushed along with the rest

Everything else

Another phone, a gateway, a SIP application.

  • You create the extension, the SIP tab carries its credentials
  • You enter them into the device, whatever the brand
  • Nothing is reserved for one particular brand

No device at all: the same extension runs in a browser, on Windows and on macOS.

See the softphone
An extension's keys: each one carries a colleague, a number or a function.
An extension's keys: each one carries a colleague, a number or a function.
Keys

Set from the record, not on the keypad

Supervision keys are set from the extension's record. You then see who's free, who's ringing and who's on a call, and one press calls the colleague or picks up their call.

  • The change goes out to the device, with no site visit
  • The same keys exist in the softphone
  • A known contact's name pops up at the ring
Quote

Your current devices, and the ones missing

Give us the brand and model of what you already have. We'll tell you what provisions itself, what needs to be registered by hand, and what's better replaced.

Get a priced quote now

Five more fields, and we'll reply with an amount instead of a question.

Your traffic
Your numbers
Your destinations
Billing address optional

Response within one business day. Without the price fields, we'll call you back to talk it through.