Skip to main content
DialNexa phone numbers route live traffic to published agent versions. A number can be bought through the Plivo purchase flow, linked through SIP trunking, assigned to inbound and outbound agents, and used for one-off outbound calls. DialNexa Phone Numbers table showing active numbers, provider, assigned agent context, call type, and outbound call action. DialNexa Phone Numbers page showing active Plivo numbers, renewal date, assigned agent, inbound and outbound call type, and outbound call action. DialNexa Buy Phone Number modal showing Plivo provider, country, region, available numbers, monthly rate, and buy action. DialNexa SIP trunking modal showing fields for linking an existing number through SIP.
A published agent without a route is a script waiting by the phone with no phone.

Number Types In The Dashboard

Number pathUse it whenWhat to test
Plivo number purchaseYou want to buy and manage a number inside DialNexa.Compliance readiness, active status, inbound routing, outbound routing, and recording quality.
SIP trunk linked numberYou bring your own telephony path and want DialNexa to connect to it.Termination URI, optional credentials, caller ID, inbound route, outbound route, and transfer handling.
Existing workspace numberYou already have a number and need to review or change assignments.Status, provider, rental state, SIP state, and agent version mapping.

Phone Number Fields Users Should Recognize

FieldMeaning
StatusWhether the number is pending, active, or unavailable for production routing.
Rental statusWhether the number is active, expired, or available for reassignment.
ProviderThe telephony path. SIP trunk numbers display as SIP trunk.
Country codeStored separately from the local number and used for formatted dialing.
SIP trunk enabledWhether the number is linked to SIP trunk details.
Inbound agent versionThe published agent version that answers incoming calls to the number.
Outbound agent versionThe published agent version used when this number places outbound calls.

Inbound And Outbound Assignments Are Separate

The Phone Numbers table shows assigned agent context and call direction for each number. Use the agent or routing configuration flow for version changes. The table row itself is not where you rename agents or edit published versions.
AssignmentWhat it controlsCommon mistake
Inbound agentWhich agent answers when a caller dials the number.Updating outbound assignment and expecting inbound behavior to change.
Outbound agentWhich agent speaks when the number starts a single call, batch call, or workflow call.Starting outbound traffic before assigning an outbound published version.

Telephony Pricing Behavior

RouteHow to think about cost
Plivo-style routingDestination matching is based on the called number, using the longest matching prefix for country and network group.
SIP trunkingDialNexa shows a flat SIP trunking rate when configured, such as ₹x.xx/min, before saving the trunk link.
Web callBrowser audio avoids carrier routing, but call behavior should still be reviewed in Call History.
Source number country does not decide outbound destination pricing. The called number does.

Outbound Destination Validation

Single outbound calls and batch calls validate the destination before creating call records. The checks happen in this order:
  1. The destination must be present, parseable, and possible as an international phone number.
  2. If KYC is not verified, the owner can only call the registered verification number.
  3. For non-SIP routes, the destination country must be enabled in Workspace Settings > Telephony Config.
  4. If the enabled network group has prefixes, the destination number must start with one of those prefixes.
  5. SIP trunk numbers and enabled SIP/BYOC workspace config bypass destination country rules.
When validation fails, the dashboard shows the API error message. Batch CSV uploads can group many failed rows by the same validation reason so users can fix the file faster.

Prepare A Number For Production

1

Confirm active state

Pending or expired numbers should not be used for critical traffic.
2

Check readiness

Complete KYC or regional requirements where the dashboard asks for them.
3

Assign published versions

Select the inbound and outbound agent versions that should own live calls.
4

Review Telephony Config

Confirm the destination countries and network groups you plan to call are enabled for this workspace.
5

Run one inbound test

Call the number and confirm the correct agent answers.
6

Run one outbound test

Start a call from the number and review status, recording, transcript, and extracted fields.

Common Phone Number Mistakes

Check direction. Inbound and outbound assignments are independent.
Live routes should use published versions. Publish the version before assigning it.
Test the exact SIP trunk path. Your carrier, trunk configuration, and caller ID behavior can change audio and routing.
Confirm whether the number is active, default, or used by campaigns before deleting it.

SIP Trunking

Link a number to SIP trunking.

Inbound Calls

Route incoming callers.

Outbound Calls

Start individual outbound calls.

Audio Quality

Understand phone audio and transcription.