Problem on rct file

Problem on rct file SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through May 19, 2016 » Problem on rct file « Previous || Next »
Author Message
storm
New member
Username: Bara9181

Post Number: 21
Registered: 02-2014
Posted on Friday, August 21, 2015 - 07:52 am:   

hi,

I have problem in (.rct) file that its take long time to send to 2-way,but (.in) file direct send to 2-way.

i have this configuration in my SMSGW.ini, and I'M using NOWSMS v.2012.06.28

[SMSGW]
CacheQSize=yes
TrackSMPPReceipts=yes
TrackSMPPReceiptsAlways=yes
2WaySMSThreadCount=100
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5407
Registered: 08-2008
Posted on Friday, August 21, 2015 - 01:09 pm:   

Hi,

Generally, this suggests that there is a problem resolving the upstream message ID. If the message ID can't be resolved, there is a delay in processing it.

If you enable the SMSDEBUG.LOG, I expect you would see statements like this:

Receipt message id = XXXXXXX not in database for SMPP - servername

This problem could occur if you have multiple connections defined in the SMSC list to the same server. Normally, it's not a problem if you have one SMSC link defined with multiple sessions under Advanced Settings. And it's also not a problem if multiple entries are defined and NowSMS recognizes this my appending #2, #3, etc., to the server address. I mention this, because if you do have multiple connections to the same SMSC, this may be a problem...and requires closer inspection of settings.

It may also be a problem if you are connecting to that SMSC from multiple clients using the same account, as delivery reports intended for a different client may be getting routed to NowSMS, and NowSMS has no record of the message.

The only other known issue that might affect the version you are running would be if the provider uses a hex value for the message ID, but a 64-bit integer for the message ID in receipts (suspect if message ID in receipt is a decimal number > 4294967295).

Extremely long message IDs might also be a problem. I don't remember the limit, but if longer than 50 characters, that might be an issue.

Assuming that we're not dealing with one of the above issues, the next step would be to take a closer look at the message ID in the delivery report, which is the text after id:

Look in the SMSOUT-yyyymmdd.LOG and try to manually match the receipt to the original message. The ID in the delivery report should match the SMSCMsgId= value in the log entry. If it does not, what are the values.

--
Des
NowSMS Support
storm
New member
Username: Bara9181

Post Number: 22
Registered: 02-2014
Posted on Friday, August 21, 2015 - 02:17 pm:   

hi,

I have separate the connection , the Sender on server and the receiver on server, dos this what make the problem and how i can solve it before one week it was work with out any problem
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5409
Registered: 08-2008
Posted on Friday, August 21, 2015 - 02:53 pm:   

Hi,

So there are 2 connections in the SMSC list in NowSMS, one send only and one receive only? This can cause a problem because the delivery reports usually come via the receiver connection only.

Are both connections to the same IP address/host name, or are they different?

If the same, NowSMS should automatically handle.

If they are different, there is a way to work-around this with INI settings, but that is best avoided unless there is a strong reason to configure this way.

My recommendation would be to configure one SMSC connection in NowSMS, as baby default NowSMS will create separate transmitter and receiver connections (unless transceiver mode is enabled).

If there is a good reason for configuring like you have (for example, receiver connection requires slightly different parameters), it is possible to link the message ID database for the 2 connections.

This should only be done when you are connecting to an SMSC via multiple addresses where you are certain that the SMSC shares a message ID space across the IP addresses (like what you describe).

To enable this, you need to edit the SMSGW.INI file.

Under the [SMPP - server:port] section header for each connection that shares the same receipt message ID namespace, add TrackSMPPReceipts=somename

"somename" can be any text that makes sense to you. NowSMS will group together receipt message ID tracking for all connections that share the same TrackSMPPReceipts value.

--
Des
NowSMS Support

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