help needed on making use of the call monitor service

[goaskin]

Since the B-series, Samsung TVs have a feature called Personal Message Service. For that, a server runs on port 52235 and if you send a well-formated SOAP-request to this port, the TV should display messages about incoming calls, SMS or calendar schedules. The manual says that some mobile phones with WIFI are able to inform the TV about calls etc.

On a german forum, we try since more than half an year to find out how this service works. But without any success yet. Furthermore nobody knows a mobile phone that is usable for this. Can anybody help us?

[goaskin]

The latest non-working code is:

Code: Select all

POST /PMR/control/MessageBoxService HTTP/1.0
Content-Type: text/xml; charset="utf-8"
HOST: 192.168.178.20
Content-Length: 469
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:12345678-1234-1234-1234-12345678abcd</MessageID>
         <Message>category:PmrIncomingCallMessage:sender:4627325:receiver:62347</Message>
      </u:AddMessage>
   </s:Body>
</s:Envelope>

I think the necessary changes are very few but nobody has an idea yet.

[erdem_ua]

Hi goaskin.
I don't know if samsung implementation is functional to the date. (Might be they leave their work at half)...
Do you inspect exeDSP via IDA?
It's not scary as it sounds came.
When you find functions that process this code, you might have found what is wrong.
Also might be "Debug Menu" could help you on this.

[goaskin]

This service seems to be functional because I read a forum discussion (linked into the thread of another forum) that this feature works with one Nokia Handy that isn't available on the european market (I remembered N71).

Regarding Samsung Handies, they use three different operating systems. Some Windows, some Symbian and some Android. The technical realization, the features and the available applications are completely different. Possibly it works on Samsung Jet mobiles but not with Samsung Omnia.

[doodlecz]

Yesterday I tried to send the latest non-working XML to the TV.
And I must say, with such request, we (you ) are still far away from the moment when the TV tries to parse and process the Message or MessageID node.

In some of your tests I read about
- error 412 - precondition failed - it means badly formatted XML (or Content-Length is too short, so the XML is not completely and therefore badly formatted).
- error 402 - invalid request - this seems to be about some session management, but still to be checked.
These are also two errors I encountered during tests..

Anyway, except some first checks (-> possible error 412), the content of the request is not checked and current issue IMO is not about content of the AddMessage node.

[goaskin]

There are either additional tags required that are not part of the service description or the message itself is a specially formatted string. The exeDSP checks for things like sender, receiver, messagetype (numeric IDs for sms, calls and calendar schedules), messages and a few unknown parameters more.

For the message ID I guess I am right. With

Code: Select all

urn:uuid:12345678-1234-1234-1234-12345678abcd

I get error 412. When changing to something else (other format), I always get 402. The routines handle something different if the message-id begins with urn:uuid: with a set of numbers following. My intension to submit a MessageID with this format was because a messageID-parameter is often used on SOAP requests and has nearly always this format.

[doodlecz]

How exactly look your requests and related responses? (with and without MessageID node)
For me it doesn't matter if there is MessageID node or not. Just if the request is OK (by header and syntax) -> 402, if not -> 412..

Btw, I let exeDSP generate some uuids (cd_uuid_generate) and got following:
e6394016-2275-3743-fbde-60412921747d
64f32c88-f357-ac8f-acec-05f3eee35a7c
..just for confirmation of correct format.