<div dir="ltr">Thanks a lot for you feedback.<div>To give you more detailed information what is my case...</div><div>- Cisco utilizes two Gb interfaces. One has public IP, second one has VLAN configured with private IP address.</div><div>- our customer is sending calls via VLAN and Cisco routes all the calls to public network (CUSTOMER ----via vlan ----> Cisco CUBE ------via public---> our infrastructure)</div><div>We've been informed that if we setup additional/secondary IP address on the same VLAN and route all outgoing calls via new IP we will be able to send them SIP traffic - those are they requirements (our infrastructure ----via public---> Cisco CUBE ----via vlan---->CUSTOMER)</div><div>Furthermore they IP address remain unchanged (they have 2 IPs for incoming and outgoing traffic).</div><div>Our private IP: <span style="font-family:Menlo;font-size:11px">ip address 105.164.22.191 255.255.255.254</span></div><div>and current routing</div><div><p style="margin:0px;font-size:11px;line-height:normal;font-family:Menlo">ip route 7.212.177.14 255.255.255.248 105.164.22.190</p>
<p style="margin:0px;font-size:11px;line-height:normal;font-family:Menlo">ip route 7.212.177.22 255.255.255.248 105.164.22.190</p><p style="margin:0px;line-height:normal">of course they IPs are 7.212.177.14 and .22.<br></p><p style="margin:0px;line-height:normal"><br></p><p style="margin:0px;line-height:normal">So i could try with</p><p style="margin:0px;line-height:normal">- setup secondary IP address on Cisco</p><p style="margin:0px;line-height:normal">- use .14 only for incoming traffic</p><p style="margin:0px;line-height:normal">- use .22 only for outgoing traffic</p><p style="margin:0px;line-height:normal">- specify "ip route" </p><p style="margin:0px;font-size:11px;line-height:normal;font-family:Menlo">ip route 7.212.177.14 255.255.255.248 105.164.22.190</p><p style="margin:0px;font-size:11px;line-height:normal;font-family:Menlo">ip route 7.212.177.22 255.255.255.248 NEW_IP_HERE</p><p style="margin:0px;line-height:normal">assuming our customer will agree on that.</p><p style="margin:0px;line-height:normal"><br></p><p style="margin:0px;line-height:normal">or</p><p style="margin:0px;line-height:normal">- setup subinterface with new IP</p><p style="margin:0px;line-height:normal">- assign new VLAN </p><p style="margin:0px;line-height:normal">- proceed with control binging on dial-peer</p><p style="margin:0px;line-height:normal">- adjust "ip route"</p><p style="margin:0px;line-height:normal">assuming our customer will agree on new VLAN.</p><p style="margin:0px;line-height:normal"><br></p><p style="margin:0px;line-height:normal">Will using loopback along with bing control do its job here?</p><p style="margin:0px;line-height:normal"><br></p><p style="margin:0px;line-height:normal">Thanks</p><p style="margin:0px;line-height:normal">Maciej.</p><p style="margin:0px;line-height:normal"><br></p></div></div><div class="gmail_extra"><br><div class="gmail_quote">2016-02-19 20:46 GMT+01:00 Barnett, Nick <span dir="ltr"><<a href="mailto:Nick.Barnett@countryfinancial.com" target="_blank">Nick.Barnett@countryfinancial.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" link="blue" vlink="purple">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">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).<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> cisco-voip [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>]
<b>On Behalf Of </b>Anthony Holloway<br>
<b>Sent:</b> Friday, February 19, 2016 10:38 AM<br>
<b>To:</b> NateCCIE<br>
<b>Cc:</b> Cisco VoIP Group</span></p><div><div class="h5"><br>
<b>Subject:</b> Re: [cisco-voip] dial-peer pointing secondary IP address<u></u><u></u></div></div><p></p><div><div class="h5">
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">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?<u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Two things come to mind:<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">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<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">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<u></u><u></u></p>
</div>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">On Fri, Feb 19, 2016 at 9:50 AM, NateCCIE <<a href="mailto:nateccie@gmail.com" target="_blank">nateccie@gmail.com</a>> wrote:<u></u><u></u></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">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.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">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.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">-Nate</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> cisco-voip [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>]
<b>On Behalf Of </b>Anthony Holloway<br>
<b>Sent:</b> Friday, February 19, 2016 8:37 AM<br>
<b>To:</b> Maciej Bylica <<a href="mailto:mbgatherer@gmail.com" target="_blank">mbgatherer@gmail.com</a>><br>
<b>Cc:</b> Cisco VoIP Group <<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>><br>
<b>Subject:</b> Re: [cisco-voip] dial-peer pointing secondary IP address</span><u></u><u></u></p>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
<div>
<p class="MsoNormal">You would bind the SIP outgoing traffic to that new interface on your dial-peers which you would like to use this interface:<u></u><u></u></p>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">dial-peer voice 100 voip<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"> destination-pattern 2...$<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"> session protocol sipv2<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"> session-target ipv4:10.1.1.1<u></u><u></u></p>
</div>
<div>
<div>
<p class="MsoNormal"> <span style="background:#fff2cc">voice-class sip bind
</span><span style="background:#b6d7a8">control</span><span style="background:#fff2cc"> source-interface GigabitEthernet0/0</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"> <span style="background:#fff2cc">voice-class sip bind
</span><span style="background:#b6d7a8">media</span><span style="background:#fff2cc"> source-interface GigabitEthernet0/0</span><u></u><u></u></p>
</div>
</div>
<div>
<p class="MsoNormal"> codec g711ulaw<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"> dtmf-relay sip-kpml rtp-nte digit-strip<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"> no vad<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">!<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">That will make sure that all SIP traffic going to 10.1.1.1 will come from interface G0/0.<u></u><u></u></p>
</div>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
<div>
<p class="MsoNormal">On Thu, Feb 18, 2016 at 10:22 AM, Maciej Bylica <<a href="mailto:mbgatherer@gmail.com" target="_blank">mbgatherer@gmail.com</a>> wrote:<u></u><u></u></p>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">Hi Guys<br>
<br>
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)<br>
<br>
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.<br>
<br>
I cannot see any possibilities how to achieve that?<br>
Maybe somebody could help me here?<br>
Any help would be appreciated.<br>
<br>
Thanks<u></u><u></u></p>
<div>
<p class="MsoNormal"><span style="color:#888888">Maciej</span><u></u><u></u></p>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="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=" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><u></u><u></u></p>
</blockquote>
</div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div></div></div>
</div>
<br>_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br></div>