IX workplace for IP office User not able to login 2

[Bailly34]

Hello all,

I have set up IX workplace to connect directly to the IP office with a FQDN <avaya.Domainname.com>. The app seems to connect, but when I enter the user credentials it gives me a message that the credentials are wrong. I have programmed the IPO per IX docs. Also, changed remote TCP/UDP port to 7070. Is their any extra work I need to be done to the IPO? I have seen adding /46xxsetting.txt to the domain. Any help would be great.

Oscar
Business Linxs
Miami, Florida

 

[ipohead]

From my quick tests

user = extension number
pwd = not the phone password but user-telephony-supervisor settings-login code

 

[janni78]

The password is the one in the main user tab, not login code.

You should not edit the 46xxsettings file, the auto-generated will work just fine.
Also you should use TLS and not TCP, especially if connecting from remote locations.

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

 

[Bailly34]

This is what I get from the app: Invalid extension or password

below is what monitor shows.


********** Warning: Logging to Screen Started **********

********** SysMonitor v11.0.4.2.0 build 58 [connected to 10.''''.34 (Coral Gables)] **********

********** SysMonitor v11.0.4.2.0 build 58 [connected to 10.'''.34 (Coral Gables)] **********
57769593mS Sip: SipTCPUser 51 incoming f520addc created local 10.'''.34:7070 remote 10.175.0.1:6895 list size 42

********** SysMonitor v11.0.4.2.0 build 58 [connected to 10.'''.34 (Coral Gables)] **********
57772923mS SIP Rx: TCP 10.1'''.1:6895 -> 10.'''.34:7070


57772923mS SIP Tx: TCP 10.7'''.34:7070 -> 10'''.1:6895

57772924mS SIP Rx: TCP 10.'''.1:6895 -> 10.'''.34:7070
REGISTER sip:av''''al.com SIP/2.0
From: <sip:234@av''''al.com>;tag=9f9a0e22-fb10-456f-bc5d-5b825ceac2cd
To: <sip:234@av''''al.com>
Call-ID: 6b63da11-093c-416e-bb57-f7606f2d3b82
CSeq: 1 REGISTER
Max-Forwards: 70
Via: SIP/2.0/TCP 10.'''.1:40717;branch=z9hG4bK91e21ff2-8a05-471f-84d1-1745637d98d4
Supported: eventlist,outbound,replaces,vnd.avaya.ipo
Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,MESSAGE,REFER,INFO,PUBLISH,UPDATE
User-Agent: Avaya Communicator Android/3.7.4 (FA-RELEASE41-BUILD.2; moto g(6))
Contact: <sip:234@10.'''.1:40717;transport=tcp>;q=1;expires=3600;+sip.instance="<urn:uuid:c3d63bbc-b447-496a-b6de-3edeba7899e2>";reg-id=1;mobility="mobile";+av-altnet="mobile";+av-altaor="786""'1001";+av.sip.iptolerance;+av.sip.
sig=4;avaya-actions="presence.initiate-pubsub, presence.redirect"
Content-Length: 0

57772927mS SIP Reg/Opt Rx: phone
REGISTER sip:ava’'’’al.com SIP/2.0
From: <sip:234@av’''’’al.com>;tag=9f9a0e22-fb10-456f-bc5d-5b825ceac2cd
To: <sip:234@av’'''’al.com>
Call-ID: 6b63da11-093c-416e-bb57-f7606f2d3b82
CSeq: 1 REGISTER
Max-Forwards: 70
Via: SIP/2.0/TCP 100. 10'''.1:40717;branch=z9hG4bK91e21ff2-8a05-471f-84d1-1745637d98d4
Supported: eventlist,outbound,replaces,vnd.avaya.ipo
Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,MESSAGE,REFER,INFO,PUBLISH,UPDATE
User-Agent: Avaya Communicator Android/3.7.4 (FA-RELEASE41-BUILD.2; moto g(6))
Contact: <sip:234@10'''.1:40717;transport=tcp>;q=1;expires=3600;+sip.instance="<urn:uuid:c3d63bbc-b447-496a-b6de-3edeba7899e2>";reg-id=1;mobility="mobile";+av-altnet="mobile";+av-altaor="7865621401";+av.sip.iptolerance;+av.sip.
sig=4;avaya-actions="presence.initiate-pubsub, presence.redirect"
Content-Length: 0

57772928mS Sip: SIPDialog f5508aec created, dialogs 42 txn_keys 1 video 1 presentation 1 camera 1 unsupp audio 0
57772929mS SIP Reg/Opt Tx: phone
SIP/2.0 403 Forbidden
Via: SIP/2.0/TCP 10.''''.61:40717;branch=z9hG4bK91e21ff2-8a05-471f-84d1-1745637d98d4
From: <sip:234@av'''''''al.com>;tag=9f9a0e22-fb10-456f-bc5d-5b825ceac2cd
Call-ID: 6b63da11-093c-416e-bb57-f7606f2d3b82
CSeq: 1 REGISTER
User-Agent: IP Office 11.0.4.2.0 build 58
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,REFER,NOTIFY,INFO,SUBSCRIBE,REGISTER,PUBLISH
Server: IP Office 11.0.4.2.0 build 58
Content-Length: 0
To: <sip:234@av''''al.com>

57772929mS SIP Tx: TCP 10'''''4:7070 -> 10.'''''.1:6895
SIP/2.0 403 Forbidden
Via: SIP/2.0/TCP 100.''''.161:40717;branch=z9hG4bK91e21ff2-8a05-471f-84d1-1745637d98d4
From: <sip:234@av''''al.com>;tag=9f9a0e22-fb10-456f-bc5d-5b825ceac2cd
Call-ID: 6b63da11-093c-416e-bb57-f7606f2d3b82
CSeq: 1 REGISTER
User-Agent: IP Office 11.0.4.2.0 build 58
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,REFER,NOTIFY,INFO,SUBSCRIBE,REGISTER,PUBLISH
Server: IP Office 11.0.4.2.0 build 58
Content-Length: 0
To: <sip:234@av''''al.com>

57772930mS Sip: SIPDialog f5508aec deleted, dialogs 41 txn_keys 0
57772930mS Sip: SipTCPUser 51 incoming f520addc destroyed list size 41

********** Warning: Logging to Screen Stopped **********



Oscar
Business Linxs
Miami, Florida

 

[JazzWizzard]

Port 7070 is the Web Manager's port. I don't know if that could create conflict of something, but perhaps another port should be used.

IX Workplace uses the user name and user password for login.

Also, go on System Status and check System/VoIP Security/Black listed extensions and Quarantined extension to see if your extension is on there.

 

[Bailly34]

Jazz Wizzard thanks for your reply. No quarantined extension. So I should use "User name" (example: BLinxs) instead of "extension number"? Is it case sensitive? Which port do you suggest that will not conflict with IP office?

Oscar
Business Linxs
Miami, Florida

 

[Bailly34]

I tried with user name, but still getting "403 forbidden"

Oscar
Business Linxs
Miami, Florida

 

[JazzWizzard]

What is the type of password you are using for that user?

 

[Bailly34]

I set the password in Extension tab, User tab, and supervisor settings to: 135790. Does it need to be a stronger or longer password?

Oscar
Business Linxs
Miami, Florida

 

[Bailly34]

I made the password more difficult. I tried User name and Extension number with no success.




Oscar
Business Linxs
Miami, Florida

 

[Bailly34]

I'm using Comcast as the provider. Should I make sure they don't have ALG on?

Oscar
Business Linxs
Miami, Florida

 

[janni78]

Have you enabled Remote Worker on the User?


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

 

[JazzWizzard]

I would also change the port back to 5060.

 

[Bailly34]

I changed the port back to 5060. Do you think it would help making LAN 2 the public address?

Oscar
Business Linxs
Miami, Florida

 

[HyTech]

I believe Comcast does block ports on the residential side- it would be worth checking into.

 

[janni78]

You should always try with a WiFi connected on the mobile device first so you don't spend time troubleshooting something the mobile provider blocks.

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

 

[rgunther]

I just got our IX workplace working for our organization. All remote users have VPN access back to our local LAN, so to connect with their IX workplace clients they all use the local IP address. As far as user setup - they have to have either a Office Worker, Teleworker, or Power user license. Then under the license they need to have the "Enable Desktop/Tablet VoIP client" checked. The user will login using there extension number, and the password on the User tab. This cannot be 1234 (learned the hard way), but any other 4-digit user password worked fine for us. Also - You have to have SIP Registrar Enabled under the LAN port you are using. We are not using a Domain Name as everything we do is all connected via local LAN.

 

[Bailly34]

rgunther, thank you. Isn't there a way to do without the VPN connection?

Oscar
Business Linxs
Miami, Florida

 

[rgunther]

Yeah absolutely... however in our setup we never really had any remote workers or the need for remote extensions; so we never exposed our IPO's to the public inet. Now that we have a few temp remote workers; they already need the VPN for access to other local content, so we just kept it local. If we really needed to - we could use a public IP and forward it to our local IP office and then point the IX workplace to the FQDN.

 

[Bailly34]

That's what I'm doing and connecting, but user name and password does not work.

Oscar
Business Linxs
Miami, Florida