Dropped calls on IPO4

[573dawn]

Hi All, our system is dropping calls all over the place, and we cannot seem to discover why. Our BP has finally taken some logs and sent them off to Avaya. We have replaced our main DS unit, replaced the cat5 cable back to the PRI, SBC says the circuit tests clean, and I can't correlate the drops to network events.

One thing I have seen in Monitor (which I can barely read) is CALL DELETED. The DS units don't appear to be rebooting every time, although we do have somewhat of an issue there.

I am at a loss and we're headed into our biggest volume weekend of the year, so we're in trouble if we can't figure this one out.

Thanks, Dawn

 

[tlpeter]

call deleted is a normal thing
if i call you and hang up you will this in monitor
so that is no thing to worry about at all
can you put a trace here ???
it is hard to tell what it is just over the internet
if i could then i would be very rich

ACA - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[573dawn]

tlpeter, thanks How do I do a trace on the phone system and what should it tell me?

 

[tlpeter]

run monitor

then enter the ip adres of the ip office with the password (if it is changed,if not then password as password)

then go to filters and tab isdn
check layer 1,2 and 3

then let it run
then when you have a dropped call stop the trace and save it
search for the time when the call dropped and put it overhere with a minute or 2 before the dropped call



ACA - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[573dawn]

Shall do.

 

[573dawn]

Ok, here we go:
Timed: 29/06/07 13:19
92364497mS CMTARGET: 10.625.1 860 H323TrunkEP: TimerExpired cause=4
92364497mS CMTARGET: 10.625.1 860 H323TrunkEP: GetNoAnswerTimer:25
92364502mS CMLineTx: v=3
CMSetup
Line: type=AnalogueLine 3 Call: lid=0 id=4256 in=0
Called[6920371] Type=Unknown (0) Reason=CMDRdirect Calling[3147430001] Type=Unknown Plan=ISDN Pres=Allowed (0)
BC: CMTC=Speech CMTM=Circuit CMTR=64 CMST=Default CMU1=ULaw
IE CMIECalledPartyName (224) Ken Smith
IE CMIEOriginalCalledPartyName (236) Ken Smith
IE CMIEOriginalCalledPartyNumber (238)(P:100 S:100 T:101 N:100 R:4) number=506
IE CMIERedirectingPartyName (232) Ken Smith
IE CMIERedirectingPartyNumber (234)(P:100 S:100 T:101 N:100 R:4) number=506
IE CMIEIcrPriorityDetail (239) Priority = 1
92364555mS CMLineRx: v=3
CMSetupAck
Line: type=AnalogueLine 3 Call: lid=0 id=4256 in=0
BChan: slot=2 chan=3
IE CMIERespondingPartyNumber (230)(P:100 S:100 T:0 N:100 R:4) number=6920371
IE CMIEDeviceDetail (231) LOCALE=enu HW=8 VER=4 class=CMDeviceAlogTrunk type=0 number=3 channel=0 gain=0
92364555mS CMARS: LINE ep Received: CMSetupAck - child->state = CMCSOffering - ARS Call State = CMCSOverlapRecv
92364555mS CMTARGET: TargetOnProgress: res: 0
92364557mS PRN: Windowed EchoCancellation started: chunnel=1, command= 0x8401
92367426mS RES: Fri 29/6/2007 13:19:41 FreeMem=46673952(67) CMMsg=7 (8) Buff=100 584 500 1092 5 Links=9431
92368504mS CD: CALL: 10.625.1 State=1 Cut=1 Music=2.0 Aend="Line 10" (0.0) Bend="" [Ken Smith(506),Ken Smith(506)] (0.0) CalledNum=506 (Ken Smith) CallingNum=3147430001 () Internal=0 Time=14020 AState=1
92368695mS CMLineRx: v=3
CMProgress
Line: type=AnalogueLine 3 Call: lid=0 id=4256 in=0
BChan: slot=2 chan=3
IE CMIEProgressIndicator (30) cs=CMCSITUT (0), loc=CMLUser (0), pd=CMPDNotISDN (1)
IE CMIERespondingPartyNumber (230)(P:100 S:100 T:0 N:100 R:4) number=6920371
IE CMIEDeviceDetail (231) LOCALE=enu HW=8 VER=4 class=CMDeviceAlogTrunk type=0 number=3 channel=0 gain=0
92368695mS CMARS: LINE ep Received: CMProgress - child->state = CMCSOverlapRecv - ARS Call State = CMCSOverlapRecv
92368696mS CMTARGET: TargetOnProgress: res: 0
92368696mS CMTARGET: TargetOnProgress: res: 0
92368697mS CMLineRx: v=3
CMAlerting
Line: type=AnalogueLine 3 Call: lid=0 id=4256 in=0
BChan: slot=2 chan=3
IE CMIERespondingPartyNumber (230)(P:100 S:100 T:0 N:100 R:4) number=6920371
IE CMIEDeviceDetail (231) LOCALE=enu HW=8 VER=4 class=CMDeviceAlogTrunk type=0 number=3 channel=0 gain=0
IE CMIERedirectingPartyName (232) Ken Smith
IE CMIERedirectingPartyNumber (234)(P:100 S:100 T:101 N:100 R:4) number=506
92368697mS CMARS: LINE ep Received: CMAlerting - child->state = CMCSAccept - ARS Call State = CMCSAccept
92368697mS CMTARGET: TargetOnProgress: res: 0
92368698mS CMLineRx: v=3
CMConnect
Line: type=AnalogueLine 3 Call: lid=0 id=4256 in=0
BChan: slot=2 chan=3
IE CMIERespondingPartyNumber (230)(P:100 S:100 T:0 N:100 R:4) number=6920371
IE CMIEDeviceDetail (231) LOCALE=enu HW=8 VER=4 class=CMDeviceAlogTrunk type=0 number=3 channel=0 gain=0
IE CMIERedirectingPartyName (232) Ken Smith
IE CMIERedirectingPartyNumber (234)(P:100 S:100 T:101 N:100 R:4) number=506
92368698mS CMARS: LINE ep Received: CMConnect - child->state = CMCSRinging - ARS Call State = CMCSRinging
92368699mS CMTARGET: 10.625.1 860 H323TrunkEP: CancelTimer CMTCNoAnswerTimeout
92368701mS CMExtnTx: v=506, p1=0
CMReleaseComp
Line: type=DigitalExtn 3 Call: lid=0 id=4254 in=0
Cause=124, Answered By Other(IPO)
Timed: 29/06/07 13:19
92368703mS CMARS: CMARSEndpoint::CallLost(cause=124) - Address: 0.4255.0 860 ARS for [8] - Call State: CMCSRinging
92368703mS CMARS: ~CMARSEndpoint() - Address: fec7f4a4
92368705mS CMLineTx: v=10
CMConnect
Line: type=IPLine 10 Call: lid=10 id=625 in=1
BChan: slot=2 chan=3
IE CMIERespondingPartyNumber (230)(P:100 S:100 T:0 N:100 R:4) number=6920371
IE CMIEDeviceDetail (231) LOCALE=enu HW=8 VER=4 class=CMDeviceAlogTrunk type=0 number=3 channel=0 gain=0
IE CMIERedirectingPartyName (232) Ken Smith
IE CMIERedirectingPartyNumber (234)(P:100 S:100 T:101 N:100 R:4) number=506
92368709mS CD: CALL: 10.625.1 State=2 Cut=3 Music=0.0 Aend="Line 10" (0.0) Bend="" [Line 3] (2.3) CalledNum=6920371 (Ken Smith) CallingNum=3147430001 () Internal=0 Time=14225 AState=2
92368711mS CMMap: a=0.0 b=0.0 pcp[270]b0r1 RTPR0
92368712mS CMMap: PCG::MapBChan pcp[270]b0r1 cp_b 0 other_cp_b 0 type CGTypeSimple
92368712mS CMMap: PCGS CPReserveCodec for the other end (pcp[270]b0r1) true
92368712mS CMMap: PCG::MapBChan pcp[70]b1r0 cp_b fee88892 other_cp_b fee8fb4a type CGTypeSimple
92368712mS CMMap: a=3.6 b=2.3 M1
92368716mS H323Evt: v=0 stacknum=10 State, new=Active, old=Received id=625
92368725mS CMLineRx: v=10
CMConnectAck
Line: type=IPLine 10 Call: lid=10 id=625 in=1
92368725mS CMTARGET: 10.625.1 860 H323TrunkEP: ~CMTargetHandler
92368730mS CMLineTx: v=3
CMConnectAck
Line: type=AnalogueLine 3 Call: lid=0 id=4256 in=0
Called[] Type=Default (100) Reason=CMDRdirect Calling[3147430001] Type=Unknown Plan=ISDN Pres=Allowed (0)
92368733mS PRN: Windowed EchoCancellation stopped: chunnel=1, command= 0x401
92368751mS CMLineRx: v=10
CMFacility
Line: type=IPLine 10 Call: lid=10 id=625 in=1
92368752mS CMLineTx: v=3
CMFacility
Line: type=AnalogueLine 3 Call: lid=0 id=4256 in=0
92368933mS CMLineRx: v=10
CMFacility
Line: type=IPLine 10 Call: lid=10 id=625 in=1
92368935mS CMLineTx: v=3
CMFacility
Line: type=AnalogueLine 3 Call: lid=0 id=4256 in=0
92368956mS CMLineRx: v=10
CMFacility
Line: type=IPLine 10 Call: lid=10 id=625 in=1
92368960mS CMLineTx: v=3
CMFacility
Line: type=AnalogueLine 3 Call: lid=0 id=4256 in=0
92368960mS CMLineRx: v=10
CMFacility
Line: type=IPLine 10 Call: lid=10 id=625 in=1
IE CMIERespondingPartyNumber (230)(P:0 S:3 T:0 N:1 R:4) number=3147430001
IE CMIEDeviceDetail (231) LOCALE=enu HW=8 VER=4 class=CMDeviceISDNTrunk type=2 number=5 channel=2 gain=0
IE CMIERedirectingPartyName (232) Ken Smith
IE CMIERedirectingPartyNumber (234)(P:100 S:100 T:101 N:100 R:4) number=506
92368961mS CMLineTx: v=3
CMFacility
Line: type=AnalogueLine 3 Call: lid=0 id=4256 in=0
IE CMIERespondingPartyNumber (230)(P:0 S:3 T:0 N:1 R:4) number=3147430001
IE CMIEDeviceDetail (231) LOCALE=enu HW=8 VER=4 class=CMDeviceISDNTrunk type=2 number=5 channel=2 gain=0
IE CMIERedirectingPartyName (232) Ken Smith
IE CMIERedirectingPartyNumber (234)(P:100 S:100 T:101 N:100 R:4) number=506
92368962mS CMLineRx: v=10
CMFacility
Line: type=IPLine 10 Call: lid=10 id=625 in=1
IE CMIESupplementaryService (3)
Interpretation APDU
rejectAnyUnrecognisedInvokePdu
CallTransferComplete.Invoke.CodePageUnknown
invokeId 15949
redirection name '' redirection number '3147430001' primary end answered
IE CMIERespondingPartyNumber (230)(P:0 S:3 T:0 N:1 R:4) number=3147430001
IE CMIEDeviceDetail (231) LOCALE=enu HW=8 VER=4 class=CMDeviceISDNTrunk type=2 number=5 channel=2 gain=0
IE CMIERedirectingPartyName (232) Ken Smith
IE CMIERedirectingPartyNumber (234)(P:100 S:100 T:101 N:100 R:4) number=506
92368963mS CMLineTx: v=3
CMFacility
Line: type=AnalogueLine 3 Call: lid=0 id=4256 in=0
IE CMIERespondingPartyNumber (230)(P:0 S:3 T:0 N:1 R:4) number=3147430001
IE CMIEDeviceDetail (231) LOCALE=enu HW=8 VER=4 class=CMDeviceISDNTrunk type=2 number=5 channel=2 gain=0
IE CMIERedirectingPartyName (232) Ken Smith
IE CMIERedirectingPartyNumber (234)(P:100 S:100 T:101 N:100 R:4) number=506
92368965mS CMMap: a=2.3 b=0.0 PCGS CPReserveCodec (pcp[270]b0r1) true
92368965mS CMMap: PCG::MapBChan pcp[270]b0r1 cp_b fee8fb4a other_cp_b fee88892 type CGTypeSimple
92368965mS CMMap: a=2.3 b=3.6 M1
92458720mS CMLineRx: v=10
CMFacility
Line: type=IPLine 10 Call: lid=10 id=625 in=1
92458721mS ERR: EXCEPTION ON MEDIA CONNECTION --- Error from protocol entity! MSDSE --- local timer expired ...
92458722mS CMLOGGING: CALL:2007/06/2913:19,00:01:30,014,3147430001,I,506,506,,,,1,,""n/a,0
92458723mS CD: CALL: 10.625.1 State=2 Cut=3 Music=0.0 Aend="Line 10" (0.0) Bend="" [Line 3] (2.3) CalledNum=6920371 (Ken Smith) CallingNum=3147430001 () Internal=0 Time=104239 AState=2
92458723mS CD: CALL: 10.625.1 Deleted
92458725mS CMLineTx: v=10
CMReleaseComp
Line: type=IPLine 10 Call: lid=10 id=625 in=1
Cause=2, No route to specific transit network/(5ESS)Calling party off hold
92458731mS CMLineTx: v=3
CMFacility
Line: type=AnalogueLine 3 Call: lid=0 id=4256 in=0
92458738mS CMMap: PCG::UnmapBChan pcp[70]b1r0 cp_b fee88892 other_cp_b fee8fb4a
92458738mS CMMap: a=3.6 b=2.3 M0
92458738mS CMMap: PCG::UnmapBChan pcp[270]b0r1 cp_b 0 other_cp_b 0
92458740mS CMMap: a=3.6 b=0.0 Mapper::FreeCodec freed CMRTVocoder resource busy 0, total 8
92458741mS H323Evt: v=0 stacknum=10 State, new=ReleaseReq, old=Active id=625
92458742mS H323Evt: v=0 stacknum=10 State, new=NullState, old=ReleaseReq id=625
92458746mS PRN: Windowed EchoCancellation started: chunnel=1, command= 0x8401
92458926mS RES: Fri 29/6/2007 13:21:13 FreeMem=46721000(83) CMMsg=7 (8) Buff=100 584 499 1092 5 Links=9507
92460748mS PRN: Windowed EchoCancellation stopped: chunnel=1, command= 0x501
92463926mS RES: Fri 29/6/2007 13:21:18 FreeMem=46722708(83) CMMsg=7 (8) Buff=100 584 499 1092 5 Links=9508

********** contact lost with 192.168.3.180 at 13:22:12 29/6/2007 - reselect = 238 **********
******************************************************************


********** SysMonitor v6.0 (5) **********

********** contact made with 192.168.3.180 at 13:22:12 29/6/2007 **********

********** System (192.168.3.180) has been up and running for 1day, 1hr, 41mins and 58secs(92518077mS) **********

 

[tlpeter]

i did a quick look and saw these two things


92458721mS ERR: EXCEPTION ON MEDIA CONNECTION --- Error from protocol entity! MSDSE --- local timer

Cause=2, No route to specific transit network/(5ESS)Calling party off hold


ACA - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[573dawn]

I saw those too, but I don't know what they mean in relation to the phone system. My vendor thinks we are having time slips on the PRI, and wants me to have SBC switch over th the backup circuit.

Also, and I hadn't thought of this, but a few weeks ago a careless worker with an industrial lawn mower took out one of our PTP T1's, the one to the location with the most problems. ATT spliced the line and covered the pedestal with a trash bag (really).

 

[tlpeter]

so the cable is repared temporarly ?
then first call the provider and let them fixe it
a little bit of fog has influence on your lines

but another thing,how can somebody damage the cablewith a lawnmower ?
the cable should be in the ground deep enough or in the air
this is to ipmortant for your company
so call your provider and if they are not comingcall your boss and let him call again


ACA - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[573dawn]

tlpeter, you would have to see the lawnmower. It is actually a tractor with a huge moving arm attached with a blade unit about 4-5' across. They can move this thing up and down and in or out depending on the terrain. Where I am is extremely rocky, so many lines are above ground because no one wants to pay to dig into solid rock. SO, the phone company has a "pedestal" right near the road where the copper (I am assuming) converges from the CO. When the county sent their mowers, they hit the pedestal with the blade, severing our T1 and damaging the pedestal. In the words of the ATT rep who showed up, "they chewed it up pretty good". I will see what I can find out regarding why it is still sitting there with a trashbag taped over it and see if I can actually get them to something about it. I can see that today there is a regular "lost connection" to the DS unit (but it isn't rebooting), although no one has called me about drops this morning, I think they are suffering from "drop fatigue" and just don't bother telling every time.

Did I mention is has been raining for days? Or that the location of the pedestal is on a downslope where water could easily run down the hill to it?

On the other hand, I'm not seeing carrier transitions or interface resets, and have a low incidence of T1 errors to that location.

 

[tlpeter]

you did not mention the rain
but that has a big influence on your cable
just keep complaining to your provider because the temporary solution will keep giving problems


ACA - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[573dawn]

I can do that. I have now been informed that a different location is getting alot of drops as well. It has been suggested that we have SBC go to the back-up circuit for the PRI, just to see what happens. I can also tell you that cable cuts are fairly common here, because there is a great deal of new construction and road improvements. We've had more than our share of them in the last year, including one so bad to this location that they knocked out every business and home for about 3 miles up and down this road and several connecting roads. Cable, POTS, T1, they got them all. Who knows how well that was repaired?

As for the rain, the ground is completely saturated, and our problems seem to have increased over the last few days. We have many flood advisories and the parking lot here this morning was so flooded that my hubby had to pull right up to the stairs for me. The PRI & PTPs come in here underground, but last year one of our people cut one and ATT had to splice it. The area where this occurred always collects a big puddle when the weather is like this. I am thinking that maybe we have a severe water problem right now, and it just keeps raining. Hopefully it will stop by tomorrow, but meanwhile I'm going to look over the logs on all of my DS units and see if I can see some of the same things the log above showed.

Thanks again, Dawn

 

[573dawn]

While talking to SBC just now, I was dropped. I immediately went to my Monitor log, and it had no alarms, just the "call deleted" and of all things showed "normal call clearing". ??????????????????

 

[kurthansen]

Dawn,

Check SSA it will show slips in the alarm, line section under 24hr performance. Also it will show when you have different alarms on the T1.

 

[573dawn]

kurthansen, I don't see alarms for every lost call. The occasional alarm yes, but not to the degree we are losing calls. Some people are reporting that they usually lose their calls at about 2 minutes into the call. I am at a loss.

This morning ATT replaced a repeater on the PRI, we shall see how that works out.

Thanks, Dawn

 

[kurthansen]

You should see no alarms under the lines. If you do then the carrier needs to get it fixed.

Also make sure you don't see any slips or other errors under the 24hr performance tab. Those won't show up as an alarm but will cause calls to drop and some times cause noise on the line.

 

[573dawn]

Hi kurthansen, I don't see a 24-hour tab, there is just one screen. Am I looking in the wrong place?

I have already had several drops this morning despit the changes ATT made. On at least one of them I can see the EXCEPTION ON MEDIA CONNECTION error, is this definitely indicative of a carrier issue? We are starting to really lean on ATT.

Thanks, Dawn

 

[kurthansen]

Go to the alarms section then trunks and pick the line that your T1/PRI is on. Then you will see the alarms on that trunk. If the alarms are black that means they are not happening now but if they are red then you are experiencing the alarm. That is also where the 24 hr performance history tab is located. There should be nothing in there.

For some reason in 4.0 it seems you can't see slips on Monitor only SSA.

 

[573dawn]

kurthansen, I can see the line out od service for this morning when we intentionally took it down. Otherwise, I see nothing.

On the other hand, I just had a call from my 1mm location having lost a call, and there in Monitor is the EXECPTION, and a "no route to specific transport network/(5ESS) calling party off hold".

Does this sound like it is more likely my network or the carrier?

 

[kurthansen]

5ESS would be a T1/PRI error I would think.