Open Source Training Seminar FreePBX Paid Support

Ticket #1036 (closed Feature Requests: fixed)

Opened 2 years ago

Last modified 1 year ago

unable to add a # in a trunk dial rule

Reported by: steve_mcneill Assigned to:
Priority: minor Milestone:
Component: Asterisk Configuration Version: SVN-HEAD
Keywords: Cc:
Confirmation: SVN Revision (if applicable):
Backend Engine: All Backend Engine Version:

Description

when creating a dial rule, if a number has a "#" in it, it will be deleted when you "apply changes"

i.e. a number used in australia to disable a call forward is #21#. when this is entered as a dial rule under "trunks", the whole line is deleted when it is applied. it seems to works ok under "outbound routes", though.

steve.

Change History

09/15/06 02:47:56 changed by vgster

  • priority changed from 5 to 2.

09/15/06 04:16:43 changed by RobThomas

This is valid. It's actually virtually impossible to _dial_ a '#' with a SIP phone, or with a Zap channel. Asterisk, and most SIP phones, interpret '#' as 'Send' (Eg, similar to a mobile phone). If you _really_ need to dial '#21#', create a Custom Extension of something (**21?) with the 'Dial' string Zap/g0/w#21#

It should, however, be warning you about not using #.

09/15/06 04:20:09 changed by RobThomas

  • type changed from Bugs to Feature Requests.

Actually, looking further into it, what exactly do you want to do in trunk dial rules? You can put #21# into outbound routes if you really need to.

(Changed to a Feature Request)

11/10/06 08:23:58 changed by gregmac

  • priority changed from crash to minor.

12/13/06 06:00:22 changed by eddtomu

can't even add a '+' to dial pattern?!

06/25/07 09:23:30 changed by wvroger

  • status changed from new to closed.
  • resolution set to fixed.
  • engine_version changed.
  • svn_rev changed.

fixed

Donate



Support
Download
Develop
Forums
News
Documentation
Paid Support
About

Paid Ads