Repository navigation
fix(mgcp): announce GCP actor as GridConnectionPoint (MGCP TS 3.2.2.1) - #265
Open
ckast-enqs wants to merge 1 commit into
Open
ckast-enqs wants to merge 1 commit into
ckast-enqs wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
gcp/mgcpcurrently registers its own actor asMonitoringAppliance, so a device implementing the Grid onnection Point side announcesactor = MonitoringApplianceinnodeManagementUseCaseData.MGCP UC TS 1.0.0, section 3.2.2.1:
Remote monitoring appliances filtering by actor (e.g.
ma/mgcpwithvalidActorTypes = GridConnectionPoint) therefore don't detect the use case support.Changes
usecases/gcp/mgcp/usecase.go: useUseCaseActorTypeGridConnectionPointas local actorusecases/gcp/mgcp/usecase_test.go: addTest_UseCaseActorchecking the announced actor