Search results for query: *

Doesn't 9.5 need the virtual data mod configured as well? 'Knows enough to be dangerous. Wait... make that really dangerous.'

remove it and add it back. 'Knows enough to be dangerous. Wait... make that really dangerous.'

Swap out the phone for a known good one? 'Knows enough to be dangerous. Wait... make that really dangerous.'

http://tek-tips.com/faqs.cfm?fid=5454 Run 'cha ip-i (board location i.e. 01a05)' [Enter] Set 'Enable Ethernet Port' to 'N' [Enter] *Must disable before changes are made* Run ‘cha node-n ip (board location i.e. 01a05)’ [Enter] Change Subnet address [Enter] *I prefer to make the changes with one...

A T1 doesn't have dial tone. The dial tone is generated by the PBX. I would check how the Avaya box is programmed to route incoming calls to the auto attendant. 'Knows enough to be dangerous. Wait... make that really dangerous.'

ICDA is not enabled on the phones I need to look at. So I know I won't get internal to internal cdr data. 'Knows enough to be dangerous. Wait... make that really dangerous.'

Type of PBX please. Does the voice mail handle the auto attendant or does the PBX? 'Knows enough to be dangerous. Wait... make that really dangerous.'

I would like to know the solution to this. VoIP STEs are going to be shoved my way soon. 'Knows enough to be dangerous. Wait... make that really dangerous.'

No, you would run the amphenol pigtail from your rack/backboard to it. 'Knows enough to be dangerous. Wait... make that really dangerous.'

Nortel 81c with Callpilot VM. I can run a report and get the standard info as far as inbound and outbound calls for extensions. That Cost Analysis Extension Detail report does not show internal to internal calls nor does it show the difference of being answered by someone picking up a phone or...

Isn't there some 'time of day/day of the week' options screen where this can be all set up? I think it was in 5.X and later. 'Knows enough to be dangerous. Wait... make that really dangerous.'

Describe your system please. 'Knows enough to be dangerous. Wait... make that really dangerous.'

Many techs that I worked with back in the day were IP-challenged. I saw most of them retire when given the chance because they just didn't want to learn the new stuff. It was all given to the 'kid that knows computers'. There were a couple of guys that wanted (didn't mind) to learn it. I was...

mikeydidit, I found out a little bit of info. It seems like there will be some sort of Avaya maintenance tied into your BP contract. For this added cost, Avaya (not the BP) will be coming out to your sites and swaping out hardware. Very strange. I wonder when the Avaya BP's are going to band...

I think you can only make it two buttons minimum. One button for 'nhc' and then the button above it for the speed dial of the number. 'Knows enough to be dangerous. Wait... make that really dangerous.'

you call the guy in the post above yours. 'Knows enough to be dangerous. Wait... make that really dangerous.'

Put the cabinet back in with all associated hardware then remove all translations associated with cabinet. You can X port the stations. 'Knows enough to be dangerous. Wait... make that really dangerous.'

busy & release it. if that doesn't work, remove the station and then rebuild it in software. 'Knows enough to be dangerous. Wait... make that really dangerous.'

It's very simple folks. It's an old Windows trick. Create a shortcut for ASA on your desktop. You know, right click on your open desktop and select 'New' -> 'Shortcut'. Browse to the ASA.exe file and select it. Now at the end of that directory string that ends in '.exe' press the right arrow key...

http://support.avaya.com/css/P8/documents/100015095 and for firmware to phone to pbx reference... http://www.tek-tips.com/faqs.cfm?fid=7465 'Knows enough to be dangerous. Wait... make that really dangerous.'