[cisco-voip] Mobility Advantage Server

[Ryan Ratliff]

CUMC doesn't do any of the mid-call features that section of the SRND refers to, though you can't expect the 6.0 SRND to have any inkling of what CUMC can or cannot do since the product didn't exist when the doc was written.

There is no smart client that I'm aware of that can automate the mid-call features available to users.  They were designed with such a client in mind (since they are not at all user-friendly or intuitive to use) and the latest SRND will have some edits to this section to reflect the current situation.

-Ryan

On Jan 26, 2010, at 4:48 PM, Glen Cobby wrote:

Hi All,

I am just reading through the SRND for CCM 6.0 under the Mobility Applications.

With reference to using the Mobility Smart Client on a Blackberry, the main feature we are looking for at the moment is the mid call features mainly to allow transferring of the call. Currently without the smart client it is very clunky to transfer call.

I was looking for screenshots/info on how the smart client works when transferring a call and came across the following note :-



Note	Currently no Smart Client applications provide programmed softkeys for automating mid-call features, therefore the only method available today for invoking mid-call features is manual key presses. 


This is right under a table that shows the smart phone key sequences.

So I am rather confused, if the client purchases the Mobility Advantage Software / Server, connects to their Blackberry Enterprise Server (Assuming it is the correct version etc) Will they be able to carry out transfers using the keys within the application, e.g. Enterprise Hold, Transfer, Conference?

Has anyone on here had experience of this solution and does it work well?

Thanks

Glen  

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20100127/02dfba30/attachment.html>