NOTIFYs not generated on Hint State Changes

[PitzKey]

Hello,

Asterisk 18.17.1
PJPROJECT version 2.13

It seems like Asterisk simply stops sending a SIP Notify after a while. There are active hint watchers, but when looking at sngrep I don’t see any NOTIFY being sent.

Changing the state to InUse:

root@pbx2:~# asterisk -x "core show hints" | grep DND_105@T3
DND_105@T3_extension: Custom:T3_DND_105     State:InUse           Presence:not_set         Watchers  4

Then we changed it back:

root@pbx2:~# asterisk -x "core show hints" | grep DND_105@T3
DND_105@T3_extension: Custom:T3_DND_105     State:Unavailable     Presence:not_set         Watchers  4

But no NOTIFY was sent.

If we add a new watcher, Asterisk will send a NOTIFY only to the 5th new watcher, and not to the previous 4 watchers.

Appreciate any pointers.

Thanks

[jcolp]

There is core debug logging around device state and other things, so the first step would be to get a log[1] and see if anything stands out. There is also the “pjsip show subscriptions inbound” CLI command to verify that the subscriptions are actually still active.

[1] Collecting Debug Information - Asterisk Documentation

[PitzKey]

Thanks. I’ll try to get a log.

Looking at the inbound subs I see the below:

Endpoint: GT105/"John Doe" <105>
Resource: DND_105/dialog
  Expiry:        0  106712756351905-581141140314699@REMOTE_WAN_IP

Endpoint: GT105/"John Doe" <105>
Resource: DND_105/dialog
  Expiry:        0  371454462044969-360622824216565@REMOTE_WAN_IP

Endpoint: GT105/"John Doe" <105>
Resource: DND_105/dialog
  Expiry:        0  611255120157165-245104492615373@REMOTE_WAN_IP

Endpoint: GT105/"John Doe" <105>
Resource: DND_105/dialog
  Expiry:      769  469964006827744-641356236947188@REMOTE_WAN_IP

Does Expiry 0 indicate that it is expired? And 769 is the amount of seconds until it expires?

[jcolp]

Yes, and yes. I’m also not sure why the subscription is still active there - but I recall changes being done in that area and multiple fixes being done.

[PitzKey]

I see. It seems to me like the issues were introduced after updating PJSIP to 2.13, but I may be wrong.

I see some work was done to correct this under: [ASTERISK-30469] res_pjsip_pubsub: Regression for subscription shutdowns - Digium/Asterisk JIRA

[jcolp]

If it can be reproduced under the current release then please file an issue on Github.