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

Jump to bottom

SCCP doesn't respect point-code for incoming message #13

Closed
vetss opened this issue Dec 29, 2015 · 2 comments
Closed

SCCP doesn't respect point-code for incoming message #13

vetss opened this issue Dec 29, 2015 · 2 comments
Labels
bug
Milestone
8.0.0

Comments

@vetss
Copy link
Contributor

vetss commented Dec 29, 2015 •
edited

Suppose SCCP stack is configured with multiple rsp and SCCP Rule1 configured to use PC1 as primary and PC2 as secondary. Now if message received from PC2 and consumed by SCCP-User and replies back, the GT matches for Rule1, it will use PC1 for out going message instead of PC2.

We need to make a discussion firstly how it is better to achieve this task
@deruelle deruelle modified the milestone: 3.0.0 Jan 18, 2016
@vetss vetss removed this from the 3.0.0 milestone Mar 13, 2016
@vetss
Copy link
Contributor Author

vetss commented Mar 13, 2016

The described case is needed for more thinking if it is a bug or not.

@vetss vetss added the bug label May 15, 2016
@faizann
Copy link
Contributor

faizann commented Apr 6, 2017

Hi
I think this is a normal behaviour in the network. The M3UA layer is transaction agnostic and hence pointcodes/addresses should be decided based on SCCP rules (loadsharing/dominant/solitary).

This can be an issue only when the services like USSD/SMSCs are not behind STPs which means that users need to rethink their network implementation.

knosach pushed a commit that referenced this issue Mar 3, 2018
@kostyantynnosach-mobius
issue #13 (SCCP doesn't respect point-code for incoming message)
11c363c
knosach pushed a commit that referenced this issue Mar 7, 2018
@kostyantynnosach-mobius
issue #13 (SCCP doesn't respect point-code for incoming message)
615cabb
@vetss vetss added this to the 8.0.0 milestone Apr 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
8.0.0
Development

No branches or pull requests
3 participants
@deruelle @faizann @vetss