Retrieving MMS: making up a bogous UAgent

Retrieving MMS: making up a bogous UAgent SearchSearch
Author Message
Sominush Rex
New member
Username: Ominush

Post Number: 1
Registered: 05-2004
Posted on Sunday, May 23, 2004 - 04:17 pm:   

Hello everyone!
New to NowSMS but relatively knowledgeable with mobile technology, I ran into the following problem:
My provider's MMSC (or more accurately its WAP gateway) fails to recognize the way NowSMS identifies itself while retrieving MMS payloads (using MM1 over GPRS). Since it cannot find a matching User Agent, it renders the media for the most premitive device - and deletes all other content other than text (puts in an XML file stub with the filename and a "deleted" qualifier).
How can I make Now SMS indentify itself as a normal, well-known MMS capable UA? (like a Nokia 3510 for example)
I believe my provider is using LogicaCMG's MMSC.

Would be very greatful for any hint given :-)

Somi.
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2674
Registered: 10-2002
Posted on Wednesday, May 26, 2004 - 09:40 pm:   

Hi Somi,

We've added configuration settings for specifying custom "User-Agent:" and "Profile:" headers in the MM1 transactions.

I'm going to send an update with this support to the e-mail address in your profile. If for some reason you do not receive this, please e-mail me at nowsms@now.co.uk, and I will resend in reply.

Details of the setting available in this update:

* MMS over GPRS: Add support for inserting custom "User-Agent:" and "Profile:" headers when submitting/retrieving MMS messages from an operator MMSC. To insert a custom "User-Agent:" header, add a setting to MMSC.INI, under the [MMSC] section header of HeaderUserAgent=string. Similarly, use a setting of HeaderProfile=http://profileurl for setting a custom "Profile:" header.

-bn