You can move the configuration of Diafaan SMS Server from one server to another by moving the folder 'C:\ProgramData\Diafaan\Diafaan Message Server\' and all of its sub-folders. The location of the 'ProgramData' folder can be different on older versions of Windows. Make sure you stop the Diafaan SMS Server service and close the console program on both servers before copying the folder.
How can we import the configuration (Configuration.xml) when will carry Diafaan SMS Server from the test server to a production server ?
We usually release a new version of Diafaan SMS Server once every 4 to 5 months or so. The next version will probably not be released before March 2016. It is not guaranteed that any of the new features discussed in this topic will be included in a new version.
We can provide plugins to customers with a valid license that is still in the free support and update period for new features that are contained within a single Gateway or Connector. But changes to the core of Diafaan SMS Server are only available in a new release.
When can we expect the release of the version with the updates that we discussed in this post ?
The reports in Diafaan SMS Server are calculated on the fly from the send- and receive logs. That means that the reports only contain the messages that are still in the logs, messages that are already removed from the logs are not included in the reports.
Since the send- and receive logs count a long multi-part SMS as one message, the message count in the reports can be different from the message count in the statistics of the separate gateways. If you need a consistent and reliable message accounting then you can use the HTTP callback functionality of Diafaan SMS Server or calculate your reports from your own SQL database. The reports in Diafaan SMS Server are only intended to give a general idea about the number of messages that are sent and received.
I will add your suggestion about the send log layout to the list of requested new features.
Notice that incorrectly calculated the number of messages in reports (reports). Checked several times to different SMPP clients. Perhaps this is also related to the number of parts.
Also, it will be convenient to see on the tab "Send log" the name of the modem through which a message is sent.
I have been able to replicate this problem, it turns out to be a bug in the handling of long multi-part message in combination with the send limit of the GSM Modem Gateway of Diafaan SMS Server version 22.214.171.124 or lower.
This bug will be fixed in the next version of Diafaan SMS Server, users of Diafaan SMS Server with a license that is still in the free upgrade and support period can send an email to firstname.lastname@example.org with a request for a plugin with a temporary solution for the bug.
When sim cards exceeded the limit of SMS messages, the program still tries to send messages via this modem and we get the message: "300, Error: Send limit reached: 250D". On another modem even there is traffic, but the message is not delivered.
I'm afraid that the market for SMS software like Diafaan SMS Server is not large enough to support sales offices all over the world.
In response to an earlier question about the validity period, the current version of Diafaan SMS Server does not support custom validity period per message. It is only possible to set a gateway specific validity period for the GSM Modem Gateway and the SMPP Gateway. If you send a message with a specific validity period from an SMPP Client to the SMPP Connector of Diafaan SMS Server, the validity period is ignored.
We will have a look to see if the option to specify a different validity period per message for messages sent from the SMPP Connector can be added to a future version of Diafaan SMS Server.
Thank you, I will be grateful. This is very important for our business.
Have you thought about opening a representative office for the sale and implementation of Your product in Russia ?
I'm sorry, I thought your question was about the SMPP Gateway in Diafaan SMS Server instead of the SMPP Connector.
At the moment, the SMPP Connector can only return the status 'UNDELIV' in the receipt when the message could not be delivered. I will put the functionality to return the status 'EXPIRED' on the wish list for the next version of Diafaan SMS Server.
As a gateway we are using GSM modems, as the server SMPP Connector. For each modem, set the ValidityPeriod parameter in the advanced settings. In excess of the period in the logs of the gateway see status "70, Message validity period expired", but Diafaan SMPP Connector still gives the status of SMPP clients "not delivered" (UNDELIV) instead of "expired" (EXPIRED).
If the SMPP server sends a receipt back to Diafaan SMS Server with the status 'EXPIRED', Diafaan SMS Server will update the status of the message from 'Sent' (status code 200) to 'Error' (status code 301). But if the SMPP server does not send a receipt back to Diafaan SMS Server the status will stay 'Sent'.
We need to SMPP server Diafaan gave status EXPIRED after expiration of Validity period in the received message. Is this possible ?
The status 'Sent' in Diafaan SMS Server does not mean that the message hangs, it merely means that the message is sent to (and accepted by) the SMPP server. The status will only be changed to 'Error' or 'Received' when Diafaan SMS Server receives a delivery report from the SMPP server.
Not all SMPP servers allow a custom validity period, in that case the SMPP server will ignore the 'ValidityPeriod' property of the SMPP Gateway of Diafaan SMS Server and set the validity period to (usually) three days.
Created a smpp gateway in the program. Connect client message to be sent indicating the Validity period = 10 min. For undeliverable messages at this time we have not received the status of the delay of the message. They remain hanging as sent.
Thanks for the prompt reply.
Will test further.
Do You have an office in Russia?
We want to pay for the software by Bank transfer to the settlement account of our organization.
A message with status code 301 means that the message was sent successfully by Diafaan SMS Server and accepted by the mobile operator but that it could not be delivered to the mobile phone. The 'Service rejected' error does not specify the exact reason for the error, it could be an invalid number or unsupported number format, or perhaps the number belongs to another mobile network that does not have SMS roaming with the SIM card you use.
The error codes (in this case error code 99) that the mobile operators return do not always give a reliable indication of the real cause of the error, the only thing that is certain is that the message was not delivered to the mobile phone.
Hello, considering to buy Your product. Now test and sometimes get a similar status:
Status: 301, Status error received after the message was accepted by the GSM operator.
Error: 99, Service rejected
What do they mean ?
Most Users Ever Online: 494
Currently Browsing this Page:
Guest Posters: 539
Newest Members:, Henk Helmantel
Administrators: Henk Helmantel: 1067