| Capability Negotiation |  Search
|
|
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through August 08, 2004 ⬆ |
◄ ► |
| Author | Message | |||
| Anonymous |
Hi, I was looking at the WAP-206-MMSCTR.pdf where a UAProf sample is given in xml format. It is having some MMS Attributes MmsMaxMessageSize , MmsCcppAccept etc... My doubt is where can i get the binary encoding for these attributes, like how we have encoding for Push , Software, hardware.. etc.. characteristics in WAP-UAProf Specification. Once the encoding of the UAProf is done, how an MMS Client will pass the info?? Somewhere it is said that the Client will pass the URL of the UAProf file. But how can a phone store the file and provide a link for the UAProf file, since a phone is not something similar to a server to do this. Is there any way to store the UAProf file in some http server of the phone's service provider and send the link as UAProf link??. But are there any service providers who providing this facility?? How exactly this is being done in phones which are in the market??. In wsp there is also a Capability Negotiation which define client sdu size etc. what's the difference between this Capability Negotiation and wsp Capability Negotiation??? is there any relationship of them?? Plz let me know abt it... Thanx in advance | |||
