Your endpoint
A phone, softphone or voice application starts a call.
Make sense of business voice. Clear explanations of numbers, SIP, call quality and AI — from the first connection to the next stage of growth.
VoIP carries voice over an IP network. A business phone, softphone or voice platform turns audio into digital data and exchanges it with another endpoint. When a call reaches a traditional telephone number, a provider connects the IP side to the relevant telephone network.
PUT IT INTO PRACTICEBefore choosing a service, map who calls whom: internal teams, incoming customers or outbound destinations.
SIP establishes, changes and ends communication sessions. RTP carries real-time media such as voice. A call can connect successfully while its audio fails, because signalling and media can follow different network paths.
PUT IT INTO PRACTICEWhen troubleshooting, separate “the call does not connect” from “the call connects but has no audio”.
A PBX handles your extensions, queues and call rules. A SIP trunk provides connectivity between your voice system and a provider. A DID is an incoming telephone number. These are separate building blocks, even when purchased together.
PUT IT INTO PRACTICEStart with your call-handling platform, then define connectivity, numbers and capacity.
Direct Inward Dialling lets an external caller reach a number that your provider routes to your business phone system. Your platform then decides whether to ring an agent, play an IVR or send the call to a queue. One number does not automatically mean one simultaneous call.
PUT IT INTO PRACTICEConfirm number availability, inbound capacity and the intended call destination separately.
Number types differ in reach, caller charging and eligibility. A local number is associated with a geographic area; national and toll-free ranges follow country-specific rules. Availability, registration documents and inbound reachability need checking before a rollout.
PUT IT INTO PRACTICETell your provider where callers are located and which type of number they should dial.
Porting transfers a number between providers where the number range and local process allow it. Eligibility, account details and supporting documents must be checked first. Plan routing and acceptance tests around the confirmed transfer date.
PUT IT INTO PRACTICEKeep the existing service active until the transfer and incoming call tests are complete.
Concurrent call capacity describes how many calls can be active at once. Calls per second describes the rate of new call attempts. A short outbound campaign can need a high attempt rate even when average conversation length is low.
PUT IT INTO PRACTICEEstimate both peak active calls and peak new attempts; agree limits before launch.
Inbound routing brings calls from your numbers into your platform. Outbound routing sends your platform’s calls towards destination networks. Each direction needs its own routing rules, number formatting and permissions.
PUT IT INTO PRACTICETest both directions with representative numbers and verify what happens when a destination is unavailable.
SIP responses show progress or an outcome. For example, 180 indicates ringing, 200 indicates success and 486 means the endpoint reports busy. A response is a diagnostic clue, not always a complete explanation of the underlying problem.
PUT IT INTO PRACTICERecord the timestamp, Call-ID and response sequence when asking for technical help.
Latency is the time audio takes to travel. Jitter is variation in packet arrival timing. Packet loss means some media packets never arrive. These problems can create awkward pauses, uneven playback or gaps in speech.
PUT IT INTO PRACTICECompare several calls and check the local network, endpoint and media path before changing routes.
A codec encodes and decodes audio. Codec choice affects bandwidth and audio characteristics, while compatibility determines what endpoints can negotiate. Transcoding adds processing and can affect the result.
PUT IT INTO PRACTICEAgree supported codecs across the PBX, provider and destination; test with real speech.
ASR compares answered calls with call attempts. ACD is the average duration of answered calls. PDD measures the delay after dialling before call progress is heard, with the exact event depending on the reporting system. None of these alone proves that audio is good.
PUT IT INTO PRACTICECompare like-for-like destinations and traffic, and combine statistics with sample calls and user feedback.
Include the affected direction, destination, timestamp with timezone, Call-ID and what each party experienced. Where permitted, add a relevant SIP trace or CDR excerpt. Remove unrelated personal information and credentials.
PUT IT INTO PRACTICEA precise example is more actionable than “all calls are bad”. Include one working comparison if available.
Restrict allowed destinations and access, protect credentials, set appropriate usage limits and review unusual traffic. A sudden rise in attempts or unexpected destinations deserves investigation. No single setting removes every risk.
PUT IT INTO PRACTICEDefine who receives alerts and who can suspend affected access before an incident occurs.
A Call Detail Record contains metadata about a call, such as numbers, timestamps, duration and outcome. The available fields and billing interpretation depend on the platform. A CDR is not the call recording.
PUT IT INTO PRACTICECheck timezone, billed duration and rounding rules before comparing records or reconciling charges.
A voice agent combines speech recognition, conversation logic and speech generation with a telephony connection. The phone number or outbound route connects callers; the AI application decides what to say and when to transfer the conversation.
PUT IT INTO PRACTICEConfirm SIP compatibility, transfer behaviour and human fallback with every platform involved.
A voice conversation includes network travel, speech processing, model response and audio playback. Delays can accumulate across that chain. Measure the whole exchange, including interruptions and transfers, rather than judging one component alone.
PUT IT INTO PRACTICETest realistic conversations and recovery paths before increasing traffic.
A phone number that receives voice is not necessarily enabled for SMS. Messaging support depends on the number type, destination, provider and use case. Sender registration and permitted traffic can also vary.
PUT IT INTO PRACTICEConfirm voice and messaging capabilities separately before using a number in a customer journey.
A phone, softphone or voice application starts a call.
The PBX or application applies routing and call rules.
The provider routes the call towards the destination network.
The receiving endpoint answers and the conversation begins.
Tell us about your platform, destinations and expected traffic. We’ll help turn your requirements into a practical connectivity discussion.