Table of Contents

Using MFCR2 Outpulse Rule Tokens

Example #1—Incoming Call Using Inpulse Rules
Example #2—Incoming Call Using $68 Host Command
Example #3—Outgoing Call

R2 Signaling Examples

This chapter provides examples of R2 signaling that use the following call control elements:

Using MFCR2 Outpulse Rule Tokens

MFCR2 outpulse rule tokens include the following tones:

• Forward tones—These tones fall into Groups I and II. All Group I and II tones use the ITU R2 forward group tone frequencies. Most of the tones in Group I are used for addressing and identification. Group II tones give information about the origin of the call. Group II tones are also sent by an outgoing MFCR2 service circuits in response to one of the following backward signals.
  
  
• Change over to the reception of Group B signals.
  
  
• Send calling party's category.
  
  
• Backward tones—These tones fall into Groups A, B, and C. The Group A tones acknowledge Group I forward signals. Under certain conditions, Group A tones also acknowledge Group II tones. Group B tones convey the following information to an outgoing MFCR2 register.
  
  
• The condition of the switch equipment in the incoming exchange.
  
  
• The condition of the called subscriber's line.
  
  

These tones correspond to Category and Fields in the following manner.

Example #1—Incoming Call Using Inpulse Rules

Example #1 illustrates a simple R2 digit collection scenario after an incoming seize on the VCO/4K system E1 circuit at port address $00 61. A Venezuela specific inpulse rule is executed to perform R2 digit collection on this circuit.

The inpulse rule performs the following general tasks:

• Collects an unspecified number of called party number digits and stores them in Field 1. A-1 (send next digit) signals prompt the network register for each new digit. When an I-15 digit is received, the system sends an A-5 (send category), then sends an A-9 (send calling party digits).
  
  
• Collects the Group II signal and calling party number and stores it in the ANI number field. C-1 signals (send calling party's number) prompt the network register for each new digit. After the digits are received, the system sends an A-3 (send Group II) digit.
  
  
• Collects the Group II signal (1 digit) and stores it in Field 3. After the Group II signal is collected, the system sends a B-6 (set up speech conditions) digit.
  
  

At the end of this example, the system establishes speech conditions with the connected equipment (network register) and generates an Inpulse Rule Complete ($DD) report to the host. The processing flow for this example is shown in Figure 4-1. In this example, it is assumed that the Venezuela specific inpulse rule for the incoming circuit has been defined as inpulse rule #1 (shown below).

Refer to the Cisco VCO/4K System Administrator's Guide for more information about specific MFCR2 inpulse rule tokens.

Example #2—Incoming Call Using $68 Host Command

Example #2 also illustrates a simple R2 digit collection scenario on an incoming E1 circuit (port address $00 61). However, all R2 digit collections in this scenario are initiated by host command; no inpulse rule processing is used. Three MF Collection Control ($68) commands perform the following actions.

• Collect an unspecified number of called party number digits until I-15 digit is received, then send an A-5 to get the Group II signal.
  
  
• Collect the Group II signal followed by an unspecified number of calling party's digits until the I-15 digit is received by sending back A-1, then send back A-3 to get the Group II signal tone.
  
  
• Collect the Group II signal tone, then send a B-6 (set up speech conditions) digit.
  
  

An MF Digit ($D0) report reports each digit collection to the host.

At the end of this example, the system establishes speech conditions with the connected equipment (network register). The processing flow for this example is shown in Figure 4-4.

Refer to the Cisco VCO/4K Standard Programming Reference and the Cisco VCO/4K Extended Programming Reference for more information about the $68 command and the $D0 report.

Example #3—Outgoing Call

Example #3 describes R2 digit outpulsing on an E1 circuit at port address $00 40. This scenario involves both host command and outpulse rule processing. The host initiates the outpulsing using an Outgoing Port Control ($69) command that populates the digit fields and specifies the outpulse rule to execute (refer to the Cisco VCO/4K Standard Programming Reference or the Cisco VCO/4K Extended Programming Reference for a command description).

The outpulse rule performs the following actions.

• Seizes out on the E1 trunk at port address $00 40 and waits for a wink signal (executing the WAIT SUP W preconfigured answer supervision template documented in the Cisco VCO/4K System Administrator's Guide).
  
  
• Outpulses five digits of the called party number (stored in Field 1) after wink signal is detected. The system responds to A-1 (send next digit) signals that request each new digit.
  
  
• Outpulses the Group II signal and calling party number stored in the ANI field when an A-6 digit is received.
  
  
• Outpulses the Group II signal digit specified in the rules OP CAT token in response to an A-3.
  
  

This rule is shown below.

At the end of this example, the system establishes speech conditions with the connected equipment (network register) and generates an Outgoing Port Change of State ($DA) report to the host indicating the final backward digit. The processing flow for this example is shown in Figure 4-7 through Figure 4-9.

Refer to the Cisco VCO/4K System Administrator's Guide for more information about OP MFCR2, OP ANI, OP FIELD [xx], and OP CAT [xx] outpulse rule tokens.

Posted: Sat Sep 28 22:11:30 PDT 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.