Support forum

Advanced Search

— Forum Scope —




— Match —





— Forum Options —





Minimum search word length is 3 characters - maximum search word length is 84 characters

sp_TopicIcon
What is the difference between the pause-sending and stop-gateway API commands
sp_NewPost Add Reply sp_NewTopic Add Topic
December 19, 2023
10:43 am
Henk Helmantel
Admin
Forum Posts: 1502
Member Since:
May 28, 2013
sp_UserOfflineSmall Offline

If you do not need to process incoming messages and delivery reports when the capacity is maxed out then the best option is probably the 3rd option. After the gateway is disabled with the HTTP API call, the messages are still routed to the other gateways in the routing table of the connector.

If you make the HTTP Gateway a primary gateway in the routing table and the other gateway(s) a backup gateway, the messages will be sent with the HTTP Gateway if the gateway is enabled and with the other gateway(s) if the HTTP Gateway is disabled.

Regards, Henk

December 18, 2023
12:55 pm
Sorin
Guest
Guests

My final goal is that after the capacity is maxed out, no more messages are routed to this gateway and any remaining messages are routed to different gateways until the capacity is freed up. How would I achieve this ?

December 18, 2023
10:33 am
Henk Helmantel
Admin
Forum Posts: 1502
Member Since:
May 28, 2013
sp_UserOfflineSmall Offline

Hello Sorin,

There are three ways to disable the gateway with an HTTP API call, each have a different effect:

1. Pausing the gateway for sending means that sending of the messages through this gateway is paused. The message stay in the send queue until the gateway is resumed or re-started (or if they are sent with another gateway). The gateway is still active and still receives messages and handles delivery reports:
http://localhost:9710/http/send-server-command?username=admin&password=&command=pause-sending&gateway=HTTP+Gateway

2. Stopping the gateway disables the gateway temporarily. The gateway is completely inactive and it does not receive messages anymore until the gateway is re-started. After a specific timeout the gateway is regarded as unavailable and pending messages are removed from the send queue:
http://localhost:9710/http/send-server-command?username=admin&password=&command=stop-gateway&gateway=HTTP+Gateway

3. Disabling the gateway disables the gateway completely and sets 'Enabled' to false. The gateway is regarded as unavailable and pending messages are removed from the send queue. To activate the gateway again you have to set the 'Enabled' parameter to '1' or check the 'Enabled' option in the gateway settings:
http://localhost:9710/http/send-server-command?username=admin&password=&command=set-gateway-property&gateway=HTTP+Gateway&property=Enabled&value=0

Changing the routing options is also possible but probably not the best option to disable the gateway.

Regards, Henk

December 17, 2023
11:36 am
Sorin
Guest
Guests

Related to this, I was thinking that I could use 'set-routing-property' API call to remove the gateway from routing when capacity becomes 0, but I can't figure out the parameters for that call, namely the 'property' parameter. What values can it have and what do they control ?

Thank you

December 16, 2023
12:32 pm
Sorin
Guest
Guests

I'm trying to figure out how to modulate the number of SMS sent via a HTTP gateway. I have a way to check the instant capacity of the gateway, and I was trying to issue a API command to stop the gateway from routing any more messages to that when the capacity is 0. However, even after stop-gateway, messages are still comming in.

What am I missing ?

Forum Timezone: Europe/Amsterdam

Most Users Ever Online: 529

Currently Online:
1 Guest(s)

Currently Browsing this Page:
1 Guest(s)

Top Posters:

Member Stats:

Guest Posters: 677

Members: 0

Moderators: 0

Admins: 1

Forum Stats:

Groups: 2

Forums: 3

Topics: 1149

Posts: 3928

Newest Members:

, Henk Helmantel

Administrators: Henk Helmantel: 1502