| Many SMPP connections in one NowSms Gateway |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through October 19, 2005 ⬆ |
◄ ► |
| Author | Message | |||
| Mohamed Salim ALI New member Username: Salim Post Number: 30 Registered: 04-2005 |
Hello All,  We have bought a Full version of nowsms gateway and we are in testing purpose for NowWap trial version. I face two big problems: I would like to set 3 SMPP conections to differents SMSC Servers. I set the first one is working well, i send and receive SMS. I set the second one, the connection is Ok, but when I send an SMS trought the web interface, I get it from the first one short code only. I create SMS users, I can log in the web interface with a separate short code. But my Problem is on 2 way, Which parameters I have to set in my HTTP URL username and password ? So How I can manage the three smpp connections with the web interface, and the parameters to set in 2 way tab command for each SMPP connection URL ? For the WAP, I trying to set it, but I am pending to set the important parameters in the Wap proxy. My WAP proxy is behind a ISA Firewall Server. ==> So what are the important parameters must be set in, to enable the browse of some WML/XHTML files from my Web Server. ==>Thank you for any one who can give Help ! Regards//Salim. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4704 Registered: 10-2002 |
Hello Salim, I apologise for the delay in answering your questions, but I'm not sure that I understand your questions completely. So let me offer some suggestions that might help. And if this does not answer your questions, can you please try to explain in more detail what is not working as you would like it to work. To route messages outbound to a particular SMSC, NowSMS needs to have rules for how the messages are to be routed. The two pieces of information that NowSMS looks for is a match on the "Sender address" associated with the message and the "default sender address" for an SMSC ... as well as the "Preferred SMSC Connection for" information (recipient matching) associated with the SMSC. There is a good description of this logic in the following thread: http://support.nowsms.com/discus/messages/1/4664.html For 2-way messaging, if you have different short codes for each SMSC connection, then you can use the "Receive phone number(s):" field associated with a 2-way command definition to associate different 2-way commands with messages received for different short code numbers. When this parameter is defined for a "2-way" command, it means that the 2-way commmand will only be executed if the message was addressed to a number listed in the "Receive phone number(s)" field. (This field can contain a comma-delimited list of numbers if you want to have more than one number defined for a command. It can also use * or ? characters for pattern matching against the receiving phone number.) This way, you can easily define different "2-way" commands for different short codes. If you are using the same short code across multiple SMSCs, then it is more difficult. We did recently add a "2-way" replaceable parameter that can identify the route from which a message was received. This is included in an update for NowSMS v5.51 that can be downloaded from the following URL: http://www.nowsms.com/download/latestpatch.zip In the PATCH.TXT file included in the ZIP, is the following information: --- * SMS Gateway - Add the ability for HTTP message submissions to indicate that the message should be routed via a specific SMSC. The HTTP interface now supports "&SMSCRoute=xxxxx", where the value of this setting can be the name of a defined SMSC (e.g., "Bluetooth Modem" or "SMPP - a.b.c.d:xyz"), or it can be a route name that is defined to be associated with the SMSC. To define a route name for an SMSC, it is necessary to manually edit SMSGW.INI, and under the appropriate section header (e.g., [Modem - Bluetooth Modem] or [SMPP - a.b.c.d:xyz]), add RouteName=xxxxx. * SMS Gateway - Add support for passing the SMSC name (or route name) to a 2-way SMS command, so that the command can identify the SMSC from which the message was received. The following additional variable is available in HTTP 2-way commands: @@SMSCROUTE@@. This variable will contain the SMSC name (e.g., "Bluetooth Modem" or "SMPP - a.b.c.d:xyz"), or the route name associated with the SMSC. --- Also, in that update, there is a way that you can define that only certain user accounts are allowed to route messages to particular SMSC definitions: --- * New configuration settings are defined to limit particular outbound "SMSC" connections to use by selected "SMS Users" accounts. These settings cannot yet be configured via the user interface, but can be configured by direct edits of the SMSGW.INI file. Under the SMSC section (e.g., [Modem - modem driver name] or [SMPP - ip:port]) header, the following configuration settings can be applied: 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. -- For question #2, I also need more detail to understand what the question is asking about. Let me offer some explanation of what a WAP Proxy is, because perhaps there is some confusion about the role of a WAP Proxy. Generally speaking, there are no parameters to set in the WAP Proxy itself in order to enable access. By default it is enabled to accept connections, and you simply connect to it, and it proxies the request to the content server. There is no need to configure which content server because the request from the client must include the URL of the content server being requested. You can think of a WAP Proxy as being similar to an HTTP Proxy. A Proxy does not serve up its own content, it proxies requests to other servers. If your proxy is behind a firewall, then you need to open up ports to enable access to it. WAP devices will either use the WSP (WAP 1 or WAP2 devices) or W-HTTP/W-TCP (WAP2 devices only) protcols for connecting to the proxy. Typically, in the phone, you must configure data connectivity settings that give you a TCP/IP connection (either a GPRS APN = access point name, or a circuit switched dial-up connection using standard PPP), and then you configure the IP address of the gateway, and possibly a port number. It is a requirement that the device be able to make an IP connection to the proxy. When WSP is used, devices will attempt to connect on UDP (connectionless IP) port 9200 or 9201. So, these ports must be open in a firewall. When W-HTTP/W-TCP is used, the port number is configurable, and is the "HTTP Proxy Port" number configured on the "HTTP" page of the NowWAP configuration dialog. The client needs to be able to make a TCP connection to that port number, so that port must be open in a firewall. The proxy must be able to establish TCP (HTTP) connections to any content servers that the devices need to access. I hope that helps answer your questions. If not, please feel free to respond back with further clarification. -bn | |||
