*5 Doesn't make outbound calls anonymous

[Emdelco]

Hey there, can someone help me out (a walk through) of anonymous calling?
So *5 is the default value for calling out as anonymous, so i dial *5905xxxxxxx and it is registering through active calls as that number The *5 isn't being stripped by the system. So the call just stays silent and never actually gets through to the intended other end. There are no other dial codes for *5x so I don't think the DCs are getting confused. why is the system not pulling the *5

NEXT

Outbound rules,
First attempt: make a rule with just a prefix of *5 (Still does the endless call)
Second attempt: Make a rule with prefix *5 and strip 2 digits ( I also tried with only stripping 1 digit) (STILL does the endless call)
Third attempt: Make sure the Trunk is working (make a standard outbound rule for 10 digit numbers) WORKS FINE but no call anonymity
Fourth attempt: Make a post of the forum, and hope someone smarter than me can teach me something

Note* It's not even getting a SIP failure or anything, I'm not sure how this call is even making it to active

 

[JohnS_3CX]

Your phone will send the invite with the *5 to the PBX, but you need to see the invite that the PBX sends to the provider. You do not need to create any rules for this, your PBX will know how to handle the call.

Are you using a supported provider? And does your provider support anonymous calling?

A WireShark capture should show you if the call leaves the PBX and goes to the provider.

 

[eddv123]

Very rare but does your provider support *5 for CLID masking ? who are they ?

I have almost always found the *5 to work, the only time I experienced issues was with trying to dial *5 on Worldwide trunks which require in international format.