Search results for query: *

Hey Dave, I have a feeling when using VO to login to a MADN, it simply takes the first entry that appears in the list when you do a PRT/DNB? You could test this on your system, make a change to a TN that has this DN, it will move to the top of the list, now when you VO to this MADN, you should...

You should be able to use the interflow feature, you will need to check the documentation to ensure it is what you want, however if you enable automatic interflow, from above, using the IFDN and OVTH should extend the call to another number after a set number of callers are waiting, which could...

You should be able to use interflow in this case, you should be able to configure the ACD queue such that 1 call waiting with trigger interflow, did this functionality not work? What happened when you tried interflow?

I believe access ports are also licensed on the CallPilot server, you will need to have spare access port licenses to enable you to configure.

Can you provide a print of the dch's involved here perhaps it is the T306 timer or MCT option enabled?

It sounds like you have connected the 3903 handset to a digital LC TN that is not configured/programmed. The handset is prompting you to select a template to start the TN configuration via the 3903 handset itself. If you have already programmed a TN through CLI or GUI, check that you handset is...

There is no pdt and no keycode, the system you have runs the x11 software directly (no vxworks host os), the packages etc were restricted/unrestricted through the use of a hardware cartridge as firebirdscrambler mentioned.

I have seen a few systems connected to Mediant product, provided they are a DevConnect partner and achieved this via the T1/E1 connectivity then both Avaya and Mediant should have application notes describing the configuration requirements of each device. Your Mediant distributor should be able...

Notes suggest this feature ACD BUSY ROUTING, needs package 411, but I can't see what package 411 is? Maybe it's restricted in your system?

If the operating hours for the user on 7717 are fixed, you could create it as an SDN, have an application use a time of day control such that during operating hours a call will EM mailbox 7717, after hours it will EM 6440 and therefore perform the required page etc.

Not sure you can just convert the scripts from Procomm into CLI*Manager, there were some training vids when CLI*Manager first came out, perhaps you could get access to the scripting vid, scripting _overview_v1.0.exe, this might help you rekey the scripts you need into CLI*manager format.

I think the attendant queue is set to longest idle gets the next call. If the other attendants are doing anything on the console, it resets the idle time of that attendant. I had a case once were an attendant 2 was toggling position busy imediately after attendant 1 released a call, ensureing...