Scheduling destruction of SIP dialog '3454b5824281b22730679d827108bbd6@210.5.19.5' in 6400 ms (Method: NOTIFY)
Reliably Transmitting (NAT) to 110.33.18.4:1031:
NOTIFY sip:3019@192.168.0.33:5065 SIP/2.0
Via: SIP/2.0/UDP 210.5.19.5:5060;branch=z9hG4bK5ca3ed5c;rport
From: "asterisk" <sip:asterisk@210.5.19.5>;tag=as360397b9
To: <sip:3019@192.168.0.33:5065>
Contact: <sip:asterisk@210.5.19.5>
Call-ID: 3454b5824281b22730679d827108bbd6@210.5.19.5
CSeq: 102 NOTIFY
User-Agent: Thomson TG782T Build 8.2.3.8
Max-Forwards: 70
Event: message-summary
Content-Type: application/simple-message-summary
Content-Length: 94

Messages-Waiting: yes
Message-Account: sip:asterisk@210.5.19.5
Voice-Message: 7/2 (0/0)

---
voip01*CLI>
<--- SIP read from 110.33.18.4:1031 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 210.5.19.5:5060;branch=z9hG4bK5ca3ed5c;rport
From: "asterisk" <sip:asterisk@210.5.19.5>;tag=as360397b9
To: "3019" <sip:3019@192.168.0.33:5065>;tag=BBC4ADA5-169E8B6C
CSeq: 102 NOTIFY
Call-ID: 3454b5824281b22730679d827108bbd6@210.5.19.5
Contact: <sip:3019@192.168.0.33:5065>
Event: message-summary
User-Agent: PolycomSoundPointIP-SPIP_320-UA/3.2.3.1734
Accept-Language: en
Content-Length: 0