Call forward with proper Caller ID?

[bbrendon]

Hello. I've noticed that the Call Forward (follow me) feature sends the wrong CID. It's sending the forwarding party's 4 digit extension to the carrier which causes the call to drop.

I'm on 5.0.1.

Is there some way to change CID when forwarding? Am I doing something wrong? Maybe this is fixed in a newer version?

I found some older threads about it but they all seem to apply to 4.x versions.

Thanks.

 

[mcs3ss2]

Account > Extentions > Ext No > Call Forward > > Call Forward

I just tested it. I am on 5.1.0

 

[bbrendon]

Thanks @mcs3ss2 . I'll see about upgrading as well.

 

[bbrendon]

I just updated to 5.2. It's still broken. Its showing the CID of the extension, the cell phone doesn't ring and says its Junk call.

 

[bbrendon]

I did more testing on this. The Polycom phone rings from a ring group. The person answers. Blind Transfer forwards the Caller ID of the calling party and the call goes through. Assisted Transfer gets flagged as a spam with the calling party caller ID. I'm not sure exactly why one works and the other doesn't.

I think the real issue is the spoofed caller ID.

 

[neeek]

I did more testing on this. The Polycom phone rings from a ring group. The person answers. Blind Transfer forwards the Caller ID of the calling party and the call goes through. Assisted Transfer gets flagged as a spam with the calling party caller ID. I'm not sure exactly why one works and the other doesn't.

I think the real issue is the spoofed caller ID.

We had the same issue with forwarded calls being rejected by the receiving party as they thought we were spoofing the caller id

The trick is to set the diversion header, you add the following just before the final line
export > sip_h_Diversion=<sip:${caller_destination}@${external_sip_ip}>;reason=unconditional

Under the dialplan call_forward_all