View source for HOWTO MultiUser extension in depth version 5 and 6

''' HOWTO 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.

''' Methods used for connection ''' 

Two authentication methods that are used for a Multi-User extension:

● Registration

● IP Authentication


''' Requirements before setup '''

1. Enable multi-user extension in the license

a. To do so, please contact your account manager

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]]




3. Create a dedicated Extension

a. More information on this link -> https://wiki.bicomsystems.com/MT_6_Extensions

<span style="color: red"> NOTE : ‘Enhanced Services’ should not be enabled on the multi-user extension. </span>

4. Create a dedicated DID

a. More information on this link -> https://wiki.bicomsystems.com/MT_6_DID

After the creation of the the DID, edit the same on a tenant level and set 

‘Destination’ & ‘Value’ fields as shown below:

● Destination → Set to ‘Multi-User’

● Value → Set to a dedicated multi-user extension

[[image:DID.png|left|MultiUser selection]]




















Registration method

For setting a multi-user extension using a registration method, one should navigate to the following path:

● For CC : Home → Extensions → Edit dedicated extension for a multi-user

● For MT : Tenant in question → Home → Extensions → Edit dedicated extension
for a multi-userThe following needs to be set on the multi-user extension:

● Username

● Secret password

<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> 

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:

● 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

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

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

● For MT : Tenant in question → Home → Extensions → Edit dedicated extension for a multi-user

For an IP authentication to be set correctly, one should populate the following fields in

the following way:

[[image:ip.png|left|Incoming IP addresses]]








● '' 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:Host.png|left|Host Field]]






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]]

Additional needed field on the multi-user extension:

● '' Set Caller ID '' → set to  ‘No’

[[image:setcallerid.png|left|Set CallerID]]