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

    Unsolved yealink dial plan syntax

    IT Discussion
    yealink voip sip telephony yealink t46g
    4
    7
    2.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.
    • M
      Mike Davis
      last edited by scottalanmiller

      I have a yealink T46G. When calls come in the come in without the 1 so it's area code + telephone number. My phone wants me to dial a 1 for every outbound call. When I would miss a call or go through my call history, I couldn't just scroll down to the number and hit send because it wouldn't dial out without the 1.

      I created a dial plan for prefix (.) replace: 1$1
      That worked for outside calls, but since our internal numbers start with 1, when I tried to dial someone internally, it would add another 1 to their extension and fail.

      As a work around for that issue, I created a dial plan that looks for my most used area code, which is 315 and the rule looks like: Prefix: 315(.) replace: 1315$1

      That works and I can call internal extensions. Of course it only works for that area code and I would have to program every area code I might want to call back in there like that.

      Is there a way to only use the replace rule on 10 digit long numbers and leave the 3 digit numbers alone? It seemed like it would be something like:
      Prefix xxxxxxxxxx replace 1xxxxxxxxxx
      but that didn't work.

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

        Do you not have a PBX handling this? The phones should never need configured away from default.

        1 Reply Last reply Reply Quote 1
        • M
          Mike Davis
          last edited by

          yes I do. @Mike-Ralston would know more about it.

          1 Reply Last reply Reply Quote 0
          • M
            Mike Ralston
            last edited by

            @Mike-Davis @JaredBusch
            What's going on here is that we have several different entities using a single phone system, and they all need their own outbound routes. This is just a temporary situation that should be resolved soon.

            S J 2 Replies Last reply Reply Quote 0
            • S
              scottalanmiller @Mike Ralston
              last edited by

              @Mike-Ralston said in yealink dial plan syntax:

              @Mike-Davis @JaredBusch
              What's going on here is that we have several different entities using a single phone system, and they all need their own outbound routes. This is just a temporary situation that should be resolved soon.

              Shouldn't that be done by determining the source of the call, rather than a number prefix?

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

                @scottalanmiller said in yealink dial plan syntax:

                @Mike-Ralston said in yealink dial plan syntax:

                @Mike-Davis @JaredBusch
                What's going on here is that we have several different entities using a single phone system, and they all need their own outbound routes. This is just a temporary situation that should be resolved soon.

                Shouldn't that be done by determining the source of the call, rather than a number prefix?

                Yes in the outbound route you specify the extensions that the calls come from to fix this

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

                  @Mike-Ralston look at the PBX I have with NTG you can see outbound route there like that

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