Outbound rules # illegal character

[SimonDeLaplace]

Hi everyone,

after v18 upgrade the # is illegal as character for outbound rules.
Can you solve it?

the rules imported from v16 to v18, that yet have #, there no issue. But if i modify one of the rules or i make a new one, i cannot use the #

And yes, i need the #, i cannot change
BR

 

[Evolute IT]

Hi everyone,

after v18 upgrade the # is illegal as character for outbound rules.
Can you solve it?

the rules imported from v16 to v18, that yet have #, there no issue. But if i modify one of the rules or i make a new one, i cannot use the #

And yes, i need the #, i cannot change
BR

Where do you try to use the # sign?

We use it in prefixes and it works, but I don't believe it works for Prepend.

 

[ChrisC_3CX]

It should actually work for prepend too. What exact version of v18 are you running? You can check this under "Dashboard >> Information >> License/Version"

This was re-added in v18 U1:
https://www.3cx.com/blog/change-log/phone-system-change-log/

 

[SimonDeLaplace]

last versio on v.18
Sip trunk--> Route calls to--> impossible to use the outbound rules

 

[ChrisC_3CX]

Instead of specifying # on the forwarding, just prepend it on the Outbound Rule:

SIP Trunk/DID/CID Rule:


Outbound Rule:

 

[SimonDeLaplace]

I cannot because i have the rule with # and other rule without #

#60 -->go to voip provider ext call
60--> go to trunto to another 3cx

And i have a lot of this cause is a hotel booking company.
# to call outside the the hotel number
whitout # to call the 3cx of the hotel

 

[SimonDeLaplace]

I just ask to developer to add the # on that sip trunk page in the next patch.
I think is just a code error on charatchers control setting.
I can't belive that . _* works and # no, on pourpose

 

[ChrisC_3CX]

For the rules you have with # I would recommend simply creating an Outbound Rule specifically for the whole number since it's a static number and just place that Outbound Rule at the top so that it is matched first.