SMS GATEWAY CONFIGURATION
HTTP Messaging Gateway Interface document Version: 0.1
SMS GATEWAY INFORMATION NEEDED FROM YOU
Customer SMS Gateway URL: (the URL destination of the messaging gateway)
Secondary SMS Gateway URL:
Gateway Client Secret:
Security Token: (GTIGLOBAL will provide)
Message Gateway - Configuration GTIGLOBAL Messaging Gateway is configured as part of GTIGLOBAL Application server.
Partner must implement an interface to GTIGLOBAL Provisioning API or provide the above configure. The configuration items include the following items that must be configured per GTIGLOBAL Message Gateway.
● Primary URL ● Secondary URL ● Client Security Token ● GTIGLOBAL Security Token Primary URL Secondary URL Required Optional GTIGLOBAL Messaging Gateway uses this URL to send the HTTPs requests to the UCaas Server. This URL is always the first option used to deliver an Http Message. If the Primary Server returns an error. The GTIGLOBAL Messaging Gateway may try to deliver the message to the secondary server. See the section on Response Code Handling to understand when the secondary server is used. Client Security Token GTIGLOBAL Security Token Required Required Any Request delivered to the GTIGLOBAL Messaging Gateway must contain an Bearer Authorization Header containing this token. Any Request delivered to the UCaas server must contain an Bearer Authorization Header containing this token.
Termination URL When the UCaas server sends a request to GTIGLOBAL Messaging Gateway. The URL needs to be as follows: https://messaging.mobileuc.global:8445/GTIGLOBALMsgGateway/v2/message
Store And Forward In the case where a message fails to deliver to the UCaas Server. GTIGLOBAL Application server could perform store and forward where the request is stored and delivered at a later time. GTIGLOBAL Application server performs store and forward based on the error response received from the UCaas server. Any response considered a temporary failure is processed by the store and forward service. Refer to the section on Error Responses for information on which responses are considered permanent or temporary. A message that has been stored is tried again roughly every 30 seconds and will persist for 7 days.
After which the message is discarded. These durations are controlled by GTIGLOBAL and cannot be changed by a customer. In order to maintain message order. After a subscriber’s message has been placed into the Store and Forward service. All future messages for this subscriber are automatically placed in the store. The messages are then delivered based on the re-try timer (30 seconds) and delivered based on the order placed in the store service.
Group Messaging Group Messaging is supported. Each recipient of the message is contained in the list of TO users. All Group messages delivered as an MMS type message. Origination Group Messaging When a subscriber originates a group message. GTIGLOBAL Messaging Gateway delivers a single MMS message to the UCaas Platform. The To field contains the number of each participant that needs to receive the message. Termination Group Messaging When a 3rd party generates a group message. The UCaas Server is expected to send a message to GTIGLOBAL Messaging Gateway for each GTIGLOBAL Subscriber (SIM) that is part of the group.
The To field contains the number of each participant that needs to receive the message. The Owner field contains the number of the subscriber that receives this message.