sipXcom 25.01.0-rc-002 UI Internal Error

[SipXcom Newbie]

Dear OnRelay Support,

### Expected Behaviour
Creating an "Unmanaged gateway" after having created 4 "SIP trunk"s
succeeds.


### Observed Behaviour
Creating an "Unmanaged gateway" after having created 4 "SIP trunk"s
fails with "An internal error has occurred. Click here to continue."

Performing `# service sipxecs restart` does not fix. Once triggered
UI navigation "Devices > Gateways"
https://fqdn/sipxconfig/gateway/ListGateways.html?state:admin/commserver/EditLocationPage=
errors as above.


### Steps to Reproduce
1. Create 1st "SIP trunk". Populate "Caller ID" and "ITSP Account"
with "Enable" unchecked.
2. Repeat for 2nd-4th trunks
3. Check "Enable" of all trunks
4. Create an "Unmanaged Gateway". Populate "Caller ID" towards the
IP-Authenticated ITSP with "Enable" left checked. Apply.


### Additional Info
Contents of sipxbridge.log contains INFO and WARNING level messages
(including "------- REGISTERING--------", "PROCESSING ITSP ACCOUNTS")
but no errors.

sipxconfig.log contains this:
**********************************************************
Unable to process client request: Unable to read OGNL expression '<parsed OGNL expression>' of $GatewayTable_1@730a0101[gateway/ListGateways/gatewayTable]: ModelSource not set

Session id : node01cmbz9dbn758t1hy33y6gxjcjg1

Exceptions:

org.apache.tapestry.BindingException: Unable to read OGNL expression '<parsed OGNL expression>' of $GatewayTable_1@730a0101[gateway/ListGateways/gatewayTable]: ModelSource not set
binding: ExpressionBinding[gateway/ListGateways/gatewayTable currentRow.model.label]
location: context:/WEB-INF/gateway/GatewayTable.html, line 12

org.apache.hivemind.ApplicationRuntimeException: Unable to read OGNL expression '<parsed OGNL expression>' of $GatewayTable_1@730a0101[gateway/ListGateways/gatewayTable]: ModelSource not set
component: $GatewayTable_1@730a0101[gateway/ListGateways/gatewayTable]
location: Annotation @org.apache.tapestry.annotations.Component(inheritInformalParameters=false, id="gatewayTable", inheritedBindings={}, type="gateway/GatewayTable", copyOf="", bindings={}) of public abstract org.sipfoundry.sipxconfig.components.GatewayTable org.sipfoundry.sipxconfig.site.gateway.ListGateways.getGatewayTable()

java.lang.IllegalStateException: ModelSource not set
org.sipfoundry.sipxconfig.gateway.Gateway.getModel(Gateway.java:209)
$ASTChain_19ef3d34dc1.get($ASTChain_19ef3d34dc1.java)
org.apache.tapestry.services.impl.ExpressionEvaluatorImpl.read(ExpressionEvaluatorImpl.java:141)
$ExpressionEvaluator_19ef3d34c16.read($ExpressionEvaluator_19ef3d34c16.java)
org.apache.tapestry.binding.ExpressionBinding.resolveExpression(ExpressionBinding.java:139)
org.apache.tapestry.binding.ExpressionBinding.getObject(ExpressionBinding.java:125)
org.apache.tapestry.binding.AbstractBinding.getObject(AbstractBinding.java:84)
$Insert_3.getValue($Insert_3.java)


SipXcom Newbie

[Support]

Hello, thanks! Loks like a cousin of the other missing model error that was reported yesterday. The SBC and Phone share a common Device base class, and as mentioned in a different thread Hibernate has become much stricter when enforcing SQL table consistency than it was with older CO7 based versions. We will try to reproduce.

[Donkiss Boss]

Licensed Pharmaceuticals And Psychedelics Online Store
Buy the best Pharmaceuticals And Psychedelics products in our website with safe and guaranteed shipping and delivery Worldwide
Check out our website below if interested in our products.
https://shorturl.at/BvDVf
https://shorturl.at/ITBJW
https://shorturl.at/wCGS4
https://shorturl.at/RnP0b
https://shorturl.at/GTr8Q

[SipXcom Newbie]

What about the digest auth'd "SIP trunks". After enabling them, UI navigation: "DIAGNOSTICS > SIP Trunk Statistics" showed nothing -- no list of digest auth'd trunks and the status of registering on the remote ITSP was displayed (empty list without error). Expected to see them all registered or reason (unreachable, auth failed) etc.

SipXcom Newbie

[Support]

Note we are tracking this issue at: https://github.com/onrelay/sipxecs/issues/58

[SipXcom Newbie]

Thank you for creating.

How should we observe the correct protocol here: Should issues/requests for
help be raised to the community list in the first instance and only created
on Github when validated through discussion etc?

SipXcom Newbie


----- Original Message -----
Date: Tue, 23 Jun 2026 14:21:19 +0200
From: Support <sup...@onrelay.net>
To: SipXcom Newbie <sipxcom-text...@tel.co.uk>
Cc: Sipxco...@googlegroups.com
Subject: Re: sipXcom 25.01.0-rc-002 UI Internal Error

[Support]

Yes, that is a simple process, just report to this user group, and following a discussion we will register confirmed software errors as GitHub issues to keep the issues list tight, avoid duplicates, and not the least ensure the issues list is properly qualified, managed and understood so it doesn’t grow out of control.