New SMSC not connecting | Search |
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through June 03, 2020 ⬆ |
◄ ► |
Author | Message | ||||
Antonio Medina Ortega New member Username: Antoniomedina Post Number: 7 Registered: 07-2015 |
Hi all, We are running NOWSMS/MMS Gateway v2016.03.28 release. We have one active SMSC connection on port 5001. We have tried to setup a new SMSC connection on port 6200, but this new connection is failing. We see on Wireshark that MMSC sends Bind, which is successfully replied by SMSC peer, but it intermediately sends an Unbind. MMSC repeats this sequence one more time and it stops trying setting up the connection. Any idea about what's going on? We are attaching the trace and the corresponding entry in SMSC.ini file for this new SMSC (we have removed the number info) Thanks in advance. Kind regards, Antonio. [SMSGW] Modem2=SMPP - 172.27.35.22:6200 [SMPP - 172.27.35.22:6200] SMPPVersion=v3.4 UserName=TEST Password=TEST SenderAddress=XXXXXXXXXXX SenderAddressOverride=Yes Receive=Yes ReceiveMMS=No UseSSL=No RoutePrefOnly=Yes Route1=+XX* LongSMSAlt=Yes
| ||||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5929 Registered: 08-2008 |
Hi, Is an error being reported anywhere? Is this when you are initially setting up the connection? The configuration program tests the connection details by connecting to the SMSC...that is what this looks like. By default, there are separate transmitter and receiver binds and both are tested...and both look OK. -- Des NowSMS Support | ||||
Antonio Medina Ortega New member Username: Antoniomedina Post Number: 8 Registered: 07-2015 |
Hi Des, you can find below all the entries I have been able to see on log files. I wonder why the connection is not kept stable by MMSC. I mean, why enquire messages are not being sent. Am I missing some config? Could be a problem of licenses limiting the number of SMSC? File SMSDEBUG 15:41:00:571 [19] ThreadProcessModem: SMPP - 172.27.35.22:6200 15:41:00:574 [19] ThreadProcessModem: SMPP Failure -- Unable to connect to SMPP server at 172.27.35.22:6200 15:41:00:574 [21] ThreadProcessSMPPReceive: SMPP Receiver Failure -- Unable to connect to SMPP server at 172.27.35.22:6200 15:41:06:570 [0] LoadPreferredRouteList: Route list updated - 2/1 15:41:06:570 [0] LoadPreferredRouteList: Route list updated - 2/1 15:41:06:570 [0] LoadPreferredRouteList: Reload 15:41:06:570 [0] LoadPreferredRouteList: preferred routing = +350*,SMPP - 10.192.3.91:5001 15:41:06:570 [0] LoadPreferredRouteList: preferred routing = +34711*,SMPP - 172.27.35.22:6200 15:41:08:570 [0] LoadPreferredSenderList: Reload 15:41:08:570 [0] LoadPreferredSender: preferred sender = 35020052200,SMPP - 10.192.3.91:5001 15:41:08:570 [0] LoadPreferredSender: preferred sender = 34711000000,SMPP - 172.27.35.22:6200 15:41:10:570 [0] UseRouteCache: Yes 15:41:10:570 [0] main: RoutingDbReset 15:41:11:070 [0] main: RoutingDbReset2 15:41:11:070 [17] MessageRoutesAdd: TESTD05C.REQ 15:41:11:070 [17] MessageRoutesAdd: *=SMPP - 172.27.35.22:6200 15:41:25:675 [19] ThreadProcessModem: SMPP Failure -- Unable to connect to SMPP server at 172.27.35.22:6200 15:41:25:676 [21] ThreadProcessSMPPReceive: SMPP Receiver Failure -- Unable to connect to SMPP server at 172.27.35.22:6200 15:41:26:835 [20] Debug: 25a51decac8f75c5f7f7c511d9f9f958d98e6d7987b597f713eb9f7d4cd47482d79fc0489060ad8c 2907698819c08446 15:41:26:835 [20] debug: session still valid 15:41:26:835 [20] ThreadProcessConnection: Processing request /null.htm 15:42:10:778 [19] ThreadProcessModem: SMPP Failure -- Unable to connect to SMPP server at 172.27.35.22:6200 15:42:10:779 [21] ThreadProcessSMPPReceive: SMPP Receiver Failure -- Unable to connect to SMPP server at 172.27.35.22:6200 15:42:15:879 [19] InetServerConnect: Connected to 10.255.4.130 (10.255.4.130:25) 15:42:24:837 [20] Debug: 25a51decac8f75c5f7f7c511d9f9f958d98e6d7987b597f713eb9f7d4cd47482d79fc0489060ad8c 2907698819c08446 15:42:24:837 [20] debug: session still valid 15:42:24:837 [20] ThreadProcessConnection: Updating cached user info 15:42:24:837 [20] ThreadProcessConnection: Processing request /null.htm 15:43:15:124 [19] ThreadProcessModem: SMPP Failure -- Unable to connect to SMPP server at 172.27.35.22:6200 15:43:15:883 [21] ThreadProcessSMPPReceive: SMPP Receiver Failure -- Unable to connect to SMPP server at 172.27.35.22:6200 15:43:22:837 [20] Debug: 25a51decac8f75c5f7f7c511d9f9f958d98e6d7987b597f713eb9f7d4cd47482d79fc0489060ad8c 2907698819c08446 15:43:22:837 [20] debug: session still valid 15:43:22:837 [20] ThreadProcessConnection: Processing request /null.htm 15:44:20:838 [20] Debug: 25a51decac8f75c5f7f7c511d9f9f958d98e6d7987b597f713eb9f7d4cd47482d79fc0489060ad8c 2907698819c08446 15:44:20:838 [20] debug: session still valid 15:44:20:838 [20] ThreadProcessConnection: Updating cached user info 15:44:20:838 [20] ThreadProcessConnection: Processing request /null.htm 15:44:40:229 [19] ThreadProcessModem: SMPP Failure -- Unable to connect to SMPP server at 172.27.35.22:6200 15:44:40:987 [21] ThreadProcessSMPPReceive: SMPP Receiver Failure -- Unable to connect to SMPP server at 172.27.35.22:6200 15:45:18:841 [20] Debug: 25a51decac8f75c5f7f7c511d9f9f958d98e6d7987b597f713eb9f7d4cd47482d79fc0489060ad8c 2907698819c08446 15:45:18:841 [20] debug: session still valid 15:45:18:841 [20] ThreadProcessConnection: Processing request /null.htm File SMSOUT 2018-06-12 15:41:00,System,,SMPP - 172.27.35.22:6200,SMPP Failure -- Unable to connect to SMPP server at 172.27.35.22:6200 2018-06-12 15:41:00,System,,SMPP - 172.27.35.22:6200,SMPP Receiver Failure -- Unable to connect to SMPP server at 172.27.35.22:6200 2018-06-12 15:41:25,System,,SMPP - 172.27.35.22:6200,SMPP Failure -- Unable to connect to SMPP server at 172.27.35.22:6200 2018-06-12 15:41:25,System,,SMPP - 172.27.35.22:6200,SMPP Receiver Failure -- Unable to connect to SMPP server at 172.27.35.22:6200 2018-06-12 15:42:10,System,,SMPP - 172.27.35.22:6200,SMPP Failure -- Unable to connect to SMPP server at 172.27.35.22:6200 2018-06-12 15:42:10,System,,SMPP - 172.27.35.22:6200,SMPP Receiver Failure -- Unable to connect to SMPP server at 172.27.35.22:6200 2018-06-12 15:43:15,System,,SMPP - 172.27.35.22:6200,SMPP Failure -- Unable to connect to SMPP server at 172.27.35.22:6200 2018-06-12 15:43:15,System,,SMPP - 172.27.35.22:6200,SMPP Receiver Failure -- Unable to connect to SMPP server at 172.27.35.22:6200 2018-06-12 15:44:40,System,,SMPP - 172.27.35.22:6200,SMPP Failure -- Unable to connect to SMPP server at 172.27.35.22:6200 2018-06-12 15:44:40,System,,SMPP - 172.27.35.22:6200,SMPP Receiver Failure -- Unable to connect to SMPP server at 172.27.35.22:6200 2018-06-12 15:46:25,System,,SMPP - 172.27.35.22:6200,SMPP Failure -- Unable to connect to SMPP server at 172.27.35.22:6200 2018-06-12 15:46:26,System,,SMPP - 172.27.35.22:6200,SMPP Receiver Failure -- Unable to connect to SMPP server at 172.27.35.22:6200 2018-06-12 15:48:30,System,,SMPP - 172.27.35.22:6200,SMPP Failure -- Unable to connect to SMPP server at 172.27.35.22:6200 2018-06-12 15:48:31,System,,SMPP - 172.27.35.22:6200,SMPP Receiver Failure -- Unable to connect to SMPP server at 172.27.35.22:6200 File SMPP-172.27.35.22-6200.ERR SMPP Failure -- Unable to connect to SMPP server at 172.27.35.22:6200 | ||||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5930 Registered: 08-2008 |
Hi Antonio, This particular error indicates a TCP/IP connection failure when the server tries to connect. I'm going to guess that the web interface for the SMS gateway is bound to a specific IP address. This has a side effect that the SMS gateway will try to use that IP address for outbound connections to an SMSC. The quick solution is to set the IP address of the web interface to all available. If that is not wanted for security reasons, manually add a BindIP=a.b.c.d setting to the [SMPP - server:port] section for that SMSC. (If the IP on that particular network is dynamic, I believe BindIP=0.0.0.0 will also work. -- Des NowSMS Support | ||||
Antonio Medina Ortega New member Username: Antoniomedina Post Number: 9 Registered: 07-2015 |
Hi Des, we have added the BindIP statement and now the connection is ok. Thanks for your help. Kind regards, Antonio. |