使用 SMS 网关进行移动开发 - 缺少什么？
我有一个基于移动服务的项目的想法。我在线阅读了一些内容，包括以下教程： SMS 教程 并发现它非常有帮助，但是我有一些基本问题，请耐心等待。
我经营一家小型（如我和朋友）公司，希望设置一种情况，让人们可以发短信并接收回复信息，或者在我的网站上设置让他们收到短信让他们知道是时候做点什么了，或者“技术支持”如果愿意的话可以给他们发短信，等等。
所以根据我收集的信息，我可以使用 Kannel 作为我的“短信网关”，与我可以购买的 GSM 调制解调器交互。对于这个调制解调器，我可以购买短信套餐 SIM 卡。然后我可以设置 Kannel 将我的 GSM 调制解调器用作虚拟 SMSC。因此，用户可以通过短信发送 SIM 卡的电话号码，该号码将发送到调制解调器并由 Kannel 进行解释。我的应用程序只需与 Kannel 交互。将来，如果我决定需要更多短信吞吐量并升级到真正的 SMSC，我的应用程序不需要更改。
我有什么遗漏/误解吗？
谢谢！
I have an idea for a mobile service based project. I have read some stuff online, including the following tutorial: SMS Tutorial and find it to be pretty helpful but I have some basic questions so please bear with me.
I run a small (as in me and a friend) company and want to setup a situation where people can text a number and receive information back, or setup on my website that they receive text messages letting them know its time to do something, or "tech support" can text them if they wish, etc.
So from what I've gathered, I can use Kannel as my "SMS gateway" interacting with a GSM Modem that I can purchase. For this modem I can buy a texting plan SIM. I can then setup Kannel to use my GSM modem as a virtual smsc. So, users can text that SIMs phone number, which will go to the modem and be interpreted by Kannel. My application will only have to interact with Kannel. And in the future, if I decide I need more texting throuput and upgrade to a real SMSC my application does not need to change.
Is there anything I'm missing/misunderstanding?
Thanks!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
对于小公司来说，使用 Kannel 作为 SMS 网关是一个不错的选择。它确实带来了很多令人头痛的问题，因为你必须构建、配置、维护等等。你需要的所有服务，这就是每个人所说的“大量工作”。
您想要做的是将 GSM 调制解调器用作长代码（与短代码）用于短信。
我认为对于小型设备来说，这是一个可预期的解决方案，如果是针对本地区域，服务、延迟和可用性可能不那么重要。但如果这是需要可靠的东西，我会考虑获取一个短代码（或共享一个短代码）或只是一个没有长/短代码的 SMS 消息服务（参见下面的 Twilio）。
此外，如果您尝试推出自己的服务，则需要考虑 SMSC 的一些事项。如果您的 Kannel/GSM 调制解调器不支持该运营商，您将必须联系该运营商并连接到他们的 SMSC。连接到运营商的价格很高。这就是聚合商的吸引力，因为他们拥有所有运营商连接并支付这些费用。
当您从 Kannel 过渡到网关服务提供商时，这是另一个令人头痛的问题，因为您需要从头开始并使用任何服务提供商 API 并完全替换 Kannel/GSM。您的工作流程可能相同，但发送和接收消息的方式却有很大不同。大多数（如果不是全部）聚合商将提供自己版本的 SDK/API/服务，您需要遵守该版本才能使用他们的服务。
如果在美国，您可能会考虑其他一些选择：
注意：这些只是少数服务，还有很多很多服务。
使用短代码也有一些注意事项，因为如果您所在的国家/地区需要自己的短代码，您将需要注册新的短代码。示例：您可以使用美国短代码为加拿大提供服务，您还需要加拿大短代码。如果您只进行少量流量，这可能会导致成本高昂。
Using Kannel as a SMS gateway is a good option for a small company. It does come with a lot of headaches as you have to build, configure, maintain, etc.. all of the services you need, This is what everyone is referring to as "A lot of work".
What you are looking to do is use the GSM modem as a Long Code (verses short Code) for text messaging.
I think this is an expectable solution for something small and where service, latency and availability might not be as important if it's for a local region. But if this is something that needs to be reliable I would think about getting a short code (or sharing a short code) or just a SMS Messaging service with No Long/Short Code (See Twilio Below).
Also if you're trying to rollout your own service there are some things to consider with the SMSC's. If your Kannel/GSM Modem doesn't support the Carrier, you would have to reach out to that Carrier and connect to thier SMSC. This is a hefty price to connect to a Carrier. This is way Aggregators are appealing as they Have all the Carrier connections and pay those fees.
As you transitioning from Kannel to a Gateway Service Provider, that's another headache as you would need to start from scratch and use whatever the service provider API is and replace the Kannel/GSM altogether. Your workflow might be the same but how you send and receive messages with differ greatly. Most (if not all) Aggregators will offer there own version of a SDK/API/Service that you would need to comply with to use their service.
If it's in the US there are some other options you might consider:
Note: These are just a few services as there are many, many more
There are also some caveats with having a Short Code as you will need to register a new Short Code if the country you are services needs it's own Short Code. Example: you can use your US Short Code to service Canada, You would also need a Canadian Short Code as well. This can get costly if your only doing small amounts of traffic.
我想你已经有了基本的考虑。约翰是对的，使用短信网关是更好的主意，您将获得更好的可靠性和吞吐量。而且你可以获得缓慢的价格。
I think you have got basic considerations. John is right, and using a sms gateway is better idea, you will get better reliability and thoughput. And you could get slow prices.