SMPP TLV parameter for PRICEPOINT

SMPP TLV parameter for PRICEPOINT SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through November 14, 2013 » SMPP TLV parameter for PRICEPOINT « Previous || Next »
Author Message
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4632
Registered: 08-2008
Posted on Friday, September 06, 2013 - 12:17 pm:   

This message was received in our support mailbox. I am posting it here to help both the customer asking the questions and to help others who are having questions about configuring TLV parameters:


quote:


Dear Concerned,

As discussed I am configuring NOWSMS gateway for SMS configuration in both way (MO and MT).

And while MT I need to add TLV parameters like (as per DOC by SMSC team):
- PRICEPOINT (0x1400)
- PRODUCT (0x1401)
- PARTNER ROLE ID (0x1402)

While setting TLV parameter in SMSGW.INI file like:
[SMPPOptions]
PRICEPOINT=284335,Integer,tag=0x1400,length=4
PRODUCT=2591,Integer,tag=0x1401,length=4
PARTNER ROLE ID=429,Integer,tag=0x1402,length=4

Getting ERROR:::
Retry Pending - ERROR: Delivery Failure (used for data_sm_resp) -- SMPP -

Pls help me to solve issue.


Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4633
Registered: 08-2008
Posted on Friday, September 06, 2013 - 01:37 pm:   

Hi,

The format of your SMPPOptions settings is not correct. NowSMS will interpret that as if you are trying to define TLV tag numbers 0x284335 0x2591 and 0x429.

To try to clarify some of the confusion about defining TLV parameters, we just published an article yesterday at http://www.nowsms.com/smpp-tlv

As I understand your desired configuration, this is the [SMPPOptions] section that you want to add to SMSGW.INI:

[SMPPOptions]
PRICEPOINT=1400,Integer,4
PRODUCT=1401,Integer,4
PARTNER_ROLE_ID=1402,Integer,4

This section tells NowSMS what TLV parameters are being used and what the data format is for the parameter value. It does not define the values to be used for the parameters.

(Two side notes: Parameter names cannot include space characters, you will notice that I have replaced spaces with underscores in the above settings. Type support for 4 byte integer TLV parameters requires an updated version of NowSMS at http://www.nowsms.com/download/nowsms20130830.zip. You should verify the data format expected by your provider is actually a 4 byte integer. Most providers use String values, even if the strings contain decimal numbers, because strings are easier to encode.)

Now that the TLV parameters have been defined to NowSMS, the next step is to use them.

If NowSMS receives an SMS from the provider via SMPP which includes any of these parameters, accounting callbacks and 2-way commands will automatically have the parameters added to the HTTP request, such as &SMPPOption_PRICEPOINT=284335&SMPPOption_PRODUCT=2591&SMPPOption_PARTNER_ROLE_ID =429

When submitting a message to NowSMS via HTTP, these same parameters can be used to specify that the TLV parameter should be included when submitting the message to the SMPP provider.

If you want to automatically include a TLV parameter in every message without requiring it to be explicitly set for each message submission, it is possible to configure NowSMS to use a default value for this parameter when submitting messages to your SMPP connection.

To define a default value for this parameter, manually edit the SMSGW.INI, and in the section header for an SMPP connection (e.g., [SMPP - ip.address:port]), add a “DefaultSMPPOptions=” setting, where the value of this setting can contain any of the “SMPPOptions” settings.

For example:

DefaultSMPPOptions=PRICEPOINT=284335

Or, if you have multiple SMPPOptions parameters defined that need to be set as default, separate them with a “;”. For example:

DefaultSMPPOptions=PRICEPOINT=284335;PRODUCT=2591;PARTNER_ROLE_ID=429

Keep in mind that this DefaultSMPPOptions setting goes under a section header for an SMPP connection (e.g., [SMPP - ip.address:port]), not under the [SMPPOptions] section where the parameter formats are defined.

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

Post Number: 4634
Registered: 08-2008
Posted on Friday, September 06, 2013 - 01:47 pm:   

As a further point of clarification, Wireshark is a great tool to use to help you confirm that parameters are set the way you expect them to be.

It can also help in seeing how parameters are set in messages that are being received from the provider and help verify that you are using the correct format.

As an example, I configured an SMPP connection on a test server to use the parameters you describe, and here is a Wireshark decode of the resulting packet when submiting via SMPP:



(Note that Wireshark does not know that these TLV parameters are to be interpreted as 4 byte integers, so their values are displayed as a binary hex string.)

If your SMPP submit looks like this one, but you still get errors from your provider, recheck the documentation from your provider to verify TLV parameter formats. As I mentioned earlier, I am suspicious that they might want you to be using string formats instead of integer.

--
Des
NowSMS Support
PREETINDER SINGH
New member
Username: Preet

Post Number: 1
Registered: 09-2013
Posted on Friday, September 06, 2013 - 03:52 pm:   

Hi Expert,

As above wireshark's logs shown by you.
Now same kind of LOG is also showing to me after changing by your side.
Screen short attached herewith...
1st_Screen2nd screen

Now Please suggest TLV params have been added successfully or not.

But till now in SMSOUTXXXXX.log file error is like that...
Retry Pending - ERROR: Delivery Failure (used for data_sm_resp) - ESME_RDELIVERYFAILURE (0xFE).

Pls suggest....
PREETINDER SINGH
New member
Username: Preet

Post Number: 2
Registered: 09-2013
Posted on Friday, September 06, 2013 - 04:06 pm:   

One more thing I want to clear that, while configuration new setup by your side I enabled "UseDataSM=Yes", then before setting TLV parameters, message send by myside and there is entry in SMSOUTXXXXX.log as "OK -- SMPP -".

What it means OK -- SMPP...
What is difference b/w DATA_SM and SUBMIT_SM???

(This is for your kind knowledge that above/earlier shared log of (i.e. wireshark's log) is after remove "UseDataSM=Yes" from SMSGW.INI file..)


Pls specify...
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4635
Registered: 08-2008
Posted on Friday, September 06, 2013 - 04:07 pm:   

The TLV parameters are being set as you have indicated that they should be.

However, are you sure that this is the format that your provider wants them in (4 byte integer)? What documentation do you have from your provider about these parameters? Perhaps that documentation will suggest a different format.

One other detail that I notice is that you appear to be sending from a short code address (4 digit number). However the SMPP submit packet indicates that the sender address is an international number.

By default, NowSMS will encode a sender address of 5 digits or less as a network specific number (TON = 3). So I am wondering if you manually configured the TON to be 1. Your provider might accept a short code sender with TON=1 ... that is up to them ... but normally NowSMS would set TON=3 automatically. So I am suspicious of this.

Other than these suggestions, you would need to ask your provider why they are returning this error.

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

Post Number: 4636
Registered: 08-2008
Posted on Friday, September 06, 2013 - 04:15 pm:   

OK means that the message was accepted by the SMSC. The log entry should also report SMSCMsgId=xxxx which reports the message ID that was assigned to the message by the provider.

Did the provider tell you that you need to use data_sm?

It is not normal for a provider to require the use of data_sm.

It is difficult to explain, but in SMPP, ESME to SMSC normally uses submit_sm format. SMSC to ESME normally uses deliver_sm format.

data_sm is not required to be supported. When it is, it can be used in either direction. It is often used for hub/peer types of connections between SMSCs, or when there are other very specialised requirements.

--
Des
NowSMS Support
PREETINDER SINGH
New member
Username: Preet

Post Number: 3
Registered: 09-2013
Posted on Friday, September 06, 2013 - 04:17 pm:   

As I am getting you that You are asking about length of ORIGINATOR Address XXXXXX (i.e. in 6 digit)

Its changed by manual actually 9876.

According to u what is the problem behind this error occured in SMSOUTXXXX.log.??

Can we share captured wireshark log with operator for more clarifications about TLV parameters. If there is anything wrong, then they update us..

What is ur opinion for above said points.??
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4637
Registered: 08-2008
Posted on Friday, September 06, 2013 - 04:38 pm:   


quote:

According to u what is the problem behind this error occured in SMSOUTXXXX.log.??




Ok ... perhaps you do not understand that this error is not coming from NowSMS?

The error code is coming from your provider. Only they can tell you why they are refusing to accept the message.

We can only make guesses based upon other experiences.

Your provider is returning SMPP error code 0xFE. The only information about this error code in the SMPP specification is "Delivery Failure (used for data_sm_resp)".

That is the actual text from the SMPP specification, and it provides no insight as to why your provider is returning this error. (Perhaps they want you to use data_sm instead of submit_sm. That would be unusual, but perhaps.)


quote:

As I am getting you that You are asking about length of ORIGINATOR Address XXXXXX (i.e. in 6 digit). Its changed by manual actually 9876.




This is just one possibility of something the provider might not like. Often (but not always) providers require source TON = 3 for a short code sender.

NowSMS automatically uses source TON = 3 when a sender address is 5 digits or less. So I was surprised to see source TON =1 for a sender of 9876. It would only be this way if you changed the TON settings for the SMPP connection under "Advanced Settings".

It may be worth clearing all TON and NPI settings in the "Advanced Settings" for the SMPP connection. Then add MaxSMPPShortCodeLen=6 to the [SMSGW] section of SMSGW.INI, so that NowSMS will then use source TON = 3 for a 6 digit source/sender/originator address.

There is low probability that this will resolve your problem. It is just the only unusual point that I notice.


quote:

Can we share captured wireshark log with operator for more clarifications about TLV parameters.




YES. Please do. They are the only ones that can answer why.

My best guess is that they want the TLV parameters in a different format.

--
Des
NowSMS Support
PREETINDER SINGH
New member
Username: Preet

Post Number: 4
Registered: 09-2013
Posted on Friday, September 06, 2013 - 05:39 pm:   

Thanks... I will share log with my providers.
Below mentioned is req. from provider side.
(Provider mailed me that shows under '------')
------------------------
The partner to send us some extra parameters,The extra parameters required are:
- PRICEPOINT (0x1400)
- PRODUCT (0x1401)
- PARTNER ROLE ID (0x1402)
For the TLV have the Length=4 and Type=Integer. Let us know in case of any further doubts.
-----------------------------------

You kindly suggest, If My configuration/parameters are not fulfilling the provider req.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4638
Registered: 08-2008
Posted on Friday, September 06, 2013 - 06:03 pm:   

The Wireshark trace does confirm the TLV parameters encoded in those formats.
PREETINDER SINGH
New member
Username: Preet

Post Number: 5
Registered: 09-2013
Posted on Tuesday, September 10, 2013 - 11:26 am:   

Hi,

As discussed earlier now MT SMS working fine.(Thanks for help.)

But not getting MO message from operator....
Below is SMSGW.INI file..
[SMPP]
[SMPP - XXX.XXX.XXX.XX:XXXXX]
SMPPVersion=v3.4
UserName=XXX
Password=XXXXXXXX
SenderAddressOverride=Yes
Receive=Yes
ReceiveMMS=No
UseSSL=No
UseTLV=Yes
ReceiveSingleConnection=Yes
LongSMSAlt=Yes
SourceTON=1
SourceNPI=1
DestTON=1
DestNPI=1
BindTON=0
BindNPI=0
[SMSGW]
Modem1=SMPP - XXX.XXX.XXX.XX:XXXXX
WebAuth=No
WebMenu=Yes
WebPort=8800
SeparateUserQueues=Yes
ReceiveSMS=Yes
ReceiveMMS=No
PHPEnable=No
PHPAllowRemote=No
ReceiveSMSCommand1=* http://localhost:8080//SubManagerRel/SubManager?param&mdn=@@SENDER@@&dnis=@@RECI P@@&mo=@@FULLSMS@@ No No
ReceiveSMSCharset=utf-8
[SMPPOptions]
PRODUCT=1401,Integer,4
PRICEPOINT=1400,Integer,4
PARTNER_ROLE_ID=1402,Integer,4

- Pls check that NOWSMS is configured in TRX mode.
- URL <<<http://localhost:8080//SubManagerRel/SubManager?param&mdn=@@SENDER@@&dnis=@@R ECIP@@&mo=@@FULLSMS@@>> is working fine as hit by manually.
- Can we check online trace by WIRESHARK etc???????

Pls suggest.........!
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4645
Registered: 08-2008
Posted on Tuesday, September 10, 2013 - 01:23 pm:   

Hi,


quote:

- Pls check that NOWSMS is configured in TRX mode.




Yes, I can see from your configuration settings that NowSMS is configured for one transceiver (TRX mode) connection.


quote:

But not getting MO message from operator....




Does the SMSIN-yyyymmdd.LOG show any activity? If the provider is delivering any messages to you, there would be a record there.

I am assuming this log shows no activity.


quote:

- Can we check online trace by WIRESHARK etc???????




That is a good idea to confirm to yourself that the provider is making no attempt to deliver any messages.

I expect you will only see the following transactions initiated by NowSMS: bind_transceiver , submit_sm and enquire_link_sm.

I expect only the corresponding _resp transactions from SMSC to NowSMS. If the SMSC were attempting to deliver messages, there would be deliver_sm (or data_sm) requests from the SMSC.


quote:

Pls suggest.........!




All you can do is confirm that everything looks right from your side. Looking at the Wireshark trace will confirm that you are in transceiver mode, and that there is no evidence of delivery attempts.

Most likely your provider has to adjust something on their end to route the messages to you.

There is only one setting that might have an impact. Did your provider indicate that you need to specify an "address range" parameter when connecting? It is a very rare requirement, but there are some systems that will not deliver messages unless an appropriate parameter is specified. This is rare ... but double-check the info that your service provider gave you to make sure there is no mention of this.

I suspect your provider needs to do something on their side to enable the message routing.


quote:

As discussed earlier now MT SMS working fine.(Thanks for help.)




Out of curiosity, what was the solution?

Did it just start working after applying the settings, or did you have to talk to the provider?

--
Des
NowSMS Support
PREETINDER SINGH
New member
Username: Preet

Post Number: 6
Registered: 09-2013
Posted on Wednesday, September 11, 2013 - 07:28 am:   

Hi...
I got SMS from provider side and "SMSIN-20130911.LOG" and entry in this file is:

2013-09-11 11:25:27,+XXXXXXXXXXXX,SMPP - BBB.BBB.BB.BBB:AAAAA,Text="Test";Recip=9876

Here +XXXXXXXXXXXX is Mobile number from i got MO.
Here BBB.BBB.BB.BBB:AAAAA is SMSC IP and PORT.

ALso in folder "SMS-IN\20130911\" file created as 522A0432.SMS and value like::
[SMS-IN]
ModemName=SMPP - BBB.BBB.BB.BBB:AAAAA
Sender=+XXXXXXXXXXXX
PhoneNumber=9876
Data=Test


And configured Tomcat's URL as
ReceiveSMSCommand1=* http://localhost:8080//SubManagerRel/SubManager?param&mdn=@@SENDER@@&dnis=@@RECI P@@&mo=@@FULLSMS@@ No No

- but TOMCAT URL is not called while MO GOT by NOWSMS.
- Total of 15 files in "SMS-IN\20130911\" i.e. 15 MO got from provider.

Pls help me to solve same ASAP...
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4646
Registered: 08-2008
Posted on Wednesday, September 11, 2013 - 11:21 am:   

OK ... that is easier to troubleshoot.

As the files have a .SMS extension, this means that NowSMS thinks there is no matching 2-way command.

Rename the files with a .IN extension. Do they get processed by the 2-way command or renamed back to a .SMS extension?

If they get renamed back to a .SMS extension, my guess is that the editor you used to manually edit SMSGW.INI replaced tab characters with whitespace characters...which causes problems for parsing the 2-way command. (NOTEPAD is a safe editor.)

Manually delete that line from the SMSGW.INI. Then add the command back in with the configuration UI.

Rename .SMS files to .IN to trigger reprocessing.

--
Des
NowSMS Support
PREETINDER SINGH
New member
Username: Preet

Post Number: 7
Registered: 09-2013
Posted on Wednesday, September 11, 2013 - 11:47 am:   

Sorry, I am not getting you..
I only tried following>>>
Have Changed SMS-IN\20130911\522A0432.SMS to 522A0432.IN..

It got changed with 522A0432.SMS.

Pls explain in details...
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4648
Registered: 08-2008
Posted on Wednesday, September 11, 2013 - 11:49 am:   


quote:

If they get renamed back to a .SMS extension, my guess is that the editor you used to manually edit SMSGW.INI replaced tab characters with whitespace characters...which causes problems for parsing the 2-way command. (NOTEPAD is a safe editor.)

Manually delete that line from the SMSGW.INI. Then add the command back in with the configuration UI.




For clarification:

Step 1- Remove ReceiveSMSCommand1 line from SMSGW.INI

Step 2- Add 2-way command back in with configuration program

Step 3- Rename .SMS files to .IN to trigger reprocessing.
PREETINDER SINGH
New member
Username: Preet

Post Number: 8
Registered: 09-2013
Posted on Wednesday, September 11, 2013 - 12:05 pm:   

Hi.. Yes Its working now..
Thanks..
One more issue regarding MT MESSAGE....

When I am sending MT MESSAGE having "300 characher" its send by my APP to NOWSMS with in single URL, but in SMSOUTXXXXX.log
Entry like that>>(in two lines..)
2013-09-11 16:55:26,SAR-XXXXXXXXXXXX-522a1ba4-2-1,112.196.2.204,XXXXXXXXXXXX,OK -- SMPP - AAA.AAA.AA.AAA:BBBB,Sender=9876;SMSCMsgId=0;UDH=0500033C0201;Text="UUUUUUUUUUUUU UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU"
2013-09-11 16:56:00,SAR-XXXXXXXXXXXX-522a1ba4-2-2,112.196.2.204,XXXXXXXXXXXX,OK -- SMPP - AAA.AAA.AA.AAA:BBBB,Sender=9876;SMSCMsgId=571569895;UDH=0500033C0202;Text="UUUUU UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU"

IP:AAA.AAA.AA.AAA:BBBB
MDN:XXXXXXXXXXXX
MESSAGE:UUUUUUUUUUUUU

What it means??
Is there two different messages sent from my side or a single msg???

Pls suggest...!
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4649
Registered: 08-2008
Posted on Wednesday, September 11, 2013 - 12:28 pm:   

Hi,

SMS messages have an over the air limit of 160 text characters (or 140 binary bytes, or 70 16-bit Unicode characters). Longer messages are segmented and then reassembled by the receiving device.

The following article provides more detail:

http://www.nowsms.com/long-sms-text-messages-and-the-160-character-limit

--
Des
NowSMS Support
PREETINDER SINGH
New member
Username: Preet

Post Number: 9
Registered: 09-2013
Posted on Wednesday, September 11, 2013 - 12:37 pm:   

If same will be reassembled by receiving device, then customer/user got single message or double message.
example>
1. I sent below said message.
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
(This is a message and XXXXX part is of 160 character and AAAA part is also 160 ch.)
2. Then MY NOWSMS will forwarded in two parts.

3. Operator/providers will reassemble same at their end.

4. Finally User will received two message or a single message in case of above example????????????????
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4651
Registered: 08-2008
Posted on Wednesday, September 11, 2013 - 02:02 pm:   


quote:

If same will be reassembled by receiving device, then customer/user got single message or double message.




A single message is presented to end user. The device, however, actually receives multiple messages.

This is true as long as the segmentation parameters can be properly transmitted across all interim SMSC links. (Note: If sending to a CDMA network, such as Verizon in the US, multiple messages will be received because CDMA does not support segmentation parameters.)


quote:

1. I sent below said message.
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
(This is a message and XXXXX part is of 160 character and AAAA part is also 160 ch.)
2. Then MY NOWSMS will forwarded in two parts.

3. Operator/providers will reassemble same at their end.

4. Finally User will received two message or a single message in case of above example????????????????




1 - OK
2 - OK
3 - Operator / providers will NOT reassemble message. (They might reassemble, and then split it again before delivery ... but that is extra/unnecessary work.)
4 - Device ALWAYS receives multiple messages. Software in device recombines to present as a single message.;

It is not clear to me whether you are experiencing a problem, or just discussing theory.

If you receive multiple separate messages when sending a long message:

Your INI file above suggests that under "Advanced Settings" for the SMPP connection you have enable "Use TLV parameters for port numbers and segmentation". (The default is for this setting to be disabled.)

If the recipient is seeing multiple messages, this probably means that your provider does not support TLV parameters for segmentation. Disable this setting and NowSMS will use GSM UDH for segmentation, which is what most SMS providers expect. (This setting is independent and separate from SMPPOptions, so you can disable this setting and still have your extra TLV parameters.) Note that the NowSMS logs always show UDH segmentation. If TLV segmentation is enabled, UDH is converted to TLV in the raw SMPP packet.

(For completeness: There is also an option where NowSMS will not segment the message and will submit the long message in a single transaction using a parameter called message_payload. Few SMS providers support this, but if you need to use it, check "Enable WDP Adaptation..." and UNcheck "Use TLV parameters for port numbers and segmentation". NowSMS logs will still show multiple messages, but the SMPP request will be a single long message. Note that in this scenario, the SMSC must segment the message into multiple messages to deliver to the receiving device.)

--
Des
NowSMS Support
PREETINDER SINGH
New member
Username: Preet

Post Number: 10
Registered: 09-2013
Posted on Monday, September 16, 2013 - 05:33 am:   

Hi Expert,

As no my NOWSMS is working fine, but after 12-15 hours, might be their connectivity with SMSC goes down and then I manually stop then start the gateway via GUI and same time provider will mailed me that "Your connectivity is down".

Is there any schedule/criteria to refresh the connection.??

pls suggest.!!!
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4653
Registered: 08-2008
Posted on Monday, September 16, 2013 - 02:24 pm:   

NowSMS sends an SMPP enquire_link request (if there is no other traffic) every x seconds, as configured under the "Advanced Settings" as "Keep-alive interval".

The default for this setting is 58 seconds (or just under a minute).

The server is expected to reply back with an enquire_link response, which is how both parties know the connection is still valid.

If a response is not received, NowSMS closes the connection and reconnects automatically..

So if your connectivity goes down ... the question is ... how are you determining that it has gone down? You start getting errors when sending messages? You stop receiving messages?

If this is happening regularly, it'd be a good idea to enable the SMSDEBUG.LOG (which also enables the SMPPDEBUG.LOG, which is the file we are interested in). When you have determined the connection is dead, we'd like to see the SMPPDEBUG.LOG and SMPPDEBUG.BAK to see the activity and better understand what is happening. (You can e-mail these files to nowsms@nowsms.com. Please put the text "Attention: Des" in the subject line, and also post a reply here to tell me to go look for the e-mail.)


BEFORE doing this, I'd like you to try one setting. Edit SMSGW.INI (using Notepad to avoid the problem you experienced before) and under the [SMSGW] header, add SMPPNoDelay=Yes ... then restart the NowSMS service. This is a setting that stops buffering on the SMPP connection, and I suggest trying this in case this buffering is confusing the SMPP server.

--
Des
NowSMS Support
PREETINDER SINGH
New member
Username: Preet

Post Number: 11
Registered: 09-2013
Posted on Thursday, October 24, 2013 - 01:54 pm:   

Hi Concerned,

I am getting TPS issue with configured NOWSMS GW.

- Alloted TPS is 10 from service provider.
- Getting huge Pendency in Quesue folder i.e. "C:\Program Files (x86)\NowSMS\Q\".
- Sample Config file is as follows b/w Stars>>>
**********************************************************
[SMPP - IP:PORT]
SMPPVersion=v3.4
UserName=XXXXX
Password=XXXXXX
SenderAddressOverride=Yes
Receive=Yes
ReceiveMMS=No
UseSSL=No
ReceiveSingleConnection=Yes
LongSMSAlt=No
[SMSGW]
Modem1=SMPP - IP:PORT
WebAuth=No
WebMenu=Yes
WebPort=8800
ReceiveSMS=Yes
ReceiveMMS=No
PHPEnable=No
PHPAllowRemote=No
ReceiveSMSCharset=utf-8
ReceiveSMSCommand1=* http://localhost:8080/SubManagerRel/SubManager?param&mdn=@@SENDER@@&mo=@@FULLSMS @@&dnis=@@RECIP@@ No
[SMPP]
*******************************************************************
SMSOUT FILE>>>>>>>
2013-10-24 15:34:25,5239A9F7,10.10.10.11,MSISDN,OK -- SMPP - MESSAGE"XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX "
2013-10-24 15:34:25,5239A9F8,10.10.10.11,MSISDN,OK -- SMPP - MESSAGE"XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX "
2013-10-24 15:34:26,5239A9F9,10.10.10.11,MSISDN,OK -- SMPP - MESSAGE"XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX "
2013-10-24 15:34:26,5239A9FA,10.10.10.11,MSISDN,OK -- SMPP - MESSAGE"XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX "
2013-10-24 15:34:27,5239A9FB,10.10.10.11,MSISDN,OK -- SMPP - MESSAGE"XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX "
2013-10-24 15:34:27,5239A9FC,10.10.10.11,MSISDN,OK -- SMPP - MESSAGE"XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX "
2013-10-24 15:34:28,5239A9FD,10.10.10.11,MSISDN,OK -- SMPP - MESSAGE"XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX "
2013-10-24 15:34:28,5239A9FE,10.10.10.11,MSISDN,OK -- SMPP - MESSAGE"XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX "
2013-10-24 15:34:29,5239A9FF,10.10.10.11,MSISDN,OK -- SMPP - MESSAGE"XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX "
2013-10-24 15:34:29,5239AA00,10.10.10.11,MSISDN,OK -- SMPP - MESSAGE"XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX "
(In above sample XXXXX and MSISDN by my side manulay)

Getting 2 TPS as per above shared logs.

Waiting your quick responce...
PREETINDER SINGH
New member
Username: Preet

Post Number: 12
Registered: 09-2013
Posted on Thursday, October 24, 2013 - 02:31 pm:   

Dear Concerned,

I am waiting your revert... There is urgent requirement..

Pls help me for TPS issue...
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4703
Registered: 08-2008
Posted on Thursday, October 24, 2013 - 09:02 pm:   

Hi,

Do you have a licensed copy (with serial number) or is this a trial version?

If this is a trial version, there is a limit of around 30 messages per minute. We will issue test licenses to allow testing of higher speeds. However, you need to contact our sales department for a temporary higher speed license.

Contact information for our sales department can be found at http://www.nowsms.com/contact ... if you contact our sales department via e-mail or via the web form, I suggest you include your full contact details and the "installation reference code" that is displayed on the "Serial #" page of NowSMS. Explain that you need a temporary license to test a higher speed connection and your 10 TPS target.

(Note that after applying a license, it is necessary to restart the NowSMS services to activate it.)

If you already have a license (purchased or temporary type), and you are not seeing the licensed speed, then with some SMSC connections it is necessary to enable async mode in NowSMS.

To do this ...

In NowSMS, go to the SMSC page. Highlight the SMSC connection and press "Properties".

In the SMPP settings page, press "Advanced Settings". Enable async mode at the bottom of that screen and set a window size of 10. Press OK twice. You do not have to test the SMSC connection and can answer "No" if prompted to test the SMSC connection.

VERY IMPORTANT ... when back at the SMSC list, press "Apply" to activate these changes.


If you're still not seeing 10 TPS, then your provider may not have applied limits for your account correctly. But we can take a closer look to determine what type of SMSC response is occurring. On the "Serial #" page ... enable the SMSDEBUG.LOG. Repeat your sending test, then e-mail the SMSDEBUG.LOG and SMPPDEBUG.LOG to nowsms@nowsms.com ... be sure to put Attention: Des in the subject line of the e-mail and post a reply here to tell me you have sent a log that I need to look at.


--
Des
NowSMS Support

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