:) Lets narrow it down:
MMSC is working fine. It forwards the message to VASP. VASP is not communicating with the HTTP server.
I hardly made changes to the example configuration files. And everything works fine with other MMS(es). However, the MMS created with NowSMS utility "mmscomp" fails.
I think it may be the problem with the headers. However, you know best. For your reference, I am sending across the MMS created by this tool.
Thanks
Ankit
On 7/14/06,
Paul Bagyenda <[EMAIL PROTECTED]> wrote:
Hi Ankit,Could you simplify the setup description a little. In short, lets narrow down the issue.- The message is received and queued fine by Mbuni MMSC, right?- Does the MMSC then hand over the mmsbox (Mbuni VASP)?Perhaps a look at your confs would be nice too.P.On Jul 14, 2006, at 13:01, Ankit Jalota wrote:Hi Everyone!
I have been using Mbuni MMSC and VASP for sometime now. With the examples provided in CVS (conf files), and by looking at the thread sending SMIL file to send-mms port was fairly easy. Likewise sending MM from MMSC to VASP to a HTTP server was easy.
However, today I tried composing a MMS using "mmscomp" utility provided by NowSMS. When I try to send this message to Mbuni using mmssend to MMSC, it gets transferred to VASP successfully.
This is what I get at MMSC end:
Sent Global Queue MMS Send: From 123/TYPE=PLMN, to 456/TYPE=PLMN, msgsize=29119: err=(null)
However, at the VASP side (mmsbox), the MMS isn't uploaded to the server :(
2006-07-14 15:11:31 [4979] [3] DEBUG: immutable: 0
2006-07-14 15:11:31 [4979] [3] DEBUG: data: 61 75 64 69 6f 2f 6d 70 65 67 00 c0 22 3c 77 69 audio/mpeg.."<wi
2006-07-14 15:11:31 [4979] [3] DEBUG: data: 6e 2e 6d 70 33 3e 00 8e 77 69 6e 2e 6d 70 33 00 n.mp3>..win.mp3.
2006-07-14 15:11:31 [4979] [3] DEBUG: Octet string dump ends.
2006-07-14 15:11:31 [4979] [3] DEBUG: WSP: decoded headers:
2006-07-14 15:11:31 [4979] [3] DEBUG: Content-Type: audio/mpeg
2006-07-14 15:11:31 [4979] [3] DEBUG: Content-ID: < win.mp3>
2006-07-14 15:11:31 [4979] [3] DEBUG: Content-Location: win.mp3
2006-07-14 15:11:31 [4979] [3] DEBUG: WSP: End of decoded headers.
2006-07-14 15:11:31 [4979] [3] DEBUG: HTTP: Resetting HTTPClient for `127.0.0.1'.
2006-07-14 15:11:31 [4979] [3] DEBUG: entered free_clientinfo 0, ip=135803368
2006-07-14 15:11:31 [4979] [3] DEBUG: left free_clientinfo
Generally, with a successful MMS upload, the server responds with a 'success message'. Also, if the upload fails, due to any reason, some error message is displayed. In the present case, however, nothing is displayed! Nor is the message uploaded on the server. What could be the problem?
This is what I'm passing as a header file in mmscomp:
X-Mms-Message-Type: application/vnd.multipart.related
X-Mms-Transaction-Id: text-string
X-Mms-Version: 1.0
From: [EMAIL PROTECTED]
To: 8877996644
Subject: text-string
Many Thanks for you kind consideration.
Regards,
Ankit_______________________________________________Users mailing list
_______________________________________________
Users mailing list
Users@mbuni.org
http://mbuni.org/mailman/listinfo/users_mbuni.org
header.MMS
Description: Binary data
_______________________________________________ Users mailing list Users@mbuni.org http://mbuni.org/mailman/listinfo/users_mbuni.org
