Administering Page three of the Survivable Processor screen

Last Updated : Apr 24, 2024 |
Prolog information
Metadata
Keywords:
Use page three if you have an Application Enablement Services (AES), a CDR that connects to the Processor Ethernet interface of the survivable remote server or survivable core server that you identified in page one, or Survivable CDR. If the AES or the CDR is administered on the IP Services screen, the system automatically displays on page three of the Survivable Processor screen. You cannot add an adjunct using this screen. The adjunct must be administered in the ip-services screen first.
Note:
For more information on Survivable CDR, see Survivable CDR. For more information on how to administer Survivable CDR, see Avaya Aura® Communication Manager Feature Description and Implementation.
  1. The Service Type field identifies the server application type/adjunct connection used on this channel.
    ADDITIONAL INFORMATION:
    Valid entries include the following:
  2. , and
  • Enter one of the following values in the Enabled field:
    • Enter n (no) if this ip-services link is disabled on the survivable remote server or the survivable core server.
    • Enter i (inherit) if this link is to be inherited by the survivable remote server or survivable core server. Generally you would use the inherit option in the following scenario, where the main server connects to the adjuncts using the main servers Processor Ethernet interface and you want the survivable remote server or survivable core server to connect to the adjunct using their Processor Ethernet interface.
    • Enter o (over-ride) to over-ride the processor channel information sent in the file sync from the main server. The over-ride option causes the near-end (servers end of the link) address of the link to change to p when the translations are sent from the main server to the survivable remote server or the survivable core server. Generally you would want the over-ride
    • Enter y to enable Survivable CDR for this survivable remote server or survivable core server.
      When the Service Type field is set to CDR1 or CDR2 and the Store to Dsk field is set to y, all CDR data for the specific survivable remote server or survivable core server being administered will be sent to the hard disk rather than output to an IP link. Survivable remote server or survivable core server will only store CDR records to hard disk when the survivable remote server or survivable core server is controlling a gateway or media gateway.
  • The Local Node field contains the node name as defined on the Node Names screen.
  • The Local Port field contains the originating port number. For client applications such as CDR, this field defaults to
  • The Remote Node field specifies the name at the far end of the link for the CDR. The remote node should not be defined as a link on the IP Interfaceor Data Module screen. The Remote Node field does not apply for AESs.
  • The Remote Port field specifies the port number of the destination. Valid entries range from 5000 to 65500 for CDR or AESs. The remote port number must match the port administered on the CDR or AESs server.
    ADDITIONAL INFORMATION:
    Note:
    There can only be one AESs entered for each Processor Ethernet interface.
    Note:
    The System-Parameters CDR screen is removed on the survivable remote server or the translations of the survivable core server when no is entered in the Enabled field on the page three of the Survivable Processor screen.
    • Related links
    Survivable CDR