| Receive MMS with Nokia D211 |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through February 20, 2004 ⬆ |
◄ ► |
| Author | Message | |||
| eisho |
I am able to send and receive SMS as well as send MMS but not able to receive as most of the people here in the forum encountered. For sure I have an MMS-enabled SIM card. As mentioned above, I tried with Nokia D211 and when I sent an MMS to it and it appeared to be two unknown SMS received in its SMS application. I guess those were the concatenated SMS for MMS notification message. I remembered in this post http://support.nowsms.com/discus/messages/485/773.html Bryce said D211 doesn't support AT command set for SMS receiving, that was what you meant, Bryce? Do you have a list of phones and PC cards that can do MMS receiving? I know now that: Phone: Siemens MC35 PC card: Sierra Wireless Aircard 750 Anyone care to update the list? How about any Nokia phones? Thanks alot... | |||
| Bryce Norwood - NowSMS Support |
Hi eisho, Yes, that is the behaviour that you would see with the D211. It is frustrating that they do not support the standard AT commands for receiving SMS messages on that device. All received messages get processed by the built-in application, and I believe there is an API to interface to that application, but we have not investigated it. I'll be curious if anyone else has any recommendations. Phones usually aren't a good solution for this particular purpose because the MMS client always intercepts the notification from the SMS client, so the message never goes over the modem interface. That leaves you with dedicated GSM modem devices. | |||
| eisho |
Bryce, I have captured the packet flow of MMS sending event from PPP. Do you know why it took two WSP connect event to send MMS(packet 1 - 8)? and why it took 7 m-send-req to get a confirmation from the MMSC (m-send-conf)? I have tried this with two different operators and different phones (7650 and D211) and they showed the same packet flow. Here the packet flow (172.16.14.10 is WAP gateway to MMSC and 172.23.101.100 is the MMS client/phone): No. Time Source Destination Protocol Info 1 8.397302 172.23.101.100 172.16.14.10 WTP+WSP WSP Connect 2 9.678783 172.16.14.10 172.23.101.100 WTP+WSP WSP ConnectReply 3 9.679261 172.23.101.100 172.16.14.10 WTP+WSP WTP Ack 4 9.701445 172.23.101.100 172.16.14.10 WTP+WSP WTP Ack 5 9.725285 172.23.101.100 172.16.14.10 WTP+WSP WSP Disconnect 6 10.496362 172.16.14.10 172.23.101.100 WTP+WSP WTP Abort 7 10.680829 172.23.101.100 172.16.14.10 WTP+WSP WSP Connect 8 11.33242 172.16.14.10 172.23.101.100 WTP+WSP WSP ConnectReply 9 11.334021 172.23.101.100 172.16.14.10 WTP+WSP WTP Ack 10 11.334143 172.23.101.100 172.16.14.10 WTP+WSP WTP Ack 11 11.357645 172.23.101.100 172.16.14.10 MMSE MMS m-send-req 12 12.002001 172.23.101.100 172.16.14.10 MMSE MMS m-send-req 13 12.642897 172.23.101.100 172.16.14.10 MMSE MMS m-send-req 14 16.074533 172.16.14.10 172.23.101.100 WTP+WSP WTP Ack 15 16.075121 172.23.101.100 172.16.14.10 MMSE MMS m-send-req 16 16.71877 172.23.101.100 172.16.14.10 MMSE MMS m-send-req 17 17.35972 172.23.101.100 172.16.14.10 MMSE MMS m-send-req 18 20.654097 172.16.14.10 172.23.101.100 WTP+WSP WTP Ack 19 20.672302 172.23.101.100 172.16.14.10 MMSE MMS m-send-req 20 23.085172 172.16.14.10 172.23.101.100 MMSE MMS m-send-conf 21 23.085673 172.23.101.100 172.16.14.10 WTP+WSP WTP Ack 22 23.089523 172.23.101.100 172.16.14.10 WTP+WSP WSP Disconnect 23 23.766416 172.16.14.10 172.23.101.100 WTP+WSP WTP Abort thanks | |||
| Bryce Norwood - NowSMS Support |
The extra Connect is an internal issue to our implementation. The multiple m-send-req aren't really multiple m-send-req. WTP segmentation and re-assembly is being used to send a larger packet. | |||
| eisho |
You are right about the segmentation & reassembly. If the MMS is sent out directly from the phone instead of through NowSMS, there may not be this extra WSP Connect, right? Any idea how could we disable the extra Connect in NowSMS? Or this is compulsory in your implementation? Care to share the reasons? | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 905 Registered: 10-2002 |
It's doubtful that an MMS client in a phone would use a similar approach. I'm not aware of any way to disable NowSMS from performing the extra connect ... we do it for reasons very specific to our internal architecture. Is it causing a problem for you? We have considered some re-engineering to avoid it, but so far there have been more pressing concerns. | |||
