Bluetooth caller ID

[russellfortune]

Hello,

We are evaluating Cisco 8851 3PCC devices. A primary reason for choosing the 8851 was its Bluetooth functionality however, when paired with an iPhone, the caller ID doesn't work as expected for local calls.

For example, if a local call comes in from XXXX XXXX, and the contact is saved in the phone book exactly this way, the name appears on the screen on the Cisco phone as expected. However, if the contact has been saved in E.164 format, e.g. +XX XXXX XXXX, the iPhone shows correct caller ID name from the phone book however, the Cisco phone does not show anything - just the number in local format.

It is fairly common for us to save numbers in E.164 format in our contacts as we are a very international business. This way, it also has the advantage being directly dial-able from the synced phone book when using the SIP lines without the need to reformat.

I have tested this all the way up to the latest firmware (11.3.1 MSR1-3). As this is part of the embedded Bluetooth feature, I'm not really sure where to start adjusting this in the same way I might if it was part of the SIP server. Does anyone have any suggestions or, is this a "feature"? :)

Thanks! 

[Dan Lukes]

Well, I have no personal experience with 8851, but I have some experience with SPA525G2, the predecessor of Bluetooth 3PCC 8851. based on it I have one advice only - phone numbers in address book needs to use same format if numbers as used in caller id.

Thus either:

 because incoming calls have are in national format, use national format in addressbook as well

 because your address book uses E.164 format, use E.164 format in incoming caller id as well (ask your VoIP proxy administrator to modify format of number)

If format of numbers needs not to be same for some reason, you may try to use "Caller ID Map" feature  to rewrite it, but I never tried it, so I don't know it will help even in your case.

[russellfortune]

It does seem a caller ID map would be the solution! This thread was helpful in understanding the details of it:

https://community.cisco.com/t5/voice-systems/caller-id-mapping/td-p/3237665

I would simply need to do something like this:

<:+xx>xxxxxxxx

However, Caller ID maps and Dial Plans seem to only be configurable for the SIP lines. Is there any way to use a caller ID map for the Bluetooth feature? We aren't having this issue on the SIP lines as everything comes in from the SIP Trunks in E.164 anyway. 

[Dan Lukes]

---

<:+xx>xxxxxxxx

---

It will not work for calls originated abroad.

---

Is there any way to use a caller ID map for the Bluetooth feature? We aren't having this issue on the SIP lines as everything comes in from the SIP Trunks in E.164 anyway. 

---

Sorry, it seems I misunderstood the issue. You said the iPhone (I assumed it's connected via BT) shows correct caller ID name from the phone book while Cisco (I assumed SIP lines configured on it) does not show anything. Moreover you sail "if a local call comes in from XXXX XXXX" while now you you are saying "everything comes in from the SIP Trunks in E.164 anyway", So I'm lost ...

[russellfortune]

Sorry, let me clarify. This is a 100% Bluetooth issue. No issues at all with the SIP lines.

The iPhone is intelligent enough to be able to do the matching from the phone book no matter whether the number is saved in local or E.164 format. The Cisco phone will only show the caller ID if there is a verbatim match from the contacts synced from the iPhone, which is an issue only for local calls as they could be saved in either format in the phone book.

The Caller ID map is clearly the solution as it will allow me to re-write the number it's just there seems to be no way to use it on a Bluetooth line?

[Dan Lukes]

Still lost, somewhat.It seems your "local call" is not mine "local call".

I assume incoming call not originated abroad delivered via SIP trunk to Cisco phone, passed thru BT to iPhone. According your description, the caller id of incoming call is E.164 which works on both Cisco and iPhone.

What your "local call" is ? Source, target, format of numbers, please.

All at all, Cisco uses exact match. It's because SIP uses no "phone numbers" but string identification of endpoint (although you may decide to restrict self to use only phone-number-like identificators).

Called id map works for calls arriving from SIP proxy to a Cisco ExtN only.

[russellfortune]

By local call I mean from a number that is within the country (i.e. not international) is received via. the cell network on the iPhone and the Cisco phone is used as a Bluetooth audio interface for that call. The SIP lines are in no way involved in this. If that were an international call, it would come up in E.164 format on the iPhone in the same way that all calls arrive on the SIP lines, so there would be no issue. The issue is specifically when a local call arrives via. the cellular network to the iPhone, the +XX is not included and thus does not match in the phonebook. 

[Dan Lukes]

I has been true, your "local call" is different beast than mine. OK.

Unfortunately, it seems you are out of luck (at least with SPA525G2; as I claimed already, I have no personal experience with enterprise/3PCC mode you are evaluating).   Cisco uses "string match" algorithm. Either you can configure iPhone to send numbers in E.164 format all the times, or you need to use national format of "local" numbers even in address book (and use caller id map to strip E.164 prefix from incoming local SIP call).