UCM 6.0 and Mobility Connect

[SBCdd7343]

I see that Mobility Connect comes with UCM 6.0 (and is part of the UCM configuration). Is their any extra licensing needed for users of Mobility Connect in this scenario?

Also, the UCM 6.0 Features and services guide specifies that Mobility Voice Access is only available for H.323 Gateways. Am I correct then that Mobility Connect is compatable with MGCP gateways, and it's only the Voice Access feature that is not?

Thanks to all

[Jon Nelson]

Mobility Manager is now built into UCM6.x. Each user that wants the service will require 2 Device License Units (DLU).

Mobile Voice Access will work with MGCP, you have to use hairpinning to make it work, but it will work.

Thank you,

Jon

[kdamisch]

Jon,

Have you (or anyone else here??) tested this with MGCP? We have a customer that wants to use both Mobile Connect and Mobile Voice Access features and the gateway is MGCP. I'm curious why the Features and Services Guide says that only H.323 will work. Our customer only has a T1 CAS circuit now, but will be getting a PRI soon which I believe is what is needed instead of the T1 CAS.

Thanks,

Kevin

[Jon Nelson]

Yes, both features work great. Keep in mind that a gateway can be configured for both H323 and MGCP. You create H323 dial-peers for the Mobile Voice Access feature. These dial-peers point to the VXML files on CUCM. Your PRI can still utilize MGCP and the full functionality is still there.

Why does the documentation say what it does? I can't answer that. My guess is that it was copied from the MobMan docs and not actually revised for CUCM6.

HTH

Jon

[jasonfaraone]

Can anyone point me to a reasonably sane guide for configuring Mobile Connect? I have a similar setup (MGCP gateways) and Cisco's documentation... well, I can tell that it was written by an engineer. For example, I'm not sure how my rerouting CSS or calling party transformation CSS should be setup.

I wish Cisco Press had some decent UCM6 books out.