CLI, nCLI and TDM: Choosing SIPEASY Outbound Routes

The route discussion becomes clearer when you start with the call your business needs to make. Where is it going? Does caller-ID presentation matter? What volume will the system send during busy periods? SIPEASY focuses on outgoing traffic through CLI, nCLI and TDM route offerings.

Define caller-ID requirements first

For a CLI route discussion, describe the caller identity you need to present and the destination networks involved. Use an identity you are authorized to use. Include receiving-side caller-ID behavior in your test criteria and retain the observed result with the call record.

For an nCLI route discussion, state whether your workflow depends on presenting the original caller identity. Confirm the actual presentation behavior for the destination during testing. The commercial route name is the start of the discussion; the agreed terms and observed calls are what the team will operate against.

Discuss TDM for the specific destination

TDM is one of SIPEASY's priority route offerings. When requesting it, include the destination network, expected volume and calling workflow. Confirm the available option, current tariff and test requirements for that destination with the team.

Keep route selection and evaluation together. Inspect call setup, two-way audio, relevant caller-ID behavior and the resulting charge under the conditions your business expects to use.

Create a short route brief

• Destinations: countries and networks where known.
• Traffic: expected volume and busiest time windows.
• Calling setup: SIP device or PBX and its version.
• Identity: caller-ID requirements for the workflow.
• Capacity: expected simultaneous calls and call-attempt rate.
• Test criteria: the observations needed before moving traffic.

Keep distinct traffic profiles separate in the brief. A reseller can prepare one profile per customer use case; an internal team can organize it by destination group or calling workflow.

Compare routes with the same test method

Choose representative recipients who expect the call. Use a consistent device and local connection. Note the timestamp, route selection and destination for each test. Check both audio directions and any workflow-specific signaling.

Inspect call records and charges, then repeat across the time periods that matter to the business. Share a small set of affected and successful examples when support needs to investigate a difference.

Keep PBX features and route requirements distinct

SIPEASY offers one-device pay-as-you-go access with a $0 monthly package fee. Paid PBX packages add devices, recording and supervision features: Minimum at $50/month, Standard at $100/month and Pro at $250/month. Their device allowances are three, five and up to twenty respectively.

Try Standard for one month free. Sign in to your SIPEASY panel and activate the offer yourself using its dedicated button. Standard normally costs $100/month. Outgoing calls remain chargeable at the applicable tariff. See current packages and call rates.

Choose the route from the calling requirements and the package from the team's device and feature needs. Discuss busy-hour capacity separately so the setup is sized around the real workload.

Start the conversation with SIPEASY

Registration and outbound route access are KYC-free. DID numbers are available by special order with KYC when needed for the project.

Send your route brief to SIPEASY or create an account. Use the first controlled test to turn the requirements into a practical outbound setup.