Requirement

Mobile Operator (AT&T)

• Webex Go Mobile Operator can only be provisioned on active, corporate-owned AT&T (CRU) mobile phone numbers with a supported rate plan.
  • Rate plan must include voice and messaging (for example: for smartphones)
  • Data-only rate plans aren’t eligible

Webex

• Webex Go Mobile Operator users require an Active Webex Suite or Calling Professional License.
• Webex Calling Org must be enabled with Webex Go Mobile Operator (a-webex-go-m-c) SKU to enable the provisioning of Webex Mobile Numbers (AT&T Wireless CTN/CRUs).

• AT&T Cloud Voice with Webex Go bolt-on/service operation code must be activated through Control Hub (assigning of Webex Mobile Number to Webex Calling user) in order to enable the Webex Go with AT&T experience.

Voicemail experience

• The built-in voicemail interface and notifications on the Apple or Android Mobile device doesn’t currently integrate with Webex Calling.
• To access Voicemails, users can access Webex Voicemails with a long press on the 1 digit or dialing 11*86 from the built-in dialer for voice portal access, or using the Webex App for visual voicemail.
• Webex Go isn’t compatible with Apple Live Voicemail. This feature must be disabled when using an iPhone with Webex Go.

Calling experience

• Ring Notifications or Terminations to the Webex Go Mobile device may take longer or be slightly delayed as compared to the other Webex Calling devices that are configured for the user. All endpoints (Desk phone, laptop with Webex App, Desk Pro or AT&T Mobile) may not ring exactly at the same time. This is due to the overhead of alerting the mobile on the mobile network versus routing the call directly to an IP endpoint.
• When a user declines a call on the Webex Go mobile device all other Webex Calling endpoints continue to ring. However, if a user declines a call on a desk phone or Webex App, the call will be routed to busy treatment.
• Two-digit extension dialing isn’t supported on Webex Go.
• All Webex Calling, Routing, and Notification Policies are followed when making or receiving calls on the Webex Go device.

  Example: If a Webex user sets Don’t Disturb (DND), the mobile device won’t ring or be alerted for inbound calls. All calls go directly to the Webex VM. This also applies to Availability Quiet Hours to silence Call notifications, or when the user is sharing/presenting in the Webex App.

• Traditional Feature Access Codes (FAC) for Webex Calling don’t work on an AT&T mobile device. FACs must be prefixed with the digits 11.

  Example: To initiate CALL PULL from your laptop Webex App to the Webex Go enabled mobile device, the user needs to dial 11*11 from the built-in dialer on the mobile phone. Call Pull from other devices still utilize *11 or the traditional FAC or the Call Pull icon in the calling window of the laptop Webex App.

• Call Forwarding and Transferring to International destinations isn’t supported for users with Webex Go w/AT&T mobile numbers.

• If a user configures a Cisco Calling Plan number as the outbound caller ID (CLID) of a Webex Go Mobile enabled user, the user must be configured with a Cisco Calling Plan. Usage for calls using a traditional PSTN number is consumed when using a nonmobile number as the CLID. Calls with a non-mobile CLID are routed to the PSTN provider that owns that number. They aren’t routed to the mobile operator.

  

Provisioning experience

• Post assigning the AT&T Mobile Number to a Webex Calling User in Control Hub, it may take up to 10 minutes for the AT&T mobile device to appear in either the location/org device list.
• Control Hub isn’t properly reflecting the AT&T Mobile Device Status in the current release - Under Users it shows ATT Mobile Device, green status but says status unavailable.
• To ADD Mobile Numbers, Control Hub admin must enter the Operator Account ID. Operator Account ID for AT&T Wireless is the AT&T Foundational Account Number (FAN) for the specific enterprise or business account. Only 1 FAN per organization is allowed. Ensure you have the RIGHT FAN and once provisioned it cannot be changed after authorization.
• As part of the Operator Account Authorization set. Admin should confirm with AT&T Wireless Sales that their AT&T Wireless admin contact details for the assigned, Day to Day Contact is accurate and they have an SMS/Text enabled number and device to ACCEPT and APPROVE the Control Hub Admin to proceed.
• Control Hub Add Number is limited to up to 20 AT&T mobile numbers that can be imported into Webex Number Pool (as “Webex Mobile”) in a single request. Admins must do batch provisioning if you want to add more than 20 numbers into the Control Hub.

AT&T known issues and limitations

• AT&T NumberSync isn’t compatible with Webex Go. This must be disabled for any mobile numbers assigned to a user.
• AT&T FirstNet mobile plans aren’t compatible with Webex Go. FirstNet users must be converted to a different plan with AT&T before assignment of a mobile number to a Webex Calling user. AT&T does include FastTrack (FirstNet equivalent) with Webex Go.
• AT&T Office@hand Wireless devices aren’t compatible with Webex Go.