Yes. That is what I thought. Further research showed we were only seeing packets flowing in one direction!
Thanks, Andrew _____ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Saturday, April 07, 2007 2:55 AM To: [EMAIL PROTECTED] Cc: [email protected]; [EMAIL PROTECTED] Subject: Re: [Sip-implementors] RTP ports Hi Achal, Offer in INVITE contains the RTP receive ports of Caller. Similarly answer contained in 2XX or 1XX contains the RTP receive ports of Callee. As per RFC 3261, - If the initial offer is in an INVITE, the answer MUST be in a reliable non-failure message from UAS back to UAC which is correlated to that INVITE. For this specification, that is only the final 2xx response to that INVITE. That same exact answer MAY also be placed in any provisional responses sent prior to the answer. The UAC MUST treat the first session description it receives as the answer, and MUST ignore any session descriptions in subsequent responses to the initial INVITE. Hence the UAS MUST send an answer in 2xx either by setting all m-lines to zero ( rejecting offer ) or set valid RTP ports in m-lines where it wishes to receive media. With Regards Raghu <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 04/06/2007 08:42 PM To <[email protected]> cc Subject [Sip-implementors] RTP ports I know the INVITE message contains the inviter's RTP port in the m=audio field but how is the recipient's RTP port determined when it is not sent as part of the message detail in the 200 OK message? Many thanks. _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors *********************** Aricent-Unclassified *********************** "DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus." _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
