Skip to main content

Google Voice - it's rather cool

We have just started moving over to Google Voice in Trust schools. This is to replace the existing telephony systems. If you are a G Suite organisation, then its a really cool solution and works very well.

If you didn't know, this is a cloud-based solution and you users can use their Voice number on any device, anywhere - not just the physical desk phone (entirely optional) sitting at school. You have integration with all of the other G Suite tools - especially Calendar and Meet. Basically read all about it here. I'm not going to duplicate the Google blurb - but go through a few things to be aware of.

Cost

  • Voice licences come in at around £8 per month. Each user who needs a Voice number needs one and every physical handset is associated with a user.
  • Handsets - you have to use the Polycom handsets - VVX150's start at around £75. Remember you can use Voice on any internet-connected device - so these are strictly optional. You can see the full range of handsets here.
  • Calls to Voice numbers are free - others are £0.01 per minute.

Admin Setup

  • This is all done in the G Suite admin console and follows these basic steps:
  • Initiate number Porting. You want to keep your old number? This takes about 3-4 weeks - so kick it off and set you switch over date.
  • Enable Voice as a service for the users who are going to use it.
  • Add a Voice licence to the users who are getting numbers.
  • Create locations. You need to specify the address of your site or sites as you will need to specify a location when assigning a number to a user. This is also used to determine what the local number code will be for the user.
  • Assign a number to each user - you can pick a local area number.
  • Create an auto-attendant to hand incoming calls.
  • Assign the ported number to the auto-attendant.
  • Create ring groups if required - these can make multiple handsets ring at once and other things.

All of the above is very easy and all point and click. You can have a large site set up very quickly. Now the harder bit - physical handsets!

Handset Setup

I've so far provisioned the handsets offsite at a location I know works well with Google Voice. You should get the OBI edition handsets. We did not - our ones came with the SIP firmware. This means you have to firmware flash each phone. So our phone provisioning went something like this:
  • Add a desk phone in the management console. To do this you need the MAC address of the phone written on the back of the phone. You also need to give the handset a name and assign it to a user. then stick a label on the phone so you know which is which.
  • Plug the phone into a POE port and let it boot up. If it has the correct firmware on it, then it will reboot a few times and come up with the name of the user after a while. If not you need to flash it.
  • On your DHCP server look up the IP address of the phone (they say Polycom in the hostname - so easy to find).
  • Go to the web interface https://phone ip
  • Enter the default password: 456
  • Navigate to the firmware update menu and select custom.
  • Paste in the following URL into the box: https://www.obitalk.com/VVX-OE/6.3.1.1/release.xml
  • Click check for updates. You will see one.
  • Apply the update and wait - the phone will reboot a few times and show the username of the assigned user after a while.

Physical handset deployment

  • You need a POE data outlet. The phones have a passthrough port for a computer if you are short of ports.
  • Scope the site before you install and confirm there is a data outlet and if not, how you are going to get one to where the phone is meant to be. You might need a bunch of POE injectors if they don't have POE switches. af standard is fine as the phones use less than 15W.
  • Ensure the network will support the requirements - these are detailed here. Depending on the site, I've had to put phones on DHCP reservations and exclude from filtering.

If after all that, you have succeeded, you will be greeted with lots of green happy phones on the management console:





Comments

  1. How many phones are you deploying? Are you replacing classroom phones as well? What about emergency calls when God forbid internet goes?

    ReplyDelete
    Replies
    1. Varies by site. 6 in a small primary - 18 in a bigger one. We have put some in classrooms. Voice works on any device - so you can make calls on mobiles phones - so you can use you school numbers even if the school burns down.

      Delete
  2. Hi Roger,

    Are you using this phone system primarily or do you have something in addition to this. My concerns with Google Voice is that it is not very feature rich in comparison to other phone systems ie

    No Hunt groups
    Doesn't have the ability to allow calls at certain times only Avaya call them time profiles)
    How do you transfer calls?

    ReplyDelete
    Replies
    1. Primary phone system.

      We have found its features are far more extensive that other systems and definitely compared to what we have replaced. It also ties in nicely with G Suite. You have to be a G Suite org for it to make sense.

      Hunt groups from a quick Google = Ring Groups in Google Voice - so for example we have things like press 1 on the auto attendant > makes two phones ring > if they don't pick up > another phone rings etc - can be as elaborate as you want and dead easy to do.

      You link active hours to your Google Calendar.

      Transfer calls - on a Polycom handset press the transfer call button or on the web/app press transfer call - not much too it really. Much the same as any other system I've used.

      Delete

Post a Comment

Popular posts from this blog

Delete a specific email using GAM

If a user send an inappropriate email to a loads of people or get stung by some sort of email exploit you can quickly delete the email from all of the recipients using a GAM command. Step 1 - get the email header Go into Google Vault and search for the offending user or someone known to have got the message. Click show details and grab the email ID. This will be a long string of characters followed by @mail.gmail.com Step 2 - find out who has the email Go into Google Vault and find the original message sent by the offending user. Look at the details to see who got it. Copy the list and dump it into a spreadsheet. Clean up to just a list of emails with a column header 'mail'. Save as a csv file. Step 3 - delete messages with GAM Put your CSV file in your GAM folder - this e.g. assumes its called mail.csv Run: gam csv mail.csv gam user ~mail delete messages query rfc822msgid: MESSAGEIDHERE doit The alternative nuke option is: gam all users delete messages query rf

Adding subdomains to G Suite

This is how I add subdomains (so basically new schools) to out G suite setup. I've got these steps documented on a scruffy set of notes that I've now got in Keep - so time to document them - for myself as much as anyone else! Steps in order (roughly) Add the new domain Verify the new domain Add MX records to hosting Add SPF record for Google to hosting Turn on email authentication Add DMARC record to hosting Setup custom Directory and restrict students OU to this. Create an admin quarantine for the domain. Configure SPAM setting for the domain. Turn on and off services as appropriate. Map a blank Google Site to the naked domain - if required. Setup some basic groups - allstaff, allusers (for directory) and students with appropriate permissions. Deploy custom wallpapers. So the steps in a bit of detail: Add the new domain & Verify ownership Click on Domains in the admin console: Add/remove domains followed by "add a domain" At this

My favorite GAM commands - well a few of them at least!

Where would be without GAM? Paying for expensive syncing tools or doing tedious manual tasks in the admin console. GAM can automate most things you might want to do in G Suite. So these are a few of my favourite commands - one I use either as part of a batch file - or just standalone. There are loads more - but these are ones that are used daily. Classroom Create a spreadsheet of all your domains classes -  gam print courses todrive Create a spreadsheet of a teacher's classes:  gam print courses teacher fred@mydomain.com todrive Bulk create classes: gam csv classes.csv gam create course alias ~alias name ~alias section ~subject teacher ~teacher status ACTIVE where classes.csv is a list of classes you want to make. Add teachers: gam csv teachers.csv gam course ~alias add teacher ~teacher Add students: gam csv students.csv gam course ~alias add teacher ~student Sync Students (in this example to a group - but could be an ou/csv file) gam csv groups.csv gam course ~g