| Error getting MMS |  Search
|
|
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through August 08, 2004 ⬆ |
◄ ► |
| Author | Message | ||||
| Carlo Bertolino Unregistered guest |
Hi, I try to receive an MMS from my application and I send a WAP-GET pdu to the MMSC of my phone-operator with the url received in the SMS notification message. As appear at the end of this message I receive an error from MMSSERVER. With AT commands on my phone I can see content of SMS wich transport the M-notification-ind: AT+CMGF=1 (text mode) AT+CMGR=1 (first SMS received) AT+CMGR=2 (second SMS received) I obtain this sequence: 0C05040B8423F00804066102013406276170706C69636174696F6E2F766E642E7761702E6D6D732D 6D65737361676500AF848D0191B48 08C829841454C5A6256785379583733676C314D63008D908919 802B3339333335363938333037382F545950453D504C4D4E009654696 C6162204D4D533A20333020 6F72652031303A30C05040B8423F00804066102028103016DA083687474703A2F2F6D6D732E74696 D2E6 9742F736572766C6574732F6D6D732F6D6D73633F41454C5A6256785379583733676C314D630 I think that the last part: 687474703A2F2F6D6D732E74696D2E69742F736572766C6574732F6D6D732F6D6D73633F41454C5A 6256785379583733676C314D630 correspond to the URL: http://mms.tim.it/servlets/mms/mmsc?AkZGUQ5WVskwGIpye At this point I can send the wsp-get-pdu at this url but I see an error: Can someone tell me were is the problem? Thanks Carlo This is the last part of the trace: Frame 1168 (94 bytes on wire, 94 bytes captured) Ethernet II, Src: 00:00:0c:00:00:00, Dst: 44:cd:20:00:0c:00 Internet Protocol, Src Addr: CPQ12224.cselt.it (10.208.34.209), Dst Addr: 10.103.212.213 (10.103.212.213) User Datagram Protocol, Src Port: 49200 (49200), Dst Port: 49200 (49200) Wireless Transaction Protocol, PDU: Invoke (1), Transaction Class: Reliable Invoke with Reliable Result (2) 0... .... = Continue Flag: No TPI .000 1... = PDU Type: Invoke (0x01) .... .01. = Trailer Flags: Last packet of message (0x01) .... ...0 = Re-transmission Indicator: First transmission 0... .... .... .... = TID Response: Original .000 0000 1011 0011 = Transaction ID: 0x00b3 00.. .... = Version: Current (0x00) ..0. .... = TIDNew: TID is valid ...1 .... = U/P flag: User Acknowledgement required .... 00.. = Reserved: 0x00 .... ..10 = Transaction Class: Reliable Invoke with Reliable Result (0x02) Wireless Session Protocol, Method: Get (0x40), URI: mms.tim.it/servlets/mms/mmsc?AkZGUQ5WVskwGIpye PDU Type: Get (0x40) URI Length: 46 URI: mms.tim.it/servlets/mms/mmsc?AkZGUQ5WVskwGIpye Frame 1393 (387 bytes on wire, 387 bytes captured) Ethernet II, Src: 44:cd:20:00:0c:00, Dst: 00:00:0c:00:00:00 Internet Protocol, Src Addr: 10.103.212.213 (10.103.212.213), Dst Addr: CPQ12224.cselt.it (10.208.34.209) User Datagram Protocol, Src Port: 49200 (49200), Dst Port: 49200 (49200) Wireless Transaction Protocol, PDU: Result (2) 0... .... = Continue Flag: No TPI .001 0... = PDU Type: Result (0x02) .... .01. = Trailer Flags: Last packet of message (0x01) .... ...0 = Re-transmission Indicator: First transmission 1... .... .... .... = TID Response: Response .000 0000 1011 0011 = Transaction ID: 0x00b3 Wireless Session Protocol, Method: Reply (0x04), Status: 500 Internal Server Error (0x60), Content-Type: text/html PDU Type: Reply (0x04) Status: 500 Internal Server Error (0x60) Headers Length: 161 Content-Type: text/html; charset=us-ascii Headers Line-based text data: text/html <HTML><TITLE>Error</TITLE><BODY><H1>Error 500: 8533:1406: Variable "browserType.indexOf" is not a function type. Error near :34 [:Global Initialization)].</H1></BODY></HTML> | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 2486 Registered: 10-2002 |
Maybe you don't have an "accept:" header that indicates that you support "application/vnd.wap.mms-message"? | ||||
| carlo Bertolino Unregistered guest |
Hy Bryce, thank you for your suggest. After some attempts with different headers values in wap_get message, I'm able to receive the m-retrieve-conf from MMSC. As you can see in the attached file, now I receive a different error. 1. What do you think about this error? 2. Can you tell me if tipycally MMSC start a timeout when it send the m-retrieve-message and, when this timeout expire, the message can't be downloaded by the mobile but only via web? Thank for all Carlo
| ||||
MMS_get_trace
