| Uaprofile logging! |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through June 09, 2011 ⬆ |
◄ ► |
| Author | Message | |||
| Gonzalo Escuder New member Username: Gdescuder Post Number: 22 Registered: 06-2010 |
Hi Des, is it possible to log UAProfile used by the client? I'm being required to have this information for our MMSC solution. Thank you, Best regards, Gonzalo | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2359 Registered: 08-2008 |
Hi Gonzalo, I had to run this by our engineering team. There are two ways that you could extract this information. While the MMSC does not log this information in any of its log files, the NowWAP Proxy does log the "User-Agent:" string in its request logs. You could parse those logs to track the "User-Agent:" string from a client. Additionally, there is a way to pass the "User-Agent:" and/or "Profile:" / "X-WAP-Profile:" header to the MMS Accounting Callbacks, which would allow your accounting callbacks to see the device type that is connecting to the MMSC. The article at the following link describes this capability: http://blog.nowsms.com/2010/04/operator-mmsc-accounting-detecting.html The article doesn't specifically address these specific headers, it talks about other headers. However, if you added this to the [MMSC] section of MMSC.INI: AccountingExtraHeaders=User-Agent,X-WAP-Profile,Profile Then NowSMS would append these header values to the MMS Accounting callback URLs: &User-Agent=xxxxxx&X-WAP-Profile=xxxxxx&Profile=XXXXX (There is some discrepancy regarding the Profile and X-WAP-Profile headers. WAP 1.x devices generally use the Profile header, while WAP 2.x devices use the X-WAP-Profile header.) -- Des NowSMS Support | |||
