如何从一个或几个服务器电话号码“多路复用”多个短信会话(How to “multiplex” multiple sms conversations from one or a few server phone numbers)

 所以这是用例：我们希望将聊天从我们的移动应用程序桥接到短信，这样他们就不必使用自定义信使应用程序。 服务器端，使用像Twilio这样的服务，您是否必须为每个会话/对话提供单独的电话号码？ 如果是这样，那将是非常昂贵的。 
 
 在一个简单的用例中，一个服务器电话号码可以处理来自多个客户端和对话的所有传入短信。 它可以根据客户端发送者的电话号码，区分短信属于哪个对话，并将相应的回复过滤回每个对话中参与者的电话号码。 这将允许通过单个服务器电话号码管理多个对话。 
 
 但是，在增强的用例中，如果客户端同时在多个对话中，除非我们能够以某种方式在回复文本本身中嵌入信息，否则没有简单的方法来确定客户端的回复来自服务器的对话。 。 
 
 这只是一个限制，还是有办法允许这个增强的用例？ 
 
 Twilio或SMS技术中有什么东西，或者我正在考虑的方式，这样可以让对话信息以傻瓜式的方式发回（例如，不要让用户手动输入对话ID）允许从同一客户端用户多路复用多个并发短信会话？ 

So here's the use case: we want to bridge chats from our mobile application to sms, so that they don't have to use a custom messenger app. Server-side, using a service like Twilio, would you have to provision separate phone numbers for every session/conversation? If so, that would be prohibitively expensive.
 
In a simple use case, one server phone number can handle all the incoming sms messages from multiple clients and conversations. It can, based on the client sender's phone number, discriminate what conversation the sms belongs to and send appropriate replies back filtered to the phone numbers of the participants in each conversation. This would allow multiple conversations to be managed by a single server phone number.
 
However, in an enhanced use case, if the client is in more than one conversation at the same time, there is no easy way to determine which conversation the client's reply was for from the server unless we can somehow embed info in the reply text itself.
 
Is that just a limitation or is there a way to allow for this enhanced use case?
 
Is there something in Twilio or in SMS technology, or in the way that I'm thinking about this that would allow that conversation info to be sent back in a fool-proof way (not making the user manually type the conversation id for instance) to allow multiplexing multiple concurrent sms conversations from the same client user?

原文：https://stackoverflow.com/questions/35612448