| Deploying SMTP to SMS solution |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through July 28, 2006 ⬆ |
◄ ► |
| Author | Message | |||
| Kube New member Username: Kube Post Number: 1 Registered: 04-2006 |
Hi, We are going to use mainly the SMTP to SMS functionality of NowSMS. Since the SMTP protocol won’t recognize recipients that are not defined in the MMSC users section or that are not valid SMS or MMS recipients , it will be hard for us to manage the users( having more than 30000 users), we know that we can import users into the system using the mmscusers.exe but our list of users changes often, so we were wondering if there is some way to integrate the system with an existing Users Directory (LDAP database) or if there is someway to automate the creation and deletion of users process. Kube | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5858 Registered: 10-2002 |
Hi Kube, I can think of two possible solutions. Solution #1: This solution does not require any users to be defined to the "MMSC Users" list in NowSMS. It does, however, require that another SMTP server be setup to relay SMTP message to the NowSMS server. E-mail messages from the open internet need to first be accepted by this other SMTP server, with this other SMTP server then relaying the messages to NowSMS. In this configuration, you will make this other SMTP server look like an inbound MM4 connection to the NowSMS MMSC. (MM4 uses the SMTP protocol.) On the "MMSC VASP" page of the NowSMS configuration dialog, define the IP address of the SMTP server as the "Account Name". Leave the "Password" field blank. Make sure "Accept Connections via" has "MM4" checked. All of the default values for this configuration dialog can be used. At this point, NowSMS will now accept SMTP messages from this IP address addressed to *any* phone number. Of course, it is likely that you do not want to allow messages to any phone number, you will want to restrict this capability only to users in your database. You can implement an accounting callback to perform this restriction. Each time NowSMS receives an SMTP message from the other SMTP server's IP address, it can issue an "MMSEMail Pre-Auth" callback, as defined in http://www.nowsms.com/support/bulletins/tb-nowsms-001.htm. You configure an HTTP script running on another web server, and each SMTP message will cause that script to be executed with the "MMSEMail Pre-Auth" parameters. You can determine if you want to accept a message for the specified recipient phone number ... if you want to accept it, just return a usual HTTP OK response. If you want to reject it, return an HTTP OK response but include the text "PreAuth=Deny" in the response, and the NowSMS server will reject the recipient. Solution #2: This solution does require users to be defined in the "MMSC Users" list in NowSMS. You can initially import users using the MMSUSER.EXE utility, as you described. To keep things in sync, you can issue HTTP requests to add and delete users. These HTTP requests for adding and deleting users are described in the following document: http://www.nowsms.com/support/bulletins/tb-nowsms-013.htm Hope that helps. -bn | |||
