Modular Messaging TTS and Antivirus Port Blocking

[Stinney]

We discovered that when new mailboxes are being created in our Modular Messaging system that the text-to-speech is not converting the subscriber name and the system is playing the mailbox number instead. The system is supposed to play the user's name until the user records their own name or personal greeting.

Found this Avaya support article: SOLN152828

Explains that this is being caused by a recent McAfee update which blocks TCP port 6666.

Document can be found here:

https://support.avaya.com/ext/index?page=content&id=SOLN152828&group=UG_ENTITLED_CUSTOMER

We don't use text-to-speech for anything else like fax or email, so we didn't know it was an issue until recently.

If you go to your MAS server and run C:\Avaya_Support\Monitor.msc check for 1018 errors.

I'll let you know if it fixes the problem after we make this change.

- Stinney

I love learning and passing on knowledge. "Because knowing is half the battle".... GI JOOOOOE!

 

[texeric]

That's a pretty well known issue discovered years ago. That port was/is a known IRC chat port that other AV software makers also blocked, McAfee was just more well known to block it back then.

 

[Stinney]

Interesting then, that it never was an issue for us until recently. The article I found also had an April 2013 date as if it was new. But stranger things have happened. Thanks for the information on why it was blocked by the antivirus.

- Stinney

I love learning and passing on knowledge. "Because knowing is half the battle".... GI JOOOOOE!

 

[texeric]

knowing is half the battle......

 

[Stinney]

So, this didn't resolve the issue Avaya is looking into it. Anyone got any ideas on why the system stopped playing the TTS names of mailboxes and now says to leave a message for extension xxxxx?

- Stinney

I love learning and passing on knowledge. "Because knowing is half the battle".... GI JOOOOOE!

 

[Stinney]

Well, back to the security/server group with this, it is McAfee blocking port 6666 (found it in the McAfee logs). It's also blocking port 6669 that vserver.exe is trying to use.

- Stinney

I love learning and passing on knowledge. "Because knowing is half the battle".... GI JOOOOOE!

 

[Stinney]

Correction: port 6668

- Stinney

I love learning and passing on knowledge. "Because knowing is half the battle".... GI JOOOOOE!

 

[Stinney]

Okay, so we had to add the program files: vserver.exe and ttsservice_server.exe to the exclusion list specific to the IRC port blocking. Once we added them *ahem* correctly, it started working again.

- Stinney

I love learning and passing on knowledge. "Because knowing is half the battle".... GI JOOOOOE!