Trying to make a SIP call via endpoint to VCSc and travering to the VCSe.
Problem is search history sees the call going to Traversal Zone
Value: firstname.lastname@example.org;user=phone;transport=tcp Zone (2) Name: TRAVERSAL ZONE Type: TraversalClient Protocol: H323 Found: False Reason: Not registered - Destination not found StartTime: 2020-07-11 08:16:33
Duration: 0.5 Gatekeeper (1) Address: 184.108.40.206:6001 Alias (1)Type: Url
Neither of those parameters are the issue. The “userinfo=phone” indicates that the URI LHS represents a tel URI, in this case an H.323 E.164 address. The “transport=tcp” is just indicating that the OSI Layer 4 transport is TCP.
Your Search Rules on VCS-E don’t match for some other reason. Likely because they are scoped to a different incoming zone, protocol, or your RegEx is off.
PS- VCS in general and the x8.8 train specifically are approaching end End of SW Maintenance. You should be planning a transition to Expressway series.
Pexip has a nice spot to easily check for DNS records - dns.pexip.com. That domain doesn't show any SRV records for SIP or H.323, so even if you have your search rules and zones all done correctly, without the DNS records the name will not resolve because the records don't exist - hence the "not found" you are seeing.
on January 25th and 26th, we're hosting a Technical Enablement Workshop which will guide you through the steps involved in updating your organisation from Jabber and/or Meetings to Webex App.
Very useful for partners and for customers t...
hi Team, we are planning to deploy Multi-Factor Authentication for Jabber. The main requirement is to use MFA over internet (MRA).Is it possible to deploy MFA just for MRA and don't touch impact any on-prem existing setup?Can someone please guide on ...
Looking to expand your professional network? Interested in gaining an edge with exclusive technology insights? Engage with Cisco experts, share feedback on products and connect with peers from across the globe. Cisco Champion 2021 applications are open fo...
UCCX does not natively protect HTTP Triggers.
I wanted to come up with a solution to handle HTTP cookie based authentication.
There is a zip file for this project attached to this article. It was written on UCCX 12.5...