Diafaan SMS Server does not have an option to close an individual connection at a random time but it is possible to close a connection when the client is sending a message.
If the response of a 'message_out' HTTP callback contains the parameter 'close_connection=1', the SMPP Connector will close the connection to the client after handling the message. The combination 'result=0&close_connection=1' rejects the message and closes the connection.
Ok its clear we have used SMPPSIM and its working fine for the sumliations.
Last question , how we can closed the client smpp connection example
Client A connected to Diafaan SMPP connector , and for some reasons we need to force his connection to be closed.
As for now the accept connection call back only doing the checking one time when the client will established his connection to us for the first time.
But how about if we want to terminate his connection to diafaan smpp connector ? is there anyway for that ?
The Emulator Gateway does not actually send any messages and does not split long messages. The message is handled internally as 1 message and that is the number you see in the send log.
There is no fixed formula for the number of message parts of a single long message, it depends on the gateway that is used to send the messages, how the gateway is set up and on the Message Type of the message. For instance if you send a long message with the HTTP Gateway it is usually sent in 1 message part, the same message can be sent in 2 message parts if it is sent with a GSM Modem Gateway or SMPP Gateway and even 3 or 4 message parts if the Message Type is set to 'sms.unicode'.
If you want to test the message part count, you can set up a 2nd server with a trial license of Diafaan SMS Server using an SMPP Connector and an Emulator Gateway. You can then use that server to send the messages from an SMPP Gateway on your primary server and the message part count will be correct for the type of gateway and the settings that you want to use. You can also do this on a single server but that slows down performance and makes testing more complicated.
The issue with long message , for the sending not receiving , note we are not using any GSM , all our connections are SMPP connections.
So the emulator issue , is when we sent a long sms the message parts came at the smslog which it will be saved at sql server side as 1 part not the actual number of the message parts.
Same time on real smpp connection with smsc the message parts working fine and been inserted in the sql in correct way, so the issue in the emulator it self.
can you please check , just send long message either english or unicode to the emulator and check the message parts counting.
Thank you for the purchase of Diafaan SMS Server.
Can you explain in more detail what goes wrong with the long messages? Is the problem related to outgoing messages or oncoming messages? Are the long messages received in multiple parts or only the first 160/40 characters?
When SMS messages are sent with a GSM modem, Diafaan SMS Server takes care of splitting and combining messages in multiple messages parts. However, when the messages are sent and received by the GSM Modem Emulator on an Android phone, Android takes care of the splitting and combining of the message parts itself. The GSM Modem Emulator sends the long message to Android and receives the long messages from Android. If the message parts don't work as expected, it could be an issue with the specific version of the Android phone that you are using.
Thank you for the observation that the full HTTP callback option is faster in your case. This will be different on different servers but when we developed the HTTP callbacks we noticed that on some servers the full HTTP callback handling was unusable slow. That is the reason that we added a lightweight 'quick and dirty' HTTP callback option as well. Apparently the full HTTP callback option is not always slower.
We have already bought the full edition version our order id is : **
The emulator have issue when we are sending long SMS Unicode or English the message parts still showing 1 instated of 2 or 3..etc.
Please check ASAP , as we are doing the final test for all our integration .
BTW we are able to send 900 SMS per second with your software , we have add Redis and Mysql and SQL server for the log messages, we have achieved that by make load balancing with multi connectors.
Another note for you is the HTTP call back full option is faster more than the HTTP call back simple option
Most Users Ever Online: 494
Currently Browsing this Page:
Guest Posters: 629
Newest Members:, Henk Helmantel
Administrators: Henk Helmantel: 1342