• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 885
  • Last Modified:

Avaya extension to extension across WAN not working

Hi everyone,  to start I am not an Avaya expert.

I have a client that has an issue with their Avaya system and extension to extension dialing.

They have two Avaya PBX units; IP500(Site1) and an IP500v2(Site2) on either side of the WAN.  

Site1 is an existing site and has been up for over 3 years.
Site2 is a new installation and addition.

I had recommended and installed Sonicwall TZ205 devices at each site and configured a site to site VPN for each office.  The VPN is up and from all accounts is working properly.

I can ping the Avaya PBX boxes from either side of the WAN.  For that matter, all communication is function correctly across the WAN.

The issue is when trying to initiate extension to extension dialing to phones on either side of the WAN.

The error message that appear on the phones are:

From Site1 they dial ext 510 located at Site2 – After long pause it showed: "Unobtainable 510".

From Site2 they dial ext 420 located at Site1: "Incompatible 420".

Here is the interesting part, their Avaya tech says this is because the firewall is dropping the Avaya communications between sites.

I totally disagree as the VPN is a trusted link and I have allowed all traffic between the two sites over VPN.

Does any one have any thoughts on this issue?
0
nappy_d
Asked:
nappy_d
  • 2
  • 2
1 Solution
 
Blue Street TechLast KnightsCommented:
Hi nappy_d,

I won't speak to the Avaya side because that is not my forte either.

When you say,
Here is the interesting part, their Avaya tech says this is because the firewall is dropping the Avaya communications between sites.

I totally disagree as the VPN is a trusted link and I have allowed all traffic between the two sites over VPN.
To rule out the firewall as playing a part in this...on the SonicWALL, go to Log > Categories and make sure Log is selected so that all categories will be logged.

Also, do a Packet Capture to see what is happening to the packets. Please post results.

Let me know how it goes!
0
 
nappy_dThere are a 1000 ways to skin the technology cat.Author Commented:
Thanks. I've been on the phone with Sonicwall and we see no proof of VOIP traffic being dropped. we've actually done packet tracing between the two PBX boxes' IP.

I found this doc that shows it is a supported connectivity solution. https://devconnect.avaya.com/public/download/dyn/SonicWall-IPO.pdf. Their Avaya tech hasn't even as much provided possible ports their PBX requires to be open for inter device communication.

I'm really hoping an Avaya tech is out here and can lend some input.
0
 
Blue Street TechLast KnightsCommented:
Glad to hear you have it buttoned up on the network side. I'm not a phone Expert so I'm making a call for more Experts (hopefully Avaya ones!) to look at this question.
0
 
nappy_dThere are a 1000 ways to skin the technology cat.Author Commented:
No experts with VOIP experience has responded :(
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

NEW Internet Security Report Now Available!

WatchGuard’s Threat Lab is a group of dedicated threat researchers committed to helping you stay ahead of the bad guys by providing in-depth analysis of the top security threats to your network.  Check out this quarters report on the threats that shook the industry in Q4 2017.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now