Couldn't recieve SMS from SMSC about node-smpp HOT 7 CLOSED

The MO (received message) have esm_class different of 4.
But despite of this you have to check with your broker if the connection that you use support 2-way message

from node-smpp.

@guicuton thanks, I found that the SMSC I am using only uses SOAP to send MO messages to my application, therefore it doesn't really relate to SMPP.

from node-smpp.

Hello @guicuton
I tried bind_transciever and actually, I am getting MO messages but one issue here is when the user sends some keywords that trigger the subscription to my service I am not receiving those messages, in my case 'OK' is for subscription and 'Stop' is to unsubscribe.

Any ideas on this?

from node-smpp.

Hello @guicuton
I tried bind_transciever and actually, I am getting MO messages but one issue here is when the user sends some keywords that trigger the subscription to my service I am not receiving those messages, in my case 'OK' is for subscription and 'Stop' is to unsubscribe.

Any ideas on this?

Usually the SMSC only will send the MO to you as an answer of a MT.

If your user is sending, for example "OK" (doesn't matter the word) for your shortcode without being an answer from a previous MT that you sent to him this message will reach your SMSC provider but they will not know to which client they have to reflect the MO, which means that you'll not receive the message.

To work with keywords you have to check with your SMSC provider if they support work with keywords and if they have the keyword available for you.

Once they have settled up for you the shortcode and the keyword, every time that someone sends "ok" for your shortcode 29999 you will receive the message on deliver_sm event

from node-smpp.

If your user is sending, for example "OK" (doesn't matter the word) for your shortcode without being an answer from a previous MT that you sent to him this message will reach your SMSC provider but they will not know to which client they have to reflect the MO, which means that you'll not receive the message.

But as I said earlier, I am receiving MO messages already (with the bind_transceiver method) here is an example I am outputting sending SMS from my phone:

Oct 20 15:38:35 fedora node[11193]: { message: 'Hey ' }
Oct 20 15:39:03 fedora node[11193]: { message: 'Hey ' }
Oct 20 15:39:25 fedora node[11193]: { message: 'Hey ' }
Oct 20 15:39:37 fedora node[11193]: { message: 'Test' }

But as I send Ok and Stop it won't send to my application, that's what confused me.

To work with keywords you have to check with your SMSC provider if they support work with keywords and if they have the keyword available for you.

The keywords are 'OK' for subscription and 'Stop' for unsubscribe. If they subscribe with OK they will receive SMS sent from my application.

Once they have settled up for you the shortcode and the keyword, every time that someone sends "ok" for your shortcode 29999 you will receive the message on deliver_sm event

I have a shortcode for both MT and MO, currently, I am only using an MT shortcode to send SMS, but I have no clue where I need to use the MO shortcode in my code.

from node-smpp.

@guicuton any ideas on my reply?

@farhadi @juliangut any suggestions on this issue?

Thanks

from node-smpp.

Well, finally it seems the SMSC is sending the MO messages through HTTP post request with an XML request body, that way I am parsing the request body to receive the details.

from node-smpp.