So I am doing some testing......

[kflounders]

I have an IP hard phone connecting through the internet to a 412 I hard coded everything on the station but I am stuck on discovering. I am trying to see if we can utilize the hard phones without lan to lan VPNs. I am pointing the 4606 to the public address of the 412 and have opened up all ip traffic from my routers public IP address. I am used to utilizing VPNs for home users so this is a first for me.

What me do wrong?

 

[Morrack]

You cannot put a hardphone behind a NAT box without VPN tunnels. Does the 412 truly have a public IP address, or are you NAT'ing at that end too?

IP Hardphones embed their local IP address deep within the h.323 packet, and the 412 will try to respond to that ip address not the public NAT address of your home 4606 users gateway. Regardless of what the packet header has to say on the subject.

To do what you want, both ends must operate in non-NAT mode (sometimes referred to as router mode vs. gateway mode), and you must have multiple public IP's, even for the home users.

Peter

 

[kflounders]

Well I know how to do that, but there isn't any fun in it. I was hoping that someone figured out a super secret NAT enabler .txt code to work.

Oh well, LAN to LAN VPN's to all.

 

[Morrack]

LOL. Au contraire, my friend, there is plenty of fun in it. I've had hours of entertainment fighting with linksys over a bug in their code (they won't admit that of course) that prevents http traffic from passing through properly when in router mode and using blocks of IP's

Peter

 

[big70]

It can be done.

We do it with IP from Tadicom.

I have a IP-hardstation and my Collega to at home and the PABX is at the Vendor.
I am using Nat at Home and nothing special.
I now the use a special box Called Sentinal to route the call from the public adress to there adress.
I wil try to get more information.

Greets Peter

 

[kflounders]

Yes, more info please.

 

[big70]

This is how the Coral Sentinel works.

Coral Sentinel — Session Border Control
The Coral Sentinel terminal is a Session Border Control (SBC) solution enabling
connection of remote IP phones that sit behind NAT (Network Address Translation)
servers or firewalls.
In standard operations a firewall has to expose numerous holes in its defenses - one for
each endport. The Coral Sentinel addresses that and maintains one defined access point
to the firewall or NAT server, through which all incoming traffic connects. Therefore,
many separate IP phones can connect to the internet via the firewall or NAT server,
without the need to open up a separate channel to connect each call, as all incoming
traffic is now routed through one firewall-controlled channel to the Coral Sentinel.
The Coral Sentinel enables the connection between external IP phones via the NAT
server, and the local IP phones via the UGW card and the LAN.


What i dont now is if you can use this with other Vendors.
When i have the time i wil check this out, and maby there are other session border controllers we can use for the IP-Office.

Greets Peter

 

[Morrack]

With a cursory read sounds to me like you're still using NAT, just a more secure method. Therefore I doubt it will work with IPO.

Peter