vPanel Contacts - unable to create custom caller ID
I have a support ticket open on this issue (KNN-120901), but they don't seem to think anything is wrong. I'm unable to create a custom caller ID anymore. It just erases the fields when I click the "Create Contact" button and nothing shows up in the contact list. I'm using Win 7 w/ IE8. Could someone else please try testing by creating a new contact with the example below using vPanel->Features-> Contacts.....Thanks
Group: Family
Custom caller ID: John's cell
Firstname: John
Lastname: Doe
Does the contact show up in your contact list?
Re: vPanel Contacts - unable to create custom caller ID
I have the same problem. Win 7 tried Chrome, Safari and IE9.
Let me know if you find a solution. Thanks
Re: vPanel Contacts - unable to create custom caller ID
Just worked for me. Win vista, firefox.
Re: vPanel Contacts - unable to create custom caller ID
It's the apostrophe. Using Windows 7 and Firefox. I can create the contact as "Johns Cell" but not as "John's Cell". Certainly a bug. Let's hope it gets fixed when and if we ever see the new VPanel.
Re: vPanel Contacts - unable to create custom caller ID
Works for me now, just leave out the apostrophe.
Re: vPanel Contacts - unable to create custom caller ID
Thanks....I left out the apostrophe and it works now. I could have sworn that I tried without the apostrophe before and it still didn't work. Anyway, something has changed since the last time I used it because I currently have over 20 entries that have the apostrophe included.
Re: vPanel Contacts - unable to create custom caller ID
I have the exact same problem... The only factor that is the same between all of us is the apostrophe, I really hope they fix this as my talking caller-ID does not work without punctuation too well lol.
Re: vPanel Contacts - unable to create custom caller ID
I contacted support about the problem and they were able to fix the issue with the apostrophe. I am impressed with the speed that they were able to respond and resolve the problem. It was escalated to T2 support after a few back and forth troubleshooting sessions.