Known Issues and Limitations with Hybrid Call Service Aware and Connect

Document created by Cisco Documentation Team on Dec 11, 2015Last modified by Cisco Documentation Team on Sep 1, 2017
Version 40Show Document
  • View in full screen mode

Hybrid Call Service Aware

Use CaseExpected BehaviorLimitations and ExceptionsIssues and Workarounds

Deployment

Register the Expressway-C to host Call ConnectorDownload and install Call Connector on Expressway-CEach Expressway-C cluster must have a unique IP address for the master peer
Configure Call ConnectorEstablish AXL and CTI connections between Call Connector and Unified CM
Configure SIP connection between Unified CM and Cisco Spark through Expressway-C/ECalls to and from domain call.ciscospark.com securely routed through the Expressway-C/E over public InternetMultiple secure SIP trunks between Unified CM and Expressway-C are not supported by Unified CMUnsecured SIP trunks between Unified CM and Expressway-C may result in duplicate entries in Expressway call status and call history list
Enable User for AwareFind user’s home cluster, assign user to Call Connector, monitor lines and devices for callsExtension Mobility-only users are not yet supported

UC devices recently assigned to a user may not be discovered by Call Connector:

  • Wait overnight

  • Restart Call Connector for newly added or removed devices

For newly added users, waiting overnight or restarting call connector are workarounds.

Call Behavior

UC call established between Aware users
  • Create or activate a space in the People list

  • “Share” available in both users’ Cisco Spark desktop app

  • “Join” available in both users’ Cisco Spark mobile apps

  • No space created for unanswered call

  • No “Share” or “Join” for call on non-CTI-controllable device

  • No “Share” or “Join” for SNR call

Call between Aware user on UC device and user on Cisco Spark“Join” available in Aware user’s Cisco Spark app“Join” may create audio feedback between Aware user’s UC device and Cisco Spark app

Hybrid Call Service Connect

Use CaseExpected BehaviorLimitations and ExceptionsIssues and Workarounds

Deployment

Enable User for ConnectUse call connector to create a CTI remote device (CTI-RD) or Cisco Spark remote device (Spark-RD), depending on Unified CM release. Or manually provision the remote device in Unified CM. Call connector adds the remote destination URI (Cisco Spark SIP Address) in both cases.

User activation failure because of remote destination URI being too long:

  • Upgrade Unified CM to fix CSCux74780

  • Replace CTI RD by Cisco Spark RD (may require Unified CM upgrade)

Call Behavior

Call from Connect user’s Cisco Spark app to company extension or PSTN numberAddress is interpreted and call is routed by Connect user’s Unified CM

No video or share:

  • Replace Unified CM MTP by IOS MTP

  • Configure IOS MTP for passthrough

  • IOS MTP upgrade may be required for share

  • Replace CTI RD by Cisco Spark RD (may require Unified CM upgrade)

No DTMF: Upgrade IOS gateway to fix CSCuz74156

Unified CM licensing out of compliance:

  • Replace CTI RD by Cisco Spark RD (may require Unified CM upgrade)

  • Request temporary licensing (until required Unified CM upgrade is available

Call to Connect user’s UC device also offered to Connect user’s Cisco Spark appNotification and option to “Answer” on Connect user’s Cisco Spark app

Call may be offered to Connect user’s Jabber client or SNR Remote Destination on same platform as Cisco Spark app, with resulting conflicts

Calls from a Connect user’s Cisco Spark app to a hunt group are not offered to the Cisco Spark app of a hunt group member who is also a Connect user

Connect user’s UC devices may continue to alert after the call is declined on the Connect user’s Cisco Spark app

Call does not alert on Connect user’s Cisco Spark app:

  • Reset CTI RD

  • Upgrade Unified CM to fix CSCvc21883

  • Replace CTI RD by Cisco Spark RD (may require Unified CM upgrade)

Call answered on UC device may be reported as missed on Connect user’s Cisco Spark app

Persistent Call busy

  • Upgrade Unified CM to fix CSCuy54870

  • Replace CTI RD with Cisco Spark RD (may require Unified CM upgrade)

A call from a Connect user's Cisco Spark app to a hunt group does not alert the Cisco Spark app of a hunt group member.

Hunt groups are not supported

Call from Connect user’s Cisco Spark app to IP addressNot supported



Attachments

    Outcomes