| Routing transfer from one nowSMS server to another |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through June 02, 2006 ⬆ |
◄ ► |
| Author | Message | |||
| Alon Ben New member Username: Alonb Post Number: 1 Registered: 01-2006 |
Hi, Is there any site that might help us configuring this scheme or something that might help us doing so. we would like to make a plan how to transfer from one nowSMS server to another a SMS message, and execute a 2-way command on the other hand. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5409 Registered: 10-2002 |
Hi, I'm not sure that I understand what you're trying to do. I'm guessing that you're trying to construct a "simulation" environment? Where basically you submit a message to one NowSMS, and it gets forwarded to another NowSMS where the message gets routed to a 2-way command. If that's what you're trying to do ... generally speaking, the best way to link two NowSMS servers together is with SMPP. This particular scenario is a little tricky because NowSMS only routes messages to a 2-way command when it receives them via a connection defined in that server's SMSC list. (Otherwise NowSMS expects that the intent is for the message to be routed outbound, so it doesn't go to the 2-way command facility.) So let me give you an example ... Server A as the "submit server". You're going to need to define a dummy entry in the "SMSC" list, in order to enable basic message routing. The easiest thing to do here is to define an "HTTP SMSC", and just point it to any web server address. Make sure "Support any outbound message traffic" is unchecked, so that NowSMS doesn't actually try to route any messages via the dummy connection. (If it did try to route the message, it would just make an HTTP request to the configured web server, so that wouldn't really be a problem. But to avoid confusion, it is best if no messages are actually routed via this connection.) Next, on the "Web" page of the configuration dialog, enable the SMPP server and define a port number for it to use. Then, define an account on the "SMS Users" page. This account will be used for the other server to connect into this server and retrieve messages. Check "Enable SMPP Login for this user", and check "Route received messages to user via SMPP". In "Recipient Address(es) to route to this user", put "*" ... which effectively means that all messages will get routed for delivery to this user account. Enable the SMS service. Now on to Server B, which will be the 2-way command server. In the "SMSC" list, add an SMPP connection to Server A, logging in with the username and password defined above. Make sure that you enable "Receive SMS" for that connection. Then go about the 2-way configuration. Any messages submitted to Server A will get routed back to Server B's 2-way command facility. General 2-way tips/suggestions here: http://support.nowsms.com/discus/messages/1/4520.html If I've misinterpreted your question, please clarify exactly what you're trying to accomplish. -bn | |||
| Jimmy Cherian New member Username: Jimmykcherian Post Number: 3 Registered: 09-2004 |
Hi Bryce, When Now SMS acts as an SMPP Server, it can route the messages from a specific smsc connection to the SME Client (SMS User account already created). The messages received are routed to the client can be parsed only by the phone numbers of the users. Is it possible to route the messages to the SMS Client using the short code of the smsc connection (ie, if we have connected to more than one short code for the same smsc connection, i would prefer only messages from one short code to be send to the SMS Client connected to the Now SMS SMPP Server. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5749 Registered: 10-2002 |
Hi Jimmy, Yes, this is possible. In this case, in the defintion of the "SMSC" connection, leave the "Route SMS to Local User" setting blank or "(disabled)". Then in the setup of the individual "SMS Users" accounts, you want to define the appropriate short codes in the "Recipient address(es) to route to this user" field. This field can contain a comma delimited list (e.g., 10000,10001,10002). We added the "Route SMS to Local User" setting primarily to make it easier for people who were routing messages out via GSM modems. But when you need more flexibility, the best way is to define the short codes and associate them with the appropriate "SMS Users" account. That way, when NowSMS receives a message for that short code, it routes it to the appropriate account. The only catch is that you might need to do some checking with your SMSC connections. Ususually when a message is received from an SMSC connection the recipient is shown as the short code. But sometimes, instead of the actual short code you see an alias that was assigned for internal use at the operator for that short code. So you need to test and see if the operator routes the message back with the proper short code as the recipient. Usually this is only an issue for UCP/EMI connections, but I mention it just in case. -bn | |||
