VoIP.infoThe independent guide to business communications.
VoIP.info Troubleshooting

Asterisk PJSIP Realtime object is missing, stale or from the wrong source

Find the first divergence among Sorcery type, mapping order, Realtime family, connector, schema row, cache and PJSIP runtime view.

Reviewed 2026-10-15Current Asterisk Realtime architecture, PJSIP Realtime tutorial, Sorcery mapping and caching guidance, Realtime schema-management guidance, PJSIP troubleshooting guide, and upstream extconfig and sorcery samples reviewed October 15, 2026; installed Asterisk branch, packaged modules, mapping order, connector, DSN, driver, schema revision, database account, rows, cache policy, reload behavior and PJSIP runtime state remain deployment specific; no host, module, connector, credential, database, schema, row, cache, endpoint, registration, message, packet or live call was inspected or testedAdvancedDocumentation based · not lab tested

Capture one object identity and observation timeline

Preserve timestamp and timezone, installed Asterisk branch and package, exact PJSIP object type and ID, owning module, expected source, Sorcery section and mapping order, Realtime family, driver and connection name, redacted schema key, cache name and policy, last database change, reload or restart boundary, module-specific CLI output and final symptom. Include a known-good object from the same intended path.

Classify the symptom as absent mapping, wrong owning section, unavailable driver or connection, missing table or column, absent row, invalid row, duplicate static object, wrong source order, stale cache, incomplete full-set cache, unsupported object type, reload boundary or later PJSIP behavior. Do not edit the row before this evidence is preserved.

Walk from Sorcery type to the exact database owner

Match the object type to the correct Sorcery configuration section; optional PJSIP modules can own mappings outside the base res_pjsip section. Then follow the selected wizard and family into extconfig.conf, the Realtime driver and connection name, res_odbc.conf, the system DSN, driver, database account and target table.

Confirm the required modules are packaged and loaded before interpreting a blank PJSIP listing as a missing row. A connected ODBC resource proves neither the family mapping nor the selected table, and a successful direct SQL query proves neither Asterisk permissions nor Sorcery retrieval.

Separate row existence from object validity and selection

Inspect one redacted row by its exact ID and compare columns with the schema revision for the installed branch. Distinguish missing table or column, null and blank values, type or enumeration validation, truncation, case mismatch, duplicate IDs and related-object references. Preserve database error classes without copying credentials or secret values.

Next compare static and Realtime sources in Sorcery order. A valid row can remain unused when an earlier mapping supplies the same ID, while a later source may be consulted only after the earlier source has no object. Do not delete a static object or reorder all mappings merely to test a hypothesis.

Prove whether cache owns the stale observation

Record whether the object type has a memory cache, its position before the Realtime wizard, configured lifetime, stale time, maximum, reload expiry and full-backend mode. Compare the database modification time, cache observation time and module-specific CLI view. A backend change does not automatically invalidate an indefinitely retained cache entry.

Use a narrowly scoped, approved cache expire, stale or populate action only after the mapping and backend row are known. For object types commonly retrieved as a set, distinguish an incomplete per-object cache from a full-backend cache. A refreshed cache that still shows the wrong object points back to source order, schema or the record itself.

Investigate schema drift and database availability safely

When retrieval errors follow an upgrade, compare the installed branch, Alembic revision, table definition and applicable CHANGES and UPGRADE material. Asterisk warns that cross-series schema migrations can lose data; take a verified backup and use the branch-matched migration path rather than hand-adding one column during an incident.

For intermittent absence, separate connection establishment, pool capacity, authentication, network path, database listener, query latency, lock wait and server failover. Retain an unaffected Realtime object as a control. Do not broaden database access or replace the service account with an administrator credential to make the diagnostic pass.

Correct one owner and verify the intended PJSIP behavior

Correct only the first proved divergence: owning Sorcery section, mapping order, family, connector, DSN, module load order, schema revision, row value, duplicate source or cache policy. Preserve the prior configuration, database backup, rollback trigger and cache impact.

Re-read the object through Sorcery and the PJSIP CLI, then test the behavior it is meant to supply: request identification, authentication, AoR association, contact binding, registration or one bounded call. Keep those results separate and repeat the known-good control. No host, connector, database, row, cache, endpoint, registration, message or live call was inspected or tested for this diagnostic.

Sources & applicability

Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.

Examples require adaptation to your topology. No live PBX or hardware testing is claimed.

Continue your research

Guide · Current Asterisk Realtime architecture, PJSIP Realtime tutorial, Sorcery mapping and caching guidance, Realtime schema-management guidance, PJSIP troubleshooting guide, and upstream extconfig and sorcery samples reviewed October 15, 2026; installed Asterisk branch, packaged modules, mapping order, connector, DSN, driver, schema revision, database account, rows, cache policy, reload behavior and PJSIP runtime state remain deployment specific; no host, module, connector, credential, database, schema, row, cache, endpoint, registration, message, packet or live call was inspected or tested

Asterisk PJSIP Realtime: Sorcery mapping, schema and cache boundaries

Map one PJSIP object from Sorcery type and source order through Realtime family, connector, schema row, cache and runtime consumer.

Read guide →
Troubleshooting · Current Asterisk PJSIP_ENDPOINT and CHANNEL function documentation, res_pjsip endpoint configuration reference, object-relationship guidance and PJSIP troubleshooting guidance reviewed October 13, 2026; PJSIP_ENDPOINT is documented since Asterisk 12.0.0, while installed branch, maintenance release, loaded modules, configuration backend, object names, defaults, endpoint identification, channel association, contacts, signaling and media remain deployment specific; no PBX, module, configuration, endpoint, identify object, channel, SIP exchange, packet or call was inspected or tested

Asterisk PJSIP endpoint lookup is empty, missing or shows the wrong field

Trace the function, exact endpoint name, loaded object, current channel association, default resolution and consuming decision before changing SIP policy.

Read guide →
Troubleshooting · Current Asterisk PJSIP_AOR, PJSIP_CONTACT and PJSIP_DIAL_CONTACTS function documentation plus PJSIP object-relationship and troubleshooting guidance reviewed October 13, 2026; both inspection functions are documented since Asterisk 13.2.0, while installed branch, maintenance release, loaded modules, configuration source, object names, registrations, contacts, qualification state, timing and routing remain deployment specific; no PBX, module, configuration, endpoint, AoR, contact, registration, OPTIONS exchange, packet, channel or call was inspected or tested

Asterisk PJSIP AoR or contact lookup is empty, stale or wrong

Trace the exact endpoint, AoR name, returned contact identifier, lifecycle and queried field before changing registration, qualification or dial logic.

Read guide →
Troubleshooting · Asterisk 22 LTS res_pjsip and endpoint-identifier references, the Asterisk endpoint-identification article, current object-relationship and troubleshooting guidance and GHSA-qqxj-v78h-hrf9 were reviewed October 8, 2026; the installed branch, patches, modules, generated configuration, endpoints, identify objects, DNS, provider signaling addresses, proxy path and SIP transactions require runtime verification

Asterisk PJSIP cannot identify an inbound request: endpoint-matching diagnosis

Trace the rejected SIP message through loaded identifier modules, global order, endpoint permissions and exact IP, username, header or request-URI evidence before changing authentication or routing.

Read guide →
Guide · Asterisk 22 LTS and current Asterisk configuration, CLI, dialplan, module-loader, PJSIP transport and restart documentation reviewed October 5, 2026; exact packaged builds, managed platforms and installed modules require runtime verification

Asterisk configuration lifecycle: source, reload, restart and proof

Trace one change from its supported configuration owner through generated input, loaded runtime state, activation scope, call evidence and rollback.

Read guide →
Guide · Current Asterisk logging, runtime command, logger.conf, debug-collection, call-identifier and console-verbosity documentation reviewed September 30, 2026; no process, logger, trace, storage path or call tested

Asterisk logging without permanent debug overload

Map configured destinations, console levels, call identifiers and a bounded protocol trace without leaving sensitive debug collection active.

Read guide →
Guide · Current Asterisk CLI, logging, PJSIP troubleshooting and call-identifier documentation reviewed September 30, 2026; CLI commands are not shell commands; no PBX, trace, call or media tested

Asterisk CLI and PJSIP logging for one failed call

Bind one failed call to the loaded PJSIP objects, dialplan decision and short signaling trace, then prove diagnostic cleanup.

Read guide →
Guide

PBX logs and packet captures: useful evidence with limited exposure

Collect enough to diagnose a call while protecting identities, secrets and audio.

Read guide →
Hub

VoIP troubleshooting

Use symptoms and evidence to isolate registration, routing, media and device faults.

Explore topic →