什么是建设SMS服务器的最佳实践 [英] What are the best practices for building an SMS server

问题描述

我试图建立在我所能够通过GSM网络发送/接收短信的终端节点的系统。我现在需要建立一个服务器解决方案，将派遣作为一个网络服务器之间的网关握着我的业务逻辑和客户端（节点）短信。沟通是双向的。
我读过一些有关完整的SMS服务器解决方案（即充当GSM网关，可能），但他们最终被证明过于昂贵。
我想过手机连接到我的服务器（然后使用一些API），但它可能是我的服务器会去一个数据中心，由此我不能以这种方式将任何东西。
我不希望有太多的信息（如每天100 /双向）。我不打算有太多的客户太（小于100）。
在这里，我问了一个通用的系统解决方案（例如最佳做法）。

I am trying to build a system in which I have terminal nodes capable of sending/receiving SMS messages over a GSM network. I now need to construct a server solution which would send SMS messages acting as a gateway between a webserver holding my business logic and the clients (nodes). The communication is both ways. I've read something about complete SMS server solutions (that act as a GSM gateway, possibly), but they turn out to be too expensive. I've thought about attaching a mobile phone to my server (and then using some APIs), but it may be that my server will go to a data-center whereby I cannot attach anything in this way. I do not expect to have too many messages (like 100 per day/both ways). And I do not plan to have too many clients too (less than 100). Here I'm asking for a general system solution (e.g. best practice).

推荐答案

有建立这样一个SMS服务器三个基本选择：

There are three basic alternatives for building such an SMS server:

1）将移动电话或USB GSM棒到服务器，并使用这些用于SMS communicaton。限制是

1) Attach mobile phones or USB GSM sticks to the server and use these for SMS communicaton. Limitations are

• 量有限（但你​​100条短信/天应该是罚款）。

• Limited volumes (however your 100 SMS/day should be fine).

可能不可靠的，由于消费类硬件产品（如手机/棒固件没有专为全天候运行，则可能需要定期重置设备;大多数手机，以便需要电池功能，电池磨损）。

Possibly rather unreliable due to consumer hardware (e.g. phone/stick firmware is not built for 24x7 operation, you may need to reset devices regularly; most mobile phones require a battery in order to function, batteries wear out).

有可能在数据中心不placable，由于RF的规则和移动网络的覆盖范围。

Possibly not placable in data centers, due to RF rules and mobile network coverage.

手机号码计划仅限于SIM MSISDN。

Mobile number scheme limited to SIM MSISDN.

2）短信连接到网络运营商的短信网关。网络运营商使用这些正是为这样的场景：群发短信沟通。这些都是专有的，通常讲的更容易消化消息传输协议。限制：

2) Connect the SMS to a network operators SMS gateway. Network operators use these exactly for this scenario: bulk SMS communication. These are proprietary and usually talk an "easier" to digest message transport protocol. Limitations:

• 您绑定到网络运营商，连接明智和协议明智的。

• You are bound to the network operator, connection-wise and protocol-wise.

可能延误沟通，因为网关可以做存储和转发。

Possibly delays in communication since the gateway might do store-and-forward.

根据定价方案可能是有意义的只对高卷。

Depending on pricing scheme might make sense only for high volumes.

3）SMS服务器连接至移动运营商SS7网络，增加它作为一个网络元件。限制：

3) Connect the SMS server to the mobile operators SS7 network, adding it as a network element. Limitations:

• 复杂的实施。需要专用硬件（一个SS7接口卡）和驱动程序进行编程。

• Complex implementation. Requires dedicated hardware (an SS7 interface card) and drivers to be programmed.

需要与网络运营商不平凡的网络集成，包括广泛的测试。

Requires non-trivial network integration with network operator including extensive testing.

需要一个E1 / T1线路（或大，或SIGTRAN），用于连接这是一个典型的数据中心的事情，但在每一个数据中心不可用。

Requires an E1/T1 line (or bigger, or SIGTRAN) for connection this is typically a data center thing, but not available in every data center.

贵，定价方案和操作方面。

Expensive, in terms of pricing scheme and operation.

假设我理解你的要求，你的情况我会去选择1）和地方，它有良好的覆盖SMS服务器，即不一定要在数据中心。出售它作为一个头端对服务器的基础设施。如果把它在数据中心是必须的，然后去选择2），并检查了您的移动网络运营商的短信批发产品。

Assuming I understand your requirements, for your case I would go for option 1) and place the SMS server where it has good coverage, i.e. not necessarily in the data center. Sell it as a head-end for the server infrastructure. If putting it in the data center is a must, then go to option 2) and check out your mobile network operators SMS wholesale offerings.

这篇关于什么是建设SMS服务器的最佳实践的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！