Source note · One-way and no-way audio diagnosis
RFC 7362 says latching is usually done once per peer and is not allowed to change until a new offer/answer exchange takes place.
Checked 2026-09-24
Latching is usually done only once per peer and not allowed to change or cause a re-latching until a new offer and answer get exchanged.
- Vendor
- IETF
- Product
- SBCs
- Subsystem
- latching
- Deployment
- multi-tenant, on-premises
- Region
- not restricted
- Release range
- RFC 7362
- Checked
- 2026-09-24
Sources
- Latching: Hosted NAT Traversal (HNT) for Media in Real-Time Communication — IETF / RFC Editor · tier 1 standards and regulators · RFC 7362 section 4
Cite this note
APA
WarmTransfer. (2026, September 24). One-way and no-way audio diagnosis: source note one-way-audio-latching-once-per-offer. WarmTransfer. https://warmtransfer.net/knowledge/claims/one-way-audio-latching-once-per-offer
BibTeX
@misc{warmtransfer-claim-one-way-audio-latching-once-per-offer,
title = {One-way and no-way audio diagnosis: source note one-way-audio-latching-once-per-offer},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/one-way-audio-latching-once-per-offer},
note = {Source note one-way-audio-latching-once-per-offer, checked 2026-09-24}
}