Messages stuck with status=queued

Messages stuck with status=queued SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through April 11, 2011 » Messages stuck with status=queued « Previous || Next »
Author Message
Mustafa Rangwala
New member
Username: Mrangwala

Post Number: 1
Registered: 01-2011
Posted on Thursday, January 13, 2011 - 08:17 pm:   

I have 2 NowSMS instances. Instance 1 is connected to the SMSC and receives SMSs. For Some shortcodes it forwards to the 2nd NowSMS instance that is connected to the first as a SMPP Client.

The 2nd NowSMS instance also acts as a SMPP server and my custom SMPP client binds to the 2nd NowSMS instance. I have a SMS User defined, and have setup the forwarding rule based on phone number to this user. I am use this user to bind to the 2nd NowSMS instance.

The problem is that the 2nd NowSMS instance always shows status of received messages from the 1st NowSMS as queued. It does not send the message on to my SMPP client. To make sure my client is written correctly, I tried binding from my client to the 1st NowSMS instance. In this configuration my client gets the messages.

The 2nd NowSMS is the latest download, while the 1st one is I think Oct 2010.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 2826
Registered: 08-2008
Posted on Thursday, January 13, 2011 - 09:20 pm:   

I'm not sure what you mean by instance, but it sounds like you have more than one copy of NowSMS installed on the same machine. That is NOT a supported configuration.

I'm not sure what you're trying to accomplish, but generally NowSMS is flexible enough to support multiple clients and servers without multiple installations. If you are trying to simulate a more complex scenario, it will require multiple machines (or virtual machines).

--
Des
NowSMS Support
Mustafa Rangwala
New member
Username: Mrangwala

Post Number: 2
Registered: 01-2011
Posted on Friday, January 14, 2011 - 01:53 pm:   

I have two machines. The first machine runs the primary NowSMS and binds to the a SMSC. The primary NowSMS handles all messages, and based on some shortcodes forwards to the secondary NowSMS.

My client binds to the secondary NowSMS using credentials established in the secondary NowSMS. In the SMS User tab of the secondary NowSMS, I have it setup to forward messages using SMPP based on shortcode to that user (aka my client).

The primary NowSMS is able to forward the messages to the secondary. The secondary NowSMS does not seem to forward the messages to my client though. The 2way tab's view button shows that all the messages are in queued status.

To ensure that my client is coded correctly, I tested it against the primary NowSMS with the credentials used by the secondary NowSMS. Disconnected the secondary NowSMS, and in this setup, my client receives the messages from the Primary NowSMS correctly.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 2827
Registered: 08-2008
Posted on Friday, January 14, 2011 - 05:26 pm:   

Is "Process Received SMS Messages" option checked on the "2-way" page?

If so, messages received inbound from an SMSC connection will not get routed to any local user accounts.

--
Des
NowSMS Support
Mustafa Rangwala
New member
Username: Mrangwala

Post Number: 3
Registered: 01-2011
Posted on Friday, January 14, 2011 - 05:28 pm:   

No, it is not checked. The relevant settings are:

a) SMS User has the Forward using SMPP option
enabled with a specific shortcode
b) The SMSC properties has the 'Receive' SMS enabled, but the Route to Local User is not specified there.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 2828
Registered: 08-2008
Posted on Friday, January 14, 2011 - 06:05 pm:   

I'm sorry, there was a typo in my previous reply.

Instead of "If so", it should read "If not"... in other words, this is what I meant to type:


Is "Process Received SMS Messages" option checked on the "2-way" page?

If NOT, messages received inbound from an SMSC connection will not get routed to any local user accounts.


To be clearer, make sure that setting is checked.

--
Des
NowSMS Support
Mustafa Rangwala
New member
Username: Mrangwala

Post Number: 4
Registered: 01-2011
Posted on Friday, January 14, 2011 - 07:58 pm:   

Hmm, this is odd. If I check this box then I am expected to provide a script/command to Process the message. In our case the client is a SMPP client and therefore there is no script/command to process the received messsage. I don't believe I have this option checked in the primary NowSMS and it correctly forwards to the secondary NowSMS (which is acting as a SMS user).
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 2829
Registered: 08-2008
Posted on Friday, January 14, 2011 - 08:06 pm:   

It may be odd, but that is how it works.

You can leave the list empty.

The logic that routes inbound messages (received from an SMSC connection) to local user accounts is only enabled if this box is checked.

Perhaps on the other system it is outbound messages that are being routed to a local user account.

Login Login / Register Logout Logout Search Last 30 Days Topics Topics