ShoreTel

From VoIP.ms Wiki

This guide will cover the basics of getting your ShoreTel phone system working with a VoIP.ms SIP trunk. The ShoreTel documentation is not quite complete, although overbearing, so the purpose of this guide is a quick and dirty to get a trunk up and running and provide you with the couple of little config bits that the ShoreTel documentation lacks.

For this guide, I am using a fresh install of Server2008 with ShoreTel Server 14.2. Server 2008 will need SP1 applied, .NET Framework 4.5 installed, UAC disabled, and all other documented prerequisites fulfilled (SMTP, QWAVE, FTP, IIS, etc) for the installation of ShoreTel Server.

Once ShoreTel Server is installed, navigate to the Director homepage and log in with the default user/pass of admin/changeme

Steps:

- Config SIP profile
- Config trunk group
- config indiv. trunk

Configuring the SIP profile

Under Trunks -> SIP Profiles configure the SIP trunk options as shown in the screenshot. Give your profile a name (VoIP.ms in this example), and enter anything in the User Agent field; the field must be populated to continue, but its not actually used.

The Custom Parameters section is the key information which ShoreTel does not include in the built in documentation. RegisterUser defaults to BTN (BillingTelNumber), however this field ONLY accepts 10 digits with no special chars. We need to change this to RegisterUser=UserID, and we will fill in the UserID field later. The rest here is pretty basic, Register=1 causes the trunk to register with VoIP.ms, RegisterExpiration I have set to 60 seconds for NAT keepalive, otherwise inbound calls will fail once the firewall closes the ports.

Configuring the Trunk Group

Under Trunks -> Trunk Groups add a new SIP trunk group from the drop down list. A screen similar to below will appear. Before continuing, check to see that you have the ability to save the page; if the New, Copy, Save etc buttons are missing, and you have a message something to the effect of "Unable to modify the database, some ShoreTel services may not be running", you have likely forgot to install QWAVE. Unlike all the other pre-install requirements, the ShoreTel server install won't complain if QWAVE is not installed - rather it allows you to bang your head against the desk for a while at this stage trying to determine what service isn't running.

Give it a name (I simply used VoIP.ms again). Fill in the required username & password (your VoIP.ms account/subaccount information); this Username field corresponds to the UserID option in the SIP profile, above. Select the SIP Profile that you previously created from the dropbox, and set Digest-Auth to Outbound-Only. There are a few other required fields to be filled in on this page to continue such as local area code, etc. Complete and save.

Configuring the trunk

At this point, you should have already configured your hardware under Platform Hardware -> Voice Switches -> Primary. I am using a ShoreGear 220T1A hardware appliance. Configure your hardware as required, or you can use a virtual switch. I have never tried the virtual switch as there is additional licensing fees and I already had the 220T1A hardware on hand from a previous T1 installation.

Under Trunks -> Individual Trunks, create a new trunk in the trunk group you created above by selecting it in the dropdown box. Give your trunk a name, I used toronto3.voip.ms to signify which server this trunk is landing on. In the IP Address field, fill in the resolved address of the voip.ms server your DID is terminating on.... this is where I cringe. You CANNOT enter a friendly name here, which means no failover if this IP goes down hard (I don't know if this is a VIP for multiple servers on the VoIP.ms side?). In my small branch office, this is not an issue and I can quickly remap my trunk to a new IP, but if this is a critical phone system for you, you should investigate other ways to provide some redundancy here. At the time of this writing, toronto3.voip.ms resolves to 158.85.70.150, however it was only a couple of months ago or so (October 2015?) that we had an outage due to VoIP.ms changing IP's on us.