SMS 网关 - 有关 SMS 网站通信的常见问题
我问这个问题时对短信网关及其相关技术知之甚少/一无所知，所以请耐心等待。
我想要的是这样的：
- 用户向给定号码发送短信
- 这条短信被转发到我的网站进行处理
因此，从我所做的（少量）研究来看，看起来我需要为短信网关付费。
有什么建议吗？已知的限制？
我的网站将是一个在 IIS7 上运行的 ASP.NET MVC 应用程序。
我不需要从我的网站发送短信，只需接收它们。
我不知道这是否可能 - SMS 网关可以通过 HTTP 向网站发送消息吗？那么图像呢？我这边需要什么类型的网络基础设施？
在这个阶段，我真正关心的是消息的正文以及发送者。但当然，我想让自己面向未来，所以希望提前了解其中的陷阱。
一旦网站通过 HTTP 接收到 SMS，我需要将其保存到 SQL Server 2008 数据库中。或者 SMS 网关可以保留到它自己的数据库吗？
有人可以提供任何指导吗？以前有人做过这种事吗？
感谢您的帮助。
I'm asking this question with little/no knowledge of SMS gateways and it's relevant technologies, so bear with me.
What i want is this:
- User Sends an SMS to a given number
- This SMS is forwarded to my website for processing
So from the (little) research i've done, it looks like i need to pay for an SMS Gateway.
Any recommendations? Known limitations?
My website will be an ASP.NET MVC application running over IIS7.
I dont need to SEND sms's from my website, only receive them.
I have no idea if this is even possible - can an SMS gateway send messages to a website over HTTP? What about images? What type of network infrastructure is required on my end?
At this stage, all i really care about is the body of the message, and who sent it. But of course i want to future-proof myself so looking to know the pitfalls up front.
Once the website receives the SMS over HTTP, i need to persist this to a SQL Server 2008 database. Or can the SMS gateway persist to it's own DB?
Can anyone provide any guidance? Anyone done this type of thing before?
Appreciate the help.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
您需要一个 SMS 网关，它可以为您分配一个号码并将该号码转发到 Web 服务或您根据其标准发布的其他资源。
在澳大利亚，一些提供商这样做（大多数提供商将其捆绑为“双向”短信，因此您也可以发送，即使您已经说过不需要它）。
是两个示例。我以前使用过 SMS Global，而且非常容易上手。
您需要一个可以发布服务的 Web 服务器（根据网关的不同，要求也有所不同），但通常是 REST 或 SOAP 或带有参数的普通 GET。当网关收到您号码上的短信时，它会点击配置的 URL，将数据传递给它。
然后，从网关接收到命中的服务将解释这些参数，并且您可以根据需要将其保存到数据库中。
根据您收到的短信数量，您可能需要将其外包，但这与任何网络存在的容量规划相同。负载只是每条消息对服务器上资源的 HTTP 请求。
You need an SMS gateway that can assign you a number and forwards that number onto a web service, or other resource you publish according to their standard.
In Australia a few providers do this (most of them bundle it as "Two Way" SMS so you get Send as well, even though you've said you don't need it).
Are two examples. I've used SMS Global before and it's pretty easy to get going.
You'll need a web server that can publish a service (depending on the gateway the requirements differ), but generally its REST or SOAP or plain GET with parameters. When the gateway receives an SMS on your number it hits the configured URL passing the data to it.
Your service that receives the hit from the gateway will then interpret the parameters, and you can persist that to your database as you wish.
Depending on how many SMS's you're getting you may need to farm it out, but its the same capacity planning that goes into any web presence. The load is just an HTTP request to a resource on your server per message.