FreeSBC: Multiple Domains/Hosted PBXs Configuration - Revision history

Luc Morissette: Changed from FreeSBC to ProSBC

2023-10-18T13:23:38Z

Changed from FreeSBC to ProSBC

← Older revision		Revision as of 09:23, 18 October 2023
Line 1:		Line 1:
	=== '''''Applies to version: v3.0, 3.1''''' ===		=== '''''Applies to version: v3.0, 3.1''''' ===

	{{DISPLAYTITLE:~~FreeSBC~~:Multiple Domains/Hosted PBXs Configuration:Example}}		{{DISPLAYTITLE:ProSBC:Multiple Domains/Hosted PBXs Configuration:Example}}
	=Introduction=		=Introduction=
	~~FreeSBC~~ Hosted PBX Example (see [[FreeSBC:Hosted PBX:Configuration A\|~~FreeSBC~~:Hosted PBX]]) provides a step by step Hosted PBX Configuration of [~~[FreeSBC\|FreeSBC]~~] systems, using the Web Portal configuration tool. What will be discussed here, with guide for example configuration, is when there are multiple domains per PBX or several PBXs with different domains. This multiple domains/PBXs configuration is basically the extension of what is configured in single domain/hosted PBX, that including the setting of different domains, followed by specific routing for different domain destinations.		ProSBC Hosted PBX Example (see [[FreeSBC:Hosted PBX:Configuration A\|ProSBC:Hosted PBX]]) provides a step by step Hosted PBX Configuration of [ProSBC] systems, using the Web Portal configuration tool. What will be discussed here, with guide for example configuration, is when there are multiple domains per PBX or several PBXs with different domains. This multiple domains/PBXs configuration is basically the extension of what is configured in single domain/hosted PBX, that including the setting of different domains, followed by specific routing for different domain destinations.

	=Hosted PBXs Example=		=Hosted PBXs Example=
Line 82:		Line 82:
	==Access Control List==		==Access Control List==

	~~FreeSBC~~ will automatically create Access Control List for each NAP you created.		ProSBC will automatically create Access Control List for each NAP you created.

	[[Image:Remote_Workers_Access_Control_List_1.png]]		[[Image:Remote_Workers_Access_Control_List_1.png]]

	If you double-click one of the created ACL, you will see ~~FreeSBC~~ only accept the calls if source IP matches. In this sample; the calls from 192.168.1.10, 192.168.1.11, 192.168.1.12 will be accepted only.		If you double-click one of the created ACL, you will see ProSBC only accept the calls if source IP matches. In this sample; the calls from 192.168.1.10, 192.168.1.11, 192.168.1.12 will be accepted only.

	[[Image:SIP_Access_Control_List_2.png]]		[[Image:SIP_Access_Control_List_2.png]]
Line 252:		Line 252:
	=Activating the Configuration=		=Activating the Configuration=

	Changes made to the configuration of the ~~FreeSBC~~ units are stored in the OAM&P Configuration and Logging database. In order for changes to be used by the system, they must first be activated. This is done at the system level and accessed from the Navigation panel.		Changes made to the configuration of the ProSBC units are stored in the OAM&P Configuration and Logging database. In order for changes to be used by the system, they must first be activated. This is done at the system level and accessed from the Navigation panel.

	Check the following link for activating the configuration;		Check the following link for activating the configuration;

Luc Morissette: Added link to ProSBC use cases

2023-01-11T15:28:11Z

Added link to ProSBC use cases

← Older revision		Revision as of 11:28, 11 January 2023
Line 259:		Line 259:

	=SBC Use Cases=		=SBC Use Cases=
	[[~~Toolpack:Tsbc Use Cases A~~\|~~SBC~~ Use Cases]] ~~<br />~~		*[[ProSBC_Use_Cases\|ProSBC Use Cases]]
	[[~~FreeSBC_Use_Cases~~\|~~FreeSBC~~ Use Cases]]		*[[Toolpack:Tsbc Use Cases A\|SBC Use Cases]]

	=SBC Tutorial Guide V3.0=		=SBC Tutorial Guide V3.0=

Serdar Civici: /* Hosted PBXs Example */

2022-05-09T11:13:54Z

Hosted PBXs Example

← Older revision		Revision as of 07:13, 9 May 2022
Line 7:		Line 7:
	=Hosted PBXs Example=		=Hosted PBXs Example=

	[[Image:~~Hosted_Multiple_PBX_topo_1~~.png]]<br>		[[Image:Multiple_PBX_topology.png]]<br>

William Wong: /* Route Configuration for SIP Server to Remote Phones */

2020-10-21T08:37:42Z

Route Configuration for SIP Server to Remote Phones

← Older revision		Revision as of 04:37, 21 October 2020
Line 248:		Line 248:
	* for incoming call belonging to example2.com, on the route "called" field, can input /^([0-9]*)@example2.com/		* for incoming call belonging to example2.com, on the route "called" field, can input /^([0-9]*)@example2.com/

	[[Image:Multiple domains routes.png]]		[[Image:Multiple domains routes.png\|800px\|]]

	=Activating the Configuration=		=Activating the Configuration=

William Wong: /* Route Configuration for SIP Server to Remote Phones */

2020-10-21T08:36:25Z

Route Configuration for SIP Server to Remote Phones

← Older revision		Revision as of 04:36, 21 October 2020
Line 247:		Line 247:
	* for incoming call belonging to example2.com, on the route "called" field, can input /^([0-9]*)@example2.com/		* for incoming call belonging to example2.com, on the route "called" field, can input /^([0-9]*)@example2.com/
	* for incoming call belonging to example2.com, on the route "called" field, can input /^([0-9]*)@example2.com/		* for incoming call belonging to example2.com, on the route "called" field, can input /^([0-9]*)@example2.com/

			[[Image:Multiple domains routes.png]]

	=Activating the Configuration=		=Activating the Configuration=

William Wong: /* Route Configuration for SIP Server to Remote Phones */

2020-10-21T08:12:23Z

Route Configuration for SIP Server to Remote Phones

← Older revision		Revision as of 04:12, 21 October 2020
Line 242:		Line 242:
	[[Image:Route_Server_to_Remote_3.png]]		[[Image:Route_Server_to_Remote_3.png]]

	5- Here, we are creating 1 route entry for ~~each domain, in total of~~ 3 ~~routes in this example for incoming call from OPEN_NAP~~. In order for Registration/call to terminate correctly to the right NAP/PBX/Registrar, we need to set some condition to match specifically the registration/call		5- Here, we are creating 3 pairs of route entry from above for 3 domains. In order for Registration/call to terminate correctly to the right NAP/PBX/Registrar, we need to set some condition to match specifically the registration/call

	* for incoming call belonging to example1.com, on the route "called" field, can input /^([0-9]*)@example1.com/		* for incoming call belonging to example1.com, on the route "called" field, can input /^([0-9]*)@example1.com/

William Wong: /* Route Configuration for SIP Server to Remote Phones */

2020-10-21T08:09:24Z

Route Configuration for SIP Server to Remote Phones

← Older revision		Revision as of 04:09, 21 October 2020
Line 241:		Line 241:

	[[Image:Route_Server_to_Remote_3.png]]		[[Image:Route_Server_to_Remote_3.png]]

			5- Here, we are creating 1 route entry for each domain, in total of 3 routes in this example for incoming call from OPEN_NAP. In order for Registration/call to terminate correctly to the right NAP/PBX/Registrar, we need to set some condition to match specifically the registration/call

			* for incoming call belonging to example1.com, on the route "called" field, can input /^([0-9]*)@example1.com/
			* for incoming call belonging to example2.com, on the route "called" field, can input /^([0-9]*)@example2.com/
			* for incoming call belonging to example2.com, on the route "called" field, can input /^([0-9]*)@example2.com/

	=Activating the Configuration=		=Activating the Configuration=

William Wong: /* SIP NAP Configuration for Local Area Network */

2020-10-21T07:59:22Z

SIP NAP Configuration for Local Area Network

← Older revision		Revision as of 03:59, 21 October 2020
Line 78:		Line 78:
	[[Image:SIP_Server_NAP_Create_4.png]]		[[Image:SIP_Server_NAP_Create_4.png]]

	* Here, we need to repeat above steps and create NAP for every Hosted PBX, for example, NAP_PBX1 for PBX1 (192.168.1.10), NAP_PBX2 for PBX2 (192.168.1.11), and NAP_PBX3 for PBX3 (192.168.1.12) and so on if more.		* Here, we need to repeat above steps and create NAP for every Hosted PBX, for example, NAP_PBX1 (instead of SIP_SERVER_NAP) for PBX1 (192.168.1.10), NAP_PBX2 for PBX2 (192.168.1.11), and NAP_PBX3 for PBX3 (192.168.1.12) and so on if more.

	==Access Control List==		==Access Control List==

William Wong: /* Associate a SIP Domain with the new NAP */

2020-10-21T07:56:27Z

Associate a SIP Domain with the new NAP

← Older revision		Revision as of 03:56, 21 October 2020
Line 183:		Line 183:
	[[Image:Associate_SIP_NAP.png]]		[[Image:Associate_SIP_NAP.png]]

			* For each domain, for example, example1.com, choose OPEN_NAP and NAP_PBX1, and for example2.com, choose OPEN_NAP and NAP_PBX2, and so on.

	=Call Route=		=Call Route=

William Wong: /* Create New SIP Registration Registrar */

2020-10-21T07:52:56Z

Create New SIP Registration Registrar

← Older revision		Revision as of 03:52, 21 October 2020
Line 174:		Line 174:


	5- ~~Here, different~~ Registrars need to be created, so ~~repeat~~ the above steps for SIP_Registrar_1 for example1.com and choose NAP_PBX1 (192.168.1.10), SIP_Registrar_2 for example2.com and choose NAP_PBX2 (192.168.1.11), and SIP_Registrar_3 for example3.com and choose NAP_PBX3 (192.168.1.12).		5- Different Registrars need to be created, so do the above steps for SIP_Registrar_1 for example1.com and choose NAP_PBX1 (192.168.1.10), SIP_Registrar_2 for example2.com and choose NAP_PBX2 (192.168.1.11), and SIP_Registrar_3 for example3.com and choose NAP_PBX3 (192.168.1.12).

	==Associate a SIP Domain with the new NAP==		==Associate a SIP Domain with the new NAP==