Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

original Caller ID not propagated on unconditional call forwarding

Description

When we want to make an unconditional call forward the number of the caller should be transmitted (with the necessary SIP options), however this is not the case if the CallerID is present in the outcall extension of the tenant.
If I delete this callerid in the outcall extension, I can find the number of the caller to the transfer.

Exemple :
A: extern caller (0123456789)
B: transferred user
C: destination number

If I have a callerID configured in Outcall Extension:
When A call B which is transferred to C the number of A 0123456789 is overwritten by the callerID number of the outcall.

If I don't configure CallerID in Outcall Extension:
When A call B which is transferred to C the number of A 0123456789 is displayed on C

Technical things

  • See if difference between FR and US. stir shaken may make things more strict on the US.

Zendesk Ticket IDs

1286

Activity

Show:

Charles Langlois 
November 28, 2024 at 4:47 PM

Just to clarify, it might not be viable to rewrite caller id information( From or P-Asserted-Identity headers) with the identity of when making outbound calls, but SIP does support specific headers to carry forwarding information, such as Diversion and History-Info . However, those might not be supported by all SIP operators, and when it comes to the PSTN there’s little guarantee the information will be carried to the destination as something the receiving phone device will be able to handle meaningfully.

Sylvain Boily 
February 27, 2024 at 3:09 PM

I gave some information internally, the biggest issue here is to in general in many countries you don’t have the right to make a call with a number you don’t own. Depends also on provider who care about the local laws. Needs more discussion and find the best way to address this issue correctly.

Charles Langlois 
February 5, 2024 at 8:20 PM

Awaiting your follow up on whether this should be closed, otherwise how it could be resolved.

Charles Langlois 
January 19, 2024 at 4:43 PM



Seems implemented since 16.11.0 , using res_pjsip_diversion module.

Charles Langlois 
January 19, 2024 at 4:35 PM
(edited)

Okay, I saw this distinguished as “cold/unattended transfer” and “warm/attended transfer”.
This is a case of call forwarding/cold/unattended transfer.

RFC5806 not being official doesn't mean it’s not implemented, as evidenced by the presence of the Diversion header in our SIP traces in this scenario.

There’s also this: .
That’s official, but is it implemented in asterisk? Is it usable by the endpoints we support?

Won't Do

Details

Priority

Assignee

Reporter

Sprint

Story Points

Zendesk Ticket Count

Labels

Zendesk Support

1
Created April 21, 2020 at 2:26 PM
Updated November 28, 2024 at 4:47 PM
Resolved November 28, 2024 at 4:41 PM