CME Transfer Call Alerting Name Question

[Tyler-Paquet]

Hello,

I've got a client who we recently installed a CME 12.0 system, 11 88xx phones, all SIP of course. They approached me with a question that I'm not too sure of the answer. When the receptionist uses Call Transferring, the alerting name (the caller display on the receiving phone) shows up as the reception's extension, and not the information of the call being transferred (Like the incoming call). I know that when you press the transfer button, it first attempts to establish a call between extension A and B, then clicking transfer a second time actually transfers the call.

My question is, is there a way to have the incoming number's information be sent instead of the extension details when transferring a call? Not sure if I'm wording this correctly or not...

[Maren Mahoney]

To have the original-caller's callerID show up during transfer, configure "Blind Transfer". Here is how to do this for SIP CME:

CUCME Administration Guide - Configure Call Transfer on SIP Phones

Maren

[Tyler-Paquet]

I read that link you sent me. I guess there's not a simple way to just tell the system to always do a blind transfer?

[Maren Mahoney]

For SCCP phones, there was a telephony-service command that would set the default as blind-transfer. For SIP phones, this must be accomplished via the template. The good news is that the templates can do a good deal more as well.

[Vaijanath Sonvane]

Hi,

I think you are facing similar issue as mentioned in this post:

https://community.cisco.com/t5/ip-telephony-and-phones/cme-sip-phone-consult-transfer-not-changing-caller-id/td-p/3329624

The solution on that post was to remove asserted-id ppi.

voice service voip
 sip
 no asserted-id ppi

Check that post for more details.

[Maren Mahoney]

Good catch!

And do read the whole post to the end. Removing asserted-id ppi globally will affect other features such as call park and call pickup. In addition to removing it globally, you will want to add it at the dial-peer level for inbound external calls.

Maren

[Tyler-Paquet]

In doing that, it seems like some stuff like call parking is disabled.

Also, this system uses FXO ports for PSTN access, using connection plar opx (ext) as it's mean to put the call to the hunt group. Should I make an incoming dial-peer to solve this issue?

[Maren Mahoney]

If you are not using SIP for PSTN access, I think you will need to leave the asserted-id ppi in place globally and go with templates for the blind transfer.