| Summary: | ASTERISK-24366: Qualify frequency on AoRs is not reflected properly on permanent contacts. | ||
| Reporter: | Mark Michelson (mmichelson) | Labels: | |
| Date Opened: | 2014-09-29 11:54:55 | Date Closed: | 2014-10-08 11:16:15 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Resources/res_pjsip |
| Versions: | 13.0.0-beta2 | Frequency of Occurrence | Constant |
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | 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}}. | ||
| Comments: | By: Joshua C. Colp (jcolp) 2014-10-08 11:16:15.915-0500 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. | ||