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

    FreePBX outbound call routing

    IT Discussion
    4
    64
    5.2k
    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.
    • brandon220B
      brandon220
      last edited by

      2_1522936706969_Capture3.PNG 1_1522936706969_Capture2.PNG 0_1522936706969_Capture1.PNG

      JaredBuschJ 1 Reply Last reply Reply Quote 0
      • brandon220B
        brandon220
        last edited by

        0_1522936896325_Capture4.PNG

        1 Reply Last reply Reply Quote 0
        • brandon220B
          brandon220
          last edited by

          2_1522937122919_Capture7.PNG 1_1522937122918_Capture6.PNG 0_1522937122918_Capture5.PNG

          1 Reply Last reply Reply Quote 0
          • brandon220B
            brandon220
            last edited by

            Both trunks are registered in VOIP.MS and show online in the FreePBX dashboard. Inbound calls are working with no issues.

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

              I only see one trunk's SIP server settings.

              Are both trunks on houston.voip.ms? That will not work, I can get technical about it, but just trust me. Put one on houston2.voip.ms

              You will have to change the DID inside voip.ms also.

              This is one reason why I started out at the beginning of this thread questioning why you have multiple trunks. I have had to deal with this also because of desired separated billing.

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

                @brandon220 said in FreePBX outbound call routing:

                2_1522936706969_Capture3.PNG

                Is this on the trunk or the outbound route?

                If trere is any dialed number manipulation on the trunk, delete all of it.

                brandon220B 1 Reply Last reply Reply Quote 0
                • brandon220B
                  brandon220
                  last edited by

                  Ok... I will do that now. I will report back.

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

                    @jaredbusch There is no manipulation on the trunk.

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

                      @brandon220 said in FreePBX outbound call routing:

                      @jaredbusch There is no manipulation on the trunk.

                      Ok, so next step. Let's get rid of all that shit. I hate the dial pattern wizard. People have no idea what any of it means and it just makes things confusing.

                      Tell me how are your users supposed to be dialing the phone?

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

                        @jaredbusch They just pick up the phone and dial a 10-digit number. No prefix. No special anything.

                        JaredBuschJ 1 Reply Last reply Reply Quote 0
                        • brandon220B
                          brandon220
                          last edited by brandon220

                          I changed the trunk to houston2 and now outbound calls are flowing..... I wish I would have known that would cause an issue. I'm learning though and that is what matters. Edit: I did change it inside voip.ms before I changed it in FreePBX. That trunk was NOT registered. It was yesterday.

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

                            @brandon220 said in FreePBX outbound call routing:

                            @jaredbusch They just pick up the phone and dial a 10-digit number. No prefix. No special anything.

                            This means the only dial pattern you want is NXXNXXXXXX for normal US calling. and 011. for international calling.

                            How is your dialing mode setup on VoIP.ms?
                            0_1522939488920_36ab8988-029d-4916-8fa4-55ee331e1e8b-image.png

                            As you can see if you are set to NANPA, then you do not need to prepend a 1, but it will work if you do.
                            If you are set to E164, then you are required to send the 1.

                            Because of this, I simply always send the 1 on the NXXNXXXXXX line.
                            0_1522939655336_3645f65a-dfbb-4dfb-90fa-09b8fe1f7325-image.png

                            1 Reply Last reply Reply Quote 0
                            • brandon220B
                              brandon220
                              last edited by

                              Voip.ms is set like your example on NANPA for both trunks.

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

                                @brandon220 said in FreePBX outbound call routing:

                                Voip.ms is set like your example on NANPA for both trunks.

                                Then, all you want are those two lines as I have above.

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

                                  @jaredbusch Ok. Making those changes now.

                                  1 Reply Last reply Reply Quote 0
                                  • brandon220B
                                    brandon220
                                    last edited by

                                    All is good now. I REALLY APPRECIATE the assistance. I wish I would have used separate trunks paths from the beginning and avoided the mess. It was a learning experience for sure. I will monitor it and see if anything changes. Again, thank you.

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

                                      @brandon220 said in FreePBX outbound call routing:

                                      All is good now.

                                      Not quite. You cannot dial 911 yet.

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

                                        Make a new outbound route.

                                        Name it SAS_e911 or Parish_e911 appropriately.
                                        Mark it as an emergency route, and specify the caller ID that is tied to your address in VoIP.ms's system. Also check the override extension option.

                                        0_1522941959240_3a4f1ffe-f1b3-4e1d-9dff-36a69e489893-image.png

                                        Setup the following two dial patterns. The first is a test to the voip.ms system. the second is the real one.
                                        0_1522942100666_3ee2c402-0613-44f7-aae6-3ad818aa97eb-image.png

                                        Finally, make sure the outbound routes for e911 are ordered above all other outbound routes. This way you know that they were processed first.
                                        0_1522941858588_3c297f25-0976-4206-b729-6f16c3a1a940-image.png

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

                                          And make sure you have no caller ID specified in your trunk. I cannot ever say that enough.

                                          Yes it will bitch about it. Ignore it.

                                          1 Reply Last reply Reply Quote 0
                                          • brandon220B
                                            brandon220
                                            last edited by

                                            I do have caller ID specified in the trunk as it shows in my attached image above. I has not given any error messages or anything. Seems to be working correctly. What is the recommended way to handle outbound CID?

                                            JaredBuschJ 1 Reply Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 3
                                            • 4
                                            • 3 / 4
                                            • First post
                                              Last post