Solved Sending Anonymous CallerID options

[whiteym]

This is more of an idea but apparently I can't post in the ideas section.
I have a customer with a Telstra SIP Connect - Enterprise service which requires that the callerID be an actual number from their trunk. When users use the *5 code 3CX changes this to 'anonymous' which Telstra rejects.
Telstra honors the SIP privacy header RFC and also accepts a dial code of *67 to make a number private.

My idea is that there be a setting (ideally per trunk) on the behaviour of the *5 code. There could be 3 options; send anonymous, send privacy header, send custom dial code.
That way if you have multiple trunks with different privacy formats the user only needs to know *5.

The SIP trunk documentaion for this should also be updated with this information re anonymous calling.

 

[YiannisH_3CX]

Hi @whiteym

I think you are not using the default Telstra template which is included in the PBX. The template is set up so *5 does not override the caller ID when calls are sent to the provider.
I suggest you follow the guide to set your trunk up: https://www.3cx.com/docs/telstra-australian-sip-trunk/
The guide also mentions that *5 should be changed if you are using Telstra to avoid conflicting with their Malicious Call Trace functionality.

 

[whiteym]

Hi @YiannisH_3CX

I think you are not using the default Telstra template which is included in the PBX.

I am using the template.

The template is set up so *5 does not override the caller ID when calls are sent to the provider.

The template does not make changes to the dial codes as that is handled elsewhere and is a global setting, so the template is not can't make any changes to *5.
If I don't change the *5 to something else it simply means that I cannot use the MCT feature.

The problem as I stated before is that when trying to make an anonymous outbound call the 3CX method to achieve this (regardless of the number configured for the dial code) is to change the from field in the sip header from <caller number>@<system ip or fqdn> to anonymous@<system ip or fqdn>.
Telstra SIP Connect will not route calls if the <caller number> is not associated with the trunk, since anonymous isn't a number in the trunk's range it rejects it playing a message that the call cannot be completed at this time.

In order to make an anonymous outbound call 3CX either needs to set the SIP privacy header as detailed in the RFC (which Telstra honors) or prepend *67 to the dialed number.

 

[YiannisH_3CX]

The template does not make changes to the dial codes as that is handled elsewhere and is a global setting, so the template is not can't make any changes to *5.

That means that the template is set up so that *5 is handled differently for that trunk, not that it can make changes to the dial code.


The template will replace the From: DisplayName to Anonymous but not the From:UserPart which is what Telstra reads. So the from will look like Anonymous<caller number@<system ip or fqdn>



That is what the EnforcedOutboundCallerID does.

If your outbound parameters do not look like that then you are using the wrong template.
Did Telstra say that they need the From: DisplayName appear as a normal number?

 

[whiteym]

I am using the right template. The screenshot I have of the original settings shows from: user being outboundcallerid. It's possible someone else was on the system making changes and I happened to get that instead of what it should be.
Changing it back to what it should be seems to have resolved the issue, thanks.

 

[NickD_3CX]

We can't really say how and why the settings were wrong, only point out what is the correct ones.

Regardless though, we are glad we could help you resolved the problem!