Cisco Call Connector Server Confusion

Hi all, we have a customer who is interested in the Cisco Call Connector Server.
In terms of ordering do I need 1 X SW-UCC-SERVER and then however many client licenses SW-UCC-CLIENT-1? Or are the Client licenses SW-UCC-CME?
Also does anyone know if the Call Connector Client will work over terminal services?
Also can Cisco provide copies for demo purposes?
Any info greatly appreciated.

Hi Nathan, from my understanding CallRex registers the TAPI under the ephone, correct?  The Cisco Call Connector also does the same thing. In the past I've had issues trying to setup the UC system to dial out from a CRM along with having the Cisco Call Connector. In this experience I had an issue as the Call Connector server would register and hold onto the TAPI for that ephone and it broke the dial out function of the CRM.  So you are saying to setup a dual endpoint on the Cisco device, one being hard phone and one being a softphone, registering 1 TAPI to CallRex and the other TAPI to Call Connector? 
If that's the case though, the softphone would need to be on at all times in order for it to register the TAPI, correct?  Am I understanding this or missing something?

Similar Messages

  • German Dial Plan Smart Cisco Call Connector Server

    Hi everyboddy,
    has someone the Dialplan Config for the UCC ?
    In the rar Documents in this Forum the Links for the examples are down.
    https://supportforums.cisco.com/docs/DOC-11019
    Philipp

    jeliasoncisco wrote:Hello. I have a growing practice selling UC500 and would like to know this too. Cisco, please keep selling and developing this. Thanks a million!
    Check forums here or talk to your Channel Account Manager.
    Cisco doesn't care for the UC500 anymore and will not continue selling it for much longer.

  • CallRex and Cisco Call Connector software

    I'm quoting a UC560 solution for a client that needs call recording along with Call Connector.  I am interested in CallRex but it appears it is based on TAPI and therefore, unlikely to get it setup in the same environment as Call Connector. Am I correct in assuming I can't get both for the same phones?  Anyone have experience with this or any recommendations or workarounds?  I'm also looking at TIM Talk, but I may only need to do a few phones and CallRex appears attractive for recording only a few select phones based on their user cost.   
    thanks,
    Steve

    Hi Nathan, from my understanding CallRex registers the TAPI under the ephone, correct?  The Cisco Call Connector also does the same thing. In the past I've had issues trying to setup the UC system to dial out from a CRM along with having the Cisco Call Connector. In this experience I had an issue as the Call Connector server would register and hold onto the TAPI for that ephone and it broke the dial out function of the CRM.  So you are saying to setup a dual endpoint on the Cisco device, one being hard phone and one being a softphone, registering 1 TAPI to CallRex and the other TAPI to Call Connector? 
    If that's the case though, the softphone would need to be on at all times in order for it to register the TAPI, correct?  Am I understanding this or missing something?

  • Windows 8 and Cisco Call Connector

    Hi,
    Does Cisco Call Connector work on Windows 8?
    We have a customer running Windows 8 and they have encountered the following error when they tried to install it.
    Thanks
    Raymond

    try using PPTP vpn. it will work without Cisco vpn client. below is config example.
    http://www.cisco.com/en/US/tech/tk827/tk369/technologies_configuration_example09186a00801e51e2.shtml
    hope this helps.

  • Smart Call Connector Advanced

    Hi, im just wondering when we can expect an update to Smart Call Connector Server and Advanced Clients?
    This software is in need of some serious bug fixes...and feature enhancements!

    Indeed, but roadmap questions and questions related to when a new product release will be published are matters that cannot be discussed in a public forum. That's why you need to reach your AM, also to submit a PER you need to do so via AM.
    HTH
    java
    if this helps, please rate
    www.cisco.com/go/pdihelpdesk

  • Call connector error!!!

    I recently configure call connector server and client solution , everything works except for one issue, when I try to chat with an external user I got the following error :
    "No external IM account setup. Unable to send IM"
    I'm trying to send it to a facebook or gmail user the account is setup by default.
    Any Ideas ?
    Regards

    SOrry I dont have an answer for you but do you know if you can still purchase this software and does it support windows 8?

  • Cisco Smart Call Connector / Advanced Client / Server for UC500

    Would like to hear from Cisco:
    Is there still development in progress on Cisco Smart Call Connector, the advanced client, server and operator involving compatibility and support for Windows 8 / Outlook 2013 / and IE 10 32 and 64 bit ?
    Please vote this up if interested !

    jeliasoncisco wrote:Hello. I have a growing practice selling UC500 and would like to know this too. Cisco, please keep selling and developing this. Thanks a million!
    Check forums here or talk to your Channel Account Manager.
    Cisco doesn't care for the UC500 anymore and will not continue selling it for much longer.

  • RMI Connector Server not running in java 1.4

    I have an application using sun JDMK implementation which is running fine in java 1.3 As I go to java 1.4, the RMI connector server is not running, the state goes to OFFLINE. I don't see any exception except that the server doesn't stay alive. Any idea on the problem ?

    If you have the possibility of changing your application so that it uses the RMI connector defined by the JMX Remote API, then I would strongly encourage you to do so. You can get an implementation from http://java.sun.com/javase/technologies/core/mntr-mgmt/javamanagement/download.jsp (look for JMX Remote API Reference Implementation).
    If you don't have the option of doing this in the short term, then you could try turning on JDMK traces by calling com.sun.jdmk.TraceManager.parseTraceProperties() in the main method of your application, and specifying -DLEVEL_DEBUG on the command-line. You will probably see some logging information that will help you diagnose your problem.
    �amonn McManus -- JMX Spec Lead -- http://weblogs.java.net/blog/emcmanus

  • Cisco Call Manager 8.5 and Lync 2013

    Dear all,
    Our customer wants to integrate their Lync 2013 to the Cisco Call Manager 8.5.
    Out of some not so recent information i thought that if u want to use the enterprise voice of lync you'll have to make a sip trunk between Cisco Call Manager & Lync 2013.
    I think that this still counts, i've also heard that there have been a moderate amount of changes between cucm 8.5 and cucm 8.6 on matters of sip.
    I'm unable to find them though, also what does CUCI - Lync do?
    Kr,
    Yannick Vranckx

    Hi Yannick,
    There can be three types of integrations between Lync and Cisco Systems
    1)      Direct SIP Trunk between Lync Server and Call Manager - In this, we can setup shared line between Cisco extensions and Lync extensions, and Sip trunk between the servers. Any Cisco phone / Lync client  can call each other vice-versa. Initial setup needs planning, but later it does not need much configurations in client side. The following document explains the configurations needed.
    http://www.cisco.com/en/US/docs/voice_ip_comm/cucilync/9/CUCI_BK_C0B36AC1_00_cisco-uc-integration-for-microsoft.pdf
    2) CUCILYNC, which is like Cisco Jabber client but connects with Lync and Call Manager: Lync Client <----> CUCILYNC <-----> CUCM
    In this option, a plug-in is installed in each client side. Although initial configurations is easier, each user needs to install the client and operate it. The below document explains the configuration and setup.
    http://www.cisco.com/en/US/docs/voice_ip_comm/cucilync/9/CUCI_BK_C0545A41_00_cisco-uc-integration-for-microsoft.html
    3) RCC (Remote Call Plugin) which just provides basic call control feature but for that you need Cisco Unified Presence Server: Lync Client <----> CUPS <-----> CUCM
    HTH
    Manish

  • Cisco Call Manager TFTP requests.

    I was looking to see if there was a way to look at what devices request config files from a Cisco Call Manager TFTP server.
    I know that you can use RTMT to look at the total number of requests made, but is there a way to know what device make the request.
    Thanks in advance,
    Robert

    You could do this by doing a packet capture on the server as described in the link below
    https://supportforums.cisco.com/docs/DOC-11599

  • Cisco call manager Network Failover Configuration

    Hi all,
    I have a cisco call manager 6.0.
    The server is configured and is functioning very well.
    Only  today I realized that the server MCS has two NIC and there is the  possibility to configure a networ failover by cli interface.
    Now the question are:
    is it possible to configure this function now without problem?
    if yes what are the ordered steps to follow?
    Thanks all.

    Hi
    you can use EtherChannel, 2 phisical ports as 1 logical

  • Cisco call manager and ip phone software.

    Hi everybody.
    Does Cisco call manager also include software required for ip phone? Or software for ip phone needs to be installed on tftp server and it does not come with cisco call manager.?
    thanks and have a great weekend.

    Hi Sarah,
    by ip phone software, do you mean Cisco IP Phone Agent software?
    if  yes, then you need to have Customer Response Solution (CRS) and Call Manager together to setup ip phone software (services).
    check this link for further info:
    http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_configuration_example09186a00801c5765.shtml
    plz Rate if it helped.
    Soroush.

  • FreeRadius and Cisco 2600 Terminal Server [IOS 12.1(3)T]

    Hi Cisco People
    I'm using FreeRadius 2 and Cisco 2600 Terminal server to coordinate access to cisco routers based on time‏ ranges.
    Basically we are an education/training environment where we have some students accessing the routers and switches for practise, terminal server are used to consolidate the console access, and these terminal servers authenticate the users through a Radius server (as shown in the following figure). Additionally, the students are categorized into few groups. We want to implement policy on the radius server so that only a certain group can access the resources in a given duration of time (the user should be dropped from the terminal when the subscribed time is reached and cannot access thereafter .) 
    +++++++++++++++                                           +++++++++++++++++                                      +++++++++++++
    +         User          +++++++++++++++++++++++   Cisco 2600          +++++++++++++++++++++   Network      +
    +                          +                                           +   Terminal Serv     +                                      +    Devices      +
    +++++++++++++++                                           +++++++++++++++++                                      +++++++++++++
                                                                                            (NAS)
                                                                                                +
                                                                                                +
                                                                                   +++++++++++++++     
                                                                                  +   FreeRadius      +
                                                                                  +++++++++++++++
    Right now I'm able to do the "hello-world" setup with the following users and clients.conf. On the terminal server side, aaa new-model is enabled on the cisco terminal server to communicate with this radius server.
    users
    =============
    cisco Auth-Type := System
      Service-Type = NAS-Prompt-User,
      cisco-avpair = "shell:priv-lvl=15"
    clients.conf
    ==============
    client 192.168.1.1 {
      secret = SECRET_KEY
      shortname = termserver
      nastype = cisco
    A typical transaction would be :
    Access-Request
    =======
            NAS-IP-Address = 192.168.1.1
            NAS-Port = 35
            NAS-Port-Type = Async
            User-Name = "cisco"
            Calling-Station-Id = "1.1.1.1"
            User-Password = "cisco"
    Access-Accept
    =======
            Service-Type = NAS-Prompt-User
            Cisco-AVPair = "shell:priv-lvl=15"
    This works fine but doesn't provide any timing limitations. So I have modified the FreeRadius config to be :
    users
    =============
    cisco Auth-Type := System
      Service-Type = NAS-Prompt-User,
      cisco-avpair = "shell:priv-lvl=15",
      Session-Timeout = 20
    Cisco Terminal Server
    ==============
    aaa new-model
    aaa authentication login default group radius local none
    aaa authorization exec default group radius if-authenticated 
    aaa accounting exec default start-stop group radius
    aaa accounting network default start-stop group radius
    aaa accounting connection default start-stop group radius
    After this, I am able to see that the terminal server actually receives an Access-Accept including the Session-Timeout attributes like the following :
            Service-Type = NAS-Prompt-User
            Cisco-AVPair = "shell:priv-lvl=15"
            Session-Timeout = 20
    But the problem is that it doesn't really terminate the session after the 20 seconds are reached . My questions is that :
    1. Is the terminal server really able to enforce such time limit after receiving the attribute ?
    2. Is the 2600 terminal server  with [IOS 12.1(3)T] compliant with RFC 2865?
    3. What can I do so that the terminal server forces the user to be logged out after the session time limit is reached ?
    Thanks
    Frank

    Frank,
    I think you should use the login time s well:
    Login-Time
    Login-Time is a very powerful internal check AVP. It allows flexible authorization and its value is used by the logintime (rlm_logintime) module to determine if a person is allowed to authenticate to the FreeRADIUS server or not. This value is also used to calculate the Session-Timeout reply value. Session-Timeout is subsequently used by the NAS to limit access time.
    The following line will grant Alice access only between 08:00 and 18:00 each day.
    "alice" Cleartext-Password := "passme", Login-Time := 'Al0800-1800'
    The logintime module will calculate the reply value of Session-Timeout if Alice has logged in within the permitted timeslots to inform the NAS how long she is allowed to stay connected. If Alice tries to access the network when she is not permitted, the request will be rejected.
    http://www.packtpub.com/article/getting-started-with-freeradius
    http://wiki.freeradius.org/config/Users
    yes, the terminal server is RFC 2865 compliant.
    Rate if Useful :)
    Sharing knowledge makes you Immortal.
    Regards,
    Ed

  • Cisco Call Manager Upgrade from Ver 5.1.3 to Ver 8.6

    Hi ,
    My organization have 4 Subscribers and 1 publisher between 4 different sites. version of all call manager are 5.1.3. all are running on HP Proliant server.
    I looking to upgrade to Version 8.6. Do I need to upgrade server hardware as well for upgrading latest version of call manager or I can use my old server ?
    Thanks
    Amit Sharma

    Hi GP,
    Thanks for your reply.
    Please find below the hardware details of my old server. these details I get from Cisco call manager application.
    Hardware Resources
    Hardware platform type    7835H
    The CPU type    Intel(R) Xeon(TM) CPU 3.40GHz
    Memory    2048 Mbytes
    Detailed Report
    Machine_Type = XXXX
    Model_Number =
    Serial_Number = GB8637LRFE     
    Product_Name = ProLiant DL380 G4
    BIOS_Version =
    BIOS_Build_Level = P51
    BIOS_Date = 04/26/2006
    BIOS_Manufacturer = HP
    BIOS_Language =
    Number_Of_Enclosures =
    Enclosure_Type.0 =
    Processor_Slots = 2
    Active_Processors = 1
    Processor_Family.0 = Xeon
    Processor_Speed_MHz.0 = 3400
    Total_Enabled_Memory_Mb = 2048
    ROM_Diagnostics_Build_Level =
    Thanks
    Amit

  • Connectivity Issue between ASA 5520 firewall and Cisco Call Manager

    Recently i have installed ASA 5520 firewall, Below is the detail for my network
    ASA 5520 inside ip: 10.12.10.2/24
    Cisco Switch 3560 IP: 10.12.10.1/24 for Data and 10.12.110.2/24 for Voice
    Cisco Call Manager 3825 IP: 10.12.110.2/24
    The users and the IP phone are getting IP from the DHCP server which configured on cisco 3560 Switch.
    the Default Gateway for Data user is 10.12.10.2/24 and
    for the voice users is 10.12.110.2/24
    now the problem is that the users is not able to ping 10.12.110.2 call manager. please if somebody can help in this regard. i will appreciate the prompt response against this issues.

    Actually i don't wana to insert new subnet and complicate the nework. i need a simple way to solve the problem. below is the details for the asa 5520 config.
    ASA Version 8.2(1)
    name x.x.x.x Mobily
    interface GigabitEthernet0/0
     nameif inside
     security-level 99
     ip address 10.12.10.2 255.255.255.0
    interface GigabitEthernet0/1
     nameif outside
     security-level 0
     ip address x.x.x.x 255.255.255.252
    object-group service DM_INLINE_SERVICE_1
     service-object tcp-udp
     service-object ip
     service-object icmp
     service-object udp
     service-object tcp eq ftp
     service-object tcp eq www
     service-object tcp eq https
     service-object tcp eq ssh
     service-object tcp eq telnet
    access-list RA_VPN_splitTunnelAcl_1 standard permit Inside-Network 255.255.255.0
    access-list RA_VPN_splitTunnelAcl standard permit Inside-Network 255.255.255.0
    access-list inside_nat0_outbound extended permit ip Inside-Network 255.255.255.0 10.12.10.16 255.255.255.240
    access-list inside_nat0_outbound extended permit object-group DM_INLINE_SERVICE_1 10.12.10.16 255.255.255.240 Inside-Network 255.255.255.0
    access-list inside_nat0_outbound_1 extended permit ip Inside-Network 255.255.255.0 10.12.10.16 255.255.255.240
    pager lines 24
    logging enable
    logging asdm informational
    mtu inside 1500
    mtu outside 1500
    mtu mgmt 1500
    ip local pool VPN-Pool 172.16.1.1-172.16.1.30 mask 255.255.255.0
    ip local pool VPN-Users 10.12.10.21-10.12.10.30 mask 255.255.255.0
    no failover
    icmp unreachable rate-limit 1 burst-size 1
    asdm image disk0:/asdm-641.bin
    asdm history enable
    arp timeout 14400
    global (inside) 2 interface
    global (outside) 1 interface
    nat (inside) 0 access-list inside_nat0_outbound_1
    nat (inside) 1 Inside-Network 255.255.255.0
    route outside 0.0.0.0 0.0.0.0 Mobily 1
    timeout xlate 3:00:00
    timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
    timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00
    timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00
    timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute
    timeout tcp-proxy-reassembly 0:01:00
    dynamic-access-policy-record DfltAccessPolicy
    http server enable
    http Mgmt-Network 255.255.255.0 mgmt
    http Inside-Network 255.255.255.0 inside
    no snmp-server location
    no snmp-server contact
    snmp-server enable traps snmp authentication linkup linkdown coldstart
    crypto ipsec transform-set ESP-AES-256-MD5 esp-aes-256 esp-md5-hmac
    crypto ipsec transform-set ESP-DES-SHA esp-des esp-sha-hmac
    crypto ipsec transform-set ESP-DES-MD5 esp-des esp-md5-hmac
    crypto ipsec transform-set ESP-AES-192-MD5 esp-aes-192 esp-md5-hmac
    crypto ipsec transform-set ESP-3DES-MD5 esp-3des esp-md5-hmac
    crypto ipsec transform-set ESP-AES-256-SHA esp-aes-256 esp-sha-hmac
    crypto ipsec transform-set ESP-AES-128-SHA esp-aes esp-sha-hmac
    crypto ipsec transform-set ESP-AES-192-SHA esp-aes-192 esp-sha-hmac
    crypto ipsec transform-set ESP-AES-128-MD5 esp-aes esp-md5-hmac
    crypto ipsec transform-set ESP-3DES-SHA esp-3des esp-sha-hmac
    crypto ipsec security-association lifetime seconds 28800
    crypto ipsec security-association lifetime kilobytes 4608000
    crypto dynamic-map SYSTEM_DEFAULT_CRYPTO_MAP 65535 set pfs
    crypto dynamic-map SYSTEM_DEFAULT_CRYPTO_MAP 65535 set transform-set ESP-AES-128-SHA ESP-AES-128-MD5 ESP-AES-192-SHA ESP-AES-192-MD5 ESP-AES-256-SHA ESP-AES-256-MD5 ESP-3DES-SHA ESP-3DES-MD5 ESP-DES-SHA ESP-DES-MD5
    crypto map outside_map 65535 ipsec-isakmp dynamic SYSTEM_DEFAULT_CRYPTO_MAP
    crypto map outside_map interface outside
    crypto isakmp enable outside
    crypto isakmp policy 10
     authentication pre-share
     encryption 3des
     hash sha
     group 2
     lifetime 86400
    crypto isakmp policy 30
     authentication pre-share
     encryption 3des
     hash md5
     group 2
     lifetime 86400
    telnet Inside-Network 255.255.255.0 inside
    telnet timeout 5
    ssh Inside-Network 255.255.255.255 inside
    <--- More --->              ssh timeout 5
    console timeout 0
    threat-detection basic-threat
    threat-detection statistics access-list
    no threat-detection statistics tcp-intercept
    webvpn
    group-policy RA_VPN internal
    group-policy RA_VPN attributes
     dns-server value 86.51.34.17 8.8.8.8
     vpn-tunnel-protocol IPSec
     split-tunnel-policy tunnelspecified
     split-tunnel-network-list value RA_VPN_splitTunnelAcl
    username admin password LPtK/u1LnvHTA2vO encrypted privilege 15
    tunnel-group RA_VPN type remote-access
    tunnel-group RA_VPN general-attributes
     address-pool VPN-Users
     default-group-policy RA_VPN
    tunnel-group RA_VPN ipsec-attributes
     pre-shared-key *
    class-map inspection_default
     match default-inspection-traffic
    policy-map type inspect dns preset_dns_map
     parameters
      message-length maximum 512
    policy-map global_policy
     class inspection_default
      inspect dns preset_dns_map
      inspect ftp
      inspect h323 h225
      inspect h323 ras
      inspect netbios
      inspect rsh
      inspect rtsp
      inspect skinny 
      inspect esmtp
      inspect sqlnet
      inspect sunrpc
      inspect tftp
      inspect sip 
      inspect xdmcp
    service-policy global_policy global
    prompt hostname context
    Cryptochecksum:e5a64fa92ae465cd7dabd01ce605307d
    : end

Maybe you are looking for