Source note · Setting up CUBE for a carrier SIP trunk
In SIP a registrar or user agent challenges with 401 Unauthorized and a proxy with 407 Proxy Authentication Required, and the client retries with credentials.
Checked 2026-09-25
- Vendor
- multi-vendor
- Product
- SIP
- Subsystem
- authentication
- Deployment
- any
- Region
- not restricted
- Release range
- RFC 3261
- Checked
- 2026-09-25
Sources
- RFC 3261 — SIP: Session Initiation Protocol — IETF / RFC Editor · tier 1 standards and regulators · Sections 22.2 (User-to-User Authentication) and 22.3 (Proxy-to-User Authentication)
Cite this note
APA
WarmTransfer. (2026, September 25). Setting up CUBE for a carrier SIP trunk: source note cube-carrier-trunk-setup-sip-digest-challenge. WarmTransfer. https://warmtransfer.net/knowledge/claims/cube-carrier-trunk-setup-sip-digest-challenge
BibTeX
@misc{warmtransfer-claim-cube-carrier-trunk-setup-sip-digest-challenge,
title = {Setting up CUBE for a carrier SIP trunk: source note cube-carrier-trunk-setup-sip-digest-challenge},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cube-carrier-trunk-setup-sip-digest-challenge},
note = {Source note cube-carrier-trunk-setup-sip-digest-challenge, checked 2026-09-25}
}