Obi110 - Crashes over night
Rick:
Have you read the posts re: changing to Full Duplex?
http://www.obitalk.com/forum/index.php?topic=2642.0;topicseen
timpea:
Yea, I changed it to full duplex at the end of last week. It had crashed again this morning, I have setup a syslog, left it at level 7, I will leave it running and see what it says next time it happens.
timpea:
Ok, it appears that the Obi110 has just semi crashed now, I am not able to access it through its IP address, I just tried to make a call out, 1st time it didn't do anything, 2nd time it rang the phone I was ringing, but I couldn't hear anything through my VOIP phone.
Here is the log from around this time:
Oct 3 16:41:26 192.168.1.248 [DAA]: POLARITY REVERSAL (51 V)
Oct 3 16:41:26 192.168.1.248 : [0]DAA PolRev
Oct 3 16:41:27 192.168.1.248 ------ caller id (pcm_id: 1) received! ------------
Oct 3 16:41:27 192.168.1.248 : [0]DAA CND 10031641,01623-421202,,^A,,
Oct 3 16:41:28: --- last message repeated 1 time ---
Oct 3 16:41:28 192.168.1.248 [DAA]: FXO ring on
Oct 3 16:41:28 192.168.1.248 : [0]Ring On
Oct 3 16:41:28 192.168.1.248 FXO: NewTermState:ringing
Oct 3 16:41:28 192.168.1.248 fxo: cp proceeding
Oct 3 16:41:35 192.168.1.248 RTP: DtmfTxMtd:1(1),0
Oct 3 16:41:35 192.168.1.248 fxo: cp answered
Oct 3 16:41:35 192.168.1.248 [DAA]: FXO OFFHOOK
Oct 3 16:41:35 192.168.1.248 [DAA]: detecting disconnect tone, reinit: 0
Oct 3 16:41:35 192.168.1.248 FXO: NewTermState:offhook
Oct 3 16:41:35 192.168.1.248 FXO: Stop Tone
Oct 3 16:41:35 192.168.1.248 RTP: Start->c0a801f9:19170(80);0;0;0:0:0;0(58)
Oct 3 16:41:35 192.168.1.248 : [DAA] FXO ring off
Oct 3 16:41:36 192.168.1.248 [DAA]: POLARITY REVERSAL (-8 V)
Oct 3 16:41:36 192.168.1.248 : [0]DAA PolRev
Oct 3 16:44:36 192.168.1.248 [DAA]: FXO ONHOOK MONITOR
Oct 3 16:44:36 192.168.1.248 FXO: NewTermState:onhook
Oct 3 16:44:36 192.168.1.248 RTP: Del Channel
Oct 3 16:44:36 192.168.1.248 [JB] call overall status --
pee]: 192.168.1.249:19170,\nlocal: 192.168.1.248:16836,\npkt_tx: 9058,\npkt_rx: 9044,\nbytes_tx: 1557976,\nbytes_rx: 1555568,\nclk_diff: 193 PPM,\npkt_in_jb: 0,\npkt_ooo: 0,\npkt_lost: 0,\npkt_late: 0,\npkt_loss_rate: 0 %,\npkt_drop_rate: 0 %,\njb_len: 130 ms,\ncurr_rcvd_jitter: 2 ms,\nrcvd_digits: 0,\nunderruns: 0,\noverruns: 0,\nseq_num_broken: 0,\npkt_interp: 7,\nskew_comp: 0 ms,
Oct 3 17:13:35 192.168.1.248 TCP: Broken Connection(HTTPD) 13 -257
Oct 3 17:17:17 192.168.1.248 FXO: make new call
Oct 3 17:17:17 192.168.1.248 [DAA]: FXO OFFHOOK
Oct 3 17:17:17 192.168.1.248 [DAA]: detecting disconnect tone, reinit: 0
Oct 3 17:17:17 192.168.1.248 FXO: NewTermState:offhook
Oct 3 17:17:17 192.168.1.248 [DAA]: FXO ONHOOK MONITOR
Oct 3 17:17:17 192.168.1.248 FXO: NewTermState:onhook
Oct 3 17:17:17 192.168.1.248 RTP: Del Channel
timpea:
I am still struggling with this, it has crashed again last night, network light flashing fast.
The last thing in my log is from after a missed call and it going back into onhook monitor:
Oct 4 17:50:04 192.168.1.248 [DAA]: FXO ring off
Oct 4 17:50:04 192.168.1.248 : [0]Ring Off
Oct 4 17:50:04 192.168.1.248 FXO: NewTermState:onhook
Oct 4 17:50:04 192.168.1.248 : FXO tell cc end-call
Oct 4 17:50:04 192.168.1.248 RTP: Del Channel
Oct 4 17:50:04 192.168.1.248 [DAA]: FXO ONHOOK MONITOR
I have now turned X_SipDebugOption to Log All messages, see if that helps.
Will I get more logged info if I change the log level?
CoalMinerRetired:
You can turn on SIP logging. However, I think the better approach if you cannot see anything obvious is to contact Obi support saying it crashes etc., and inform then you have an overnight syslog if they need it.
Navigation
[0] Message Index
[#] Next page
[*] Previous page