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
1219
Views
5
Helpful
13
Replies

vcsc-vcse ip dialing.

Bar1s
Level 1
Level 1

‎04-17-2012 12:31 PM - edited ‎03-17-2019 11:04 PM

Hello all,

I created to search rule from vcs control.  I tried to call direction to Internet tandberg test device which is  sip:87.234.224.200

I applied all rules from this guide: 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

Vcsexpress way has dual ip interface option key so i deployed like that.

You can see same call log for both side.  Is there any idea ?

vcs control : any ip, dial to traversalzone

call log:

    Search (33)

        State: Completed

        Found: False

        Reason: Not found

        Type: SIP (INVITE)

        CallSerial Number: 21013cc2-88b4-11e1-abdf-0010f3200af0

        Tag: 21013da8-88b4-11e1-b73d-0010f3200af0

        StartTime: 2012-04-17 20:38:22

        Duration: 0.03

        Source (1)

            Authenticated: False

            Aliases (1)

                Alias (1)

                    Type: Url

                    Origin: Unknown

                    Value: 2010@domain.com

            Zone (1)

                Name: LocalZone

                Type: Local

            Path (1)

                Hop (1)

                    Address: 172.16.10.45:5061

        Destination (1)

            Alias (1)

                Type: Url

                Origin: Unknown

                Value: sip:87.234.224.200

        SubSearch (1)

            Type: Transforms

            Action: Not Transformed

            ResultAlias (1)

                Type: Url

                Origin: Unknown

                Value: 87.234.224.200

            SubSearch (1)

                Type: Admin Policy

                Action: Proxy

                ResultAlias (1)

                    Type: Url

                    Origin: Unknown

                    Value: 87.234.224.200

                SubSearch (1)

                    Type: FindMe

                    Action: Proxy

                    ResultAlias (1)

                        Type: Url

                        Origin: Unknown

                        Value: 87.234.224.200

                    SubSearch (1)

                        Type: Search Rules

                        SearchRule (1)

                            Name: External Ip Address

                            Zone (1)

                                Name: TraversalZone

                                Type: TraversalClient

                                Protocol: SIP

                                Found: False

                                Reason: Not found

                                Gatekeeper (1)

                                    Address: 172.16.10.26:7001

                                    Alias (1)

                                        Type: Url

                                        Origin: Unknown

                                        Value: 87.234.224.200

                            Zone (2)

                                Name: TraversalZone

                                Type: TraversalClient

                                Protocol: H323

                                Found: False

                                Reason: Destination not found

                                Gatekeeper (1)

                                    Address: 172.16.10.26:6001

                                    Alias (1)

                                        Type: Url

                                        Origin: Unknown

                                        Value: 87.234.224.200

vcs expressway:  same call log from vcsexpress.

    Search (20)

        State: Completed

        Found: False

        Reason: Not found

        Type: SIP (INVITE)

        CallSerial Number: 2105a172-88b4-11e1-b7cb-0010f32103aa

        Tag: 21013da8-88b4-11e1-b73d-0010f3200af0

        StartTime: 2012-04-17 20:38:22

        Duration: 0

        Source (1)

            Authenticated: False

            Aliases (1)

                Alias (1)

                    Type: Url

                    Origin: Unknown

                    Value: 2010@domain.com

            Zone (1)

                Name: TraversalZone

                Type: TraversalServer

            Path (1)

                Hop (1)

                    Address: 172.16.10.25:5061

                Hop (2)

                    Address: 172.16.10.45:5061

        Destination (1)

            Alias (1)

                Type: Url

                Origin: Unknown

                Value: sip:87.234.224.200

        SubSearch (1)

            Type: Transforms

            Action: Not Transformed

            ResultAlias (1)

                Type: Url

                Origin: Unknown

                Value: 87.234.224.200

            SubSearch (1)

                Type: Admin Policy

                Action: Proxy

                ResultAlias (1)

                    Type: Url

                    Origin: Unknown

                    Value: 87.234.224.200

                SubSearch (1)

                    Type: FindMe

                    Action: Proxy

                    ResultAlias (1)

                        Type: Url

                        Origin: Unknown

                        Value: 87.234.224.200

                    SubSearch (1)

                        Type: Search Rules

Labels:
0 Helpful
13 Replies 13

Martin Koch
VIP Alumni
VIP Alumni

‎04-17-2012 01:18 PM

Did you set "Calls to unknown IP addresses" to Direct?

As its a sip call, if you have SIP UDP enabled on the expressway the call setup might take 30 secs.

Please remember to rate helpful responses and identify

0 Helpful

Bar1s
Level 1
Level 1

‎04-17-2012 01:26 PM

Hello Martin,

Yes, I exatly setup like this.

Udp and Tcp enable.

Regards,

Baris.

0 Helpful

Martin Koch
VIP Alumni
VIP Alumni
In response to Bar1s

‎04-17-2012 01:39 PM

You only confirmed udp and tcp beeing enabled, but not the "Direct IP dialing" like in the included screenshot above.

If that is enabled on the VCS-E I would expect something like that:

[...]

    • Destination (1)
      • Alias (1)
        • Type: Url
        • Origin: Unknown
        • Value: sip:87.234.224.200
    • SubSearch (1)
      • Type: Transforms
      • Action: Not Transformed
      • ResultAlias (1)
        • Type: Url
        • Origin: Unknown
        • Value: 87.234.224.200
      • SubSearch (1)
        • Type: Admin Policy
        • Action: Proxy
        • ResultAlias (1)
          • Type: Url
          • Origin: Unknown
          • Value: 87.234.224.200
        • SubSearch (1)
          • Type: FindMe
          • Action: Proxy
          • ResultAlias (1)
            • Type: Url
            • Origin: Unknown
            • Value: 87.234.224.200
          • SubSearch (1)
            • Type: Search Rules
            • CallsToUnknownIPAddresses (3)
              • Mode: Direct
              • Found: True
              • Zone (1)
                • Name: DefaultZone
                • Type: Default
                • Protocol: SIP
                • Found: False
                • Reason: Request Timeout
                • Gatekeeper (1)
                  • Alias (1)
                    • Type: Url
                    • Origin: Unknown
                    • Value: 87.234.224.200
              • Zone (2)
                • Name: DefaultZone
                • Type: Default
                • Protocol: H323
                • Found: False
                • Reason: Cancelled
                • Gatekeeper (1)
                  • Address: 87.234.224.200:1720
                  • Alias (1)
                    • Type: Url
                    • Origin: Unknown
                    • Value: 87.234.224.200

Its strange that your search details stops with:

  • SubSearch (1)
    • Type: Search Rules

Is there nothing mentioned below that?

Please remember to rate helpful responses and identify

0 Helpful

Bar1s
Level 1
Level 1
In response to Martin Koch

‎04-17-2012 01:46 PM

Hello Martin,

Vcse setup direct ip dialing enabled.

Call started from ex60 like sip:x.x.x.x from vcsc site.

Sent from Cisco Technical Support iPhone App

0 Helpful

Martin Koch
VIP Alumni
VIP Alumni
In response to Bar1s

‎04-17-2012 01:57 PM

Is the system you try to call registered to your VCS-E or is there a neighbor zone with its ip defined?

How is your network setup? You mentioned the dual interface option. It is recomended to use

the second interface for the internet connectivity.

Is this ip behing the interface with the default route or the other one? I assume that the default one

is the one with internet access. Any NAT involved?

Please include the full search details after the

SubSearch (1)
                        Type: Search Rules

or ack that your search details really end with this line

Please remember to rate helpful responses and identify

0 Helpful

Bar1s
Level 1
Level 1

‎04-17-2012 07:54 PM

Vcsc ip : 172.16.10.25

Vcse ip first : 172.16.10.26

second : 172.16.3.12 / nat real ip gived.

Default gateway lan2: 172.16.3.254.

Traversal client and server relation deployed as mentioned for basic guide.

Ex60 registered to vcscontrol as sip and h323.

I have two search rule Default search rule and for ip dialing search rule for vcs control.

Vcsex: just one search rule which is default.

I tried to call unregistered any internet device.

I coudn't figured out this problem.

Regards,

Sent from Cisco Technical Support iPhone App

0 Helpful

Alok Jaiswal
Cisco Employee
Cisco Employee
In response to Bar1s

‎04-17-2012 08:11 PM

Hi Baris,

under the VCS-expressway i do not see any attempt for "unknown ip-address"??? can you post the full search attempt on expressway, i think you truncated some of the stuff.

Also what i understand is that you have second NIC connected towards with internet using NAT address defined on expressway. right?

if the calls to unknown ip-address is set to "direct" and if you have network reachability then i am thinking this to work.

Can you try to ping the external device from expressway? jsut to make sure you have reachability.

Thanks

Alok

0 Helpful

Bar1s
Level 1
Level 1

‎04-17-2012 08:39 PM

Hi Alok,

I pinging to any internet ip address, also trace and dns lookup is working for outside.

I noticed at vcsex. Default ip gateway is displayed 127.0.0.1 at bottom of the page. but i setup lan2 as default gateway.

Before i upgraded vcs control and expressway 7.0.1 to 7.1.

Is there any requirement for release key renew.

When i tried to call ip address call search details like that.

What is requirement for ip dialing suggestion ?

Regads,

Sent from Cisco Technical Support iPhone App

0 Helpful

Alok Jaiswal
Cisco Employee
Cisco Employee
In response to Bar1s

‎04-17-2012 08:56 PM

Baris,

You do not require any new release key for x7.0.1 to x7.1 upgrade. the x7 release key would be same. New rlease key is only require in case of major upgrade (for e.g. x6 to x 7 upgrade) and not for minor upgrade.

for ip dialing on expressway you need to setup the calls to unknown ip-address field to "direct".

calls for external ip-address willl hit the traversal zonee on expressway and will go out directly to internet if its reachable.

This is the recomended way for dialing to public ip-address.

Also i see you have pointed that your default gateway is wrongly setup ?please correct the configuration on the Lan1 and Lan 2 both and check again.

Thanks

Alok

0 Helpful

Bar1s
Level 1
Level 1

‎04-17-2012 09:42 PM

I am pretty sure about ip address lan1 and lan2. Also i am entered default ip address correctly and select lan2. But i dont understand why default ip address displayed like that. Also ping, trace and dns search working.

Reason can be dual interface and nat setting ?

I will try to renew settings.

Regards.

Sent from Cisco Technical Support iPhone App

0 Helpful

Alok Jaiswal
Cisco Employee
Cisco Employee
In response to Bar1s

‎04-17-2012 10:24 PM

Hi Baris,

I think you are hitting this bug "CSCtw75336" for wrong ip on default gateway.

The IPv4 default gateway status on GUI shows "127.0.0.1" while configuring default gateway IP address a part of LAN 2 segment.

Although netstat shows proper gateway status (as configured on VCS) and packet routed properly through configured gateway, so seem just display issue on GUI.

For example, configured 192.168.0.1 as default gateway (a part of LAN2 segment) and IPv4 gateway status shows "127.0.0.1".
In same condition, below is netstat result.
============================================================================
~ # netstat -rn
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
192.168.0.0     0.0.0.0         255.255.255.0   U         0 0          0 eth1
10.81.16.0      0.0.0.0         255.255.248.0   U         0 0          0 eth0
0.0.0.0         192.168.0.1     0.0.0.0         UG        0 0          0 eth1
============================================================================

so only issue remains is the calling to outside ip-address. let us know if you made any progress on it.

Thanks

Alok

0 Helpful

Bar1s
Level 1
Level 1
In response to Alok Jaiswal

‎04-24-2012 01:14 PM

Hi Gents,

This case solved by TAC,

Problem, one of link is missing. we applied before xcommand defaultlinksadd command but not fixed properly.

So we created link which is TraversalclientToTraversalsubzone. then problem was fixed. at VCSControl

weird problem, when we created traversalclient zone, link is not created. i think.

Regards,

Baris

Martin Koch
VIP Alumni
VIP Alumni
In response to Bar1s

‎04-25-2012 06:10 AM

Hi Baris! Thx for the feedback!

Not sure, can you mark the thread as asnwered with your own message?

Please remember to rate helpful responses and identify

0 Helpful
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Customers Also Viewed These Support Documents