Correlation-ID for sendRoutingInfoForSM and MTforwardSM

[Armache Antoni]

Hi good people,

I hope everyone made it so far...... and it's Friday.

I have a small issue when sending sms...... As i understand the technical flow when dealing with sms:

SRI >>> is sent firstly to (operator-HLR)

           Then MT-FORWARD-SM is sent after forwards.

******** How do we know or identified this specific MT-FORWARD come from this specific SRI ?

***** is there any value or correlation ID that is present in both SRI and MT-FORWARD ? I mean like a specific value present in both request....

**** I am thinking about scenarios dealing with large loads of sms .

[BarbosSergos .]

Hi Antoni,

SRIForSm_resp from HLR contains IMSI and MSC address(GT) which serve subscriber right now. So MT-FSM contains that IMSI and MSC address.

SRIForSM and SRIForSM_resp have same tcap_id, so you can correlate them. Same goes for MT-FSM and MT-FSM_resp.

Hope it'll help you.

Best regards,

Sergey Yashchenkov

--
You received this message because you are subscribed to the Google Groups "mobicents-public" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mobicents-publ...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mobicents-public/8887879b-7429-432b-a217-27808ca84749%40googlegroups.com.

[Vilius Panevėžys]

On Fri, 24 Jan 2020 07:31:52 -0800 (PST)
Armache Antoni <arma...@gmail.com> wrote:

> I have a small issue when sending sms...... As i understand the
> technical flow when dealing with sms:
>
> SRI >>> is sent firstly to (operator-HLR)
>
> Then MT-FORWARD-SM is sent after forwards.
>
>
> ******** How do we know or identified this specific MT-FORWARD come
> from this specific SRI ?

SRI is typically used before forwarding the message to get IMSI and
network node number, but it is not mandatory in case you happen to
"know" the current values. Hence, there is no 1 to 1 mapping between
SRI and forward SM messages in the general case.

To save the guesswork, could you describe what is the problem you are
solving? What is the scenario you are working on that makes you
look for the correlation?


--
Vilius Panevėžys
Elitnet

[Armache Antoni]

I have a SS7 firewall for sms between the SMSC and OPERATOR which block specific sms based on GT, message, source-number.

SMSC >>> FIREWALL >>> OPERATOR.

*** when i send MT-FSM i usually print the logs to kibana containing the following :

Source number | Destination number | sms | status-white or status-black | localGT | remoteGT

*** The problem is when i received MT-FSM there is no (Destination number) even in the TCAPtrace, as one of my requirement [ on receiving MT-FSM request ] i need to log the Destination number !!!!

*** So i took Destination number from SRI request and put it in a PUBLIC STATIC VALUE in my app then i was able to get it on MT-FSM request and log it ....... BUT THIS IS for 1 message scenarios.....

*** Upon performing bulk sms testing i quickly noticed that sometimes i am not getting SRI request just  MT-FSM.

*** In order for me to have a clean structure i need to make sure when logs are sent to kibana ... it belongs  to (SRI-REQUEST number1 and MT-FSM number1) As i am taking data from both Request.

I don't wanna end up getting data from (SRI number1 and MT-FSM number2) due to large volume of request ...... i wanna be sure the data correspond 

[personal gmail]

Hi Antoni,

the only choice you really got is:

- link SRI and SRI-response by TCAP transaction id. Based on SRI response you know how to link msisdn and IMSI returned for it

- pick corresponding MTForwardSM by IMSI

There is no other way to link the two. 

Best regards,

Ildar

24 янв. 2020 г., в 19:19, Armache Antoni <arma...@gmail.com> написал(а):



--
You received this message because you are subscribed to the Google Groups "mobicents-public" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mobicents-publ...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/mobicents-public/cfff822c-f2f6-4436-b66e-eff176e8e813%40googlegroups.com.

[Gaurav Singh]

Yes,

There is Mt-correlation Id defined in 3GPP-24.011 . The value is generated and sent in sri-sm-response which is expected to come in mt-fsm.

Regards

Gaurav

--

You received this message because you are subscribed to the Google Groups "mobicents-public" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mobicents-publ...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/mobicents-public/8887879b-7429-432b-a217-27808ca84749%40googlegroups.com.