Phone not registering

[J.T. D]

25.01u8

Everything else recently found/fixed works beautifully (thank you thank you thank you!,) except for this. 

New install, manually configured (not from backup/restore of older version.)

I configured server features/services identical to my working sipxcom server.

DNS records were updated to point to new sipxcom server.

I manually created new users.  I manually created new phones. I associated user/lines to the phones.  I generated/sent profiles for the server and all phones.

I did a device reset of the phones (Polycom VVX) to clear any previous configuration.

After phone reboot, they do not register.  They do get the provisioning files successfully, but when attempting registering, it fails.  The phone records a generic 480 temporarily not available error.

I see from the sipregistrar.log file:

"2026-07-21T13:17:01.522030Z":1345:AUTH:ERR:**sipxcom server name**l::7fcbecafe640:sipxregistry:"Response auth hash does not match (bad password?) toUri='sip:200@**internal sip domain**' requestUser='200/4825670be793' requestNonce='0c42e2065aa8ee62b0951c94490f201b6a5f714d' uriParam='sip:**internal sip domain**;transport=tcp' passTokenDB='N98whbrqkl67sw' authTypeDB='DIGEST'"

The passTokenDB matches the SIP password on the user.  I've even reset it to a new value and sent profiles.  The log does record this updated token, but no successful registration.

This suggests to me (admittedly I'm reaching a little bit beyond my knowledge) that either the phone generates the wrong hash, or the user record in the database/sipxcom didn't get updated with the new value when a new SIP password was created?

[OnRelay Support]

Does rebuilding the search index resolve it?

--
You received this message because you are subscribed to the Google Groups "sipxcom-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-user...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/sipxcom-users/1d8acec3-fdb9-4d39-87c0-39fb550785a2n%40googlegroups.com.

[J.T. D]

Rebuilt search index by typing in arbitrary values in search box, then clicking 'Rebuild Search Index'.   No change: lines still unregistered and sipregistrar.log shows response auth hash does not match.

I found an alternative procedure to clearing the index (remove files in /var/sipxdata/tmp/index and restart services.)  sipregistrar.log has stopped recording the response auth hash messages (progress!) but is now recording 401 Unauthorized and no registration.  I'll continue troubleshooting, but clearing out the index did appear to fix the immediate symptoms.  Thank you!

[Support]

We don’t have any problems registering auto provisioned Polycoms as well as manually provisioned Brias from here. 

To view this discussion visit https://groups.google.com/d/msgid/sipxcom-users/55ba491f-6dea-4509-9343-a169605e817fn%40googlegroups.com.

[J.T. D]

After some trial and error, I was able to get lines registered.  In the Primary registration server settings, I had to change the transport from the default of TCPOnly to UDPOnly.  TCPpreferred doesn't work for me, either.

[Ivar Plahte]

Albeit we normally use TLS we don’t see any problems registering over TCP here either. Could it be something with your networking environment or setup?

To view this discussion visit https://groups.google.com/d/msgid/sipxcom-users/f8306522-e207-485e-84df-8a10ea12adc6n%40googlegroups.com.