Search found 60 matches

by NickAskew
Thu Jun 07, 2012 2:33 pm
Forum: Inetlab.SMPP v1.0
Topic: Null exception within a Try block?
Replies: 14
Views: 111135

Re: Null exception within a Try block?

Hi Ishmel, Is it possible that the last parameter you use for .PrepareSubmit could be Nothing/Null? The SMPP component may well be handling the exceptions internally and seeing null it then passes a null out which will then freak out the assignment [oRespList = ] meaning the SMPP exception will not ...
by NickAskew
Wed Feb 29, 2012 3:42 pm
Forum: Inetlab.SMPP v1.0
Topic: Message Loss while using asynchronous message sending
Replies: 20
Views: 128355

Re: Message Loss while using asynchronous message sending

Hi Major, I only use the async method - Maximum throughput I have attained connected to 'mBlox' is ~250 message parts per second per server, mBlox provide connection to two servers simultaneously so the best I have managed is ~500 message parts per second spread over two 'mBlox' servers communicatin...
by NickAskew
Wed Feb 29, 2012 2:24 pm
Forum: Inetlab.SMPP v1.0
Topic: Message Loss while using asynchronous message sending
Replies: 20
Views: 128355

Re: Message Loss while using asynchronous message sending

Hi Major, I only use the ASYNC methods myself (for speed). 1) I prepare my message to send using InetLab, this splits the message into 1 or more parts that are required. 2) I store the 1 or more parts in a 'messagesend' sql table, and use the unique record id of each message to set the 'sequence num...
by NickAskew
Wed Feb 29, 2012 12:34 pm
Forum: Inetlab.SMPP v1.0
Topic: Message Loss while using asynchronous message sending
Replies: 20
Views: 128355

Re: Message Loss while using asynchronous message sending

Hi Major The ESME_RTHROTTLED is returned with the Message Id and Sequence number. When you send any message you always receive a unique identifier (Message Id) from the SMSC, you need to store this alongside the message in your (sql table? - I use the unique id of each message record as the sequence...
by NickAskew
Thu Feb 09, 2012 2:04 pm
Forum: Inetlab.SMPP v1.0
Topic: Message Loss while using asynchronous message sending
Replies: 20
Views: 128355

Re: Message Loss while using asynchronous message sending

Hi

You will have to implement your own throttling code. Keep a counter going that resets every 1 second, if the counter > 20 then pause 10ms and check again.

Cheers
Nick
by NickAskew
Thu Feb 02, 2012 2:03 pm
Forum: Inetlab.SMPP v1.0
Topic: Message Loss while using asynchronous message sending
Replies: 20
Views: 128355

Re: Message Loss while using asynchronous message sending

Ask the SMSC which PDU they return that contains the Throttle Response. The SMPP v3.4 Specification says this: The command_status field of an SMPP message response indicates the success or failure of an SMPP request. It is relevant only in the SMPP response message and should be set to NULL in SMPP ...
by NickAskew
Mon Jan 30, 2012 2:05 pm
Forum: Inetlab.SMPP v1.0
Topic: Queue empty error.
Replies: 3
Views: 9735

Re: Queue empty error.

Works perfectly now, many thanks.
by NickAskew
Mon Jan 30, 2012 1:21 pm
Forum: Inetlab.SMPP v1.0
Topic: Queue empty error.
Replies: 3
Views: 9735

Re: Queue empty error.

Hi Alexey,

Further information:

The error still occurs even when I don't do any work in the SmppServer events - it happens after receiving 10000+ submissions which have been sent at around 400 per second. It isn't related to me sending the same client DeliverSm's.

Regards

Nick
by NickAskew
Mon Jan 30, 2012 1:07 am
Forum: Inetlab.SMPP v1.0
Topic: Queue empty error.
Replies: 3
Views: 9735

Queue empty error.

Hi Alt, I am receiving the exception below when I am stress testing the SMPP Server component. I am receiving approximately 250 SubmitSm's per second from a single ESME, and delivering DeliverSm's back to it using SmppServerClient.Deliver within another thread at approximately the same rate. System....
by NickAskew
Sun Jan 29, 2012 10:58 pm
Forum: Inetlab.SMPP v1.0
Topic: Message Loss while using asynchronous message sending
Replies: 20
Views: 128355

Re: Message Loss while using asynchronous message sending

Hi MajorTargets, Do you check the command_status of the returned SubmitSmResp? I have noticed one of our providers simply drop the DeliverSm if I attempt to send more messages to them per second than is in our contract - They should send back a throttle response but this provider doesn't support it....
by NickAskew
Sun Jan 29, 2012 10:46 pm
Forum: Inetlab.SMPP v1.0
Topic: Message encoding & submit mode detection
Replies: 4
Views: 13220

Re: Message encoding & submit mode detection

Hi Shazia1, You need to determine before you send the message whether it requires a unicode character set or whether the characters used could be sent via GSM character set. Arabic would need to be UCS2, which allows you to send 70 symbols at a time, so a message using 150 Arabic characters would ta...
by NickAskew
Wed Jan 25, 2012 12:44 am
Forum: Inetlab.SMPP v1.0
Topic: DeliverSm.Serialize throwing exception
Replies: 1
Views: 6146

Re: DeliverSm.Serialize throwing exception

I downloaded v1.0.12.2 and it has fixed the problem, so no investigation required - thanks!
by NickAskew
Tue Jan 24, 2012 9:36 pm
Forum: Inetlab.SMPP v1.0
Topic: DeliverSm.Serialize throwing exception
Replies: 1
Views: 6146

DeliverSm.Serialize throwing exception

Hi Alt, Inetlab.SMPP v1.0.11.3 I can't serialize a DeliverSm, it keeps throwing an exception, the stack trace is as follows: StackTrace " at Inetlab.SMPP.PDU.DeliverSm.WddAOCwt0e() at Inetlab.SMPP.PDU.DeliverSm.GetBytes() at Inetlab.SMPP.PDU.DeliverSm.Serialize(DeliverSm deliver) at tms.SmscProcesso...
by NickAskew
Tue Oct 25, 2011 3:23 pm
Forum: Inetlab.SMPP v1.0
Topic: Missing Question Mark using DataCodings.Default
Replies: 7
Views: 16080

Re: Missing Question Mark using DataCodings.Default

v1.0.11.3 has fixed the issue, many thanks for such a quick turnaround :)
by NickAskew
Mon Oct 24, 2011 6:51 pm
Forum: Inetlab.SMPP v1.0
Topic: Binary messages
Replies: 7
Views: 15974

Re: Binary messages

RE: Intelisense
I am using the compiled library v1.0.11.1 and Intellisense is working fine for me in Visual Studio 2008 and Visual Studio 2010.