to be even more compliant to ZRTP spec I added the zrtp-hash
attribute to the SDP part of SIP messages. While implementing
and testing this I also looked into the SDP processing of SC.
As far as I can see SC does not process any codec specific
stuff defined in SDP attributes like rtmap, ftmp but
uses fixed strings and mappings. SC seems to use / implement
SDP codec handling that is not compliant to RFCs 2327, 3264,
1890. SC uses codec numbers in the dynamic range without looking
at rtmap etc.
Is this a correct interpretation of the code in CallSessionImpl?
Just for curiosity: the Jain SIP RI library (latest version)
also seems to have some problems with SDP handling. At least
two methods seem "suspicious":
The description and implementation of these methods somehow
don't map. I'll check that again.
PS: the zrtp-hash attribute does not do any harm to SC SDP
processing :-). I'll do a check-in of CallSessionImpl during
the weekend after some more tests.