Avaya Communicator not working from different subnet

[TOPBAY]

IPO (Server Edition R9.1) with "Avaya Communicator 2.1" (Softphone software) works good within same subnet.
Trying the communicator from other subnet gives an error on the communicator software, saying "Phone server is not available"
Where is setting to allow softphone access from other subnet?

 

[TOPBAY]

BTW, there is no firewall blocked between 2 network segments, no nat, just routed network.

 

[janni78]

Have you added the IP Route in IP Office? =)

"Trying is the first step to failure..." - Homer

 

[TOPBAY]

I can ping from PC (Communicator software) to IPO.
When I put wrong password, the communicator says wrong user or password, when I put correct password it says "Phone server is not available" so it is communicating and not network issue. Everything works fine within same subnet.. is it license issue?

 

[nnaarrnn]

Have you added the IP Route in IP Office? =)

This.

What does your routing look like in the IPO?
What does your routing table on devices between the IPO and your device with communicator look like?

 

[TOPBAY]

IPO is 192.168.20.203/24 and only pointing to a default gateway 192.168.20.254, no additional route.
PC for Avaya Communicator is 192.168.10.240/24 and only pointing to a default gateway 192.168.10.254, no additional route.

I can ping from PC to IPO.
I can ping from IPO (bcz of Server Edition I can ssh to IPO) to PC.

As long as I can ping each other this is not routing issue.
I have tried Win2012, Win8, and Win7 from 192.168.10.0/24 but no luck.
There is no problems on same subnet 192.168.20.0/24 .

Also tried SSL VPN from outside to access to IPO, I can ping, I can brows https to IPO, I can connect IPO with Manager but not Communicator..

So symptom is everything works fine within same subnet but IPO reject Avaya communicator accessing from other subnet.
Do I need some kind of remote user license?

 

[janni78]

I assume there is a firewall that handles the routing so something is probably blocked there.

Is SIP ALG disabled for example?

"Trying is the first step to failure..." - Homer

 

[nnaarrnn]

You didn't answer my question.

Does your IPO's route have

0.0.0.0 0.0.0.0 Gateway = 192.168.20.254, or is it more like 192.168.20.0 255.255.255.0 Gateway = 192.168.20.254?

 

[derfloh]

Do you see SIP requests in system monitor? Is there a NAT in between these subnets? If yes IPO will treat it as remote extension. Do you get license errors?

 

[amriddle01]

I've seen oddness like this when a customer uses a Sonicwall to route between subnets, they're not supposed to firewall it but they never do what they're told.... it's easy to prove. We put a router we control in to test and it works fine

 

[TOPBAY]

I am using PFSence firewall both ends and VPN between 2 subnets.
All ports are fully opened but PFSence is doing something I guess, such as rewriting sip header or something.
It looks more application layer that PFSence is doing unnecessary thing.