>> The connector list parameter can only limit the routing options,
>> it cannot route the messages to a connector that is not in the original routing table.
That would kind of work I think, as it's broadly the same thing in my use case, however ...
>> If you are interested I can send you a plugin for the Scripting Gateway and a script
>> that uses the option.
Yes please! Anything that furthers my understanding of what I can do in the scripts is always welcome, and that would, I think, be perfect for me.
At the moment the script in the Scripting Gateway does not offer a way to route the messages to a specific connector. It is possible to do this with an HTTP Callback script by returning the 'connector_list' parameter in the response to the 'message_in' HTTP callback call. The connector list parameter can only limit the routing options, it cannot route the messages to a connector that is not in the original routing table.
It is not difficult to add an option to the Scripting Gateway to be able to set the connector list in the script itself. If you are interested I can send you a plugin for the Scripting Gateway and a script that uses the option.
I might be over thinking this, but ...
Each customer that comes in to my scripting gateway may have to go over a different connector. I was wondering how I would choose a specific connector in the script, if that's even possible.
I could obviously start a new scripting gateway for each customer, but that just seems wasteful to me to start so many http servers. Maybe there's not much impact? I don't know.
In the 'Gateways' settings of each connector, you can specify from which gateways the connector receives inbound messages. You can see the routing in the status window of the gateways, the inbound messages are routed to all connectors with a blue arrow in the routing icon.
How does this mechanism choose the connector to send the message over? I guess it uses the connector that has the scripting gateway in the "gateways" part of the config.
Is there any way to override this and choose the connector programatically in the script?
Thanks for the notification, I have updated the script in the Scripting Pack to fix this issue.
Just to say I put the word "redacted" in angle brackets for the http address, and they got stripped.
This works great, apart from one thing.
If I do this, the first field is blank, whatever it is (in this example, "to") :
but if i do this - put a dummy first field in - then all is good :
The easiest way to do this is to use a Scripting Gateway with a script that starts an HTTP server and routes the messages back to an SMPP Connector. There is no need to use a Web Connector for this functionality.
The Scripting Pack that you can download from the download page of this website contains a script that starts an HTTP server. You can find it in the folder 'GatewayScripts\ClickatellCallbackScript' of the Diafaan_Scripting_Pack.zip file. The script is made for inbound messages from the Clickatell SMS service but you can use it without change for your application as well.
With this script, the SMS messages are forwarded to the SMPP Connector as inbound message and sent as 'deliver_sm' SMPP packets to the SMPP client.
Actually, I assume I must connect the web conne3ctor to a scripting gateway to forward the message back to the smpp connector?
I have a need to send inbound messages arriving on a Web connector to an SMPP customer who has to connect to me (via an SMPP connector).
I can only see options to send to a gateway. Is there a way to achieve this?
Most Users Ever Online: 494
Currently Browsing this Page:
Guest Posters: 590
Newest Members:, Henk Helmantel
Administrators: Henk Helmantel: 1239