Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Populate orignally called number into yate headers #10

Open
garw opened this issue Apr 9, 2023 · 0 comments
Open

Populate orignally called number into yate headers #10

garw opened this issue Apr 9, 2023 · 0 comments

Comments

@garw
Copy link
Member

garw commented Apr 9, 2023

A call forward or a group call may cause the called number to change. In order to create transparency about this, we want to populate the originally called number into the yate message and sip headers so that yate to yate sip traffic can also pick up the originally called number
garw added a commit that referenced this issue Apr 9, 2023
@garw
Add original caller to routing info
8f0fb30 
As requested in #10, provide the information
which extension was originally called via SIP
header and as yate parameter. This enables scripts
or apps to identify which extension was called if
they're included in a group call or the call was
forwarded to them.
@garw garw mentioned this issue Apr 9, 2023
Merged
garw added a commit that referenced this issue Aug 18, 2023
@garw
Add original caller to routing info
d8614f7 
As requested in #10, provide the information
which extension was originally called via SIP
header and as yate parameter. This enables scripts
or apps to identify which extension was called if
they're included in a group call or the call was
forwarded to them.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@garw