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

    VOIP.ms more secure

    IT Discussion
    4
    5
    173
    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.
    • Dashrender
      Dashrender last edited by

      Just received this notice.
      c5ea9876-3df0-47f8-9785-781fa4fac050-image.png

      I'm not sure how this is more secure? I would assume you would have to know the password or be on forwarding through the listed registration IP to be able to use the sip trunk. How does limiting this to this specific IP or POP help? if you have the password, can't you just log in and change it to whatever you want?

      JaredBusch 1 Reply Last reply Reply Quote 1
      • JaredBusch
        JaredBusch @Dashrender last edited by

        @Dashrender said in VOIP.ms more secure:

        Just received this notice.
        c5ea9876-3df0-47f8-9785-781fa4fac050-image.png

        I'm not sure how this is more secure? I would assume you would have to know the password or be on forwarding through the listed registration IP to be able to use the sip trunk. How does limiting this to this specific IP or POP help? if you have the password, can't you just log in and change it to whatever you want?

        Registered SIP trunking is not the recommended method by a lot of systems. Yeah, it makes magic with NAT most of the time, but still.

        So by adding this, you can now securely use IP based trunking on VoIP.ms.

        1 Reply Last reply Reply Quote 1
        • Skyetel
          Skyetel last edited by

          SIP Trunking by IP is so much better than registration, we don't even allow you to register.

          About a year ago, a customer came to us from one of our competitors that used SIP Registration. A hacker broke into his PBX, and instead of relaying all the calls through his PBX like they normally do, they got his SIP Trunking username & password for his carrier. They then proceeded to register half a dozen systems and burned through tens of thousands of dollars before the carrier realized something was wrong. They then forced him to pay the bill (which is why he quickly looked to move away to us).

          I can rant all day about the pitfalls of SIP Registration, but I shall refrain 😛

          scottalanmiller JaredBusch 2 Replies Last reply Reply Quote 1
          • scottalanmiller
            scottalanmiller @Skyetel last edited by

            @Skyetel said in VOIP.ms more secure:

            SIP Trunking by IP is so much better than registration, we don't even allow you to register.

            About a year ago, a customer came to us from one of our competitors that used SIP Registration. A hacker broke into his PBX, and instead of relaying all the calls through his PBX like they normally do, they got his SIP Trunking username & password for his carrier. They then proceeded to register half a dozen systems and burned through tens of thousands of dollars before the carrier realized something was wrong. They then forced him to pay the bill (which is why he quickly looked to move away to us).

            I can rant all day about the pitfalls of SIP Registration, but I shall refrain 😛

            It would be fine if you use IP locking and registration. But registration alone, I agree.

            1 Reply Last reply Reply Quote 0
            • JaredBusch
              JaredBusch @Skyetel last edited by

              @Skyetel said in VOIP.ms more secure:

              SIP Trunking by IP is so much better than registration, we don't even allow you to register.

              About a year ago, a customer came to us from one of our competitors that used SIP Registration. A hacker broke into his PBX, and instead of relaying all the calls through his PBX like they normally do, they got his SIP Trunking username & password for his carrier. They then proceeded to register half a dozen systems and burned through tens of thousands of dollars before the carrier realized something was wrong. They then forced him to pay the bill (which is why he quickly looked to move away to us).

              I can rant all day about the pitfalls of SIP Registration, but I shall refrain 😛

              Multiple failures in the scenario you listed. Anyone of those failures being not there would’ve made the entire thing not a problem.

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