4.1.3 Deregistration

  • Article

If the server deregisters a user's endpoint because of policy, it sends a deregister NOTIFY, as follows. Note that such deregistrations are usually triggered by server policies, such as endpoint quota enforcement.

NOTIFY sip:10.1.2.178:4126;transport=tls;ms-opaque=9a9503bcdb;ms-received-cid=600 SIP/2.0
Via: SIP/2.0/TLS 10.1.2.178:5061;branch=z9hG4bKD948963B.BFDD97BF;branched=FALSE;ms-ts="Wed, 06 Feb 2008 00:41:50 GMT 0"
Authentication-Info: Kerberos rspauth="602306092A864886F71201020201011100FFFFFFFFCC4C8119E16FEC024B25E89E96BA0865", srand="AA69CAF1", snum="9", opaque="28CE6668", qop="auth", targetname="sip/ocs.fabrikam.com", realm="SIP Communications Service"
Max-Forwards: 70
Content-Length: 27
From: <sip:alice@fabrikam.com>;tag=25498F391570ACE435E286F873E6AACC
To: sip:alice@fabrikam.com>;tag=7c503117ea;epid=90e62db136
Call-ID: 6d7b09278d574162a4ef50c25e4e5051
CSeq: 1 NOTIFY
Content-Type: text/registration-event
Event: registration-notify
subscription-state: terminated;expires=0
ms-diagnostics-public: 4141;reason="User disabled"
 
deregistered;event=rejected