You can install a
log watching program that looks out for specific log
entries and can take action. Eg; writing a firewall rule
to ban the ip address of the system trying to make
unauthorised calls.
'swatch' is a good tool for this in linux systems.
Ok
look at the 3rd column... This is someone
trying to figure out how to get calls thru
your public context with various prefix
codexs... Notices how all the calls end with
972598371070 <-- that’s the intl
destination umber probably a phone in gaza
(definitely in Isreali controlled areas, but I
think I looked up this number or similar
number in the past)
To protect yourself, only allow calls to local
extentsions from the public context...
The call duration is
0 seconds so no they didn't get in. Any
accepted call attempt will generate a CDR
even if it was not answered.
They're coming in on the 'public' context
which'll mean an unauthenticated call on the
external profile. That would be the context
allowing you to receive calls from
strangers. Providing that context doesn't
allow them to dial out via providers that
charge you this isn't an issue.
-Steve
On 13 May 2013 07:17, Bala Murugan Mahendran
<b2m@a-cti.com>
wrote:
I have lot
of entries like 1000,1001,1002 and so on,
Is someone trying to get inside?
I believe they didn't in yet but how come
we have cdr log like this?