Message Id not matched signifies that the DLR received from vendor is not matching with Message ID which was originally sent in submit_sm response. For e.g. a. Message id recieved from gateway vendor in submit_sm response is c86d461a-a349-4354-8b3a-ae5614eb0541 b. Message id recieved from gateway vendor in deliver_sm request is 5b718c13-9372-4805-9d3a-2629b983add5 In that above case the […]
Event Viewer client option helps admin to monitor and collect all error and crash events that are affecting your user’s SMS traffic, full error log events are displayed to troubleshoot the problems. Please note: The logs are visible in the admin time zone.
This option helps you to capture the live message traffic entering in SMSC or going out, it’s used for troubleshooting the gateway or ESME user in real-time. This feature can be used when you don’t have a NOC team or don’t hold the network expertise.
ITextPro logs each message entered in SMSC or going out is logged for troubleshooting, a large amount of data is generated via PDU logger. iTextPro online PDU logger comes with a filter to trace the journey of any message in a single click for upstream [Gateway Vendor] and downstream traffic [SMPP User] and inspect the […]