You only have to use the message_out HTTP callback to change the routing of messages from the SMPP Connector to the SMPP Gateway. The message_in HTTP callback is used for inbound messages, messages that are received by the SMPP Gateway and routed back to one or more of the SMPP Connectors.
The message_out HTTP callback can only be used to limit the default routing of the connector, it can't be used to expand the routing to a gateway that is not in the routing table of the connector. For instance , if you have one connector, Connector1, and three gateways, Gateway1, Gateway2 and Gateway3, and Connector1 routes the messages to Gateway1 and Gateway2, you can use the message_out HTTP callback to route the message to Gateway1 only, but not to Gateway3.
Sorry I'm struggling again to work something out.
I have an SMPP Connector (server) accepting messages from several users. I want all the messages received over this connector from one specific user_id to go straight out over an SMPP gateway. I don't want any other user_id's to be affected by this routing.
I thought I could do that via the HTTP callback result (using result=1&gateway=xxx) but that seems only to work with "message_out" and not "message_in". I don't see how I can hardwire the connector to the gateway in the connector properties as that will surely affect all users?
Is this possible to do or will I have to split this user into a new connector? I'd rather not if it's possible.
Most Users Ever Online: 494
Currently Browsing this Page:
Guest Posters: 634
Newest Members:, Henk Helmantel
Administrators: Henk Helmantel: 1353