NowSMS session timeout help needed

NowSMS session timeout help needed SearchSearch

SMS & MMS Technical Forum » NowSMS Support - MMS & Advanced Issues (Product Support Only) » Archive through July 14, 2004 » NowSMS session timeout help needed « Previous || Next »
Author Message
Dan Johnston
New member
Username: Dan

Post Number: 1
Registered: 04-2004
Posted on Tuesday, April 13, 2004 - 02:11 am:   

Hello all.
I am new to NowSMS and this is my first posting. I am looking for help regarding a session timeout that I can control on the NowSMS server. I am not even sure if it exists or not but I have found a similar setting for WAP3GX.
With the WAPGW.INI file I can add SessionTimeout=(Num of minutes) to override the default 10 wait before a timeout occurs. I would like to know if a similar setting exists with NowSMS and if so, how to set it.
Thank you for any help you can spare.
robby zulkarnain
Unregistered guest
Posted on Thursday, April 15, 2004 - 04:46 pm:   

hi,
i am using motorolla c350. i have registered to my celluler operator how to activate my gprs and mms. now the gprs signal was work already, but the mms is not. is there somebody could tell me why? or maybe do i have to set my phone first?, for my mms? then how to set it up? please tell me.

many thanks
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2310
Registered: 10-2002
Posted on Monday, April 19, 2004 - 02:10 pm:   

Hi Dan,

There isn't a concept of a session in NowSMS, so I'm curious what behaviour you are wanting to change.

When you are using the web interface to submit messages, it might look like there is a session, but the browser sends an "Authorization:" header with each request to authenticate.

It works similar for the MMSC (where authentication is handled either by username=password in the URL, or from an X-MSISDN header from the WAP proxy).

If I'm not understanding what you're asking, please feel free to clarify.

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

Post Number: 2311
Registered: 10-2002
Posted on Monday, April 19, 2004 - 02:18 pm:   

Robby ...

You can download a manual for the Motorola C350 at the following link:

http://commerce.motorola.com/consumer/QWhtml/manual.html

Page 57&58 explain where you configure the settings for the browser. This is where your GPRS WAP settings would be configured ... note that the actual settings are mobile operator dependent, so you would need to check your mobile operator's web site.

As for MMS, well, I don't see any mention of MMS support in the manual.

And, as I check other web sites, I see that the Motorola C350 does not support MMS ... so that could present a formidable challenge to your getting it to work.

-bn
Dan Johnston
New member
Username: Dan

Post Number: 2
Registered: 04-2004
Posted on Sunday, April 25, 2004 - 11:33 pm:   

Hi Bruce,
Sorry for the late reply. I really appreciate your response to my query. My explanation was not all that clear. This is what I am trying to do basically. When an application for a project I am involved in is downloading MMS message contents from the NowSMS server and there is a network disconnection there seems to be some timeframe that needs to expire before the contents can be downloaded again. This occurs over the HTTP protocol but not WSP. With WSP if a similar thing happens, the timeframe after the network disconnection is much shorter as the WAP3GX ini file allows you to specify a session timeout value. It is this similar control that I am looking for on the NowSMS server.

Does this make sense to you?

Thanks again.
Dan
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2417
Registered: 10-2002
Posted on Wednesday, April 28, 2004 - 06:29 pm:   

Hi Dan,

There shouldn't be any problem like that with an HTTP connection. There is not a session concept, and the same message could be downloaded simultaneously over multiple connections if desired.

There is, however, a bug in WAP3GX that sounds like what you describe ... which would only affect WSP connections. It was described and fixed in the following thread:

http://support.nowsms.com/discus/messages/485/3394.html

I don't know how this could happen when connecting via HTTP.

Perhaps you could enable the debug log in the MMSC, and we could take a closer look at it to see if there is some other unusual activity?

Edit MMSC.INI, and under the [MMSC] section header, add Debug=Yes. Then restart the NowSMS MMSC service. An MMSCDEBUG.LOG will be produced as it runs, and perhaps that will give us some clues.

-bn

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