You Are Here:

Community: Developer Discussion Boards

#1 Old MMSC EAIF simulator - OriginatingDecoder error - 2009-11-03, 21:43

Join Date: Nov 2009
Posts: 1
dwel
Offline
Registered User
Hi,

I am trying to set up a EAIF MMSC using Nokia EAIF MMSC simulator v1.1.
Originating application is opened and listens on port 8189.

I am sending the following POST message to simulator:


Transmission Control Protocol, Src Port: 37051 (37051), Dst Port: 8189 (8189), Seq: 1, Ack: 1, Len: 692
Source port: 37051 (37051)
Destination port: 8189 (8189)
[Stream index: 0]
Sequence number: 1 (relative sequence number)
[Next sequence number: 693 (relative sequence number)]
Acknowledgement number: 1 (relative ack number)
Header length: 20 bytes
Flags: 0x18 (PSH, ACK)
0... .... = Congestion Window Reduced (CWR): Not set
.0.. .... = ECN-Echo: Not set
..0. .... = Urgent: Not set
...1 .... = Acknowledgement: Set
.... 1... = Push: Set
.... .0.. = Reset: Not set
.... ..0. = Syn: Not set
.... ...0 = Fin: Not set
Window size: 50400
Checksum: 0x9301 [validation disabled]
[Good Checksum: False]
[Bad Checksum: False]
[SEQ/ACK analysis]
[Number of bytes in flight: 692]
Hypertext Transfer Protocol
POST /eaif HTTP/1.1\r\n
[Expert Info (Chat/Sequence): POST /eaif HTTP/1.1\r\n]
[Message: POST /eaif HTTP/1.1\r\n]
[Severity level: Chat]
[Group: Sequence]
Request Method: POST
Request URI: /eaif
Request Version: HTTP/1.1
Host: 192.168.40.216:8189\r\n
X-NOKIA-MMSC-To: +1541/TYPE=PLMN\r\n
X-NOKIA-MMSC-From: +12345/TYPE=PLMN\r\n
X-NOKIA-MMSC-Message-Id: Default-v-qf6620.2.x424.5\r\n
X-NOKIA-MMSC-Version: 3.0\r\n
X-NOKIA-MMSC-Message-Type: MultiMediaMessage\r\n
Content-Type: application/vnd.wap.mms-message\r\n
Content-Length: 378\r\n
[Content length: 378]
\r\n
MMS Message Encapsulation, Type: m-send-req
X-Mms-Message-Type: m-send-req (0x80)
X-Mms-Transaction-ID: Default-msg.6621.x2.23.34
X-Mms-MMS-Version: 1.2
Date: Nov 3, 2009 20:30:20.000000000
From: +12345/TYPE=PLMN
To: +1541/TYPE=PLMN
Message-Id: Default-v-qf6620.2.x424.5
LinkedID: (null)
X-Mms-Priority: Low (0x80)
X-Mms-Delivery-Report: Yes (0x80)
X-Mms-Date: Tue, 03 Nov 2009 19:30:20 GMT
X-Mms-TimeStamp: Tue, 03 Nov 2009 19:30:20 GMT
EarliestDeliveryTime: Tue, 03 Nov 2009 19:30:20 GMT
Subject: dxrttf
X-Mms-Message-Class:
Unknown field (0xbc): (Not decoded)
ChargedParty:
Unknown field (0xbd): No (Not decoded)
Unknown field (0xbe): No (Not decoded)
X-Mms-MM-Flags: <Well-known value 0x81> (not decoded)
X-Mms-Store: <Well-known value 0x81> (not decoded)
VASPID: testqueue
VASID: vasid
X-Mms-Originator-System: 000000
Content-Type: text/plain; charset=utf-8
Charset: utf-8
Data (Post)

Response in eaifem.log

Tue Nov 03 20:36:21 CET 2009 <E> [OriginatingDecoder.decode] Error
Tue Nov 03 20:36:21 CET 2009 <E> 385
Tue Nov 03 20:36:21 CET 2009 <E> [ThreadRequestHandler.run] Error
Tue Nov 03 20:36:21 CET 2009 <E> null

Can you tell me what is wrong with my message?

Thanks
Renaud
Reply With Quote
Reply « Previous Thread | Next Thread »
Display Modes
Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules

You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump
Similar Threads
Thread Thread Starter Forum Replies Last Post
Error with makesis.exe and creating the .pkg file gramya87 Symbian Tools & SDKs 7 2007-10-10 14:53
please help cell id perthachy General Symbian C++ 12 2007-07-10 14:14
Carbide.vs 2.01 Registration Problem baykal Symbian Tools & SDKs 5 2006-12-22 17:55
MMSC EAIF emulator : error PDU type britishmimil General Messaging 1 2004-03-22 07:44
MMSC reports error 405, but not EAIF emultor erand1972 General Messaging 3 2003-04-01 09:43

Rate This

 
Bookmark this page: DeliciousDiggFacebookGoogleYahooStumbleUponRedditDiigoTechnocratiTwitter  Share this page Share this page Print this Page Print this page Invite a friend Invite a friend
京ICP备05048969号    Email Newsletters Press Terms & Conditions Privacy Policy Sitemap Contact Us © 2009 Nokia