Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
17013
Views
0
Helpful
12
Replies

Outbound Video calls not working from VCS Control to Expresway

paul alves
Level 4
Level 4

‎08-14-2012 12:37 PM - edited ‎03-17-2019 11:36 PM

Hi All,

I've trying to make outbound video calls to test sites and other 3rd party video systems and I'm unable to get any outbound calls working.

Inbound calls work fine, no issues there at all.

I'm getting namely "NOT FOUND" or "Request Timeout" errors in the VCSE logs (I know the end points I'm trying to call are working as I can reach them with other 3rd party SIP products).

I'm going to see if there are any SIP/H323 "fixup" type settings on the firewall.

In addition, I do have a Dual Network option key installed, but its not cabled for the dual option (not certain this may be causing the issue or not), I don't need it so I'm not using it.

Its a basic config, single VCS control on the inside and single VCS Expressway on the outside (with Public IP Address) and only a single interface cabled. The outside interface is in the clear (no firewall in front of it).

Here's a couple examples of the logs taken from the VCSE

(this call was a movi user connected from the internet)

tvcs: Event="Call Rejected" Service="SIP" Src-ip="x.x.x.x" Src-port="53268" Src-alias-type="SIP" Src-alias="sip:user.movi@domain.com" Dst-alias-type="SIP" Dst-alias="sip:loopback.sip@cisco.com" Call-serial-number="d17985da-e644-11e1-b39b-0010f323814a" Tag="d17986c0-e644-11e1-a46f-0010f323814a" Detail="Not found" Protocol="TLS" Response-code="404" Level="1" UTCTime="2012-08-14 19:18:34,801"

and

This call was a dual profile 55 on the inside of the network making an outbound call to a user on the internet using the Cisco Jabber video software (movi, jabber.com)

Aug 14 14:50:50tvcs: Event="Call Rejected" Service="SIP" Src-ip="IP_of_VCS_Control" Src-port="25153" Src-alias-type="SIP" Src-alias="sip:5005@domain.com" Dst-alias-type="SIP" Dst-alias="sip:user@jabber.com" Call-serial-number="411dc2bc-e649-11e1-afaf-0010f323814a" Tag="41e14408-e649-11e1-9d51-0010f32305ae" Detail="Request Timeout" Protocol="TLS" Response-code="408" Level="1" UTCTime="2012-08-14 19:50:50,826"

The IP Address of the VCS control is listed as the source IP (not sure this is normal or not).

Note: I removed names/ip addresses for security reasons.

Any ideas?

thanks,

Paul

Labels:
0 Helpful
12 Replies 12

awinter2
Level 7
Level 7

‎08-14-2012 02:00 PM

Paul,

checking that inspection/fixup is disabled for SIP and H323 is always a good initial troubleshooting step.

As for the log entries you provided, the first entry shows a call to loopback.sip@cisco.com, and the response code for that call is 404 Not found, which could for example be caused by a lack of a DNS zone on your Expressway. A 404 response can in many cases be a completely legit and expected response.

The second log entry indicates that there seemingly isn't any NAT between your VCS Control and the Expressway, since the source address is shown as the actual IP address of the VCS Control (According to what you describe).

Can you confirm that your network routing allows the VCS-E to reach the subnet of the VCS-C through the default gateway that is configured on the VCS-E, and that traffic sent from the VCS-C to the VCS-E is actually being routed through the router which is acting as the default gateway for the VCS-E?

If not, then you might have an asymmetric routing problem which could explain the 408 Request timeout response which you are seeing in your logs. 408 Request timeout is a response which you normally shouldn't be seeing in a healthy network (Assuming the network configuration on your VCS's is correct).

- Andreas

0 Helpful

bannouraw
Level 1
Level 1
In response to awinter2

‎06-14-2017 05:02 AM

Hi All,

Greetings !!

From SX20 telepresence unit, I am able to receive calls but cannot dial outside calls.

Please can anyone help in identifying the issue and resolve it

below are the logs and config for your reference or vcs c and e

Logs in VCS-C:

State Connection Failed
Start time 2017-06-14 12:52:29
End time 2017-06-14 12:53:27
Duration 58 seconds
Tag 71343458-a756-45b5-a6ed-a2857c413c82
Serial number 6565b4e0-d62d-4b0a-9447-9294bf2ac49c
Type Video
SIP variant Standards-based
Bandwidth
Requested 384 kbps
Allocated 384 kbps
Route CUCM Neighbor -> Zone001ToTraversalSZ -> TraversalSubZone -> Zone004ToTraversalSZ -> Traversal Zone
Leg 1
Bandwidth node CUCM Neighbor
Source alias 1 sip:123@10.30.27.15 (Url)
Target alias 1 sip:709@kdcc.com (Url)
Protocol SIP
Address 10.30.27.15:5070
Transport TCP
Reason Not found
Cause 404
Leg 2
Bandwidth node Traversal Zone
Target alias 1 sip:709@kdcc.com (Url)
Protocol SIP
Address 10.30.27.19:7002
Transport TLS
Encryption type None
Leg 3
Bandwidth node Traversal Zone
Target alias 1 709@kdcc.com (H323Id)
Protocol H323
Address 10.30.27.19:6001
Reason Not registered
Cause Destination not found
Session 1
Status Failed
Media routed True
Call routed True
Participant 1 Leg 1
Participant 2 Leg 2
Bandwidth allocated 384 kbps
Bandwidth requested 384 kbps
Route CUCM Neighbor -> Zone001ToTraversalSZ -> TraversalSubZone -> Zone004ToTraversalSZ -> Traversal Zone
Session 2
Status Failed
Media routed True
Call routed True
Participant 1 Leg 1
Participant 2 Leg 3
Bandwidth allocated 384 kbps
Bandwidth requested 384 kbps
Route CUCM Neighbor -> Zone001ToTraversalSZ -> TraversalSubZone -> Zone004ToTraversalSZ -> Traversal Zone

  • Search (16)
    • State: Completed
    • Found: False
    • Reason: Not Found
    • Info: Policy Response
    • Type: SIP (INVITE)
    • SIPVariant: Standards-based
    • CallSerial Number: 6565b4e0-d62d-4b0a-9447-9294bf2ac49c
    • Tag: 71343458-a756-45b5-a6ed-a2857c413c82
    • Source (1)
      • Authenticated: False
      • Aliases (1)
        • Alias (1)
          • Type: Url
          • Origin: Unknown
          • Value: 123@10.30.27.15
      • Zone (1)
        • Name: CUCM Neighbor
        • Type: Neighbor
      • Path (1)
        • Hop (1)
          • Address: 10.30.27.15:5070
    • Destination (1)
      • Alias (1)
        • Type: Url
        • Origin: Unknown
        • Value: sip:709@kdcc.com
    • StartTime: 2017-06-14 12:52:29
    • Duration: 58.26
    • SubSearch (1)
      • Type: Transforms
      • Action: Not Transformed
      • ResultAlias (1)
        • Type: Url
        • Origin: Unknown
        • Value: 709@kdcc.com
      • SubSearch (1)
        • Type: Admin Policy
        • Action: Proxy
        • ResultAlias (1)
          • Type: Url
          • Origin: Unknown
          • Value: 709@kdcc.com
        • SubSearch (1)
          • Type: FindMe
          • Action: Proxy
          • ResultAlias (1)
            • Type: Url
            • Origin: Unknown
            • Value: 709@kdcc.com
          • SubSearch (1)
            • Type: Search Rules
            • SearchRule (1)
              • Name: Traversal zone search rule
              • Zone (1)
                • Name: Traversal Zone
                • Type: TraversalClient
                • Protocol: SIP
                • Found: False
                • Reason: Not Found
                • StartTime: 2017-06-14 12:52:29
                • Duration: 38.12
                • Gatekeeper (1)
                  • Address: 10.30.27.19:7002
                  • Alias (1)
                    • Type: Url
                    • Origin: Unknown
                    • Value: 709@kdcc.com
              • Zone (2)
                • Name: Traversal Zone
                • Type: TraversalClient
                • Protocol: H323
                • Found: False
                • Reason: Not registered - Destination not found
                • StartTime: 2017-06-14 12:53:07
                • Duration: 20.13
                • Gatekeeper (1)
                  • Address: 10.30.27.19:6001
                  • Alias (1)
                    • Type: Url
                    • Origin: Unknown
                    • Value: 709@kdcc.com
Priority Rule name Protocol Source Authentication required Mode Pattern type Pattern string Pattern behavior On match Target SIP variant Enabled Actions
1 Route to CUCM Any Any No Alias pattern match Regex (.*)@gulfsls.com Replace Stop CUCM Neighbor Any   View/Edit | Clone
2 Local Zone - No domain Any Any No Alias pattern match Prefix (.+)@gulfsls.com.* Replace Continue LocalZone Any   View/Edit | Clone
5 LocalZoneMatch Any Any No Alias pattern match Regex (.+)@gulfsls.com.* Leave Continue LocalZone Any   View/Edit | Clone
10 Dial IP Address Search Rule Any Any No Any IP address Stop Traversal Zone Any   View/Edit | Clone
45 CEtcp-cucmadmin.gulfsls.com SIP Any No Alias pattern match Prefix cucmadmin.gulfsls.com;transport=TCP Leave Stop CEtcp-cucmadmin.gulfsls.com All SIP Variants   View | Clone
50 Route to CUCM Outside Any Any No Alias pattern match Regex ^(\d(8))@gulfsls.com(.*)$ Leave Stop CUCM Neighbor Any   View/Edit | Clone
90 External IP address search rule Any Any No Any IP address Continue Traversal Zone Any   View/Edit | Clone
100 Traversal zone search rule Any Any No Any alias Continue Traversal Zone Any   View/Edit | Clone

2 Enabled "Add domain where none exists" ([^@]*) Regex Replace \1@gulfsls.com View/Edit
5 Enabled Convert unified CM supplied domain information to Expressway (1\d{2})@vcse.gulfsls.com)(:.*)? Regex Replace \1@gulfsls.com View/Edit
13 Enabled Transform to strip domain from IP-address call (.*)\.(.*)\.(.*)\.(.*)@h323.gulfsls.com Regex Replace \1.\2.\3.\4 View/Edit

Logs in VCS-E:

State Connection Failed
Start time 2017-06-14 12:52:29
End time 2017-06-14 12:53:07
Duration 38 seconds
Tag 71343458-a756-45b5-a6ed-a2857c413c82
Serial number 85679bc2-c38a-413a-a279-cf5a5a8cfe53
Type Video
SIP variant Standards-based
Bandwidth
Requested 384 kbps
Allocated 384 kbps
Route Traversal Zone -> Zone003ToTraversalSZ -> TraversalSubZone -> Zone002ToTraversalSZ -> DNS Zone
Leg 1
Bandwidth node Traversal Zone
Source alias 1 sip:123@10.30.27.15 (Url)
Target alias 1 sip:709@kdcc.com (Url)
Protocol SIP
Address 10.30.27.18:25031
Transport TLS
Encryption type None
Reason Not found
Cause 404
Leg 2
Bandwidth node DNS Zone
Target alias 1 sip:709@kdcc.com (Url)
Protocol SIP
Address 62.215.248.172:5061
Transport TLS
Encryption type None
Leg 3
Bandwidth node DNS Zone
Target alias 1 sip:709@kdcc.com (Url)
Protocol SIP
Address 62.215.248.172:5060
Transport TCP
Encryption type None
Leg 4
Bandwidth node DNS Zone
Target alias 1 sip:709@kdcc.com (Url)
Protocol SIP
Address 62.215.248.172:5060
Transport UDP
Encryption type None
Leg 5
Bandwidth node DNS Zone
Target alias 1 709@kdcc.com (H323Id)
Protocol H323
Address 62.215.248.172:1719
Reason Undefined reason
Cause Request timeout
Session 1
Status Failed
Media routed True
Call routed True
Participant 1 Leg 1
Participant 2 Leg 2
Bandwidth allocated 384 kbps
Bandwidth requested 384 kbps
Route Traversal Zone -> Zone003ToTraversalSZ -> TraversalSubZone -> Zone002ToTraversalSZ -> DNS Zone
Session 2
Status Failed
Media routed True
Call routed True
Participant 1 Leg 1
Participant 2 Leg 3
Bandwidth allocated 384 kbps
Bandwidth requested 384 kbps
Route Traversal Zone -> Zone003ToTraversalSZ -> TraversalSubZone -> Zone002ToTraversalSZ -> DNS Zone
Session 3
Status Failed
Media routed True
Call routed True
Participant 1 Leg 1
Participant 2 Leg 4
Bandwidth allocated 384 kbps
Bandwidth requested 384 kbps
Route Traversal Zone -> Zone003ToTraversalSZ -> TraversalSubZone -> Zone002ToTraversalSZ -> DNS Zone
Session 4
Status Failed
Media routed True
Call routed True
Participant 1 Leg 1
Participant 2 Leg 5
Bandwidth allocated 384 kbps
Bandwidth requested 384 kbps
Route Traversal Zone -> Zone003ToTraversalSZ -> TraversalSubZone -> Zone002ToTraversalSZ -> DNS Zone

  • Search (16)
    • State: Completed
    • Found: False
    • Reason: Not Found
    • Info: Policy Response
    • Type: SIP (INVITE)
    • SIPVariant: Standards-based
    • CallSerial Number: 85679bc2-c38a-413a-a279-cf5a5a8cfe53
    • Tag: 71343458-a756-45b5-a6ed-a2857c413c82
    • Source (1)
      • Authenticated: False
      • Aliases (1)
        • Alias (1)
          • Type: Url
          • Origin: Unknown
          • Value: 123@10.30.27.15
      • Zone (1)
        • Name: Traversal Zone
        • Type: TraversalServer
      • Path (1)
        • Hop (1)
          • Address: 10.30.27.18:5061
        • Hop (2)
          • Address: 10.30.27.15:5070
    • Destination (1)
      • Alias (1)
        • Type: Url
        • Origin: Unknown
        • Value: sip:709@kdcc.com
    • StartTime: 2017-06-14 12:52:29
    • Duration: 38.11
    • SubSearch (1)
      • Type: Transforms
      • Action: Not Transformed
      • ResultAlias (1)
        • Type: Url
        • Origin: Unknown
        • Value: 709@kdcc.com
      • SubSearch (1)
        • Type: Admin Policy
        • Action: Proxy
        • ResultAlias (1)
          • Type: Url
          • Origin: Unknown
          • Value: 709@kdcc.com
        • SubSearch (1)
          • Type: FindMe
          • Action: Proxy
          • ResultAlias (1)
            • Type: Url
            • Origin: Unknown
            • Value: 709@kdcc.com
          • SubSearch (1)
            • Type: Search Rules
            • SearchRule (1)
              • Name: LocalZoneMatch
              • Zone (1)
                • Name: LocalZone
                • Type: Local
                • Protocol: SIP
                • Found: False
                • Reason: Not Found
                • StartTime: 2017-06-14 12:52:29
                • Duration: 0
                • Gatekeeper (1)
                  • Address: 10.30.27.19:0
                  • Alias (1)
                    • Type: Url
                    • Origin: Unknown
                    • Value: 709@kdcc.com
              • Zone (2)
                • Name: LocalZone
                • Type: Local
                • Protocol: H323
                • Found: False
                • Reason: Not Found
                • StartTime: 2017-06-14 12:52:29
                • Duration: 0
                • Gatekeeper (1)
                  • Address: 10.30.27.19:0
                  • Alias (1)
                    • Type: Url
                    • Origin: Unknown
                    • Value: 709@kdcc.com
            • SearchRule (3)
              • Name: DNS Zone search rule
              • Zone (1)
                • Name: DNS Zone
                • Type: DNS
                • Protocol: SIP
                • Found: False
                • Reason: Request Timeout
                • StartTime: 2017-06-14 12:52:29
                • Duration: 10.64
                • Gatekeeper (1)
                  • Alias (1)
                    • Type: Url
                    • Origin: Unknown
                    • Value: 709@kdcc.com
              • Zone (2)
                • Name: DNS Zone
                • Type: DNS
                • Protocol: H323
                • Found: False
                • Reason: Undefined reason - Request timeout
                • StartTime: 2017-06-14 12:52:50
                • Duration: 17.24
                • Gatekeeper (1)
                  • Alias (1)
                    • Type: Url
                    • Origin: Unknown
                    • Value: 709@kdcc.com
Priority Rule name Protocol Source Authentication required Mode Pattern type Pattern string Pattern behavior On match Target SIP variant Enabled Actions
50 LocalZoneMatch Any Any No Any alias Continue LocalZone Any   View/Edit | Clone
100 Traversal Search Rule Any Any No Any alias Continue Traversal Zone Any   View/Edit | Clone
150 DNS Zone search rule Any All zones No Alias pattern match Regex (?!.*@gulfsls.com.*$).* Leave Continue DNS Zone Any   View/Edit | Clone

Priority State Description Pattern Type Behavior Replace Actions
1 Enabled Transform destination aliases to URI format ([^@]*) Regex Replace \1@gulfsls.com View/Edit
0 Helpful

Martin Koch
VIP Alumni
VIP Alumni

‎08-14-2012 02:06 PM

you can limit some generic mistakes by checking out:

http://www.cisco.com/en/US/docs/telepresence/infrastructure/vcs/config_guide/Cisco_VCS_Basic_Configuration_Cisco_VCS_Control_with_Cisco_VCS_Expressway_Deployment_Guide_X7-1.pdf

Than would look into:

* do you have a dns zone

* do you have a search rule hitting that zone

* can you resolve dns from the vcs-e (see screenshot on how to test it)

under maintenance / tools you can also find the locate tool. Try that with loopback@cisco.com and copy paste the result here.

You should see a green True somewhere like:

If all this did not help,

  • does it make a difference if you use h323 to initiate the call?
  • How does the search history of failed real calls look like.
  • Check your firewall / routes
  • Do network traces, check logs, enable debugging and analyze it.
  • Call your Cisco TelePresence partner for help!

Please remember to rate helpful responses and identify

0 Helpful

paul alves
Level 4
Level 4
In response to Martin Koch

‎08-14-2012 08:45 PM

Here's a failed call detail

151.124.146.111 = Real dual 55 profile IP on internal network

205.214.144.152 = VCSE Public IP Address

Call details

You are here:Status Calls Calls Call details

Call information

State

Connection Failed

Start time

2012-08-14 22:29:07

Duration

38 seconds

Tag

5ed43ae4-e689-11e1-b15c-0010f32305ae

Serial number

5ed439fe-e689-11e1-88cd-0010f32305ae

Bandwidth

Requested

6000 kbps

Allocated

6000 kbps

Route

DefaultSubZone -> DefaultSZtoTraversalSZ -> TraversalSubZone -> Zone001ToTraversalSZ -> TraversalZone

Leg 1

Bandwidth node

Default Subzone

Source alias 1

sip:source@domain.com (Url)

Target alias 1

sip:loopback.sip@cisco.com (Url)

Protocol

SIP

Address

151.124.146.111:5060

Transport

UDP

Reason

Request Timeout

Cause

408

Leg 2

Bandwidth node

TraversalZone

Source alias 1

source@domain.com (Url)

Target alias 1

sip:loopback.sip@cisco.com (Url)

Protocol

SIP

Address

205.214.144.152:7001

Transport

TLS

Encryption type

None

Leg 3

Bandwidth node

TraversalZone

Target alias 1

loopback.sip@cisco.com (H323Id)

Protocol

H323

Address

205.214.144.152:6001

Reason

Undefined reason

Cause

Request timeout

Session 1

Status

Failed

Media routed

True

Call routed

True

Participant 1

Leg 1

Participant 2

Leg 2

Bandwidth allocated

6000 kbps

Bandwidth requested

6000 kbps

Route

DefaultSubZone -> DefaultSZtoTraversalSZ -> TraversalSubZone -> Zone001ToTraversalSZ -> TraversalZone

Channel 0

Type

Audio

Protocol

PCMU

Rate

0 bps

Packets forwarded

0

Keepalives

0

Errors

0

Duplicate packets

0

Lost packets

0

Out of order packets

0

Jitter

0 ms

From

sip:loopback.sip@cisco.com

Channel 1

Type

Video

Protocol

PCMU

Rate

0 bps

Packets forwarded

0

Keepalives

0

Errors

0

Duplicate packets

0

Lost packets

0

Out of order packets

0

Jitter

0 ms

From

sip:loopback.sip@cisco.com

Channel 2

Type

Application

Protocol

BFCP

Rate

0 bps

Packets forwarded

0

Keepalives

0

Errors

0

Duplicate packets

0

Lost packets

0

Out of order packets

0

Jitter

0 ms

From

sip:loopback.sip@cisco.com

Channel 3

Type

Unknown

Protocol

UNKNOWN

Rate

0 bps

Packets forwarded

0

Keepalives

0

Errors

0

Duplicate packets

0

Lost packets

0

Out of order packets

0

Jitter

0 ms

From

sip:loopback.sip@cisco.com

Channel 4

Type

Application

Protocol

H224

Rate

0 bps

Packets forwarded

0

Keepalives

0

Errors

0

Duplicate packets

0

Lost packets

0

Out of order packets

0

Jitter

0 ms

From

sip:loopback.sip@cisco.com

Session 2

Status

Failed

Media routed

True

Call routed

True

Participant 1

Leg 1

Participant 2

Leg 3

Bandwidth allocated

5952 kbps

Bandwidth requested

5952 kbps

Route

DefaultSubZone -> DefaultSZtoTraversalSZ -> TraversalSubZone -> Zone001ToTraversalSZ -> TraversalZone

0 Helpful

paul alves
Level 4
Level 4
In response to paul alves

‎08-14-2012 08:55 PM

I have the DNS Zone and I was able to resolve DNS names using the DNS tool

Using Tools/Locate from the VCS Control (endpoint registerd to the VCS Control)

  • Search (1)

  • State: Searching

  • Found: False

  • Type: SIP (OPTIONS)

  • CallSerial Number: f85ee00e-e68b-11e1-865d-0010f32305ae

  • Tag: f85ee130-e68b-11e1-bde6-0010f32305ae

  • StartTime: 2012-08-14 22:47:43

  • Source (1)
    • Authenticated: True
    • Aliases (1)
      • Alias (1)
        • Type: Url
        • Origin: Unknown
        • Value: xcom-locate
    • Zone (1)
      • Name: DefaultZone
      • Type: Default
    • Path (1)
      • Hop (1)
        • Address: 127.0.0.1


  • SubSearch (1)
    • Type: Transforms
    • Action: Not Transformed
    • SubSearch (1)
      • Type: Admin Policy
      • Action: Proxy
      • SubSearch (1)
        • Type: FindMe
        • Action: Proxy
        • SubSearch (1)
          • Type: Search Rules
          • SearchRule (1)
            • Name: Traversal Zone Search Rule
            • Zone (1)
              • Name: TraversalZone
              • Type: TraversalClient
              • Protocol: SIP
              • Found: False

Using Tools/Locate on the VCSE (not sure which source zone to use, used the Traversal Zone).

Note: IP Address 127.0.0.1 is the IP on the 2nd NIC on the VCSE (Its licensed for Dual NICs, but I'm not using Dual NICs).

The Ethernet interface has a public IP Address and directly connected to the internet.

Search completed.
  • Search (8)
    • State: Completed
    • Found: False
    • Reason: Request Timeout
    • Type: SIP (OPTIONS)
    • CallSerial Number: 5e67a128-e6f6-11e1-a0a1-0010f323814a
    • Tag: 5e67a20e-e6f6-11e1-b727-0010f323814a
    • StartTime: 2012-08-15 11:29:21
    • Duration: 20.56
    • Source (1)
      • Authenticated: True
      • Aliases (1)
        • Alias (1)
          • Type: Url
          • Origin: Unknown
          • Value: xcom-locate
      • Zone (1)
        • Name: TraversalZone
        • Type: TraversalServer
      • Path (1)
        • Hop (1)
          • Address: 127.0.0.1
    • SubSearch (1)
      • Type: Transforms
      • Action: Not Transformed
      • SubSearch (1)
        • Type: Admin Policy
        • Action: Proxy
        • SubSearch (1)
          • Type: FindMe
          • Action: Proxy
          • SubSearch (1)
            • Type: Search Rules
            • SearchRule (2)
              • Name: DNS Zone Search Rule
              • Zone (1)
                • Name: DNSZone
                • Type: DNS
                • Protocol: SIP
                • Found: False
                • Reason: Request Timeout
0 Helpful

Martin Koch
VIP Alumni
VIP Alumni
In response to paul alves

‎08-15-2012 03:39 AM

I have the feeling you did not really follow the standard deployment

http://www.cisco.com/en/US/docs/telepresence/infrastructure/vcs/config_guide/Cisco_VCS_Basic_Configuration_Cisco_VCS_Control_with_Cisco_VCS_Expressway_Deployment_Guide_X7-1.

I do not really see that the DNS zone is hit at all by your search, so there is most likely something wrong with your

dns zone, search rules or transforms.

Also do you expect to find "loopback.sip@cisco.com" on the second search I only see loopback.sip@compucom.com

To be honest, this looks like the typical "if you know how it shall work its fixed in no time." issue.

The back and forth in the forum is not really helpful, a hands on check would be way easier.

If you can not fix it yourself you should call your Cisco TelePresence partner and ask for help.

Please remember to rate helpful responses and identify

0 Helpful

paul alves
Level 4
Level 4
In response to Martin Koch

‎08-15-2012 09:34 AM

I accidentally typed in the wrong URI (meant cisco.com and not compucom.com). Compucom.com is the internal domain, so it wouldn't have searched/went to the DNS zone, that's why it appears the DNS zone wasn't hit.

I have set it up as per the guide you mentioned.

I edited my post with loopback.sip@cisco.com, back above, but here it is anyhow (from the VCSE from an internal endpoint), trying to reach the outside.

Search completed.
  • Search (8)
    • State: Completed
    • Found: False
    • Reason: Request Timeout
    • Type: SIP (OPTIONS)
    • CallSerial Number: 5e67a128-e6f6-11e1-a0a1-0010f323814a
    • Tag: 5e67a20e-e6f6-11e1-b727-0010f323814a
    • StartTime: 2012-08-15 11:29:21
    • Duration: 20.56
    • Source (1)
      • Authenticated: True
      • Aliases (1)
        • Alias (1)
          • Type: Url
          • Origin: Unknown
          • Value: xcom-locate
      • Zone (1)
        • Name: TraversalZone
        • Type: TraversalServer
      • Path (1)
        • Hop (1)
          • Address: 127.0.0.1
    • SubSearch (1)
      • Type: Transforms
      • Action: Not Transformed
      • SubSearch (1)
        • Type: Admin Policy
        • Action: Proxy
        • SubSearch (1)
          • Type: FindMe
          • Action: Proxy
          • SubSearch (1)
            • Type: Search Rules
            • SearchRule (2)
              • Name: DNS Zone Search Rule
              • Zone (1)
                • Name: DNSZone
                • Type: DNS
                • Protocol: SIP
                • Found: False
                • Reason: Request Timeout


thanks,

Paul

0 Helpful

Martin Koch
VIP Alumni
VIP Alumni
In response to paul alves

‎08-15-2012 09:57 AM

yea, but then we are back to what I said in the early begining,

either it does not find the proper dns records, or your firewall is blocking or changing the request.

Please remember to rate helpful responses and identify

0 Helpful

mgolcuk_8
Level 1
Level 1
In response to Martin Koch

‎03-16-2016 01:23 AM

Hello there;

I receive the same error on Cisco expressway to me. call falls on iOS does not fall "Call Rejected" is. I get this error every time. can you help me get it.

Error log: 

tvcs: Event="Call Rejected" Service="SIP" Src-ip="10.1.1.1" Src-port="10006" Src-alias-type="SIP" Src-alias="sip:5000@10.1.0.32" Dst-alias-type="SIP" Dst-alias="sip:04a27964-e582-4801-3f29-bcb59c30d91a@10.218.156.67" Call-serial-number="932f3edb-e32e-4011-a1ea-55f69d2895b3" Tag="d5121b51-6ef1-4b8e-9c4b-7ff0acc474c1" Detail="Request Terminated" Protocol="TLS" Response-code="487" Level="1" UTCTime="2016-03-15 14:04:46,217"

0 Helpful

jeliasoncisco
Level 5
Level 5
In response to mgolcuk_8

‎11-02-2016 07:52 PM

Hello,

We are getting the same Response code="487"

Did you ever resolve this? Cisco TAC has not been helpful in this case.

Thanks. Jordan

0 Helpful

Tomonori Taniguchi
Cisco Employee
Cisco Employee

‎08-14-2012 10:42 PM

Just quick check, do you have DNS zone and any search rule pointing DNS zone in VCS Control?

For external URI dialing, DNS lookup should be done at VCS Expressway.

If you have any search rule on VCS Control pointing DNS zone, please remove it and try making outgoing external call.

0 Helpful

paul alves
Level 4
Level 4
In response to Tomonori Taniguchi

‎08-15-2012 09:44 AM

Hi Tomonori,

Thanks for your reply.

I do not have any DNS Zones or any search rules pointing DNS zone in the VCS Control.

The only places I have the DNS lookup for external URI dialing is on the VCS Expressway.

See below....


VCS Control

VCS Expressway

Here's the VCSE DNS Zone Configuration and Search Rule

DNS Search Rule

thanks,

Paul

0 Helpful
Customers Also Viewed These Support Documents