Multiple language greetings, can record under optional greetings but cannot play

[rejackson]

I set up my mailbox for english and dutch. It gives the caller the option for english or dutch but plays the main personal greeting with both selections.

There is no option under the main greeting to record both languages so I tried the optional greetings. They let you record a greeting in each language and I set up a rule to paly them internal, external, all calls, but I cannot get them to play.

I am not sure what this means in the TUI guide. I dont find any specific feature to enable or disable called Call Handling.

● Optional greetings
Use your mailbox as a personalized answering system by recording optional greetings. You
can set up rules that determine which optional greeting a caller hears based on call type
(internal, external, or both), time of day (during business hours, out of business hours, any
time), and if your extension is busy, not answered, or both.

Note: You can use optional greetings only if Call Handling is supported by your
telephone system and the system administrator has enabled Call Handling for
your mailbox.

The only way I have found to use multiple languages on a mailbox is to delete my greeting and it uses the recorded name with the language prompts.

 

[rejackson]

I finally found the Call Handling feature in the MM COS settings. Looked there several times before I found it. It is on, so I still dont know why the optional greetings do not work.

 

[KenMeans]

what software level is the system on ?

Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

 

[rejackson]

The MM is 5.2.1, the CM is 3.1.5

 

[KenMeans]

are the optional greetings set to play under what call types ?


Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

 

[rejackson]

I created a rule that they should play for internal or external calls. When that didnt work I tried the other options number engaged and not answered. Still no change.

Now that I found call handling defined in the MM COS I have been looking for a similar feature in Communication Manager and have not found it yet.

 

[KenMeans]

you got love this. I have never been able to get any modem to work right on a S8730 so i would try a different type of modem but the one on the MSS is going to be a real pain.

PSN # PSN002512u
Original publication date: 10-Aug-09. This is Issue #01, published date:
10-Aug-09.
Severity/risk level Medium Urgency When convenient
Name of problem MT9234ZBA-USB modem lockup issues in APAC on Modular Messaging Message Application Servers.
Products affected
Modular Messaging (MM) 4.0, 5.0 and 5.1
Problem description
The MT9234ZBA-USB modems can lockup and cause a grey screen when accessing the systems with Microsoft Remote Desktop
both through the modem connection or across the network.
Resolution
Avaya and the modem manufacturer do not have a resolution for this issue. If this issue is encountered, the customer or Business
Partner should source a modem locally.





PSN # PSN002143u
Original publication date: 27-Jan-09. This is Issue #02, published date:
27-Jan-09.
Severity/risk level High Urgency Immediately
Name of problem Problems with USB Modem (Model no: MT5634ZBA) on the Message Storage Server.
Products affected
Modular Messaging (MM) 4.0 Message Storage Sever (MSS) Box.
Problem description
• There have been several issues reported with the old MT5634ZBA USB modems when used with an MM 4.0 MSS.
• There have been issues reported when installing the modems, removing the modems, and setting up alarming. The issues
occur when the modems are unplugged and plugged in while moving between the USB ports.
There is a new USB modem MT9234ZBA available. If you face problems with the MT5634ZBA modem, it is recommended that you
replace the MT5634ZBA modem with the MT9234ZBA modem. The comcode for the MT9234ZBA modem is 700451172. Please
state that the comcode should not be substituted. You can identify the modem on the system remotely by typing the following
command:
systemname% ls -la /dev/usb*
lrwxrwxrwx 1 root root 7 Oct 24 09:58 /dev/usbmodem0 -> ttyACM0 (This is the MT5634ZBA Modem.)
lrwxrwxrwx 1 root root 7 Oct 24 09:58 /dev/usbmodem0 -> ttyUSB0 (This is the MT9234ZBA Modem.)
The modem number is also displayed on the bottom of the USB modem.
Resolution
Replace the MT5634ZBA with the new MT9234ZBA modem (COMCODE 700451172). Once the new MT9234ZBA modem is
received follow these instructions.
Note:
This will require a technician to be on-site, he will perform the given instructions unless he fails step 3 and then have to call the
Backbone Engineer team for assistance.
1. Turn off alarm by setting Alarm Configuration to INACTIVE on the Alarming Configuration web screen and click Save.
2. Remove all USB modems configured from the web screens under Server Administration -> Modem/Terminal Removal
3. If the removal fails contact your Avaya Global Services Team for assistance, else go to step 5.
4. After a Backbone Engineer has been engaged from the command line the following should be performed:
- dsp_device (shows the modems that the system is detecting; it might show images of modems that are no longer
connected)
- rmv_device <device name> to remove modem images from the command line. (There may be more than one
modem listed. Remove all modems listed from the above command output).
Note: If the MSS modem is not working access will need to be acquired by using putty from a Messaging Application
Server (MAS).
5. Unplug all USB modems from the MSS.
6. Reboot the system. If prompts (Kudzu) to remove modem configuration, then click Yes.
7. Once the system comes up, plug in the new MT9234ZBA modem into the top USB slot.
8. The Technician should go to the Modem/Terminal Configuration and administer the modem by selecting the box and saving
configuration.
9. Dial into the MSS.
10. Administer alarming and test.
11. The technician should activate alarming from the web screens.
12. Once the alarming is administered in the web screens, send a test alarm.
13. Verify if the test alarm works. If this fails then verify that alarming is linked properly by doing the following:
a. Type ls –la /dev/alarm (If this comes back you will have to manually link the file.)
• ln –s /dev/ttyUSB0 /dev/alarm (This will link the alarm file.)
© 2009 Avaya Inc. All Rights Reserved. Page 2
b. Retest alarming and verify it works and if not working then reboot the system one more time and retest alarming.
c. If alarming is still failing the BBE engineer should escalate a case to the ADE (Advanced Diagnostics Engineering )
Team.

Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

 

[texeric]

I think Ken posted a reply to the wrong thread .

rejackson - I don't believe the multiple languages was designed for you to use different language greetings. It was designed for a caller to press their desired language option and then the system prompts (not your greeting) would be presented to them (the caller) for the remainder of their call with the system.

 

[rejackson]

I got this working. The key seemed to be to delete the normal greeting.

 

[KenMeans]

Yes i did must be getting old.

Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)