You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
A-leg / B-leg codecs which are used
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
The text was updated successfully, but these errors were encountered:
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:
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
The text was updated successfully, but these errors were encountered: