I haven't messed with H323 but have SIP and asterisk phone server. I know in that case you have to set both the phone (or it auto detects) for nat and for the phone to use the public ip on their end. On the server you set the entry for that phone for nat also.
Maybe that helps some. Terri Kelley Network Engineer 254-697-6710 This email message is intended only for the named recipient(s) above, and may contain, together with any attachment(s), confidential information that is privileged. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing, copying or distribution of this message and any attachment(s) is strictly prohibited. On May 6, 2008, at 8:03 AM, Rick Smith wrote: > > btw... they're running H323, not SIP... > > -----Original Message----- > From: [EMAIL PROTECTED] on behalf of Rick Smith > Sent: Tue 5/6/2008 8:54 AM > To: [email protected] > Subject: [Mikrotik] VOIP server seeing internal address ? > > > I've got a customer with a VOIP server (Altigen) inside a Mikrotik > router (3.0beta5 for various reasons) > > Let's say outside IP is 1.1.1.1 - internal is 192.168.15.1 > > All internal phones have 192.168.15.x addresses, remote phones in > various places with various IP's. > > Remote phone connects to public IP, gets dst-nat'd to 192.168.15.250 > (Altigen server IP). They have several publics on this router - we > picked one and just dst-nat'd the whole public -> internal > > When the phone server gets the connection from the remote IP, it > sees 192.168.15.1 as the incoming IP, and it can't talk to the > remote phone because the phone server's expecting the public IP > (according to the dealer on-site) > > No matter what I do, I can't get the public IP to appear on the > internal network as the source address. I'm pretty sure that's the > way NAT is SUPPOSED to work - but of course they're telling me that > Altigen works just fine with every other router in the world and > "they've never had this problem with sonicwall or ciscos" > > What to do? What to do. > > R > PS...we do dst-nat'ing on another public, straight to a webserver > inhouse, and it works great, although the logs on the server say > 192.168.15.1 is requesting the page... > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://www.butchevans.com/pipermail/mikrotik/attachments/20080506/f3b79748/attachment.html > _______________________________________________ > Mikrotik mailing list > [email protected] > http://www.butchevans.com/mailman/listinfo/mikrotik > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://www.butchevans.com/pipermail/mikrotik/attachments/20080506/0af65365/attachment.html > _______________________________________________ > Mikrotik mailing list > [email protected] > http://www.butchevans.com/mailman/listinfo/mikrotik -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.butchevans.com/pipermail/mikrotik/attachments/20080506/2eda1353/attachment.html -------------- next part -------------- A non-text attachment was scrubbed... Name: LogoHzlsigtest.jpg Type: image/jpeg Size: 2158 bytes Desc: not available Url : http://www.butchevans.com/pipermail/mikrotik/attachments/20080506/2eda1353/attachment.jpg
