Enabling Messages: Difference between revisions

From Integrics Wiki
Jump to navigation Jump to search
Content deleted Content added
Vlasis (talk | contribs)
No edit summary
No edit summary
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:

Revision as of 03:55, 14 May 2019

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 in versions 3.14 and older, except as an add-on from Voisonics.

The custom script:

  • Must be customised for each provider to match the protocol they use
  • Is located at: /usr/local/sbin/enswitch_message_out
  • Must be on the same machines as enswitch_sipd.

Here is an example enswitch_message_out script to send requests via HTTP.

Besides customising this script, you need to:

  • In System -> Configuration set "Enable text messages" (or "Enable messaging" in 3.13 and earlier) 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.