Skip to end of metadata
Go to start of metadata

In this section:

 

Use this profile to create a template for the ISUP signaling services used by the SBC Core 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.

To see the list of available default signaling profiles, execute the following command from the CLI configure mode:

% show profiles signaling isupSignalingProfile <profile name>

Create a custom signaling profile by copying a default profile and then modifying your copy rather than directly modifying a default profile. This leaves the master copy intact and avoids potential problems should the default profiles need to be reset. This strategy also provides more flexibility if controls need to be modified. To copy a default profile, create your new profile using the following command setting baseProfile parameter to the appropriate default profile.

% set profiles signaling isupSignalingProfile <profile name>

Caution

When a base profile is applied to an ISUP Signaling profile for SIP-I, the base profile value overrides the ISUP Signaling Profile value in the application even though the "show" command for ISUP Signaling Profile in CLI may display different values. To overcome this, set the required value in the ISUP Signaling profile again to sync the configuration database and the application code with each other as per the configured value.

 

Command Syntax

% set profiles signaling isupSignalingProfile <profile name> <parameter name> <supported | unSupported>

% show profiles signaling isupSignalingProfile <profile name> <parameter>

% delete profiles signaling isupSignalingProfile <profile name> <parameter> 

ISUP Parameter List

[ a ] [ b ] [ c ] [ d ] [ e ] [ f ] [ g ] [ h ] [ i ] [ j ] [ l ] [ m ] [ n ] [ o ] [ p ] [ r ] [ s ] [ t ] [ u ] [ v ]
a
accessDelivery  accessTransInFar  accessTransport  accessTransportInFac 
addInfoTransfer  adpNumber  ait  allianceScreenInd 
allowCaForAnnouncements  allowCallsOnHwBlock  allowSGDinGenericDigits allowUnscreenedCin 
alwaysAddCnId  alwaysAddOptionalPtr  announcementInd  ansi95Cfn 
ansi95Cqm  ansi95Grs  apm  assumeOutgoingDeviceIncluded 
atRel  awaitTwoGroupMsgs     

 

b
backwardGvns baseProfile  baseVersion  bbIam 

bciInCpgWithCit

bciRel

bcm

bloAfterSetup

blueBookInRel

buildRdiForSipIwk

businessGroup

 

 

c
callDiversion  callDiversionTreatment  callHistory  callModMsgs 
callOfferingTreatment  callReference  callReferenceFrj  callTransferNumber 
callTransferReference  calledBsm  calledDirectoryNumber  calledInNum 
calledNoa8ForNp  calledTfm  callingBsm  callingOfm 
carrierSelection  causeInCpg  causeInRlc  ccl 
ccnr  ccss  cellularCpcs  cfn 
chargeArea chargeIndSetting  chargeMsgInSpeech  chargeNumber 
checkIxcAgainstTlec  chgBetweenAcmAndAnm  chgMsgBeforeAcm  ci 
circuitAssignmentMap  citTermExchangeLogic  collectCallReq  colpColrIgw 
com  compatibility  con  conferenceTreatment 
conferenceTreatmentInAnm  connectedNumber  connectedNumberInAcm  connectedNumberInCpg 
connectionPointTrunkType  connectionReq  connectionReqInFaa  connectionReqInFar 
connectionReqInIam  connectionReqInInf  continuity  correlationId 
cpgBeforeAcm  cpnRel  cqmCqr  cqmForResync 
cqmOnCardSwap  cugInterlockCode  cvtCvr   

 

d
deleteIxcTcCode  diagnostics  dialedNumber  discardContractorNum 
displayInfoInAcm  displayInfoInCon  displayInfoInCpg  displayInfoInIam 
displayInformation  dmsFe  dontClearCdrFields  dontGenerateDiags 
dontMapToHeaderToOcn  dontSendExm  dpc  dpcInformation 
dropAPPinIAM  dropCauseInAcmWhenIwk  dropUsiFromNonIsup  drs 

 

e
eMcid  earlyAcmChgNoInd  echoControl  echoControlInIam 

eci

eciTrap

egressService

eit

emergencyCallInf

 

 

f
fac  facility  fallback  fciUserPartChosenCarrier 
fciUserPartIwk  fciUserPartTrans  forceEchoCntrl  forceEchoCntrlNoUpdate 
forwardCallProgress  forwardGvns  forwardNetworkSpecificInfo  forwardSuspend 
forwardTransferMessage  freePhoneInd     

 

g
generateJapanIcsParams  genericAddressRel  genericDigits  genericName 
genericNotification  genericNotificationInFac  genericNotificationRepeatable  genericNumInAcm 
genericNumInFac  genericNumInInf  genericNumber  genericNumberInCpg 
genericNumberRepeatable  genericNumberRepeatableIam  genericOperation  genericReference 
gi  gr317ChargeNumberCompliance

gr317ScreeningInd

groupRedirectionCount

 

h
hardToReachInd  holdingInd  hopCountState  hopCountValue 

hopCounter

 

i
iamGeneratedCarrierCodeInCdr  iepsCpc  incomingTrunkIdCode  informationInd 
inrInAllStates  inrInf  invTnsRelease  iriOri 
iriOriRcv  iriOriSent  isubTypeFromSip  ituCai24 
itxTxa  iui jti   

 

 

j
jurisdiction 

 

l
ldli  locationNumber  locationOfRel  locationOfRel34 
locationOfRel42  lookAheadForBusy  loopPrevention 

lpa 

 

m
maRel  mapDmsFeParameter  maxCalledPartyDigits  maxCallingPartyDigits 
mi  mlpp  msi  multiCarrierEnvironment 

 

n
ncr  networkData  networkIdentity  networkIndicator 
networkManagement  networkManagementInfo  networkSwitchNumber  networkTransport
nfci  nfciLblRciProc nfciLnk nft
nii niri noAcmObciForSipApn noChgCountIfFlexChgRate
noInNumberUpdates  noIpEchoInd noObciSipAcm notificationInd
npfi nrmSupport nrop nsa
nsf      

 

o
obciAnm olipCheck olipCheckOnSend olm
onlyCpgInBandBeforeAcm onlyScreenCitGen onlySendAcmFor181 operatorSelection
operatorServiceInfo opr optionalFci originalCalledNumber originatingIscPointCode
otgnAnsi92 otherDigitStringSpecialDigitF overrideInBand  

 

p
pam pciPassOnDefault pcli presentationNumber
preventAcmToCpgMapping propagationDelay propagationDelaySupport  

 

r
reaffirmBlockAfterReset recommendationInCai redirectingNumber redirectionCap
redirectionInfoAcm redirectionInfoIam redirectionNumRestrictionInRel redirectionNumber
redirectionNumberInAcm redirectionNumberInAnm redirectionNumberRestriction relForDuplicateIam
relForEarlyAnm releaseLinkTrunking remoteMnpDip remoteOperationInRel
remoteOperations removeHlcIfNoLlc revision rlcAcknowledgeGrs
routeInformation routingInfoInd rr russiaRng

 

s

saveIamCit

sccpProcedure

scfId  

screenCitBeforeCdr

sdnIncrement

segmentation

sendAPPinAPMforCBWF

sendBloOnHwBlock

sendPRIonRELforCBWF

sendRscForCallsOnHwBlock

sendTwoGroupMsgs

sendingEnbloc

serviceActivation

serviceActivationInRel

serviceCodeInd

setBciCdpsBasedOnSipCallStatus

sgmPci

signalOnlySipAlert

signalingPointCode

simpleEcBciInAllBkMsg

sliInIam

slovakChargeMessage

spc6 spcInIrs

specialDigits

specialProcessReq

storeChargeForIscTcTypeAndPayPhone

subscriberPriorityClass

subsequentAddressMessage

suppressCitForPreSubAcm

 

 

 

 

t
t7Transit t11Active t11EarlyAcm tandemCallCounter
tandemLimitCounter tci tit tmrPrime
transMedUsedInNrm transactionReq transferInfo transitCfn
transitNetworkSelection transitReceivedCit transitUnrecognized transmissionMediumUsed
truncateCdpn trunkOfferingSupport    

 

u

u2uServiceLevel

ucic

uidActionInd

uidCapabilityInd

uniqueTransitCit

upaUpt

updateAnmBci   

updateInternalNetworkIndicatorInCalledPartyNumber

updateNumberIncompleteIndicatorInCallingPartyIndicator 

upvExchangeRoles

usePsxChgIndForCpgInPresubCall

userServiceInformation

userTeleService

usiPrime

usr

uuIndAcm

uuIndCon

uuIndInFar

uuIndRel

uuInfo

uuInfoAcm

uuiInInf

uuiRestrictions

uuindAnm

uuindCpg

 

 

v
validateIsubFromSip versionId visitorMa
[ a ] [ b ] [ c ] [ d ] [ e ] [ f ] [ g ] [ h ] [ i ] [ j ] [ l ] [ m ] [ n ] [ o ] [ p ] [ r ] [ s ] [ t ] [ u ] [ v ]

Command Parameters

Table : ISUP Signaling Profile Parameters

Parameter

Length/Range

Description

isupSignalingProfile

1-23

The name of the ISUP signaling group you are configuring. This name must match the strings to be used in the version field of the SIP message header. The following default (base) ISUP profiles are available:

  • ansi00
  • ansi88
  • etsi121
  • etsi356
  • gr317
  • itu-t88
  • itu-t92+
  • ttc87
  • ttc93+

accessDelivery

N/A

Specifies whether the access delivery information is supported for the ISUP Signaling Profile.

  • supported
  • unSupported (default) 

accessTransInFar

N/A

Specifies whether the access transport parameter is supported in the FAR for the ISUP Signaling Profile:

  • supported
  • unSupported (default) 

accessTransport

N/A

Specifies whether the access transport parameter is supported for the ISUP Signaling Profile.

  • supported
  • unSupported (default) 

accessTransportInFac

N/A

Specifies whether the access transport parameter is supported in the FAC for the ISUP Signaling Profile.

  • supported
  • unSupported (default) 

addInfoTransfer

N/A

Use this flag to support decoding and transiting of additional Info Transfer Parameters.

  • supported
  • unSupported (default) 

adpNumber

N/A

Use this flag to support decoding and transiting ADP Number Parameters.

  • supported
  • unSupported (default) 

ait

N/A

Specifies whether the AIT is supported for the ISUP Signaling profile.

  • supported
  • unSupported (default) 

allianceScreenInd

N/A

Specifies whether the Alliance Screen Indicator parameter is supported for the ISUP Signaling profile.

  • supported
  • unSupported (default) 

allowCaForAnnouncements

N/A

Specifies whether the allow charge area parameter for announcements are supported for the ISUP Signaling profile.

  • supported
  • unSupported (default) 

allowCallsOnHwBlock

N/A

Use this flag to allow calls on a hardware blocked circuit.

  • supported
  • unSupported (default) 
allowSGDinGenericDigits N/A

Specifies whether SGD parameter (Generic Digits type 25) in mime of SIP-I message is supported.

  • supported
  • unSupported (default) 

This flag is not applicable when the SBC is configured for ERE mode.


To process or send the SGD parameter in the SIP-I mime, Generic Digits must also be supported. The command syntax to configure ISUP Signaling Profile to allow Generic Digits is shown below:

% set profiles signaling isupSignalingProfile <profile name> genericDigits <supported | unSupported>

allowUnscreenedCin

N/A

Use this flag to allow values "0" and "2" of the Screening Indicator in the ISUP Signaling profile.

  • supported
  • unSupported (default) 

alwaysAddCnId

N/A

Set flag to "supported" to include cause code of CNID parameter in IAM when calling party number is restricted even if there is no parameter data received from SIP. When set to "unsupported", CNID is only generated if received from SIP. (Protocol: Japan)

  • supported
  • unSupported (default) 

alwaysAddOptionalPtr

N/A

Set to "supported" to always add optional parameter pointer should into ISUP messages even when no optional parameters are defined:

  • supported
  • unSupported (default) 

announcementInd

N/A

Specifies whether the announcement indicator parameter is supported for the ISUP Signaling Profile.

  • supported
  • unSupported (default) 

ansi95Cfn

N/A

Specifies whether the ANSI-95 format for Confusion (CFN) which includes optional parameters should be used.

  • supported
  • unSupported (default) 

ansi95Cqm

N/A

Specifies whether the ANSI 95 version of the CQM message containing the optional pointer is supported for the ISUP Signaling Profile.

  • supported
  • unSupported (default) 

ansi95Grs

N/A

Specifies whether the ANSI-95 format for Group Reset Circuit (GRS) which includes optional parameters should be used.

  • supported
  • unSupported (default) 

apm

N/A

Specifies whether the APM is supported for the ISUP Signaling profile.

  • supported
  • unSupported (default) 

assumeOutgoingDeviceIncluded

N/A

Set flag to "supported" to allow egress echo cancellation software to assume for an ISUP transit call that an outgoing device is included regardless of the NCI setting.

  • supported
  • unSupported (default) 

atRel

N/A

Specifies whether the AT is supported in the REL for the ISUP Signaling profile:

  • supported
  • unSupported (default) 

awaitTwoGroupMsgs

N/A

Set flag to "supported" to await two group messages in the ISUP Signaling Profile.

  • supported
  • unSupported (default) 

backwardGvns

N/A

Specifies whether the backward GVNS parameter is supported for the ISUP Signaling Profile:

  • supported
  • unSupported (default) 

baseProfile

N/A

Specifies the Base Signaling group profile name.

  • defaultRfc3204Ansi00
  • defaultRfc3204Ansi88
  • defaultRfc3204Etsi121
  • defaultRfc3204Etsi356
  • defaultRfc3204Gr317
  • defaultRfc3204ItuT88
  • defaultRfc3204ItuT92
  • defaultRfc3204Ttc87
  • defaultRfc3204Ttc93

baseVersion

N/A

Specifies the Base Signaling group version from RFC3204.

  • ansi00
  • ansi88
  • etsi121 (default)
  • etsi356
  • gr317
  • itut88
  • itut92
  • none
  • ttc87
  • ttc93

bbIam

N/A

Specifies whether the User-To-User indicator parameter is supported in IAM for the ISUP Signaling Profile.

  • supported
  • unSupported (default) 

bciInCpgWithCit

N/A

This control determines whether BCI parameter is included in CPG message, and only applies when a CPG is generated and no ACM/CPG message is received.

  • unSupported – (default) BCI parameter is included in CPG with or without CIT parameter.
  • supported – BCI parameter is not in CPG unless it contains CIT parameter.

bciRel

N/A

Specifies whether the BCI is supported in the REL for the ISUP Signaling Profile.

  • supported
  • unSupported (default) 

bcm

N/A

Specifies if the Backwards Charging Message is supported for the ISUP Signaling Profile.

  • supported
  • unSupported (default) 

bloAfterSetup

N/A

Indicates to send a BLO message for some ANSI protocols when blocking a circuit after a backwards message is received during the call.

  • supported
  • unSupported (default) 

blueBookInRel

N/A

Specifies whether the Blue Book parameters are supported in REL for the ISUP Signaling Profile.

  • supported
  • unSupported (default) 

buildRdiForSipIwk

N/A

When interworking with SIP and the IAM contains the original called number and redirecting number parameters but no redirecting information (RDI) parameter, the SBC generates RDI with the following values:

  • redirecting indicator (3) call forwarded
  • redirecting counter (1)
  • original redirection reason (2) no reply
  • redirection reason (2) no reply

    Flag options:
  • unSupported (default)
  • supported

businessGroup

N/A

Specifies if the Business Group parameter is supported for the ISUP Signaling profile.

  • supported
  • unSupported (default) 

callDiversion

N/A

Specifies if the call diversion is supported for the ISUP Signaling profile.

  • supported
  • unSupported (default) 

callDiversionTreatment

N/A

Specifies if the call diversion treatment parameter is supported for the ISUP Signaling profile.

  • supported
  • unSupported (default) 

callHistory

N/A

Specifies if the call history parameter is supported for the ISUP Signaling profile.

  • supported
  • unSupported (default) 

callModMsgs

N/A

Use flag to specify that the CMR, CMA and CMRJ are supported for the ISUP Signaling profile.

  • supported
  • unSupported (default) 

callOfferingTreatment

N/A

Indicates if the call offering treatment parameter is supported for the ISUP Signaling profile.

  • supported
  • unSupported (default) 

callReference

N/A

Indicates if the call reference parameter is supported for the ISUP Signaling profile.

  • supported
  • unSupported (default) 

callReferenceFrj

N/A

Indicates that the call reference parameter is supported in the FRJ message.

  • supported
  • unSupported (default) 

callTransferNumber

N/A

Indicates if the call transfer number parameter is supported for the ISUP Signaling profile.

  • unSupported (default)
  • supported

callTransferReference

N/A

Indicates if the call transfer reference parameter is supported for the ISUP Signaling profile.

  • supported
  • unSupported (default) 

calledBsm

N/A

Indicates if the called Subs Basic Service Marks parameter is supported for the ISUP Signaling profile.

  • supported
  • unSupported (default) 

calledDirectoryNumber

N/A

Indicates if the called directory number parameter is supported for the ISUP Signaling profile.

  • unSupported (default)
  • supported

calledInNum

N/A

Indicates if the called IN number parameter supported for the ISUP Signaling profile.

  • unSupported (default)
  • supported

calledNoa8ForNp

N/A

Indicates if Called Noa value 8 is supported. (Protocols: ITU, China).

  • unSupported (default)
  • supported

calledTfm

N/A

Indicates if Called Subs Term Facility Marks parameter is supported for the ISUP Signaling profile.

  • unSupported (default)
  • supported

callingBsm

N/A

Indicates if the Calling Subs Basic Service Marks parameter is supported for the ISUP Signaling profile.

  • unSupported (default)
  • supported

callingOfm

N/A

Indicates if Calling Subs Orig Facility Marks parameter is supported for the ISUP Signaling profile.

  • unSupported (default)
  • supported

carrierSelection

N/A

Indicates if carrier selection is supported for the ISUP Signaling profile.

  • unSupported (default)
  • supported

causeInCpg

N/A

Indicates if the cause parameter supported in the CPG for the ISUP Signaling profile.

  • unSupported (default)
  • supported

causeInRlc

N/A

Indicates if cause parameter is supported in the RLC for the ISUP Signaling profile.

  • unSupported (default)
  • supported

ccl

N/A

Indicates if Calling Party Clearing (CCL) message is supported.

  • unSupported (default)
  • supported

ccnr

N/A

Indicates if CCNR Possible Indicator parameter is supported for the ISUP Signaling profile.

  • unSupported (default)
  • supported

ccss

N/A

Indicates if CCSS parameter supported for the ISUP Signaling profile.

  • unSupported (default)
  • supported

cellularCpcs

N/A

Indicates if Calling Party Category values Cellular and Cellular Roaming are recognized. (Protocols: ITU, China)

  • unSupported (default)
  • supported

cfn

N/A

Indicates if Confusion (CFN) message is supported for the ISUP Signaling profile. CFN is sent in response to any message (other than a confusion message) if the node does not recognize the message or part of the message is unrecognized.

  • unSupported (default)
  • supported

chargeArea

N/A

Use this Service Control to populate the Charge Area with a valid 5-digit Charge Area code. The Charge Area is set in the ACM or CPG message if a script is returned from the ERE, or for Disconnect treatment for SIP MIME case.

chargeIndSetting

N/A

Use this flag to set the BCI charge indicator to charge or no charge, transit whatever is received, or simply to nothing at all (in the case of ISDN where it defaults to "0").

  • charge
  • noCharge
  • noIndication
  • transit – (default) Transit whatever is received from the sending side (egress of network).

chargeMsgInSpeech

N/A

Indicates if the Charge Message In Speech parameter is supported for the ISUP Signaling profile.

  • unsupported (default)
  • supported

chargeNumber

N/A

Indicates if the Charge Number parameter is supported for the ISUP Signaling profile.

  • unsupported (default)
  • supported

checkIxcAgainstTlec

N/A

Set flag to "supported" to allow the SBC to compare the IXC code configured on policy server with the TLEC carrier code added by the terminating exchange. If they are the same, SBC will not add in duplicate information.
Set flag to "unsupported" to allow SBC to add in IXC data with the same carrier code as the TLEC information. (Protocol: Japan)

  • unsupported (default)
  • supported

chgBetweenAcmAndAnm

N/A

When set to "supported", the SBC sends the CHG message in the backward direction between an ACM and ANM. (Protocol: Japan)

  • unsupported (default)
  • supported

chgMsgBeforeAcm

N/A

When set to "supported", the SBC transits the CHG message in the backward direction before ACM is received. (Protocol: Japan)

  • unsupported (default)
  • supported

ci

N/A

Specifies if CI6 is supported in the ISUP Signaling profile.

  • unsupported (default)
  • supported

circuitAssignmentMap

N/A

Specifies if circuit assignment map parameter is supported for the ISUP Signaling profile.

  • unsupported (default)
  • supported

citTermExchangeLogic

N/A

Use this control to specify whether to include CIT/CAI information in first or all backward (ACM/CPG) messages.

  • unsupported – (default) CIT/CAI information is added to all backward ACM/CPG messages supporting them.
  • supported – Only the first backward message contains CIT/CAI information.

collectCallReq

N/A

Specifies if the collect call request parameter is supported for the ISUP Signaling profile.

  • unsupported (default)
  • supported

colpColrIgw

N/A

Use this parameter to enable/disable support COLP-COLR and IGW functionality. The supported protocols are ITU/ANSI.
COLP = Connected Line id Presentation
COLR = Connected Line id Restriction
IGW = ISUP Gateway

  • unsupported (default)
  • supported

com

N/A

Specifies if COM message is supported for the ISUP Signaling profile.

  • unsupported (default)
  • supported

compatibility

N/A

Specifies if compatibility is supported for the ISUP Signaling profile.

  • unsupported (default)
  • supported

con

N/A

Specifies if CON message is supported before an ACM is transited.

  • unsupported
  • supported (default)

conferenceTreatment

N/A

Specifies if the conference treatment parameter is supported for the ISUP Signaling profile.

  • unsupported (default)
  • supported

conferenceTreatmentInAnm

N/A

Specifies whether the Conference Treatment parameter in the ANM is supported for the ISUP Signaling profile.

  • unsupported (default)
  • supported

connectedNumber

N/A

Specifies if the connected number is supported for the ISUP signaling profile.

  • unsupported
  • supported (default)

connectedNumberInAcm

N/A

Specifies if the connected number parameter is supported in the ACM for the ISUP Signaling profile.

  • unsupported (default)
  • supported

connectedNumberInCpg

N/A

Specifies if the connected number parameter is supported in the CPG for the ISUP Signaling profile.

  • unsupported (default)
  • supported

connectionPointTrunkType

N/A

Specifies if the Connection Point Trunk Type is supported for the ISUP Signaling profile.

  • unsupported (default)
  • supported

connectionReq

N/A

Specifies whether the Connection Request parameter is supported for the ISUP Signaling profile.

  • unsupported (default)
  • supported

connectionReqInFaa

N/A

Specifies if connection request parameter is supported in the FAA for the ISUP Signaling profile.

  • unsupported (default)
  • supported

connectionReqInFar

N/A

Specifies if connection request parameter is supported in the FAR for the ISUP Signaling profile.

  • unsupported (default)
  • supported

connectionReqInIam

N/A

Specifies if connection request parameter is supported in the IAM for the ISUP Signaling profile.

  • unsupported
  • supported (default)

connectionReqInInf

N/A

Specifies if connection request is supported in the INF for the ISUP Signaling profile.

  • unsupported (default)
  • supported

continuity

N/A

Specifies if the Continuity procedures are supported for the ISUP Signaling profile.

  • unsupported
  • supported (default)

correlationId

N/A

Specifies if correlation ID parameter supported for the ISUP Signaling profile.

  • unsupported (default)
  • supported

cpgBeforeAcm

N/A

Specifies if CPG arriving before an ACM is transited.

  • unsupported (default)
  • supported

cpnRel

N/A

Specifies if the CPN is supported in the REL for the ISUP Signaling profile.

  • unsupported (default)
  • supported

cqmCqr

N/A

Specifies if the CQM/CQR is supported for the ISUP Signaling profile.

  • unsupported (default)
  • supported

cqmForResync

N/A

Specifies if a Cqm PDU is sent to resync when transitioning from Mtp Pause to Resume state.

  • unsupported (default)
  • supported

cqmOnCardSwap

N/A

Specifies if CQM on Card Swap operation is supported in the ISUP Signaling profile.

  • unsupported (default)
  • supported

cugInterlockCode

N/A

Indicates if the Closed User Group Interlock Code is supported for the ISUP signaling profile.

  • unsupported
  • supported (default)

cvtCvr

N/A

Specifies if Circuit Validation Test/Response procedures are supported for the ISUP Signaling profile.

  • unsupported (default)
  • supported

deleteIxcTcCode

N/A

Delete the IXC/TC code in the CIT for SIP MIME case. (up to 4 characters)

diagnostics

N/A

Indicates if Diagnostics field is supported for the ISUP signaling profile.

  • unsupported
  • supported (default)

dialedNumber

N/A

Indicates if the Dialed Number parameter is supported for the ISUP Signaling profile.

  • unsupported (default)
  • supported

discardContractorNum

N/A

When set to "supported", the SBC discards Contractor number parameter in the IAM (SBB-specific) message. (Protocol: Japan)

  • unsupported (default)
  • supported

displayInfoInAcm

N/A

Indicates if the Display Information parameter in the ACM is supported for the ISUP Signaling profile.

  • unsupported (default)
  • supported

displayInfoInCon

N/A

Indicates if the Display Information parameter in the CON is supported for the ISUP Signaling profile.

  • unsupported (default)
  • supported

displayInfoInCpg

N/A

Indicates if Display Information parameter in the CPG is supported for the ISUP Signaling profile.

  • unsupported (default)
  • supported

displayInfoInIam

N/A

Indicates if the display Information parameter in the IAM is supported for the ISUP Signaling profile.

  • unsupported (default)
  • supported

displayInformation

N/A

Indicates if the display information parameter is supported for the ISUP Signaling profile.

  • unsupported (default)
  • supported

dmsFe

N/A

Indicates if DMS FE field should be supported for the ISUP Signaling profile.

  • unsupported (default)
  • supported

dontClearCdrFields

N/A

Set flag to "supported" to not clear Called Charge Area and/or Charging Rate when Charge Information Delay parameter is received in ACM or CPG. (Protocol: Japan)

  • unsupported (default)
  • supported

dontGenerateDiags

N/A

Set flag to "supported" to not generate diagnostics for JAPAN.

  • unsupported (default)
  • supported

dontMapToHeaderToOcn

N/A

Set flag to "supported" to not interwork the To header field to ISUP original called number when interworking between SIP and ISUP.

  • unsupported (default)
  • supported

dontSendExm

N/A

Set flag to "supported" to not send EXM messages on a trunk group.

  • unsupported (default)
  • supported

dpc

N/A

If flag is set to "supported", DPC parameters are decoded and transited. (Protocol: Japan)

  • unsupported (default)
  • supported

dpcInformation

N/A

If set to "supported", the SBC generates/transits or discards the DPC information parameter in the IAM. (Protocol: Japan)

  • unsupported (default)
  • supported

dropAPPinIAM

N/A

Use this parameter to drop the APP with context ID = 0x3FFF in IAM for ANSI.

  • unsupported (default)
  • supported

dropCauseInAcmWhenIwk

N/A

Specifies if the CAUSE parameter in ACM is suppressed when announcement is played after interworking.

  • unsupported (default)
  • supported

dropUsiFromNonIsup

N/A

Specifies if the USI parameter is supported when the far-side is not ISUP.

  • unsupported (default)
  • supported

drs

N/A

Specifies if DRS is supported in the ISUP Signaling Profile.

  • unsupported (default)
  • supported

eMcid

N/A

Specifies if MCID is supported for the ISUP Signaling Profile.

  • unsupported (default)
  • supported

earlyAcmChgNoInd

N/A

Specifies if Charge Indication in Early ACM is always set to 'No Indication'. (Protocols: all)

  • unsupported (default)
  • supported

echoControl

N/A

Specifies if Echo Control parameter is supported for the ISUP Signaling Profile.

  • unsupported (default)
  • supported

echoControlInIam

N/A

Secifies if Echo Control parameter supported in IAM for the ISUP Signaling Profile.

  • unsupported (default)
  • supported

eci

N/A

Specifies if the Japan Emergency Indicator parameter is supported for the ISUP Signaling Profile.

  • unsupported (default)
  • supported

eciTrap

N/A

If ECI is received in the IAM, call is marked as an emergency call and a trap is generated. (Protocol: Japan)

  • unsupported (default)
  • supported

egressService

N/A

Specifies if Egress Service parameter is supported for the ISUP Signaling Profile.

  • unsupported (default)
  • supported

eit

N/A

Specifies if EIT is supported for the ISUP Signaling Profile.

  • unsupported (default)
  • supported

emergencyCallInf

N/A

Specifies if Emergency Call Information parameter is supported in the CPG.

  • unsupported (default)
  • supported

fac

N/A

Specifies if FAC is supported for the ISUP Signaling Profile.

  • unsupported (default)
  • supported

facility

N/A

Specifies if FAA, FAR and FRJ are supported for the ISUP Signaling Profile.

  • unsupported (default)
  • supported

fallback

N/A

Specifies if Fallback is supported for ISUP Signaling Profile.

  • unsupported (default)
  • supported

fciUserPartChosenCarrier

N/A

Set flag to "supported" to overwrite FCI ISDN User Part indicator based on the Chosen Carrier.

  • unsupported (default)
  • supported

fciUserPartIwk

N/A

Set flag to "supported" to overwrite FCI ISDN User Part indicator for NON-ISUP to ISUP calls.

  • unsupported (default)
  • supported

fciUserPartTrans

N/A

Set flag to "supported" to overwrite FCI ISDN User Part indicator for ISUP to ISUP calls.

  • unsupported (default)
  • supported

forceEchoCntrl

N/A

Set flag to "supported" to force echo cancellation on calls regardless of information contained in signalling messages (with the exception of data calls).

  • unsupported (default)
  • supported

forceEchoCntrlNoUpdate

N/A

When flag is set to "supported", Echo Cancelling is enabled, but ECI bit is not updated.
When set to "unsupported", Echo Cancelling is enabled dependent upon ECI bit. (Protocol: all)

  • unsupported (default)
  • supported

forwardCallProgress

N/A

Set flag to "supported" to specify that Call Progress (CPG) message is supported in the forward direction.

  • unsupported (default)
  • supported

forwardGvns

N/A

Specifies if forward GVNS parameter is supported for the ISUP Signaling Profile.

  • unsupported (default)
  • supported

forwardNetworkSpecificInfo

N/A

Specifies if Forward Network Specific Information parameter is supported for the ISUP Signaling Profile.

  • unsupported (default)
  • supported

forwardSuspend

N/A

Specifies if Suspend (SUS) message is supported in the forwards direction.

  • unsupported
  • supported (default)

forwardTransferMessage

N/A

Specifies if Forward Transfer Message is supported for the ISUP Signaling Profile.

  • unsupported
  • supported (default)

freePhoneInd

N/A

Specifies if Freephone Indicators parameter is supported for this ISUP Signalling Profile.

  • unsupported (default)
  • supported

generateJapanIcsParams

N/A

Specifies whether to support generating ICS information in SIP MIME case for the signalling group.

  • unsupported (default)
  • supported

genericAddressRel

N/A

Specifies if Generic Address parameter is supported in the REL message for the ISUP Signaling Profile.

  • unsupported (default)
  • supported

genericDigits

N/A

Specifies if Generic Digits parameter supported for the ISUP Signaling Profile.

  • unsupported (default)
  • supported

genericName

N/A

Specifies if Generic Name parameter is supported for the ISUP Signaling Profile.

  • unsupported (default)
  • supported

genericNotification

N/A

Specifies if Generic Notification parameter is supported for the ISUP Signaling Profile.

  • unsupported (default)
  • supported

genericNotificationInFac

N/A

Specifies if Generic Notification parameter is supported for the ISUP Signaling Profile.

  • unsupported (default)
  • supported

genericNotificationRepeatable

N/A

Specifies if Generic Notification Repeatable parameter is supported for the ISUP Signaling Profile.

  • unsupported (default)
  • supported

genericNumInAcm

N/A

Specifies if Generic Number parameter in the ACM is supported for the ISUP Signaling Profile.

  • unsupported (default)
  • supported

genericNumInFac

N/A

Specifies if Generic Number parameter in the FAC is supported for the ISUP Signaling Profile.

  • unsupported (default)
  • supported

genericNumInInf

N/A

Specifies if Generic Number parameter in the INF is supported for the ISUP Signaling Profile.

  • unsupported (default)
  • supported

genericNumber

N/A

Specifies if Generic Number parameter is supported for the ISUP Signaling Profile.

  • unsupported (default)
  • supported

genericNumberInCpg

N/A

Specifies if Generic Number parameter in the CPG is supported for the ISUP Signaling Profile.

  • unsupported (default)
  • supported

genericNumberRepeatable

N/A

Specifies if generic number is a repeatable parameter.

  • unsupported (default)
  • supported

genericNumberRepeatableIam

N/A

Specifies if generic number is a repeatable parameter in IAM.

  • unsupported (default)
  • supported

genericOperation

N/A

Specifies if Generic Operation parameter is supported for the ISUP Signaling Profile.

  • unsupported (default)
  • supported

genericReference

N/A

Specifies if Generic Reference parameter is supported for the ISUP Signaling Profile.

  • unsupported (default)
  • supported

gi

N/A

Specifies if GI is supported for the ISUP Signaling Profile.

  • unsupported (default)
  • supported

gr317ChargeNumberCompliance

N/A

Use this flag to check the charge number digit length is in compliance with GR317 which specifies a maximum of 10 digits in IAM message. The gr317ChargeNumberCompliance flag does not affect the charge number header contents in SIP messages. When the egress trunk group has the isupMimeBodyRelay flag enabled, any charge number parameter received in the ingress ISUP MIME is sent in the egress ISUP MIME irrespective of the value of gr317ChargeNumberCompliance setting.

  • unSupported – SBC does not check charge number digit length for GR317 compliance.
  • supported – SBC checks charge number digit length for GR317 compliance, and does not send message if digit length is greater than 10 digits. If digit length is 11 or more digits, the charge number parameter is discarded and a MINOR log message is logged to the debug log.

This flag can only be set to “supported” for ANSI ISUP variant. Additionally, the gr317ChargeNumberCompliance check only applies to the ISUP MIME sent by SBC; it does not apply to the ISUP MIME received by SBC.

gr317ScreeningInd

N/A

When set to "supported", this flag turns on various screening indicators for GR317 parameter compliancy.

  • unsupported (default)
  • supported

groupRedirectionCount

N/A

Specifies if Group Redirection Count parameter is supported for the ISUP Signaling Profile.

  • unsupported (default)
  • supported

hardToReachInd

N/A

Set flag to "supported" to enable the Hard To Reach Indicator automatic congestion control parameter for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

holdingInd

N/A

When set to "supported', the sending of a holding request is supported.

  • supported (default)
  • unSupported

hopCountState

N/A

When set to "supported" the Hop Counter feature is supported for the Signaling Group.

  • supported (default)
  • unSupported

When hopCountState is enabled, the following applies:

  • If a Hop Counter parameter is received from the ingress leg of the call, it is decremented and included in the outgoing IAM message. If no Hop Counter is present in the ingress leg of the call, it is included in the outgoing IAM message using Hop Count Value.
  • If a Hop Counter of zero is present in the ingress leg of the call, the call is released with a cause of "exchange routing error".

When hopCountState is disabled, the following applies:

  • If a Hop Counter parameter is received from the ingress leg of the call, it is passed transparently in the outgoing IAM message.
  • If a Hop Counter of value zero is present in the ingress leg of the call, the call is released with a cause of "exchange routing error".

hopCountValue

10-32

The Hop Counter value is used to set the maximum forward header value, and is used to prevents a loop from happening when call is made between the PSTN and SIP domain. (default = 10).

hopCounter

N/A

When set to "supported" the Hop Counter feature is supported for the ISUP Signaling Profile.

  • supported (default)
  • unSupported

iamGeneratedCarrierCodeInCdr

N/A

Set to "unsupported" to always populate the IAM-Generated Carrier Code in the CDR for Japan regardless of type.

  • supported
  • unSupported (default)

iepsCpc

N/A

Set flag to "supported" to allow recognition of Calling Party Category value IEPS. (Protocols: ITU, China).

  • supported
  • unSupported (default)

incomingTrunkIdCode

N/A

Use this flag to support/not support Incoming Trunk Identity Code parameter for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

informationInd

N/A

Use this flag to support/not support Information Indicator parameter for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

inrInAllStates

N/A

Use this flag to support/not support INR and INF messages in all states for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

inrInf

N/A

Use this flag to support/not support INR/INF for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

invTnsRelease

N/A

Set this flag to "supported" to apply the Q931 Release handling for invalid TNS.

  • supported
  • unSupported (default)

iriOri

N/A

Use this flag to support/not support IRI/ORI for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

iriOriRcv

N/A

Use this flag to support/not support the reception of IRI/ORI for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

iriOriSent

N/A

Use this flag to support/not support sending IRI/ORI messages for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

isubTypeFromSip

N/A

Use this flag to specify the ISUP type supported. (Protocol: Japan).

  • both – NSAP and User-Specific ISUB from SIP supported.
  • none – No ISUB types from SIP supported.
  • nsap – (default) Only ISUB of type NSAP from SIP supported.
  • userspec – only ISUB of type User-Specific from SIP supported.

ituCai24

N/A

Use this flag to specify if ITU Cause Value 24 "Call Rejected due to Feature at Destination" is supported or rejected (unsupported).
SUPPORTED - ITU Cause Value 24 is recognized. (Protocols: ITU, China).

  • supported – ITU Cause Value 24 is recognized.
  • unSupported – (default) ITU Cause Value 24 is rejected.

itxTxa

N/A

Are the ITX and TXA messages supported for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

iui

N/A

Use this flag to specify if IUI6 is supported in the ISUP Signaling Profile.

  • supported
  • unSupported (default)

jti

N/A

Use this flag to support/not support the JT-specific ISUP Parameter in the ISUP Signaling Profile.

  • supported
  • unSupported (default)

jurisdiction

N/A

Use this flag to support/not support the Jurisdiction parameter for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

ldli

N/A

Use this flag to support/not support the Last Diverted Line Identity parameter for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

locationNumber

N/A

Use this flag to support/not support the Location Number parameter for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

locationOfRel

N/A

Use parameter to specify the REL cause location for SIP MIME case.

  • internationalNet
  • natReserved6
  • natReserved8
  • natReserved9
  • natReserved11
  • natReserved12
  • natReserved13
  • natReserved14
  • natReserved15
  • netBeyondInterPoint
  • notUsed (default)
  • privateLocal
  • privateRemote
  • publicLocal
  • publicRemote
  • transitNet
  • user

locationOfRel34

N/A

Use this flag to specify the REL cause 34 location for SIP MIME case. (default is "notUsed")
(see locationOfRel description for list of options)

locationOfRel42

N/A

Use this flag to specify the REL cause 42 location for SIP MIME case. (default is "notUsed")
(see locationOfRel description for list of options)

lookAheadForBusy

N/A

Use this parameter to allow, not allow or reserve path for the default value in the Look Ahead For Busy field of the ISUP Precedence parameter within SIP-T.

  • allowed
  • notAllowed (default)
  • pathReserved

loopPrevention

N/A

Use this flag to support/not support the loop prevention indicators parameter for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

lpa

N/A

Use flag to support/not support Loop Back Acknowledgement (LPA) requests for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

maRel

N/A

Use this flag to specify if MA6 is supported in the REL message for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

mapDmsFeParameter

N/A

Use flag to support mapping service group to the Completion Code in the DMS FE parameter (ANSI ISUP only).

  • supported
  • unSupported (default)

maxCalledPartyDigits

N/A

The maximum digit string length for the Called Party Number parameter supported for this ISUP Signaling Profile. (range: 1-30 / default = 30).

maxCallingPartyDigits

N/A

The maximum digit string length for the Calling Party Number parameter supported for this ISUP Signaling Profile.(range: 1-30 / default = 30).

mi

N/A

Use this flag to specify if MI6 is supported in the ISUP Signaling Profile.

  • supported
  • unSupported (default)

mlpp

N/A

Use this flag to specify if MLPP parameter is supported for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

msi

N/A

Use this flag to specify if MSI6 is supported in the ISUP Signaling Profile.

  • supported
  • unSupported (default)

multiCarrierEnvironment

N/A

Use this flag to specify if the Multi-Carrier Environment parameter is supported for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

ncr

N/A

Use this flag to specify if the Network Call Reference (NCR) Parameter is supported for ISUP Signaling Profile.

  • supported
  • unSupported (default)

networkData

N/A

Use this flag to specify if Network Data is supported in the IAM message. (Protocols: ANIS, ITU).

  • supported
  • unSupported (default)

networkIdentity

N/A

The default value used for 4-digit Network Identity field in the ISUP precedence parameter within SIP-T. (default = 0000).

networkIndicator

N/A

The setting of the Network Indicator as it would be for ISUP if the SIP-T link were an ISUP link (to prevent unnecessary interworking - not really applicable to SIP-T).

  • int10
  • int11
  • nat10 (default)
  • nat11

networkManagement

N/A

Use this flag to specify if Network Management Controls parameter is supported for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

networkManagementInfo

N/A

Use flag to specify if the Network Management Information parameter is supported for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

networkSwitchNumber

N/A

Use this flag to specify if the Network Switch Number parameter is supported for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

networkTransport

N/A

Use this flag to specify if the Network Transport is supported for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

nfci

N/A

Use this flag to specify if the National Forward Call Indicators parameter is supported for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

nfciLblRciProc

N/A

Use this flag to specify if the National Forward Call Indicators Link-by-Link parameter procedure is supported for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

nfciLnk

N/A

Use this flag to specify if National Forward Call Indicators Link-by-Link parameter is supported for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

nft

N/A

Use this flag to specify if the NFT is supported for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

nii

N/A

Use this flag to specify if the National Information Indicators parameter is supported for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

niri

N/A

Use this flag to specify if the National Information Request Indicators parameter is supported for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

noAcmObciForSipApn

N/A

Set this flag to "supported" to prevent the SBC from including 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. (Protocol: Generic).

  • supported
  • unSupported (default)

noChgCountIfFlexChgRate

N/A

Set flag to "supported" to specify that CHG count is not incremented if there is Flexible Charge Rate. (Protocol: Japan).

  • supported
  • unSupported (default)

noInNumberUpdates

N/A

Set flag to "supported" to prevent from updating the called IN and original called IN number parameters used in Japan based on the new called party number parameter w hen the PSX performs a TOLL FREE number translation.

  • supported
  • unSupported (default)

noIpEchoInd

N/A

Use this flag to specify if the Echo Control indication is set for an IP to PSTN call.

  • supported
  • unSupported (default)

noObciSipAcm

N/A

Set flag to "supported" for SBC to not include the Optional Backward Call Indicator (OBCI) parameter in the Address Complete Message (ACM) in all the existing scenarios. (Protocol: Generic)

  • supported
  • unSupported (default)

This flag only applies when interworking from SIP-I to SIP when the SBC is acting as a terminating exchange.

notificationInd

N/A

Use this flag to specify that the Notification Indicator parameter is supported for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

npfi

N/A

Use this flag to support the Number Portability Forward Information parameter. (Protocols: ITU, China).

  • supported
  • unSupported (default)

nrmSupport

N/A

Use this flag to support NRM for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

nrop

N/A

Use this flag to support NROP6 in the ISUP Signaling Profile.

  • supported
  • unSupported (default)

nsa

N/A

Use this flag to support the Network Specific ANM parameter in the ANM.

  • supported
  • unSupported (default)

nsf

N/A

Use this flag to support the NSF parameter for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

obciAnm

N/A

Use this flag to support OBCI parameter in the ANM for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

olipCheck

N/A

Use this flag to support checking for presence of an OLIP when determining that a call is invalid.

  • supported
  • unSupported (default)

olipCheckOnSend

N/A

This flag specifies whether to check for presence of an OLIP when sending an IAM.

  • supported
  • unSupported (default)

olm

N/A

Use this flag to support OLM for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

onlyCpgInBandBeforeAcm

N/A

Set this flag to "supported" to either transit a CPG containing an in-band information event arriving before an ACM or discard CPG when in-band information event is not present.

  • supported
  • unSupported (default)

onlyScreenCitGen

N/A

Use this flag to specify whether to generate screen sub-parameters in CIT (Protocol: Japan)

  • supported – Generate screen sub-parameters in CIT.
  • unSupported – (default) Generate sub-parameters in CIT without restrictions.

onlySendAcmFor181

N/A

(ISUP-to-SIP call only) If flag is set to "supported", an ACM message is only sent if a 181 is received. If an ACM has already been sent, the 181 is mapped to a CPG.

  • supported
  • unSupported (default)

operatorSelection

N/A

Use this flag to support the Operator Selection parameter.

  • supported
  • unSupported (default)

operatorServiceInfo

N/A

Use this flag to support Operator Service Information parameter for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

opr

N/A

Use this flag to support Operator (OPR) message.

  • supported
  • unSupported (default)

optionalFci

N/A

This flag specifies whether the Optional Forward Call Indicators is supported for the ISUP Signaling Profile.

  • supported (default)
  • unSupported

originalCalledNumber

N/A

This flag specifies whether the Original Called Number parameter is supported for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

originatingIscPointCode

N/A

This flag specifies whether the originating ISC point code parameter is supported for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

otgnAnsi92

N/A

This flag specifies whether the OTGN Parameter (up to 5 octets) is supported in the EXM message.

  • supported
  • unSupported (default)

otherDigitStringSpecialDigitF

N/A

This flag specifies whether the Special Digit F is supported in digit strings other than the Called Party.

  • supported
  • unSupported (default)

overrideInBand

N/A

Set flag to "supported" to ignore Inband indicator in OBCI or Event Indicator in CPG message unless Interworking Indicator is set for BCI. (Protocols: all)

  • supported
  • unSupported (default)

pam

N/A

This flag specifies whether PAM is supported for ISUP Signaling Profile.

  • supported
  • unSupported (default)

pciPassOnDefault

N/A

Use flag to specify whether to support necessary information exchange when receiving an unrecognized PCI Pass On Not Possible value in the ISUP Signaling Profile.

  • supported
  • unSupported (default)

pcli

N/A

This flag specifies whether Partial Calling Line Identity parameter is supported for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

presentationNumber

N/A

This flag specifies whether the Presentation Number parameter is supported for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

preventAcmToCpgMapping

N/A

If an ACM is sent on the ingress trunk group due to a script and T11 timer expires (or some other event), if an ACM is received on the egress trunk group it is usually converted into a CPG message on the ingress trunk group.
Set this control to "supported" to prevent ACM-to-CPG mapping and silently discard the received ACM on the ingress side.

  • supported
  • unSupported (default)

propagationDelay

0-400

The propagation delay value (in milliseconds) for this SIP-T signaling group. (default = 0)

propagationDelaySupport

N/A

This control specifies whether propagation delay is supported for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

qor

N/A

Use this flag to specify whether the Query on Release parameter is supported. (Protocols: ITU, China)

  • supported
  • unSupported (default)

reaffirmBlockAfterReset

N/A

If set to "supported", when RSC or GRS is sent on a locally- blocked circuit, BLO is also sent to reaffirm the blocking.

  • supported
  • unSupported (default)

recommendationInCai

N/A

Use flag to specify whether Recommendation field is supported in the cause parameter for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

redirectingNumber

N/A

Use flag to specify whether the Redirecting Number parameter is supported for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

redirectionCap

N/A

Use flag to specify whether Redirection Capability parameter is supported for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

redirectionInfoAcm

N/A

Use flag to specify whether the Redirection Information parameter is supported in the ACM message for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

redirectionInfoIam

N/A

Use flag to specify whether the Redirection Information parameter is supported within the IAM message foe the ISUP Signaling Profile.

  • supported
  • unSupported (default)

redirectionNumRestrictionInRel

N/A

Use this flag to specify whether to support Redirection Number Restriction Parameter in the REL message. (Protocols: ITU, China).

  • supported
  • unSupported (default)

redirectionNumber

N/A

Use this flag to specify whether to support Redirection Number parameter for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

redirectionNumberInAcm

N/A

Use this flag to specify whether the redirection number is supported in the ACM for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

redirectionNumberInAnm

N/A

Use this flag to specify whether the redirection number is supported in the ANM for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

redirectionNumberRestriction

N/A

Use this flag to specify whether the redirection number restriction parameter is supported for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

relForDuplicateIam

N/A

Use this flag to specify which message to send when a misplaced call is detected. (Protocols: all)

  • supported – Send a REL with CV=31 to clear the circuit.
  • unSupported – (default) Send an RSC to clear the circuit.

relForEarlyAnm

N/A

Use this control to specify action to take if an ANM is received before a backward message (Protocols: ITU, Japan, China).

  • supported – Send REL cause 31 in both directions.
  • unSupported – (default) Reattempt the call.

releaseLinkTrunking

N/A

Use this control to specify whether the Release Link Trunking (RLT) Service is supported.

  • supported
  • unSupported (default)

remoteMnpDip

N/A

Use this control to specify whether Remote MNP Dipping service is supported.

  • supported
  • unSupported (default)

remoteOperationInRel

N/A

Use this control to specify whether Remote Operations parameter is supported in the REL for ISUP Signaling Profile.

  • supported
  • unSupported (default)

remoteOperations

N/A

Use this control to specify whether Remote Operations parameter is supported for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

removeHlcIfNoLlc

N/A

Set control to "supported" to remove HLC if LLC is not present. (Protocols: all).

  • supported
  • unSupported (default)

revision

N/A

Select the ISUP protocol revision supported on this Signaling Group. (default is "ituq767").
ansi1992 | ansi1995 | ansiatt | argentina | argent | inaidt | belgacom | brazil | chile | chinacnc | denmarkic | etsi2 | etsi2plus | etsi3 | hongkongic | india | israel | italy | itu1988 | itu1993 | itu1997 | |ituq767 | korea | mexicoic | nttcom | nttfcc | peru | portugaloni | russia | singapore | slovak2 | spain | spirou | ukisup

rlcAcknowledgeGrs

N/A

Use this control to specify whether to support acknowledging a GRS with an RLC message.

  • supported
  • unSupported (default)

routeInformation

N/A

Set this control to "supported" to allow SBC to process the Route Information parameter received in the IAM message, and enable KGL-specific routing. (Protocol: ITU)

  • supported
  • unSupported (default)

routingInfoInd

N/A

Use this control to specify whether the Routing Information Indicator parameter is supported for ISUP Signaling Profile.

  • supported
  • unSupported (default)

rr

N/A

Use this control to specify whether the RR6 is supported in the ISUP Signaling Profile.

  • supported
  • unSupported (default)

russiaRng

N/A

Use this control to specify whether the Russia RNG message is supported. (Protocol: Russia)

  • supported
  • unSupported (default)

saveIamCit

N/A

Use this control to specify whether or not to save CIT information (Protocol: Japan).

  • supported – CIT information in the IAM will not be overwritten by backwards information.
  • unSupported – (default) Existing functionality and IAM CIT can be overwritten.

sccpProcedure

N/A

Use this control to specify if SCCP procedure is supported for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

scfId

N/A

Use this control to specify if the SCF ID parameter is supported for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

screenCitBeforeCdr

N/A

Use this control to specify action to take against CIT before applying to CDR. (Protocol: Japan)

  • supported – SBC screens out any carrier information transfer data that will not be sent in the signaling message and stores this information in the CDR.
  • unSupported – (default) SBC adds all the carrier information transfer parameter data to the CDR and screens out any unneeded data before generating the signaling message.

sdnIncrement

N/A

Use this control to specify whether to support the SDN SID/ANI Increment Message for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

segmentation

N/A

Use this control to specify whether to support segmentation for the ISUP Signaling Profile.

  • supported
  • unSupported (default)
sendAPPinAPMforCBWF N/A Use this flag to send CBWF-related APP (ACI=126) in a new APM message. If set to "unsupported" , APP is sent in the regular signaling message (e.g. ACM instead of APM). See Call Back When Free Support for feature details.
  • supported
  • unSupported (default)

The flag sendAPPinAPMforCBWF applies to SIP-I (UK-ISUP variant) only.

sendBloOnHwBlock

N/A

Set to "supported" to send BLO when a circuit is hardware blocked.

  • supported
  • unSupported (default)

sendPRIonRELforCBWF

N/A

Use this flag to send either APM or PRI message with Call Back When Free (CBWF) information on the SIP-I (UK-ISUP) leg during tear down of CBWF call. See Call Back When Free Support for feature details.

  • supported – Send PRI message
  • unSupported (default) – Send APM message

 

The flag sendPRIonRELforCBWF applies to SIP-I (UK-ISUP variant) only.


sendRscForCallsOnHwBlock

N/A

Use this flag to send RSC when a call is impacted by a circuit hardware blockage.

  • supported
  • unSupported (default)

sendTwoGroupMsgs

N/A

Use this flag to send two group messages in the ISUP Signaling Profile.

  • supported
  • unSupported (default)

sendingEnbloc

N/A

Set this flag to allow the trunk group to only send enbloc (Protocols: ITU, China).

  • supported – Trunk group will only send enbloc.
  • unSupported – (default) Trunk group can send overlap and enbloc.

serviceActivation

N/A

Set this flag to support the service activation parameter for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

serviceActivationInRel

N/A

Set this flag to support the Service Activation Parameter in the REL message.

  • supported
  • unSupported (default)

serviceCodeInd

N/A

Set this flag to support Service Code Indicator parameter for the ISUP Signaling Profile.

  • supported
  • unSupported (default)
setBciCdpsBasedOnSipCallStatus N/A

Set this flag to "supported" to modify the called party's status indicator in BCI parameter of MIME data as per the SIP status. If 183 Session Progress is carrying a MIME of called party's status indicator in BCI with a value OTHER THAN "No indication", then it is updated to a value "No indication". Similarly, if 180 Ringing is carrying a MIME of called party's status indicator in BCI with a value OTHER THAN "Subscriber Free", then it is updated to a value "Subscriber Free".

  • supported
  • unSupported (default)

sgmPci

N/A

Set this flag to support the PCI parameter in the SGM for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

signalOnlySipAlert

N/A

Set this control to only allow generation of ACM/CPG message during an ISUP-to-SIP call in response to an 180 message.

  • supported
  • unSupported (default)

signalingPointCode

N/A

Set this control to support the signaling point code parameter for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

simpleEcBciInAllBkMsg

N/A

Set this control to support simple echo control whereby every backward message is examined for the BCI echo control indication field, and then appropriate action is taken.

  • supported
  • unSupported (default)

sliInIam

N/A

Set this control to support the Supplementary Line Info parameter in the IAM.

  • supported
  • unSupported (default)

slovakChargeMessage

N/A

Use this flag to support the Slovak charge message. (Protocol: Slovak)

  • supported
  • unSupported (default)

spc6

N/A

Use this flag to support SPC6 in the ISUP Signaling Profile.

  • supported
  • unSupported (default)

spcInIrs

N/A

Use this flag to support the SPC parameter with the IRS message for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

specialDigits

N/A

Use this control identify which special digits can appear in dialed digit strings (select all that apply).

  • digitA – BIT 0
  • digitB – BIT 1 (default)
  • digitC – BIT 2 (default)
  • digitD – BIT 3
  • digitE – BIT 4
  • digitF – BIT 5 (default)
  • none – BIT 6

specialProcessReq

N/A

Use this flag to support the Special Processing Request parameter for the ISUP Signaling Profile.

  • supported
  • unSupported (default)
storeChargeForIscTcTypeAndPayPhone


N/A

Use this control to specify which Charge Information is stored in CDR. (Protocol: Japan)

  • supported – The First Charge Information is stored in the CDR Records.
  • unSupported – (default) The Last Charge Information is stored in the CDR Records.

subscriberPriorityClass

N/A

Set this flag to support the subscriber priority class parameter for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

subsequentAddressMessage

N/A

Set this flag to support the Subsequent Address Message for the ISUP Signaling Profile.

  • supported (default)
  • unSupported

suppressCitForPreSubAcm

N/A

Set this flag to ensure the Carrier Information Transfer parameter is suppressed in Early ACM for Pre-Subscription call.

  • supported
  • unSupported (default)

t7Transit

N/A

Set flag to run the T7 Timer for a Transit Call in the ISUP Signaling Profile.

  • supported
  • unSupported (default)

t11Active

N/A

Set flag to specify that ISUP T11 timing is active at interworking exchanges for Signaling Profile.

  • supported
  • unSupported (default)

t11EarlyAcm

N/A

Set flag to enable ISUP T11 Early ACM guard timer for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

tandemCallCounter

N/A

Set this flag to allow SBC to decode/encode, increment and transit the Tandem Call Counter parameter received in IAM message. (Protocol: Japan)

  • supported
  • unSupported (default)

tandemLimitCounter

0-15

Specify value of Limit Counter set in outgoing IAM in Tandem Call Counter parameter in SIP MIME case. (default = 0)

tci

N/A

Specify if TCI is supported for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

tit

N/A

Set flag to support the TIT parameter for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

tmrPrime

N/A

Set flag to support TMR prime parameter for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

transMedUsedInNrm

N/A

Set flag to support TMU parameter within the NRM Message for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

transactionReq

N/A

Set flag to support Transaction Request parameter for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

transferInfo

N/A

Set flag to decode and transit Transfer Info parameters. (Protocol: Japan)

  • supported
  • unSupported (default)

transitCfn

N/A

Set flag to transit the CFN message to the other leg for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

transitNetworkSelection

N/A

Set flag to support the Transit Network Selection parameter for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

transitReceivedCit

N/A

Use this flag to specify whether to modify received CIT parameter. (Protocol: Japan)

  • supported – Transit the received CIT parameter as-is.
  • unSupported – (default) Modify received CIT parameter as usual.

transitUnrecognized

N/A

Use this flag to support transiting unrecognized parameters for the ISUP service Group.

  • supported
  • unSupported (default)

transmissionMediumUsed

N/A

Set flag to support the Transmission Medium Used parameter for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

truncateCdpn

N/A

Use this flag to specify whether to truncate or release the call if the CDPN is greater than the MaxCalledPartyDigits.

  • supported – Truncate the call.
  • unSupported – (default) Release the call.

trunkOfferingSupport

N/A

Set flag to support trunk offering messages can, fan, ofr, rcl (presently, this only applies to mexico).

  • supported
  • unSupported (default)

u2uServiceLevel

N/A

Use flag to specify the level of user-to-user services supported in the ISUP Signaling Profile.

  • implicit (default)
  • level1
  • level2
  • level3
  • none

ucic

N/A

Set flag to support UCIC for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

uidActionInd

N/A

Set flag to support UID Action Indicators parameter for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

uidCapabilityInd

N/A

Set flag to support UID Capabilities parameter for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

uniqueTransitCit

N/A

Use this control to define transit carrier data (Protocol: Japan).

  • supported – The SBC compares the transit carrier code configured on the PSX with the last carrier code added by the previous exchange. If both are transit and have the same carrier code, the SBC does not add in duplicate information. The ingress signaling profile controls checking backward messages and the egress signaling profile controls checking forward messages.
  • unSupported – (default) The SBC adds transit carrier data with the same carrier code as the previous code if configured by the PSX.

upaUpt

N/A

Set flag to support UPA/UPT for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

updateAnmBci

N/A

Use flag to specify how to treat BCI in ANM (Protocol: Japan).

  • supported – BCI in ANM is taken from last received in ACM or CPG; charge indicator is updated.
  • unSupported – (default) BCI in ANM set to default if not present.
updateInternalNetworkIndicatorInCalledPartyNumber


N/A

Use this parameter to specify how to update the Internal Network Indicator in the Called Party Number.

  • transit – (default) Value received is unchanged.
  • allowed – Internal Network Indicator may be updated.
  • notAllowed – Internal Network Indicator may not be updated.
updateNumberIncompleteIndicatorInCallingPartyIndicator
 

N/A

This parameter is used to update the Number Incomplete Indicator in the Calling Party Number.

  • transit – (default) Value received is unchanged.
  • complete – The delivered number is marked as complete.
  • incomplete – The delivered number is marked as incomplete.

upvExchangeRoles

N/A

Use this control to identify the exchange roles allowed to perform Unrecognized Parameter Value (UPV) handling. By default, BITs 0-5 are selected.

  • orig – (BIT 0) Originating exchange
  • term – (BIT 1) Terminating exchange
  • intwk – (BIT 2) Interworking exchange
  • trans – (BIT 3) Transit exchange
  • int – (BIT 4) International exchange
  • unknown – (BIT 5) Unknown exchange
  • none – (BIT 6) No exchange roles allowed

usePsxChgIndForCpgInPresubCall

N/A

Set flag to use the PSX ACM charge indicator to overwrite the charge indicator field of the BCI for CPG messages, or leave as "unSupported" to transit the value received.

  • supported
  • unSupported (default)

userServiceInformation

N/A

Set flag to support User Service Information (information sent in forward direction indicating bearer capability requested by calling party) for the ISUP Signaling Profile.

  • supported (default)
  • unSupported

userTeleService

N/A

Set flag to support User Teleservice parameter for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

usiPrime

N/A

Set flag to support the USI Prime parameter for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

usr

N/A

Set flag to support USR parameter for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

uuIndAcm

N/A

This flag specifies whether the User-to-User Indicators parameter is supported in ACM for the ISUP Signaling Profile.

  • supported (default)
  • unSupported

uuIndCon

N/A

This flag specifies whether the User-to-User Indicators parameter is supported in CON for ISUP Signaling Profile.

  • supported (default)
  • unSupported

uuIndInFar

N/A

This flag specifies whether the User-to-User Indicators Parameter is supported in FAR for ISUP Signaling Profile.

  • supported
  • unSupported (default)

uuIndRel

N/A

This flag specifies whether the User-to-User Indicators Parameter is supported in REL for the ISUP Signaling Profile.

  • supported (default)
  • unSupported

uuInfo

N/A

This flag specifies whether the User-to-User Information parameter is supported for the ISUP Signaling Profile.

  • supported (default)
  • unSupported

uuInfoAcm

N/A

This flag specifies whether the UU Information is supported in the ACM for the ISUP Signaling Profile.

  • supported (default)
  • unSupported

uuiInInf

N/A

This flag specifies whether the User-to-User Information parameter is supported in the INF.

  • supported
  • unSupported (default)

uuiRestrictions

N/A

(Protocol: Japan)
Set flag to discard subsequent UUIs based on BCI field values received in ACM/CPG.

  • supported
  • unSupported (default)

uuindAnm

N/A

Set flag to support the UUI parameter in the ANM for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

uuindCpg

N/A

Set flag to support the UUI parameter in the CPG for the ISUP Signaling Profile.

  • supported
  • unSupported (default)

validateIsubFromSip

N/A

Set this flag to validate ISUB from SIP. (Protocol: Japan)

  • supported – The SBC ensures only digits 0-9 are allowed in the NSAP ISUB from SIP.
  • unSupported – (default) The SBC does not check the ISUB digits.

versionId

100-65535

Enter version ID to identify a signaling group.

version IDs 0-99 are reserved for seed data.

visitorMa

N/A

Set this flag to support Visitor MA parameter.

  • supported
  • unSupported (default)

  • No labels