ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Podcast: Defending Against SIP Hackers

    Self Promotion
    sip voice telecom phone voip
    4
    4
    1.7k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • MikeSmithsBrainM
      MikeSmithsBrain
      last edited by

      alt text

      Cloud Therapy with AeroComInc.com E010: SIP Security Tips with Bill Bollinger

      VoIP pioneer and co-founder of Appia, Bill Bollinger sees thousands of hack attempts every day. In this episode, he tells Mike his tips on how your company can avoid having their SIP service hacked. He also tells a story of a company that could've done something very simple to avoid getting hacked and paying $10k in fraudulent calls.

      1 Reply Last reply Reply Quote 2
      • JaredBuschJ
        JaredBusch
        last edited by JaredBusch

        Saw this the other day when looking at the logs for a hosted Asterisk solution I have.

        [Jun 27 04:04:59] NOTICE[2773] chan_sip.c: Registration from '1010 <sip:[email protected]:5060>' failed for '81.30.158.12:5085' - Wrong password
        [Jun 27 04:05:01] NOTICE[2773] chan_sip.c: Registration from '111 <sip:[email protected]:5060>' failed for '81.30.158.12:52293' - Wrong password
        [Jun 27 04:14:59] NOTICE[2773] chan_sip.c: Registration from '1010 <sip:[email protected]:5060>' failed for '81.30.158.12:46824' - Wrong password
        [Jun 27 04:15:11] NOTICE[2773] chan_sip.c: Registration from '111 <sip:[email protected]:5060>' failed for '81.30.158.12:5064' - Wrong password
        [Jun 27 04:25:03] NOTICE[2773] chan_sip.c: Registration from '1010 <sip:[email protected]:5060>' failed for '81.30.158.12:5098' - Wrong password
        [Jun 27 04:25:27] NOTICE[2773] chan_sip.c: Registration from '111 <sip:[email protected]:5060>' failed for '81.30.158.12:34926' - Wrong password
        [Jun 27 04:35:08] NOTICE[2773] chan_sip.c: Registration from '1010 <sip:[email protected]:5060>' failed for '81.30.158.12:38950' - Wrong password
        [Jun 27 04:35:35] NOTICE[2773] chan_sip.c: Registration from '111 <sip:[email protected]:5060>' failed for '81.30.158.12:5098' - Wrong password
        [Jun 27 04:45:06] NOTICE[2773] chan_sip.c: Registration from '1010 <sip:[email protected]:5060>' failed for '81.30.158.12:5095' - Wrong password
        [Jun 27 04:45:41] NOTICE[2773] chan_sip.c: Registration from '111 <sip:[email protected]:5060>' failed for '81.30.158.12:36400' - Wrong password
        [Jun 27 04:55:00] NOTICE[2773] chan_sip.c: Registration from '1010 <sip:[email protected]:5060>' failed for '81.30.158.12:53867' - Wrong password
        [Jun 27 04:55:51] NOTICE[2773] chan_sip.c: Registration from '111 <sip:[email protected]:5060>' failed for '81.30.158.12:42956' - Wrong password
        [Jun 27 05:05:11] NOTICE[2773] chan_sip.c: Registration from '1010 <sip:[email protected]:5060>' failed for '81.30.158.12:36470' - Wrong password
        
        1 Reply Last reply Reply Quote 1
        • RamblingBipedR
          RamblingBiped
          last edited by

          Wow, this is kind of right along the lines of what I've been researching on remote extensions...

          scottalanmillerS 1 Reply Last reply Reply Quote 1
          • scottalanmillerS
            scottalanmiller @RamblingBiped
            last edited by

            @RamblingBiped said in Podcast: Defending Against SIP Hackers:

            Wow, this is kind of right along the lines of what I've been researching on remote extensions...

            One of the things that we routinely do is to block all non-free calling so even if our extension, PBX or platform were to be hacked, even if they gained access to our SIP trunk, they can't rack up long distance calls or whatever.

            1 Reply Last reply Reply Quote 1
            • 1 / 1
            • First post
              Last post