4.3.9 Sending 200 OK Response (Action: Allow Client with Static URL)
The following code is an example of a 200 OK REGISTER response sent back by the server. In this case, the user can get the newer version of the client from the following link specified in the Warning header.
-
https://fabrikam.com/ClientUpdate.html SIP/2.0 200 OK From: <sip:alice@fabrikam.com>;tag=90a265ed3f;epid=a0ae9e6cb0 To: sip:alice@fabrikam.com CSeq: 1 REGISTER Call-ID: 6b2dec5dfd9a4eaf90180bb2f8f699ea ms-keep-alive: UAS; tcp=no; hop-hop=yes; end-end=no; timeout=300 Proxy-Authentication-Info: Kerberos rspauth="602306092A864886F71201020201011100FFFFFFFF104A8EDFA12CC095AAA663DF55824DCB", srand="5E058A82", snum="1", opaque="E0DA4F74", qop="auth", targetname="sip/DB19-LCT.Production.cdmedia.tv", realm="SIP Communications Service" Via: SIP/2.0/TLS 10.2.50.42:1699;ms-received-port=1699;ms-received-cid=200 Contact: <sip:10.2.50.42:1699;transport=tls;ms-opaque=89eaec8ad6;ms-received-cid=200>;expires=7200;+sip.instance="<urn:uuid:c1589240-e660-594f-a8b3-4b55f358cbc1>";gruu="sip:alice@fabrikam.com;opaque=user:epid:QJJYwWDmT1mos0tV81jLwQAA;gruu" Expires: 7200 presence-state: register-action="added";primary-cluster-type="central";is-connected-to-primary="yes" Allow-Events: vnd-microsoft-provisioning,vnd-microsoft-roaming-contacts,vnd-microsoft-roaming-ACL,presence,presence.wpending,vnd-microsoft-roaming-self,vnd-microsoft-provisioning-v2 Supported: adhoclist Server: RTC/3.5 Supported: msrtc-event-categories Warning: 313 lcs.microsoft.com "https://fabrikam.com/ClientUpdate.html" ms-diagnostics: 17002;reason="Invalid Request";source="DB19-LCT.Production.cdmedia.tv";appName="ClientVersionFilter" Content-Length: 0