[cisco-voip] Connecting to third party CUCM via ICT trunk

Ryan Ratliff rratliff at cisco.com
Thu Jun 2 12:01:05 EDT 2011


The point of a TRP or MTP will be to anchor the RTP stream to a known IP address for NAT purposes.  The port range will still be wide open as you stated, but the IP address will be known (so you can do NAT and not PAT).

-Ryan

On Jun 2, 2011, at 11:03 AM, Damian Turburville wrote:

I am probably being thick here but will the phones not try and establish an RTP connection between themselves which could be on a wide range of ports? 
Damian


From: Ryan Ratliff <rratliff at cisco.com>
To: Paul <asobihoudai at yahoo.com>
Cc: Damian Turburville <d_turburville at yahoo.com>; "cisco-voip at puck.nether.net" <cisco-voip at puck.nether.net>
Sent: Tue, May 31, 2011 9:35:37 PM
Subject: Re: [cisco-voip] Connecting to third party CUCM via ICT trunk

IME is quite the complex solution for sites that are already connected.  Using an ICT will be the way to go. 
If firewalls traversal is required then TRPs or MTPs should be sufficient.  ICTs use H.323 as far as firewalls are concerned.

-Ryan

On May 31, 2011, at 10:59 AM, Paul wrote:

I would suggest you upgrade and use IME which was created for this exact purpose...but that's obviously not the answer you were looking for. . .


________________________________
From: Damian Turburville <d_turburville at yahoo.com>
To: cisco-voip at puck.nether.net
Sent: Tuesday, May 31, 2011 7:30 AM
Subject: [cisco-voip] Connecting to third party CUCM via ICT trunk


Hi,
I am looking for some advice. I have a CUCM 6.1 system at one of my sites and we have a third-party who is on our WAN (but controls their own LAN and servers etc) who also has a Call Manager (not sure what revision) and they would like to make calls between the two sites. I was thinking it would probably be fairly easy to setup an ICT trunk between the two systems but I am sure our security team would have some issues with that. Is there any way of making the trunk more secure? Locking down ports on the firewall etc, maybe some kind of VPN connection? Is there anyone out there that has done this that could share their experiences?
Many thanks,
Damian

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20110602/0328cb41/attachment.html>


More information about the cisco-voip mailing list