Does LiveKit Cloud accept inbound SIP and RTP traffic from an Iranian carrier?

Hello,

We are evaluating LiveKit Cloud for a Persian-language AI voice assistant using Agent Builder and an OpenAI Realtime model with our own API key.

Our telephone number and SIP trunk are provided by an Iranian telecom carrier. Before requesting a routing change from the carrier, we need to confirm:

  1. Does LiveKit Cloud accept inbound SIP INVITE and RTP traffic originating from an Iranian telecom carrier or Iranian public IP address?
  2. Is commercial LiveKit Cloud telephony usage supported when the SIP carrier and callers are located in Iran?
  3. Are there geographic, compliance, sanctions, account, signaling, or media restrictions that could block this traffic?
  4. Which transport should the carrier use: UDP 5060, TCP 5060, or TLS 5061?
  5. Which RTP port ranges and codecs should the carrier allow?

We tested our project-specific LiveKit SIP hostname from an Iranian server. DNS resolution succeeded, but TCP 5060, TCP 5061, and UDP SIP OPTIONS all timed out. We cannot determine whether this is caused by the Iranian hosting network or a restriction on the LiveKit side.

We would appreciate an official confirmation before asking our telecom carrier to route the number.

Thank you.

Hi Majid, thanks for the details and for asking before making carrier changes.

I’m actually not sure about this one. Deploying commercial telephony with a carrier and end users in Iran raises export-control and sanctions questions that our legal and compliance team has to answer. Our Terms of Service (§2.2, Compliance with Laws) require that use of the Services comply with applicable export and sanctions laws, and that customers aren’t barred from receiving the Services under US law or the law of the country they’re using them from.

So I don’t want to give you routing, port, or codec guidance that implies the setup is approved before we’ve assessed it. Let me put this in front of our compliance team and come back with a definitive answer, rather than a technical workaround.

Can you confirm the contracting entity and where it’s registered? That’s the first thing they’ll ask.

I am sure this is not the answer you were hoping for.

I have confirmed with legal that we cannot serve customers using any technology, service, business, traffic, etc., from Iran, and US law also prohibits us from providing any service to entities and individuals domiciled in Iran.