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-boun...@puck.nether.net] On Behalf Of Anthony Holloway Sent: Friday, February 19, 2016 8:37 AM To: Maciej Bylica <mbgathe...@gmail.com> Cc: Cisco VoIP Group <cisco-voip@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 <mbgathe...@gmail.com <mailto:mbgathe...@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@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
