Search results for query: *

Apparently it is the RC-2A I need, not the SRC-1, since I need the unit itself to answer a call an wait for the code.

We are wanting to interface with our door control system so we can lock down the building by dialing a code from a phone.

We are running Avaya CM 6.3 with G650 cabinets and are looking for a way to operate a contact closure from the phones. Anyone have any good ideas?

Can you keep them from changing the ring volume as well?

well, I guess I'll make the change to the file. Not looking forward to rebooting all the phones though. Thanks.

So I cannot do it per station in the Avaya CM?

We run a call center with hot desking across three shifts and we need to keep the users from changing the ring pattern.

In our PSAP we are connecting CAMA trunks into AudioCodes M-118 to convert them to SIP to interface with our Avaya CM6. We are having a heck of time getting them to work reliably. When AT&T test the trunks they get "bad wink" intermittently, meaning if they test a trunk 5 times it will fail...

Our biggest issue is scheduled outages. We will occupy both the main center and the backup center. Once our call takers are logged into the system they start answering calls. Our trunks, both PRI and E911 CAMA are distributed between both sites and will ring in both locations. When the WAN...

Is there a similar solution for the H.323? One that would allow either local or dual registration so there won't be any interruption in phone service?

Apparently session manager only works with SIP and no H.323?

It looks likes BSM is the way to go, if I am understanding it correctly. If I have a session manager running at each site the SIP phones will register to both and if the WAN goes down between sites then the phones will fail over to the session manager they see as still active with out...

We have two sites, the main center (MC) and the backup center (BC), each with two servers. Our BC needs to be able to act as an overflow to the MC during times of high call volume and each of the sites needs to be able to survive on it's own either due to a scheduled outage or the proverbial...

Thanks, apparently they have to take down the PRIs to make this change and we were trying to avoid that, but we gotta do what we gotta do.

OK, so I cannot program a "default" outgoing CID number. The carrier is sending our our main billing number which is not a number we want people calling.

I understand that but how, where, do I get 423-555-1234 to be the default outgoing number so I don't have to program every extension into the public unknown numbering tables? Basically, if the extension is not in the public unknown numbering tables it sends out the 1234 number.

Is there a way to set a default outgoing caller ID? Meaning, if the nothing is programed in the "public-unknown-numbering" tables for an extension the Avaya will send a different specified number. i.e. All out going calls will display 423-555-1234 except for extension 768 which should show...

Thanks randycarroll. I'll look into the 1600 phones. We are unsure of what the future has for us as far as telephone systems are concerned. We will be upgrading our current 911 telephony system to be Next Gen 911 compliant and depending on the what is available and offered we may be letting...

Thanks montyzummer, I understand that. It's the line item inside the above commands I am not sure of.

I'm not certain if it is enabled or not. Where would I find that?