unable to dial #21# [closed]

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP

up vote
1
down vote

favorite

using FreePBX 14.0.5.2 pjsip outbound trunk, I did not find a way to dial out #21#.

Leading hash sign seems to be eaten and not make it through the trunk.

Tried multiple ways (dialing through custom feature code, etc.) and adding a custom dial plan in the trunk or outbound route (compose 21# and prepend #), etc. Nothing seems to work.

In contrast, dialing *21x.# through the trunk works well with setting up an outbound route dial plan (compose 21x.# and prepend *).

This question is addressed here, as I did not find any helpful answers in the freepbx community forum.

share|improve this question

closed as too broad by Rui F Ribeiro, G-Man, RalfFriedl, msp9011, JigglyNaga Dec 7 at 9:54

Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

    up vote
    1
    down vote

    favorite

    using FreePBX 14.0.5.2 pjsip outbound trunk, I did not find a way to dial out #21#.

    Leading hash sign seems to be eaten and not make it through the trunk.

    Tried multiple ways (dialing through custom feature code, etc.) and adding a custom dial plan in the trunk or outbound route (compose 21# and prepend #), etc. Nothing seems to work.

    In contrast, dialing *21x.# through the trunk works well with setting up an outbound route dial plan (compose 21x.# and prepend *).

    This question is addressed here, as I did not find any helpful answers in the freepbx community forum.

    share|improve this question

    closed as too broad by Rui F Ribeiro, G-Man, RalfFriedl, msp9011, JigglyNaga Dec 7 at 9:54

    Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

      up vote
      1
      down vote

      favorite

      up vote
      1
      down vote

      favorite

      using FreePBX 14.0.5.2 pjsip outbound trunk, I did not find a way to dial out #21#.

      Leading hash sign seems to be eaten and not make it through the trunk.

      Tried multiple ways (dialing through custom feature code, etc.) and adding a custom dial plan in the trunk or outbound route (compose 21# and prepend #), etc. Nothing seems to work.

      In contrast, dialing *21x.# through the trunk works well with setting up an outbound route dial plan (compose 21x.# and prepend *).

      This question is addressed here, as I did not find any helpful answers in the freepbx community forum.

      share|improve this question

      using FreePBX 14.0.5.2 pjsip outbound trunk, I did not find a way to dial out #21#.

      Leading hash sign seems to be eaten and not make it through the trunk.

      Tried multiple ways (dialing through custom feature code, etc.) and adding a custom dial plan in the trunk or outbound route (compose 21# and prepend #), etc. Nothing seems to work.

      In contrast, dialing *21x.# through the trunk works well with setting up an outbound route dial plan (compose 21x.# and prepend *).

      This question is addressed here, as I did not find any helpful answers in the freepbx community forum.

      freepbx

      share|improve this question

      share|improve this question

      share|improve this question

      share|improve this question

      edited Dec 6 at 17:36

      Rui F Ribeiro

      38.6k1479128

      38.6k1479128

      asked Dec 6 at 17:27

      mats1

      63

      63

      closed as too broad by Rui F Ribeiro, G-Man, RalfFriedl, msp9011, JigglyNaga Dec 7 at 9:54

      Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

      closed as too broad by Rui F Ribeiro, G-Man, RalfFriedl, msp9011, JigglyNaga Dec 7 at 9:54

      Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

          active

          oldest

          votes

          active

          oldest

          votes

          active

          oldest

          votes

          active

          oldest

          votes

          active

          oldest

          votes

          Leave a Reply

          Your email address will not be published. Required fields are marked *