Enabling Messages - Revision history

Dcunningham at 03:23, 3 August 2022

2022-08-03T03:23:38Z

← Older revision		Revision as of 03:23, 3 August 2022
Line 8:		Line 8:
	* Any custom-written API which then uses Integrics::Enswitch::Texts or the messages/text/send JSON API method.		* Any custom-written API which then uses Integrics::Enswitch::Texts or the messages/text/send JSON API method.

	The custom script:		The outbound custom script:
	* Must be customised for each provider to match the protocol they use		* Must be customised for each provider to match the protocol they use
	* Is located at: <code>/usr/local/sbin/enswitch_message_out</code>		* Is located at: <code>/usr/local/sbin/enswitch_message_out</code>
	* Must be on the same machines as enswitch_sipd.		* Must be on the same machines as enswitch_sipd.
			* Should be careful to properly escape characters in the message.

	Here is an [[SMS_Send_Script_Example\|example]] enswitch_message_out script to send requests via HTTP.		Here is an [[SMS_Send_Script_Example\|example]] enswitch_message_out script to send requests via HTTP.

Dcunningham at 03:23, 3 August 2022

2022-08-03T03:23:02Z

← Older revision		Revision as of 03:23, 3 August 2022
Line 3:		Line 3:
	* A custom script for external destinations.		* A custom script for external destinations.

	Inbound SMS to the Enswitch system is not supported in versions 3.14 and older, except as an add-on from Voisonics.		Inbound SMS to the Enswitch system is not supported in versions 3.14 and older, except as an add-on from Voisonics. In 3.15 and later inbound SMS messages can be send to the web API methods at:
			* /api/bandwidth/
			* /api/twilio/
			* Any custom-written API which then uses Integrics::Enswitch::Texts or the messages/text/send JSON API method.

	The custom script:		The custom script:

Dcunningham at 01:34, 3 June 2022

2022-06-03T01:34:11Z

← Older revision		Revision as of 01:34, 3 June 2022
Line 15:		Line 15:
	* In System -> Configuration set "Enable text messages" (or "Enable messaging" in 3.13 and earlier) to Yes.		* In System -> Configuration set "Enable text messages" (or "Enable messaging" in 3.13 and earlier) to Yes.
	* Restart enswitch_sipd.		* Restart enswitch_sipd.
			* In System -> Roles set "Actions » Send a message" to "Yes" for desired roles.

	In System -> ~~Roles~~ ~~set~~ ~~"Actions~~ » ~~Send~~ a ~~message~~" to "~~Yes~~" ~~for desired roles~~.		* In System -> Routes create routes with the "Media type" set to "Message".
	In System -> ~~Routes~~ ~~create~~ ~~routes~~ ~~with~~ the ~~"Media~~ ~~type"~~ ~~set~~ to "~~Message~~".		* In System -> Peers for each peer which is used by a message route, edit the outbound costs and define the "Cost to send a message".
	In System -> Peers for each peer which is used by a message route, edit the outbound costs and define the "Cost to send a message".
	* In each Rate plan set:		* In each Rate plan set:
	** Features -> "Send SMS messages" to "Allow".		** Features -> "Send SMS messages" to "Allow".

Dcunningham at 01:33, 3 June 2022

2022-06-03T01:33:58Z

← Older revision		Revision as of 01:33, 3 June 2022
Line 15:		Line 15:
	* In System -> Configuration set "Enable text messages" (or "Enable messaging" in 3.13 and earlier) to Yes.		* In System -> Configuration set "Enable text messages" (or "Enable messaging" in 3.13 and earlier) to Yes.
	* Restart enswitch_sipd.		* Restart enswitch_sipd.

	* In System -> Roles set "Actions » Send a message" to Yes for desired roles.		In System -> Roles set "Actions » Send a message" to "Yes" for desired roles.
⚫	* In each ~~Peer~~ used ~~for~~ ~~messaging~~, in the outbound costs define the "Cost to send a message".
	* In ~~each~~ ~~Route~~ ~~used~~ ~~for~~ ~~messaging,~~ ~~define~~ the "~~Peer~~ ~~for~~ ~~messages~~".		In System -> Routes create routes with the "Media type" set to "Message".
		⚫	In System -> Peers for each peer which is used by a message route, edit the outbound costs and define the "Cost to send a message".
	* In each Rate plan set:		* In each Rate plan set:
	** Features -> "Send SMS messages" to "Allow".		** Features -> "Send SMS messages" to "Allow".

Dcunningham at 20:06, 16 February 2022

2022-02-16T20:06:10Z

← Older revision		Revision as of 20:06, 16 February 2022
Line 16:		Line 16:
	* Restart enswitch_sipd.		* Restart enswitch_sipd.
	* In System -> Roles set "Actions » Send a message" to Yes for desired roles.		* In System -> Roles set "Actions » Send a message" to Yes for desired roles.
	* In each Peer's outbound costs define the "Cost to send a message".		* In each Peer used for messaging, in the outbound costs define the "Cost to send a message".
	* In each Route define the "Peer for messages".		* In each Route used for messaging, define the "Peer for messages".
	* In each Rate plan set:		* In each Rate plan set:
		⚫	** Features -> "Send SMS messages" to "Allow".
	** ~~Relevant~~ fields in "Default markups" and "Included in rate plan".		** Optionally, set relevant fields in "Default markups" and "Included in rate plan".
⚫	** Features -> "Send SMS messages".
	** Outbound call cost exceptions -> "Cost to send message".		** Optionally, set "Outbound call cost exceptions" -> "Cost to send message".
	We recommend your configuration is thoroughly tested prior to making it available to users.		We recommend your configuration is thoroughly tested prior to making it available to users.

Dcunningham at 03:55, 14 May 2019

2019-05-14T03:55:23Z

← Older revision		Revision as of 03:55, 14 May 2019
Line 3:		Line 3:
	* A custom script for external destinations.		* A custom script for external destinations.

	Inbound SMS to the Enswitch system is not supported in versions 3.14 and older.		Inbound SMS to the Enswitch system is not supported in versions 3.14 and older, except as an add-on from Voisonics.

	The custom script:		The custom script:

Vlasis at 08:54, 2 November 2018

2018-11-02T08:54:00Z

← Older revision		Revision as of 08:54, 2 November 2018
Line 3:		Line 3:
	* A custom script for external destinations.		* A custom script for external destinations.

	Inbound SMS to the Enswitch system is not supported.		Inbound SMS to the Enswitch system is not supported in versions 3.14 and older.

	The custom script:		The custom script:

Dcunningham at 01:14, 4 October 2018

2018-10-04T01:14:03Z

← Older revision		Revision as of 01:14, 4 October 2018
Line 13:		Line 13:

	Besides customising this script, you need to:		Besides customising this script, you need to:
	* In System -> Configuration set "Enable messaging" to Yes.		* In System -> Configuration set "Enable text messages" (or "Enable messaging" in 3.13 and earlier) to Yes.
	* Restart enswitch_sipd.		* Restart enswitch_sipd.
	* In System -> Roles set "Actions » Send a message" to Yes for desired roles.		* In System -> Roles set "Actions » Send a message" to Yes for desired roles.

Cloos: fix typo

2016-02-16T15:16:23Z

fix typo

← Older revision		Revision as of 15:16, 16 February 2016
Line 6:		Line 6:

	The custom script:		The custom script:
	* Must be customised for each provider to match the protocol they ~~yse~~		* Must be customised for each provider to match the protocol they use
	* Is located at: <code>/usr/local/sbin/enswitch_message_out</code>		* Is located at: <code>/usr/local/sbin/enswitch_message_out</code>
	* Must be on the same machines as enswitch_sipd.		* Must be on the same machines as enswitch_sipd.

Dcunningham: Created page with "SMS messages are sent using: * SIP SIMPLE messages when the destination is a phone registered with Enswitch. * A custom script for external destinations. Inbound SMS to the E..."

2015-02-25T00:20:25Z

Created page with "SMS messages are sent using: * SIP SIMPLE messages when the destination is a phone registered with Enswitch. * A custom script for external destinations. Inbound SMS to the E..."

New page

SMS messages are sent using:
* SIP SIMPLE messages when the destination is a phone registered with Enswitch.
* A custom script for external destinations.

Inbound SMS to the Enswitch system is not supported.

The custom script:
* Must be customised for each provider to match the protocol they yse
* Is located at: <code>/usr/local/sbin/enswitch_message_out</code>
* Must be on the same machines as enswitch_sipd.

Here is an [[SMS_Send_Script_Example|example]] enswitch_message_out script to send requests via HTTP.

Besides customising this script, you need to:
* In System -> Configuration set "Enable messaging" to Yes.
* Restart enswitch_sipd.
* In System -> Roles set "Actions » Send a message" to Yes for desired roles.
* In each Peer's outbound costs define the "Cost to send a message".
* In each Route define the "Peer for messages".
* In each Rate plan set:
** Relevant fields in "Default markups" and "Included in rate plan".
** Features -> "Send SMS messages".
** Outbound call cost exceptions -> "Cost to send message".
We recommend your configuration is thoroughly tested prior to making it available to users.