| To check for MMS headers in log files |  Search
|
|
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through November 21, 2009 ⬆ |
◄ ► |
| Author | Message | ||||
| Deepak Kumar Khantwal New member Username: Deepu111 Post Number: 3 Registered: 02-2009 |
Hi, Basic information:- I have a Test Environment set up consisting of NowSMS server and Wireless network simulator (Anritsu). Procedure:- I am sending MMS from phone (under testing) to deliver back on same phone for testing purpose. Issue:- I want to check the below mentioned MMS header in log files, but could not able to trace them. 1. X-Mms-Message-Type 2. X-Mms-Transaction-ID 3. X-Mms-Message-Class 4. X-Mms-Delivery-Report I explore MMSCDEBUG.log file under NOwSMS directory. (please refer the attached file) I feel (NOT SURE) that some headers value is there, but I could not able to recognize which value represents which headers. Is there some option which I need to activate on NowSMS via some INI file modification? I am looking for log in below format, which I found over internet 20:07:45:712 [4] ThreadRouteSMTPIn: X-MMSC-RCPT-TO: +99977777777/TYPE=PLMN 20:07:45:712 [4] ThreadRouteSMTPIn: X-MMSC-Auth-User: VASP:64.124.233.134 20:07:45:712 [4] ThreadRouteSMTPIn: X-MMSC-Received-From: 64.124.233.134 20:07:45:712 [4] ThreadRouteSMTPIn: Sender: +8613910778817/TYPE=PLMN@t-mms.aicent.grx 20:07:45:712 [4] ThreadRouteSMTPIn: X-Mms-Message-Type: MM4_forward.REQ 20:07:45:712 [4] ThreadRouteSMTPIn: X-Mms-Transaction-ID: 0120000647980050817110727001 20:07:45:712 [4] ThreadRouteSMTPIn: X-Mms-Message-ID: 081711072791000001206 20:07:45:712 [4] ThreadRouteSMTPIn: From: +8613910778817/TYPE=PLMN 20:07:45:712 [4] ThreadRouteSMTPIn: X-Mms-Delivery-Report: Yes 20:07:45:712 [4] ThreadRouteSMTPIn: Subject: FW:test 20:07:45:712 [4] ThreadRouteSMTPIn: X-Mms-Ack-Request: Yes 20:07:45:712 [4] ThreadRouteSMTPIn: X-Mms-Originator-System: admin@t-mms.aicent.grx Could you please suggest me, how to get headers in above format so that I can easily recognized. Regards Deepak Kumar
| ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 683 Registered: 08-2008 |
Hi, The log file excerpt that you reference is showing the details of an MMS message being received over an MM4 interconnect. So you wouldn't see that unless you were receiving a message over an MM4 interconnect. In your scenario, the log is simply not going to show that information. There is, however, a trick that you might be able to use where you could configure NowSMS to translate messages that you send to a particular number into a text format. Here's what you would have to do. First, configure an "MMSC VASP" account. For the sake of this example, give it an account name and password of "inbound". Check "Receive to MMS-IN Directory". Leave the other settings at their defaults. Next, configure an "MMSC Routing" account. This account is going to be used to route a message you send out from the NowSMS MMSC, and looping back to itself so that we can route it to the "MMS-IN" directory. Use the same "Account name" of "inbound". Check "Allow Sender Address Override". For "Route messages to this account for recipient phone number(s)", put in a number like "1111". Every time you send to "1111", it will get routed this way. Pick "MM1" as the protocol to use, and use a "Server Address" of "http://127.0.0.1:xxxx/mm1/inbound=inbound" (where "xxxx" is the HTTP port number of the MMSC). Any messages you send to "1111" should now end up in the "MMS-IN" subdirectory of NowSMS, with headers translated into a text format. -- Des NowSMS Support | ||||
MMSCDBUG.log
