Display of audio-codecs(SDP Data)

[Harunbk]

Hello,

thanks for the previous help. I have another little question.

How can the CCM show the current used audio-codec (like opus, G722) or SDP-parameters on the overview page during a call?

I added my user agent (in this case "SIPPER for PhonerLite") to Administration --> User Agents (logged in as root User) and linked it with the profil "Internet Stereo". The profile Internet Stereo is described as "OPUS 256.......".

Or do I have to use a special user agent to use this functionality?

Attached you find some screenshots (I translated the page into german in the meantime).

Thank you in advance!
Best regards

harunbk

[Roog]

Hi!
We have had discussions on how to do this. Currently there is no neat way to get it. The codecs them-self are the only ones knowing what they used. Since there is a list with SDPs exchanged in the action of making a call, and we don't know what they agreed on. If and for the codecs we have API:s to we could get the information, but the possibility varies quite a lot.

There might be a way to parse the SDPs for this. I'm not an expert unfortunately on this. I think @fredrikbergholtz-sr might have tried something. Or knows more?

Since we have the profile list and locations, one way would be to show what's most likely is being used.

Great with the German, I've tried to make sure that everything is translatable. But there is still some minor things that aren't. Would you share the translation to German?

Best regards
Roger

[fredrikbergholtz-sr]

I think that there could be a way, but as Roger said, it isn't very neat.

CCM knows about calls because of the notifications it gets from the SIP server. We have been experimenting with having these notifications contain the actual SDP from the SIP messages. Today, I don't think that we use this anywhere, but it could be made to, at least, provide the information about what could be the current coding algorithm.

At risk of going into way too much detail here, there is a slight confusion/inconsistency about what the SDPs of the offer (typically INVITE) vs answer (typically OK) messages should mean. In ACIP applications we think of it as the offer defines a list of possible options and the answer is the single selection from that list. This interpretation means that the SDP of the answer (OK message) is the one that has most chance of holding the parameter values that are actually used. Note that some SIP UAs might have a different idea about this and specify multiple algorithms in the answer, reserving the right to switch between them at will during the call. This is one of the many points where the SIP standard is ambiguous and somewhat difficult to work with - but so far it is the best we have.