locked
Mediation server calls to CUCM, which is the preferred route? RRS feed

  • Question

  • which is the preferred route:

    - Mediation server direct to CUCM

    - Mediation server to NET Gateway/Audio codes/etc then to CUCM

    - Mediation server to NET gateway/Audio codes/etc then a Cisco IOS gateway then to CUCM?

     

    granted less hops is better, but we all know how CUCM and Mediation play together in the sandbox... one throws sand, the other digs tunnels underneath you.

    Wednesday, May 5, 2010 8:43 PM

All replies

  • I would say if the version of Call Manager is listed here http://technet.microsoft.com/en-us/office/ocs/bb735838.aspx then I would go down the Direct SIP route. In my experience this works pretty well and hopefully no one will get any sand in their eyes.

    Matt.

     


    Matt Nixon | http://unifiedmatt.blogspot.com
    Thursday, May 6, 2010 12:41 AM
  • Hi,

    In general, I'd agree with Matt N: SIP trunk from CUCM to Mediation is best. The integration works well in production and, believe it or not, both MS and Cisco support that particular configuration pretty well.

    However - you can only have the mediation server point at one CUCM box. So if you have a publisher/subscriber setup, you can only have Mediation go to one of them. And if the CUCM box you pick goes down or is being rebooted for patching, or whatever, then the SIP trunk will be down.

    If you want the Mediation to be able to talk to both Pub/Sub, then I'd suggest an NET gateway. You can create 2 SIP trunks on the NET - one for each CUCM, then a SIP trunk to OCS Mediation. You can then have the NET decide which CUCM to route to, load balance etc.

    You could accomplish the same thing by having a Cisco IOS router with the Cisco Unified Border Element (CUBE) featureset running instead of the NET gateway. But the NET gateway can do a lot of other useful things, so I generally prefer it.

    Regards,

    Matt


    Matt McGillen, PointBridge - https://blogs.pointbridge.com/Blogs/mcgillen_matt/default.aspx
    Thursday, May 6, 2010 6:39 PM
  • Nice point Matt about the NET.  I will use the NET approach.  (no sand!)
    Tuesday, May 11, 2010 6:09 PM
  • Another benefit of using a media gateway is allowing both OCS and CUCM to utilize native numbering plans and then configuring the media gateway to handle digit manipulation (like stripping the +, which can be performed natively in OCS as well incidentally).  This prevents you from having to modify any configuration within CUCM in order to match RFC3966-compliant (E.164 with + prefix) numbering plans in OCS.
    Jeff Schertz, PointBridge | MVP | MCITP: Enterprise Messaging | MCTS: OCS
    Tuesday, May 11, 2010 6:27 PM