We are a CLEC and have SS7 trunks. From my limited understanding, SMS rides over ISUP, so in theory we would simply have an entry in an SMS DB that says all our SMS messages should be sent to a particular point code correct? Do I have this at all right, and if so, how do I enter this SMS DB point code information? Thanks! -Eric
On 04/26/2011 10:50 AM, Eric Hiller wrote:
We are a CLEC and have SS7 trunks. From my limited understanding, SMS rides over ISUP, so in theory we would simply have an entry in an SMS DB that says all our SMS messages should be sent to a particular point code correct? Do I have this at all right, and if so, how do I enter this SMS DB point code information?
I've been thinking this myself for some time, and there's a place to input this information in NPAC LTI. I assume you'd also need an SMSC to receive the SMS data, and you'd have to get all the wireless carriers to open up your point code in all their STPs. I presume there's a way to get that information broadcast to all of them. -Paul
I don't believe it's that "simple". The main issue is that SMS messages were originally hacked into the GSM standard, not a SS7 protocol. While SMS can be carried over SS7, most wireless networks, at least traditionally, did not follow standard SS7 and PSTN concepts in their implementation of SMS, so they are basically separate systems not really connected to the PSTN. As I understand it, most of the interconnections between different networks that carry SMS are done through gateway providers or private peering. Verisign was the most popular and/or well known for some time: http://www.verisign.com/static/005168.pdf This is also part of why it took so long to start having inter-carrier MMS. Of course the other problem is at "layer 8", so using a well-established gateway is the best way to ensure you have connectivity to all the players without building your own legal team. Nowadays, many of the SMS gateway companies offer all types of connectivity including SS7 or SIGTRAN, SOAP, SMTP, and a bunch of proprietary protocols. There are also some good open source projects for running your own SMSC: http://www.kannel.org/news.shtml -Scott -----Original Message----- From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Paul Timmins Sent: Tuesday, April 26, 2011 11:01 AM To: Eric Hiller Cc: voiceops at voiceops.org Subject: Re: [VoiceOps] SMS enabled DIDs On 04/26/2011 10:50 AM, Eric Hiller wrote:
We are a CLEC and have SS7 trunks. From my limited understanding, SMS rides over ISUP, so in theory we would simply have an entry in an SMS DB that says all our SMS messages should be sent to a particular point code correct? Do I have this at all right, and if so, how do I enter this SMS DB point code information?
I've been thinking this myself for some time, and there's a place to input this information in NPAC LTI. I assume you'd also need an SMSC to receive the SMS data, and you'd have to get all the wireless carriers to open up your point code in all their STPs. I presume there's a way to get that information broadcast to all of them. -Paul _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
So any idea what Syniverse or Verisign charges to act as your gateway provider? High monthly commits? -Eric On Tue, April 26, 2011 9:19 pm, Scott Berkman wrote:
I don't believe it's that "simple".
The main issue is that SMS messages were originally hacked into the GSM standard, not a SS7 protocol. While SMS can be carried over SS7, most wireless networks, at least traditionally, did not follow standard SS7 and PSTN concepts in their implementation of SMS, so they are basically separate systems not really connected to the PSTN.
As I understand it, most of the interconnections between different networks that carry SMS are done through gateway providers or private peering. Verisign was the most popular and/or well known for some time:
http://www.verisign.com/static/005168.pdf
This is also part of why it took so long to start having inter-carrier MMS.
Of course the other problem is at "layer 8", so using a well-established gateway is the best way to ensure you have connectivity to all the players without building your own legal team.
Nowadays, many of the SMS gateway companies offer all types of connectivity including SS7 or SIGTRAN, SOAP, SMTP, and a bunch of proprietary protocols.
There are also some good open source projects for running your own SMSC:
http://www.kannel.org/news.shtml
-Scott
-----Original Message----- From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Paul Timmins Sent: Tuesday, April 26, 2011 11:01 AM To: Eric Hiller Cc: voiceops at voiceops.org Subject: Re: [VoiceOps] SMS enabled DIDs
On 04/26/2011 10:50 AM, Eric Hiller wrote:
We are a CLEC and have SS7 trunks. From my limited understanding, SMS rides over ISUP, so in theory we would simply have an entry in an SMS DB that says all our SMS messages should be sent to a particular point code correct? Do I have this at all right, and if so, how do I enter this SMS DB point code information?
I've been thinking this myself for some time, and there's a place to input this information in NPAC LTI. I assume you'd also need an SMSC to receive the SMS data, and you'd have to get all the wireless carriers to open up your point code in all their STPs. I presume there's a way to get that information broadcast to all of them.
-Paul _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
Syniverse bought Verisign Messaging (Metcalf) messaging back in 2009. The other major player is Sybase365 in the US. I know Sybase has a minimum now, but not sure what it is. I haven't heard if Syniverse has a minimum. There are other aggregators as well. Vail/Level3 and Iris. You'd have to have your own SPID and use SMPP to connect into the aggregator. In other parts of the world, Mack, Belgacom, IC3S, GMSU are also major aggregators. -Jared On Wed, Apr 27, 2011 at 9:59 PM, Eric Hiller <clec at cygnustel.com> wrote:
So any idea what Syniverse or Verisign charges to act as your gateway provider? High monthly commits?
-Eric
On Tue, April 26, 2011 9:19 pm, Scott Berkman wrote:
I don't believe it's that "simple".
The main issue is that SMS messages were originally hacked into the GSM standard, not a SS7 protocol. While SMS can be carried over SS7, most wireless networks, at least traditionally, did not follow standard SS7 and PSTN concepts in their implementation of SMS, so they are basically separate systems not really connected to the PSTN.
As I understand it, most of the interconnections between different networks that carry SMS are done through gateway providers or private peering. Verisign was the most popular and/or well known for some time:
http://www.verisign.com/static/005168.pdf
This is also part of why it took so long to start having inter-carrier MMS.
Of course the other problem is at "layer 8", so using a well-established gateway is the best way to ensure you have connectivity to all the players without building your own legal team.
Nowadays, many of the SMS gateway companies offer all types of connectivity including SS7 or SIGTRAN, SOAP, SMTP, and a bunch of proprietary protocols.
There are also some good open source projects for running your own SMSC:
http://www.kannel.org/news.shtml
-Scott
-----Original Message----- From: voiceops-bounces at voiceops.org [mailto: voiceops-bounces at voiceops.org] On Behalf Of Paul Timmins Sent: Tuesday, April 26, 2011 11:01 AM To: Eric Hiller Cc: voiceops at voiceops.org Subject: Re: [VoiceOps] SMS enabled DIDs
On 04/26/2011 10:50 AM, Eric Hiller wrote:
We are a CLEC and have SS7 trunks. From my limited understanding, SMS rides over ISUP, so in theory we would simply have an entry in an SMS DB that says all our SMS messages should be sent to a particular point code correct? Do I have this at all right, and if so, how do I enter this SMS DB point code information?
I've been thinking this myself for some time, and there's a place to input this information in NPAC LTI. I assume you'd also need an SMSC to receive the SMS data, and you'd have to get all the wireless carriers to open up your point code in all their STPs. I presume there's a way to get that information broadcast to all of them.
-Paul _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
On Wed, Apr 27, 2011 at 6:59 PM, Eric Hiller <clec at cygnustel.com> wrote:
So any idea what Syniverse or Verisign charges to act as your gateway provider? High monthly commits?
The monthly minimums are extremely negotiable, especially with a well-reasoned argument. It's a typical enterprise sales process - start high, adjust, and use whatever ammo you have (from the customer or from corporate) to get a deal done. You won't get in with $100/mo but it doesn't need to be $2500. And the process is convoluted enough that if you aren't spending a few hundred $$ a month, it's too much work for them to do the interop with you/your DID provider anyway. At that volume you'd be better off getting one or more upstreams to work with them, or buying from someone who already presents their own SMS access. Troy
We are a facilities based CLEC, so we are the "DID provider" and have our own SPID. Does this change anything? On Thu, April 28, 2011 1:31 pm, Troy Davis wrote:
On Wed, Apr 27, 2011 at 6:59 PM, Eric Hiller <clec at cygnustel.com> wrote:
So any idea what Syniverse or Verisign charges to act as your gateway provider? High monthly commits?
The monthly minimums are extremely negotiable, especially with a well-reasoned argument. It's a typical enterprise sales process - start high, adjust, and use whatever ammo you have (from the customer or from corporate) to get a deal done.
You won't get in with $100/mo but it doesn't need to be $2500. And the process is convoluted enough that if you aren't spending a few hundred $$ a month, it's too much work for them to do the interop with you/your DID provider anyway. At that volume you'd be better off getting one or more upstreams to work with them, or buying from someone who already presents their own SMS access.
Troy
Eric, One of the free services that NetNumber provides is "Type one" override data to the messaging industry. This provides us the ability to SMS enable landlines in the same manner as routing messages based on which MVNO has struck a messaging deal with the different aggregators. Today we distribute MVNO records to many of the aggregators and wireless operators in North America. Just to be clear, we don't provide any SMS GW access, but we provide the Messaging folks the knowledge that a number can receive a TXT versus having the aggregator drop it in the bit bucket. We do this by establishing 1 or more pseudo-SPID(s) and then let you publish numbers under them. You can work with any aggregator to accomplish the same, but they just send them to NetNumber to publish anyway. Hope this helps de-mystifies the process a bit to the list. Contact me if you would like a white paper that details this a bit more. Thanks, Rob Mercer - +1 636 544 4800 Sr. Director On Apr 28, 2011, at 4:25 PM, "Eric Hiller" <clec at cygnustel.com> wrote:
We are a facilities based CLEC, so we are the "DID provider" and have our own SPID. Does this change anything?
On Thu, April 28, 2011 1:31 pm, Troy Davis wrote:
On Wed, Apr 27, 2011 at 6:59 PM, Eric Hiller <clec at cygnustel.com> wrote:
So any idea what Syniverse or Verisign charges to act as your gateway provider? High monthly commits?
The monthly minimums are extremely negotiable, especially with a well-reasoned argument. It's a typical enterprise sales process - start high, adjust, and use whatever ammo you have (from the customer or from corporate) to get a deal done.
You won't get in with $100/mo but it doesn't need to be $2500. And the process is convoluted enough that if you aren't spending a few hundred $$ a month, it's too much work for them to do the interop with you/your DID provider anyway. At that volume you'd be better off getting one or more upstreams to work with them, or buying from someone who already presents their own SMS access.
Troy
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
On Thu, Apr 28, 2011 at 2:25 PM, Eric Hiller <clec at cygnustel.com> wrote:
We are a facilities based CLEC, so we are the "DID provider" and have our own SPID. Does this change anything?
Probably, but I have no idea what. Their sales team is responsive, say hi on http://www.syniverse.com/business-solutions/solutions/SMS-Interworking-Gatew... Troy
Eric, Syniverse charges two MRC componants 1) VPN charges 2) Monthly minimium We are bound by NDA , so I can not disclose their pricing , but If you are interested in sharing a cost of monthly minimum we are happy to work with you. Please contact me offline. thanks, Jay. On Wed, Apr 27, 2011 at 9:59 PM, Eric Hiller <clec at cygnustel.com> wrote:
So any idea what Syniverse or Verisign charges to act as your gateway provider? High monthly commits?
-Eric
On Tue, April 26, 2011 9:19 pm, Scott Berkman wrote:
I don't believe it's that "simple".
The main issue is that SMS messages were originally hacked into the GSM standard, not a SS7 protocol. While SMS can be carried over SS7, most wireless networks, at least traditionally, did not follow standard SS7 and PSTN concepts in their implementation of SMS, so they are basically separate systems not really connected to the PSTN.
As I understand it, most of the interconnections between different networks that carry SMS are done through gateway providers or private peering. Verisign was the most popular and/or well known for some time:
http://www.verisign.com/static/005168.pdf
This is also part of why it took so long to start having inter-carrier MMS.
Of course the other problem is at "layer 8", so using a well-established gateway is the best way to ensure you have connectivity to all the players without building your own legal team.
Nowadays, many of the SMS gateway companies offer all types of connectivity including SS7 or SIGTRAN, SOAP, SMTP, and a bunch of proprietary protocols.
There are also some good open source projects for running your own SMSC:
http://www.kannel.org/news.shtml
-Scott
-----Original Message----- From: voiceops-bounces at voiceops.org [mailto: voiceops-bounces at voiceops.org] On Behalf Of Paul Timmins Sent: Tuesday, April 26, 2011 11:01 AM To: Eric Hiller Cc: voiceops at voiceops.org Subject: Re: [VoiceOps] SMS enabled DIDs
On 04/26/2011 10:50 AM, Eric Hiller wrote:
We are a CLEC and have SS7 trunks. From my limited understanding, SMS rides over ISUP, so in theory we would simply have an entry in an SMS DB that says all our SMS messages should be sent to a particular point code correct? Do I have this at all right, and if so, how do I enter this SMS DB point code information?
I've been thinking this myself for some time, and there's a place to input this information in NPAC LTI. I assume you'd also need an SMSC to receive the SMS data, and you'd have to get all the wireless carriers to open up your point code in all their STPs. I presume there's a way to get that information broadcast to all of them.
-Paul _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
participants (7)
-
clec＠cygnustel.com -
clecny＠gmail.com -
jared＠compuwizz.net -
paul＠timmins.net -
rmercer＠netnumber.com -
scott＠sberkman.net -
troy＠yort.com