Using *5 in outbound rules, but is has stopped to work after SP6, how to solve?

[jed]

Hi

We have a customer with a beroNet ISDN Gateway, and a outbound rule that add *5:
Call starting with 7, and it is a 9 digets number, we want to Strip 1 Digit and add *5 to call out as an anonymous. This have been working like a charme until SP6.

We have been testing:
On another customers beroNet ISDN gateway, same problem.

We have been testing the same outgoing roule on a SIP Trunk, and we see that we send *5 and the number ang recieve a 403 Permission denied from the SIP Trunk, so I expect them to recieve the complete number including *5.

If I just use a "Send all" Outbound Roule and dial *5 in front of the number, I do call out with anonymous number.

If I just use a "Send all" Outbound Roule and dial *5 in front of the number that goes through the beroNet gate way, I do show the trunknumber..

Anyone had the same and came acros a solution for this?

Thank you in advance

 

[complex1]

Hi,

Do not prepend *5 to the number in the outbound rule, but prepend *5 when dialing the number.

 

[jed]

Thank you @complex1 for your time to answer.

However I was looking for an answer for what has changed with SP6, and how to get our functionality back, to just show "Hidden number" or anonymous, when using our Outbound Rules, which was working before SP6.

Thanks.

 

[CentrexJ]

Jed, perhaps the Beronet can be modified to use a different code than *5 to block the number?

 

[jed]

Hi @CentrexJ
Thank you. The beroNet box has not changed, the only thing that has changed is updating from SP5 to SP6, and the complains is hitting us like "Florence", so we just want to come back to "normal".

With SP6, I see a change in the SIP Outbound Parameters where we can now select: "EnForceOutboundCallerId" To be used when you want to send Anonymous via PAI.
The Parameter might have be added because of all the talking about 911 numbers, however, I cant find any thing decribing this new Paramneter, nor if it should have "spioled" the old functionality.

Thank you

 

[leejor]

In Denmark, the prefix to block Caller ID would seem to be #31#. Would you not prepend the number in the outbound rules with that?

 

[jed]

Hi @leejor
Thank you, you are right about the #31# in DK, but we get an "Not allowed" from our 3CX PBX when using signs * / # in the Prepend after installing SP6 :-(

For this case I made a workarround Prepending 1111 and use this as a filter on the beroNet to make the beroNet box send the anonymous.
However this "is not 3CX standard" and it looks odd in the Calllog adding 1111 in front of the number, and dosent answer what has been changed with the SP6, perhaps we are not allowed to use special caracters anymore in the Prepend, or I have to set something different in the SIP Outbound Parameters for the beroNet box / SIP Trunks?

Thank you

 

[leejor]

I would hope that blocking the use of # or * in the prepend was intentional. If so, there must be an explanation. If not, then it may be "corrected" in future updates.

I know that in North America, to block, we use *67 as a prefix, the workaround is to send 1167, as 11 was the rotary dial substitution for *. I have encountered gateways that will not take * on 3CX trunks.

 

[jed]

@leejor Did you by any change test on your system, to see if it is just me that have the error when prepending *5?
I dont know if * and # is removed by a mistake or it's on purpose?
I did try to change the Dial Code to 1111 to Block Outbound CallerID, but the Dial Codes need to start with a *

 

[leejor]

I'm not using the same version as you, so I can't confirm a change with the latest update. I just remember years ago, when trying to send a * to a SPA3102 .and the character recieved by the gateway did not correspond to a *

You say you are using a Beronet ISDN gateway and you say you get

403 Permission denied from the SIP Trunk

Are there logs, in the gateway that allow you to determine exactly what was sent by 3CX and, in turn, what caused the 403 message. Was it the gateway itself (and why), or the digits sent out on the ISDN line? Perhaps using Wireshark.

Compare a failing call, with a successful one done this way...

If I just use a "Send all" Outbound Roule and dial *5 in front of the number, I do call out with anonymous number.