Hiding the calleID

Status
Not open for further replies.

Dominique_CH

SMB User
Advanced Certified
Joined
Mar 20, 2020
Messages
84
Reaction score
15
Hi folks,
I understood that we can use *5 to hide the callerID, which works fine if the user types *5 ahead of the number to be dialed as 3CX removes that code before sending it to an outbound rule. However, I have a problem w/ one SIP-provider who doesn't manage well the callerID-settings, so that I need to hide it only when selecting that provider. I went into the specific outbound rule and prepended *5. But that doesn't work and results in following log entry: "Target=Unknown:*50041xxxxxxxxx@(Ln.10001@myprovider)". Moving *5 in the callerID-field doesn't work either as it is ignored by the provider.

So, it there a way to prepend the *5 before it getting to the outbound rule so that 3CX removes it or any other way to resolve this issue?
 
To first clarify what it is exactly you are trying to achieve, are you saying that you want to hide the Caller ID only for calls going through this one specific SIP Provider?

If yes, prepending *5 on the Outbound rule will not work as it is a 3CX dialcode and it is 3CX that will change your Caller ID to anonymous before sending the call outward. That said, the dialed number will not have *5 prepended when it gets matched against Outbound rules as the dialcode (*5) has already been process and removed at this point. If you want calls to *5 to match a specific Outbound rule you will have to use a second prefix that will actually be used to match an Outbound Rule.

For instance:

Let's say you want to call number 123456789 but you want to hide your Caller ID. You also want this call to go out through a specific SIP Trunk. Create an Outbound Rule for that SIP Trunk to match calls with a specific prefix such as 888 and then strip 3 digits(3 for this case since it's 888). Then, dial *5 for the dial code + the Outbound Rule prefix + the number. You will end up with *5888123456789. 3CX will process the *5 dial code and remove it from the dialed number, it will also change your Caller ID to "anonymous". It will then have the remaining dialed number matched against the Outbound Rules (remaining number at this point = 888123456789) and it will match your one Outbound rule that looks for 888 as the prefix. Since the Outbound Rule strips 3 digits, the 888 will be removed and the call will be sent outward to 123456789 with Caller ID "anonymous".

Hope this helps!

Please do elaborate further or correct me if I have misunderstood the situation.
 
Chris,
I don't want users to dial specific prefixes if that's what you're proposing by "Then, dial *5 for the dial code + the Outbound Rule prefix + the number" and if so, I wouldn't need a prefix.
For example, I want all calls starting with 00 to use that provider. Now I'd like to add a prefix *5 somewhere so that 00XXXXXX becomes *500XXXXXX BEFORE getting to the Outbound rule. Possible?
 
You can have the outbound rules route all calls starting with 00 to that provider, but, if you want to make use of the *5 option, then the caller will have to dial that. It must be sent from the set, to 3CX. The only other way to add it is if the set has an internal dialplan, that allows digit strings to be modified. You could then replace 00 with *500.

What you might be able to do, is to add the call blocking prefix, used by your provider, in the outbound rules, for that route.

Talk to them and see what sort of prefix they require.

Keep in mind, that there may be times when you need to send a CID number, as not everyone accepts anonymous calls, so, you may have to have another prefix, that takes a different outbound rule, to the same trunk group.
 
Last edited:
  • Like
Reactions: ChrisC_3CX
leejor above is quit right when he/she states "may be times when you need to send a CID number". That is indeed the requirement for my Network Service Provider otherwise a 403 Forbidden (good reason for that) will result if you just sent anonymous. There are three ways to get around that from the Network Service Provider perspective: (1) Code Prefix Dialing in front of the TO number which you would set within your Outgoing Rules assocuated with the SIP Trunk Group; (2) Ask the Network Service Provider to apply the Number Withhold Service per DDI as needed or all DDI within their network; (3) Use the PRIVACY Header (PRIVACY: id) within the outgoing INVITE. For all these methods the FROM is still a valid DDI. I have tried looking for a PRIVACY Header in the 3CX configurable settings for my own use but can't find it yet, if it exists. Good luck.
 
Ok, thanks for your advice confirming I wasn't missing something in the 3CX-configuration.
It might be a feature to think about by 3CX to provide some future release w/ a shortcode-functionality allowing to change a user's input such as 00n into xx00n or anything else before it gets processed.
 
I'd love to, but I have "insufficient privileges" to do so
 
@Dominique_CH

Restrictions do apply for posting in our Ideas section, however, anyone should be able to upvote a feature request in our ideas section. To upvote a post, simply click on the +1 button(green) in the upper-right corner of the post.
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,982
Messages
590,119
Members
164,908
Latest member
FarizQasimov