Difference between revisions of "HOWTO MultiUser extension in depth version 5 and 6"

From Bicom Systems Wiki

 
(9 intermediate revisions by 3 users not shown)
Line 1: Line 1:
''' HOWTO Multi-User Extension '''
+
'''HOWTO Multi-User Extension'''
  
What is a Multi-User Extension?
+
==What is a Multi-User Extension?==
  
Multi-user extension is used for connecting another PBXware or a third party PBX to our PBXware. It can be compared to a trunk as it is very similar.
+
A Multi-User Extension is used for connecting another PBXware or a third party PBX to our PBXware. It can be compared to a Trunk as it is very similar.
  
''' Methods used for connection '''
+
==Authentication Methods Used for Connection==
  
Two authentication methods that are used for a Multi-User extension:
+
Two authentication methods can be used for a Multi-User Extension:
  
Registration
+
*Registration Method
  
IP Authentication
+
*IP Authentication Method
  
 +
==Requirements Before Setup==
  
''' Requirements before setup '''
+
===Enable a Multi-User Extension in the license===
  
1. Enable multi-user extension in the license
+
*To do so, please contact your account manager.
  
a. To do so, please contact your account manager
+
===Allow IP Authentication on Tenants (if wanting to use IP auth)===
 +
[[image:allow.png|left|350px|Enable IP authentication]]
  
2. Allow IP authentication on tenants (if you wish to use IP auth.)
 
  
a. To do so, please navigate to the following path:
 
  
For MT​ : Master Tenant → Tenants → Edit tenant → ‘Features’ section → Allow IP Authentication for Extensions → Set to ‘Yes’
 
  
For CC​ : Settings → Servers → ‘Features’ section → Allow IP Authentication for Extensions → Set to ‘Yes’
 
  
[[image:allow.png|left|Enable IP authentication]]
+
*To do so, please navigate to the following path:
  
 +
''For Multi-Tenant Edition​:''
 +
'Master Tenant' → 'Tenants' → Edit 'Tenant' → ‘Features’ section → 'Allow IP Authentication for Extensions' → Set to ‘Yes’
  
 +
''For Contact Center Edition:''
 +
'Settings' → 'Servers' → ‘Features’ section → 'Allow IP Authentication for Extensions' → Set to ‘Yes’
  
 +
===Create a Dedicated Extension===
  
3. Create a dedicated Extension
+
:''For more information, please refer to this link:'' https://wiki.bicomsystems.com/MT_6_Extensions
  
a. More information on this link -> https://wiki.bicomsystems.com/MT_6_Extensions
+
<span style="color: red">'''NOTE​:'''</span> ‘Enhanced Services’ should not be enabled on the Multi-User Extension.  
 +
[[image:DID.png|right|450px|MultiUser selection]]
 +
===Create a Dedicated DID===
  
<span style="color: red"> NOTE​ : ‘Enhanced Services’ should not be enabled on the multi-user extension. </span>
+
:''For more information, please refer to this link:'' https://wiki.bicomsystems.com/MT_6_DID
  
4. Create a dedicated DID
+
After the creation of the DID, edit the same on a Tenant level and set the ‘Destination’ & ‘Value’ fields as shown below:
  
a. More information on this link -> https://wiki.bicomsystems.com/MT_6_DID
+
* '''Destination'''​ → Set to ‘Multi-User’
 +
:(Select box)
  
After the creation of the the DID, edit the same on a tenant level and set
+
* '''Value'''​ → Set to a dedicated Multi-User Extension
 +
:(Select box)
  
‘Destination’ & ‘Value’ fields as shown below:
+
==Registration Method==
  
● Destination​ → Set to ‘Multi-User’
+
When setting a Multi-User Extension by using a registration method, a user should navigate to the following path:
  
● Value​ Set to a dedicated multi-user extension
+
''For Contact Center Edition:''
 +
'Home' 'Extensions' → Edit dedicated 'Extension' for a Multi-User
  
[[image:DID.png|left|MultiUser selection]]
+
''For Multi-Tenant Edition​:''
 +
'Tenant' in question → 'Home' → 'Extensions' → Edit dedicated 'Extension' for a Multi-User
  
  
 +
''The following needs to be set on the Multi-User Extension:''
  
 +
* '''Username'''
  
 +
* '''Secret password'''
  
 +
<span style="color: red">'''NOTE:'''</span>  All mentioned information set on a Multi-User Extension above '''must be set in the same way''' on the remote side as well.
  
  
 +
''Further, it is very important to set the following on the remote side:''
  
 +
* '''FROM USER:''' Must contain the Tenant number & Extension number
  
 +
''For a proper caller ID to be sent from the remote side, it needs to be sent through:''
  
 +
* '''RPID''' (Remote-Party-ID)
  
 +
* '''PAI''' (P-Asserted-Identity)
  
 +
==More about RPID==
  
 +
The Remote Party ID (RPID) header field enables popular services as well as some regulatory and public safety requirements.
  
 +
These services include the following:
  
 +
*calling identity delivery
  
 +
*calling identity delivery blocking
  
 +
*tracing originator of call
  
 +
==More about PAI==
  
 +
The P-Asserted-Identity (PAI) and Privacy headers are defined in RFC 3325. The P-Asserted-Identity contains the caller ID information for the call on the INVITE SIP packet. The Privacy header contains information on which parts of the caller ID are private.
  
Registration method
+
==IP Authentication Method==
  
For setting a multi-user extension using a registration method, one should navigate to the following path:
+
When setting a Multi-User Extension by using an IP authentication method, a user should navigate to the following path:
  
For CC​ : Home → Extensions → Edit dedicated extension for a multi-user
+
''For Contact Center Edition:''
 +
'Home' 'Extensions' → Edit a dedicated 'Extension' for a Multi-User
  
For MT​ : Tenant in question → Home → Extensions → Edit dedicated extension
+
''For Multi-Tenant Edition​:''
for a multi-userThe following needs to be set on the multi-user extension:
+
'Tenant' in question → 'Home' 'Extensions' → Edit a dedicated 'Extension' for a Multi-User
  
● Username
 
  
● Secret password
+
In order for an IP authentication to be set correctly, a user should populate the suggested fields in the following way:
  
<span style="color: red">NOTE: Mentioned information set on a multi-user extension above must be set as the same on the remote side as well. </span>
+
[[image:ip.png|left|Incoming IP addresses]]
  
Further, on the remote side it is very important to set the following:
 
  
● ''' FROM USER ''' -> ​ must contain a ​ tenant number ​ & ​ extension number
 
For a proper caller ID to be sent from the remote side it needs to be sent through:
 
  
● ''' RPID ''' (Remote-Party-ID)
 
  
● ''' PAI ''' (P-Asserted-Identity)
 
  
More about RPID:
 
  
Remote Party ID header field enables popular services as well as some regulatory and public safety requirements.
 
  
These services include the following:
+
[[image:Host.png|left|Host Field]]
  
● calling identity delivery
 
  
● calling identity delivery blocking
 
  
● tracing originator of call
 
  
More about PAI:
 
  
P-Asserted-Identity and Privacy headers are defined in RFC 3325. The
+
* '''Incoming IP addresses (new line separated)''' → Set an IP address from the remote side
 +
:[(0-9)]
  
P-Asserted-Identity contains the caller id information for the call on the INVITE SIP packet. The Privacy header contains information on which parts of the caller id are private.
+
* '''Insecure'''​ → Set to ‘port,invite’
 +
:(Select box)
  
IP authentication method
+
* '''Host''' → Must contain the same IP address set in the '''‘Incoming IP addresses’'''
 +
:[(0-9)]
  
For setting a multi-user extension using an IP authentication method, one should navigate to the following path:
 
  
● For CC​ : Home → Extensions → Edit dedicated extension for a multi-user
+
Further, for a proper Caller ID to be displayed, the following needs to be set on the Multi-User Extension as well as on the remote side:
  
● For MT​ : Tenant in question → Home → Extensions → Edit dedicated extension for a multi-user
+
[[image:trust.png|left|Trust RPID and Use RPID]]
  
For an IP authentication to be set correctly, one should populate the following fields in
 
  
the following way:
 
  
● '' Incoming IP addresses​ '' → set an IP address from the remote side
 
  
● '' Insecure ''​ → set to ‘port,invite’
 
  
● '' Host​ '' → must contain the same IP address set in the ''' ‘Incoming IP addresses’ '''
 
  
[[image:ip.png|left|Incoming IP addresses]]
+
*'''Trust Remote-Party-ID​''' → Set to ​ ‘Yes’
 +
:(Options button)
  
 +
*'''Send Remote-Party-ID​''' → Set to 'Use Remote-Party-ID​'
 +
:(Select box)
  
  
 +
Here is another additional needed field on the Multi-User Extension:
  
[[image:Host.png|left|Host Field]]
+
[[image:setcallerid.png|left|Set CallerID]]
  
Further, for a proper Caller ID to be displayed, the following needs to be set on the multi-user extension as well as on the remote side:
 
  
● '' Trust Remote-Party-ID​ '' → set to ​ ‘Yes’
 
  
● '' Send Remote-Party-ID​ '' → set to “​ Use Remote-Party-ID​ ”
 
  
[[image:trust.png|left|Trust RPID and Use RPID]]
+
* '''Set Caller ID​''' → Set to ​ ‘No’
 
+
:(Options button)
Additional needed field on the multi-user extension:
+
 
+
'' Set Caller ID​ '' → set to ​ ‘No’
+
 
+
[[image:setcallerid.png|left|Set CallerID]]
+

Latest revision as of 07:22, 8 December 2020

HOWTO Multi-User Extension

What is a Multi-User Extension?

A Multi-User Extension is used for connecting another PBXware or a third party PBX to our PBXware. It can be compared to a Trunk as it is very similar.

Authentication Methods Used for Connection

Two authentication methods can be used for a Multi-User Extension:

  • Registration Method
  • IP Authentication Method

Requirements Before Setup

Enable a Multi-User Extension in the license

  • To do so, please contact your account manager.

Allow IP Authentication on Tenants (if wanting to use IP auth)

Enable IP authentication



  • To do so, please navigate to the following path:

For Multi-Tenant Edition​:

'Master Tenant' → 'Tenants' → Edit 'Tenant' → ‘Features’ section → 'Allow IP Authentication for Extensions' → Set to ‘Yes’

For Contact Center Edition:

'Settings' → 'Servers' → ‘Features’ section → 'Allow IP Authentication for Extensions' → Set to ‘Yes’

Create a Dedicated Extension

For more information, please refer to this link: https://wiki.bicomsystems.com/MT_6_Extensions

NOTE​: ‘Enhanced Services’ should not be enabled on the Multi-User Extension.

MultiUser selection

Create a Dedicated DID

For more information, please refer to this link: https://wiki.bicomsystems.com/MT_6_DID

After the creation of the DID, edit the same on a Tenant level and set the ‘Destination’ & ‘Value’ fields as shown below:

  • Destination​ → Set to ‘Multi-User’
(Select box)
  • Value​ → Set to a dedicated Multi-User Extension
(Select box)

Registration Method

When setting a Multi-User Extension by using a registration method, a user should navigate to the following path:

For Contact Center Edition:

'Home' → 'Extensions' → Edit dedicated 'Extension' for a Multi-User

For Multi-Tenant Edition​:

'Tenant' in question → 'Home' → 'Extensions' → Edit dedicated 'Extension' for a Multi-User


The following needs to be set on the Multi-User Extension:

  • Username
  • Secret password

NOTE: All mentioned information set on a Multi-User Extension above must be set in the same way on the remote side as well.


Further, it is very important to set the following on the remote side:

  • FROM USER: Must contain the Tenant number & Extension number

For a proper caller ID to be sent from the remote side, it needs to be sent through:

  • RPID (Remote-Party-ID)
  • PAI (P-Asserted-Identity)

More about RPID

The Remote Party ID (RPID) header field enables popular services as well as some regulatory and public safety requirements.

These services include the following:

  • calling identity delivery
  • calling identity delivery blocking
  • tracing originator of call

More about PAI

The P-Asserted-Identity (PAI) and Privacy headers are defined in RFC 3325. The P-Asserted-Identity contains the caller ID information for the call on the INVITE SIP packet. The Privacy header contains information on which parts of the caller ID are private.

IP Authentication Method

When setting a Multi-User Extension by using an IP authentication method, a user should navigate to the following path:

For Contact Center Edition:

'Home' → 'Extensions' → Edit a dedicated 'Extension' for a Multi-User

For Multi-Tenant Edition​:

'Tenant' in question → 'Home' → 'Extensions' → Edit a dedicated 'Extension' for a Multi-User


In order for an IP authentication to be set correctly, a user should populate the suggested fields in the following way:

Incoming IP addresses




Host Field



  • Incoming IP addresses (new line separated) → Set an IP address from the remote side
[(0-9)]
  • Insecure​ → Set to ‘port,invite’
(Select box)
  • Host → Must contain the same IP address set in the ‘Incoming IP addresses’
[(0-9)]


Further, for a proper Caller ID to be displayed, the following needs to be set on the Multi-User Extension as well as on the remote side:

Trust RPID and Use RPID




  • Trust Remote-Party-ID​ → Set to ​ ‘Yes’
(Options button)
  • Send Remote-Party-ID​ → Set to 'Use Remote-Party-ID​'
(Select box)


Here is another additional needed field on the Multi-User Extension:

Set CallerID



  • Set Caller ID​ → Set to ​ ‘No’
(Options button)