| How to use NowSMS to read out the MMS user agent and the MMS x-wap-... |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through October 14, 2015 ⬆ |
◄ ► |
| Author | Message | |||
| Andy28 New member Username: De_afeider Post Number: 8 Registered: 11-2011 |
Hi NowSMS team, is there any way to read out the MMS user agent and MMS UAProfile (x-wap-profile) with NowSMS connected via GPRS/UMTS modem? Our goal is to find a way using NowSMS - without additional network tracing needed, to verify that devices send out the correct user agents and UAprofile data according to OMA specification and our requirements. Note: We do not want to check the user agent of the browser, as this can differ for some devices. Kind regards Andy | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4803 Registered: 08-2008 |
Hi Andy, An MMS client generates those headers in transactions between the MMS client and the MMSC. However, that is the extent/lifespan of those headers ... they would not exist in the MMS data after MMSC processing. You could point clients to a NowSMS server configured as an MMSC to observe this traffic. -- Des NowSMS Support | |||
| Andy28 New member Username: De_afeider Post Number: 9 Registered: 11-2011 |
Hi Des, if I understood correctly this would be your proposed configuration: - Configure NowSMS to use the internal MMSC - Configure the MMS APN settings in the phone with the corresponding values - Send a MMS Now I should be able to see the user agent/UAprof values somewhere, at least as admin. Is it also somehow possible to see the user agent/UAProf as a NowSMS user somehow (ideally via web interface)? Kind regards, Andy | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4807 Registered: 08-2008 |
Hi Andy, Providing that information is not what I would consider to be primary functionality ... or even an intended functionality ... it is more of a side effect of having a lot of different functionality. In other words, if you don't have a better way to retrieve this information, you could view it in the debug logs. Here's what I would do ... First, I'm assuming that the intent is testing only, so when you send the MMS message from the phone, it is for capture purposes only, and you do not want NowSMS to actually send the message. Under "MMSC VASP", create an account. Give it a simple account name and password ... for simplicity, set both to IN. Make sure "MM1" is enabled for "Accept Connections". Set the "MMSC Routing" to be "Receive to MMS-IN Directory". Other settings can be left at defaults. Note: Normally you would create an MMSC user account for this purpose. We used a VASP because that allows us to just save the received message to a directory without additional processing. Under "SMS Users" create an account for yourself, and be sure to check "Enable Admin Access". On the "Serial #" page, enable MMSCDEBUG.LOG and press Apply. Manually edit MMSC.INI, and under the [MMSC] header, add DebugFull=Yes On the device, configure an APN with full internet access, and set the MMS Server URL to http://host:port/MM1/IN=IN (host is a host name and IP address that routes to the NowSMS server, and port is the HTTP port number configured on the "MMSC" page.) To retrieve the logs from the web ... connect to http://host:port/ADMIN (different port number, this is the one configured on the "Web" page of the configuration) and login with the SMS user credentials. Under "Log Files", MMSCDEBUG.LOG will have a dump of the MMSC transactions received. Under "Received Messages", received MMS content will be displayed. The headers you are after will only be in the MMSCDEBUG.LOG -- Des NowSMS Support | |||
