[cisco-voip] cube and address hiding
Zoltan.Kelemen at Emerson.com
Zoltan.Kelemen at Emerson.com
Wed Dec 18 04:11:52 EST 2013
Hi Erick,
You couldn't have address hiding and media flow-around working at the same time for sure. Media flow-through is the default setting anyway and address hiding command may or may not enforce that, but if you have media flow-around, then by definition there is no way the CUBE could do anything about media IPs.
That being said, with flow-through and address hiding no internal IPs should wander out beyond the CUBE, so not only remote endpoints but provider's border element as well would only see the CUBE's IPs.
Also, the CUBE is already acting as an MTP between AT&T and your cluster so you would only need to enable MTP's in your CUCM if you need to do something with the traffic from your CUBE to the rest of your network (like DTMF conversion to a H.323 gateway or similar)
Cheers,
Zoltan Kelemen
Global Communications and Information Security
Implementation Engineering
w: +40 374 132356 | m: +40 757 039093
From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Erick Wellnitz
Sent: Tuesday, December 17, 2013 5:39 PM
To: cisco-voip
Subject: [cisco-voip] cube and address hiding
First major CUBE/SIP deployment using AT&T Flex Reach.
Unfortunately I've had to parse two documents from AT&T as well as one from Cisco to get the config put together.
One aspect I'm not 100% certain on is address hiding, media flow through and MTP.
I've configured address hiding per the Cisco document. All of the documentation I have read says this hides the signaling and media peer addresses from the endpoints. Does this include the provider's border element? Do I need medai flow through or MTP to make this work without advertising our network into the provider's network?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20131218/518a0ff1/attachment.html>
More information about the cisco-voip
mailing list