Please, be more specific.. this says nothing much useful to others. Error 412 - precondition failed may be because of badly formatted XML or incorrect content-length, not because there is some tag missing (I'm not saying that's your case..). Error 500 is internal error and probably with specific reason inside XML (like "Invalid request!!!!"), this would be also interesting information.goaskin wrote:I played around with some XML texts yesterday and found one thing out: If no <MesageSizeType> is defined into the <Message> tag, I receive error 412 - precondition failed. If this tag is set, I get error 500.
help needed on making use of the call monitor service
Re: help needed on making use of the call monitor service
Re: help needed on making use of the call monitor service
If <MessageSizeType> is missing, the server returns 412 - on badly formatted XML too. If <MessageSizeType> is set, it returns 500. I played around with that. So I think 412 is either returned of the XML is formatted badly or if essential tags are missing. Same for <ExpireState> I found out yet - 412 if missing.
I am currently trying to format a SOAP using the tags like shown above. The biggest questions are possible values for <Category> and <ExpireState>. 'sms' is no suitable value because the exeDSP nowhere parses for 'sms' (no constant existing with that string). What I am currently trying is to set 0, 1, 2,3 or the same like on <MessageSizeType> for <Category>. But while I have no idea for <ExpireState> that may not help...
I am currently trying to format a SOAP using the tags like shown above. The biggest questions are possible values for <Category> and <ExpireState>. 'sms' is no suitable value because the exeDSP nowhere parses for 'sms' (no constant existing with that string). What I am currently trying is to set 0, 1, 2,3 or the same like on <MessageSizeType> for <Category>. But while I have no idea for <ExpireState> that may not help...
Re: help needed on making use of the call monitor service
Code: Select all
POST /PMR/control/MessageBoxService HTTP/1.0
Content-Type: text/xml; charset="utf-8"
HOST: 192.168.178.20
Content-Length: 697
SOAPACTION: "uuid:samsung.com:service:MessageBoxService:1#AddMessage"
Connection: close
<?xml version="1.0" encoding="utf-8"?>
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<s:Body>
<u:AddMessage xmlns:u="urn:samsung.com:service:MessageBoxService:1">
<MessageID>urn:uuid:64f32c88-f357-ac8f-acec-05f3eee35a7c</MessageID>
<Message>
<Category>PmrIncomingCallMessage</Category>
<MessageSizeType>Incoming Call</MessageSizeType>
<ExpireState />
<CallTime>2009-11-26T13:59:29.593Z</CallTime>
<Callee>70777</Callee>
<Caller>95095</Caller>
</Message>
</u:AddMessage>
</s:Body>
</s:Envelope>
Code: Select all
HTTP/1.1 500 Internal Server Error
CONTENT-LENGTH: 406
CONTENT-TYPE: text/xml; charset="utf-8"
DATE: Thu, 01 Jan 1970 04:02:36 GMT
EXT:
SERVER: Linux/9.0 UPnP/1.0 PROTOTYPE/1.0
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body><s:Fault><faultcode>s:Client</faultcode><faultstring>UPnPError</faultstring><detail><UPnPError xmlns="urn:schemas-upnp-org:control-1-0"><errorCode>402</errorCode><errorDescription>Invalid Request!!!!!</errorDescription></UPnPError></detail></s:Fault></s:Body></s:Envelope>
Connection closed by foreign host.
Re: help needed on making use of the call monitor service
I won't repeat myself regarding the "Invalid Request!!!!" message. Find the string reference and look into that function. There is no content parsing in this function.
In fact, there is "SMS" reference, but it's not represented as string by IDA because it's only 3 bytes long - it is represented as dword by default.
In fact, there is "SMS" reference, but it's not represented as string by IDA because it's only 3 bytes long - it is represented as dword by default.
Re: help needed on making use of the call monitor service
I only disassembled the code using the OBJDUMP command. And the result is incredible - many things are too hard to find out. I need a better solution (like OTX for PPC code on OSX) that supports string resolution in cmp instructions and so far.
Re: help needed on making use of the call monitor service
Because the disassembled code represents the machine code. It can theoretically be used to reconstruct the exeDSP like it is - so it is a copyright violation. If posted into a forum or if it is published on a webspace does not matter.meinsource wrote: Can we have a common file space to share and search such code? Or are there legal concerns to do this in public views?