Source note · Carrier escalation evidence packages
Because SBCs and B2BUAs change the Call-ID between legs, an escalation to a carrier should quote the identifiers seen on the carrier-facing leg (its Call-ID, numbers and UTC-or-zoned timestamp) rather than an internal platform ID such as a Teams Correlation ID.
inferred · Checked 2026-09-24
- Vendor
- multiple
- Product
- SIP trunking
- Subsystem
- evidence identifiers
- Deployment
- any
- Region
- not restricted
- Release range
- current as of 2026-09-24
- Status
- inferred
- Checked
- 2026-09-24
Sources
- RFC 7989: End-to-End Session Identification in IP-Based Multimedia Communication Networks — IETF / RFC Editor · tier 1 standards and regulators · Section 1, read with bandwidth-help-call-logs-page Call ID field and ms-learn-pstn-usage-report Correlation ID
Cite this note
APA
WarmTransfer. (2026, September 24). Carrier escalation evidence packages: source note carrier-escalation-evidence-trunk-leg-identifiers. WarmTransfer. https://warmtransfer.net/knowledge/claims/carrier-escalation-evidence-trunk-leg-identifiers
BibTeX
@misc{warmtransfer-claim-carrier-escalation-evidence-trunk-leg-identifiers,
title = {Carrier escalation evidence packages: source note carrier-escalation-evidence-trunk-leg-identifiers},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/carrier-escalation-evidence-trunk-leg-identifiers},
note = {Source note carrier-escalation-evidence-trunk-leg-identifiers, checked 2026-09-24}
}