Hello all, I have an SDP that is being rejected by PJSUA. See error message: 09:47:18.250 sip_inv.c Error parsing/validating SDP body: Invalid SDP payload type in media line (PJMEDIA_SDP_EINPT) 09:47:18.250 pjsua_call.c Bad SDP in incoming INVITE: Invalid SDP payload type in media line (PJMEDIA_SDP_EINPT) [status=220033] 09:47:18.250 pjsua_core.c TX 425 bytes Response msg 400/INVITE/cseq=1 (tdta0x98854e8) to UDP 192.168.30.122:5060: SIP/2.0 400 Bad SDP Via: SIP/2.0/UDP 192.168.30.122:5060;received=192.168.30.122;branch=z9hG4bK90991384-224468 Call-ID: GLPG90991384224467 From: "green995" <sip:green995@192.168.30.122 <mailto:sip%3Agreen995 at 192.168.30.122> >;tag=GLPG_90991384-224469 To: "red005" <sip:red005 at 192.168. <mailto:sip%3APacketProbe005 at 192.168.30.170> 30.170>;tag=z9hG4bK90991384-224468 CSeq: 1 INVITE Warning: 399 red "Invalid SDP payload type in media line (PJMEDIA_SDP_EINPT)" Content-Length: 0 ---------------------------------- The only difference between the rejected SDP and an accepted SDP is as follows (accepted SDP on top): a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 vs a=rtpmap:196 telephone-event/8000 a=fmtp:196 0-15 Googling the SDP RFC did not shed any light, but when I google rtpmap 101 it is repeatedly linked to telephone-event where rtpmap 196 is not. So is that all that is going wrong here? 196 telephone-event/8000 is not valid? Does anyone know where these standards are defined? Thoughts on how to get PJSUA to ignore this and accept the SDP (I'm never actually going to use telephone-event, I only want to use mulaw and g729 - I don't know why telephone event is even being sent)? Thanks, Steven Egan -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20120217/c2665224/attachment.html>
