dial peers session targets using loopbacks

[jeffreywatson]

Setting up dial peers between two routers and have  a question about the session target.  We're trying to run this over redundant VPNs between A and B.   If I set the session target to one of the tunnel address' on the either side  everything works.  But If I set the session target to a routable loopback address on either side we're broke.    It works fine also if the receive side sets the target to the tunnel.  I did some packet captures and the source address of the sender is always the exit interface.

Is there any way to get this work using Loopback interfaces as the session target or does it always have to be the exit interface ?

tu0

ip address 10.10.10.2

SITE A

dial-peer voice 1 voip

session target ipv4:10.10.10.1

SITE B

tu 0

ip address 10.10.10.1

dial-peer voice 1 voip

session target ipv4:10.10.10.2

*SITE A**********   THIS DOESNT WORK

tu0

ip address 10.10.10.2

dial-peer voice 1 voip

session target ipv4:172.22.1.1

L0

192.168.1.1

SITE B

tu 0

ip address 10.10.10.1

dial-peer voice 1 voip

session target ipv4:192.168.1.1

L0

172.22.1.1

[Wilson Samuel · Accepted solution]

Hi,

Since it is a VoIP session across the VPN Tunnels, would it make any difference if you used SIP Protocol? If not, then why not try, binding the source interface (Loopback Interface) at the dial-peer ?

It should look something like this:

1.    enable

2.    configure terminal

3.    interface type / number

4.    ip address ip-address mask [secondary]

5.    exit

6.    dial-peer voice tag voip

7.    session protocol sipv2

8.    voice-class sip bind {control | media} source interface interface-id[ipv6-address ipv6-address]

9.    exit

For detailed information, please visit the following URL

www.cisco.com/c/en/us/td/docs/ios-xml/ios/voice/sip/configuration/12-4t/Configuring_SIP_Bind_Features.html#GUID-5C2458B7-4939-4CF1-855C-8E2E6909AAB2


Please let us know if it doesn't work

HTH

[jeffreywatson]

Thank you - I was looking for a way to set the source address.

didn't think of setting it at the interface.

awesome ! thanks again

[Mohammed al Baqari · Accepted solution]

The reason for using exist interface as source IP because you didn't define the source interface for signaling and media. This is the behavior if you don't define source interfaces.

Not sure what is your signaling protocol. But here is the config for SIP and H323.

SIP

voice service voip

 sip

  bind all source-interface LoopbackX

H323

interface LoopbackX

 ip address x.x.x.x y.y.y.y

 h323-gateway voip interface

 h323-gateway voip bind srcaddr x.x.x.x