UniMRCP-Client ignores asymmetric Payload Type negotation

Created by: schlagert

I just found that the UniMRCP client does not correctly handle asymmetric payload types that were otherwise correctly negotiated using SDP. The client (library) does ignore the fact, that the server sent a matching codec with a different payload type.

How to reproduce? Configure an UniMRCP-based server with

<codecs own-preference="true">L16/96/8000</codecs>

Configure an UniMRCP-based client (e.g. asrclient) with

<codecs>L16/97/8000</codecs>

When trying to run a scenario, the SDP found in the client logs will totally ignore and therefore miss payload type 96.