Hi, The "a=rtpmap" attributes in the SDP answer below are in session-level, while they must only be in media-level, so it seems the SDP answer below (from the log) is broken and it is quite expected that the format '101' (dynamic payload type) cannot be resolved. v=0 o=EHang 20 001 IN IP4 *.*.*.* s=EH-Call c=IN IP4 *.*.*.* t=0 0 a=rtpmap:101 telephone-event/8000/1 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 m=audio 10000 RTP/AVP 0 8 101 ---------------- Here is what RFC 4566 says about this: Section 5.13: ... Attributes may be defined to be used as "session-level" attributes, "media-level" attributes, or both. ... Section 6: a=rtpmap:<payload type> <encoding name>/<clock rate> [/<encoding parameters>] ... It is a media-level attribute that is not dependent on charset. ... --------------- Regards, nanang On Sat, May 2, 2009 at 4:37 PM, jf <smjxf at 163.com> wrote: > > ? --end msg-- > ?17:07:14.528 ? ?pjsua_acc.c ?sip:813@*.*.*.*: registration success, status=200 (OK), will re-register in 3600 seconds > ?17:07:14.528 ? ?pjsua_acc.c ?Keep-alive timer started for acc 1, destination:*.*.*.*:5060, interval:15s > ?17:07:14.528 ? ? ? ? ? ?APP ?Reg state changed for account 1 :200 > ?17:07:14.528 ? ? ? ? ? ?APP ?Registration success! > ?17:07:19.572 ? pjsua_core.c ?RX 716 bytes Response msg 183/INVITE/cseq=15780 (rdata0x8fa8524) from UDP *.*.*.*:5060: > SIP/2.0 183 Session Progress > From: <sip:813@*.*.*.*>;tag=79ab98ce-5b3d-44ee-894f-ccafd66ff545 > To: <sip:**************@*.*.*.*>;tag=1b71568-d362c652-13c4-a3ce1d-12132177-a3ce1d > Call-ID: ef6d4132-b4b7-49ca-9334-50b215234a80 > CSeq: 15780 INVITE > Via: SIP/2.0/UDP *.*.*.*:5060;rport=5060;branch=z9hG4bKPj9db95156-b19d-44ee-a7b3-89be0b9e79ea > Supported: 100rel,timer,replaces > Require: 100rel > RSeq: 678 > Contact: <sip:**************@*.*.*.*:5060> > Content-Type: application/SDP > Content-Length: 196 > > v=0 > o=EHang 20 001 IN IP4 *.*.*.* > s=EH-Call > c=IN IP4 *.*.*.* > t=0 0 > a=rtpmap:101 telephone-event/8000/1 > a=rtpmap:0 PCMU/8000 > a=rtpmap:8 PCMA/8000 > m=audio 10000 RTP/AVP 0 8 101 > > --end msg-- > ?17:07:19.572 ? ? ? ? ? ?APP ?Call 0 state changed to EARLY (183 Session Progress) > ?17:07:19.572 ? ? ?sip_inv.c ?Error parsing SDP in Response msg 183/INVITE/cseq=15780 (rdata0x8fa8524): Missing SDP rtpmap for dynamic payload type (PJMEDIA_SDP_EMISSINGRTPMAP) > ?17:07:19.572 ? pjsua_core.c ?TX 431 bytes Request msg PRACK/cseq=15781 (tdta0x8fab298) to UDP *.*.*.*:5060: > PRACK sip:**************@*.*.*.*:5060 SIP/2.0 > Via: SIP/2.0/UDP *.*.*.*:5060;rport;branch=z9hG4bKPj91f92143-0171-4808-af3b-7cf899c398cf > Max-Forwards: 70 > From: sip:813@*.*.*.*;tag=79ab98ce-5b3d-44ee-894f-ccafd66ff545 > To: sip:**************@*.*.*.*;tag=1b71568-d362c652-13c4-a3ce1d-12132177-a3ce1d > Call-ID: ef6d4132-b4b7-49ca-9334-50b215234a80 > CSeq: 15781 PRACK > RAck: 678 15780 INVITE > Content-Length: ?0 > > > --end msg-- > ?17:07:19.590 ? udp0x8fa9ce0 ?Remote RTCP address switched to *.*.*.*:10001 > ?17:07:19.769 ? udp0x8fa9ce0 ?Remote RTP address switched to *.*.*.*:10000 > ?17:07:19.786 ? pjsua_core.c ?RX 396 bytes Response msg 200/PRACK/cseq=15781 (rdata0x8fa8524) from UDP *.*.*.*:5060: > SIP/2.0 200 OK > From: <sip:813@*.*.*.*>;tag=79ab98ce-5b3d-44ee-894f-ccafd66ff545 > To: <sip:**************@*.*.*.*>;tag=1b71568-d362c652-13c4-a3ce1d-12132177-a3ce1d > Call-ID: ef6d4132-b4b7-49ca-9334-50b215234a80 > CSeq: 15781 PRACK > Via: SIP/2.0/UDP *.*.*.*:5060;rport=5060;branch=z9hG4bKPj91f92143-0171-4808-af3b-7cf899c398cf > Supported: 100rel,timer,replaces > Content-Length: 0 > > > --end msg-- > ?17:07:21.858 ? pjsua_core.c ?RX 714 bytes Response msg 200/INVITE/cseq=15780 (rdata0x8fa8524) from UDP *.*.*.*:5060: > SIP/2.0 200 OK > From: <sip:813@*.*.*.*>;tag=79ab98ce-5b3d-44ee-894f-ccafd66ff545 > To: <sip:**************@*.*.*.*>;tag=1b71568-d362c652-13c4-a3ce1d-12132177-a3ce1d > Call-ID: ef6d4132-b4b7-49ca-9334-50b215234a80 > CSeq: 15780 INVITE > Via: SIP/2.0/UDP *.*.*.*:5060;rport=5060;branch=z9hG4bKPj9db95156-b19d-44ee-a7b3-89be0b9e79ea > Supported: 100rel,timer,replaces > Contact: <sip:**************@*.*.*.*:5060> > Session-Expires: 1800000;refresher=uas > Content-Type: application/SDP > Content-Length: 196 > > v=0 > o=EHang 20 001 IN IP4 *.*.*.* > s=EH-Call > c=IN IP4 *.*.*.* > t=0 0 > a=rtpmap:101 telephone-event/8000/1 > a=rtpmap:0 PCMU/8000 > a=rtpmap:8 PCMA/8000 > m=audio 10000 RTP/AVP 0 8 101 > > --end msg-- > ?17:07:21.858 ? ? ? ? ? ?APP ?Call 0 state changed to CONNECTING > ?17:07:21.858 ? ? ?sip_inv.c ?Error parsing SDP in Response msg 200/INVITE/cseq=15780 (rdata0x8fa8524): Missing SDP rtpmap for dynamic payload type (PJMEDIA_SDP_EMISSINGRTPMAP) > ?17:07:21.858 ? pjsua_core.c ?TX 403 bytes Request msg ACK/cseq=15780 (tdta0x8ffdf48) to UDP *.*.*.*:5060: > ACK sip:**************@*.*.*.*:5060 SIP/2.0 > Via: SIP/2.0/UDP *.*.*.*:5060;rport;branch=z9hG4bKPj0eeb412d-4734-48f4-aa85-ac40f8e07b46 > Max-Forwards: 70 > From: sip:813@*.*.*.*;tag=79ab98ce-5b3d-44ee-894f-ccafd66ff545 > To: sip:**************@*.*.*.*;tag=1b71568-d362c652-13c4-a3ce1d-12132177-a3ce1d > Call-ID: ef6d4132-b4b7-49ca-9334-50b215234a80 > CSeq: 15780 ACK > Content-Length: ?0 > > > --end msg-- > ?17:07:21.858 ? inv0x9001174 ?SDP offer/answer incomplete, ending the session > ?17:07:21.858 ? pjsua_core.c ?TX 403 bytes Request msg BYE/cseq=15782 (tdta0x8ffef50) to UDP *.*.*.*:5060: > BYE sip:**************@*.*.*.*:5060 SIP/2.0 > Via: SIP/2.0/UDP *.*.*.*:5060;rport;branch=z9hG4bKPjc75c5be6-dd86-41ac-9d8c-062e58d799f5 > Max-Forwards: 70 > From: sip:813@*.*.*.*;tag=79ab98ce-5b3d-44ee-894f-ccafd66ff545 > To: sip:**************@*.*.*.*;tag=1b71568-d362c652-13c4-a3ce1d-12132177-a3ce1d > Call-ID: ef6d4132-b4b7-49ca-9334-50b215234a80 > CSeq: 15782 BYE > Content-Length: ?0 > > ==================== > Error parsing SDP in Response msg 200/INVITE/cseq=15780 (rdata0x8fa8524): Missing SDP rtpmap for dynamic payload type (PJMEDIA_SDP_EMISSINGRTPMAP) > > why?....................................... > -------------- > jf > 2009-05-02 > > > > _______________________________________________ > 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
