Sunday, 23 October 2016

Cisco Extend and Connect

This feature isn't supported with Expressway MRA deployment

  • Extend and Connect vs. Single Number Reach
    • Same: Both of these features extend incoming calls to user's remote devices
    • Different:
      • SNR use Remote Destination Profile (RDP) to configure remote destinations. Extend and Connect use CTI Devices to configure remote destinations
      • Extend and Connect utilize Jabber client to control remote device (using CTI) and invoke features such as hold, transfer, conference, etc. SNR uses Enterprise Feature Access Codes to invoke features
      • In Extend and Connect, users can configure their own remote destinations using jabber client. Remote destinations can be configured by admins as well. In SNR, remote destinations can be configured by admins only
      • For outgoing calls, Extend and Connect will use Dial Via Office - Reverse (DVO-R) to dial remote devices and destination numbers then hairpin both call legs on the gateway. SNR will use Mobile Voice Access (MVA) feature for remote device to dial enterprise MVA number then initiate outgoing calls after successful authentication
  • Call Flow
    • Inbound Calls
      • Received incoming call @ jabber extension
      • All shared DNs will ring for incoming call
      • UCM will dial remote destination define by user using jabber client or admin
      • If user answers the call on jabber client, all mid-call features will be available including transfer, hold, conference.
    • Outbound Calls
      • User initiates outbound call using jabber client
      • UCM will dial remote destination using DVO-R
      • User will answer the call and will be redirected to called party.
      • Call will be hairpinned on the gateway
      • Calling Party ID displayed on called party and remote destination will be jabber DN (with digit manipulation applied)
  • Configuration
    • Add End User (local or LDAP)
      • Enable Mobility for End User
      • Assign Standard CCM End User and Standard CTI Enabled permissions
    • Add new phone
      • Select type CTI Remote Device
      • Select the desired Owner User ID (Device name populated automatically)
      • Assign Rerouting Calling Search Space which will be used to for receiving and placing calls to remote destination
      • Assign DN to the phone. This should be same as Jabber extensions
    • Assign CTI Remote Device and Jabber Client to End User
    • Set the Primary Extension on the End User
    • Optionally, you can create Remote Destination Device and assign it CTI Remote Device
      • Remote Destination Device name should be JabberRD to be used with Jabber Client
      • By default, Jabber Client can't add Remote Destination. Set UserDefinedRemoteDestinations in jabber-config.xml to True for users to be able to add remote devices

1 comment:

  1. Hi Mohammad,

    thank you for the sharing, Do we need to configure dial via office using MVA for making outbound calls for jabber for windows ?