FXO Gateway Caller ID

Status
Not open for further replies.

Heath

Customer
Advanced Certified
Joined
Aug 12, 2017
Messages
287
Reaction score
3
I installed a Grandstream FXO Gateway on the system.. Issue is there is No caller ID being transmitted to the 3CX system. There is Caller ID on the line as I had a legacy Caller ID display and was working, but not being sent on the 3CX. Everything else is working but the Caller ID.
 
Check that the caller ID type is correct, and if using Bellcore type, that the gateway is waiting for the caller ID to be sent before passing onto 3CX. That would be about 3 seconds or a couple of rings.

If I recall correctly, it is called number of rings before pickup.
 
Last edited:
The caller ID type is correct. It’s set for 4 rings
 
Looking at the 3CX Activity Logs shows no sign of caller ID?

Four rings is an awful long time before an incoming call begins ringing an extension on the PBX. Is that , in fact, what is happening?
 
in looking in the user manual it states the default for number of rings for caller ID is 4. In also looking in the webgui firmware of the FXO under the caller ID number of rings it does say default is 4.

Caller ID is broadcasting. I pulled the telco cord from the FXO and reconnected to traditional phone with caller id display to test and see if caller id is being broadcasted and nunber snd name is being displayed. So if it broadcasting it seems it’s a setting either with the FXO or PBX or both
 
  • Like
Reactions: Evolute IT
What model Grandstream gateway are you using? Waiting 4 rings before the gateway passing a call onto the PBX is way too long, you risk people hanging up. Perhaps you are not looking at the correct option. Other posts I've come across, seem to suggest that the Grandstream default is 2 rings.

Did you check the 3CX Activity Log (Verbose) to see if the caller ID is there?
 
I'm using a GrandStream GXW4108. I've attached a screen print of the user manual. I noted where it states default is 4 for Caller ID.
 

Attachments

  • fxo.png
    fxo.png
    333.6 KB · Views: 7
So, according that the information, the gateway is smart enough to send the call sooner if caller Id is detected, and will only wait for 4 rings if it does not detect anything.

The question now is...how long does it take before a call rings on the PBX? Is the gateway actually waiting 4 rings, because if it isn't, then that suggests it is detecting caller ID.
 
  • Like
Reactions: Evolute IT
Just dialed it from my cell. And it’s about 2 rings before the PBX rings
 
So if it is set to answer on 4 rings, then it suggests that the gateway is detecting caller ID and passing the call after only 2 rings. Did you check the 3CX Activity Log (Verbose) to see if 3CX is receiving caller ID?
 
I didn’t see it
 
Haven't used Grandstream devices a lot. Does it have any sort of syslog available, that will show what is happening internally?
How many PSTN lines into the gateway? They all have caller ID assigned? Is here an option to assign the caller ID options on a per-trunk basis, and perhaps all have not been assigned correctly?

Could the caller ID transport type, on the gateway be incorrect?
 
Last edited:
  • Like
Reactions: N_G
There is something to setup syslog but it’s asking for server info to send syslog info which I don’t have. 2 pots lines are connected to the gateway and both have caller ID. I couldn’t find anything on the caller id per line basis
 
If you still don't have any luck in getting this working, as a last resort, I would suggest doing a "factory" reset on the gateway and re-provision. I've seen devices "say" that they are set one way, but don't behave as if they are. Something gets "stuck". Perhaps a reset will fix, if that is the case here.
 
  • Like
Reactions: Evolute IT
I did a factory reset and re-provision and no change.
 
Any luck in using the syslog to confirm that the gateway is seeing the caller ID?
 
I did the syslog. And from what it looks like the from says unknown. What's interesting is the phone company is broadcasting the Caller ID Information, as I connected back my traditional phone and made a test call, and was broadcasting the caller ID Information. I'm still at a loss here
 
Maybe there is an issue with the gateway(hardware, or firmware), without a second one to test with, you are not left with a lot of options at this point. Did it work correctly in the past, or is it new? Is it running the latest firmware? If it is, and it allows, you might try going back to the previous release, just to see what happens. You don't seem to have much to loose at this point.

The only other thing that it might be,(and I have seen things like this), but it is long shot, is that the piece of hardware (CLASS service card) in the central office switch, has an issue. It might be that it is being sent at a low level, still enough to be detected by your caller ID device, but not by the gateway. If your lines come from a "remote switch" , then there is more likelihood that all will be affected. If you are close to the host switch, then there more of a chance that each line equipment will be assigned to a different "part" of the switch so the issue would not be happening on all lines. Of course that will also depend on the line capacity of the switch and where you line equipment was assigned.

You did try calls on more than one line, right?
 
Well it just so happens that I do have a 2nd FXO gateway. Same model. And I tried that and still caller ID still comes up with unknown. Now as far as the switch. I am next door to the main hub switching office (can’t get any closer).

Now for kicks and giggles I tried the gateway at a different location and still same issue on the caller ID. Still broadcasting unknown on both gateways.

And this is a new setup and I checked it has the latest and most recent firmware.
 
Status
Not open for further replies.

Forum statistics

Threads
111,973
Messages
590,071
Members
164,892
Latest member
Phone1stStop