|
|
This chapter shows you how to configure Settlement for Packet Telephony. The Cisco Settlement for Packet Telephony feature equips Cisco conferencing infrastructure products to use third-party settlement systems on multiple protocols. The Settlement for Packet Telephony feature allows Internet telephony service providers to do the following:
The Settlement for Packet Telephony feature complies with the ETSI Technical Specification (TS) 101 321.
This chapter contains the following sections:
For a complete description of the commands used in this chapter, refer to the Cisco IOS Multiservice Applications Command Reference publication. To locate documentation of other commands that appear in this chapter, use the command reference master index or search online.
When you make a telephone call, the cost charged can be divided between different carriers involved in the completion of the call. Settlement is the method used to divide the cost among carriers. Traditionally, settlement agreements have been arranged between the carriers in a pairwise fashion. With the advance of voice and video conferencing over IP, pairwise settlement agreements have become cumbersome. A number of companies have entered the market offering settlement on a subscription basis. As a result, the settlement process has become a more manageable, many-to-one system, with a set of public interfaces that service providers implement.
The Cisco gateway-based Settlement protocol interacts between carriers to create a single authentication at initialization. The authentication is the basis for the establishment of a secure communication channel between the Settlement system and the infrastructure component. This channel then allows the following three types of transactions to be handled:
Figure 63 shows a typical gateway-based settlement setup. A voice or fax call is originated and routed through the gateway (Cisco AS5300 access server, or Cisco 2600 or 3600 series routers) to a database server (RADIUS or TACACS+) for user authentication and intra-ISP call accounting. Using TCL IVR scripts to gather and manipulate the caller data, the gateway forwards the call to the settlement server, which authorizes the call and adds settlement details in a token. The call, now carrying its unique settlement token, passes through the originating gateway to the terminating gateway. The terminating gateway uses TCL IVR to validate the settlement token and forwards the call to the receiving telephone or fax machine.
 |
Note For a complete description of the IVR feature, see the "Configuring Interactive Voice Response" chapter. |
When the call is completed, both the terminating and originating gateways communicate the call details to the Settlement server. The Settlement server then reconciles the information it receives about the call from both gateways.
Before you can configure your access server platform (Cisco AS5300, Cisco 3600, or other supported voice platform) with the Settlement for Packet Telephony feature, perform the following tasks:
To configure settlement for packet telephony, perform the following tasks:
|
Note Ensure that you have secure communication between the access platform or router and the Settlement server. |
To configure the PKI, use the following commands beginning in privileged EXEC mode:
| Command | Purpose | |||
|---|---|---|---|---|
Step 1 | Router# configure terminal | Enters global configuration mode. | ||
Step2 | Router(config)# no crypto ca id name | Clears the old certificate if one exists. | ||
Step3 | Router(config)# crypto key zeroize rsa | Clears the existing RSA key. | ||
Step4 | Router(config)# hostname router-name | Configures the router hostname if this has not been done already. | ||
Step5 | Router(config)# ip domain-name domain-name | Configures the router's IP domain name. | ||
Step6 | Router(config)# crypto ca identity name | Enters CA-identity configuration mode and declares a Certification Authority (CA) name. For example, the CA name could be fieldlabs.cisco.com. | ||
Step7 | Router(ca-identity)# enrollment url url | Uses a nonstandard cgi-bin script location URL.
| ||
Step8 | Router(ca-identity)# enrollment retry count number | (Optional) Specifies how many times the router will send unsuccessful certificate requests before giving up. | ||
Step9 | Router(ca-identity)# enrollment retry period minutes | (Optional) Specifies the amount of time (in minutes) that the router waits to receive a certificate from the CA. If the router doe not receive a certificate within a specified period of time (the retry period), the router will send another certificate request. | ||
Step10 | Router(ca-identity)# exit | Exits CA-identify configuration mode. | ||
Step11 | Router(ca-identity)# crypto ca authenticate name | Obtains the CA public key. Use the same name that you used when declaring the CA with the crypto ca identify command. | ||
Step12 | Router(config)# crypto key generate rsa | Generates the RSA key pair. | ||
Step13 | Router(config)# crypto ca enroll name | Obtains the router certificate for all your RSA key pairs.
|
|
NoteIf your router reboots after you issue the crypto ca enroll command but before you receive the certificate, you must reissue the command. |
To configure the originating gateway to use the Settlement for Packet Telephony feature, use the following commands beginning in privileged EXEC mode:
| Command | Purpose | |
|---|---|---|
Step1 | Router# configure terminal | Enters global configuration mode. |
Step2 | Router(config)# settlement number | Enters Settlement configuration mode and configures the Settlement provider number. |
Step3 | Router(config-settlement)# type osp | Configures the Settlement provider type. In this release, OSP is the only type available. |
Step4 | Router(config-settlement)# url url | Enters the Settlement provider URL for the ISP hosting the Settlement server. |
Step5 | Router(config-settlement)# no shut | Brings up the Settlement provider. |
|
NoteIf you are configuring a TransNexus server, first enter the url command, then enter the customer-id and the device-id commands. |
To configure the inbound POTS dial peer, use the following commands beginning in privileged EXEC mode:
| Command | Purpose | |||
|---|---|---|---|---|
Step1 | Router# configure terminal | Enters global configuration mode. | ||
Step2 | Router(config)# dial-peer voice number pots | Enters dial-peer configuration mode to configure a POTS dial peer.
| ||
Step3 | | Associates the IVR TCL script application with the incoming POTS dial peer. | ||
Step4 |
| Defines the telephone number associated with this dial peer. | ||
Step5 | | Defines the voice port associated with this dial peer. |
To configure the outbound VoIP dial peer, use the following commands beginning in global configuration mode:
| Command | Purpose | |||
|---|---|---|---|---|
Step1 | Router(config)# dial-peer voice number voip | Enters dial-peer configuration mode to configure the outbound VoIP dial peer.
| ||
Step2 |
| Defines the telephone number associated with this dial peer. | ||
Step3 | Router(config-dial-peer)# session target settlement | Configures settlement as the target to resolve the terminating gateway address. |
|
NoteThe originating gateway system clock must synchronize with the settlement server clock. Use the clock or ntp command to set the router clock. |
 |
CautionIf the terminating gateway is not configured to use TCL IVR application scripts, the Settlement tokens are bypassed, calls can get through, and Settlement calls will not be audited; therefore, you will not be notified that the calls are not going through the billing service. |
To configure the terminating gateway, use the following commands beginning in global configuration mode:
| Command | Purpose | |
|---|---|---|
Step1 | Router(config)# settlement number | Enters Settlement configuration mode and configures the Settlement provider number. |
Step2 | Router(config-settlement)# type osp | Configures the Settlement provider type. In this release, OSP is the only type available. |
Step3 | Router(config-settlement)# url url | Enters the Settlement provider URL for the ISP hosting the Settlement server. |
Step4 | Router(config-settlement)# no shut | Brings up the Settlement provider. |
|
NoteIf you are configuring a TransNexus server, enter the url command, then enter the customer-id and device-id commands. |
To configure the inbound VoIP dial peer, perform the following tasks beginning in global configuration mode:
| Command | Purpose | |||
|---|---|---|---|---|
Step1 | Router(config) | Enters the dial-peer configuration mode to configure the inbound VoIP dial peer.
| ||
Step2 | | Associates the IVR TCL script application with the inbound VoIP dial peer. | ||
Step3 | | Defines the telephone number associated with the voice port for this dial peer. | ||
Step4 | Router(config-dial-peer)# | Enters the Settlement as the target to resolve the terminating gateway address. |
To configure the outbound POTS dial peer, use the following commands beginning in global configuration mode:
| Command | Purpose | |
|---|---|---|
Step1 | Router(config)# dial-peer voice number pots | Enters dial-peer configuration mode to configure the outbound POTS dial peer. The number value of the dial-peer voice pots command is a tag that uniquely identifies the dial peer. |
Step2 |
| Defines the telephone number associated with this dial peer. Use the called number for the string argument. |
Step3 | Router(config-dial-peer)# port port-number | Associates the dial peer with a specific voice port. |
|
NoteThe terminating gateway system clock must synchronize with the Settlement server clock. Use the clock or ntp command to set the router clock. |
You can verify the Settlement for Packet Telephony feature configuration by performing the following tasks:
The following example shows settlement configurations for both the originating and terminating gateways. Figure 64 shows the topology for these configuration examples.
The following output displays the configuration for the originating gateway; this output was creating by using the show running configuration command:
! version 12.0 service timestamps debug uptime service timestamps log uptime no service password-encryption service internal service udp-small-servers service tcp-small-servers ! hostname c3620-px15 ! ip subnet-zero ! settlement 0 type osp url http://xxx.xxx. ! voice-port 1/0/0 alerting audible ! voice-port 1/0/1 alerting audible ! dial-peer voice 1 pots application session destination-pattern 5551111 port 1/0/0 ! dial-peer voice 2 voip destination-pattern 5552222 session target settlement: ! interface Ethernet0/0 ip address 172.22.65.131 255.255.255.224 no ip directed-broadcast ip route-cache same-interface standby 1 priority 110 ! interface Serial0/0 no ip address no ip directed-broadcast shutdown ! interface Ethernet0/1 no ip address no ip directed-broadcast shutdown ! router eigrp 109 network 172.22.0.0 ! router rip network 172.22.0.0 ! ip default-gateway 172.22.65.129 no ip classless ip route 0.0.0.0 0.0.0.0 172.22.65.129 ! ! line con 0 transport input none line aux 0 line vty 0 4 password login ! end
The following output displays the configuration for the terminating gateway; this output was creating by using the show running configuration command:
! version 12.0 service timestamps debug uptime service timestamps log uptime no service password-encryption service internal service udp-small-servers service tcp-small-servers ! hostname 3620-px16 ! ip subnet-zero ip domain-name cisco.com ip name-server 198.92.30.32 ! settlement 0 type osp url http://xxx.xxx. ! voice-port 1/0/0 alerting audible ! voice-port 1/0/1 alerting audible ! dial-peer voice 1 pots destination-pattern 5552222 port 1/0/0 ! dial-peer voice 2 voip application session incoming called-number 5552222 session target settlement:0 ! interface Ethernet0/0 ip address 172.22.65.143 255.255.255.224 no ip directed-broadcast ip route-cache same-interface ! interface Serial0/0 no ip address no ip directed-broadcast shutdown ! interface Ethernet0/1 no ip address no ip directed-broadcast shutdown ! router eigrp 109 network 172.22.0.0 ! router rip network 172.22.0.0 ! ip default-gateway 172.22.65.129 no ip classless ip route 0.0.0.0 0.0.0.0 172.22.65.129 ! snmp-server community public RO ! line con 0 exec-timeout 0 0 transport input none line aux 0 line vty 0 4 password login ! end
Posted: Wed Jul 26 23:50:35 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.