cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2015
Views
0
Helpful
10
Replies

Attendant console unable to consult transfer.

rferullo
Level 1
Level 1

We have attendant console running on call manager version 6.1

When the attendant console receives a phone call and tries to do a consult transfer, nothing happens. No error messages.

I tried restarting the attendant console and CTI manager services. I also confirmed that windows firewall isn't turned on on the users workstation.

10 Replies 10

Rob Huffman
Hall of Fame
Hall of Fame

Hi Robert,

Can the Operator do a Blind Transfer? Have you checked the Max Calls setting on the DN involved?

Let us know,

Rob

egrinkin1
Level 1
Level 1

Nothing happens at all? No pop up window for the operator to enter the extension? Or nothing happens after the extension is dialed?

We had a similar issue after upgrading to 6.0. We needed to upgrade to an engineer build to get Consult Transfer to work. But the operator also had to press consult transfer again, after entering the extension and dial, in order to complete the call.

I was about to post something similar to this. I'm running UCCM 6.1 and I have an Attendant Console that will not transfer, put on-hold, or perform any actions involving softkeys on the associated 7961G-GE phone when receiving calls with "Unknown Caller" on the caller ID. All other calls transfer, put on-hold, etc just fine. Weird right?? Any input on this would be most appreciated.

Totally weird. Our solution was to rebuild our servers to 6.1 and change our VG to MGCP from H.323. After that, we were all good.

But our issue was with MTP resources not being released after a call was terminated so eventually we would have none for the AC processes. And, we saw the issue with every call no matter how it was presented.

I'd say call TAC. I know it's painful, but sounds like a job for them for sure.

Yep, sounds like a job for TAC. Thx.

Found my issue and I didn't have to open the TAC after all.

- Found that the "Unknown Callers" were not calling the DID for the main number

- They were calling a POTS line number that is configured on the VGW as a member of a hunt group reserved for failover/SRST

- As configured, any incoming call received by this hunt group is forwarded to one of the non-DID extensions assigned to the receptionist IP phone

- Calls would appear to be coming in and routed via the AC pilot point hunt group, but were in fact being routed to a direct extension via the hunt group in the MGCP VGW config

I'm guessing the Call Attendant console didn't know what to do with calls forwarded in this fashion to a direct ext and I don't know if there's a fix for this type of scenario.

Can the Attendant press the softkey on ther IP Phone to transfer the call?

I know ours use 7961s and can still use the softkeys in lieu of the AC if needed.

Just my input on my way out the door for the night. Good luck!

Can the Attendant press the softkey on ther IP Phone to transfer the call?

I know ours use 7961s and can still use the softkeys in lieu of the AC if needed.

Just my input on my way out the door for the night. Good luck!

No, that's what made it so weird. When she would depress any of the softkeys, nothing would happen at all; just like the issue explained in the 1st post to this conversation. However, an error did pop-up on the Call Attendant PC; "Failed to transfer the call due to internal error." I looked to see where any details of the error could have been logged, but could not find.

I am sorry I can't help and best of luck to you.

I hope you get the help you need from one of the pros here or from TAC. Keep us posted.

~Liz

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: