SMS Received On Mobile Status Not getting Updated | Community
Skip to main content
K
krishnakanth_patnaik_cc
Level 3
August 11, 2023
Solved

SMS Received On Mobile Status Not getting Updated

  • August 11, 2023
  • 1 reply
  • 1310 views

Hi,

The functionality to update Status from "Sent" to "Received on Mobile" used to work.

It suddenly stopped working.

 

We raised this with Adobe team as well. 

 

We checked in nms:providerMsgId, and the status is showing as "Received on Mobile". But the same status is not getting updated in Delivery logs.

 

Did anyone face this issue. Is there any script or workflow which is being used in Back end to check this status and update it?

 

Any documentation for this will help.

 

We checked from SMS Vendor the data is coming from their side and getting updated in NMSProvider but not in Delivery logs

 

Thanks,

Krishna

 

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by aggabhi

Hi @krishnakanth_patnaik_cc ,

 

It seems that you are getting Deliver_SM from vendor correctly, The
identifier is stored in the providerId field of nms::providerMsgId and this is linked to broadLogId and deliveryId.

 

Matching operation between these 2 tables done by SMS process which is not working.

 

There is only 3 reason for same :-

 

1. Check that the sms process is up and running: check in the process list in the monitoring section of the console home page (you
can also use the "ps aux" linux command). Restarting the sms process will make it poll the web server immediately,

 

2. Check the regex which you have put in external account, seems regex which you are put in external account are not correct. Regex is responsible for reading the format of SR and if format doesn't match then it will fail to update the same.

 

3. Also make sure you do not have any other external account with same server+userid+ port number is not active on prod or in stage.

 

Regards

Abhishek

1 reply

A
aggabhiAccepted solution
Level 5
August 11, 2023

Hi @krishnakanth_patnaik_cc ,

 

It seems that you are getting Deliver_SM from vendor correctly, The
identifier is stored in the providerId field of nms::providerMsgId and this is linked to broadLogId and deliveryId.

 

Matching operation between these 2 tables done by SMS process which is not working.

 

There is only 3 reason for same :-

 

1. Check that the sms process is up and running: check in the process list in the monitoring section of the console home page (you
can also use the "ps aux" linux command). Restarting the sms process will make it poll the web server immediately,

 

2. Check the regex which you have put in external account, seems regex which you are put in external account are not correct. Regex is responsible for reading the format of SR and if format doesn't match then it will fail to update the same.

 

3. Also make sure you do not have any other external account with same server+userid+ port number is not active on prod or in stage.

 

Regards

Abhishek

    K
    krishnakanth_patnaik_ccAuthor
    Level 3
    August 17, 2023

    The inputs you provided. Shared these with Adobe and Vendor.

     

    Looking forward for their inputs.

    K
    krishnakanth_patnaik_ccAuthor
    Level 3
    August 29, 2023

    Issue was with regex setting.

    It's resolved

      Terms & ConditionsAccessibility statement

      Loading footer...