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

    Setting up a Skyetel SIP trunk in FreePBX

    IT Discussion
    skyetel freepbx freepbx 14 pjsip
    4
    22
    3.5k
    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.
    • S
      Skyetel @DustinB3403
      last edited by

      @DustinB3403 said in Setting up a Skyetel SIP trunk in FreePBX:

      @Skyetel said in Setting up a Skyetel SIP trunk in FreePBX:

      Super helpful - thanks @JaredBusch

      We typically recommend creating multiple trunks with our IPs so that you don't rely on DNS. In older versions of Asterisk (we still have users who use 1.4!), DNS would cause Asterisk to crash. Additionally, some people use less-than-awesome DNS solutions that either take a long time to propagate or are just providing inaccurate results.

      That being said, if you are feeling ambitious and want to try an unpublished (but supported) technique, you can use srv.skyetel.com instead of term.skyetel.com. It uses SRV records instead of A records. We keep this unpublished to encourage people to use our IPs - SRV causes a lot of problems for inexperienced administrators, but some PBXs require it when using multiple IPs like we do.

      It's not unpublished now. . .

      shhhh... don't tell anyone 🙂

      It's not a state secret, it's just not encouraged. We don't publish it in our docs, but it is supported. ML is mostly experts who understand the downsides of DNS & SRV + they don't use TrixBox

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

        @Skyetel said in Setting up a Skyetel SIP trunk in FreePBX:

        so that you don't rely on DNS. In older versions of Asterisk (we still have users who use 1.4!), DNS would cause Asterisk to crash.

        This is specifically a PJSIP trunk. It cannot exist prior to Asterisk 12, and wasn't normal until Asterisk 13.

        @Skyetel said in Setting up a Skyetel SIP trunk in FreePBX:

        Additionally, some people use less-than-awesome DNS solutions that either take a long time to propagate or are just providing inaccurate results.

        If they are that bad, they will have other support issues anyway. You cannot fix stupid.

        @Skyetel said in Setting up a Skyetel SIP trunk in FreePBX:

        We typically recommend creating multiple trunks with our IPs

        That creates its own disaster of teaching people how to route outbound calls.

        S 1 Reply Last reply Reply Quote 1
        • J
          JaredBusch @DustinB3403
          last edited by

          @DustinB3403 said in Setting up a Skyetel SIP trunk in FreePBX:

          It uses SRV records instead of A records.

          One would assume that any modern OS can handle that.

          S D 2 Replies Last reply Reply Quote 0
          • S
            Skyetel @JaredBusch
            last edited by

            @JaredBusch said in Setting up a Skyetel SIP trunk in FreePBX:

            @DustinB3403 said in Setting up a Skyetel SIP trunk in FreePBX:

            It uses SRV records instead of A records.

            One would assume that any modern OS can handle that.

            We seriously do have users who still use TrixBox.

            D J 2 Replies Last reply Reply Quote 0
            • D
              DustinB3403 @JaredBusch
              last edited by

              @JaredBusch yeah I was only quoting @Skyetel.

              But thanks for the props?

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

                @Skyetel said in Setting up a Skyetel SIP trunk in FreePBX:

                @JaredBusch said in Setting up a Skyetel SIP trunk in FreePBX:

                @DustinB3403 said in Setting up a Skyetel SIP trunk in FreePBX:

                It uses SRV records instead of A records.

                One would assume that any modern OS can handle that.

                We seriously do have users who still use TrixBox.

                And what is wrong with that? It's only 7 years out of date. . . 🙂

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

                  @JaredBusch said in Setting up a Skyetel SIP trunk in FreePBX:

                  @Skyetel said in Setting up a Skyetel SIP trunk in FreePBX:

                  so that you don't rely on DNS. In older versions of Asterisk (we still have users who use 1.4!), DNS would cause Asterisk to crash.

                  This is specifically a PJSIP trunk. It cannot exist prior to Asterisk 12, and wasn't normal until Asterisk 13.

                  @Skyetel said in Setting up a Skyetel SIP trunk in FreePBX:

                  Additionally, some people use less-than-awesome DNS solutions that either take a long time to propagate or are just providing inaccurate results.

                  If they are that bad, they will have other support issues anyway. You cannot fix stupid.

                  @Skyetel said in Setting up a Skyetel SIP trunk in FreePBX:

                  We typically recommend creating multiple trunks with our IPs

                  That creates its own disaster of teaching people how to route outbound calls.

                  We prefer "inexperienced" to "stupid" 😛

                  We also do have the guide for outbound routing:
                  https://skyetel.atlassian.net/wiki/spaces/SUG/pages/16613436/FreePBX+Outbound+Routes

                  But I do agree - this is a more elegant implementation than what we document. Thanks for writing it 🙂

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

                    @Skyetel said in Setting up a Skyetel SIP trunk in FreePBX:

                    @JaredBusch said in Setting up a Skyetel SIP trunk in FreePBX:

                    @DustinB3403 said in Setting up a Skyetel SIP trunk in FreePBX:

                    It uses SRV records instead of A records.

                    One would assume that any modern OS can handle that.

                    We seriously do have users who still use TrixBox.

                    Still use is one thing. Phone systems are still very legacy mindset about lasting forever with no maintenance.

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

                      @JaredBusch said in Setting up a Skyetel SIP trunk in FreePBX:

                      @Skyetel said in Setting up a Skyetel SIP trunk in FreePBX:

                      @JaredBusch said in Setting up a Skyetel SIP trunk in FreePBX:

                      @DustinB3403 said in Setting up a Skyetel SIP trunk in FreePBX:

                      It uses SRV records instead of A records.

                      One would assume that any modern OS can handle that.

                      We seriously do have users who still use TrixBox.

                      Still use is one thing. Phone systems are still very legacy mindset about lasting forever with no maintenance.

                      Still use = actively deploy. We obviously discourage this lol

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

                        @Skyetel said in Setting up a Skyetel SIP trunk in FreePBX:

                        @JaredBusch said in Setting up a Skyetel SIP trunk in FreePBX:

                        @Skyetel said in Setting up a Skyetel SIP trunk in FreePBX:

                        @JaredBusch said in Setting up a Skyetel SIP trunk in FreePBX:

                        @DustinB3403 said in Setting up a Skyetel SIP trunk in FreePBX:

                        It uses SRV records instead of A records.

                        One would assume that any modern OS can handle that.

                        We seriously do have users who still use TrixBox.

                        Still use is one thing. Phone systems are still very legacy mindset about lasting forever with no maintenance.

                        Still use = actively deploy.

                        Yeah, ok.. i would refuse to service them. Does that even run on CentOS 5? How woudl they even find it? All fo the old domains redirect.

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

                          @JaredBusch said in Setting up a Skyetel SIP trunk in FreePBX:

                          @Skyetel said in Setting up a Skyetel SIP trunk in FreePBX:

                          @JaredBusch said in Setting up a Skyetel SIP trunk in FreePBX:

                          @Skyetel said in Setting up a Skyetel SIP trunk in FreePBX:

                          @JaredBusch said in Setting up a Skyetel SIP trunk in FreePBX:

                          @DustinB3403 said in Setting up a Skyetel SIP trunk in FreePBX:

                          It uses SRV records instead of A records.

                          One would assume that any modern OS can handle that.

                          We seriously do have users who still use TrixBox.

                          Still use is one thing. Phone systems are still very legacy mindset about lasting forever with no maintenance.

                          Still use = actively deploy.

                          Yeah, ok.. i would refuse to service them. Does that even run on CentOS 5? How woudl they even find it? All fo the old domains redirect.

                          I assume they've kept the ISO for years. TrixBox isn't the only legacy system people still deploy - we have ancient Avaya, Mitel, and even Toshiba systems on our network. People tend to stick with what they know and are afraid of updating their PBXs. We do our best to help, but when they are using systems that old, usually they already know that they are going to have a hard time before they even contact our support department.

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

                            @Skyetel said in Setting up a Skyetel SIP trunk in FreePBX:

                            @JaredBusch said in Setting up a Skyetel SIP trunk in FreePBX:

                            @Skyetel said in Setting up a Skyetel SIP trunk in FreePBX:

                            @JaredBusch said in Setting up a Skyetel SIP trunk in FreePBX:

                            @Skyetel said in Setting up a Skyetel SIP trunk in FreePBX:

                            @JaredBusch said in Setting up a Skyetel SIP trunk in FreePBX:

                            @DustinB3403 said in Setting up a Skyetel SIP trunk in FreePBX:

                            It uses SRV records instead of A records.

                            One would assume that any modern OS can handle that.

                            We seriously do have users who still use TrixBox.

                            Still use is one thing. Phone systems are still very legacy mindset about lasting forever with no maintenance.

                            Still use = actively deploy.

                            Yeah, ok.. i would refuse to service them. Does that even run on CentOS 5? How woudl they even find it? All fo the old domains redirect.

                            I assume they've kept the ISO for years. TrixBox isn't the only legacy system people still deploy - we have ancient Avaya, Mitel, and even Toshiba systems on our network. People tend to stick with what they know and are afraid of updating their PBXs. We do our best to help, but when they are using systems that old, usually they already know that they are going to have a hard time before they even contact our support department.

                            Heck, we still have an old ass inter-tel.

                            Hope to change that either this summer or next.

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

                              @Dashrender said in Setting up a Skyetel SIP trunk in FreePBX:

                              Hope to change that either this summer or next.

                              Not holding my breath

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

                                @JaredBusch said in Setting up a Skyetel SIP trunk in FreePBX:

                                @Dashrender said in Setting up a Skyetel SIP trunk in FreePBX:

                                Hope to change that either this summer or next.

                                Not holding my breath

                                yeah - sadly, neither am I - I'm guessing they might go the cheaper route and simply replace the digital brain with the modern/supported unit, and keep the rest of the infrastructure intact...

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

                                  @Skyetel said in Setting up a Skyetel SIP trunk in FreePBX:

                                  We typically recommend creating multiple trunks

                                  VitalPBX's guide also uses a single pjsip trunk in the same method I did here.

                                  They posted a guide a couple days before I did this one, apparently with the assistance of Skyetel staff.
                                  9af0986e-5e5e-44a2-a0d2-86062468bc21-image.png

                                  So you might want to rethink your "recommendation"

                                  1 Reply Last reply Reply Quote 0
                                  • J
                                    JaredBusch
                                    last edited by

                                    One thing to clarify here (I will also put this info in the first post).

                                    By default, @Skyetel does not use the e164 standard for the inbound DID format, they use an 11 digit number. There is nothing wrong with this, but it makes it more work to "standardize" the displayed number to your users. I'm a huge fan of never showing the country code. So for US numbers that means stripping the 1.

                                    FreePBX does not have anything built into their inbound dial plan code to strip a 1 fomr an 11 digit number. But they do have a process to strip the +1 from a number of any length. That is the from-pstn-e164-us context I say to use in the guide.

                                    Fortunately, @Skyetel makes it very simple to send the DID in the e164 format.

                                    Select your phone number(s) and click edit.

                                    Right on the General tab you will see SIP Format.

                                    47ca3cf1-432c-48f3-9ada-e155ea15453a-image.png

                                    Click on the drop down and change it to +1NXXNXXXXXX and click save.

                                    6372dc17-9170-4a80-b56c-78fedcf67f9b-image.png

                                    1 Reply Last reply Reply Quote 1
                                    • J
                                      JaredBusch
                                      last edited by

                                      The benefit (to me) of setting this up like this means that your inbound routing is all just 10 digit numbers.
                                      80b943b7-bc27-4b89-82a3-498dec52b007-image.png

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