Vantage K175 "SIP Login Failure" - "Empty SIP Controller List"

[dsm600rr]

Hello all,

So I finally got the phone to grab and update its firmware to "K1xx_SIP-R2_2_0_3_7053.tar" (Latest Firmware Version from Avaya)

When viewing the Auto Generated K1xxSupgrade.txt from the IPO I noticed it was not showing the correct Firmware Versions or Dialer Application

## IPOFFICE/11.0.4.3.0 build 3 172.30.20.1 AUTOGENERATED
IF $MODEL4 SEQ K175 GOTO K165_K175_SW
IF $MODEL4 SEQ K165 GOTO K165_K175_SW
IF $MODEL4 SEQ K155 GOTO K155_SW
GOTO END
# K165_K175_SW
SET APPNAME K1xx_SIP-R2_1_0_0_6028.tar
GOTO GETSET
# K155_SW
SET APPNAME K1xx_SIP-R2_1_0_0_6528.tar
GOTO GETSET
# GETSET
SET ACTIVE_CSDK_BASED_PHONE_APP "com.avaya.android.flare"
SET PUSH_APPLICATION "equinox-gaRelease-3.5.5.39.FA-RELEASE11-BUILD.20.apk"
GET 46xxsettings.txt
# END

I copied the auto generated file and modified it as such:

## IPOFFICE/11.0.4.3.0 build 3 172.30.20.1

SET ADMIN_PASSWORD 2468

IF $MODEL4 SEQ K175 GOTO K165_K175_SW
IF $MODEL4 SEQ K165 GOTO K165_K175_SW
IF $MODEL4 SEQ K155 GOTO K155_SW
GOTO END

# K165_K175_SW
SET APPNAME K1xx_SIP-R2_2_0_3_7053.tar
GOTO GETAPP

# K155_SW
SET APPNAME K1xx_SIP-R2_2_0_3_7053.tar
GOTO GETAPP

# GETAPP
IF $GROUP SEQ 0 GOTO BASIC_CONNECT
IF $GROUP SEQ 1 GOTO EQUINOX
GOTO GETSET

# BASIC_CONNECT
SET ACTIVE_CSDK_BASED_PHONE_APP "com.avaya.android.vantage.basic"
SET PUSH_APPLICATION VantageConnect_armeabi-v7a_2.2.0.3.0108_220420_643534b.apk
GOTO GETSET

# EQUINOX
SET ACTIVE_CSDK_BASED_PHONE_APP "com.avaya.android.flare"
SET PUSH_APPLICATION workplace-gaRelease-3.8.0.125.FA-RELEASE-BUILD.52.apk
GOTO GETSET

# GETSET
GET 46xxsettings.txt
# END

After doing so I noticed the Phones Background changed to show the 3 people sitting around a desk and the Avaya Vantage Login.

For my "Username" I entered in my Extension

And for the password I entered in the Extensions Password

I then get the error: "Empty SIP Controller List"

What is this error?

ACSS

 

[derfloh]

You should be able to check the config values within the K175 settings. What does it show as SIP server, port and protocol?

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

 

[dsm600rr]

derfloh: Thats kind of the strange part to me. We created ix.pfcommunications.com as a FQDN Sub-Domain for testing with IX Workplace (Which I still have not got working outside of our LAN). I am not sure why the phone is pulling that.

SIP Domain: pfcommunications.com
SIP Proxy Settings: ix.pfcommunications.com / Port=5060; Transport=tcp

ACSS

 

[dsm600rr]

ACSS

 

[bahmonkeys]

I tested the 2 different domains you have and that will not work. Can you put them on the same public IP Address where the PBX is located.
Get this working on your IX Workplace first before trying on the Vantage as it will be a step or 2 easier with setting up SIP.
Use ports 5061 and TLS for remote workers externally.

 

[dsm600rr]

bahmonkeys: This phone is internal, on the same LAN as the PBX.

PBX: 172.30.20.1
Application Server / VM Pro: 172.30.20.2
Vantage Phone: DHCP - 172.30.20.106

I am only looking to get this working internally.

The Vantage phone pulled: pfcommunications.com / ix.pfcommunications.com / Port=5060; Transport=tcp from the autogenerated 46xxsettings file I am assuming.

ACSS

 

[bahmonkeys]

Externally these 2 domains pfcommunications.com / ix.pfcommunications.com point to 2 different public ip addresses. The issue is a certificate issue. You will have to create a new identity certificate map the all the DNS domains, Public IP address, Local PBX address.

You do not actually need a different registrar domain name if you are only using 1 PBX.

I recommend keeping the same domain name, create an A record internally and Externally to the PBX and Public IP. Turn on TLS 5061 and do not accept any external access from port 5060.

Get this working on the IX Workplace first then you can try the Vantage setup.

 

[dsm600rr]

We created ix.pfcommunications.com that points to our Firewall (Same IP Address if I do an ipchicken.com)

This is the area I fall short in - which is why I put it on the back burner for some time. IX Workplace Works perfectly internally, and auto configures with an email address and password as it should.

https://dnschecker.org/#A/ix.pfcommunications.com

PBX Programming:

I believe we have an External A Record set up properly and pointing to the external IP Address of our Firewall, we do not have an Internal A Record set up yet. I would assume that would need to point to the PBX?

From Zang:

Is it an issues that pfcommunications.com and ix.pfcommunications.com do not point to the same public IP? I have no idea what IP pfcommunications.com is point to. I do know ix.pfcommunications.com points to my firewall.

Any assistance would be greatly appreciated to get the IX Workplace working from the outside as well - as I have been working on it forever.

I have yet to create any certificates, so assistance with that would also be appreciated.

"Turn on TLS 5061 and do not accept any external access from port 5060" - Under LAN > VoIP are you saying disable UDP 5060 and TCP 5060 and only check (enable) TLS 5061?

Thank you!

ACSS

 

[derfloh]

SET SIP_CONTROLLER_LIST ix.pfcommunications.com:5060;transport=tcp
SET CONFERENCE_FACTORY_URI "ConfServer@pfcommunications.com"
SET PSTN_VM_NUM "VM.user@pfcommunications.com"
SET SETTINGS_FILE_URL "

https://ix.pfcommunications.com:411/46xxsettings.t..."

SET FQDN_IP_MAP "ix.pfcommunications.com=172.30.20.1"

It's configured as SIP FQDN in the LAN interface configuration.

You have to make sure that the DNS Server used by the phone resolves that FQDN against 172.30.20.1

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

 

[derfloh]

Within the internal network you have to use an internal DNS server. Not the google DNS.

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

 

[bahmonkeys]

Use this domain as your registrar and domain: ix.pfcommunications.com.

Just remember this is a public forum and sharing your DNS name can point straight to your pbx which is a security issue. Close port 5060 on your firewall and only have it opened for your Sip provider. You can leave port 5060 enabled on the PBX and yes enable TLS port 5061. Only use port 5061 for sip clients as it's encrypted.

No internal DNS A record setup for ix.pfcommunications.com to point to your PBX is your issue.

@derfloh
You have resolved the exact same issue for a lot of people here.

 

[derfloh]

@bahmonkeys


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

 

[dsm600rr]

bahmonkeys: When I updated the following, all of my J179's displayed "Login". When I tried to log them back in i got "Invalid name or password" (I tried both the password under "Extensions" as well as the password I set after the initial login)

So I defaulted my J179's and when i attempted to log in it hung at "Verifying login credentials" for a few seconds and then "Acquiring service"

I then unchecked "TLS", Rebooted the PBX and defaulted the J179 again - and I was able to log the phones back in. Any ideas why this would of happened?

Also, should I update this from pfcommunications.com to ix.pfcommunications.com?

What about the Verified Domain on my zang account?

ACSS

 

[derfloh]

I personally would leave the config as it was and just use an internal DNS server

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

 

[bahmonkeys]

Yes updating the DNS name will cause the IPO to generate a new certificate. This will cause all sip devices to show acquiring service. You will have to default them to pull the new certificate.
Double check your DNS server IP address on the ipo, make sure that it is pointed to your DC or whatever internal IP address is handling your DNS resolutions.

For now don't worry about Zang this can be updated when you get TLS working.

 

[dsm600rr]

Thanks gents.

So should I leave my SIP Domain Name and SIP Registrar FQDN both at: ix.pfcommunications.com?

So my SIP Trunk, DHCP Server (PBX), SIP Domain Name, SIP Registrar FQDN, IP Route, VM Pro and everything phone related is on the PBX's WAN which is 172.30.20.XXX, the Voice VLAN

The LAN is on my Data Network for local access from local PC's, which is 192.168.1.XXX is on the Data VLAN

Can I set the DNS on the PBX from the Data VLAN (Where I have a internal DNS Server)?



ACSS