You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently use many cht-gateway phones for multiple SMS instances to send instant and scheduled messages. Our gateway phones are stored in a gateway rooms and are diagnosed remotely. However, when there's a case of message delivery failure or messages not sent until days, we need to remotly access phone and look into event log and scroll down to figure out the cause. Sometimes, by the time we realize there was an issue and check, the message is no longer in event log.
It'd be really helpful for us to have this information uploaded somewhere on the cloud like how we've log available for cht-api and sentinel.
The text was updated successfully, but these errors were encountered:
We currently use many cht-gateway phones for multiple SMS instances to send instant and scheduled messages. Our gateway phones are stored in a gateway rooms and are diagnosed remotely. However, when there's a case of message delivery failure or messages not sent until days, we need to remotly access phone and look into event log and scroll down to figure out the cause. Sometimes, by the time we realize there was an issue and check, the message is no longer in event log.
It'd be really helpful for us to have this information uploaded somewhere on the cloud like how we've log available for cht-api and sentinel.
The text was updated successfully, but these errors were encountered: