Search results for query: *

I ran across this on this site a few months back. I have not had an opportunity to test it out. budbyrd (Vendor) 23 Jun 23 10:28 Use an analog port. Set it to MOH Source. Set the MOH source to XTN:(what ever the extension). You should be able to reference that for any system on the SCN. Dermis...

I am using an analog station port for page access. I replaced the 500V2A cabinet with an older 500V2 cabinet we had on the shelf and the whine immediately went away.

IamaSherpa you get the whine right out of the IP Office if you test it with a test set so its not something thats being induced into the wiring.

The last two systems we have received have had the power supply whine. One of them is so bad that I could not leave it plugged in on the bench because the whine was so loud that it was giving people a headache. Hopefully Avaya has addressed the issue so we don't run into it on future systems. Rick

As has been discussed here before the new 500V2A cabinets have a high pitched power supply whine which can be quite annoying if the cabinet is going to be mounted in an occupied area. I had an install where the cabinet was to be mounted in an unoccupied area and figured the whine would not...

This is from another post on here that I copied into my IP Office notes folder. In 10.0 you configure it through IP Office Manager or Web Manager as normal. Look for the atrociously named setting "Advertize Callee State to Internal Caller Rick

Is it possible that the user is set to forward voicemail messages to email and the email address is incorrect? Rick

There is a post on the requirement for 31 digits in the voicemail password for 11.1 FP1 on Avaya's support page. https://support.avaya.com/ext/index?page=content&id=SOLN361538&viewlocale=en_US Problem Clarification Unable to change the voicemail password in security settings, unless it has 31...

Yep just tested here and it is working again.

I am experiencing the same issue as you. I too use the IPO toolbox on an almost daily basis and would love to have it back again. Rick

We have recently run into an unusual situation. We have 2 sites one is 11.1 and the other is 11.04.1. We have recently deployed J169 phones at these two sites and what we are finding is that if a user is on a call and a second call starts ringing in, if the original caller hangs up it...

I think Budybyrd is correct. Put your testset on line 2 then call line 1 and see if the call rolls to line 2 if its not answered. I have seen this same scenario where instead of just having trunks roll over on a busy they also roll over on a no answer.

This is a know issue in VMPro 11.1 and 11.1 SP1. Avaya will address the issue in an upcoming service pack but has also released a critical patch to address the issue on current systems. https://support.avaya.com/ext/index?page=content&id=SOLN356241&viewlocale=en_US Rick

Log into the web management on port 7070 and select voicemail pro system preferences from the application tab and set enable voicemail pro client interface to yes.

We have this happening on two systems now. The voicemail service will stop at random intervals but can be restarted from the app server web control page. In looking at the error trail in both app servers they show the same error message. Voicemail Pro started at 29/06/2020 08:03, last idle time...

Any more developments on this? We have a customer that we upgraded their app server to 11.1 and it has exhibited the same behavior ran fine for 2 weeks then the voicemail service stopped in the middle of the night.

I ran into this yesterday on some softphone clients at a customer site. There is a No User Source Number that disables direct media system wide. It fixed the issue I was having. The NUSN is DISABLE_DIRECT_MEDIA. Hope it works for you as well. Rick

Pepp we just recently set this up for the first time and this is what we added to Option 242 on the DHCP server. Option 242 MCIPADD=192.168.42.1,MCPORT=1719,HTTPSRVR=192.168.42.1   granted we were not running TLS. Hope this helps. Rick

They should have built it as ESF/B8ZS right from the start. I Don't believe that you can run a PRI on D4/AMI. My guess would be that once they reconfigure it properly it will come right into service. Rick

As Intrigrant stated according to Avaya's support site the fix is not included in Rel 11 FP 4