Issue around Transmitter only vs Receiver binds | Search |
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through January 22, 2009 ⬆ |
◄ ► |
Author | Message | |||
Sean Swift New member Username: Sswift Post Number: 1 Registered: 10-2008 |
Hello! I have an SMPP bind configured as a transmit only (the "route to user" check box is unchecked), but when the service starts, it connects as a receiver. This causes our vendor to send messages to this server, but it is not configured to properly route the messages. I'm using the latest 2008 version that is available for download, and I did a clean install with just the one bind configured. I verified the connection type by doing a packet capture. Here's the weird thing. If I "test" the connection before starting the service, the packet capture shows it as a transmitter bind. But then if I start the service, it comes up as a receiver in the packet capture. Any help would be appreciated. | |||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7667 Registered: 10-2002 |
Hi Sean, This happens if the bind is configured with the following settings: 1.) "Support any outbound message traffic" is NOT checked. 2.) The "Preferred SMSC Connection for" list is empty. 3.) Under "Advanced Settings", "Send and Receive Messages over the same connection" is NOT checked. Technically, before it configures itself as a "receive only" bind, NowSMS should also require "Receive SMS Messages" to be checked. (As described at the following link http://blog.nowsms.com/2008/07/smpp-connection-types-sender-receiver.html) However, it does appear to be a bug. If any of the three conditions above are met, then NowSMS establishes the bind as receive only. It should require the fourth condition, but apparently it does not. You can work around this by putting the text "explicit" in the "Preferred SMSC Connection for" as described in the link that I referenced above.) -bn | |||
Sean Swift New member Username: Sswift Post Number: 2 Registered: 10-2008 |
Yep, that worked! The other thing I would consider a bug is that when you "Test" the connection, it's behaving differently than when the service actually starts. The "Test" isn't really a test if it's using some other configuration for the connection. Thanks for the help! Sean | |||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7671 Registered: 10-2002 |
Hi Sean, Glad to hear that resolved the issue. You're right ... technically the test should behave just like the service. That is the intent. Unfortunately, there have been some subtle differences over the years. I thought we had found them all, but apparently not. This is scheduled to be corrected in the next update. -bn | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 172 Registered: 08-2008 |
Follow-up posting ... This behaviour has been corrected in an interim update for NowSMS that is available for download at http://www.nowsms.com/download/nowsmsupdate.zip.
-- Des NowSMS Support |