Shoretel

Shoretel Call problems with Juniper SRX 220

Posted on Updated on

Symptoms:

  • Calls to a workgroups on a different Shoretel site drops after few seconds or times out
  • Calls to an ACD queue times out
  • Call transfers don’t work
  • Phones behind Juniper SRX 220 had same issue as above when registered to a Shoregear on a different site.
  • Regular extension to extension calls work just fine

Setup:

  • Phone and Shoregear switch is behind a Juniper SRX 220
  • Shoregear is on a different VLAN as the phones

Findings:

  • We have worked intensively with Juniper support and what they figured out is that ALG MGCP is not correctly allowed within the Juniper SRX 220.  SRX isn’t handling the second MDCX connection for complex calls as expected. If the Shoregear is on the same VLAN as the phone, then the problem goes away.  However, there are instances where you need the Shogear to be on a separate VLAN especially when you have a multistory building and you only have 1 shoregear at the whole site.  Or if there is a Shoregear failure and you have to register the phones to a different site.

Workaround:

  • As of the time of this post, Juniper is still working on a fix.  But the workaround is to disable MGCP and allow MGCP related applications on the firewall.

#Disable MGCP

Set security alg mgcp disable

#Clear MGCP Sessions

clear security flow session application mgcp-ua

clear security flow session application mgcp-ca

#Allow MGCP traffic

[edit security policies from-zone trust to-zone untrust policy TR-UNTR-MGCP]

set match source-address NET-LOCAL

set match destination-address any

set match application junos-MGCP

set match application junos-MGCP-CA

set match application junos-MGCP-UA

set then permit

[edit security policies from-zone untrust to-zone trust policy UNTR-TR-MGCP]

set match source-address any

set match destination-address NET-LOCAL

set match application junos-MGCP

set match application junos-MGCP-CA

set match application junos-MGCP-UA

set then permit

 

 

 

Shoretel IM (Instant Messenger) presence not showing in Outlook 2013

Posted on Updated on

Hi there,

I recently just reimaged my PC due to issues, and after installing Outlook 2013 and Shoretel Communicator, I noticed that my IM presence is no longer showing.

Here are the things that worked for me:

1.  Under HKCU\Software\IM Providers, the DefaultIMApp was set to Lync, and I had to change it to Communicator.  Try re-launching Outlook and see if it works.

2.  If IM presence still does not show, under HKCU\Software\IM Providers\Communicator, check and make sure the UpAndRunning value is set to 2.  You may have to toggle from 0 and back to 2.

Shoretel Voicemail notification setup

Posted on

There are several ways to enable voicemail notifications via email in Shoretel.

Here are the things you will have to set on the user profiles:

1.  In Shoreware Director, Administration, Users, Individual Users; on each of the user profiles, specify the user’s email address in the General Tab.

2.  Under the General tab, click the link for ‘Escalation Profiles and Other Mailbox Options’ and specify the user’s email address and ‘Deliver Message as Email’ option.

Here are the settings for the server:

1.  Under Voicemail, Options; specify the ‘From Address for Email Notifications’

2.  If you are using a Voicemail switch, go to Sites and open your Headquarters Site.  And then specify the SMTP relay which is your Exchange server address or your smart host.

3.  If you are using your Shoretel server for voicemails, login to your server and open IIS6.0.  Expand your server and right click on SMTP Virtual Server and select Properties.  Under the Delivery tab, click Advanced and enter your Exchanger server or Smart Host address under Smart Host.  You will have to restart IIS after making the changes.  The voicemails will be saved in the queue folder under C:\inetpub\mailroot as they are being sent.