VoIP troubleshooting

Capture a reproducible incident

Write down the timestamp and timezone, calling and called identities, direction, devices and exact symptom. Identify whether the problem affects one endpoint, one site, one destination or every call. Those boundaries guide the next check.

Choose the right branch

A phone that cannot register needs an identity and reachability investigation. A phone that registers but cannot call needs request, permission and routing checks. A call that connects with missing or distorted sound needs a media-path investigation. A call reaching the wrong person needs destination and schedule review.

Start with a known-working internal call if possible, then change one variable: endpoint, site or destination. Do not change NAT, codecs and dialplan simultaneously. You need to know which change affected the result.

Prove electrical loss before treating a phone as rebooting

For a phone that repeatedly boots, powers briefly or disappears when PoE load changes, follow the IP-phone power-cycle diagnostic. It distinguishes phone uptime from link, VLAN, DHCP, provisioning and SIP recovery, then correlates the exact switch port with detection, classification, allocation, draw, budget and controller faults before any broad power change.

Resolve endpoint matching before inbound routing

For an Asterisk warning that an inbound PJSIP request could not be identified, the endpoint-matching diagnosis starts with one rejected message and the loaded identifier order. It keeps identification separate from registration, digest authentication, DID routing and media, and requires a negative test before accepting a broader match.

Prove ARI application ownership before debugging call logic

When a channel reaches Stasis() and immediately returns, the ARI Stasis registration guide separates HTTP reachability, ARI authorization, WebSocket upgrade, exact application registration, STASISSTATUS and application behavior. It does not treat a running process or successful REST request as proof that the named application owns the channel.

Trace missing or duplicate ARI events through the control plane

When ARI events disappear, repeat or move to another client, use the event-delivery diagnostic. It separates application registration, resource scope, subscribeAll, event filters, one active WebSocket owner, raw delivery, client parsing and downstream idempotency.

Trace an ARI dynamic object through Sorcery

When a dynamic configuration object is absent, rejected, stale or functionally ineffective, use the ARI push-configuration diagnostic. It keeps exact object identity, ARI authorization, Sorcery mapping, persistence wizard, cache state, related-object order and the final PJSIP behavior independently observable.

Preserve evidence safely

Use read-only status information and a narrowly scoped trace first. Logs and captures can contain credentials, identities and conversation content. Restrict access, redact shared extracts and remove temporary diagnostic logging when the investigation ends.

After a repair, repeat the failed scenario and a small set of surrounding workflows. Successful registration alone is not enough: verify two-way audio, hangup and any transfer behavior involved in the original report.

Prove softphone capture before changing the network

When only the softphone user's speech is missing, the microphone diagnostic checks operating-system permission and local capture before following SDP and outbound RTP. It keeps a connected headset, registration, call answer and received audio from standing in for an active microphone path.

Trace mobile wake-up before changing call media

A mobile softphone that rings only while open usually requires an evidence chain across registration ownership, push enrollment, notification-service delivery, app wake-up and the retained INVITE. The background ringing diagnostic keeps those stages separate from later alert, answer and RTP failures.

Trace a repeated SIP authentication challenge as a sequence

The new Asterisk PJSIP 401/407 diagnosis first distinguishes a normal challenge from a loop, then follows the selected auth object, realm, algorithm, credential material, authorized retry and final result. It keeps registration and INVITE exchanges separate and avoids rotating a working secret before the object and realm are known.

Separate transport generation, binding and selection

When a PJSIP transport edit appears ignored, the refreshed Asterisk transport diagnostic separates the saved platform setting, generated configuration, loaded object, local listener, endpoint or registration selection and actual message path. It checks local bind conflicts and the restart boundary before changing credentials, NAT or firewall policy.

Preserve the active audio route across device changes

When a softphone rings or talks through the wrong speaker, headset or microphone, the audio-device diagnostic separates connected hardware, operating-system defaults, per-app routing, client selection, browser permission and the call's active path. It keeps a working system sound or paired Bluetooth label from standing in for the route actually used by the call.

Trace Local-channel data through answer and optimization

When a variable, Dial() option or CDR field appears to vanish after answer, the Local-channel data diagnosis maps both Local halves, the exact read and write moments, inheritance depth, pre-dial placement and optimization events. It does not use /n unless a named behavior must remain on the Local pair.

Trace a stale BLF through its subscription

The Asterisk BLF update diagnosis follows one failed transition through provider state, loaded hint and context, watcher, SUBSCRIBE response, NOTIFY body and phone mapping. It keeps a working lamp separate from registration, routing and queue evidence.

Trace a taskprocessor high-water warning before changing limits

The Asterisk taskprocessor overload diagnosis follows the named queue, producer, consumer, depth, service time and recovery. It separates queue ownership from PJSIP admission control and does not treat a larger water mark or a restart as a root-cause fix.

Follow FreePBX media through both generated call legs

For a FreePBX PJSIP call that connects with one-way or no audio, the focused media investigation follows the final offer and answer, observed RTP, generated and loaded objects, direct-media topology and each NAT or media control separately.

A pickup code rings busy, fails or finds no call

Use the FreePBX call-pickup investigation to distinguish general group pickup, directed pickup, ring-group pickup and BLF behavior, then correlate the request with the target channel while it is still ringing.

A transfer disconnects, returns or reaches the wrong destination

Use the FreePBX transfer investigation to distinguish blind, attended, BLF, SIP REFER and feature-code paths, then correlate permissions, context, consultation channels and the final bridge.

A device is replaced or registration exceeds Max Contacts

Follow the FreePBX PJSIP max-contacts investigation across managed intent, generated configuration, loaded AoR contacts, NAT source changes and actual dial behavior.

A PJSIP request leaves on the wrong transport

Use the Asterisk transport-selection diagnostic to prove the request URI, DNS target, explicit or implicit object, connection reuse and proxy owner before changing transport order or restarting.

A registered trunk's inbound call uses the wrong endpoint

Use the registration return-path diagnostic to prove Contact, returned line token, endpoint selection, context and called extension as separate steps.

Call drops when a PJSIP session refresh is due

Use the Asterisk refresh-drop diagnostic to prove the negotiated interval, named refresher, failed re-INVITE or UPDATE and releasing component on the exact leg.

Softphone registration disappears after a network change

The network-change diagnostic separates operating-system path events, stale SIP flows, keepalive evidence, replacement registration, registrar contacts, push state and the later call path.

Asterisk receives a digit but the far IVR ignores or doubles it

Use the PJSIP DTMF mismatch diagnostic to correlate ingress receipt, bridge ownership, egress representation and application timing. It keeps RFC 4733 payload mappings, SIP INFO and in-band audio separate on both call legs.

Asterisk early media or PRACK fails

Use the Asterisk PJSIP early-media diagnostic to trace 180 or 183, 100rel, PRACK, SDP and early RTP before changing endpoint policy.

Asterisk PJSIP advertises or uses the wrong media address

Use the focused diagnostic to compare final SDP, loaded transport and endpoint controls, both RTP directions, direct media and proxy ownership before changing NAT settings.

Small SIP messages work but a large UDP request fails

Use the large-message UDP diagnostic to correlate complete message size, selected transport, effective path MTU, IP fragments, intermediary behavior and the final SIP transaction before changing codecs or firewall policy.

Asterisk WebRTC registers but the call is silent

Use the Asterisk WebRTC no-audio diagnostic to separate HTTPS, WSS and SIP success from final SDP, the selected ICE pair, DTLS-SRTP, protected packet flow and browser playback.

Trace a silent IP-button press by action path

When a fixed button produces no call or alert, use the IP-button diagnostic to separate gesture and input detection, standalone endpoint versus smart-relay host, loaded action, SIP answer and audio, multicast receivers, platform or API delivery, supervision and responder acknowledgement.

Trace an unprocessed Asterisk call file without duplicating the job

Use the call-file diagnostic to verify the loaded watcher, effective spool path, atomic same-filesystem rename, modification time, parser, channel attempt and answered action before resubmitting an unknown job.

Trace an AMI originate without blind retries

Use the AMI Originate diagnostic to separate authorization, action acceptance, event visibility, first-leg outcome and downstream dialplan behavior before repeating an ambiguous request.

An ARI-originated channel never reaches the application

Use the Stasis registration diagnostic to separate HTTP creation or origination from the exact application's WebSocket registration and StasisStart. The ARI origination guide defines the IDs and lifecycle gates to capture before any retry.

External Media exists but the audio is absent or wrong

Use the ARI External Media diagnostic to trace driver selection, Stasis ownership, bridge membership, fixed format, outbound destination and inbound return tuple before changing codecs or firewall policy.

ARI channel will not stay in a bridge

Use the ARI bridge diagnostic to separate missing resources, Stasis ownership, membership events, bridge type and media topology from codec or firewall guesses.

Zoom Phone BYOC-P trunk is down or calls fail

Use the BYOC-P diagnostic to trace one call through carrier service, the customer SBC, cluster-specific network and certificate state, Zoom routing objects, E.164 number assignment and negotiated media.

Trace Linphone XML through restart and overwrite semantics

When Linphone fetches a provisioning document but a setting remains stale or returns, use the remote-provisioning diagnostic to prove URL selection, restart-time retrieval, XML input, key support, overwrite behavior and one-time versus repeated application.

Trace a Zoiper call that stops reaching a backgrounded client

Use the Zoiper background incoming-call diagnostic to distinguish an application or operating-system reachability issue from registration expiry, NAT lifetime, Push Proxy wake-up, registrar contact selection and a later media problem.

Trace a 3CX mobile push subscription across an extended absence

Use the 3CX mobile push-expiry diagnostic to separate PBX-version lifetime, last client connection, subscription state, PBX-to-push reachability, device notification controls, re-enrollment and the later call path.

Trace a Genesys Cloud BYOC call across platform and routing boundaries

Use the Genesys Cloud BYOC diagnostic to follow one call through Voice platform, regional peers, directional transport, inbound organization identity, Number Plan Site, carrier response and negotiated media.

Trace an Orange Business Talk failure through its ordered access and trunk

Use the Orange Business Talk diagnostic to follow one call through the selected access type, customer SBC or PBX, certificate state, SIP peers, ordered Voice Channels, country-specific number policy, Orange response and negotiated media.

Trace a Wi-Fi voice interruption across one roam

Use the Wi-Fi phone roaming diagnostic to line up old and new BSSID, client and network roaming decisions, authentication, VLAN and IP continuity, RF conditions and RTP loss before changing AP power or fast-roam policy.

Trace an ACS Direct Routing failure through retirement and application boundaries

Use the Azure Communication Services Direct Routing diagnostic to follow transition eligibility, SBC identity, TLS, SBC-originated OPTIONS, route pattern, bounded failover, carrier result, application event and media.

Trace a quiet or missing horn-speaker page

Use the IP horn-speaker diagnostic to separate source audio, SIP or multicast delivery, receiver selection, PoE, satellite sharing, loaded processing, aiming and site acoustics before raising volume.

ARI prompt is queued, stuck or silent

Use the ARI playback diagnostic to distinguish missing media, wrong scope, Stasis ownership, an existing media queue, control-state races and endpoint audio.

FreePBX hold music is silent or wrong

Use the FreePBX Music on Hold guide and the paired diagnostic to trace category precedence, runtime class, source process, media ownership and audible result.

CCAI Platform BYOC call fails or has no audio

The CCAI Platform BYOC diagnostic follows one call through instance activation, unique SIP FQDN, directional authentication, route and metadata selection, signaling, media and transfer ownership.

Browser softphone gets an INVITE but does not ring

Use the browser no-ring diagnostic to separate WSS and registration, INVITE delivery, visible call state, autoplay policy, user activation, answer and remote conversation audio.

Trace a DECT repeater that associates but still fails

Use the DECT repeater coverage and call diagnostic to separate compatibility and association from region, overlap, topology, local relay capacity, base registration, routing and media.

FreePBX contact is missing or stale

Use the Contact Manager guide and focused diagnostic to separate the authoritative record, override, group membership, viewer permission and consumer delivery.

A ported number still reaches the old carrier

Use the ported-number diagnostic to separate the order milestone from range-holder routing, originating-network propagation, new-carrier ingress, PBX matching and final answer. Keep the former path until the agreed acceptance set is complete.

Trace FreePBX prompt language from the channel to the selected file

When a prompt is missing, mixed or in the wrong language, use the FreePBX prompt-language diagnostic. It keeps Sound Languages pack inventory, call-flow language selection, Asterisk fallback, file format, playback and audible result separate.

Trace a Custom Destination from selection through return

The Custom Destination diagnostic follows one call through the selecting module, saved target, generated destination, loaded context and direct-transfer or subroutine stack before changing custom code or downstream routes.

Asterisk AGI script fails or hangs

Freeze one call and separate dialplan reachability, local process launch or FastAGI connection, AGI dialogue, external dependency, hangup cleanup and the post-AGI branch. Capture AGISTATUS only after return and avoid blind retries while a process or connection may still be active.

A SIP-trunk 911 address or callback is wrong

Follow the location-to-call-path diagnostic across direct dialing, route and trunk selection, registered or dispatchable location, callback identity, provider validation and notification without making an uncoordinated emergency call.

MicroSIP registers but calling or audio fails

Use the MicroSIP diagnostic to trace the active account, dial-plan output, SIP response, Via and Contact, SDP and RTP, protection policy, session refresh and Windows audio devices without applying a generic NAT or codec fix.

Trace a room video bar by media path

Use the video-bar camera and room-audio diagnostic to separate session and device selection from privacy, BYOD transport, camera capture, microphone transmit, speaker output, displays, content and network service before resetting the room.

Trace a FreePBX conference that waits, rejects or has no audio

Use the FreePBX conference diagnostic to follow one caller through entry routing, PIN and role, marked-user lifecycle, live ConfBridge state, participant media and bridge mixing before changing room-wide settings.

Trace a FreePBX queue caller's wait, announcements and exit

Use the queue caller diagnostic to follow one call through admission, music and announcements, live eligibility, exit reason and failover without treating a long wait as a network fault or staffing result by itself.

Trace a FreePBX Announcement from route to final destination

Use the Announcement diagnostic when callers hear the wrong recording, cannot repeat or skip, return to the wrong IVR or reach the wrong next destination. It preserves shared recordings and separates answer state, digit receipt, IVR context and downstream routing.

Trace FreePBX voicemail from route to authenticated retrieval

Use the FreePBX voicemail diagnostic when callers reach the wrong mailbox or greeting, a message is missing or silent, or the owner cannot retrieve it. It separates the managed destination, mailbox context, recording result, stored message and retrieval authorization.

Trace a FreePBX dial-by-name search and return path

Use the FreePBX Directory diagnostic when callers cannot find a name, select the wrong person or return repeatedly to an IVR. It follows one call through the Directory entry, DTMF match, announcement, dial target and invalid branch.

Trace a FreePBX Misc Application from code to destination

When a custom internal code is absent, collides or reaches the wrong target, use the feature-code diagnostic with the Misc Applications guide. Preserve phone digits, enabled record, collision, loaded match, destination and permission boundary in order.

Trace a FreePBX blacklist miss or false positive

When a blocked caller still rings or a legitimate caller is rejected, use the FreePBX blacklist diagnostic. It preserves received number and presentation, inbound route, loaded hook, match result, destination and mutation timeline instead of treating the saved row as runtime proof.

Reconcile a failed or partial FreePBX Bulk Handler import

When a Bulk Handler import fails, partly completes or changes the wrong records, use the bounded diagnostic. It preserves the literal artifact, installed schema, full validation detail, update scope, per-row result, Apply Config and owning module instead of blindly replaying the file.

Separate certificate renewal from service activation

For a FreePBX Let's Encrypt failure or stale served certificate, use the renewal investigation. It now versions the Certificate Manager module and keeps issuance, stored object, default selection, proxy or web binding, PJSIP reload and client-observed serial separate.

Contain a restored FreePBX system that reaches production

When a recovery target unexpectedly registers a live trunk or routes real calls, use the restored-PBX diagnostic. It separates registration, IP authorization, inbound delivery, routing and automation while preserving evidence and the production recovery path.

Find the active owner of wrong or rejected FreePBX caller ID

Use the refreshed FreePBX outbound caller-ID diagnostic to prove the selected route and trunk, resolve identity precedence, inspect the outbound INVITE and place carrier authorization after the PBX boundary.

Trace missing, repeated or apparently misordered CEL events

Use the Asterisk CEL diagnostic to separate event selection, per-channel ordering, backend delivery, storage and downstream import before changing collection or deleting records.

Trace a missing, incomplete or misattributed Asterisk queue log

Use the Asterisk queue-log diagnostic to separate Queue admission, logger policy, file or realtime storage, event identity, rotation and downstream reporting before changing queue behavior.

Trace a FreePBX UCP login or feature-access failure

Use the FreePBX User Management and UCP diagnostic to separate account existence, authentication, UCP Allow Login, group inheritance, feature scope, templates, saved layout and web sessions before resetting credentials or widening access.

Trace a FreePBX calendar event that does not match or routes incorrectly

Use the FreePBX Calendar diagnostic to follow one event through remote retrieval, timezone and recurrence, group policy, consumer semantics, generated state and the actual branch.

Find why voicemail or the wrong ring-group member answered

Use the FreePBX ring-group answer-race diagnostic to follow member branches, remote answer supervision, confirmation, timers, cancellation and the final bridge.

Find why Groundwire or Acrobits rings the wrong device

Use the Acrobits device-lifecycle diagnostic when a duplicate, wrong or removed handset reacts to an incoming call. It preserves registration ownership, token cleanup and push progress as separate evidence.

Trace a received FreePBX fax that is missing from email or UCP

Use the FreePBX post-receipt fax diagnostic after ReceiveFAX completes to follow recipient mapping, attachment conversion, local storage, quota, UCP visibility and email delivery.

Find why peoplefone offline fallback did not route the call

Use the peoplefone fallback diagnostic to correlate registration expiry, provider line state, the offline role, number filtering and the alternate call leg.

Find why an A&A number rings an old device and the PBX

Trace provider registrations, SIP-to-server delivery, inherited DDI targets, Also Ring branches, answer and cancellation with the A&A duplicate-ringing diagnostic.

Trace a display speaker by content object and trigger

Use the IP display-speaker screen diagnostic when audio works but the panel is dark, stale, unreadable or shows the wrong content. It separates power and local rendering from slide, screen, event, priority, API, time and physical-visibility owners.

Trace a missing or misrouted FreePBX Callback

Use the FreePBX Callback diagnostic to follow one attempt through the inbound trigger, chosen number, generated object, originated leg, outbound route, answer and final destination.

Find why PortSIP ONE rings only while open

Trace one missed mobile call through version, token, push request, platform delivery, wake-up, new registration and the replacement INVITE with the PortSIP ONE mobile diagnostic.

Find why Bria Mobile rings only while open

Follow one Bria call across Push Service enrollment, registration mode, Contact routing, APNs or FCM, wake-up tunnel, SIP timing and later media with the Bria mobile background-call diagnostic.

Trace Snom M400 roaming through radio and registration

Use the Snom M400 dual-cell roaming diagnostic to distinguish weak synchronization and failed handover from SIP registration replacement, PBX contact policy, call capacity and media.

Find why a registered Zen trunk call has no audio

Follow registration, dialog establishment, SDP, Zen’s documented media ranges, both RTP directions and G.711 decoding with the Zen SIP trunk no-audio diagnostic.

Find why SureVoIP did not try the next destination

Trace the configured order, first-destination response, timeout trigger and next attempt with the SureVoIP inbound destination diagnostic.

Fix a missing, wrong or stale FreePBX caller name

Use the FreePBX caller-name workflow to follow one number through route selection, lookup, optional AstDB cache, channel identity and the phone display.

Trace a missing or mistimed FreePBX Wake Up Call

Follow one reminder through timezone, stored epoch, generated call file, Asterisk spool processing, attempts, answer, prompt and confirmation with the focused diagnostic.

Trace a Poly Rove B4 roaming or audio failure

Use the Poly Rove B4 roaming diagnostic to separate RSSI and cell identity, synchronization chain, DECT handover, SIP state, codec capacity and two-way media.

Trace an Asterisk Gosub that does not return or owns the wrong channel

Use the Gosub diagnostic to follow one invocation through its loaded target, stack frame, arguments, branch, Return() and caller- or callee-channel effect.

Trace a missing, duplicate or slow Asterisk hangup handler

Use the Asterisk hangup-handler diagnostic to follow one channel through push, stack order, run, return, teardown timing, final cause and downstream records.

Trace an Asterisk post-bridge continuation failure

Use the Asterisk after-bridge diagnostic to follow one channel from configured destination through bridge entry, exit, survival and the first executed priority.

Trace a Sangoma Phone login loop before SIP registration

Use the Sangoma Phone login diagnostic to follow one installed or browser client through supported release, PBX readiness, RTAPI reachability, certificate, WSS, user authorization and session creation.

Find why one Magrathea resilience destination receives no calls

Trace the number, nominated pool, provider health probes, pool membership, new-call selection and PBX route with the Magrathea SIP Resilience diagnostic.

Diagnose missing, early or late Asterisk talking events

Follow the Asterisk TALK_DETECT workflow from one channel and its media frames through threshold crossings, audiohook order and the selected AMI or ARI consumer.

Trace a wrong or failed FreePBX Misc Destination

Follow the FreePBX Misc Destination workflow from the selecting module and stable destination ID through exact digits, generated handoff, loaded match and final route or feature owner.

Diagnose missing FreePBX queue priority or wrong caller order

Follow the FreePBX Queue Priorities workflow from the selecting route through inherited QUEUE_PRIO, queue admission, member offers and the final outcome.

Find why an NFON backup PBX receives no calls

Trace the ordered mode, trunk set, endpoint readiness, number route, provider selection and PBX route with the NFON SIP Trunk Flexx diagnostic.

Diagnose an Asterisk channel count or bypassed local limit

Follow the channel-group workflow from loaded key and selected owner through created legs, count timing, decision, transfer and teardown.

Trace a menu prompt that plays but ignores the caller digit

Use the Asterisk BackGround diagnostic to follow one key from channel reception through playback options, destination context, extension matching, timeout and the first executed priority.

Trace a FreePBX API token or GraphQL failure

Use the FreePBX API diagnostic to follow one sanitized request through TLS, application identity, grant, token, scope, active schema and resolver outcome.

Trace a PJSIP multi-contact ring failure

Use the PJSIP_DIAL_CONTACTS diagnostic when one registered device—or none—rings for an endpoint expected to reach multiple contacts.

Trace a PJSIP media-offer override that did not take effect

Use the PJSIP_MEDIA_OFFER diagnostic when a codec stays in the offer, another codec is selected, the call is rejected or media fails after a refresh.

Trace an empty or unexpected PJSIP URI component

Use the PJSIP_PARSE_URI diagnostic when a user, host, port or URI parameter is blank, zero, minus one or different from the expected value.

Trace a missing hold event or unexpected peer behavior

Use the HOLD_INTERCEPT diagnostic when AMI or ARI sees no event, a consumer acts on the wrong channel, or the peer does not enter or leave the intended hold state.

Find why SIP DNS failover did not try the next target

Trace the configured URI, NAPTR, SRV, target addresses, cached state, selected transport, response or timeout and new transaction with the Voip Unlimited DNS diagnostic.

Find why a Baresip account loads but registration or audio fails

Follow the selected config path, module load set, account User-Agent, REGISTER transaction, SDP, RTP and audio endpoints with the Baresip diagnostic.

Trace an Asterisk fax application that fails or selects the wrong mode

Follow the loaded res_fax stack, application channel, FAXOPT values, file access, T.38 or audio path and final result with the Asterisk fax diagnostic.

Investigate empty or misleading Asterisk RTCP statistics

Trace the exact PJSIP owner, stream, RTCP reporter, bridge topology, raw counters and audible symptom with the Asterisk RTCP diagnostic.

Diagnose an empty or mis-scoped Asterisk response header

Trace the release, module, answered callee, uppercase U() handler, response name and instance with the Asterisk PJSIP response-header diagnostic.

Find why an answered fax call never becomes T.38

Trace the initial call, re-INVITE, SDP answer, UDPTL path, ECM and received document with the T38Fax T.38 diagnostic.

Diagnose an empty or wrong Asterisk PJSIP contact lookup

Trace the endpoint, AoR association, contact lifecycle, complete identifier and selected field with the focused Asterisk diagnostic.

Diagnose an empty or wrong Asterisk PJSIP endpoint lookup

Trace function support, the loaded endpoint, exact channel owner, inbound identification, selected field and resolved session behavior with the focused Asterisk diagnostic.

Diagnose an ignored Asterisk PJSIP DTMF override

Trace function support, channel ownership, endpoint policy, runtime mode, protocol event, bridge direction and IVR result with the focused Asterisk diagnostic.

Diagnose a missing ARI transfer event or stalled REFER

Trace version support, endpoint permission, channel timing, WebSocket delivery, REFER correlation, application action, NOTIFY state and final bridge with the focused Asterisk diagnostic.

Diagnose an empty or misplaced Asterisk From parameter

Trace release support, explicit parameter type, callee pre-dial ownership, emitted SIP and intermediary behavior with the focused PJSIP diagnostic.

Diagnose a missing, rejected or ignored PJSIP NOTIFY

Trace release support, loaded content, target mode, endpoint or dialog state, arbitrary-URI configuration, emitted request, SIP response and independent action evidence with the focused Asterisk diagnostic.

Diagnose an ineffective PJSIPRegister or PJSIPUnregister action

Trace release support, AMI permission, exact object name, action response, SIP exchange, Registry event and fresh detail state with the focused runtime-control diagnostic.

Trace Linphone encryption and ZRTP state before changing policy

When a Linphone call is unencrypted, fails under required protection or shows a changed ZRTP SAS, use the focused diagnostic to inspect policy, offer and answer, selected media protection and peer verification without forcing a downgrade or marking an unchecked token valid.

Trace a missing or duplicated inheritable PJSIP header

Use the Asterisk inheritable-header diagnostic to test branch support, source-channel state, callee creation, per-leg mutation, the emitted request and intermediary handling.

Diagnose a rejected PJSIP refresh or post-refresh media loss

Use the Asterisk session-refresh diagnostic to trace channel ownership, re-INVITE or UPDATE, offer-answer collision, SDP result and RTP.

Diagnose an empty or incomplete Asterisk PJSIP header list

Trace release support, loaded module, INVITE scope, current channel, prefix and repeated instances with the focused PJSIP diagnostic.

Diagnose PJSIP hold passthrough and wrong MOH ownership

Use the focused Asterisk diagnostic when hold is not signaled to the peer, local music is unexpected, remote silence appears or media does not resume.

Trace Linphone ICE and relay selection before swapping servers

When a Linphone call lacks candidates, fails checks or never selects an expected relay, use the focused diagnostic to follow effective NatPolicy, discovery, authentication, allocation, SDP, selected pair and RTP in order.

Trace the first final response when PJSIPHangup looks wrong

Use the focused diagnostic when an intended rejection becomes 200, a different final code or an unexpected cause. It checks version, channel, timing and transaction evidence before a bounded correction.

Diagnose an empty or wrong Asterisk PJSIP channel value

Use the channel URI and address diagnostic to prove technology, leg, timing, selector and direction before changing SIP configuration.

Diagnose an empty or wrong Asterisk PJSIP RTP value

Use the RTP address, secure and hold diagnostic to prove channel, stream and timing before changing media configuration.

Find where a LoopUp secure trunk fails

Trace regional DNS, TCP, customer certificate, LoopUp chain, mutual TLS, SIP, SDP security descriptions and SRTP packets with the LoopUp secure-trunk diagnostic.

Trace a Linphone background call from token to media

When Linphone rings only while open, use the focused diagnostic to separate account push parameters, registrar binding, proxy action, platform delivery, app wake, refreshed registration, INVITE, call interface and media.

Diagnose PJSIP MessageSend routing and delivery claims

Use the Asterisk MessageSend diagnostic to separate destination parsing, endpoint and contact selection, Request-URI, header precedence, handler status, SIP response and endpoint presentation.

Diagnose missing or overbroad Asterisk LOG_GROUP output

Use the LOG_GROUP diagnostic when a named channel group hides expected dialplan lines or exposes unrelated ones.

Diagnose a wrong or dropped FreePBX Dynamic Route

Use the Dynamic Routes diagnostic to locate the first mismatch across module state, input, substitution, lookup, exact match and fallback.

Find where FreePBX Set CallerID was skipped or replaced

Use the Set CallerID diagnostic to locate the first mismatch among selection, generated and loaded state, channel identity, downstream policy and provider presentation.

Trace wireless-headset controls and mute state

Use the wireless-headset control diagnostic to locate the first mismatch among physical control, radio or adapter, host, vendor service, softphone state and remote audio.

Find a SIPTRUNK registration or IP-authentication mismatch

Use the SIPTRUNK mode-mismatch diagnostic to align the portal mode, REGISTER or public-source evidence, inbound destination, PBX route and failover result.

Diagnose a Blink Reject that stops other phones or voicemail

Use the Blink inbound-disposition diagnostic to map Reject, Busy or Escape to the actual SIP response, fork cancellations and final caller treatment.

Diagnose SIP.US gateway, secondary-trunk or inbound failover failure

Use the SIP.US failover diagnostic to distinguish current gateway selection, registration or IP authentication, Contact reachability, DID assignment and PSTN treatment.

Diagnose a rejected Bulk Solutions 911 or wrong 922 address safely

Use the Bulk Solutions 911 and 922 diagnostic to verify number provisioning, address, trunk path, caller identity and provider readback before any locally authorized live operator test.

Diagnose restored FreePBX 17 custom Macro failures

Use the FreePBX 17 custom-macro diagnostic to locate the first failure among archive content, loaded includes, removed Macro support, Gosub targets, variable scope, return behavior and downstream routing.

Find why a Flowroute inbound failover route was not tried

Use the Flowroute inbound-failover diagnostic to verify route relationships, destination type, provider edge, first failure, next attempt and restoration.

Find why DIDWW did not try the next trunk-group member

Use the DIDWW trunk-group diagnostic to separate assignment, priority, weight, timeout, rerouting-code, capacity, CDR and PBX evidence.

Diagnose a missing Asterisk frame without hiding it

Follow the FRAME_TRACE diagnostic across version, dialplan execution, channel leg, RX or TX viewpoint, filter and logger state before considering any controlled frame suppression.

Trace lock waits and incorrect shared state

Use the Asterisk lock diagnostic to separate mutex contention, name mismatch, nested ordering, unprotected access, failed updates and caller treatment.

Trace missing, blank, stale or deleted AstDB keys

Use the Asterisk AstDB diagnostic to separate namespace errors, blank values, destructive reads, concurrent writes, wrong-node evidence and restore gaps.

Trace Twilio termination silence or 403 Forbidden

Use the Twilio termination diagnostic to separate trunk-domain identification, DNS reachability, ACL, credentials, number format, caller identity and account policy.

Trace a SessionTalk push call from PBX to direct media

Use the SessionTalk push diagnostic when foreground calls work but a background call does not wake, present, answer or complete with two-way media.

Find why a SIPStation DID does not reach FreePBX

Use the SIPStation inbound diagnostic to separate registration mode, provider delivery order, configured failover, firewall receipt, inbound-route matching and media.

Trace an Asterisk time condition that selects the wrong branch

Use the GotoIfTime diagnostic to separate upstream routing, channel clock, timezone, timespec fields, primitive behavior, fall-through, targets and downstream handling.

Trace an Asterisk variable missing on a child leg

Use the channel-variable diagnostic to separate wrong owner, late write, inheritance depth, Gosub shadowing, master lifetime and explicit cross-channel reads.

Trace an Asterisk exception handler that does not run

Use the Asterisk exception diagnostic to separate wrong event class, context scope, local special-handler precedence, missing e and overwritten status evidence.

Trace a wrong Asterisk dialplan lookup or repeated side effect

Use the dialplan lookup diagnostic to separate branch availability, exact target, Return data, arguments, evaluation timing and downstream outcome.

Diagnose choppy Asterisk audio without blind buffer tuning

The Asterisk jitter-buffer diagnostic separates affected direction, RTP ownership, effective policy, packet evidence, added delay and endpoint processing.

Diagnose empty, partial or noisy Asterisk PJSIP History

The PJSIP History diagnostic checks module state, capture timing, retained entries, filter grammar and call-leg identity before drawing a signaling conclusion.

Diagnose missing, stale or excessive Asterisk metrics

The Asterisk Prometheus diagnostic separates branch support, module state, HTTP path, authentication, provider families, scrape timing, labels and cardinality.

Diagnose empty, failed or slow Asterisk ODBC lookups

The Asterisk func_odbc diagnostic separates module, DSN, connection, query, result and call-path timing evidence.

Diagnose Asterisk ODBC writes that vanish or duplicate

The ODBC mutation diagnostic follows one change through statement execution, transaction selection, commit or rollback, teardown and retry.

Diagnose missing or stale PJSIP Realtime objects

The PJSIP Realtime diagnostic finds the first divergence across Sorcery, source order, connector, schema, row, cache and PJSIP runtime state.

Diagnose missing, duplicated or late Asterisk periodic hooks

The periodic-hook diagnostic follows module, creation, ID, owner, async execution, playback, media and teardown in order.

Diagnose Asterisk silence or noise waits that stall or advance early

The silence and noise diagnostic follows loaded application, channel, frames, units, iterations, timeout, status and downstream routing in order.

Diagnose Asterisk condition waits that time out or return early

The WaitForCondition diagnostic follows installed contract, loaded expression, deferral, state owner, writer, truth, timing, status and downstream routing in order.

Diagnose Asterisk epoch waits that return PAST, fail or fire at the wrong time

The WaitUntil diagnostic follows installed contract, loaded epoch, conversion, clock, channel lifetime, timeout, status and downstream action in order.

Diagnose Dial that returns early, reports a surprising status or never answers

The Asterisk Dial diagnostic follows loaded invocation, created legs, signaling, answer, bridge, result and continuation in order.

Diagnose Originate success with a missing call or second leg

The Asterisk Originate diagnostic separates loaded arguments, sync or async return, first-channel answer, destination entry and any later Dial outcome.

Diagnose Bridge failure, loops, missing targets and missing media

The Asterisk Bridge diagnostic follows two live channels through lookup, answer, membership, exit and two-way media.

Diagnose BridgeWait entertainment and BridgeAdd failure

The Asterisk holding-bridge diagnostic follows handles, roles, answer, entertainment, target lookup and membership.

Diagnose accepted AMI bridge actions with wrong membership

The AMI bridge diagnostic follows authorization, correlation, identities, events and media.

Diagnose an accepted AMI transfer with the wrong call result

The AMI transfer diagnostic follows authorization, action contract, live identities, dialplan entry, target and media.

Diagnose CancelAtxfer failure or the wrong resumed call

The CancelAtxfer diagnostic follows action availability, abort configuration, transfer phase, re-bridging and media.

Diagnose a disappearing or unoptimized Asterisk Local channel

The Local optimization diagnostic follows modifiers, manager evidence, event correlation, final topology and media.

Diagnose missing, stale or mis-correlated AMI channel snapshots

The AMI channel snapshot diagnostic follows version support, list boundaries, live identity, topology and media.

Diagnose missing, delayed or duplicated AMI events

The AMI event-delivery diagnostic follows permissions, masks, filters, transport, parsing and storage.

Diagnose missing, duplicated or misleading AMI UserEvent telemetry

The AMI UserEvent diagnostic traces the producer, USER delivery controls, raw event, storage and outcome.

Diagnose missing, stale or wrong AMI device state

The AMI device-state diagnostic traces version support, EntityID, caching, list completion, provider ownership, hint aggregation and the endpoint outcome.

Diagnose missing, stale or wrong AMI presence state

The AMI presence-state diagnostic traces provider ownership, direct query, bounded list, event scope, hint mapping, subscription and the final consumer.

Diagnose missing, stale or wrong AMI extension state

The AMI extension-state diagnostic traces one Exten-and-Context pair from providers and hint through list completion, live event and subscriber outcome.

Diagnose missing, stale or wrong AMI dialplan extensions

The AMI dialplan diagnostic traces one exact key across source, loaded state, manager transaction, match selection, execution and call outcome.

Diagnose missing, stale or wrong AMI configuration updates

The AMI configuration diagnostic finds the first divergence across file scope, ordered operations, ownership, reload, runtime and outcome.

Diagnose a loaded Asterisk module with a missing capability

The module capability diagnostic traces package, load, registration, configuration and behavior without reaching first for refresh.

Diagnose a missing or denied Asterisk AMI action

The AMI missing-action diagnostic follows one action through session identity, user-visible inventory, server registry, support, authorization and outcome.

Diagnose AMI login and dropped sessions

The AMI login diagnostic traces protected reachability, framing, plain or MD5 authentication, event selection and termination.

Diagnose VoIPstudio Desktop from online state to two-way media

Use the VoIPstudio Desktop diagnostic to separate application login, endpoint registration, call authorization, device selection, network tests and each RTP direction.

Diagnose a registered VoIP Much trunk beyond the green state

Use the VoIP Much trunk diagnostic to separate source blocking, registration cadence, number routing, channel scope, signaling, SDP and both RTP directions.

Trace a passing FreePBX destination test to the actual archive

Use the FreePBX missing-artifact diagnostic to separate job execution, local creation, handler invocation, remote object placement, retention and retrieval.

Diagnose missing or stale AMI core evidence

Use the Asterisk AMI core-query diagnostic to separate wrong node, session, framing, permissions, response correlation, parser and cache faults.

Diagnose missing or incomplete AMI queue snapshots

Use the Asterisk AMI queue diagnostic to separate target, session, permissions, filters, response correlation, completion, parser and cache faults.

Diagnose a registered VoIPline trunk beyond the green state

Use the VoIPline trunk diagnostic to separate mode, interconnect, identity, routing, channel, SDP and media failures.

Diagnose Webex App after the phone service connects

Use the Webex App diagnostic to locate the first failure across assigned service, registration, entitlement, address or number, call control, devices and media.

Trace a missing or stale FreePBX Asterisk Info report

Use the Asterisk Info discrepancy diagnostic to isolate module, dependency, query, transform, observation time and loaded-object state before reloading or restarting a working PBX.

Trace a stale or contradictory FreePBX dashboard card

Use the FreePBX dashboard diagnostic to isolate module, hook provider, collector, cache, clock, unit and runtime source before restarting services or changing a working call path.

Trace a GDS3712 call, video or unlock failure

Use the GDS3712 diagnostic to isolate power, network, SIP, endpoint video, control request, relay, lock, input and event evidence before resetting or rewiring the station.

Diagnose a Voip Unlimited DDI that fails after registration

Use the inbound-DDI workflow to find the first missing provider assignment, port, alias, attempt, edge receipt, identity, route or destination.

Diagnose missing, stale or inverted AMI mailbox results

Use the Asterisk AMI mailbox diagnostic to trace target, context, permissions, raw field semantics, storage freshness, parsing and cache behavior.

Diagnose incomplete AMI voicemail-user results

The AMI voicemail-user diagnostic traces module ownership, permissions, framing, identity and parsing.

Diagnose AMI voicemail refresh and MWI control

The AMI MWI control diagnostic traces one request without conflating acceptance, storage, subscription, delivery or phone display.

Diagnose missing or stale ConfBridge list data

The ConfBridge list diagnostic traces node, module, permission, room identity, framing, filters and parser state.

Diagnose accepted ConfBridge controls that appear ineffective

The ConfBridge control diagnostic traces availability, permission, exact scope, response, events, snapshots and recording files.

Diagnose missing or contradictory ConfBridge lifecycle events

The ConfBridge event diagnostic traces node, profile, permission, filter, transport, identity, threshold and snapshot evidence.

Diagnose a wrong ConfBridge menu, prompt or exit result

The focused ConfBridge diagnostic traces dialplan, profile fallback, DTMF, prompt assets, authorization, action and CONFBRIDGE_RESULT.

Diagnose SignalWire calls that fail after credential registration

Use the SignalWire failed-call workflow to find the first missing profile, handler, number-resource, PBX-route, identity, protection or media boundary.

Diagnose AMI recording that is missing, empty or wrong

The MixMonitor workflow follows one channel from action through events, file close, decode and retention.

Diagnose an AMI parked-call lifecycle

The parked-call workflow follows one channel through assigned slot, retrieval, give-up or timeout and verifies media separately.

Diagnose an accepted queue-member control with wrong state

The queue-member control workflow follows one mutation through exact scope, event visibility, snapshot and call outcome.

Diagnose an accepted queue reload or reset with wrong state

The queue reload and reset workflow traces scope, generation, rule framing, statistics and retained history.

Diagnose queue caller priority or withdrawal that appears ineffective

The queue caller-control workflow traces exact channel identity, later snapshot, dialplan return and historical evidence.

Diagnose an accepted ring-in-use change with wrong ringing

The ring-in-use workflow traces identity, policy, state, eligibility, offer and outcome.

Diagnose an accepted QueueLog action with no useful record

The QueueLog workflow traces node, row, storage, parser and report evidence.

Find the first wrong boundary in a Telnyx inbound path

Use the Telnyx inbound-route diagnostic to trace number assignment, Connection authentication, regional network evidence, route attempts, PBX matching and restoration.

Find the first wrong boundary in a Bandwidth inbound path

Use the Bandwidth inbound-route diagnostic to trace number configuration, route priority, endpoint selection, provider attempts, PBX matching and media.

Start a GRP2624 radio incident with the hardware label

Use the GRP2624 Wi-Fi diagnostic to separate hardware-version capability, firmware lane, scan, authentication, association, IP service, provisioning, registration and media.

Trace a MicroSIP call on the installed build

The MicroSIP diagnostic separates active account, dial-plan result, Request-URI, PAI, SIP response, advertised addresses, negotiated media, DTMF and Windows audio. A 3.22.19 release note is not an incident diagnosis.

Find the first wrong boundary in a Voipfone inbound path

Use the Voipfone inbound-number diagnostic to trace number routing, registration, provider delivery, PBX matching, diverts, fallback and media.

Find the first wrong boundary in a VoIP.ms inbound path

Use the VoIP.ms DID diagnostic to trace routing, POP, identity, number format, PBX matching, failover and media.

Find the first wrong boundary in Twilio origination

Use the Twilio origination diagnostic to trace number association, URL eligibility, provider attempts, PBX handling and recovery.

Find the first wrong boundary in Plivo inbound delivery

Use the Plivo inbound diagnostic to trace number assignment, URI reachability, provider attempts, PBX handling and media.

Find the first wrong Vonage inbound boundary

Use the Vonage inbound diagnostic to trace number linking, URI order, provider attempts, PBX handling and media.

Find the first wrong FreePBX administration boundary

The Admin login diagnostic distinguishes unreachable web service, unfinished setup, rejected identity, SSO, session and missing module authorization.

Trace missing or noisy Asterisk security events by custody stage

The security-event diagnostic distinguishes generation, module, logger channel, file, rotation, parser, alert and enforcement failures.

Diagnose Asterisk features missing after version or build changes

The version/build diagnostic finds the first divergence among branch docs, source, dependencies, build selection, installed files, module state and runtime registry.

Find the first wrong boundary in a Voxtelesys inbound path

Use the Voxtelesys DID-route diagnostic to trace number assignment, route profile, destination priority, provider attempt, PBX match, transfer and media.

Find the first wrong Amazon Chime inbound boundary

Use the Voice Connector group and origination diagnostic to trace assignment, connector choice, host attempt, customer edge, PBX and media.

Find why PhonerLite opened a different local state

The PhonerLite update diagnostic separates executable, write context, data directory, profile, history, audio settings and recording links.

Trace missing Linphone state without overwriting it

The Linphone local-data diagnostic identifies the exact build, user, directories, configuration, databases and provisioning source before restore.

When didlogic outbound works but inbound does not

Use the didlogic inbound-DID diagnostic to find the first mismatch across number destination, identity, provider attempt, PBX match and media.

Trace Callcentric DID Forward and Network Down precedence

Use the Callcentric forwarding diagnostic when a DID bypasses the PBX or a network-down destination is not selected.

Trace empty or changing Asterisk structured state

Use the HASH and ARRAY diagnostic when keys change during iteration or positional values land in the wrong variables.

Trace an empty, stale or wrong Asterisk dial group

Use the DIALGROUP diagnostic to separate membership operations, contact expansion, Dial results and fallback routing.

Trace an empty, slow, redirected or unsafe Asterisk CURL result

Use the Asterisk CURL diagnostic to isolate URL, scope, timing, HTTP, body and fallback ownership.

Trace empty, truncated or misparsed Asterisk input

Use the dialplan input diagnostic to isolate assignment, FILTER, REGEX, delimiter, CUT and downstream ownership.

Trace an Asterisk channel that disappears or maps to the wrong call

Use the channel lifetime diagnostic to separate inventory, identity, Local optimization, bridge and hangup evidence.

Trace a missing or wrong Asterisk extension check after upgrade

Use the VALID_EXTEN upgrade diagnostic to prove function availability, explicit arguments and loaded routing.

Trace a missing or mis-scoped Asterisk feature code

Use the dynamic-feature diagnostic to separate mappings, authorization, DTMF, execution leg and application outcome.

Trace a wrong or blank AMI variable result

Use the AMI Getvar and Setvar diagnostic to separate framing, channel lifetime, namespace, function policy, events and the consumer.

Trace a gray Blink account or registration timeout

Use the Blink registration diagnostic to separate identity, discovery, transport, no-response, 503 and retry evidence.

Trace a missing, stale or over-deleted AstDB value

Use the AMI AstDB diagnostic to separate version, session, namespace, writer, deletion and recovery boundaries.

Diagnose static rows or a missing phone in an AMI registration list

The PJSIP inbound-registration diagnostic finds the first mismatch in action choice, framing, ownership, expiry or node scope.

Diagnose a wrong PJSIP endpoint state, count or object set

The AMI endpoint-state diagnostic finds the first divergence in framing, node, loaded objects, contacts, device state or channels.

Diagnose an empty, stale or unexpected PJSIP AoR list

The AMI AoR-list diagnostic traces framing, permissions, loaded ownership, policy and current contacts.

Diagnose stale PJSIP contact state and missing AMI events

The AMI contact-state diagnostic traces one contact through snapshot, lifecycle, event stream and bounded qualify evidence.

Diagnose missing or unsafe PJSIP auth inventory

The AMI auth-list diagnostic traces completion, relationships, versioned digest support and credential exposure.

Diagnose an Algo 8450 wrong zone, action or silent output

The 8450 control diagnostic follows one button through SIP, multicast or API evidence to the intended receivers.

Diagnose a Commio route that skips or never reaches backup

The Commio inbound-route diagnostic correlates the active profile, exact response, provider attempt and PBX outcome.

Diagnose an 8x8 X Series trunk profile mismatch

The 8x8 X Series diagnostic separates SOW, address identity, challenge, number assignment, security and media.

Diagnose a registered Nextiva trunk with the wrong route or number

The Nextiva diagnostic follows support handoff, registration, assignment, PBX route, capacity and media to the first divergence.

Diagnose an Intermedia DID sent to the wrong route

The Intermedia diagnostic follows location assignment, monitoring, failover selection, PBX handling, call history and media to the first divergence.

Diagnose Infobip route skipping or slow failover

The Infobip route diagnostic follows one call through selection, eligibility, OPTIONS state, connection timing, answer timeout and per-leg logs.

Diagnose an IntelePeer wrong package, route or failover

The IntelePeer route diagnostic follows one call through number inventory, package policy, trunk selection, translation, CDR and PBX evidence.

Diagnose a BCM One wrong route or recovery target

The BCM One route diagnostic follows one inbound attempt from number configuration to provider target, PBX and disaster recovery.

Diagnose a Cox registered trunk with wrong DID routing

The Cox inbound diagnostic follows pilot registration, E-SBC delivery, PBX route and continuity selection.

Diagnose a Comcast wrong group or forward destination

The Comcast diagnostic identifies the first divergence without collapsing five continuity controls into generic failover.

Diagnose a Lumen wrong route plan or trunk

The Lumen diagnostic finds the first divergence while preserving service-family and transition constraints.

Diagnose the wrong AT&T trunk group or route

The AT&T diagnostic finds the first divergence across portal objects, routing controls, edge delivery and PBX handling.

Diagnose the wrong Verizon PBX route or redirect

The Verizon diagnostic finds the first divergence across number cutover, continuity controls, edge delivery and PBX handling.

Diagnose unexpected Bell forwarding

The Bell diagnostic finds the first divergence across schedule, outage rule, provider overflow, edge delivery and PBX handling.

Diagnose an unexpected Rogers peer or redirect

The Rogers diagnostic finds the first divergence across order, peer state, capacity, access, edge delivery and PBX handling.

Diagnose a skipped ThinkTel binding or SureCall forward

The ThinkTel diagnostic finds the first divergence across inventory, OPTIONS, selection, response code, edge and PBX handling.

Diagnose rejected or unscheduled Asterisk registrations

The outbound-registration diagnostic traces completed state, exact vocabularies, retry policy and runtime control.

Diagnose missing, stale or unsafe AMI transport detail

The TransportDetail diagnostic traces framing, association, activation and credential exposure.

Diagnose missing, stale or wrong-endpoint AMI identify detail

The AMI IdentifyDetail diagnostic traces framing, ownership, hostname expansion, order and the actual inbound winner.

Diagnose an Iristel wrong route or failover destination

The Iristel diagnostic finds the first divergence from portal inventory through PBX routing.

Diagnose a TELUS wrong trunk group or edge

The TELUS diagnostic finds the first divergence from the order through PBX routing.

Diagnose a SaskTel RTM or wrong overflow destination

The SaskTel diagnostic finds the first divergence from the order through PBX routing.

Diagnose a Cogeco wrong active trunk or PBX route

The Cogeco diagnostic finds the first divergence from provider selection through PBX routing.

Diagnose missing, stale or ineffective PJSIP maintenance mode

The maintenance-mode diagnostic traces release, manager framing, node scope and actual traffic behavior.

Diagnose missing, stale or incomplete PJSIP subscription inventories

The Asterisk subscription-list diagnostic traces AMI completion, direction, dialog identity, state owner and endpoint display.

Diagnose ignored, stale or over-broad Linphone provisioning

The Linphone provisioning diagnostic follows source ownership, URI timing, authentication, MDM precedence, XML merge and effective runtime state.

Diagnose Poly Studio V52 camera, audio or update failure

The V52 diagnostic finds the first divergence across USB, host selection, room behavior, management and firmware sequencing.

Diagnose Poly Studio V72 camera, audio, peripheral or update failure

The V72 diagnostic finds the first divergence across USB, ports, accessories, privacy, room behavior, management and firmware.

Diagnose Poly Studio E60 camera, pairing or framing failure

The E60 diagnostic finds the first divergence across power, USB, IP-LLN, provider mode, privacy, selection, tracking and firmware.

Diagnose PJSIPHangup wrong-leg, wrong-response and missing-event failures

The AMI PJSIPHangup diagnostic traces version, identity, timing, causes and lifecycle evidence.

Diagnose failed, stuck or refreshing Linphone registration

The Linphone registration diagnostic follows account parameters, route, DNS, transport, AuthInfo, state callbacks and later reachability.

Diagnose a Flowroute wrong PoP, route or failover path

The Flowroute diagnostic finds the first divergence from DID assignment through Direct Media.

Diagnose accepted PJSIPQualify with missing or stale status

The AMI PJSIPQualify diagnostic traces endpoint scope, event visibility, policy and network evidence.

Diagnose an AireSpring wrong route, DTO or capacity result

The AireSpring diagnostic finds the first divergence from order and DID state through provider routing, PBX handling and media.

Diagnose OnSIP registration, 000, transfer and failover

The OnSIP diagnostic finds the first divergence from account state through signaling, PBX routing and media.

Diagnose DIDforSale interconnection, gateways and DID routing

The DIDforSale diagnostic finds the first divergence from portal state through signaling, PBX routing and media.

Diagnose Zadarma registration, IP authorization and SIP-URI routing

The Zadarma diagnostic finds the first divergence from connection model through identity, PBX routing and media.

Diagnose Voxbeam source IP, prefix, DID endpoint and PBX driver

The Voxbeam diagnostic finds the first divergence from portal state through signaling, routing and media.

Diagnose GoTrunk endpoint, POP, DID route and current PBX driver

The GoTrunk diagnostic finds the first divergence from portal state through registration, routing, signaling and media.

Diagnose a missing, stale or over-broad Sorcery cache change

The Sorcery cache diagnostic traces owner, mapping, mode, action, backend retrieval and first consumer.

Diagnose a loaded, missing or not-running Asterisk module

The module diagnostic traces build, startup policy, AMI lifecycle, events and first capability.

Trace a GXW4200 v2 port that rings wrong or cannot call

The GXW4200 v2 diagnostic isolates physical, registration, hunt, route and media boundaries.

Trace JsSIP connected or registered without assuming calls work

The JsSIP diagnostic follows package, page, WSS, REGISTER, RTCSession and media stages in order.

Trace FreePBX ARI authentication or missing events

The FreePBX ARI diagnostic distinguishes managed user, listener, REST, WebSocket, application and Stasis failures.

Diagnose DIDWW direction, destination, authentication and Caller ID

The DIDWW diagnostic finds the first divergence before changing multiple trunk layers.

Diagnose Exotel trunk state, call direction and media

The Exotel diagnostic follows one failed transaction from management objects through signaling and media.

Diagnose Voximplant registration, rule, scenario, leg and media boundaries

The Voximplant diagnostic finds the first divergence before multiple layers are changed.

Diagnose incomplete or secret-bearing outbound-registration lists

The Asterisk AMI diagnostic checks completion, counts, state vocabulary, timers and redaction.

Diagnose Colt failover, recovery and one-way media

The Colt SIP trunk diagnostic follows peer order, timers, blacklist, diversion, TLS, SRTP and bidirectional media.

Diagnose Gamma wrong routing or failed continuity

The Gamma SIP and Call Manager diagnostic follows product ownership, rules, trunk path, PBX, capacity and media.

Diagnose Bandwidth realm or Registrar failures

The Bandwidth outbound diagnostic traces product entitlement, realm, credentials, optional registration, identity and media.

Diagnose Commio source, prefix and inbound-route failures

The Commio diagnostic follows one transaction from portal objects through answer and media.

Diagnose LES.NET DID, channel and outbound-call failures

The LES.NET diagnostic follows one transaction from portal ownership through answer and media.

Diagnose Wavix registration, routing and limit symptoms

The Wavix diagnostic follows one transaction from authentication and number ownership through answer and media.

Diagnose wrong GRP keys, network or firmware state

The GRP2613/GRP2615 diagnostic finds the first mismatch across exact hardware, firmware, discovery, template, VLAN, registration and VPK state.

Diagnose wrong Poly Edge E lines, headset, network or firmware

The E100/E220 diagnostic finds the first mismatch across model, key pages, configuration precedence, Ethernet, Bluetooth, registration and PVOS.

Diagnose Jitsi Desktop registration, call, audio and certificate failures

The Jitsi Desktop diagnostic finds the first mismatch across product identity, package, account, DNS, TLS, SIP, audio and RTP.

Diagnose an HT812 V2 or HT814 V2 port beyond registration

The paired diagnostic finds the first mismatch across V2 identity, FXS mapping, analog behavior, media, fax, NAT or firmware.

Diagnose missing Grandstream V2 ports, network mode or firmware

The HT802/HT818 V2 diagnostic locates the first mismatch across model, port count, topology, profile, provisioning and image family.

Diagnose wrong-line, lifeline and post-firmware HT8x1 failures

The HT841/HT881 diagnostic locates the first mismatch across port role, routing, topology, lifeline mapping and activation state.

Diagnose HT813 call direction before changing templates

The HT813 diagnostic locates the first mismatch across port role, SIP profile, PSTN flow, topology, lifeline and firmware.

Diagnose wrong phone time before resetting the endpoint

The wrong-time diagnostic finds the first mismatch across DHCP, DNS, NTP, UTC, zone, daylight rules, certificates and scheduling.

Preserve the Linphone profile before repairing post-update loss

The Linphone 6.2.4 diagnostic finds the first mismatch across artifact, user, path, database, account deletion and provisioning ownership.

Diagnose Sipnetic after Android 16 or DNS-over-TLS change

The Sipnetic workflow finds the first changed state across package, resolver, DNS answers, SIP destination, TLS trust, REGISTER, background delivery and media.

Diagnose Allstream Unavailable forwarding or a wrong PBX route

The Allstream diagnostic finds the first divergence from portal object through PBX routing and media.

Diagnose Cloudli or legacy babyTEL trunk state

The Cloudli diagnostic finds the first divergence across identity, portal parameters, NAT, continuity, PBX routing and media.

Diagnose Orange Business Talk site, trunk, routing and media state

The Orange Business Talk diagnostic finds the first divergence across site activation, DNS, time, certificate, eSBC, routing and media.

Diagnose Vodafone Evolved Voice order, access, routing and media

The Vodafone Evolved Voice diagnostic finds the first divergence without importing another Vodafone service model.

Diagnose Swisscom Enterprise SIP access, SBC, routing and media

The Swisscom Enterprise SIP diagnostic finds the first divergence without importing another Swisscom service model.

Diagnose Sunrise Business Voice SIP access, SBC, routing and media

The Sunrise Business Voice SIP diagnostic finds the first divergence without importing another Sunrise service model.

Diagnose Proximus Business Trunking by first divergence

The Proximus Business Trunking diagnostic follows flavour, access, CPE, SBC, PBX, number, signaling and media without importing another service.

Diagnose AMI voicemail message operations without blind retries

The AMI voicemail message diagnostic finds the first divergence across action, identity, response, storage and user-visible state.

Diagnose AMI DTMF, MF or hook flash without broad retries

The AMI signalling diagnostic isolates action, channel, direction, transport and downstream handling.

Diagnose AbsoluteTimeout without shortening the wrong call

The AMI AbsoluteTimeout diagnostic isolates channel identity, units, competing writers, dialplan and final Hangup evidence.

Diagnose MuteAudio without guessing from silence

The MuteAudio diagnostic isolates channel identity, PBX-relative direction, mute mechanism and media proof.

Diagnose remote playback control without guessing from sound

The ControlPlayback diagnostic isolates target identity, initiator compatibility, control semantics and audible result.

Diagnose legacy AMI Monitor by version before storage

The AMI Monitor diagnostic isolates removal, availability, identity, lifecycle ordering, mixing and artifact evidence.

Diagnose accepted Hangup without ending another call

The AMI Hangup diagnostic isolates selector scope, identity, authority, cause, events, cleanup and linked legs.

Diagnose accepted SendText without changing the wrong channel

The AMI SendText diagnostic isolates identity, authority, content, driver, protocol and presentation.

Diagnose accepted out-of-call messages without changing the wrong layer

The AMI MessageSend diagnostic isolates framing, destination, contact, transport, response and presentation.

Diagnose missing or wrong Advice of Charge evidence by layer

The AMI AOCMessage diagnostic isolates target, phase, encoding, event and presentation.

Diagnose Crazytel by the first divergent boundary

The Crazytel SIP trunk diagnostic follows product, authentication, edge, DID, identity, signaling and media without importing another service.

Diagnose MaxoTel at the first divergent boundary

The MaxoTel SIP trunk diagnostic follows portal, UDP registration, blocklist, DID, identity, signaling and media evidence.

Diagnose configuration preprocessing before editing duplicates

The include diagnostic follows configuration root, include set, generated output, effective sections and loaded objects.

Diagnose missing or contradictory AMI agent state

The AMI agent diagnostic follows module, definition, completed inventory, login, filters, logoff and queue-call events.

Diagnose missing or contradictory AMI fax state

The AMI fax-session diagnostic follows module support, completed list, session detail, event delivery, counter scope and terminal result.

Diagnose missing or stale PJSIP resource lists

The AMI resource-list diagnostic follows module, AMI, configuration, dialog and endpoint boundaries.

Diagnose missing or alarmed DAHDI spans and channels

The AMI DAHDI diagnostic finds the first divergence from AMI support through the physical circuit.

Diagnose a missing or down PRI span

The AMI PRI diagnostic finds the first divergence from action support through the carrier circuit.

Diagnose missing legacy SIP peer actions after upgrade

The missing SIPpeers diagnostic moves from release and driver proof to bounded PJSIP validation.

Diagnose Aussie Broadband at the first divergent boundary

The Aussie Broadband SIP trunk diagnostic follows order, NBN access, handoff, PBX, number, signaling, channel and media evidence.

Diagnose Grandstream Wave by the first divergent boundary

The Grandstream Wave diagnostic follows platform, UCM identity, RemoteConnect, background delivery, browser, signaling and media evidence.

Trace a Wireless Phone 9821 failure across battery, WLAN, call and Action paths

The 9821 diagnostic localizes one symptom without treating association or registration as end-to-end proof.

Diagnose RingCentral App at the first divergent boundary

The RingCentral diagnostic follows organization, build, identity, call handling, notification, signaling and media evidence.

Diagnose missing or stale IAX2 AMI evidence

The IAX2 AMI diagnostic traces action availability, framing, registration and active-channel timing.

Diagnose Symbio at the first divergent boundary

The Symbio Enterprise SIP trunk diagnostic follows order, access, handoff, number, PBX route, signaling, media and selected dual-network evidence.

Diagnose Telstra SIP Connect at the first divergent boundary

The Telstra SIP Connect diagnostic follows order, access, CPE, number, capacity, route, signaling, media and continuity evidence.

Diagnose Optus Evolve Voice at the first divergent boundary

The Optus Evolve Voice diagnostic follows agreement, application, access, handoff, PBX, number, signaling, media and continuity evidence.

Diagnose One NZ SIP at the first divergent boundary

The One NZ SIP diagnostic follows product, order, access, demarcation, PBX, channels, DDIs, signaling, media and continuity evidence.

Diagnose 2degrees SIP at the first divergent boundary

The 2degrees SIP diagnostic follows order, access, handoff, PBX, channels, DDIs, signaling, media and continuity evidence.

Diagnose missing or suspended Asterisk bridge technologies

The focused bridge-technology diagnostic traces list framing, registration, mutation and future bridge selection.

Diagnose accepted LoggerRotate actions with missing or stale files

The focused LoggerRotate diagnostic traces manager, policy, strategy, file, command and collector boundaries.

Diagnose Vocus SIP at the first divergent boundary

The Vocus SIP Voice diagnostic follows product, order, access, interface, PBX, channels, numbers, signaling, media and continuity evidence.

Diagnose Superloop at the first divergent boundary

The Superloop diagnostic follows order, access, PBX, identity, DID, media, outage and fault evidence.

Diagnose Zoom Workplace calling at the first divergent boundary

The Zoom Workplace diagnostic follows entitlement, build, Phone visibility, handling, network, device and media without broad resets.

Trace a Yealink VP59 edition, firmware or media failure

The VP59 diagnostic localizes one symptom without treating sign-in, registration or preview as end-to-end proof.

Diagnose Enreach at the first divergent boundary

The Enreach diagnostic follows product, country, profile, number, signaling, media and continuity evidence.

Diagnose Asterisk 24 candidate changes at the first divergent boundary

The Asterisk 24 diagnostic follows artifact, build, runtime, module, configuration, integration and protocol evidence.

Diagnose NextivaONE at the first divergent boundary

The NextivaONE diagnostic follows product identity, account, handling, background delivery, network, local devices and media.

Diagnose Teams Phone at the first divergent boundary

The Teams Phone diagnostic follows entitlement, voice enablement, policy, routing, notification, device and media.

Diagnose Dialpad at the first divergent boundary

The Dialpad app diagnostic follows assignment, line identity, routing, notification, device, network and media.

Diagnose MetTel at the first divergent boundary

The MetTel SIP trunk diagnostic follows order, site, access, number, policy, identity, signaling, media and support evidence.

Diagnose NUSO at the first divergent boundary

The NUSO diagnostic follows order, access, channel, peer, number, failover, fraud, signaling, security and media evidence.

Diagnose a missing core dump or incomplete backtrace

The Asterisk crash-evidence diagnostic follows incident identity, dump policy, matching artifacts, symbols, reports and secure escalation.

Diagnose Telesystem at the first divergent boundary

The Telesystem diagnostic follows order, tenant, handoff, authentication, capacity, forwarding, number, signaling and media evidence.

Diagnose TPx UCx SmartVoice at the first divergent boundary

The TPx diagnostic follows order, handoff, access, capacity, forwarding, continuity, SIP and media evidence.

Diagnose Lingo Cloud SIP at the first divergent boundary

The Lingo diagnostic follows order, access, path allocation, bursting, failover, SIP and media evidence.

Diagnose Asterisk memory growth and missing debug artifacts

The Asterisk memory-growth diagnostic follows process accounting, build proof, mmlog, reference logs, activity evidence and safe escalation.

Diagnose Voyant at the first divergent boundary

The Voyant diagnostic follows order, access, elastic policy, caller identity, E911, SIP, media and support evidence.

Diagnose 8x8 Work at the first divergent boundary

The 8x8 Work diagnostic follows tenant assignment, capability, extension identity, route, notification, device, network and media.

Diagnose an apparently deadlocked Asterisk process

The Asterisk deadlock diagnostic follows process state, diagnostic build, threads, locks, all-thread stacks, safe capture and restoration evidence.

Diagnose VBC at the first divergent boundary

The VBC diagnostic follows account assignment, extension identity, route, notification, device, network, continuity and media.

Diagnose an Asterisk stop or restart that waits or leaves readiness unclear

The Asterisk restart diagnostic follows command mode, channel admission, drain, Shutdown, process replacement, FullyBooted and restoration.

Diagnose Windstream Dynamic IP at the first divergent boundary

The Windstream diagnostic follows order, access, capacity, DTO, number, QoS, SIP, media and support evidence.

Diagnose Aircall at the first divergent boundary

The Aircall diagnostic follows company access, line assignment, distribution, availability, notification, device, network and media.

Diagnose Granite at the first divergent boundary

The Granite diagnostic follows agreement, order, handoff, capacity, DTFO, E911, SIP, media, SLA and support evidence.

Diagnose FirstLight at the first divergent boundary

The FirstLight diagnostic follows order, access, handoff, numbers, E911, SIP, media, SLA and support evidence.

Diagnose GAC2570 at the first divergent boundary

The GAC2570 diagnostic follows workflow owner, power, network, provisioning, identity, conference legs, accessories, firmware and room media.