Obi200 Stability?

<< < (4/4)

restamp:
Just an observation -- off-topic, but not really worth starting a new thread over -- but from my perspective, if the OBi developers would just allow the changes made from the built-in web server to be fed back to OBiTalk, it would make the OBiTalk interface a lot more palatable.

Time_Lord:
Something obviously changed on the Obi device, the last reload was approx 7 days ago but the device no longer lists the reason code next to the uptime. 

Not that it makes any difference to me that I'm aware of but I noticed that the outgoing calls in the call history now show "+1...." where before the "+" wasn't included, this according to my call logs changed sometime between June 10 and June 15.

The syslog server still shows the reason code:
Jun 21 10:27:48 172.18.19.19  Obi200: SYSTEM REBOOTED (Reason: 3, lifecycle: 637833)

Of course this means Obi may remove the reason code from the syslog output too if they want to hide the fact that they are making changes

Software version hasn't changed, still 3.2.2 Build 5859EX

-TL

Navigation

[0] Message Index

[*] Previous page