[asterisk-bugs] [JIRA] (ASTERISK-25400) Hints broken when "CustomPresence" doesn't exist in AstDB

[Andrew Nagy (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-25400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Nagy updated ASTERISK-25400:
-----------------------------------

    Description: 
Four (PJSIP & SIP) extensions:

core show hints:
{code}
1000 at ext-local      : PJSIP/1000&Custom:DN  State:Idle            Presence:available       Watchers  0
1002 at ext-local      : SIP/1002&Custom:DND1  State:Idle            Presence:available       Watchers  0
1003 at ext-local      : PJSIP/1003&Custom:DN  State:Unavailable     Presence:                Watchers  0
1004 at ext-local      : SIP/1004&Custom:DND1  State:Unavailable     Presence:                Watchers  0
{code}

1003 and 1004 were just created, 1000 and 1002 were previously created. 1003 and 1004 don't have "CustomPresence" Asterisk Database trees. Therefore their presence shows up as "" eg NULL. After talking with Josh in IRC about this he all but confirmed that Asterisk should be setting "not_set" when there aren't any CustomPresence states instead of null. Null ends up blocking any and all subscription events

database show CustomPresence:
{code}
/CustomPresence/1000                              : available
/CustomPresence/1002                              : available
{code}

{quote}
12:59 PM <tm1000> file: I guess I should just report on the fact that when Presence is somehow set to a null state (Blank) no hints work
1:00 PM <@file> include the astdb entries for the custom presence
1:02 PM <tm1000> file: yeah there is no “CustomPresence/XXXX” value for those
1:02 PM <tm1000> should we be creating them?
1:02 PM <@file> nope, lack of them should make it not_set
{quote}

If I later add a CustomPresence key into the database then hints work once again

  was:
Four (PJSIP) extensions:

core show hints:
{code}
1000 at ext-local      : PJSIP/1000&Custom:DN  State:Idle            Presence:available       Watchers  0
1002 at ext-local      : SIP/1002&Custom:DND1  State:Idle            Presence:available       Watchers  0
1003 at ext-local      : PJSIP/1003&Custom:DN  State:Unavailable     Presence:                Watchers  0
1004 at ext-local      : SIP/1004&Custom:DND1  State:Unavailable     Presence:                Watchers  0
{code}

1003 and 1004 were just created, 1000 and 1002 were previously created. 1003 and 1004 don't have "CustomPresence" Asterisk Database trees. Therefore their presence shows up as "" eg NULL. After talking with Josh in IRC about this he all but confirmed that Asterisk should be setting "not_set" when there aren't any CustomPresence states instead of null. Null ends up blocking any and all subscription events

database show CustomPresence:
{code}
/CustomPresence/1000                              : available
/CustomPresence/1002                              : available
{code}

{quote}
12:59 PM <tm1000> file: I guess I should just report on the fact that when Presence is somehow set to a null state (Blank) no hints work
1:00 PM <@file> include the astdb entries for the custom presence
1:02 PM <tm1000> file: yeah there is no “CustomPresence/XXXX” value for those
1:02 PM <tm1000> should we be creating them?
1:02 PM <@file> nope, lack of them should make it not_set
{quote}

If I later add a CustomPresence key into the database then hints work once again


> Hints broken when "CustomPresence" doesn't exist in AstDB
> ---------------------------------------------------------
>
>                 Key: ASTERISK-25400
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25400
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 13.5.0
>            Reporter: Andrew Nagy
>
> Four (PJSIP & SIP) extensions:
> core show hints:
> {code}
> 1000 at ext-local      : PJSIP/1000&Custom:DN  State:Idle            Presence:available       Watchers  0
> 1002 at ext-local      : SIP/1002&Custom:DND1  State:Idle            Presence:available       Watchers  0
> 1003 at ext-local      : PJSIP/1003&Custom:DN  State:Unavailable     Presence:                Watchers  0
> 1004 at ext-local      : SIP/1004&Custom:DND1  State:Unavailable     Presence:                Watchers  0
> {code}
> 1003 and 1004 were just created, 1000 and 1002 were previously created. 1003 and 1004 don't have "CustomPresence" Asterisk Database trees. Therefore their presence shows up as "" eg NULL. After talking with Josh in IRC about this he all but confirmed that Asterisk should be setting "not_set" when there aren't any CustomPresence states instead of null. Null ends up blocking any and all subscription events
> database show CustomPresence:
> {code}
> /CustomPresence/1000                              : available
> /CustomPresence/1002                              : available
> {code}
> {quote}
> 12:59 PM <tm1000> file: I guess I should just report on the fact that when Presence is somehow set to a null state (Blank) no hints work
> 1:00 PM <@file> include the astdb entries for the custom presence
> 1:02 PM <tm1000> file: yeah there is no “CustomPresence/XXXX” value for those
> 1:02 PM <tm1000> should we be creating them?
> 1:02 PM <@file> nope, lack of them should make it not_set
> {quote}
> If I later add a CustomPresence key into the database then hints work once again



--
This message was sent by Atlassian JIRA
(v6.2#6252)