Performance problem

Performance problem SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through October 19, 2005 » Performance problem « Previous || Next »
Author Message
MBJ
Unregistered guest
Posted on Thursday, March 24, 2005 - 08:41 am:   

Hello,

We use NowSMS for performance (response time, availability, etc.) tests since a year and we bought 2 licences of the v5.01 version. During the first 6 months everything was ok, and we were very happy with this product. After that, a telecommunication equipement was replaced by our operator with more faster one. Since that time, we have an important problem with nowSMS which receive SMS notification after a very long time (sometimes more than 15 minutes). I worked on that with our engineer team who took some log from the MMS platform. After their investigation, they told me that this problem has no relation with the MMS platform. They think that it is due to nowSMS who keep the ressources too long, and as the first notification arrives too fast with this new platform, we have to wait a very long time for the next re-sending of this first notification by the platform.
We have also another problem : we use MM1 and sometimes after the MMS was send the RAS connection is still maintained and we have to disconnect it manually.
Thank you, and we will be really happy if you could help us to resolve these problems.

Best regards.
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 4213
Registered: 10-2002
Posted on Thursday, March 24, 2005 - 09:16 pm:   

Hi MBJ,

I need more information on your configuration.

I assume that you are using a GPRS modem for the connection?

What GPRS modem?

Generally speaking, it wouldn't be NowSMS that is not seeing the notification because it is coming too fast ... it would be the modem.

I'd also like some clarification on the following statement: "They think that it is due to nowSMS who keep the ressources too long" ... what resources are they referring to?

Regarding the RAS connection staying open ... there are configurations where NowSMS will keep a RAS connection open indefinitely (for performance reasons). But this only happens when you configure an MM1 connection and the "Modem Used" field is blank ... or refers to a modem that is not configured in the "SMSC" list to receive SMS messages. In such a scenario, NowSMS will keep the GPRS/RAS connection open. It will only close the connection if it detects that there is some other reason that it needs to close the connection, such as if it needs to receive SMS messages over the modem.

-bn
MBJ
Unregistered guest
Posted on Friday, March 25, 2005 - 04:36 pm:   

Hi Bryce,

Thank you very much for your answer. Here's my 4 answers and 2 another questions.

**ANSWERS**

1)I assume that you are using a GPRS modem for the connection? --> It's a classic Windows RAS Connection.
2)What GPRS modem? --> Wavecom FASTRACK GSM/GPRS modem.
3)... what resources are they referring to? --> While sending an MMS a radio data chanel is open, at the end this channel isn't immedialtly closed. As the new equipement (which is the server that runs the notifivations) is very fast, the logs of our SMS platform show that while trying to send the first SMS notification, the modem isn't found in the network. So, may be NowSMS which manages all RAS connection don't react as fast as the first notification is sent by the platform.
4)Regarding the RAS connection staying open ... --> in the MM1 configuration section of MMSC the "Modem Used" field contains the right modem used which is the same configured in the "SMSC" list.

**QUESTIONS**

1)We downloaded the newest NowSMS version, and we wasn't able to receive MMS with it, we always receive an SMS saying "Please contact your service customers". When we had use the v5.01 of NowSMS just after that we didn't meet this problem. Is there any problem of USER AGENT ? How to configure it while receiving MMS (AS I know when using MM1, no USER AGENT is transmitted.

2)Attached to this post, the MMSC-20050324 file. We haven't understand what happened from 02:59:25 to 03:36:10. We have never seen that.

Think you very much for your help,
MBJ.
text/plain
MMSC-20050324.txt (1.2 k)
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 4239
Registered: 10-2002
Posted on Monday, March 28, 2005 - 07:53 pm:   

The modem should still receive (and buffer) the SMS for the MMS notification, even though the modem is in GPRS mode.

NowSMS would not see the SMS that contains the MMS notification until it had dropped the GPRS connection. But the modem should be buffering it.

Try putting this into the appropriate modem section of SMSGW.INI, and see if it makes a difference:

CommandPreInit0=AT+CNMI=0,0

(Admittedly, this is a strange command to specify for "pre-init". But a quirk of the implementation is that the command will also be sent before we release the modem for the GPRS connection. And this command would explicitly tell the modem to buffer the SMS that contains the notification.)

This whole issue of mode switching between GPRS mode and SMS mode is one reason why I really like the Sierra Wireless Aircard (which is unfortunately only available in a PC card factor, and can only have one instance per computer). It can keep both channels open at the same time. The GPRS connection is always live, and we can keep receiving the SMS part of MMS notifications at the same time. It completely avoids this mode switching and potentially missed notifications problem.

Regarding 4-Answer ... and the modem in the "SMSC" list is configured to receive SMS messages? I assume it must be.

I'd probably have to see debug logs for when we are not releasing the connection in order to understand. It is possible that it may be the RAS subsystem that is delaying the disconnect, but I'd have to see debug logs (both MMSCDEBUG.LOG and SMSDEBUG.LOG) to understand.

Regarding new questions:

1.) I cannot see how a newer version would have any impact on this.

But then again, I do not know where you are seeing "Please contact your service customers".

2.) I'm sorry, but I don't know what you're asking. Are you asking about the FAILED entries at 03:33:19 and 03:36:10? I'd probably have to see an MMSCDEBUG.LOG (and MMSWAPDEBUG.LOG) to have any hope of understanding what is going on.

If you don't want to post the logs publicly, you can e-mail them to nowsms@now.co.uk, mark them "Attention: Bryce" in the subject line, and reference this thread so that I have some context of why I'm looking at the logs.

-bn
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 4240
Registered: 10-2002
Posted on Monday, March 28, 2005 - 07:55 pm:   

Regarding the MM1 User-Agent question ...

See bullet #10 at the following link:

http://support.nowsms.com/discus/messages/53/5898.html
MBJ
Unregistered guest
Posted on Friday, April 01, 2005 - 12:32 pm:   

Hi,

Think tou again for these information. I added "CommandPreInit0=AT+CNMI=0,0" in smsgw.ini under eache modem section and nothing has changed. But I'm wondering something. You told me that this problem is due to a bad switching between GPRS and GSM mode, and our modems are completely controllable with AT commands, so is there any way to access modems and force them to detach from GPRS newtwork (with "at+cgatt=0" and "at+cgact=0"), because when NowSMS and NowMMSC services are launched COM ports are opened so we have no way to send AT Commands.

Thank you.
MBJ
Unregistered guest
Posted on Tuesday, April 05, 2005 - 07:02 am:   

Hi,

One more thing, do you think updating modem firmware will change anything ?
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 4301
Registered: 10-2002
Posted on Sunday, April 10, 2005 - 11:54 am:   

You can do some control of sending AT commands through SMSGW.INI file parameters. Here is the info:

Adding additional modem initialisation commands:

In the appropriate modem section of the SMSGW.INI file, the following configuration parameters are supported:
CommandPreInit#=modem commmand
CommandPostInit#=modem command
CommandPreSend#=modem command
CommandPostSend#=modem command
Substitute # with a number, starting at 1, and increasing sequentially for each additional command to be sent. CommandPreInit is sent before NowSMS performs its modem initialisation sequence. CommandPostInit is sent after NowSMS performs its modem initialisation sequence. CommandPreSend is sent before NowSMS attempts to send a message using the modem. CommandPostSend is sent after NowSMS attempts to send a message using the modem. Examples:
CommandPreInit1=ATZ
CommandPreInit2=ATE0V1
CommandPreInit3=AT+CSMS=0

I'm not sure that any +CGATT or +CGACT commands will make a difference. The problem looks to me like an issue that when we activate a PDP context to send or receive an MMS message, the modem will not receive SMS messages (used for notification) while the PDP context is active. I suggested the AT+CNMI=0,0 to tell the modem to save received messages to the SIM (or device memory), but not try to route them directly to NowSMS while the GPRS connection is active. I thought that might be a solution if the modem was getting confused trying to route a received SMS to the application while there was an active data connection.

A firmware update couldn't hurt. I do believe it is the modem that is not accepting the SMS message of the notification.

-bn
Anonymous
 
Posted on Friday, July 29, 2005 - 11:07 am:   

why is that sometimes when we send one sms to a person, the receiver gets multple copies of the same sms....when only we had sent it once.
Kuntal
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 4714
Registered: 10-2002
Posted on Friday, July 29, 2005 - 02:51 pm:   


quote:

why is that sometimes when we send one sms to a person, the receiver gets multple copies of the same sms....when only we had sent it once.




I don't know. I would need more details on your configuration.

And it would probably help to have an SMSDEBUG.LOG enabled, although there is probably some information that could be obtained from the standard SMSOUT-yyyymmdd.LOG files.

I suspect that the SMSOUT log files will show sending retries, and the log entries should indicate the error condition that triggered a retry.

Basically, what it sounds like is happening is that NowSMS is submitting a message to the SMSC connection ... the SMSC connection is returning an error back to NowSMS, but it is still sending the message.

This type of scenario happens most often with GSM modems, where the modem times out waiting for a response back from the SMSC. I'm not talking about a timeout in the modem firmware, not a timeout that NowSMS can control. In this case, you'd most likely see "CMS ERROR 500" in the logs. And the situation might be caused by a weak GSM signal which might be resolved by either physically relocating the modem or connecting an external antenna.

-bn

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