Cisco VCS X7.1 RFC 4480 support (Rich Presence)

Hi all,
This is regarding Cisco VCS-C X7.1 or 7.2.
We’re trying to implement Rich Presence (RFC 4480) which is stated as supported in this document (page 34):
http://www.cisco.com/c/dam/en/us/td/docs/telepresence/infrastructure/vcs/release_note/Cisco_VCS_Release_Note_X7-1.pdf
However, the VCS returns “Online” indication even if the system in question is in a call. There’s no “busy” status for some reason. I’m referring to the SIP PUA which gives an option for using the presence even with H.323 endpoints, given their registration in a form of URI.
Is the Rich Presence supported for Jabber only?
Thanks!

Rich Presence isn't available for the normal endpoints, only the SIP SIMPLE status generated by the Presence User Agent (PUA). From the on-line help:
Endpoints that do not support presence can have status published on their behalf by the VCS. The service that publishes this information is called the Presence User Agent (PUA).
The PUA takes information from the local registration database and the call manager and determines, for each endpoint that is currently locally registered, whether or not it is currently in a call. The PUA then provides this status information via a PUBLISH message.
For the PUA to successfully provide presence information about a locally registered endpoint:
The endpoint must be registered with an alias in the form of a URI.
The domain part of the URI must be able to be routed to a SIP registrar that has a presence server enabled. (This could be either the local Presence Server, if enabled, or another Presence Server on a remote system.)
When enabled, the PUA generates presence information for all endpoints registered to the VCS, including those which already support presence. The status information provided by the PUA is either:
online (registered but not in a call)
in call (registered and currently in a call)
The PUA will update and publish presence information on receipt of:
a registration request (for new registrations)
a registration refresh (for existing registrations)
a deregistration request
call setup and cleardown information
Wayne
Please remember to rate responses and to mark your question as answered if appropriate.

Similar Messages

JDBC---RFC will Support Sync?????????

Hi All,
Wil JDBC--RFC Senario supports for Sync Comunication with out using BPM???
Regards
Vamsi

Hi Vamshi,
For JDBC (Sender/Receiver )Scenario we have to Install the JDBC Drivers on XI Server.
Use those Driver name and Connection in JDBC Adapter to connect to the Database.
For RFC Sender Adapter we have to create the Program ID in SAP R/3 side.
For RFC Receiver no need of any Extra settings.
step by step RFC to JDBC scenario
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/step%2bby%2bstep%2brfc%2bto%2bjdbc%2bscenario
Tips and Tutorial for Sender JDBC Adapter
/people/yining.mao/blog/2006/09/13/tips-and-tutorial-for-sender-jdbc-adapter
http://help.sap.com/saphelp_nw04s/helpdata/en/22/b4d13b633f7748b4d34f3191529946/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/22/b4d13b633f7748b4d34f3191529946/content.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/3867a582-0401-0010-6cbf-9644e49f1a10
Also you can look at this scenario --> File to JDBC:-
/people/sap.user72/blog/2005/06/01/file-to-jdbc-adapter-using-sap-xi-30
/people/yining.mao/blog/2006/09/13/tips-and-tutorial-for-sender-jdbc-adapter
/people/sameer.shadab/blog/2005/10/24/connecting-to-ms-access-using-receiver-jdbc-adapter-without-dsn
/people/saravanakumar.kuppusamy2/blog/2005/01/19/rdbms-system-integration-using-xi-30-jdbc-senderreceiver-adapter
SENDER RFC
Registered server program name which is maintained in the ABAP should be called in the program ID.
for more information follow this links
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
/people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009
How to test the RFC to Flat File scenario
Type 3 ABAP Connection :
ex 1) If we want to execute any function module from one SAP system in another , we need type 3.
We define an RFC destination say ECC6CLNT100 with required parameters.
and to test it go to SE37, select any common sap function module and when you execute that it will ask
for RFC destination. you provide this destination and the function module will be executed in the target
system.
ex2) when you create a partner profile, you need to create a port and for creating a port, we need to
specify an RFC destination. here also we use type 3.
Type H.
ex1) when we need to send xml messages from an SAP system to any other system, we need this.
For example when we send messages using proxy from SAP system to the integration engine of XI, we
need type H.
Type T.
ex1) To we make an RFC call from R/3 to XI , we use sender RFC adapter in XI.
In R/3 system we need to create an RFC destination of type T.
Different types of RFC are :-
Asynchronous RFC - aRFC
Synchronous RFC - sRFC
Transactional RFC - tRFC
Queue RFC - qRFC
Parallel RFC - pRFC
Chk this link also:
Link :http://help.sap.com/saphelp_nw04/helpdata/en/6f/1bd5b6a85b11d6b28500508b5d5211/content.htm
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1685 [original link is broken] [original link is broken] [original link is broken]
Please go through the following links.
/people/bhavesh.kantilal/blog/2006/07/03/jdbc-receiver-adapter--synchronous-select-150-step-by-step JDBC Receiver Adapter -- Synchronous Select Step by Step
/people/yining.mao/blog/2006/09/13/tips-and-tutorial-for-sender-jdbc-adapter Sender JDBC adapter
/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
FILE- RFC-FILE Synchronous (Using BPM)
/people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009 Trouble Shooting RFC and SOAP Scenario
Regards,
Vinod.

Decode Error in Cisco VCS for a call from Jabber to telyHD

Hi,
We have the following setup:
Cisco Jabber <---> Cisco VCS <---> telyHD (Our Video Product)
Now, the call works well when the call is intiated from telyHD to Cisco Jabber.
But, the call fails when the Cisco Jabber initiates the call towards telyHD.
The packet capture on VCS shows that there is a syslog message from VCS to Jabber indicating the following when 180 Ringing is received from telyHD:
Message [truncated]: tvcs: Event="Decode Error" Service="SIP" Src-ip="10.1.1.19" Src-port="5060" Dst-ip="10.1.11.11" Dst-port="25331" Detail="(User-Agent) Single header User-Agent appeared twice in message" Protocol="TCP" Level="1" UTCTime
Can you please help in troubleshooting this issue. I don't see multiple "User-Agent" headers in the 180 Ringing sent by telyHD.
I have attached the packet capture on VCS.

I am also having the same issue. Can someone please respond? Thanks.

Attaching Second Pool to Trusted Application for Cisco VCS

I have completed the Cisco VCS to Lync 2013 integration found here but needless to say, the guide
is very much lacking in clarity on the Lync end and doesn't take larger deployments into consideration; or I'm just missing something.
Most of the document thinks of Lync as a single pool entity but in my case, we have two pools on campus. My question is as follows:
Can I use DNS to trick the Lync topology builder into thinking there is an alternate device that can be assigned to a trusted application?

Integration and communication between Lync 2013 and Cisco Voice Communication Server, in conjunction with Cisco Tandberg room units.
I wasn't aware of the change taking place site wide and assumed that since the application lists and only accepts my Pool1 as a next hop that the static line between the two could only travel server to server (pool).
Video initiation works from Pool1 to Cisco and vice versa. Video integration between Pool2 and Cisco will only initialize if started by the Cisco endpoint dialing said Lync client. Presence information (provided by Jabber) works for users in
Lync Pool1 but not in Pool2.

Cisco VCS Starter Pack Express

Hi,
I would like to ask if "dual network interface" option key is needed for a Movi Client to register to VCS Starter Pack Express via public or internet?
Details:
VCS Starter Pack Express is installed as part of DMZ.
Able to ping and access VCS via public or internet.
Movi Client was able to register via internal network.
Movi Client was not able to register via public or internet. Same account used in internal network.
Regards,
Arvie

I disagree with your 100%.
The initial question was, can I run Movi with just the VCS Starter Pack Express with out an TMS.
Any yes, you can.
Yes, Movi requires provisioning to run. In general its:
* TMS + VCS + Licenses
In this model the License management for Movi is indeed handled by TMS
btw, you also need a "Device Provisioning Key" on the VCS, not only movi Licenses on the TMS
* VCS Starter Pack Express
Which gives you up to 50 registrations, limited findme and 5 (default) up to 25 (additional purchase) call licenses.
Here a info from the deployment guide: (found in the cisco vcs doc section)

Does Cisco 3845 with NM-16A/S support OIR feature or Hot swap for this NM.

Dear Sir
My customer would like to implement Cisco 3845 with NM-16A/S x 4. I found that Cisco 3845 support OIR function but I am not sure OIR function that Cisco 3845 support, it support with which NM models. Can anyone tell me that NM-16A/S on Cisco 3845 support OIR function on this NM or not.
Thank you very much
Wisit

Hi,
From what I have read from the following document.
http://www.cisco.com/en/US/products/ps5855/products_installation_guide_chapter09186a00802ccf1d.html
Network Modules
Network modules install directly into slots in the rear of the router. The Cisco 3845 router supports online insertion and removal (OIR, or hot swap) of network modules. The Cisco 3825 router does not support OIR.
Caution The Cisco 3845 router supports OIR with similar modules only. If you remove a network module, along with any installed WAN or voice interface cards, install another module and card combination exactly like it.
Interface Cards
Cisco 3800 series routers do not support OIR (hot swap) of interface cards inserted directly into router slots. You must turn off the router before installing or removing an interface card.
The Cisco 3825 router and the Cisco 3845 router each provide four interface card slots, labeled on the rear panel by HWIC and a number. Each slot can be occupied by one single-wide WIC, VIC, VWIC, or HWIC.
Hope this helps
Sarb

Does Cisco UCCE 8.5 Virtual Machine support VMXNET3 driver?

Does Cisco UCCE 8.5 Virtual Machine support VMXNET3 driver?
VMware ESXi 5.0

Saeed,
about " can you provide with link which highlight the current support VM for UCCE. " not sure if I understood you right, but if you wanted to know which are all the UCCE components can be virtualized on VM, then please refer " Contact Center Applications " section of http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Supported_Applications
Pls remember to rate helpful posts.
GP

Cisco VCS Microsoft Office 365 interop

As I understand this in order to connect Cisco Telepresence endpoints to the MS Lync client a VCS gateway is required.
This is supported for the on premises version of MS Lync. However I cannot find anything that details support or a road map
of the support of MS Lync within MS Office 365.
Does anyone have a road map or information on when support for Lync MS Office 365 may be forthcoming?
Thanks
Mark

Ah, but is SIP a "standard"? There are multiple RFCs outlining the protocol, but it isn't a standard per se, not in the way that H.323 is a "standard".
Yes, I'm splitting hairs, however, I agree with you and when companies bastardise SIP for their own nefarious purposes, they should at the very minimum provide an open interoperable gateway so that they can communicate will "normal" SIP based product that do comply to the RFCs. An example of a way that it could be done is through the StarLeaf (ex Codian) products. They use their own propitiatory SIP stack, yet their backend allows for full interoperability with H.323 , 'normal' SIP, and Lync - I must admit that I do like what they offer. The only ironic thing is that they don't negotiate AAC audio when hooked up to the Codian MCUs due to there product not being "white-listed"!. As Cisco now own Codian, we did forward a request to Cisco to add the StartLeaf product to the whitelist for these MCUs - we will have to see what happens....
Nevertheless, the last I read about this was that MS were looking to bring such a development to Lync, probably in 2015. I can't remember where I read it, but I think it may have come out of the last Lync Conference. My guess is that it will be rolled into a part of the next evolution of the product such as Lync 2015/16?

SPA-50x RFC 4235 support

As I have not been able to find any way to submit a support case to Cisco regarding these phones, and in hopes that someone from Cisco may see this, I'd like to request full support for RFC 4235 in the SPA-50x series phones. This is so that in SIP proxy environments the SPA phones can provide their own presence information to the server. The server would SUBSCRIBE to the phone, and the phone would send NOTIFYs of type application/dialog-info+xml whenever there is a state change (ringing, on the phone, etc.). The acceptable Expires time received in a SUBSCRIBE should also be allowed to be VERY short (1 second) so that if the proxy needs to only see what calls are ringing on the phone in order to intercept them, it won't have to make a persistent subscription to the phone.
I have attached a packet capture showing how Polycom sends NOTIFYs on state change in accordance with RFC 4235. If anyone knows how to get this information to the Cisco SPA team for review I would greatly appreciate letting them see this.
If you have any questions post here and I will attempt to answer them.

As I have not been able to find any way to submit a support case to Cisco regarding these phones, and in hopes that someone from Cisco may see this, I'd like to request full support for RFC 4235 in the SPA-50x series phones. This is so that in SIP proxy environments the SPA phones can provide their own presence information to the server. The server would SUBSCRIBE to the phone, and the phone would send NOTIFYs of type application/dialog-info+xml whenever there is a state change (ringing, on the phone, etc.). The acceptable Expires time received in a SUBSCRIBE should also be allowed to be VERY short (1 second) so that if the proxy needs to only see what calls are ringing on the phone in order to intercept them, it won't have to make a persistent subscription to the phone.
I have attached a packet capture showing how Polycom sends NOTIFYs on state change in accordance with RFC 4235. If anyone knows how to get this information to the Cisco SPA team for review I would greatly appreciate letting them see this.
If you have any questions post here and I will attempt to answer them.

Cisco VCS

Hi,
I am new on the Cisco Telepresence and we will be getting Cisco Telepresence VCS to installed on our Campus and what to know:
1. Is this appliance support any dynamic routing "ospf, ..."
2. How many ethernet port this appliance has ? I would like to connect one port to FW and one port to Server Farm switch, is this OK as design ?
3. How about QoS, Is autoQoS enough to do in the access layer switches or need more ?
4. Any design recommendation or tips will be appreciated.
Thanks

Looking at the basics of that error message - there's been a timeout when trying to establish a TLS connection. Are you able to check your firewalls to see whether you've got all the required ports open?
You don't mention which VCS software version you're using, but you can find the firewall traversal guides for all the different versions at: http://www.cisco.com/c/en/us/support/unified-communications/telepresence-video-communication-server-vcs/products-installation-and-configuration-guides-list.html
Note: Your question would be better placed in the TelePresence section of the forums where these devices are more actively discussed than in the Video Over IP section you've posted in - I'd suggest, if the above hasn't answered your query, that you move your discussion over there.
Wayne
Please remember to rate responses and to mark your question as answered if appropriate.

CISCO VCS exresspress

Hi Team,
From India we are trying to reach our client who is in US.In Video conference tangberg device.we unable to reach from here.
Please find the logs and provide me solution.
2015-01-26T10:32:53-05:00
tvcs: Event="Outbound TLS Negotiation Error" Service="SIP" Src-ip="159.108.120.5" Src-port="25585" Dst-ip="159.108.1.120" Dst-port="7001" Detail="Timeout" Protocol="TLS" Level="1" UTCTime="2015-01-26 15:32:53,365"
I can able to ping and tracert from the client pc I'm unable to reach the web access of the gateway in client side.(159.108.1.120 - VCS expressway)
Let me know wht will the issue

Looking at the basics of that error message - there's been a timeout when trying to establish a TLS connection. Are you able to check your firewalls to see whether you've got all the required ports open?
You don't mention which VCS software version you're using, but you can find the firewall traversal guides for all the different versions at: http://www.cisco.com/c/en/us/support/unified-communications/telepresence-video-communication-server-vcs/products-installation-and-configuration-guides-list.html
Note: Your question would be better placed in the TelePresence section of the forums where these devices are more actively discussed than in the Video Over IP section you've posted in - I'd suggest, if the above hasn't answered your query, that you move your discussion over there.
Wayne
Please remember to rate responses and to mark your question as answered if appropriate.

Cisco VCS/Codian MCU and Lync 2013 integration

Hi,
I would like to know if Lync 2013 is supported to work with:
- Cisco Tandberg VCS version x6.1
- Cisco Codian 4.1 (comp. 6.16)
Is it necessary to update both devices to be supported/homologated/qualified?
Thanks

Hi, Kent ... From what I'm seeing so far the challenges of integrating Cisco/Tandberg equipment and Lync 2013 are the same as what you may have already encountered with Lync 2010. Since the Cisco endpoints and MCU cannot register directly to Lync 2010
or 2013, you will need to leverage the VCS systems as your SIP gateway between them and Lync clients. In Lync 2010 there were limitations as to the interoperability of the H.263/264 codec used by Cisco gear and the RTV codec that Lync was restricted
to, and we often experienced frozen video feeds from Lync clients or an inability to connect to individual Cisco endpoints or conferences hosted by the Codian MCU. Even though Lync 2013 will use H.264 as a codec for the video stream, I anticipate there
will still be challenges interconnecting through the VCS as well as providing content between Lync and Cisco endpoints. However, I expect an increase in the video quality since Lync 2013 supports higher resolutions and also uses a non-proprietary codec.
I expect content to still be unreliable for the Lync participant, even when using a Codian MCU.
You will still need to setup your VCS with a separate Neighbor zone for the Lync 2013 server just as you did for Lync 2010. I wouldn't hold my breath for Cisco to update the VCS software to accomodate the specific needs of Lync 2013, but at least the
VCS will get the correct video codec and connect your call. I don't know about you but I had to put my Cisco units and MCU into a separate SIP domain from the Lync pool, and then create a static route for the Cisco SIP domain on the Lync 2010 front-end
server. I expect to do the same in Lync 2013.
Ideally, Microsoft and Cisco would agree that SIP is SIP, and whether an endpoint registers with VCS, UCM or Lync shouldn't be relevant. Alas, it'll be a long, long time before that is true, certainly not as long as Microsoft and Polycom have
such a tight bond. I plan on implementing Lync 2013 in the next few months and will gladly post any progress here. At this point my plan is to simply mirror the static route and configuration I have with Lync 2010. My VCS and Codian units
are running software versions just a little ahead of yours and work fine.
Good luck!

Enhancement Request for RFC 4021 Support in Mail

I'm not sure if this is appropriate for this forum, or complies with the click-through agreement which neither I nor the vast majority of anyone here probably read, but here it goes.
Mail does not appear to support RFC 4021. In particular, there are several header fields that are used by various applications that Mail cannot create in messages, and provides no means for adding in. Of interest to me is the Sensitivity header, which flags the message as having a particular sensitivity. This is used by at least one product (Cisco IronPort) through which mail flows in corporate networks with the device. If it sees this header it will automatically save the message off and send a new email with a URL that the original recipients can use to retrieve the secured message. Now, all of this is done outside of Mail and is a feature of the IronPort product. All that Mail, or any email application needs to do, is to include the appropriate header field.
I created a support case, but there is no such feature for setting the sensitivity of an email. If it is appropriate for me to do so, I would encourage you to head over to http://www.apple.com/feedback and send feedback asking for support of RFC 4021, either through an explicit GUI interface to set the sensitivity of email or through the ability to include arbitrary headers and values so that future header fields can be added without Apple having to update the application constantly. If it's not appropriate for me to do so, then I would not encourage you to head over to http://www.apple.com/feedback and provide such feedback
I'd also be interested if anyone knows how Mail processes email, and in particular sending email. My particular example unfortunately includes an exchange server (2007), so I'm guessing that it is not processed by postfix or any other application, and is sent directly from Mail to Exchange. If it were, I supposed it may be possible to include an entry in /etc/postfix/header_checks to look for a header that CAN be included via Mail, such as a BCC to a specific fictitious address, and REPLACE it with the appropriate header field. If anyone is aware of how Mail actually processes email outbound to an Exchange server I'd be interested in those details.
Thanks,
Fred Reimer

I'm not sure if this is appropriate for this forum,
Mail does not appear to support RFC 4021
To request an enhancement, try: http://www.apple.com/feedback/macosx.html

RFC SDK support on solaris-intel?

I have some questions about the C SAP RFC SDK. I cannot seem to find a complete list of supported UNIX platforms.
What is the current version of the C RFC SDK?
Is it supported on the solaris intel platform?
I notice that the dynamic version of the RFC library (rfc32.dll) is installed with SAP Netweaver on Windows. Is the equivalent dynamically loaded library (i.e. librfc.so) always included with a SAP installation on UNIX as well? Does this mean that the static libraries provided in the RFC SDK are no longer required to build a client RFC application, since a client application can dynamically load the run-time library instead?

We don't certify Solaris on NT.
          You can find this information on platform support page.
          -- Prasad
          Puneet Maini wrote:
          > Hi
          > Is Clustering comfiguration supported for this System Requirement?
          > :
          >
          > Processor: Intel
          > Operating system: Solaris 8
          >
          > Thanks & Regards
          > Puneet Maini

Cisco prime 2.1 / 2.2 support for Cisco ise 1.3 ?

Hi, I just tried to connect cisco PI 2.1 to cisco ISE 1.3, but fails.
I read the release Notes, only ISE 1.2 ist supported.
But I was wondering that the ssl handshake fails (I have done a packet capture).
So PI 2.1 has not tried to connect to ise 1.3 via api, because of the connection fails at the ssl handshake stage.
Anyway, does anybody know if ISE 1.3 will be supported with PI 2.2 or a version of PI 2.1.x ?

Why doesn't the REST API communication in Prime 2.1 (2.1.0.0.87) support TLS? The platform itself seem to be able to handle TLS-DHE-RSA with AES-128-CBC-SHA. Why is it trying to use SSLv2 ?
These protocol is incompatible and very much outdated: http://en.wikipedia.org/wiki/Transport_Layer_Security#SSL_1.0.2C_2.0_and_3.0
Can this behavour be reconfigured in CLI or at least be allowed in ISE 1.3 to make a workaround until a working patch or upgrade is done? Could or should adding the Cisco Prime server as managed node in ISE circumvent the incompability?

Cisco VCS X7.1 RFC 4480 support (Rich Presence)

Similar Messages

Maybe you are looking for