I am doing a new implementation at one of client location, below are devices:
1. TMS 14.3 with tmep 1.1
2. VCS-c x7.2.1
3. VCS-e x7.2.1
Need your suggestion on configuration of VCS-e, i don't have dule Nic card lic.
n/w goes like this client have one firewall sonicwall 4500 , 6 port. behind that having only one n/w subnet.
I have configured TMS and VCS-c and things are working fine for internal endpoints.
TMS (192.168.10.32) ---- VCS-s(192.168.10.40)----VCS-e(192.168.10.217) got static 1 to 1 net at firewall with public ip 203.x.x.x
when i am pointing traversal client zone towards local ip of VCS-e i.e 192.168.10.217 both SIP and H323 connections are ok , but i am not able to register any endpoint to VCS-e Jabber is also not able to login.
Same way if i am pointing traversal client zone towards Public ip i.e. 203.x.x.x at VCS-s end both SIP and H.323 both protocols are up ,, but at VCS-e end only H.323 protocol is up SIP says failed. In this conf. also i am not able to register any endpoint at VCS-e.
Please suggest if both VCS-c and VCS-e and same subnet will work out or i need to look for some other concept.
It was somthing related to firewall , i got public IP for VCS-e and now its working.
I have one requirement from client,, they are having one Ex90 system that is used for monitoring of Hospital ICU's ,, ICU systems are C20 and dont have any monitor installed, all c20 systems are on auto answer.
Whenever Doctors from from Command center calls C20 it will getting auto answered and they can monitor full ICU.
Problem is if any one dial to C20 system from there I-pad, from EX90 they cant connect,is there any work arround in VCS that when we are a call from command center ussing Ex90 , one to one between C20 and I-pad get disconnect and Ex90 will connect automatically.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...