Incoming wild-card routing still possible?

[usa2k]

I took my cell phone out of my Phone Book a while ago.
I have had 734******* as a white list call route
A test a moment ago, my cell phone went straight to Voicemail.

I will reboot the TA and retry. (But its not related to my end is it?)
Reboot, no-go.

I see if I try 1734* it dumps the 1 and adds the seven asterisks

[VOIPoTim]

I took my cell phone out of my Phone Book a while ago.
I have had 734******* as a white list call route
A test a moment ago, my cell phone went straight to Voicemail.

I will reboot the TA and retry. (But its not related to my end is it?)
Reboot, no-go.

I see if I try 1734* it dumps the 1 and adds the seven asterisks

Ray worked on it today, so I'll ask him to post about the usage cases and have him double check it again tomorrow.

[VOIPoRay]

I took my cell phone out of my Phone Book a while ago.
I have had 734******* as a white list call route
A test a moment ago, my cell phone went straight to Voicemail.

Should work now.... I was under the impression that you had DND set to go to voicemail and that wasn't working... after reviewing your account, i saw that it was "all unknown contacts" set to go to voicemail.... since the wildcard wasn't working on DND either, i ASSuMEd i'd found the problem and stopped there...

[usa2k]

I'll check when I get home, but the phone rang 3 times from work before going to VM and that is a good sign

[usa2k]

Confirmed. 734* is routing to white list