Hello Md Faruk Apel Chowdhury ,
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++ http://tools.ietf.org/html/rfc3261#section-8.1.1.8 8.1.1.8 Contact The Contact header field provides a SIP or SIPS URI that can be used to contact that specific instance of the UA for subsequent requests. The Contact header field MUST be present and contain exactly one SIP or SIPS URI in any request that can result in the establishment of a dialog. For the methods defined in this specification, that includes only the INVITE request. For these requests, the scope of the Contact is global. That is, the Contact header field value contains the URI at which the UA would like to receive requests, and this URI MUST be valid even if used in subsequent requests outside of any dialogs. If the Request-URI or top Route header field value contains a SIPS URI, the Contact header field MUST contain a SIPS URI as well. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Your listen port is the port that you have provided into REGISTER's CONTACT. ( where UA will send a new request to you). For INVITE initiate by you there is no reason to have two listen ports just because you have two calls. You already have different dialogs based on call-id Thanks! Valdemar -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of ext Md Faruk Apel Chowdhury Sent: Wednesday, April 13, 2011 4:57 AM To: [email protected] Subject: [Sip-implementors] new request from called to Caller For a new request INVITE , with new call- ID , What should be the listening port. A# B# INVITE Contact: 10.129.32.20:5064 Call _Id: X New INVITE Contact:10.129.160.4:5064 Call_id: Y New INVITE contact port should be 5064 or 5060(default SIP port) Appreciate answer with RFC [cid:[email protected]] ________________________________ The content of this email together with any attachments, statements and opinions expressed herein contains information that is private and confidential are intended for the named addressee(s) only. If you are not the addressee of this email you may not copy, forward, disclose or otherwise use it or any part of it in any form whatsoever. If you have received this message in error please notify [email protected] by email immediately and delete the message without making any copies. _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
