it's fixed but for some reason the Reference number jump's in odd number (not critical but just to know)

yes fixed!

Hi Alt,
i tried to do a load test,
sent to 10200 phones with 300 chars.
the DLR in my db toke : 262 seconds
the DLR to my log toke : 528 seconds,
this is after i sent them in groups (more the one time in a DeliverAsync command).
all is done on my pc.
any way to improve it?
is it a reasonable time?

Hi alt,
first question : is i call a lot of times the DeliverAsync,
and not all released yes, it there some property that will should me how many are waiting to be Delivered,
something that you have in the Metrics that should how many not sent yet (for SubmitSm?

No,
this is why i asked if there is possible a queue of the DLR? and how to check it
is there something under the Metrics for this?

one of my customers complains about missing/big delay of DLR
when i use client.DeliverAsync, without await first,
is it possible that there is some queue that wait for release ?
how can i check it?

i switched to : Inetlab.SMPP.2.8.1-beta-2021
run the test twice:
one all was ok, 100K messages and no duplicates.

i am running the next code which sender to 100,000 phones in speed of 100/sec.
i see in the db that some of the number that received in the , so i added a log and i see :

2020-05-20 11:55:04.4614 WindowsServiceTemplate.SMPP.SmppServerManager::ToNumber=0500003304
2020-05-20 11:55:04.4614 ...

i tried but still the Reference on the server side is 0

i tried to do : but still the Refernece number is 0
should i do something else too?

i can't find in the documents how send wap
can some one assiste?

this is good
did you add it already?

is there a ready method to check if a text is GSM or not?
so i can set the correct coding?

can you tell me what error to take on the dissconnect event?from which object?