DID not working and Inbound CLID query using Telstra - Business SIP

[TrevorC]

We've just reconfigured the Telstra NTU (OneAccess One270) for our customer so we can move them to 3CX (Version 16.0.4) using this guide https://www.3cx.com/docs/telstra-sip-trunk/
We're using Gateway Attached mode and as noted in the above there is no 3CX profile so we've chosen NEC SL2100.

Both in and outbound calls are working perfectly however I can't seem to get the DID's working. I also noticed the inbound caller ID is missing the leading 0 and I'm wondering if this may be related.

I've added the DID's to the Telstra SIP trunk and also added inbound rules but calls to any of the DID's just hit the main reception number (the first in the 100 number range). I even tried adding the DID without the leading 0 but that makes no difference. (though I didn't delete all of the DID's with leading 0's as I didn't want to have to re-add them all).

This is the first Telstra trunk we've setup but we have setup DID's for other sites using a different SIP provider. We also have a second trunk on this same system with the other provider and the DID's and inbound CLID on that are working as expected.

I'm not sure if Telstra need a different setup for the DID's or it's a side effect of the profile being used on the OneAccess NTU.

Any suggestions would be appreciated.

 

[cobaltit]

It's just a matter of looking at the logs/wireshark and seeing where the DID is being sent and then telling 3CX to look there.

 

[leejor]

Confirm that DID information is , in fact, being sent. (DID and caller ID information are two different things) If it is being sent, confirm the format of the number. Have a look at the 3CX Activity Log.

 

[TrevorC]

Thanks - I'll give both of those things a go today and advise what I find out.

 

[TrevorC]

OK both issues have been sorted.
The inbound DID issue was with the formatting of the DIDs on the trunk. I had to specify them without the leading 0 as that's how they are being presented by the NTU.
I'm not sure what I did wrong when I tested his before as it didn't want to work before.

The inbound Caller ID display was fixed by setting up inbound source patterns on the trunk (Caller ID tab).