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

Allow custom configurations via json file input to replace default rtpengine parameters #225

Open
psanders opened this issue Sep 27, 2023 · 0 comments

Comments

@psanders
Copy link
Member

Is your feature request related to a problem? Please describe.

Currently, the RTPRelay module hardcodes the Offer/Answer parameter according to the most common use case for Routr. This approach limits the flexibility for users who may have different requirements based on specific use cases.

Describe the solution you'd like

Allow users to overwrite the default parameters by passing a JSON file with their own configurations. The file could look as follows:

{
  "webToWeb": {
    "ICE": "force",
    "SDES": "off",
    "flags": ["trust-address", "replace-origin", "replace-session-connection"]
  },
  "webToPhone": {
    "transport-protocol": "RTP/AVP",
    "rtcp-mux": "demux",
    "ICE": "remove",
    "flags": ["trust-address", "replace-origin", "replace-session-connection"]
  },
  "phoneToWeb": {
    "transport-protocol": "UDP/TLS/RTP/SAVPF",
    "rtcp-mux": "required",
    "ICE": "force",
    "SDES": "off",
    "flags": ["trust-address", "replace-origin", "replace-session-connection", "generate-mid"]
  },
  "phoneToPhone": {
    "transport-protocol": "RTP/AVP",
    "rtcp-mux": "demux",
    "ICE": "remove",
    "flags": ["trust-address", "replace-origin", "replace-session-connection"]
  }
}

Describe alternatives you've considered

As of now, implementing the ability to pass a JSON file for configurations seems like a more efficient solution.

Additional context

N/A

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant