Source note · Running a virtual SBC in Azure or AWS

Because a cloud VM only sees its private address behind the provider's one-to-one NAT, a cloud-hosted SBC must be configured to write its public address into SIP and SDP, or remote peers receive unroutable private addresses.

inferred · Checked 2026-10-14

Vendor: not restricted
Product: not restricted
Subsystem: nat
Deployment: iaas
Region: not restricted
Release range: current as of 2026-10-14
Status: inferred
Checked: 2026-10-14

Sources

Enable internet access for a VPC using an internet gateway — Amazon Web Services · tier 2 current vendor documentation · Internet gateway basics, IP addresses and NAT

Cite this note

APA

WarmTransfer. (2026, October 14). Running a virtual SBC in Azure or AWS: source note cloud-hosted-sbc-inf-sbc-must-advertise-public-ip. WarmTransfer. https://warmtransfer.net/knowledge/claims/cloud-hosted-sbc-inf-sbc-must-advertise-public-ip

BibTeX

@misc{warmtransfer-claim-cloud-hosted-sbc-inf-sbc-must-advertise-public-ip,
  title  = {Running a virtual SBC in Azure or AWS: source note cloud-hosted-sbc-inf-sbc-must-advertise-public-ip},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/claims/cloud-hosted-sbc-inf-sbc-must-advertise-public-ip},
  note   = {Source note cloud-hosted-sbc-inf-sbc-must-advertise-public-ip, checked 2026-10-14}
}

Read in context