[cisco-voip] natting on a cisco will it work properly on voice

[Jonathan Charles]

Ah...

Good point, cuz the config will contain the actual IPs, and the phone
is connecting to the NATted IP...

Yeah, you will have to double NAT (on the remote side, so that the
inside local IP of the CCM is reachable by the outside global IP...)



J

On Nov 12, 2007 9:20 AM, Linsemier, Matthew <MLinsemier at apcapital.com> wrote:
> I had some issues with NAT and CallManager when we were doing some tests
> in the past.  I believe that you will have to do some double NATing to
> get this to work correctly.
>
> We were testing a CallManager server in a DMZ with IP Communicator and
> we ran into some issues, not with connectivity to the server, but with
> the configurations that were downloaded to the phones downloaded.  The
> server was NATed to a public address, but the configurations that were
> being sent to the phones all had the private address of the server.
> When the phones tried to register, they were trying to find the server
> by the private address, not the NATed address.  I didn't spend too much
> time with this so there is probably a workaround, but I thought I would
> make a quick mention.
>
> Matt
>
>
> -----Original Message-----
> From: cisco-voip-bounces at puck.nether.net
> [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Jonathan
> Charles
> Sent: Monday, November 12, 2007 10:01 AM
> To: Alex Koss
> Cc: Christopher M. Bomba; cisco-voip at puck.nether.net
> Subject: Re: [cisco-voip] natting on a cisco will it work properly on
> voice
>
> Sure, why wouldn't it?
>
> Just make sure Option 150 at the remote site points to the NAT address
> of the Publisher...
>
> If you are double NATting, it could get more complex, but as long as
> you aren't screwing with the ports, everything should be okay...
>
>
> J
>
> On Nov 11, 2007 7:15 PM, Alex Koss <willams23 at hotmail.com> wrote:
> >
> >
> > Hi
> >    I wnat to ask if natting will work on voice properly on cisco
> >  Alex
> >
> >
> >  ________________________________
> >  Date: Fri, 9 Nov 2007 10:32:33 +0200
> > From: yahoo at cumhur.com
> > To: cbomba at s4nets.com
> > CC: cisco-voip at puck.nether.net
> > Subject: Re: [cisco-voip] Using MRTG to monitor PRI usage
> >
> > Hi Chris,
> >
> > MIB: 1.3.6.1.4.1.9.10.19.1.1.1.1.7
> > Also please check this page
> >
> http://www.cisco.com/univercd/cc/td/doc/cisintwk/intsolns/dialsol/nmssol
> /mrtg.htm
> >
> > Best Regards,
> > Cumhur
> >
> >
> > On Nov 8, 2007 10:18 PM, Christopher M. Bomba <cbomba at s4nets.com>
> wrote:
> >
> > I am trying to monitor or archive the usage of my PRIs I have.  I
> heard you
> > can use MRTG to do that.  Does anyone know the MIB I need to use to
> get that
> > information?
> >
> > Thanks,
> > Chris
> >
> > _______________________________________________
> > cisco-voip mailing list
> > cisco-voip at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-voip
> >
> >
> > ________________________________
> > Windows Live Hotmail and Microsoft Office Outlook - together at last.
> Get it
> > now!
> >
> > _______________________________________________
> > 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
> CONFIDENTIALITY STATEMENT
> This communication and any attachments are CONFIDENTIAL and may
> be protected by one or more legal privileges. It is intended
> solely for the use of the addressee identified above. If you
> are not the intended recipient, any use, disclosure, copying
> or distribution of this communication is UNAUTHORIZED. Neither
> this information block, the typed name of the sender, nor
> anything else in this message is intended to constitute an
> electronic signature unless a specific statement to the
> contrary is included in this message. If you have received this
> communication in error, please immediately contact me and delete
> this communication from your computer. Thank you.
>