Cisco Systems MC-413 User Manual

Configuring Support for PBX Signalling Protocols

This chapter describes how to configure support for PBX signalling formats such as Q.SIG and transparent common channel signalling (CCS). Configuring support for these signalling protocols on your router enables the router to interoperate with PBXs running these signalling protocols.

This chapter includes the following sections:

• Configuring Q.SIG PRI Signalling Support

• Configuring Transparent CCS on the Cisco MC3810

For a complete description of the commands used in this chapter, refer to the Cisco IOS Multiservice Applications Command Reference. To locate documentation of other commands that appear in this

chapter, use the command reference master index or search online.

Configuring Q.SIG PRI Signalling Support

Configuration Tasks for Q.SIG PRI signalling support are described in the following sections:

• Configuring Voice over IP Q.SIG Network Transparency on the Cisco AS5300

• Configuring Q.SIG PRI Signalling Support on the Cisco MC3810

Although the procedures for configuring Q.SIG signalling support on the Cisco AS5300 and on the Cisco MC3810 are very similar, implementation differences are described in the respective sections.

Benefits of Q.SIG

On both the Cisco AS5300 and the Cisco MC3810, Q.SIG voice signalling provides the following benefits:

• Enables Cisco devices to connect with digital PBXs that use the Q.SIG form of CCS.

• Provides access to multiple remote PBXs with a single connection to a Cisco device.

• Provides transparent support for supplementary PBX services, so that proprietary PBX features are

not lost when connecting PBXs to Cisco AS5300 and Cisco MC3810 networks.

• Provides Q.SIG support based on widely used ISDN Q.931 standards. Cisco Q.SIG implementation

follows the following European Telecommunications Standards Institute (ETSI) implementation standards:

–

ECMA 143: Private Telecommunication Network (PTN) Inter-exchange Signalling Protocol Circuit Mode Basic Services. (This specification covers Q.SIG basic call services.)

Cisco IOS Multiservice Applications Configuration Guide

MC-413

Configuring Support for PBX Signalling Protocols

Configuring Q.SIG PRI Signalling Support

–

ECMA 142: Specification, Functional Model and Information Flows for Control Aspects of Circuit Mode Basic Services in Private Telecommunication Networks.

–

ECMA 141: Private Telecommunications Networks Inter-exchange Signalling Data Link Layer Protocol.

–

ECMA 165: Generic Functional Protocol for the Support of Supplementary Services.

• Provides compatibility with H.323 for IP call setup and transport of Q.SIG messaging.

• Provides support for calls that do not require a bearer channel for voice transport.

• Provides support for bandwidth-on-demand, utilizing network resources only when a connection is

desired.

Configuring Voice over IP Q.SIG Network Transparency on the Cisco AS5300

Integration of Q.SIG support with VoIP enables Cisco voice switching services to connect PBXs, key systems, and CO switches that communicate by using the Q.SIG protocol.

In Cisco IOS Release 12.1, Q.SIG PRI signalling on the Cisco AS5300 applies only to VoIP.

The Q.SIG protocol is a variant of ISDN D-channel voice signalling. It is based on the ISDN Q.921 and Q.931 standards and is becoming a worldwide standard for PBX interconnection. By using Q.SIG signalling, Cisco devices can route incoming voice calls from a private integrated services network exchange (PINX) device across a WAN to a peer Cisco device, which can then transport the signalling and voice packets to a second PINX device.

Note In Cisco IOS Release 12.1, the Cisco AS5300 supports ISDN PRI only when a Q.SIG

connection to the PINX is configured on the T1/E1 controller.

Q.SIG allows the user to place Q.SIG calls into and receive Q.SIG calls from Cisco VoIP networks. The Cisco packet network appears to PBXs as a large, distributed transit PBX that can establish calls to any destination served by a Cisco voice node. The switched voice connections are established and torn down in response to Q.SIG control messages that come over an ISDN PRI D channel. The Q.SIG message is passed transparently across the IP network and the message appears to the attached PINX devices as a transit network. The PINX devices are responsible for processing and provisioning the attached services.

Figure 96 shows an example of a Q.SIG signalling configuration. In this example, the Cisco AS5300 acts as either a master to a slave PBX or as a slave to a master PBX.

Figure 96 Cisco AS5300 Q.SIG Signalling Configuration

3001

PBX

Slave

Q.SIG

E1/T1 channel

Cisco

AS5300

No. 1

Master

The following restrictions and limitations apply to the Cisco AS5300 Q.SIG implementation:

• Q.SIG functionality on the AS5300 requires Cisco IOS Release 12.0(7)T or later and VCWare

version 4.04.

Cisco

AS5300

No. 2

Slave

Q.SIG

E1/T1 channel

PBX

Master

4001

22864

MC-414

Cisco IOS Multiservice Applications Configuration Guide

Configuring Support for PBX Signalling Protocols

• Q.SIG data calls are not supported. All calls with bearer capability indicating a nonvoice type (such

as video telephony) are rejected.

• The incoming POTS dial peer must have DID configured to prevent generation of a secondary dial

tone to ensure end-to-end Q.SIG feature transparency.

Q.SIG Prerequisite Tasks

The following configuration tasks should be completed before you configure Q.SIG for VoIP:

• Configure the ports used on the Cisco AS5300 as voice ports. For information on how to configure

ports to be used as voice ports, see “Configuring Voice Ports” section in the “Configuring Voice over IP” chapter.

• Install VCWare version 4.04. For information on how to upgrade or install VCWare, see the

“Managing Cisco AS5300 VFCs ” section in the “Configuring Voice over IP” chapter.

• Configure VoIP. For information on how to configure VoIP, see the “Configuring Voice over IP”

chapter.

Configuring Q.SIG PRI Signalling Support

Q.SIG Configuration Task List

To configure Q.SIG for Voice over IP, complete the tasks shown in the following sections. Some of these tasks are optional.

• Configuring VoIP Q.SIG

• Configuring Fusion Call Control Signalling (NEC Fusion) on the Cisco AS5300

Configuring VoIP Q.SIG

To configure Q.SIG signalling support on the Cisco AS5300, use the following commands beginning in global configuration mode:

Command Purpose

Step 1

Router(config)# isdn switch-type primary-qsig

Configures the ISDN switch-type to support Q.SIG signalling.

Note You can configure the ISDN switch type

using either this global command or the same command in interface configuration mode, depending on your configuration. (See Step

5.) If you configure the global isdn-switch-type command for Q.SIG support, you need not configure the interface isdn-switch-type command for Q.SIG.

If the PBX in your configuration is an NEC PBX, and you are using Fusion Call Control Signalling (FCCS). See the “Configuring Fusion Call Control Signalling (NEC Fusion) on the Cisco AS5300” later in this chapter.

Cisco IOS Multiservice Applications Configuration Guide

MC-415

Configuring Q.SIG PRI Signalling Support

Command Purpose

Step 2

Step 3

Step 4

Step 5

Step 6

Router(config)# controller {T1 | E1} controller number

Router(config-controller)# pri-group [timeslot range]

Router(config-controller)# exit

Router(config)# interface serial 1:x

Router(config-if)# isdn switch-type primary-qsig

Configuring Support for PBX Signalling Protocols

Enters controller configuration mode.

Configures the PRI group for either T1 or E1 to carry voice traffic. For T1, available time slots are from 1 to 23, and for E1, available time slots are from 1 to

31.

You can configure the PRI group to include all available time slots, or you can configure a select group of time slots for the PRI group. For example, if only time slots 1 to 10 are in the PRI group, enter the pri-group timeslot 1-10 command. If the PRI group includes all channels available for T1 (channels 1 to

23), enter the pri-group timeslot 1-23 command. If the PRI group includes all channels available for E1 (channels 1 to 31), enter the pri-group timeslot 1-31 command.

Exits controller configuration mode.

Enters interface configuration mode for the ISDN PRI interface. For T1, enter serial 1:23. For E1, enter serial 1:15.

If you did not configure the global ISDN switch type for Q.SIG support in Step 1, configures the interface ISDN switch type to support Q.SIG signalling.

Step 7

Step 8

Step 9

Router(config-if)# isdn protocol-emulate {user | network}

Router(config-if)# isdn overlap-receiving value

Router(config-if)# isdn incoming-voice modem

The conditions that apply to this command in global configuration mode also apply to this command in interface configuration mode.

This interface command overrides the global isdn switch-type command setting for this interface.

Configures the ISDN interface to serve as either the primary Q.SIG slave or the primary Q.SIG master. For this command, the user keyword specifies slave and the network keyword specifies master.

If the PINX is the primary Q.SIG master, configure the Cisco AS5300 to serve as the primary Q.SIG slave. If the PINX is the primary Q.SIG slave, configure the Cisco AS5300 to serve as the primary Q.SIG master.

Activates overlap signalling to send to the destination PBX.

This command is not mandatory; you can leave the default value.

Routes incoming voice calls to the modem and treats them as analog data.

MC-416

Cisco IOS Multiservice Applications Configuration Guide

Configuring Support for PBX Signalling Protocols

Command Purpose

Step 10

Step 11

Router(config-if)# isdn network-failure-cause [value]

Router(config-if)# isdn bchan-number-order {ascending | descending}

Configuring Q.SIG PRI Signalling Support

(Optional) Specifies the cause code to pass to the PBX when a call cannot be placed or completed because of internal network failures. Possible values are from 1 to 127.

All cause codes except for Normal Call Clearing (16), User Busy (17), No User Responding (18), and No Answer from User (19) will be changed to the specified cause code.

(Optional) Configures the ISDN PRI interface to make the outgoing call selection in ascending or descending order.

The default is descending order, in which the first call from the Cisco AS5300 uses channel 23 (T1) or channel 31 (E1). The second call then uses channel 22 (T1) or channel 30 (E1), and so on in descending order.

If you select ascending order and the PRI group starts with 1, the first call uses channel 1, the second call uses channel 2, and so on in ascending order. If the PRI group starts with a different time slot, the ascending order starts with the lowest time slot.

Step 12

Router(config-if)# exit

Exits interface configuration mode.

As shown in the preceding section, you have a choice of configuring the isdn-switch-type command to support Q.SIG at either the global configuration level or the interface configuration level. For example, if you have a Q.SIG connection on one line and on the PRI port, you can configure the ISDN switch type in one of the following combinations:

• Set the global isdn-switch-type command to support Q.SIG and set the interface isdn-switch-type

command for interface serial 0:23 to a PRI setting such as 5ess.

• Set the global isdn-switch-type command to support PRI 5ess and set the interface

isdn-switch-type command for interface serial 1:23 to support Q.SIG.

• Configure the global isdn-switch-type command to another setting (such as switch type VN3), set

the interface isdn-switch-type command for interface serial 0:23 to a PRI setting, and set the interface isdn-switch-type command for interface serial 1:23 to support Q.SIG.

Configuring Fusion Call Control Signalling (NEC Fusion) on the Cisco AS5300

If you have an NEC PBX in your network and you are running FCCS, you will need to configure this device appropriately. FCCS, also known as NEC Fusion, allows individual nodes anywhere within a network to operate as if they were part of a single integrated PBX system. The database storage, share, and access routine of NEC Fusion allow real-time access from any node to any other, allowing individual nodes to “learn” about the entire network configuration. This capability allows network-wide feature, functional, operational, and administration transparency.

Figure 97 shows an example of an AS5300 Q.SIG signalling configuration using an NEC PBX.

Cisco IOS Multiservice Applications Configuration Guide

MC-417

Configuring Q.SIG PRI Signalling Support

Figure 97 Q.SIG Signalling Configuration with NEC PBX

Configuring Support for PBX Signalling Protocols

Step 1

Step 2

Step 3

NEC PBX

FCCS

T1 channel

Ethernet signaling

Cisco

AS5300

QoS

cloud

To configure NEC Fusion signalling support on the Cisco AS5300, use the following commands beginning in global configuration mode:

Command Purpose

Router(config)# controller T1 controller number

Enters controller configuration mode.

NEC Fusion does not support fractional T1/E1; all 24 channels must be available. If they are not available, the configuration request will fail.

Router(config-controller)# pri-group nec-fusion {pbx-ip-address/pbx-ip-host-name} pbx-port number

Configures the controller to communicate with an NEC PBX using NEC Fusion.

The range for the PBX port is 49152 to 65535. If you do not specify a port number, the default value of 55000 will be used. If this value is already in use, the next greater value will be used.

Router(config-controller)# exit

Exits controller configuration mode.

Cisco

AS5300

FCCS

T1 channel

Ethernet signaling

NEC PBX

28853

Verifying VoIP Q.SIG Software on the Cisco AS5300

After you complete the configuration for the AS5300, verify that you configured Q.SIG properly. Enter the show isdn status command to view the ISDN layer information. The following output shows that you have correctly designated the global ISDN switch type to be primary-Q.SIG.

router# show isdn status

Global ISDN Switchtype = primary-qsig ISDN Serial1:23 interface dsl 0, interface ISDN Switchtype = primary-qsig **** Slave side configuration **** Layer 1 Status: DEACTIVATED Layer 2 Status: TEI = 0, Ces = 1, SAPI = 0, State = TEI_ASSIGNED Layer 3 Status: 0 Active Layer 3 Call(s) Activated dsl 0 CCBs = 0 The Free Channel Mask: 0x7FFFFF

MC-418

Cisco IOS Multiservice Applications Configuration Guide

Configuring Support for PBX Signalling Protocols

Q.SIG for VoIP Configuration Example

The following configuration example configures interface serial 1:23 for Q.SIG PRI and to act as the Q.SIG slave:

! version 12.0 service timestamps debug uptime service timestamps log uptime no service password-encryption ! hostname as5300A ! ip subnet-zero ! isdn switch-type primary-qsig ! controller T1 0 shutdown ! controller T1 1 framing esf clock source line primary linecode b8zs pri-group timeslots 1-24 ! controller T1 2 shutdown ! controller T1 3 shutdown ! ! voice-port 1:D ! ! dial-peer voice 3001 pots destination-pattern 3001 port 1:D ! dial-peer voice 4001 pots incoming called-number 4001 direct-inward dial ! dial-peer voice 4002 voip destination-pattern 4001 session target ipv4:1.14.82.14 ! ! interface Ethernet0 ip address 1.14.82.13 255.255.0.0 no ip directed-broadcast ! interface 1:23 no ip address no ip directed broadcast isdn switch-type primary-qsig isdn protocol-emulate user isdn incoming-voice modem ! interface FastEthernet0 no ip address no ip directed-broadcast

Configuring Q.SIG PRI Signalling Support

Cisco IOS Multiservice Applications Configuration Guide

MC-419

+ 15 hidden pages