I cannot reproduce the issue. In my tests after the first publish the rest do have SIP-If-Match header, for example: ``` T 2020/07/30 20:57:06.251465 127.0.0.1:50064 -> 127.0.0.1:5080 [AP] #20 PUBLISH sip:foo@test.tutpro.com SIP/2.0. Via: SIP/2.0/TCP 192.168.43.82;branch=z9hG4bK549a.f9d86324000000000000000000000000.0. To: sip:foo@test.tutpro.com. From: sip:foo@test.tutpro.com;tag=ded145cd44a1108aee8ba0e30b80344c-7d4055df. CSeq: 10 PUBLISH. Call-ID: 24b1a5bf25ad843a-12771@192.168.43.82. Content-Length: 94. User-Agent: OpenSIPg SIP Proxy (5.4.0-0b01 (x86_64/linux)). Max-Forwards: 70. Event: message-summary. Expires: 7776001. SIP-If-Match: a.1594729867.26073.6.12. Content-Type: application/simple-message-summary. P-Flags: 0. .. Messages-Waiting: yes. Message-Account: sip:foo@vm.test.tutpro.com. Voice-Message: 1/0 (0/0). ``` That happens because etag param is included in the json request: ``` Jul 30 20:57:06 char /usr/bin/sip-proxy[12771]: INFO: Executing JSON request <{"jsonrpc":"2.0","method":"pua.publish","params":["sip:foo@test.tutpro.com","7776000","message-summary","application/simple-message-summary",".","a.1594729867.26073.6.12","sip:127.0.0.1:5080;transport=tcp","P-Flags: 0\r\n","Messages-Waiting: yes\r\nMessage-Account: sip:foo@vm.test.tutpro.com\r\nVoice-Message: 1/0 (0/0)\r\n"],"id":1}> from <127.0.0.1> with host <127.0.0.1:6060> ``` Why can't pua_dialoginfo do the same?