short questions about InetLab

.NET library for SMPP protocol
Locked
rayxelloss
Posts: 2
Joined: Tue Jun 14, 2011 3:54 am

short questions about InetLab

Post by rayxelloss » Tue Jun 14, 2011 4:03 am

I am searching a smpp client library to help me work with smsc.
But I have a little questions about Inetlab.
Did Inetlab support unicode character when submit or recevie the message?
Did Inetlab support the windows size setting in this library?
Did Inetlab support the deliver report since we submit an submit_sm to smsc?
Did Inetlab support the option field like message_payload to receive/submit a long message ?
alt
Site Admin
Posts: 985
Joined: Tue Apr 25, 2006 9:45 am

Re: short questions about InetLab

Post by alt » Tue Jun 14, 2011 8:45 am

Yes, Inetlab.SMPP supports unicode characters.
Inetlab.SMPP is class library, there is no Windows Forms part.
Yes, Inetlab.SMPP supports delivery receipt.
Yes, Inetlab.SMPP supports optional TLV parameters.
rayxelloss
Posts: 2
Joined: Tue Jun 14, 2011 3:54 am

Re: short questions about InetLab

Post by rayxelloss » Tue Jun 14, 2011 8:55 am

Sorry, the window size is the message traffic in one second.
Can I set how many message I can recevice and sent persecond?
We may need over 1000/ per second.
alt
Site Admin
Posts: 985
Joined: Tue Apr 25, 2006 9:45 am

Re: short questions about InetLab

Post by alt » Wed Jun 15, 2011 8:14 pm

Only methods SubmitText and AdvancedSubmit use limit of messages per minute.
These methods use property client.SubmitSpeed.
Some SMSCs have limit of allowed SMS per minute. And when this limit is exceeded, SMSC returns status ESME_RTHROTTLED.

All other methods do not have limits. So SMS traffic depends on network and hardware.

You can test performance with applications SmppClientDemo and SmppServerDemo.
Locked