You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: