I have implemented both of them but the expected wait time seems to be a better idea. The position in queue may cause misunderstandings when a call with a higher priority takes precedence (imagine: "You are the secon - oh wait, no, you're the third customer... er... wait, now you're just the fif... what am I talking about you're the fourth" etc)
The expected wait time is more meaningful. The customer actually knows he's going to wait and based on this information he may decide whether to start brushing his teeth or start a new episode of .
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...