<div dir="ltr"><div><div><div>Hi Jason,<br><br></div>I have tried both ways on two separate occasions. Unfortunately I needed two to get the result I needed (one in and one out). The Dial peer seems to complete the first action then ignore anything else (regardless of its positioning) <br>
<br></div>This was on 152-4 and 15.1<br><br><br>dial-peer voice 1 <span tabindex="-1" id=":4ie.2" style class="">voip</span><br> description **** Incoming Calls from SIP ****<br> translation-profile incoming INGRESS<br> session protocol sipv2<br>
voice-class <span tabindex="-1" id=":4ie.3" style class="">codec</span> 1<br> <span tabindex="-1" id=":4ie.4" style class="">dtmf</span>-relay sip-notify <span tabindex="-1" id=":4ie.5" style class="">rtp</span>-<span tabindex="-1" id=":4ie.6" style class="">nte</span><br>
!<br>dial-peer voice 20 <span tabindex="-1" id=":4ie.7" style class="">voip</span><br> description **** From CUBE to SUB () ****<br> preference 1<br> destination-pattern 2T<br> session target ipv4:<span tabindex="-1" id=":4ie.8" style class="">CUCM</span><br>
voice-class <span tabindex="-1" id=":4ie.9" style class="">codec</span> 1<br> <span tabindex="-1" id=":4ie.10" style class="">dtmf</span>-relay h245-alphanumeric<br><br><br></div>HTH<br><div><br><br><br><br><br><div><br>
<br></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jun 25, 2014 at 6:08 PM, Jason Aarons (AM) <span dir="ltr"><<a href="mailto:jason.aarons@dimensiondata.com" target="_blank">jason.aarons@dimensiondata.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div link="#0563C1" vlink="#954F72" lang="EN-US">
<div>
<p class="MsoNormal">Does a CUBE have to have two separate dial-peers (incoming and outgoing) for it to be a CUBE? Or can I use a single dial-peer matching both in and out.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">voice service voip<u></u><u></u></p>
<p class="MsoNormal">no ip address trust auth<u></u><u></u></p>
<p class="MsoNormal">allow-connection sip to sip<u></u><u></u></p>
<p class="MsoNormal">mode border-element<u></u><u></u></p>
<p class="MsoNormal">!<u></u><u></u></p>
<p class="MsoNormal">dial-peer voice 2001 voip<u></u><u></u></p>
<p class="MsoNormal"> destination-patter 6...$ <<<<matches out<u></u><u></u></p>
<p class="MsoNormal"> session proto sipv2<u></u><u></u></p>
<p class="MsoNormal"> session target ipv4:10.10.64.11<u></u><u></u></p>
<p class="MsoNormal"> voice-class codec 2<u></u><u></u></p>
<p class="MsoNormal"> dtmf-relay rtp-nte<u></u><u></u></p>
<p class="MsoNormal"> no vad<u></u><u></u></p>
<p class="MsoNormal"> incoming called-number <<<< matches in<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">I was taught that a dial peer for CUBE must have two separate dial-peers to be a CUBE. Is that correct, or will the above “combo” dial-peer work?<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">IOS 15.24M4<u></u><u></u></p>
<p class="MsoNormal">CUCM 9.1.2<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
</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" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>- Nick<br>
</div>