RESOLVED ! Unable to dial out of PSTN line from a remote Obi throuh AA
Obitalk:
Another symptom I have noticed is that once the call fails to connect through the PSTN line, I'm unable to access the remote Obi web interface for 5-10 mins. Thanks
RonR:
Is there anyone there who can watch it and try to use it locally while it's in that state. It would be interesting to know if it's rebooting after 5 - 10 minutes and that's what brings it back to life.
Obitalk:
Obisupport,
I can confirm that both parties can hear audio and the call is ok when dialling **9 to the remote Obi.
Thanks
Obitalk:
RonR
I think you are on the right track. I think the remote Obi rebooted after the PSTN called failed.
See below:
HardwareVersion 2.8
SoftwareVersion 1.1.0 (Build: 1892)
SystemTime 05:47:15 01/-40176/2010, Monday
UpTime 0 Days 0:17:15 (6)
Uptime of 17mins. I couldn't access it for approximately 15mins.
Thanks
RonR:
Quote from: Obitalk on March 16, 2011, 06:04:32 am
HardwareVersion 2.8
SoftwareVersion 1.1.0 (Build: 1892)
SystemTime 05:47:15 01/-40176/2010, Monday
UpTime 0 Days 0:17:15 (6)
The Reboot Reason Code is suspicious looking, especially if this is a reproducible scenario:
6: New Profile Invoked AND Profile URL Changed
I believe that Reboot Reason Code would normally mean the OBi rebooted because it just received new provisioning info (but it could also be meaningless if the OBi rebooted because of an unexpected software malfunction).
I would suggest trying several more calls and observing whether each of them show the same Reboot Reason Code. Then I would disable Auto Provisioning and try several more calls to see if the results change.
It's possible your calls through the Auto Attendant aren't happening because they're crashing the OBi for some reason. You need to collect more data and symptoms in order to narrow down what's really occurring.
Navigation
[0] Message Index
[#] Next page
[*] Previous page