Okay, here is the "Big List of CID Attempts and Results using Google Voice (GV) on Panasonic cordless phone connected to OBi202"
My actual number last 4-digits start with 0, seems to funk things up in places, so I tried a 1. Anonymized my number to be: aaa-bbb-cccc or last 4 as 5678
{(<+:=555>xx.):ph} / Works!!!
{(<x:3>xxxxxxxxxx):ph} /Doesn't match to ring
Google Voice requires + in front (adds to CID) to match
{(<+x:3>xxxxxxxxxx):ph} /WORKS!!! 3-aaa-bbb-cccc on first, main screen
{(<+x:3>xxxxxxxxxx):ph},{ph} / WORKS! 3-aaa-bbb-cccc displayed. extra {ph} catches odd calls if miss the match
{(<+x:h>xxxxxxxxxx):ph},{ph} / Matches and rings. PRIVATE CALLER displayed
{(<+x:5678>xxxxxxxxxx):ph},{ph} / Matches and rings. PRIVATE CALLER displayed
{(<+x:78>xxxxxxxxxx):ph},{ph} / Matches and rings. 78aaabbbcccc displayed, no dashes
Noticed some stuff on 2nd page of CallerID upon checking call log
{(<+x:1678>xxxxxxxxxx):ph},{ph} / Matches and rings. 1678aaabbbcc.. displayed on first page, no dashes. On second page, last 2 cc on second line.
{(<+x:678>xxxxxxxxxx):ph},{ph} / Matches and rings. 678aaabbbccc. displayed on first page, no dashes. On second page, last 1 c on second line
{(<+x:2>xxxxxxxxxx):ph},{ph} /
Final Solution for SP2 (home) 2-aaa-bbb-cccc displayed on first page, with dashes (final, for now

)
{(<+1:*>xxx<->xxx<->xxxx):ph},{ph} / *-aaa-bbb-cccc
{(<+1:12>xxxxxxxxxx):ph} / 12aaabbbcccc No dashes
I know examples help me understand syntax, maybe this list will help someone.