[cisco-voip] CUBE 15.2 ?

[Nick Britt]

Hi Jason,

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)

This was on 152-4 and 15.1


dial-peer voice 1 voip
 description **** Incoming Calls from SIP ****
 translation-profile incoming INGRESS
 session protocol sipv2
 voice-class codec 1
 dtmf-relay sip-notify rtp-nte
!
dial-peer voice 20 voip
 description **** From CUBE to SUB () ****
 preference 1
 destination-pattern 2T
 session target ipv4:CUCM
 voice-class codec 1
 dtmf-relay h245-alphanumeric


HTH









On Wed, Jun 25, 2014 at 6:08 PM, Jason Aarons (AM) <
jason.aarons at dimensiondata.com> wrote:

>  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.
>
>
>
> voice service voip
>
> no ip address trust auth
>
> allow-connection sip to sip
>
> mode border-element
>
> !
>
> dial-peer voice 2001 voip
>
>    destination-patter 6...$  <<<<matches out
>
>    session proto sipv2
>
>    session target ipv4:10.10.64.11
>
>    voice-class codec 2
>
>   dtmf-relay rtp-nte
>
>   no vad
>
>   incoming called-number   <<<< matches in
>
>
>
>
>
>
>
> 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?
>
>
>
> IOS 15.24M4
>
> CUCM 9.1.2
>
>
>
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>


-- 
- Nick
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20140625/9be304fe/attachment.html>