Activity Log Spam: "DI.ADS(1758526) can not subscribe to non-extension: sip:[email protected]:5060"

[acs4]

At least 4 times per minute I'm seeing messages like the above in the activity log on a client's system. There's no obvious problem, but I don't want the clutter in the logs.

It's right, there is no extension 220, although there might have been in the past. I have a suspicion this relates to the M365 integration but it's a just guess. Can anyone help me with this?

 

[T3chn!k3r]

Yep, same here, with other contents in the log-string.
We have not configured any integration.
DI.ADS(38746) can not subscribe to non-extension: sip:[email protected]:5060

 

[wizards]

Here too - any clues? It's an ext number we deleted a year or more ago and before upgrading to v.20.

 

[pauls23]

Had the same issue with 4 extensions, they are deleted users in the past with v16 and v18.
Currently running v20 and tested the following:
1) Adding as dummy extensions with the noted extension number will stop the activity log entries.
2) Deleting them after 5 minutes will start creating the same logging again.
Looks like some remnants in the database that needs cleaning up.

 

[gmag]

Same here with deleted user. Version 20.0.2.715.

 

[jenos]

I am having the same problem Version 20.0 Update 2 (Build 715 Release). Any idea how to get this to stop without having to recreate the ext?

 

[KMorley]

I'm seeing similar symptoms.

Our system is Version 20.0 Update 2 (Build 715 Release) - 8 SC - Hosted by 3CX.

Every ten minutes a new entry is added to the Activity Log:

08/15/2024 9:51:49.426 AM	DI.ADS(944182) can not subscribe to non-extension: sip:[email protected]:5060
08/15/2024 9:41:49.146 AM	DI.ADS(943017) can not subscribe to non-extension: sip:[email protected]:5060
08/15/2024 9:31:48.876 AM	DI.ADS(941874) can not subscribe to non-extension: sip:[email protected]:5060
08/15/2024 9:21:48.433 AM	DI.ADS(940706) can not subscribe to non-extension: sip:[email protected]:5060

We do not have an extension 229. This installation is less than six months old and it's possible I created an extension 229 by mistake and then later deleted it. I don't recall doing that, but it's possible.

This is not causing any real problems, but just clutters-up the Activity Log.

 

[Connectify]

Same issue here....

V20.0.2.715, 32SC hosted in our data centre.

(replaced PBX internal IP by xxx.xxx.xxx.xxx for privacy reasons)

26-08-2024 14:42:42.863	DI.ADS(1512706) can not subscribe to non-extension: sip:*[email protected]:5060
26-08-2024 14:42:41.535	DI.ADS(1512688) can not subscribe to non-extension: sip:*[email protected]:5060
26-08-2024 14:32:42.792	DI.ADS(1510103) can not subscribe to non-extension: sip:*[email protected]:5060
26-08-2024 14:32:41.296	DI.ADS(1510094) can not subscribe to non-extension: sip:*[email protected]:5060
26-08-2024 14:22:42.569	DI.ADS(1507194) can not subscribe to non-extension: sip:*[email protected]:5060
26-08-2024 14:22:41.272	DI.ADS(1507191) can not subscribe to non-extension: sip:*[email protected]:5060

 

[fender]

I have the same Problem, but I think I fixed it for me.
First I created the deleted Ext. and deleted them again, but I think this was not the Fix.
Some of my User have these extensions as BLF configured. After deleting the BLF, SPAMing stops.

3CX V 20.0 U3 B659

 

[JohnS_3CX]

This happens when you have an invalid BLF on an IP phone (whether added manually or by deleting the extension the BLF points to).

 

[David Forster]

This happens when you have an invalid BLF on an IP phone (whether added manually or by deleting the extension the BLF points to).

Thanks John, any easy way of telling which extension it is with the rogue BLF buttons?

 

[garyasher]

I have the same Problem, but I think I fixed it for me.
First I created the deleted Ext. and deleted them again, but I think this was not the Fix.
Some of my User have these extensions as BLF configured. After deleting the BLF, SPAMing stops.

3CX V 20.0 U3 B659

Thanks, this fixed my issue.

 

[David Liddle]

Thanks John, any easy way of telling which extension it is with the rogue BLF buttons?

Hi there, I just saw the same error messages on my own system. I don't know if a more verbose log would reveal the phone, but I found mine by searching the PBX configuration file that I pulled from a backup. It's going to be tucked inside a string that looks like this:

<BLF BLFNo="10" BLFType="BLF" BLFTypeID="0" ID="52">1234</BLF>

Where the segment "&gt;1234&lt;" contains the deleted extension number. Searching backwards from that point for "<Number>" will reveal the extension that has that BLF configured.

 

[Martin_Thomas_HPA]

Hi, is there an easy way to find the extensions who have configured the non existing extensions as BLF. We have >1000 of users....

 

[fxbastler]

Hi, is there an easy way to find the extensions who have configured the non existing extensions as BLF. We have >1000 of users....

Not easy but possible and repeatable: powershell.
Get all extensions, search for the parameter SHARED_BLFS in each extension (this is an XML file without line breaks), check whether there are any non-existent BLF extension and delete the whole <BLF> entry.

Another solution may be using the new v20 REST API.

 

[Martin_Thomas_HPA]

Not easy but possible and repeatable: powershell.
Get all extensions, search for the parameter SHARED_BLFS in each extension (this is an XML file without line breaks), check whether there are any non-existent BLF extension and delete the whole <BLF> entry.

Another solution may be using the new v20 REST API.

Hello,
our 3cx is running on Debian..... There is no powershell !?

 

[fxbastler]

our 3cx is running on Debian..... There is no powershell !?

# install Powershell on Debian10 (3CX v16 / v18) or Debian12 (3CX v20):
# https://learn.microsoft.com/de-de/powershell/scripting/install/install-debian?view=powershell-7.4
#
#   source /etc/os-release
#   wget -q https://packages.microsoft.com/config/debian/$VERSION_ID/packages-microsoft-prod.deb
#   dpkg -i packages-microsoft-prod.deb
#   wget https://github.com/PowerShell/PowerShell/releases/download/v7.4.4/powershell_7.4.5-1.deb_amd64.deb
#   dpkg -i powershell_7.4.5-1.deb_amd64.deb
#   apt install -f

 

[Martin_Thomas_HPA]

Thank you. But i have found a way with the API and Postman....

 

[fxbastler]

Thank you. But i have found a way with the API and Postman....

Yes, that works really well and is officially supported. It just takes longer. We then use the REST API with Powershell.

 

[tomdou]

export extensions via admin web interface and in csv filter >extension number< (including><) - not so cool, but fastest i guess...