Can't register Workplace for Windows on IPO Server R12.1

[AlexeyM]

I haven't set up IP Office for many years.
New R12.1 system. Can't register Workplace for Windows 3.38. J129 under the same number registers normally. The user has a Power User profile specified in the settings. The "Allowed SIP UA" setting was set to "Allow All". To configure Wokplace, the auto-generated 46xxsettings.txt was used, with which J129 registers perfectly. I want to register Workplace in the simultaneous registration mode, but I can not register at all. There are enough Power User licenses.

15:56:20    2378680mS SIP Rx: TCP 172.20.0.94:63916 -> 172.20.0.230:5060
                    REGISTER sip:example.com SIP/2.0
                    From: <sip:1111@example.com>;tag=698bedfb-554d-433b-8393-6f72d4182706
                    To: <sip:1111@example.com>
                    Call-ID: f789ad6f-b6a4-4972-a94f-0e8cbca7ea61
                    CSeq: 1 REGISTER
                    Max-Forwards: 70
                    Via: SIP/2.0/TCP 172.20.0.94:63916;branch=z9hG4bKf9e1e787-dd5c-4195-9467-a3e08c39f8d6
                    Supported: eventlist,outbound,replaces,vnd.avaya.ipo
                    Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,MESSAGE,REFER,INFO,PUBLISH,UPDATE
                    User-Agent: Avaya Communicator/3.0 (3.38.1.10.24; Avaya CSDK; Microsoft Windows NT 10.0.19045.0)
                    Contact: <sip:1111@172.20.0.94:63916;transport=tcp>;q=1;expires=3600;+avaya.model="acw";+sip.instance="<urn:uuid:86689189-caad-4323-bcfd-46ebc1adcbe0>";reg-id=1;+av.sip.iptolerance;+av.sip.sig=4;+av.sip.max-sim-reg=1;+av.stir-shaken
                    Content-Length:     0

 15:56:20    2378680mS Sip: TCP packet known set owner
 15:56:20    2378680mS Sip: SIPDialog 800109a0 created, dialogs 1 txn_keys 1 video 1 presentation 1 camera 1 unsupp audio 0
 15:56:20    2378680mS Sip: (800109a0) SetUnIntTransactionCondition to UnInt_None
 15:56:20    2378680mS Sip: SIP REG: 1111 +sip.instance="<urn:uuid:86689189-caad-4323-bcfd-46ebc1adcbe0>"
 15:56:20    2378680mS Sip: SIP REG: 1111 reg-id=1
 15:56:20    2378680mS Sip: ProcessNewRegistrationRequest name <> extn <1111> cfg_extn 0 cfg_user bc0bebf0
 15:56:20    2378681mS Sip: ... is_flare 0 (centr 0) is_oneXmobile 0 is_XMSI 0 is_WebRTC 0 equinox_softphone 1 equinox_mobile 0 csdk_softphone 0 csdk_mobile 0  is_uc_server 0 IsSimultaneousClient 1
 15:56:20    2378681mS Sip: (800109a0) SendSIPResponse: REGISTER code 401 SENT TO 172.20.0.94 63916
 15:56:20    2378681mS SIP Tx: TCP 172.20.0.230:5060 -> 172.20.0.94:63916
                    SIP/2.0 401 Unauthorized
                    Via: SIP/2.0/TCP 172.20.0.94:63916;branch=z9hG4bKf9e1e787-dd5c-4195-9467-a3e08c39f8d6
                    From: <sip:1111@example.com>;tag=698bedfb-554d-433b-8393-6f72d4182706
                    Call-ID: f789ad6f-b6a4-4972-a94f-0e8cbca7ea61
                    CSeq: 1 REGISTER
                    User-Agent: IP Office 12.1.0.0.0 build 80
                    Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,REFER,NOTIFY,INFO,SUBSCRIBE,REGISTER,PUBLISH
                    WWW-Authenticate: Digest nonce="66bd90cae9030bc50451",realm="ipoffice",algorithm=MD5
                    Supported: vnd.avaya.ipo
                    Server: IP Office 12.1.0.0.0 build 80
                    To: <sip:1111@example.com>;tag=213b7fe7d81b7695
                    Content-Length: 0
                    
 15:56:20    2378684mS SIP Rx: TCP 172.20.0.94:63916 -> 172.20.0.230:5060
                    REGISTER sip:example.com SIP/2.0
                    From: <sip:1111@example.com>;tag=698bedfb-554d-433b-8393-6f72d4182706
                    To: <sip:1111@example.com>
                    Call-ID: f789ad6f-b6a4-4972-a94f-0e8cbca7ea61
                    CSeq: 2 REGISTER
                    Max-Forwards: 70
                    Via: SIP/2.0/TCP 172.20.0.94:63916;branch=z9hG4bKe66281f6-7d98-41b2-9783-b900517cb31f
                    Supported: eventlist,outbound,replaces,vnd.avaya.ipo
                    Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,MESSAGE,REFER,INFO,PUBLISH,UPDATE
                    User-Agent: Avaya Communicator/3.0 (3.38.1.10.24; Avaya CSDK; Microsoft Windows NT 10.0.19045.0)
                    Contact: <sip:1111@172.20.0.94:63916;transport=tcp>;q=1;expires=3600;+avaya.model="acw";+sip.instance="<urn:uuid:86689189-caad-4323-bcfd-46ebc1adcbe0>";reg-id=1;+av.sip.iptolerance;+av.sip.sig=4;+av.sip.max-sim-reg=1;+av.stir-shaken
                    Authorization: Digest realm="ipoffice",nonce="66bd90cae9030bc50451",uri="sip:example.com",response="2f2fa45eef2d7ed5245df7a045b50a10",username="1111"
                    Content-Length:     0
 15:56:20    2378684mS Sip: TCP packet known set owner
 15:56:20    2378684mS Sip: SIP REG: 1111 +sip.instance="<urn:uuid:86689189-caad-4323-bcfd-46ebc1adcbe0>"
 15:56:20    2378684mS Sip: SIP REG: 1111 reg-id=1
 15:56:20    2378684mS Sip: ProcessNewRegistrationRequest name <> extn <1111> cfg_extn 0 cfg_user bc0bebf0
 15:56:20    2378684mS Sip: ... is_flare 0 (centr 0) is_oneXmobile 0 is_XMSI 0 is_WebRTC 0 equinox_softphone 1 equinox_mobile 0 csdk_softphone 0 csdk_mobile 0  is_uc_server 0 IsSimultaneousClient 1
 15:56:20    2378684mS Sip: SIP FindUserFromAuthentication, <1111> cfg_user bc0bebf0 from_unregister 0 is_ipo_behind_nat 0 is_phone_behind_nat 0
 15:56:20    2378684mS Sip: authenicateChallengeRtn 0 cfg_user bc0bebf0
 15:56:20    2378685mS Sip: SIP REG: user 1111 authentication failure cause 1
 15:56:20    2378685mS Sip: (800109a0) SendSIPResponse: REGISTER code 403 SENT TO 172.20.0.94 63916

I can't understand what's going on. Tell me if anyone has encountered this.

 

[Menniss]

You cut your trace off a bit soon what we the response to the registration request with Authorization detail?

You are using the right password I assume and not the phone password?

 

[AlexeyM]

Thank you very much for the tip!
I did enter the phone password when registering Workplace.
My mistake. It is unusual to use a different password for a SIP softphone, in Aura the password for all types of SIP devices is the same.
Thanks again for your help!

 

[Menniss]

Good to hear its working, yes the User password is what is used for applications. Workplaces Soft Console etc