[cisco-voip] dial-peer pointing secondary IP address

[Barnett, Nick]

Depending on why a secondary IP is being used… I could see possibly moving that IP to a loopback address. You could easily bind control to a Loopback in the dial-peer(s).

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Anthony Holloway
Sent: Friday, February 19, 2016 10:38 AM
To: NateCCIE
Cc: Cisco VoIP Group
Subject: Re: [cisco-voip] dial-peer pointing secondary IP address

I actually missed the "secondary" nature of this request.  I don't believe this is possible to force.  CUBE can only bind to interfaces not IP addresses.  Why are you adding a secondary IP address anyway?  What's the use case/requirement?

Two things come to mind:

1) To Nate's point about letting the underlying routing process decide, I'm not sure this is going to work in your example unless your peer is in the same network as the secondary IP, otherwise, I think the traffic will be sourced from the primary address on the interface

2) Create this secondary network on a sub interface, and this implies changing your existing network to a sub interface as well, and then setup VLAN trunking to the switch port, followed by using my example to bind to the correct sub interface

On Fri, Feb 19, 2016 at 9:50 AM, NateCCIE <nateccie at gmail.com<mailto:nateccie at gmail.com>> wrote:
Generally, BINDS on a multi-interface CUBE are not friendly.  It is much better to let the router use the egress interface as the source IP address.

I am not aware of a way to bind to a secondary IP, but I would think that if the secondary IP is on a different subnet, it would automatically use that IP if the ip routing table would also source from that IP to the configured destination.

-Nate

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net>] On Behalf Of Anthony Holloway
Sent: Friday, February 19, 2016 8:37 AM
To: Maciej Bylica <mbgatherer at gmail.com<mailto:mbgatherer at gmail.com>>
Cc: Cisco VoIP Group <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: Re: [cisco-voip] dial-peer pointing secondary IP address

You would bind the SIP outgoing traffic to that new interface on your dial-peers which you would like to use this interface:

dial-peer voice 100 voip
 destination-pattern 2...$
 session protocol sipv2
 session-target ipv4:10.1.1.1
 voice-class sip bind control source-interface GigabitEthernet0/0
 voice-class sip bind media source-interface GigabitEthernet0/0
 codec g711ulaw
 dtmf-relay sip-kpml rtp-nte digit-strip
 no vad
!

That will make sure that all SIP traffic going to 10.1.1.1 will come from interface G0/0.

On Thu, Feb 18, 2016 at 10:22 AM, Maciej Bylica <mbgatherer at gmail.com<mailto:mbgatherer at gmail.com>> wrote:
Hi Guys

I need to add one IP address to GbE interface of Cisco 3845 - C3845-IPVOICE_IVS-M, Version 15.1(4)M4 - as a secondary IP (this is not the problem)

What is more i need to be able to create dial-peer to send SIP call attempts via newly defined secondary IP address, not the main one.

I cannot see any possibilities how  to achieve that?
Maybe somebody could help me here?
Any help would be appreciated.

Thanks
Maciej

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip<https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_cisco-2Dvoip&d=BQMFaQ&c=M-KQspD_LQogCbR-BWCHOaeDEPOhF8vWqHZTaiwxT3c&r=T9uVLZucbHG2NKKKzOrp-o5cpdReHj02PkJJsCVkgfwcv7S0R5lDeFJg2VRbiNih&m=CI5SyddUBY7kEbC6Z8zrkBlkpUCm2F7BrPnL9azlFPM&s=bZF6EEEG_aFpNAtKJOPBEo-6U57pwcNSvjpXqrP4k00&e=>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160219/d999313a/attachment.html>