Register multiple identities on your SIP desktop phone
Published on:
February 11, 2020
To register multiple identities on a SIP desktop phone, start by resetting the phone to factory defaults and locating its MAC address. After logging in to the Vodia PBX, add the MAC address to the relevant extensions. Use MAC-based provisioning to enable the phone to register correctly, ensuring it can handle multiple identities. When configuring outbound calls, assign specific caller IDs (ANI) to each extension, which allows agents to show the appropriate company number when making calls. Additionally, set up hunt groups to manage inbound calls, enabling agents to identify calls by company name and enhancing efficiency in multi-company environments.
Every company has agents that pickup multiple calls; In some scenarios an agent will answer multiple calls for a slew of companies they manage. In just a few steps we will show you how to program the identities of multiple extensions on a desktop phone, how to route inbound calls to multiple call agents and how to make outbound calls with different caller IDs.
Overview
Register multiple identities
Program multiple identities on your desktop phones
Program inbound calls
Show different CID when making an outbound call
Register multiple identities
To register multiple identities on your phone, you will need to reset the phone to factory default. Next, you will need to find out the IP address of the phone and log in to the unit with default credentials.
Next you will need to locate the MAC address of the unit.
Factory reset the unit
Find the MAC address of the unit
Check if the desktop phone supports multiple identities
Adding the MAC address
You will need to add the MAC address of the phone to the extensions in order to register multiple identities.
Log in to your Vodia PBX
Navigate to All accounts and choose extensions
Choose multiple extensions you would like to register and append the MAC address to each extension.
Navigate to "Provisioning" and add the MAC address to each extension under "Bind to MAC address"
Open MAC based provisioning
Open MAC-based provisioning on the Vodia PBX is based on a timer. It allows the phone to register based on a timer; if not set, the Vodia PBX will reject the request for provisioning.
Navigate to extensions
Tick box, the extensions you've added the MAC address to
Scroll down to "Please select an action" and choose "Open account for MAC-based provisioning"
Activate Open MAC based provisioning
Manual provisioning
For this tutorial, we are logging in to the phone and manually adding the Vodia PBX URL:
The IP address of the Vodia PBX
FQDN
Option 66
RPS
We are using a Yealink T29G, but the procedure is the same for all the phones that support multiple identities.
Log in to your Desktop phone by typing its IP address
Into the URL of the PBX; if it's local you can also enter http://IP_of_the_PBX
Save and press the auto-provision now button
Success!
You should now see all registered identities on the phone.
Spicing things up!
Some deployments are unique; for example, let say the customer has the following criteria:
They need to use multiple CID when making outbound calls, which will show the companie's number
They need to know how to answer the call when it comes into the queue
Setting up the company name and assigning CID
Since we have registered multiple identities on the desktop phone, all we need to do is change the name of the extensions to a company name and the ANI to each extension:
Navigate to the extension and choose the extension registered and change the name to the respected company name.
Under the extension Outbound number (ANI), add the companie's phone number (you can repeat the process for the other extensions).
Note: Since the phone is provisioned to the Vodia PBX, the desktop phone will auto update with the new name.
Outbound Call with ANI
As you can see below, the user made an outbound call with the company name "Home Depot" with caller ID 800-666-9988.
Inbound calls with company from header
Now that we have the name and CID setup, let's create a hunt group account:
Navigate to accounts and choose hunt groups
Assign an account number, a DID and the name of the group to one of the company names
Note: When you add a DID to an account, the format is the following: extension number space DID, example 90 1-800-666-9988
Stage 1-3 can be a specific extension - final stage can go to voice mail using the prefix 8 and the extension number.
Scroll down below to Behavior and choose the From-header; here you can choose Group name (calling number) or calling name. This will make it easier for the agent to answer the incoming call with the respective company name.
Repeat this method for each hunt group and add the extension with its respective company name.
Inbound Routing
How do we route inbound calls to their respective DID? Well that's easy. Navigate to your SIP trunk and choose the following feature:
Navigate to Routing /Rediection and choose "Send calls to destination in the Request -URI"
When an inbound call comes in to the PBX it will look at the Request -URI and match the incoming DID to the hunt group account.
Skills-based routing in V70 helps ensure incoming calls are matched with the most qualified available agents based on defined skills, language, and expertise. By combining IVR input with intelligent call distribution, organizations can reduce unnecessary transfers, improve first-contact resolution, and shorten handling time. With V70, skills can be defined directly within the PBX, allowing teams to set thresholds, prioritize expertise, and control how calls are routed across departments, queues, and different operational environments.
PBX snapshots in V70 provide a reliable way to capture system state before changes are applied, enabling fast recovery, controlled rollback, and more predictable system management when updating configurations, testing call flows, or operating across multiple tenants. By preserving a point-in-time version of the system, administrators can reduce the risk of disruption, restore services quickly when issues arise, and maintain stability while making ongoing changes in complex communication environments.
V70 introduces emergency alerts and notifications designed to ensure critical events are not missed and responses happen immediately. Alerts can be triggered directly by users, delivered across multiple channels including phones, email, mobile apps, and SMS, and can automatically initiate calls to predefined numbers. Administrators have full control over how alerts are configured, enabling consistent, reliable handling of incidents across real-world, multi-tenant environments.
.svg)
