Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Issue Call Externat-Internal VCS-E//VCS-C

Hello,

  I have configured the vcs-e with dual nic, lan 1 in dmz with nat static public IP address

lan 2: Data segment internal network without nat

vcs-c - data segment internal network

Traversal zone in the vcs-c is active

When making a call from the internet from a registered endpoint vcs-e to a registered endpoint vcs-c, the call is trying it but never established. Likewise, if it is from the internal to the Internet.

The calls from two endpoints registered on the VCS-e work perfectly.

  The firewall is configured to allow all ports.

  What is happening? in call history tells me 480 No route for bandwidth calculation.

Check in both vcs and no bandwidth limitations and no one else is using it because these are the only two testing equipment.

10 REPLIES

Issue Call Externat-Internal VCS-E//VCS-C

Hi Vianfyel,

can you check if VCS-E or VCS-C has a error for default links missing? if yes, can you try those to add using command

xcommand defaultLinksAdd.

Thnx

Alok

New Member

Issue Call Externat-Internal VCS-E//VCS-C

Hi,

Yes, default had the error for missing links, but i place the command you told me and the alarm no longer appears. And yes I have the created route. But even still does not work the call .. What else can it be?

Bronze

Issue Call Externat-Internal VCS-E//VCS-C

you should get a different error message. what's that?

there could be search rule is not configured correctly. when you make a test call from the external endpoint, can you see the call is going through the traversal zone and reaches VCSC?

New Member

Issue Call Externat-Internal VCS-E//VCS-C

Hello, I now see this when doing a debug log

FROM VCS-C

2013-08-19T14:56:34-04:-30tvcs: UTCTime="2013-08-19 19:26:34,061" Module="network.sip" Level="DEBUG": Src-ip="192.168.0.250" Src-port="7001"
SIPMSG:
|SIP/2.0 200 OK
Via: SIP/2.0/TLS 192.168.0.252:5061;branch=z9hG4bK888018d366bac477aa0f5194a00f1c81180618;received=192.168.0.252;rport=25607
Call-ID: a4ce0567e9e08ff4@192.168.0.252
CSeq: 25597 OPTIONS
From: <192.168.0.252>;tag=7615d077d48c0c27
To: <192.168.0.250:7001>;tag=ad47af41c562b4f6
Server: TANDBERG/4120 (X7.2.1)
Supported: com.tandberg.vcs.resourceusage,path,outbound,gruu
Content-Type: text/xml
Content-Length: 253

25075024991800|
2013-08-19T14:56:34-04:-30tvcs: UTCTime="2013-08-19 19:26:34,061" Module="network.sip" Level="INFO": Src-ip="192.168.0.250" Src-port="7001" Detail="Receive Response Code=200, Method=OPTIONS, To=sip:192.168.0.250:7001, Call-ID=a4ce0567e9e08ff4@192.168.0.252"
2013-08-19T14:56:34-04:-30tvcs: UTCTime="2013-08-19 19:26:34,055" Module="network.sip" Level="DEBUG": Dst-ip="192.168.0.250" Dst-port="7001"
SIPMSG:
|OPTIONS sip:192.168.0.250:7001;transport=tls SIP/2.0
Via: SIP/2.0/TLS 192.168.0.252:5061;branch=z9hG4bK888018d366bac477aa0f5194a00f1c81180618;rport
Call-ID: a4ce0567e9e08ff4@192.168.0.252
CSeq: 25597 OPTIONS
From: <192.168.0.252>;tag=7615d077d48c0c27
To: <192.168.0.250:7001>
Max-Forwards: 0
User-Agent: TANDBERG/4120 (X7.2.1)
Authorization: Digest nonce="48e9f5e5655e6944c67198a8d83b0f457e785eabfd5730cff33d3cf1c6bd", realm="TraversalZone", opaque="AQAAAEF/nuaSdwsZlU/9yaDkYYsu11E1", algorithm=MD5, uri="sip:192.168.0.250:7001;transport=tls", username="vcszone", response="0984375cc972c92cccf710183491aead", qop=auth, cnonce="9ab851059766add43edce48f0bba8c752d356945c048671f6857a04ef052", nc=00000001
Supported: com.tandberg.vcs.resourceusage
Content-Type: text/xml
Content-Length: 250

25075024970|

FROM VCS-E

2013-08-19T14:57:14-04:-30tvcs: UTCTime="2013-08-19 19:27:14,071" Module="network.sip" Level="DEBUG": Dst-ip="192.168.0.252" Dst-port="25607"
SIPMSG:
|SIP/2.0 200 OK
Via: SIP/2.0/TLS 192.168.0.252:5061;branch=z9hG4bK86b25ae20b00d0435d53847c147081cb180622;received=192.168.0.252;rport=25607
Call-ID: 0926bf9559b47e72@192.168.0.252
CSeq: 44944 OPTIONS
From: <192.168.0.252>;tag=dadc503c0fd72dba
To: <192.168.0.250:7001>;tag=c277e9fcd58a03de
Server: TANDBERG/4120 (X7.2.1)
Supported: com.tandberg.vcs.resourceusage,path,outbound,gruu
Content-Type: text/xml
Content-Length: 253

25075024991800|
2013-08-19T14:57:14-04:-30tvcs: UTCTime="2013-08-19 19:27:14,070" Module="network.sip" Level="INFO": Dst-ip="192.168.0.252" Dst-port="25607" Detail="Sending Response Code=200, Method=OPTIONS, To=sip:192.168.0.250:7001, Call-ID=0926bf9559b47e72@192.168.0.252"
2013-08-19T14:57:14-04:-30tvcs: UTCTime="2013-08-19 19:27:14,070" Module="network.ldap" Level="INFO": Detail="Authentication credential found in directory for identity: vcszone"
2013-08-19T14:57:14-04:-30tvcs: UTCTime="2013-08-19 19:27:14,070" Module="network.http" Level="DEBUG": Message="Response" Src-ip="127.0.0.1" Src-port="9998" Dst-ip="127.0.0.1" Dst-port="43284" Response="200 OK" ResponseTime="0.002725" Ref="0x7ff99c938480"
2013-08-19T14:57:14-04:-30tvcs: UTCTime="2013-08-19 19:27:14,067" Module="network.http" Level="DEBUG": Message="Request" Method="POST" URL="http://127.0.0.1:9998/credential/name/vcszone" Ref="0x7ff99c938480"
2013-08-19T14:57:14-04:-30tvcs: UTCTime="2013-08-19 19:27:14,067" Module="network.sip" Level="DEBUG": Src-ip="192.168.0.252" Src-port="25607"
SIPMSG:
|OPTIONS sip:192.168.0.250:7001;transport=tls SIP/2.0
Via: SIP/2.0/TLS 192.168.0.252:5061;branch=z9hG4bK86b25ae20b00d0435d53847c147081cb180622;received=192.168.0.252;rport=25607
Call-ID: 0926bf9559b47e72@192.168.0.252
CSeq: 44944 OPTIONS
From: <192.168.0.252>;tag=dadc503c0fd72dba
To: <192.168.0.250:7001>
Max-Forwards: 0
User-Agent: TANDBERG/4120 (X7.2.1)
Authorization: Digest nonce="db11252bdd9837ff873907242b1460d9f8292c8f88d1fab85531e0b5428f", realm="TraversalZone", opaque="AQAAAEF/nuaSdwsZlU/9yaDkYYsu11E1", algorithm=MD5, uri="sip:192.168.0.250:7001;transport=tls", username="vcszone", response="1116d99b35d3ad1ded6401fc317633c5", qop=auth, cnonce="854263bd27fac1037a1ffaeb0a892a4e6d81898aa265b153d6476ae3fa1c", nc=00000001
Supported: com.tandberg.vcs.resourceusage
Content-Type: text/xml
Bronze

Issue Call Externat-Internal VCS-E//VCS-C

Hi,

I don't see any error message in what you posted. it is wise to open a TAC case, so all logs can be looked at once.

unless you inspect the logs and see what error message you get after fixing the missing link within subzones.

regards, Ahmad

New Member

Issue Call Externat-Internal VCS-E//VCS-C

Hello,

As still the same error:

480 No route for bandwidth calculation.

I had to delete the route in the vcs-e, then went back to add the route, and then went back to the command xcommand defaultLinksAdd after I restart both VCS and the call now works perfect.

Thanks!!!!!

Issue Call Externat-Internal VCS-E//VCS-C

Hi Vianyfel,

I think ou might be a having route missing for probably the zone and that's the reason adding default links might not help.

Anyways great to hear it started working after your hardwork.

Rgds

Alok

New Member

Issue Call Externat-Internal VCS-E//VCS-C

Hi Vianfyel,

Please be aware that you have to reboot/restart VCS after making any changes with static routes.

The actual routing table you can check with "route" CLI command (use ssh and root credentials).

Best regards,

Sergey Kuzmin

Issue Call Externat-Internal VCS-E//VCS-C

Hi Vianfyel,

As Ahmad said i too don't see any errors. Now can you tell me if you still have same issue ?

are you still getting the same error message or message changed?

Rgds

Alok

Bronze

Issue Call Externat-Internal VCS-E//VCS-C

in Addition to Alok suggestion, also check whether you configured static route pointing to internal network since you are using dual port.

regards, Ahmad

439
Views
0
Helpful
10
Replies