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?

 

[NickKulkarni]

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

Thank you that worked

 

[ebrowne_sts]

Don't mean to resurrect this thread but is there a reason why the BLF entries are not removed or blanked once the extension is deleted (like in v18)? It will be a pain to go through 76 extensions removing 8-9 deleted extensions one by one!

 

[NickKulkarni]

Don't mean to resurrect this thread but is there a reason why the BLF entries are not removed or blanked once the extension is deleted (like in v18)? It will be a pain to go through 76 extensions removing 8-9 deleted extensions one by one!

That's a very good question and I see there are no answers yet

 

[ebrowne_sts]

That's a very good question and I see there are no answers yet

Haha, love your signature

 

[NickKulkarni]

Haha, love your signature

Thank you, after more years than I care to remember in IT these are the things that I see as reality.
I do wish there was an answer to your question though as it is a real pain in the backside to track down and edit one by one. It seems like a bug if there is no specific reason for the change from the normal behaviour in v18.

 

[ebrowne_sts]

Thank you, after more years than I care to remember in IT these are the things that I see as reality.
I do wish there was an answer to your question though as it is a real pain in the backside to track down and edit one by one. It seems like a bug if there is no specific reason for the change from the normal behaviour in v18.

Agreed. Hopefully a (near) future update resolves this