[VoiceOps] SMS enabled DIDs

[Jared Geiger]

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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20110428/9e8415b9/attachment.html>