4.8 History-Info

  • Article

This section follows the product behavior described in endnote <79>.

The following example shows the History-Info header field inserted by the proxy in the INVITE request forwarded to the registered endpoint.

INVITE sip:192.0.2.1:51152;transport=tls;ms-opaque=bab87d7e6e;ms-received-cid=244100 SIP/2.0
RecordRoute: <sip:server.contoso.com:5061;transport=tls;opaque=state:F:Ci.R2>;ms-rrsig=djvCtpOBl7EzJlJIPA8FZ2TtCdfcZHZduS3M4K_QAA;tag=C2FBFDDF86D85988E2FE9C475D8B20D0
Via: SIP/2.0/TLS 192.168.0.2:5061;branch=z9hG4bK.A1ABD;branched=TRUE;ms-internal-info="bvL4ijJzvRAsUh9KHAufCF_yfKiWpHZduSTBXqAAAA"
Via: SIP/2.0/TLS 192.168.0.3:1199;branch=z9hG4bK94bd;msreceivedcid=A552C00
Authentication-Info: NTLM rspauth="01000000ECFE1CAD61AAC15164000000", srand="AC62DEB8", snum="504", opaque="DC8F829A", qop="auth", targetname="server.contoso.com", realm="SIP Communications Service"
Max-Forwards: 68
Content-Length: 0
From: <sip:Alice@contoso.com>;epid=01010101
To: <sip:Bob@contoso.com>;epid=02020202C
Seq: 39513 
INVITECall-ID: 772937b8-0e12-4639-8c79-9d2ac32f2a56
Contact: <sip:alice@contoso.com;gruu;opaque=user:epid:qIIWS2j5AVeD_HxnQdxmlwAA>
Supported: gruu-10History-Info: <sip:Bob@contoso.com>;index=1