Network Intelligence/Restcomm Configuration - Revision history

Allyntree at 14:15, 16 May 2022

2022-05-16T14:15:40Z

← Older revision		Revision as of 10:15, 16 May 2022
Line 1:		Line 1:
	{{DISPLAYTITLE:Restcomm CPaaS Platform Configuration}}		{{DISPLAYTITLE:Restcomm CPaaS Platform Configuration}}

	~~{{DISPLAYTITLE:Setting the Role to Standalone}}~~
	{\| class="wikitable"		{\| class="wikitable"
	\|-		\|-

Allyntree at 14:14, 16 May 2022

2022-05-16T14:14:45Z

← Older revision		Revision as of 10:14, 16 May 2022
Line 1:		Line 1:
	{{DISPLAYTITLE:Restcomm CPaaS Platform Configuration}}		{{DISPLAYTITLE:Restcomm CPaaS Platform Configuration}}

			{{DISPLAYTITLE:Setting the Role to Standalone}}
			{\| class="wikitable"
			\|-
			\|rowspan="3"\|This article applies to:
			\|'''Product'''
			\|'''Version'''
			\|-
			\|SBC
			\|3.0, 3.1
			\|}
	=Introduction=		=Introduction=
	This document provides instructions on how to configure ProSBC to interoperate with the [https://www.restcomm.com/ Restcomm] Communications ~~platform~~ as a ~~service~~ (CPaaS) system. <br/>		This document provides instructions on how to configure a ProSBC to interoperate with the [https://www.restcomm.com/ Restcomm] Communications Platform as a Service (CPaaS) system. <br/>
	Restcomm CPaaS platform provides programmable voice like IVR service, programmable SMS service, mail, chat services and more, for service ~~provider~~ and enterprise customers. <br/>		Restcomm CPaaS platform provides programmable voice-like IVR service, programmable SMS service, mail, chat services and more, for service providers and enterprise customers. <br/>
	[[ProSBC]] acts as a Session Border Controller to protect the Restcomm CPaaS platform and provides many essential protection features for voice communications over SIP and RTP traffic. <br/>		[[ProSBC]] acts as a Session Border Controller to protect the Restcomm CPaaS platform and provides many essential protection features for voice communications over SIP and RTP traffic. <br/>
	With the example below, a softphone - PhonerLite, and a real mobile phone are used to provide an originating endpoint that will call through [[ProSBC]] to Restcomm platform. <br/>		With the following example below, a softphone - PhonerLite, and a real mobile phone are used to provide an originating endpoint that will call through [[ProSBC]] to the Restcomm platform. <br/>
	Furthermore, in this example, [[ProSBC]] AWS is used, but in fact, any [[ProSBC]] platform will be able to achieve the same setup. <br/>		Furthermore, in this example, [[ProSBC]] AWS is used, but in fact, any [[ProSBC]] platform will be able to achieve the same setup. <br/>

Line 12:		Line 22:


	# '''Restcomm welcome announcement''' - PhonerLite sends 'direct call' to ProSBC with called information 1234@52.60.132.155 where 52.60.132.155 is the public Elastic IP used for voip interface in this ProSBC AWS. ProSBC makes a mapping of called number to 1234@netg2.restcomm.com before making an outgoing call to Restcomm platform. PhonerLite hears a welcome greeting from Restcomm platform. Configuration steps (available in different sections of PhonerLite Configuration, ProSBC Configuration below):[[File:Restcomm_welcome_announcement.PNG\|1000px]]		# '''Restcomm welcome announcement''' - PhonerLite sends 'direct call' to ProSBC with called information 1234@52.60.132.155 where 52.60.132.155 is the public Elastic IP used for voip interface in this ProSBC AWS. ProSBC makes a mapping of the called number to 1234@netg2.restcomm.com before making an outgoing call to the Restcomm platform. PhonerLite hears a welcome greeting from Restcomm platform. Configuration steps (available in different sections of PhonerLite Configuration, ProSBC Configuration below):[[File:Restcomm_welcome_announcement.PNG\|1000px]]
	##[[Network_Intelligence/Restcomm_Configuration#PhonerLite_direct_call_setting\|PhonerLite direct call setting]]		##[[Network_Intelligence/Restcomm_Configuration#PhonerLite_direct_call_setting\|PhonerLite direct call setting]]
	##[[Network_Intelligence/Restcomm_Configuration#ProSBC Local NAT Traversal setting\|ProSBC Local NAT Traversal setting]]		##[[Network_Intelligence/Restcomm_Configuration#ProSBC Local NAT Traversal setting\|ProSBC Local NAT Traversal setting]]
Line 30:		Line 40:
	==PhonerLite direct call setting==		==PhonerLite direct call setting==

	~~Below~~ are ~~sections~~ required to ~~setup~~ outbound direct call on PhonerLite,		The following section are required to set up the outbound direct call on PhonerLite,

	'''Server''' setting: All Proxy/Registrar and Domain/Realm are empty		'''Server''' setting: All Proxy/Registrar and Domain/Realm are empty
Line 48:		Line 58:
	[[File:PhonerLite_direct_call_Codecs_and_DTMF.png\|500px]]		[[File:PhonerLite_direct_call_Codecs_and_DTMF.png\|500px]]

	For ~~dialout~~, we can specify the called number as 1234@52.60.132.155 where 52.60.132.155 is the public Elastic IP used for voip interface in this ProSBC AWS.		For dial out, we can specify the called number as 1234@52.60.132.155 where 52.60.132.155 is the public Elastic IP used for voip interface in this ProSBC AWS.

	=ProSBC Configuration=		=ProSBC Configuration=

Serdar Civici at 07:49, 25 January 2021

2021-01-25T07:49:38Z

Serdar Civici at 07:48, 25 January 2021

2021-01-25T07:48:40Z

Serdar Civici at 07:47, 25 January 2021

2021-01-25T07:47:32Z

William Wong: /* Network Diagram and Call Scenarios */

2019-03-21T08:00:59Z