Dzmitry Yablonski wrote: > Hello > > I have tested the codec iLBC and found that PjSip does mismatch RFC 3264 for dynamical payload types (all types). > > According the RFC 3264 (section 6.1 Unicast Stream ) http://tools.ietf.org/html/rfc3264 > In the case of RTP, if a particular codec was referenced with a > specific payload type number in the offer, that same payload type > number SHOULD be used for that codec in the answer. Even if the same > payload type number is used, the answer MUST contain rtpmap > attributes to define the payload type mappings for dynamic payload > types, and SHOULD contain mappings for static payload types. > Details you can find in attached log. > Sip client one Capanga - IP 10.0.0.145 > Sip client two dialer based on pjproject ver 1.8.5 - IP 10.0.0.151 > Server Asterisk - IP 10.0.0.122 > > payload for codec iLBC in invite from 10.0.0.145 = 98 payload for codec iLBC in invite from 10.0.0.122 = ??? Is the call routed via Asterisk? If yes, what payload type uses Asterisk? regards klaus > payload for codec iLBC in 200 OK from pjproject = 109 (should be same as in invite 98) > > Any suggestion for solving this problem? > > Best regards, Dzmitry. > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip at lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
