I think the answer is yes. I send three HTTP1.1 key-value pairs,
<CR><LF><CR><LF> termination and the m-send-req multipart body. I use
"connect" to connect to the socket as a client, and the "send" to send data,
"recv" to receive.
The post from Marc was helpful in this topic (example MMS) because using
that I managed to find that my encoder was doing the expiry and delivery
date one character longer. I am in the process of rewriting the encoder and
test it then. In fact, the example is based on an Ericcson MMS server and I
need to talk to a Nokia MMS server.
I will test it today. :)
-----Original Message-----
From: Guy Harris [mailto:guy@xxxxxxxxxxxx]
Sent: Tuesday, September 30, 2003 11:06 PM
To: sandor.hadas@xxxxxxxxxxxxx
Cc: ethereal-users@xxxxxxxxxxxx
Subject: Re: [Ethereal-users] Capturing MMS
On Sep 26, 2003, at 12:20 AM, sandor.hadas@xxxxxxxxxxxxx wrote:
> I am quite new to Ethereal and found a problem I cannot solve. Using
> the
> Nokia EAIF (MMS Creating) Emulator on one machine, I send a valid MMS
> to
> another machine which runs an MMS Server. Then the communication
> between the
> computers gets captured using the "host" capture filter.
> The problem is that the content of the messages are shown in a field
> called
> Data (below Frame <n>, Ethernet II, Internet Protocol, Transmission
> Control
> Protocol) but this data (which is fragmented to multiple frames) never
> gets
> decoded as MMS.
Ethereal has an MMSE dissector (packet-mmse.c) for MMS encapsulation
running over WSP and over HTTP. Is MMSE the encapsulation of MMS being
used here and, if so, is it running directly over TCP?