FreePBX Version
FreePBX 16
Issue Description
Using the Sangoma CRM webhook integration, the END webhook fires at the time of the attended transfer, not at the actual call end. As a result, the owner and destination fields capture the transferring agent instead of the final agent who resolved the call.
Operating Environment
Call Flow:
Inbound call received on a DID
Call rings a ring group → Agent A answers
Agent A performs a blind transfer to another ring group
Agent B answers
Agent B performs an attended transfer back to the original ring group
Agent C answers and resolves the call
Expected behavior:
END webhook should fire at actual call end
owner and destination should reflect the final agent who resolved the call
Questions:
Is this behavior (END firing at transfer time) intended or a known bug?
Is there a configuration option to ensure the END webhook fires at true call end?
Is there a way to capture the final agent correctly in the payload for attended transfer scenarios?
Relevant log output
FreePBX Version
FreePBX 16
Issue Description
Using the Sangoma CRM webhook integration, the END webhook fires at the time of the attended transfer, not at the actual call end. As a result, the owner and destination fields capture the transferring agent instead of the final agent who resolved the call.
Operating Environment
Call Flow:
Inbound call received on a DID
Call rings a ring group → Agent A answers
Agent A performs a blind transfer to another ring group
Agent B answers
Agent B performs an attended transfer back to the original ring group
Agent C answers and resolves the call
Expected behavior:
END webhook should fire at actual call end
owner and destination should reflect the final agent who resolved the call
Questions:
Is this behavior (END firing at transfer time) intended or a known bug?
Is there a configuration option to ensure the END webhook fires at true call end?
Is there a way to capture the final agent correctly in the payload for attended transfer scenarios?
Relevant log output