| Impossible to send MMS with LG gw620 |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through June 09, 2011 ⬆ |
◄ ► |
| Author | Message | |||||
| marc bazimon New member Username: Marc_orange Post Number: 6 Registered: 01-2007 |
Hi , Orange Reunion want to sell LG GW620 but we found some trouble with MMS issue. The LG GW620 can receive MMS but not send it. I take a trace from the MMSC interface and i can see M-SEND.REQ message but it is not treated by MMSC. i join the corresponding trame from gw620 and from a samsung that is working. From this trace , i see that the user agent is a bit long for LG but only that I don't see anything about the message send on log. do you have an idea why the mms coming from this handset are not treated by our MMSC ? Thx for advice i am stuck with this issue and marketing team wait for this to start sell it BR Marc
| |||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1628 Registered: 08-2008 |
Hi Marc, Are you sure that the settings are configured correctly on the new phone? What I notice is that the MSISDN header is missing, so the MMSC does not know who is sending the message. Actually, the MSISDN headers are a bit suspicious on both ... so I'm not sure where the trace is taking place. Is the new phone configured to connect to the MMSC through the same proxy/gateway for MSISDN identification? It would be helpful to see an MMSCDEBUG.LOG ... or if not that, I'd like to at least see what error response is coming back from the MMSC, as that error code would give us a clue. But I'm suspecting it's an MSISDN issue. -- Des NowSMS Support | |||||
| marc bazimon New member Username: Marc_orange Post Number: 7 Registered: 01-2007 |
Hi Des Thx for your response, my trace has been taking at the incoming interface from MMSC and it was only the M-SEND.REQ trame, as configuration for msisdn header in MMSC.INI are like this : MSISDNHeader=msisdn Information about MSISDN should take place on msisdn field and not X-MSISDN please find below the copy of tcp stream of gw620 M-SEND.req as you can see the gw620 add on his header a field call x-MSISDN ( i did not see that for other handset ) POST / HTTP/1.1 Accept: */*, application/vnd.wap.mms-message, application/vnd.wap.sic x-wap-profile: http://gsm.lge.com/html/gsm/GW620-M6-D2.xml Accept-Language: fr-FR, en-US X-MSISDN: Content-Length: 45113 Content-Type: application/vnd.wap.mms-message User-Agent: Mozilla/5.0 (Linux; U; Android 1.5; en-us; LG Eve-Orange) AppleWebKit/528.5+ (KHTML, like Gecko) Version/3.1.2 Mobile Safari/525.20.1 Java/Jbed/7.0 Profile/MIDP-2.1 Configuration/CLDC-1.1 MMS/LG-Android-MMS-V1.0/1.2 Connection: Keep-Alive msisdn: 262692387830 X-WAP-Client-IP: 10.40.10.26 Host: mms.orange.re I also joint the pcap fle i take , the trame from gw620 are on 362 line
Even if the header configuration are on msisdn and not X-MSISDN, is it possible that mmsc don't take request because of the blank X-MSISDN ? can you tell me how to do to fill MMScDEBUGLOG please, i will have to make it during night because we use mmsrouting callback that are very gluttonous on CPU. Thx for advice MArc | |||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1633 Registered: 08-2008 |
Hi Marc, It's definitely a problem related to the blank X-MSISDN header being present. The MMSC is still looking at that header, even though it should not be. I investigated some work-around options, but our engineering team got back to me quickly with a fix ... and I think that's the best option. An updated build with a fix for this issue can be downloaded at http://www.nowsms.com/download/nowsms20100106.zip. -- Des NowSMS Support | |||||
| marc bazimon New member Username: Marc_orange Post Number: 8 Registered: 01-2007 |
Hi Des Good news, and good job we already install another fix, does this fix won't remove older ? BR Marc | |||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1635 Registered: 08-2008 |
Hi Marc, The fixes are cumulative, so this includes any previous fixes or patches. -- Des NowSMS Support | |||||
| marc bazimon New member Username: Marc_orange Post Number: 9 Registered: 01-2007 |
ok , i will apply the patch, do i have to uninstall the current version that is v2008.06.03 before apply fix? Sorry for the question but the mmsc are in production and treat about 10 000 MMS per day so i am a bit anxious when a patch has to be apply ^^ Thx for advice BR Marc | |||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1636 Registered: 08-2008 |
Hi Marc, I understand. I usually prefer to avoid patches, as they result in more support. (Usually they don't cause a problem, but because the system is being watched more closely after the update, there are always more questions.  ) From an MMSC perspective, most of the updates have been for improved interoperability with different MM4 connections. In fact, I think you want to update as there was one critical 100% CPU utilisation problem that was resolved in 2009. The only operational problem that I have seen in MMSC customers upgrading to 2009 and other recent versions has to do with accounting callbacks. We added support for keep-alive sockets to maximize performance. Normally NowSMS can detect and recover from keep-alive problems, but at one site this was a problem. There were sporadic handset errors downloading messages, and we had to add the configuration setting AccountingKeepAlive=No under the [MMSC] header of MMSC.INI. We weren't concerned enough to change the default implementation of this setting, as it doesn't seem to be problematic elsewhere. But this is the only update issue that I've seen which has been a problem for MMSC installations recently. -- Des NowSMS Support | |||||
| marc bazimon New member Username: Marc_orange Post Number: 10 Registered: 01-2007 |
Thx Des i will do upgrade monday, i will tell you what happen ^^ BR Marc | |||||
| marc bazimon New member Username: Marc_orange Post Number: 11 Registered: 01-2007 |
Hi Des we applied your patch yesterday and it had been fixed the trouble with sending MMS with LG gw620 with no regression on other services. Thanks a lot for your reactivity , i am always surprised by the the quality of your support even if customer don't pay it annualy like it is done by other telecom supplier and by experience i can say that the reactivity is not the same ( you kill all other supplier in term of deploying patch ) BR Marc | |||||
| tony julu New member Username: Tonjulu Post Number: 1 Registered: 08-2010 |
how do you apply the patch plz ? | |||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2446 Registered: 08-2008 |
Hi Tony, Are you sure you need this particular patch? Are you running a mobile operator MMSC? The current link from the download page is a more recent product build than the one referenced in this thread, and I would suggest that you use it instead: http://www.nowsms.com/downloads/smsmmsgateway.htm It is not a patch, but a complete install that includes updated product components. It can be installed over an existing installation without losing configuration information. -- Des NowSMS Support | |||||
| tony julu New member Username: Tonjulu Post Number: 2 Registered: 08-2010 |
had the phone 4 weeks 2nd hand, all i know is i cant send mms messages. other than that i have no idea. i downloaded the ptch from this page but cant find a way to install it | |||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2448 Registered: 08-2008 |
This is NOT a patch for the phone. This is software that provides MMS services for a mobile operator. It will not resolve your problem. It is also extremely unlikely that the problem you are experiencing is in anyway related to this particular situation. You should check the web site of your mobile operator to see if they have any help pages for enabling MMS messaging for the model phone that you have. Settings for SMS (text) messaging are preconfigured on the SIM card that you put into the phone. However, this is not the case for MMS (picture/video) messaging. MMS settings need to be configured in your phone. (When a mobile operator sells a phone, they preconfigure these settings for you.) The MMS settings are different for every different mobile phone operator. And there is a different process for how you configure these settings in different phone models. This can be very confusing. For the mobile operator settings, there are usually the following settings that define how a phone connects to send/receive MMS messages: APN (or access point name) MMS Message Server URL Gateway/Proxy Address (and port) And sometimes, a username/password (the same for all users) is required for access to the APN. You need that information from your mobile operator. Then you need to consult the documentation for your mobile phone to see how to configure these settings into your phone. There's not much else I can do to help you. However, maybe this explanation will help you better refine your searches to find the information that you need. -- Des NowSMS Support | |||||
GW620 trace
trace pcap from ncoming interface from mmsc
