Hi, we had the following problem: SEMS gets an SDP offer or answer with one codec mapping to multiple payload types. This is allowed. In our case the second payload type mapping had additional attributes like the following: gpmd:97 vbd=yes.
In this case the expected behaviour is, that the first offered remote payload type is used for sending, if the codec is chosen for sending. However sems always uses the later offered payload type for sending. The attached patch fixes this. Regards, Emil -- Emil Kroymann VoIP Services Engineer Email: [email protected] Tel: +49-30-203899885 Mobile: +49-176-38389303 ISACO GmbH Kurfürstenstraße 79 10787 Berlin Germany Amtsgericht Charlottenburg, HRB 112464B Geschäftsführer: Daniel Frommherz
diff --git a/core/AmRtpStream.cpp b/core/AmRtpStream.cpp
index e2edf80..9e97744 100644
--- a/core/AmRtpStream.cpp
+++ b/core/AmRtpStream.cpp
@@ -572,7 +572,7 @@ int AmRtpStream::init(const AmSdp& local,
}
}
- if(pmt_it != pl_map.end()){
+ if(pmt_it != pl_map.end() && (pmt_it->second.remote_pt < 0)){
pmt_it->second.remote_pt = sdp_it->payload_type;
}
++sdp_it;
signature.asc
Description: PGP signature
_______________________________________________ Semsdev mailing list [email protected] http://lists.iptel.org/mailman/listinfo/semsdev
