What are the generic SIP settings for connecting a SIP compliant device to your service?

What are the generic SIP settings for connecting a SIP compliant device to your service?

Customers with their own SIP enabled phone, gateway or PBX are free to use this to connect to Tech Connections Internet's service. The device must be SIP v2 compatible. Refer to the settings below for a guide to how you should configure your device to connect to the Tech Connections Internet service.

 

Username/Login/User ID: Your Tech Connections Internet Phone Number inc. area code (e.g. 092420000)
Authorisation Name/Display Name: Your Tech Connections Internet Phone Number inc. area code (e.g. 092420000)
Password: Your Tech Connections Internet Password (assigned at signup)
Host/Proxy/Domain: sip.techconnections.co.nz  (or sip.techconnections.co.nz:50600)
Outbound Proxy: sip.techconnections.co.nz  (or sip.techconnections.co.nz:50600)
DTMF Mode: rfc2833 (or AVT/out of band)
Default voice codecs: G.711 alaw, G.711 ulaw, G.722, G.729a.  Please use a 'ptime' of 20ms for your media.  The lower ptime of 10ms is not supported.
Default video codecs: H.264, H.263
SIP Transport: UDP, TCP or TLS (TLS preferred)
SIP port: 5060 or 50600 (udp, tcp) or 5061 (tls)
STUN Server: stun.techconnections.co.nz (port 3478)
Firewall Rules: Allow all traffic from subnet 103.212.52.0/24  (UDP portrange 1024-50000, TCP port 5060 and 5061).

Troubleshooting

If you are having problems registering your phone or PBX with our service then this may be due to a SIP ALG (Application Layer Gateway) on your router or firewall interfering with the SIP traffic or blocking it in some way.  It may also be a firewall issue.  We recommend in this case to try and use 'TLS' as your SIP transport (rather than the usual default of UDP).  This will switch the traffic to an encrypted port which will effectively hide the SIP traffic from your network equipment.

If you do not have TLS transport as an option on your device then another work around is to switch the port number you use to register to us to be 50600 (instead of 5060) - this again can avoid ALG related problems since the port is unknown to the router as a SIP port.  Usually the port is set on the end of the Outbound Proxy/Proxy address (e.g. sip.techconnections.co.nz:50600) but can sometimes be in a separate 'port' field.  Do not confuse your own SIP port with the one you are connecting to on our side.  If in doubt contact support@techconnections.co.nz for assistance.

    • Related Articles

    • Tech Connections generic SIP settings for connecting a SIP compliant device to our service

      Customers with their own SIP enabled phone, gateway or PBX are free to use this to connect to Tech Connections's service. The device must be SIP v2 compatible. Refer to the settings below for a guide to how you should configure your device to connect ...

    • Disabling SIP Application Layer Gateway (ALG) functionality

      If you are experiencing one way voice particularly on incoming calls the most probable cause is SIP ALG. While originally designed to resolve a NAT related problems, with no standard implementation many routers and software based firewalls corrupt ...

    • Receiving silent or 'ghost' calls on your SIP phone

      Some of our users complain that they receive unwanted or ghost calls on their VOIP phone lines where they pick up the phone and nobody is there and this might happen several times a day or week. The first thing you should do is check the Tech ...

    • SIP Registration, Peering and IAX2 explained

      Tech Connections supports SIP registration, SIP peering and IAX2 registration to connect your VoIP service. SIP Registration The simplest of the three connection types “Registration” is used to connect IP phones and some IP-PBX machines to our hosted ...

    • How to setup a SIP trunk

      SIP trunks are typically used to connect a PBX to Tech Connections Internet such as an Asterisk or 3CX PBX to our platform. Tech Connections Internet make connecting a PBX simple by allowing a different type of connection profile which we call a ...