Page History
Resources | profiles | signaling | isupSignalingProfile
 isupSignalingProfileThis object creates a template for the ISUP signaling services used by the ISUP service group manipulating this signaling profile. Sonus supplies a number of default signaling profiles that correspond to the ISUP protocol revision that the ISUP service group uses. These default profiles effectively assign the signaling conventions used under that protocol revision. |
Configuration
| Parameter | Presence | Type | Default | Description | |
|---|---|---|---|---|---|
  | name | M | string | The name of the ISUP Signaling Profile. | |
| versionId | M | uint16 | The version ID to identify a signaling group. | |
| baseProfile | O | union | The Base Signaling group name. | |
| olipCheck | O | enumeration | unSupported | Specifies whether or not to support check for the presence of an OLIP when determining that a call is invalid. |
| hopCountValue | O | uint8 | 10 | The global Iteration count limit for DNS iterations of server requests. |
| hopCountState | O | enumeration | unSupported | The Hop Counter support for the Signaling Group. |
| baseVersion | O | enumeration | etsi121 | The Base Signaling group from rfc3204. |
| revision | O | enumeration | ituq767 | The revision of the ISUP protocol supported on this Signaling Group. |
| olipCheckOnSend | O | enumeration | unSupported | Specifies whether or not to check for the presence of an OLIP when sending an IAM. |
| networkIndicator | O | enumeration | natl0 | The setting of the Network Indicator as it would be for ISUP if the SIP-T link were an ISUP link. This is here to prevent unnecessary interworking only, and is not really applicable to SIP-T. |
| propagationDelaySupport | O | enumeration | unSupported | Is propagation delay supported for the ISUP Signaling Profile. |
| propagationDelay | O | uint16 | 0 | The propagation delay value in milliseconds for this SIP-T signaling group. |
| lookAheadForBusy | O | enumeration | notAllowed | The default value used in the look ahead for busy field in the ISUP Precedence parameter within SIP-T. |
| networkIdentity | O | string | 0000 | The default value used for the 4 digit Network Identity field in the ISUP precedence parameter within SIP-T. |
| generateJapanIcsParams | O | enumeration | unSupported | Specifies whether to support generating ICS information in SIP MIME case for the signaling group |
| compatibility | O | enumeration | unSupported | Is compatibility supported for the ISUP Signaling Profile. |
| accessDelivery | O | enumeration | unSupported | Is Access Delivery Information supported for the ISUP Signaling Profile. |
| genericNumber | O | enumeration | unSupported | Is the generic number parameter supported for the ISUP Signaling Profile. |
| genericNotification | O | enumeration | unSupported | Is the generic notification parameter supported for the ISUP Signaling Profile. |
| genericDigits | O | enumeration | unSupported | Is the generic digits parameter supported for the ISUP Signaling Profile. |
| locationNumber | O | enumeration | unSupported | Is the location number parameter supported for the ISUP Signaling Profile. |
| originatingIscPointCode | O | enumeration | unSupported | Is the originating ISC point code parameter supported for the ISUP Signaling Profile. |
| userTeleService | O | enumeration | unSupported | Is the user teleservice parameter supported for the ISUP Signaling Profile. |
| segmentation | O | enumeration | unSupported | Is segmentation supported for the ISUP Signaling Profile. |
| fallback | O | enumeration | unSupported | Is fallback supported for the ISUP Signaling Profile. |
| eMcid | O | enumeration | unSupported | Is MCID supported for the ISUP Signaling Profile. |
| subscriberPriorityClass | O | enumeration | unSupported | Is the subscriber priority class parameter supported for the ISUP Signaling Profile. |
| apm | O | enumeration | unSupported | Is APM supported for the ISUP Signaling Profile. |
| connectedNumberInAcm | O | enumeration | unSupported | Is the connected number parameter supported in the ACM for the ISUP Signaling Profile. |
| causeInCpg | O | enumeration | unSupported | Is the cause parameter supported in the CPG for the ISUP Signaling Profile. |
| multiCarrierEnvironment | O | enumeration | unSupported | Is the multi carrier environment parameter supported for the ISUP Signaling Profile. |
| carrierSelection | O | enumeration | unSupported | Is carrier selection supported for the ISUP Signaling Profile. |
| inrInf | O | enumeration | unSupported | Is INR/INF supported for the ISUP Signaling Profile. |
| cqmCqr | O | enumeration | unSupported | Is CQM/CQR supported for the ISUP Signaling Profile. |
| callReference | O | enumeration | unSupported | Is the call reference parameter supported for the ISUP Signaling Profile. |
| cfn | O | enumeration | unSupported | Is CFN supported for the ISUP Signaling Profile. |
| facility | O | enumeration | unSupported | Are FAA, FAR and FRJ supported for the ISUP Signaling Profile. |
| pam | O | enumeration | unSupported | Is PAM supported for the ISUP Signaling Profile. |
| obciAnm | O | enumeration | unSupported | Is the OBCI parameter supported in the ANM for the ISUP Signaling Profile. |
| drs | O | enumeration | unSupported | Is DRS supported the ISUP Signaling Profile. |
| redirectionNumber | O | enumeration | unSupported | Is the redirection number parameter supported for the ISUP Signaling Profile. |
| lpa | O | enumeration | unSupported | Is LPA supported for the ISUP Signaling Profile. |
| ucic | O | enumeration | unSupported | Is UCIC supported for the ISUP Signaling Profile. |
| olm | O | enumeration | unSupported | Is OLM supported for the ISUP Signaling Profile. |
| blueBookInRel | O | enumeration | unSupported | Are Blue Book parameters supported in REL for the ISUP Signaling Profile. |
| usr | O | enumeration | unSupported | Is USR supported for the ISUP Signaling Profile. |
| bbIam | O | enumeration | unSupported | Is User-To-User ind parameter supported in IAM for the ISUP Signaling Profile. |
| callModMsgs | O | enumeration | unSupported | Are CMR, CMA and CMRJ supported for the ISUP Signaling Profile. |
| callDiversion | O | enumeration | unSupported | Is call diversion supported for the ISUP Signaling Profile. |
| callHistory | O | enumeration | unSupported | Is the call history parameter supported for the ISUP Signaling Profile. |
| genericReference | O | enumeration | unSupported | Is the generic reference parameter supported for the ISUP Signaling Profile. |
| mlpp | O | enumeration | unSupported | Is the MLPP parameter supported for the ISUP Signaling Profile. |
| nsf | O | enumeration | unSupported | Is the NSF parameter supported for the ISUP Signaling Profile. |
| redirectionNumberRestriction | O | enumeration | unSupported | Is the redirection number restriction parameter supported for the ISUP Signaling Profile. |
| remoteOperations | O | enumeration | unSupported | Is the remote operations parameter supported for the ISUP Signaling Profile. |
| serviceActivation | O | enumeration | unSupported | Is the service activation parameter supported for the ISUP Signaling Profile. |
| signalingPointCode | O | enumeration | unSupported | Is the signaling point code parameter supported for the ISUP Signaling Profile. |
| tmrPrime | O | enumeration | unSupported | Is the TMR prime parameter supported for the ISUP Signaling Profile. |
| transmissionMediumUsed | O | enumeration | unSupported | Is the transmission medium used parameter supported for the ISUP Signaling Profile. |
| usiPrime | O | enumeration | unSupported | Is the USI prime parameter supported for the ISUP Signaling Profile. |
| redirectionNumberInAcm | O | enumeration | unSupported | Is the redirection number supported in the ACM for the ISUP Signaling Profile. |
| redirectionNumberInAnm | O | enumeration | unSupported | Is the redirection number supported in the ANM for the ISUP Signaling Profile. |
| connectionReqInFaa | O | enumeration | unSupported | Is the connection request parameter supported in the FAA for the ISUP Signaling Profile. |
| connectionReqInFar | O | enumeration | unSupported | Is the connection request parameter supported in the FAR for the ISUP Signaling Profile. |
| fac | O | enumeration | unSupported | Is the FAC supported for the ISUP Signaling Profile. |
| echoControl | O | enumeration | unSupported | Is the echo control parameter supported for the ISUP Signaling Profile. |
| backwardGvns | O | enumeration | unSupported | Is the backward GVNS parameter supported for the ISUP Signaling Profile. |
| circuitAssignmentMap | O | enumeration | unSupported | Is the circuit assignment map parameter supported for the ISUP Signaling Profile. |
| ccss | O | enumeration | unSupported | Is the CCSS parameter supported for the ISUP Signaling Profile. |
| callDiversionTreatment | O | enumeration | unSupported | Is the call diversion treatment parameter supported for the ISUP Signaling Profile. |
| calledInNum | O | enumeration | unSupported | Is the called IN number parameter supported for the ISUP Signaling Profile. |
| collectCallReq | O | enumeration | unSupported | Is the collect call request parameter supported for the ISUP Signaling Profile. |
| conferenceTreatment | O | enumeration | unSupported | Is the conference treatment parameter supported for the ISUP Signaling Profile. |
| correlationId | O | enumeration | unSupported | Is the correlation ID parameter supported for the ISUP Signaling Profile. |
| callOfferingTreatment | O | enumeration | unSupported | Is the call offering treatment parameter supported for the ISUP Signaling Profile. |
| callTransferNumber | O | enumeration | unSupported | Is the call transfer number parameter supported for the ISUP Signaling Profile. |
| callTransferReference | O | enumeration | unSupported | Is the call transfer reference parameter supported for the ISUP Signaling Profile. |
| displayInformation | O | enumeration | unSupported | Is the display information parameter supported for the ISUP Signaling Profile. |
| forwardGvns | O | enumeration | unSupported | Is the forward GVNS parameter supported for the ISUP Signaling Profile. |
| loopPrevention | O | enumeration | unSupported | Is the loop prevention indicators parameter supported for the ISUP Signaling Profile. |
| networkManagement | O | enumeration | unSupported | Is network management controls parameter supported for the ISUP Signaling Profile. |
| scfId | O | enumeration | unSupported | Is the SCF ID parameter supported for the ISUP Signaling Profile. |
| uidActionInd | O | enumeration | unSupported | Is the UID action indicators parameter supported for the ISUP Signaling Profile. |
| uidCapabilityInd | O | enumeration | unSupported | Is the UID capabilities parameter supported for the ISUP Signaling Profile. |
| connectedNumberInCpg | O | enumeration | unSupported | Is the connected number parameter supported in the CPG for the ISUP Signaling Profile. |
| genericNumberInCpg | O | enumeration | unSupported | Is the generic number parameter supported in the CPG for the ISUP Signaling Profile. |
| echoControlInIam | O | enumeration | unSupported | Is the echo control parameter supported in the IAM for the ISUP Signaling Profile. |
| remoteOperationInRel | O | enumeration | unSupported | Is the remote operations parameter supported in the REL for the ISUP Signaling Profile. |
| accessTransportInFac | O | enumeration | unSupported | Is the access transport parameter supported in the FAC for the ISUP Signaling Profile. |
| genericNotificationInFac | O | enumeration | unSupported | Is the generic notification parameter supported for the ISUP Signaling Profile. |
| uuindAnm | O | enumeration | unSupported | Is the UUI parameter supported in the ANM for the ISUP Signaling Profile. |
| uuindCpg | O | enumeration | unSupported | Is the UUI parameter supported in the CPG for the ISUP Signaling Profile. |
| nrmSupport | O | enumeration | unSupported | Is the NRM supported for the ISUP Signaling Profile. |
| causeInRlc | O | enumeration | unSupported | Is the cause parameter supported in the RLC for the ISUP Signaling Profile. |
| upaUpt | O | enumeration | unSupported | Are UPA/UPT supported for the ISUP Signaling Profile. |
| recommendationInCai | O | enumeration | unSupported | Is the recommendation field supported in the cause parameter for the ISUP Signaling Profile. |
| transitUnrecognized | O | enumeration | unSupported | Is the transiting of unrecognised parameters supported for the ISUP service Group. |
| u2uServiceLevel | O | enumeration | implicit | The level of user to user services supported in the the ISUP Signaling Profile. |
| subsequentAddressMessage | O | enumeration | supported | Is the Subsequent Address Message supported for the ISUP Signaling Profile. |
| forwardTransferMessage | O | enumeration | supported | Is the Forward Transfer Message supported for the ISUP Signaling Profile. |
| specialDigits | O | enumeration | digitB digitC digitF | Indicates the special digits which can appear in dialed digit strings BIT 0 - Is digit A allowed in the digit string BIT 1 - Is digit B allowed in the digit string (default) BIT 2 - Is digit C allowed in the digit string (default) BIT 3 - Is digit D allowed in the digit string BIT 4 - Is digit E allowed in the digit string BIT 5 - Is digit F allowed in the digit string (default) BIT 6 - No special digits in the digit string |
| transitNetworkSelection | O | enumeration | unSupported | Is the Transit Network Selection Parameter supported for the ISUP Signaling Profile. |
| accessTransport | O | enumeration | supported | Is the Access Transport parameter supported for the ISUP Signaling Profile. |
| jurisdiction | O | enumeration | unSupported | Is the Jurisdiction parameter supported for the ISUP Signaling Profile. |
| originalCalledNumber | O | enumeration | unSupported | Is the Original Called Number parameter supported for the ISUP Signaling Profile. |
| businessGroup | O | enumeration | unSupported | Is the Business Group parameter supported for the ISUP Signaling Profile. |
| connectionReq | O | enumeration | unSupported | Is the Connection Request parameter supported for the ISUP Signaling Profile. |
| informationInd | O | enumeration | unSupported | Is the Information Indicator parameter supported for the ISUP Signaling Profile. |
| networkTransport | O | enumeration | unSupported | Is the Network Transport supported for the ISUP Signaling Profile. |
| notificationInd | O | enumeration | unSupported | Is the Notification Indicator parameter supported for the ISUP Signaling Profile. |
| redirectionInfoAcm | O | enumeration | unSupported | Is the Redirection Information parameter supported in the ACM message for the ISUP Signaling Profile. |
| egressService | O | enumeration | unSupported | Is the Egress Service parameter supported for the ISUP Signaling Profile. |
| serviceCodeInd | O | enumeration | unSupported | Is the Service Code Indicator parameter supported for the ISUP Signaling Profile. |
| specialProcessReq | O | enumeration | unSupported | Is the Special Processing Request parameter supported for the ISUP Signaling Profile. |
| transactionReq | O | enumeration | unSupported | Is the Transaction Request parameter supported for the ISUP Signaling Profile. |
| chargeNumber | O | enumeration | unSupported | Is the Charge Number parameter supported for the ISUP Signaling Profile. |
| genericAddressRel | O | enumeration | unSupported | Is the Generic Address parameter supported in the REL message for the ISUP Signaling Profile. |
| uuIndAcm | O | enumeration | supported | Is the User to User Indicators parameter supported for the ISUP Signaling Profile. |
| uuInfo | O | enumeration | supported | Is the User to User Information parameter supported for the ISUP Signaling Profile. |
| operatorServiceInfo | O | enumeration | unSupported | Is the Operator Service Information parameter supported for the ISUP Signaling Profile. |
| cvtCvr | O | enumeration | unSupported | Are the Circuit Validation Test/Response procedures supported for the ISUP Signaling Profile. |
| genericName | O | enumeration | unSupported | Is the Generic Name parameter supported for the ISUP Signaling Profile. |
| redirectionCap | O | enumeration | unSupported | Is the Redirection Capability parameter supported for the ISUP Signaling Profile. |
| groupRedirectionCount | O | enumeration | unSupported | Is the Group Redirection Count parameter supported for the ISUP Signaling Profile. |
| sendTwoGroupMsgs | O | enumeration | unSupported | Set the Flag to Send Two Group Messages in the ISUP Signaling Profile. |
| awaitTwoGroupMsgs | O | enumeration | unSupported | Set the Flag to Await Two Group Messages in the ISUP Signaling Profile. |
| cqmOnCardSwap | O | enumeration | unSupported | Set the Flag to perform CQM on Card Swap in the ISUP Signaling Profile. |
| ansi95Grs | O | enumeration | unSupported | Should the ANSI-95 format for Group Reset Circuit (GRS), which includes optional/ parameters, be used. |
| cpgBeforeAcm | O | enumeration | unSupported | Should a CPG arriving before an ACM be transited. |
| mapDmsFeParameter | O | enumeration | unSupported | Specifies if the service group should perform mapping of the Completion Code in the DMS FE parameter (ANSI ISUP only) |
| trunkOfferingSupport | O | enumeration | unSupported | Describes if the trunk offering messages can,fan,ofr,rcl are supported, at the moment this is just for mexico. But as sure as eggs is eggs other international variants are going to want to as well at some time |
| operatorSelection | O | enumeration | unSupported | Describes if the operator selection parameter is supported |
| maxCallingPartyDigits | O | uint8 | 30 | The maximum digit string length for the Calling Party Number parameter supported for this ISUP Signaling Profile |
| maxCalledPartyDigits | O | uint8 | 30 | The maximum digit string length for the Called Party Number parameter supported for this ISUP Signaling Profile |
| freePhoneInd | O | enumeration | unSupported | Is the Freephone Indicators parameter supported for this ISUP Signaling Profile. |
| itxTxa | O | enumeration | unSupported | Are the ITX and TXA messages supported for the ISUP Signaling Profile. |
| sccpProcedure | O | enumeration | unSupported | Is the SCCP Procedure supported for the ISUP Signaling Profile. |
| connectionReqInIam | O | enumeration | supported | Is the Connection Request parameter supported in the IAM for the ISUP Signaling Profile. |
| ccnr | O | enumeration | unSupported | Is the CCNR Possible Indicator parameter supported for the ISUP Signaling Profile. |
| transitCfn | O | enumeration | unSupported | Should the CFN message be transited for the ISUP Signaling Profile. |
| holdingInd | O | enumeration | supported | Should the Holding Indicator be supported for the ISUP Signaling Profile. |
| displayInfoInAcm | O | enumeration | unSupported | Should the Display Information parameter in the ACM be supported for the ISUP Signaling Profile. |
| displayInfoInCon | O | enumeration | unSupported | Should the Display Information parameter in the CON be supported for the ISUP Signaling Profile. |
| displayInfoInCpg | O | enumeration | unSupported | Should the Display Information parameter in the CPG be supported for the ISUP Signaling Profile. |
| displayInfoInIam | O | enumeration | unSupported | Should the Display Information parameter in the IAM be supported for the ISUP Signaling Profile. |
| genericNumInAcm | O | enumeration | unSupported | Should the Generic Number parameter in the ACM be supported for the ISUP Signaling Profile. |
| genericNumInFac | O | enumeration | unSupported | Should the Generic Number parameter in the FAC be supported for the ISUP Signaling Profile. |
| genericNumInInf | O | enumeration | unSupported | Should the Generic Number parameter in the INF be supported for the ISUP Signaling Profile. |
| conferenceTreatmentInAnm | O | enumeration | unSupported | Should the Conference Treatment parameter in the ANM be supported for the ISUP Signaling Profile. |
| continuity | O | enumeration | supported | Should the Continuity procedures be supported for the ISUP Signaling Profile. |
| userServiceInformation | O | enumeration | supported | Should User service information be supported for the ISUP signaling profile |
| connectedNumber | O | enumeration | supported | Should connected number be supported for the ISUP signaling profile |
| diagnostics | O | enumeration | supported | Should the Diagnostics field be supported for the ISUP signaling profile |
| optionalFci | O | enumeration | supported | Should the Optional Forward Call Indicators be supported for the ISUP signaling profile |
| cugInterlockCode | O | enumeration | supported | Should Closed User Group Interlock Code be supported for the ISUP signaling profile |
| com | O | enumeration | supported | Should the COM message be supported for the ISUP Signaling Profile. |
| con | O | enumeration | supported | Describes if the CON message is supported |
| iriOriRcv | O | enumeration | unSupported | Is the IRI/ORI expected for the ISUP Signaling Profile. |
| iriOriSent | O | enumeration | unSupported | Is the IRI/ORI to be sent out for the ISUP Signaling Profile. |
| t11Active | O | enumeration | unSupported | Is ISUP T11 timing active at interworking exchanges for Signaling Profile. |
| iriOri | O | enumeration | unSupported | Is the IRI/ORI supported for the ISUP Signaling Profile. |
| transMedUsedInNrm | O | enumeration | unSupported | Is the TMU parameter within the NRM Message supported for the ISUP Signaling Profile. |
| rlcAcknowledgeGrs | O | enumeration | unSupported | Is acknowledging a GRS with an RLC supported. |
| incomingTrunkIdCode | O | enumeration | unSupported | Is the Incoming Trunk Identity Code parameter supported for the Signaling Profile. |
| spcInIrs | O | enumeration | unSupported | Is the SPC parameter with the IRS message supported for the ISUP Signaling Profile. |
| redirectionInfoIam | O | enumeration | unSupported | Is the Redirection Information parameter supported within the IAM message foe the ISUP Signaling Profile. |
| redirectingNumber | O | enumeration | unSupported | Is the Redirecting Number parameter supported for the ISUP Signaling Profile. |
| bloAfterSetup | O | enumeration | unSupported | For some ANSI protocols a BLO message should be sent when blocking a circuit, after a backwards message has been received during the call. |
| calledDirectoryNumber | O | enumeration | unSupported | Is the called directory number parameter supported for the ISUP signaling Profile. |
| forwardCallProgress | O | enumeration | unSupported | Is the Call Progress (CPG) message supported in the forwards direction. |
| forwardSuspend | O | enumeration | supported | Is the Suspend (SUS) message supported in the forwards direction. |
| uuInfoAcm | O | enumeration | supported | Is the UU Information supported in the ACM for the ISUP Signaling Profile. |
| atRel | O | enumeration | unSupported | Is the AT supported in the REL for the ISUP Signaling Profile. |
| uuIndRel | O | enumeration | supported | Is the UU Indicator supported in the REL for the ISUP Signaling Profile. |
| eit | O | enumeration | unSupported | Is the EIT supported for the ISUP Signaling Profile. |
| gi | O | enumeration | unSupported | Is the GI supported for the ISUP Signaling Profile. |
| tit | O | enumeration | unSupported | Is the TIT supported for the ISUP Signaling Profile. |
| ait | O | enumeration | unSupported | Is the AIT supported for the ISUP Signaling Profile. |
| tci | O | enumeration | unSupported | Is the TCI supported for the ISUP Signaling Profile. |
| nft | O | enumeration | unSupported | Is the NFT supported for the ISUP Signaling Profile. |
| cpnRel | O | enumeration | unSupported | Is the CPN supported in the REL for the ISUP Signaling Profile. |
| bciRel | O | enumeration | unSupported | Is the BCI supported in the REL for the ISUP Signaling Profile. |
| ci | O | enumeration | unSupported | Is the CI6 supported in the ISUP Signaling Profile. |
| iui | O | enumeration | unSupported | Is the IUI6 supported in the ISUP Signaling Profile. |
| nrop | O | enumeration | unSupported | Is the NROP6 supported in the ISUP Signaling Profile. |
| msi | O | enumeration | unSupported | Is the MSI6 supported in the ISUP Signaling Profile. |
| rr | O | enumeration | unSupported | Is the RR6 supported in the ISUP Signaling Profile. |
| mi | O | enumeration | unSupported | Is the MI6 supported in the ISUP Signaling Profile. |
| spc6 | O | enumeration | unSupported | Is the SPC6 supported in the ISUP Signaling Profile. |
| maRel | O | enumeration | unSupported | Is the MA6 supported in the REL message for the ISUP Signaling Profile. |
| connectionReqInInf | O | enumeration | unSupported | Is the Connection Request supported in the INF for the ISUP Signaling Profile. |
| sgmPci | O | enumeration | unSupported | Is the PCI parameter supported in the SGM for the ISUP Signaling Profile. |
| gr317ScreeningInd | O | enumeration | unSupported | Turns on various screening indicators for GR317 parameter compliancy. |
| opr | O | enumeration | unSupported | Is the Operator (OPR) message supported. |
| ccl | O | enumeration | unSupported | Is the Calling Party Clearing (CCL) messsage supported. |
| otherDigitStringSpecialDigitF | O | enumeration | unSupported | Is the Special Digit F supported in digit strings other than the Called Party. |
| callReferenceFrj | O | enumeration | unSupported | Is the Call Reference Parameter supported in the FRJ message. |
| pciPassOnDefault | O | enumeration | unSupported | The handling required when received an unrecognised PCI Pass On Not Possible value in the ISUP Signaling Profile. |
| otgnAnsi92 | O | enumeration | unSupported | Is the OTGN Parameter, upto 5 octets supported in the EXM message. |
| dropCauseInAcmWhenIwk | O | enumeration | unSupported | Should CAUSE parameter in ACM be suppressed if announcement played after interworking. |
| chargeIndSetting | O | enumeration | transit | Sets the BCI charge indicator to either charge or no charge, or will transit whatever is received from the sending side (egress of network). This can be nothing at all in the case of ISDN - defaults to 0, or whatever we received in the case of ISUP. |
| t11EarlyAcm | O | enumeration | unSupported | Is ISUP T11 Early ACM guard timer started for the ISUP Signaling Profile. |
| dmsFe | O | enumeration | unSupported | Should the DMS FE field be supported for the ISUP signaling profile |
| cqmForResync | O | enumeration | unSupported | Send a Cqm pdu to resync when transitioning from Mtp Pause to Resume State |
| ncr | O | enumeration | unSupported | Is the Network Call Reference (NCR) Parameter Supported. |
| sliInIam | O | enumeration | unSupported | Is the Supplementary Line Info Parameter Supported in the IAM. |
| releaseLinkTrunking | O | enumeration | unSupported | Is the Release Link Trunking (RLT) Service Supported. |
| accessTransInFar | O | enumeration | unSupported | Is the Access Transport Parameter Supported in the FAR. |
| uuIndInFar | O | enumeration | unSupported | Is the User-to-User Indicators Parameter Supported in the FAR. |
| upvExchangeRoles | O | enumeration | orig term intwk trans int unknown | Indicates the exchange roles which can perform unrecognised parameter value handling BIT 0 - Is the originating exchange allowed to perform UPV (default) BIT 1 - Is the terminating exchange allowed to perform UPV (default) BIT 2 - Is the interworking exchange allowed to perform UPV (default) BIT 3 - Is the transit exchange allowed to perform UPV (default) BIT 4 - Is the international exchange allowed to perform UPV (default) BIT 5 - Is the unknown exchange role allowed to perform UPV (default) BIT 6 - No exchange roles are allowed to perform UPV |
| calledBsm | O | enumeration | unSupported | Is the Called Subs Basic Service Marks parameter supported for the ISUP Signaling Profile. |
| callingBsm | O | enumeration | unSupported | Is the Calling Subs Basic Service Marks parameter supported for the ISUP Signaling Profile. |
| callingOfm | O | enumeration | unSupported | Is the Calling Subs Orig Facility Marks parameter supported for the ISUP Signaling Profile. |
| calledTfm | O | enumeration | unSupported | Is the Called Subs Term Facility Marks parameter supported for the ISUP Signaling Profile. |
| nii | O | enumeration | unSupported | Is the National Information Indicators parameter supported for the ISUP Signaling Profile. |
| niri | O | enumeration | unSupported | Is the National Information Request Indicators parameter supported for the ISUP Signaling Profile. |
| nfci | O | enumeration | unSupported | Is the National Forward Call Indicators parameter supported for the ISUP Signaling Profile. |
| presentationNumber | O | enumeration | unSupported | Is the Presentation Number parameter supported for the ISUP Signaling Profile. |
| ldli | O | enumeration | unSupported | Is the Last Diverted Line Identity parameter supported for the ISUP Signaling Profile. |
| pcli | O | enumeration | unSupported | Is the Partial Calling Line Identity parameter supported for the ISUP Signaling Profile. |
| nfciLnk | O | enumeration | unSupported | Is the National Forward Call Indicators Link-by-Link parameter supported for the ISUP Signaling Profile. |
| inrInAllStates | O | enumeration | unSupported | Are the INR and INF messages supported supported in all states for the ISUP Signaling Profile. |
| nfciLblRciProc | O | enumeration | unSupported | Is the National Forward Call Indicators Link-by-Link parameter procedure supported for the ISUP Signaling Profile. |
| ansi95Cfn | O | enumeration | unSupported | Should the ANSI-95 format for Confusion (CFN), which includes optional parameters, be used. |
| allianceScreenInd | O | enumeration | unSupported | Is the Alliance Screen Indicator parameter supported for the ISUP Signaling Profile |
| announcementInd | O | enumeration | unSupported | Is the Announcement Indicator parameter supported for the ISUP Signaling Profile. |
| dialedNumber | O | enumeration | unSupported | Is the Dialed Number parameter supported for the ISUP Signaling Profile. |
| forwardNetworkSpecificInfo | O | enumeration | unSupported | Is the Forward Network Specific Information parameter supported for the ISUP Signaling Profile. |
| genericOperation | O | enumeration | unSupported | Is the Generic Operation parameter supported for the ISUP Signaling Profile. |
| hardToReachInd | O | enumeration | unSupported | Is the Hard To Reach Indicator parameter supported for the ISUP Signaling Profile. |
| networkManagementInfo | O | enumeration | unSupported | Is the Network Management Information parameter supported for the ISUP Signaling Profile. |
| networkSwitchNumber | O | enumeration | unSupported | Is the Network Switch Number parameter supported for the ISUP Signaling Profile. |
| routingInfoInd | O | enumeration | unSupported | Is the Routing Information Indicator parameter supported for the ISUP Signaling Profile. |
| sdnIncrement | O | enumeration | unSupported | Is the SDN SID/ANI Increment Message supported for the ISUP Signaling Profile. |
| ansi95Cqm | O | enumeration | unSupported | Is the ANSI 95 version of the CQM message containing the optional pointer supported for the ISUP Signaling Profile. |
| bcm | O | enumeration | unSupported | Is the Backwards Charging Message supported for the ISUP Signaling Profile. |
| eci | O | enumeration | unSupported | Is the Japan Emergency Indicator parameter supported for the ISUP Signaling Profile. |
| genericNumberRepeatable | O | enumeration | unSupported | Is the Generic Number a Repeatable Parameter. |
| genericNumberRepeatableIam | O | enumeration | unSupported | Is the Generic Number a Repeatable Parameter in the IAM Message. |
| genericNotificationRepeatable | O | enumeration | unSupported | Is the Generic Notification a Repeatable Parameter. |
| serviceActivationInRel | O | enumeration | unSupported | Is the Service Activation Parameter supported in the REL message. |
| uuIndCon | O | enumeration | supported | Is the User-to-User Indicators Parameter Supported in the CON. |
| uuiInInf | O | enumeration | unSupported | Is the User-to-User Information Parameter Supported in the INF. |
| chargeMsgInSpeech | O | enumeration | unSupported | Is the Charge Message In Speech Parameter supported for the ISUP Signaling Profile. |
| emergencyCallInf | O | enumeration | unSupported | Is the Emergency Call Information Parameter supported in the CPG. |
| t7Transit | O | enumeration | unSupported | Is the T7 Timer run for a Transit Call in the ISUP Signaling Profile. |
| nsa | O | enumeration | unSupported | Is the Network Specific ANM Parameter Supported in the ANM. |
| invTnsRelease | O | enumeration | unSupported | Should the Q931 Release handling for invalid TNS be applied. |
| jti | O | enumeration | unSupported | Is the JT Specific ISUP Parameter Supported in the ISUP Signaling Profile. |
| fciUserPartIwk | O | enumeration | unSupported | Should the FCI ISDN User Part indicator be overwritten for NON-ISUP to ISUP calls. |
| fciUserPartTrans | O | enumeration | unSupported | Should the FCI ISDN User Part indicator be overwritten for ISUP to ISUP calls. |
| connectionPointTrunkType | O | enumeration | unSupported | Is the Connection Point Trunk Type supported for the ISUP Signaling Profile. |
| fciUserPartChosenCarrier | O | enumeration | unSupported | Should the FCI ISDN User Part indicator be overwritten based on the Chosen Carrier. |
| truncateCdpn | O | enumeration | unSupported | If the CDPN is greater than the MaxCalledPartyDigits should it be truncated or the call released |
| noIpEchoInd | O | enumeration | unSupported | If the Echo Control indication should be set for an IP to PSTN call |
| visitorMa | O | enumeration | unSupported | If the Visitor MA parameter is supported |
| sendBloOnHwBlock | O | enumeration | unSupported | Send BLO when a circuit is hardware blocked. |
| allowCallsOnHwBlock | O | enumeration | unSupported | Do not reject calls on a hardware blocked circuit. |
| sendRscForCallsOnHwBlock | O | enumeration | unSupported | Send RSC for when a call is impacted by a hardware blockage on a circuit. |
| allowUnscreenedCin | O | enumeration | unSupported | Should the values 0 and 2 of Screening Indicator be allowed in ISUP. |
| iamGeneratedCarrierCodeInCdr | O | enumeration | unSupported | Should the IAM-Generated Carrier Code always be populated in the CDR for Japan regardless of type. |
| dropUsiFromNonIsup | O | enumeration | unSupported | If the USI parameter is supported when the far-side is not ISUP. |
| assumeOutgoingDeviceIncluded | O | enumeration | unSupported | Should the egress echo cancellation software assume for an ISUP transit call that an outgoing device has been included, regardless of the NCI setting. |
| preventAcmToCpgMapping | O | enumeration | unSupported | If an ACM has already been sent on the ingress trunk group due to a script, T11 timer expiry or some other event and an ACM is received on the egress trunk group it is usually converted into a CPG message on the ingress trunk group. When this control is set to supported the ACM to CPG mapping is prevented and the received ACM is silently discarded on the ingress side. |
| signalOnlySipAlert | O | enumeration | unSupported | On an ISUP-SIP call, only generate the ACM/CPG message in response to an 180 message - alerting. No ACM/CPG should be generated for other 18x messages or 300 messages. |
| dontMapToHeaderToOcn | O | enumeration | unSupported | When interworking between SIP and ISUP the To header field should not be interworked to the ISUP original called number parameter. |
| noInNumberUpdates | O | enumeration | unSupported | When the PSX performs a TOLL FREE number translation the called IN and original called IN number parameters used in Japan should not be updated based on the new called party number parameter. |
| usePsxChgIndForCpgInPresubCall | O | enumeration | unSupported | Should the PSX ACM charge indicator be used to overwrite the charge indicator field of the BCI for CPG messages or should the value received be transited. |
| alwaysAddOptionalPtr | O | enumeration | unSupported | Should the optional parameter pointer always be added into ISUP messages even when no optional parameters are defined |
| suppressCitForPreSubAcm | O | enumeration | unSupported | Ensure the Carrier Information Transfer parameter is suppressed in an Early ACM for Pre-Subscription call. |
| onlySendAcmFor181 | O | enumeration | unSupported | For an ISUP-SIP call, only send an ACM message if a 181 is received before an ACM is sent. In this case we do not want to send an ACM and CPG. If an ACM has already been sent then the 181 is mapped to a CPG |
| dontSendExm | O | enumeration | unSupported | Specifies whether its ok to send EXM messages on a trunk group |
| citTermExchangeLogic | O | enumeration | unSupported | CIT and CAI only in first backward message when terminating exchange |
| bciInCpgWithCit | O | enumeration | unSupported | BCI only in CPG if CIT is in the msg |
| reaffirmBlockAfterReset | O | enumeration | unSupported | When RSC or GRS is sent on a locally blocked circuit, BLO will also be sent to reaffirm the blocking. |
| dontGenerateDiags | O | enumeration | unSupported | Specifies if diagnostics should not be generated for JAPAN |
| onlyCpgInBandBeforeAcm | O | enumeration | unSupported | Should a CPG containing an inband information event arriving before an ACM be transited. If set CPG without an inband information event arriving before ACM will be discarded |
| simpleEcBciInAllBkMsg | O | enumeration | unSupported | For simple echo control, examine every backward message for the BCI echo control indication field and act accordingly |
| allowCaForAnnouncements | O | enumeration | unSupported | Allow charge area parameter for announcements |
| uniqueTransitCit | O | enumeration | unSupported | PROTOCOLS - Japan only DEFAULT - UNSUPPORTED UNSUPPORTED - The GSX will add in transit carrier data with the same carrier code as the previous code if configured by the PSX SUPPORTED - The GSX will compare the transit carrier code configured on the PSX with the last carrier code add by the previous exchange and if they are both transit and both have the same carrier code the GSX will not add in duplicate information. The ingress signaling profile controls checking the backward messages and the egress signaling profile controls checking the forward messages. CMD - UNIQUE TRANSIT CIT SCREEN - Services - Unique Transit CIT CONTROL - SS7_CONTROL_UNIQUE_TRANSIT_CIT REQS - PCR710 CQID51235 |
| validateIsubFromSip | O | enumeration | unSupported | PROTOCOLS - Japan Only DEFAULT - UNSUPPORTED UNSUPPORTED - The GSX will not check the ISUB digits SUPPORTED - The GSX will ensure that only digits 0-9 are allowed in the NSAP ISUB from SIP CMD - VALIDATEISUBFROMSIP SCREEN - Services - Validate ISUB CONTROL - SS7_CONTROL_VALIDATE_ISUB_FROM_SIP REQS - WILLCOM PCR 151 and PCR 152 |
| isubTypeFromSip | O | enumeration | nsap | PROTOCOLS - Japan Only DEFAULT - NSAP NSAP - only ISUB of type NSAP from SIP supported USERSPEC - only ISUB of type USER SPECIFIC from SIP supported BOTH - NSAP and USER SPECIFIC ISUB from SIP supported NONE - No ISUB types from SIP supported CMD - ISUBTYPEFROMSIP SCREEN - Services - ISUB Type from SIP CONTROL - SS7_CONTROL_ISUB_TYPE_NSAP SS7_CONTROL_ISUB_TYPE_USER_SPEC SS7_CONTROL_ISUB_TYPE_NONE SS7_CONTROL_ISUB_TYPE_BOTH REQS - WILLCOM PCR 151 and PCR 152 |
| qor | O | enumeration | unSupported | PROTOCOLS - ITU + CHINA DEFAULT - UNSUPPORTED UNSUPPORTED - The Query on release capability parameter will not be supported SUPPORTED - The Query on release capability parameter will be supported CMD - QOR SCREEN - Parameter - Query on Release CONTROL - SS7_CONTROL_QOR REQS - Q763 section 3.91 for supporting number portability |
| npfi | O | enumeration | unSupported | PROTOCOLS - ITU + CHINA DEFAULT - UNSUPPORTED UNSUPPORTED - The Number Portability Forward Information parameter will not be supported SUPPORTED - The Number Portability Forward Information parameter will be supported CMD - NPFI SCREEN - Parameter - NPFI CONTROL - SS7_CONTROL_NPFI REQS - Q763 section 3.101 for supporting number portability |
| chgMsgBeforeAcm | O | enumeration | unSupported | PROTOCOLS - Japan only DEFAULT - UNSUPPORTED UNSUPPORTED - The GSX will not transit the CHG message in the backward direction before an ACM has been received. SUPPORTED - The GSX will transit the CHG message in the backward direction before an ACM has been received. CMD - CHGBEFOREACM SCREEN - Messages - CHG before ACM CONTROL - SS7_CONTROL_CHG_BEFORE_ACM |
| forceEchoCntrl | O | enumeration | unSupported | Indicated that echo cancellation will be applied on calls regardless of information contained in signalling messages with the exception of data calls |
| noObciSipAcm | O | enumeration | unSupported | PROTOCOLS - Generic DEFAULT - UNSUPPORTED UNSUPPORTED - The GSX will not include the OBCI parameter in the ACM in all the existing scenarios. SUPPORTED - The GSX will not include the OBCI parameter in the ACM message when interworking with SIP CMD - NOOBCISIPACM SCREEN - Services - No OBCI SIP ACM CONTROL - SS7_CONTROL_NO_OBCI_SIP_ACM |
| buildRdiForSipIwk | O | enumeration | unSupported | PROTOCOLS - All DEFAULT - UNSUPPORTED SUPPORTED - when interworking with SIP and the IAM contains the original called number and redirecting number parameters but no redirecting information parameter the GSX will generated one with the following values. redirecting indicator (3) call forwarded redirecting counter (1) original redirection reason (2) no reply redirection reason (2) no reply UNSUPPORTED - no RDI is generated. CMD - BUILDRDIFORSIPIWK SCREEN - Services - Build RDI for SIP IWK CONTROL - SS7_CONTROL_BUILD_RDI_FOR_SIP_IWK REQS - WILLCOM PCR 982 |
| noAcmObciForSipApn | O | enumeration | unSupported | PROTOCOLS - Generic DEFAULT - UNSUPPORTED UNSUPPORTED - The GSX will include the OBCI parameter in the ACM. SUPPORTED - The GSX will not include the OBCI parameter in the ACM message when interworking to SIP and the NOA is 0x78 (APN). When interworking with SIP-I with MIME containing ACM with OBCI the ACM is transited with OBCI. CMD - NO OBCI FOR SIP APN SCREEN - Services - No OBCI FOR SIP APN CONTROL - SS7_CONTROL_NO_OBCI_FOR_SIP_APN |
| networkData | O | enumeration | unSupported | PROTOCOLS - ANSI, ITU DEFAULT - UNSUPPORTED UNSUPPORTED - Network Data is not Supported in the IAM message. SUPPORTED - Network Data is Supported in the IAM message. CMD - NETWORK DATA SCREEN - Parameters - Network Data CONTROL - SS7_CONTROL_NETWORK_DATA |
| alwaysAddCnId | O | enumeration | unSupported | PROTOCOLS - Japan DEFAULT - UNSUPPORTED SUPPORTED - when interworking with SIP and the calling party number is restricted then the cause of no ID parameter is included in the IAM even if there is no parameter data received from SIP. UNSUPPORTED - CNID is only generated if received from SIP. CMD - CNID ALWAYS ADDED SCREEN - Services - CNID always added CONTROL - SS7_CONTROL_ALWAYS_ADD_CNID REQS - CQ60811 |
| chgBetweenAcmAndAnm | O | enumeration | unSupported | PROTOCOLS - Japan DEFAULT - SUPPORTED. UNSUPPORTED - The GSX will not transit the CHG message in the backward direction between an ACM and ANM. SUPPORTED - The GSX will transit the CHG message in the backward direction between an ACM and ANM. CMD - CHGBETWEENACMANDANM SCREEN - Messages - CHG between ACM-ANM CONTROL - SS7_CONTROL_CHG_BETWEEN_ACM_AND_ANM REQS - CQ63302,CQ63184 |
| ituCai24 | O | enumeration | unSupported | PROTOCOLS - ITU, CHINA DEFAULT - UNSUPPORTED UNSUPPORTED - ITU Cause Value 24 - Call Rejected due to Feature at Destination - is not recognized. SUPPORTED - ITU Cause Value 24 is recognized. CMD - ITUCAI24 SCREEN - Services - ITU CAI 24 CONTROL - SS7_CONTROL_ITU_CAI_24_SUPPORT REQS - MGCF TS29.163 |
| cellularCpcs | O | enumeration | unSupported | PROTOCOLS - ITU, CHINA DEFAULT - UNSUPPORTED UNSUPPORTED - Calling Party Category values Cellular and Cellular Roaming are not recognized. SUPPORTED - Calling Party Category values Cellular and Cellular Roaming are recognized. CMD - CELLULARCPCS SCREEN - Services - Cellular CPCs CONTROL - SS7_CONTROL_CELLULAR_CPCS_SUPPORT REQS - MGCF TS29.163 |
| iepsCpc | O | enumeration | unSupported | PROTOCOLS - ITU, CHINA DEFAULT - UNSUPPORTED UNSUPPORTED - Calling Party Category value IEPS is not recognized. SUPPORTED - Calling Party Category value IEPS is recognized. CMD - IEPSCPC SCREEN - Services - IEPS CPC CONTROL - SS7_CONTROL_IEPS_CPC_SUPPORT REQS - MGCF TS29.163 |
| tandemCallCounter | O | enumeration | unSupported | PROTOCOLS - JAPAN DEFAULT - UNSUPPORTED UNSUPPORTED - The GSX will not be able to decode and transit the Tandem Call Counter parameter received in IAM message. SUPPORTED - The GSX will decode/encode, increment and transit the Tandem Call Counter parameter received in IAM message. CMD - TANDEMCALLCOUNTER SCREEN - Parameters - Tandem Call Counter CONTROL - SS7_CONTROL_TANDEM_CALL_COUNTER_SUPPORT REQS - SBTM - PCR1404 |
| routeInformation | O | enumeration | unSupported | PROTOCOLS - ITU DEFAULT - UNSUPPORTED. UNSUPPORTED - GSX will not process the Route Information parameter received in the IAM message. KGL-specific routing is not enabled SUPPORTED - GSX will process the Route Information parameter received in the IAM message. KGL-specific routing is enabled CMD - ROUTEINFORMATION SCREEN - Parameters - RouteInformation CONTROL - SS7_CONTROL_ROUTE_INFORMATION_SUPPORT REQS - KDDI - PCR1624 |
| noChgCountIfFlexChgRate | O | enumeration | unSupported | PROTOCOLS - JAPAN DEFAULT - UNSUPPORTED UNSUPPORTED - CHG count is incremented if there is Flexible Charge Rate SUPPORTED - CHG count is not incremented if there is Flexible Charge Rate CMD - NOCHGCOUNTIFFLEXCHGRATE SCREEN - Services - No CHG Count If Flex Chg Rate CONTROL - SS7_CONTROL_NO_CHG_COUNT_IF_FLEX_CHG_RATE REQS - PCR1411 |
| removeHlcIfNoLlc | O | enumeration | unSupported | PROTOCOLS - ALL DEFAULT - UNSUPPORTED UNSUPPORTED - HLC is not removed if there is no LLC SUPPORTED - HLC is removed if there is no LLC CMD - REMHLCIFNOLLC SCREEN - Services - Remove HLC If No LLC CONTROL - SS7_CONTROL_REMOVE_HLC_IF_NO_LLC REQS - PCR1409 |
| updateAnmBci | O | enumeration | unSupported | PROTOCOLS - JAPAN DEFAULT - UNSUPPORTED UNSUPPORTED - BCI in ANM defaulted if not present SUPPORTED - BCI in ANM taken from last received in ACM or CPG and the charge indicator is updated. CMD - UPDATEANMBCI SCREEN - Services - ANM BCI from ACM/CPG CONTROL - SS7_CONTROL_UPDATE_ANM_BCI_SUPPORT REQS - Pcr1407-SBTM |
| discardContractorNum | O | enumeration | unSupported | PROTOCOLS - JAPAN DEFAULT - UNSUPPORTED UNSUPPORTED - The GSX will not discard the Contractor number parameter in the IAM (SBB specific) IAM message. SUPPORTED - The GSX will discard the contractor number parameter in the IAM (SBB specific) CMD - DISCARDCONTRACTORNUM SCREEN - Services - Discard Contractor Num CONTROL - SS7_CONTROL_DISCARD_CONTRACTOR_NUM_SUPPORT |
| addInfoTransfer | O | enumeration | unSupported | PROTOCOLS - JAPAN DEFAULT - UNSUPPORTED UNSUPPORTED - Additional Info Transfer Parameters are not decoded and transited SUPPORTED - Additional Info Transfer Parameters are decoded and transited CMD - AITE0 SCREEN - Parameters - Add Info Transfer CONTROL - SS7_CONTROL_ADDITIONAL_INFO_TRANSFER_SUPPORT REQS - PCR1402 |
| adpNumber | O | enumeration | unSupported | PROTOCOLS - JAPAN DEFAULT - UNSUPPORTED UNSUPPORTED - ADP Number Parameters are not decoded and transited SUPPORTED - ADP Number Parameters are decoded and transited CMD - ADP NUMBER SCREEN - Parameters - ADP Number CONTROL - SS7_CONTROL_ADP_NUMBER_SUPPORT REQS - PCR1402 |
| transferInfo | O | enumeration | unSupported | PROTOCOLS - JAPAN DEFAULT - UNSUPPORTED UNSUPPORTED - Transfer Info Parameters are not decoded and transited SUPPORTED - Transfer Info Parameters are decoded and transited CMD - TRANSFER INFO SCREEN - Parameters - Transfer Info CONTROL - SS7_CONTROL_TRANSFER_INFO_SUPPORT REQS - PCR1402 |
| dpc | O | enumeration | unSupported | PROTOCOLS - JAPAN DEFAULT - UNSUPPORTED UNSUPPORTED - DPC Parameters are not decoded and transited SUPPORTED - DPC Parameters are decoded and transited CMD - DPC SCREEN - Parameters - DPC CONTROL - SS7_CONTROL_DPC_SUPPORT REQS - PCR1402 |
| uuiRestrictions | O | enumeration | unSupported | PROTOCOLS - JAPAN DEFAULT - UNSUPPORTED UNSUPPORTED - Do not discard subsequent UUIs based on BCI field values received in ACM/CPG. SUPPORTED - Discard subsequent UUIs based on BCI field values received in ACM/CPG. CMD - UUIRESTRICTIONS SCREEN - Services - UUI Restrictions CONTROL - SS7_CONTROL_UUI_RESTRICTIONS REQS - SBTM - PCR1496 |
| calledNoa8ForNp | O | enumeration | unSupported | PROTOCOLS - ITU + CHINA DEFAULT - UNSUPPORTED UNSUPPORTED - The Called Noa value 8 will not be supported SUPPORTED - The Called Noa value 8 will be supported CMD - CALLEDNOA8FORNP SCREEN - Services - Called NOA 8 for NP CONTROL - SS7_CONTROL_CALLED_NOA_8_FOR_NP REQS - Q763 section 3.9 (b) for supporting number portability |
| dontClearCdrFields | O | enumeration | unSupported | PROTOCOLS - JAPAN DEFAULT - UNSUPPORTED UNSUPPORTED - Clear called Charge Area and/or Charging Rate when Charge Information delay parameter is recieved in ACM or CPG. SUPPORTED - Do not clear Called Charge Area and/or Charging Rate when Charge Information Delay parameter is recieved in ACM or CPG. CMD - DONTCLEARCDRFIELDS SCREEN - SERVICES - Dont Clear Cdr Fields CONTROL - SS7_CONTROL_DONT_CLEAR_CDR_FIELDS REQS - SBTM-PCR1560,PCR1570 |
| saveIamCit | O | enumeration | unSupported | PROTOCOLS - JAPAN DEFAULT - UNSUPPORTED UNSUPPORTED - existing functionality and IAM CIT can be overwritten SUPPORTED - CIT information in the IAM will not be overwritten by backwards information. CMD - SAVEIAMCIT SCREEN - SERVICES - Save IAM CIT CONTROL - SS7_CONTROL_SAVE_IAM_CIT_SUPPORT REQS - SBTM - PCR1560 |
| storeChargeForIscTcTypeAndPayPhone | O | enumeration | unSupported | PROTOCOLS - JAPAN DEFAULT - UNSUPPORTED UNSUPPORTED - The Last Charge Information is stored in the CDR Records SUPPORTED - The First Charge Information is stored in the CDR Records CMD - STORE CHARGE FOR IXC TC TYPE AND PAYPHONE SCREEN - Services - Store Charge for IXC/TC Type and Payphone CONTROL - SS7_CONTROL_STORE_SHARGE_FOR_IXC_TC_TYPE_AND_PAYPHONE REQS - PCR1411 |
| dpcInformation | O | enumeration | unSupported | PROTOCOLS - JAPAN DEFAULT - UNSUPPORTED UNSUPPORTED - The GSX will not generate/transit DPC Information parameter in the IAM SUPPORTED - The GSX will generate/transit or discard the DPC Information parameter in the IAM CMD - DPCINFORMATION SCREEN - Parameters - DPC Information CONTROL - SS7_CONTROL_DPC_INFORMATION_SUPPORT REQS - PCR1405 |
| relForDuplicateIam | O | enumeration | unSupported | PROTOCOLS - ALL DEFAULT - UNSUPPORTED UNSUPPORTED - When a misplaced call is detected, send an RSC to clear the circuit. SUPPORTED - When a misplaced call is detected, send a REL with CV=31 to clear the circuit. CMD - RELFORDUPLICATEIAM SCREEN - Services - REL for Duplicate IAM CONTROL - SS7_CONTROL_REL_FOR_DUPLICATE_IAM REQS - PCR1573 |
| relForEarlyAnm | O | enumeration | unSupported | PROTOCOLS - JAPAN, ITU, CHINA DEFAULT - UNSUPPORTED UNSUPPORTED - Call reattempted. SUPPORTED - If an ANM is received before a backward message, send REL cause 31 in both directions. CMD - RELFOREARLYANM SCREEN - Services -- REL for early ANM CONTROL - SS7_CONTROL_REL_FOR_EARLY_ANM_SUPPORT REQS - SBTM -- PCR1569 |
| forceEchoCntrlNoUpdate | O | enumeration | unSupported | PROTOCOLS - ALL DEFAULT - UNSUPPORTED UNSUPPORTED - Echo Cancelling will be enabled dependent on ECI bit. SUPPORTED - Echo Cancelling will be enabled but ECI bit will not be updated. CMD - FORCEECHOCNTRLNOUPDATE SCREEN - Services -- Force Echo Control No Update CONTROL - SS7_CONTROL_FORCE_ECHO_CNTRL_NO_UPDATE REQS - PCR1652 |
| earlyAcmChgNoInd | O | enumeration | unSupported | PROTOCOLS - ALL DEFAULT - UNSUPPORTED UNSUPPORTED - Charge Indication in Early ACM will not always be No Indication. SUPPORTED - Charge Indication in Early ACM will always be No Indication. CMD - EARLYACMCHGNOIND SCREEN - Services -- Early ACM Chg No Ind CONTROL - SS7_CONTROL_EARLY_ACM_CHG_NO_IND REQS - SBTM -- PCR1649 |
| transitReceivedCit | O | enumeration | unSupported | PROTOCOLS - JAPAN DEFAULT - UNSUPPORTED UNSUPPORTED - Modify received CIT parameter as usual SUPPORTED - Transit received CIT parameter unchanged CMD - TRANSITRCVDCIT SCREEN - Services - Transit Received CIT CONTROL - SS7_CONTROL_TRANSIT_RECEIVED_CIT REQS - SBTM - PCR1499 |
| onlyScreenCitGen | O | enumeration | unSupported | PROTOCOLS - JAPAN DEFAULT - UNSUPPORTED UNSUPPORTED - Generate sub-parameters in CIT without restrictions SUPPORTED - Screen sub-parameters generated in CIT CMD - ONLYSCREENCITGEN SCREEN - Services - Only Screen CIT Gen CONTROL - SS7_CONTROL_ONLY_SCREEN_CIT_GEN REQS - SBTM - PCR1499 |
| slovakChargeMessage | O | enumeration | unSupported | PROTOCOLS - Slovak Only DEFAULT - UNSUPPORTED UNSUPPORTED - The Slovak charge message will not be supported SUPPORTED - The Slovak charge message will be supported CMD - SLOVAK CHARGE MESSAGE SCREEN - Messages - CRG (Slovak) CONTROL - SS7_CONTROL_SLOVAK_CRG_SUPPORT REQS - Slovak Telecom - PCR1676 |
| eciTrap | O | enumeration | unSupported | PROTOCOLS - JAPAN DEFAULT - UNSUPPORTED UNSUPPORTED - No traps for ECI SUPPORTED - If ECI is recieved in the IAM, the call will be marked as an emergency call and a trap will be generated. CMD - ECITRAP SCREEN - Services - ECI Trap CONTROL - SS7_CONTROL_ECI_TRAP REQS - SBTM - PCR1685 |
| checkIxcAgainstTlec | O | enumeration | unSupported | PROTOCOLS - JAPAN DEFAULT - UNSUPPORTED UNSUPPORTED - GSX will add in IXC data with the same carrier code as the TLEC info, if configured by PSX SUPPORTED - GSX will compare the IXC code configured on PSX with the TLEC carrier code added by the terminating exchange and if they are the same, GSX will not add in duplicate information. CMD - CHECKIXCAGAINSTTLEC SCREEN - Services - Check IXC Against TLEC CONTROL - SS7_CONTROL_CHECK_IXC_AGAINST_TLEC REQS - SBTM - PCR1827 |
| redirectionNumRestrictionInRel | O | enumeration | unSupported | PROTOCOLS - ITU, CHINA DEFAULT - UNSUPPORTED UNSUPPORTED - Redirection Number Restriction Parameter will not be supported in the REL message. SUPPORTED - Redirection Number Restriction Parameter will be supported in the REL message. CMD - REDNUMRISTINREL SCREEN - Parameter - RedNumRistInRel CONTROL - SS7_CONTROL_RNR_REL REQS - SONUS00079696 |
| screenCitBeforeCdr | O | enumeration | unSupported | PROTOCOLS - JAPAN DEFAULT - UNSUPPORTED UNSUPPORTED - GSX will add all the carrier information transfer parameter data to the CDR and then screen out any unneeded data before generating the signaling message SUPPORTED - GSX will screen out any carrier information transfer data that will not be sent in the signaling message and then store the carrier information transfer parameter in the CDR. CMD - SCREEN CIT BEFORE CDR SCREEN - Services - Screen CIT before CDR CONTROL - SS7_CONTROL_SCREEN_CIT_BEFORE_CDR REQS - SBTM - PCR1935 |
| russiaRng | O | enumeration | unSupported | PROTOCOLS - Russia Only DEFAULT - UNSUPPORTED UNSUPPORTED - The Russia RNG message will not be supported SUPPORTED - The Russia RNG message will be supported CMD - RNG SCREEN - Messages - RNG (Russia) CONTROL - SS7_CONTROL_RUSSIA_RNG_SUPPORT REQS - ISUP-R-2000 - PCR1223 |
| overrideInBand | O | enumeration | unSupported | PROTOCOLS - ALL DEFAULT - UNSUPPORTED UNSUPPORTED - Normal behaviour SUPPORTED - Inband indicator in OBCI or Event Indicator in CPG message will be ignored unless BCI has Interworking Indicator Set CMD - OVERRIDE INBAND SCREEN - Services - Override Inband CONTROL - SS7_CONTROL_OVERRIDE_INBAND REQS - ATT - PCR2034 |
| sendingEnbloc | O | enumeration | unSupported | PROTOCOLS - ITU/CHINA DEFAULT - Dependent on SAM control UNSUPPORTED - The Trunkgroup is able to send overlap and enbloc. SUPPORTED - The Trunkgroup is only able to send enbloc. CMD - SENDING ENBLOC SCREEN - Services - Sending Enbloc CONTROL - SS7_CONTROL_SENDING_ENBLOC REQS - PCR2062 |
| hopCounter | O | enumeration | unSupported | Is the hop counter parameter supported for the ISUP Signaling Profile. |
| tandemLimitCounter | O | uint8 | 0 | Limit Counter to be set in outgoing IAM in Tandem Call Counter parameter in SIP MIME case |
| chargeArea | O | string | This Service Control is used to populate the Charge Area if it contains a valid 5 digit Charge Area. The Charge Area will be set in the ACM or CPG message if a script is returned from the PSX or for Disconnect treatment for SIP MIME case | |
| deleteIxcTcCode | O | string | Delete the IXC/TC code in the CIT for SIP MIME case | |
| locationOfRel | O | enumeration | notUsed | Update the Location in the REL for SIP MIME case |
| locationOfRel34 | O | enumeration | notUsed | Update the Location in the REL if Cause Value is 34 for SIP |
| locationOfRel42 | O | enumeration | notUsed | Update the Location in the REL if Cause Value is 42 for SIP |
| colpColrIgw | O | enumeration | unSupported | PROTOCOLS - ITU/ANSI DEFAULT - UNSUPPORTED UNSUPPORTED - Connect Number will not have support COLP-COLR functionality SUPPORTED - Connect Number will have support for COLP-COLR and IGW functionality. CMD - COLPCOLRIGW SCREEN - Services - COLPCOLRIGW CONTROL - SS7_CONTROL_COLPCOLRIGW_SUPPORT REQS - PCR3816 |
| updateInternalNetworkIndicatorInCalledPartyNumber | O | enumeration | transit | This parameter is used to update the Internal Network Indicator in the Called Party Number. Is set to TRANSIT, the value received is unchanged, otherwise the value configured (ALLOWED/NOTALLOWED) is sent. |
| updateNumberIncompleteIndicatorInCallingPartyIndicator | O | enumeration | transit | This parameter is used to update the Number incomplete Indicator in the Calling Party Number. Is set to TRANSIT, the value received is unchanged, otherwise the value configured (COMPLETE/INCOMPLETE) is sent. |
| remoteMnpDip | O | enumeration | unSupported | This parameter is used to support remote MNP Dipping service |
| dropAPPinIAM | O | enumeration | unSupported | This parameter is used to drop the APP with context ID = 0x3FFF in IAM for ANSI |
| allowSGDinGenericDigits | O | enumeration | unSupported | Controls whether SGD parameter(digit type 25) in GDP in the SIP-I messages is supported. |
| setBciCdpsBasedOnSipCallStatus | O | enumeration | unSupported | Set the BCI parameter, called party status indicator based on egress SIP call status. |
| sendPRIonRELforCBWF | O | enumeration | unSupported | This controls sending of CBWF Information in APP parameter in PRI/APM message during tearing down of CBWF call. |
| sendAPPinAPMforCBWF | O | enumeration | unSupported | Controls whether to send CBWF Information in APP parameter(ACI=126) in a new APM message or to send the APP in the next backward messages like ACM,ANM etc. |
| gr317ChargeNumberCompliance | O | enumeration | unSupported | PROTOCOLS - ANSI, DEFAULT - UNSUPPORTED, UNSUPPORTED - Dont check charge number digit length for GR317 compliance, SUPPORTED - Check charge number digit length for GR317 compliance and dont send if greater than 10 digits. |
| REST API: GET Example |
|---|
curl -kisu 'admin:secret' -X GET https://{SBX-SERVER}/api/config/profiles/signaling/isupSignalingProfile/{name} |
| REST API: POST Example |
|---|
curl -kisu 'admin:secret' -X POST -H 'Content-Type: application/vnd.yang.data+xml' https://{SBX-SERVER}/api/config/profiles/signaling --data ' |
| REST API: DELETE Example |
|---|
curl -kisu 'admin:secret' -X DELETE https://{SBX-SERVER}/api/config/profiles/signaling/isupSignalingProfile/{name} |
Overview
Content Tools