Mobile and Remote Access Through Cisco Expressway Deployment Guide (X15.2) - MRA Troubleshooting

Publisher

Cisco Systems

URL

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/expressway/config_guide/X15-2/mra/exwy_b_mra-deployment-guide-x152/exwy_m_mra-troubleshooting.html

Published

2024-10-15

Updated

unknown

Accessed

2026-09-24

HTTP status

200

License

Cisco documentation; all rights reserved; no-redistribution; short excerpts and locators only

Source notes citing this source

• Expressway diagnostic logs are captured through Maintenance > Diagnostics > Diagnostic logging, with log levels set under Maintenance > Diagnostics > Advanced > Support Log configuration. in context
• Expressway's Maintenance > Tools > Network utilities > DNS lookup checks _collab-edge._tls and _cisco-uds._tcp SRV records; run from Expressway-C it shows the internal view and from Expressway-E the DMZ view. in context
• Secure MRA registrations fail if the Expressway-C server certificate's Subject Alternative Names do not include the phone security profile names in use, and from X12.6 those profile names must be FQDNs in both Unified CM and the certificate. in context
• MRA endpoints can fail to register if a SIP trunk exists between Unified CM and Expressway-C using the same listening port as SIP line registrations; the trunk needs a different listening port on Unified CM. in context
• Expressway-C's Status > Unified Communications page shows synchronization with Unified CM, and Unified CM and IM and Presence nodes should be rediscovered after configuration changes on them. in context
• Cisco's Collaboration Solutions Analyzer CollabEdge validator simulates a Jabber sign-in to validate an MRA deployment. in context
• Expressway diagnostic logging is run from Maintenance > Diagnostics > Diagnostic logging and the resulting logs can be analysed in Collaboration Solutions Analyzer. in context
• Maintenance > Tools > Network utilities > DNS lookup on Expressway can run SRV lookups for _collab-edge._tls and _cisco-uds._tcp. in context
• The Expressway-E FQDN built from its System host name and Domain name must be resolvable in public DNS. in context
• The MRA troubleshooting chapter lists unreliable NTP synchronisation on the Expressways as a cause of 403 Forbidden responses. in context
• MRA device sessions are listed via View provisioning sessions under Status > Unified Communications and devices registered through Expressway show the Expressway-C IP address in Unified CM. in context
• Status > Unified Communications on Expressway-C and Expressway-E shows MRA configuration errors and missing services and Status > Alarms should be checked first. in context

Cite this source record

APA

WarmTransfer. (2024, October 15). Mobile and Remote Access Through Cisco Expressway Deployment Guide (X15.2) - MRA Troubleshooting. WarmTransfer. https://warmtransfer.net/knowledge/sources/cisco-mra-x152-troubleshooting

BibTeX

@misc{warmtransfer-cisco-mra-x152-troubleshooting,
  title  = {Mobile and Remote Access Through Cisco Expressway Deployment Guide (X15.2) - MRA Troubleshooting},
  author = {{WarmTransfer}},
  year   = {2024},
  url    = {https://warmtransfer.net/knowledge/sources/cisco-mra-x152-troubleshooting},
  note   = {Cisco Systems, accessed 2026-09-24}
}