Search results for query: *

I see!", said the blind man. That makes sense. We have 15 t.1's inbound/outbound so that would be max callers at once. Historically, we haven't had trouble with trunking when Employees are calling in. We currently do it with a bulletin board in Audix but callers are maxing out our ports to...

I'm still confused. Sorry. The VAL board is brand new. There are no other announcements on it. I am only going to record one announcement. It will be used for Company-wide announcements (CEO Records announcement, e-mails everyone and says go listen). In that situation, will I only get 32...

I'm trying to determine total number of callers on one VAL board at one time. We are planning on putting one announcement on a VAL board. Two questions: How many simultaneous callers can listen to this single announcement? How many callers, if any, will not hear the announcement from the...

One more thing, be sure and put a Converse On Data Return code in your Features. You'll need that if you are bringing the call back from the AVP to the CM to transfer or return any other data.

When you build your hunt group, change the AAS field to Y on page 2. When you build you agent login id's, change the AAS field in the top right hand corner to Y and then put an AVP extension in the station port field. This will auto-assign the login id to the AVP station. The vector is a...

I tried that already. That works for when they are on the conference bridge but also kills moh for all other calls. I'm trying to figure a way to only kill moh when they call the conference bridge. Folks can't seem to remember to not use the hold feature. Thanks again.

Check your CTI application. I ran into the same problem on a recording solution. The application had to have the VDN's identified before they would record. The Event Notif Adj field was only populated after we identified the VDN's in the recording application.

Question. How do I keep music on hold from playing in this specific scenario? 3rd Party in-house conference bridge. Connected to G.3/R V11 via internal t.1's configured at Tie Trunk group. This trunk group has a COR that does NOT allow MOH. Users call an internal extension that uses Uniform...