You could for instance differentiate the SDP in your offer in recvonly and sendonly:
m=video 1338 RTP/AVP 34 a=recvonly a=rtpmap:34 H263/90000 a=fmtp:34 QCIF=2 m=audio 1340 RTP/AVP 0 a=recvonly a=rtpmap:0 PCMU/8000 m=video 1342 RTP/AVP 34 a=fmtp:34 CIF=2 a=sendonly a=rtpmap:34 H263/90000 m=audio 1344 RTP/AVP 0 a=sendonly a=rtpmap:0 PCMU/8000 and the clients would response with the 'mirrored' counterpart. Stephane van Hardeveld VirtuosoMedia ----- Original Message ----- From: "Jaikar Nalthooru" <[email protected]> To: <[email protected]> Sent: Friday, March 06, 2009 12:53 PM Subject: [Sip-implementors] SIP Conference negotiation Dear All, I am implementing the Audio and Video conferencing in my embedded device using SIP protocol. Due to MIPS constraints, I need to restrict my device to receive encoded video data in QCIF format and send the decoded video data in CIF format(H.264 codec). That means- - MCU receive the encoded video data in QCIF format (low mips intensive) from participants - MCU sends the encoded video data in CIF format to participants My question is how to negotiate the capabilities in SIP? Thanks in advance Best regards Jay _______________________________________________ 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
