cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements
Please be advised, the GuideMe Wizard is no longer available on the Small Business Support Community. For search capability please use the community search field to find content related to Cisco Small Business documents, videos, and discussions.

Remote end name versus device local lists

953
Views
15
Helpful
8
Comments

During the call not only the number of remote end but name associated with remote end is displayed to local user. In some cases, the name delivered by SIP protocol is ignored by local device and other name is displayed instead.

Exact behavior seems to be documented nowhere.

Following interactions has been observed on SPA508G with 7.5.4 firmware. For the purpose of text bellow, the term 'local list' mean local phone directory maintained by user within phone. Interactions to other phone directories, like LDAP, has not been tested.

A. Incoming call

Name extracted from local list is preferred against name delivered by SIP protocol. If no record in local list, then name delivered by SIP protocol is displayed. Placed/answered/missed calls list are not used. Call record will be placed in answered or missed calls list with name shown on display.

B. Outgoing call

Name extracted from local/missed/answered calls list is displayed. If more than one list contain name related to called number, then local list is preferred against missed call list which is preferred against answered calls list. If more than one record matches within same list, then newest record wins. Displayed name WILL NOT BE changed, even after different remote name will be delivered from remote end (COLP service, 'Remote-Party-ID: ...;party=called;...' header within SIP 18x (or 200) response).

If no list contain name related to called number then COLP delivered remote name will appear on display when become available.

In both cases, call record will be added to "placed" list with name shown on display.

I would like to configure the device to always prefer COLP name against name stored in local answered/missed call list (but not against local phone directory maintained intentionally by local user), but it seems not to be possible. It's annoying because obsolete names related to particular line is are shown to many user just because they are in missed or answered list despite valid current name is delivered to phone by SIP protocol.


Also note SPA5xx Call History error on transferred calls (I didn't verified it by self yet)

Comments
Beginner

Hi Dan!

I cannot help you here, but just to let you know I would like to make the same configuration as you.

Joao

Beginner

We have the same issue. The fact that there seems to be no way of clearing the call lists remotely makes this even more unbelievable. It's definitely a showstopper for any large deployment.

Engager

Call lists can be cleared remotely using IPPhoneExecute/Init:CallHistory method triggered by SIP NOTIFY. But it clear all records from all lists (Missed Calls, Received Calls, and Placed Calls). It's not acceptable to clear all lists on all phones whenever name of a phone line changed ...

Beginner

I've come across your tip meanwhile, I haven't been aware of this, thanks! Sadly, the existing installation has a large number of SPA 900 series phones that IIRC can't be scripted this way. Besides, as you say, it's really not an acceptable workaround. It really makes me wonder how come so few people have issues with this behaviour...

Engager

It's very old method so it may be supported even on SPA9xx. May be with slight change - on older firmwares the SIP notify contain no URL of IPPhoneExecute script but script itself.

Hall of Fame Master

Post under discussions, not documents.

Community Member

This is a very serious problem. Dan, did you find any solution ? Better solution than clearing all missed/answered calls registers after every name change ? Thanks

Engager

I consider it very serious problem as well. Unfortunatelly, Cisco seems not to agree with it.

Naštěstí se u nás jména nemění až tak často takže to příjímáme jako nepříjemnou vlastnost, kterou lze přetrpět ...