I have a BCM450 with three phones in a "Ring Only" hunt group. After the caller ends the call, the "intercom" button stays lit and that phone stops receiving calls. If you go off hook and press the intercom button, the message in the display is "line in use". The only way to clear this is to...
I have an incoming PRI that rings an attendant console, if the attendant does not answer it overflows to a hunt group. The phones in the hunt group all have voicemail. So, any inbound caller may receive one of the overflow users voicemail at random. Is there a way to have the inbound call ring...
Has anyone else had this problem? Is there a command line interface into the BCM50 that might allow an individual port reset of the paging port? I assume if the page port is dead then I will have to swap the main chassis.
Thanks in advance for the replies.
I have multiple BCM's (400 & 450) setup so the first 3 virtual park spaces are appearances on all the phones (801, 802, 803). My client has introduced an analog extension in the mix and I have learned that a call parked from an analog extension starts at 825 and works it's way down. My dilemma...
Guys,
I just replaced an Avaya Partner with a BCM450 and I cannot get the paging to work. I have discovered the paging system is a 70VRMS system. What are my options? I am attempting to use the paging output port on the front of the BCM. Will a trunk port work?
Thanks in Advance for your replies.
The scenario is this: I have a BCM450 with a PRI. Each extension has their own DID assigned. When I call that DID and get their voicemail, I need to be able to dial 0 and rollout to a particular hunt group. I have each phone configured with a "recall" key to act as an appearance key for this...
I am looking for suggestions as to the best way to setup "local" policies for all terminal server users without causing the same policy to apply to their XP machines.
This scenario has two DC's with the terminal server being a member server. All users logon to the domain.
Does anyone know how to turn off the automatic detection on WIN2000 Terminal Server? I have multiple thin clients with proprietary printers locally attached. Each time a user from one of those thin clients logs on, it attempts to install the printer on the terminal server, thus generating errors...
A recent crash of my VMPRO PC and a subsequent restore has many of my users at random receiving the prompt "you have 6,764 messages in your mailbox" however when you press select to listen to them you may or may not have one or two legitimate voicemails. I also have the issue of the message...
Does anyone know of a way to lock down the Terminal server without creating a domain policy that affects the entire company? Specific user policies do not work due to the fact several users login to both XP PC's and terminal server.
I have two offices connected via cable modem with a site to site VPN provided by Symantec Enterprise edition firewall. I have a Level 3 tech at Avaya telling me the IP403 will not work across that VPN due to Symantec problems. Does anyone else have this issue? Any Solutions?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.