On a related topic, is it possible to call into CTMS from endopoint registered to VCS?
EX90 -> VCS -> CUCM -> SIP Trunk -> CTMS
We have a VCS environment however we connect to another organisation's CUCM/CTS environment. Currently we use our TP Server to host conferences between our orgniasations however it would be good to be able to use their CTMS sometimes (e.g. if they have many of their own CTS endpoints connecting and we only have 1 - 2 of our endpoints in the conference).
Since CTMS does not support Native interop as of today , I would front end CTMS with MXE so u dont hit any interop issue ...we always front end with MXE and the one such scenario we tested with CTMS .for Eg : 9971 ---UCM ---UCM ----SIP trunk--- MXE --SIP T--UCM --SIP T-CTMS . if you calling from TIP capable endpoint behind VCS i dont see any reason why it would not work.if you run into any issue let us know.
Jeff, you are asking C-Series endpoints as teleworker endpoint and have it registered to UCM
C-Series -- >ISP ---->VCSe -----> UCM
VCS Expressway integration with UCM is not yet supported. traversal integration i.e traversal client is with VCS control only at present. we are actually looking into development of this new architecture with UCM.
we typically use anyconnect vpn to connect ,,, on 9971 and cius endpoints to connect to UCM enterprise.
i understand your concern,
Is this a acceptable solution ? Ex90 ---> UCM ---> VCS ---->VCSx . ex90 registering to UCM via VCS ? VCS will serve as proxy and traversal agent and the UCM feature set and registration would terminate on UCM.
In that scenerio, the endpoint registers to the VCS, not the CUCM. How can I get endpoints to register to CUCM? Is this something that's possible with CUBE?
The scenario was actually this way, Ex90 ---> ISP ---VCSx ---> VCS ---->UCM , ex90 residing in remote location ,
at present we dont have the capability in VCS to proxy the registration , the solution i mentioned above will be available sometime early next year and it being roadmapped
i think you are referring to CUBE registration pass through , if it is here are the config steps, refer to configuring support for SIP registration section in the below link
Jeff, it is possible to proxy the registration across VCSe and VCSc. traversal agent that you setup between VCSe and VCSc has to be configured to allow proxy registration and in the neighbor zone of VCSc that connects to UCM via SIP trunk has to be set to allow proxy registration. in this case the register packets from teleworker site will be funnneled all the way to UCM.
I'm wondering what are the advantages and disadvantages of registering EX60/EX90 end points to CUCM 8.6+ as opposed to registering them to a VCS. Thanks.
1. you can leverage BFCP support on the endpoints and do presentation share with other UCM video capable endpoints
2. if you just have Unified communications in your enterprise you can leverage these gears for point to point video call with other UCM video capable endpoints , like Ex90 --- to ---- CTS with no xcoder in between
3. endpoints support TIP
4. you can join adhoc video conference from these phones
5. High resolution video
6. you can leverage same voicemail system that is being used for UCM phones
Register endpoints to VCS when these are required
We want to setup our VCS starter pack in our DMZ so that movi clients may register through the internet. Also we want to be able to make and allow calls in to our system from an systems external to our VCS.
Reading the support forum I see people insisting that you must have the dual NIC option with static NAT enabled. At the same time I was given the impression that you do this NAT in your ASA.
Does the VCS really need to have a public ip on one interface to accept external calls/registrations?
I currently have an external dns zone setup, if I initiate external call from inside will this call succeed even though VCS has private ip behind firewall?
Please look as VCS control /expressway deployment guide found at the link
what holds true for the Expressway holds true for the starter pack, If you want to use static NAT on VCS you need the dual network interfaces key.
the call needs to be delivered to the VCS and if you do not have dual network interfaces the call must not have a NAT between it and the endpoint
.. so simple answer is NO VCS does not need to have a public IP, but it depends on your configuration ,
...also signalling should work, but VCS will send media to private IP address, will other device be able to send media to that address? is the expressway behind a firewall?
Thanks for your answer.
Well I see your point. Expressway is behind a firewall and firewall holds the public ip address anyway.
To answer my last question " I currently have an external dns zone setup, if I initiate external call from inside will this call succeed even though VCS has private ip behind firewall? "
I tested today and this holds true. I called an engineer by calling email@example.com and call was established between us even though VCS was internal to my network. I can understand that my call being initiated from the inside allowed traffic back into the VCS and my endpoint. My idea was if this works why cant it work in reverse?
Well thanks again for the insight!
Is IP address of VCS a routable address as far as endpoint is concerned, or is outside calling device registered to the VCS?
What IP forwarding has been set up in the outside firewall?
I am assuming a config:
VCS – Firewall – network – Endpoint
Please provide details of IP address of VCS, and IP address of outside firewall in DMZ.