You can also use call join.
Put the initial call on hold, use another dn to call the other party.
You can go back and forth between the 2, and when you are ready to conference the other party, just press conference and press the other dn key.
considering that 5.0, 5.5, 6.0, 7.0 and now 7.5 are out, how do you feel about being unsupported? Support for 6.o should go to 2015. (sale just ended). Just sayin....considering you are a hospital.
When did the problem start?
If it's new, something must have changed.
Is this possibly a trunk side issue?
You don't use 66 blocks do you? I once had to fly out to CA for a serious "switch problem" Turned out the 66 blocks were not split blocks....
does anyone know a way around the latency restrictions on a carrier remote? It comes up fine when the tested latency on the DS1 circuit is under 45 ms, but when the latency changes to 52 ms due to the carrier topology changing, the XPEC can not be enabled. Wondering if there is a patch for this?
We've gone from CC6 to 7 to 8. No real issues that have not been resolved. The big jump from 6-7 changes the database from Sybase to Cache, so if you have queries going directly to the database, you will have to recreate them. The canned reports all work just fine.
Contact center really does not...
Depends on whether or not you are using broadcast music.
(see BDCT prompt in RDB). Broadcast is licensed, you can see what's used/left when you load overlay 14.
If not, you can add another trunk (bridged to the original source) and assign it to another added conf pack, assuming this is not a MG...
After upgrading our multi site TM from 3.2 to 4.0, all of the switch types changed in TM to 1000S, you cannot change them back, nor will it allow you to select release 6. You can add a new site correctly, but I would rather not have to re-enter everything and loose a years worth of traffic. Any...
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.