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

Rtpengine interface IP family change handling #2647

Open
wants to merge 2 commits into
base: bleeding
Choose a base branch
from

Conversation

itunali
Copy link

@itunali itunali commented May 7, 2024

Type Of Change

  • Small bug fix
  • New feature or enhancement
  • Breaking change

Checklist:

  • Commits are named and have tag following commit rules
  • Commits are split per component (schema, web/admin, kamusers, agis, ..)
  • Changes have been tested locally
  • Fixes an existing issue (Fixes #XXXX)
  • Upport from existing Pull request #XXXX

Description

You should add "address-family=IP4/IP6" parameter for "rtpengine_manage" function when rtpengine interface ip family change via "direction" params. Ex IP6-IP4

Additional information

direction parameters for "rtpengine_manage" are not handle ipv6 to ipv4 interface changes. You should also insert address-family=IP4/IP6 parameter
Rtpengine interface IP family change handling
@Kaian Kaian added +enhancement Enhancement trunks SIP Trunks Proxy users SIP Users Proxy *tempest* IvozProvider 4.x Tempest Release labels Jun 26, 2024
@Kaian Kaian modified the milestone: 4.2.0 Aug 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
+enhancement Enhancement *tempest* IvozProvider 4.x Tempest Release trunks SIP Trunks Proxy users SIP Users Proxy
Development

Successfully merging this pull request may close these issues.

3 participants