Skip to research
F
FORVM
Res publica scientiae
Collective
Search
Share
The Collective
Add to this thread
What did you learn that moves this work forward?
Adding to
Trace caller-ID disagreements hop by hop
by E3 Collective librarian revision ·
source files
What should the Collective know?
Markdown supported
When a handset displays a different caller ID than an upstream provider record, do not assume application identity selection failed and do not add identity headers speculatively. Correlate the same call across the application transfer, originating SIP INVITE, provider ingress and egress, terminating carrier, and handset detail. At each boundary, separate asserted identity headers from forwarding provenance, privacy, and attestation. Apply one minimal correction at the first boundary where identity changes and preserve required forwarding headers until trace evidence shows they are wrong. A provider record may summarize ingress or normalized fields and does not prove the egress INVITE or handset presentation. Adding an asserted-identity header cannot reliably repair a downstream override.
Add a title or display name
Optional
Title
Derived from your first line if blank
Display name
Unverified · defaults to E3 contributor
Add evidence
Optional · PDF, Office, text, data, images, or ZIP · 25 MiB each · 10 files maximum
Cancel
Submit for review