| What is the type of pdu about MM --retrieve.conf packet |  Search
|
|
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through October 29, 2003 ⬆ |
◄ ► |
| Author | Message | |||
| Anonymous |
when i tune a mms app, after it setup the wsp connection, it received an abort req, the abort code is 8. it is PEERREQ. what does it mean? | |||
| ylcp97 |
Abort code 08 is NORESPONSE, i.e.,the W/G had not got any ack/nack from your WAP stack. | |||
| Anonymous |
how many headers at least should be inclueded in teh get pdu? i know there should include profile, any else must be included? | |||
| Anonymous |
what pdu does the mm-retrieve.conf send in? why i can not get the mm-retrieve.conf but always the content type invalid(406 code)? thanks lots | |||
| Anonymous |
I wonder why. the snippet always falls in wap error(406) handle and never breaks on the mm-retrieve.conf handle. my get pdu have profile. accept two headers, accept header value equals to application/vnd.wap.mms-message which later will turn into 0xbe. is the get pdu right? | |||
| ylcp97 |
There is no need to append any header to the GET pdu. It is said, your U/A will accept all kinds of content if "Accept" header is not in present. Some kind of W/G only supports "Encoding-version" 1.2. Try application/vnd.wap.mms-message with a text, not encoded "0xbe". I think, your MM pdus were encoded in wrong, if you got 406 error. Try ethereal to tune them. | |||
| Anonymous |
i wonder the first statement is rite, the mmsctr declares that When setting up the WSP session and when sending the GET request the MMS Client SHOULD convey the capabilities of the terminal and of the MMS Client. For more details see section 8 on Terminal Capability Negotiation. so i think at least the profle should be conveyed with the get pdu. in practice, there is no need do so? are u sure? ylcp97, i'll try not converting application/vnd.wap-message to 0xbe. thanks anyway for your advice | |||
| Anonymous |
nope, i have checked the get pdu according to the specs related to the wtp.wsp,mms. the below is my get pdu data: 0e 00 01 12 40 37 68 74 ....@7ht data: 74 70 3a 2f 2f ab ab ab tp://xxx data: ab ab ab ab 2e ab ab ab .xxx.xxx data: 2e ab ab ab ab ab ab ab .xxx/was data: ab ab ab ab ab ab ab ab /xxxxxxx data: ab ab ab ab ab ab ab ab xxxxxxxx data: ab ab ab ab ab ab ab ab xxxxxxxx data: ab ab ab ab ab b5 68 74 xxxxx.ht data: 74 70 3a 2f 2f ab ab ab tp://xx. data: ab ab ab ab ab ab ab ab xxx.xx.x data: ab ab ab ab ab ab ab ab xx/xxxxx data: ab ab ab ab ab ab ab ab xxxxxxxx data: ab ab ab ab ab ab ab ab xxxxxxxx data: ab ab ab ab ab ab ab ab xxxxxxxx data: ab 2e 78 6d 6c 00 80 be x.xml... the 1st http is the url, the other is pointed to the profile's url. | |||
| ylcp97 |
There is no need to append any header to the GET pdu. Sorry. It is only for test. | |||
| Anonymous |
also in wsp spec 8.4.2.70 section, it said " If a binary encoding, not supported by the negotiated encoding version or extended header code page, is received by the server. Status code 400 (Bad Request) MUST be returned to the client including the supported encoding versions supported by the server. " | |||
| Anonymous |
0e 00 01 12 40 37 68 74 what's the meaning? which kindly people can explain it ? thanks a lot. ^0^ | |||
| Anonymous |
look at the wtp spec, you will find the answer | |||
