InetLab - Mobile Internet Solutions

could you show log file of query response?

Please also read this topic
http://www.inetlab.ru/support/viewtopic.php?t=656

sorry for delay,
this error displays the reason of connection problem.

Do you have something before
2010/2/6 9:07:02 AM: SmppClient disconnected

?

What version do you use now?

1. is only for SMSC side 2. implemented. When client did not send any requests or did not received any response within specified period it sends enquire_link packet to the server. 3. not implemented. Client always tries to support active session. 4. true only for synchronous methods when client wait...

please attach to event evError, it has to show you the reason of disconnection

Applications that require more than 160 characters of information transfer can use the message_payload parameter which can hold up to a maximum of 64K. However, the maximum size supported is SMSC dependent and the application should take this into account. Another available method for sending more ...

command status error codes 0x00000100-0x000003FF are reserved for SMPP extension.

I think you need to ask SMPP server side.

Last error message is normal behaviour when SMPP server drops connection.

Now i'm investigating cases of disconnects without evError.

what in the evError event you got?

fixed in version 2.8.2

Note that you can also get message Id using code

Code: Select all

TLV receiptedMessageId = data.Optional[OptionalTags.ReceiptedMessageId];
if (receiptedMessageId != null)
{
      string messageId = SmppClient.GetMessageText(receiptedMessageId.Value, DataCodings.ASCII);
}

Hi rom,

Can you post here received bytes from the event evReceiveData ?

4097 (0x1001) code returns when SmppClient is not able to parse reposnse from SMSC. In this case please post here bad response and I'll try to find the reason. Event evReceiveData will help you to get SMPP response before parsing.

Please could you try last version 2.8.1.

ESME_RBINDFAIL error occurs when an access has a limit of concurrent connections. Because of network problems SMPP server still think that client is connected and does not allow to bind with second connection.

It is the same situation as it was in
http://www.inetlab.ru/support/viewtopic.php?t=618

Your SMSC sends packet with two fields sm_length
first value 0x8d and second 0x8c

What SMSC side said about this situation?

Hi Raksa,

Correct. Method SendTextAsync() much faster then SendText().

SendText waits for response from SMSC.

SendTextAsync does not wait for response from SMSC, but response still can be retrieved in the event evSubmitComplete.

Search found 987 matches