Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Codec / Transcoding information returned by ng query

Open
  • Is something wrong?
#1,807 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 3 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
20/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
perl
Domain
audio-video-rtc

Research direction

Start from the handler that builds the ng query reply in the rtpengine control protocol and see what per-call state is already available there. Codec selection is decided during SDP handling for the A-leg and B-leg media streams, so trace where negotiated codecs and any transcoding decision are recorded on the call. Nothing in the issue names files or tests, so locating those entry points is the first task. Done means the ng query output reports A-leg and B-leg codecs plus a flag for whether transcoding was engaged.

Written by the indexing model from the issue text.

Description

Is your feature request related to a problem? Please describe

When a call is established and the ng query command is ran, we get a lot of useful information about what is happening, however this information about what codecs are being used.

This is particularly important if we want to limit the amount of transcoded calls which are allowed to pass through a system. By being able to know if transcoding was engaged for a specific call we can better help to control the capacity allowed from OpenSIPs/Kamalio, etc.

Describe the solution you'd like

If RTPEngine is aware of what codec's are used the information should be available in the response to the ng query command.

This can include:

  1. A-leg / B-leg codecs which are used
  2. Has the call been transcoded
Describe alternatives you've considered

There is no simple feasible solution.

The rtpengine version you checked that didn't have the feature you are asking for

12.1.1

Dominant language
Perl
Stars
992
Forks
459
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from sipwise/rtpengine

All issues in sipwise/rtpengine

Similar issues

More Perl issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.