What are the many circumstances that could arise when troubleshooting a Short Video Address Format for a Cisco Webex Meeting?
Unable to connect to Cisco Webex Meetings Video Endpoints using the new short video address
When attempting to use OBTP from cloud-registered video devices, the call does not connect to the Cisco Webex event.
In order to participate in a Cisco Webex meeting or event utilizing a video system, it is no longer necessary for you to recall the name of the Cisco Webex site. Because you will simply need to know the meeting or event number, you will be able to join the meeting much more quickly.
Note:
- The Webex Business Suite (WBS) 39.11 and later versions, as well as lockdown sites running WBS 33.6 and WBS 39.5.x, are compatible with the Short Video Address functionality.
- The Webex products that have been authorized by FedRAMP do not have access to the Short Video Address capability.
If you are having trouble connecting calls when using the new short URI format, please check your symptoms against the symptoms listed below:
Troubleshooting Symptoms: |
Diagnosis: |
- If a user is joining via a short video URI, and the call connects, but the media portion is only working in one direction [or no directions]. What could be the issue?
|
- The user can join the meeting using a short video URI format, but the media portion is not working; it is frequently firewall related, please check help.webex.com for firewall recommendations.
- WBX264 – How Do I Allow Webex Meetings Traffic on My Network?
|
- When a user joins a meeting via short video URI, the call connects, but the <meeting_id> is not accepted in real-time, even when the meeting_id is entered accurately from the endpoint, followed by # when prompted. What could be the issue?
|
- This issue seems like a DTMF configuration problem between the endpoint and the Cisco Expressway. Please contact TAC for assistance.
|
- The user is unable to connect using a short video URI, and the video call drops when using OBTP from on-prem video endpoints.
|
- This issue could be related to your search rule on your Cisco Expressway. The old dialing format or the configuration guide had a search rule that was too specific. Please update your Cisco Expressway by going to Cisco Webex Meetings Enterprise Deployment Guide for Video Device Enabled Meetings and following the procedure.
- Workaround:
- Use the old dialing format to join the meeting <meeting_id>@site.webex.com or <personal_room_id>@site.webex.com until the search rule on your Cisco Expressway gets updated.
|
- The user is unable to connect using a short video URI, and the video call drops when using OBTP from Cloud registered video devices.
|
- This issue could be Cloud device-related, and there are no on-prem configuration changes to support the new short video URI format. The changes are made from our end. Please open a TAC case with Cisco to get support.
|
- The calls are not connecting for invitees who are dialing into the meetings using the new short URI format, and the calls end abruptly.
|
- The issue could be that your invitee needs to update the search rule on their Cisco Expressway. The old dialing format or the configuration guide had a search rule that was too specific. Please ask your invitee to update their Cisco Expressway by going to Cisco Webex Meetings Enterprise Deployment Guide for Video Device Enabled Meetings and following the procedure.
- Workaround:
- Use the old dialing format to join the meeting <meeting_id>@site.webex.com or <personal_room_id>@site.webex.com until the search rule on your Cisco Expressway gets updated.
|
- Unable to connect the inbound calls using ‘callback my video system’ from a Webex meeting.
|
- The issue doesn’t have anything to do with the short video URI format because the SIP call from the cloud to the customer’s video URI is the same as before, with the same calling information. Double-check your inbound Cisco Expressway configuration / DNS SRV record from our deployment guide.
- Cisco Webex Meetings Enterprise Deployment Guide for Video Device Enabled Meetings
|