Tandberg MX 990 MultiSite (embedded MCU) + VT Advantage?

Has anybody used a Tandberg MXP 990 with the MultiSite feature (embedded MCU) to join multiple MXP 990's and multiple VT Advantage stations into a call?
I figure it should work. The MX 990 is an H.323 endpoint to CallManager. Call signalling from a VT Advantage (SCCP) station will be converted by CallManager.
I'm trying to avoid purchasing a 3515 MCU today.
With this equipment, on CM 4.1.X, will I be able to "host" a conference on the MXP 990, by dialing into it?
Tandberg MXP 990 + MultiSite MCU
Tandberg MXP 770
VT Advantage equipped 7960
VT Advantage equipped 7960
7960
Thanks!

Yes, I've used the multisite functionality (embedded MCU) in the Tandberg MXP 990 for multipoint conferences with VTA clients. In my scenario, the H.323 MXP 990 device (code revision F4.1) was registered to a gatekeeper, and the SCCP (VTA clients) simply dialled the E.164 number of the H.323 device. The MXP 990 spots another incoming call and creates a conference. I did find that the MCU functionality wouldn't work through an IP-IP Gateway, but I haven't tried this with a more recent 12.4T IPIPGW release. Also, I didn't try the MXP registered as a native H.323 device in CallManager.
In its role as an embedded MCU, the device will be generating multiple audio and video RTP streams with the conference participants, so you should be mindful of the bandwidth requirements and the placement of the endpoint within the network. (The placement of dedicated MCU resources may be different to an embedded MCU within an endpoint, which will more likely be sited towards the network edge).
Please rate useful posts.

Similar Messages

The Difference about LIC EX90

Dear All,
can you tell me, the difference about
LIC-EX90-MS
LIC-EX90-PR
LIC-EX90-DD
Thank you for your attention.
Regards,
Rinaldy

Hi,
LIC-EX90-MS = MultiSite option. Enables embedded MCU (you can do a videoconference up to four participants).
LIC-EX90-PR = Premium Resolution option. Enables support for video resolution 1280x720@60 fps (720p60).
LIC-EX90-DD = Dual display option. Enables a second display that can be dedicated to content.
Hope to help, please remember to rate the post if it does.
Kind regards!.
- Adrian.

Advantages of using labview in embedded application when compared to c ?

Hello all,
I am looking to develop embedded application with help of labview programming
Started with Lm3s8962 evaluation board.
So i would like to know
1 Advantages of using labview in embedded application when compared to c ?
2 Can we deploy the code in any kind of controller by writting drivers for it ?

hello, the LM3S8962 microcontroller is a good sispositivos for developing applications of medium complexity, according to your questions:
1. if you work applications with embedded systems will save labview time in prototyping, we know that if you work with a company specific microcontroller, you must learn the language with which you are working Asm, Basic, C, then if you change hardware again start adapting your code in the libraries of the new compiler. Labview does not happen.
2. Labview only works with some microcontroller manufacturers and specific models.
Atom
Certified LabVIEW Associate Developer

Advantages & disadvantages with embedded, external use of sub reports

Hi Guys,
I have a Question on "re-import subreport when open" option, which is available for sub report and it will reimport the sub report every time when we open the main report.
With that option we can see every modification until when we open that report.
My question is, does we have any document which specifies the Advantages & disadvantages of using Embedded, external(re-import) subreports in Main reports.
And i have one more scenario, i have a subreport which is used in ten reports. In every report i am taking the same Sub report from shared location and check the option "reimport subreport when open". So when i apply any change that change will applied for all ten reports at my next schedule.
My Question is: if the Subreport executes 10 minutes and i scheduled all the 10 main reports at a time. At that time does the sub report lock for one report or it will use for all the 10 reports? Can anyone give brief explanation about this?
Regards,
Naga.

hi Naga,
the only advantage to this feature is that changes are reflected when opening your report. that's it....useful for changes when you're in dev mode. disadvantage may be slight loss of speed vs. just embedding the subeport and then manually reimporting.
the second question should probably be directed to the bi platform and not in cr design as you're scheduling.
-jamie

END OF LIFE NOTICE FOR TANDBERG MCU 8+8/16+16

Does any have a copy of the .pdf end of life notice for the TANDBERG MCU 8+8/16+16 ???
I saw the link in the CISCO web site dated 15DEC2011 but when I clicked on the link the replay was document not found.
Hoping someone has a copy they can send or provide the exact URL to get it.
Email: [email protected]
Thank you.

Yes .. they are looking and though someone on the community might have a copy.

Advantage of using Spring Context over Java Embedding

Hi ,
Is there any advantage of using Spring Context over Java Embedding?
--Steve

Hi All,
Anybody can answer my question?
--steve

Tandberg Codian MCU 4505 integration with Microsoft Lync server 2010

Hi,
We are trying to integrate Tandberg Codian MCU 4505 with Microsoft Lync server 2010.
We do not have any VCS in the setup.
If anybody has tried it before, please suggest configuration to be done on Tandberg Codian MCU 4505 and Lync server.
Regards,
RN

Hi,
so, i have the same environment. Lync 2013 and a cisco 1000V router on esxi with VRFs.
here is m config:
vrf definition Mgmt-intf
address-family ipv4
exit-address-family
address-family ipv6
exit-address-family
voice vrf Mgmt-intf
voice service voip
no ip address trusted authenticate
address-hiding
media disable-detailed-stats
allow-connections sip to sip
no supplementary-service sip moved-temporarily
no supplementary-service sip refer
sip
bind control source-interface GigabitEthernet0
bind media source-interface GigabitEthernet0
listen-port non-secure 5066
voice class codec 1
codec preference 1 g711ulaw
codec preference 2 g711alaw
codec preference 3 g729r8
voice class codec 2
codec preference 1 ilbc
codec preference 2 g722-64
codec preference 3 g711alaw
codec preference 4 g711ulaw
interface GigabitEthernet0
vrf forwarding Mgmt-intf
ip address 172.16.1.164 255.255.255.0
negotiation auto
dial-peer voice 15 voip
tone ringback alert-no-PI
numbering-type unknown
preference 1
destination-pattern 4.
rtp payload-type comfort-noise 13
session protocol sipv2
session target ipv4:172.16.2.207:5068
session transport tcp
voice-class codec 2
dtmf-relay rtp-nte
dial-peer voice 17 voip
numbering-type unknown
preference 1
destination-pattern 7.
rtp payload-type comfort-noise 13
session protocol sipv2
session target ipv4:172.16.1.32:5060
session transport udp
voice-class codec 2
dtmf-relay rtp-nte
gateway
timer receive-rtp 1200
sip-ua
keepalive target ipv4:172.16.2.207:5068 tcp
172.16.1.32 - Asterisk with a extensions on it.
172.16.2.207 - Lync 2013 mediation server with other extension on it
i can call from Asterisk extension via router and to Lync extension.
i cannot call from Lync to Asterisk.
TCP session with the router from Lync on port 5066 does not come up. three way handshake seems to come up.
strange. lync person seems to configured everything correctly
any thoughts?

3511 MCU with video Advantage

1.DOe the 3511 MCU supports cisco Unified video advantage ( PC- USB camer based video product) for 3 or more party video conferencing ?
2. Does the video advantge endpoint can do video conference with IP phone 7985G ?

Answer is 'Yes' for both questions.
You can configure 3511 to use either Skinny or H323 protocol. If configure as Skinny, then it is just another CFB in CM; CM will allocate it as per MRG and MRGL configuration. If configured as H323, then you have to configure 3511 as H323 gateway in callmanager and have a RP to point to the gateway. Typically, the RP will be your conference ID number.
7985 is just another video phone like VTA with an IP Phone; and they do support same type of codecs. Hence you can use 7985 to do video call with VTA as well to do conference with an MCU.

Cisco UCM 8.0 and new Tandberg VCS/ MCU

I can find a lot of quite old interoperability documents on Tandberg and Cisco.
But if a customer already had Tandberg H.323 endpoints and wanted to add a Tandberg VCS and MCU for VC bridging, what is the best way to get the Cisco phones to be able to join a multi-party video call on the MCU?
I'm thinking the MCU could run as an end point to Call Manager (phones running SCCP)?
Or, can you have SIP trunk(s)from CUCM 8.0 to the VCS and use traversal calls?
Or even if the phones were running SIP, can they talk to the VCS via the CUCM. Do they even need to - I can't imagine they can act as SIP endpoints registered to the VCS while their "day job" is being registered to CUCM.
Any help appreciated....Even if it means telling my questions don't make sense - as long as you tell me why!
Regards

Gordon,
The latest deployment guide for Cisco VCS and Unified Communications Manager (UCM) is available here:
http://www.cisco.com/en/US/docs/telepresence/infrastructure/vcs/config_guide/Cisco_VCS_Cisco_Unified_Communications_Manager_Deployment_Guide_CUCM_6-1_7_8_and_X6.pdf
Based on your post, I'd think you want to go this route:
1. Build a SIP trunk between VCS and CUCM. You have to make some decisions as to how you are going to do this:
- Security: Are you going to use TLS for setup? SRTP for media? If yes, then you will need to look at getting certificates aligned on both systems. The best approach is to use an internal CA to generate server certs for both clusters and then configured CUCM and VCS with the appropriate CA trust list. There are several docs for both products that cover this.
- Call failover and/or load balancing: If load balancing is required, you will need to leverage DNS SRV records that point to your CUCM cluster and a separate set of DNS SRV records for your VCS cluster. The pros: you can get away with one SIP trunk on CUCM and a single DNS neighbor zone on VCS. The cons: Some folks get squeamish with DNS SRV. An alternate approach is detailed in the deployment guide reference above. You would createa "neighbor zone" on the VCS. One per CUCM call processing node. On the CUCM you would create a separate SIP trunk for each VCS (or, if using CUCM 8.6 you can get away with one trunk, multiple peers).
- SIP profiles: This is easy. The deployment guide lays it out for you and the VCS includes a pre-canned profile so it knows how to talk to CUCM.
2. Dial plan. You will want to configure your dial plan so that you avoid overlaps/conflicts/call routing loops. As a simple example, assume you program all 7xxxx extensions to be video. Done. Tell CUCM to send all 7xxxx extensions to VCS. Tell VCS to send CUCM extensions to CUCM. Tricky parts come in when you want to enable features like SnR. Both products have a facility for this. You have to learn both and pick one as an authority. There is more to it. But no need to get too fancy at this point.
3. SIP/H323 interworking. The VCS Control can support up to 100 concurrent, interworked calls. So, the VCS can handle SIP to H323 interworking for you. It is good like that.
- MCU: You can avoid interworking for your MCU if it supports SIP natively. If your MCU is one of the Codian boxes then it can do H323 and SIP simultaneously. A discussion on this can get quite involved. The basic idea is that you configure a SIP Neighbor Zone for the MCU. You configure membership rules on the VCS to put MCU SIP URI registrations into this neighbor zone. Finally, you configure search rules on the VCS so that H323 and SIP dial patterns for a MCU resource are given the same search priority. Say, you use 100 as your H323 prefix. Then you would have a "100\d*" H.323 rule and a "100\d*@mcu.uri.com" SIP rule. The first rule points to Local Zone and the 2nd points to the MCU SIP Neighbor Zone. They are given equal priority and are searched at the same time. VCS will prefer SIP if the original caller is SIP. If this is too much info for you, just do the interworking until you get comfy and can optimize your design.
- VCS registered endpoints: VCS registered endpoints that support SIP and H.323 should have both protocol stacks enabled. This will minimize interworking when you call from VCS-to-CUCM. For CUCM-to-VCS you will probably still deal with interworking since your SIP URis probably are something more useful than an e164 number@yourdomain.
Phones on the CUCM can stay on the CUCM. Their calls will route via CUCM to VCS over the SIP trunk. You may need to dork around with CODECs, regions, and locations to ensure transcoding isn't needed. The bottom line is that if a phone is registered to CUCM, it doesn't need to have a separate registration for VCS:
phone-->CUCM-->VCS-->endpoint/mcu/etc.
Get things configured right, then you can think of this solution as a single system with multiple components rather than individual systems spliced together.
HTH.
Regards,
Bill
Please rate helpful posts.

Tandberg codian MCU+IPVCR+ISDNGW

Hi Folks,
We have the following setup at DC & DR as show in the attached diag. I have a few technical queries related to how this kind of system should
be setup & made to working. Please input your comments & suggestion on it.
As you can see that we have 2 x MCU, 1 x IPVCR & 1 x ISDNGW at each DC, DR & an additional TMS suite at DC. And 22 sites are connected
to DC & DR with MPLS as of now, as BRI is not yet available for any sites. Presently we have setup the system with basic settings all the Devices & endpoints are assigned IP's. So we are able to make IP-IP calls directly to any endpoint. we can also make conference through any MCU.
1.) Please suggest if instead of Point-Point calls directly from Endpoint should be a good idea or whether to use MCU in between point to point calls.
2.) Presently we dont have any external gatekeeper, we plan to make use of internal gatekeeper, how can we achieve this ?
3.) If for example i divide my sites equally between DC & DR, & while using MCU internal Built-in gatekeeper for registration, how can we use it & integrate it with ISDNGW & IPVCR. Also how can we use prefix scheme, instead of using IP to call endpoint.
I will be very thanksful to anyone who can give their suggestions, comments & support out here & give a overview of how this system should work based on best practices. So that we can proceed to setup this architecture.

Hi Folks,
We have the following setup at DC & DR as show in the attached diag. I have a few technical queries related to how this kind of system should
be setup & made to working. Please input your comments & suggestion on it.
As you can see that we have 2 x MCU, 1 x IPVCR & 1 x ISDNGW at each DC, DR & an additional TMS suite at DC. And 22 sites are connected
to DC & DR with MPLS as of now, as BRI is not yet available for any sites. Presently we have setup the system with basic settings all the Devices & endpoints are assigned IP's. So we are able to make IP-IP calls directly to any endpoint. we can also make conference through any MCU.
1.) Please suggest if instead of Point-Point calls directly from Endpoint should be a good idea or whether to use MCU in between point to point calls.
2.) Presently we dont have any external gatekeeper, we plan to make use of internal gatekeeper, how can we achieve this ?
3.) If for example i divide my sites equally between DC & DR, & while using MCU internal Built-in gatekeeper for registration, how can we use it & integrate it with ISDNGW & IPVCR. Also how can we use prefix scheme, instead of using IP to call endpoint.
I will be very thanksful to anyone who can give their suggestions, comments & support out here & give a overview of how this system should work based on best practices. So that we can proceed to setup this architecture.

Connecting VT Advantage to Polycom MCU

I'm trying to get VTA(s)to connect to a polycom MCU.
I can call other Polycom VSX / PVX units with no problems, only the MCU is giving issues. I get to a mulit screen display wih VTA but then the MCU complains about a Video Sync Loss and neither end can see VTA Video. Though VTA cleints see polycom endpoints in the confrence
I've got a Polycom Gatekeelper and the hole mess integrated into call manager 4.1(3)
I'm tried limiting the codec of the meeting room to H.263 with no luck.
Funny thing is I have a Polycom VSX with a "soft" MCU software on it and it can run VTA clients i split screen OK.
anybody have any experiece with this is so please reply.

FYI - I resolved my own issue. There was a variable that had to be set on the Polycom MCU and the Polycom MCU needed to be set for Auto layout.
I'm still in process of figuring out what "breaks" the VTA and the polycom MCU

3545 MCU v5.7 with Tandberg TMS v11

Hello.
Does anyone know of any compatibility issues between TMS v11 and 3545 v5.7?
I know that TMS v11 has been tested with v5.1.0.0.16 but nothing found about v5.7.
Cheers
David

VC3515 MCU connectivity with h323 unregister endpoints

We recently purchased the IPVC3515 MCU and I currently have it configured for H323 registering to a cisco IOS gatekeeper which is in turn registered to our CCM 4.02 installation. We just added some Video Advantage cameras that will successfully connect to the MCU thru an H323 trunk. We also have the typical Polycom H323 endpoints that register with the Gatekeeper and will also connect successfully to the MCU. So all that is working as it should.
My question is whether it's possible to allow unregistered endpoints the ability to connect to a conference on the MCU. We eventually want to be able to pull in some H323 video endpoints from the internet and I would rather not require them to register with our GK if at all possible. I can currently call out to an unregistered endpoint from the MCU and it connects successfully. I do this by disabling the gatekeeper in one of my polycom units and than initiate the invite from the MCU. Eventually I plan on doing this with endpoints on the internet but I wanted to keep the whole firewall complexity out of the equasion for now so I am testing on our LAN. However I have not found a way for that same endpoint to call into the MCU without being registered to the Gatekeeper. Does anyont know of a way on the MCU to make this happen? Is there anytype of software or gateway out there that could forward the endpoint into the MCU?

We have done the same here though we use a Tandberg instead of a Polycom.
It is NOT possible to connect from a H.323 endpoint that is not registered at your gatekeeper.
I know that Tandberg offers border controllers to resolve this issue, have a look at your vendor to figure out what they have.
Hugo

Cisco advantage vs skype.

good morning,
We have recentley started using the cisco video advantage and our users like the quality and ease of setup. we are running in to issues in which we need more than one on one calls. I know an mcu would need to be added to get multi point conferencing. we are now trying skype group calling but the quality, for whatever reason, is not good. we have teleworkers and need a solution that would allow 2-6 on a call at a time. My question, does anyone now use a similar setup?? and is the quality better through an MCU than it would be with skype...or is it really just a case of we are at the mercy of the IP of our teleworkers?
Thank you

I am not sure about the best approach to dealing with call quality in the situation where at least a portion of the video stream is traversing the internet. That being said, my opinion is that you should expect better overall quality when leveraging a MCU. This doesn't mean that all calls will be high quality. The MCU has a very distinct advantage in that it will ensure that the call quality for all users is not dumbed down to the lowest common denominator. Put another way, if you had 5 callers in a video conference and one of those callers has a crappy connection (for whatever reason) the other callers will still maintain their call quality. Now, those 4 callers will still see poor quality from the endpoint experiencing issues but they will still have good quality with each other.
This is true with any system implementing a MCU that leverages hardware DSPs for media mixing.
With Cisco acquiring Tandberg you may also take a look at leveraging Movi. I personally think Movi is a better software codec than CUVA but I always had a dislike for CUVA which may or may not be fair. If using Movi then you would still need a MCU to provide the multipoint capabilities. Integration with CUCM and CSF is underway from my understanding. Which is to say you will likely see a push to Movi in the upcoming months.
HTH.
Regards,
Bill

What is the use of preview JPEG embedded in DNG?

I tried converting a CR2 file to DNG, choosing different size JPEG preview, including full, medium and none. The converted DNG file all look the same when I open them in LR3. So the image we see in the library and develop module is not the JPEG embedded in DNG??? What is the JPEG preview used for then?

I never was able to see any preview in Windows 7, whether I use Canon's CR2 or DNG.
You need WIC codecs for the given format. If you have the codecs installed Vista/Win7 will be able to display thumbnails in Explorer and previews in the built-in preview apps. As far as I know there are free codecs available from manufacturers for most raw formats (Nikon, Canon, DNG), but most (all?) are 32-bit only. There's a commercial third-party 64-bit DNG codec available.
So what application on Windows 7 takes advantage of the preview exactly?
I use the free IrfanView. It does use embedded previews from all raw files, both proprietary and DNG. It can be configured to demosaic too.

Tandberg MX 990 MultiSite (embedded MCU) + VT Advantage?

Similar Messages

Maybe you are looking for