SIP Client Data

SIP client data is available for SIP-based VoIP clients. The data in these fields is based on the Request for Comments (RFC) for SIP: Session Initiation Protocol.

 SIP: the version of SIP implemented and the current status of the connection.

 Via: the IP address of the LANsurveyor computer (which receives the response to the SIP request) and a branch parameter that identifies this request (transaction).

 From: the display name ("LANsurveyor") and a SIP or SIPS URI that indicate the originator of the request (sip:LANsurveyor). There is also a tag parameter containing an identification string.

 To: the display name and a SIP or SIPS URI that indicate the request destination (the map node).

 Call-ID: a globally unique identifier for the current request.

 CSeq: the Command Sequence contains a request ID and the name of the request LANsurveyor made to populate these data fields.

 Contact: contains a SIP or SIPS URI that represents a direct route to the node, usually composed of a username at a fully qualified domain name (FQDN). While an FQDN is preferred, many end systems do not have registered domain names, so IP addresses are permitted. While the Via header field tells other elements where to send the response, the Contact header field tells other elements where to send future requests.

 User-Agent: the type of SIP device (which may also include the specific software version).

 Accept-Language: the preferred language for the transaction.

 Accept: the type of message body acceptable in the response.

 Allow: a list of commands supported by the node.

 Allow-Events: a list of events supported by the node.

 Supported: the list of SIP option tags supported.

 Content-Length: a byte count of the message body.