ESME_RSYSERR

ESME_RSYSERR SearchSearch
Author Message
Gagandeep
New member
Username: Egagand

Post Number: 1
Registered: 01-2011
Posted on Friday, January 21, 2011 - 11:21 am:   

Hi

I am gettign ESME_RSYSERR on submitSM. what is the reason and how can i rectify this error.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 2841
Registered: 08-2008
Posted on Friday, January 21, 2011 - 04:02 pm:   

Hi,

You need to ask your SMPP provider.

Most likely you are not specifying one of the parameters that they require.

The most likely problem is that you are using a sender address that they do not support. Did you configure a Default Sender Address for the connection when defining it in NowSMS. If not, do so and use a sender address that your provider will support.

What parameters did your provider tell you to use for the SMPP connection? Did they mention any unusual parameters such as system type or service type settings?

--
Des
NowSMS Support
Gagandeep
New member
Username: Egagand

Post Number: 2
Registered: 01-2011
Posted on Saturday, January 22, 2011 - 06:01 am:   

I am using short code in senders address, For rest of the parameters I will get back to you after checking this with my Provider.

Thanks..!
Gagandeep
New member
Username: Egagand

Post Number: 3
Registered: 01-2011
Posted on Saturday, January 22, 2011 - 11:36 am:   

Please see the submitSM packet and it response which has a failure message. Does it require any modification..?
mac/unknown
RelienceSubmitSm.snoop (3.6 k)
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 2853
Registered: 08-2008
Posted on Tuesday, January 25, 2011 - 09:35 pm:   

I didn't originally notice that you posted this in the unsupported area, so my initial response assumed you were using NowSMS.

Seeing that you are not using NowSMS, here are some observations:

1.) The message content is null. It would not be unusual for a provider to reject a blank message.

2.) The source TON is 0. Some providers require a different TON value when using a short code. (Refer to provider documentation for more information.)

3.) I also notice that you are using a validity_period parameter. It appears to be formatted correctly, but just in case your provider does not support it, you should try without it.

4.) If your provider requires system_type or service_type settings, that could be an issue. (It would be unusual, but some require additional parameters as an additional level of security.)

--
Des
NowSMS Support