Can the same logic be applied to 'fmtp'? I mean, if I offer some video codec with 'a=fmtp:31 QCIF=2', does it mean I want to receive QCIF/15fps? So, the other side can accept it and in the answer it may send 'a=fmtp:31 CIF=1', indicating it want to receive CIF/30fps. This means we end up with a call that we send CIF/30fps and we receive QCIF/15fps. Is that correct?
Thanks, Erez -----Original Message----- From: Diego B [mailto:[EMAIL PROTECTED] Sent: Monday, January 23, 2006 2:38 PM To: Erez Morabia Cc: Even, Roni; [email protected] Subject: Re: [Sip-implementors] Asymmetric media format Hi; yes, correct. Yuo will send paquets marked with payload 97, and ready to receive wit payload 96. Erez Morabia wrote: >Hi, >So, if I understand you right, it means that the list of video media >format numbers indicate only which payload type should be in the >incoming RTP payloads. >In such case, if I sent the below offer, then the other side can send an >answer with: > m=video 6794 RTP/AVP 97 > a=rtpmap:97 H263-2000/90000 > a=sendrecv > >....and this means the other side accepted my offer, but it want to >receive the RTP with payload 97. > >Is that correct? > >Thanks, >Erez > >-----Original Message----- >From: Diego B [mailto:[EMAIL PROTECTED] >Sent: Monday, January 23, 2006 2:23 PM >To: Erez Morabia >Cc: Even, Roni; [email protected] >Subject: Re: [Sip-implementors] Asymmetric media format > >Hi; >This is your offer, or answer,and it states where ae you ready to >receive packets for payload 96 >The other side maybe has statically configured payload types and 96 is >used for some other media ( DTMF maybe ). > >Regards > >Erez Morabia wrote: > > > >>I see. Thanks. >>I have another question in the same area. >>If I send the following offer: >>m=video 6794 RTP/AVP 96 >>a=rtpmap:96 H263-2000/90000 >>a=sendrecv >>Does it mean that the dynamic payload 96 should be used in RTP for both >> >> >directions? > > >>Is it possible to use different payload type for each direction? If >> >> >yes, how do I indicate that in the offer/answer SDP model? > > >>Thanks, >>Erez >> >>________________________________________ >>From: Even, Roni [mailto:[EMAIL PROTECTED] >>Sent: Tuesday, January 17, 2006 10:38 AM >>To: Erez Morabia; [email protected] >>Subject: RE: [Sip-implementors] Asymmetric media format >> >>Hi, >>For the b= qualifier look in >> >>http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdp-new-25.txt >> >>and >> >>http://www.ietf.org/rfc/rfc3890.txt >> >>The current H.261 draft is >> >>http://www.ietf.org/internet-drafts/draft-ietf-avt-rfc2032-bis-11.txt >> >> >>Roni Even >> >>-----Original Message----- >>From: Erez Morabia [mailto:[EMAIL PROTECTED] >>Sent: Tuesday, January 17, 2006 10:34 AM >>To: Even, Roni; [email protected] >>Subject: RE: [Sip-implementors] Asymmetric media format >> >>Hi, >>I have looked into RFC 4317 (SDP Offer/Answer Examples), but I could >> >> >not > > >>find example related to this issue. >>I know that some vendors do use the MaxBR field. Where can I find the >>payload specification? >> >>Thanks, >>Erez >> >>-----Original Message----- >>From: Even, Roni [mailto:[EMAIL PROTECTED] >>Sent: Tuesday, January 17, 2006 9:51 AM >>To: Erez Morabia; [email protected] >>Subject: RE: [Sip-implementors] Asymmetric media format >> >>Hi, >>I think it is OK. >>The problem I see is with the MaxBR field. I am not aware that it is in >>the payload specification. >>You should use b=AS:440 or b=TIAS:440000 for each m line >>Roni Even >> >>-----Original Message----- >>From: [EMAIL PROTECTED] >>[mailto:[EMAIL PROTECTED] On Behalf Of Erez >>Morabia >>Sent: Tuesday, January 17, 2006 8:23 AM >>To: [email protected] >>Subject: [Sip-implementors] Asymmetric media format >> >>Hi, >>Suppose I want to announce different format parameters for the receive >>direction and for the transmit direction. >>For example, >>Receive : QCIF, 110Kbps, 15fps >>Transmit: CIF, 440Kbps, 30fps >> >>Is there a way for doing it? >> >>The only thing I can think of is: >>m=video 6794 RTP/AVP 31 >>a=rtpmap:31 H261/90000 >>a=fmtp:31 CIF=1/MaxBR=4400 >>a=sendonly >>m=video 6794 RTP/AVP 31 >>a=rtpmap:31 H261/90000 >>a=fmtp:31 QCIF=2/MaxBR=1100 >>a=recvonly >> >>Thanks, >>Erez >> >> >>_______________________________________________ >>Sip-implementors mailing list >>[email protected] >>https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors >> >>_______________________________________________ >>Sip-implementors mailing list >>[email protected] >>https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors >> >> >> >> > > > > -- ------------------------------------------------------------------------ Regards, Diego B (:-:) MailVision Ltd. *tel*:+97248508000;ext=102 <callto:+97248508000> *mailto*:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> *sip*:[EMAIL PROTECTED] <sip:[EMAIL PROTECTED]> *http*://www.mailvision.com <http://www.mailvision.com/> MailVision End to End SIP Solutions <http://www.mailvision.com/> See us at 3GSM Barcelona <http://www.3gsmworldcongress.com/> <http://www.3gsmworldcongress.com/> _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
