Read a system diagram
Endpoint: a phone or application participating in a call. PBX: the organization's call-control system. Registrar: a SIP service that maintains contact bindings. Proxy: a SIP intermediary that routes requests. Carrier: the service responsible for the agreed connection to outside telephone destinations.
These are roles, not necessarily separate boxes. A deployment can combine several roles on one system or distribute them across multiple services. Draw responsibilities explicitly when two suppliers share the call path.
Read a carrier proposal
DID: an outside telephone number delivered into the system. Extension: an internal destination or identity. Concurrent calls: simultaneous activity supported under the service and platform limits. SIP trunk: the interconnection between a PBX and a carrier. Porting: moving number service between providers through their transfer process.
Seat, line and unlimited are commercial terms whose exact meaning depends on the proposal. Ask for definitions, included destinations, fair-use conditions and whether forwarded calls consume separate capacity.
Read a packet trace
SIP: signaling used to establish and manage sessions. SDP: a session description carrying details such as media addresses and formats. RTP: media transport with sequence and timing information. RTCP: related reporting used to describe reception and other session information. Codec: the encoding of audio samples.
A response code belongs to a particular request and call leg. A 200 response to REGISTER is not proof that an INVITE succeeded. A successful INVITE does not prove that RTP reached both speakers.
Read an operations note
NAT changes network addressing across a boundary. A firewall permits or blocks traffic according to policy. QoS applies handling priorities; it does not create missing link capacity. Jitter is variation in packet arrival timing. A jitter buffer trades added delay against uneven arrival. Packet loss means expected packets did not arrive at the measurement point.
When reporting a problem, pair the term with evidence: which direction, which endpoint, what time and what observation. Precise incident language reduces unnecessary configuration changes.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.