cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
447
Views
1
Helpful
8
Replies

DX650 Caller name not displayed for contacts configured for speed dial

ilana_ilana
Level 1
Level 1

Hello,

Is there any fix for DX650 BUG ID " Caller name not displayed for contacts configured for speed dial "

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCup95171

I am facing exactly same issue as mentioned into bug and there is no workaround mentioned by Cisco.

My DX650 version is sipdx650.10-1-2-41.

Can any one has alternate solution ?

Regards,

1 Accepted Solution

Accepted Solutions

Yup, As suggested by Mohammed,

Try to upgrade or downgrade, see if that works.

Because the bug lists 10.1(2) as the known affected release.

Thanks

Haris

View solution in original post

8 Replies 8

HARIS_HUSSAIN
VIP Alumni
VIP Alumni

If cisco Says there is not WorkAround, I fear there is none.!!

Now as the problem seems to be with Speed dials,

Try this

Phone A (Dx650) say 1111

Phone B (Any Model ) say 2222

Extension 3333 (Just an free extension not assigned to any phone) :- Configure call forward all to 2222

Instead of creating Speed dial for 2222 create for 3333, Check what is displayed !! 

If not try creating a Translation Pattern converting 3333 to 2222.

Update if it works

Thanks

haris

Please take time to rate and mark correct answers.!!!<<

Thank you Haris for alternate suggestion.

This will work but the speed dial display on phone itself will be 3333 not 2222 (actual number) 

You can mask the same so that it  displays the label or name instead of number

Please rate and mark correct as applicable

Sorry gents for late update.

The issue fixed after upgrading to the latest version.

Regards,

Did you try to download the suggest fixed release? Or even downgrade/upgrade?

There is no suggested fixed release mentioned on bug page.

I looked into the datasheet of latest version to find if bug is resolved in that but didn't find any thing.

You shld give it a try and downgrade or upgrade.

Yup, As suggested by Mohammed,

Try to upgrade or downgrade, see if that works.

Because the bug lists 10.1(2) as the known affected release.

Thanks

Haris