[cisco-voip] CUBE 15.2 ?

[Tim Smith]

Hey mate,

Philosophically? If a CUBE connects two calls with a single dial peer is it still a CUBE?

I think the quality that makes it a "CUBE" is mainly the fact that it's connecting two IP legs instead of a POTS leg and an IP leg.
Then of course then there are all the nice CUBEY things you can do on top of that.
A CUBE license also makes sure the CUBE police don't raid your house in the middle of the night and drag you away.

I've seen it working with single dial peer the same as some people used to do with just POTS dial peers.
But usually we are going back to these installs and separating them out for troubleshooting or to make something else work.

CUBEY things that may drive you down the two dial peer approach

-          Force one type of DTMF on one side, and another on the other side

-          Force once codec on one side, and different one on the other

Cheers,

Tim


From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Jason Aarons (AM)
Sent: Thursday, 26 June 2014 3:09 AM
To: cisco-voip (cisco-voip at puck.nether.net)
Subject: [cisco-voip] CUBE 15.2 ?

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


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