Summary:	ASTERISK-30110: chan_pjsip: endpoints that register elsewhere are not called from app_queue
Reporter:	Jasper Hafkenscheid (jasper.hafkenscheid)	Labels:	patch
Date Opened:	2022-06-14 06:37:07	Date Closed:
Priority:	Minor	Regression?
Status:	Open/New	Components:	Applications/app_queue Channels/chan_pjsip
Versions:	18.12.0	Frequency of Occurrence
Related Issues:
Environment:		Attachments:	( 0) chan_pjsip-rtstatic.patch
Description:	We run opensips instances that manage the sip registrations, without relaying them to Asterisk. This causes the endpoints to be marked as `AST_DEVICE_UNAVAILABLE`. When a call is placed to a registered uac we have a separate service to determine which opensips instance to send the call to. Thus fare it is not so much of an issue, but `app_queue` depends on this status to determine if it should initiate calls to them. This causes calls to not be placed to members. Removing the `state_interface` does work, but will also place calls to members that are already in a call. The fix we implemented is to have an option to always return `AST_DEVICE_UNKNOWN`, which is good enough for app_queue to attempt to ring the endpoint. Would such a patch be appreciated, or is there some other method to get the described scenario to work?
Comments:	By: Asterisk Team (asteriskteam) 2022-06-14 06:37:08.783-0500 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur. Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/]. By: Jasper Hafkenscheid (jasper.hafkenscheid) 2022-06-14 06:39:46.628-0500 patch to introduce rtstatic pjsip setting, resulting in AST_DEVICE_UNKNOWN when not in a call. By: Joshua C. Colp (jcolp) 2022-06-14 06:40:37.631-0500 You can attach the patch if you wish, or put it up for code review. As for doing it some other way the community forum at https://community.asterisk.org/ would be a better location for such a question.