No, you don’t need to create different SMPP accounts for the same user if you want to send through multiple gateways simultaneously because if the messages are received at the application from the downstream then you can create a MT routing rule from the routing rule manager for that particular SMPP user to route messages […]
1. Confirm if Client is able to telnet SMPP Server and Port 2. Confirm if Client is blacklisted (check on panel as well as on network level: (iptables -S)) 3. What error code is received on Bind response on Live PDU 4. Check the total SMPP Server socket connections (max sockets allowed=300) sudo netstat -plunta […]
If an ESME User is Blacklisted, and you want to remove from Blacklisting, Kindly Navigate to CONFIGURATION >> Manage Interface >> Seach the user >> Click on EDIT >> Advance settings >> Blacklisted >> DISABLE IT.
Is Async: In the majority of cases ‘Async’ should be checked to facilitate faster submission of traffic to SMSC using asynchronous mode. In rare condition, some SMSC supports only synchronous mode. SMPP Async mode is a windowing protocol: Each side of the connection is free to send multiple transactions without waiting for a response to […]
It depends on the Total ESME Client session
In case the gateway has not sent Message ID in the Submit_sm_repsonse, then the ItextHUB application will generate the fake DLR passing the same message ID as the system generated Alias Message ID. This can also be the case in any non-zero command status (non-zero error code) received in submit_sm_response from the gateway, resulting into […]
A matching ruleset (having best match parameters) with the highest priority will apply.
Kindly navigate to Configuration >> OA/DA Normalization Rule >> Add New >> Fill Up the parameters as required >> Configure CHANGE FROM parameters and CHANGE TO parameters .
OA/DA normalization: OA/DA stands for Originator Address and Destination Address. At times we need to normalize originator (source) / destination address of MO/MT messages which are entering/leaving our SMSC. These rules serve various purposes for manipulation of messages, source address & destination address.
Kindly navigate to Monitoring >> Event Viewer Client >> You can see the Re-initialization or Gateway session termination logs. Secondly, Navigate to Utility >> PDU Capture >> Capture the PDU.