Wired Intelligent Edge

We have been getting a lot of droped calls lately on our v3000 nbx. We are running in analog mode no sip phones. I went and got a syslog viewer to monitor in real-time what is going on and here is an sample of the log file that I have been getting. Any ideas as to what any of the errors mean?



2009-09-23 08:36:01 Daemon.Error 10.10.25.2 SEP 23 08:35:57 V3000 nbxLogger: 0923:083557:0211 H3LinkLayer E Got a Pkto TimeOut - Application Should Mark Device 0xe0 0xbb07 0xf729 DOWN ..

2009-09-23 08:37:13 Local1.Error 10.10.25.2 SEP 23 08:37:09 V3000 nbxLogger: 0923:083709:0326 CDR E BillingServer::lPrepareCommonDataBuffer - Invalid duration: answer 0x4aba4eb5 end 0x4aba4ea3

2009-09-23 08:37:18 Daemon.Error 10.10.25.2 SEP 23 08:37:13 V3000 nbxLogger: 0923:083713:0788 H3LinkLayer E Got a Pkto TimeOut - Application Should Mark Device 0xe0 0xbb07 0xf729 DOWN ..

2009-09-23 08:37:19 Local2.Warning 10.10.25.2 SEP 23 08:37:15 V3000 nbxLogger: 0923:083715:0019 Transfer W 153 : OtherParty's extension= 262

2009-09-23 08:38:02 Local2.Warning 10.10.25.2 SEP 23 08:37:57 V3000 nbxLogger: 0923:083757:0846 Transfer W 131 : OtherParty's extension= 469

2009-09-23 08:38:21 Local2.Warning 10.10.25.2 SEP 23 08:38:16 V3000 nbxLogger: 0923:083816:0615 Transfer W 131 : InitTransfer::waitForSessionsToBeMerged::connected virtualAns is true

2009-09-23 08:38:47 Local3.Error 10.10.25.2 SEP 23 08:38:43 V3000 nbxLogger: 0923:083843:0057 DIL E CCMMessage.send():: Error writing TCP socket 90

2009-09-23 08:38:47 Local3.Error 10.10.25.2 SEP 23 08:38:43 V3000 nbxLogger: 0923:083843:0076 DIL E CCMMessage.send():: Error writing TCP socket 90

2009-09-23 08:38:50 Local3.Error 10.10.25.2 SEP 23 08:38:45 V3000 nbxLogger: 0923:083845:0673 DIL E CCMMessage.send():: Error writing TCP socket 90

2009-09-23 08:38:50 Local3.Error 10.10.25.2 SEP 23 08:38:46 V3000 nbxLogger: 0923:083846:0192 DIL E CCMMessage.send():: Error writing TCP socket 90

Usual stuff but nothing serious . Some PKTMO errors mean the tels lost site of the NBX , maybe unplugged or just for a while they could not communicate with the NBX . Daemon errors are from the syslog and are not responsible for dropped calls , as well as the other errors here .



You are also running some sort of TAPI application as the ccmreader errors are TAPI errors meaning that the connection seems to have an issue as well , maybe losing connection ? CCMReader errors could cause an issue with your application running , maybe dropped calls on this as well . we have seen this sort of error in the past , and if this is the issue then open a case up with us and we can work with you for a resolution.



You do not state what type of dropped calls , telco / internal etc . I am guessing another possible issue may be you have a PRI from your local provider and are dropping calls :



I would set up a hyperterminal ( straight cable between the NBX PRI board and a pc runninng at 9600 , 8,1,none run hyperterminal on your PC , and plug it into the PRI board and see if you get any SABM/SABME messages ( D channel reset ) . Quickest way to see if the PRI board D channel is "bouncing" , going up and down on you . Most common cause for dropped calls .

This message was edited by merlin on 9-24-09 @ 6:57 AM

Question to Merlin-- where would the reset message orginate from?

CO or NBX?

From the CO to the NBX Digital Line card ( Span ) . SABM/SABME multiframe established means the D channel shook hands with the span then restarted after the span was up and running .

co went down then up??

or nbx/pri went down then up?