Incoming Caller ID

[budmaster]

Lately I have noticed numbers that call are shown as unavailable. The same number can call again later in the day and the name shows. I have noticed this with a few numbers lately.

[VOIPoBrandon]

Have you experienced this issue any further? Look forward to hearing back from you - thanks!

[andrew]

Have you experienced this issue any further? Look forward to hearing back from you - thanks!

I have the same issue

[GreenLantern]

Doesn't happen too often, but it does randomly happen every now and then.

Sometimes I'll get 2 or more calls in a day from the same person. One call may show caller id, but the other(s) may not.

[andrew]

I submitted a ticket with call examples (date/time + Call Reference ID) and they want me to do some network test? This has nothing to do with my network, if I unplug the device the web portal would still show the same thing! Speaking of the device mine died months ago, any way to get it replaced, and can someone look into ticket #EJX-745-15552 about the callerid?

[VOIPoTim]

I submitted a ticket with call examples (date/time + Call Reference ID) and they want me to do some network test? This has nothing to do with my network, if I unplug the device the web portal would still show the same thing! Speaking of the device mine died months ago, any way to get it replaced, and can someone look into ticket #EJX-745-15552 about the callerid?The issue with Caller ID that some of you were seeing should be resolved now. Please re-test now.

[tritch]

The issue with Caller ID that some of you were seeing should be resolved now. Please re-test now.

Whatever your developers did to fix this issue, has now broken your Custom Caller ID CNAM feature effective 7/17/16.

My dad who also has Voipo has been complaining that all of his Custom Caller ID (CNAM) are no longer working (except for Voipo-to-Voipo calls). The Custom CNAM shows up OK in vPanel call history, but the actual CNAM sent to the phone now shows the normal CNAM not the Custom CNAM anymore.

Please fix this feature.

[VOIPoTim]

Whatever your developers did to fix this issue, has now broken your Custom Caller ID CNAM feature effective 7/17/16.My dad who also has Voipo has been complaining that all of his Custom Caller ID (CNAM) are no longer working (except for Voipo-to-Voipo calls). The Custom CNAM shows up OK in vPanel call history, but the actual CNAM sent to the phone now shows the normal CNAM not the Custom CNAM anymore.Please fix this feature.Yes, it looks like the main Caller ID name fix did break the "custom" name in contacts. Our developers have a fix for this in place now and it should be pushed out later today or tomorrow. They're just finalizing testing. Sorry for the inconvenience.

[tritch]

Yes, it looks like the main Caller ID name fix did break the "custom" name in contacts. Our developers have a fix for this in place now and it should be pushed out later today or tomorrow. They're just finalizing testing. Sorry for the inconvenience.

Thanks Tim. The feature is working again...much appreciated.

[andrew]

Now most inbound calls don't show a name at all in the VPanel.

[RingyDingyDave]

Now most inbound calls don't show a name at all in the VPanel.

FWIW, I am seeing the same thing, in both VPanel and the CallerID on my phone. Incoming calls that used to show a name now show only the number.

[tritch]

Everyone else still seeing this issue starting a few months ago?

The proper CNAM is not coming through to the phone, but showing up OK in vPanel call history.

I received 2 spam calls this morning as shown below....

vPanel shows:

Caller ID: 2812058935
CNAM: TOMBALL TX

Caller ID: 5714444350
CNAM: ARLINGTON VA

Phone shows:

Caller ID: 2812058935
CNAM: 2812058935

Caller ID: 5714444350
CNAM: 5714444350

The correct CNAM is not being delivered to the phone anymore.

UPDATE: My fault. It seems Voipo made a protocol change to their SIP INVITE "Caller ID Header" to support PAI (P-asserted Identity) protocol. I reconfigured my device to support both Caller ID header "PAI" and "FROM" protocols and the CNAM is coming through properly now.