| Using Syniverse |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through January 23, 2007 ⬆ |
◄ ► |
| Author | Message | |||
| Marcos Nowosad New member Username: Mnowosad Post Number: 5 Registered: 08-2006 |
I need to configure the NowSMS gateway to work with Syniverse, for some type of SMS services we will provide. I already have another SMSC configured (mBlox) with NowSMS gateway to provide a different set of SMS services. So my questions are: 1) Is there any source material about how to make NowSMS work with Syniverse? I searched for it in the Discussion Board and did not find any thread mentioning Syniverse (as opposed to mBlox, which is mentioned in a dozen of threads, with many useful tips). 2) If I have two SMSC configured in NowSMS (in the case, Syniverse and mBlox), how I can define to which SMSC a given SMS message will be sent, using the HTPP protocol? For instance, today if I send a HTPP request like "http://localhost:8800/?PhoneNumber=4085555555&Text=Hello", NowSMS sends the corresponding SMPP message to the mBlox SMSC. With two configured SMSC, how does it know to which to send? 3) Similar question for 2-Way commands: how can I define commands that are only executed if they come from mBlox SMSC and others that only execute if they come from Syniverse? Thanks, Marcos | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6512 Registered: 10-2002 |
Hi Marcos, 1.) I can't recall anyone asking about Syniverse for quite some time. I believe used to be known as TSI. And I do remember a customer that was using them for SMS delivery in the US. The only reason I remember this was because I recall that this customer was doing WAP Push to GSM users in the US, and they had to use DCS=4 to reach AT&T Wireless (this was before Cingular and ATTWS merged). Anyway ... usually things are pretty straight-forward for SMPP connections ... until you start talking about premium rate SMS. mBlox has defined several extended SMPP parameters for premium rate SMS parameters, and that's what you'll find discussed on quite a few threads here. I don't know if Syniverse has similar extensions, or if they use a different approach. I'd be interested in seeing any information that you have on how they support premium rate SMS. (If it cannot be posted here, feel free to e-mail to nowsms@now.co.uk with "Attention: Bryce" in the subject line.) 2.) There's a good explanation here: http://support.nowsms.com/discus/messages/1/11908.html 3.) For 2-way commands, we don't make a distinction based upon the receiving SMSC. But we can make a distinction based upon the phone number (or short code) that is specified as the recipient. You can put one or more numbers in the "Recieve Phone Number(s)" field, and the 2-way command will only be executed if the recipient matches. If the receive phone number logic is not sufficient for your needs, then you can also have the SMSC route name included in the 2-way command by specifying the @@SMSCROUTE@@ variable in your URL. (See http://support.nowsms.com/discus/messages/1/15288.html.) In this case, the same 2-way command is executed, but this parameter allows your script to know from which SMSC this message was received. -bn | |||
