Yealink SIP-T2 SERIES Administrator's Manual page 341

<?xml version="1.0"?>
<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="1" state="full"
entity="sip:1000@10.2.1.48:5060">
<dialog id="65626" call-id="0_3138198645@10.10.20.31" local-tag="2331766736"
remote-tag="1786911541" direction="initiator">
<state>confirmed</state>
<local>
<identity>sip:1000@10.2.1.48:5060</identity>
<target uri="sip:1000@10.2.1.48:5060"/>
</local>
<remote>
<identity>sip:1@10.2.1.48:5060</identity>
<target uri="sip:1@10.2.1.48:5060"/>
</remote>
</dialog>
<dialog id="65622">
<state>terminated</state>
</dialog>
</dialog-info>
Example of a NOTIFY message (The busy party has finished the call and is available
again. A new notification update from the busy party is received by the caller):
NOTIFY sip:10111@10.10.20.32:5060 SIP/2.0
Via: SIP/2.0/UDP 10.10.20.31:5060;branch=z9hG4bK3431394016
From: <sip:1000@10.2.1.48:5060>;tag=1558968605
To: "10111" <sip:10111@10.2.1.48:5060>;tag=140677866
Call-ID: 0_2584152566@10.10.20.32
CSeq: 5 NOTIFY
Contact: <sip:1000@10.10.20.31:5060>
Content-Type: application/dialog-info+xml
Max-Forwards: 70
User-Agent: Yealink SIP-T23G 44.80.0.60
Subscription-State: active;expires=48
Event: dialog
Content-Length: 217
<?xml version="1.0"?>
<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="4" state="partial"
entity="sip:1000@10.2.1.48:5060">
<dialog id="65644">
<state>terminated</state>
</dialog>
</dialog-info>
Configuring Basic Features
319