PRI random outbound calls don't connect... 1

[CIDCrane]

Working with carrier on an issue where calls randomly fail when dialed. No problem on the inbound side. I was provided the following trap by the carrier....

Bad call

274 06112013 152222.00001:1.11.18051.Info .ISDN : Service PRI-1-11-1-24 D1 : L3 RX CREF=004a SETUP (MsgLen=39 CRLen=2 CRFlag=0[orig] IE[01]=04039090a2 IE[02]=1803a98390 IE[03]=6c0c218038303332353632333731 IE[04]=70088037373138303037)
209 06112013 152222.00002:1.11.18052.Info .ISDN : Service PRI-1-11-1-24 D1 : L3 RX CREF=004a IE[01]=BEARCAP (Coding=CCITT Cap=3.1kHz Mode=Circuit Rate=64kbps L1=G.711ulaw)
252 06112013 152222.00003:1.11.18053.Info .ISDN : Service PRI-1-11-1-24 D1 : L3 RX CREF=004a IE[02]=CHANID (IntfID=Implicit Intf=Primary Pref/Excl=Excl DChInd=N ChanSel=Ch#16 Coding=CCITT ChanInd=Num ChanType=B-ch)
245 06112013 152222.00004:1.11.18054.Info .ISDN : Service PRI-1-11-1-24 D1 : L3 RX CREF=004a IE[03]=CALLGNUM (NumType=National NumPlan=ISDN/Telephony[E.164] PresentInd=Allowed ScrnInd=None Digits=8032562371)
195 06112013 152222.00005:1.11.18055.Info .ISDN : Service PRI-1-11-1-24 D1 : L3 RX CREF=004a IE[04]=CALLDNUM (NumType=Unknown NumPlan=Unknown Digits=7718007)
274 06112013 152226.00003:1.11.18056.Info .ISDN : Service PRI-1-11-1-24 D1 : L3 RX CREF=004a SETUP (MsgLen=39 CRLen=2 CRFlag=0[orig] IE[01]=04039090a2 IE[02]=1803a98390 IE[03]=6c0c218038303332353632333731 IE[04]=70088037373138303037)
209 06112013 152226.00004:1.11.18057.Info .ISDN : Service PRI-1-11-1-24 D1 : L3 RX CREF=004a IE[01]=BEARCAP (Coding=CCITT Cap=3.1kHz Mode=Circuit Rate=64kbps L1=G.711ulaw)
252 06112013 152226.00005:1.11.18058.Info .ISDN : Service PRI-1-11-1-24 D1 : L3 RX CREF=004a IE[02]=CHANID (IntfID=Implicit Intf=Primary Pref/Excl=Excl DChInd=N ChanSel=Ch#16 Coding=CCITT ChanInd=Num ChanType=B-ch)
245 06112013 152226.00006:1.11.18059.Info .ISDN : Service PRI-1-11-1-24 D1 : L3 RX CREF=004a IE[03]=CALLGNUM (NumType=National NumPlan=ISDN/Telephony[E.164] PresentInd=Allowed ScrnInd=None Digits=8032562371)
195 06112013 152226.00007:1.11.18060.Info .ISDN : Service PRI-1-11-1-24 D1 : L3 RX CREF=004a IE[04]=CALLDNUM (NumType=Unknown NumPlan=Unknown Digits=7718007)
189 06112013 152230.00001:1.11.18061.Info .ISDN : Service PRI-1-11-1-24 D1 : L3 RX CREF=004a RELCOM (MsgLen=9 CRLen=2 CRFlag=0[orig] IE[01]=0802809f)
218 06112013 152230.00002:1.11.18062.Info .ISDN : Service PRI-1-11-1-24 D1 : L3 RX CREF=004a IE[01]=CAUSE (Coding=CCITT Location=User Cause="Normal, unspecified (31)" Class=Normal)

Good call

274 06112013 152300.00014:1.11.18110.Info .ISDN : Service PRI-1-11-1-24 D1 : L3 RX CREF=004b SETUP (MsgLen=39 CRLen=2 CRFlag=0[orig] IE[01]=04039090a2 IE[02]=1803a98390 IE[03]=6c0c218038303332353632333731 IE[04]=70088037373138303037)
209 06112013 152300.00015:1.11.18111.Info .ISDN : Service PRI-1-11-1-24 D1 : L3 RX CREF=004b IE[01]=BEARCAP (Coding=CCITT Cap=3.1kHz Mode=Circuit Rate=64kbps L1=G.711ulaw)
252 06112013 152300.00016:1.11.18112.Info .ISDN : Service PRI-1-11-1-24 D1 : L3 RX CREF=004b IE[02]=CHANID (IntfID=Implicit Intf=Primary Pref/Excl=Excl DChInd=N ChanSel=Ch#16 Coding=CCITT ChanInd=Num ChanType=B-ch)
245 06112013 152300.00017:1.11.18113.Info .ISDN : Service PRI-1-11-1-24 D1 : L3 RX CREF=004b IE[03]=CALLGNUM (NumType=National NumPlan=ISDN/Telephony[E.164] PresentInd=Allowed ScrnInd=None Digits=8032562371)
195 06112013 152300.00018:1.11.18114.Info .ISDN : Service PRI-1-11-1-24 D1 : L3 RX CREF=004b IE[04]=CALLDNUM (NumType=Unknown NumPlan=Unknown Digits=7718007)
192 06112013 152300.00050:1.11.18115.Info .ISDN : Service PRI-1-11-1-24 D1 : L3 TX CREF=004b CALLPROC (MsgLen=10 CRLen=2 CRFlag=1[dest] IE[01]=1803a98390)
252 06112013 152300.00051:1.11.18116.Info .ISDN : Service PRI-1-11-1-24 D1 : L3 TX CREF=004b IE[01]=CHANID (IntfID=Implicit Intf=Primary Pref/Excl=Excl DChInd=N ChanSel=Ch#16 Coding=CCITT ChanInd=Num ChanType=B-ch)
189 06112013 152301.00001:1.11.18117.Info .ISDN : Service PRI-1-11-1-24 D1 : L3 TX CREF=004b ALERT (MsgLen=9 CRLen=2 CRFlag=1[dest] IE[01]=1e028288)
199 06112013 152301.00002:1.11.18118.Info .ISDN : Service PRI-1-11-1-24 D1 : L3 TX CREF=004b IE[01]=PROGIND (Coding=CCITT Loc=Pub[local] ProgDes=InBandInfoAvail)
189 06112013 152313.00001:1.11.18128.Info .ISDN : Service PRI-1-11-1-24 D1 : L3 TX CREF=004b CONN (MsgLen=9 CRLen=2 CRFlag=1[dest] IE[01]=1e028282)
199 06112013 152313.00002:1.11.18129.Info .ISDN : Service PRI-1-11-1-24 D1 : L3 TX CREF=004b IE[01]=PROGIND (Coding=CCITT Loc=Pub[local] ProgDes=NonISDNDestAddr)
173 06112013 152313.00003:1.11.18130.Info .ISDN : Service PRI-1-11-1-24 D1 : L3 RX CREF=004b CONNACK (MsgLen=5 CRLen=2 CRFlag=0[orig])
189 06112013 152618.00001:1.11.18370.Info .ISDN : Service PRI-1-11-1-24 D1 : L3 RX CREF=004b DISC (MsgLen=9 CRLen=2 CRFlag=0[orig] IE[01]=08028090)
214 06112013 152618.00002:1.11.18371.Info .ISDN : Service PRI-1-11-1-24 D1 : L3 RX CREF=004b IE[01]=CAUSE (Coding=CCITT Location=User Cause="Normal clearing (16)" Class=Normal)
173 06112013 152618.00003:1.11.18372.Info .ISDN : Service PRI-1-11-1-24 D1 : L3 TX CREF=004b REL (MsgLen=5 CRLen=2 CRFlag=1[dest])
173 06112013 152618.00004:1.11.18373.Info .ISDN : Service PRI-1-11-1-24 D1 : L3 RX CREF=004b RELCOM (MsgLen=5 CRLen=2 CRFlag=0[orig])

the pbx is failing the call (note from carrier tier 2)

Carrier telling me that I am sending two call set ups on the failed call. On the failed call I never see a call proceeding message from the carrier. Does this look like a pbx issue or a carrier issue? thanks

 

[Nortel4Ever]

Using System Status are you able to determine if a failed call always uses the same channel on the PRI card as opposed to a good call?
If possible try replacing the PRI card and if the issue goes unresolved you have some ammo to point back to the Telco.

 

[CarGoSki]

Why would you EVER spend money to solve a issue when proper troubleshooting has not been performed. With that type of troubleshooting why not insist that telco change out all smart cards - cable pairs- coils in the street - mux or their central office switch.

How about start sysmon traps with ISDN traces on and have the site keep a log of the events.
Also good Q&A is in order.
How long has this issue occurred?
Weather related?
Power outage?
New install?
Changing providers?

What release and control unit is IPO?

etc
etc
etc
etc
etc

 

[CIDCrane]

Sorry, kept it brief before.
Issue started about 10 days ago but they just involved me today. Carrier has been running traps. I have used monitor and it occurs on the same channel on the IP Office. But the good calls are also going out on the same channel as the bad calls. System is old, 406 V2 running 3.2.69. Same carrier for last five years, no change there that I am aware of. Monitor says system up and running for 47 days so power to PBX doesn't appear to be an issue. My thinking is to replace the PRI module to prove my point to the carrier at a vendor meet. The absence of a call proceeding message got me thinking it may be the carrier. Have about 450 PRIs out in the field and haven't lost one yet, but there is always a first, have my doubts though. thanks

 

[tlpeter]

The bad call gives a Cause="Normal, unspecified (31)" Class=Normal

This means cause=31

I think i saw this recently and i tried to send a call over a channel (i used etsi chi) and tried to send a number that i do not own at that pri.

So try to see if you are trying to send a CLI out that is not of this customer.

Can you make a monitor trace as this is not really a good trace to see what happens.


BAZINGA!

I'm not insane, my mother had me tested!

 

[CarGoSki]

31 1F Normal, Unspecified.
This is a very common cause code and happens when the network is not able to determine what to do
with the call being made

You really need to examine a sysmon trace with ISDN traces on.