| I cannot still download mm from operator mmsc. please help me. |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through June 06, 2005 ⬆ |
◄ ► |
| Author | Message | |||
| Duan Unregistered guest |
Hi, Bryce I am so so sorry to bother you about failure of downloading mm from operator mmsc again. I have looked through the article you provide on this topic and configured NOW as what it describes. However, my handphone can only get a notification of incoming mm and can not download it, no matter this mm is sent by NOW/web or a MM7 vas developed by myself (my vas sends mm to NOW and NOW forward it to operator mmsc). I looked article about how now.sms/mms works and I believe there should be no problem in above process. I have no any idea now and could you please give me some clue or advice? Any will be appreciated. Thanks you a lot about your hard work on this board and I am look forward your reply. Best Regards Duan | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4516 Registered: 10-2002 |
Hi Duan, Does sending a multimedia WAP Push message from the web menu interface work? If it does, but MMS does not, then this suggests that your mobile operator does not allow MMS message delivery by external MMSCs. If that option sends you a push link, but you cannot open it, then this suggests that there is a problem with the "Local Host Name or IP Address" setting in the MMSC configuration, indicating that the device cannot connect to your server via the "Local Host Name or IP Address" setting that you have configured. The basic issue is that many mobile operators block message delivery from external MMSCs. In those cases, you have to configure NowSMS to deliver the MMS message by routing it through the operator MMSC over GSM/GPRS. (The default configuration mode of NowSMS is that it acts as a direct delivery MMSC.) So, try the WAP Multimedia Push option ... Tell me how that works. And then tell me more about your configuration ... how you are sending MMS messages, and what mobile operator you are subscribed to. -bn | |||
| Duan Unregistered guest |
Dear Bryce, Thank you very much for your quick reply. I have tried sending WAP Multimedia Push from web menu interface, it works and my handphone received a message with url=http://a.b.c.d:6789/20050516/16/A988B719C.WML?id=%2b8613810211071 a.b.c.d is the ip address which I set in Local Host Name or IP Address field and 6789 is my NOW/MMSC listening port. Because my computer is in company's inner network, my ip is not a public address. It is normal that I can not download the wap push message. As to the MMS message, I configure NOW to forward mm to operator's mmsc through operator's gateway without using NOW's internal mmsc. The mobile operator I am subscribed to is China Mobile. here is my configuration: ------------MMSC.INI------------- [MMSC] Debug=yes WebPort=6789 SMTPPort=25 RelayHost=smtp.mycompany.com HostName=a.b.c.d DomainName=a.b.c.d AdminUser= AdminPassword= SMTPRequireAuth=No EnableDeliveryNotification=Yes ConvertImages=Yes ConvertEMailWAVAMR=Yes ConvertEMailBMPJPG=Yes ConvertScaleToScreen=Yes SMSEMail=No SMSDomainName= SMSPerEMail=1 DefaultOutboundRoute=to cmcc [Outbound MMS Routing] to cmcc=* ------------to cmcc/VASP.INI------------- [VASP] Protocol=MM1 Server=http://mmsc.monternet.com ForceSenderAddress=Yes UseDial=Yes WAPGatewayIP=10.0.0.172 DialUpProfile=Network: GPRS - AirCard 710/750 APN=cmwap ------------smsgw.INI------------- [SMSGW] Modem1=Sierra Wireless AirCard GPRS Modem WebAuth=Yes WebMenu=Yes WebPort=8800 ReceiveSMS=No ReceiveMMS=No [IPRestrictions] Allowed1=*.*.*.* Allowed2=127.0.0.1 [Modem - Sierra Wireless AirCard GPRS Modem] MMSURL=mmsc.monternet.com UseDial=Yes WAPGatewayIP=10.0.0.172 DialUpProfile=Network: GPRS - AirCard 710/750 APN=cmwap PhoneNumber=+8613810368658 ReceiveSMS=Yes ReceiveMMS=Yes MMSRouting=deliver to our vas ------------------------------------------- The message stream likes this: my vas--(mm7.submitreq)-->NOW--(mm1.submitreq)-->operator--(mm1)-->handphone on the side of mm7, NOW works as a mmsc and on the mm1 side, NOW works as a mobile. Is there anything wrong? I am not sure if there is something wrong with my mm format, so I attach my mm7 submit request here. ------------mm7.submitreq------------ POST /mm7/blrc=blrc HTTP/1.1 Host: 135.252.6.121 Content-Type: multipart/related; boundary="--=_blrc-mmsgw-boundary-1116298310684939-1"; type=text/xml;start="<blrc-mmsgw-contentid-1116298310684939-1>" Content-Length: 1963 SOAPAction: "" ----=_blrc-mmsgw-boundary-1116298310684939-1 Content-Type: text/xml; charset="us-ascii" Content-ID: <blrc-mmsgw-contentid-1116298310684939-1> <?xml version="1.0" encoding="UTF-8"?> <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <env:Header> <mm7:TransactionID xmlns:mm7="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1-4" env:mustUnderstand="1" xsi:type="xsd:string">test00001-submit</mm7:TransactionID> </env:Header> <env:Body> <SubmitReq xmlns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1-4"> <MM7Version>5.3.0</MM7Version> <SenderIdentification><SenderAddress><Number>+8613810368658</Number></SenderAddr ess></SenderIdentification> <Recipients><To><Number>+8613810211071</Number></To></Recipients> <MessageClass>Personal</MessageClass> <DeliveryReport>false</DeliveryReport> <ReadReply>false</ReadReply> <Subject>test mm</Subject> <Content href="cid:mms_cid"/> </SubmitReq> </env:Body> </env:Envelope> ----=_blrc-mmsgw-boundary-1116298310684939-1 Content-Type: multipart/related; type="application/smil"; start="<smil>"; boundary="--=_blrc-mmsgw-boundary-1116298310684939-2" Content-ID: <mms_cid> ----=_blrc-mmsgw-boundary-1116298310684939-2 Content-ID: <smil> Content-Type: application/smil; charset="utf-8" <smil> <head> <layout> <root-layout width="128" height="128"/> <region id="Image" width="100%" height="70%" left="0%" top="0%" /> <region id="Text" width="100%" height="30%" left="0%" top="70%" /> </layout> </head> <body> <par dur="5000ms"> <text src="text" region="Text" /> </par> </body> </smil> ----=_blrc-mmsgw-boundary-1116298310684939-2 Content-ID: <text> Content-Type: text/plain; charset="utf-8" Hello, this text is for testing. ----=_blrc-mmsgw-boundary-1116298310684939-2-- ----=_blrc-mmsgw-boundary-1116298310684939-1-- I am very sorry for bothering you with so many words. I can not capture any mm1 message sending from NOW to operator's gateway and have no idea of the process and response from operator's mmsc. So I hope you can give me some clue or suggestion. Thanks again for your kindness. BOW! Best Regards Duan | |||
| curtis Unregistered guest |
hi i have a problem trying to connect with GPRS. im on vodacom. i set the settings manaily but they still do not work. i phoned customer care a number of times but it didn't help, could u please help me out. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4533 Registered: 10-2002 |
Duan, Thank you for all of the words. That is helpful as I better understand your configuration now. It is unusual in a situation where you are submitting the message through an operator MMSC, that a phone would receive the MMS notification message, but not be able to retrieve the actual MMS message. Can you confirm that the handphone is able to send an MMS message to itself? This type of problem suggests that the handphone is unable to retrieve the URL that is published by the MMSC. (That is why I thought you were using NowSMS as the MMSC.) If that doesn't get us anywhere, then let's try sending a message from the modem to its own phone number. Also, try sending an MMS from the handphone to the modem. Do those messages get retrieved? If not, enabled the various debug logs (easiest done by the checkboxes on the "Serial #" page). I'd be most interested in the SMSDEBUG.LOG (MMS message retrieval details end up logged here), and also the MMSWAPDEBUG.LOG. -bn P.S. - I didn't try it myself, but the MM7 looks fine. I would include a "Content-location:" header in the text part, because your SMIL refers to a name rather than a "Content-ID:". We should handle this correctly, and make changes before submitting it to the MMSC, but I point this out as you might have problems with this elsewhere. | |||
