Incoming call number recognition from Remote Phone Book

[Attila]

Hello,

Our company recently switched to VOIP with SIP-T48G as the IP phones. I did the setup and configuration of all the SIP T48G's myself and there working great. But I have small differences on some of these phones concerning the incoming call display and contact recognition.

all are SIP-T48G
all on firmware 35.81.0.110
all have same hardware number
all have the same configurations (except the accounts off course)
all have the same Remote Phone Book and they are all updated
Remote Phone Book number format is with the + and no spaces between numbers
all have been restarted after configuration

This is happening:
Some IP Phones display incoming calls with the + like +32xxxxxxxx and some with the 00 like 0032xxxxxxxx for a call from the same caller.
Again our Remote Phone Book number format is with the + and no spaces between numbers.

These are the 2 problems:
Contact names are not found in the RPBook on the T48G that display the incoming calls like 0032xxxxxxxx? Despite that they both have the same RPBook setup in the Directory>Settings>Search Source List In Dialling. When I change the RPBook format to dubbel zero 00 instead of the + the problem reverts to the other IP phones.
Also if I use blank spaces in the phone numbers format (+32123 45 67 89) the contact name is also not found in the RPBook

I've checked all the settings on 2 phones and was unable to detect a difference in setup or settings. hopefully there is an easy solution and this long explanation wasn't even necessary.

Thx

[Kevin_Yealink]

(08-12-2017 05:51 AM)Attila Wrote:  Hello,

Our company recently switched to VOIP with SIP-T48G as the IP phones. I did the setup and configuration of all the SIP T48G's myself and there working great. But I have small differences on some of these phones concerning the incoming call display and contact recognition.

all are SIP-T48G
all on firmware 35.81.0.110
all have same hardware number
all have the same configurations (except the accounts off course)
all have the same Remote Phone Book and they are all updated
Remote Phone Book number format is with the + and no spaces between numbers
all have been restarted after configuration

This is happening:
Some IP Phones display incoming calls with the + like +32xxxxxxxx and some with the 00 like 0032xxxxxxxx for a call from the same caller.
Again our Remote Phone Book number format is with the + and no spaces between numbers.

These are the 2 problems:
Contact names are not found in the RPBook on the T48G that display the incoming calls like 0032xxxxxxxx? Despite that they both have the same RPBook setup in the Directory>Settings>Search Source List In Dialling. When I change the RPBook format to dubbel zero 00 instead of the + the problem reverts to the other IP phones.
Also if I use blank spaces in the phone numbers format (+32123 45 67 89) the contact name is also not found in the RPBook

I've checked all the settings on 2 phones and was unable to detect a difference in setup or settings. hopefully there is an easy solution and this long explanation wasn't even necessary.

Thx

Hi

Thanks for your information.
Firstly, let me expliain how callerID match contact work on yealink phone.
1. When phone receive incoming call, the server will send INVITE packet to phoen side, and phone will get number from FROM header or PAI header.
2. Phone will searvh all contact and match name for this number.
3. If matched, it will display name. It not, it will display this number.

For this issue, i need your help to exported PCAP file so that i can check which number the server send. So please help to reproduce this issue and export it for me.

BR
Kevin

[Attila]

Hey,

thanks for your explenation. So the question now is why on phone A the number is displayed with a +xxx and on Phone B is displayed with double zero like 00xxx?
while the caller is my celphone?

Thanks again.


Update: Problem Solved:
Afther I read Kevin's explenation again I checked the settings online on the server side and there is was. The caller ID number format was set to double zero for some of our voip acounts.

thx Kevin