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

Using "named" TCAP listeners #81

Closed
AlerantAppNGIN opened this issue May 13, 2016 · 2 comments
Closed

Using "named" TCAP listeners #81

AlerantAppNGIN opened this issue May 13, 2016 · 2 comments
Assignees

Comments

@AlerantAppNGIN
Copy link
Collaborator

Issue short: Create NamedTCListener interface (TClistener with a name attribute) and implement it in MAP and CAP providerImpl.

Description: Multiple CAP and/or MAP stacks can use the same TCAP stacks. From the point of view of the TCAP stack these higher level layers are TCAP listeners.
It could be beneficial if these listeners can be labeled. For example: Suppose that we have a MAP and a CAP stacks on the same TCAP subsystem. When an event is propagated from TCAP to the higher layers a special listener is called which examines the Application context of the dialog the incoming message corresponds to and decides that the event have to route to a TCListner of a CAP or a MAP stack.
In this case the labeling (the name attribute of NamedTClistener) can be used to describe if the listener belongs to a CAP or MAP stack.

@vetss
Copy link
Contributor

vetss commented May 20, 2016

Please see my comments in #79

@vetss vetss removed this from the 8.0.0 milestone Feb 20, 2017
@vetss vetss closed this as completed Feb 20, 2017
@vetss
Copy link
Contributor

vetss commented Feb 20, 2017

Closing becuse of no activity

@vetss vetss reopened this Feb 20, 2017
@vetss vetss closed this as completed Feb 20, 2017
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