RE: MMSC server

Thanks for your response.

We need here to send 2 SMS, do you send SmartMessage or EMS?

I send SmartMessage, and I thing T68i don't support it.

Eric

-----Message d'origine-----
De : Stipe Tolj [mailto:[email protected]]
Envoyé : lundi 28 avril 2003 20:50
À : Debienne Eric
Cc : Marcel Jansen; [email protected]
Objet : Re: MMSC server


Hi Eric,

> Did you try to send a MMS to the Panasonic GD87 phone.

not yep. We don't have one of those arround here. But I'll be able to
grap it somewhere.

> I've got some problems to send a MMS to it.
> 
> In fact, I managed to send a MMS notification (SMS) to the T68i, I can
send
> another MMS notification (SMS) to the panasonic.
> 
> But the notification contents are differents.
> The T68i needs to send the content type in its binary form, and the
> panasonic in the text form.

nop, Kannel's MMSC is able to push indication messages (ie.
M-Notification.ind and M-Delivery.ind) over PI-to-PPG or even to
bearerbox directly for SMS bearer transport.

I use the *same* construction for all phones. And it works for Nokia,
Ericssson and Siemens.

> Does anyone know how the send a unique notification to this two phones

Ok, here is the decoded MMS header that should be used:

  Message-Type: m-notification-ind
  Transaction-Id: <some ID>
  MMS-Version: 1.0
  Message-Class: Personal
  Message-Size: <size of the message>
  Expiry: <expiry value>
  Content-Location: http://<our mmsc>/<some ID>

this gets encoded to the following:

   data:    8c 82 98 35 64 30 64   ....5d0d
   data: 32 66 61 62 32 61 30 63   2fab2a0c
   data: 66 37 34 65 61 63 63 37   f74eacc7
   data: 39 64 64 63 62 36 34 34   9ddcb644
   data: 64 62 35 37 00 8d 90 8a   db57....
   data: 80 8e 02 02 32 88 05 81   ....2...
   data: 03 01 51 80 83 68 74 74   ..Q..htt
   data: 70 3a 2f 2f xx xx 2e xx   p://xx.x
   data: xx 2e xx xx 2e xx 36 xx   x.xx.xx:
   data: xx xx xx xx 2f 72 65 63   xxxx/rec
   data: 65 69 76 65 6d 6d 73 3f   eivemms?
   data: 6d 69 64 3d 35 64 30 64   mid=5d0d
   data: 32 66 61 62 32 61 30 63   2fab2a0c
   data: 66 37 34 65 61 63 63 37   f74eacc7
   data: 39 64 64 63 62 36 34 34   9ddcb644
   data: 64 62 35 37 00            db57.


where 0x8c is the Message-Type
      0x82 is M-Notification.ind

and so on (see MMSEncapsulation document for details).

But this is yet not all. You need to prefix this WSP body with WSP
headers, so that you end up in the following encoded block:

 Octet string at 0x10067298:
   len:  181
   size: 182
   immutable: 0
   data: 00 06 36 61 70 70 6c 69   ..6appli
   data: 63 61 74 69 6f 6e 2f 76   cation/v
   data: 6e 64 2e 77 61 70 2e 6d   nd.wap.m
   data: 6d 73 2d 6d 65 73 73 61   ms-messa
   data: 67 65 00 96 6c 6f 63 61   ge..loca
   data: 6c 68 6f 73 74 3a 39 30   lhost:90
   data: 39 30 00 af 84 8d fc b4   90......
   data: 80 8c 82 98 35 64 30 64   ....5d0d
   data: 32 66 61 62 32 61 30 63   2fab2a0c
   data: 66 37 34 65 61 63 63 37   f74eacc7
   data: 39 64 64 63 62 36 34 34   9ddcb644
   data: 64 62 35 37 00 8d 90 8a   db57....
   data: 80 8e 02 02 32 88 05 81   ....2...
   data: 03 01 51 80 83 68 74 74   ..Q..htt
   data: 70 3a 2f 2f xx xx 2e xx   p://xx.x
   data: xx 2e xx xx 2e xx 36 xx   x.xx.xx:
   data: xx xx xx xx 2f 72 65 63   xxxx/rec
   data: 65 69 76 65 6d 6d 73 3f   eivemms?
   data: 6d 69 64 3d 35 64 30 64   mid=5d0d
   data: 32 66 61 62 32 61 30 63   2fab2a0c
   data: 66 37 34 65 61 63 63 37   f74eacc7
   data: 39 64 64 63 62 36 34 34   9ddcb644
   data: 64 62 35 37 00            db57.
 Octet string dump ends.

I blanked out the IP!

If you want to use Kannel's PPG to push the M-Notification.ind to the
MMS client, then use the *first* block (the WSP body) as PPG content.

If you want to send the full WSP encoded block via sendsms interface,
then use the *second* block including the WSP headers.

Here is a snapshot from access.log:

2003-04-28 15:28:25 Sent SMS [SMSC:smpp_wapme] [SVC:] [ACT:]
[from:MMSC] [to:+49xxx] [flags:0:2:0:0:0]
[msg:128:0006366170706C69636174696F6E2F766E642E7761702E6D6D732D6D65737361676
500966C6F63616C686F73743A393039300
0AF848DFCB4808C8298356430643266616232613063663734656163633739646463623634346
4623537008D908A808E020232880581030
1518083687474703A2F2Fxxxx2Exxxx2Exxxx2Exxxx3A]
[udh:12:0B05040B8423F00003000201]
2003-04-28 15:28:25 Sent SMS [SMSC:smpp_wapme] [SVC:] [ACT:]
[from:MMSC] [to:+49xxx] [flags:0:2:0:0:0]
[msg:53:xxxxxxxx2F726563656976656D6D733F6D69643D3564306432666162326130636637
3465616363373964646362363434646235
3700] [udh:12:0B05040B8423F00003000202]

you see that the message has been slit to 2 SMS messages. The UDH you
have to use is "0605040b8423f0".

Ok, this is enough information to send M-Notification.ind.

Stipe

[email protected]
-------------------------------------------------------------------
Wapme Systems AG

Vogelsanger Weg 80
40470 Düsseldorf

Tel: +49-211-74845-0
Fax: +49-211-74845-299

E-Mail: [email protected]
Internet: http://www.wapme-systems.de
-------------------------------------------------------------------
wapme.net - wherever you are