Add option to disable or ignore SIP back-end admin warning, when SIP is intentionally unused

[EradicationGod]

Tip

How to use GitHub

• Please use the 👍 reaction to show that you are affected by the same issue.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

---

Feature request

Which Nextcloud Version are you currently using:
Nextcloud 34.0.0.12 (Arch Linux. Extra Repository)

Is your feature request related to a problem? Please describe.
Yes. In Nextcloud Talk admin settings / overview, there is a persistent warning:

No SIP back-end configured

This warning is useful for installations that actually want SIP / phone integration, but not every Talk installation needs SIP. Some setups use Talk only for browser/app based calls, with HPB/signaling, TURN/STUN, recording back-end, and whiteboard configured, but no SIP provider or PBX.

In that situation the warning stays visible even though SIP is intentionally not used. This makes the admin overview look like something is mis-configured, while the missing SIP back-end is an intentional choice.

Describe the solution you'd like
Please add an explicit option to mark SIP as unused / disabled / ignored, for example:

SIP back-end: Disabled / Not used

or:

Ignore SIP back-end warning for this instance

When this option is enabled, Talk should stop showing the SIP back-end warning in the admin overview.

This should not disable Talk itself, HPB, TURN/STUN, or recording. It should only tell the admin check that SIP/telephone integration is intentionally not part of this deployment.

Describe alternatives you've considered
The only current alternative is to leave the warning visible, or configure a SIP back-end that is not actually needed. Both are undesirable:

Leaving it visible creates permanent warning noise.
Configuring SIP just to silence a warning makes no sense for deployments without a SIP provider, PBX, or phone-number integration.

Additional context
Example deployment:

Nextcloud Talk is used for normal browser/app calls.
HPB/signaling is configured and working.
TURN/STUN is configured and working.
Recording back-end is configured and working.
Whiteboard back-end is configured and working.
SIP is intentionally not configured because there is no SIP provider, PBX, or phone-number integration requirement.

The request is not to remove the SIP warning globally. The request is to allow administrators to explicitly mark SIP as intentionally unused, so the admin overview does not keep reporting it as a configuration problem.

[nickvergessen]

do you mean this?

That is not a warning but an info level.

[EradicationGod]

Yes, I do mean that sir. It is annoying as heck to someone like me If SIP is not configured at the start, there should be a way to tell the backend it is deliberately disabled. I know it is a warning, but the style and context it conveys, it reads like a warning and not an info text. For people who do not need this functionality or have no access to it, should be able to specify this somewhere, so this annoying infobox is gone. I mean, leave it there as an info text, but let it disappear when a admin/user disables this module in the backend specifically. Thank you

…

On Wed, 24 Jun 2026 at 08:56, Joas Schilling ***@***.***> wrote: *nickvergessen* left a comment (nextcloud/spreed#18401) <#18401 (comment)> do you mean this? grafik.png (view on web) <https://github.com/user-attachments/assets/aa1eec81-283f-4367-9f80-44f69f6137ce> That is not a warning but an info level. — Reply to this email directly, view it on GitHub <#18401?email_source=notifications&email_token=AOSULGMUNZLJX46UC6DKWL35BN3RTA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINZYGY3DONZVGY2KM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-4786677564>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AOSULGPD5BKK6Y7R44MNKUD5BN3RTAVCNFSNUABEKJSXA33TNF2G64TZHM3DOMJRGE2DINR3JFZXG5LFHM2DOMBWHA3DSNRRG6QXMAQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Antreesy]

Shall we wrap it in if ($this->subscription->delegateHasValidSubscription())?

[EradicationGod]

Hi, not sure how, I am not that tech savvy. Still learning a lot on my own programming. I picture a radio button/switch to turn off the module in the backend or flag an ignore state to the SIP info box

…

On Fri, 26 Jun 2026, 14:34 Maksim Sukharev, ***@***.***> wrote: *Antreesy* left a comment (nextcloud/spreed#18401) <#18401 (comment)> Shall we wrap it in if ($this->subscription->delegateHasValidSubscription())? — Reply to this email directly, view it on GitHub <#18401?email_source=notifications&email_token=AOSULGOK3NMNFKHFE3O342T5BZUTVA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOBQHE3DANBSGU4KM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-4809604258>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AOSULGJPYK6XJH435NTNPEL5BZUTVAVCNFSNUABEKJSXA33TNF2G64TZHM3DOMJRGE2DINR3JFZXG5LFHM2DOMBWHA3DSNRRG6QXMAQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>