Cause 38, network out of order

[deltaserver403]

When i make call on ISDN PRI E1 - 30 channels, after some time it get cut, i get eror cause 38 , network out of order,
this problem from Service provider or the PABX system,

I told service provider he is telling his part is ok may be problem with the PABx but PABx guy tells this problem due to Service provider i am bit confused pls can any body tell where the problem lies & what is this cause 38 - Network out of order

Thanks in Advance

 

[johnpoole]

very ambiguous err code, basicly says the pbx can't see the netework. we could help if we knew the the switch type. you need a loop back from the demark to the switch to see if the red alarm goes away.. you also need to stat that e1 to get a more detailed trouble discription... two basic trouble alarms red and/or yellow alarms. red is layer one, yellow is layer 7.. because both ends want to point the finger instead of fixing the problem, call the provider and the vendor, request a vendor meet. both techs on line with the vendor on site.. at my site a e1(t1) problem has an automatic one hour repair window, i can't leave the site unless the provider agrees that the trouble is his problem.. i would be looking for a new vendor, quickly

john poole
bellsouth business
columbia,sc

 

[johnpoole]

very ambiguous err code, basicly says the pbx can't see the network. we could help if we knew the the switch type. you need a loop back from the demark to the switch to see if the red alarm goes away.. you also need to stat that e1 to get a more detailed trouble discription... two basic trouble alarms red and/or yellow alarms. red is layer one, yellow is layer 7.. because both ends want to point the finger instead of fixing the problem, call the provider and the vendor, request a vendor meet. both techs on line with the vendor on site.. at my site a e1(t1) problem has an automatic one hour repair window, i can't leave the site unless the provider agrees that the trouble is his problem.. i would be looking for a new vendor, quickly

john poole
bellsouth business
columbia,sc

 

[johnpoole]

guess that was an echo

john poole
bellsouth business
columbia,sc

 

[TripleT]

Another little hint is that in the Cause IE there is a Location Field. This can tell you where the Cause has been generated from.

Basically here are the options: -

0000 User The handset if it is an ISDN Phone.
0001 Private Netork serving the local User, You local Private PABX Network.
0010 Public Network Serving the local User, The Public Exchange you are connected to.
0011 Transit Network, Any where in the Public Network between your local Exhange and the other ends Exchange.
0100 Public Network Serving the Remote User, The exchange that the other end is connected to.
0101 Private Network Serving the Remote User, The remote PABX or Private Network.
0111 International Network, Somewhere outside your own Country.
1010 Network Beyond Interworking Point. Somewhere after the ISUP Network finishes and the call transists to a Dumber Network.

This can be useful when trying to find the source.

 

[ISDNman]

Amen tripleT. That location filed is VERY useful.

Deltaserver403 - Can your equipment capture an ISDN protocol trace? If so, capture a call setup that results in the cause 38.

This is not a very common cause code.

Good luck

 

[ISDNman]

What is the protocol and switch?

If it happens to be NI-2 on a DMS, and the cause is coming from the PBX then this thread might be the clue:

http://www.tek-tips.com/viewthread.cfm?qid=997953&page=1

 

[johnpoole]

intel by harris, looks like. not one of my favorites, drop down windows are good but other gate openers define the drop down choices, and those gate openers are hidden elsewhere. maybe if i had one to maintain i could get used to it

john poole
bellsouth business
columbia,sc