Vijay, I have seen a lot of impelmentation from ITSP side which returns the public IP address (received IP) of your NAT router whereas you have been sent the local (private) IP in Register. Your system should have some mechanism to know your public IP address (either STUN or Fixed IP) to successfully fetched the expiry timer for specific binding. Else, you would be in trouble if multiple contacts are received in 200 OK with different expiry for each contact.
It would be better if you add some header (I have seen this in some IP Phone which adds 'rinstance' with dynamic value) with contact in Register and you can expect the same header in contact of 200 OK, this will make the work easy to fetch the expiry timer for individual binding from 200 OK. Best Regards, Vivek Batra -----Original Message----- From: sip-implementors-boun...@lists.cs.columbia.edu [mailto:sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of vijay Sent: Sunday, August 30, 2009 12:21 PM To: sip-implementors@lists.cs.columbia.edu Subject: [Sip-implementors] Contact mismatch in 200 resp for Register req Hi, If we get different contact in 200 response for Register request, Is it successful registration? If yes, Can we consider the expires(for reg refresh) value present in the Contact? If no, Please suggest, what should we do? Thanking you in advance. Regards Vijay Email Scanned for Virus & Dangerous Content by : www.CleanMailGateway.com _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
