Having issues after upgrading 3.1 to 3.2 Help!

[telewhore]

The company went from 3.1(55) to 3.2(69) and now they seem to be having issues with their long distance PRI as well as their incoming 800 numbers...i have a print out of a test LD call and noticed something interesting "Network out of order" but I dont know what it means any ideas?? Thanks in advance!


36780mS CMTARGET: LOOKUP CALL ROUTE:69 type=100 called_party=18472783510 sub= calling=5181 in=0 complete=0
36781mS CMTARGET: ADD TARGET:69 number=18472783510 type=100 depth=1 nobar=1 setorig=1 fwduser=
36781mS CMTARGET: OVERLAP LOOKUP CALL ROUTE:69 returned 0
40780mS CMTARGET: LOOKUP CALL ROUTE:69 type=100 called_party=18472783510 sub= calling=5181 in=0 complete=1
40780mS CMTARGET: ADD TARGET:69 number=18472783510 type=100 depth=1 nobar=1 setorig=1 fwduser=
40781mS CMTARGET: SYS SC:69 18472783510 3 8472783510 sc=type=Dial code=[9]1N;, num=1Nsi317298e
40781mS CMTARGET: LCR NOT MATCHED:69 (cpn=18472783510)
40781mS CMTARGET: DIAL LINE:69 GROUP=1 SUCCESS=1
40781mS CMTARGET: OVERLAP LOOKUP CALL ROUTE:69 returned 1
40782mS CD: CALL: 0.1138.0 BState=Idle Cut=1 Music=0.0 Aend="OpenEngr(5181)" (10.10) Bend="Line 2" [Line 2] (0.0) CalledNum=18472783510 () CallingNum=3172985181 () Internal=0 Time=9308 AState=Dialling
40783mS CMExtnTx: v=5181, p1=8
CMSetupAck
Line: type=DigitalExtn 4
Call: lid=0 id=1138 in=0
Called[18472783510] Type=Default (100)
BChan: slot=10 chan=10
Product Unknown
Display [18472783510]
Timed: 12/11/09 10:26
40784mS CD: CALL: 0.1138.0 BState=Idle Cut=1 Music=0.0 Aend="OpenEngr(5181)" (10.10) Bend="Line 2" [Line 2] (0.0) CalledNum=18472783510 () CallingNum=3172985181 () Internal=0 Time=9310 AState=Dialled
40785mS PRN: Line 2 AdjustCount 1,1 -> cur=1 out=1 v=1 d=0
40786mS PRN: Outgoing Setup Processing
40786mS PRN: Choose outgoing channel 23
40786mS PRN: TNS= sss=00000000 service=00
40786mS PRN: Setting configured voice gain for ch 23.
40787mS CMLineTx: v=2
CMSetup
Line: type=Q931Line 2
Call: lid=0 id=1139 in=0
Called[18472783510] Type=Default (100) Calling[3172985181] Type=National (2) Pres= (101)
BC: CMTC=Speech CMTM=Circuit CMTR=64 CMST=Default CMU1=ULaw
BChan: slot=0 chan=24
Product Unknown
Display [Open Engineering]
Cause=16, Normal call clearing
Locale: enu
44794mS CMLineRx: v=2
CMReleaseComp
Line: type=Q931Line 2
Call: lid=0 id=1139 in=0
Product Unknown
Cause=38, Network out of order
44794mS CD: CALL: 0.1138.0 BState=Disconnecting Cut=1 Music=0.0 Aend="OpenEngr(5181)" (10.10) Bend="Line 2" [Line 2] (0.0) CalledNum=18472783510 () CallingNum=3172985181 () Internal=0 Time=13320 AState=Dialled
44795mS PRN: CALL: 0.1138.0 Deleted leaving 1 CMCall objects
44795mS CALL:2009/11/1210:25,00:00:00,000,5181,O,18472783510,918472783510,OpenEngr,,,1,,""n/a,0
44796mS CD: CALL: 0.1138.0 BState=Idle Cut=0 Music=0.1 Aend="OpenEngr(5181)" (10.10) Bend="Line 2" [Line 2] (0.0) CalledNum=18472783510 () CallingNum=3172985181 () Internal=0 Time=13322 AState=Idle
44797mS CMExtnTx: v=5181, p1=8
CMInbandTone
Line: type=DigitalExtn 4
Call: lid=0 id=1138 in=0
Product Unknown
UUI type=User2User [TB1\r\n] [0x54 0x42 0x31 0x0d 0x0a ]
Cause=38, Network out of order
Timed: 12/11/09 10:26
44798mS PRN: Line 2 AdjustCount -1,-1 -> cur=0 out=0 v=0 d=0
44798mS CD: CALL: 0.1138.0 Deleted
44996mS CMExtnRx: v=5181, p1=8
CMShortCode
Line: type=NoLine 0
Call: lid=0 id=-1 in=0
ShortCode GetCallInfo (108) = []
Product Unknown
44996mS CMExtnTx: v=5181, p1=8
CMShortCode
Line: type=DigitalExtn 4
Call: lid=0 id=-1 in=0
ShortCode GetCallInfo (108) = []
BChan: slot=10 chan=10
Product Unknown
Timed: 12/11/09 10:26
45248mS RES: Thu 12/11/2009 10:26:06 FreeMem=46461464(7) CMMsg=5 (6) Buff=100 602 798 1004 2 Links=8843 Elements=0
45333mS CMExtnRx: v=5072, p1=28
CMSetup
Line: type=NoLine 0
Call: lid=0 id=-1 in=0
BC: CMTC=Speech CMTM=Circuit CMTR=64 CMST=Default CMU1=ULaw
Product Unknow

 

[alexdykes]

Its basically saying it can't communicate with the network. Have you contacted the carrier to help diagnose the problem? Are you getting any alarm lights on the smart jack or any alarms logged on the IPO?

Do you have one or two PRIs? If you have two, how is the network clock set on them?

 

[tlpeter]

Cause=38, Network out of order

That is the problem
Did the pri came back after the upgrade ?




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

 

[telewhore]

There are 2 PRIs..the one is question is the second one used for LD. They are both up via PRI status in Monitor. I did notice that the switch type was set to "5ESS" and the clock was set to "fallback"...I'm not sure if somehow I accidently changes these but I've always thought for most cases it should be set to NI2 and Network...so i made these changes and did a soft reboot with no new results...should i do a hard reboot? I had the customer call the provider and they are in the middle of their testing.

 

[telewhore]

Provider tested good through the smart jack so it looks like the problem is on my end..

 

[alexdykes]

One should be set to network, I would set the other to unsuitable. The switch type is something you would need to ask your carrier about. Get the carrier on the horn and run thru all the configuration options to make sure they match what they have on their end. Personally I like NI2, but we are always at the mercy of our carriers. I've had clock problems create enough framing errors that I have had similar problems.

 

[telewhore]

I verified from an old config that the 2nd PRI was set to 5ESS and fallback...should the fallback be changed to unsuitable because of the upgrade I just performed to 3.2(69)?

 

[telewhore]

haha wow, i reverted back to the old settings and did a reboot and now I'm good to go! I could have sworn that this was the original settings but I must of had syncing issues...with the csu and the system. Thanks for responding everyone!