Hi,
When push message is sent through SMSC. SMPP v3.4 'submit_sm' is used by
kannel. Kannel sets 'service_type'as NULL and 'protocol-id' as zero.The
short message is WDP/WSP encoded PDU.
When this message is sent to Terminal, how does the terminal distinguish
application type of short message?
Hi Vijay,
Vijay Patwari wrote:
Hello All,
i hve an smil file cats.smil( which contains text
cat image audio) , i wnt it to be represented it
into mms (.mms), hw this possible.., can u say me.
hw to create mms message. say me.
first I'd like to ask you an counter-question: Have
Clean patch, my vote is +1 for this.
It does minimal changes, and does not modify the default behaviour if the
new directive is not used.
Angel Fradejas
Mediafusion Espana, S.A.
[EMAIL PROTECTED]
www.mediafusion.es
Tel. +34 91 252 32 00
Fax +34 91 572 27 08
-Mensaje original-
De:
ok, this has been commited to cvs now.
But we *SHOULD* abstract this to the upper SMSCConn layer, so that the
new config directive is available for all SMSC module types.
Stipe
[EMAIL PROTECTED]
---
Wapme Systems AG
Vogelsanger
I changed mime parsing to that Kannel would accept lf as a
separator. This should help Ritesh, and lots of use lf as a
separator anyway. Will commit this, if there is interest.
Crlf separator still works, of course.
Aarno
On Thursday, April 3, 2003, at 01:30 PM, Ritesh Shah wrote:
Hi Aarno,
Crlf would work, as I said before. Mime parsing would look after
two kind of separators. But, yes, configuration directive like
mime-parsing = strict/sloppy would be nice.
Aarno
On Thursday, April 3, 2003, at 02:58 PM, Paul Keogh wrote:
I changed mime parsing to that Kannel would accept lf as a
Guanghua Hou wrote:
When push message is sent through SMSC. SMPP v3.4 'submit_sm' is used by
kannel. Kannel sets 'service_type'as NULL and 'protocol-id' as zero.The
short message is WDP/WSP encoded PDU.
When this message is sent to Terminal, how does the terminal distinguish
application
Enzo dell'Aquila wrote:
Hi Aarno,
Sharp GX10 works well if you don't send AF, so Kannel PPG should have no
problem with Sharp. Other Openwave browsers should work too.
so there is no problem here? is this right?
Stipe
[EMAIL PROTECTED]
Citando David Chkhartishvili [EMAIL PROTECTED]:
Here is smsbox log. original message I've sent was: 99182418*t t t t
and curillic letter on the end. You can see that '@' sign was added
before all characters.
2003-03-28 18:16:02 [4] INFO: Starting to service @[EMAIL PROTECTED]@[EMAIL
Hi,
UDH header is WDP header, not SMPP header. SMSC system will treate WDP PDU
as a short message and transfer it to mobile terminal transparently. SMSC
won't parse WDP header. So only SMPP header can be used to distinguish
different application by SMSC.
BR,
Guanghua Hou
Guanghua Hou wrote:
Hi
At 11:09 AM 4/4/03 +0500, David Chkhartishvili wrote:
Hi Bruno,
I didn't followed to cvs tree for a bit, and I was suprised that my mo
doesn't come to smsbox (same config works well with older versions).
Do you get a message No sender/reciever in your smsbox logs?
Nisan
I've read cvs
Nope,
I'm getting message:
INFO: NOTE: sender and receiver same number 520, ignoring!
Nisan Bloch wrote:
Hi
At 11:09 AM 4/4/03 +0500, David Chkhartishvili wrote:
Hi Bruno,
I didn't followed to cvs tree for a bit, and I was suprised that my
mo doesn't come to smsbox (same config works well
12 matches
Mail list logo