Status: Accepted
Owner: [email protected]
CC: [email protected],  [email protected]
Labels: Type-Defect Priority-Medium Component-SS7 Roadmap-Fix Version-2.0.0.BETA1

New issue 21 by [email protected]: SSN ==0 should not be considered while making translation check for primary/secondary SCCPAddress
http://code.google.com/p/jss7/issues/detail?id=21

As of now, the SSN from primary/secondary address is checked if its SCCP Management SSN (SSN==1) or if its not, whether the SCCPListener is registered for this SSN; if both above condition fails it returns TranslationAddressCheckingResult.destinationUnavailable_SubsystemFailure.

However SSN of primary/secondary address can be 0 indicating that SSN received from called SccpAddress is to be used in translated SccpAddress.

Reply via email to