Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

transfer to voicemail FAC not working since upgrade to MM 5.2.1

Status
Not open for further replies.

9mmgeek

MIS
Jun 29, 2005
225
US
CM 3.1.2, just upgraded from MM 3.0 to MM 5.2.1. Its a toss up as to whether this is a CM or MM problem. The transfer to voicemail feature access code was heavily used by people with bridged appearances of other people's phones. They answer a call and if the caller wants to leave a message they would press transfer, our fac for transfer to voicemail, then transfer. After the upgrade it opens the callers voicemail instead of the recipient. It does not go to the greeting, it transfers to the extension.
 
9mmgeek,

I had a similar issue. Here is what I did to resolve it.

In "Voicemail System Configuration" open the "The Telephone User Interface". Under the "General" tab uncheck the box "Enable Transfer to Voicemail using Extension Number".
We don't use the MM Auto Attendant so I unchecked this box as well.

Enable Automated Attendant
… When the Automated Attendant is disabled, the system transfers callers directly to the subscriber’s mailbox, where they can leave a message. They cannot transfer to the subscriber’s extension…

Enable Transfer to Voicemail Using Extension Number
Select this option to allow callers to transfer to subscribers’ voice mail using an extension number rather than a mailbox number.
If Modular Messaging does not recognize the number as a mailbox, it validates the number against a subscriber’s extension, then transfers the caller to the corresponding mailbox.


Hope this helps...
 
did you change to SIP or stay on the QSIG integration.

Ken Means

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)
 
MM 5.2.1 does not support qsig anymore. SIP is the only choice.

Mike, thanks, I tried your suggestions and it broke the dial by name. It just went straight to voicemail.
 
yep.... My BP told me that we needed to create a extension and point it to an application on MM, we could no longer use the ## in a system speed dial.... it works!!
 
So when you upgraded you got new servers and that is why you are not using QSIG any longer.

The name of the feature is QSIG transfer to voice mail and hence the reason why it does not work with SIP. Avaya needs to update this in the PBX side

Ken Means

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

The BP said qsig was dropped after 5.1 (or 5.2.0?), anyway we had just missed the opportunity to continue to use qsig. The phone system is still old, CM 3.1.2, and it sees it as qsig up to an audio codes box which makes it SIP to MM. This was an upgrade from MM 3.0 on S3400 servers.

When you say the "name of the service" are you talking about CM because that is where the feature access code is that I am talking about.

IMMike,

We have a caller app that the attendants use to send callers to other people's voicemail. It is very slow, even slower now with sip because avaya intentionally programmed in a 2 second delay. It goes "Please hold", there is a short blast of MOH while the very slow transfer on a sip trunk takes place, then "please enter the destination mailbox", delay, "please transfer the caller now".

The feature access code still does a transfer, the problem is that it sends the caller to their own mailbox instead of the called persons mailbox.
 
ou can still use QSIG in 5.x and 5.2 as long as you are on S3500 or S8730 servers. The S8800 server will not support a T-1 card or at least that is what the say.

The PBX does not know that the T-1 is not connected to the MM and that is why it fails.

Ken Means

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)
 
S8800 server are a single RU, and no space for the Dialogic card to fit. However when configuring a system via the DCT, QSIG is still a valid option, because customers can provide their own MAS server as well as Dialogic cards.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top