Using SMPP with www.AQL.com - errors

Using SMPP with www.AQL.com - errors SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through February 09, 2012 » Using SMPP with www.AQL.com - errors « Previous || Next »
Author Message
Paul Carmody
New member
Username: Macjasp

Post Number: 1
Registered: 12-2011
Posted on Friday, December 02, 2011 - 01:09 pm:   

Hi,

Not 100% sure where the issue lies with this one but we are using NOWSMS to send SMS to an SMPP server ran by www.aql.com.

This configuration works fine for all our clients - except one.

This particular clients NOWSMS gets rejection notices from the AQL service on a frequent basis, the error being;
==================================================
SMPP failure - Unable to login to SMPP server with specified parameters: ERROR: Invalid username/system id - ESME_RINVSYSID (0x0F)
==================================================

AQL have debugged this and are fairly sure the issue lies with NOWSMS, they gave the following information back to me;

==================================================
Below are the log lines showing the incoming PDUs:

2303 Client (13528) => 01-12-2011 11:33:23: [INFO2] IP Address checked and verified (213.38.213.226)
2304 Client (13528) => 01-12-2011 11:33:23: [INFO2] >> Full outgoing pdu: 000000198000000200000000000000016171736d734f757400

The above 2 lines showed the connection was established. The PUD sent back was 'bind_transmitter_resp' (80000002).

2305 Client (13528) => 01-12-2011 11:33:23: [INFO] << Full incoming pdu: 00000010000000060000000000000002
2306 Client (13528) => 01-12-2011 11:33:23: [INFO2] >> Full outgoing pdu: 00000010800000060000000000000002
2307 Client (13528) => 01-12-2011 11:33:24: [INFO] Exiting ........
2308 Client (13528) => 01-12-2011 11:33:24: [INFO] Successfully shutdown

The above lines show the unbind request sent from you (80000006). That was why the connection was shut down.
==================================================

Can anyone shed any light on this issue and where within NOWSMS we could investigate to hopefully resolve the matter?

Many thanks
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 3648
Registered: 08-2008
Posted on Friday, December 02, 2011 - 01:28 pm:   

H Paul,

They're probably missing the transaction that is problematic when looking at their logs. We wouldn't send an unbind unless there was an established connection (successful bind). However, the error logged indicates a bind is failing.

My guess is that there is a concurrent connection limit that limits how many active binds are allowed by any account. By default, NowSMS tries to establish two binds, a transmitter and a receiver. I suspect one bind succeeds, but the second is rejected because of a concurrent connection limit. Try changing the properties of the connection, under Advanced Settings, to use transceiver mode which uses a single bind for both sending and receiving.

If I have misdiagnosed the issue, enable the smsdebug.log. This will cause an smppdebug.log to be generated, and I'd like to see that to understand the SMPP transaction flow. Feel free to email the log to nowsms@nowsms.com, just put Attention: Des in the subject line. That said, I have high hopes that my transceiver mode guess will resolve the issue.

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

Post Number: 3649
Registered: 08-2008
Posted on Friday, December 02, 2011 - 02:03 pm:   

Hi Paul,

Thanks for sending the logs. Here is what I see.

There are 3 connections to the provider.,.same user credentials, different host names. smpp3, smpp6 and smpp7 host names.

Log shows connection attempt to smpp3. Provider rejects with error code referenced above.

Connection attempt to smpp6. Same error.

Connection attempt to smpp7. Ok

Reconnect attempt to smpp3. Ok

I suspect it may still be a concurrent connection limit at the provider. Keep in mind that some providers have a slight delay after disconnect before they reduce their internal count.

I suspect the providet's analysis did not consider multiple concurrent connections. They looked at there logs and saw one of the successful connects, not one of the failures. I'd suggest you check with them about their concurrent connection limits. Connecting to multiple of their servers simultaneously may be subject to limitations.

--
Des
NowSMS Support

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