SIP REG: extn NULL not created or cm_extn invalid... 4

[ltxn]

Hi,

Today, I was deploying a site with 25 Avaya Communicator softphones, when all of a sudden I got an error:
[pre]Incorrect extension or password[/pre]
All users have valid Power User licenses and are Communicator enabled.
I tried recreating these users and reboot the IP Office. This didn't resolve the issue.

In the System Monitor I see the following error:
[pre]Sip: SIP REG: extn NULL not created or cm_extn invalid...[/pre]

Any ideas, on what's going on?
Thanks!

2016-03-18T19:36:09     821809mS Sip: SipTCPUser 22 incoming f4eae8c0 created local 192.168.0.1:5060 remote 192.168.1.2:64119
2016-03-18T19:36:09     821809mS Sip: SIPPhoneReceiver 24 (f19870cc) tcp created, srcaddress 192.168.1.2, list size 3 
2016-03-18T19:36:09     821824mS SIP Rx: TCP 192.168.1.2:64119 -> 192.168.0.1:5060
                    REGISTER sip:ipo.xxx SIP/2.0
                    From: sip:305@ipo.xxx;tag=-3522127056ec4a9a57a097f8_F305192.168.1.2
                    To: sip:305@ipo.xxx
                    Call-ID: 1_b44d2942c43d4557a097ec_R@192.168.1.2
                    CSeq: 1 REGISTER
                    Via: SIP/2.0/TCP 192.168.1.2:64119;branch=z9hG4bK1_b44d29-ead1e4d57a09806_R305
                    Content-Length: 0
                    Max-Forwards: 70
                    Contact: <sip:305@192.168.1.2:64119;transport=tcp>;q=1;expires=900;reg-id=1;+sip.instance="<urn:uuid:da6ab3b9-cec2-5b3d-a588-8574d83b7f17>"
                    Allow: INVITE,CANCEL,BYE,ACK,SUBSCRIBE,NOTIFY,MESSAGE,INFO,PUBLISH,REFER,UPDATE
                    User-Agent: Avaya Flare Engine/2.0.0 (Avaya 2.0 46; Windows NT Server 6.2, 64-bit)
                    Supported: eventlist, replaces, vnd.avaya.ipo
                    
2016-03-18T19:36:09     821826mS Sip: TCP packet known set owner
2016-03-18T19:36:09     821827mS Sip: SIPDialog f4ef6bbc created, dialogs 1 txn_keys 1
2016-03-18T19:36:09     821827mS Sip: SIP REG: 305 reg-id=1
2016-03-18T19:36:09     821827mS Sip: SIP REG: 305 +sip.instance="<urn:uuid:da6ab3b9-cec2-5b3d-a588-8574d83b7f17>"
2016-03-18T19:36:09     821828mS Sip: (f4ef6bbc) SendSIPResponse: REGISTER code 401 SENT TO 192.168.1.2 64119
2016-03-18T19:36:09     821829mS SIP Tx: TCP 192.168.0.1:5060 -> 192.168.1.2:64119
                    SIP/2.0 401 Unauthorized
                    Via: SIP/2.0/TCP 192.168.1.2:64119;branch=z9hG4bK1_b44d29-ead1e4d57a09806_R305
                    From: <sip:305@ipo.xxx>;tag=-3522127056ec4a9a57a097f8_F305192.168.1.2
                    Call-ID: 1_b44d2942c43d4557a097ec_R@192.168.1.2
                    CSeq: 1 REGISTER
                    User-Agent: IP Office 9.1.6.0 build 153
                    Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,REFER,NOTIFY,INFO,SUBSCRIBE,REGISTER,PUBLISH
                    [URL unfurl="true"]WWW-Authenticate:[/URL] Digest nonce="4dab454148b9705dbd0b",realm="ipoffice",algorithm=MD5
                    Supported: timer,vnd.avaya.ipo
                    Server: IP Office 9.1.6.0 build 153
                    To: <sip:305@ipo.xxx>;tag=aa8ab8cdc112f6ac
                    Content-Length: 0
                    
2016-03-18T19:36:09     821835mS SIP Rx: TCP 192.168.1.2:64119 -> 192.168.0.1:5060
                    REGISTER sip:ipo.xxx SIP/2.0
                    From: sip:305@ipo.xxx;tag=-3522127056ec4a9a57a097f8_F305192.168.1.2
                    To: sip:305@ipo.xxx
                    Call-ID: 1_b44d2942c43d4557a097ec_R@192.168.1.2
                    CSeq: 2 REGISTER
                    Via: SIP/2.0/TCP 192.168.1.2:64119;branch=z9hG4bK2_b44d384ca58d3757a097de_R305
                    Content-Length: 0
                    Max-Forwards: 70
                    Contact: <sip:305@192.168.1.2:64119;transport=tcp>;q=1;expires=900;reg-id=1;+sip.instance="<urn:uuid:da6ab3b9-cec2-5b3d-a588-8574d83b7f17>"
                    Allow: INVITE,CANCEL,BYE,ACK,SUBSCRIBE,NOTIFY,MESSAGE,INFO,PUBLISH,REFER,UPDATE
                    User-Agent: Avaya Flare Engine/2.0.0 (Avaya 2.0 46; Windows NT Server 6.2, 64-bit)
                    Supported: eventlist, replaces, vnd.avaya.ipo
                    Authorization: Digest username="305",realm="ipoffice",nonce="4dab454148b9705dbd0b",uri="sip:ipo.xxx",response="e958f32f04e4d7ea4d08f61379a32160"
                    
2016-03-18T19:36:09     821838mS Sip: TCP packet known set owner
2016-03-18T19:36:09     821838mS Sip: SIP REG: 305 reg-id=1
2016-03-18T19:36:09     821839mS Sip: SIP REG: 305 +sip.instance="<urn:uuid:da6ab3b9-cec2-5b3d-a588-8574d83b7f17>"
2016-03-18T19:36:09     821839mS Sip: SIP REG: extn NULL not created or cm_extn invalid...
2016-03-18T19:36:09     821840mS Sip: (f4ef6bbc) SendSIPResponse: REGISTER code 403 SENT TO 192.168.1.2 64119
2016-03-18T19:36:09     821840mS SIP Tx: TCP 192.168.0.1:5060 -> 192.168.1.2:64119
                    SIP/2.0 403 Forbidden
                    Via: SIP/2.0/TCP 192.168.1.2:64119;branch=z9hG4bK2_b44d384ca58d3757a097de_R305
                    From: <sip:305@ipo.xxx>;tag=-3522127056ec4a9a57a097f8_F305192.168.1.2
                    Call-ID: 1_b44d2942c43d4557a097ec_R@192.168.1.2
                    CSeq: 2 REGISTER
                    User-Agent: IP Office 9.1.6.0 build 153
                    Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,REFER,NOTIFY,INFO,SUBSCRIBE,REGISTER,PUBLISH
                    Supported: timer,vnd.avaya.ipo
                    Server: IP Office 9.1.6.0 build 153
                    To: <sip:305@ipo.xxx>;tag=3d6087934e378cff
                    Content-Length: 0
                    
2016-03-18T19:36:09     821841mS Sip: SIPDialog f4ef6bbc deleted, dialogs 0 txn_keys 0
2016-03-18T19:36:09     821841mS Sip: SIPPhoneReceiver 24 (f19870cc) destroyed, list size 2
2016-03-18T19:36:09     821841mS Sip: SipTCPUser 22 incoming f4eae8c0 destroyed

 

[budbyrd]

extn NULL not created or cm_extn invalid
Sounds like the extension hasn't been created. Users and extensions are two different things. If auto create isn't on, it won't make them on their own.

Dermis and feline can be divorced by manifold methods.*
*(Disclaimer for all advise given)--'Version Dependent'

 

[ltxn]

It is an Avaya Communicator softphone, though, so the IP Office should automagically create the extension when logging in.

Last week i did an upgrade from R9.0 SP8 to R9.1 SP6 to be able to use the communicator in stead of the IP Office Video Softphone.
This is are the versions of the system at the moment:
IPO: IP500v2 R9.1 SP6
Avaya Communnicator 2.0.3.40

 

[budbyrd]

Communicator is an odd duck. I just recently started playing with it. Soft phone used to create random extensions in the IPO if you hadn't built one. I deleted the one it had created for soft phone, and logged in with communicator for that extension, and it let me in with out creating an extension.
Monitor trace~~
12:20:11 945117218mS PRN: Created simultaneous sip extension f179a8dc extn number 451
12:20:11 945117218mS Sip: SIP REG: CreateSimultExtn for Flare 451

Did a lot of testing, found a lot of ways to make it not work, just none of them matched what your trace shows.
Though I am seeing differences. Make sure your SIP registrar is enabled on that LAN port. Mine has 'SIP Reg/Opt Rx: phone' on the line that yours has SIP Rx: TCP.

Don't know if any of that helps.


Dermis and feline can be divorced by manifold methods.*
*(Disclaimer for all advise given)--'Version Dependent'

 

[ltxn]

Hi,

I ended up by recreating the configuration and defaulting the IP Office.
Now all Communicators register fine.

I guess something got corrupted during the upgrade.

Thanks for your input bubyrd!

 

[MrTechnical]

I know you resolved this by defaulting but I had this same issue and wanted to share my findings.
I found that someone enabled block forwarding in the user rights the users were a member of, This will cause the issue you are describing.
Disable it and you will be good to go