Skip to content

Solutions

Unified communications

Subnet designs and supports business calling, meetings and contact centres for South Australian organisations, with Microsoft Teams calling at the centre.

Since 2006

designing and supporting business phone systems

Since 2022

delivered on the Access4 platform

40+

Teams projects

WHAT WE DELIVER

Calls, meetings and customer contact in one plan

These are the parts Subnet delivers, and the technology we use for each.

Microsoft Teams calling interface with dial pad and call history

Calling

Microsoft Teams calling

External calling inside Microsoft Teams, so calls, chat and meetings share one app and one directory.

What it solves

  • Paying for Teams and a separate phone system
  • A phone system at end of life
  • Staff tied to a desk phone

How Subnet works with it

We confirm licensing, port numbers and build call flows with your reception staff.

Phone system

Hosted voice

A cloud phone system with handsets and apps for sites and roles where Teams is not the right fit.

What it solves

  • Sites without Microsoft 365 licences
  • Shared areas and counters
  • Copper and ISDN lines being withdrawn

How Subnet works with it

We mix hosted voice and Teams calling in one design where that works better.

CC4Teams contact centre interface on a desktop display

Customer contact

Contact centre

Queues, wallboards, reporting and CRM integration for the people who answer customer calls.

What it solves

  • Calls going unanswered
  • No view of who is waiting
  • Callers asked to repeat who they are

How Subnet works with it

We set up queues and reporting around your team and tune them with real data.

Two people discussing work beside video-conferencing equipment

Rooms

Meeting rooms and devices

Headsets, handsets and meeting room systems certified for Teams.

What it solves

  • Meeting rooms with poor audio
  • Not knowing which devices work with Teams
  • Remote attendees left out

How Subnet works with it

We recommend by room and role, install and show people how to use them.

WORK WITH SUBNET

How a communications project runs

1. Assess

We audit lines, numbers, devices and call flows.

2. Design

Call flows, numbers and devices are agreed at a fixed price.

3. Deploy

Numbers are ported in a planned window with staff trained first.

4. Manage

Changes are handled by our service desk.

5. Review

Call reporting is reviewed and call handling tuned.

WORK WE HAVE COMPLETED

Unified communications work by sector

Local government

A full Teams calling rollout for a regional council, including handsets, call reporting and fax services.

Not-for-profit

A new Teams phone system replacing a legacy platform.

Health and community services

Cloud phone systems for multi-site providers, with link upgrades to support voice quality.

YOUR QUESTIONS

A LITTLE MORE CLARITY.

Who sets up business phone systems and Microsoft Teams calling in Adelaide?

Subnet does. We are based in Forestville, Adelaide, and have designed and supported business phone systems for South Australian organisations since 2006. Since 2022 our voice services have run on the Access4 platform, with Microsoft Teams calling as the main focus, alongside hosted voice and contact centre options.

Do calling and meetings have to be decided together?

Not necessarily. Phone calling, online meetings and shared room systems are licensed and connected in different ways. Microsoft’s service description says calling to the public phone network in Teams needs a Teams Phone licence and a connection through Calling Plans, Operator Connect or Direct Routing, while room systems have their own licences. Start with what each team needs from calls, meetings and customer enquiries, then agree which parts are bought together and which are scoped separately.

Do shared numbers such as reception need their own licences?

Often they do. Microsoft’s service description says each Teams Phone resource account needs a Teams Phone Resource Account licence, and shared numbers handled by services such as auto attendants and call queues commonly run on resource accounts. List every shared number you rely on, including reception, after-hours and department lines, so the licences are identified and priced at the start. Whether any are included depends on the agreed proposal.

What should we check on our existing lines before retiring a legacy phone system?

nbn says some business Special Services delivered over copper, including ISDN, are subject to disconnection, with dates that vary by service type, location and provider product exits. Not every service is affected, and migration is not automatic: your provider has to place the order. Review the services and invoices at each location, ask your provider for the expected date and note which products sit at which site. Then plan the changeover so it is not left until a line is about to be switched off.

Who is responsible for lift phones, alarms and similar devices on old lines?

For copper lift emergency phones and monitored fire alarms, nbn says the owner or manager of the equipment is responsible, not nbn. Ask your lift or alarm provider what options exist before the copper service is disconnected, and ask your phone and internet provider about the connection. After migration, have the device tested. Useful questions include whether it works on nbn, whether it can call out in a power outage and what it costs. Put these on the changeover checklist.

Can people outside our organisation join our meetings?

Yes, in many cases. Microsoft says anonymous join is allowed by default, and administrators can control it through meeting policies for specific organisers, with lobby settings deciding how outside participants enter. Teams Premium adds an email code check for anonymous attendees. Anonymous participants have limits, such as no access to meeting chat before or after. Decide who may host meetings with outsiders, what lobby rules apply and whether verification is needed, noting that policy changes can take up to 24 hours.

Can we record calls and meetings for compliance?

Microsoft supports policy-based compliance recording of Teams meetings, calls and call queues through certified third-party recording solutions, with a recording policy assigned to the users concerned. It lists exclusions, including emergency calling and users in survivable branch appliance mode. Whether recording is required or allowed for your organisation is a legal and policy question to settle first. Agree who provides the recording service, who can access recordings, how people are notified and how long recordings are kept.

What happens to calls if our internet connection fails?

It depends on the design. Cloud calling relies on connectivity unless resilience is planned. For Direct Routing, Microsoft describes an optional survivable branch appliance that can keep outside calling working at a site that loses its internet connection but can still reach its local session border controller. It supports a limited set of call features, works on particular desktop clients and does not share location for emergency calls. Decide per site what must keep working, then test the fallback before go-live.

Where is our Teams call and meeting data stored?

Microsoft says Teams data resides in the geographic region associated with your Microsoft 365 organisation. Microsoft’s February 2024 documentation said Australian country-level residency applied to new tenants, with existing Australian tenants’ Teams data in its Asia-Pacific region; check the current arrangement for your tenant. You can see your tenant’s data location in the Microsoft 365 admin centre under Settings and Organisation profile. Microsoft’s documentation covers which data types are included, so if a funder or regulator sets location requirements, have them checked during scoping.

Will moving calling and meetings onto one platform lower our costs?

Not automatically. Compare licence, connectivity, device and support costs against the current setup, then confirm included features, contract terms and migration costs before assuming consolidation will reduce spend. Include costs that sit outside the platform, such as phone-network connections, handsets and headsets, room equipment and any overlap while old services keep running. Ask for each cost to be shown separately in the proposal.

BEFORE WE TALK

A useful starting point.

You do not need a finished technical brief. Start with the outcome, what you know today and the questions you need answered.

  • What outcome matters to your organisation?
  • Which users, applications, systems and risks are involved?
  • What would a practical first step look like?
Discuss these priorities

LET’S TALK

WHAT WOULD YOU LIKE TO DO NEXT?

Tell us about your organisation and what you need. Start a conversation, discuss a project or request a meeting.

Prefer to talk?(08) 7127 9400Already a customer and need help? Go to Support.
PROPOSED FORM · PRIVATE PREVIEW ONLY

Preview only. Nothing is sent, stored or booked.

A live version will need final routing, consent and privacy review. Subnet privacy policy

Contact us