messagingtoolkit

Hi,

For issue 1, refer to this thread

http://twit88.com/platform/boards/2/topics/show/217

You should use the RoundRobinLoadBalancer

For issue 2, a new GatewayId property is added to MessageInformation. Use the property to differentiate. Please download the attached core library

Could not load file or assembly 'MessagingToolkit.MMS, Version=1.1.0.1, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.

If i add the reference to the Old Dll of the MessagingToolkit.Core.dll the Gateway works fine but if i use the new version you have attached i got the above exception, it seems that the new toolkit is using some features of the MMS, although i am not using anything from that.

Also if i also added the reference to the MessagingToolkit.MMS, and then run the app, it runs fine but on receiving the messages it is not populating the message properly, like in the Content property i get the message in the raw format like "0791293303001505240C912933520184250000013011219372020E32994C2693C96432994C269301" and other properties does not get populated like the dates, RawMessage and PhoneNumber are all Null.

Also there is another change in this dll, instead of using the mobileGateway.Statistics.OutgoingMessage it is usinng the property mobileGateway.Statistics.OutgoingSms

Please make sure you use the latest version 1.1.0.0, and also the BulkGateway source code.

In this release, MMS is supported, and the BulkGateway has some minor changes, like the OutgoingSms rename to accomodate for both SMS and MMS

"Also if i also added the reference to the MessagingToolkit.MMS, and then run the app, it runs fine but on receiving the messages it is not populating the message properly, like in the Content property i get the message in the raw format like "0791293303001505240C912933520184250000013011219372020E32994C2693C96432994C269301" and other properties does not get populated like the dates, RawMessage and PhoneNumber are all Null."

I'm also having the same problem and have the latest version 1.1.0.0.

You have to attach the screenshots and also the log files for us to troubleshoot.

The decoded value of your raw PDU

0791293303001505240C912933520184250000013011219372020E32994C2693C96432994C269301

<< SmsDeliveryPdu >>
Raw Pdu: 0791293303001505240C912933520184250000013011219372020E32994C2693C96432994C269301

SMSC Address: [Length: 7 (07) octets, Type: 91 (10010001), Address: 923330005150]

First Octet: 24 [TP-MTI: (SMS-DELIVER), TP-MMS: (Has more messages), TP-SRI: (Requests Status Report), TP-UDHI: (no UDH)]
Originator Address: [Length: 12 (0C), Type: 91 (10010001), Address: 923325104852]
TP-PID: 00 (00000000)
TP-DCS: 00 (7-bit GSM Alphabet) (00000000)
TP-SCTS: Thu, 11 Mar 2010 12:39:27 GMT+5:00

User Data Length: 14 (0E) septets
User Data (pdu) : 32994C2693C96432994C269301
User Data (decoded): [22222222222222]

If you are writing your own applications, please make sure all dlls are included also.

see
http://twit88.com/platform/boards/2/topics/show/261

Just to let you know that my problem was solved after including all the DLLs.
I think that licencing method is misleading because the PDU decoder has a separate price so I thouth it was not required.
To solve this maybe the Core DLL should not compile without the correct dependacies.

We are working on the Wiki and licensing. Thanks for your feedback.