Custom CallerID Hiccup?

[Russell]

Russell,
I've corrected your Forum Access - give the News and Announcements forum another refresh.
With regards to a custom CID - please open a ticket. We'll get this looked into.

Thanks. I did have forum access. Just didn't see anything related to what's being discussed in this thread or to the behavior others were reporting about the leading "1" - so wondering if there was somewhere else I needed to look for system changes.

[voipinit]

Same is happening here. 1 prefixed before the number on the phone CID and doesn't pick up the custom caller contact. I guess because with the 1 prefix it doesn't match the contact number.

[Russell]

The friendly support folks (Dylan in this case) mention my issue is fixed, which I confirmed. Thanks!

[VOIPoDylan]

This has now been fixed. Thanks for your ticket submissions and confirmations in this thread.

[VOIPoDylan]

The friendly support folks (Dylan in this case) mention my issue is fixed, which I confirmed. Thanks!

Russell,
You're quite welcome. Sorry about the hiccup folks!

[usa2k]

Thanks for the fix!

[fisamo]

Russell,
You're quite welcome. Sorry about the hiccup folks!

Any word on the cause of the hiccup? Sounds like something changed that shouldn't have...

[VOIPoTim]

Any word on the cause of the hiccup? Sounds like something changed that shouldn't have...

It was related to the migration. There was something not fully changed.

We're continuing to migrate remaining portions of our system out of The Planet gradually.

[sr98user]

My caller id always showed with a prefix "1-". I checked my caller id log for the last 6-7 days. But my caller id name was messed up yesterday and this morning. I have not checked after the fix was made. Hopefully the fix was global and not tied to individual account.

[sr98user]

Looking at the ATA configuration page, Last called number field does not have a prefix 1. Maybe my panasonic phone is adding it.