IPO 9.0.12 Extension error when logging in Remote Worker 2

[MightyMrMatt]

Client has a PBX at their call center and wants to use remote workers at other sites over site-to-site VPNs. I've set up a test extension to try this out this set up, but after programming the phone to the call center PBX, after entering the extension and password, I get "Extension Error". Now, these sites do have a local PBX, but since the phone is programmed to look for a different call server, I assume that it should go around the local PBX in search of the call center PBX. Am I correct in this or am I missing something?

 

[Pepp77]

To save lots of back and forth Q&As please can you post

Each subnets network info (ip range, subnet mask, gateway)
Settings exactly as set on phone.
IP routes on remote system

| ACSS SME |

 

[MightyMrMatt]

Certainly.

Call center PBX:
IP range: 10.127.30.X
IP Address: 10.127.30.19
Mask: 255.255.255.0
Gateway: 10.127.30.1
Includes IP route to 10.10.127.0

Local PBX:
IP range: 10.10.127.X
IP Address: 10.10.127.19
Mask: 255.255.255.0
Gateway: 10.10.127.1
Includes IP route to 10.127.30.0

IP Phone (Avaya 5610)
IP Address: 10.10.127.173
Call Server: 10.127.30.19
Mask: 255.255.255.0
Gateway: 10.10.127.1
File server: 10.10.127.89
Network Port: 1719
801.q: Off

Both PBX can ping not only each other, but also other IP addresses on the other networks. Ping times are running under 3ms. There are no filters setup in the VPN, it's a direct and open connection.

 

[critchey]

As stated previously, the gateway on the phone did you point at the local internet gateway or did you point at the VPN gateway. It needs to point at the VPN gateway or it will not hit the VPN.

The truth is just an excuse for lack of imagination.

 

[MightyMrMatt]

Critchey,

Haven't had a chance to make those changes yet; this is just what is int eh phone now. Soon as I get a chance to change those settings, I'll let you know how it goes.

 

[MightyMrMatt]

Changed the gateway to our VPN router, still getting "Discover 10.127.30.19".

 

[critchey]

From system status you can ping the phone's IP from the interface making the connection to the VPN? You manually entered all IPs into the phone so it is no longer getting any DHCP information? Have you tried defaulting the phone and resetting everything up from scratch including statically assigning all IPs?

Otherwise I am out of ideas. IP phones over VPN is usually very simple to setup and get working and I rarely if ever run into issues.

The truth is just an excuse for lack of imagination.

 

[MightyMrMatt]

Yes, I can ping the phone's IP from System Status. I've reset the phone twice before entering the static IP information.

You are right, normally, this is much easier, but this is my nightmare Avaya client. Everything that can go wrong does.

 

[critchey]

I guess you could take the phone onsite and see if it connects. If it does you can start to assume the issue is the VPN connection (maybe H323 transformation or something silly like that is turned on?).

The truth is just an excuse for lack of imagination.

 

[MightyMrMatt]

After doing some investigating, turns out that the client had their co-ax ISP replaced with P2P fiber connections, so no VPNs are employed anymore. This makes it even more puzzling as I have setup phones over P2P without issues in the past.

 

[MightyMrMatt]

The IP routes were changed on the remote PBX after the changeover to P2P. Now that I have the correct info, I can connect the phone to the remote PBX. Thanks for all of your help!

 

[critchey]

Well glad you got it working and thanks for the star.

The truth is just an excuse for lack of imagination.

 

[MightyMrMatt]

You deserve it!

 

[holdmusic34]

Star for posting resolution.

Try to spend the next 10 seconds not thinking about a blue eyed polar bear.

 

[MightyMrMatt]

My first star! Thanks holdmusic34!