Attendant Console - unable to initialize call & line is not available errs
Hoping someone out there can help. I am pulling what little hair I have left out over this/these problem/s.
Scenario: Three attendant consoles deployed, associated with IP Communicators. All communicators share the same 8 lines (the reason for this was that broadcast hunting was not an option as it did not make the phones ring when there was an incoming call and it automatically sent the users to MOH rather than giving the caller a ring tone). Pilot point is associated with a hunt group that lists all the lines by directory number. It uses the "first available" algorithm to route calls to the appropriate lines.
Problem description: When more than one incoming call is being answered by the AC users, (that is , they are talking and have not yet transfered etc the caller) and one of them tries to transfer a call, then they get one of two errors. Either "Unable to initialize call" (less common) or "line is not available" (more common). They then have to wait until the other AC user has got off the phone and then transfer the call.
What I have tried: I have set the "Maximum number of calls" on the primary two lines to 10, with a "Busy Trigger" of 2, and the rest of the lines with a "Maximum number of calls" value of 4. This does not appear to have resolved the issue. I thought it might be that as when I turned on the CCM traces, it had an error line saying max calls=2.
Re: Attendant Console - unable to initialize call & line is not
Many thanks for the reply. Unfortunately, we need to use shared lines to overcome a problem that they had with the previous system of not using shared lines where other operators would not know that another call was waiting at another operators console who was already on the phone because it did not show up on their console. They would have to wave at the other operator to get them to answer it and then swap headets mid-call. It was all a bit crazy.
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...