SIP Protocol Details

Supported Network and Transport Protocols

DIDWW supports SIP signaling over UDP, TCP, and TLS transports. Communication can be established using the following ports: 5060 for UDP/TCP and 5061 for TLS. Both IPv4 and IPv6 are supported as network protocols for signaling and media.

Signaling Endpoints

Calls can be sent to any of our load balancers. Each load balancer operates as a redundant cluster with multiple nodes that uses the same IP address.

Location

DNS A/AAAA record

LB IPv4 address

LB IPv6 address

New York

nyc.us.out.didww.com

46.19.209.44

2a01:ad00:1:1::44

Los Angeles

lac.us.out.didww.com

46.19.212.54

2a01:ad00:4:2::54

Miami

mia.us.out.didww.com

46.19.213.54

2a01:ad00:5:2::54

Frankfurt

fra.eu.out.didww.com

46.19.210.19

2a01:ad00:2:1::19

Singapore

sg.out.didww.com

46.19.214.54

2a01:ad00:6:2::54

DNS SRV

DNS SRV acts as a failover mechanism that is used to reroute a call to a backup data center in the event of failure. We recommend enabling this feature if it is supported by your equipment.

DNS SRV record

Priority

Weight

LB IPv4 address

LB IPv6 address

LB Location

Role

nyc.us.out.didww.com

10

10

46.19.209.44

2a01:ad00:1:1::44

New York

Primary

20

10

46.19.213.54

2a01:ad00:5:2::54

Miami

Backup

lac.us.out.didww.com

10

10

46.19.212.54

2a01:ad00:4:2::54

Los Angeles

Primary

20

10

46.19.213.54

2a01:ad00:5:2::54

Miami

Backup

mia.us.out.didww.com

10

10

46.19.213.54

2a01:ad00:5:2::54

Miami

Primary

20

10

46.19.209.44

2a01:ad00:1:1::44

New York

Backup

fra.eu.out.didww.com

10

10

46.19.210.19

2a01:ad00:2:1::19

Frankfurt

Primary

20

10

46.19.209.44

2a01:ad00:1:1::44

New York

Backup

sg.out.didww.com

10

10

46.19.214.54

2a01:ad00:6:2::54

Singapore

Primary

20

10

46.19.212.54

2a01:ad00:4:2::54

Los Angeles

Backup

BGP Anycast

We also providing BGP anycast signaling endpoint any.out.didww.com (185.238.172.4). Anycast prefix 185.238.172.0/24 announced from all our Points of Presense and BGP protocol will automatically provide best path according to customer AS connectivity.

Warning

Sometimes best BGP path is not actually best from latency/quality point of view. We recommend to test anycast endpoint in your environment before production use.

Note

It is recommended to use UDP transport within any.out.didww.com endpoint - this tecnhology works better for UDP services.

RTP and RTCP information

DIDWW uses the following Subnet and Ports for RTP traffic: 46.19.208.0/21, 16383 - 32767. RTP port + 1 is used for RTCP sending/receiving.

Encryption

Our systems supports TLS as a secure transport for SIP signaling and SRTP as a media encryption mechanism. All three SRTP key negotiation mechanisms are supported - SDES, DTLS and ZRTP.

Warning

The SRTP media encryption is disabled by default. Please contact our sales team sales@didww.com to enable SRTP support for your account.

Codecs

  • g.711 alaw/ulaw

  • g.729

  • g.723.1

  • gsm

  • telephone-event

P-Charge-Info Header

Customers can append additional technical information using the header described at https://tools.ietf.org/html/draft-york-p-charge-info-08. Our system will store P-Charge-Info value to the CDR, later this data could be used for billing purposes with CDR streaming tool. Header value format is optional.