Search results for query: *

Don't have the notes in front of me but it's a specific release of XOS that freed up QP6 in a stack. I think it was somewhere in 12.2 or 12.3, so hopefully you've kept your code updated and can use QP6.

The "Voicemail On" checkbox only indicates that the extension's coverage path to voicemail is active. They still have a mailbox, and can still send callers to that mailbox using the described method. You can also forward messages to that mailbox. Since the Embedded and VM Pro options are built...

They make a tool called "IP Collector" but last I checked it was still the release in their Beta downloads that worked with IP Office formatted data. The GA release of IP Collector did not support the IPO last I tried, but with a little tweaking the Beta version did.

Unconfigure switch - resets everything except user accounts and date/time. Unconfigure switch all - deletes the config completely.

If you can either VPN from a PC or Remote Desktop to one in the office with Phone Manager, in Telecommuter mode? I think even lite has the "Record Call" button doesn't it?

Match the software level of the stack, then add it to the stack. Then use the MAC address to assign it the desired slot number configure stacking node-address aa:bb:cc:dd:ee:ff slot number x aa:bb:cc:dd:ee:ff represents the MAC address of the switch you're adding, x is the slot number you...

Your description's difficult to follow - you want only one subnet to have internet access? And what's the reason for a second firewall? I'm unsure why you wouldn't want the BD to handle all routing...it's a very capable L3 device, more than a firewall is.

The specific translation of the errors, no - but watch out since they're basically Avaya's version of Window's "Blue Screen" - an indication of an unrecoverable problem and the system rebooted.

No problem, sometimes that's what it takes...clear it out and start over. Glad it's working.

You need option 242 in both scopes, the data scope to at least tell the phones to go to the voice VLAN (L2QVLAN=10, I think?) Double check that the DHCP server is not on a port that's both voice and data - it needs to be only on the data VLAN untagged. If you hard-code a phone with VLAN 10...

Your DHCP server need to be set for both DHCP and bootp? Phones need to be reset to start on data VLAN and then get told by option 176 or 242 to go to the voice vlan? The DHCP server's default gateway is the Extreme? (it needs a route to 10.x)

If the scope option 242 is added to DHCP as a server option, it must also be checked for each scope (scope options) as well for it to use it. Creating the server options only adds it to the list of scope options you can use, still needs to be checked.

That's correct, it allows DHCP to cross over to the voice vlan.

Sorry, also anything that is NOT a phone in voice-avaya (like PBX, VM Server, etc) need to be on a port that is only voice-avaya and untagged. config voice-avaya delete port x, y config data-avaya delete port x, y config voice-avaya add port x, y untagged

CHANGE: config vlan voice-avaya qosprofile QP6 ADD config vlan voice-avaya delete port x (x being the port that the DHCP server is plugged into) configure bootprelay add <ip address of DHCP server> enable bootprelay

QoS is (as stated) a fairly complex setup, even for some pretty seasoned Network guys. A quick writeup or PDF doesn't really do it justice. BUT, here's some basics. A lot of times the correct method depends on the network hardware used (Cisco, HP, Extreme, Juniper etc). The Avaya systems and...

Also check permission on the files in the wwwroot folder. Sometimes dropping them in there changes read permissions and won't allow the phones to get the files. Try by browsing to your server and see if you can read one of the files. http://<myservername>/46xxsettings.txt You should be able to...

You'll want to look into 802.1x - too much to walk through on a forum discussion but it's what you want. Check out Extreme's Concepts and CLI reference guides here: http://www.extremenetworks.com/services/software-userguide.aspx

Ingress = packets incoming Egress = packets outgoing

That my friend, is a little piece of gold. Star for the link to the manual.