Why doesn't name resolution work between networked locations?

If an employee from location A calls location B, only the internal extension is displayed in the XPhone Client. Since the phone numbers are included in the address book complete with dialling code and main phone number, name resolution does not work.

You must create rules that add the full phone number to the extension.

These two scenarios are common:

1. Unique / closed phone number plan

There is a unique / closed phone number plan, meaning there are no single extensions used in multiple locations. In our example there is a fixed phone number range assigned to each location.

Example:
Location Munich
+49 (89) 123456-0
3- to 4-digit extensions 100 to 300 or 1000 to 3000 

Location Wien  
+43 (1) 98765-0
3-digit extensions 400 to 699

On the XPhone Server open the XPhone Connect Server Manager (XPhone Connect) or XPhone Server Service Manager (XPhone UC). Open "Tools" > " Special configuration of dialling parameters". Log on with a XPhone Server Admin ID.

Now select the Munich dialling parameter and add the following rules:

PhoneToDisplay  
Value 1: ^[4-6][0-9]{2}$  
Value 2: 0043198765$0  

PhoneToDisplay  
Value 1: ^[1-3][0-9]{2,3}$  
Value 2: 004989123456$0

Save this setting.

Now select the Wien dialling parameter and add the same rules. Alternatively to adding the rules manually, you can export the rules with the "Export" button and import them again for Wien.

With these settings internal calls are signalled complete with dialling code and main phone number. This leads to the correct resolving of the names.

If a Munich employee now calls a complete number from Wien from the call journal, this call must also be converted to an internal call via additional rules. This is not necessary if the PBX implements these calls internally already.

Select the Munich dialling parameter and add the following rule:

DisplayToDialable  
Value 1: ^0043198765([4-6][0-9]{2})$  
Value 2: i$1  

Save this setting.

Select the Wien dialling parameter and add the following rule:

DisplayToDialable  
Value 1: ^004989123456([1-3][0-9]{2,3})$  
Value 2: i$1  

2. Connecting locations with node numbers

There is a non-unique or open phone number plan, meaning single extensions are used on multiple locations. This way for example the extension 123 is used in both Munich and Wien. Over the TAPI- or CSTA-interface by calls across locations, e.g. from Wien (node number 44) to Munich the node number is signalled, too (e.g. 44123).

Example:
Location Munich
+49 (89) 123456-0
3- to 4-digit extensions 

Location Wien  
+43 (1) 98765-0
3-digit extensions

On the XPhone Server open the XPhone Connect Server Manager (XPhone Connect) or XPhone Server Service Manager (XPhone UC). Open "Tools" > " Special configuration of dialling parameters". Log on with a XPhone Server Admin ID.

Now select the Munich dialling parameter and add the following rules:

PhoneToDisplay
Wert1: ^44([0-9]{3})$
Wert2: 0043198765$0  

PhoneToDisplay  
Wert1: ^33([0-9]{3,4})$
Wert2: 004989123456$0

Save this setting.

Now select the Wien dialling parameter and add the same rules. Alternatively to adding the rules manually, you can export the rules with the "Export" button and import them again for Wien.

With these settings calls across locations will be signalled without node number complete with dialling code and phone number. This leads to the correct resolving of the names.

If a Munich employee now calls a complete number from Wien from the call journal, this call must also be converted to an internal call (node number plus extension) via additional rules. This is not necessary if the PBX implements these calls internally already.

Select the Munich dialling parameter and add the following rule:

DisplayToDialable  
Value 1: ^0043198765([4-6][0-9]{2})$  
Value 2: i44$1

Save this setting.

Select the Wien dialling parameter and add the following rule:

DisplayToDialable  
Value 1: ^004989123456([1-3][0-9]{2,3})$  
Value 2: i33$1  

Note: If you have locations or dialling parameter in the same country, the number format in "Value 1" needs to be entered in the national format. If you have locations or dialling parameters with the same area codes, you must not enter the area code in the field "Value 1"! Always use the shortest possible callable format in the field "Value 1" with DisplayToDialable-rules.