| purpose | direction | IPv4 | IPv6 |
|---|---|---|---|
twilio-sip/sip-media | both | · | · |
twilio-sip/sip-signaling | both | · | · |
twilio-sip/sip-media
Direction: both. Twilio Elastic SIP Trunking publishes these ranges for traffic in either direction; use them in the rule direction your integration needs. The example below shows egress.
loading ranges from the feed…
This purpose currently publishes more IPv4 ranges than the default rules-per-SG quota (60). Each CIDR consumes one rule; the hosted prefix list spends quota once per list instead. Details in the FAQ.
Terraform
data "ipranges_egress" "twilio_sip_sip_media" {
service = "twilio-sip"
purpose = "sip-media"
}
resource "aws_security_group_rule" "twilio_sip_sip_media" {
type = "egress"
from_port = 443
to_port = 443
protocol = "tcp"
cidr_blocks = data.ipranges_egress.twilio_sip_sip_media.ipv4_cidrs
security_group_id = aws_security_group.app.id
}
twilio-sip/sip-signaling
Direction: both. Twilio Elastic SIP Trunking publishes these ranges for traffic in either direction; use them in the rule direction your integration needs. The example below shows egress.
loading ranges from the feed…
This purpose currently publishes more IPv4 ranges than the default rules-per-SG quota (60). Each CIDR consumes one rule; the hosted prefix list spends quota once per list instead. Details in the FAQ.
Terraform
data "ipranges_egress" "twilio_sip_sip_signaling" {
service = "twilio-sip"
purpose = "sip-signaling"
}
resource "aws_security_group_rule" "twilio_sip_sip_signaling" {
type = "egress"
from_port = 443
to_port = 443
protocol = "tcp"
cidr_blocks = data.ipranges_egress.twilio_sip_sip_signaling.ipv4_cidrs
security_group_id = aws_security_group.app.id
}
keep rules current automatically
Terraform data sources refresh only when you run an apply. The hosted tier publishes the same data via AWS managed prefix lists (slash0.twilio-sip.sip-media.v4 and so on), shared into your account via AWS RAM: rules reference one pl-… id and update within a minute of a vendor change, with removals held through a 72 hour grace window. Request early access or read how it works.
provenance
Ranges come from Twilio Elastic SIP Trunking's official publication: https://www.twilio.com/docs/sip-trunking/ip-addresses. Fetched sources:
Every publish is signed (ECDSA P-256 over the feed index, each service document hash-chained to it) and every range change is recorded in the changelog. Verification steps: security. Provider setup: quickstart.