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.

Sign up for GitHub

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

SMSC not being able to identify ESME of type CLIENT correctly #28

Closed
olenara opened this issue Sep 13, 2017 · 1 comment
Closed

SMSC not being able to identify ESME of type CLIENT correctly #28

olenara opened this issue Sep 13, 2017 · 1 comment
Assignees
@olenara
Labels
bug
Milestone
7.1.0

Comments

@olenara
Copy link
Contributor

olenara commented Sep 13, 2017

When two ESMEs connect at the same time with same system id and password, then SMSC identifies both of them as same Esme and accepts connections from both. It causes different problem, for example:

  1. request received from one channel and response is sent via another;
  2. invalid message_id for response, etc.

Tickets related:
https://telestax.zendesk.com/agent/tickets/34628
https://telestax.zendesk.com/agent/tickets/34633
satanatoly pushed a commit that referenced this issue Sep 13, 2017
@olenara
Added localSessionId to differentiate activityHandle after reconnect.
d540880 
Modified Server ESME type session id generator handling.
Changed to using a new state variable from Esme class.
Added new test to simulate connecting of two esmes with same syst id/passw at the same time.
Related issue #28, zendesk tickets 34628 and 34633
satanatoly pushed a commit to RestComm/cloudhopper-smpp that referenced this issue Sep 14, 2017
@olenara
Added debug logging as per ticket 34388.
6be5875 
Fixed issue with connection being stuck on awaitUninterruptibly() as per fizzed#1
Fixed blocking issue at channel write.
Related issue RestComm/smpp-extensions#28
satanatoly pushed a commit to satanatoly/jain-slee.smpp that referenced this issue Sep 14, 2017
@olenara
Added inactivity timers related to related github issue RestComm/smpp…
4648265 
…-extensions#28 and ticket 34388
satanatoly pushed a commit to satanatoly/jain-slee.smpp that referenced this issue Sep 14, 2017
@olenara
Added localSessionId to differentiate activityHandle after reconnect.…
bd7df55 
… Added some logging per ticket 34633. Related githun issue RestComm/smpp-extensions#28
olenara added a commit to RestComm/jain-slee.smpp that referenced this issue Sep 15, 2017
@olenara
Added localSessionId to differentiate activityHandle after reconnect.…
e2a611e 
… Added some logging per ticket 34633. Related github issue RestComm/smpp-extensions#28
@vetss vetss added the bug label Sep 19, 2017
@vetss vetss added this to the Anatoly-7.4.0-sprint1 milestone Sep 19, 2017
@olenara
Copy link
Contributor Author

olenara commented Sep 19, 2017 •
edited

Fixed by
d540880
RestComm/cloudhopper-smpp@6be5875
RestComm/jain-slee.smpp@e2a611e

@olenara olenara closed this as completed Sep 19, 2017
olenara added a commit to RestComm/cloudhopper-smpp that referenced this issue Sep 28, 2017
@olenara
Fixed issue with connection being stuck on awaitUninterruptibly() as …
3e695e7 
…per fizzed#1

Fixed blocking issue at channel write.
Related issue RestComm/smpp-extensions#28
@vetss vetss modified the milestones: Anatoly-7.4.0-sprint1, 7.1.0 Jan 15, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@olenara olenara

Labels
bug
Projects
None yet
Milestone
7.1.0
Development

No branches or pull requests
2 participants
@vetss @olenara