Recent content by Rappy

Thank you so much for your replies. I am now in the process of installing additional 16 port DS to accommodate growth and to remove some of the phones from the DS30. The DS30 is a V1, and according to the documentation that they provided me, the V2's had issues with line power, not the V1. the...

thank you so much for your response- this is news! exactly how do i go about securing an external power source for these phones, and where do you plug it in? on the bottom of the phone it states "Use only with communication circuit power source!" there is a slot on the side to plug in the...

that raped my ears... it's like watching a train wreck in slow motion. Beets? Yes! Ask me how I feel about Beets! I like Beets!

i have been struggling with an IPO 406v1 with approximately 30 users, connected to DS30 and DS16 expansion stations. About 15 times a day, 90% of the phones will lose their display, the voicemail light blinks, and then it goes back to displaying name/ext. We are on release 3.2.69. I stabilized...

I have to perform this procedure every 6 weeks to keep that issue at bay. As per Avaya, please see below A user states that he/she is not receiving voicemails. How do I perform maintenance on the voicemail folder? 1.Stop the VoicemailPro service on the voicemail server having the issue 2. Save...

using a spare ip office 406 and a digital expansion unit, i have been able to duplicate the issue. The lab is as follows: ip office 406- connected to power, using expansion slot 2- connected to DS 16 using the Avaya cable provided (someone called it a TDM cable?!) ip DS 16- using single...

Hi everyone! I have a remote office connected via IP VPN to the main branch. Main branch is ipo 412 running 3.2.69. Remote is ipo 406 V1 running 3.2.69. Problem is at remote branch with 2 digital expansion units. The users connected to both units are seeing their phones shut off completely. All...

i moved my IPO to a separate VLAN about 2 months ago. there were some issues with caller ID after the move, but they have been resolved. but putting that POS on its own vlan so it can just sit there and scream at the other device on the VLAN (the voicemail server) is the best thing i couldve...

Welcome! We are sorry for your loss! i mean! you will love your new IPO! we need particulars- IPO 412? 500? We need the software version? 4.x? 3.x? 5.x? and the version of manager and VM pro that you are using. Just for kicks and giggles also throw in your favorite day of the week and vacation...

i have run into this issue after upgrades were done (never downgraded before). I have resolved it by unplugging the phones having the issue from the phone wall and leaving them unplugged until i reboot the IPO. Once you reboot the IPO, plug the phones back in and the light should accurately...

i have been unable to run the wireshark traces as that laptop went kaput last time i fired up wireshark. However, i do remember seeing AVRIP traffic in monitor. i believe i may have actually found the issue, and may have a fix for it, but i still need to test my theory. In the IPO 406 AND 412...

i have never done an export. Ooh! It may just be corrupted, hence the reason i am dilligent about backing up a config at least once a week, or when changes are made. I will look into it and see what i need to do. Thanks for the suggestion! Beets? Yes! Ask me how I feel about Beets! I like Beets!

I knew someone would get their feathers ruffled about making the slightest comment about "Avaya not working as intended." Dont shoot, i am just repeating myself! Dont take it personal, stuff breaks and does not work as intended all the time. I know it would seem coincidental, but you are not...

Be that as it may, it has been the case since we got this thing. The carrier blames Avaya for not timing properly, and Avaya blames the carrier for not timing properly. The cabling guy has tested the extension from the DEMARC and noted that there are no issues with cabling, and we are left...

It is an IPO 406 V1. Beets? Yes! Ask me how I feel about Beets! I like Beets!