Plenty of customers choose to setup voicemail “send to email” functionality, so that the ShoreTel system emails the user when they receive an voicemail. The feature isn’t extremely well documented, so I will attempt to explain how it works to assist with the troubleshooting process.
- ShoreTel Director (SWD) receives a voicemail
- SWD looks up the MX records for the domain of the user
- SWD sends the voicemail notification (or WAV file) via SMTP on Port 25
If this is not working, I would check the following components:
- Verify that the SMTP server feature is installed on the ShoreTel Director (SWD) server
- Verify the user that wants to receive the email has the correct email address populated in their user profile within SWD
- Verify the user’s personal settings have send to email enabled
- Verify that SWD has DNS servers configured
- Verify that SWD can look up MX records for the user’s email domain
- You can check what results Director will receive by going to the CMD line and using NSLOOKUP to find the MX records. THIS article should help.
- Verify if mail is getting stuck in the queue: C:\\inetpub\mailroot\queue
- If you need to send voicemail directly to a mail server, then you can enable the IIS SMTP settings for SmartHost
- The receiving mail server should also provide some logs to identify if voicemails are being received
If you are using Google Apps integration, all you should need to do is enter the Gmail consumer key and secret into SWD and verify that SWD can successfully look up your domain’s MX record. If you make any changes, restart the SMTP service to verify all changes are active.
If you do not do daily backups on your 50V or 90V switches, these steps well allow you to backup and restore voicemails.
- On the ShoreTel Director server, go to the C:\inetpub\ftproot folder and edit the security permissions, so that “\Users” have Write permissions
- Log into Director web interface, and navigate to Platform Hardware–>Voice Switches–>Primary and click on the VM switch
- At the bottom of the page are backup options, enter:
- IP address of the Director server
- Folder name (it will create the folder)
- Username: anonymous
- Password: password (any password will work here)
- The “Daily Backup” box does not have to be checked (unless you want to do daily backups)
- SSH into the 50V or 90V switch with username “root” and password “ShoreTel”
- Log into the service cli with: svccli
- Backup all VM with: backupvm (this will create the folder specified and start copying all VM)
- You can also restore the voicemails with the command: restorevm
- Once you are done, edit the security permissions of the ftproot back to the original settings if desired
This should be performed when burnflashing a 50V or 90V, as a burnflash wipes the configuration (including IP information) on voicemail switches.
VMware Tools needs to be manually upgraded on the new ShoreTel Voice vSwitch or ShoreTel Virtual SA100. As these appliances are running linux, here is the article that VMware published:
I’ve already posted how to enable telnet and get to the shell for ShoreTel (non-V) switches here: danielkuchenski.com/2013/05/15/telnet-commands-for-shoretel-switches-and-shell-access/
Here are some more advanced commands that I have found useful for troubleshooting:
ifShow – Shows network interface information
lsp_ping “192.168.1.1”,100 – Tests LSP UDP connectivity to “192.168.1.1”, repeats 100 times
lspConList – Shows connectivity to other switches/servers
lspTelList – Shows all extensions known to switch
lspTelList1 – Shows detailed info for local extensions
lspTelList2 – Shows detailed info for remote extensions
reboot – Restarts the switch
routeShow – Shows the routing table
sip_debug_level=2 – Shows detailed SIP info on the console. sip_debug_level=0 is the default
**Note** Commands are case sensitive
More commands can be found in the ShoreTel release maintenance guides.
The ShoreTel VPN Concentrator responds to NTP requests (for remote IP phones), which makes it vulnerable to the NTP DDOS attacks that have been happening lately. To enable the WAN firewall on the ShoreTel VPN Concentrator (off by default) you must access a hidden menu.
- Log into your VPN concentrator, and click “Network” on the left-hand side
- Access the hidden firewall menu by changing the URL to page=5
- http://192.168.200.100/cgi-bin/config?page=3 change to:
- Check the box “Enable WAN Firewall“
- CHECK THE BOXES TO ALLOW HTTP & HTTPS ACCESS THROUGH FIREWALL
- This allows you to manage the concentrator via HTTP or HTTPS
- Press submit (All current VPN sessions will drop for ~30 seconds)
- The concentrator will be unresponsive for 30-60 seconds while it applies, and you are done!
From a ShoreTel phone, you can ping, view configuration, etc directly from the phone:
For each operation, you press MUTE and then hit the number + #:
Press MUTE then 7464# (PING)
CLEAR CACHED VALUES:
Press MUTE then 25327# (CLEAR)
Press MUTE then 73738# (RESET)
Press MUTE then 73887# (SETUP)
Press MUTE then 4636# (INFO)
Press MUTE then 772667# (RRAMOS), then press 1234 as password and confirm.
**NOTICE** Changing these settings can impact your ability to make/receive calls, do not change unless instructed by ShoreTel TAC.
With that said, hopefully this information can be useful if you have a similar situation:
I had two ShoreTel sites within the same area code, HQ site had the PRI, and the Remote site had an analog trunk to be used for primary 911 and secondary voice failover (if the network connection failed between both sites or the PRI went down). The tricky part was having the ShoreTel system prefer the PRI at HQ ONLY for normal voice calls, even though there was a local analog trunk at the Remote site. The ShoreTel system still needed to to prefer the local analog trunk for 911 calls.
Least Cost Routing can only be changed on the Director through the Support Entry mode, accessed by hold Ctrl + Shift and clicking on the “U” in Username. Then login using your normal admin credentials.
Verify that “Parent as Proxy” is not checked (PaP allows normally unroutable calls out the Parent site, like 911, which we don’t want in this scenario)
Navigate to the PRI trunk group, and at the bottom of the page, there is “Trunk Group Dialing Rules”. Click “Edit” and add “;2E;-26A” without the quotation marks. Click “Save” and wait about 2-3 minutes for the changes to take effect and test failover and 911!
ShoreTel AD integration is pretty simple, just a couple of important steps to remember:
1. To use AD integration, check “Enable AD Integration” under System Parameters -> Other
2. ShoreTel is a top-level LDAP reader, so you do not need to specify certain OUs. Your LDAP string should look like this:
3. At least one system administrator account has to be AD enabled for ShoreTel to use and perform LDAP lookups. To use the “Test” or “Sync” buttons on an AD enabled user, you must be logged in with an administrator account that is AD enabled.
Great informational article regarding ShoreTel TMSNcc logs: http://www.netdungeon.com/articles/how-decipher-tmsncclog
Call Code Parameters:
||Call Creation Event
||Leg Create Event
||Follows a C-CE; Internal Transfers
||Leg Info Event
||Provides information on other parties in the call.
||Call State Event
State of call in progress; RingBack, Offering, etc.
||Leg State Event
||Follows a C-SE to inform the leg state changes.
||Leg Destroy Event
||Call tear down; Leg is destroyed.
||Call Destroy Event
||Call Destroyed by user or system hung up.
||Media State Event
||Media states for the terminated call leg.
Example from the article linked above:
|Trunk Call Leg To PSTN
|Internal Call Leg
|PBX Responding to Party
(s:1, r:378, l:0),(j:0,u:0,o:0)
The above packet information lists sent and recieved packets, and jitter. This is very useful in understanding why calls fail. In many cases we will see issues with jitter readjustments during problem or dropped calls. The s:1 indicates 1 packet was sent, the r:378 indicates 378 packets were recieved. The second set of parentheses (j:0,u:0,o:0) describes the jitter buffer, and in this case was adjusted 0 times. This is more of an ideal scenario as problem calls will vary in their jitter and packet amounts.
To connect to a V switch, you do not need to enable telnet from the Director server, but you do need to connect via SSH. If you connect directly to the console, remember to set your speed to 19200.
Login with username/password: root | ShoreTel
Enter svccli and then getsvcstatus to verify services are running. You can start services manually with startsvc *
To get back to the shell, type “q” and hit enter
Type date and press enter to verify NTP is working correctly. If the date is off, resolve your NTP issue, since certain services will not start without NTP working properly.
To enter the ShoreTel menu, enter stcli
Reference : http://customers.btxchange.com/Manuals/ShoreTel/ShoreTel%20V%20-%20Voicemail%20Switches.pdf