|TCP/TLS Proxy||tls.l2access.com.au (port 5061)|
|SIP Registration||126.96.36.199 (phone.yourcloudtelco.com.au)|
|SIP Port – UDP||5060|
|SIP Port – TLS||5061 (ensure transport = TLS)|
|Firewall IP Range||188.8.131.52/24|
|RTP and UDPTL||Set by your router (our port range is 30,000 – 40,000)|
Overview of our physical setup
We maintain two geographically separate but identical data centers at Equinix Sydney’s SY1 and SY3 co-location facilities connected by private fibre.
Our voice infrastructure is configured in an active / passive modes while all other systems, including billing operate in an active / hot-standby mode meaning the loss of anyone part fails over to its alternate, in part or in full. If we lose the primary voice service, while the call will drop, our network will fail over to its alternate within a few seconds allowing either caller to quickly reconnect the call. While we rely on virtualization for a number of supporting systems, our core voice applications operate on their own bare metal instances.
We connect directly with all our upstream carriers via fiber xConnects into our Equinix SY1 and SY3 data centers and therefore DO NOT use the public internet to connect with any direct carriers.
For customers connecting over the public internet, we advertise our assigned IP via BGP using Vocus IP transit. Publicly customers will only ever need to connect to our 184.108.40.206 proxy, which we internally manage within our network. Because Vocus have direct peering with all the primary Australian ISPs’, we minimise the number of hops between networks to ultimately reach our Equinix datacentres.
Direct Cross Connect
For our Wholesale and Enterprise customers wanting to connect directly into one or both data centers we can support a combination of copper or fiber connectivity. While we do not charge customers to connect to our infrastructure, customers will need to arrange with Equinix to bring the physical connection into our racks. Equinix monthly charges will apply (see below for rack details).
- SY3:01:050010:0141-A (Colo 5)
Megaport enables us to reach more service providers and customers via the shortest network path without the restriction to the 4 walls of our data-centres or the uncertainty of the public internet.
In Australia they’ve got a surprising number of service providers and enterprise customers. In our case within seconds of enabling a Megaport XC we saw traffic from customers and wholesale partners as they routed away from our own Vocus internet transit.
We’re now on Megaport meaning we advertise our assigned IP via BGP on the Megaport fabric. If considering direct cross connects into our DCs we’d recommend a quick call with your Megaport sales person.
If you connect using the IAX2 protocol then you should ensure that your IAX2 peer settings are set to:
- IAX2 peer/host: iax.yourcloudtelco.com.au
If you have entered any fixed IP addressing into your IAX2 device or firewall rules you will need to update these to our new IP address range. This is as follows:
- SIP Proxy/Host: 220.127.116.11
What’s the difference between UDP & TCP
UDP and TCP SIP are both used to send data over the Internet or a local network with UDP being older but more common protocol and TLS the more modern & preferred protocol for companies like Microsoft. UDP has no error checking to speak of with no regard to the order or reliability of the data. TCP is all about reliability — packets sent with TCP are tracked so no data is lost or corrupted in transit.
We support both TCP and UDP.
Real Time Protocol (RTP)
RTP is the protocol used to deliver audio and video over IP networks. RTP uses the UDP protocol because its efficient in low quality networks such as phones communicating over the public internet. (NB – while your router sets the specific RTP port, we will accept communication between the 30-40k range).
We support TLS connections from devices that support this protocol for deployments that require increased security. You can use call.sipcity.com.au as your proxy/host but set the transport to TCP via 5061.
We support Secure RTP connections from devices that support the protocol. SRTP allows for secure transmission of the media/audio stream for deployments that require increased security.
Do we support QoS?
Yes; while we support QoS for our direct Cross Connect customers and partners, Australian ISPs by default remark QoS rules as Best Efforts over the public internet.
From our side we mark our SIP/RTP Voice Services with the following QoS rules up to our IP transit provider:
- SIP is marked as DSCP value of AF31
- RTP (media) and Fax payload is marked as DSCP value of EF
- All other traffic – web portal access etc is marked as DSCP value of Best Efforts
NB – IP phones as trusted end points by default will usually mark the packets correctly, however when connecting via switch ports on a Cisco for example you’d normally need to enable following interface: mls qos trust dscp.
Telstra NBN Services
Telstra are blocking all class of service (QoS) on their NBN services which will prevent Registration or Peering to our platform. To enable registration on a Telstra NBN service simply disable DSCP (see below).
Set IP DSCP (overrides IP ToS) to a value of 0.