anchor.diff:  
       sccpStack.start();
   ----
  +
  +For RestcommONE (Telscale) version creation of SccpStackImpl looks like:
  +
  +[source]
  +----
  +    sccpStack = new SccpStackImpl(schedulerMBean, beanName, ss7ExtInterfaceTelscale);
  +----
  +
   For connection-oriented protocol classes support configure SCCP layer the following way:
   [source]
   ----
  
positive.code:     SccpAddress pattern = new SccpAddressImpl(RoutingIndicator.ROUTING_BASED_ON_GLOBAL_TITLE, gt, 0, 0);
      sccpStack.getRouter().addRule(1, RuleType.SOLITARY, LoadSharingAlgorithm.Bit0, OriginationType.REMOTE, pattern, "K", 1, -1, null, 0);
      sccpStack.getRouter().addRule(2, RuleType.SOLITARY, LoadSharingAlgorithm.Bit0, OriginationType.LOCAL, pattern, "K", 2, -1, null, 0);
  ----		
  
  Once SCCP is configured and started, next step it to build TCAP layer.
  
  == Building TCAP
  
  There is no configuration to persist in case of TCAP. 
  [source]
  ----
      org.restcomm.protocols.ss7.tcap.api tcapStack = null;
  
negative.code: Before starting SCCP stack all it needs to know is underlying MTP3 layer and scheduler.
  This scheduler is used for asynchronously sending outgoing messages.
  Above sections explained building SCTP and M3UA,  however if you are using Dialogic boards or dahdi based boards (Diguim/Sangoma), you need to build and configure respective MTP3 layers depending on hardware used and set those in SCCP Stack `sccpStack.setMtp3UserPart(1, this.clientM3UAMgmt)`.
  
  
  One of the best features of jSS7 is it supports multiple MTP3 layers and hence you can have combination of many MTP3 layers (each of different or same type like M3UA, Dialogic and Dahid;  all used at same time).
  
  Once SCCP stack is started, it should be configured for local and remote signaling point-code, network indicator, remote sub system number and routing rules. For removing all previously configured resources you need to call this command (after a Stack start).
  [source]
  