summaryrefslogtreecommitdiffstats
path: root/res/xml
diff options
context:
space:
mode:
authorChristian Gustafsson <qmfd78@motorola.com>2009-06-20 14:48:03 -0500
committerWink Saville <wink@google.com>2009-06-29 15:52:40 -0700
commit89e7af1acc0b62f2822ace8df6d56f4c6d37a40f (patch)
tree871777ff1c3bb04b3d9674236078e89bed09da14 /res/xml
parentd808dd7a449839282d13426d353b7007122ddb64 (diff)
downloadpackages_apps_Mms-89e7af1acc0b62f2822ace8df6d56f4c6d37a40f.zip
packages_apps_Mms-89e7af1acc0b62f2822ace8df6d56f4c6d37a40f.tar.gz
packages_apps_Mms-89e7af1acc0b62f2822ace8df6d56f4c6d37a40f.tar.bz2
Additional customization options for mms http transport.
Modified the MMS http transport and configuration to allow for more settings. This is needed for CDMA carriers. 1. UserAgent needs to be modifiable. Most MMSC on the CDMA side will use the user agent name as the device identification to invoke the right transcoder settings. 2. The tag name for the UAProfUrl is not the same for all carriers. Instead of "x-wap-profile" they might require "Profile". 3. There are additional http parameters required some with the users phone number. For example: x-up-calling-line-id: 15555550000 where 15555550000 would the users telephone number. Since these parameters vary wildly from carrier to carrier the code was written to be flexible. All additional parameters can be added to a single string in the mms_config.xml file. They are separated by '|'. The substitution string for the users phone number is also flexible to avoid a carrier parameter clash. Example: <string name="httpParams">x-up-calling-line-id: UserNumerGoesHere</string> <string name="httpParamsLine1Key">UserNumerGoesHere</string> If the users number happens to be 15555550000 then at runtime a x-up-calling-line-id: 15555550000 would appear in the http transactions with the MMSC. Additional parameters can be added: <string name="httpParams">x-up-calling-line-id:#LINE1#|x-iot-pass-date: 20001122</string> <string name="httpParamsLine1Key">#LINE1#</string> In this case two additional parameters would be added to the http transaction: x-up-calling-line-id: 15555550000 x-iot-pass-date: 20001122
Diffstat (limited to 'res/xml')
-rw-r--r--res/xml/mms_config.xml16
1 files changed, 16 insertions, 0 deletions
diff --git a/res/xml/mms_config.xml b/res/xml/mms_config.xml
index 020be38..55d19a9 100644
--- a/res/xml/mms_config.xml
+++ b/res/xml/mms_config.xml
@@ -21,8 +21,24 @@
<!-- Maximum message size in bytes for a MMS message -->
<int name="maxMessageSize">1048576</int>
+ <!-- User-Agent parameter used in MMS http request -->
+ <string name="userAgent">Android-Mms/0.1</string>
+
+ <!-- UAProf parameter tag name -->
+ <string name="uaProfTagName">x-wap-profile</string>
+
<!-- UAProf URL -->
<string name="uaProfUrl">http://www.google.com/oha/rdf/ua-profile-kila.xml</string>
+
+ <!-- Additional http parameters used in MMS http request.
+ Parameters are seperated by '|'. Optional.
+ -->
+ <string name="httpParams">x-up-calling-line-id: ##LINE1##|x-carrier-magic: http://magic.google.com</string>
+
+ <!-- Substitution key to be used when adding the users telephone number (Line1) to the
+ httpPrams at runtime. Optional.
+ -->
+ <string name="httpParamsLine1Key">##LINE1##</string>
<!-- Maximum height for an attached image -->
<int name="maxImageHeight">480</int>