directing cisco fxs port voip traffic over ipsec tunnel
Ive got an existing setup with a remote and local router.
The local router runs ccm and uplinks to pstn via fxo ports.
The remote router has some voip phones that get ip addresses from a local pool.
I have an ipsec tunnel setup between the 2 routers. An acl directs traffic between the remote site's local ip pool and the local site's loopback address across the tunnel.
I have now installed an fxs module on the remote router and am trying to figure out how to direct its traffic across the tunnel.
Help!?!
The local router runs ccm and uplinks to pstn via fxo ports.
The remote router has some voip phones that get ip addresses from a local pool.
I have an ipsec tunnel setup between the 2 routers. An acl directs traffic between the remote site's local ip pool and the local site's loopback address across the tunnel.
I have now installed an fxs module on the remote router and am trying to figure out how to direct its traffic across the tunnel.
Help!?!
ASKER
Is there a way for me to associate an ip address from the remote internal pool with the fxs port and/or extension? Alternatively, is there a way to associate the fxs port and/or extension with the ipsec tunnel's acl?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I ended up attaching private addresses to the loopback on both routers and including them in the tunnel config on top of the remote router's internal pool in order to push the fxo traffic over the tunnel.
Private-line automatic ringdown (PLAR) circuits have statically configured endpoints and do not require that the user dial in order to connect calls. The connection plar command provides a mechanism to create a switched VoIP call without digit dialing. PLAR connections are often referred to as a bat-phone type of application. This is when a phone (or DS0) goes off-hook and a remote phone rings (or remote DS0 goes off-hook) without digits being dialed. This is a useful tool for customer requirements such as:
The provision of an Off-Premises eXtension (OPX) from a private branch exchange (PBX).
Connection PLAR allows remote users on Foreign Exchange Station (FXS) ports to look to a central PBX like physical extensions.
The provision of dial-tone from a remote PBX.
Many customers want to offer toll-bypass VoIP services without having the routers provide dial-tone or change their existing dial plan. This allows stations at remote sites to look like they are physically connected stations to a PBX.