2 Way receiving MMS on a N 7110

2 Way receiving MMS on a N 7110 SearchSearch
Author Message
Lars Nielsen Mservice.dk
Posted on Tuesday, May 20, 2003 - 11:14 pm:   

I use a Nokia 7110 for the 2 waystuff in nowsms.
Works fine in receiving sms etc. Even though i think the 7110 is a bit unstable. In 8 hours it has disconnected itself 3 times, so i am lookig for advice on stability on the com port etc.

Another mych more important question is that i have activated the Process received MMS Messages.
That does not work at all. I receive nothing at all. Whose fault is it you think? Nowsms program or N7110?
nowsms saves sms messages perfectly, but when sending a mms to the N7110 nothing happends in nowsms. The logfiles says nothing either. So i think that nowsms does not see the mms coming in on the phone.
I read some postings in this forum and some even aid that the N7110 was perfect for it, but i guess my N7110 stinks ;-)

If any has advice uot there, please mail me Lars@12send.dk
Lars Nielsen Mservice.dk
Posted on Tuesday, May 20, 2003 - 11:52 pm:   

Additional:

Often when i have sent a MMS to the phone, nowsms looses connection to the phone.
Under SMSC i press the TEST button.

A MSGBOX returns this: Unable to initilize modem: 80000018 from lineGetID

After that another msgbox: unable to access modem etc. etc.

Then i have to restart the phone. restart nowsms and then the connection is ok again.
Bryce Norwood - NowSMS Support (Bryce)
Posted on Thursday, May 22, 2003 - 11:46 pm:   

Hi Lars,

Try enabling the debug log for the SMS gateway. Manually edit SMSGW.INI, and under the [SMSGW] section header add Debug=Yes. Then restart the gateway.

You might get a clue in the SMSDEBUG.LOG.

If this is an MMS message coming through an operator MMSC, then there might be a problem.

Many operators have their MMSCs firewalled off from the world (which is probably a good idea as I think some of the MMSCs in use are somewhat unstable :-)). The end result is that when NowSMS receives the MMS notification message, the notification message contains a pointer to a URL that contains the MMS message content. However, the URL is on a private IP address that is only accessible to a mobile phone connecting through the operator WAP gateway. As a result, the NowSMS gateway cannot retrieve the URL. So it is likely that there is a message file in the SMS-IN directory that NowSMS is looping on, trying to retrieve the MMS message content.

We've got a plan for how to deal with this situation coming in the v5.0 release which I hope we will be able to make available in beta format here within a couple of weeks. In that version, we can open a GPRS connection with a GPRS modem and retrieve the URL through a WAP connection over GPRS. It won't be extremely fast, but as long as the MMSC is firewalled off from the internet, it's the only way to support receiving MMS from an operator MMSC.

Regarding the 7110 losing its connection, I've got a 7110 that I don't see that problem with. In this type of situation, you might be better off with a Wavecom modem.

-bn
Bryce Norwood - NowSMS Support (Bryce)
Posted on Friday, May 23, 2003 - 01:15 am:   

Lars,

Another thought just crossed my mind, regarding the 7110 losing its modem connection. The 80000018 error is a somewhat generic error. I get that error on my PC if either the modem is not attached, or if another application has the COM port open (only one application can have a COM port active at a time).

It would be curious if you tried configuring NowSMS to talk to the COM port instead of going through the modem driver to see if you notice any difference in this behaviour.

I know in the past we've generally recommended using a modem driver, but the direct COM port interfacing is much better in the v4.20 version, and I'm just curious if it would make a difference in this situation, or if the modem truly is going out to lunch. A lot of the early 7110 models did have quite a few problems. I remember removing the battery to reset the phone many times. But I do have one 7110 that runs very happily as a GSM modem for days on end.

-bn
lars, mService.dk
Posted on Friday, May 23, 2003 - 02:17 pm:   

Hi Bryce

Good to hear from u again. Been a while;-)


About the 7110. I have had it running on a radioservice for a long time, where to connection to it was very stable. But i will try and make nowsms connect to the comport instead just for testing it. i have ordered 2 wavecoms now and awating them;)

The mms i send to the phone i from my own server, and i usually can download these with my other mms-enabled phones. Even on a none-gprs connection. So this should not be a problem.

The 7110 works fine when it receives a sms message. it retrieves it, and puts the content in a .sms file

But when i send the mms nothing happends, still.

But now i'll try and do the com-connection instead and see what happends.
lars, mservice.dk
Posted on Friday, May 23, 2003 - 02:38 pm:   

just did the testing now.
The phone can keep the connection fine, but when the phone receives the mms notif. nothing happends at all, and when i then check the connection to the phone, the connection is lost.

The softw. version of the phone is: V. 5.00 09-11-00 NSE-5


Anyone got an upgrade for it? send it to lars@mservice.dk ;-)
Bryce Norwood - NowSMS Support (Bryce)
Posted on Friday, May 23, 2003 - 03:36 pm:   

Hi Lars,

Yes, I'm a bit behind on questions in the support mailbox as well as here on-line, so it has been awhile.

Believe it or not, I think the problem with the firmware on the phone is that it is too new. Some later versions of the 7110 had support for WAP push (if memory serves me correctly, v3.x and v4.x did not support push). Go into the services area of the phone, and see if there is a "push inbox" (I forget the exact terminology that Nokia used in the early implementations, they might have called it by some other name).

I'm suspecting that the phone does have some support for WAP push, and because MMS is encapsulated inside of a WAP push, that firmware doesn't know what to do when it receives an MMS notification and it confuses the phone.

A firmware upgrade might help that ... but unfortunately if the phone has WAP push support, it doesn't pass along MMS notifications to the modem interface.

-bn
lars mservice
Posted on Friday, May 23, 2003 - 07:21 pm:   

I am sorry but there is absolutely no push support in the 7110. i tried to send one and nothing happend, and there are no menus for push anywhere.
Exactly how does it retrieve the mms.
The notification comes into the phone.
Nowsms gets it and reads the url for the mms file.
But who retrieves the mms file. Is it nowsms over http? or does it get it htrough the phones wap. My guess is via http...

Anyway i ordered some wavecoms that i hve to wait for a while to get. And my impatience told me to go on using the 7110 that i have. I have this idea wich will be the fist of its kind in Denmark and thats the reason for my impatience;)

Could it be the simcard thats fucked up?
Its a card that i have used for so many phonetypes, nd maybe theres too much crap on it.
Bryce Norwood - NowSMS Support (Bryce)
Posted on Saturday, May 24, 2003 - 07:38 pm:   

Lars,

I don't think the SIM is screwed up, it's more likely the device. The device doesn't know how to handle the message and the firmware in the phone enters a state of confusion.

Currently NowSMS retrieves the MMS via HTTP over the default internet connection of the PC.

In the upcoming v5.0 release, we will have an option to retrieve the MMS over a WAP connection over the GPRS modem. (Some mobile operators have their MMSCs firewalled off from the world, and this is the only way that we can get the MMS message content.)

-bn
lars, mservice
Posted on Saturday, May 24, 2003 - 08:14 pm:   

Ok. I will wait for my wavecom's arrive.
I just got hold of a company that has about 10 N7110's lying in a box. if any interested in buying them let me know on lars@mservice.dk


When do you think version 5.0 is ready?
Bryce Norwood - NowSMS Support (Bryce)
Posted on Saturday, May 24, 2003 - 11:46 pm:   

I'm not sure. We were planning for beta by the end of May ... but we are now planning for beta by June 15. I hope it doesn't slide further, but it seems we have been very busy sneaking some other features in based upon specific user requests.

-bn