UI fails to load after phone config

5 views
Skip to first unread message

J.T. D

unread,
Jun 22, 2026, 12:57:17 PM (2 days ago) Jun 22
to sipxcom-users
25.01 update 6, brand new/reset instance (cleared mongo dir and did --reset-all.)

Once UI came up with page to reset admin password, I got an error that was temporary (reloaded UI page and was then able to log in.)

I added new phones, checking the box to "create another phone after this one" and added two more.  On the last phone, I unchecked the box.  Saved.  Got the red "internal error" message.  Couldn't get back into UI (would get the login screen, log in, but then immediately the internal error message.)

I restarted the services (both restart and a full reboot.)  Now getting a 503 service unavailable when trying to open the UI (no login window.)

Reviewing sipxconfig.log, I see two java faults: 

"2026-06-22T16:40:01.402000Z":382:JAVA:DEBUG:sip-obs.jtdavies.internal:main:00000000:SQL:"select g1_0.phone_id,g1_1.group_id,g1_1.branch_id,g1_1.description,g1_1.name,g1_1.resource,g1_1.weight from phone_group g1_0 join group_storage g1_1 on g1_1.group_id=g1_0.group_id where g1_0.phone_id=?"
2026-06-22 09:40:01.403:ERROR:osss.IndexManagerImpl:main: Error during indexing
java.lang.IllegalStateException: Model ID not set

(Is this related to recent patch for "Fixed indexing issues"?)


And then I see: 

2026-06-22 09:40:01.515:WARN :oeje10w.WebAppContext:main: Failed startup of context oeje10w.WebAppContext@6778aea6{sipXconfig-web,/sipxconfig,b=file:///var/sipxdata/tmp/sipxconfig/webapp/,a=AVAILABLE,h=oeje10s.SessionHandler@7ff35a3f{STARTED}}{/usr/share/java/sipXecs/sipXconfig/sipxconfig.war}
org.hibernate.AssertionFailure: collection owner not associated with session: org.sipfoundry.sipxconfig.phone.Phone.lines

Any thoughts?

OnRelay Support

unread,
Jun 22, 2026, 1:27:51 PM (2 days ago) Jun 22
to J.T. D, sipxcom-users
Hello, it may indirectly related since previously reindexing did not always trigger after a save, but the root cause there is that model ID is missing from a phone definition triggering a java exception. 

Hibernate has gotten stricter with accepting empty fields etc, and should be a simple fix.

--
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/f2b16dde-ad95-49d9-ae04-6905f81db7d6n%40googlegroups.com.

Support

unread,
Jun 23, 2026, 5:34:27 AM (20 hours ago) Jun 23
to J.T. D, sipxcom-users
Hello, thanks again for sharing this. We will try to incorporate a fix in update 7 if you can help us reproduce. Potentially one of the phone xml bean definitions has an error. What exact phone model were you trying to add? 

Donkiss Boss

unread,
Jun 23, 2026, 6:38:51 AM (19 hours ago) Jun 23
to sipxcom-users

J.T. D

unread,
Jun 23, 2026, 8:06:31 AM (17 hours ago) Jun 23
to sipxcom-users
Absolutely!  Polycom VVX 450.

Support

unread,
Jun 23, 2026, 8:09:36 AM (17 hours ago) Jun 23
to J.T. D, sipxcom-users
Reply all
Reply to author
Forward
0 new messages