Cisco MXP 3000/6000 & VCS

Hello all,
We are in stage of deploying MXP 3000/6000.
MXP 3000/6000 are registered with VCS Server as H.323 Devices.
I am not able to find how to assign extension or DN to MXP 3000/6000.
Will H.323 ID be use as DN ?
Regards,

I think you might be looking for the E.164 field - that's where you'd put in the directory number / extension.

Similar Messages

CUCM 7.1 sip to Tandberg MXP 3000

Hi All,
Does anybody have any pointers on getting a CUCM 7.1 cluster talking to a Tandberg MXP 3000 via SIP.
We have separate ISDN Bri for our Tandberg and want to get rid of them and pass voice only calls via call manager and a 2821 gateway router with 2 PRI's.
Any pointers would be real helpful.

yes you can
just setup a SIP trunk or H323 ICT trunk with the CUCM
and make sure you have the right setup in VCS and CUCM interns of SIP uri, or H323 ID
and in CUCM make sure you setup the right, regions/codec, locations, and CSS
also by using search rules and transformations in VCS you can control which call to send to CUCM ( for example on PSTN calls )
you can test it before you remove the existing PSTN lines ( recommended )
good luck

Can't Ciscoworks LMS 4.2.2 back up the configuration of Cisco VPN 3000 concerntrator?

Hi All,
In VPN 3000 concerntrator, I've enabled tftp, telnet, snmp. I've also successfully added the concerntrator into Ciscoworks LMS 4.2.2. All the ports are verified open to Ciscoworks. No question mark shows next to this device in the device management of LMS. However, when I run configuration Achive Job, I always get the following failed message. Can anybody tell me how to to back up the configuration of Cisco VPN 3000 concerntrator in Ciscoworks LMS 4.2.2? Thanks in advance.

Sorry, but apparently not. Please see the supported devices table (here).
That table states, among other things:
The following features are not supported:
Network Topology Layer 2 Services
Fault Management
Configuration Deploy Protocols: HTTPS, TELNET, SSH, SCP, TFTP, RCP
Configuration Fetch Protocols: HTTPS, TELNET, SSH, SCP, TFTP, RCP

Cisco IE-3000-8TC switches and CNA

A colleague of mine has installed a set of 3 Cisco IE-3000-8TC switches which look like they have had a minimal amount of configuration applied to them, and I have now been asked to integrate them into a CNA community.
I can;
ping them and get replies
connect to them through telnet
connect to them with a web browser
I can create a community and the 3 switches are detected as shown in the attached file, CreateCommunity.png
However, when I try to connect to the newly created community CNA returns the error –1, as shown in the attached file, CommunityError.png
It then hangs at 83% Processing discovered devices…
Has anyone out there had experience of integrating these switches into CNA?
What do I need to do to them?

A colleague of mine has installed a set of 3 Cisco IE-3000-8TC switches which look like they have had a minimal amount of configuration applied to them, and I have now been asked to integrate them into a CNA community.
I can;
ping them and get replies
connect to them through telnet
connect to them with a web browser
I can create a community and the 3 switches are detected as shown in the attached file, CreateCommunity.png
However, when I try to connect to the newly created community CNA returns the error –1, as shown in the attached file, CommunityError.png
It then hangs at 83% Processing discovered devices…
Has anyone out there had experience of integrating these switches into CNA?
What do I need to do to them?

Maximum number of local users on a Cisco VPN 3000 Concentrator

Hi,
Do you know if there is a specific maximum number of local users that can be created on a Cisco VPN 3000 Concentrator? If possible, we would like to know the number for the different models.
Thanks in advance for your help!
Harry

Hi Harry,
Please see table 13-1 for that information, and read Authentication Server Limits paragraph
http://www.cisco.com/en/US/docs/security/vpn3000/vpn3000_47/configuration/guide/Usermgt.html#wp1685274
Pls rate any helpful posts
Bst Rgds
Jorge

Cisco IE-3000 8TC doesn't recogze 4SM fiber sfp module

Have a few Cisco IE-3000 8TC switches with the 4SM FIber SFP expansion modules. The switches do not discover these ports at all. I'm assuming that thhere is a fix or firmware upgrade, would appreciate any help.

Isgabrillo, Please see below.
I wasn't able to see a PID for the SFP's, but they are Cisco GLC-FE-100LX
THe switch doesn't seem to recognize the 4SM module that is currently attached. As I stated, I have a few already installed in the field that I am not able to contact right now, but have the same issue. I think I read in a blog somewhere that someone had the same issue and there was an IOS update that cured it.
Switch#sh inv
NAME: "1", DESCR: "IE-3000-8TC"
PID: IE-3000-8TC       , VID: V03 , SN: FOC1826Y36B
NAME: "IE-3000-8TC - Module in slot 1", DESCR: "IE-3000-8TC - Module in slot 1"
PID: IE-3000-8TC       , VID: V03 , SN: FOC1826Y36B
Switch#dir flash
%Error opening flash:/flash (No such file or directory)
Switch#sh version
Cisco IOS Software, IES Software (IES-LANBASEK9-M), Version 12.2(58)SE2, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2011 by Cisco Systems, Inc.
Compiled Thu 21-Jul-11 00:59 by prod_rel_team
ROM: Bootstrap program is Xmen2 boot loader
BOOTLDR: IES Boot Loader (IES-HBOOT-M) Version 12.2(44r)EX5, RELEASE SOFTWARE (fc1)
Switch uptime is 4 minutes
System returned to ROM by power-on
System image file is "flash:/ies-lanbasek9-mz.122-58.SE2/ies-lanbasek9-mz.122-58.SE2.bin"
This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.
A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
If you require further assistance please contact us by sending email to
[email protected].
cisco IE-3000-8TC (PowerPC405) processor (revision S0) with 131072K bytes of memory.
Processor board ID FOC1826Y36B
Last reset from power-on
1 Virtual Ethernet interface
8 FastEthernet interfaces
2 Gigabit Ethernet interfaces
The password-recovery mechanism is enabled.
64K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address       : 50:67:AE:72:AE:00
Motherboard assembly number     : 73-15595-01
Motherboard serial number       : FOC18258RWT
Model revision number           : S0
Motherboard revision number     : A0
Model number                    : IE-3000-8TC
System serial number            : FOC1826Y36B
Top Assembly Part Number        : 800-28538-03
Top Assembly Revision Number    : A0
Version ID                      : V03
CLEI Code Number                : CMMFE00ARB
Hardware Board Revision Number : 0x02
CIP Serial Number               : 0x8E72AE00
SKU Brand Name                  : Cisco
Switch Ports Model              SW Version            SW Image
*    1 10    IE-3000-8TC        12.2(58)SE2           IES-LANBASEK9-M
Configuration register is 0xF
Switch#exit
Switch#dir flash:
Directory of flash:/
736 -rwx        3096   Mar 1 1993 00:00:55 +00:00 multiple-fs
    2 drwx        1024   Mar 1 1993 00:06:38 +00:00 ies-lanbasek9-mz.122-58.SE2
732 -rwx         676   Mar 1 1993 00:07:33 +00:00 vlan.dat
733 -rwx        1915   Mar 1 1993 00:00:58 +00:00 private-config.text
735 -rwx        1424   Mar 1 1993 00:00:58 +00:00 config.text
64094208 bytes total (45407744 bytes free)
Switch#exit

QoS for Cisco TelePresence 3000

What are the QoS requirments for the Cisco TelePresence 3000 connected to a Cisco 6500 running CAToS?
Thanks in Advance.

This doc should help you:
http://www.cisco.com/en/US/products/hw/switches/ps708/products_configuration_guide_chapter09186a00800c65c9.html

Cisco 4000 & 3000 series ip route & ip default gateway

Dear all ;
I have Enterprise Network Contain :
- Foundry Big Iron work on layer 3 , and Combination of 4000 and 3000 and 2000 cisco switches work on layer 2;
management network for the switches is 192.168.100.0
Foundry Big Iron is 192.168.100.1
i use ip default-gateway 192.168.100.1 on all cisco switches.
all other subnets route through the foundry.
but when i ping from any subnet (192.168.15.0) to any 3000 or 2000 switches series it replay and when i ping to 4000 series it don't replay.
when i use default route command on 4000 series it replay.
i need some explanation
Kind Regards

In the original post it describes the Cisco switches as operating as layer 2 switches and I assume that in terms of how they are configured to forward traffic all the Cisco switches including the 4000 are configured only for layer 2 forwarding. But with IP routing enabled (as seems to have been the case on the 4000) the behavior of the switch becomes a bit different. In particular is the difference in how you identify the default route. For a switch that is layer 2 only you use the default-gateway command (which apparently worked fine for the 2000 and 3000 switches). But when you enable IP routing then the switch does not use the default-gateway to learn its default route and would look for some other mechanism to learn its default route. I am assuming that there was not any other mechanism and so the 4000 basically did not have a default route. When you configure no ip routing (which was good advice from Paul) then the 4000 stops working as layer 2 switch and at that point will use default-gateway to determine its default route.
HTH
Rick

Cisco Nexus 3000 ssh access

I have a Cisco Nexus 3172T in a small environment running System version: 6.0(2)U3(1). I am using a vlan as management access, i.e. vlan100 is on every device and is using for snmp/ssh access. On the same switch I have one non-switchport (routed) port (eth1/6 in this case) connecting to a remote datacenter. I am able to SNMP poll and ping the vlan100 interface on the switch from everywhere, and I am able to SSH login while I am connected on any of the VLANs that are known to the switch. My problem comes when trying to access (SSH) the switch from the remote datacenter location (SNMP/Ping also works from the remote location). The only way to SSH access the switch from the remote location is only if I SSH in on the routed port (i.e. eth 1/6).
I am not using the dedicated management port on the switch (nor I have any plans in the future). I am also running very plain config, a few switchports, one routed port, and the default control-plane policy (which is only policy pps). There are the ACLs on the VTY.
Am I running into a known bug or is there some configuration requirement to allow this ?
thanks
dragan

Its not in a VRF or anything like that is it?
Also have you tried setting the ssh source interface to be vlan 100.
http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus3000/sw/security/6x/b_Cisco_n3k_Security_Config_6x/b_Cisco_n3k_Security_Config_6x_chapter_0110.html#task_4AFC76AF5CD04C728EF30CB15EAE2655

Configuring TACACs Server for Cisco VPN 3000

Does anyone know how to get to the configuration setting to specify a TACACs server?

You need to be very careful when setting
up this thing. If the AAA server is down
for whatever reason, you will NOT be able to
log into the Concentrator again. As far
as the VPn3k console is concerns, it will
let you login with the "admin" account,
even though the AAA is up and running. In
other words, you can login from console
with both "admin" and AAA account at the same
time.
What a mess.

IAS and Cisco Concentrator 3000 series?

Is anyone authenticating their VPN users via Windows IAS, if so how. I would like them to be only to get on the network if they are in a particular Active Directory group (not local IAS users)
Thanks

Hi,
Yes , it works fine. For network access you need to set up group policy.
Regards,
~JG

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!

Will Nortel's Contivity VPN Client work with Cisco's VPN 3000 concentrator?

Hi, need help. We have VPN 3000 concentrator and a number of VPN clients (these are using Cisco VPN client).
We have one user that wants to use Nortel's Contivity VPN Client. Will this work with the Cisco COncentrator 3000?

Tricky question - in theory yes, if the nortel client follows all the ISPEC RFC's.
I did try to get the cisco VPN client working on a Nortel Contivity once - did not get it working - but did'nt have that much time to test and get it working.
My advise - Configure, TEST DEBUG TEST DEBUG!

Installation VCS Control and Expressway vmware applications on one BE6000

Hello Community,
I want to buy one BE6000 and additional VCS Expressway vmware application. Then I'm going to deploy VCS Control vmware application and VCS Expressway vmware application on this BE6000. Also I plan to place this BE6000 in the DMZ.
Please help me, may I do that kind of deployment - VCS Control and Expressway vmware applications on ONE BE6000 ?
Thanks in advance.
Regards, Maksim.

The BE6000 supports VCS-c I belive you would need a seperate box for the VCS-e
http://www.cisco.com/en/US/prod/collateral/voicesw/ps6788/vcallcon/ps11369/at_a_glance_c45-720492.pdf
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/BE6000/InstallationGuide/9_x/CUCM_BK_IA4BAD3A_00_installing-cisco-business-edition-6000.pdf
Also I would check Cisco site for the new Co-residency Policy Requirements
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/BE6000/Coresidency/9_x/BE6K_coRes.html

Two EX90 devices can make video calls over Internet with No VCS-C and VCS-E

Dear Experts;
I have just started TelePresence and VCS 2 weeks before by going through cisco docs and videos and I had taken a risk of implementing the infrastructure elements.
We are now implementing Cisco Tele presence with VCS-C, VCS-E TMS,TCS,MCU and End points with Jabber in One setup.
and in another setup CUCM 10.5,UCCX 10.5 IM&P,Jabber with some 10 agents.
Now the question is In our same building in 2nd floor we have one EX90 and in 5th Floor one EX90 and over LAN we can make video calls using IP address.
In the same way is it possible to make a video call between 2 EX90 devices present in different location in the same city over Internet without the involvement of VCS-C and VCS-E.
Appreciate your valuable reply.
Regards
Debashis

The simple answer to that is NO! Where is the EX90 registered to at the moment? Is it on the VCS? or CUCM

Cisco MXP 3000/6000 & VCS

Similar Messages

Maybe you are looking for