<?xml version="1.0" encoding='utf-8'?>
<!DOCTYPE wml PUBLIC "-//WAPFORUM//DTD WML 1.1//EN" "http://www.wapforum.org/DTD/wml_1.1.xml">
<wml>
<card id="card1" title="Multimedia Messaging Service - Page 10 - Wikipedia">
<p>
<a accesskey="1" href="page.php?w=Multimedia_Messaging_Service&amp;p=9">1.Previous</a><br />
<a accesskey="3" href="page.php?w=Multimedia_Messaging_Service&amp;p=11">3.Next</a>
</p>
<p>public phone number and a special domain name, which is typically carrier-specific.</p>

<p><big> Challenges </big></p>
<p>There are some challenges with MMS that do not exist with SMS:<br/>
* <b><a href="page.php?w=Content_adaptation">Content adaptation</a></b>: Multimedia content created by one brand of MMS phone may not be entirely compatible with the capabilities of the recipient's MMS phone. In the MMS architecture, the recipient MMSC is responsible for providing for content adaptation (e.g., image resizing, audio codec transcoding, etc.), if this</p><p>
<a accesskey="1" href="page.php?w=Multimedia_Messaging_Service&amp;p=9">1.Previous</a><br />
<a accesskey="3" href="page.php?w=Multimedia_Messaging_Service&amp;p=11">3.Next</a>
</p>

<do type="prev" label="Search">
        <go href="search.wml"/>
</do>

</card>
</wml>
