| Multiple Network Card IP Support |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through April 05, 2007 ⬆ |
◄ ► |
| Author | Message | ||||
| Rhea New member Username: Rhea Post Number: 23 Registered: 08-2006 |
Hi Bryce, If my Server has 2 network cards, each with a different IP, and NowSMS is configured with 2 SMPP Connections, where one SMPP Connection connects to the operator's SMSC using one of the Network Card IPs and the other SMPP Connection connects to the operator's SMSC using the other Network Card IP. Can this work? Can NowSMS handle this scenario? We need to do this because the Operator has limitation in his SMSC when it comes to connecting several shortcodes using the same IP Address. | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6748 Registered: 10-2002 |
Hi Rhea, If you need to bind an SMPP connection to a specific IP source address, then it is possible to do this by manually editing the SMSGW.INI file. Under the [SMPP - server:port] header, it is possible to add a configuration parameter: BindIP=1.2.3.4 This parameter will not be used for connection tests from the NowSMS configuration program, but it will be used by the actual NowSMS server when it makes its connections to the SMSC. -bn | ||||
| Rhea New member Username: Rhea Post Number: 27 Registered: 08-2006 |
Dear Bryce, I did what you told me and it worked. But there is a very strange problem and i cannot seem to figure out the reason. I have a total of 2 2-way Services, each is now connected using a separate (IP/Network Card) to the SMSCs. One service is only connected to one operator (A) - (4 Multiple Sessions, Connect Port is not limited), the other service is connected to 2 Operators (A & B) with the same shortcode number, but different route prefixes. Now for each service i defined the following: - Routename - Bind IP - UserOnly - Route Prefix What is happening is when i send to the first service using Operator (A) and then send to the other service using both Operator (A) & (B), one service replies back, the other keeps the messages in the Q and converted to ERR. When i manually change the ERR to REQ it sends the message off. I think the problem is the confusion between 2 services having different BIND IPs, as if the system cannot be connected to both at the same time, and reply back using both IPs at the same time. I really need your feedback because this is a bit complicated for me. Do you want me to send you the INI file? | ||||
| Rhea New member Username: Rhea Post Number: 28 Registered: 08-2006 |
I noticed this error in the SMS Log File: ThreadProcessModem: Error: ERROR: Invalid Dest Addr | ||||
| Rhea New member Username: Rhea Post Number: 29 Registered: 08-2006 |
Hi Bryce, Any feedback on the above? | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6766 Registered: 10-2002 |
Hi Rhea, I don't understand enough of your setup or what is occurring. "ERROR: Invalid Dest Addr" indicates that the SMSC is rejecting the message, and returning an error code that means invalid destination (recipient) address. I'd be curious ... when you renamed the .ERR file back to .REQ ... did the message then get picked up by the other SMSC? I suspect that is what happened. I would be curious if the SMSOUT-yyyymmdd.LOG file mentioned the "ERROR: Invalid Dest Addr" referencing one SMSC connection, but then when you renamed it, the "OK" entry references a different SMSC connection. If that is what is happening, then this suggests that you need to set your route prefixes ("Preferred SMSC Connection for") correctly for each SMSC connection, because the SMSC will reject messages for which it does not support. It would probably help me to understand if I could see your SMSGW.INI and SMSOUT-yyyymmdd.LOG file. (xxxxx out the username and password from SMSGW.INI, even though you're probably safe because the provider has IP address restrictions on your account.) Then we can look at which messages are being rejected, and see if we can determine if the reason for the rejection is because they are being routed to a different SMSC from what we expect. -bn | ||||
| Rhea New member Username: Rhea Post Number: 30 Registered: 08-2006 |
Hi Bryce, Thank you very much for your reply. I will send you the ini and log files. What email should i send it to? | ||||
| Rhea New member Username: Rhea Post Number: 31 Registered: 08-2006 |
Hi Bryce, to which email should i send you the ini and log files? | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6797 Registered: 10-2002 |
If you still need to send these files, send them to nowsms@now.co.uk with "Attention: Bryce" in the subject line. Or you can post them as an attachment to a reply here. | ||||
| Rhea New member Username: Rhea Post Number: 33 Registered: 08-2006 |
Dear Bryce,
Yes when i renamed the .ERR file back to .REQ the message did then get picked up by the other SMSC. But i noticed that this happened with one msg (route prefix = 2010) not the other (route prefix = 2012). Maybe because there are other SMSC connections having route prefix = 2012? I have attached the INI, IN, OUT files. You will notice in the INI file that i have defined for each service/connection the following: Now for each service i defined the following: - Routename - Bind IP - UserOnly - Route Prefix I would appreciate your feedback as soon as you can because i am really tight on time. | ||||
| Rhea New member Username: Rhea Post Number: 34 Registered: 08-2006 |
Dear Bryce, I looke again into the problem, and it definitely seems like a routing problem, because the gateway tries to route the message using the other defined connection for the same BINDIP & SMSCROUTE & USER so in the end the diffrentiator is the Route Prefix. But the strange thing is that i checked thoroughly and the Route Prefix definied are correct. So i am clueless where the problem is?! | ||||
| Rhea New member Username: Rhea Post Number: 35 Registered: 08-2006 |
Hi Bryce, Any feedback? | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6838 Registered: 10-2002 |
Hi Rhea, It's hard for me to fully understand your configuration. I notice that you have "RouteName=" definitions for each of your SMSCs, but I don't know if you are referencing them when you submit messages. (If you are, that would override any prefix matching logic.) If I look at the situations where "Invalid Dest Addr" is returned, then I notice the following failures: +20127498088 failed: SMPP - 163.121.178.15#2:1035 SMPP - 163.121.178.15:1035 succeeded: SMPP - 213.131.69.45#3 SMPP - 213.131.69.76:4305 +20101900254 failed: SMPP - 213.131.69.76:4305 succeeded: SMPP - 163.121.178.15#2:1035 In all cases, I would agree that based upon the configuration details you supplied, the messages should not have been routed to the SMSC connection that rejected them. So I ran some tests, using your INI file, and I couldn't get NowSMS to use the wrong route. So I guess my question would be ... what version of NowSMS? I don't know of any bugs in this area, but maybe there is a version-specific with a particular setting. I tried with the latest 2006.10.31 version. But I don't see any changes that would have affected this logic. -bn | ||||
| Rhea New member Username: Rhea Post Number: 36 Registered: 08-2006 |
Hi Bryce, I am trying the latest version with the October Patch. Like you said i am using RouteName= definitions when submitting, but as you will notice that there are 2 different SMSC connections having the same route name, and the differentiator between them is the route prefix. Is this the problem? that when you apply RouteName= it overlooks the route prefix? | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6841 Registered: 10-2002 |
Hi Rhea, That sounds like the problem. If a route name is present, the route prefixes (and all other routing criteria) are ignored. -bn | ||||
| Rhea New member Username: Rhea Post Number: 37 Registered: 08-2006 |
Dear Bryce, If this is the problem, then i guess its something that need to be enabled in NowSMS. Can you help me to overcome this problem in a roundabout manner, because i need to enable RouteNames & Prefixes. | ||||
INI_OUT_IN_Files
