H.245 deliver VCS - C / VCS-E

Hi all

We have problems with our VCSC and vcse, when we call to our neighborzone (CUVCM - 3515/3545).

The H.225 (RAS and Q.931) works fine, but the H.245 process fails.

The call immediately, disconnect cause: normal compensation call.

This is a diagnostic log file in debug mode:

"tanvcsx01 tvcs: elements UTCTime =" 2012-06-04 09:27:28, 769"Module =" network.h323 "Level ="INFO": Dst - ip ="10.133.246.20"Dst-port ="1719 ".

Detail = "sending RAS RSQ SeqNum = retransmission 46766 = True"

4 Jun 11:27:32 tanvcsx01 tvcs: elements UTCTime = "2012-06-04 09:27:32, 169" Module ="network.tcp" Level = "ERROR": Src - ip = "10.150.246.51" Src-port = "15457" Dst - ip = "10.49.4.201" Dst-port = detail "11247" = 'TCP connection failure' "

"4 Jun 11:27:32 tanvcsx01 tvcs: elements UTCTime =" 2012-06-04 09:27:32, 169"Module =" network.h323 "Level ="ERROR": Dst - ip ="10.49.4.201"Dst-port ="11247.

Detail = "unable to connect outbound H.245 TCP connection. Rejecting the H.245 TCP incoming connection requests. »

4 Jun 11:27:32 tanvcsx01 tvcs: elements UTCTime = "2012-06-04 09:27:32, 169" Module ="network.tcp" Level = "DEBUG": Src - ip = "10.151.1.51" Src-port = "17588" Dst - ip = "10.150.246.51" Dst-port = detail '2776' = "TCP connection is closed" "

"4 Jun 11:27:32 tanvcsx01 tvcs: elements UTCTime =" 2012-06-04 09:27:32, 201"Module =" network.h323 "Level ="INFO": Src - ip ="10.151.1.51"Src-port ="17623.

Detail = "" call received H.225 ReleaseComplete Q.931 Cause: Normal, clearing, H.225, reason Cause: unknown, more info: None ""

"4 Jun 11:27:32 tanvcsx01 tvcs: elements UTCTime =" 2012-06-04 09:27:32, 201"Module =" network.h323 "Level ="DEBUG": Src - ip ="10.151.1.51"Src-port ="17623.

Thanks for the help,

Stefan,

There seems to be something in the network by blocking the attempt to connect TCP VCS - E endpoint (the attempt to connect to 10.150.246.51 port 15457 to 10.49.4.201 port 11247).

You have no idea why this is happening? Is there a firewall/switch ACL that may be responsible for this block?

Tags: Cisco Support

Similar Questions

Calls disconnect unexpectedly after a fixed period of CODIAN and VCS

I have the following problem:

Media codian blade use the VCS control as a goalkeeper.

One day, when do the new conference of the codian (or MSD)... AFTER 2 hours and 15 seconds, the present end point at the Conference to close the connection. In the paper, I see messase 'normal clear call '.

In the debugging of vcs log, I see in the same second:

in the log, I see the call disconnected... message endpoint leave the Conference with number 3315 (is the virtual room)

the first request was born form point endpoint or the codian? the programmer, there are the same time.

I don't know what can do to see if it is present a timer in the VCS control configuration.

Until there are, the problem was not present. I don't know what is coming.

Is possible that endpoint to signal to close the Conference?

Thanks for your help

FCostalunga

ECO

Unfortunately, these screenshots and the event of VCS log extract provide really enough information to explain why the call drops, and I therefore recommend that you open a case with TAC so that appropriate newspapers can be collected to solve the problem more far.

Best regards

Andreas

MX200 (TC6.2) cannot save with SIP TLS for control of VCS

Hi all

I just got a brand-new MX200 in our laboratories.

We will evaluate at the moment the overall upgrade to the version sw TC6.2.

The MX200 was delivered with TC6.1.1.7. Check in the control of VCS with SIP TLS works without any problem at all.

VCS - C eventlog:

"26 aout 14:16: 47 tvcs: event ="Accepted for registration"Service ="SIP"Src - ip ="172.18.93.88"Src-port ="5061"Protocol ="TLS"AOR ="[email protected] / * /"Contact =" sip:[email protected]/ * /: 5061; transport\ = tls"duration ="60"Level = '1' elements UTCTime = '2013-08-26 14:16:47, 833'

"26 aout 14:16: 47 tvcs: event ="The requested record"Service ="SIP"Src - ip ="172.18.93.88"Src-port ="5061"Protocol ="TLS"AOR ="[email protected] / * /"Contact =" sip:[email protected]/ * /: 5061; transport\ = tls"duration ="60"Level = '1' elements UTCTime = '2013-08-26 14:16:47, 831'

After registration TC6.2 update fails.

The 26 aout 14:36: 26 tvcs: event = "Rejected registration" reason = "Received no authenticated source" Service = "SIP" Src - ip = "172.18.93.88" Src-port = "36545" Protocol = "TLS" AOR = "sip:DOMAIN.com" Contact ="<>[email protected]"/ * /: 5061;transport\=tls>;+sip.instance\= '"" duration = '3600' level = '1' elements UTCTime = "2013-08-26 14:36:26, 481"

26 aout 14:36: 26 tvcs: event = "The requested record" Service = "SIP" Src - ip = "172.18.93.88" Src-port = "36545" Protocol = "TLS" AOR = "sip:DOMAIN.com" Contact ="<>[email protected]"/ * /: 5061;transport\=tls>;+sip.instance\= '"" duration = '3600' level = '1' elements UTCTime = "2013-08-26 14:36:26, 481"

As far as I can see there's something doesn't quite work with the protocoll in relationship with the SIP URI (AOR). Miss me the prefix "[email protected] / * /"

All other systems (profile, ex, sx) work properly with TC6.2.

Anyone have an idea?

Hi adil,.

Since the inscription "AOR" is only said AOR = "sip:DOMAIN.com"

I belive you must have some sort of rule research on the VCS the sip domain and pointing to the crossing or a nearby area and the policy setting must be "audit powers.

and since there is no name of user and password available the record attempts will fail with the message "from source" unauthenticated

did you recently create transformations on the VCS? also, check your configuration of endpoint.

You can create a rule to send this registration through local area message passing in turn to the subzone to registration. Please note the subfield must be set on "treat as authenticated" If you do not use authentication.

Rgds

Alok

Question of syslog VCS

Everything started working with VCS/TMS, group get our syslogs asks me a few questions. The events are connected on the syslog seem to correspond to events since the events and Configuration logs, but do not seem network logs appears.

Here are the specs:

VCS - ver7.1

Under system > Logging > Log level = 2

Not sure if this is normal or not?

Hi David,

syslog on VCS only provides the event logs. He also noted the network logs but relating to SIP messages. see the Administrator's guide for x7.1 for more updates.

http://www.Cisco.com/en/us/docs/Telepresence/infrastructure/VCs/admin_guide/Cisco_VCS_Administrator_Guide_X7-1.PDF

Assigned level events

Level

High-level events such as registration and attempts to call. Easily human-readable. For example:

call n attempt/connected/disconnected

n record attempt/accepted/rejected

Level

All level 1 events, more:

n logs of sent and received messages Protocol (SIP, H.323, LDAP, etc.) excluding loud messages

as H.460.18 KeepAlive and video H.245 fast-updates

Level

All level 1 and level 2 Events, more:

Protocol n KeepAlive

n SIP calls and signaling messages

Level

The more detailed level: all level 1, level 2 and level 3 events, more:

SIP n network level messages

You can control which events are logged by the VCS by setting the log level. All events with a level

numerically equal to and below that the specified logging level are recorded in the event log. Thus, at level 1,

Only level 1 events are recorded; at level 2, level 1 and level 2 events are recorded and so on. The default journal

level is 1.

Note that:

n logging at level 3 or 4 is usually not recommended because the event log may contain a maximum of 2 GB of data

and logging at these levels on a busy system can cause the event log be recycled too quickly.

Thank you

Alok

2 MCU and VCS Expressway, routing problem

Hi all

We have a design with a group of control VCS (2 members), cluster VCS Expressway (2 members), and a couple of microcontrollers (registred H.323 on VCS control cluster with the same prefix: 90).

Each highway has a public IP address and incoming calls from outside can only be routed to microcontrollers:

[email protected]/ * / for MCU_1 and [email protected]/ * / for MCU_2 (we don't have external DNS resolution).

I put a conversion into motorway of VCS to change [email protected]/ * / to [email protected] / * / and [email protected]/ * / to [email protected] / * /.

The problem is when someone calls [email protected]/ * / sometimes (randomly) the call is routed to MCU_2 (instead of MCU_1) and if the appellant see the auto attendant.

The occcurs even then of the appeal [email protected]/ * / (MCU_2), sometimes the call is routed to MCU_1.

Any idea what can cause this device or a way to make it work well?

Thanks for help.

José

I think still that separate prefix would work, but here are a few ideas:

Are incoming calls which do not possibly using SIP that is being interoperability H323 or incoming calls all certainly the H323?

If you want to keep pure H323, you could perhaps just have a search rule/turn on your VCS-E who changed [email protected] to an E164 e.g. 90... and had a search on your VCS - C rule that says 90... stop at the local area.

I also noticed that you direct calls to [number]@MCU-IP - have you tried to direct all calls to [number]@VCS-C IP instead? If the VCS is the holder of a registration for a number, it should be able to deliver accordingly.

Change caller id / name of the SIP URI of VCS calls

Hello

I have clusted CUCM 9.1 with a SIP to a VCS - C trunk. When making calls, the calls show a caller id of [email protected] / * / address, for example [email protected] / * /. I have a configuration URI directory on the phone that generates the call, but now it shows the URI. Incoming calls from SIP URI properly.

Thank you

Hello

On the trunk SIP for VCS, under outgoing calls, there should be an adjustment: vocation and connected part format, change it to URI deliver only partially connected. Also, under the profile SIP assigned to the SIP trunk to VCS, there should be a setting use entirely field in queries, check this box. The SIP profile should also be attributed to the device SIP calls.

HTH, if yes, please rate.

TMS IS involved in a VCS database call

Hi guys,.

I am just geeting my head around such empty things, so please easy tale about me

I was watching a call log FRO a call between a VC VC. And I saw these lines below. Can someone please clarify how the TMS is involved in the call flow. I can see the VCS C requesting a license manager and by sending a POST request to the TMS... Are TMS of the License Manager? or VCS are just inform the TMS of the call?

2014 01-28 T 23: 36:16 + 00:00 SCR01-GROUND-AFREN tvcs: elements UTCTime = "2014-01-28 23:36:16, 228" Module ="network.http" Level = "DEBUG": Message = 'Request' method = 'POST' URL ='http://127.0.0.1:9999/licensemanager/acquire"Ref ="0x5369d10 ".
2014 01-28 T 23: 36:16 + 00:00 SCR01-GROUND-AFREN tvcs: elements UTCTime = "2014-01-28 23:36:16, 229" Module ="network.http" Level = "DEBUG": Message = "Request" method = "POST", URL ="http://127.0.0.1:4370 / status/call/call/uuid/fb147b6a-8874-11e3-8ddf-0010f31e26cc" Ref = "0x53c3c70".
"2014 01-28 T 23: 36:16 + 00:00 SCR01-GROUND-AFREN tvcs: elements UTCTime ="2014-01-28 23:36:16, 231"Module =" network.http"Level ="DEBUG": Message = 'Response' Src - ip ="127.0.0.1"Src-port ="4370"Dst - ip ="127.0.0.1"Dst-port = '40056' response =" 200 OK "ResponseTime ="0.001804"Ref ="0x53c3c70 ".
"2014 01-28 T 23: 36:16 + 00:00 SCR01-GROUND-AFREN elements UTCTime ="2014-01-28 23:36:16, 234"Module =" developer.licensemanager.service.manager"Level ="INFO"CodeLocation =" licensemanager (132) ' detailed = "License" call_id = "fb147aca-8874-11e3-8b16-0010f31e26cc" lic_type = "nontraversal".
2014 01-28 T 23: 36:16 + 00:00 SCR01-GROUND-AFREN licensemanager: Level = 'INFO' detailed = "License" call_id = "fb147aca-8874-11e3-8b16-0010f31e26cc" lic_type = "nontraversal" elements UTCTime = "2014-01-28 23:36:16, 234"
"2014 01-28 T 23: 36:16 + 00:00 SCR01-GROUND-AFREN tvcs: elements UTCTime ="2014-01-28 23:36:16, 235"Module =" network.http"Level ="DEBUG": Message = 'Response' Src - ip ="127.0.0.1"Src-port ="9999"Dst - ip ="127.0.0.1"Dst-port = '40133' response =" 200 OK "ResponseTime ="0.006763"Ref ="0x5369d10 ".
2014 01-28 T 23: 36:16 + 00:00 SCR01-GROUND-AFREN tvcs: elements UTCTime = "2014-01-28 23:36:16, 237" Module ="network.dns" Level = "DEBUG": detail = "Query DNS sending" name = 'AFREN-SOL - STM01.afren .net .net' Type = ' has or AAAA ""
2014 01-28 T 23: 36:16 + 00:00 SCR01-GROUND-AFREN tvcs: elements UTCTime = "2014-01-28 23:36:16, 237" Module ="network.tcp" Level = "DEBUG": ip - Src = "192.168.0.171" Src-port = "17642" Dst - ip = "192.168.68.142" = "1720" detail = "TCP connection" Dst-port "
2014 01-28 T 23: 36:16 + 00:00 SCR01-GROUND-AFREN tvcs: elements UTCTime = "2014-01-28 23:36:16, 238" Module ="network.http" Level = "DEBUG": Message = "Request" method = "POST", URL ="http://127.0.0.1:4370 / status/call/call/uuid/fb147b6a-8874-11e3-8ddf-0010f31e26cc" Ref = "0x53c3c70".
2014 01-28 T 23: 36:16 + 00:00 SCR01-GROUND-AFREN tvcs: elements UTCTime = "2014-01-28 23:36:16, 238" Module ="network.dns" Level = "DEBUG": detail = "resolved host name to: ['IPv4"TCP"192.168.0.175'] (A/YYYY) number of records retrieved: 1"
2014 01-28 T 23: 36:16 + 00:00 SCR01-GROUND-AFREN tvcs: elements UTCTime = "2014-01-28 23:36:16, 238" Module ="network.tcp" Level = "DEBUG": Dst - ip = "192.168.0.175" Dst-port = '80' retail = "TCP connection" "
2014 01-28 T 23: 36:16 + 00:00 SCR01-GROUND-AFREN tvcs: elements UTCTime = "2014-01-28 23:36:16, 238" Module ="network.tcp" Level = "DEBUG": ip - Src = "192.168.0.171" Src-port = "40343" Dst - ip = "192.168.0.175" Dst-port '80' retail = "TCP connection" = "
"2014 01-28 T 23: 36:16 + 00:00 SCR01-GROUND-AFREN tvcs: elements UTCTime ="2014-01-28 23:36:16, 241"Module =" network.http"Level ="DEBUG": Message = 'Response' Src - ip ="127.0.0.1"Src-port ="4370"Dst - ip ="127.0.0.1"Dst-port = '40056' response =" 200 OK "ResponseTime ="0.003146"Ref ="0x53c3c70 ".
2014 01-28 T 23: 36:16 + 00:00 SCR01-GROUND-AFREN tvcs: elements UTCTime = "2014-01-28 23:36:16, 245" Module ="network.tcp" Level = "DEBUG": ip - Src = "192.168.0.171" Src-port = "17642" Dst - ip = "192.168.68.142" = "1720" detail = "TCP connection" Dst-port "
"2014 01-28 T 23: 36:16 + 00:00 SCR01-GROUND-AFREN tvcs: elements UTCTime =" 2014-01-28 23:36:16, 245"Module =" network.h323 "Level ="INFO": Dst - ip ="192.168.68.142"Dst-port ="1720 ".

Please note all useful posts

"The essence of Christianity is not the induction, but the Self-effacement - William Barclay"

Hello

In this case, the License Manager's internal VCS code - take care of the course and non-traversal call licenses etc.

Every Post in your logs requests will the VCS loopback address - 127.0.0.1 - VCS talking to himself.

Thank you

Guy

HDX 8000 on VCS not sending Video - H.264/H.323

Hi guys,.

I need a little help to make heads or tails of a few H.241/H.245 of e-mail that seems to show the VCS rejecting the video from the HDX 8000 registered as H.323. The other device in the call (opening) is a DX70. The HDX 8000 receives audio and video of the DX70, however the DX70 receives only audio. A capture of packets on the VCS shows no video of the HDX 8000, and media stats thus confirm the absence of video. I have the tool some diagnostic logs of the call which shows a rejection of OLC for H.264.

Call flow is DX70-> CUCM-> SIP Trunk-> VCS-> HDX 8000

I cut the video clips of sent TCS and OLC received underneath. I don't know what the problem is that my understanding of these protocols is quite limited, and I'm not sure what I can do on VCS or possibly CUCM to fix. The HDX 8000 has no support so I have more luck there.

Apparently it worked for them before their call manager has been upgraded to 11 or so claimed. VCS is on 8.6

Rejection of the OLC:

Module = "Developer.IWF" level = 'ERROR' CodeLocation="ppcmains/oak/calls/iwf/IWFLCListMgr.cpp(315)" method = "IH245OLCRejResponseMsg::CauseCode IWFLCListMgr::updateInboundOLCListForOLC" = "0x7f749ed6f700" Thread: State = "IWFConnectedState" Global-CallId="2e9acc06-a188-4712-b9da-4698eca8d34f' Local-CallId="6d42819b-205d-454f-ae95-5a283199f74c' Sip-CallId ="[email protected]"/ * / ' Local-Tag = "f653265efcb77e05" Remote-Tag="2397002~70309dbf-e7dd-4b85-aad8-82d36153a410-45698833" H225-ip = "10.176.11.130" H225-port = "1720" H245-ip = "10.176.11.130" H245-port = '39551' last States = 'IWFAwaitingTCSState IWFAwaitingAckWithSdpAnswerState IWFAwaitingMSDCompleteState IWFSipConnectedConnectingH323State IWFConnectedState' received an OLC for cap: 0: [109] 90000 bitrate: 17920 hbits/s video H264 [tags = 2 profile_level_id = {profile_idc = 66 " [{, profile_iop = 0, level_idc = 13}, max_mbps = 23500, max_fs = 3840, max_br = 1500, packetization_mode = NAL] was in the CHT sent sideways H323, therefore not sending an OLC reject. The TCS has sent confined: Capset(2) contains 5 items for packaging: rfc3984nil

Did a bit of translation for the params are collapsing, but I won't pretend that I really understand them.

Video caps from TCS (VCS):

videoCapability
{
genericVideoCapability:
{
standard capabilityIdentifier: {0 0 8 241 0 0 1},.
maxBitRate 18560,
collapse
{

{
standard parameterIdentifier: 41, * profile: Basline profile
parameterValue booleanArray: 64
},

{
standard parameterIdentifier: 42, * level: 2.2
parameterValue unsignedMin: 57
},

{
standard parameterIdentifier: 3, * CustomMaxMBPS
parameterValue unsignedMin: 534
},

{
standard parameterIdentifier: 4, * CustomMaxFS
parameterValue unsignedMin: 34
},

{
standard parameterIdentifier: 8, * rcmd-nal-unit-maximum size
parameterValue unsigned32Max: 256000
},

{
standard parameterIdentifier: 13, * not sure, can't find documentation on this
parameterValue unsignedMin: 6000
}
}
}
}

Video clips OLC received (from HDX):

videodata data type: genericVideoCapability:
{
standard capabilityIdentifier: {0 0 8 241 0 0 1},.
maxBitRate 17920,
collapse
{

{
standard parameterIdentifier: 41, * profile: Basline profile
parameterValue booleanArray: 64
},

{
standard parameterIdentifier: 42, * level: 1.3
parameterValue unsignedMin: 36
},

{
standard parameterIdentifier: 3, * CustomMaxMBPS
parameterValue unsignedMin: 216
},

{
standard parameterIdentifier: 6, * CustomMaxBRandCPB
parameterValue unsignedMin: 60
},

{
standard parameterIdentifier: 4, * CustomMaxFS
parameterValue unsignedMin: 15
}
}
}

What version of your Polycom software runs on? We had a lot of problems with Polycom HDXs prior to version 3 of the software running. It is highly recommended that you update the Polycom if it is on an older version, not only for reasons of compatibility, but also to address all security vulnerabilities in previous versions of the software (software, Shellshock, GHOST, etc.).

Wayne
--
Remember the frequency responses and mark your question as answered as appropriate.

integration of lync 2013 with cisco vcs - c

Hello

I found a lot of documentation on integrating to Lync 2010 with VCS - C, but can't find much on the integration of Lync 2013. Could someone shine some light on this for me?

Thank you!

Hi, David,.

It would be preferable that you contacted Cisco re: integration

https://supportforums.Cisco.com/thread/2181356

Cisco PDF

Or try to repost your question to the TechNet Forum

http://social.technet.Microsoft.com/forums/en-us/ocsinterop/thread/319f9e94-f7ec-4c6e-994C-f5412e345e2e

Question about the design of VCS-C/VCS-E

Hello

Customer has no DMZ. So, what are my options to configure a deployment of VCS-C/VCS-E?

How is it I could reach the goal that VCSC and VCSe contact area of neighbor?

Do I need to assign an internal IP address (without static nat) and LAN2 in also an IP address in-house with NAT static external IP LAN1.

Prerequisite for which is 'Dual touch Option NIC', no?

At the moment I have no double key Option of NIC, then the only way in my deployment is the DMZ preffered way, right? Or make me another option?

Concerning

Thorsten

Well, in this case, you can have the VCS-E in public, VCS - C behind the firewall and an area between the two.

You can increase the security nat'ing and with who use dual NICs on the VCS-E option.

I also either turn off or at least to block SSH on VCS-E to the public.

Deployment 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

/Jens

Cisco VCS and integration Lync2013

Hello!

Could you tell me please, when CISCO officially support Lync2013 - free new software for VCS - C and documentation on integration?

The main interest is the possibility of transferring video between CISCO/MCU and Lync endpoints on the H.264 Protocol, who hails from Lync2013.

Right now, I've got VCS - C and RTM Lync2013 X7.2. During the video call without AMGW appeal established as audio only.

When using with Lync2010, it worked on Protocol H.263 and CIF resolution.

Evgeniy salvation,

We are currently investigating the possibilities to achieve interoperability between Lync 2013, VCS and video devices on the side of the VCS standards-based, it is a work in progress and at this stage, it is to early to provide any factual information on when interop will be available.

In contrast to Lync 2010, Lync 2013 does not support H.263 for video and it so that will remove the OCS/Lync integration. I do however think that you should be able to make a two-way video between Lync 2013 and VCS-joined endpoints if you use an AMGW tried that yet?

Thank you

Andreas

VCS followed Analyzer?

Greetings,

Is it possible within the VCS C or E, call records for billing and calls for performance analysis. I work in the health field and I want to keep track of the devices registered to the guards and how long it was a call if everything was done. Is there a way to retreat this type of information on the VCS logs somehow to push to a .csv file?

VCS is not a way to generate reports, you must use something like TMS for this. To keep track of what endpoints are registered in the VCS, there is no report to do this, so you will need to check active listings and history of the markings on the VCS itself. For CDR data, as long as the VCS or endpoints are added to the MSD, you can generate a report > Call Detail Record.

Restricting calls between a subarea and specific extensions on Cisco VCS

Hello, I use Cisco VCS 8.5.3, my goal is to restrict calls between a subarea and specific extensions.
I tried following solutions:

Download of XML strategy
Use of political appeal web interface in order to limit calls

XML file:

But when I apply the XML file, or try using the web simple rule (for example: 11111 12222 destination source, dismiss the action) I'm still able to place the call to 11111 to 12222.

What can be the cause of the problem and what else can I try to be able to prohibit calls between a particular Subzone and exentions?

Attached, is an example of CPL script that should work. Using this script, CPL, I was able to block calls to a subarea set to a destination alias located in the subzone of default and was always able to call any other end point in the default subfield without problem. Note that you must enter the name of the subarea, as you have configured on the VCS, including spaces if they exist.

The scenario is based on the example of CPL "limiting access to a local gateway" X8.5 VCS Administrator's Guide on pg 413, other documents of CPL reference and examples can be seen starting on pg 410.

VCS X8.1 search fields

Updated our VCS to X8.1 according to the TAC suggests perhaps a problem and noticed that the search boxes on the registration pages are gone. Haven't checked the other pages, but noticed when I went to see if someone has been registered on this page for you. Without the search fields, find a record can get heavy if you have lots of records.

Anyone else notice?

Hi Patrick, I checked our internal documentation and the X 8 release notes, and I don't see this mentioned as intentional. I filed the bug No. CSCun57539 to describe this withdrawal and ask for the updated documentation to reflect that if it was on purpose.

-Jonathan

Control of VCS and VCS expressway design

I have a problem with the design of control and track Express VCS. Now, here's two VCS control and a highway. As you know, put on the Internet Highway and a control on my seat. At the same time, I want to put the other control on the management of my company which is in another city. Can it work correctly? How dose it work?

You must create two zones on VCS Expressway crossing server and a customer journey area by control VCS.

In other words, you should have a link path by VCS - C connection VCS-E separately.

Please be sure to set different H.323/SIP port on each VCS - C.

For example:

VCS - C1 (Headquarters): area of traversal client pointing to VCS-E 6001 as port H323 and SIP traversal port 7001.

VCS - C2 (branch): area of traversal client pointing to VCS - E with 6002 as port H323 and SIP traversal port 7002.

VCS-E: a traversal server zone list for VCS - C1 (6001 as port H323 and SIP traversal port 7001) and other traversal server list for VCS - C2 (6002 as port H323 and SIP traversal port 7002)

1 February 14:10:54	"" "" "" TVCS: event = "call disconnected" Service ="H323" Src - ip = "media_blade_ip_address" Src-port ="63029" type-aliases-Src = "H323" CBC-alias ='3300"CBC-alias-type ="E164"CBC-alias ='3315" Dst - ip = "ip_Endpoint" serial number Call = "62c91b6e-4cc5-11e1-b738-0010f320109c" Tag ='62c91c86-4cc5-11e1-9c2b-0010f320109c"Protocol ="TCP"Level ="1"elements UTCTime ='2012-02-01 13:10:54, 904"
1 February 14:10:46	"" "" "" "TVCS: event ="Message sent"Service ="H.245"Message-type ="CloseLogicalChannelRequest"Src - ip ="IP_VCS_CONTROL"Src-port ="15741"Dst - ip ="ip_Endpoint"Dst-port ="9012"call-number ="62c91b6e-4cc5-11e1-b738-0010f320109c"Tag ='62c91c86-4cc5-11e1-9c2b-0010f320109c" detail = "LCN:62" Protocol ="TCP" Level = "3" elements UTCTime = '2012-02-01 13:10:46, 935"
1 February 14:10:46	"" "" "" TVCS: event = "Message received" Service ="H.245" Message-type = "CloseLogicalChannelRequest" Src - ip ="media_blade_ip_address" Src-port = "63028" Dst - ip ="IP_VCS_CONTROL" Dst-port = "15577" call-number ="62c91b6e-4cc5-11e1-b738-0010f320109c" Tag = "62c91c86-4cc5-11e1-9c2b-0010f320109c" detail ="LCN:62" Protocol = "TCP" Level = "3'elements UTCTime ='	1 February 14:10:46	"" "TVCS: Event =" Message sent "Service ="H.245"Message-type ="CloseLogicalChannelRequest"Src - ip ="IP_VCS_CONTROL"Src-port ="15741"Dst - ip ="ip_Endpoint"Dst-port ="9012"call-number ="62c91b6e-4cc5-11e1-b738-0010f320109c"Tag ='62c91c86-4cc5-11e1-9c2b-0010f320109c" detail ="LCN:61" Protocol ="TCP" Level = "3" elements UTCTime ='2012-02-01 13:10:46, 925"
1 February 14:10:46	"" "" "" TVCS: event = "Message received" Service ="H.245" Message-type = "CloseLogicalChannelRequest" Src - ip ="media_blade_ip_address" Src-port = "63028" Dst - ip ="IP_VCS_CONTROL" Dst-port = "15577" call-number ="62c91b6e-4cc5-11e1-b738-0010f320109c" Tag = "62c91c86-4cc5-11e1-9c2b-0010f320109c" detail ="LCN:61" Protocol = "TCP" Level = "3" elements UTCTime ='2012-02-01 13:10:46, 925"
1 February 14:10:46	"" "" "" TVCS: event = "Message sent" Service ="H.245" Message-type = "CloseLogicalChannelAckResponse" Src - ip ="IP_VCS_CONTROL" Src-port = "15741" Dst - ip ="ip_Endpoint" Dst-port = "9012" call-number ="62c91b6e-4cc5-11e1-b738-0010f320109c" Tag = "62c91c86-4cc5-11e1-9c2b-0010f320109c" detail ="LCN:1" Protocol = "TCP" Level = "3'elements UTCTime ='	1 February 14:10:46	"" "" "" "TVCS: Event ="Message received"Service =" "H.245" Message-type ="CloseLogicalChannelAckResponse" Src - ip = "media_blade_ip_address" Src-port ="63028" Dst - ip = "IP_VCS_CONTROL" Dst-port ="15577" call-number = "62c91b6e-4cc5-11e1-b738-0010f320109c" Tag ='62c91c86-4cc5-11e1-9c2b-0010f320109c"detail ="LCN:1"Protocol ="TCP"Level ="3"elements UTCTime = '2012-02-01 13:10:46, 915"
1 February 14:10:46	"" "" "" TVCS: event = "Message sent" Service ="H.245" Message-type = "CloseLogicalChannelAckResponse" Src - ip ="IP_VCS_CONTROL" Src-port = "15741" Dst - ip ="ip_Endpoint" Dst-port = "9012" call-number ="62c91b6e-4cc5-11e1-b738-0010f320109c" Tag = "62c91c86-4cc5-11e1-9c2b-0010f320109c" detail ="LCN:2" Protocol = "TCP" Level = "3" elements UTCTime ='2012-02-01 13:10:46, 905"
1 February 14:10:46	"" "" "" TVCS: event = "Message received" Service ="H.245" Message-type = "CloseLogicalChannelAckResponse" Src - ip ="media_blade_ip_address" Src-port = "63028" Dst - ip ="IP_VCS_CONTROL" Dst-port = "15577" call-number ="62c91b6e-4cc5-11e1-b738-0010f320109c" Tag = "62c91c86-4cc5-11e1-9c2b-0010f320109c" detail ="LCN:2" Protocol = "TCP" Level =62c91c86-4cc5-11e1-9c2b-0010f320109c"Protocol ="TCP"Level ="3"elements UTCTime ='2012-02-01 13:10:46, 905"
1 February 14:10:46	"" "" TVCS: Event = "Message received" Service ="H.245" Message-type = "EndSessionCommand" Src - ip ="ip_Endpoint" Src-port = "9012" Dst - ip ="IP_VCS_CONTROL" Dst-port = "15741" call serial number ="62c91b6e "

H.245 deliver VCS - C / VCS-E

Similar Questions

Maybe you are looking for