Direct SIP: Cisco Unified Communications Manager 6.1

re: Direct SIP: Cisco Unified Communications Manager 6.1

Dave Banthorpe — Mon, 21 Jun 2010 18:16:41 GMT

One thing you should mention up front is the effect of the MTP on the SIP trunk - i.e. forcing all audio through CUCM. This can cause horrible WAN routing for audio if the customer has deployed centralised or regional CUCM clusters. Should be able to mitigate this by switching phones to SIP rather than SCCP (avoids need for MTP) -- but that's a big change for customers.

Also - what about the user experience lost, e.g. caller name display. Direct SIP trunking means that the Callers Name is not displayed on incoming calls to CUCM from OCS. CUCM users are used to seeing name rather than number for internal users. Using an SIP-SIP gateway between Mediation and CUCM (e.g. NET VX1200) allows you to modify SIP traffic and replace caller name in the SIP header. These sorts of things are really important for user adoption of such hybrid solutions.

re: Direct SIP: Cisco Unified Communications Manager 6.1

Matt Marlor — Sun, 13 Jun 2010 21:23:13 GMT

Awesome. A great starting point, and very relevant to what I may have to configure soon! :-)

re: Direct SIP: Cisco Unified Communications Manager 6.1

Joachim Farla [MVP] — Sun, 13 Jun 2010 20:04:23 GMT

Good article - thanks!

re: Direct SIP: Cisco Unified Communications Manager 6.1

Sheila McGee-Smith — Sun, 13 Jun 2010 19:53:23 GMT

Why CUCM 6.1?? Current release is 8.0...

re: Direct SIP: Cisco Unified Communications Manager 6.1

John Cook — Sun, 13 Jun 2010 19:51:43 GMT

Hi, wasn't there a limitation in call manager 6 where we had to strip the e.164 format before we send to CUCM?

Thank you.

re: Direct SIP: Cisco Unified Communications Manager 6.1

DW Hunter — Sun, 13 Jun 2010 19:48:38 GMT

this is great - very helpful - I did something very similar in my CUCM 7.x / Exchange 2010 environment - hadn't tried to bring my OCS 2007 R2 in the mix yet. Now I might! :)