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
Sending message from ESME to SMPP:
For this I have created a connector in between Jasmine and SMPP. And added a MT router to this connector and the Flow is working fine.
Sending message from SMPP to ESME:
For this I have created a Connector in between Jasmine and ESME, but when I check the connection status using 'smppccm --l', it is not as BOUND_TRX/BOUND_TX.
From SMPP to Jasmin the messages are received in jasmine but those messages are not sending to ESME.
And also, I have created the MO router also. Due to this, my messages are not reaching ESME.
Can you please help us to resolve this issue.
The text was updated successfully, but these errors were encountered:
Hello @raghupradeep0702,
I was also looking for this solution but later found a work-around. I don't know whether it's Jasmin Bug or not but it's serving the SMPP to ESME SMS forwarding purpose..
So, I created a SMPP connection with SMPPSIM and named the CID, same as ESME user name.
Then placed that SMPP connection on MO-Router.
Now, whenever any MO-SMS is landing to Jasmin it automatically forwarding the DeliverSM of that SMS to the ESME
Hi @farirat
My flow is
ESME <-----> Jasmine SMS Gateway <------> SMPP
Sending message from ESME to SMPP:
For this I have created a connector in between Jasmine and SMPP. And added a MT router to this connector and the Flow is working fine.
Sending message from SMPP to ESME:
For this I have created a Connector in between Jasmine and ESME, but when I check the connection status using 'smppccm --l', it is not as BOUND_TRX/BOUND_TX.
From SMPP to Jasmin the messages are received in jasmine but those messages are not sending to ESME.
And also, I have created the MO router also. Due to this, my messages are not reaching ESME.
Can you please help us to resolve this issue.
The text was updated successfully, but these errors were encountered: