Contents

X.25 Call Confirm Packet Address Control

The X.25 Call Confirm Packet Address Control feature provides options for controlling the source and destination addresses that are encoded in outgoing Call Confirm packets. You can suppress the addresses completely or specify that the addresses originally proposed in the received Call packet be encoded in the Call Confirm packet. This feature may be necessary when connecting to equipment that implements a nonstandard or proprietary X.25 service.

Finding Support Information for Platforms and Cisco IOS Software Images

Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image support. Access Cisco Feature Navigator at http:/​/​www.cisco.com/​go/​fn . You must have an account on Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at the login dialog box and follow the instructions that appear.

Finding Feature Information

Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table at the end of this module.

Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/​go/​cfn. An account on Cisco.com is not required.

Information About X.25 Call Confirm Packet Address Control

Address Encoding in X.25 Call Confirm Packets


Note

This document refers to Call packets and Call Confirm packets. These names differ from those standardized by X.25. The standard distinguishes between a Call packet sent by the data terminal equipment (DTE) station (a Call Request) and one sent by the data communications equipment (DCE) station (an Incoming Call), and similarly between a Call Confirm packet sent by the DTE (a Call Accepted) and one sent by the DCE (a Call Connected). The packets are encoded identically, and in many cases the processing that X.25 does is identical; however, there are cases where the behavior is predicated on the station type that is receiving or sending the packet.

An X.25 switched virtual circuit (SVC) is established between two stations through the exchange of a Call and a Call Confirm packet. The X.25 standards specify that Call packets include source and destination addresses. Call Confirm packets might also encode source and destination addresses, depending on the circumstances.When the source address is encoded in a Call Confirm packet, the X.25 standards require that it be the same address that was specified in the Call packet. When the destination address is encoded in a Call Confirm packet and is different from the destination address in the Call packet, the newer X.25 standards (those after ITU-T 1980 X.25) require that the reason for the difference be signaled by the encoding of the Called Line Address Modified Notification (CLAMN) facility.

For example,when an X.25 Call is routed through a configured hunt group, a Call Redirection/Call Deflection Notification (CRCDN) facility is encoded in the forwarded call along with the original destination address. This encoding notifies the receiver that the Call packet was redistributed by a hunt group. If such a Call is accepted by a returned Call Confirm packet, a CLAMN facility and the destination address of the accepting station will be encoded in the Call Confirm packet. This encoding notifies the originator that the accepting destination was reached by distribution through a hunt group.

X.25 Call Confirm Packet Address Control

Network devices that implement nonstandard X.25 service may have different requirements for address encoding in the Call Confirm packet. The no x25 security call-confirm address outcommand enables you to control the source and destination addresses that are encoded in outgoing Call Confirm packets. You can suppress the addresses completely, or you can specify that the addresses originally presented in the received Call packet be encoded unmodified in the Call Confirm packet. When address suppression is configured, any address block in the Call Confirm packet will specify the null address (zero digits) for the suppressed addresses.


Caution

X.25 specifies address signaling behavior as a security measure to ensure that connecting devices are given clear notice of a Call setup that encountered redirection, deflection, or distribution to an alternate destination. Disabling these security features should be done only when the risks of doing so are understood and acceptable.

X.25 Call Confirm packet address control can be configured on an interface or in an X.25 profile. When the feature is configured on an interface, all Call Confirm packets sent over the services that use that interface will be affected, including SVCs that use a configuration from a subinterface. When the feature is configured in an X.25 profile, all services using that profile will be affected.

Benefits of X.25 Call Confirm Packet Address Control

Users implementing nonstandard X.25 service may have specific requirements for the encoding of source and destination addresses in Call Confirm packets. The X.25 Call Confirm Packet Address Control feature enables you to control the source and destination addresses that are encoded in outgoing Call Confirm packets. This feature allows you to suppress the addresses completely or specify that the addresses originally proposed in the received Call packet be encoded in the Call Confirm packet.

How to Configure X.25 Call Confirm Packet Address Control

Configuring X.25 Call Confirm Packet Address Control on an Interface

To suppress the addresses in a Call Confirm packet, or to specify that the addresses presented in the original Call packet are to be encoded in the Call Confirm packet, perform the following steps:

SUMMARY STEPS

    1.    enable

    2.    configure terminal

    3.    interface serial number

    4.    encapsulation x25

    5.    no x25 security call-conf address out source {suppress | unmodified} dest {suppress | unmodified}

    6.    exit


DETAILED STEPS
     Command or ActionPurpose
    Step 1 enable


    Example:
    Router> enable
     

    Enables privileged EXEC mode.

    • Enter your password if prompted.
     
    Step 2 configure terminal


    Example:
    Router# configure terminal
     

    Enters global configuration mode.

     
    Step 3 interface serial number


    Example:
    Router(config)# interface serial 0
     

    Specifies an interface and enters interface configuration mode.

     
    Step 4 encapsulation x25


    Example:
    Router(config-if)# encapsulation x25
     

    Enables the default X.25 DTE operation mode.

     
    Step 5 no x25 security call-conf address out source {suppress | unmodified} dest {suppress | unmodified}


    Example:
    Router(config-if)# no x25 security call-conf address out source suppress dest suppress
     

    Suppresses the addresses in transmitted X.25 Call Confirm packets or specifies that the addresses originally received in a Call packet are to be encoded in the Call Confirm packet.

     
    Step 6 exit

    Example:
    Router(config-if)# exit
     

    Returns to global configuration mode.

     

    Troubleshooting Tips

    Use the debug x25 events command to determine when the source and destination addresses in Call Confirm packets have been suppressed or configured to remain unmodified from the addresses proposed in the original Call packet.

    Configuring X.25 Call Confirm Packet Address Control in an X.25 Profile

    To suppress the addresses in a Call Confirm packet, or to specify that the addresses presented in the original Call packet are to be encoded in the Call Confirm packet, perform the following steps:

    SUMMARY STEPS

      1.    enable

      2.    configure terminal

      3.    x25 profile name {dce | dte | dxe}

      4.    no x25 security call-conf address out source {suppress | unmodified} dest {suppress | unmodified}

      5.    exit


    DETAILED STEPS
       Command or ActionPurpose
      Step 1 enable


      Example:
      Router> enable
       

      Enables privileged EXEC mode.

      • Enter your password if prompted.
       
      Step 2 configure terminal


      Example:
      Router# configure terminal
       

      Enters global configuration mode.

       
      Step 3 x25 profile name {dce | dte | dxe}


      Example:
      x25 profile NetworkNodeA dce
       

      Configures an X.25 profile.

       
      Step 4 no x25 security call-conf address out source {suppress | unmodified} dest {suppress | unmodified}


      Example:
      Router(config-if)# no x25 security call-conf address out source suppress dest suppress
       

      Suppresses the addresses in transmitted X.25 Call Confirm packets or specifies that the addresses originally received in a Call packet are to be encoded in the Call Confirm packet.

       
      Step 5 exit

      Example:
      Router(config-if)# exit
       

      Returns to global configuration mode.

       

      Troubleshooting Tips

      Use the debug x25 events command to determine when the source and destination addresses in Call Confirm packets have been suppressed or configured to remain unmodified from the addresses proposed in the original Call packet.

      Configuration Examples for X.25 Call Confirm Packet Address Control

      Suppressing Addresses in Call Confirm Packets Example

      The following example shows how to suppress both the source and destination addresses in Call Confirm packets:

      interface serial 0
 no ip address
 encapsulation x25
 no x25 security call-conf address out source suppress dest suppress

      Using Addresses from Original Call Packets in the Call Confirm Packets Example

      The following example show how to specify that the addresses presented in the original Call packet are encoded in the Call Confirm packet:

      interface serial 0
 no ip address
 encapsulation x25
 no x25 security call-conf address out source unmodified dest unmodified

      Additional References

      Related Documents

      Related Topic

      Document Title

      X.25 commands

      Cisco IOS Wide-Area Networking Command Reference , Release 12.3

      X.25 configuration tasks and examples

      Cisco IOS Wide-Area Networking Configuration Guide, Release 12.3

      Commands and tasks for configuring suppression of CRCDN and CLAMN security signaling facilities

      X.25 Suppression of Security Signaling Facilities, 12.2(13)T new feature document

      Standards

      Standards

      Title

      ITU-T X.25
      • ITU-T 1980 X.25 Recommendation
      • ITU-T 1984 X.25 Recommendation
      • ITU-T 1988 X.25 Recommendation
      • ITU-T 1993 X.25 Recommendation

      MIBs

      MIBs

      MIBs Link

      None

      To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:

      http:/​/​www.cisco.com/​go/​mibs

      RFCs

      RFCs

      Title

      None

      --

      Technical Assistance

      Description

      Link

      Technical Assistance Center (TAC) home page, containing 30,000 pages of searchable technical content, including links to products, technologies, solutions, technical tips, and tools. Registered Cisco.com users can log in from this page to access even more content.

      http:/​/​www.cisco.com/​public/​support/​tac/​home.shtml

      Feature Information for X.25 Call Confirm Packet Address Control

      The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.

      Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/​go/​cfn. An account on Cisco.com is not required.

      Table 1 Feature Information for X.25 Call Confirm Packet Address Control

      Feature Name

      Releases

      Feature Information

      X.25 Call Confirm Packet Address Control

      12.3(2)T

      The X.25 Call Confirm Packet Address Control feature provides options for controlling the source and destination addresses that are encoded in outgoing Call Confirm packets. You can suppress the addresses completely or specify that the addresses originally proposed in the received Call packet be encoded in the Call Confirm packet. This feature may be necessary when connecting to equipment that implements a nonstandard or proprietary X.25 service.

      In Cisco IOS Release 12.3(2)T, this feature was introduced.

      The following commands were introduced or modified: x25 security call-conf address out .

      X.25 Call Confirm Packet Address Control

      X.25 Call Confirm Packet Address Control

      The X.25 Call Confirm Packet Address Control feature provides options for controlling the source and destination addresses that are encoded in outgoing Call Confirm packets. You can suppress the addresses completely or specify that the addresses originally proposed in the received Call packet be encoded in the Call Confirm packet. This feature may be necessary when connecting to equipment that implements a nonstandard or proprietary X.25 service.

      Finding Support Information for Platforms and Cisco IOS Software Images

      Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image support. Access Cisco Feature Navigator at http:/​/​www.cisco.com/​go/​fn . You must have an account on Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at the login dialog box and follow the instructions that appear.

      Finding Feature Information

      Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table at the end of this module.

      Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/​go/​cfn. An account on Cisco.com is not required.

      Information About X.25 Call Confirm Packet Address Control

      Address Encoding in X.25 Call Confirm Packets


      Note

      This document refers to Call packets and Call Confirm packets. These names differ from those standardized by X.25. The standard distinguishes between a Call packet sent by the data terminal equipment (DTE) station (a Call Request) and one sent by the data communications equipment (DCE) station (an Incoming Call), and similarly between a Call Confirm packet sent by the DTE (a Call Accepted) and one sent by the DCE (a Call Connected). The packets are encoded identically, and in many cases the processing that X.25 does is identical; however, there are cases where the behavior is predicated on the station type that is receiving or sending the packet.

      An X.25 switched virtual circuit (SVC) is established between two stations through the exchange of a Call and a Call Confirm packet. The X.25 standards specify that Call packets include source and destination addresses. Call Confirm packets might also encode source and destination addresses, depending on the circumstances.When the source address is encoded in a Call Confirm packet, the X.25 standards require that it be the same address that was specified in the Call packet. When the destination address is encoded in a Call Confirm packet and is different from the destination address in the Call packet, the newer X.25 standards (those after ITU-T 1980 X.25) require that the reason for the difference be signaled by the encoding of the Called Line Address Modified Notification (CLAMN) facility.

      For example,when an X.25 Call is routed through a configured hunt group, a Call Redirection/Call Deflection Notification (CRCDN) facility is encoded in the forwarded call along with the original destination address. This encoding notifies the receiver that the Call packet was redistributed by a hunt group. If such a Call is accepted by a returned Call Confirm packet, a CLAMN facility and the destination address of the accepting station will be encoded in the Call Confirm packet. This encoding notifies the originator that the accepting destination was reached by distribution through a hunt group.

      X.25 Call Confirm Packet Address Control

      Network devices that implement nonstandard X.25 service may have different requirements for address encoding in the Call Confirm packet. The no x25 security call-confirm address outcommand enables you to control the source and destination addresses that are encoded in outgoing Call Confirm packets. You can suppress the addresses completely, or you can specify that the addresses originally presented in the received Call packet be encoded unmodified in the Call Confirm packet. When address suppression is configured, any address block in the Call Confirm packet will specify the null address (zero digits) for the suppressed addresses.


      Caution

      X.25 specifies address signaling behavior as a security measure to ensure that connecting devices are given clear notice of a Call setup that encountered redirection, deflection, or distribution to an alternate destination. Disabling these security features should be done only when the risks of doing so are understood and acceptable.

      X.25 Call Confirm packet address control can be configured on an interface or in an X.25 profile. When the feature is configured on an interface, all Call Confirm packets sent over the services that use that interface will be affected, including SVCs that use a configuration from a subinterface. When the feature is configured in an X.25 profile, all services using that profile will be affected.

      Benefits of X.25 Call Confirm Packet Address Control

      Users implementing nonstandard X.25 service may have specific requirements for the encoding of source and destination addresses in Call Confirm packets. The X.25 Call Confirm Packet Address Control feature enables you to control the source and destination addresses that are encoded in outgoing Call Confirm packets. This feature allows you to suppress the addresses completely or specify that the addresses originally proposed in the received Call packet be encoded in the Call Confirm packet.

      How to Configure X.25 Call Confirm Packet Address Control

      Configuring X.25 Call Confirm Packet Address Control on an Interface

      To suppress the addresses in a Call Confirm packet, or to specify that the addresses presented in the original Call packet are to be encoded in the Call Confirm packet, perform the following steps:

      SUMMARY STEPS

        1.    enable

        2.    configure terminal

        3.    interface serial number

        4.    encapsulation x25

        5.    no x25 security call-conf address out source {suppress | unmodified} dest {suppress | unmodified}

        6.    exit


      DETAILED STEPS
         Command or ActionPurpose
        Step 1 enable


        Example:
        Router> enable
         

        Enables privileged EXEC mode.

        • Enter your password if prompted.
         
        Step 2 configure terminal


        Example:
        Router# configure terminal
         

        Enters global configuration mode.

         
        Step 3 interface serial number


        Example:
        Router(config)# interface serial 0
         

        Specifies an interface and enters interface configuration mode.

         
        Step 4 encapsulation x25


        Example:
        Router(config-if)# encapsulation x25
         

        Enables the default X.25 DTE operation mode.

         
        Step 5 no x25 security call-conf address out source {suppress | unmodified} dest {suppress | unmodified}


        Example:
        Router(config-if)# no x25 security call-conf address out source suppress dest suppress
         

        Suppresses the addresses in transmitted X.25 Call Confirm packets or specifies that the addresses originally received in a Call packet are to be encoded in the Call Confirm packet.

         
        Step 6 exit

        Example:
        Router(config-if)# exit
         

        Returns to global configuration mode.

         

        Troubleshooting Tips

        Use the debug x25 events command to determine when the source and destination addresses in Call Confirm packets have been suppressed or configured to remain unmodified from the addresses proposed in the original Call packet.

        Configuring X.25 Call Confirm Packet Address Control in an X.25 Profile

        To suppress the addresses in a Call Confirm packet, or to specify that the addresses presented in the original Call packet are to be encoded in the Call Confirm packet, perform the following steps:

        SUMMARY STEPS

          1.    enable

          2.    configure terminal

          3.    x25 profile name {dce | dte | dxe}

          4.    no x25 security call-conf address out source {suppress | unmodified} dest {suppress | unmodified}

          5.    exit


        DETAILED STEPS
           Command or ActionPurpose
          Step 1 enable


          Example:
          Router> enable
           

          Enables privileged EXEC mode.

          • Enter your password if prompted.
           
          Step 2 configure terminal


          Example:
          Router# configure terminal
           

          Enters global configuration mode.

           
          Step 3 x25 profile name {dce | dte | dxe}


          Example:
          x25 profile NetworkNodeA dce
           

          Configures an X.25 profile.

           
          Step 4 no x25 security call-conf address out source {suppress | unmodified} dest {suppress | unmodified}


          Example:
          Router(config-if)# no x25 security call-conf address out source suppress dest suppress
           

          Suppresses the addresses in transmitted X.25 Call Confirm packets or specifies that the addresses originally received in a Call packet are to be encoded in the Call Confirm packet.

           
          Step 5 exit

          Example:
          Router(config-if)# exit
           

          Returns to global configuration mode.

           

          Troubleshooting Tips

          Use the debug x25 events command to determine when the source and destination addresses in Call Confirm packets have been suppressed or configured to remain unmodified from the addresses proposed in the original Call packet.

          Configuration Examples for X.25 Call Confirm Packet Address Control

          Suppressing Addresses in Call Confirm Packets Example

          The following example shows how to suppress both the source and destination addresses in Call Confirm packets:

          interface serial 0
 no ip address
 encapsulation x25
 no x25 security call-conf address out source suppress dest suppress

          Using Addresses from Original Call Packets in the Call Confirm Packets Example

          The following example show how to specify that the addresses presented in the original Call packet are encoded in the Call Confirm packet:

          interface serial 0
 no ip address
 encapsulation x25
 no x25 security call-conf address out source unmodified dest unmodified

          Additional References

          Related Documents

          Related Topic

          Document Title

          X.25 commands

          Cisco IOS Wide-Area Networking Command Reference , Release 12.3

          X.25 configuration tasks and examples

          Cisco IOS Wide-Area Networking Configuration Guide, Release 12.3

          Commands and tasks for configuring suppression of CRCDN and CLAMN security signaling facilities

          X.25 Suppression of Security Signaling Facilities, 12.2(13)T new feature document

          Standards

          Standards

          Title

          ITU-T X.25
          • ITU-T 1980 X.25 Recommendation
          • ITU-T 1984 X.25 Recommendation
          • ITU-T 1988 X.25 Recommendation
          • ITU-T 1993 X.25 Recommendation

          MIBs

          MIBs

          MIBs Link

          None

          To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:

          http:/​/​www.cisco.com/​go/​mibs

          RFCs

          RFCs

          Title

          None

          --

          Technical Assistance

          Description

          Link

          Technical Assistance Center (TAC) home page, containing 30,000 pages of searchable technical content, including links to products, technologies, solutions, technical tips, and tools. Registered Cisco.com users can log in from this page to access even more content.

          http:/​/​www.cisco.com/​public/​support/​tac/​home.shtml

          Feature Information for X.25 Call Confirm Packet Address Control

          The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.

          Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/​go/​cfn. An account on Cisco.com is not required.

          Table 1 Feature Information for X.25 Call Confirm Packet Address Control

          Feature Name

          Releases

          Feature Information

          X.25 Call Confirm Packet Address Control

          12.3(2)T

          The X.25 Call Confirm Packet Address Control feature provides options for controlling the source and destination addresses that are encoded in outgoing Call Confirm packets. You can suppress the addresses completely or specify that the addresses originally proposed in the received Call packet be encoded in the Call Confirm packet. This feature may be necessary when connecting to equipment that implements a nonstandard or proprietary X.25 service.

          In Cisco IOS Release 12.3(2)T, this feature was introduced.

          The following commands were introduced or modified: x25 security call-conf address out .