SMS routing is generally handled by NetNumber's routing database (the name escapes me at the moment). NNIDs are the routing identifiers that they use - perhaps they meant NNID vs SSID?
Twilio has a "hosted messaging" service, I think, which is where they SMS-enable your number on their platform by changing the NNID to theirs while leaving the voice-routing intact. But that process lead to a lot of fraud across lots of carriers, so it's more restricted now. On Wed, Aug 17, 2022 at 6:36 PM Chris Aloi via VoiceOps < voiceops@voiceops.org> wrote: > We’ve done this, essentially porting away the SMS piece of a number. From > my experience, Bandwidth doesn’t allow “3rd party SMS enablement” of their > numbers, but INTQ does. I have a subset of my numbers with INTQ > specifically because of this. > > --- > Christopher Aloi > cta...@gmail.com > Sent from my iPhone > > On Aug 17, 2022, at 6:21 PM, Carlos Alvarez via VoiceOps < > voiceops@voiceops.org> wrote: > > > I mentioned this as an option, but the scheduling vendor didn't like the > idea. I'm guessing they don't have a billing method for this. Right now > it's on hold until he can get someone on his tech side involved. I was > more just curious about his concept that he thinks they have done a split > before. He may be completely mistaken. > > > > On Wed, Aug 17, 2022 at 3:15 PM Matthew Duggan <matthew.dug...@ciptex.com> > wrote: > >> Hi There, >> >> Twilio Gold Partner here. If they port the number to Twilio then using >> Twilio Programmable Voice they calls could be forwarded either via sip or >> pstn back to yourselves. >> >> They would have to pay Twilio the Egress cost. Feel free to message me >> offline for further assistance. >> >> Best Regards, >> >> *Matthew Duggan | Head of DevOps* >> *Mobile:* +447954163438 >> *Phone:* +44 (0)345 8800 808 >> *Email:* matthew.dug...@ciptex.com >> *Address:* Peter House, Oxford Street, Manchester M1 5AN, United Kingdom >> >> *www.ciptex.com* <http://ciptex.com/> >> [image: Logo] <http://ciptex.com/> [image: linkedin icon] >> <https://www.linkedin.com/company/ciptex/> [image: facebook icon] >> <https://www.facebook.com/ciptex> [image: twitter icon] >> <https://twitter.com/ciptex> [image: youtube icon] >> <https://www.youtube.com/channel/UC8puyBCaT5tomGyMcnlbmsA?reload=9> >> [image: Banner] <http://ciptex.com/> >> Legal: CAUTION - This message may contain privileged and confidential >> information intended only for the use of the addressee named above. If you >> are not the intended recipient of this message you are hereby notified that >> any use, dissemination, distribution or reproduction of this message is >> prohibited. If you have received this message in error please notify Ciptex >> Ltd. immediately. Any views expressed in this message are those of the >> individual sender and may not necessarily reflect the views of Ciptex Ltd. >> Ciptex Ltd - Registered Office: Chancery House, 30 St. Johns Road, Woking, >> Surrey, GU21 7SA. Company Number: 05671321 >> ------------------------------ >> *From:* VoiceOps <voiceops-boun...@voiceops.org> on behalf of Jorge >> Guntanis via VoiceOps <voiceops@voiceops.org> >> *Sent:* Wednesday, August 17, 2022 11:04:12 PM >> *To:* Carlos Alvarez <caalva...@gmail.com> >> *Cc:* VoiceOps <voiceops@voiceops.org> >> *Subject:* Re: [VoiceOps] Splitting voice and SMS >> >> >> CAUTION: This email may have originated from outside of the >> organization. Do not click links or open attachments unless you recognize >> the sender and know the content is safe. >> >> If they are already in twilio, they can create a SIP Trunk where you'd >> connect to to get the inbound calls. >> That way SMS stays at twilio and voice goes to you. >> >> I'm not aware of another way to do it cleanly. >> >> El mié, 17 de ago. de 2022 3:56 p. m., Carlos Alvarez via VoiceOps < >> voiceops@voiceops.org> escribió: >> >> We had an odd customer request, via a vendor trying to provide them with >> automated scheduling services via SMS. They are asking us to "release the >> SSID" to allow them to do SMS on the number, but we keep the voice. I'm >> unaware of this ability, and they even said that so far, most carriers >> won't even discuss it with them. >> >> Their service rides on the Twilio API, and I *think* Twilio uses >> Bandwidth. This number is currently with Bandwidth. So I don't know if >> that might make a difference. >> _______________________________________________ >> VoiceOps mailing list >> VoiceOps@voiceops.org >> https://puck.nether.net/mailman/listinfo/voiceops >> >> _______________________________________________ > VoiceOps mailing list > VoiceOps@voiceops.org > https://puck.nether.net/mailman/listinfo/voiceops > > _______________________________________________ > VoiceOps mailing list > VoiceOps@voiceops.org > https://puck.nether.net/mailman/listinfo/voiceops >
_______________________________________________ VoiceOps mailing list VoiceOps@voiceops.org https://puck.nether.net/mailman/listinfo/voiceops