System Account logging into ASA every day at same time and changing one station?

[avayatech2018]

OK we have a weird one today. I'm new to Avaya as of April. We're a two person Telecom team. My co-worker just retired and we have his replacement working here now. We changed the name on the extension and put her name on. We discovered it wasn't staying. Scratching our heads now. And she actually brings about 15 years Avaya experience to the table so I'm glad to have her. She did some digging and in looking at List History we find an account that seems to log in every day at 11:46 am and appears to change the name back on the extension? Is this even possible?? It appears if we leave it with the old name the account logs in and does nothing. But like this morning she changed it to her name and then at 11:46 today it logged in and changed it back. Are we crazy?

"10/22","11:52","MAINT","us","logf","",""
"10/22","11:47","MAINT","us","cha","station","3066"
"10/22","11:47","MAINT","us","cha","station","3066"
"10/22","11:46","MAINT","us","cha","secondary-us",""
"10/22","11:46","MAINT","us","logn","",""

40 years in Telecom. New to Avaya! Go easy.

 

[kyle555]

us smells like utility server. I mean, something's doing it. stat login will catch the IP when it happens. Might be a ssh log you can see too to figure out the IP.

Hmmm...maybe MyPhone. The Utility Server has a web application to manage your phone settings. Something basic you login with your extn+set passwd to and can set call forwarding and stuff. Maybe change the station security code and log in to myphone for that extension and see if there's something in there.

The utility server should have somewhere where you can see it's cm login info as well, so that'll tell you if it happens to be the mysterious 'us' that's logging in.

 

[AvayaTier3]

Sounds like System Manager is out of sync with CM
When you use System Manager for CM changes, CM and System Manager sync up.
If you then use ASA and make changes with CM command, they may revert back when System Manager syncs with CM.

You can change your logging-level in CM to include before and after for your changes and they will be logged in /var/log/ecs/commandhistory files.





A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

45 years Bell, AT&T, Lucent, Avaya
Tier 3 for 35 years and counting
[URL unfurl="true"]http://bshtele.com[/url]

 

[jordy5535]

Make sure your user's account in SM has the field "Override Endpoint Name and Localized Name" unchecked. Otherwise SM will change the name in CM every night

 

[avayatech2018]

Thanks for the responses. I think it might have pointed us in the right direction. Will update when we know more.

40 years in Telecom. New to Avaya! Go easy.

 

[avayatech2018]

So yes it was in System Manager. We mostly only have SIP devices built in System Manager. But that extension had a SIP account built. I found where I could change the name and it fixed the account in ASA. I still have lots to learn on this Avaya. As far as the SIP accounts it appears to have a listing for both servers. Primary and backup. I can't seem to change the name on the backup entry but it has not been an issue. I'm still looking at it in my spare moments. I need to understand it better. The reason I didn't think about it being in System Manager is because it mostly only holds our SIP conference phones.

Thanks again for the response. I really appreciate your help everyone!!

40 years in Telecom. New to Avaya! Go easy.