You need to get the CLI being read correctly by the Grandstream gateway before you have any hope of passing it through to the other end of the SIP trunk. Is there anywhere in the gateway that would show a call log? Might also be worth asking Grandstream support.

I think the grandstream has the ability to syslog, could provide some information.

I will see what grandstream have to say. Probably worth asking over the the freepbx forums as well.

maybe this helps

https://community.freepbx.org/t/configure-grandstrea...

The problem is Caller Id is showing up as the trunk number instead of the PSTN number.

These are PSTN lines, not VOIP … is that correct ?

Sounds to me like they be ‘Feature Lines’ which a main hunt group number, which is what have been displayed, but each had a direct dial in number too.

Hi ,

It is a single BT PSTN line terminated to a single FXO port on the HT813 ATA.

I am not convinced that the Caller ID is getting relayed to Freepbx from the POTS line.

Well Pjsip logging shows this:

[2024-10-11 11:28:39] VERBOSE[462063][C-00000026] pbx.c: Executing [5000@from-pstn:9] ExecIf("PJSIP/5000-00000066", "1 ?Set(CALLERID(name)=5000)") in new stack

I think that is the root problem.

In reply to a post by dlucas46:

Hi ,

It is a single BT PSTN line terminated to a single FXO port on the HT813 ATA.

I am not convinced that the Caller ID is getting relayed to Freepbx from the POTS line.

In your original post you said ….

The problem is Caller Id is showing up as the trunk number instead of the PSTN number.

What do you mean by he ‘trunk number’ ? And what is the ‘wrong number’ you’re receiving instead .. (not the actual numbers themselves, {obv} just a description.

Do you have a standard analogue handset which has the ability to show caller display ?

You could connect this to the NTE and disconnect its current connection to the handset .. if this then works as you expect , the problem IS as you first guessed, your kit or its set up … if it doesn’t do as expected, it’s time to contact the voice service supplier.

In reply to a post by dlucas46:

Well Pjsip logging shows this:

[2024-10-11 11:28:39] VERBOSE[462063][C-00000026] pbx.c: Executing [5000@from-pstn:9] ExecIf("PJSIP/5000-00000066", "1 ?Set(CALLERID(name)=5000)") in new stack

I think that is the root problem.

The entry in the log file is only a symptom. As I said earlier, you have 2 things named 5000, so if you change one of them, you might get closer to pinning it down.

Hi,

Yes I get you point, but FreePBX wants the Trunk SIP name to match the Sip account on the ATA.
I am not sure I can change one or or the other and have them different if you get my meaning.

Edited by dlucas46 (Fri 11-Oct-24 23:00:19)

In Freepbx I have defined an incoming trunk. This is a PJSip extension with the number 5000.

On the Grandstream HTA the FXO port sip user is 5000 and pointed at Freepbx by IP address.
I have also used an option called Unconditional forward.

The Handsets I have are Analogue units on another H814 ATA , They are displaying internal caller ID correctly.

But if I get a phone call on the landline which is connected to a Grandstream H813 ATA FXO port,
the caller ID displayed is that of the PJSIP trunk / extension (5000) instead of the Mobile or other landline number. This information does not seem to be being feed through to Freepbx and then onto the handset.