AFAIK, telephony-event has no static payload type, so each endpoint should decide its own payload type for its receiving direction, it has nothing to do with peer/other endpoint, CMIIW. So, I guess you should redirect the question to EyeBeam forum. Regards, nanang On Sun, Oct 19, 2008 at 12:57 PM, fcch2k <fcch2000 at gmail.com> wrote: > Why Eyebeam sends the INVITE ACK with invalid payload 4294967295? > > > On Sat, Oct 18, 2008 at 6:42 AM, Nanang Izzuddin <nanang at pjsip.org> wrote: >> >> Hi, >> >> Payload type value was invalid/out of range (it must be in the range >> of 0-127), as it mentioned by this line: >> 00:23:26.000 sip_inv.c Error parsing SDP in Response msg >> 200/INVITE/cseq=11205 (rdata0012DE54): Invalid SDP payload type in >> media line (PJMEDIA_SDP_EINPT) >> >> Regards, >> nanang >> >> >> On Sat, Oct 18, 2008 at 1:28 PM, fcch2k <fcch2000 at gmail.com> wrote: >> > Hi, >> > >> > What is the reason to get the "SDP offer/answer incomplete, ending the >> > session" in the latest rc4 release? >> > It is happes very often in my rc4 windows XP (or wince5.0) when sends >> > INVITE >> > to eyebeam, and eyebeam repose with payload -1 (4294967295). >> > >> > s=eyeBeam >> > c=IN IP4 99.2.230.157 >> > t=0 0 >> > m=audio 35122 RTP/AVP 0 8 4294967295 >> > a=fmtp:4294967295 0-15 >> > a=rtpmap:4294967295 telephone-event/8000 >> > a=sendrecv >> > >> > >> > Thanks, >> > >> > >> > ================================ >> > 00:23:18.000 tsx00192594 Incoming Response msg >> > 100/INVITE/cseq=11205 >> > (rdata0012DE54) in state Calling >> > 00:23:18.000 tsx00192594 State changed from Calling to Proceeding, >> > event=RX_MSG >> > 00:23:18.000 dlg0019CF84 Received Response msg >> > 100/INVITE/cseq=11205 >> > (rdata0012DE54) >> > 00:23:18.000 dlg0019CF84 Transaction tsx00192594 state changed to >> > Proceeding >> > 00:23:18.000 ec00193DE0 Underflow, buf_cnt=0, will generate 1 >> > frame >> > 00:23:18.000 sip_endpoint.c Processing incoming message: Response msg >> > 180/INVITE/cseq=11205 (rdata0012DE54) >> > 00:23:18.000 pjsua_core.c RX 496 bytes Response msg >> > 180/INVITE/cseq=11205 (rdata0012DE54) from UDP 99.2.230.157:5060: >> > SIP/2.0 180 Ringing >> > Via: SIP/2.0/UDP >> > >> > 192.168.2.104:5060;received=24.6.208.227;rport=5061;branch=z9hG4bKPjD5ZP92kpDSuemPfA3CDa1W9soK6gso3r >> > Record-Route: >> > <sip:99.2.230.157;lr;ftag=0ltQVmV7hboIxDxMSZso0Ob6FlCG5TRR> >> > Contact: <sip:5552 at 24.6.208.227:12340> >> > To: <sip:5552 at 99.2.230.157>;tag=a743b240 >> > From: <sip:5551@99.2.230.157>;tag=0ltQVmV7hboIxDxMSZso0Ob6FlCG5TRR >> > Call-ID: cXOmpFhkzJQCQ1835h1TLW2tH3OOp375 >> > CSeq: 11205 INVITE >> > User-Agent: eyeBeam release 3010n stamp 19039 >> > Content-Length: 0 >> > --end msg-- >> > 00:23:18.000 tsx00192594 Incoming Response msg >> > 180/INVITE/cseq=11205 >> > (rdata0012DE54) in state Proceeding >> > 00:23:18.000 tsx00192594 State changed from Proceeding to >> > Proceeding, >> > event=RX_MSG >> > 00:23:18.000 dlg0019CF84 Received Response msg >> > 180/INVITE/cseq=11205 >> > (rdata0012DE54) >> > 00:23:18.000 dlg0019CF84 Route-set updated >> > 00:23:18.000 dlg0019CF84 Transaction tsx00192594 state changed to >> > Proceeding >> > 00:23:20.000 ec00193DE0 Underflow, buf_cnt=0, will generate 1 >> > frame >> > 00:23:22.000 ec00193DE0 Underflow, buf_cnt=0, will generate 1 >> > frame >> > 00:23:24.000 ec00193DE0 Underflow, buf_cnt=0, will generate 1 >> > frame >> > 00:23:25.000 pjsua_acc.c Sending 2 bytes keep-alive packet for acc >> > 0 to >> > 99.2.230.157:5060 >> > 00:23:25.000 tdta0019FC50 Destroying txdata raw >> > 00:23:25.000 udp00184490 Remote RTCP address switched to >> > 192.168.2.102:9207 >> > 00:23:26.000 sip_endpoint.c Processing incoming message: Response msg >> > 200/INVITE/cseq=11205 (rdata0012DE54) >> > 00:23:26.000 pjsua_core.c RX 833 bytes Response msg >> > 200/INVITE/cseq=11205 (rdata0012DE54) from UDP 99.2.230.157:5060: >> > SIP/2.0 200 OK >> > Via: SIP/2.0/UDP >> > >> > 192.168.2.104:5060;received=24.6.208.227;rport=5061;branch=z9hG4bKPjD5ZP92kpDSuemPfA3CDa1W9soK6gso3r >> > Record-Route: >> > <sip:99.2.230.157;lr;ftag=0ltQVmV7hboIxDxMSZso0Ob6FlCG5TRR> >> > Contact: <sip:5552 at 24.6.208.227:12340> >> > To: <sip:5552 at 99.2.230.157>;tag=a743b240 >> > From: <sip:5551@99.2.230.157>;tag=0ltQVmV7hboIxDxMSZso0Ob6FlCG5TRR >> > Call-ID: cXOmpFhkzJQCQ1835h1TLW2tH3OOp375 >> > CSeq: 11205 INVITE >> > Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, >> > SUBSCRIBE, >> > INFO >> > Content-Type: application/sdp >> > Supported: eventlist >> > User-Agent: eyeBeam release 3010n stamp 19039 >> > Content-Length: 204 >> > >> > v=0 >> > o=- 8793205 8793262 IN IP4 192.168.2.102 >> > s=eyeBeam >> > c=IN IP4 99.2.230.157 >> > t=0 0 >> > m=audio 35122 RTP/AVP 0 8 4294967295 >> > a=fmtp:4294967295 0-15 >> > a=rtpmap:4294967295 telephone-event/8000 >> > a=sendrecv >> > >> > --end msg-- >> > 00:23:26.000 tsx00192594 Incoming Response msg >> > 200/INVITE/cseq=11205 >> > (rdata0012DE54) in state Proceeding >> > 00:23:26.000 tsx00192594 State changed from Proceeding to >> > Terminated, >> > event=RX_MSG >> > 00:23:26.000 dlg0019CF84 Received Response msg >> > 200/INVITE/cseq=11205 >> > (rdata0012DE54) >> > 00:23:26.000 dlg0019CF84 Route-set updated >> > 00:23:26.000 dlg0019CF84 Route-set frozen >> > 00:23:26.000 dlg0019CF84 Transaction tsx00192594 state changed to >> > Terminated >> > 00:23:26.000 sip_inv.c Error parsing SDP in Response msg >> > 200/INVITE/cseq=11205 (rdata0012DE54): Invalid SDP payload type in media >> > line (PJMEDIA_SDP_EINPT) >> > 00:23:26.000 inv0019CF84 Received Response msg >> > 200/INVITE/cseq=11205 >> > (rdata0012DE54), sending ACK >> > 00:23:26.000 endpoint Request msg ACK/cseq=11205 (tdta001A0E90) >> > created. >> > 00:23:26.000 dlg0019CF84 Sending Request msg ACK/cseq=11205 >> > (tdta001A0E90) >> > 00:23:26.000 sip_resolve.c Target '99.2.230.157:0' type=Unspecified >> > resolved to '99.2.230.157:5060' type=UDP (UDP transport) >> > 00:23:26.000 pjsua_core.c TX 407 bytes Request msg ACK/cseq=11205 >> > (tdta001A0E90) to UDP 99.2.230.157:5060: >> > ACK sip:5552 at 24.6.208.227:12340 SIP/2.0 >> > Via: SIP/2.0/UDP >> > >> > 192.168.2.104:5060;rport;branch=z9hG4bKPjSDcs58z-8Ig3SzK5Ph9cpVXloZ0OPHpR >> > Max-Forwards: 70 >> > From: sip:5551@99.2.230.157;tag=0ltQVmV7hboIxDxMSZso0Ob6FlCG5TRR >> > To: sip:5552 at 99.2.230.157;tag=a743b240 >> > Call-ID: cXOmpFhkzJQCQ1835h1TLW2tH3OOp375 >> > CSeq: 11205 ACK >> > Route: <sip:99.2.230.157;lr;ftag=0ltQVmV7hboIxDxMSZso0Ob6FlCG5TRR> >> > Content-Length: 0 >> > --end msg-- >> > 00:23:26.000 inv0019CF84 SDP offer/answer incomplete, ending the >> > session >> > 00:23:26.000 endpoint Request msg BYE/cseq=11207 (tdta001A1EA0) >> > created. >> > 00:23:26.000 inv0019CF84 Sending Request msg BYE/cseq=11207 >> > (tdta001A1EA0) >> > 00:23:26.000 dlg0019CF84 Sending Request msg BYE/cseq=11207 >> > (tdta001A1EA0) >> > 00:23:26.000 tsx001A2F14 Transaction created for Request msg >> > BYE/cseq=11206 (tdta001A1EA0) >> > 00:23:26.000 tsx001A2F14 Sending Request msg BYE/cseq=11206 >> > (tdta001A1EA0) in state Null >> > 00:23:26.000 sip_resolve.c Target '99.2.230.157:0' type=Unspecified >> > resolved to '99.2.230.157:5060' type=UDP (UDP transport) >> > 00:23:26.000 pjsua_core.c TX 407 bytes Request msg BYE/cseq=11206 >> > (tdta001A1EA0) to UDP 99.2.230.157:5060: >> > BYE sip:5552 at 24.6.208.227:12340 SIP/2.0 >> > Via: SIP/2.0/UDP >> > >> > 192.168.2.104:5060;rport;branch=z9hG4bKPjy2jBxf8q3NyLtfPY0NNp6bcPt7NbtT4J >> > Max-Forwards: 70 >> > From: sip:5551@99.2.230.157;tag=0ltQVmV7hboIxDxMSZso0Ob6FlCG5TRR >> > To: sip:5552 at 99.2.230.157;tag=a743b240 >> > Call-ID: cXOmpFhkzJQCQ1835h1TLW2tH3OOp375 >> > CSeq: 11206 BYE >> > Route: <sip:99.2.230.157;lr;ftag=0ltQVmV7hboIxDxMSZso0Ob6FlCG5TRR> >> > Content-Length: 0 >> > >> > >> > _______________________________________________ >> > 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 >> > >> > >> >> _______________________________________________ >> 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 > > > _______________________________________________ > 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 > >
