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.

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

[improvement]: Endpoint identifier transport #672

Closed
viktike opened this issue Mar 28, 2024 · 1 comment · Fixed by #602
Closed

[improvement]: Endpoint identifier transport #672

viktike opened this issue Mar 28, 2024 · 1 comment · Fixed by #602
Assignees
Labels
improvement support-level-core Functionality with core support level

Comments

@viktike
Copy link
Contributor

viktike commented Mar 28, 2024

Improvement Description

Add a new identify_by option to res_pjsip_endpoint_identifier_ip
called 'transport' this matches endpoints based on the bound
ip address (local) instead of the 'ip' option, which matches on
the source ip address (remote).

viktike added a commit to viktike/asterisk that referenced this issue Mar 28, 2024
…ddress.

Add a new identify_by option to res_pjsip_endpoint_identifier_ip
called 'transport' this matches endpoints based on the bound
ip address (local) instead of the 'ip' option, which matches on
the source ip address (remote).

UserNote: set identify_by=transport for the pjsip endpoint. Then
use the existing 'match' option and the new 'transport' option of
the identify.

Fixes: asterisk#672
@jcolp jcolp added support-level-core Functionality with core support level and removed triage labels Mar 28, 2024
viktike added a commit to viktike/asterisk that referenced this issue Mar 29, 2024
…ddress.

Add a new identify_by option to res_pjsip_endpoint_identifier_ip
called 'transport' this matches endpoints based on the bound
ip address (local) instead of the 'ip' option, which matches on
the source ip address (remote).

UserNote: set identify_by=transport for the pjsip endpoint. Then
use the existing 'match' option and the new 'transport' option of
the identify.

Fixes: asterisk#672
viktike added a commit to viktike/asterisk that referenced this issue Apr 2, 2024
…ddress.

Add a new identify_by option to res_pjsip_endpoint_identifier_ip
called 'transport' this matches endpoints based on the bound
ip address (local) instead of the 'ip' option, which matches on
the source ip address (remote).

UserNote: set identify_by=transport for the pjsip endpoint. Then
use the existing 'match' option and the new 'transport' option of
the identify.

Fixes: asterisk#672
asterisk-org-access-app bot pushed a commit that referenced this issue Apr 3, 2024
…ddress.

Add a new identify_by option to res_pjsip_endpoint_identifier_ip
called 'transport' this matches endpoints based on the bound
ip address (local) instead of the 'ip' option, which matches on
the source ip address (remote).

UserNote: set identify_by=transport for the pjsip endpoint. Then
use the existing 'match' option and the new 'transport' option of
the identify.

Fixes: #672
asterisk-org-access-app bot pushed a commit that referenced this issue Apr 3, 2024
…ddress.

Add a new identify_by option to res_pjsip_endpoint_identifier_ip
called 'transport' this matches endpoints based on the bound
ip address (local) instead of the 'ip' option, which matches on
the source ip address (remote).

UserNote: set identify_by=transport for the pjsip endpoint. Then
use the existing 'match' option and the new 'transport' option of
the identify.

Fixes: #672
asterisk-org-access-app bot pushed a commit that referenced this issue Apr 3, 2024
…ddress.

Add a new identify_by option to res_pjsip_endpoint_identifier_ip
called 'transport' this matches endpoints based on the bound
ip address (local) instead of the 'ip' option, which matches on
the source ip address (remote).

UserNote: set identify_by=transport for the pjsip endpoint. Then
use the existing 'match' option and the new 'transport' option of
the identify.

Fixes: #672
asterisk-org-access-app bot pushed a commit that referenced this issue Apr 3, 2024
…ddress.

Add a new identify_by option to res_pjsip_endpoint_identifier_ip
called 'transport' this matches endpoints based on the bound
ip address (local) instead of the 'ip' option, which matches on
the source ip address (remote).

UserNote: set identify_by=transport for the pjsip endpoint. Then
use the existing 'match' option and the new 'transport' option of
the identify.

Fixes: #672
asterisk-org-access-app bot pushed a commit that referenced this issue May 9, 2024
…ddress.

Add a new identify_by option to res_pjsip_endpoint_identifier_ip
called 'transport' this matches endpoints based on the bound
ip address (local) instead of the 'ip' option, which matches on
the source ip address (remote).

UserNote: set identify_by=transport for the pjsip endpoint. Then
use the existing 'match' option and the new 'transport' option of
the identify.

Fixes: #672
(cherry picked from commit 62bee37)
asterisk-org-access-app bot pushed a commit that referenced this issue May 9, 2024
…ddress.

Add a new identify_by option to res_pjsip_endpoint_identifier_ip
called 'transport' this matches endpoints based on the bound
ip address (local) instead of the 'ip' option, which matches on
the source ip address (remote).

UserNote: set identify_by=transport for the pjsip endpoint. Then
use the existing 'match' option and the new 'transport' option of
the identify.

Fixes: #672
(cherry picked from commit c8769f3)
asterisk-org-access-app bot pushed a commit that referenced this issue May 9, 2024
…ddress.

Add a new identify_by option to res_pjsip_endpoint_identifier_ip
called 'transport' this matches endpoints based on the bound
ip address (local) instead of the 'ip' option, which matches on
the source ip address (remote).

UserNote: set identify_by=transport for the pjsip endpoint. Then
use the existing 'match' option and the new 'transport' option of
the identify.

Fixes: #672
(cherry picked from commit 7c3e2cf)
@gtjoseph
Copy link
Member

NOTE: The original PR that addressed this issue has been reverted due to security issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
improvement support-level-core Functionality with core support level
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants