How to fix SMSCReceiptMsgID format from hexadecimal to decimal?

How to fix SMSCReceiptMsgID format from hexadecimal to decimal? SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through April 16, 2015 » How to fix SMSCReceiptMsgID format from hexadecimal to decimal? « Previous || Next »
Author Message
lana rel
New member
Username: Lanarel

Post Number: 3
Registered: 01-2015
Posted on Friday, February 06, 2015 - 03:10 am:   

Our client want to get the SMSCReceiptMsgID as decimal but the SMSCReceiptMsgId is now in hexadecimal like this:
SMSCReceiptMsgId=5498306F;
So how can I change its format?

Thanks for reading!
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5195
Registered: 08-2008
Posted on Friday, February 06, 2015 - 01:33 pm:   

Hi,

Sorry, but that is not possible.

When NowSMS delivers a delivery report to an SMPP client, the message ID in the delivery report will always match the message ID from the submit response.

--
Des
NowSMS Support
lana rel
New member
Username: Lanarel

Post Number: 4
Registered: 01-2015
Posted on Monday, February 09, 2015 - 05:49 am:   

Hi Des,

By the way, I figure that sometimes our client system can't get the DR but the log file recorded them all.
I think it's being bottlenecks, is there any retry with DR request back?
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5198
Registered: 08-2008
Posted on Monday, February 09, 2015 - 10:16 pm:   

Hi Lana,

DRs will be queued until the client picks them up.

If there is a connection error delivering the DR, retries will be attempted (default=20).

If the client reports an error in the deliver_sm_resp other than ESME_RTHROTTLED or ESME_RMSGQFUL, no retries will be attempted.

In practice it is very rare for a client to return anything other than success in deliver_sm_resp, so any retries tend to only happen when there are connection errors.

When you say that some DRs are not seen by the client, the only idea that comes to mind is that if SMPP async mode is enabled, a client that does not support async mode will messages (they will be retried, but the NowSMS logs will not show this). Async mode for the SMPP server is not enabled by default. But if you enabled it with the SMPPServerAsyncWindowSize=## setting, that could be the issue.

Beyond that, it can be difficult to troubleshoot client problems. Often it requires using a tool like Wireshark to confirm that the message (or DR) was posted.

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

Post Number: 5199
Registered: 08-2008
Posted on Monday, February 09, 2015 - 10:22 pm:   

I did think of another issue. If multiple clients are connected to NowSMS using the same account name, the DR could be routed back to any client connected with that account name, not necessarily on the same connection.

Oh...and one more note. I am assuming that you are running a relatively recent version of NowSMS. There was an issue fixed in 2013-04-30, where if a client failed to return a deliver_sm_resp, but kept sending enquire link packets, it could block further delivery.

--
Des
NowSMS Support

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