Page 1 of 3 123 LastLast
Results 1 to 10 of 22

Thread: HELP: hacker attempts despite firewall set to high

  1. #1

    Angry HELP: hacker attempts despite firewall set to high

    Situation:
    ip lines and sip accounts do not register
    web interface extremely slow

    When I check the even log, I see many attempts from ip address 222.173.187.7:5118 to register on the Epygi. The IP address is from China.

    The firewall is set to high and this IP address is not set as an exception (obviously). The only IP addresses that are specified as allowed are local ip addresses and the SIP provider adresses.

    How is it possible that this ip address is getting in and tries to register?

    I even blocked this ip address on the router, but still there is traffic. Here are the SIP traces:

    SIP/2.0 401 Unauthorized
    Via: SIP/2.0/UDP 61.133.xx.xx:5093;rport=5093;received=222.173.187. 7;branch=z9hG4bK-3095032986
    To: "admin" <sip:admin@82.136.xx.xxx>
    From: "admin" <sip:admin@82.136.xx.xxx>
    CSeq: 1 REGISTER
    Call-ID: 4078xxxx0
    Server: Epygi Quadro SIP User Agent/v5.1.19 (QUADRO-2X)
    WWW-Authenticate: Digest realm="quadro.epygi-config.loc",nonce="af6b94b70ea553fea49ec3fd339126f 0",opaque="1365080835"
    Content-Length: 0

    ***************************** SIP message buffer end ******************************

    15:07:49 Receive SIP message # (04/04/2013 13:07:49:468 GMT) # UDP # 341 bytes # buff size 998 # from: 222.173.187.7:5093 # to: 192.168.1.160:5060

    What is going on?

    How did this hacker get in?

    Does he/she already have an account set up which makes the blocking attempts from my side useless?


    UPDATED INFO:
    when I take the Epygi off the internet, then all local phones register immediately. The Web Interface is fast.
    As soon as I put the internet back on, the same problems occur.

    I see the following problem under SIP user agent:
    16:27:26 TLayer # Local queue for NetAgent is full

    It is caused by the same Chinese IP address as above that I am not able to block. The SIP registration tab shows that this IP address is trying to register several times per second, making the device unusable:

    For clarity sake, here is the IP address lookup info:

    61.133.41.48 - IP in China
    222.173.187.7 - IP address in china
    82.136.xx.xxx - my IP address
    192.168.1.160 - IP address of Epygi in local network

    ***************************** SIP message buffer end ******************************

    16:32:29 UACore::TLReqMsgProc # Got REGISTER SIP request
    16:32:29 Registrar # GetAORByName #user: admin, host 222.173.187.7 user count 1
    16:32:29 Receive SIP message # (04/04/2013 14:32:29:352 GMT) # UDP # 343 bytes # buff size 1000 # from: 222.173.187.7:5093 # to: 192.168.1.160:5060

    ***************************** SIP message buffer start *****************************
    REGISTER sip:82.136.xx.xxx SIP/2.0
    Via: SIP/2.0/UDP 61.133.41.48:5093;branch=z9hG4bK-3951372225;rport
    Content-Length: 0
    From: "admin" <sip:admin@82.136.xx.xxx>
    Accept: application/sdp
    User-Agent: friendly-scanner
    To: "admin" <sip:admin@82.136.xx.xxx>
    Contact: sip:123@1.1.1.1
    CSeq: 1 REGISTER
    Call-ID: 1300430102
    Max-Forwards: 70

    ***************************** SIP message buffer end ******************************

    16:32:29 TLayer::MsgToTU # Msg type: 52 # TID: 34496 # DID: 0
    16:32:29 UACore::TLReqMsgProc # Got REGISTER SIP request
    16:32:29 Registrar # GetAORByName #user: admin, host 222.173.187.7 user count 1
    16:32:29 Try to send SIP message # (04/04/2013 14:32:29:359 GMT) # UDP # 438 bytes # buff size 999 # from: 192.168.1.160:5060 # to: 222.173.187.7:5093

    ***************************** SIP message buffer start *****************************
    SIP/2.0 401 Unauthorized
    Via: SIP/2.0/UDP 61.133.41.48:5093;rport=5093;received=222.173.187. 7;branch=z9hG4bK-1771135566
    To: "admin" <sip:admin@82.136.xx.xxx>
    From: "admin" <sip:admin@82.136.xx.xxx>
    CSeq: 1 REGISTER
    Call-ID: 3523115486
    Server: Epygi Quadro SIP User Agent/v5.1.19 (QUADRO-2X)
    WWW-Authenticate: Digest realm="quadro.epygi-config.loc",nonce="3a4999a35ac0e9345e0e9993002af5f 9",opaque="1365085948"
    Content-Length: 0

    ***************************** SIP message buffer end ******************************

    16:32:29 Receive SIP message # (04/04/2013 14:32:29:388 GMT) # UDP # 342 bytes # buff size 999 # from: 222.173.187.7:5093 # to: 192.168.1.160:5060
    Last edited by keeskoets; 04-04-2013 at 09:39 AM. Reason: Updated information

  2. #2

    Default

    I found a TEMPORARY fix. I blocked both IP addresses specifically in the filtering rules of the firewall on the Epygi. This worked immediately. All is working again.

    However, as soon as the hackers use a different IP address the whole thing will start again.

    I set both "SIP access" and "Allowed IP List" on the Epygi Firewall settings to a specific "allowed IP Pool" group, so why does the Epygi let any other IP address go through??

  3. #3

    Default

    Hello,

    I guess, when you changed the Firewall settings to allow traffic only with IPs within the particular "IP Pool Group", the hackers had been already attacking the Quadro and thus active UDP connections with the hackers' IP remained open. Quadro doesn't close active UDP/TCP connections on the fly when the Firewall config is changed in order to save established calls from disconnecting. Your case is specific and if you want to apply the changes immediately you will need to reboot the Quadro.

    Thanks,
    Aram.

  4. #4

    Default

    Hi Aram,

    thank you very much for your reply.

    The firewall config was set to high in 2011 and I never changed it. The unit was rebooted several times since then. Even after the hacker attempts the epygi was rebooted because of the DoS attacks. It made the unit unusable.

    I noticed today that IP addresses from Germany, France and the US are trying to register an IP line. They are not overflowing the system, but slowly trying to find a valid IP phone user name. For example in the event list the following is listed:

    IP phone user 6000 [85.25.137.31:5538]: registration failed. Reason: No Such Line Configured.

    A few weeks ago I set up an external extension. I put the ip address of this external user in the IP pool list.

    Could it be that the epygi allows attempts to register an external extension from ANY IP address, even if it is not in the IP pool list and the firewall is set to high?

    This would be a major flaw in the software.

  5. #5

    Default

    You know by default the "SIP Access" is open for all destinations in order to communicate with other sip devices. Please double check if your IP Pool Group is configured with correct IPs which you want to allow communication. Then check if under "SIP Access" that Pool group is applied and the rule is enabled at all. If it's done correctly all incoming/outgoing traffic rather then to/from the "IP Pool Group" will be blocked(If the Firewall is set "High"). You shouldn't have any problem there. If you still experience the problem please download the system logs of the Quadro and attach to the topic.

    Thanks,
    Aram.

  6. #6

    Default

    All that you mentioned is in place:
    The SIP access is restricted to the IP Pool Group and this service is enabled. This IP pool includes the IP addresses fo all VOIP service providers. The SIP accounts are properly registered at the server.
    The firewall is set to high.

    Regarding the system log:
    I am worried about posting the system log as it contains private information everywhere. And there are lots of files. I am afraid I will overlook something when blanking it out.
    Just the user name of my extensions will help the hackers a great deal. They are trying to crack the system as we speak. And I need to stay online or the business will not function.

    Could you tell me which part of the system log you would like to look at?

    I can post that.

  7. #7

    Default

    You could send them by private message.
    1. "proc" folder.
    2. "current\firewall" folder.
    3. "logs\sip_reg.log" file where attacks persist.
    Thanks,
    Aram.

  8. #8

    Default

    I deactivated the (only) external extension on the epygi 5 hours ago (the employee is on Easter break!), to see if this would stop the epygi from accepting registration attempts from outside the local network.

    Since then I do not see any hacking attemps. This can be a coincidence, but I suspect that the fact that I created an external extension, opened the epygi up despite the firewall being at high.

    So now the sip log does not show any attacks as it only goes back a few minutes. Just regular traffic - phone calls, local extensions registering etc.

    Yesterday's attacks and the SIP log file are posted in the first message of this thread.

    I will send the required files by PM

  9. #9

    Default

    Unfortunately, I was wrong. Deactivating the external extension did not stop the attacks.

    Here are the SIP traces of a new attack 1 minute ago:

    16:06:12 TLayer::ErrToTU # Error: Timeout occured # TID: 29903 # DID: 29902
    16:06:12 SipRegDlg::TLErrProc # Got error from TL: Timeout occured # OID: 29902
    16:06:12 Registering error (Timeout occurred), move to terminate state # OID: 29902
    16:06:12 SipRegDlg::SetRegNextTimer # Next registration will be in 96 seconds # OID: 29902
    16:06:44 Registrar # GetAORByName #user: admin, host 50.57.234.31 user count 1
    16:06:45 Registrar # GetAORByName #user: admin, host 50.57.234.31 user count 1
    16:06:45 Registrar # GetAORByName #user: admin, host user count 1
    16:06:45 Registrar # GetAORByName #user: admin, host 50.57.234.31 user count 1
    16:06:45 TLayer::MsgToNet # Sent message to the Network num 29200 r 82871 s 58134
    16:06:46 Registrar # GetAORByName #user: admin, host 50.57.234.31 user count 1
    16:06:46 Registrar # GetAORByName #user: admin, host 50.57.234.31 user count 1
    16:06:46 Registrar # GetAORByName #user: admin, host user count 1
    16:06:46 Registrar # GetAORByName #user: admin, host 50.57.234.31 user count 1
    16:06:47 Registrar # GetAORByName #user: admin, host 50.57.234.31 user count 1
    16:06:48 Registrar # GetAORByName #user: admin, host 50.57.234.31 user count 1
    16:06:48 Registrar # GetAORByName #user: admin, host user count 1
    16:06:48 Registrar # GetAORByName #user: admin, host 50.57.234.31 user count 1
    16:06:48 Registrar # GetAORByName #user: admin, host 50.57.234.31 user count 1
    16:06:48 Registrar # GetAORByName #user: admin, host user count 1
    16:06:48 Registrar # GetAORByName #user: admin, host 50.57.234.31 user count 1
    16:06:49 Registrar # GetAORByName #user: admin, host 50.57.234.31 user count 1
    16:06:49 Registrar # GetAORByName #user: admin, host 50.57.234.31 user count 1
    16:06:49 Registrar # GetAORByName #user: admin, host user count 1
    16:06:49 Registrar # GetAORByName #user: admin, host 50.57.234.31 user count 1
    16:06:51 Registrar # GetAORByName #user: admin, host 50.57.234.31 user count 1
    16:06:51 Registrar # GetAORByName #user: admin, host 50.57.234.31 user count 1
    16:06:51 Registrar # GetAORByName #user: admin, host user count 1
    16:06:51 Registrar # GetAORByName #user: admin, host 50.57.234.31 user count 1
    ------------------------------------------------------------------------------------

    The IP address 50.57.234.31 (USA) is not in the IP Pool List. Why does the epygi not black this IP address???

  10. #10

    Default

    Hacking attacks continue, I will need to take my epygi off line:

    New Fri Apr 5 20:43:34 2013 3 SIP ip phone registration rejected IP phone user 87654321 [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:33 2013 3 SIP ip phone registration rejected IP phone user 987654321 [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:33 2013 3 SIP ip phone registration rejected IP phone user 0987654321 [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:33 2013 3 SIP ip phone registration rejected IP phone user 1234567890 [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:33 2013 3 SIP ip phone registration rejected IP phone user 123456789 [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:32 2013 3 SIP ip phone registration rejected IP phone user 12345678 [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:32 2013 3 SIP ip phone registration rejected IP phone user 1234567 [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:32 2013 3 SIP ip phone registration rejected IP phone user 123456 [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:31 2013 3 SIP ip phone registration rejected IP phone user 12345 [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:31 2013 3 SIP ip phone registration rejected IP phone user 1234 [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:31 2013 3 SIP ip phone registration rejected IP phone user 123 [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:31 2013 3 SIP ip phone registration rejected IP phone user 12 [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:30 2013 3 SIP ip phone registration rejected IP phone user voipphone [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:30 2013 3 SIP ip phone registration rejected IP phone user voipcall [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:30 2013 3 SIP ip phone registration rejected IP phone user passroot [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:30 2013 3 SIP ip phone registration rejected IP phone user rootpass [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:29 2013 3 SIP ip phone registration rejected IP phone user root12 [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:29 2013 3 SIP ip phone registration rejected IP phone user root1 [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:29 2013 3 SIP ip phone registration rejected IP phone user root [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:28 2013 3 SIP ip phone registration rejected IP phone user nopass [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:28 2013 3 SIP ip phone registration rejected IP phone user info1234 [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:28 2013 3 SIP ip phone registration rejected IP phone user info123 [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:28 2013 3 SIP ip phone registration rejected IP phone user info12 [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:27 2013 3 SIP ip phone registration rejected IP phone user info1 [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:27 2013 3 SIP ip phone registration rejected IP phone user passedc [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:27 2013 3 SIP ip phone registration rejected IP phone user passwsx [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:26 2013 3 SIP ip phone registration rejected IP phone user passqaz [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:26 2013 3 SIP ip phone registration rejected IP phone user passzxc [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:26 2013 3 SIP ip phone registration rejected IP phone user passasd [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:26 2013 3 SIP ip phone registration rejected IP phone user passqwe [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:25 2013 3 SIP ip phone registration rejected IP phone user pass12345 [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:25 2013 3 SIP ip phone registration rejected IP phone user pass1234 [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:25 2013 3 SIP ip phone registration rejected IP phone user pass123 [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:24 2013 3 SIP ip phone registration rejected IP phone user pass12 [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:24 2013 3 SIP ip phone registration rejected IP phone user pass1 [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:24 2013 3 SIP ip phone registration rejected IP phone user pass [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:24 2013 3 SIP ip phone registration rejected IP phone user password [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:23 2013 3 SIP ip phone registration rejected IP phone user testtest [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:23 2013 3 SIP ip phone registration rejected IP phone user test123 [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:23 2013 3 SIP ip phone registration rejected IP phone user test12 [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:23 2013 3 SIP ip phone registration rejected IP phone user test1 [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:22 2013 3 SIP ip phone registration rejected IP phone user sippis [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:22 2013 3 SIP ip phone registration rejected IP phone user sipopen [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:22 2013 3 SIP ip phone registration rejected IP phone user sipsip [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:21 2013 3 SIP ip phone registration rejected IP phone user sipcall [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:21 2013 3 SIP ip phone registration rejected IP phone user sip123456 [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:21 2013 3 SIP ip phone registration rejected IP phone user sip12345 [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:21 2013 3 SIP ip phone registration rejected IP phone user sip1234 [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:20 2013 3 SIP ip phone registration rejected IP phone user sip12 [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:20 2013 3 SIP ip phone registration rejected IP phone user sip1 [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:20 2013 3 SIP ip phone registration rejected IP phone user sip [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:19 2013 3 SIP ip phone registration rejected IP phone user temp12345 [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:19 2013 3 SIP ip phone registration rejected IP phone user temp123 [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:18 2013 3 SIP ip phone registration rejected IP phone user temp12 [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:18 2013 3 SIP ip phone registration rejected IP phone user temp1 [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:18 2013 3 SIP ip phone registration rejected IP phone user temp [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:17 2013 3 SIP ip phone registration rejected IP phone user guest1234 [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:17 2013 3 SIP ip phone registration rejected IP phone user guest123 [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:16 2013 3 SIP ip phone registration rejected IP phone user guest12 [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:16 2013 3 SIP ip phone registration rejected IP phone user guest1 [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:15 2013 3 SIP ip phone registration rejected IP phone user guest [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:14 2013 3 SIP ip phone registration rejected IP phone user office1234 [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:14 2013 3 SIP ip phone registration rejected IP phone user office12 [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:13 2013 3 SIP ip phone registration rejected IP phone user office1 [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:13 2013 3 SIP ip phone registration rejected IP phone user office [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:12 2013 3 SIP ip phone registration rejected IP phone user admin1234 [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:12 2013 3 SIP ip phone registration rejected IP phone user admin12 [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:11 2013 3 SIP ip phone registration rejected IP phone user admin1 [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:11 2013 3 SIP ip phone registration rejected IP phone user administrator [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:10 2013 3 SIP ip phone registration rejected IP phone user Administrator [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 20:43:09 2013 3 SIP ip phone registration rejected IP phone user 488793341 [62.75.202.57:5421]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 19:17:38 2013 3 SIP ip phone registration rejected IP phone user 403 [85.25.117.187:5181]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 19:17:38 2013 3 SIP ip phone registration rejected IP phone user 402 [85.25.117.187:5181]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 19:17:38 2013 3 SIP ip phone registration rejected IP phone user 401 [85.25.117.187:5181]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 19:17:37 2013 3 SIP ip phone registration rejected IP phone user 400 [85.25.117.187:5181]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 19:17:37 2013 3 SIP ip phone registration rejected IP phone user 303 [85.25.117.187:5181]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 19:17:37 2013 3 SIP ip phone registration rejected IP phone user 302 [85.25.117.187:5181]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 19:17:37 2013 3 SIP ip phone registration rejected IP phone user 301 [85.25.117.187:5181]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 19:17:36 2013 3 SIP ip phone registration rejected IP phone user 300 [85.25.117.187:5181]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 19:17:36 2013 3 SIP ip phone registration rejected IP phone user 203 [85.25.117.187:5181]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 19:17:36 2013 3 SIP ip phone registration rejected IP phone user 202 [85.25.117.187:5181]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 19:17:36 2013 3 SIP ip phone registration rejected IP phone user 201 [85.25.117.187:5181]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 19:17:35 2013 3 SIP ip phone registration rejected IP phone user 200 [85.25.117.187:5181]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 19:17:35 2013 3 SIP ip phone registration rejected IP phone user 106 [85.25.117.187:5181]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 19:17:35 2013 3 SIP ip phone registration rejected IP phone user 105 [85.25.117.187:5181]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 19:17:34 2013 3 SIP ip phone registration rejected IP phone user 104 [85.25.117.187:5181]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 19:17:34 2013 3 SIP ip phone registration rejected IP phone user 103 [85.25.117.187:5181]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 19:17:33 2013 3 SIP ip phone registration rejected IP phone user 102 [85.25.117.187:5181]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 19:17:33 2013 3 SIP ip phone registration rejected IP phone user 101 [85.25.117.187:5181]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 19:17:33 2013 3 SIP ip phone registration rejected IP phone user 100 [85.25.117.187:5181]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 19:17:33 2013 3 SIP ip phone registration rejected IP phone user 91 [85.25.117.187:5181]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 19:17:32 2013 3 SIP ip phone registration rejected IP phone user 90 [85.25.117.187:5181]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 19:17:32 2013 3 SIP ip phone registration rejected IP phone user 81 [85.25.117.187:5181]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 19:17:32 2013 3 SIP ip phone registration rejected IP phone user 80 [85.25.117.187:5181]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 19:17:31 2013 3 SIP ip phone registration rejected IP phone user 71 [85.25.117.187:5181]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 19:17:30 2013 3 SIP ip phone registration rejected IP phone user 70 [85.25.117.187:5181]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 19:17:30 2013 3 SIP ip phone registration rejected IP phone user 61 [85.25.117.187:5181]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 19:17:29 2013 3 SIP ip phone registration rejected IP phone user 60 [85.25.117.187:5181]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 19:17:28 2013 3 SIP ip phone registration rejected IP phone user 51 [85.25.117.187:5181]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 19:17:28 2013 3 SIP ip phone registration rejected IP phone user 50 [85.25.117.187:5181]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 19:17:27 2013 3 SIP ip phone registration rejected IP phone user 41 [85.25.117.187:5181]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 19:17:26 2013 3 SIP ip phone registration rejected IP phone user 40 [85.25.117.187:5181]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 19:17:26 2013 3 SIP ip phone registration rejected IP phone user 31 [85.25.117.187:5181]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 19:17:25 2013 3 SIP ip phone registration rejected IP phone user 30 [85.25.117.187:5181]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 19:17:25 2013 3 SIP ip phone registration rejected IP phone user 22 [85.25.117.187:5181]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 19:17:25 2013 3 SIP ip phone registration rejected IP phone user 21 [85.25.117.187:5181]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 19:17:24 2013 3 SIP ip phone registration rejected IP phone user 20 [85.25.117.187:5181]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 19:17:24 2013 3 SIP ip phone registration rejected IP phone user 13 [85.25.117.187:5181]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 19:17:23 2013 3 SIP ip phone registration rejected IP phone user 12 [85.25.117.187:5181]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 19:17:22 2013 3 SIP ip phone registration rejected IP phone user 11 [85.25.117.187:5181]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 19:17:22 2013 3 SIP ip phone registration rejected IP phone user 10 [85.25.117.187:5181]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 19:17:21 2013 3 SIP ip phone registration rejected IP phone user 3 [85.25.117.187:5181]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 19:17:21 2013 3 SIP ip phone registration rejected IP phone user 2 [85.25.117.187:5181]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status
    New Fri Apr 5 19:17:20 2013 3 SIP ip phone registration rejected IP phone user 1 [85.25.117.187:5181]: registration failed. Reason: No Such Line Configured. IP Lines Registration Status

    Firewall set to high. I am attaching screen shots of the settings.

    Will it help if I upgrade the firmware? I am running 5.1.19.
    Attached Images Attached Images

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Hacker attempts
    By KSComs in forum General Discussions
    Replies: 51
    Last Post: 01-21-2011, 01:12 PM
  2. Symmetric Firewall issue
    By ozbeanz in forum Troubleshooting and Problems
    Replies: 1
    Last Post: 10-25-2010, 04:49 AM
  3. Firewall - Policy High
    By cit in forum Troubleshooting and Problems
    Replies: 2
    Last Post: 06-25-2010, 03:56 AM
  4. Jitter using Cisco 5505 Firewall
    By andy@telecomhelp.co.uk in forum Installation
    Replies: 2
    Last Post: 04-29-2010, 05:00 AM
  5. Firewall and X-lite/QCM
    By AsIntented in forum Troubleshooting and Problems
    Replies: 5
    Last Post: 05-15-2009, 03:30 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •