| Using Now SMS as SMPP Server. |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through September 15, 2006 ⬆ |
◄ ► |
| Author | Message | |||
| Libyana Mobile Phone New member Username: Libyana Post Number: 1 Registered: 04-2006 |
Hello Dear, I am planning to use Now SMS as SMPP server, I will add accounts in our smpp server and add new SMSC Connection in now sms for each account, then create a sms user for each smsc, all our smpp clients will connect through Now SMS gateway. if it's possible tell me how to implement this. -br | |||
| mimo love New member Username: Mimolove247 Post Number: 1 Registered: 04-2006 |
hi | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5828 Registered: 10-2002 |
Hi br, Are you planning to define the new accounts both on your existing SMSC and on the NowSMS server? Normally what you would do is define one account on the SMSC, and then configure NowSMS ("SMSC" page) to connect to the SMSC using that account. Then, you would define user accounts for your SMPP clients on the "SMS Users" page. These users would then share a single connection to the SMSC. If I did not understand your question, please provide more detail. -bn | |||
| Libyana Mobile Phone New member Username: Libyana Post Number: 2 Registered: 04-2006 |
thank you Bryce I'm planning to bind every nowsms user account with one smsc connection for sending and receiving sms, is it possible. -br | |||
| Libyana Mobile Phone New member Username: Libyana Post Number: 3 Registered: 04-2006 |
Can i define a 2-way command for each smsc connection? | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5845 Registered: 10-2002 |
Yes, it is possible. But it is somewhat difficult to configure. Let me explain. You need to look at both the sending and receiving message flow. To avoid confusion, I am referring to the perspective of the SMPP client that is sending or receiving messages in this scenario. First, let's look at sending. When the end-user SMPP client submits an SMS message for sending, NowSMS has to somehow be configured such that this message will only be routed to a particular SMSC connection. There are a couple of different ways to configure this. a.) If every client connection is forced to use only a single short code, you can define a "Forced Sender Address" of this short code for the "SMS Users" account. Then define this same short code as the "Default Sender Address" for the matching SMSC connection. If the SMPP client uses a different sender address, NowSMS will apply the "Forced Sender Address". When NowSMS goes to route the message to an upstream SMSC, it will always route the message via the SMSC with a matching sender address. b.) An alternative approach does not rely on sender address matching, but instead can force all messages submitted by a particular "SMS Users" account to be routed via a specific "SMSC" connection. However, this approach requires manual SMSGW.INI file edits at this time. The following settings can be added to an SMSC specific section of SMSGW.INI (e.g., [SMPP - a.b.c.d:xyz] section): AllowedUserOnly= AllowedUser1= AllowedUser2= AllowedUser...= These configuration settings are defined to limit particular outbound "SMSC" connections to use by selected "SMS Users" accounts. AllowedUserOnly=Yes -- This setting specifies that the SMSC connection can only be used by users that are specifically authorised to use this SMSC. When routing messages from users that are not specifically authorised for this connection, NowSMS will not use this SMSC and route messages as if this SMSC definition did not exist. AllowedUser1=username -- This setting can be repeated with sequentially assigned numbers (e.g., AllowedUser2=xxx; AllowedUser3=yyyy). This entry is used to specify specific "SMS Users" accounts that are allowed to use the SMSC connection when AllowedUserOnly=Yes. Note: It is NOT necessary to restart NowSMS when making updates to the AllowedUserOnly or AllowedUser1 settings in SMSGW.INI. These changes will be detected dynamically by NowSMS. Second, let's look at receiving. Having all messages received via a particular "SMSC" connection routed to a specific "SMS Users" account is relatively easy in NowSMS 2006. In the "Properties" for the "SMSC" connection, there is an option "Route SMS to local user", by selecting an "SMS Users" account here, all messages received via this SMSC connection will be routed to that account. In versions prior to 2006, you can only perform routing based upon recipient phone numbers. In the "SMS Users" account definition, you can define a list of phone numbers/short codes that should be routed to this particular account. Whenever NowSMS encounters a message being received for a matching recipient, it routes it to that "SMS Users" account.
Different 2-way commands can be defined for different recipient phone numbers/short codes ... but they are not tied to a specific SMSC connection. When you define a "Receive Phone Number" mask, the command will only apply if a message is being received for a phone number/short code matching that mask. That said, there is an @@SMSCROUTE@@ replacement parameter that you can use in a 2-way command that can tell you which SMSC a message was received from. -bn | |||
| Cassie Nel New member Username: Flyingbok Post Number: 1 Registered: 06-2006 |
Libyana, Sorry to hi-jack your thread but I would really appreciate a call from you re Libyana. Please call me on 092 655 9752. Much appreciated ! Tx CN | |||
