cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements
Walkthrough Wednesdays
234
Views
0
Helpful
2
Replies
Highlighted
Participant

SEARCH HISTORY - VCS ISSUE X8.8.2

I am running VCS X8.8.2 …

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: 6930027600@swa.ds.army.mil;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: 214.16.162.2:6001
    Alias (1)Type: Url
  • Origin: Unknown
    Value: 6930027600@swa.ds.army.mil;user=phone;transport=tcp

----------------------------------------------------------------------------------

On the VCSe search history :

  • Type: Neighbor
  • Protocol: SIP
  • Found: False
  • Reason: Not Found
  • StartTime: 2020-07-11 08:16:54
    Duration: 0.46
    Gatekeeper (1)
  • Address: 158.9.217.247:5061
    Alias (1)
    Type: Url
    Origin: Unknown
    Value: 6930027600@swa.ds.army.mil;user=phone

Why is it adding the user=phone transport=tcp ???

Chet Cronin
801-815-3539(USA)
801-815-3539 (AFG)
2 REPLIES 2
Highlighted

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.

https://www.cisco.com/c/en/us/products/collateral/unified-communications/telepresence-video-communication-server-vcs/eos-eol-notice-c51-743076.html

Highlighted
Cisco Employee

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. 

Content for Community-Ad