The CUBEs will be connected

Chikona55 · ‎06-17-2015

Am trying to connect two CUCM clusters using two CUBEs. Any one with document on how to Configure this. Anything to lookout for?

dsobrinho · ‎06-17-2015

Hi Chikona55,

After you active the CUBE services you will only work with voip dial peer in each CUBE.

Exemple:

voice-card 0
 dspfarm
 dsp services dspfarm
!
!
!
voice service voip
 ip address trusted list
  ipv4 10.191.0.0 255.255.254.0
 address-hiding
 mode border-element
 allow-connections sip to sip
 redirect ip2ip
 fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback none
 sip
  header-passing
  error-passthru
  no update-callerid
  early-offer forced
  history-info
  midcall-signaling passthru
!
voice class codec 1
 codec preference 1 g729r8
!
voice class sip-profiles 1
 request REINVITE sdp-header Audio-Attribute modify "inactive" "sendrecv" 
 request ACK sdp-header Audio-Attribute modify "sendonly" "sendrecv" 
 response 200 sdp-header Audio-Attribute modify "sendonly" "sendrecv" 

!
!
dial-peer voice 81 voip
 description -------------[dialplan-to-CCM-01]
 preference 3
 destination-pattern 8...
 session protocol sipv2
 session target ipv4:10.X.X.Z
 incoming called-number .T
 voice-class codec 1  
 dtmf-relay rtp-nte
 fax-relay ecm disable
 no fax-relay sg3-to-g3
 fax protocol pass-through g711ulaw
!
dial-peer voice 82 voip
 description -------------[dialplan-to-CCM-02]
 preference 2
 destination-pattern 8...
 session protocol sipv2
 session target ipv4:10.Y.Y.Z
 incoming called-number .T
 voice-class codec 1  
 dtmf-relay rtp-nte
 fax-relay ecm disable
 no fax-relay sg3-to-g3
 fax protocol pass-through g711ulaw
!
! If you have a different PBX
!
dial-peer voice 62 voip
 description -------------[Outgoing-Mx-One]
 translation-profile outgoing MX-ONE
 preference 1
 destination-pattern 62....
 session protocol sipv2
 session target ipv4:10.X.X.C
 voice-class codec 1  
 dtmf-relay rtp-nte
 fax-relay ecm disable
 no fax-relay sg3-to-g3
 fax protocol pass-through g711ulaw
!
!

Best regards,

Daniel Sobrinho

Wilson Samuel · ‎06-17-2015

test

dial-peer voice 81 voip description -------------[dialplan-to-CCM-01] preference 3 destination-pattern 8... session protocol sipv2 session target ipv4:10.X.X.Z incoming called-number .T voice-class codec 1 dtmf-relay rtp-nte fax-relay ecm disable no fax-relay sg3-to-g3 fax protocol pass-through g711ulaw ! dial-peer voice 82 voip description -------------[dialplan-to-CCM-02] preference 2 destination-pattern 8... session protocol sipv2 session target ipv4:10.Y.Y.Z incoming called-number .T voice-class codec 1 dtmf-relay rtp-nte fax-relay ecm disable no fax-relay sg3-to-g3 fax protocol pass-through g711ulaw ! ! If you have a different PBX ! dial-peer voice 62 voip description -------------[Outgoing-Mx-One] translation-profile outgoing MX-ONE preference 1 destination-pattern 62.... session protocol sipv2 session target ipv4:10.X.X.C voice-class codec 1 dtmf-relay rtp-nte fax-relay ecm disable no fax-relay sg3-to-g3 fax protocol pass-through g711ulaw ! - See more at: https://supportforums.cisco.com/discussion/12535946/cucm-sip-cube-cube-sip-cucm-connection#sthash.T93GHh8h.dpuf

Wilson Samuel · ‎06-17-2015

Apologies,

Unknowingly it got pasted and now it does not allow me to delete / remove / edit it.

Regards

Chris Deren · ‎06-17-2015

CUBEs do not register with CUCM, so nothing much to having dial-peers pointing to each cluster and corresponding trunks on the CUCMs.

Are the CUBEs in the same data center and you want HSRP redundancy? Or are these independent CUBEs pointing to separate SIP trunks?

Chikona55 · ‎06-17-2015

The CUBEs will be connected over WAN, No HSRP redundancy. SIP trunk associated with the site CUCM pointing to the site CUBE.

Chris Deren · ‎06-18-2015

Then you treat them separately, configure identically (with different IP addresses, etc) and in CUCM for outbound dialing add SIP trunks to appropriate route groups/route lists.

Wilson Samuel · ‎06-18-2015

Hi,

I guess I do not understand your question completely, so please let me know if I am off a bit.

Just adding to what Chris said:

Whether it is one CUBE which is being used by the CCMs to talk to each other or 2, fundamentally it remains the same configuration, nothing really changes per say.

eg

CUCM Cluster A <== SIP Trunk===> CUBE <<<====WAN====>>>> CUBE <==SIPTrnk===> CUCM Cluster B

Regards

Chikona55 · ‎06-18-2015

Yes ,

CUCM Cluster A <== SIP Trunk===> CUBE <<<====WAN====>>>> CUBE <==SIPTrnk===> CUCM Cluster B -

CUCM-SIP-CUBE-CUBE-SIP-CUCM connection