Yes, Mbuni is relying on Kannel doing the splitting (too much trouble
at this stage to split it ourselves).
What Mbuni doesn't do (and should do really) is pay close attention
to size limits as spelt out in the MMS spec. For instance, From,
Subject and To fields should not exceed certain lengths (section
10.2.5 of OMA-MMS-CONF-v1_2). I believe this is the real problem.
Anybody want to do some work on this?
P.
On Aug 30, 2005, at 18:23, Loïc Minier wrote:
Hi,
It seems when a MMS notification is created, a single WAP PUSH is
sent.
This is a problem for:
- long host-aliases/hostnames (as outlined in the User Guide)
- optimize-notification-size = no
I've done some tests where Mbuni would correctly deliver
notifications
for optimize-notification-size = no or yes, but this fails when:
- host-alias/hostname is too long
- optimize-notification-size = no and the recipiend or sender is very
long (From: [EMAIL PROTECTED])
I think that the start_push() function doesn't check the size of the
PUSH and doesn't split the WAP PUSH in multiple SMSes, it
constructs a
single URL with hardcoded UDH length and send the SMS via Kannel.
I've observed the behavior of the NowSMS product, and it splits the
notification in two SMSes.
Maybe Mbuni is relying on some Kannel splitting I've missed?
Bye,
--
Loïc Minier <[EMAIL PROTECTED]>
Come, your destiny awaits!
_______________________________________________
Devel mailing list
Devel@mbuni.org
http://mbuni.org/mailman/listinfo/devel_mbuni.org
_______________________________________________
Devel mailing list
Devel@mbuni.org
http://mbuni.org/mailman/listinfo/devel_mbuni.org
