Are you using the same gateway for both inbound and outbound PSTN calls ?
1) For inbound calls , the device-level configuration or the corresponding Call Classification service parameter value determines the offnet or onnet value. So seem like it was seeing this as onnet and you can transfer to an offnet when someone calls you (onnet <--> offnet)
2) For outbound calls , the Call Classification setting in the Route Pattern Configuration window determines the offnet or onnet value and the Call Classification value in the Route Pattern Configuration window overrides the device-level configuration or the corresponding value of the Call Classification service parameter. But if you are able to get this working by changing the device level (H323) setting to onnet , seems like this device setting is overriding the setting at the route pattern level.
So do you have "Allow Device Override" parameter checked ?
3) There are 2 service parameters that are related to onNet/offNet operations. One is the "Block offNet to offNet transfer" setting. The other is "Call Classification" within "Clusterwide Parameter (Device General)", if you don't have anything on the device it applies this. So for outbound calls you can set the offnet setting at the route pattern level and leave device override unchecked, regardless the transfer shouldn't be blocked by cucm if the service parameter is set to false. So during offhours or on your lab cucm cluster you can try retstarting the CCM service to make sure that this service parameter setting has taken in to effect.
Before this you might want to pull traces and check the call clasifcation and blocked reasons and confirm if this SP value is being ignored.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.