[asterisk-bugs] [JIRA] (ASTERISK-24366) Qualify frequency on AoRs is not reflected properly on permanent contacts.

[Joshua Colp (JIRA)]

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

Joshua Colp closed ASTERISK-24366.
----------------------------------

    Resolution: Not A Bug

There doesn't appear to be a bug here. Qualify is supported on permanent contacts and works fine. What doesn't work (and can't) is the expectation that if you store in realtime, make a change there, and go back to your Asterisk that it will have picked up on this. A reload is required.

> Qualify frequency on AoRs is not reflected properly on permanent contacts.
> --------------------------------------------------------------------------
>
>                 Key: ASTERISK-24366
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24366
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip
>    Affects Versions: 13.0.0-beta2
>            Reporter: Mark Michelson
>
> On AoRs, {{qualify_frequency}} can be set, with the idea being that all contacts associated with the AoR have the {{qualify_frequency}} copied onto them. With contacts created through registrations, this works quite well.
> However, for permanent contacts (i.e. those created using the contact= option on an AoR), {{qualify_frequency}} does not work very well. In fact, it appears that the {{qualify_frequency}} is never copied onto the contact at all. Since the contact is permanent, changes to the {{qualify_frequency}} on a realtime AoR essentially don't take effect for permanent contacts.
> Fixing this task requires two changes:
> 1) Ensure that in {{res/res_pjsip/location.c}} that when an AoR is created, the {{qualify_frequency}} of the AoR is copied onto the permanent contacts.
> 2) If possible, alter {{res/res_pjsip/pjsip_options.c}} so that contacts can update their {{qualify_frequency}}.



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