Source note · Setting up a carrier SIP trunk on an AudioCodes SBC
After a 401 the client retries with an Authorization header, and after a 407 with a Proxy-Authorization header.
Checked 2026-10-01
- Vendor
- IETF
- Product
- SIP
- Subsystem
- authentication
- Deployment
- multi-tenant, on-premises
- Region
- not restricted
- Release range
- RFC 3261
- Checked
- 2026-10-01
Sources
- RFC 3261 — SIP: Session Initiation Protocol — IETF / RFC Editor · tier 1 standards and regulators · RFC 3261 sections 22.2 and 22.3
Cite this note
APA
WarmTransfer. (2026, October 1). Setting up a carrier SIP trunk on an AudioCodes SBC: source note audiocodes-carrier-sip-trunk-setup-rfc-auth-retry. WarmTransfer. https://warmtransfer.net/knowledge/claims/audiocodes-carrier-sip-trunk-setup-rfc-auth-retry
BibTeX
@misc{warmtransfer-claim-audiocodes-carrier-sip-trunk-setup-rfc-auth-retry,
title = {Setting up a carrier SIP trunk on an AudioCodes SBC: source note audiocodes-carrier-sip-trunk-setup-rfc-auth-retry},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/audiocodes-carrier-sip-trunk-setup-rfc-auth-retry},
note = {Source note audiocodes-carrier-sip-trunk-setup-rfc-auth-retry, checked 2026-10-01}
}