FXS-to-FXS Connection Using RSVP
The following example shows how to configure VoIP for simple FXS-to-FXS connection.
In this example, a very small company with two offices decides to integrate VoIP in its existing IP network. One basic telephony device is connected to Router RLB-1; therefore, Router RLB-1 is configured for one POTS dial peer and one VoIP dial peer. Router RLB-w and Router RLB-e establish the WAN connection between the two offices. Because one POTS telephony device is connected to Router RLB-2, it is also configured for one POTS dial peer and one VoIP dial peer.
In this example, only the calling end (Router RLB-1) is requesting RSVP.
Figure 3-1 illustrates the topology of this FXS-to-FXS connection example.
Figure 3-1 FXS-to-FXS Connection Example
Configuration for Router RLB-1
hostname RLB-1
! Create voip dial-peer 2
dial-peer voice 2 voip
! Define its associated telephone number and IP address
destination-pattern 14155553001
sess-target ipv4:40.0.0.1
! Request RSVP
req-qos controlled-load
! Create pots dial-peer 1
dial-peer voice 1 pots
! Define its associated telephone number and voice port
destination-pattern 14085554001
port 0/0
! Configure serial interface 0
interface Serial0
ip address 10.0.0.1 255.0.0.0
no ip mroute-cache
! Configure RTP header compression
ip rtp header-compression
ip rtp compression-connections 25
! Enable RSVP on this interface
ip rsvp bandwidth 48 48
fair-queue 64 256 36
clockrate 64000
router igrp 888
network 10.0.0.0
network 20.0.0.0
network 40.0.0.0
Configuration for Router RLB-w
hostname RLB-w
! Configure serial interface 0
interface Serial0
ip address 10.0.0.2 255.0.0.0
! Configure RTP header compression
ip rtp header-compression
ip rtp compression-connections 25
! Enable RSVP on this interface
ip rsvp bandwidth 96 96
fair-queue 64 256 3
! Configure serial interface 1
interface Serial1
ip address 20.0.0.1 255.0.0.0
! Configure RTP header compression
ip rtp header-compression
ip rtp compression-connections 25
! Enable RSVP on this interface
ip rsvp bandwidth 96 96
fair-queue 64 256 3
! Configure IGRP
router igrp 888
network 10.0.0.0
network 20.0.0.0
network 40.0.0.0
Configuration for Router RLB-e
hostname RLB-e
! Configure serial interface 0
interface Serial0
ip address 40.0.0.2 255.0.0.0
! Configure RTP header compression
ip rtp header-compression
ip rtp compression-connections 25
! Enable RSVP on this interface
ip rsvp bandwidth 96 96
fair-queue 64 256 3
! Configure serial interface 1
interface Serial1
ip address 40.0.0.2 255.0.0.0
! Configure RTP header compression
ip rtp header-compression
ip rtp compression-connections 25
! Enable RSVP on this interface
ip rsvp bandwidth 96 96
fair-queue 64 256 3
clockrate 128000
! Configure IGRP
router igrp 888
network 10.0.0.0
network 20.0.0.0
network 40.0.0.0
Configuration for Router RLB-2
hostname RLB-2
! Create pots dial-peer 2
dial-peer voice 2 pots
! Define its associated telephone number and voice-port
destination-pattern 14155553001
port 0/0
! Create voip dial-peer 1
dial-peer voice 1 voip
!Define its associated telephone number and IP address
destination-pattern 14085554001
sess-target ipv4:10.0.0.1
! Configure serial interface 0
interface Serial0
ip address 40.0.0.1 255.0.0.0
no ip mroute-cache
! Configure RTP header compression
ip rtp header-compression
ip rtp compression-connections 25
! Enable RSVP on this interface
ip rsvp bandwidth 96 96
fair-queue 64 256 3
clockrate 64000
! Configure IGRP
router igrp 888
network 10.0.0.0
network 20.0.0.0
network 40.0.0.0
Linking PBX Users with E&M Trunk Lines
The following example shows how to configure VoIP to link PBX users with E&M trunk lines.In this example, a company decides to connect two offices: one in San Jose, California, and the other in Salt Lake City, Utah. Each office has an internal telephone network using PBX, connected to the voice network by an E&M interface. Both the Salt Lake City and the San Jose offices are using E&M Port Type II, with four-wire operation and ImmediateStart signaling. Each E&M interface connects to the router using two voice interface connections. Users in San Jose dial 801-555 and then the extension number to reach a destination in Salt Lake City. Users in Salt Lake City dial 408-555 and then the extension number to reach a destination in San Jose.Figure 3-2 illustrates the topology of this connection example.Figure 3-2 Linking PBX Users with E&M Trunk Lines ExampleNoteThis example assumes that the company has already established a working IP connection between its two remote offices.
Router SJ Configuration
hostname router SJ!Configure pots dial-peer 1dial-peer voice 1 potsdestination-pattern 1408555....port 0/0!Configure pots dial-peer 2dial-peer voice 2 potsdestination-pattern 1408555....port 0/1!Configure voip dial-peer 3dial-peer voice 3 voipdestination-pattern 1801555....session target ipv4:172.16.65.182ip precedence 5!Configure the E&M interfacevoice-port 0/0signal immediateoperation 4-wiretype 2voice-port 0/1signal immediateoperation 4-wiretype 2!Configure the serial interface 0interface serial0ip address 172.16.1.123no shutdownRouter SLC Configuration
hostname router SLC!Configure pots dial-peer 3dial-peer voice 3 potsdestination-pattern 1801555....port 0/0!Configure pots dial-peer 4dial-peer voice 4 potsdestination-pattern 1801555....port 0/1!Configure voip dial-peer 1dial-peer voice 1 voipdestination-pattern 1408555....session target ipv4:172.16.1.123ip precedence 5!Configure the E&M interfacevoice-port 0/0signal immediateoperation 4-wiretype 2voice-port 0/1signal immediateoperation 4-wiretype 2!Configure the serial interface 0interface serial0ip address 172.16.65.182no shutdown
Note
Note
FXO Gateway to PSTN
FXO interfaces provide a gateway from the VoIP network to the analog PSTN or to a PBX that does not support E&M signaling so that users can reach telephones and fax machines outside the VoIP network.In this example, users connected to Router SJ in San Jose, California, can reach PSTN users in Salt Lake City, Utah, via Router SLC. Router SLC in Salt Lake City is connected directly to the PSTN through an FXO interface.Figure 3-3 illustrates the topology of this connection example.Figure 3-3 FXO Gateway to PSTN Example
Note
Router SJ Configuration
hostname router SJ! Configure pots dial-peer 1dial-peer voice 1 potsdestination-pattern 14085554000port 0/0! Configure voip dial-peer 2dial-peer voice 2 voipdestination-pattern 1801.......session target ipv4:172.16.65.182ip precedence 5! Configure serial interface 0interface serial0clock rate 2000000ip address 172.16.1.123no shutdownRouter SLC Configuration
hostname router SLC! Configure pots dial-peer 1dial-peer voice 1 potsdestination-pattern 1801.......port 0/0! Configure voip dial-peer 2dial-peer voice 2 voipdestination-pattern 14085554000session target ipv4:172.16.1.123ip precedence 5! Configure serial interface 0interface serial0ip address 172.16.65.182no shutdownFXO Gateway to PSTN (PLAR Mode)
The following example shows an FXO gateway to PSTN connection in PLAR mode.In this example, PSTN users in Salt Lake City, Utah, can dial a local number and establish a private line connection in a remote location. As in the previous example, Router SLC in Salt Lake City is connected directly to the PSTN through an FXO interface.Figure 3-4 illustrates the topology of this connection example.Figure 3-4 FXO Gateway to PSTN (PLAR Mode) Example
Note
Router SJ Configuration
hostname router SJ! Configure pots dial-peer 1dial-peer voice 1 potsdestination-pattern 14085554000port 0/0! Configure voip dial-peer 2dial-peer voice 2 voipdestination-pattern 1801.......session target ipv4:172.16.65.182ip precedence 5! Configure the serial interface 0interface serial0clock rate 2000000ip address 172.16.1.123no shutdownRouter SLC Configuration
hostname router SLC! Configure pots dial-peer 1dial-peer voice 1 potsdestination-pattern 1801.......port 0/0! Configure voip dial-peer 2dial-peer voice 2 voipdestination-pattern 14085554000session target ipv4:172.16.1.123ip precedence 5! Configure the voice portvoice port 0/0connection plar 14085554000! Configure the serial interface 0interface serial0ip address 172.16.65.182no shutdown
