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

    FreePBX outbound call routing

    Scheduled Pinned Locked Moved IT Discussion
    64 Posts 4 Posters 5.4k Views
    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

      I could be reading into this wrong.... Do I need to prepend the dialed number with a number to force the calls out a specific trunk?

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

        @brandon220 said in FreePBX outbound call routing:

        I could be reading into this wrong.... Do I need to prepend the dialed number with a number to force the calls out a specific trunk?

        No. look at the screenshot again..

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

          The extensions are not in a group.

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

            @brandon220 said in FreePBX outbound call routing:

            The extensions are not in a group.

            K. screenshot inc...

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

              @jaredbusch said in FreePBX outbound call routing:

              @brandon220 said in FreePBX outbound call routing:

              The extensions are not in a group.

              K. screenshot inc...

              Assuming you have to prepend a 1 (missed the last box there oops) and you make your users dial a 10 digit number always (NXXNXXXXXX) and you want extensions 59,63,42,55 to use this route.

              0_1520523341104_04fef18f-f5a4-4085-82d5-924bf67dab13-image.png

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

                @jaredbusch That makes sense now. What was confusing me was the 11xx in the first image. Your example does not include the xx. I will try this afternoon and see what happens.

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

                  @brandon220 said in FreePBX outbound call routing:

                  @jaredbusch That makes sense now. What was confusing me was the 11xx in the first image. Your example does not include the xx. I will try this afternoon and see what happens.

                  011. is for international calling.

                  It means match 011 and any number of digits afterwards.

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

                    @brandon220 said in FreePBX outbound call routing:

                    @jaredbusch That makes sense now. What was confusing me was the 11xx in the first image. Your example does not include the xx. I will try this afternoon and see what happens.

                    I speficially narrowed my example to make you understand.

                    But you will potentially need many more dial patterns.

                    For example. what I gave you above will not enable the users to dial 911.

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

                      I typically make a 911 route separate from all the rest of the routes.
                      0_1520523838936_Selection_999(742).png

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

                        Yes. It makes sense now. I was trying to make it more difficult. Your examples make it all clear. Thank you.

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

                          Here is the St Louis e911 route from the above screenshot.

                          Note that I do a pattern match on the extension of 51XX because all St Louis extensions are 5100-5199.
                          The first pattern is the VoIP.ms test number for e911. The second match is simply 911.
                          0_1520523901926_192f9c66-9830-490f-95a6-b02c18f814b7-image.png

                          The caller ID is forced and this DID in VoIP.ms portal has the physical address for the St. Louis Office.
                          0_1520524064871_be3eb44b-0d46-42e1-ad33-2b7653d744d4-image.png

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

                            I set up separate e911 addresses in the portal as well. The system covers 3 buildings on 1 city block. I know they are not set up geographically different as yours are but wanted to make sure each group goes out the appropriate trunk - hence the reason for my question. Your examples are very informative.

                            CCWTechC JaredBuschJ 2 Replies Last reply Reply Quote 0
                            • CCWTechC
                              CCWTech @brandon220
                              last edited by

                              @brandon220 said in FreePBX outbound call routing:

                              I set up separate e911 addresses in the portal as well. The system covers 3 buildings on 1 city block. I know they are not set up geographically different as yours are but wanted to make sure each group goes out the appropriate trunk - hence the reason for my question. Your examples are very informative.

                              It's also good to register your VOIP with your local PSAP. Most of them have online registration forms, you can use the same form if they have one for cellular phones.

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

                                @ccwtech Once I get everything fine-tuned I will be making test calls to the PSAP to ensure everything is correct since I just added the new trunk and DIDs last night.

                                CCWTechC 1 Reply Last reply Reply Quote 0
                                • CCWTechC
                                  CCWTech @brandon220
                                  last edited by

                                  @brandon220 said in FreePBX outbound call routing:

                                  @ccwtech Once I get everything fine-tuned I will be making test calls to the PSAP to ensure everything is correct since I just added the new trunk and DIDs last night.

                                  Before you do a test call, find out the non-emergency dispatch number and see if that is allowed and/or what the procedure is that they want you to follow. I know some PSAP's do this differently than others.

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

                                    @brandon220 said in FreePBX outbound call routing:

                                    I set up separate e911 addresses in the portal as well. The system covers 3 buildings on 1 city block. I know they are not set up geographically different as yours are but wanted to make sure each group goes out the appropriate trunk - hence the reason for my question. Your examples are very informative.

                                    You do not need a different TRUNK you only need a different DID.

                                    Edit: But yes, I forgot you are using different trunks for billing reasons..

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

                                      I am having difficulty implementing this and not sure why. I have 3 extensions that I want to use the alternate trunk. In the outbound routes, I put 6x in the caller id field as shown in the examples. The three extensions are 60, 61, and 62. When I try to make an outbound call, I get an "all circuits busy" message. Inbound calls flow to the correct ring group. What am I missing?

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

                                        @brandon220 said in FreePBX outbound call routing:

                                        I am having difficulty implementing this and not sure why. I have 3 extensions that I want to use the alternate trunk. In the outbound routes, I put 6x in the caller id field as shown in the examples. The three extensions are 60, 61, and 62. When I try to make an outbound call, I get an "all circuits busy" message. Inbound calls flow to the correct ring group. What am I missing?

                                        Use 6[012] instead of 6X just to be safe if you are specifically only wanting to use it on 60, 61, and 62.
                                        Specify the outbound CID

                                        Beyond that, it should be a 100% match for the other outbound routes. Same trunks and everything.

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

                                          Outbound CID is specified with the 10 digit number <aaabbbcccc>. I changed the numbers to 6[012] and am trying a call now....

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

                                            Still getting the error message... It makes no sense.

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