golfdoctor
Technical User
The saga continues...
If both nodes are running different versions of software would the Alternate NRS fail to recognize the actual status/settings associated with the Primary NRS configuration?
Have basically got everything up and running utilizing H323 trunking between node A(main) and node B(remote). I have a signalling server located at each node(site). The main node has been configured as the Primary GK containing the Primary NRS while node B was setup as the Alternate GK containing the Alternate NRS. Node A is running Succession 4.0 while node B is running Succession 4.5 software. While checking the configuration of the Alternate NRS settings configured in Node B I noticed the system does not recognize the status of the actual NRS configuration. (status unknown in NRS Overview) I understand that the different software versions prevents automatic DB synchronization, however is this also a "cause and effect" what I am seeing? I believe and hope it is as this would make sense because when I access the main NRS all of the status and system settings seem AOK.
As a precaution I have duplicated and manually entered the DB configuration in the Standby NRS hoping this should suffice in the event of the main NRS failure and until I can upgrade to 4.5 at the main site?
Am I out to lunch or in the ball game? Any thoughts would be helpful as I think I am on the home stretch...
If both nodes are running different versions of software would the Alternate NRS fail to recognize the actual status/settings associated with the Primary NRS configuration?
Have basically got everything up and running utilizing H323 trunking between node A(main) and node B(remote). I have a signalling server located at each node(site). The main node has been configured as the Primary GK containing the Primary NRS while node B was setup as the Alternate GK containing the Alternate NRS. Node A is running Succession 4.0 while node B is running Succession 4.5 software. While checking the configuration of the Alternate NRS settings configured in Node B I noticed the system does not recognize the status of the actual NRS configuration. (status unknown in NRS Overview) I understand that the different software versions prevents automatic DB synchronization, however is this also a "cause and effect" what I am seeing? I believe and hope it is as this would make sense because when I access the main NRS all of the status and system settings seem AOK.
As a precaution I have duplicated and manually entered the DB configuration in the Standby NRS hoping this should suffice in the event of the main NRS failure and until I can upgrade to 4.5 at the main site?
Am I out to lunch or in the ball game? Any thoughts would be helpful as I think I am on the home stretch...