MMS HTTP Send
This message flow simulates an MMS session over HTTP over TCP that sends (posts) data to an MMS server. It is intended to generate simple MMS traffic between the MN and the Network Host node.
When control plane protocols are used, the TCP connection is established after Data Start Delay timer expires. The MN initiates the TCP connection, using the Client Port and Server Port defined in the message flow.
The MMS request and response (shown in red) are embedded in the HTTP POST request and server response.
In the default configuration, the message flow will repeat once per second while the MN session is active. This assumes that the entire flow can be completed in one second. The flow must complete before the next iteration can begin, even if this results in a slower transaction rate.
Modifying the Message Flow
Although you can easily modify the HTTP headers, you should not change the MMS portion of the message (including the filler content) unless you are familiar with the encoding required for MMS Encapsulation and WSP specifications.
You can specify that random port numbers, in the IANA specified dynamic range of 49152 — 65535, be used by the client by entering a 0 for the Client Port.