ERROR: SIP Profile Registration SIP registration failed: 401 Unauthorized. Verify SIP configuration and connectivity to SIP proxy.

Unanswered Question
Jan 8th, 2014
User Badges:

Hi everyone,

We have two sx20 in my company, one in Korea et another one in Paris.

We use two SPI adresse provided by . Everything was normal until we create DMZ zone for each of the SX20.

know the sx20 can't register to SIP. i have this when i check the SIP configuration and nothing change, the proxy is and the discovey is manual.

SIP is also the protocol default. SIP is enable when i check the networkservice. My user id and password are still active.

This SIP provider offer video and audio and it worked normally before.

so i don't know why i can't register

Can somebody help me please

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Nikita Shrivastava Wed, 01/08/2014 - 08:03
User Badges:


What is the version on the codec and are we using a VCS here?

The codec gives 401 error when trying to register to VCS  over SIP. The reason can be the bug - CSCuj48259.

You can downgrade it to TC5.1.6 as the resolution to this is yet to be there on TC 7.1.X.


amehla Wed, 01/08/2014 - 08:18
User Badges:
  • Silver, 250 points or more

Hi Aida,

please provide the complete xconfig and xstatus SIP to look into this

Martin Koch Wed, 01/08/2014 - 11:15
User Badges:
  • Red, 2250 points or more

As I can not see the bug description I do not want to rule out that you might hit a bug.

But as you mentioned that you changed your network and placed the devices in a DMZ and

further the logs show that you use TCP and not TLS I could also picture that the new used

firewall has some SIP capability (like NAT helper, Application Layer Gateway (ALG), Inspection,

Protocol awareness, short all Layer3 sip "enhancements", ...)

All these things should be disabled.

I would also recommend that you use TLS (encryption) instead of TCP (unencrypted) and would

suggest that you search for a provider which offers VCS-E connectivity (not sure if yours does).

Please remember to rate helpful responses and identify helpful or correct answers.

adiouf001 Mon, 01/13/2014 - 01:47
User Badges:

hello to all

we finally found the problem. When placing telepresence in the DMZ we authorized access only to server while the latter used a different server for authentication.

But I have another problem. when I manage to establish communication, video and sound are cut off after 30 seconds. and I have the "no incoming video" message.

NB: i don't have any VCS or CUCM;


This Discussion