Page 1 of 1
How to post a binary message
Posted: Thu Nov 20, 2008 3:59 am
by twdev
Hello.
I have the following binary signature for a Nokia ringtone:
UserDataHeader: 06050415810000
MessageData: 024A3A6949A59194813D988151A004004D215D2690568698A22820C49A4106288A126A8A22C2A820C22820C2A82342AC30820C4984106288A12628A22C2A420800
..so the full User Data value is:
06050415810000024A3A6949A59194813D988151A004004D215D2690568698A22820C49A4106288A126A8A22C2A820C22820C2A82342AC30820C4984106288A12628A22C2A420800
How do I submit this message using your library?
I see in your sample app there is a foreach loop:
foreach (SubmitSm sm in req)
..each sm object appears to have a 'UserDataPdu' property but I can't find any docs to support this.
Can you please specify how to map the user data above to be delivered as a binary message?
Thank you.
Posted: Fri Nov 21, 2008 2:37 pm
by alt
Hello,
Please try with version 2.5.4.
byte[] bytes;
byte[] header_bytes;
sm.UserDataPdu = bytes;
sm.UserDataPdu.Headers = header_bytes;
Posted: Mon Nov 24, 2008 4:08 am
by dg
Hi,
I was previously using version 2.3.4 and have just tried to update to 2.5.4 to send binary messages in this way.
Upon upgrading my application references to the new version, I am no longer able to connect.
When I revert back to the older version, the connection occurs without issue.
Is there something I need to change with my connect method between these two versions?
Thanks,
dg
Posted: Wed Nov 26, 2008 8:32 am
by alt
Do you use IPv6?
Could you try with another method?
public bool Connect(IPEndPoint endPoint)
Posted: Wed Nov 26, 2008 8:34 am
by dg
Nope, don't use IPv6.
I will try the alternate connection method and see how it goes.
Thanks.
Posted: Wed Nov 26, 2008 9:04 am
by dg
I tried this alternate connection method and was still not able to connect.
I notice that you changed something in the connection methods recently - could it have something to do with that maybe?
Thanks for your help!
Cheers,
dg
Posted: Wed Nov 26, 2008 10:56 am
by alt
Which error did you get?
Posted: Sat Nov 29, 2008 4:22 pm
by alt
Please try version 2.5.5.
Posted: Mon Dec 01, 2008 1:45 am
by dg
Good Morning alt,
I am able to connect again now, thanks for the update!
I am still having trouble sending binary SMS however.
It seems that additional data is being prepended to my header.
I am setting the header to: 06050415810000 and in the SMPP packet it looks like 090007 is being prepended to that.
Given that was the case, I tried setting the heading to 15810000.
When I did this 060004 was prepended in the SMPP packet - so it was almost what I wanted, the 00 rather than 05 however renders the message useless (unsupported message type is returned by the handset)
Can you please advise if I am doing this correctly or if there is some setting that I might have set incorrectly (I am using octet unspecified data codings if that is of any assistance)
Thanks,
dg
Posted: Wed Jan 21, 2009 3:11 am
by dg
dg wrote:Good Morning alt,
I am able to connect again now, thanks for the update!
I am still having trouble sending binary SMS however.
It seems that additional data is being prepended to my header.
I am setting the header to: 06050415810000 and in the SMPP packet it looks like 090007 is being prepended to that.
Given that was the case, I tried setting the heading to 15810000.
When I did this 060004 was prepended in the SMPP packet - so it was almost what I wanted, the 00 rather than 05 however renders the message useless (unsupported message type is returned by the handset)
Can you please advise if I am doing this correctly or if there is some setting that I might have set incorrectly (I am using octet unspecified data codings if that is of any assistance)
Thanks,
dg
Any thoughts on this alt?
Thanks,
dg
Posted: Wed May 27, 2009 9:14 am
by suguz
dg wrote:dg wrote:Good Morning alt,
I am able to connect again now, thanks for the update!
I am still having trouble sending binary SMS however.
It seems that additional data is being prepended to my header.
I am setting the header to: 06050415810000 and in the SMPP packet it looks like 090007 is being prepended to that.
Given that was the case, I tried setting the heading to 15810000.
When I did this 060004 was prepended in the SMPP packet - so it was almost what I wanted, the 00 rather than 05 however renders the message useless (unsupported message type is returned by the handset)
Can you please advise if I am doing this correctly or if there is some setting that I might have set incorrectly (I am using octet unspecified data codings if that is of any assistance)
Thanks,
dg
Any thoughts on this alt?
Thanks,
dg
You Should use DataCoding = DataCodings.Class1ME8Bit
that's worked for me