Check out STUN regarding that. SIP Never check for the preseence of NAT. There are few additional parameters such as rport in SIP.
Regards, Kannaiyan ----- Original Message ----- From: "Thirumal Margabandhu" <[EMAIL PROTECTED]> To: "Gary Cote" <[EMAIL PROTECTED]> Cc: <[email protected]> Sent: Tuesday, March 20, 2007 2:16 PM Subject: Re: [Sip-implementors] Difference between SIP phone and IP phone > thanks Gary cote. > > Actually my question on SIP NAT , when we configure our SIP client > behind NAT setup, how will we know 'the type of NAT', the type NAT > information where it will be present in SIP message. > so this is my question on SIP NAT. > > > > > Thanks & Regards, > Thirumal Margabandhu > > ARICENT, > RR4,Guindy,Chennai. > Dir Line:044-44225657 > > > > > "Gary Cote" <[EMAIL PROTECTED]> > 03/19/2007 07:52 PM > > > To > Thirumal Margabandhu/CHE/[EMAIL PROTECTED] > cc > [email protected] > Subject > Re: [Sip-implementors] Difference between SIP phone and IP phone > > > > > > >> >> 1. How could be differented SIP softphone and IP phone. >> > > A "softphone" generally refers to a software-based VoIP endpoint that > runs, > for example, on a PC. A "SIP softphone" is simply a softphone that uses > SIP > as its signaling protocol. > > An "IP phone" generally refers to a hardware-based VoIP endpoint that runs > as a stand-alone network node. As you might've guessed, a "SIP phone" is > simply an IP phone that uses SIP as its signaling protocol. > >> >> 2.When we configure SIP client as behind NAT setup, in which SIP section >> describe the 'type of NAT' in SIP messages. >> > > I'm sorry, but I don't understand your question. We don't describe the > type of > NAT in SIP messages (at least, not that I'm aware of). > > I'd suggest reading up on SIP NAT traversal issues and solutions. I > wish I could > be more helpful than that. > > -- > Gary Cote > www.awardsolutions.com > > > > *********************** 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 > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
