Strage VLAN issue with my Avaya PBX

[dsm600rr]

All,

So I have my PBX LAN on the Data VLAN 192.168.1.XXX. The PBX is only on this VLAN to access the PBX from my Office PC's

I have my J179's, SIP Trunk, DHCP Server (IPO) and everything else voice related on this VLAN 172.30.20.XXX

IX Workplace will ONLY connect to the PBX on the Data VLAN - does not connect on the Voice VLAN.

If I unplug the LAN (Data VLAN) We are able to ping all of the phones from the Data VLAN (192.168.1.XXX) however not the PBX at 172.30.20.1

The only IP Route is on the Voice VLAN out 172.30.20.254

Both VLAN's are configured identical aside from the IP Scheme.

Thoughts?

ACSS

 

[derfloh]

Use different SIP FQDN in both interfaces of IPO and let DNS resolve them correctly.

Otherwise you have routing issues.

IP Office remote service
IP Office certificate check
CLI based call blocking
SCN fallback over PSTN

 

[dsm600rr]

derfloh: Can you elaborate a bit?

Is the issue possibly because I do not currently have an internal DNS A-Record pointed to my PBX on the voice VLAN?

ACSS

 

[icet500]

Maybe its a certificate issue as you have TLS enabled on lan2.

 

[dsm600rr]

icet500: I have also tried with TLS unchecked. Same result.

I am having certificate issues too though however. When I generate the Identity Certificate (.p12) and load it to manager I get this error:

I am not entirely sure what certificate it is requesting be placed in the Trusted Certificate Store.

ACSS

 

[icet500]

So what is the error message you get when you try to register from the voice vlan?

 

[janni78]

If you unplug the data VLAN from the IP Office you can't ping the Voice VLAN interface as it will try to send out the answer on the other port.

If you have routing to the 172-network from the data VLAN to the voice VLAN you don't need an IP address from the data VLAN on the IP Office.

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

 

[derfloh]

Oh... A third party CA? IP Office servers don't use intermediate CAs (usually).



IP Office remote service
IP Office certificate check
CLI based call blocking
SCN fallback over PSTN

 

[dsm600rr]

derfloh: All I did was create the Identity Certificate from my Application Server as Below)

I did however update the SAN to unclude both my LAN and WAN (Data / Voice) VLAN's as such:

DNS:ix.pfcommunications.com, IP:172.30.20.1, IP:192.168.1.251, IP:50.245.XXX.XX, URI:sip:ix.pfcommunications.com

I then went to Security Settings > System > Certificates and loaded the (.p12) Exported Identity Certificate to: "Set" > "Import Certificate from file" and loaded the .p12 file (Side note it would not let me add the downloaded .pem file

When I launch the Workplace App on the Data VLAN (as it wont run on the voice VLAN) it never grabs any certificate.

ACSS

 

[dsm600rr]

Side note.

I removed from my voice network the SIP Domain Name and SIP Registrar FQDN as well as TLS and I still cannot get the app to load on the Voice VLAN, only the Data VLAN

Works just fine from my Data VLAN

ACSS

 

[dsm600rr]

Communicator works from my voice VLAN

ACSS

 

[dsm600rr]

Workplace Kind of lets me log in with:

http://172.30.20.1/46xxsettings.txt

(Voice VLAN)

Rather than my email address in which I use on the Data VLAN with no issues however I get Error:

ACSS