NetSIP - Caller ID for Forwarded call.

[JettechRob]

Hi All,

I have NetSIP trunks running nicely on a self-hosted V20 Pro install for our office.
We can't get the Incoming caller ID passed through when forwarding calls out of 3CX to our on-call technicians.

NetSIP have confirmed that we have Trusted CLI active,
but we're not presenting the correct information to NetSIP to allow it to be passed on.

This is the data from NetSIP Call Log
What options do we need to set in 3CX to make this work?

Any help is appreciated

 

[TheodorosG_3CX]

Which sip field has the provider specified that require to represent the caller id upon forwarding?

 

[JettechRob]

NetSIP have asked to confirm the following.

"Check with 3CX if their platform is capable to register the original callers CLI if the call is diverted from their platform."

Also, the Trunk Settings have 3 options for presenting Caller ID Header
Which is most suitable for 3CX?
- P-AssertedID
- RemotePartyID
- From

And which Option in the 3CX trunk setup should be used to achieve what we are trying to.

 

[TheodorosG_3CX]

If your provider is taking this information from the P-AssertedID most probably this has to be configured as:


But in any case they need to clarify from which Sip field they take the information in order to forward.

 

[JettechRob]

I have updated 3CX Trunk config as above but the CLI is still the main trunk#

Awaiting NetSIP

Thanks for the help thus far.

 

[TheodorosG_3CX]

You are welcome

 

[JettechRob]

NetSIP have advised the following


Please see below the possible reason why the caller ID is being overstamped.
Please be advised that your account is intrusted mode so all CLI for outbound calls should go through unless the following below.

Trusted
Trust whatever caller ID the customer sends us. We still verify it for format, and make sure its an ACMA allocated range, but that is all.

 

[TheodorosG_3CX]

Normally and based on the your reply, testing with settings from my previous reply will work.

 

[JettechRob]

Sadly, it is not.

Am I missing anything?
both the trunk and the 3CX are configured with ONSN number formats

Does anything need to be defined in the Default CallerID box?

 

[TheodorosG_3CX]

Have you run a capture to verify that?
If so and if the PBX does sent the information you need to check this further with your provider.

 

[JettechRob]

Capture from 3CX of the invite between 3CX and my mobile with settings above

 

[TheodorosG_3CX]

If this is configured in the P-Asserted Identity what is the outcome?

 

[JettechRob]

No change

 

[TheodorosG_3CX]

Which template are you using? Is this a Generic Provider Template?

 

[JettechRob]

Yes.

 

[JettechRob]

After some further testing,
We have confirmed that our account will accept any CLI from 3CX to the trunk that we wish to present
We can put any valid number in the Default outbound caller ID and the call will work.
So it's not the carrier blocking the ID, we're just not presenting it to them correctly for some reason.

 

[TheodorosG_3CX]

Glad to know that this is resolved.

 

[JettechRob]

It's still not resolved.
We've proven that NetSIP will take whatever we send it

We still need to get 3CX to send the correct data.

 

[TheodorosG_3CX]

This has to be checked with the provider and the settings i sent in previous reply. Maybe you need to customize the template but not something i can advice further.

 

[leejor]

So when comparing what numbers work, and what you are sending (shown in the posted logs of outgoing calls), is there a difference in the number length, or format? If you take the same number, that fails on the forwarded calls, and put that directly in the trunk settings, forcing 3CX to send that, does it work?