Henk Helmantel said
The SMPP Gateway can set up an SSL connection to the SMPP server without installing an SSL certificate on Diafaan SMS Server, the SSL certificate of the SMPP server is used to secure the encrypted connection between the SMPP Gateway and the SMPP server.
Ahhh, that's the thing I was missing.
The SMPP Connector is not intended to receive MO messages from SMPP clients. The normal procedure to receive MO messages is to use the SMPP Gateway in Diafaan SMS Server to connect to the SMPP server that can deliver these messages to you. The SMPP Gateway can set up an SSL connection to the SMPP server without installing an SSL certificate on Diafaan SMS Server, the SSL certificate of the SMPP server is used to secure the encrypted connection between the SMPP Gateway and the SMPP server.
You are now using the SMPP Connector to receive MO messages from the SMPP client, this is possible but it is not the normal procedure and it is not the way that SMPP normally works. The messages are actually sent as MT messages to Diafaan SMS Server and are therefore regarded as outgoing messages. They will be put in the the send log and not in the receive log of Diafaan SMS Server and the HTTP callbacks will be sent as 'message_out' instead of 'message_in'.
Sorry I missed a bit off -
How can I stop the connector from trying to forward the message? I only have it to provide SSL, I don't want it to even attempt to send it anywhere.
Thanks for your patience 🙂
Thank you for your detailed reply, and please forgive my slowness as I try to understand this.
My context at the moment is purely MO (my customer binds as a transceiver and sends me messages)
Just to confirm - I do need the connector for the certificate, don't I? What I mean is it's not optional if I want SSL? I'm sure that's right otherwise there's no other way to add a certificate, and I can't see how the gateway can use ssl without one.
So my client's MO message (from him to me) would have come into the gateway and then passed into the connector, yes? So why do I not have a message in the received log of the gateway? All I have is a failed send in the connector (because there is no onward gateway).
There is no difference in functionality between SSL and non-SSL SMPP connections in Diafaan SMS Server. If you want to use SSL connections in the SMPP Gateway you can check the 'Use SSL/TLS' option in the 'SMPP server' settings of the SMPP Gateway. In the SMPP Connector, you can add a (self-signed) SSL certificate in the advanced settings to enable SSL. The HTTP callback is exactly the same for SSL and none-SSL connections.
The message flow in Diafaan SMS Server goes from the connectors to the gateways for outgoing Mobile Terminated (MT) messages and from the gateways to the connectors for Mobile Originated (MO) messages. For the SMPP Connector and SMPP Gateway this means that the SMPP Connector accepts messages from SMPP clients and forwards them to an SMPP gateway. The SMPP Gateway sends the messages to an SMS service that delivers them to the mobile phones (MT). Messages from the mobile phones (MO) are received by the SMPP Gateway from the SMS service and forwarded to the SMPP Connector which sends them to an SMPP client.
If you use HTTP callbacks, outgoing (MT) messages trigger a 'message_out' HTTP callback in the SMPP Connector. incoming (MO) messages trigger a 'message_in' HTTP callback in the SMPP Gateway. The 'message_out' corresponds with a 'submit_sm' SMPP packet and the 'message_in' with a 'deliver_sm' SMPP packet.
If you only want to log the messages with the HTTP callbacks then you can use an SMPP Gateway or an SMPP Connector depending on what is most convenient for you. The information in the 'message_out' HTTP callback and the 'message_in' HTTP callback is slightly different but the basic message parameters are available in both HTTP callback calls.
I probably should add what it is I'm trying to achieve.
Most of my connections are non-SSL SMPP transceiver binds. I receive messages and log them to a file using the http callback service. These files get processed externally, mostly by parsing the "message_in" records. I don't normally forward these messages to another gateway.
I need that setup, but just with SSL enabled, and the only way I could see to do that was to add a connector.
Whilst I don't do it yet, I may at some point need to send messages over the transceiver bind.
Hi, I'm struggling to understand the relationship between SMPP gateways and SMPP connectors.
Here's my set up -
I have an SMPP connector with a self signed certificate generated by Diafaan.
I have an SMPP gateway to my client containing the systemid/etc. credentials and SSL checked.
The SMPP gateway appears in the gateways tab of the connector for send and receive.
My client sent me a message which appears in the connector "send" log.
The HTTP callback logs the message as a "message_out".
The message fails with "300 erro: no gateway available"
Here's my lack of understanding -
Why is it a message_out and not a message_in like it would be on a non-SSL gateway?
Can I treat it as a message_in? If so, how?
I don't want to forward it anyway, just accept it and log it (which works fine on a regular SMPP gateway using http callback)
Do I need to set up two connectors for this to work - the one I have now to receive messages and another one to act as a dummy outgoing so I can log them? Maybe an http?
I think I don't understand how the relationship between connectors and gateways works, what order or priority they deal with incoming messages. Please can you help me understand?
Most Users Ever Online: 494
Currently Browsing this Page:
Guest Posters: 590
Newest Members:, Henk Helmantel
Administrators: Henk Helmantel: 1239