Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Attd bombarded with login violations from unknown extension 1

Status
Not open for further replies.

dracas

Technical User
Oct 26, 2009
13
US

Hey guys...having a weird issue here. I got a weird call earlier from our Switchboard guy, saying that he kept getting this "Login Violation" issue that kept screwing with his ability to answer calls. Below is a log of the trace

11:50:25 busy attendant 3330 cid 0x1191
11:50:25 idle cid 0x1191
11:50:27 Calling party cid 0x1193
11:50:27 Calling Number & Name 3213 Login Violati
11:50:27 dial 3330
11:50:27 busy attendant 3330 cid 0x1193
11:50:27 idle cid 0x1193
11:50:53 Calling party cid 0x1197
11:50:53 Calling Number & Name 3213 Login Violati
11:50:53 dial 3330
11:50:53 busy attendant 3330 cid 0x1197
11:50:53 idle cid 0x1197

I'm not understanding whats going on here, when I try to look up 3213, it says something like "Assigned to an object other than a station", so I checked VDN, and Hunt groups, and even did a "list usage extension 3213" and it says "No information in system to list"

So I have a phantom extension screwing with my switchboard...anyone know what I should be looking for, or how to identify the unknown extension 3213? Thanks in advance!
 
Thanks for the tip, that'd be super helpful, but while I have shell access, I get the following when running those commands:

cust@server1> sudo logc lxsec today > ~ftp/pub/lxsec.txt

We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:

#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.

Password:
Sorry, try again.
Password:
Sorry, user cust is not allowed to execute '/opt/ecs/bin/logc lxsec today' as r.
cust@stmbt_server1>
 
ahha I should have added this needs to be done from a dadmin or superuser level with craft permissions account....you can do it with root if you have that as well....sry for the confusion I always forget that many customer level logins are restricted by permissions. If you have a business partner they should be able to run this command...otherwise you may need to get avaya or a BP involved.

Matt--Technical Support, Network Operations Center

ACA-Voice Management
ACE-IP Telephony
Converged+ Certified
Linux+ Certified
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top