| UAProf manual provisiong |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through July 28, 2006 ⬆ |
◄ ► |
| Author | Message | ||||
| Martín Mendiguren New member Username: Martin_ Post Number: 6 Registered: 04-2006 |
Hello. We tried to send MMS with a phone TORQ P150 and we couldn't. The provider sent us the UAProf file and said that we have to manually provision it. Is it possible? If we put the file in the folder /UAPRof, is it necessary to edit the file UAMap.ini? Thanks Martín
| ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6201 Registered: 10-2002 |
Hi Martín, You say that you tried to send an MMS with this phone and couldn't ... I don't see how this would be a UAProf issue. The UAProf is only consulted when a phone is receiving a message ... not sending. (And if a UAProf can't be retrieved, it's generally no big deal, as it just means that no content adaptation will be performed. If you are having problems sending an MMS message ... then my advice would be to enable the MMSCDEBUG.LOG ... repeat the sending attempt ... and post the excerpt of the MMSCDEBUG.LOG in reply here, so that we can take a closer look at the transaction. Also, please advise what version of NowSMS you are running. If you have other information that suggests that the problem is truly UAProf related, let me explain how the logic works. When a phone connects to the MMSC, it should transmit a "Profile:" or "X-WAP-Profile:" header. This header contains a URL from the manufacturer that should contain the UAProf file. NowSMS checks the UAPROF.INI file to see if it already has a cached copy of the file referenced by the URL. If it doesn't, it tries to fetch the URL ... and if successful, updates UAPROF.INI. If the URL can't be retrieved, or there is no "Profile:" or "X-WAP-Profile:" header, then that's where UAMAP.INI comes into play. The MMSC looks at the "User-Agent:" header from the phone, and tries to find the longest substring match within UAMAP.INI to point it to a UAProf file. (Searching on UAMAP should point to other threads out here that discuss this file.) Generally speaking, if the UAProf file can't be found, it's not a problem ... unless ... the profile URL has a problem. Specifically, if the URL returned by the manufacturer points to a web site that is extremely slow to respond, this could cause the MMS client to timeout while retrieving the message, because the MMSC is too slow to respond because it is waiting on the profile server. (If this is happening, we'd see this in MMSCDEBUG.LOG ... but keep in mind that this happens on retrieval, not sending.) -bn | ||||
