Remote IP Phone over VPN 2

[telteksystems]

Having an issue with a remote IP 9608G over a VPN.

Topology is:

LAN 1 = 10.8.2.x (the phone network we installed originally)
LAN 2 = 10.8.1.x (the second network port on the IP Office system which is connected to our regular office network)
VPN = 10.8.8.x (the VPN segment over at remote office where we are trying to get some VOIP phones to work)

• All phones on 10.8.2.x network (LAN 1) are fine of course
• VOIP phone on 10.8.1.x (LAN 2) works fine for incoming/outgoing line calls, but not internal calls:
o From two phones on LAN 2: both hear fine
o From one on LAN 1 to a ext on LAN 2: only one party can hear, but the other cannot (I think the phone on LAN 1 cannot hear the extension on LAN 2
• VOIP phone over VPN on 10.8.8.x (Remote Office) works fine for incoming/outgoing line calls, but internal calls neither party can hear


So all is well on incoming/outgoing, ringing, directory lookup, – the issue seems to be only with placing internal calls to another extension going across LAN 2 to LAN 1.

Any help would be greatly appreciated!

 

[amriddle01]

You have the gateway(s) wrong on the phones/system, this is a routing issue, the fact it's an IPO is irrelevant at this stage
Turning off DMP will mask this until you fix it

 

[IPOfficeGuru]

I agree, we have found that VoIP sets perform best 90% of the time with Direct Media Path turned off, as long as routing tables are correct. Also - RIP set to listen only on LAN 1 & 2 can keep routing table maintenance low - don't forget to turn on learned RIP Routes to have priority. Also for those of you new to IPO - never directly attached IPO to public static IP - always, always utilize proven firewall.

"Never fear billing a client for services rendered, or they will think your time is worthless"

 

[critchey]

It can NOT be overstated... do NOT plug your IPO to a public IP or you WILL be hacked. Star for you sir.

 

[IPGuru]

VoIP Does NOT perform best with Direct media path turned off as it unnecessarily ties up VCM channels (& also an IP Office Data channels)

it performs best when the customer has valid routing tables between the two networks (which usualy needs to be in place on their router data switches).

Disabling Direct Media Path simply masks a fundamental setup issue with the customers data network.

Contrary to the popular marketing claim VoIP does not "make your telecoms easier because it uses the same network technology your IT dept are already familiar with".

Instead it means your data network now needs to be configured and maintained to a far higher degree (than most small companies can manage).



Do things on the cheap & it will cost you dear

 

[qtelcom]

Will the real IP Guru please stand up!

 

[IPGuru]

I am pretty certain I am the original.

interestingly Tek-tips history seems to disagree, I am sure I have been around since before 2003




Do things on the cheap & it will cost you dear

 

[IPGuru]

Spooky - if tek-tips search function is correct & they have not lost any data then IPOfficeguru would actually be the 1st person I replied to.


Do things on the cheap & it will cost you dear

 

[IPOfficeGuru]

Joined Forums on April 21, 2003.
We have been with Avaya IPO since R1.0.1. Sold our first IP403 in June 2002.
Does anyone remember Mark Massingham ? The first Avaya Product Manager for IPO. We held him accountable for buggy software by buying us 'pints' for the bugs we would find...he was from UK, pints are an acceptable form of currency. Out team made several trips to meet him at his favorite brewery in Red Bank NJ to collect on his tab
How about Norma Hayward in customer care - anyone remember her ? She was terrific !! Many times she would end up giving us free Avaya licenses for sooo many documented tech hours of troubleshooting. This was when code development was still done in the U.K.
We also served on the Business Partner steering committee for IPO product development.
There were many dedicated great people at Avaya during this time period and we worked together as a team. I could personally call Mark and he would always take the call. They treated us as their customer and peers, not like today's environment at Avaya. They think it's a priveledge for us to sell their goods and let's not forget that we work for them.
A few words of wisdom from having been in the telecom/data industry since 1987.
Never expose yourselves as early adopters of anything.
It was a Great learning experience, but came at the high cost of loosing a few customers and jeopardizing our reputation...

"Never fear billing a client for services rendered, or they will think your time is worthless"