sundance-communications.com/forum Forums TDM Business Telephone Systems Samsung Telephones & Systems os7200 voip remote sites

we have installed a os7200 with 2 remote sites using vpn to each site, 8 ip phones on each site, the ip phones can make outgoing calls and ring any extn in the main office. but we have no speech
between the 2 vpn sites. if you connect a ip phone a the main office it can talk to all sites.

any help??

what router are you using. I have a simular setup and i'm having the same problem as you.

a netgear in bridge mode and a sonic wall. Is your problem on a VPN or just that the you cant talk from ip to ip using public ip add in the mcp & mgi?
if so in mmcxxx (pub to pub) set to use mgi and this will give you speach between the ips.
(if its a vpn sorry cant help you )


(edited for spelling and mmc's above user or admin guide)

If you are using a VPN tunnel, then you should set the system to private and use the internal IP address.

One way audio is almost always a problem with your firewall. In your case, you need to make sure specific ports on your Sonic Wall are open. I don't have that info handy, but I will get it for you.

Hi

The ports that need to be open for speech are the RTP ports.

UDP 30000 - 30031 forwarded to the MGI (Voice traffic)
TCP 6100 forwarded to MCP (used to setup call)

for IP phones TCP 6000 & TCP 9000 to MCP

Also make sure that if you use a firewall and private IP and use your ip handsets public the set MMC xxx IP type to Public with firewall. otherwise no voice will be heard.

good luck

Sorry I'am late to the party (I mean post) but the answer to this is smiple. Your IP phones should be set to private, that is correct.....but you need a VPN tunnel between the two remote offices. By your description you have a VPN tunnel between the Main office (A) and remote office (B) and other remote office (C), but no VPN tunnel from Office B to C....therefore your IP phones can talk to the MCP of the system (uses UDP 6000) to log into the system and initate a call, then VoIP (SPNet) call setup communicates with the MGI this recognizes that this is a ITP phone to ITP phone communication and hands off the voice to communicate directly between the two IP phones. These are two dispare networks that do not communcate directly therfore no voice. There are two ways to solve this easily.

1. Create a full mesh nework with a VPN tunnel from office B to office C so the IP phones can communcate directly.

or

2. Setup the phones as Public IP and enable the Pub to Pub "Use MGI" and option for each of the phones. This will force the IP phones to use the MGI card to communicate with each other but consumes MGI port resources.


Edited for content above user or admin guide. Grammer and spelling not edited

OK when everyone elses post do not work. try going to XXX and make sure all 3201-3208 extensions are set for Public w/ firewall. you can do this remote thru Office Serv. This will cure your problem.

Dolphins: Your suggestion still will not work. The three networks are on a PRIVATE VPN network. The system is on the A network and ITP's on two different networks B and C....So C can talk to A and B can talk to A, but B and C can not talk to each other. If you have a VPN between A & B, A & C and B & C then all locations can talk on a PRIVATE network. What your saying won't work because you can put rules on the VPN device/Firewall to translate PUBLIC IP's for UDP ports 6000, 9000, 9001 and 30000-30031 on the A network side (because it is one system with static address's), but you can not do it on the B and C networks if you have more that one ITP phone at each site. I suppose you could if you used different UDP ports for each phone but that would be extremly messy or you could setup One-to-One NATs using multiple Public IP's, but why this guy already said he had VPN tunneling set up. Either way merly changing each ITP phone (in programing the MMC you named) to Public w/ firewall will not magically solve this problem. You are flat wrong....

Try going to MMC XXX the ITP set setup and set pub to pub to use MGI this will force a nailed up MGI channel to be used for ITP to ITP by default they try and do a peer to peer. Only draw back is tying up channels for intercom.