Hopefully a quick question. A customer trades under multiple company names. They wish to have all four of the main DIDs coming to one Receptionist, using Attendant Console. Apparently, they have been told from someone at Cisco that it is possible to have AC show them which company is being called, i.e. which DID was originally called (obviously the translated to a DN), so as to allow the receptionist to answer the phone with an appropriate greeting for each firm.
I know that ARC Console does this very nicely, but the last time I looked at Attendant Console all it showed on each line was the calling number, not the called number!
It will show just calling number I think if you use normal queueing or just hunting...
If you use broadcast hunting you see the pilot point, calling number, and waiting duration.
So you could have muliple pilot points/hunt groups, but with the same users in the groups. This would mean users have to pull calls out of the broadcast group, but would give you the ability to see where callers have come into the system.
Please rate helpful posts...
Please remember to rate helpful posts to identify useful responses, and mark 'Answered' if appropriate!
Many thanks for your reply. Can I make sure I have this correct in my mind? With broadcast hunting, and with multiple pilot points and associated hunt groups enabled, and the operator/s user ID being a member of all of such, then when a call comes in to any of these pilot points, they will display the calling number and the pilot point from which the call came to and was passed from to the Attendant Console? Without broadcast hunting, it would not be possible to see the origination point of the inbound call?
Am I correct on the above.
Many thanks for your clarification in advance. I will rate the post after this, I promise!
The easiest way we have found to set this up is to assigne each company a seperate number/line and enter that number in the attendant console users speed dial list with the company name. when a call comes in it will show up with the companies name.
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...