ERROR: Bind Failed - ESME_RBINDFAIL(0x0D)

ERROR: Bind Failed - ESME_RBINDFAIL(0x0D) SearchSearch
Author Message
Stavros Tseriotis
New member
Username: Tuccero9

Post Number: 5
Registered: 08-2016
Posted on Thursday, August 25, 2016 - 06:05 am:   

Hello,

I have Now SMS/MMS Gateway v2013.09.26 and i recently created a new SMSC (SMPP over Tcp/IP) connection that is actually connected to a GSM modem.
I do the test and i receive the SMS successfully but i see the following error message on my NowSMS Gateway screen:
SMPP - <gsm_ip>: SMPP Failure -- Unable to login to SMPP server with specified parameters: ERROR: Bind Failed - ESME_RBINDFAIL(0x0D)

Should i be worry about this message? Do i need to do some further actions?

Thank you
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 8158
Registered: 10-2002
Posted on Thursday, August 25, 2016 - 12:54 pm:   

Hi,

If everything is working OK, then the issue is likely that the SMPP server only allows a single bind (session).

By default, if receiving is enabled for the SMPP connection, NowSMS creates 2 binds, a sender and a receiver.

If you go into the advanced settings for the SMPP connection, there is a "transceiver" option. With this setting, a single bind is used for both sending and receiving. I suspect this will remove the error.

Some more info can be found here: http://www.nowsms.com/doc/configuring-smsc-connections/smpp-smsc


quote:

Send and Receive Messages over the same connection (SMPP Transceiver) – By default, when NowSMS is configured to both send and receive messages via an SMPP connection, NowSMS will connect to the SMPP server with two separate connections, one bound as a transmitter and the other bound as a receiver. Some SMS providers prefer that only a single connection resource is used, bound as a transceiver. When this option is enabled, NowSMS will use a single transceiver connection instead of two separate connections.




-bn

Bryce Norwood
Now SMS/MMS Support
Stavros Tseriotis
New member
Username: Tuccero9

Post Number: 6
Registered: 08-2016
Posted on Friday, August 26, 2016 - 06:20 am:   

Hello,

Thank you for your response.
It is a weird situation. I have a cluster of 2 SMS server that are using nowsms gateway so the same connections are configured on both servers.
SMS can be send by one or the other server they are both active at the same time.
One of the two servers is shows that all connections are OK and the other server it displays this message.
SMS are send to the clients i dont have any issue i just wanted to get rid of this message.
I checked the configuration again, i noticed that "Receive SMS Messages" checkbox is not checked. Reading the url that you provided in your post, i clicked the advanced settings and checked the box that says "Send and Receive Messages over the same connection (SMPP Tranceiver)".
I still have the same behavior. One of the server says "All connections OK" and the other displays the error message.

Best Regards,
Stavros
Stavros Tseriotis
New member
Username: Tuccero9

Post Number: 7
Registered: 08-2016
Posted on Friday, August 26, 2016 - 07:36 am:   

update on this case:
I noticed now that only the one of the two servers work.
It seems that only the server which displays "All connections OK" is sending SMS.
The second server although when i send a test SMS successfully i keep getting these error in SMSOUT log file:
"2016-08-26 09:21:33,System,,SMPP - <gsm_ip>:2775,SMPP Failure -- Unable to login to SMPP server with specified parameters: ERROR: Bind Failed - ESME_RBINDFAIL (0x0D),SMSCRouteName=SMPP - <gsm_ip>"

Any request that comes on this server for this connection it fails.
I dont understand what is the problem both of them have the same connections
Stavros Tseriotis
New member
Username: Tuccero9

Post Number: 8
Registered: 08-2016
Posted on Friday, August 26, 2016 - 09:35 am:   

another update on this issue:
It seems that i spotted the cause of the problem.
I stopped the nowsms services on the server that was working fine and only the second (problematic) server was active.
I noticed then that when a request to send SMS arrived for the GSM connection then the SMS was sent successfully and the error was cleared from the SMS gateway.
Then i started the services again on the first server and when a request for SMS on the GSM connection arrived then the error appeared on this server.
So now the second server can send SMS on GSM connection and the first cannot.
This shows that for some reason only one ip address is allowed to send SMS on the GSM.
Is it a way to configure multiple ip addresses to send on the SMPP connection through nowsms or is it something that i have to sort out on my GSM modem?
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 8160
Registered: 10-2002
Posted on Friday, August 26, 2016 - 12:34 pm:   

Hi,

It basically comes down to the first line of my earlier response. The issue is likely that the SMPP server only allows a single bind (session).

If this were a service provider, then I would say that the provider likely has a restriction of one bind per account name. Using different account names would be the only work-around.

Unfortunately, as this is a specialized device, it may have an overall limit of 1 bind. Or it may have settings to allow more than 1 bind.

Do you have to use that GSM modem? NowSMS can use an Android device as a modem over WiFi, and more than 1 NowSMS can send through that device (subject to throughput capability).

-bn

Bryce Norwood
Now SMS/MMS Support
Stavros Tseriotis
New member
Username: Tuccero9

Post Number: 9
Registered: 08-2016
Posted on Saturday, August 27, 2016 - 11:01 am:   

Hello,

Well the reason I am using the GSM modem is due to an unresolved problem that I face with my first SMPP connection which goes to my service provider.
It seems that a lot of telecommunication companies decided to put some firewall in front of their servers and when they receive an SMS from a sender that has a string and not number (eg. you receive message from sender "NOWSMS" instead of "+99999999") they blocked it.
This way I face a problem with some international numbers as I could not send SMS to them. So it lead me to the end result of using a GSM modem as a second SMPP connection that will be used for international numbers only.
About the android device, what device could be used? I mean an android phone? It can handle a lot of traffic? Cause there are a lot of customers that are using international numbers.

Best Regards,
Stavros
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5708
Registered: 08-2008
Posted on Monday, August 29, 2016 - 06:41 pm:   

Hi Stavros,

It is possible to block a message based on sender address or change the sender address when you route a message upstream.

This is done by implementing accounting callbacks. There is an article about accounting callbacks here: http://www.nowsms.com/understanding-sms-accounting-callbacks

A few years ago, I wrote an example callback that rejects messages with an alphanumeric sender. This example can be found at http://support.nowsms.com/discus/messages/1/71175.html

It would be easy to modify that example to instead change the alpha sender to +99999999 and accept the message. In fact, II only need to change one line. After determining that the sender address contains alpha characters, instead of rejecting the message (PreAuth=Deny), we issue a response to change the sender address.

 
<?php
header ("Content-Type: text/plain");

$response = "OK";

if (isset($_REQUEST['Type'])) {
if ($_REQUEST['Type'] == "SMSSend") {
if (isset($_REQUEST['PreAuth'])) {
if ($_REQUEST['PreAuth'] == "Yes") {
if (isset($_REQUEST['Sender'])) {
if (!preg_match('/^\+?\d+$/', $_REQUEST['Sender'])) {
$response = "Sender=+99999999";
}
}
}
}
}
}

echo $response;
?>



The above callback will change any alphanumeric sender to +99999999 only if SMSAccountingAllowChanges=Yes is set under the [SMSGW] section header of SMSGW.IN

--
Des
NowSMS Support
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5709
Registered: 08-2008
Posted on Monday, August 29, 2016 - 06:51 pm:   

Sorry, I forgot to answer your main question.


quote:

About the android device, what device could be used? I mean an android phone? It can handle a lot of traffic?




Pretty much any Android phone from the last 4 to 5 years. We require a minimum of Gingerbread (2.3).

An app loads on the phone, and the phone must be connected to WiFI with an IP address that NowSMS can connect to. NowSMS can either scan for the device by name if on the same network, or you can assign static IPs.

Load wise, performance is on par with a dedicated modem device, usually a little faster for SMS, and a lot faster for MMS.

--
Des
NowSMS Support
Stavros Tseriotis
New member
Username: Tuccero9

Post Number: 10
Registered: 08-2016
Posted on Tuesday, August 30, 2016 - 06:50 pm:   

Hello,

Thank you for your useful tips.
The reason I didn't think to change the sender address from a string to +99999999 (telephone number) is because I was notified that there is actually a European law about bulk SMS that basically instructs you to use an alphanumeric string as the sender address if you are sending SMS via an application.
Therefore it will be illegal to change the sender address and convert it to a telephone number in order to send the message.
So I guess it is clear that I have two choices now:
1. find a way to allow more than 1 bind (solution done on GSM modem)
2. use an android device to send SMS to international numbers

thank you again for your useful tips.

Best Regards,
Stavros