Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Specifying of SMSC GW GT and TT (TranslationType) by mproc rules #252

Closed
vetss opened this issue Sep 12, 2017 · 18 comments
Closed

Specifying of SMSC GW GT and TT (TranslationType) by mproc rules #252

vetss opened this issue Sep 12, 2017 · 18 comments
Assignees
Milestone

Comments

@vetss
Copy link
Contributor

vetss commented Sep 12, 2017

  1. Add int Sms class two extra fields that must be persisted in a database (defaul values are null)
  • String ServiceCenterGT
  • Integer ServiceCenterTT
  1. PostArrivalProcessor - add actions
  • updateServiceCenterGT(String val);
  • updateRemoteTT(Integer val);
  1. When SRI and MT message sending we need to use specified GT string / TT (if they were updated by mproc rules).

  2. add extra actions into defaul mproc rules that will set values
    mtlocalsccpgt ****
    mtremotesccptt ****

  3. we need to update a manual - chapter http://documentation.telestax.com/core/smsc/SMSC_Gateway_Admin_Guide.html#_mproc_rules_fundamentals

@vetss vetss added this to the SMSC-sprint3 milestone Sep 13, 2017
@faizann
Copy link
Collaborator

faizann commented Sep 20, 2017

Hi Sergey

I have picked this one up.

olenara added a commit that referenced this issue Sep 20, 2017
@vetss
Copy link
Contributor Author

vetss commented Sep 25, 2017

Hello @faizann

please hold on,, @olenara is processing the issue. Sorry, I have only today found your message.

@faizann
Copy link
Collaborator

faizann commented Sep 26, 2017

Roger that. I have done changes but I will take olenara.
We also have seen cases where SCCP CallingGT has to be set and is different from ServiceCenter GT. This happens when ServiceCenterGT is used to provide more info about the originating operator by adding MNC/MCC suffix. This is called OC Compliance in GSMA standard. We can add another param only for sccpCallingGt that overrides serviceCenterGt if found to be set else serviceCenterGt is used in both SCCP and MAP layers.

@vetss
Copy link
Contributor Author

vetss commented Sep 26, 2017

@faizann

  1. is it for MT messages only (or affects also MO/HR) ?
  2. if MT only - can we specify a pair of values (ServiceCenter GT and SCCP CallingGT) for each networkID value ? Or we need to specify several possible SCCP CallingGT for same ServiceCenter GT and we need mproc rules action for it (like "mtlocalsccpgt ****").

@olenara
Copy link
Contributor

olenara commented Sep 28, 2017

Fixed by:
f7c549e
18a9536
5d97c60
baf1429

@faizann
Copy link
Collaborator

faizann commented Sep 28, 2017

Hi @vetss

It is important for HR/MO as well. The OC Compliance is needed when outbound SRI/MTFSM are sent in correspondence to inbound and we want to relay the originator by appending MCC/MNC to the ServiceCenterGT. Hence a different callingGT for SCCP and for ServiceCenterGT.
If you agree then I can pick this one up.
NetworkID unfortunately won't be scalable as then we need to configure a lot of things and MProc can't hold the logic.

@vetss
Copy link
Contributor Author

vetss commented Oct 4, 2017

Hello @faizann

it will be very good if you can cover the issue of "different callingGT for SCCP and for ServiceCenterGT".
Can you open a separate issue with a requirenments description details. We can discuss then the best solution for it.
We have to close this issue soon because it is for some concrete case and better to have a discussion in a separate issue.

@vetss
Copy link
Contributor Author

vetss commented Oct 4, 2017

After discussing with a customer we have a change for this issue task:
We need to update for mproc rules:
a) GT digits for CallingPartyAdrress (origination address)
b) TT for CalledPartyAddress (destination address)

because of it we need to rename CLI names:
mtlocalgt ****
mtremotett ****
and update code accordingly

We need also to update SMSC GW manual http://documentation.telestax.com/core/smsc/SMSC_Gateway_Admin_Guide.html#_mproc_rules_fundamentals for new commands

I will update also a first record of the issue

@faizann
Copy link
Collaborator

faizann commented Oct 4, 2017

Hi @vetss
Why not also have mtlocaltt and mtremotegt since we are doing it anyway.

@faizann
Copy link
Collaborator

faizann commented Oct 4, 2017

This is the new issue #258

@vetss
Copy link
Contributor Author

vetss commented Oct 4, 2017

Hi @faizann

Why not also have mtlocaltt and mtremotegt since we are doing it anyway.

We are doing this issue for some customer and therefor we need to have hier only a related staff. Sorry for some messing.

@vetss
Copy link
Contributor Author

vetss commented Oct 9, 2017

Changing of CLI parametrs :
mtlocalgt **** -> mtlocalsccpgt
mtremotett **** -> mtremotesccptt

@olenara olenara changed the title Specifzing of SMSC GW GT and TT (TranslationType) by mproc rules Specifying of SMSC GW GT and TT (TranslationType) by mproc rules Oct 11, 2017
olenara added a commit that referenced this issue Oct 12, 2017
vetss pushed a commit to vetss/smscgateway that referenced this issue Oct 23, 2017
@faizann
Copy link
Collaborator

faizann commented Oct 27, 2017

Is this issue finished or something is pending on this one?

@vetss
Copy link
Contributor Author

vetss commented Oct 27, 2017

About finished, we need one little update, @faizann

@vetss
Copy link
Contributor Author

vetss commented Oct 31, 2017

@faizann I think we have finished this issue and code is in master branch.
We will test in a customer side, may be some extra feedback / fix.

@faizann
Copy link
Collaborator

faizann commented Oct 31, 2017

Hi
2 issues in the commits:

  1. RSDS
    I think for consistency in RsdsSbb the mtlocalsccpgt should be used for servicecenter address.
    This applies for createNewDialog call as well as servicecenter address put into MAP layer as that is used for notification.
    This is the line where we need to overriding.
    https://github.com/RestComm/smscgateway/blob/master/core/slee/services/sbbs/src/main/java/org/mobicents/smsc/slee/services/mt/RsdsSbb.java#L332

  2. Documentation
    Also in the documentation on this line it states Destination Global Title will be changed but it should be Source Global Title that gets affected.

    <span class="input-prepend" data-toggle="tooltip" data-placement="bottom" title="Once rule matches, the target SMS's destination global title (GT) will be changed to one set with this command. Set this to -1 to keep original GT. Default value is -1.">

vetss added a commit to vetss/smscgateway that referenced this issue Nov 2, 2017
@vetss
Copy link
Contributor Author

vetss commented Nov 2, 2017

Updated fixing commits list:

18a9536
5d97c60
baf1429
107150b
db8d87d
b735e23
563f9b5

@vetss
Copy link
Contributor Author

vetss commented Nov 2, 2017

Hello @faizann

Thanks for valuable bugs mentioning. RSDS update is reasonable.
I added a fix for it.

olenara added a commit that referenced this issue Dec 20, 2017
olenara pushed a commit that referenced this issue Dec 20, 2017
@vetss vetss closed this as completed Jan 19, 2018
@olenara olenara modified the milestones: SMSC-sprint3, 7.4.0 Jan 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants