|
|
The gateway capability is the ability of the Cisco AS5300 to function as an H.323 endpoint. Therefore, the gateway provides: admission control, address lookup and translation, and accounting services.
User configuration and implementation of these features take place while setting up and configuring the gatekeeper and the gateway. See "Gatekeeper and Gateway Internetworking Configuration."
RAS is the acronym for Registration, Admission, and Status. The RAS signaling function performs registration, admissions, status, and disengage procedures between the VoIP gateway and gatekeeper.
Two new fields have been added to the dial-peer entry. The gateway relies on Cisco IOS command line interface commands, outside of gateway configuration mode, to configure handling of the AAA servers. See "Sample Gateway Configuration."
The following changes have been made to the gateway to enable the RAS implementation.
The technology prefix field is applicable to the dial-peer of the "voip" encapsulation type. This field is used to indicate to the gatekeeper the type of service that the outbound call is requesting. For a complete description of technology prefix see the "Technology Prefixes" section elsewhere in this manual.
The session target field of the VoIP dial-peer indicates the address of the remote gateway where the call is terminated. If RAS (Request, Admission, and Status) Protocol is used, the session target field is used to indicate that a gatekeeper needs to be consulted in order to translate an E164 address to an IP address.
The feature AAA represents Authentication, Authorization, and Accounting features which are required in the VoIP gateway. The standard Cisco Authentication, Authorization, and Accounting functionality is enhanced to allow calls to:
The AAA authentication feature permits RADIUS to be used to authenticate users (typically incoming calls) on the gateway. It is normally used with IVR to check the legitimacy of a prospective gateway user based on an account number (collected by IVR) or based on answer number identification, (ANI).
Authentication is based on RADIUS and is performed on the gateway (as opposed to the gatekeeper).
User account and PIN information is collected by the IVR application and is passed to the AAA interface. The AAA interface then makes a RADIUS authentication request with the given information and returns to the IVR application with status of success or failure.
RADIUS is an IETF protocol based on UDP. It functions by exchanging a set of attribute/value pairs between the client, here a VoIP gateway and a RADIUS server. Standard RADIUS server implementations include CiscoSecure, Cisco UCP, Livingston, and Merit.
An authenticated user is authorized. There is no authorization of specific user capabilities for the service provider voice applications.
Accounting uses a basic start-stop method and standard RADIUS attributes where possible. Attributes that cannot be mapped to standard RADIUS are packed into the Acct-Session-Id attribute field as '/' separated ASCII string.
Data items are collected for each call leg that gets created on the gateway. A call leg is the internal representation of a connection to the gateway. Each call that is made through the gateway consists of two call legs: an incoming and an outgoing call leg. The call leg information that is emitted by the gateway(s) can be correlated by their connection ID, which is the same for all call legs of a connection.
Standard RADIUS attributes supported are:
Nonstandard RADIUS attributes packed into the Acct-Session-Id are:
In order to take advantage of standard RADIUS implementations that do not support vendor specific attributes a new method is defined which embeds the unsupported information elements in the RADIUS Acct-Session-id. The Acct-Session-id field has a maximum length of 256 characters. It is defined to contain the RADIUS account session id which is a unique identifier that links accounting records associated with the same login session for a user. The internal representation of this field is long. Therefore, the value of this Session ID can become very large as the number of sessions on a router increases. In order to support additional fields we have defined the following string format for this field:
<session id>/<setupt time>/<gateway id>/<call origin>/<call type>/<connection id>/<connect time>/disconnect time>/<disconnect cause>| Field | Description |
|---|---|
<session id> | The standard RADIUS account session id |
<setup time> | The Q.931setup time for this connection in NTP format. |
<gateway id> | The name of the underlying gateway. Name string is of form |
<call origin> | Indicates origin of the call relative to the gateway. Possible values are "originate" and "answer". |
<call type> | Indicates call leg type. Possible values are: "Telephony" and "VoIP." |
<connection id> | A unique global identifier used to correlate call legs that belong to the same end to end call. The field consists of 4 long words (128 bits). each long word is displayed in hexadecimal value and separated by a space character. |
<connect time> | The Q.931 connect time for this call leg in NTP format. |
<disconnect time> | The Q.931 disconnect time for this call leg in NTP format. |
<disconnect cause> | Documented in Q.931 specification. Can be in the range of 1-160. |
NTP time formats are displayed as: %H:%M:%S.%k %Z %tw %tn %td %Y where:
Client-Id = 172.29.248.123 NAS-Port-Type = 0 User-Name = "4004" Called-Station-Id = "+111" Calling-Station-Id = "+222" Acct-Status-Type = Start User-Service-Type = Login-User Acct-Session-Id = "4/23:21:14.078 UTC Sat Jul 18 1998/ak3620-1.cisco.com/859BF275 D7C80001 0 3AFF4/originate/VoIP///" Acct-Delay-Time = 0
Client-Id = 172.29.248.123 NAS-Port-Type = 0 User-Name = "4004" Called-Station-Id = "+111" Calling-Station-Id = "+222" Acct-Status-Type = Stop User-Service-Type = Login-User Acct-Session-Id = "4/23:21:14.078 UTC Sat Jul 18 1998/ak3620-1.cisco.com/859BF275 D7C80001 0 3AFF4/originate/VoIP/23:21:14.093 UTC Sat Jul 18 1998/23:21:23.084 UTC Sat Jul 18 1998/4" Acct-Input-Octets = 8340 Acct-Output-Octets = 8900 Acct-Input-Packets = 417 Acct-Output-Packets = 445 Acct-Session-Time = 9 Acct-Delay-Time = 0
Client-Id = 172.29.248.123 NAS-Port-Type = 0 User-Name = "4004" Called-Station-Id = "+111" Calling-Station-Id = "+222" Acct-Status-Type = 3 User-Service-Type = Login-User Acct-Session-Id = "4/21:54:17.052 UTC Mon Jul 20 1998/ak3620-1.cisco.com/BF1AC9CA 8DE60006 0 5ED24/originate/VoIP///" Acct-Delay-Time = 0
The syslog accounting option exports the information elements associated with each call leg through a system log message which can be captured by a syslog daemon that is present on the network. The syslog output consists of the following:
<server timestamp> <gateway id> <message number> : <message label> : <list of AV pairs>
| Field | Description |
|---|---|
server timestamp | The timestamp created by the server when it receives the message to log. |
gateway id | The name of the gateway emitting the message. |
message number | The number assigned to the message by the gateway. |
message label | Is a string used to identify the message category. |
list of AV pairs | Is a string consisting of <attribute name> <attribute value> pairs separated by commas. |
%VOIPAAA-5-VOIP_CALL_HISTORY:CallLegType 2,ConnectionId 300094C0 60E0F3A0 60C894C0 60C90000, SetupTime 22:35:22.023UTC Tue Aug 11 1998, PeerAddress 999, PeerSubAddress , DisconnectCause 10 ,DisconnectText normal call clearing., ConnectTime 22:35:24.027 UTC Tue Aug 11 1998, DisconnectTime 22:35:29.028 UTC Tue Aug 11 1998, CallOrigin 1, ChargedUnits 0, InfoType 2,TransmitPackets 0, TransmitBytes 0, ReceivePackets 0, ReceiveBytes 0
The following new Cisco IOS commands are designed for configuring the Service Provider VoIP AAA functionality.
To define a method list called H.323 with RADIUS as a method.
This command line registers the H.323 method list (also referred to as h323 service) which has RADIUS as its only method in the router. The VoIP calls send all their authentication requests through the H.323 service. If this line does not exist in the router configuration VoIP authentication will not take place.
A significant difference in the usage of this command is that with Cisco IOS Release 11.3(T) the name of the method list is flexible and can be changed by the user. However, when using method list for configuring AAA with the VoIP service provider software, the method list is a specific name that you should not change.
The way method lists work in Cisco IOS software is that a list is defined using the aaa authentication login h323 radius command, and is then applied to an interface. For voice authentication, we never apply this list to any interface. When enabled, (using this command), it applies to all voice interfaces and its function is activated through the IVR application.
Global configuration.
The [no] form of this command is the default.
To define the accounting method list "H.323" with RADIUS as a method and with either stop-only or start-stop accounting options. Again, as in the authentication case, the method list has to be called "h323" and is activated for all voice interfaces.
This command line tells the system to create a method list called H.323 which has start-stop radius as its method. The h323 method list is static and is applied by default to all voice interfaces if the gw-accounting h323 command is also activated.
Global configuration.
The [no] form of this command is the default.
To enable or disable gateway specific accounting.
This command line defines a method for doing the accounting and enables the gateway to do the accounting. There are two accounting methods defined.
Both H.323 and Syslog can be enabled at the same time which causes CDRs to be generated in both methods.
Global configuration.
The [no] form of this command is the default.
To enable or disable debugging messages for gateway aaa to be output to the system console.
global exec.
The [no] form of this command is the default.
The Cisco IOS software AAA user interface can be configured to use the H.323 method as follows:
The authentication command line creates a method list named H.323 with RADIUS being its only member.
Also note that the accounting command line looks like a regular RADIUS accounting command line for connection accounting. Connection accounting has to be globally enabled using this command line. Start-stop or stop only methods may be used.
| Step | Command | Purpose |
|---|---|---|
| 1 | 5300> enable Password: <password> 5300# | Enter enable mode. Enter the password. You have entered enable mode when the prompt changes to |
| 2 | 5300# config term Enter configuration commands, one per line. End with CNTL/Z. 5300(config)# | Enter global configuration mode. You have entered global configuration mode when the prompt changes to |
| 3 | 5300(config)# aaa new-model | Initiates the AAA script. |
| 4 | 5300(config)# aaa authentication login h323 radius | Configures the router to use the H.323 method list for authentication purposes. |
| 5 | 5300(config)# aaa accounting connection h323 start-stop radius | Tells the system to use connection based accounting and the H.323 service. |
| 6 | 5300(config)# radius-server host 171.69.58.104 auth-port 165 acct-port 1646 | This command sets the server host IP address, and the ports for both the authentication service and the accounting service. |
| 7 | 5300(config)# radius-server key testing123 | Tests the connection accounting service. |
| 8 | 5300(config)# end | Ends the configuration session. |
aaa new-model aaa authentication local-override aaa authentication login default radius ! gw-accounting h323 ! radius-server host 10.90.1.1 auth-port 1645 acct-port 1646 radius-server key gte
This application provides basic Interactive Voice Response (IVR) capabilities necessary to collect caller Personal Identification Number (PIN), passwords, and destination phone numbers. IVR consists of simple voice prompting and digit collection to collect information from the caller for the purpose of authenticating the user and to identify the destination.
"Simple" IVR allows the use of one of several interactive voice response scripts which are embedded in Cisco IOS software. The ability to modify the embedded scripts is not yet provided. However, the audio files (for the prompts) can be modified for the user.
The user receives a voice prompt instruction to enter a specific type of information, for example, a PIN number. After playing the voice prompt, the IVR feature starts the process of collecting some number of touch tones (digit collection).
The IVR application specifies a sequence of voice prompts and touch-tone collection instructions. IVR applications can be assigned to specific ports, or can be invoked based on DNIS. An IP/PSTN gateway can have several different IVR applications to accommodate many different gateway services. The IVR applications can be customized to present different interfaces to the caller. The functionality includes the ability to:
ANI authorization is provided by two of the "canned" simple IVR scripts. Based on authentication of the ANI and DNIS for the call, the user is either denied service (with an appropriate voice message) or prompted for an account number and PIN if authentication fails. If authentication succeeds (or subsequent authentication with the supplied account/PIN succeeds), the user is prompted for the destination phone number and the call is placed.
The four current scripts are:
Fax hop on/off is a specialized IVR application to support the use of redialer boxes in fax applications. Redialers are small units which connect between a fax machine and a telephone line, intercept the phone number dialed by the fax machine, and then place an outgoing call to another phone number (in this case, that of the voice gateway) and then forward the destination number intercepted from the fax machine to the gateway when prompted. Optionally, an account number can be included to identify the caller's organization for authentication and billing purposes.
New Cisco IOS commands are available to handle IVR functionality. These commands are entered when the dial peer is being configured.
Used by the router to refresh an .au (audio) file in the memory. This is the file which contains the announcement prompt for the caller. The router will only load the .au file when the script is initially started, or on the router restart. If the .au file is changed, the user must run this EXEC command to reread the file. This will generate an error message if the file is not accessible, or if there is a format error. Presently the <URL> pointer refers to the directory where the flash memory is stored.
Example
audio-prompt load flash:enter_pin.au
Command Mode
Privileged EXEC (also called enable mode)
Selects the session application for IVR.
Dial peer configuration mode
Configuration file example:
application clid_authen_collect, CallID 90 got event IVR_EV-CALL_SETUP_IND : : ivr action: IVR_ACT_CALL_SETUP_ACK : : ivr action: IVR_ACT_CALL_PROCEEDING : : ivr action: IVR_ACT_CALL_CONNECT
Shows the list of the voice applications configured. A one line summary is displayed about each application.It defines the names of the audio files the script will play, the operation of the abort keys, what prompts are used and caller interaction. If this command is entered without entering the summary field, a detailed summary is displayed for the application named in the <app-name> field.
Privileged EXEC (also called enable mode)
Enter the show call application voice [<app-name>| command and insert the desired script name in the <app-name> field. The output displays a description of each script. For a brief description of the IVR scripts, see "ANI Authorization".
EXAMPLES:
The following examples show the summary status for the show call application voice <app name> command:
show call application voice clid_authensblab115>show call application voice clid_authen
Application clid_authen has 8 states with 0 calls active
State start has 1 actions and 5 events
Do Action IVR_ACT_AUTHENTICATE. accountName=ani, pinName=dnis
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
If Event IVR_EV_CALL_SETUP_IND do action IVR_ACT_CALL_SETUP_ACK
and goto state start
If Event IVR_EV_AAA_SUCCESS goto state collect_dest
If Event IVR_EV_AAA_FAIL goto state authenticate_fail
State end has 1 actions and 3 events
Do Action IVR_ACT_END.
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
If Event IVR_EV_CALL_DISCONNECT_DONE do action IVR_ACT_CALL_DESTROY
and do nothing
State collect_dest has 3 actions and 5 events
Do Action IVR_ACT_TONE. tone=8
Do Action IVR_ACT_COLLECT_DIALPLAN.
Do Action IVR_ACT_TERMINATION_KEY. terminationKey=#
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
If Event IVR_EV_DIAL_COL_SUCCESS goto state place_call
If Event IVR_EV_DIAL_COL_FAIL goto state collect_fail
If Event IVR_EV_TIMEOUT do action IVR_ACT_TONE
and goto state collect_fail count=0
State place_call has 1 actions and 4 events
Do Action IVR_ACT_PLACE_CALL.
destination= called=
calling= account=
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
If Event IVR_EV_CALL_UP goto state active
If Event IVR_EV_CALL_FAIL goto state place_fail
State active has 0 actions and 2 events
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
State authenticate_fail has 1 actions and 2 events
Do Action IVR_ACT_PLAY.
URL: flash:auth_failed.au
allowInt=0, pContent=0x0
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
State collect_fail has 1 actions and 2 events
Do Action IVR_ACT_PLAY.
URL: flash:collect_failed.au
allowInt=0, pContent=0x0
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
State place_fail has 1 actions and 2 events
Do Action IVR_ACT_PLAY_FAILURE_TONE.
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
show call application voice clid_authen_collectsblab115>show call application voice clid_authen_collect
Application clid_authen_collect has 10 states with 0 calls active
State start has 1 actions and 5 events
Do Action IVR_ACT_AUTHENTICATE. accountName=ani, pinName=dnis
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
If Event IVR_EV_CALL_SETUP_IND do action IVR_ACT_CALL_SETUP_ACK
and goto state start
If Event IVR_EV_AAA_SUCCESS goto state collect_dest
If Event IVR_EV_AAA_FAIL goto state get_account
State end has 1 actions and 3 events
Do Action IVR_ACT_END.
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
If Event IVR_EV_CALL_DISCONNECT_DONE do action IVR_ACT_CALL_DESTROY
and do nothing
State get_account has 4 actions and 7 events
Do Action IVR_ACT_PLAY.
URL: flash:enter_account.au
allowInt=1, pContent=0x60E4C564
Do Action IVR_ACT_ABORT_KEY. abortKey=*
Do Action IVR_ACT_TERMINATION_KEY. terminationKey=#
Do Action IVR_ACT_COLLECT_PATTERN. Pattern account is .+
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
If Event IVR_EV_PAT_COL_SUCCESS goto state get_pin
patName=account
If Event IVR_EV_ABORT goto state get_account
If Event IVR_EV_PLAY_COMPLETE do nothing
If Event IVR_EV_TIMEOUT goto state get_account count=0
If Event IVR_EV_PAT_COL_FAIL goto state get_account
State get_pin has 4 actions and 7 events
Do Action IVR_ACT_PLAY.
URL: flash:enter_pin.au
allowInt=1, pContent=0x0
Do Action IVR_ACT_ABORT_KEY. abortKey=*
Do Action IVR_ACT_TERMINATION_KEY. terminationKey=#
Do Action IVR_ACT_COLLECT_PATTERN. Pattern pin is .+
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
If Event IVR_EV_PAT_COL_SUCCESS goto state authenticate
patName=pin
If Event IVR_EV_PLAY_COMPLETE do nothing
If Event IVR_EV_ABORT goto state get_account
If Event IVR_EV_TIMEOUT goto state get_pin count=0
If Event IVR_EV_PAT_COL_FAIL goto state get_pin
State authenticate has 1 actions and 5 events
Do Action IVR_ACT_AUTHENTICATE. accountName=account, pinName=pin
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
If Event IVR_EV_AAA_SUCCESS goto state collect_dest
If Event IVR_EV_TIMEOUT do nothing count=0
If Event IVR_EV_AAA_FAIL goto state authenticate_fail
State collect_dest has 4 actions and 8 events
Do Action IVR_ACT_PLAY.
URL: flash:enter_destination.au
allowInt=1, pContent=0x0
Do Action IVR_ACT_ABORT_KEY. abortKey=*
Do Action IVR_ACT_TERMINATION_KEY. terminationKey=#
Do Action IVR_ACT_COLLECT_DIALPLAN.
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
If Event IVR_EV_PLAY_COMPLETE do nothing
If Event IVR_EV_ABORT goto state collect_dest
If Event IVR_EV_TIMEOUT goto state collect_dest count=0
If Event IVR_EV_DIAL_COL_SUCCESS goto state place_call
If Event IVR_EV_DIAL_COL_FAIL goto state collect_dest
If Event IVR_EV_TIMEOUT goto state collect_dest count=0
State place_call has 1 actions and 4 events
Do Action IVR_ACT_PLACE_CALL.
destination= called=
calling= account=
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
If Event IVR_EV_CALL_UP goto state active
If Event IVR_EV_CALL_FAIL goto state place_fail
State active has 0 actions and 2 events
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
State authenticate_fail has 1 actions and 2 events
Do Action IVR_ACT_PLAY.
URL: flash:auth_failed.au
allowInt=0, pContent=0x0
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
State place_fail has 1 actions and 2 events
Do Action IVR_ACT_PLAY_FAILURE_TONE.
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
sblab115>show call application voice clid_authen_collect
Application clid_authen_collect has 10 states with 0 calls active
State start has 1 actions and 5 events
Do Action IVR_ACT_AUTHENTICATE. accountName=ani, pinName=dnis
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
If Event IVR_EV_CALL_SETUP_IND do action IVR_ACT_CALL_SETUP_ACK
and goto state start
If Event IVR_EV_AAA_SUCCESS goto state collect_dest
If Event IVR_EV_AAA_FAIL goto state get_account
State end has 1 actions and 3 events
Do Action IVR_ACT_END.
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
If Event IVR_EV_CALL_DISCONNECT_DONE do action IVR_ACT_CALL_DESTROY
and do nothing
State get_account has 4 actions and 7 events
Do Action IVR_ACT_PLAY.
URL: flash:enter_account.au
allowInt=1, pContent=0x60E4C564
Do Action IVR_ACT_ABORT_KEY. abortKey=*
Do Action IVR_ACT_TERMINATION_KEY. terminationKey=#
Do Action IVR_ACT_COLLECT_PATTERN. Pattern account is .+
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
If Event IVR_EV_PAT_COL_SUCCESS goto state get_pin
patName=account
If Event IVR_EV_ABORT goto state get_account
If Event IVR_EV_PLAY_COMPLETE do nothing
If Event IVR_EV_TIMEOUT goto state get_account count=0
If Event IVR_EV_PAT_COL_FAIL goto state get_account
State get_pin has 4 actions and 7 events
Do Action IVR_ACT_PLAY.
URL: flash:enter_pin.au
allowInt=1, pContent=0x0
Do Action IVR_ACT_ABORT_KEY. abortKey=*
Do Action IVR_ACT_TERMINATION_KEY. terminationKey=#
Do Action IVR_ACT_COLLECT_PATTERN. Pattern pin is .+
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
If Event IVR_EV_PAT_COL_SUCCESS goto state authenticate
patName=pin
If Event IVR_EV_PLAY_COMPLETE do nothing
If Event IVR_EV_ABORT goto state get_account
If Event IVR_EV_TIMEOUT goto state get_pin count=0
If Event IVR_EV_PAT_COL_FAIL goto state get_pin
State authenticate has 1 actions and 5 events
Do Action IVR_ACT_AUTHENTICATE. accountName=account, pinName=pin
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
If Event IVR_EV_AAA_SUCCESS goto state collect_dest
If Event IVR_EV_TIMEOUT do nothing count=0
If Event IVR_EV_AAA_FAIL goto state authenticate_fail
State collect_dest has 4 actions and 8 events
Do Action IVR_ACT_PLAY.
URL: flash:enter_destination.au
allowInt=1, pContent=0x0
Do Action IVR_ACT_ABORT_KEY. abortKey=*
Do Action IVR_ACT_TERMINATION_KEY. terminationKey=#
Do Action IVR_ACT_COLLECT_DIALPLAN.
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
If Event IVR_EV_PLAY_COMPLETE do nothing
If Event IVR_EV_ABORT goto state collect_dest
If Event IVR_EV_TIMEOUT goto state collect_dest count=0
If Event IVR_EV_DIAL_COL_SUCCESS goto state place_call
If Event IVR_EV_DIAL_COL_FAIL goto state collect_dest
If Event IVR_EV_TIMEOUT goto state collect_dest count=0
State place_call has 1 actions and 4 events
Do Action IVR_ACT_PLACE_CALL.
destination= called=
calling= account=
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
If Event IVR_EV_CALL_UP goto state active
If Event IVR_EV_CALL_FAIL goto state place_fail
State active has 0 actions and 2 events
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
State authenticate_fail has 1 actions and 2 events
Do Action IVR_ACT_PLAY.
URL: flash:auth_failed.au
allowInt=0, pContent=0x0
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
State place_fail has 1 actions and 2 events
Do Action IVR_ACT_PLAY_FAILURE_TONE.
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
show call application voice clid_authen_npwsblab115>show call application voice clid_authen_npw
Application clid_authen_npw has 8 states with 0 calls active
State start has 1 actions and 5 events
Do Action IVR_ACT_AUTHENTICATE. accountName=ani, pinName=NULL
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
If Event IVR_EV_CALL_SETUP_IND do action IVR_ACT_CALL_SETUP_ACK
and goto state start
If Event IVR_EV_AAA_SUCCESS goto state collect_dest
If Event IVR_EV_AAA_FAIL goto state authenticate_fail
State end has 1 actions and 3 events
Do Action IVR_ACT_END.
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
If Event IVR_EV_CALL_DISCONNECT_DONE do action IVR_ACT_CALL_DESTROY
and do nothing
State collect_dest has 4 actions and 7 events
Do Action IVR_ACT_PLAY.
URL: flash:enter_destination.au
allowInt=1, pContent=0x0
Do Action IVR_ACT_ABORT_KEY. abortKey=*
Do Action IVR_ACT_TERMINATION_KEY. terminationKey=#
Do Action IVR_ACT_COLLECT_DIALPLAN.
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
If Event IVR_EV_PLAY_COMPLETE do nothing
If Event IVR_EV_ABORT goto state collect_dest
If Event IVR_EV_DIAL_COL_SUCCESS goto state place_call
If Event IVR_EV_DIAL_COL_FAIL goto state collect_fail
If Event IVR_EV_TIMEOUT goto state collect_fail count=0
State place_call has 1 actions and 4 events
Do Action IVR_ACT_PLACE_CALL.
destination= called=
calling= account=
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
If Event IVR_EV_CALL_UP goto state active
If Event IVR_EV_CALL_FAIL goto state place_fail
State active has 0 actions and 2 events
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
State authenticate_fail has 1 actions and 2 events
Do Action IVR_ACT_PLAY.
URL: flash:auth_failed.au
allowInt=0, pContent=0x0
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
State collect_fail has 1 actions and 2 events
Do Action IVR_ACT_PLAY.
URL: flash:collect_failed.au
allowInt=0, pContent=0x0
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
State place_fail has 1 actions and 2 events
Do Action IVR_ACT_PLAY_FAILURE_TONE.
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
show call application voice clid_authen_col_npwApplication clid_authen_col_npw has 10 states with 0 calls active
State start has 1 actions and 5 events
Do Action IVR_ACT_AUTHENTICATE. accountName=ani, pinName=NULL
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
If Event IVR_EV_CALL_SETUP_IND do action IVR_ACT_CALL_SETUP_ACK
and goto state start
If Event IVR_EV_AAA_SUCCESS goto state collect_dest
If Event IVR_EV_AAA_FAIL goto state get_account
State end has 1 actions and 3 events
Do Action IVR_ACT_END.
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
If Event IVR_EV_CALL_DISCONNECT_DONE do action IVR_ACT_CALL_DESTROY
and do nothing
State get_account has 4 actions and 7 events
Do Action IVR_ACT_PLAY.
URL: flash:enter_account.au
allowInt=1, pContent=0x0
Do Action IVR_ACT_ABORT_KEY. abortKey=*
Do Action IVR_ACT_TERMINATION_KEY. terminationKey=#
Do Action IVR_ACT_COLLECT_PATTERN. Pattern account is .+
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
If Event IVR_EV_PAT_COL_SUCCESS goto state get_pin
patName=account
If Event IVR_EV_ABORT goto state get_account
If Event IVR_EV_PLAY_COMPLETE do nothing
If Event IVR_EV_TIMEOUT goto state get_account count=0
If Event IVR_EV_PAT_COL_FAIL goto state get_account
State get_pin has 4 actions and 7 events
Do Action IVR_ACT_PLAY.
URL: flash:enter_pin.au
allowInt=1, pContent=0x0
Do Action IVR_ACT_ABORT_KEY. abortKey=*
Do Action IVR_ACT_TERMINATION_KEY. terminationKey=#
Do Action IVR_ACT_COLLECT_PATTERN. Pattern pin is .+
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
If Event IVR_EV_PAT_COL_SUCCESS goto state authenticate
patName=pin
If Event IVR_EV_PLAY_COMPLETE do nothing
If Event IVR_EV_ABORT goto state get_account
If Event IVR_EV_TIMEOUT goto state get_pin count=0
If Event IVR_EV_PAT_COL_FAIL goto state get_pin
State authenticate has 1 actions and 5 events
Do Action IVR_ACT_AUTHENTICATE. accountName=account, pinName=pin
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
If Event IVR_EV_AAA_SUCCESS goto state collect_dest
If Event IVR_EV_TIMEOUT do nothing count=0
If Event IVR_EV_AAA_FAIL goto state authenticate_fail
State collect_dest has 4 actions and 8 events
Do Action IVR_ACT_PLAY.
URL: flash:enter_destination.au
allowInt=1, pContent=0x0
Do Action IVR_ACT_ABORT_KEY. abortKey=*
Do Action IVR_ACT_TERMINATION_KEY. terminationKey=#
Do Action IVR_ACT_COLLECT_DIALPLAN.
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
If Event IVR_EV_PLAY_COMPLETE do nothing
If Event IVR_EV_ABORT goto state collect_dest
If Event IVR_EV_TIMEOUT goto state collect_dest count=0
If Event IVR_EV_DIAL_COL_SUCCESS goto state place_call
If Event IVR_EV_DIAL_COL_FAIL goto state collect_dest
If Event IVR_EV_TIMEOUT goto state collect_dest count=0
State place_call has 1 actions and 4 events
Do Action IVR_ACT_PLACE_CALL.
destination= called=
calling= account=
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
If Event IVR_EV_CALL_UP goto state active
If Event IVR_EV_CALL_FAIL goto state place_fail
State active has 0 actions and 2 events
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
State authenticate_fail has 1 actions and 2 events
Do Action IVR_ACT_PLAY.
URL: flash:auth_failed.au
allowInt=0, pContent=0x0
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
State place_fail has 1 actions and 2 events
Do Action IVR_ACT_PLAY_FAILURE_TONE.
If Event IVR_EV_DEFAULT goto state end
If Event IVR_EV_CALL_DIGIT do nothing
IVR debug messages will be displayed when a call is being actively handled by the IVR scripts. There are two types of messages:
Error output should only occur if something is not working or an error condition has been raised. States output supplies information about the current status of the IVR script and the different events which are occurring in that state.
Debug
This command is used for debugging the call control API.
Debug
This command is used for debugging H.323 call control.
Debug
The purpose of this feature is to support the redirecting call feature of the VoIP Gateway. The redirecting number is an optional field of the Q.931 Setup message.
When a local exchange carrier (LEC) switch detects an incoming call that is destined for a busy or nonanswering party, the switch formulates a Q.931 Setup message with redirecting number field set to the originally called number, and sends it to the Gateway. The called party number of the Setup message will be set to one of the service access numbers dialed number identification service (DNIS) of the gateway.
If a redirect number is present on an incoming call, then it is used in place of the called number (DNIS).
The dial peer configuration for ISDN redirect involves setting up two audio scripts.
To process incoming ISDN voice calls, incoming dial peers need to be configured. The DNIS number of the incoming call is used to match the DNIS number field of the incoming dial peer. The direct-inward-dial flag of the dial peer determines whether a second dial tone is given to the caller to collect the target destination number. For this Cisco service provider feature, the DNIS is set to the access phone number of the Gateway, and the direct-inward-dial flag is set to TRUE.
The outgoing dial peer is selected based on the DNIS number of the incoming call. The outgoing dial peer indicates the session target of the outgoing call.
The Rotary Calling Pattern feature, also known as backoff hairpinning, provides the ability to route an incoming call arriving via a telephony interface back out via another telephony interface under certain circumstances. This is primarily used to provide reliable service during network failures. Call establishment via Rotary Call Pattern will be supported via rotary group support of dial peers, where multiple dial peers may match a given destination phone number and will be selected in sequence. Support for Rotary Call Pattern of calls active at the time of the network failure is not provided.
In prior releases of VoIP, if you wanted the system to search through a number of destinations, when a given number is dialed, you needed to configure those dial peers with the same destination pattern. Now with the Rotary Call Pattern feature, if you want the destinations to be tried in a certain order, you can assign preference (via the preference command, see "Rotary Commands") to the dial peers to reflect that order.
For example, if you wish a call processing sequence to go to destination A first, then destination B second, and third to destination C; you would assign preference (0 being the highest priority) to the destinations in the following order:
If there are several dial peers that match a particular destination pattern, the system attempts to place a call to the one with the highest preference. If the call cannot be completed because of a system outage, for example, the gatekeeper or gateway cannot be contacted, the Rotary feature performs the following tasks:
The preference command is used to indicate the preference order for matching dial peers in a rotary group. It is useful in selecting the desired dial peer when multiple dial peers are matched for a dial string.
dial-peer config mode
preference <value>---an integer value [0..10]
value 0 [0 - 10]
(highest preference = 0)
The [no] form of this command does not assign a value.
The following examples show different dial peer configurations using the preference command.
Example 1
Dialpeer destpat preference session-target 1 4085271048 0 (highest) jmmurphy-voip 2 408527 0 sj-voip 3 408527 1 (lower) backup-sj-voip 4 .......... 1 0:D (interface) 5 .......... 0 anywhere-voip
If the called number is 4085271048, the order of attempts will be 1,2,3,5,4.
Example 2
Dialpeer destpat preference 1 408527 0 2 4085271048 1 3 4085271 0 4 ..............4085271.........0
The number dialed is 4085271048, the order will be 2, 3, 4, 1.
Channel associated signaling (CAS) is the transmission of signaling information within the voice channel. Various types of CAS signaling are available in the T1 world. The most common forms of CAS signaling are loop-start, ground-start, and E&M. The biggest disadvantage of CAS signaling is the use of user bandwidth to perform signaling functions. CAS signaling is often referred to as robbed-bit-signaling because user bandwidth is being `robbed' by the network for other purposes. In addition to receiving and placing calls, receipt of DNIS and ANI information is processed through CAS signaling. This particular information (DNIS and ANI) is used to support authentication and other functions that use this information.
T1 Channel Associated Signaling (CAS) capabilities have been implemented on the Cisco AS5300 voice feature card to support common central office and PBX configurations for voice calls. The development of this feature is to enhance and integrate T1 CAS capabilities on the DSPM (DSP Module) in order to support central office (CO) and PBX configurations for voice calls.
The service provider application for T1 CAS of course includes connectivity to the public network using T1 CAS from the Cisco AS5300 to the end office switch. In this configuration, the Cisco AS5300 captures the Dialed Number or called party number information and passes it along to the upper level applications, for IVR script selection, modem pooling, and other applications. Service Providers also require access to calling party number, ANI, for user identification, for billing account number, and in the future, more complicated call routing.
Service Providers implementing Voice over IP include traditional voice carriers, new voice and data carriers, and existing Internet Service Providers. Some of these service providers may use subscriber side lines for their VoIP connectivity to the PSTN, others will use tandem-type service provider connections.
The new functionality of T1 CAS for voice includes all the T1 CAS and E1/R1 signaling already supported for the Cisco AS5300 in data applications, with the addition of dialed number and calling party number captured whenever available.
The implementation of this feature supports the following T1 CAS signaling systems for VoIP application:
Internet Service Providers can provide switched 56 kbps access to their customers using the Cisco AS5300. The subset of T1 CAS (Robbed Bit) supported features are listed as follows:
Because T1 CAS is not new to the voice and telephony industry, existing Cisco documentation describes the functionality. See the following Cisco CCO URLs for supporting documentation.
End user interface resembles the end user interface for T1 CAS for Cisco AS5300 MICA dial.
This section documents the changes to existing commands for T1 CAS.
The cas-group controller configuration command has four attributes: <tone>, <digroup>, service, and <voice>.
To configure channelized T1 timeslots with robbed bit signaling, use the cas-group controller configuration command. Use the no form of this command to disable channel associated signaling for one or more timeslots.
cas-group channel timeslots range type signal
channel | Specifies a single channel group number, which can be between 0 and 23. |
timeslots range | Specifies a timeslot range of values from 1 to 24. |
type signal | Specifies the type of robbed bit signaling. Choose one of the following signal types to configure: · e&m-fgb dtmf [dnis] · e&m-fgd dtmf [dnis] · e&m-immediate-start---Specifies ear and mouth channel signaling with immediate start support. · fxs-loop-start--- Specifies Foreign Exchange Station loopstart signaling support. · fxs-ground-start---Specifies Foreign Exchange Station ground start signaling support. · sas-loop-start---Specifies Special Access Station loopstart signaling support. · sas-ground-start---Specifies Special Access Station ground start signaling support. |
Controller configuration.
This command first appeared in Cisco IOS Release 11.2.
Use this command to enable an integrated modem to receive and transmit incoming and outgoing call signaling (such as on-hook and off-hook) through each T1 controller.
The following example configures all 24 channels with ear and mouth robbed bit signaling with feature group B support:
router(config)# controller T1 0
router(config-controller)# cas-group 1 timeslots 1-24 type e&m-fgb
router(config-controller)# %DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 1 is up %DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 2 is up %DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 3 is up %DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 4 is up %DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 5 is up %DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 6 is up %DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 7 is up %DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 8 is up %DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 9 is up %DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 10 is up %DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 11 is up %DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 12 is up %DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 13 is up %DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 14 is up %DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 15 is up %DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 16 is up %DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 17 is up %DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 18 is up %DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 19 is up %DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 20 is up
The following example configures the required signaling to support modem pooling and the digital number identification service (DNIS) over channelized T1 lines on a Cisco AS5300. Supported tone types and signaling include E&M feature group B, DTMF tones, and MF tones. By configuring DNIS as part of the cas-group command, the system can collect DNIS digits for incoming calls, which can be redirected to specific modem pools setup for different customers or uses. Additionally, you must be running MICA modems in the system and have at least 10% of your total modems in the default modem pool. Free modems are needed in the default pool to detect the incoming called number or DNIS before handing the call off to the appropriate modem pool. Therefore, two modems are actually needed to handle one incoming call that is destined for a modem pool.
router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z. router(config)# controller t1 0
router(config-controller)# cas-group 0 timeslots 1-24 type e&m-fgb dtmf dnis
router(config-controller)# exit
router(config)# router(config)# modem-pool accounts1
router(config-modem-pool)# pool-range 30-50
router(config-modem-pool)# called-number 2000 max-conn 21
router(config-modem-pool)# exit
router(config)#
The sample configuration is only intended as an example of how to use the commands to configure T1 CAS. It is not an example of a complete configuration for setting up the entire signaling for a telco network.
The following sample configuration is an example of how to configure the voice ports as a cas-group for the channelized T1 lines.
| Step | Command | Purpose | ||
|---|---|---|---|---|
| 5300> enable Password: <password> 5300# | Enter enable mode. Enter the password. You have entered enable mode when the prompt changes to | ||
| 5300# config term Enter configuration commands, one per line. End with CNTL/Z. 5300(config)# | Enter global configuration mode. You have entered global configuration mode when the | ||
| 5300(config)# controller t1 0 | Enter controller configuration mode to configure your controller port. The controller ports are labeled 0 through 3 on the Quad T1/PRI and E1/PRI cards. | ||
| 5300(config-controller)# framing esf | Enter your telco's framing type. | ||
| 5300(config-controller)# clock source line primary | Enter the clock source for the line. Configure other lines as clock source secondary or internal. Note that only one PRI can be clock source primary and one PRI can be clock source secondary. | ||
| 5300(config-controller)# linecode b8zs | Enter your telco's line code type. | ||
| 5300(config-controller)# cas-group 1 timeslots 1-24 type e&m-fgb dtmf dnis | Configure all channels for E&M, FXS, and SAS analog signaling. Enter 1-24 for T1. If E1, enter 1-31. Signaling types include e&m-fgb, e&m-fgd, e&m-immediate-start, fxs-ground-start, fxs-loop-start, sas-ground-start, and sas-loop-start. Note: To set up e&m-fgb to support modem pooling, see step 8 in this table. You must use the same type of signaling that your central office uses. For E1 using the Anadigicom converter, use cas e&m-fgb signaling. | ||
| 5300(config-controller)# controller t1 1 5300(config-controller)# framing esf 5300(config-controller)# linecode b87s 5300(config-controller)# clock source line secondary 5300(config-controller)# cas-group 2 timeslots 1-24 type e&m-fgb | Repeat steps 3 to 7 to configure each additional controller (there are four). In this example, note that the controller number is 1, instead of 0. The clock source is secondary, instead of primary. The cas-group is 2, instead of 1. | ||
| 5300(config-controller)# controller T1 2 5300(config-controller)# clock source internal 5300(config-controller)# cas-group 0 timeslots 1-24 type r1-modified ani-dnis |
| ||
| 5300(config-controller)# controller T1 3 5300(config-controller)# clock source internal |
| ||
| 5300(config-controller)# Ctrl-Z | Return to enable mode. | ||
| 5300(config-controller)# dial-peer voice 3070 pots destination-pattern +30... port 0:1 prefix 30 | Enter the dial peer configuration mode to configure a POTS peer. | ||
| 5300(config-controller)# dial-peer voice 4080 pots destination-pattern +40... direct-inward-dial port 1:1 prefix 40 | Specify destination pattern, and direct inward dial for each POTS peer. | ||
| 5300(config-controller)# dial-peer voice 1050 pots destination-pattern +10... direct-inward-dial prefix 50 | Specify the destination pattern and the direct inward dial for the dial peer. | ||
| 5300(config-controller)# dial-peer voice 2060 pots destination-pattern +20... direct-inward-dial prefix 60 | Specify the destination pattern and the direct inward dial for the dial peer. | ||
| 5300(config-controller)# dial-peer voice 5050 voip answer-address 10... destination-pattern +50... |
| ||
| 5300(config-if)# Ctrl-Z 5300# %SYS-5-CONFIG_I: Configured from console by console | Return to enable mode. This message is normal and does not indicate an error. |
To verify your controller is up and running and no alarms have been reported:
5300# sh cont t1 2
T1 2 is up.
No alarms detected.
Version info of slot 0: HW: 2, Firmware: 16, PLD Rev: 0
Manufacture Cookie Info:
EEPROM Type 0x0001, EEPROM Version 0x01, Board ID 0x42,
Board Hardware Version 1.0, Item Number 73-2217-4,
Board Revision A0, Serial Number 06467665,
PLD/ISP Version 0.0, Manufacture Date 14-Nov-1997.
Framing is ESF, Line Code is B8ZS, Clock Source is Internal.
Data in current interval (269 seconds elapsed):
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
If you are having trouble:
Make sure the show controller t1 output is not reporting alarms or violations.
All of the Service Provider for VoIP features are configured when setting up the gatekeeper and gateway internetworking configuration. The example configurations provided in this documentation are supplied for reference only.
Before you can configure your Cisco AS5300 for Service Provider Features, ensure you have the following installed:
These configuration tasks are based on the assumption that all necessary tasks and configurations have been performed as described in the document Voice Over IP for the Cisco AS5300 Software Configuration Guide, which includes the following topics:
The SNMP MIBS are available on CCO. The CISCO-VOICE-DIAL-CONTROL-MIB supports the QoV and QoS of VoIP calls. Refer to the online support reference listed at the following location:
This is an example of the configuration steps required to allow the internetworking functionality between the VoIP gateway and the gatekeeper.
Configuration
Step 1 To enable the gateway, enter the following commands:
5300# config term
5300-1(config)# gateway
Step 2 Configure the interface. Only one interface is allowed to be the gateway interface.
The user can select either the interface that is connected to the gatekeeper, or a loopback interface. The interface that is connected to the gatekeeper is usually a LAN interface (That is, Fast Ethernet, Ethernet, FDDI, or Token-Ring). In this example, the fast Ethernet interface is used.
Step 3 Enable the interface as an H.323 Gateway VoIP Interface.
An interface is identified as a Gateway VoIP interface when the following commands are entered in the interface in configuration mode:
as5300-1(config)#
%SYS-5-CONFIG_I: Configured from console by console
as5300-1(config)# int fa0
as5300-1(config-if)# h323 voip interface
Step 4 Specify an H.323 ID for this interface.
An H.323 ID specifies the ID used by this gateway when this gateway communicates with the gatekeeper. Usually, this H.323 ID is the name given to the gateway with the gatekeeper domain name appended.
For example, if the name of this gateway is voip1, and this gateway is in the domain called vm1lab, then the H.323 ID will be voip1@vm1lab.
Step 5 To specify the gateway H.323 ID, use the following command:
as5300-1(config)#
%SYS-5-CONFIG_I: Configured from console by console
as5300-1(config)# int fa0
as5300-1(config-if)# h323-gateway voip h323-id voip1@vm1lab
Step 6 Specify a technology prefix.
A technology prefix is used to identify a type of service that this gateway is capable of providing.
For example, if this gateway is connected to a Voice Mail server, and if the technology prefix that indicates voice mail service is "7#", then the following command will specify this service:
as5300-1(config)#
%SYS-5-CONFIG_I: Configured from console by console
as5300-1(config)# int fa0
as5300-1(config-if)# h323-gateway voip tech-prefix 7#
To disable a technology prefix, use the no prefix.
Step 7 Identify a gatekeeper.
This is an optional command to identify the name of the gatekeeper that this gateway wants to communicate to. If this command is not given, the gateway will use multicast to find the gatekeeper. If HSRP and the unicast address method are used, specify the virtual address shared by primary and backup gatekeepers (see "Configure the Primary Gatekeeper" and "Configure the Backup Gatekeeper").
The syntax of this command follows:
h323 voip id <name_of_the_gatekeeper> [multicast | ipaddr A.B.C.D [port <number>]
For example:
(a) Identify a gatekeeper id and use multicast:
(b) Identify a gatekeeper id and use a unicast address:
(c) Identify a gatekeeper id and specify both unicast address and port:
Step 8 To find the current registration status of the gateway, use the following show command:
as5300-1# sh gateway
If the gateway is not registered with any gatekeeper, the show command will indicate the above status. If the gateway is registered with a gatekeeper, the show command will indicate:
as5300-1# sh gateway
Step 9 Determine the dial peer change.
This is an example of a dial-peer that uses RAS
5300-1# sh dial-peer vo 1234
VoiceOverIpPeer1234
The following display is shown:
tag = 1234, destination-pattern = 1234',
answer-address = ',
group = 1234, Admin state is up, Operation state is up,
incoming called-number = ', connections/maximum = 0/unlimited,
application associated:
type = voip, session-target = ras',
technology prefix: 8#
ip precedence = 0, UDP checksum = disabled,
session-protocol = cisco, req-qos = controlled-load,
acc-qos = best-effort,
fax-rate = voice, codec = g729r8,
Expect factor = 10, Icpif = 30,
VAD = enabled, Poor QOV Trap = disabled,
Connect Time = 0, Charged Units = 0,
Successful Calls = 0, Failed Calls = 0,
Accepted Calls = 0, Refused Calls = 0,
Last Disconnect Cause is "",
Last Disconnect Text is "",
Last Setup Time = 0.
The differences between this dial-peer and a normal VoIP dial-peer are:
|
|