Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements
Users might experience few discrepancies in Search results. We are working on this on our side. We apologize for the inconvenience it may have caused.
New Member

CUBAC 2.0 transfer problem

When the receptionist transfers using CUBAC the CTI Port, from the service queue, shows up as the caller ID during the transfer until the call is answered - then the original calling number shows up. This is true even during a non-consultative transfer.

If the phone is used, the CLID shows as the original calling number from the moment the transfer button is pressed for the second time.

Any thoughts? Configuration? Bug? User error?

2 REPLIES
Bronze

Re: CUBAC 2.0 transfer problem

When the operator transfers the call, the call is terminated on a CTI Port which inturn reaches the destination phone. Once the call reaches the phone, the CTI Port bridges the two call legs and CUCM updates both parties of the Connected Number.

https://www.cisco.com/en/US/docs/voice_ip_comm/cucmac/arc/arcug20114.pdf

New Member

Re: CUBAC 2.0 transfer problem

Same problem. I believe this to be a design flaw in CUBAC. In my opinion, blind transfers shouldn't be routed through CTI ports.

Anyone have a soultion or work around?

402
Views
0
Helpful
2
Replies
CreatePlease to create content