Incorrect BIND Status for SMPP connection | Search |
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through October 16, 2008 ⬆ |
◄ ► |
Author | Message | |||
Raffi Krikorian New member Username: Rkrikorian Post Number: 1 Registered: 06-2008 |
I setup an SMPP connection to mBlox, but when I send a message, I get the following error message: [debug log] 16:16:00:748 [13] ThreadProcessModem: Error: ERROR: Incorrect BIND Status for given command - ESME_RINVBNDSTS [smsout log] 2008-06-13 16:16:00,473E9719.req,198.245.25.19,18185551212,Retry Pending - ERROR: Incorrect BIND Status for given command - ESME_RINVBNDSTS -- SMPP - smpp.psms.us.mblox.com:3204,Sender=28444 My HTTP request: http://myserver:8800/?PhoneNumber=18185551212&Text=usawire+testing+from+nowsms&S ender=28444&SMPPOption_mblox_operator=31002&SMPPOption_mblox_tariff=00000 My SMSGW.INI settings: [SMPPOptions] mblox_operator=1402,String,5 mblox_tariff=1403,String,5 mblox_sessionid=1404,String,45 user_message_reference=204,Integer,2 [SMPP - smpp.psms.us.mblox.com:3204] SMPPVersion=v3.4 UserName=xxxxxxxx Password=xxxxxxxx SenderAddress=28444 SenderAddressOverride=No Receive=No ReceiveMMS=No UseSSL=No RoutePrefOnly=Yes LongSMSAlt=Yes ServiceType=3138 Raffi Krikorian Network Telephone Service Serial #00002770 | |||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7613 Registered: 10-2002 |
Hi Raffi, The first time I read this I was completely puzzled. You also contacted Lisa Smith, and I relayed some thoughts back to her. But as I took a closer look at your configuration settings, I now know what the problem is, and the error actually makes perfect sense. What you need to do is go into the SMPP connection definition in NowSMS. Click on "Advanced Settings", and check "Send and Receive Messages over the same connection (SMPP Transceiver)". Press "OK", "OK" and "Apply" to save this change. I suspect this will resolve your problem. Why? Well, it's a particular combination of settings in NowSMS that causes it to bind with a receiver-only connection. We occasionally have customers ask us for this, and the way we implement that capability has tripped you up. If an SMPP connection is defined where "Support any outbound message traffic" is NOT checked ... and the "Preferred SMSC Connection for" list is blank ... then by default this becomes a receive-only connection, unless the transceiver option is enabled. I had completely forgotten about this until I started to write a very detailed reply here about what this error message means. As I thought about the valid situations in which this error should be returned, I thought of the example of a receive-only connection ... and then remembered the combination of settings that we usually tell users when they want to setup a receive-only connection. Sorry I didn't think of that sooner. -bn | |||
Raffi Krikorian New member Username: Rkrikorian Post Number: 2 Registered: 06-2008 |
You nailed it. Checking the "Send and Receive Messages over the same connection (SMPP Transceiver)" solved the problem. Thanks much, Raffi |