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.
Now most inbound calls don't show a name at all in the VPanel.
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.
Last edited by tritch; 10-13-2016 at 03:52 PM.
Bookmarks